RISER NATION CORP

IF YOU AREN'T BUILDING, YOU ARE DESTROYING

03.1 Define the Outcome, Obstacles and Value Equation — Part 1 of 2

Study this lesson in sequence. The teaching, practical work, supporting documents and complete available source appendices stay assigned to the original lesson.

Lesson video
Recording to be added

03.1 Define the Outcome, Obstacles and Value Equation

A high-value offer starts with the result the customer wants and the obstacles that make it hard to achieve. The value equation gives us a practical way to inspect those obstacles.

Lesson outline

  1. Define the result precisely
  2. Apply the four value levers
  3. Separate evidence from claims
  4. REALTORS-ALPHABET SOUP
  5. Demonstration
  6. Implementation
  7. Completion standard

Opening

A high-value offer starts with the result the customer wants and the obstacles that make it hard to achieve. The value equation gives us a practical way to inspect those obstacles.

Keep your current business example and supporting documents open as you work. The purpose of this lesson is to produce an observable result that you can inspect and improve.

Define the result precisely

Describe the desired change, how it will be observed, and the customer’s starting conditions. Separate the result from the format: videos, calls, and templates are delivery choices. Build an obstacle list covering what happens before purchase, during implementation, and after the initial result. Link each obstacle to customer evidence.

Apply the four value levers

Hormozi’s value equation focuses attention on the desired outcome and the perceived likelihood of achieving it, relative to time delay and effort or sacrifice. Use it as a design lens, not a guaranteed numerical prediction. Improve confidence through demonstration and support, shorten avoidable delays, and remove unnecessary work without hiding what the customer must do.

Separate evidence from claims

For each promise, identify the proof you have and the conditions it depends on. A sample demonstrates capability; a case study shows what happened in a particular context. Neither establishes that every customer will get the same result. Keep source worksheet targets and scoring thresholds identifiable as their own rubric rather than universal business facts.

Build a customer profile from evidence, not imagined motives

Bring the selected Problem Map into this lesson. The source is legacy Course 7, fifth on the First Revenue Path; retain the current spreadsheet assignments. Demographics describe context, while psychographics explore goals, experiences, beliefs and language. Neither determines an individual's behavior. The document's claims about every purchase being emotional, three-to-five-times conversion and universally lower refunds are not substantiated by a study in the source.

Use five evidence streams and all six profile layers

The source ranks personal experience, interviews, communities, reviews and secondary research. Personal experience can suggest questions but can also cause projection; triangulate it instead of automatically treating it as the most accurate evidence. Use permissioned, relevant information and identify a persona as a composite when it combines people. Never turn a composite into a supposed customer testimonial.

Layer one is the surface: concrete goals, frustrations in the person's words and daily context. Ask what outcome they want, what recently prevented it, and when and where the difficulty happens. Three clients at $3,000 is an illustrative goal, not a customer result. Preserve the original expression in the research bank; keep polished copy and reconstructed examples separate.

Layer two is failed solutions. Separate paid products or programs, do-it-yourself attempts and results that were achieved but not sustained. For each, ask why it was selected, what happened, what was missing, what partially helped, how long the improvement lasted, what came next and what a new solution must avoid. Prior spending is evidence of that purchase, not a guarantee of another. Do not promise permanent outcomes merely because the prior solution did not last.

Layer three combines six fears and three desire levels. The fears concern losing money, wasting time, feeling incapable, making the wrong choice, unwanted consequences of success and being judged. Respond with truthful terms, realistic workload, appropriate support, a clear selection rationale, honest tradeoffs and room to decide. Do not intensify shame or fabricate urgency. Separate the surface desire, its practical consequence and the desired identity. The source's $20,000-per-month, family-time and professional-control chain illustrates questioning; it does not authorize inferring a hidden desire as fact.

Layer four covers five belief categories: self-efficacy, beliefs about the solution category, timing, identity fit and how the world works. Ask what the person believes and what experience supports it. Distinguish beliefs affecting purchase from those likely to block implementation in week three. Low, medium and high self-efficacy are planning categories, not diagnoses. Identify at least two implementation beliefs and design support or prerequisites around them. Timing appears in the six-layer teaching but is missing from the final deliverable and Airtable list; add it explicitly as a documented schema correction.

Layer five is the language bank. Collect from interviews, Reddit or forums, Amazon reviews across ratings, your own actual before state and the existing Problem Statement Library. A highly upvoted phrase or the first three words of a comment are possible creative inputs, not proven hooks. Deduplicate evidence and distinguish frequency among independent people from repeated copying. Private exact quotations belong in an appropriately restricted research bank; use permissioned quotation or attributed paraphrase in public lessons and marketing.

Layer six is awareness. Schwartz's five stages are unaware, problem aware, solution aware, product aware and most aware. Match content to the current question: symptoms and context; the problem and causes; approaches and mechanisms; the specific offer and credible comparison; or the final decision and clear invitation. These stages can overlap and people can move backward or skip stages. They are not the same as the six-stage customer journey in the Search Listening worksheet.

Reconcile the language and awareness numbers

The source asks for fifty entries: fifteen problem statements, ten failed-solution statements, fifteen desired outcomes and ten identity statements. That totals fifty across four categories. Its database adds social-proof seeking as a fifth category, while the signoff elsewhere only requires thirty direct phrases. Use the stricter fifty-entry target with the four stated quotas, and add the fifth category when authentic evidence exists. If only thirty are available, disclose the shortfall rather than inventing twenty. Early collection of five entries in each of five categories yields twenty-five seed entries, not the completed fifty-entry bank.

Three direct phrases per three hundred words and a seventy/thirty language ratio are different editorial rules with different units; the latter lacks a clear denominator. Treat them as optional source heuristics, not conversion laws or permission to overquote customers. The claimed awareness distribution of 60–70%, 20–25% and 5–15% can total anywhere from 85% to 110% and is not a measured audience distribution. Allocate content using your actual research and results.

Define fit without blaming the customer

The negative-avatar section names expectation mismatch, passive consumption, missing prerequisites, value extraction and perpetual research. Translate those labels into observable requirements: realistic outcomes, willingness and capacity to perform essential work, necessary access or skill, appropriate use of resources and readiness for this offer. Consider support and accessibility needs rather than equating constraints with bad character. A critical customer is not automatically a poor fit. The source's assertions of zero results for entire categories are unsupported.

Produce the complete profile and linked bank

The seven deliverable sections are surface reality; failed solutions; fears and desires; beliefs, including timing; language; awareness; and negative-avatar fit criteria. The header needs a persona name, selected problem, version, date and next review at twenty buyers or six months. That review trigger is not proof of validation.

The proposed Profile table needs AVA ID, name, linked problem, document version, surface goals, frustration, context, top three failed solutions and failure modes, top three fears, three desire levels, self-efficacy category, category beliefs, identity beliefs, world beliefs, timing beliefs, implementation beliefs, primary awareness, negative-fit exclusions, prerequisites, research basis and last and next review dates. The original primary-awareness field only offers stages one through three because it is top-of-funnel focused; do not erase known stage-four or stage-five customers. Extend the field or record later-stage evidence separately.

The Language Bank needs LB ID, exact phrase, one of five categories, source type, reference, frequency, awareness group 1–2/3/4–5, Used In and linked avatar. Used In includes hooks, email, sales pages, ads, courses and Other. Link the actual asset and distinguish drafted from deployed use.

The source routes the profile to legacy courses 12, 15, 17, 19, 21 and 25 for outcomes, hooks, narrative, FAQs, identity and sales pages, plus the Negative Avatar SOP and content calendar. Map these functions to the current curriculum without inventing missing legacy lessons or claiming the separate SOP was recovered.

Follow the build and refresh rhythm

Week five days one and two develop surface and failed-solution evidence using five interviews. Day three develops fears, three desire levels and twenty-five seed language entries. Day four develops beliefs and at least two implementation barriers. Days four and five complete the fifty-entry bank using all available evidence streams; mark personal before-state evidence not applicable if it does not exist. Day five records awareness, at least three fit exclusions and prerequisites, then prepares mentor review.

After the first five buyers, review the first thirty days of support and delivery evidence. After each cohort of ten to twenty, update failure patterns and language. Review after a meaningful competitor, platform or economic change. Every six months, conduct three to five fresh interviews. Preserve prior versions and record what changed and why. Brunson's message progression should match awareness; Hormozi's value dimensions help convert actual desired outcomes and obstacles into an honest offer. Submit the seven-section profile, linked language bank, evidence gaps and next review date.

Complete available assigned-document reference

The following preserves the supplied document text for critical study. Historical claims and embedded prompts are not RISER promises or instructions to execute. The linked external video is studied through the original adaptation above; its full transcript is not reproduced here.

word/document.xml RISER NATION MASTER OPERATING SYSTEM — COURSE 7 — TRACK 2: FIND YOUR MARKET SOP — PSYCHOGRAPHIC DNA The Complete System for Building a Deep Buyer Intelligence Profile — The Six Psychographic Layers, the Language Mining Protocol, the Fear and Desire Mapping System, the Identity and Belief Architecture, the Buying Decision Psychology, the Awareness Stage Framework, and the Psychographic DNA Document That Powers Every Downstream Marketing Asset ⭐ First Revenue Path — Course 5 of 10 | 2026 Framework Version 1.0 | 2026 Edition | RISER Nation Master Operating System SOP Overview — Why Demographics Are a Starting Point and Psychographics Are the Strategy Most operators spend significant time defining who their buyer is in demographic terms: age range, gender, income bracket, job title, geography. This information is useful for targeting but useless for persuasion. Knowing that your buyer is a 38-year-old female entrepreneur with $80,000 in annual revenue tells you where to find them. It tells you nothing about what they are afraid of, what they have already tried, what they secretly believe about themselves and their situation, what language they use when they are most frustrated, or what specific outcome would make them feel that this purchase was the best decision they have ever made. Psychographics answer a different and more commercially critical set of questions: what does this person believe about their problem? What do they believe about themselves in relation to the problem? What have they already tried and why did it fail? What are they afraid will happen if they do not solve this problem? What are they afraid will happen if they invest in yet another solution that does not work? What specific transformation are they truly seeking — beneath the surface-level outcome they articulate? The answers to these questions are the raw material from which every hook, every email, every sales page, and every offer mechanism is built. This SOP covers: the six psychographic layers and what each contributes to the marketing system, the Language Mining Protocol (how to extract the exact words buyers use before they become buyers), the Fear and Desire Mapping System, the Identity and Belief Architecture (the deepest and most commercially valuable layer), the Buying Decision Psychology framework, the Buyer Awareness Stage model and its implications for content sequencing, the Negative Avatar Protocol, the Psychographic DNA Document format, and the specific ways the completed profile feeds every downstream course in the programme. ⭐ First Revenue Path Position — Course 5 of 10 This is the fifth course in the First Revenue Path: C1 → C2 → C3 → C6 → C7 → C10 → C11 → C12 → C15 → C22. It requires the Problem Map from Course 6 as its primary input — specifically the Problem Statement Library and the primary problem selection. The Psychographic DNA work investigates the specific person who experiences the problem the operator has identified, not the problem in the abstract. An operator who attempts Course 7 without a confirmed problem selection will produce a generic buyer profile disconnected from a specific commercial problem. The Mirror Principle — Why Buyers Buy the Operator Who Understands Them The single most powerful commercial effect of deep psychographic intelligence is this: when a buyer reads the operator's content and thinks 'this person describes exactly what I am experiencing — it is like they are reading my mind,' the probability of purchase increases more dramatically than any other single factor. This is not because the buyer thinks the operator is clever. It is because the buyer experiences recognition — the feeling of being genuinely understood by someone who has either been where they are or has studied their situation with unusual precision. Recognition converts. Generic content informs. The Psychographic DNA system is the mechanism for producing recognition at scale. The Source Hierarchy for Psychographic Research The sources for psychographic intelligence are ranked by accuracy: (1) the operator's own experience of the before-state (if they have lived it), (2) direct conversations with people currently experiencing the problem, (3) verbatim language from community discussions, (4) written accounts in reviews, posts, and comments, (5) synthesised secondary research. Sources 1 and 2 are irreplaceable. Sources 3 and 4 are highly reliable. Source 5 alone produces generic profiles. The Language Mining Protocol in this SOP is designed to reach Sources 1–4 before any secondary research is conducted. LAYER 1 Surface Psychographics — Goals, Frustrations, and Daily Context What the buyer consciously wants and what is visibly blocking them Layer 1 is the starting point — the surface-level profile that most operators produce when they think they have done buyer research. It covers the conscious goals the buyer is pursuing, the visible frustrations they experience, and the daily context in which the problem manifests. This layer is necessary but insufficient on its own. It tells the operator what the buyer says they want. It does not tell them what the buyer actually buys. The Layer 1 Elicitation Framework Psychographic Element Elicitation Questions What the Answers Reveal Common Research Error Conscious goals What are you ultimately trying to achieve? If this problem were completely solved, what would be different about your work or life? What does success look like to you in this area? The surface-level outcome the buyer is pursuing. This becomes the headline of the offer and the primary CTA language. Accepting the first answer without drilling down. 'I want to grow my business' is not a goal. 'I want to sign three new clients per month at $3,000 each' is a goal. Push to the specific number or condition that defines success. Visible frustrations What specifically bothers you most about this situation right now? What have you tried that has not worked? What do you find yourself complaining about when this topic comes up? The activated pain. The emotional content that, when reflected back in marketing language, produces the recognition effect. Writing the frustrations in polished, professional language. 'I experience inefficiency in my process' is the sanitised version. 'I spend every Sunday dreading Monday because nothing ever gets done on time' is the real version. Collect the real version. Daily context Walk me through a typical week where this problem is present. When does it show up? Where are you when it happens? What triggers it? What do you do with it when it comes up? The situational context that makes specific scenario-based content resonate. 'When you are sitting at your desk at 10pm trying to...' works because it is specific. The daily context provides the specific. Ignoring the situational specificity in favour of the general problem description. Both are needed. LAYER 2 The Failed Attempts Architecture — What Has Already Been Tried The most commercially valuable psychographic layer after identity The Failed Attempts Architecture is the map of every solution the buyer has already tried for the problem the operator's offer addresses. It is commercially important for two reasons: it tells the operator exactly what the buyer does NOT want to hear (anything that sounds like the failed solution they already tried), and it defines the specific objection landscape the operator must navigate to convert this buyer. The Three Failed Attempt Categories Category Examples What It Tells the Operator How It Is Used in the Marketing System Category 1 — Failed product or programme Bought a course, hired a coach, used software, read a book — invested time and money and did not get the promised result. The buyer is a proven purchaser in this category (removes the 'would they pay?' question). They are also sceptical of another similar product. The specific product type they tried and what disappointed them defines the positioning gap. The offer is positioned to explicitly address what the failed solution left out. 'Unlike [type of solution that failed], this programme does X specifically because that is what was missing.' The promise structure references the gap, not just the outcome. Category 2 — Failed self-directed attempt Tried to implement a free method, followed YouTube tutorials, read blog posts, created their own system — still did not solve the problem. The buyer has proven investment in solving the problem (time investment, not just money). The specific self-directed approach they tried and why it failed reveals whether the gap is information, implementation, accountability, or something else entirely. The mechanism of the offer is designed to address the specific failure mode of the self-directed attempt. If self-directed attempts fail because of accountability: the offer's accountability structure is foregrounded. If they fail because the free information is incomplete: the offer's completeness and specificity is foregrounded. Category 3 — Intermittent success, unsustained The buyer achieved partial or temporary results but could not maintain them — the problem came back. The buyer has proof of concept that a solution exists (they achieved the result temporarily). The gap is sustainability, consistency, or the conditions required for the result to hold. This is a highly motivated buyer. The offer addresses the sustainability gap directly. The mechanism explains specifically why the temporary success did not hold and what is different about the approach that makes the result permanent. THE FAILED ATTEMPTS ELICITATION — Question Sequence Ask every problem depth interview contact: 'Before we talk about what you are looking for, I want to understand what you have already tried. Walk me through the main things you have done to address this.' [Let them list. Note every item.] For each item: 'Tell me more about that. What made you try it? What happened when you did?' Then: 'What was specifically missing or wrong with it?' [This question produces the most commercially valuable language in the entire interview. The specific missing element they name is the gap the offer must fill.] Then: 'Did you get any results at all from it?' [If yes: 'What did you get? Why did it not continue or reach the full outcome?'] Then: 'What made you try the next thing after that one did not work?' [This reveals the buyer's decision-making process and what signals they use to evaluate a new solution.] Finally: 'After all of that, what specifically would a solution need to do — or not do — to feel worth trying again?' [This is the positioning brief for the offer. Record verbatim.] LAYER 3 Fear and Desire Mapping — The Emotional Architecture of the Buying Decision The specific fears and specific desires that activate or suppress the purchase Every purchase decision is ultimately an emotional event. The rational justifications come after — they are the story the buyer tells themselves and others to explain a decision that was made by a deeper system of fears and desires. The Fear and Desire Map is the operator's guide to the emotional engine of the buying decision for their specific buyer in their specific problem domain. The Six-Category Fear Map Fear Category What It Looks Like in This Buyer The Marketing Response The Positioning Failure to Avoid Fear of wasting money again 'I have already spent $[X] on [category] and have nothing to show for it. I cannot justify spending more without confidence this one is different.' Reduce the financial risk explicitly: specific guarantee structure, specific evidence of different mechanism, specific qualification criteria that shows this is built for their specific situation not the general category. Leading with the outcome promise before addressing the financial risk fear. The buyer who fears wasting money filters out outcome promises because they have heard them before. The risk reduction must come first. Fear of wasting time 'The last time I tried something like this, I spent three months going through it and ended up back where I started. I do not have another three months to waste.' Specificity of time investment and specificity of result-by-date. Not 'you will transform your business' but 'in the first 30 days you will have [specific output]. By Day 90 you will have [specific milestone].' Vague timelines or 'go at your own pace' language. For the time-fear buyer, flexibility feels like another potential time waste. Fear of being exposed as incompetent 'What if I try this and it becomes obvious that I am not capable of succeeding even with professional help? What does that say about me?' Normalise the before-state explicitly. Show that the exact starting situation the buyer is in is the expected starting state, not evidence of inadequacy. Testimonials from people who started in the same place. Content that uses 'even beginners can...' language — which implies the buyer, who has been working on this for years, is at a beginner level and therefore the statement does not apply. Fear of buying the wrong thing 'There are a hundred options in this category. What if I choose this one and the right one was somewhere else?' Evidence of the decision process: show the buyer specifically how this solution was designed to address the gap that the most common alternatives leave. Make the selection rationale visible so the buyer can follow the logic. Generic 'we are different because...' language that every competitor also uses. Fear of it working and changing their life in unwanted ways 'If I actually succeed at this, what else will change? Will it create new problems? Will it disrupt things that are currently stable?' Acknowledge the change landscape. Show specifically what changes and what stays the same. Testimonials that address the 'I was afraid of what success would mean' concern. Presenting only the upside of the transformation. For some buyers, the upside creates a different kind of anxiety. Fear of judgement from others 'What will people think if I invest in [coaching / a course / this kind of help]? Will they think I am not capable of figuring this out myself?' Normalise the investment as a strategic decision rather than a remedial one. 'The most successful people in [field] consistently use [this kind of support]' positions the purchase as what capable people do. Content that implies the buyer needs external help because they cannot do it themselves. The Desire Map — The Three Layers of What Buyers Actually Want Desire Layer Description Example in Context How It Changes the Offer Framing Surface desire The stated outcome: what they say they want when asked directly. 'I want to grow my consulting business to $20,000/month.' This is the headline promise. But if the offer is framed only at this level, it competes with every other offer making the same revenue claim. Intermediate desire The quality-of-life change the surface outcome enables: what will be different about daily experience when the surface outcome is achieved. 'I want to stop working 60-hour weeks and have time for my family. The revenue is the mechanism, not the actual goal.' Framing the offer around the intermediate desire (the daily experience) produces deeper resonance. 'Sign 3 new clients per month and end your Sunday evenings feeling prepared, not anxious' speaks to both layers. Identity desire The self-concept change: who the buyer wants to be, not just what they want to have or do. The deepest and most durable buying motivation. 'I want to feel like a real professional — not someone who is always scrambling. I want to feel like someone who has their business under control.' Offers framed at the identity layer produce the strongest loyalty, the lowest refund rates, and the highest testimonial generation because the buyer is not just buying an outcome — they are buying a transformation in who they are. LAYER 4 The Identity and Belief Architecture — The Deepest Psychographic Layer What the buyer believes about themselves, about the world, and about what is possible for someone like them The Identity and Belief Architecture is the most commercially powerful and the most frequently overlooked psychographic layer. It captures not what the buyer wants but what they believe — about themselves, about people like them, about whether this problem is solvable for someone in their specific situation, and about what kind of person succeeds at the transformation the offer promises. These beliefs are the actual gate that controls whether the purchase is made and whether the programme works after purchase. The Five Belief Categories Belief Category What to Elicit Commercially Critical Variants How It Enters the Marketing System Self-efficacy beliefs What do you believe about your own ability to change this situation? Do you think people like you typically succeed at this? Have you succeeded at other hard things before? Low self-efficacy: 'I know what to do — I just cannot seem to actually do it.' Medium: 'I think I could do this if I had the right system.' High: 'I just need the right strategy — I am fully capable of executing once I know what to do.' Low self-efficacy buyers need the accountability structure and community component foregrounded. High self-efficacy buyers need the sophistication and specificity of the method foregrounded. Category beliefs What do you believe about [courses/coaching/this type of help] in general? Have you formed opinions about whether this category works? The buyer who has been burned by the category has a strong negative category belief. The offer must be positioned as categorically different from the specific mechanism of the failure. Use the Failed Attempts Architecture to name the specific failure and show how the mechanism of this offer differs. Do not defend the category — differentiate from its failure modes. Timing beliefs Do you believe now is the right time to address this? What would have to be true for the timing to feel right? 'I am too busy right now.' 'Once [condition] is resolved, I will be ready.' 'I need to wait until [external condition].' These are the conditions-waiting pattern from the Sovereign Operator SOP applied to the buyer. Address the timing objection by showing the cost of delay in specific, concrete terms. 'Every month spent not addressing this costs [specific quantifiable consequence].' Identity match beliefs Do you see yourself as the kind of person who [takes this action / invests in this kind of help / succeeds in this domain]? The most powerful and hardest to shift: 'People like me don’t...' or 'I’ve never been someone who...' or 'This works for other people but I’m different because...' These identity mismatches must be addressed directly and early. Testimonials from people who share the specific identity the buyer uses to exclude themselves are the most effective tool. World model beliefs What do you believe about how the market / the system / the rules work for people in your situation? 'The system is rigged for people who already have [advantage].' 'By the time someone like me gets there, the opportunity will be gone.' 'The people who succeed have something I don’t — connections, capital, luck.' Address the world model belief by showing the specific mechanism through which the offer creates an outcome that does not depend on the advantages the buyer believes they lack. The Beliefs That Prevent Implementation Are More Important Than the Beliefs That Prevent Purchase An operator who maps only the beliefs that prevent purchase will design an offer that converts well and delivers poorly — because the beliefs that prevent buyers from implementing the programme are different from the beliefs that prevent them from buying it. Mapping both sets of beliefs, and designing the programme's delivery to address the implementation-preventing beliefs explicitly, produces higher completion rates, more testimonials, and better programme outcomes. The belief audit should ask: 'What will this buyer believe when they are three weeks in and have not yet seen results?' LAYER 5 The Language Mining Protocol — Finding the Exact Words Buyers Use Replacing the operator's professional language with the buyer's native language The Language Mining Protocol is the systematic process for replacing the operator's technical, polished, professional language with the specific, colloquial, emotionally charged language that buyers use when they are alone with their problem. This language replacement is the single highest-leverage copywriting action available. A headline written in buyer language and a headline written in operator language can address the same topic and produce a 3–5x difference in conversion rate purely through language. The Language Mining Sources — Priority Order Source How to Mine It What to Extract Quality Indicator Direct problem depth interviews (from Course 6) Re-read every interview transcript or note with a specific focus on exact phrasing, recurring metaphors, and emotionally loaded words. The exact sentences buyers use when describing the problem at peak frustration. The specific metaphors they reach for ('It feels like I am drowning', 'I am running on a hamster wheel', 'It is like starting from scratch every time'). Phrases that appear in multiple independent interviews. A phrase that three different people use independently is the market's natural language for that experience. Reddit and forum threads in the problem domain Search the specific problem statement and read the posts with the most upvotes and the most comments. Read every comment in threads where people are describing their personal experience. The first three words of posts with high upvotes (these words were chosen by the author to make the post get attention — they are the best-performing hooks in the market). The specific comparisons, metaphors, and emotional language in comments. Phrases that generate high agreement responses ('Yes, exactly', 'This is exactly how I feel', 'I thought it was just me') are the market's universal language for the experience. Amazon reviews (1–5 stars) of books and programmes in the category Read the 5-star reviews for the language of the transformation achieved. Read the 1–3 star reviews for the language of the frustration with current solutions. 5-star: the specific outcome language. 'Since reading this I have...' followed by the specific change. 1–3 star: 'I was hoping for X but got Y' — X is the desired outcome stated in buyer language. Reviews that use emotional language ('Finally', 'I was so frustrated that', 'Life-changing') signal the highest-intensity language associated with that problem/solution. The operator's own before-state (if applicable) If the operator has personally experienced the transformation they are selling: re-read journals, old emails, saved notes from the period when they were in the before-state. The operator's own language from before they had the expertise they are now selling. This language is the most authentic because it is genuinely from the before-state, not reconstructed. This source is only available if the operator has lived the transformation. When available, it is the highest-quality source because it is first-person and pre-expertise. Course 6 Problem Statement Library All statements already collected in the Problem Statement Library from Course 6. Cross-reference with the mining from the sources above. Identify patterns and specific phrases that appear across multiple sources. Phrases that appear in both interview transcripts and community discussions have the highest confidence as the market's natural language. The Language Bank — The Structured Output of Language Mining THE LANGUAGE BANK FORMAT — Minimum 50 entries before the bank is considered complete SECTION 1 — PROBLEM DESCRIPTION LANGUAGE (minimum 15 entries) Exact phrases buyers use when describing the problem at full intensity. Format: [verbatim quote] | Source: [where it was found] | Frequency: [how many independent sources used similar language] Examples: 'I feel like I am constantly starting over and never actually getting anywhere.' | Reddit r/[relevant] | 3 independent occurrences 'I have all this knowledge and no idea how to turn it into something people will pay for.' | Interview 3 | Also in Interview 7, similar language in Amazon review [title] SECTION 2 — FAILED SOLUTION LANGUAGE (minimum 10 entries) Exact phrases buyers use to describe what they tried and why it did not work. Format: [verbatim quote] | Specific solution being described | What the quote reveals about the failure mode SECTION 3 — DESIRED OUTCOME LANGUAGE (minimum 15 entries) Exact phrases buyers use to describe what they are actually trying to achieve. Format: [verbatim quote] | Desire layer (Surface / Intermediate / Identity) | Frequency SECTION 4 — IDENTITY LANGUAGE (minimum 10 entries) Exact phrases buyers use about themselves in relation to the problem domain. Format: [verbatim quote] | Belief category (Self-efficacy / Category / Timing / Identity match / World model) | Whether positive or negative THE LANGUAGE USAGE STANDARD All marketing copy — emails, social posts, landing pages, ad copy, sales pages — must contain a minimum of 3 direct phrases from the Language Bank per 300 words. The percentage of buyer-language phrases to operator-language phrases should favour buyer language at a 70/30 ratio minimum. Any marketing copy submitted for the AI Quality Assurance Gate review must pass the Language Bank check: does it sound like the buyer describing their own problem, or does it sound like the operator describing it from outside? LAYER 6 The Buyer Awareness Stage Framework — Meeting the Buyer Where They Are The five stages of buyer awareness and the specific content and messaging each stage requires Not all buyers are at the same stage of awareness about their problem, the category of solutions, or the specific operator's approach. Content and messaging that is calibrated for one awareness stage will fail to engage buyers at a different stage. The Buyer Awareness Stage Framework, adapted from Eugene Schwartz's foundational work, defines the five stages of buyer awareness and the specific content and messaging requirements of each. The Five Buyer Awareness Stages Stage Definition What the Buyer Knows What Content They Engage With What Will Not Work for Them Stage 1 — Unaware The buyer does not yet recognise that the problem they have is a distinct problem with a name, a cause, and a solution. They experience the symptoms but have not connected them to a specific problem category. They experience the symptoms. They have not framed it as a problem to be solved. They are not actively seeking solutions. Content that addresses the symptoms they experience without naming a category or solution. 'Does this sound familiar...' content that describes their daily experience. Content that names the category or the solution immediately. They do not yet have the frame to receive it. Stage 2 — Problem Aware The buyer recognises they have a specific problem and can name it. They are beginning to research it but have not yet committed to seeking a solution. They know the problem exists. They have named it. They have done some initial research. Content that goes deeper on the problem: why it happens, what makes it persist, why standard advice does not fix it. Mechanism-level explanation without a solution pitch. Immediate offer presentation. The Stage 2 buyer is not yet ready to commit. Pitching too early produces the opposite of the intended result: it activates scepticism. Stage 3 — Solution Aware The buyer knows solutions exist and has been researching the options. They are evaluating categories and approaches rather than specific offers. They know multiple solution categories exist. They are comparing approaches. They have opinions about which approaches seem to work better than others. Content that makes the case for the specific mechanism or approach: why this type of solution works when other types do not. Comparison content that helps them evaluate categories. Feature-level product descriptions. They are not yet choosing between specific products — they are choosing between approaches. Stage 4 — Product Aware The buyer is aware of specific offers in the market and is evaluating which one to choose. They may be aware of the operator's offer specifically. They know about the operator's offer or similar offers. They are in active consideration mode. They have specific criteria for the buying decision. Content that differentiates this specific offer from the alternatives they are considering. Social proof, specific results, guarantee structure. Comparison with named alternatives. Content that explains why they should be interested in this category — they already are. The Stage 4 buyer needs confirmation and differentiation, not persuasion to consider the category. Stage 5 — Most Aware The buyer is ready to purchase. They are waiting only for the right trigger: the right timing, the right price, the right guarantee, the right context. They have decided they want this type of solution from this type of operator. They need a specific reason to act now rather than later. Content that creates urgency, reduces friction, and answers the final remaining objections. Limited enrolment, bonus expiration, direct invitation to join. Long-form education. The Stage 5 buyer does not need more information — they need a reason to move. The Awareness Stage Distribution — Why Most Operators Fish in the Wrong Pond The most commercially significant insight from the Buyer Awareness Stage Framework is the distribution of buyers across stages at any given time. For most knowledge business markets: Awareness Stage Approximate Distribution in Most Markets Operator Behaviour The Strategic Implication Stages 1–2 (Unaware + Problem Aware) 60–70% of the total potential market Most operators produce almost no content for Stages 1–2 because it requires writing about the problem without pitching the solution. It feels like leaving money on the table. The largest segment of the potential market cannot be reached by content that assumes they are already solution-aware. TOFU (top of funnel) content — which addresses symptoms, causes, and why-it-persists — is the mechanism for reaching this majority. Stage 3 (Solution Aware) 20–25% of the market Most operators produce a moderate amount of content for Stage 3 — the mechanism and approach explanations that differentiate their category. This is the stage where category belief is formed. Content here determines whether the buyer believes the type of solution the operator offers is the right category for their problem. Stages 4–5 (Product Aware + Most Aware) 5–15% of the market Most operators produce most of their conversion-focused content for Stages 4–5 — the stage where the fewest buyers actually are. Sales page, launch emails, and direct offers all target this small minority. The pipeline problem most operators experience (not enough buyers in the funnel) is a Stage 1–2 content deficit, not a Stage 4–5 problem. The Negative Avatar Protocol The Psychographic DNA profile defines who the offer is for. The Negative Avatar Protocol defines, with equal precision, who it is not for. This is not a defensive exercise — it is a commercial one. Clarity about who the offer is not designed for prevents the wrong buyers from purchasing, reduces refund rates, reduces the support burden from buyers who cannot implement, and sharpens the positioning of the offer for the right buyers. The Five Negative Avatar Categories Negative Avatar Category Description Why They Are a Problem How to Prevent Their Purchase The Expectation Mismatch A buyer who has misunderstood what the programme delivers. They believe the programme will do something it was not designed to do. High refund rate. Negative reviews. Support burden from buyers seeking a product they did not actually purchase. Explicit 'This programme is not for...' language on the sales page. Specific 'This programme is not...' content in the pre-purchase email sequence. The Passive Consumer A buyer who wants the result but is not willing to do the implementation work the programme requires. Zero completion rate. Zero testimonials. Zero case studies. High likelihood of a refund or a complaint that the programme 'did not work.' Be explicit about the work requirement in the sales page and the welcome sequence. 'This programme requires [X hours per week] of implementation work. If you are not ready to commit that, this is not the right programme for you now.' The Premature Entry A buyer who does not yet have the prerequisites the programme requires to be useful. They cannot implement what they learn because the foundational conditions are not yet in place. They experience the programme as overwhelming or irrelevant. Explicit prerequisites on the sales page. A qualification question at the point of purchase. The enrolment sequence can include a 'is this right for you?' self-assessment. The Value Extractor A buyer who has no intention of implementing the programme but wants to take the content, the systems, or the templates and use them for purposes other than the stated application. Intellectual property risk. No testimonials. No community contribution. Terms of service that address content usage. A clear statement of the intended application and the limitations on use. The Perpetual Researcher A buyer who purchases programmes to research the field rather than to implement. They have many programmes, few results. No testimonials. High likelihood of an unenthusiastic review. Contribution to 'does not work' scepticism in the market. Programme qualification: 'Have you already purchased and not completed a programme in this category? What specifically prevented completion, and what is different about this time?' This question surfaces the Perpetual Researcher without rejecting them — it invites self-reflection. The Psychographic DNA Document — The Course 7 Deliverable The Psychographic DNA Document is the formal output of Course 7. It consolidates all six psychographic layers into a single reference document that is used as the primary input for every downstream marketing and messaging activity in the programme. Every piece of content, every email sequence, every hook, and every sales page is written with this document open. PSYCHOGRAPHIC DNA DOCUMENT — Complete Format DOCUMENT HEADER Operator Name: Primary Problem Domain (from Course 6 Problem Map): Primary Buyer Avatar Name: [a specific persona name, not 'Ideal Client'] Document Version and Date: Next Review Date: [Psychographic DNA should be reviewed after every 20 buyers or every 6 months] SECTION 1 — SURFACE PSYCHOGRAPHICS Conscious goals (3–5 specific, measurable outcomes they are pursuing): 1. [Goal with specific metric] 2. [Goal with specific metric] 3. [Goal with specific metric] Primary visible frustration (the one thing they complain about most): [1–2 sentences in buyer language] Daily context (when and where the problem shows up in their daily life): [3–4 sentences describing a specific scenario] SECTION 2 — FAILED ATTEMPTS ARCHITECTURE Solutions they have already tried (in order of most common to least common): Solution 1: [What it was] | Why they tried it | What disappointed them | Quote from Language Bank Solution 2: [same format] Solution 3: [same format] The specific failure mode that most often explains why solutions do not work for this buyer: [One specific diagnosis, not a list] What a new solution must NOT look/sound/feel like (because it will be dismissed as another version of a failed solution): [Specific language, format, or promise types that trigger scepticism] SECTION 3 — FEAR AND DESIRE MAP Top 3 fears (in order of intensity for this specific buyer): Fear 1: [Specific fear] | Intensity (High/Medium/Low) | Quote from Language Bank | Marketing response Fear 2: [same format] Fear 3: [same format] Surface desire: [The stated outcome in buyer language] Intermediate desire: [The quality-of-life change the outcome enables] Identity desire: [The self-concept transformation they are truly seeking] SECTION 4 — IDENTITY AND BELIEF ARCHITECTURE Self-efficacy belief (does this buyer believe they are capable?): [Specific description with a representative quote] Category belief (what do they believe about this type of solution?): [Specific description, noting if there is scepticism and what produced it] Identity match belief (do they see themselves as someone this is for?): [Specific description of the identity gap, if any, and the language they use to exclude themselves] World model belief (what do they believe about how the system works for people like them?): [Specific description with representative language] Implementation-preventing beliefs (what will this buyer believe when they are struggling at week 3?): [2–3 specific beliefs that produce abandonment, and the programme design response to each] SECTION 5 — LANGUAGE BANK (minimum 50 entries across five categories) [See Language Bank Format in the Language Mining section above] [Full Language Bank is appended to this document or linked from Airtable] SECTION 6 — AWARENESS STAGE DISTRIBUTION Primary stage of awareness for the top-of-funnel audience this content strategy is targeting: [Stage 1–3 for content strategy. Stage 4–5 for sales and launch strategy.] What content is required at each stage to move this buyer toward purchase: Stage 1–2: [Specific content types and themes] Stage 3: [Specific mechanism explanation themes] Stage 4–5: [Specific conversion content types] SECTION 7 — NEGATIVE AVATAR DEFINITION Who this offer is explicitly NOT for: [Category 1 from the Negative Avatar Protocol, with specific language for the sales page] [Category 2, same format] [Category 3, same format] Prerequisites for purchase: [Specific conditions that must be true for the offer to work for the buyer] SIGN-OFF This document is based on primary research: minimum 5 problem depth interviews, minimum 3 community sources mined, minimum 30 Language Bank entries completed from direct sources (not AI-generated). The buyer described in this document is a real person (or composite of real people), not an imagined ideal. How the Psychographic DNA Document Is Used Downstream Downstream Course or SOP How the Psychographic DNA Is the Primary Input Course 12 — Outcomes Greater Than Features The Desired Outcome language from Sections 1 and 3 (Surface, Intermediate, and Identity desires) becomes the verbatim source material for the offer's headline, sub-results language, and CTA language. The outcome messaging is not written from scratch — it is assembled from Language Bank entries already collected. Course 15 — Hook Engineering The Problem Description Language from the Language Bank (Section 5, Category 1) is the source material for every hook. The opening lines of the most engaging community posts are the most tested hooks in the market. They are used directly as the first line of emails, social posts, and ads. Course 17 — Narrative Influence and Story Arcs The Failed Attempts Architecture (Section 2) defines the 'false beliefs' and 'failed solutions' that the story arc must address. The Identity and Belief Architecture (Section 4) defines the specific identity transformation the story arc must produce. The narrative sequence is: before-state (buyer's current belief and experience) — turning point (the specific insight that changed everything) — after-state (the new identity and the result it produced). Course 19 — Objection Mapping and FAQ Engineering The Fear Map (Section 3) is the direct source for the objection map. Each fear category generates a specific objection that appears at the point of purchase. The FAQ engineering protocol addresses the fears in the same order as their intensity rating in the Psychographic DNA Document. Course 21 — Identity-Based Marketing The Identity Desire and Identity Match Belief from Sections 3 and 4 define the specific identity transformation the marketing must produce. The marketing is not just an offer — it is a mirror that reflects the buyer's desired identity back to them and positions the programme as the path to becoming that person. Course 25 — Sales Page Architecture The entire sales page is structured to move the buyer from their current awareness stage to Stage 5. Every section of the page addresses a specific element of the Psychographic DNA: the headline addresses the surface desire; the problem section reflects the buyer's daily context back; the mechanism section addresses the category belief by explaining why previous solutions failed; the proof section addresses the self-efficacy belief; the guarantee addresses the fear of wasting money. The Negative Avatar Modelling SOP The Negative Avatar section of the Psychographic DNA Document is the primary input for the Negative Avatar Modelling SOP. The full Negative Avatar profile is developed in that dedicated SOP using the foundation built here. Content Calendar by Awareness Level SOP The Awareness Stage Distribution from Section 6 determines the ratio of content types across the content calendar. If 60–70% of the potential audience is at Stages 1–2, then 60–70% of the content calendar should produce Stage 1–2 content. Most operators produce less than 20% of their content for Stages 1–2. The Psychographic DNA Update Protocol — Keeping the Profile Current The Psychographic DNA is not a one-time research exercise. It is a living document that evolves as the operator gains more buyers, produces more results, and collects more market intelligence. A Psychographic DNA profile written before the first buyer is the operator's best hypothesis. A profile updated after 20 buyers is market-tested intelligence. Update Trigger What to Update How to Update Cadence After the first 5 buyers have completed at least 30 days of the programme Section 4 (Identity and Belief Architecture) — especially the implementation-preventing beliefs. What actually stopped buyers in the first 30 days? Review the support tickets, community messages, and coaching call recordings from the first 5 buyers. Note the specific beliefs and language associated with difficulty. After first 5 buyers. After each cohort (every 10–20 buyers) Section 2 (Failed Attempts) — are new solution types appearing that were not in the original research? Section 5 (Language Bank) — add the most powerful testimonial language from completed buyers. Interview or survey every buyer at the end of their programme. The post-programme interview produces the most accurate transformation language. Every 10–20 buyers. After a significant market event (a major competitor enters, a platform changes significantly, a macro force shifts) Section 6 (Awareness Stage Distribution) — market events shift where buyers are in the awareness cycle. A major competitor entering the market moves some buyers from Stage 2 to Stage 3 or 4. Review the Macro Intelligence Dashboard from Course 5 and assess which awareness stage is most affected by the market event. As needed following macro events. Every 6 months as standard review Full document review: does the language still match what buyers are saying? Are the fears and desires still the primary motivators? Has the Failed Attempts Architecture changed as new solutions have entered the market? Return to the community sources from the original research. Run 3–5 new problem depth interviews. Compare findings against the current document. Biannually. Airtable Schema — Psychographic Intelligence Database Table 1 — Avatar Profile Records Field Type Notes Avatar ID Short text Format: AVA-[Seq] Avatar Name Short text A specific persona name Primary Problem Domain Link → Problem Records from Course 6 Document Version Short text Version number and date Surface Goals Long text 3–5 specific, measurable outcomes Primary Frustration Long text In buyer language Daily Context Long text Scenario description Top Failed Solution 1 Short text What was tried and how it failed Top Failed Solution 2 Short text Top Failed Solution 3 Short text Primary Failure Mode Short text The diagnosis of why solutions consistently fail Fear 1 — Type and Intensity Short text Fear 2 Short text Fear 3 Short text Surface Desire Short text Intermediate Desire Short text Identity Desire Long text Self-Efficacy Belief Single select Low / Medium / High Category Belief Short text Identity Match Belief Long text World Model Belief Short text Implementation-Preventing Beliefs Long text Primary Awareness Stage of New Audience Single select Stage 1 / Stage 2 / Stage 3 Negative Avatar Exclusions Long text Who this offer is not for Prerequisites Long text Conditions required for the offer to work Research Basis Short text Interviews conducted, sources mined, Language Bank entries Last Updated Date Next Review Date Date Table 2 — Language Bank (linked to Avatar Profile) Field Type Notes Entry ID Short text Format: LB-[Seq] Verbatim Statement Long text Exact buyer language — no paraphrasing Language Category Single select Problem Description / Failed Solution / Desired Outcome / Identity / Social Proof Seeking Source Type Single select Interview / Reddit / Facebook Group / YouTube Comment / Amazon Review / Operator Before-State / Other Source Reference Short text URL, interview reference, or document location Frequency Across Sources Number How many independent sources used similar language Awareness Stage Single select Stage 1–2 / Stage 3 / Stage 4–5 Used In Multi-select Hook Library / Email Subject Lines / Sales Page / Ad Copy / Course Content / Other Avatar Profile Link → Avatar Profile Records Master Psychographic DNA Checklist Phase 1 — Surface Psychographics and Failed Attempts (Week 5, Days 1–2) ☐ Problem Map from Course 6 confirmed — primary problem selected and commercial demand validated ☐ Minimum 5 Problem Depth Interviews conducted — failed attempts section completed for each ☐ Layer 1 (Surface Psychographics) elicited and documented from interview sources ☐ Layer 2 (Failed Attempts Architecture) mapped: top 3 solution types tried, specific failure modes per type Phase 2 — Fear and Desire Mapping (Week 5, Day 3) ☐ Six fear categories reviewed — top 3 fears ranked by intensity for this specific buyer ☐ Three desire layers mapped: surface, intermediate, and identity ☐ Language Bank seeded: at least 5 entries in each of the five language categories Phase 3 — Identity and Belief Architecture (Week 5, Day 4) ☐ All five belief categories elicited and documented ☐ Implementation-preventing beliefs identified — at least 2 specific beliefs documented ☐ Programme design implications of the belief architecture noted for later use in Course 11 Phase 4 — Language Mining Protocol (Week 5, Days 4–5) ☐ All five Language Mining sources consulted ☐ Language Bank completed: minimum 50 entries across five categories ☐ High-frequency phrases identified (appearing in 3+ independent sources) highlighted ☐ Language Usage Standard documented: 70/30 buyer/operator language ratio committed to Phase 5 — Awareness Stage Analysis and Negative Avatar (Week 5, Day 5) ☐ Primary awareness stage of the top-of-funnel audience confirmed ☐ Stage-specific content requirements documented for Stages 1–2, 3, and 4–5 ☐ Negative Avatar Protocol completed: top 3 exclusion categories defined with specific sales page language ☐ Prerequisites for purchase written The Psychographic DNA Document ☐ All seven sections of the Psychographic DNA Document completed ☐ Document is based on primary research — not AI-generated personas or demographic data alone ☐ Avatar Profile Record and Language Bank entries created in Airtable ☐ Document shared with accountability partner or mentor for an honest assessment: 'Does this sound like a real person?' ☐ Document accessible during every content creation, email writing, and copy review session RISER Nation Master Operating System | Psychographic DNA SOP | Course 7 | Version 1.0 | 2026 Edition ⭐ First Revenue Path — Course 5 of 10 | risernation.com

word/comments.xml

word/endnotes.xml

word/footer1.xml Page of

word/footnotes.xml

word/header1.xml RISER Nation | Psychographic DNA SOP | Course 7 | V1.0

Clickable sources and applicable resources

ClickFunnels educational resources

Acquisition.com educational resources

Google AI search guidance

Google spam policies

Reddit

Amazon

Airtable

Assigned document D0221, source 1

Expand keyword ideas and then validate them

The source is a worked prompting conversation around 4 bed 2 bath houses for sale. It asks for alphabetic modifiers after and before a seed, then progressively narrows the topic to renovated homes, renovated kitchens and nearby kitchen-renovated homes. These are generated candidates, not observed autocomplete data or measured demand. The complete conversation, including its unfinished line and corrections, remains below.

Run both alphabet passes deliberately

Start with a product/property description that is true. Add modifiers after the seed, A through Z, covering places, affordability, features, style, condition and availability. Then add prefixes before the seed, again A through Z. The template asks for 20 per letter in each direction:26×20×2=1,040 candidate slots. The worked output supplies about four per letter, with an interrupted H line and continuation. Do not claim it fulfills 1,040 slots or pad it with invented source data. Separate candidate count from unique useful phrases.

The suffix list ranges from Arizona/acreage to pools, waterfront, quick move-in, xeriscaping, Zillow, zip code and zoning. Prefixes range from affordable to turnkey, furnished, lakefront, vacation and zero-energy. Several entries are awkward or invented spellings, such as xcellent, xtras and xquisite. Keep them in the historical reference, but use natural wording in published copy. A place name, listing condition, price ceiling, efficiency claim or availability term needs evidence from actual inventory. A brand/platform keyword is different from your own offer's feature.

Narrow the topic through the two full tier exercises

Select 3–5 ideas that fit the actual audience and offer, then request 20 low, 20 mid and 20 high-tier phrases. The source supplies 60 for renovated homes and another 60 for renovated kitchens. These tiers assert low/medium/high competition and volume without a tool, date or measure. Treat them as hypotheses. Keyword length and specificity do not establish competition, and PPC advertiser competition differs from organic ranking difficulty.

Record platform, geography, date range, intent, relevant page, volume if available, metric source and confidence. Validate the phrases in a suitable tool and actual results. The next selected phrases move from renovated 4 bed 2 bath house to 4 bed 2 bath house with renovated kitchen and then a near-me variation. Each narrower step should correspond to a real need rather than merely making the phrase longer. Some phrases such as renovated kitchen for sale can mean cabinetry or renovation services rather than buying a house; inspect intent before assigning them to a property page.

Compare channels and investigate all thirty questions

The source then searches Google, YouTube, Instagram and TikTok and proposes forums, Reddit and Quora. These have different search behavior and metrics. Record actual observed results; an AI answer describing common questions is not a transcript of real users. Its thirty questions cover three groups of ten: general availability, price, benefits, renovation quality, features, location, value, resale and customization; practical negotiation, style, inspection, demand, seller questions, materials, older-home issues, price comparison and new-versus-renovated kitchens; and concerns about over-renovation, hidden problems, needs, financing, renovate-versus-buy, contractors, trends, maintenance and reviews.

For each question, record the source or mark it generated, write a useful answer, and identify which facts need a qualified local source or actual property evidence. Do not invent current prices, financing eligibility or legal inspection duties. Describe property features accurately and review housing advertising against applicable fair-housing requirements. Avoid turning family, kid-friendly or young prefixes into audience exclusions or steering. The goal is relevant property information, not assumptions about who should live there.

Produce a useful page rather than a keyword pile

Cluster overlapping questions into a coherent guide or listing explanation. Use readable headings, a concise answer, substantiated details and relevant internal links. Google's spam policies caution against keyword stuffing and doorway pages; do not create hundreds of near-identical city/phrase pages from the alphabet list. Brunson helps connect the searcher's question to the right next step. Hormozi helps explain the actual outcome, effort and constraints. Submit the two generated tier sets, validated shortlist, evidence log, intent map and one source-backed page brief. All 120 tier examples and 30 questions remain available in the full source below.

Complete available source reference

The following is source material for critical study. Historical offers, quoted promotional claims and embedded instructions are not RISER promises or directions to execute. Read the corrections above before adapting any example. Linked sources are not considered fully reviewed merely because a link appears.

REALTORS-ALPHABET SOUP

REALTORS-ALPHABET SOUP

Can you give me ideas for my niche in YOUR NICHE HERE with predictive words which are organized alphabetically. you will start with any keywords that start with the letter a. EXAMPLE: "YOUR NICHE HERE Arizona”, “YOUR NICHE HERE at home”, etc. Then after you complete a- z after my niche, place a letter a,b,c,d,e before my niche, example; c= cesar millan dog training, d= denver dog training, e= emotional support dog training are examples of the alphabet search before the niche keyphrase or word. Please make an outline in this type of result. Make as complete of a list as full of ideas as you can organize in outline form alphabetically. 20 Examples per Letter. The I will need 20 predictive keywords for each letter before the niche “YOUR NICHE” Each keyword phrase starts with a letter (A, B, C, etc.) followed by the word "YOUR NICHE!"

____________________________________________________________________________

Can you give me ideas for my niche in 4 bed 2 bath house for sale with predictive words which are organized alphabetically. you will start with any keywords that start with the letter a. EXAMPLE:4 bed 2 bath house for sale Arizona”, 4 bed 2 bath house for sale at home”, etc. Then after you complete a- z after my niche, place a letter a,b,c,d,e before my niche, example; c= cesar millan dog training, d= denver dog training, e= emotional support dog training are examples of the alphabet search before the niche keyphrase or word. Please make an outline in this type of result. Make as complete of a list as full of ideas as you can organize in outline form alphabetically.

Go and paste this into chatgpt.com

Here’s an outline of predictive keyword ideas for your niche "4 bed 2 bath house for sale," organized alphabetically with examples of keyword phrases where a letter is placed before the niche keyword: A-Z Keywords After the Niche ("4 bed 2 bath house for sale") * A * 4 bed 2 bath house for sale Arizona * 4 bed 2 bath house for sale affordable * 4 bed 2 bath house for sale acreage * 4 bed 2 bath house for sale at home * B * 4 bed 2 bath house for sale by owner * 4 bed 2 bath house for sale Boise * 4 bed 2 bath house for sale budget * 4 bed 2 bath house for sale beachfront * C * 4 bed 2 bath house for sale California * 4 bed 2 bath house for sale Chicago * 4 bed 2 bath house for sale cheap * 4 bed 2 bath house for sale country * D * 4 bed 2 bath house for sale Denver * 4 bed 2 bath house for sale Dallas * 4 bed 2 bath house for sale desirable * 4 bed 2 bath house for sale Durham * E * 4 bed 2 bath house for sale El Paso * 4 bed 2 bath house for sale east coast * 4 bed 2 bath house for sale exclusive * 4 bed 2 bath house for sale equity * F * 4 bed 2 bath house for sale Florida * 4 bed 2 bath house for sale fixer-upper * 4 bed 2 bath house for sale Fresno * 4 bed 2 bath house for sale farm * G * 4 bed 2 bath house for sale Georgia * 4 bed 2 bath house for sale gated community * 4 bed 2 bath house for sale Gulf Coast * 4 bed 2 bath house for sale great location * H * 4 bed 2 bath house for sale Houston * 4 bed 2 bath house for sale high end * 4 bed 2 bath house for sale historic * 4 bed 2 bath house for sale Hawaii * I * 4 bed 2 bath house for sale Indiana * 4 bed 2 bath house for sale investment * 4 bed 2 bath house for sale Illinois * 4 bed 2 bath house for sale Idaho * J * 4 bed 2 bath house for sale Jacksonville * 4 bed 2 bath house for sale just listed * 4 bed 2 bath house for sale Joplin * 4 bed 2 bath house for sale Johnson City * K * 4 bed 2 bath house for sale Kansas * 4 bed 2 bath house for sale Knoxville * 4 bed 2 bath house for sale Key West * 4 bed 2 bath house for sale kitchen remodel * L * 4 bed 2 bath house for sale Los Angeles * 4 bed 2 bath house for sale luxury * 4 bed 2 bath house for sale Las Vegas * 4 bed 2 bath house for sale large lot * M * 4 bed 2 bath house for sale Miami * 4 bed 2 bath house for sale modern * 4 bed 2 bath house for sale Memphis * 4 bed 2 bath house for sale mountain view * N * 4 bed 2 bath house for sale New York * 4 bed 2 bath house for sale Nashville * 4 bed 2 bath house for sale near me * 4 bed 2 bath house for sale New Orleans * O * 4 bed 2 bath house for sale Orlando * 4 bed 2 bath house for sale oceanfront * 4 bed 2 bath house for sale Ohio * 4 bed 2 bath house for sale Oregon * P * 4 bed 2 bath house for sale Phoenix * 4 bed 2 bath house for sale Portland * 4 bed 2 bath house for sale pool * 4 bed 2 bath house for sale private * Q * 4 bed 2 bath house for sale quiet neighborhood * 4 bed 2 bath house for sale Queens * 4 bed 2 bath house for sale quality build * 4 bed 2 bath house for sale quick move-in * R * 4 bed 2 bath house for sale Raleigh * 4 bed 2 bath house for sale rural * 4 bed 2 bath house for sale remodeled * 4 bed 2 bath house for sale riverfront * S * 4 bed 2 bath house for sale San Diego * 4 bed 2 bath house for sale Sacramento * 4 bed 2 bath house for sale spacious * 4 bed 2 bath house for sale suburban * T * 4 bed 2 bath house for sale Texas * 4 bed 2 bath house for sale Tampa * 4 bed 2 bath house for sale turnkey * 4 bed 2 bath house for sale Tucson * U * 4 bed 2 bath house for sale Utah * 4 bed 2 bath house for sale upscale * 4 bed 2 bath house for sale urban * 4 bed 2 bath house for sale unique * V * 4 bed 2 bath house for sale Virginia * 4 bed 2 bath house for sale Vegas * 4 bed 2 bath house for sale Victorian * 4 bed 2 bath house for sale Vermont * W * 4 bed 2 bath house for sale Wisconsin * 4 bed 2 bath house for sale waterfront * 4 bed 2 bath house for sale with pool * 4 bed 2 bath house for sale West Coast * X * 4 bed 2 bath house for sale x-large * 4 bed 2 bath house for sale xeriscaped * 4 bed 2 bath house for sale xcellent condition * 4 bed 2 bath house for sale xtras * Y * 4 bed 2 bath house for sale yard * 4 bed 2 bath house for sale Yosemite * 4 bed 2 bath house for sale year-round * 4 bed 2 bath house for sale yacht club * Z * 4 bed 2 bath house for sale Zillow * 4 bed 2 bath house for sale zip code * 4 bed 2 bath house for sale zen garden * 4 bed 2 bath house for sale zoned A-Z Keywords Before the Niche * A * a= affordable 4 bed 2 bath house for sale * a= amazing 4 bed 2 bath house for sale * a= active 4 bed 2 bath house for sale * a= available 4 bed 2 bath house for sale * B * b= beautiful 4 bed 2 bath house for sale * b= budget 4 bed 2 bath house for sale * b= best 4 bed 2 bath house for sale * b= big 4 bed 2 bath house for sale * C * c= charming 4 bed 2 bath house for sale * c= contemporary 4 bed 2 bath house for sale * c= country 4 bed 2 bath house for sale * c= classic 4 bed 2 bath house for sale * D * d= desirable 4 bed 2 bath house for sale * d= downtown 4 bed 2 bath house for sale * d= dream 4 bed 2 bath house for sale * d= deluxe 4 bed 2 bath house for sale * E * e= exclusive 4 bed 2 bath house for sale * e= elegant 4 bed 2 bath house for sale * e= easy 4 bed 2 bath house for sale * e= eco-friendly 4 bed 2 bath house for sale * F * f= family 4 bed 2 bath house for sale * f= furnished 4 bed 2 bath house for sale * f= fixer-upper 4 bed 2 bath house for sale * f= foreclosure 4 bed 2 bath house for sale * G * g= great 4 bed 2 bath house for sale * g= gated 4 bed 2 bath house for sale * g= garden 4 bed 2 bath house for sale * g= grand 4 bed 2 bath house for sale * H * h= high-end 4 bed 2 bath house for sale * h= historic 4 bed 2 bath house for 4o You said: more ChatGPT said: ChatGPT Continuing from where we left off: A-Z Keywords Before the Niche (continued) * H (continued) * h= homey 4 bed 2 bath house for sale * h= hidden gem 4 bed 2 bath house for sale * h= hilltop 4 bed 2 bath house for sale * I * i= immaculate 4 bed 2 bath house for sale * i= incredible 4 bed 2 bath house for sale * i= inviting 4 bed 2 bath house for sale * i= investment 4 bed 2 bath house for sale * J * j= joyful 4 bed 2 bath house for sale * j= jumbo 4 bed 2 bath house for sale * j= just renovated 4 bed 2 bath house for sale * j= jaw-dropping 4 bed 2 bath house for sale * K * k= key 4 bed 2 bath house for sale * k= killer 4 bed 2 bath house for sale * k= king-sized 4 bed 2 bath house for sale * k= kid-friendly 4 bed 2 bath house for sale * L * l= luxury 4 bed 2 bath house for sale * l= large 4 bed 2 bath house for sale * l= lovely 4 bed 2 bath house for sale * l= lakefront 4 bed 2 bath house for sale * M * m= modern 4 bed 2 bath house for sale * m= magnificent 4 bed 2 bath house for sale * m= move-in ready 4 bed 2 bath house for sale * m= must-see 4 bed 2 bath house for sale * N * n= new 4 bed 2 bath house for sale * n= nearby 4 bed 2 bath house for sale * n= nice 4 bed 2 bath house for sale * n= north-facing 4 bed 2 bath house for sale * O * o= oceanview 4 bed 2 bath house for sale * o= outstanding 4 bed 2 bath house for sale * o= open-concept 4 bed 2 bath house for sale * o= original 4 bed 2 bath house for sale * P * p= peaceful 4 bed 2 bath house for sale * p= private 4 bed 2 bath house for sale * p= pet-friendly 4 bed 2 bath house for sale * p= perfect 4 bed 2 bath house for sale * Q * q= quiet 4 bed 2 bath house for sale * q= quaint 4 bed 2 bath house for sale * q= quality 4 bed 2 bath house for sale * q= quick-sale 4 bed 2 bath house for sale * R * r= renovated 4 bed 2 bath house for sale * r= ranch-style 4 bed 2 bath house for sale * r= riverside 4 bed 2 bath house for sale * r= rare find 4 bed 2 bath house for sale * S * s= spacious 4 bed 2 bath house for sale * s= stunning 4 bed 2 bath house for sale * s= south-facing 4 bed 2 bath house for sale * s= single-story 4 bed 2 bath house for sale * T * t= traditional 4 bed 2 bath house for sale * t= two-story 4 bed 2 bath house for sale * t= turnkey 4 bed 2 bath house for sale * t= tranquil 4 bed 2 bath house for sale * U * u= unique 4 bed 2 bath house for sale * u= updated 4 bed 2 bath house for sale * u= upscale 4 bed 2 bath house for sale * u= urban 4 bed 2 bath house for sale * V * v= value 4 bed 2 bath house for sale * v= Victorian 4 bed 2 bath house for sale * v= vacation 4 bed 2 bath house for sale * v= view 4 bed 2 bath house for sale * W * w= waterfront 4 bed 2 bath house for sale * w= well-maintained 4 bed 2 bath house for sale * w= west-facing 4 bed 2 bath house for sale * w= wonderful 4 bed 2 bath house for sale * X * x= xtra large 4 bed 2 bath house for sale * x= xeriscaped 4 bed 2 bath house for sale * x= xquisite 4 bed 2 bath house for sale * x= xtreme value 4 bed 2 bath house for sale * Y * y= young 4 bed 2 bath house for sale * y= yard 4 bed 2 bath house for sale * y= year-round 4 bed 2 bath house for sale * y= yellowstone 4 bed 2 bath house for sale * Z * z= zen 4 bed 2 bath house for sale * z= zoned 4 bed 2 bath house for sale * z= zero-energy 4 bed 2 bath house for sale * z= zippy 4 bed 2 bath house for sale This outline offers a comprehensive list of keyword ideas for your niche in "4 bed 2 bath house for sale," helping you target various aspects of potential search terms related to this property type.

SEE BELOW FOR NEXT STEP

NOW SELECT THE TOP 3-5 THAT INTEREST YOU AND PASTE THEM INTO THIS PROMPT. I CHOOSE - renovated 4 bed 2 bath house for sale

BASED ON MY NICHE; INSERT YOUR NICHE HERE, SUGGEST KEYWORDS WE SHOULD BE TARGETING IN PAY PER CLICK AS WELL AS SEO. PROVIDE 20 WORDS EACH OF LOW TIER, MID TIER , AND HIGH TIER KEYWORDS WE SHOULD TARGET. ____________________________________________________________________________

BASED ON MY NICHE; renovated 4 bed 2 bath house for sale , SUGGEST KEYWORDS WE SHOULD BE TARGETING IN PAY PER CLICK AS WELL AS SEO. PROVIDE 20 WORDS EACH OF LOW TIER, MID TIER , AND HIGH TIER KEYWORDS WE SHOULD TARGET.

Go paste this into chatgpt.com

For your niche "renovated 4 bed 2 bath house for sale," here are suggested keywords categorized by their search volume and competition level: Low Tier Keywords (Low Competition, Low Search Volume)

  1. "renovated 4 bed 2 bath homes near me"
  2. "affordable renovated 4 bed 2 bath house"
  3. "renovated 4 bed 2 bath house for sale in suburbs"
  4. "small town renovated 4 bed 2 bath house"
  5. "4 bedroom 2 bathroom renovated cottage"
  6. "energy-efficient renovated 4 bed 2 bath house"
  7. "4 bed 2 bath updated homes with yard"
  8. "renovated 4 bed 2 bath starter home"
  9. "4 bed 2 bath house modern renovation"
  10. "eco-friendly renovated 4 bed 2 bath home"
  11. "renovated 4 bed 2 bath homes under $300k"
  12. "luxury renovated 4 bed 2 bath home"
  13. "4 bed 2 bath house recent renovation"
  14. "family-friendly renovated 4 bed 2 bath house"
  15. "move-in ready 4 bed 2 bath house"
  16. "renovated 4 bed 2 bath homes in quiet neighborhoods"
  17. "vintage renovated 4 bed 2 bath house"
  18. "historic renovated 4 bed 2 bath home"
  19. "renovated 4 bed 2 bath house with new appliances"
  20. "4 bed 2 bath house with renovated kitchen"

Mid Tier Keywords (Medium Competition, Medium Search Volume)

  1. "renovated 4 bed 2 bath homes for sale"
  2. "updated 4 bedroom 2 bathroom house"
  3. "4 bed 2 bath house for sale newly renovated"
  4. "renovated 4 bed 2 bath house for sale in city"
  5. "4 bed 2 bath house modern updates"
  6. "renovated 4 bed 2 bath house real estate"
  7. "updated 4 bed 2 bath home listings"
  8. "4 bed 2 bath house with modern amenities"
  9. "newly renovated 4 bed 2 bath house"
  10. "4 bed 2 bath house for sale with upgraded features"
  11. "renovated 4 bed 2 bath homes in desirable areas"
  12. "renovated 4 bed 2 bath house property listings"
  13. "modernized 4 bed 2 bath house"
  14. "4 bed 2 bath house with remodeled kitchen"
  15. "renovated 4 bed 2 bath family home"
  16. "turnkey renovated 4 bed 2 bath house"
  17. "4 bed 2 bath house with updated bathrooms"
  18. "4 bed 2 bath renovated house listings"
  19. "remodeled 4 bed 2 bath house for sale"
  20. "4 bed 2 bath house with recent renovations"

High Tier Keywords (High Competition, High Search Volume)

  1. "4 bed 2 bath house for sale"
  2. "renovated home for sale"
  3. "updated house for sale"
  4. "renovated houses near me"
  5. "modern 4 bedroom house for sale"
  6. "4 bed 2 bath home listings"
  7. "houses for sale with renovations"
  8. "move-in ready homes for sale"
  9. "4 bed 2 bath homes for sale"
  10. "newly renovated homes for sale"
  11. "updated real estate listings"
  12. "4 bedroom home for sale"
  13. "remodeled house for sale"
  14. "homes with modern updates"
  15. "luxury renovated homes"
  16. "real estate renovated homes"
  17. "homes for sale with upgraded features"
  18. "homes for sale with new renovations"
  19. "turnkey homes for sale"
  20. "remodeled 4 bedroom house"

These keywords cover a range of competition levels and search volumes, helping you target different segments within your niche of "renovated 4 bed 2 bath house for sale."

NOW I HAVE SELECTED YOUR NICHE HERE FROM THE“ BOTTOM TIERED KEYWORDS. I pasted it into google and you still see predicted ideas!!

NOW I HAVE SELECTED 4 bed 2 bath house with renovated kitchen FROM THE“ BOTTOM TIERED KEYWORDS. I pasted it into google and you still see predicted ideas!!

SO, Rinse and repeat.

I want to research 4 bed 2 bath house with renovated kitchen

BUT I AM GOING TO GO GET MORE IDEAS FIRST.

BASED ON MY NICHE; 4 bed 2 bath house with renovated kitchen , SUGGEST KEYWORDS WE SHOULD BE TARGETING IN PAY PER CLICK AS WELL AS SEO. PROVIDE 20 WORDS EACH OF LOW TIER, MID TIER , AND HIGH TIER KEYWORDS WE SHOULD TARGET.

PASTE INTO CHATGPT.COM

For your niche "4 bed 2 bath house with renovated kitchen," here are suggested keywords categorized by their search volume and competition level: Low Tier Keywords (Low Competition, Low Search Volume)

  1. "4 bed 2 bath home renovated kitchen near me"
  2. "affordable 4 bed 2 bath with updated kitchen"
  3. "4 bed 2 bath house with gourmet kitchen"
  4. "recently renovated kitchen 4 bed 2 bath"
  5. "energy-efficient kitchen 4 bed 2 bath home"
  6. "4 bed 2 bath house modern kitchen upgrade"
  7. "budget-friendly 4 bed 2 bath house with new kitchen"
  8. "4 bed 2 bath house with custom kitchen"
  9. "renovated kitchen 4 bed 2 bath homes under $300k"
  10. "luxury kitchen 4 bed 2 bath home"
  11. "4 bed 2 bath house with chef’s kitchen"
  12. "move-in ready 4 bed 2 bath with new kitchen"
  13. "4 bed 2 bath house with high-end kitchen appliances"
  14. "modernized kitchen 4 bed 2 bath home"
  15. "family-friendly 4 bed 2 bath house with updated kitchen"
  16. "vintage home with renovated kitchen 4 bed 2 bath"
  17. "4 bed 2 bath house with upgraded kitchen cabinetry"
  18. "4 bed 2 bath home with renovated open kitchen"
  19. "4 bed 2 bath house with island kitchen"
  20. "updated kitchen with 4 bed 2 bath home listings"

Mid Tier Keywords (Medium Competition, Medium Search Volume)

  1. "4 bed 2 bath house renovated kitchen for sale"
  2. "updated kitchen 4 bed 2 bath house listings"
  3. "modern kitchen 4 bed 2 bath homes"
  4. "4 bed 2 bath house with upgraded kitchen appliances"
  5. "renovated kitchen 4 bed 2 bath home near me"
  6. "4 bed 2 bath house for sale with modern kitchen"
  7. "4 bed 2 bath home with kitchen remodel"
  8. "4 bed 2 bath home with contemporary kitchen"
  9. "4 bed 2 bath house with updated kitchen features"
  10. "4 bed 2 bath house new kitchen design"
  11. "recently remodeled kitchen 4 bed 2 bath home"
  12. "4 bed 2 bath home for sale with renovated kitchen"
  13. "turnkey 4 bed 2 bath house with upgraded kitchen"
  14. "4 bed 2 bath home with stylish kitchen"
  15. "4 bed 2 bath house with energy-efficient kitchen"
  16. "4 bed 2 bath home with gourmet kitchen for sale"
  17. "4 bed 2 bath house modern kitchen remodel"
  18. "4 bed 2 bath home with open-concept kitchen"
  19. "4 bed 2 bath home with new kitchen appliances"
  20. "4 bed 2 bath house with high-end kitchen features"

High Tier Keywords (High Competition, High Search Volume)

  1. "4 bed 2 bath house for sale"
  2. "renovated kitchen for sale"
  3. "updated house for sale"
  4. "kitchen remodel house for sale"
  5. "modern 4 bedroom house for sale"
  6. "homes for sale with updated kitchen"
  7. "4 bed 2 bath home listings"
  8. "houses for sale with modern kitchens"
  9. "move-in ready homes with new kitchen"
  10. "4 bed 2 bath homes with gourmet kitchen"
  11. "renovated kitchen homes for sale"
  12. "4 bedroom home with upgraded kitchen"
  13. "remodeled kitchen house for sale"
  14. "homes with modern kitchens"
  15. "luxury kitchen homes for sale"
  16. "real estate renovated kitchens"
  17. "homes for sale with upgraded kitchen features"
  18. "homes with new kitchen renovations"
  19. "turnkey homes with renovated kitchens"
  20. "remodeled kitchen homes for sale"

These keywords are designed to help you target different segments within your niche of "4 bed 2 bath house with renovated kitchen," allowing you to optimize both PPC and SEO strategies effectively.

NOW I WILL GO THROUGH KEYWORDS AND SEE MY COMPETITORS ON SEARCH ENGINES:

GOOGLE.COM searched-4 bed 2 bath home renovated kitchen near me

YOUTUBE.COM searched- 4 bed 2 bath home renovated kitchen near me

INSTAGRAM.COM searched- 4 bed 2 bath home renovated kitchen near me

TIKTOK.COM searched- 4 bed 2 bath home renovated kitchen near me

ETC. ____________________________________________________________________________

Now use this prompt to find out what questions people have regarding 4 bed 2 bath home renovated kitchen near me

WHAT QUESTIONS ABOUT YOUR NICHE HERE ARE PEOPLE ALSO ASKING IN FORUMS, REDDIT, QUORA, GOOGLE Etc.

WHAT QUESTIONS ABOUT 4 bed 2 bath home renovated kitchen near me ARE PEOPLE ALSO ASKING IN FORUMS, REDDIT, QUORA, GOOGLE Etc.

GO Paste this into chatgpt. Here are some common questions people are asking about "4 bed 2 bath home renovated kitchen near me" across forums, Reddit, Quora, and Google: General Interest Questions

  1. Where can I find a 4 bed 2 bath home with a renovated kitchen near me?
  2. How much does a 4 bed 2 bath home with a renovated kitchen cost in my area?
  3. What are the benefits of buying a 4 bed 2 bath home with a renovated kitchen?
  4. Is it worth paying more for a home with a recently renovated kitchen?
  5. How do I know if the kitchen renovation in a 4 bed 2 bath home was done well?
  6. What features should I look for in a renovated kitchen in a 4 bed 2 bath house?
  7. Are there any specific neighborhoods where I can find 4 bed 2 bath homes with renovated kitchens?
  8. What is the typical increase in home value after a kitchen renovation?
  9. How does a renovated kitchen affect the resale value of a 4 bed 2 bath home?
  10. Can I customize a 4 bed 2 bath home’s kitchen renovation before buying it?

Practical and Decision-Making Questions

  1. How do I negotiate the price for a 4 bed 2 bath home with a renovated kitchen?
  2. What are the most popular kitchen styles in renovated 4 bed 2 bath homes?
  3. What should I inspect in a renovated kitchen before buying a 4 bed 2 bath house?
  4. Are homes with renovated kitchens in higher demand in the current market?
  5. What should I ask the seller about the kitchen renovation in a 4 bed 2 bath home?
  6. Can I get a home inspection specifically focused on the renovated kitchen?
  7. How can I verify that the kitchen renovation was done with quality materials?
  8. What are common issues found in renovated kitchens in older homes?
  9. How much more should I expect to pay for a 4 bed 2 bath home with a new kitchen compared to one without?
  10. What are the key differences between a newly built kitchen and a renovated one?

Concerns and Considerations

  1. Is it possible to over-renovate a kitchen in a 4 bed 2 bath home?
  2. What are the potential downsides of buying a 4 bed 2 bath home with a recently renovated kitchen?
  3. Can a kitchen renovation hide underlying problems in a 4 bed 2 bath house?
  4. How do I ensure the renovated kitchen meets my family’s needs?
  5. Are there financing options available for buying homes with newly renovated kitchens?
  6. Is it better to renovate the kitchen myself or buy a home that already has a renovated kitchen?
  7. What questions should I ask the contractor who renovated the kitchen before buying the home?
  8. How do kitchen renovation trends impact the long-term value of a 4 bed 2 bath home?
  9. What is the average cost of maintaining a renovated kitchen in a 4 bed 2 bath home?
  10. How can I find reviews or feedback on the quality of kitchen renovations in homes I’m interested in?

These questions reflect the various concerns, interests, and practical considerations people have when exploring or purchasing a 4 bed 2 bath home with a renovated kitchen, providing valuable insights into what potential buyers or homeowners might be thinking. 4o

Clickable sources and applicable resources

ClickFunnels educational resources

Acquisition.com educational resources

Google AI search guidance

Google spam policies

HUD fair housing resources

Google Keyword Planner

Assigned document D0216, source 1

Original named domain 1; exact historical spelling, availability unverified

Apply the pain, purchasing-power, spending, and improvement filters

This assigned document presents a Hormozi-style interpretation of niche selection. Its attributed quotations are not independently authenticated here. Teach its method as the document's framework: identify an urgent, costly problem, establish who can fund a solution, inspect existing spending, and determine what improvement you can deliver. Passion can motivate the operator, but customer evidence must support the offer.

Start with purchasing power. Ask who pays, which budget funds the purchase, and what a realistic price would displace. The source warns against markets described as students, artists, or low-income dreamers; occupation alone does not establish an individual's budget. Translate that warning into a budget-fit test rather than dismissing whole groups. A lower-priced offer, sponsor, employer, or different payer may change the economics.

Next, examine pain. The document gives three illustrative situations: a business running out of leads, a person concerned about excess weight and health, and a worker urgently seeking additional income. These examples illustrate perceived urgency; they are not evidence of medical outcomes, guaranteed sales, or actual customer findings. Ask the customer what they are trying to fix now in their business, health, or relationship, then identify the cost of leaving it unresolved.

Third, inspect existing spending. Are customers hiring coaches, consultants, or agencies? Buying courses, software, or services? Are competitors winning business? These observations suggest a market worth investigating; competitor visibility alone does not prove its profitability or your ability to win customers.

Fourth, define an improvement: a faster result, lower total cost, easier execution, a simpler process, or less frustration. Compare against what the customer currently uses. This connects the document to the course's Hormozi value-equation work and Brunson offer positioning: a specific buyer and desired result must support a credible promise and a workable delivery mechanism.

Write and test the niche statement

Use this structure: I help [specific buyer] solve [painful problem] so they can [desired outcome]. The source examples are gym owners adding $10,000 per month in 30 days without more leads; real estate agents getting qualified appointments without cold calling; and ecommerce brands improving margins through pricing. These are example offer statements, not substantiated RISER promises. A quantified claim needs evidence before use.

Talk to prospective customers before building the full product. Construct a minimum viable offer and test willingness to book or buy. Where a presale is used, explain what is and is not built, the delivery commitment, and the terms. Track responses and conversions with clear denominators and dates. Fast buying or booking is useful evidence, but a booking is not a purchase. Hesitation may reflect urgency or unclear messaging, as the source suggests, and may also reflect trust, price, timing, fit, or delivery concerns. Record the actual objection before changing the offer.

The source's avoidance list covers insufficient budget, absent urgency, demand for free help, persistent consumption without implementation, and people who do not recognize the alleged problem. Treat these as fit questions, not insults or reasons to manufacture fear. Ask whether the offer fits the person's circumstances and whether implementation is realistic.

Complete the six-trait and four-question decision

TraitEvidence to obtain
PainfulA specific, urgent problem described by the buyer
ValuableA desired outcome worth paying for
ObviousA problem the buyer recognizes without invented pressure
CommonEnough potential buyers share the problem
AccessibleA practical way to reach those buyers
SolvableA result you can help achieve measurably or promptly

Finish with four questions: Who has both the problem and a way to pay? Are they spending on it already? Can you improve the current result or experience? Can you demonstrate that improvement before scaling? Submit the niche statement, interview evidence, existing alternatives, offer test results, and unresolved objections. Strong pain improves relevance; it does not make every sale easy.

Understand the single supplied Dream 100 email

This guide contains one introductory email with placeholders. Email #2 and Email #3 are headings only; no follow-up text is supplied. Preserve that incompleteness instead of inventing two source emails.

The first message identifies something the recipient sells, states the sender is in the same niche, asks to build a mutually helpful relationship, links the sender's offers, thanks the reader, and signs with a name. Its network/net-worth line is a motivational slogan, not evidence that contact quantity produces income. Personalize only with accurate observations and offer a concrete reason the relationship could help both audiences.

The postscript asks for a simple Yes and promises a prompt reply. It also promises never to contact the person again otherwise. This is a consequential commitment: if retained, do not silently enroll nonresponders in a follow-up sequence. The blank second/third-email headings do not override the first email's promise. A response is not evidence of commitment to promote or of completed promotion.

The website, offer, and sender-name fields are blank. For a RISER draft, use www.risernationcorp.com only where relevant and verify the intended offer destination. No email address, actual recipient, sent message, or campaign result is supplied. The all-caps final sentence is source tone, not a required RISER voice.

Apply the relationship principle without inventing a campaign

Connect this to Brunson's Dream 100 through a relevant audience relationship, and to the existing value framework through a specific useful contribution. Prepare a draft containing a truthful observation, proposed mutual benefit, relevant link, identity, and response expectations you can honor. Do not claim an affiliation before agreement. This lesson does not send outreach, and missing follow-ups remain identified as missing.

Use all three tracker sections without mistaking empty fields for results

The available extracted workbook text contains three worksheets and no populated lead records or numerical results. This review explains that available structure; it does not certify unextracted formulas, formatting, hidden content, or workbook behavior.

The DREAM 100 LEADS sheet has context fields OFFER, NICHE, and OWNER, followed by seven columns: NAME, EMAIL/SUPPORT, SENT DAY#1 EMAIL, REPLY?, FOLLOW UP SENT, COMMITTED TO PROMOTE, and PROMOTED. Record actual dates or evidence according to a defined convention. OWNER's intended meaning is not specified; define it in the operating instructions rather than assuming it identifies the recipient or internal relationship manager.

Keep the stages distinct. Sending is not a reply; a reply is not an agreement; an agreement is not evidence that promotion happened. Link any promotion record to observable delivery evidence and a date. The companion email promises no further contact without a response, so the existence of a FOLLOW UP SENT column does not authorize ignoring that promise.

Sheet2 is labeled DAYS SINCE CONTACT ORIGINATED. Its STATS table has day columns 1 through 7 and the rows NEW AFFILIATES, PROMOTIONS, NON PERFORMERS, REVIEWING, and FOLLOWED UP. Define whether a cell counts events that day or a cumulative status, the cohort start, and how repeat events are handled. The extracted text supplies no definitions or formulas. In particular, define a due date and evidence before labeling someone a nonperformer.

The TASKS worksheet likewise uses DAYS and columns 1 through 7. Preserve all ten source task rows: CALL MADE; Affiliate Signed Up on JV PAge; Sign Up Reminder Sent; 2nd Inquiry Made?; 1st Promo DAte; 2nd Promo DAte; Evergreen Offer; Promo and Email; 2nd Promo and Email; and Offer 2nd Teir. These are source labels, including original spelling. A JV-page registration, a planned promotion date, an evergreen offer, and a completed email are different events; document what completion means for each.

Establish the workflow before recording progress

Define the offer and audience, identify the responsible owner, and maintain appropriate contact information for the relationship. Record actual communications and agreed next actions, then update the relevant status with evidence. The day headers do not prescribe contacting someone daily or escalating automatically. The source does not supply affiliate terms, a working JV signup page, a second-tier offer, or an evergreen promotion agreement.

Use the tracker to support the existing Dream 100 relationship plan and measurable acquisition work. Submit the field definitions, truthful records, and review cadence. Leave empty values empty or mark them pending; no lead, agreement, or promotion should be invented to populate the sheet.

Use all three tracker sections without mistaking empty fields for results

This tracker variant exposes three CSV-like extracted sections and no populated lead records or numerical results. The first has an empty column between NAME and EMAIL/SUPPORT; unnamed columns, zero-based row indices, and a blank task row are extraction/layout artifacts, not additional leads or tasks. Unlike the companion extraction, explicit worksheet names are not provided for all sections here. This review explains that available structure; it does not certify unextracted formulas, formatting, hidden content, or workbook behavior.

The first leads section has context fields OFFER, NICHE, and OWNER, followed by seven columns: NAME, EMAIL/SUPPORT, SENT DAY#1 EMAIL, REPLY?, FOLLOW UP SENT, COMMITTED TO PROMOTE, and PROMOTED. Record actual dates or evidence according to a defined convention. OWNER's intended meaning is not specified; define it in the operating instructions rather than assuming it identifies the recipient or internal relationship manager.

Keep the stages distinct. Sending is not a reply; a reply is not an agreement; an agreement is not evidence that promotion happened. Link any promotion record to observable delivery evidence and a date. The companion email promises no further contact without a response, so the existence of a FOLLOW UP SENT column does not authorize ignoring that promise.

The second section is labeled DAYS SINCE CONTACT ORIGINATED. Its STATS table has day columns 1 through 7 and the rows NEW AFFILIATES, PROMOTIONS, NON PERFORMERS, REVIEWING, and FOLLOWED UP. Define whether a cell counts events that day or a cumulative status, the cohort start, and how repeat events are handled. The extracted text supplies no definitions or formulas. In particular, define a due date and evidence before labeling someone a nonperformer.

The TASKS section likewise uses DAYS and columns 1 through 7. Preserve all ten source task rows: CALL MADE; Affiliate Signed Up on JV PAge; Sign Up Reminder Sent; 2nd Inquiry Made?; 1st Promo DAte; 2nd Promo DAte; Evergreen Offer; Promo and Email; 2nd Promo and Email; and Offer 2nd Teir. These are source labels, including original spelling. A JV-page registration, a planned promotion date, an evergreen offer, and a completed email are different events; document what completion means for each.

Establish the workflow before recording progress

Define the offer and audience, identify the responsible owner, and maintain appropriate contact information for the relationship. Record actual communications and agreed next actions, then update the relevant status with evidence. The day headers do not prescribe contacting someone daily or escalating automatically. The source does not supply affiliate terms, a working JV signup page, a second-tier offer, or an evergreen promotion agreement.

Use the tracker to support the existing Dream 100 relationship plan and measurable acquisition work. Submit the field definitions, truthful records, and review cadence. Leave empty values empty or mark them pending; no lead, agreement, or promotion should be invented to populate the sheet.

The pain-report micro-offer: deliver a small paid result

A pain report gives a customer a focused explanation of a problem and a useful next step. In this source it is an alternate validation route: deliver a small paid report before committing to the larger offer. The customer should receive useful work for the price even if they never buy anything else. A purchase tests willingness to pay for this report under these conditions; it does not prove that every hypothesis about the buyer is true.

Preserve the source's price, timing, and course context

This is M4.4, $9 Pain Report Micro-Offer, from the Riser Nation Academy 2026 syllabus. Its parent is C4, Market Reality & Niche Validation: Stage 1, Harbor; Build to Do; prerequisite C3 Primary Avatar Profile; 10–14 hours over two weeks. Those legacy identifiers and parent-course hours provide context, while the current workbook determines where this material belongs. The excerpt preserves the master syllabus rather than reproducing it in full.

The title emphasizes $9; the body permits a $9–$27 Pain Report. Keep the range visible and record the actual tested price instead of treating the title as the only permitted amount. The source says the report validates demand and produces an artifact for C6. C6 is a legacy main-offer reference, not an instruction to reassign this document to current Course 6.

The shared parent introduction calls for five real dollars from five real people and frames five paying customers as proof. This module calls the report an alternate route but supplies no separate report-sales threshold. Track both the report's results and any applicable current lesson gate; do not invent a new numerical pass rule. The claim that a nine-dollar buyer proves both pain and a wallet overstates what a transaction establishes. Record the expressed buying reason and subsequent use of the report before drawing conclusions about the problem, budget, or a larger purchase.

Build a report that earns its price

The source names a Pain Report template without its contents. Use the following RISER adaptation to create a concise deliverable with a clear purpose.

Report sectionWhat to teach and include
Customer and situationIdentify the intended reader, the problem addressed, and the limits of the report. State what inputs were actually reviewed.
Evidence of the painUse relevant observations, customer language, and source links. Distinguish direct evidence, interpretation, and hypothetical examples.
Problem explanationExplain the obstacles and plausible causes without treating guesses as a confirmed diagnosis. Identify missing information.
Priority and consequenceExplain which issue deserves attention first and why. Label any cost estimate with its assumptions; do not invent financial impact.
Practical next stepGive the buyer an action, required inputs, and a way to judge whether it helped. Keep it feasible within the scope sold.
Boundaries and resourcesInclude source links, limitations, unanswered questions, and any additional resource needed. Disclose where a resource is unavailable.

Read the report aloud as if the buyer is beside you. Can that person recognize the problem, understand the evidence, and act on one useful recommendation? If the document is only a teaser for a larger purchase, revise it so the promised small result stands on its own. Do not represent speculative research or AI-generated language as customer testimony.

Execute the 48-hour delivery sprint

The excerpt specifies a 48-hour delivery sprint but no timetable or starting event. The following schedule is an adaptation. For this exercise, define the clock as starting when payment and agreed required inputs are received, and disclose that condition before an order. If the actual offer promises 48 hours from payment, honor that promise instead of silently resetting the clock.

  1. Hours 0–4: confirm the buyer's scope, inputs, format, delivery channel, and deadline. State any missing information and resolve whether you can still deliver what was sold.
  2. Hours 4–16: review the relevant evidence and sources. Record where each important finding came from. Keep assumptions separate and avoid expanding into an unrelated research project.
  3. Hours 16–28: draft the report using the six sections above. Select a manageable next step and explain the reason for that priority.
  4. Hours 28–40: check factual support, completeness against the promise, readability, source links, and delivery formatting. Verify that examples are labeled and that the buyer has the resources needed for the proposed action.
  5. Hours 40–48: deliver through the agreed channel, record delivery, invite a focused clarification, and capture feedback on usefulness. If the deadline becomes unrealistic, communicate promptly rather than letting it lapse without explanation.

These time blocks organize the source's 48-hour requirement; they are not a supplied original SOP. Record actual working time separately from elapsed turnaround. Both matter when judging whether the price covers the work and whether the process can be repeated.

Use the report to inform the main offer

The source's third named component is conversion to the C6 main offer. No conversion script or C6 offer specification is included. After delivery, identify which problem remains beyond the small report's scope. Explain an optional next offer only when it directly addresses that need. Show what additional work it includes, what it requires from the buyer, and how it differs from what they already purchased. A report buyer does not owe you another purchase.

Carry the report forward as an artifact: preserve the problem statement, evidence, priorities, delivered recommendation, buyer questions, and observed results. Use those findings to refine the larger offer instead of assuming that a low-price purchase validates a higher price. Record invitations, subsequent purchases, non-purchases, and reasons separately; do not describe an invitation as a conversion.

The Brunson connection is a small initial offer that begins a useful customer journey and can support a relevant next step. The Hormozi connection is a concrete desired result with a short wait, manageable effort, and credible evidence. Neither connection makes the source's $9–$27 price or 48-hour sprint a universal rule or an endorsed promise.

Submit the completed test and its resources

Submit the report, price and scope used, delivery timestamps, source list, actual working time, payment and refund records, buyer feedback, and any main-offer follow-up results. Explain what the evidence supports and what remains uncertain. A completed report, a sale, useful delivery, and a larger-offer sale are different milestones; track them separately.

Read the assigned M4.4 - $9 Pain Report Micro-Offer source

The original Pain Report template, detailed sprint SOP, C3 avatar artifact, and C6 main-offer materials are not linked or reproduced in this excerpt. The report structure and timetable above are clearly labeled teaching adaptations. Preserve this gap rather than inserting invented destinations or claiming to have reviewed the missing originals.

Build an avatar that separates evidence from imagination

This prompt starts with four inputs: niche, offer type, main problem and desired transformation. Supply real business scope before asking for a vivid profile. Its examples include coaches, parents, ecommerce founders, real-estate agents, courses, services, memberships and planners; these are possible inputs, not RISER's automatically selected audience. A dream such as $5K per month, freedom from burnout or a sold-out launch is not a verified result or an advertising promise.

Complete all eleven profile sections

Section 1 gives the composite a realistic first name for easier discussion. Label it fictional and avoid implying that a real customer said the generated words. Section 2 records age range, gender and location only where relevant and supported; use unknown or a range when evidence is absent, and do not infer a person's sensitive traits from a marketing guess.

Section 3 describes goals, dreams and the customer's own definition of success. Section 4 records frustrations and feared consequences in respectful language, distinguishing interview evidence from hypotheses. A vivid fear is not evidence of prevalence and should not become manipulative pressure in copy.

Section 5 identifies online platforms, forums and communities. Section 6 identifies creators, coaches, brands or influencers the audience trusts. Section 7 identifies blogs, YouTube channels, books and podcasts. Cite observed sources and check dates; a model-generated list is a research shortlist, not proof of audience behavior or endorsement.

Section 8 describes preferred formats such as short video, podcasts, email tips or visual guides, with evidence where available. Section 9 asks for two-to-four favorite brands. Record whether that means actual purchases, stated preference or an untested suggestion. Section 10 documents buying objections: budget, fit, time, trust and other stated concerns. The source calls them thoughts, beliefs or excuses; treat them as useful decision information rather than dismissing legitimate constraints.

Section 11 describes the desired post-purchase outcome in customer terms, with an explicit distinction between aspiration and demonstrated results. Keep it consistent with what the offer can deliver and what the customer must contribute.

Create the story and optional hooks

Write the requested one-paragraph character story using the profile's supported facts and clearly labeled composite elements. The optional bonus is three-to-five hooks or angles in plain, emotionally resonant language. For each hook, connect a real problem with a useful next step; do not manufacture testimonials, imply personal knowledge of a reader's private life or promise unsupported earnings.

Brunson's dream-customer and hook-story-offer ideas organize the message. Hormozi's value framework tests whether the transformation, proof, time and effort are credible. A practical submission includes the four inputs, all eleven sections, the story, optional hooks, citations, unknowns and a plan to validate the largest assumptions with actual customers. This is an evidence-organizing exercise, not proof that an AI knows the market.

Complete available assigned-document reference

The full available source text follows for study. Its embedded prompts, proposed actions, sample claims and historical labels are source material, not instructions executed by this lesson. Apply the teaching explanations above.

CNX.1.4.07 – Avatar Prompt.docx

AVATAR PROMPT: Just drop in: * Your niche

* Your offer

* The problem you solve

* The dream result you help people achieve ____________________________________________________________________________

You are a top-tier marketing strategist, specializing in psychographic audience research and offer positioning.

I want you to create the most complete and vivid customer avatar possible for my business.

Here’s what you need to know:

- Niche: [Insert niche — e.g., new online coaches, stay-at-home moms, ecommerce founders, local real estate agents] - Offer Type: [Insert what you’re selling — e.g., digital course, lead gen service, community membership, planner] - Main Problem It Solves: [Insert primary pain point — e.g., no leads, feeling overwhelmed, inconsistent income] - Big Transformation/Promise: [Insert dream result — e.g., $5K/month, freedom from burnout, sold-out launches]

Please build me an emotionally detailed customer avatar with the following sections:

---

1. Name: Give them a realistic first name to bring the profile to life.

2. Age / Gender / Location: Provide age range, gender, and describe where they live (city, suburb, region, country).

3. Goals & Dreams: What are they actively working toward? What does success look like in their eyes?

4. Frustrations & Fears: What’s bothering them most about their current situation? What are they afraid will happen if nothing changes?

5. Where They Hang Out Online: List the main social platforms, forums, or communities they spend time on.

6. Who They Follow / Trust: Name a few influencers, creators, coaches, or brands they look up to and trust.

7. What They Read / Watch: Describe the blogs, YouTube channels, books, or podcasts they consume regularly.

8. Preferred Content Type: Do they love short-form video, podcasts, email tips, visual guides, etc.?

9. Favorite Brands: List 2–4 brands (personal or business) they already buy from, love, or resonate with.

10. Typical Buying Objections: What thoughts, beliefs, or excuses hold them back from purchasing?

11. Dream Outcome: Describe what life/business looks like for them once the problem is solved and their dream is achieved.

---

Then finish with:

🎯 One Paragraph Story Write a short, engaging story-style paragraph summarizing their life, struggles, and what they’re chasing — like a movie character arc.

📣 Bonus (optional) List 3–5 marketing hooks, angles, or emotional messaging phrases that would stop this person mid-scroll or open an email.

Write in plain language, emotionally resonant, and optimized for offer creation and ad targeting.

Clickable sources and applicable resources

ClickFunnels education

Acquisition.com education

Assigned document D0253, source 1

D0313 — Build the psychology, positioning and end-state workbook
Opening: three legacy lessons, one evidence-based workbook

The source's Module 1 contains three lessons and proposes a Circle presentation format. Keep all three parts in the spreadsheet-assigned lessons; do not replace our course numbering with its legacy 1.1–1.3 labels. Its goal is to connect decision behavior, positioning and an intended transformation. The claim that people always buy emotionally and justify logically is too absolute; decisions can involve emotion, reasoning, constraints and context.

Part one: examine three persuasion frames

The source references Ariely's *Predictably Irrational*, Cialdini's *Influence* and the Brafmans' *Sway*. Its three named concepts are loss aversion, commitment bias and fairness bias. Here, treat them as hypotheses about how a message might be interpreted rather than deterministic buttons to press.

For loss aversion, describe an evidenced cost of leaving a problem unresolved. Do not manufacture a loss or imply that declining the offer is dangerous. For commitment, acknowledge work the customer has actually done and offer a useful next step; previous effort does not obligate another purchase. For fairness, explain transparent access, terms or treatment. The source's “don't get left behind while others gain” example also resembles social comparison and fear of missing out, so it is not a clean demonstration of fairness alone.

Complete all four worksheet fields: original headline, loss-framed rewrite, commitment-framed rewrite and fairness-framed rewrite. Authored examples for an onboarding workshop: “Find the missing step delaying your first client milestone”; “Turn your existing onboarding checklist into a clear next-action plan”; and “See exactly which planning support your workshop fee includes.” These are illustrative drafts, not tested winning headlines. Review the three concepts, produce all three rewrites and save the best supported version in the Funnel Copy Draft. Choose on clarity and truthful fit, then test response rather than assuming persuasion from the label.

The named Psychology GPT is described as generating ten rewrites per headline. No agent link, prompt or actual generated set is supplied. Preserve that missing-tool status; the manual exercise remains usable.

Part two: map positioning and a possible market gap

The source contrasts crowded red oceans with blue-ocean market creation and cites positioning in the customer's mind. “AI-first funnel agency” is its category example. Naming a category of one does not establish uncontested demand or eliminate competition. Document what buyers value and which alternatives already provide it.

Research three competitors. For each, record the primary offer, price points and positioning angle, with source and date. The printed worksheet lines mention competitor/offer/positioning but omit price; retain the exercise's price requirement as an additional field. Then write the proposed Blue Ocean category and the evidence for the gap. Complete the three checklist items: researched competitors, mapped positioning chart and a distinct category hypothesis. Call it a hypothesis until customer evidence supports it.

Competitor Mapper GPT is a named proposed aid without a supplied link or configuration. A generated map would still need source verification. The official Blue Ocean ERRC resource below is a related framework, not the missing RISER GPT.

Part three: define the end in mind

Covey's Habit 2 is “Begin with the End in Mind.” Translate that planning principle into a specific customer destination before building a funnel, content or community. The source connects a clear journey, upfront outcomes and the “Risers” identity. Clear expectations may support a better experience, but the document does not prove that setting outcomes by itself reduces churn.

Write the client's twelve-month outcome and address the source's four examples: revenue goal, funnel launch, offer scaled and community built. Distinguish controllable deliverables from revenue aspirations. Authored example: “Within twelve months, complete a tested offer brief, launch a reviewed funnel, document one repeatable delivery process and establish a community onboarding routine.” This is a planning example, not a promised result. If adding a revenue target, label assumptions and dependencies.

Complete the worksheet “In 12 months, my ideal client will have…” and the checklist: outcome defined, aligned with the value ladder and reflected in the community onboarding script. Persona GPT (Nina) is named as an avatar and scenario generator, but its actual prompt and link are absent. An AI scenario is not a customer fact.

Translate the Circle layout into this course page

The source proposes an intro as a long-form post or video, an exercise as a worksheet PDF or embedded form, a tickable checklist and direct toolkit links. Our GHL accordion preserves those four roles with written teaching, worksheet fields, completion items and verified available resources. The source does not supply PDFs, forms or agent destinations; do not label placeholders as working downloads.

Brunson's value ladder connects the entry experience with continuing value. Hormozi's offer lens helps clarify the destination, evidence, time and effort. Finish with three headline variants, the complete three-competitor chart and the twelve-month outcome record.

FranklinCovey Habit 2 · Blue Ocean ERRC grid · ClickFunnels value ladder · Acquisition.com training

The books named in this source can be identified through Dan Ariely's Predictably Irrational page, Cialdini's books and publications and the publisher's Sway record. These identify related works; they do not authenticate every simplified claim in the workbook or replace its missing GPT tools.

Assigned source links

D0313 original source 1

Complete returned native document text

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

📖 Riser Nation Academy
Workbook Style

Module 1: Foundations – Psychology & Positioning
Goal: Understand how irrational behavior, positioning, and end-goal clarity define Riser Nation’s edge.

Lesson 1.1: The Psychology of Irrational Behavior
Intro:
 Human beings rarely make decisions based on logic alone. We buy emotionally and justify with logic. This lesson pulls from Ariely (Predictably Irrational), Cialdini (Influence), and Brafmans (Sway).
Core concepts:

Loss Aversion – fear of losing outweighs potential gain.

Commitment Bias – once invested, people stick even when irrational.

Fairness Bias – people act against their best interest if they feel cheated.

Exercise:
 Take your current offer headline. Rewrite it 3 different ways using:
Loss aversion framing.

Commitment bias (“You’ve already started…”).

Fairness framing (“Don’t get left behind while others gain…”).

Worksheet Prompt:
Original Headline: ____________

Loss Aversion Rewrite: ____________

Commitment Bias Rewrite: ____________

Fairness Rewrite: ____________

Checklist:
 ✅ Reviewed 3 psychological triggers.
 ✅ Rewrote offer headline 3x.
 ✅ Saved best version for Funnel Copy Draft.
AI Toolkit: Psychology GPT → generates 10 persuasion rewrites for each headline.

Lesson 1.2: Market Positioning & Blue Oceans
Intro:
 Competing in “red oceans” (crowded markets) leads to price wars. “Blue Ocean Strategy” teaches us to define uncontested space, while Trout’s Positioning reminds us the battle is in the mind of the customer.
Core concepts:

Own a category (be the “AI-first funnel agency”).

Claim mental real estate in your market.

Escape competition by reframing the game.

Exercise:
 Map 3 competitors in your niche. Chart their:
Primary offer.

Price points.

Positioning angle.
 Now identify the “gap” — what category can you own?

Worksheet Prompt:
Competitor 1 / Offer / Positioning: ____________

Competitor 2 / Offer / Positioning: ____________

Competitor 3 / Offer / Positioning: ____________

Blue Ocean Category I Can Own: ____________

Checklist:
 ✅ Competitors researched.
 ✅ Positioning chart mapped.
 ✅ Unique “category of one” identified.
AI Toolkit: Competitor Mapper GPT → auto-generates positioning map.

Lesson 1.3: The Riser Nation “End in Mind” Principle
Intro:
 Covey’s 7 Habits highlight: “Begin with the end in mind.” Before building funnels, content, or communities, we define the transformation. Every member, client, or student must know: what is the promised end state?
Core concepts:

Communities thrive when people join a journey with a clear destination.

Set outcomes upfront → reduces churn.

Tie brand identity (“Risers”) to transformation.

Exercise:
 Write your ideal client’s 12-month outcome. Be specific:
Revenue goal.

Funnel launch.

Offer scaled.

Community built.

Worksheet Prompt:
In 12 months, my ideal client will have… ____________

Checklist:
 ✅ Outcome defined.
 ✅ End-in-mind aligned with Value Ladder.
 ✅ Shared with community onboarding script.
AI Toolkit: Persona GPT (Nina) → generates customer avatar + 12-month outcome scenario.

📌 How This Will Look in Circle
Each Lesson = Post or Space Section:
Intro → longform post or video.

Exercise → worksheet PDF upload or embedded form.

Checklist → bullet list students can tick.

AI Toolkit → direct link to GPT agent or prompt template.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1Xcdhr5qcrDe7wb7LJ9TL9HYfYgGUsaDJFmD10V86G1Q/edit?usp=drivesdk"
drive_file_id: "1Xcdhr5qcrDe7wb7LJ9TL9HYfYgGUsaDJFmD10V86G1Q"
created: "2025-08-29T13:33:54.515Z"
modified: "2026-06-04T15:04:17.795Z"
---

# 📖 Riser Nation Academy

📖 Riser Nation Academy
Workbook Style
________________


Module 1: Foundations – Psychology & Positioning
Goal: Understand how irrational behavior, positioning, and end-goal clarity define Riser Nation’s edge.
________________


Lesson 1.1: The Psychology of Irrational Behavior
Intro:
 Human beings rarely make decisions based on logic alone. We buy emotionally and justify with logic. This lesson pulls from Ariely (Predictably Irrational), Cialdini (Influence), and Brafmans (Sway).
* Core concepts:

   * Loss Aversion – fear of losing outweighs potential gain.

   * Commitment Bias – once invested, people stick even when irrational.

   * Fairness Bias – people act against their best interest if they feel cheated.

Exercise:
 Take your current offer headline. Rewrite it 3 different ways using:
      1. Loss aversion framing.

      2. Commitment bias (“You’ve already started…”).

      3. Fairness framing (“Don’t get left behind while others gain…”).

Worksheet Prompt:
         * Original Headline: ____________

         * Loss Aversion Rewrite: ____________

         * Commitment Bias Rewrite: ____________

         * Fairness Rewrite: ____________

Checklist:
 ✅ Reviewed 3 psychological triggers.
✅ Rewrote offer headline 3x.
✅ Saved best version for Funnel Copy Draft.
AI Toolkit: Psychology GPT → generates 10 persuasion rewrites for each headline.
________________


Lesson 1.2: Market Positioning & Blue Oceans
Intro:
 Competing in “red oceans” (crowded markets) leads to price wars. “Blue Ocean Strategy” teaches us to define uncontested space, while Trout’s Positioning reminds us the battle is in the mind of the customer.
            * Core concepts:

               * Own a category (be the “AI-first funnel agency”).

               * Claim mental real estate in your market.

               * Escape competition by reframing the game.

Exercise:
 Map 3 competitors in your niche. Chart their:
                  * Primary offer.

                  * Price points.

                  * Positioning angle.
Now identify the “gap” — what category can you own?

Worksheet Prompt:
                     * Competitor 1 / Offer / Positioning: ____________

                     * Competitor 2 / Offer / Positioning: ____________

                     * Competitor 3 / Offer / Positioning: ____________

                     * Blue Ocean Category I Can Own: ____________

Checklist:
 ✅ Competitors researched.
✅ Positioning chart mapped.
✅ Unique “category of one” identified.
AI Toolkit: Competitor Mapper GPT → auto-generates positioning map.
________________


Lesson 1.3: The Riser Nation “End in Mind” Principle
Intro:
 Covey’s 7 Habits highlight: “Begin with the end in mind.” Before building funnels, content, or communities, we define the transformation. Every member, client, or student must know: what is the promised end state?
                        * Core concepts:

                           * Communities thrive when people join a journey with a clear destination.

                           * Set outcomes upfront → reduces churn.

                           * Tie brand identity (“Risers”) to transformation.

Exercise:
 Write your ideal client’s 12-month outcome. Be specific:
                              * Revenue goal.

                              * Funnel launch.

                              * Offer scaled.

                              * Community built.

Worksheet Prompt:
                                 * In 12 months, my ideal client will have… ____________

Checklist:
 ✅ Outcome defined.
✅ End-in-mind aligned with Value Ladder.
✅ Shared with community onboarding script.
AI Toolkit: Persona GPT (Nina) → generates customer avatar + 12-month outcome scenario.
________________


📌 How This Will Look in Circle
Each Lesson = Post or Space Section:
                                    * Intro → longform post or video.

                                    * Exercise → worksheet PDF upload or embedded form.

                                    * Checklist → bullet list students can tick.

                                    * AI Toolkit → direct link to GPT agent or prompt template.

________________

Turn the operator identity into observable working habits

Outline

  1. Understand the source's identity-before-skill proposition.
  2. Translate it into accountable decisions and work products.
  3. Identify the three referenced exercises that are not supplied.

Read the source in its original context

This excerpt belongs to the legacy Harbor Orientation and Riser Manifesto course. It labels that course Pre-Stage, Learn, with no prerequisite and six to eight hours over one week, repeating the metadata twice. These are parent-course estimates, not the duration of this short lesson or a replacement for the current twelve-course map.

The source asks learners to shift from an employee or hobbyist identity toward an operator identity before focusing on tactics. Its claims that career-pivoters will fail without that shift and that identity determines results are coaching propositions, not evidence that employees or hobbyists inevitably fail. Skill, resources, circumstances and practice also affect outcomes. Do not use the lesson to judge a person's worth or diagnose their motives.

Make the identity practical

An authored application is to define operator behavior as taking responsibility for a clear outcome, choosing the next useful action, keeping evidence of what happened and revising the plan when the evidence changes. Compare that with waiting for an undefined task or collecting tactics without producing a work product. The comparison describes behaviors that anyone can practice; it does not divide people into fixed categories.

For one current project, write the outcome, the decision you own, the action you can complete and the evidence you will review. If a constraint prevents the action, name it and decide what support or change is needed. A commitment to building includes honest recognition of limits.

The source attributes “you are the market you become” to Kennedy. That wording has not been verified against a primary source. Preserve it as the excerpt's attribution rather than treating it as an authenticated quotation or a rule that personal identity proves market demand.

Preserve the three missing exercise references

The excerpt instructs learners to take a ten-question Identity Audit, complete a Who Do I Need to Become worksheet and read the Defer-Without-Shame doctrine. It does not provide the ten questions, worksheet fields or doctrine text. Keep all three references in the lesson and mark their contents unavailable. Do not invent ten questions and call them the recovered audit.

A short reflective exercise can still be useful if it is labeled as authored guidance: identify one habit to practice, one decision to own and one task that needs a clear defer-or-proceed decision. This does not replace the missing source exercises or establish that a formal gate has been passed.

Connect identity to the marketing work

Within RISER's Brunson and Hormozi themes, this lesson supports the habits needed to understand a customer, develop an offer and test a claim. Confidence in an identity is not customer evidence. Use the operator commitment to carry out the research and delivery work that makes the message credible.

Completion check and source

Submit the outcome, owned decision, next action and review evidence for one project. List the three missing source resources so they remain visible in the curriculum audit. D0352: Identity Before Skill. The full excerpt belongs in the appendix; this lesson teaches its available proposition without claiming the missing exercises are complete.

Assigned source links

D0352 original source 1

Complete returned native document text

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

M1.3 — IDENTITY BEFORE SKILL
============================================================

Source: Riser Nation Academy 2026 Syllabus

NOTE: This document is an excerpt copied from the master syllabus.
The master syllabus remains intact and unmodified.

---

PARENT COURSE: C1 — Harbor Orientation & The Riser Manifesto
---
Stage: Pre-Stage  ·  Phase: Learn  ·  Prereq: None — entry course  ·  Time: 6–8 hours over 1 week

Stage: Pre-Stage  ·  Phase: Learn  ·  Prereq: None — entry course  ·  Time: 6–8 hours over 1 week
In Plain Words
This is the first course. You will not learn marketing tricks here. You will figure out who you have to become to make the rest of the Academy work. Riser Nation's idea is simple: who you are determines what you can do. We fix who you are first.
The Mismatch This Course Fixes
Most students arrive looking for tactics. They will fail unless they first take on the operator identity.
Modules

---

M1.3 — IDENTITY BEFORE SKILL
---

Why career-pivoters fail. The shift from employee or hobbyist to operator. Kennedy: 'you are the market you become.'
In plain words: If you act like an employee, you'll get employee results. The shift comes first; the skills follow.
Take the 10-question Identity Audit.
Complete the 'Who do I need to become?' worksheet.
Read the Defer-Without-Shame doctrine.

---
END OF M1.3
---
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1s9B9hloD5JAdIcG-WqJqeJ7lO7M_oCeod1rQYD8o094/edit?usp=drivesdk"
drive_file_id: "1s9B9hloD5JAdIcG-WqJqeJ7lO7M_oCeod1rQYD8o094"
created: "2026-05-11T23:27:58.127Z"
modified: "2026-06-04T17:48:57.156Z"
---

# M1.3 - IDENTITY BEFORE SKILL

M1.3 — IDENTITY BEFORE SKILL
============================================================


Source: Riser Nation Academy 2026 Syllabus


NOTE: This document is an excerpt copied from the master syllabus.
The master syllabus remains intact and unmodified.


---


PARENT COURSE: C1 — Harbor Orientation & The Riser Manifesto
---
Stage: Pre-Stage  ·  Phase: Learn  ·  Prereq: None — entry course  ·  Time: 6–8 hours over 1 week


Stage: Pre-Stage  ·  Phase: Learn  ·  Prereq: None — entry course  ·  Time: 6–8 hours over 1 week
In Plain Words
This is the first course. You will not learn marketing tricks here. You will figure out who you have to become to make the rest of the Academy work. Riser Nation's idea is simple: who you are determines what you can do. We fix who you are first.
The Mismatch This Course Fixes
Most students arrive looking for tactics. They will fail unless they first take on the operator identity.
Modules


---


M1.3 — IDENTITY BEFORE SKILL
---


Why career-pivoters fail. The shift from employee or hobbyist to operator. Kennedy: 'you are the market you become.'
In plain words: If you act like an employee, you'll get employee results. The shift comes first; the skills follow.
Take the 10-question Identity Audit.
Complete the 'Who do I need to become?' worksheet.
Read the Defer-Without-Shame doctrine.


---
END OF M1.3
---

Describe the customer's intended life after the offer

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome

Turn an offer's supported benefits into a relatable future-state paragraph or video script. The assigned document is a transformation-copywriting prompt with blank inputs, not an actual customer's story. Its instructions are material to learn from; they do not establish facts about your audience or authorize a fabricated testimonial.

Supply all five inputs

Identify the target audience, the specific current problem, the emotional toll, the product or service name and type, and the transformation it is intended to provide. The source's emotional examples include frustration, self-doubt, stress and wasted time. Use those only if supported by what your audience actually reports. Separate the product's features from the change the buyer wants, and distinguish a desired outcome from an established result.

Develop the five dimensions of the after-state

First describe how daily life could feel: the source suggests relief, confidence, joy and clarity. Second describe what the person can have or do more easily, using examples such as client work, income-related tasks, time or peace of mind only where the offer supports them. Third explore how others may see or treat them, such as trust or respect, without promising other people's reactions. Fourth identify new possibilities, including growth, freedom or impact, while keeping the pathway concrete. Fifth explain why the change matters deeply to this buyer in their own terms.

These dimensions move from an operational change to its possible personal meaning. They are prompts for relevance, not five guaranteed benefits. For each sentence, ask what product capability or evidence supports it and what conditions the buyer would need to meet.

Handle the time horizon and closing line

The source proposes imagining life one or three months after completing the experience. Choose a time horizon only when appropriate to the actual delivery and evidence. Label a hypothetical illustration clearly rather than presenting a one-month or three-month outcome as a promise. Keep the voice personal, relatable and vision-oriented while grounded in real benefits.

The original closing line suggests that this future waits on the other side if the buyer says yes. Teach the invitation without implying that purchase alone causes the result. An authored alternative is: “If this outcome fits your goals, review what the program includes and what participation requires.” Match the invitation to an actual next step and explain meaningful conditions.

Use the optional customization prompt

The document ends by requesting four shorthand inputs: niche, product name, problem solved and dream outcome, with an optional video-script version. Those are a shorter entry point to the five-input brief, not additional customer evidence. The emotional context still needs to be supplied or left unknown. A video version can retain the same five dimensions and supported facts while using spoken transitions. No customized paragraph, verified niche research or finished video is contained in the source.

Connect to direct-response education

This exercise develops the dream-outcome side of Hormozi's framework. Pair the vision with evidence of likelihood, realistic timing and the effort required. A Brunson-style story and offer sequence can make that connection understandable, but an emotional future scene does not prove the offer works. Deliver the filled brief, five-dimension outline, draft paragraph or script, and a list of claims still requiring evidence.

Sources and resources

- Complete assigned transformation prompt. - Acquisition.com value-equation checklist. - ClickFunnels value-ladder reference. - FTC advertising basics. - RISER NATION CORP.

Assigned source links

D0402 original source 1

Complete returned native document text

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


🌅 “New Life After Problem Solved” Transformation Prompt
You are a transformation copywriter and storytelling expert. I want you to write a vivid, emotional description of what my ideal customer’s life will look and feel like once their biggest problem is solved — thanks to my product.

Here’s what you need to know:

- **Target audience**: [Insert brief description of your audience]
- **The specific problem they’re currently struggling with**: [Insert the core problem your product solves]
- **The emotional toll of that problem**: [Insert how it affects them — frustration, self-doubt, stress, wasted time, etc.]
- **My product/offer**: [Insert name and type of your product or service]
- **The transformation it provides**: [What outcome/result they now get]

Now, please write a vivid, emotionally-driven description of what life looks like AFTER the transformation. Include:

1. **How their daily life feels now** (relief, confidence, joy, clarity, etc.)
2. **What they now have or do easily** (clients, income, time, peace of mind, etc.)
3. **How others see them or treat them** (respect, admiration, trust, etc.)
4. **What new possibilities are open to them** (growth, freedom, impact, etc.)
5. **Why this change matters deeply to them**

Make it personal, relatable, and vision-driven. Write it like you're describing their life *1 month or 3 months* after completing the product or experience.

End with an empowering line like:
> “This is what’s waiting for you on the other side… if you say yes.”

Keep it emotionally compelling, but grounded in the real-world benefits of the product.


🧠 Want Me to Fill It Out?
Just give me:
Your niche

Your product name

The problem it solves

The dream outcome the customer wants

…and I’ll write the “New Life” vision paragraph for you immediately. Want it in video script format too? Just say the word!
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1lKHm6MlBGroRQMhzLDy_sUj9X4ohwitz_s8aJ2R1EXU/edit?usp=drivesdk"
drive_file_id: "1lKHm6MlBGroRQMhzLDy_sUj9X4ohwitz_s8aJ2R1EXU"
created: "2025-03-28T21:31:40.051Z"
modified: "2026-06-04T16:31:26.564Z"
---

# 6.) LIFE AFTER ACCEPTING MY OFFER

________________


🌅 “New Life After Problem Solved” Transformation Prompt
You are a transformation copywriter and storytelling expert. I want you to write a vivid, emotional description of what my ideal customer’s life will look and feel like once their biggest problem is solved — thanks to my product.


Here’s what you need to know:


- **Target audience**: [Insert brief description of your audience]
- **The specific problem they’re currently struggling with**: [Insert the core problem your product solves]
- **The emotional toll of that problem**: [Insert how it affects them — frustration, self-doubt, stress, wasted time, etc.]
- **My product/offer**: [Insert name and type of your product or service]
- **The transformation it provides**: [What outcome/result they now get]


Now, please write a vivid, emotionally-driven description of what life looks like AFTER the transformation. Include:


1. **How their daily life feels now** (relief, confidence, joy, clarity, etc.)
2. **What they now have or do easily** (clients, income, time, peace of mind, etc.)
3. **How others see them or treat them** (respect, admiration, trust, etc.)
4. **What new possibilities are open to them** (growth, freedom, impact, etc.)
5. **Why this change matters deeply to them**


Make it personal, relatable, and vision-driven. Write it like you're describing their life *1 month or 3 months* after completing the product or experience.


End with an empowering line like:
> “This is what’s waiting for you on the other side… if you say yes.”


Keep it emotionally compelling, but grounded in the real-world benefits of the product.


________________


🧠 Want Me to Fill It Out?
Just give me:
* Your niche

* Your product name

* The problem it solves

* The dream outcome the customer wants

…and I’ll write the “New Life” vision paragraph for you immediately. Want it in video script format too? Just say the word!

Write a truthful before-and-after transformation script

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome

Build the seven-part story in the assigned template using real experience or a clearly labeled hypothetical. The original uses first-person claims and dramatic examples; it is not evidence that the speaker or a RISER customer experienced those events. Keep the complete template in the appendix while adapting claims to supported facts.

1. Opening hook

The source opens with a question about how someone arrived at their current situation, an expression of feeling stuck and the possibility of change within months. Invite recognition with a specific problem the audience actually experiences. Use “I used to feel the same” only if true of the speaker. A question about change must not imply an established few-month result when no such evidence exists.

2. The before-state

Anchor the story in an actual time or situation: starting a career, beginning a business or another relevant period. Describe the difficulty, such as overwhelm, uncertainty, limited resources or confidence, using accurate details. The original's struggle examples include growing a business, changing habits and finding purpose; its recurring emotional examples include frustration, self-doubt and financial stress. Choose what belongs to this story rather than collecting every dramatic example. Show what was difficult and what earlier efforts failed to resolve.

3. The catalyst

Name the actual new approach, mentor or realization that changed the person's direction. Explain initial skepticism and why trying this step seemed reasonable, if those details are true. Avoid using “everything changed” to erase other contributing factors or imply that merely encountering an offer produced the outcome. A catalyst begins a process; it is not the whole mechanism.

4. The transformation process

The source explicitly says change was not overnight. Describe the challenges, actions and adjustments: applying learning, changing habits or focusing on goals are its examples. Connect observable actions to observed changes without claiming more causation than the evidence supports. Its possible improvements include more clients, confidence and visible results. Identify the actual measure or experience used in your story, along with time and effort, instead of treating every example as achieved.

5. The after-state

Explain the real current condition. The template suggests business success, purpose and fulfillment; these require accurate context and may not all apply. A person's story does not prove that everyone can transform regardless of starting conditions. Replace the universal living-proof implication with what this individual experienced and what remains uncertain. Do not claim all previous struggles disappeared if they did not.

6. Relate the story to the audience

Acknowledge the audience's situation without claiming you know every person's experience. The source suggests commitment, suitable guidance and self-belief as possible lessons. Explain which lesson your account actually supports. Replace “If I can do it, so can you” with an invitation to examine whether the approach fits the buyer's needs and circumstances. Similarity can make a story relatable; it is not a guarantee of equivalent outcomes.

7. Give one clear next step

The template ends with beginning a transformation, taking control or addressing what holds the person back. Convert that aspiration into one concrete, appropriate action, such as reviewing the curriculum and participation requirements. Do not invent a missing enrollment link, deadline or offer. The source's claim that change need not take years is not substantiated timing evidence. Explain what the next step does without promising the buyer's entire future.

Review the complete arc

Check that hook, before, catalyst, process, after, audience connection and action form one coherent sequence. The source aims to make contrast inspiring and provide a pathway; the finished version should also make effort, conditions and evidence understandable. An authored quality check is to mark each sentence as documented fact, personal interpretation, illustrative example or unresolved claim before finalizing it.

This is compatible with a Brunson-style story-to-offer presentation and with Hormozi's emphasis on the desired outcome, believable achievement, time and effort. Do not label the template an exact proprietary framework or invent an endorsement. Deliver a seven-section script plus the evidence needed for its factual claims. The assigned file includes no completed verified testimonial or supporting outcome records.

Sources and resources

- Complete assigned before-and-after script. - Acquisition.com value-equation checklist. - ClickFunnels value-ladder reference. - FTC advertising basics. - RISER NATION CORP.

Assigned source links

D0403 original source 1

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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.

Apply the value equation to a documented offer mechanism

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and preparation

Produce an evidence-cited diagnosis of the four value variables and identify which later offer work addresses each weakness. The source calls this the M4.2 deliverable for a Primary mechanism, meaning the offer mechanism chosen in its preceding work. Those legacy labels remain source context; this document is assigned to current lesson 03.1.

The worksheet requests 800–1,200 words and estimates ninety minutes. Its five section ranges actually total 850–1,350 words. Keep both instructions visible and aim within their overlapping range, 850–1,200, where feasible without dropping required evidence. This is an authored reconciliation, not an amended original. The source's version is 2.0, dated April 24, 2026.

Gather the Trigger Bank with entry IDs, Customer Interview Library with interview identifiers, Competitor Scan with names, Pricing Signals observations, and the M4.1 Distinction Memo and Component Inventory. The worksheet says not to proceed when these are missing or thin. For the learner, that means an evidence-backed submission remains incomplete until the dependencies are sufficient. It does not turn a named document into an available file, nor require unrelated curriculum work to stop. No actual evidence set or direct file links for these dependencies accompanies this source.

Understand the equation

Hormozi's four variables are dream outcome, perceived likelihood of achievement, time delay, and effort and sacrifice. The first two form the numerator and the latter two the denominator. Improve relevance and supported confidence, or reduce avoidable waiting and burdens. The equation is a planning model for perceived value, not a literal dollar-value calculator. The source's application protocol is explicitly a RISER adaptation. Its additional claim that the formula synthesizes Hopkins in 1923, Abraham in 2000, Brunson in 2015/2017 and Walker in 2014 is unverified historical attribution; do not teach that lineage as established fact.

Section 1: Dream outcome, 200–300 words

State what the buyer wants to have, be or avoid in their own words. Write one sentence or a short paragraph, then support it with at least three verbatim Trigger Bank entries carrying their IDs and at least one interview quote carrying an interview number and pseudonym or initials. Do not invent quotes to complete the blanks.

Run all three self-checks: the statement uses buyer vocabulary; a buyer could recognizably say it to a friend; and the required three-plus trigger entries and one-plus interview quote are cited. Rate it strong when the evidence consistently uses the exact outcome language, moderate when the language is close but varies, or weak when operator vocabulary dominates and support is thin. Those labels assess this worksheet's evidence, not universal market demand.

Section 2: Perceived likelihood, 150–250 words

Assess how probable this particular buyer thinks the outcome is at purchase. Make the narrative honest rather than aspirational. Complete all four driver rows. For proof, record the numbers of named and anonymous cases and their source. For mechanism specificity, select strong, moderate or vague and reference the named C2 four-pillar document if available. For operator credibility, select strong, moderate or limited and identify relevant track record. For buyer-similar identification, select yes, partial or no based on whether the proof cases match the target segment.

Cite at least two Trigger Bank objection entries with IDs and at least one named competitor observation about their proof profile and what it suggests about buyer expectations. Competitor proof is context, not your proof. Preserve whether evidence is named or anonymous and whether similarity is partial.

The source's strong rating requires ten or more named cases, buyer-similar proof and high specificity. Moderate uses three to nine named cases, some similarity and moderate specificity. Weak uses zero to two named cases, limited similarity or thin specificity. These are the supplied rubric thresholds, not universal evidence standards. A large count cannot cure unreliable or irrelevant cases, and a smaller count should not be disguised to earn a higher rating.

Section 3: Time delay, 150–250 words

Name the first concrete, valuable partial result and when it arrives in days or weeks. Separately name the full desired outcome and the expected weeks or months. Distinguish irreducible cycle time required by the mechanism from compressible time that could be shortened without degrading quality. Specify the component, the reason and the amount of feasible compression rather than saying only “faster.”

Cite at least one Pricing Signals observation about an adjacent offer's outcome and timeframe, naming the competitor and relevant comparison. In this rubric, strong means a first result in under one week and a competitive full timeframe; moderate means a first result in one to two weeks and a full timeframe near the market median; weak means a first result after two weeks or a full timeframe slower than the market norm. These are source-specific ratings, not a claim that every worthwhile offer must deliver in a week. Document when necessary cycle time limits improvement.

Section 4: Effort and sacrifice, 150–250 words

Inventory hours per week, duration and total hours. Rate the learning curve low, moderate or high and explain why. List the decisions the buyer must make, because decision load is part of effort. Then itemize extra spending on software, tools or services, opportunity costs from work the buyer stops doing, and emotional or social costs such as outreach, visibility or public work.

List reducers that are available but not deployed, such as templated outreach, shared group work and pre-built lists. Explain what each would remove without fundamentally changing the mechanism. Separately list tempting done-for-you components deliberately excluded because they would turn the program into a service. These boundaries feed the source's later M4.5 anti-promise work; do not silently add a service obligation in order to improve a score.

Cite at least one Trigger Bank quote with its ID about difficulty or effort. Rate strong when effort is bounded, sacrifice minimized and feasible reducers deployed; moderate when effort is manageable but not minimal and some reducers remain available; weak when burdens are high or unbounded and significant available reducers are unused. Account for actual effort rather than making the offer appear easy by omitting tasks.

Section 5: Synthesis, 200–300 words

Identify the strongest variable with two or three evidence-cited sentences. Identify the weakest with a two- or three-sentence diagnosis and a one- or two-sentence path to improvement. Name any structurally fixed variables and explain why changing them would change the mechanism. The diagnosis should point to an actionable constraint, not repeat four ratings without interpretation.

Retain all four module-targeting rows from the source. Dream outcome points to M4.3 decomposition variants and M4.7 landing-page framing. Perceived likelihood points to M4.6 guarantee reversal and M4.5 anti-promise filtering. Time delay points to M4.3 duration variants and M4.4 pricing calibration. Effort and sacrifice point to M4.3 engagement-model variants and M4.7 honest landing-page explanation. These are legacy cross-references, not automatic links to identically numbered lessons in the current twelve-course map.

Complete the diagnostic sentence by naming your Primary's strongest variable, weakest variable and exactly what the remaining offer modules should address. Keep the source's blanks in the appendix for reuse. A useful authored check is whether a reviewer could trace every proposed change to an evidence-backed weakness.

Submission, review and next step

Fill operator name, date and total word count. The source names a Build 8 Drive folder, the Supabase table `c4_value_equations` and `value-equation-application-reviewer-v1.0.0.yaml`. It says the AI rubric checks four things: evidence for all four variables, buyer vocabulary for the outcome, explicit strongest and weakest variables, and named later modules addressing weaknesses. It sets a seven-out-of-ten pass target and says a pass unlocks M4.3, whose three decomposition variants should address the diagnosis.

Those destinations, configuration, scoring details and unlock automation are not supplied or verified as deployed. Do not claim a pass, filing or unlock simply because this lesson was written. Preserve the planned workflow while keeping actual review pending. No complete numeric scoring rubric is present beyond the named checks and threshold.

Connect the educational themes

This worksheet gives substance to Hormozi's four-lever analysis. Use a Brunson-style offer presentation later to explain the resulting exchange, proof and next step in buyer language. Improve the actual offer before polishing its message. The complete original worksheet, including both Markdown tables, blanks and module relationships, belongs with the lesson appendix; it does not replace doing the evidence-cited analysis.

Sources and resources

- Complete assigned C4 Value Equation Worksheet. - Acquisition.com primary value-equation checklist. - ClickFunnels value-ladder reference. - Supabase: named storage platform; no specific RISER table access is established by this homepage. - RISER NATION CORP.

Assigned source links

D0404 original source 1

Original embedded resource links
D0404 original worksheet table 1
DriverYour Current StateSource
Proof (case studies, testimonials)[# of named cases; # of anonymous][source document]
Specificity of mechanism (named steps)[strong / moderate / vague][C2 4-pillar doc]
Operator credibility[strong / moderate / limited][your track record in territory]
Buyer-similar identification in proof[yes / partial / no — do your proof cases match the target buyer segment][review proof cases]
D0404 original worksheet table 2
VariableCurrent StateTargeted By
Dream Outcome[rating]M4.3 (decomposition variants), M4.7 (landing page framing)
Perceived Likelihood[rating]M4.6 (guarantee reversal), M4.5 (anti-promise filter)
Time Delay[rating]M4.3 (duration variants), M4.4 (pricing calibration)
Effort & Sacrifice[rating]M4.3 (engagement model variants), M4.7 (landing page honesty)
Complete original Markdown worksheet

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

# C4 Value Equation Worksheet

**Purpose:** M4.2 deliverable. Applies Hormozi's Value Equation across four variables to your Primary mechanism, with each variable cited against specific C3 evidence.
**Target length:** 800-1,200 words total
**Time to complete:** ~90 minutes
**Filed to:** Build 8 Drive folder, `c4_value_equations` Supabase table
**Reviewed by:** `value-equation-application-reviewer-v1.0.0.yaml` (AI rubric, ≥ 7/10 to pass)

---

## The Equation (Hormozi, $100M Offers, 2021)

```
                  Dream Outcome × Perceived Likelihood of Achievement
Value   =   ─────────────────────────────────────────────────────────
                  Time Delay × Effort & Sacrifice
```

To increase perceived value: raise the numerator, lower the denominator, or both.

---

## Before You Start

Open these documents side-by-side with this worksheet:

- C3 Trigger Bank (you will cite entries by ID)
- C3 Customer Interview Library (you will cite interviews by # and name)
- C3 Competitor Scan (you will cite competitors by name)
- C3 Pricing Signals document (you will cite price observations)
- M4.1 Distinction Memo and Component Inventory (the foundation of this worksheet)

Do not proceed if any of these are missing or thin — this worksheet depends on their density.

---

## Section 1 — Dream Outcome (200-300 words)

**Variable definition:** What the buyer ultimately wants to have, be, or avoid — stated in the buyer's own language, not the operator's.

### Your Dream Outcome Statement

> [Your Dream Outcome, in buyer vocabulary — one sentence or short paragraph]

### Evidence

Cite **at least 3 verbatim Trigger Bank entries** supporting this Dream Outcome:

- **Trigger Bank entry #___:** "[verbatim quote]"
- **Trigger Bank entry #___:** "[verbatim quote]"
- **Trigger Bank entry #___:** "[verbatim quote]"

Cite **at least 1 customer interview quote** supporting this Dream Outcome:

- **Interview #___ with [pseudonym or initials]:** "[verbatim quote]"

### Self-Check

- [ ] Dream Outcome uses buyer vocabulary, not operator vocabulary
- [ ] Buyer would recognizably say this sentence out loud to a friend
- [ ] 3+ Trigger Bank entries and 1+ interview quote cited with IDs

### Strength Rating

- [ ] Strong — Trigger Bank and interviews consistently use this exact Dream Outcome language
- [ ] Moderate — Language is close but some buyer language variations exist
- [ ] Weak — Dream Outcome is mostly in operator vocabulary with thin buyer-language backing

---

## Section 2 — Perceived Likelihood of Achievement (150-250 words)

**Variable definition:** How probable the buyer thinks it is, at moment of purchase, that your offer will produce the Dream Outcome for them specifically.

### Your Perceived Likelihood Assessment

> [Your narrative assessment — honest, not aspirational]

### Four Drivers

Assess each driver:

| Driver | Your Current State | Source |
|---|---|---|
| Proof (case studies, testimonials) | [# of named cases; # of anonymous] | [source document] |
| Specificity of mechanism (named steps) | [strong / moderate / vague] | [C2 4-pillar doc] |
| Operator credibility | [strong / moderate / limited] | [your track record in territory] |
| Buyer-similar identification in proof | [yes / partial / no — do your proof cases match the target buyer segment] | [review proof cases] |

### Evidence From C3

Cite **at least 2 Trigger Bank objection entries** — the language buyers use when expressing skepticism:

- **Trigger Bank entry #___:** "[verbatim]"
- **Trigger Bank entry #___:** "[verbatim]"

Cite **at least 1 competitor observation** — an adjacent operator's proof profile for reference:

- **Competitor [name]:** [their proof profile and what it implies for buyer expectations]

### Strength Rating

- [ ] Strong — 10+ named cases; buyer-similar proof; mechanism specificity high
- [ ] Moderate — 3-9 named cases; some buyer-similar matching; mechanism specificity moderate
- [ ] Weak — 0-2 named cases; limited buyer-similar proof OR mechanism specificity thin

---

## Section 3 — Time Delay (150-250 words)

**Variable definition:** How long the buyer must wait between payment and the Dream Outcome materializing.

### Time to First Result

How quickly does the buyer experience *something concrete and valuable* (even partial)?

> [Your time-to-first-result: days or weeks. Name the specific concrete deliverable that lands at that moment.]

### Time to Dream Outcome

How long until the full Dream Outcome materializes?

> [Your time-to-Dream-Outcome: weeks or months.]

### Irreducible vs. Compressible

What part of the time delay is **irreducible** (the mechanism itself requires the cycle time)?

> [Name the specific irreducible component, with reasoning]

What part is **compressible** (could be shortened without degrading outcomes)?

> [Name the compressible component and by how much]

### Evidence From C3

Cite **at least 1 Pricing Signals observation** — adjacent offers' time-to-outcome patterns:

- **Pricing observation:** [competitor X offers similar outcome at Y weeks]

### Strength Rating

- [ ] Strong — Time-to-first-result < 1 week; Time-to-Dream-Outcome competitive with market
- [ ] Moderate — Time-to-first-result 1-2 weeks; Time-to-Dream-Outcome at or near market median
- [ ] Weak — Time-to-first-result > 2 weeks OR Time-to-Dream-Outcome longer than market norm

---

## Section 4 — Effort & Sacrifice (150-250 words)

**Variable definition:** How much the buyer must do, give up, or endure to achieve the Dream Outcome.

### Effort

Hours required from the buyer during the offer period:

> [Hours per week, duration, total]

Learning curve difficulty:

> [Low / Moderate / High — with reasoning]

Decision fatigue (number of choices the buyer must make):

> [Inventory the decisions; high-decision offers have higher Effort]

### Sacrifice

Money beyond the offer price (software, tools, additional services):

> [Itemize]

Opportunity cost (what the buyer stops doing to engage with the offer):

> [Itemize]

Emotional/social cost (discomfort of outreach, visibility, public work):

> [Itemize]

### Effort Reducers Available But Not Yet Deployed

What could reduce Effort & Sacrifice without fundamentally changing the mechanism?

> [List of compressible effort sources — e.g., templated outreach, shared group work, pre-built lists]

### Effort Reducers Deliberately Avoided

What done-for-you components are tempting but would change the mechanism into a service rather than a program?

> [List of scope boundaries you hold — these become anti-promise material in M4.5]

### Evidence From C3

Cite **at least 1 Trigger Bank entry** — buyer language about effort or difficulty:

- **Trigger Bank entry #___:** "[verbatim]"

### Strength Rating

- [ ] Strong — Effort clearly bounded; sacrifice minimized; effort reducers deployed where possible
- [ ] Moderate — Effort is manageable but not minimal; some reducers available
- [ ] Weak — Effort is high or unbounded; significant reducers are available but not deployed

---

## Section 5 — Synthesis (200-300 words)

### Strongest Variable

Which of the four variables is strongest for your Primary? What makes it strong?

> [Variable + 2-3 sentence justification with evidence citations]

### Weakest Variable

Which variable is weakest? What would strengthen it?

> [Variable + 2-3 sentence diagnosis + 1-2 sentence strengthening path]

### Structurally Fixed

Which variables are structurally fixed by the mechanism itself (cannot be moved without changing the mechanism)?

> [Name fixed variables, with reasoning]

### C4 Module Targeting

Map each weak or moderate variable to the C4 module that will work on it:

| Variable | Current State | Targeted By |
|---|---|---|
| Dream Outcome | [rating] | M4.3 (decomposition variants), M4.7 (landing page framing) |
| Perceived Likelihood | [rating] | M4.6 (guarantee reversal), M4.5 (anti-promise filter) |
| Time Delay | [rating] | M4.3 (duration variants), M4.4 (pricing calibration) |
| Effort & Sacrifice | [rating] | M4.3 (engagement model variants), M4.7 (landing page honesty) |

### One-Sentence Diagnosis

Complete the sentence:

> "My Primary's Value Equation is strongest on _______ and weakest on _______. The remaining C4 modules must specifically ________."

---

## Signature

**Operator name:** _____________________________
**Date:** _____________________________
**Total word count:** _______ (target 800-1,200)

---

## What Happens Next

This worksheet is filed to Drive. The `value-equation-application-reviewer` AI rubric scores it on:

- All 4 variables addressed with evidence citations
- Dream Outcome in buyer vocabulary (not operator)
- Synthesis identifies strongest + weakest explicitly
- Synthesis names which later C4 module targets which weakness

Target score: ≥ 7/10.

On pass, M4.3 unlocks. Your three decomposition variants in M4.3 are designed specifically to address the weakness diagnosis from Section 5. Without that diagnosis, M4.3 drifts.

---

## Attribution

The Value Equation is Alex Hormozi's formulation from *$100M Offers* (2021). It synthesizes Hopkins (1923), Abraham (2000), Brunson (2015/2017), and Walker (2014). Application protocol here is RISER Nation's adaptation.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.2*
Complete local source copy including original filing metadata and formatting

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

# C4 Value Equation Worksheet

**Purpose:** M4.2 deliverable. Applies Hormozi's Value Equation across four variables to your Primary mechanism, with each variable cited against specific C3 evidence.
**Target length:** 800-1,200 words total
**Time to complete:** ~90 minutes
**Filed to:** Build 8 Drive folder, `c4_value_equations` Supabase table
**Reviewed by:** `value-equation-application-reviewer-v1.0.0.yaml` (AI rubric, ≥ 7/10 to pass)

---

## The Equation (Hormozi, $100M Offers, 2021)

```
                  Dream Outcome × Perceived Likelihood of Achievement
Value   =   ─────────────────────────────────────────────────────────
                  Time Delay × Effort & Sacrifice
```

To increase perceived value: raise the numerator, lower the denominator, or both.

---

## Before You Start

Open these documents side-by-side with this worksheet:

- C3 Trigger Bank (you will cite entries by ID)
- C3 Customer Interview Library (you will cite interviews by # and name)
- C3 Competitor Scan (you will cite competitors by name)
- C3 Pricing Signals document (you will cite price observations)
- M4.1 Distinction Memo and Component Inventory (the foundation of this worksheet)

Do not proceed if any of these are missing or thin — this worksheet depends on their density.

---

## Section 1 — Dream Outcome (200-300 words)

**Variable definition:** What the buyer ultimately wants to have, be, or avoid — stated in the buyer's own language, not the operator's.

### Your Dream Outcome Statement

> [Your Dream Outcome, in buyer vocabulary — one sentence or short paragraph]

### Evidence

Cite **at least 3 verbatim Trigger Bank entries** supporting this Dream Outcome:

- **Trigger Bank entry #___:** "[verbatim quote]"
- **Trigger Bank entry #___:** "[verbatim quote]"
- **Trigger Bank entry #___:** "[verbatim quote]"

Cite **at least 1 customer interview quote** supporting this Dream Outcome:

- **Interview #___ with [pseudonym or initials]:** "[verbatim quote]"

### Self-Check

- [ ] Dream Outcome uses buyer vocabulary, not operator vocabulary
- [ ] Buyer would recognizably say this sentence out loud to a friend
- [ ] 3+ Trigger Bank entries and 1+ interview quote cited with IDs

### Strength Rating

- [ ] Strong — Trigger Bank and interviews consistently use this exact Dream Outcome language
- [ ] Moderate — Language is close but some buyer language variations exist
- [ ] Weak — Dream Outcome is mostly in operator vocabulary with thin buyer-language backing

---

## Section 2 — Perceived Likelihood of Achievement (150-250 words)

**Variable definition:** How probable the buyer thinks it is, at moment of purchase, that your offer will produce the Dream Outcome for them specifically.

### Your Perceived Likelihood Assessment

> [Your narrative assessment — honest, not aspirational]

### Four Drivers

Assess each driver:

| Driver | Your Current State | Source |
|---|---|---|
| Proof (case studies, testimonials) | [# of named cases; # of anonymous] | [source document] |
| Specificity of mechanism (named steps) | [strong / moderate / vague] | [C2 4-pillar doc] |
| Operator credibility | [strong / moderate / limited] | [your track record in territory] |
| Buyer-similar identification in proof | [yes / partial / no — do your proof cases match the target buyer segment] | [review proof cases] |

### Evidence From C3

Cite **at least 2 Trigger Bank objection entries** — the language buyers use when expressing skepticism:

- **Trigger Bank entry #___:** "[verbatim]"
- **Trigger Bank entry #___:** "[verbatim]"

Cite **at least 1 competitor observation** — an adjacent operator's proof profile for reference:

- **Competitor [name]:** [their proof profile and what it implies for buyer expectations]

### Strength Rating

- [ ] Strong — 10+ named cases; buyer-similar proof; mechanism specificity high
- [ ] Moderate — 3-9 named cases; some buyer-similar matching; mechanism specificity moderate
- [ ] Weak — 0-2 named cases; limited buyer-similar proof OR mechanism specificity thin

---

## Section 3 — Time Delay (150-250 words)

**Variable definition:** How long the buyer must wait between payment and the Dream Outcome materializing.

### Time to First Result

How quickly does the buyer experience *something concrete and valuable* (even partial)?

> [Your time-to-first-result: days or weeks. Name the specific concrete deliverable that lands at that moment.]

### Time to Dream Outcome

How long until the full Dream Outcome materializes?

> [Your time-to-Dream-Outcome: weeks or months.]

### Irreducible vs. Compressible

What part of the time delay is **irreducible** (the mechanism itself requires the cycle time)?

> [Name the specific irreducible component, with reasoning]

What part is **compressible** (could be shortened without degrading outcomes)?

> [Name the compressible component and by how much]

### Evidence From C3

Cite **at least 1 Pricing Signals observation** — adjacent offers' time-to-outcome patterns:

- **Pricing observation:** [competitor X offers similar outcome at Y weeks]

### Strength Rating

- [ ] Strong — Time-to-first-result < 1 week; Time-to-Dream-Outcome competitive with market
- [ ] Moderate — Time-to-first-result 1-2 weeks; Time-to-Dream-Outcome at or near market median
- [ ] Weak — Time-to-first-result > 2 weeks OR Time-to-Dream-Outcome longer than market norm

---

## Section 4 — Effort & Sacrifice (150-250 words)

**Variable definition:** How much the buyer must do, give up, or endure to achieve the Dream Outcome.

### Effort

Hours required from the buyer during the offer period:

> [Hours per week, duration, total]

Learning curve difficulty:

> [Low / Moderate / High — with reasoning]

Decision fatigue (number of choices the buyer must make):

> [Inventory the decisions; high-decision offers have higher Effort]

### Sacrifice

Money beyond the offer price (software, tools, additional services):

> [Itemize]

Opportunity cost (what the buyer stops doing to engage with the offer):

> [Itemize]

Emotional/social cost (discomfort of outreach, visibility, public work):

> [Itemize]

### Effort Reducers Available But Not Yet Deployed

What could reduce Effort & Sacrifice without fundamentally changing the mechanism?

> [List of compressible effort sources — e.g., templated outreach, shared group work, pre-built lists]

### Effort Reducers Deliberately Avoided

What done-for-you components are tempting but would change the mechanism into a service rather than a program?

> [List of scope boundaries you hold — these become anti-promise material in M4.5]

### Evidence From C3

Cite **at least 1 Trigger Bank entry** — buyer language about effort or difficulty:

- **Trigger Bank entry #___:** "[verbatim]"

### Strength Rating

- [ ] Strong — Effort clearly bounded; sacrifice minimized; effort reducers deployed where possible
- [ ] Moderate — Effort is manageable but not minimal; some reducers available
- [ ] Weak — Effort is high or unbounded; significant reducers are available but not deployed

---

## Section 5 — Synthesis (200-300 words)

### Strongest Variable

Which of the four variables is strongest for your Primary? What makes it strong?

> [Variable + 2-3 sentence justification with evidence citations]

### Weakest Variable

Which variable is weakest? What would strengthen it?

> [Variable + 2-3 sentence diagnosis + 1-2 sentence strengthening path]

### Structurally Fixed

Which variables are structurally fixed by the mechanism itself (cannot be moved without changing the mechanism)?

> [Name fixed variables, with reasoning]

### C4 Module Targeting

Map each weak or moderate variable to the C4 module that will work on it:

| Variable | Current State | Targeted By |
|---|---|---|
| Dream Outcome | [rating] | M4.3 (decomposition variants), M4.7 (landing page framing) |
| Perceived Likelihood | [rating] | M4.6 (guarantee reversal), M4.5 (anti-promise filter) |
| Time Delay | [rating] | M4.3 (duration variants), M4.4 (pricing calibration) |
| Effort & Sacrifice | [rating] | M4.3 (engagement model variants), M4.7 (landing page honesty) |

### One-Sentence Diagnosis

Complete the sentence:

> "My Primary's Value Equation is strongest on _______ and weakest on _______. The remaining C4 modules must specifically ________."

---

## Signature

**Operator name:** _____________________________
**Date:** _____________________________
**Total word count:** _______ (target 800-1,200)

---

## What Happens Next

This worksheet is filed to Drive. The `value-equation-application-reviewer` AI rubric scores it on:

- All 4 variables addressed with evidence citations
- Dream Outcome in buyer vocabulary (not operator)
- Synthesis identifies strongest + weakest explicitly
- Synthesis names which later C4 module targets which weakness

Target score: ≥ 7/10.

On pass, M4.3 unlocks. Your three decomposition variants in M4.3 are designed specifically to address the weakness diagnosis from Section 5. Without that diagnosis, M4.3 drifts.

---

## Attribution

The Value Equation is Alex Hormozi's formulation from *$100M Offers* (2021). It synthesizes Hopkins (1923), Abraham (2000), Brunson (2015/2017), and Walker (2014). Application protocol here is RISER Nation's adaptation.

---

*Last updated: April 24, 2026 · Version 2.0 · Referenced by M4.2*

Design an offer buyers can evaluate with confidence

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome

Build a complete offer by connecting the buyer's desired transformation, delivery, evidence, effort, price and terms. This lesson teaches all twelve sections of the assigned chapter. Its cinematic marketplace is an illustration: noisy stalls sell courses, coaching, services, templates and done-for-you work while one clear booth explains why its offer fits. Clarity can help a buyer decide; it cannot make a purchase inevitable. Distrust, overwhelm, uncertainty and perceived risk are problems to investigate, not weaknesses to exploit.

What is an offer?

A product, price, feature list, promise or bonus is only part of the exchange. Explain the outcome, what the customer receives, what they must contribute, what support exists and what happens if expectations are not met. The source calls this a decision environment and describes the product as the vehicle. Translate that metaphor into information a buyer can check. A well-informed no remains a legitimate outcome.

The chapter combines names from several traditions: Hormozi's Grand Slam Offer, Joyner's Irresistible Offer, Cialdini's persuasion research, Caples's clarity, Kennedy's direct response, Ariely's behavioral work and Ogilvy's precision. Those names are the source's proposed synthesis, not verification that each author endorsed this chapter or its wording.

Improve the value proposition

The source asks you to increase value, dream outcome, likelihood, speed, ease, certainty, guarantees, support and logistics while reducing delay, effort, sacrifice, risk and emotional friction. Translate each into a delivery decision. A checklist may reduce rework; a scheduled review can clarify support; a demonstrated mechanism can help a buyer assess plausibility. Faster or easier claims need evidence. These changes do not establish that conversions will explode.

The chapter attributes three elements to Joyner: a high return perceived as ten times price, a touchstone credibility boost through a mechanism, brand or proof, and an offer understandable in five seconds. Treat these as the chapter's framing, not a verified quotation or canonical summary of Joyner. Ten times and five seconds are design prompts here, not universal purchase thresholds. Test whether people understand what they receive and whether its value is credible to them.

For the central equation, use Hormozi's documented four-part version: perceived value = dream outcome × perceived likelihood of achievement ÷ (time delay × effort and sacrifice). D0405 instead prints a denominator of time delay × effort × risk. Preserve that original in the appendix, but do not teach the added risk factor as Hormozi's formula. Risk still matters when examining confidence, terms and burdens. This is a planning framework, not a validated calculator of dollar value or conversion probability.

Define the buyer's transformation

Ask all three RISER questions: What do buyers want most? How do they describe it in their own language? What transformation or identity change do they seek? Distinguish their desired outcome from your feature vocabulary and from what you think they should need. Write: “I help [audience] achieve [outcome] without [specific burden] so they can [meaningful benefit].” Check every implied claim against delivery capability and evidence. This is the source's north-star statement, not permission to promise an unavoidable transformation.

Compare the ten guarantee types

The source lists ten names without operational terms. The following explanations are authored interpretation, not missing contract language. A results guarantee attaches a remedy to a defined outcome; a time-based guarantee specifies a deadline; a milestone guarantee uses intermediate criteria; a work-with-you-until guarantee extends support. A performance guarantee specifies a measurable standard. A double guarantee combines two commitments; reverse risk shifts a defined burden to the provider; an anti-guarantee states limits or the absence of a guarantee. A partnership guarantee connects obligations between parties, while a done-for-you guarantee concerns provider-delivered work. The labels overlap and do not establish legal terms by themselves.

For any candidate, specify eligibility, customer obligations, measurement, deadline, remedy, exclusions and fulfillment capacity before presenting it. Do not imply that an anti-guarantee removes customer rights, that extended support guarantees success, or that a refund eliminates all risk. The chapter provides no completed policy, legal review or evidence that a particular type converts better for this offer.

Use persuasion without falsifying the decision

Retain all seven source entries as offer considerations: authority, social proof, scarcity, urgency, commitment and consistency, liking, and reciprocity. Authority means relevant demonstrated competence. Social proof needs authentic context, not an implication that every buyer will replicate someone else's result. Scarcity must reflect a real constraint and urgency a real deadline. Prior commitment is an invitation to consider a next step, not an obligation to buy. Liking can come from honest communication. A useful free resource does not put its recipient in your debt.

The source labels this Cialdini's stack. His current seven-principle list includes unity, while urgency is not a separate named principle in that list. Keep urgency as the source's additional marketing consideration and explain unity as shared identity without inventing an affiliation. None of these principles guarantees a yes.

Build all seven offer layers

Identify the core product or vehicle first. Add enhancers such as training, coaching, support and templates only where they help the outcome. Accelerators include appropriate shortcuts, done-for-you tools and plug-and-play components. Safety nets include clear terms, support, checklists and quality assurance. Automators may include Make.com, GPTs, workflows and repeatable systems, with review and actual operating costs considered. Community provides an opportunity for accountability, belonging and momentum; it is not evidence that these benefits will occur. The legacy layer describes the buyer's hoped-for identity change without claiming a guaranteed personal transformation.

The separate accelerator menu contains eight items: templates, scripts, automations, SOPs, cheat sheets, AI tools, swipe files and walkthrough videos. For each proposed addition, name the obstacle it addresses, how the buyer uses it and who maintains it. More files can increase effort instead of reducing it. Done-for-you components also change scope and delivery obligations.

Explain price and value honestly

The chapter asks how to deliver ten times the asking price in value. Examine savings, earnings, status gains, time returns, stress reduction and expanded opportunities separately. These can be benefits buyers care about, but uncertain earnings, status and emotional outcomes should not be booked as established dollar savings.

Its illustrative stack is a $997 course, $2,000 in templates, $1,000 in coaching, $500 in bonuses and $2,500 in support. The arithmetic totals $6,997, not literally $7,000-plus as printed. Its offered price is $497. Preserve both the original and correction. Neither the component valuations nor that selling price is verified market evidence for RISER. Anchoring and contrast explain the presentation; they do not justify invented reference prices. Use defensible comparisons and clear valuation assumptions.

Execute the ten-step build

First define the dream outcome; second define the transformation; third identify the biggest pains; fourth identify the biggest risks. Fifth choose enhancers such as tools, templates and systems; sixth choose appropriate accelerators and done-for-you elements; seventh design feasible safety nets; eighth add truthful proof and any genuine timing constraints. Ninth calculate the stack without double-counting. Tenth test a price against buyer value, costs and delivery capacity. The source's ten-times rule is a hypothesis to examine, not an instruction to manufacture values until a preferred price appears justified.

Complete all ten worksheet responses: desired outcome; intended transformation; pains addressed; specific risks reduced; enhancers; accelerators; possible guarantees; evidence supporting claims; itemized total value; and final proposed price. Where the source says “unavoidable transformation,” document an intended, conditional outcome instead. Attach evidence and unresolved assumptions to each response.

Apply the direct-response connection

Use the Brunson-style presentation sequence to make the exchange understandable: connect a truthful story and buyer problem to a concrete offer and an appropriate next step. Use Hormozi's four levers to improve what is delivered before presenting a stack. This is an authored application of those educational themes, not a quotation or a prediction of results. The assigned document contains no actual customer research, finished guarantee, validated prices or operating automation; do not count those assets as supplied.

Sources and resources

- Complete assigned chapter. - Acquisition.com value-equation checklist: primary formula reference. - Cialdini's seven principles: primary attribution check. - ClickFunnels on the value ladder: supporting funnel reference, not validation of this chapter's claims. - Make and ChatGPT: named automation and GPT-related resources; no system is configured by reading this lesson. - RISER NATION CORP.

- FTC advertising basics: supporting guidance on truthful, evidence-based claims.

Assigned source links

D0405 original source 1

Complete returned native document text

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?
→ ____________________________________
Complete local source copy including original filing metadata and formatting

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?
→ ____________________________________
________________

Build useful bonuses and a defensible value stack

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome

Create a core-and-bonus table, five offer angles and a free entry resource that connect to the paid outcome. The assigned source is labeled Module 8, with a later Module 9 platform handoff. Those legacy labels do not change this document's current spreadsheet lesson assignments.

Begin with the outcome and four levers

An offer's appeal depends on more than its files. The source uses Hormozi, Brunson, Kennedy and a RISER construction metaphor to emphasize outcomes, presentation, offer strength and useful additions. Its attributed slogans are not verified verbatim quotations. Do not teach that an offer or funnel becomes impossible to fail.

Use Hormozi's value equation: dream outcome multiplied by perceived likelihood of achievement, divided by time delay multiplied by effort and sacrifice. A bonus can shorten a step, simplify work or provide evidence and support that help someone judge the likelihood of success. Reduced risk is a design consideration here, not a fifth variable inserted into that formula. The source's ten-times-more-valuable objective is a design aspiration, not a guaranteed valuation.

Build the stack with names, descriptions and supported values

List the core and each bonus separately, with a useful name, an explanation of what the buyer receives and a defensible price or valuation basis. The chapter's example is a 90-Day Niche Mastery System at $997, an Avatar Clarity Worksheet at $97, Plug & Play Funnel Templates at $497 and a Private Riser Nation Mastermind at $997. These add to $2,588, compared with an example selling price of $997. These numbers are illustrative, not verified RISER current prices or evidence of realized customer value.

Explain how each component helps the promised outcome. Avoid double-counting something already included in the core or representing an invented list price as a normal selling price. A side-by-side comparison can show the components, burdens removed and limitations. This applies the source's Brunson presentation theme without making sheer bonus quantity the measure of quality.

Place the MIFGE before the paid offer

The source expands MIFGE as Most Incredible Free Gift Ever. Its role is to preview the transformation and make a relevant paid next step understandable. Its example is a free Funnel Cheat Sheet leading to a paid Funnel Playbook plus Templates. The free resource should solve a bounded problem on its own and explain what additional help the paid product provides. A recipient remains free to stop there; the gift creates no purchase obligation. No finished gift is attached to this source.

Develop all five angles

For scarcity, describe actual seat capacity or a genuine bonus expiration. For authority, use supported credentials, accurate featured-in references or authentic social proof. For speed, name a measured deliverable and realistic timing; the source's “results in seven days” is example copy, not evidence. For safety, explain actual conditions and remedies; the examples of a 30-day guarantee or paying only after profit require defined, feasible terms. For community, state what access and participation actually include rather than promising belonging or outcomes.

These angles should answer different buyer questions about one consistent offer. Do not use a different angle to conceal a material limitation or turn a hypothetical guarantee into a current policy.

Run the bonus creation SOP

Brainstorm five possible bonuses. Check each against time, effort and risk: which obstacle does it address, and is it usable by this buyer? Assign a market value only when a reasonable basis exists; otherwise describe usefulness without an unsupported dollar claim. Arrange the retained components on the offer page in a sequence that shows how they support delivery.

The source's pro tips ask whether a bonus could be worth buying on its own, recommend showing value with comparisons, and suggest shifting a defined risk toward the provider. Treat these as source-attributed advice, not authenticated quotations or a demand to assume unlimited risk. RISER's house metaphor describes the core as foundation and bonuses as custom finishes. A finish cannot repair a broken foundation: fix the core delivery before adding extras.

Complete the four deliverables and checkpoint

Prepare the Value Stack Table with core, bonuses and total. Write the scarcity, authority, speed, safety and community angles. Finalize a proposed MIFGE entry point. Add the work to the Offer Blueprint Worksheet. The source names that worksheet but does not provide its actual file or a completed blueprint; record that dependency rather than claiming submission.

Before the legacy Module 9 handoff, check that three to five retained bonuses reduce a real burden, that totals are arithmetically correct and supported, and that the angles communicate an understandable exchange. Replace the subjective “stupid good deal” test with buyer feedback on usefulness and clarity. The next source topic is platform and delivery systems, naming ClickFunnels, Circle, Kajabi and WordPress. This lesson does not select a platform, create an account or configure delivery.

Sources and resources

- Complete assigned bonuses and value-stack source. - Acquisition.com value-equation checklist. - ClickFunnels value-ladder explanation. - Named platform resources: ClickFunnels, Circle, Kajabi and WordPress. - RISER NATION CORP.

- FTC advertising basics: supporting guidance on truthful, evidence-based claims.

Assigned source links

D0406 original source 1

Complete returned native document text

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

Module 8 – Bonuses, Value Stacks & Irresistible Angles
(Turn a Good Offer Into a No-Brainer with Strategic Stacking)
Objective
By the end of this module, you’ll know how to engineer bonuses, stack value, and frame angles so your offer feels 10x more valuable than its price tag.

Why This Matters
Alex Hormozi: People don’t buy products—they buy outcomes multiplied by value and divided by risk.

Russell Brunson: “Stack the cool.” Every bonus must increase excitement and push the offer into no-brainer territory.

Dan Kennedy: “Your offer is the strongest sales copy you’ll ever write.” Get the offer right, and the rest is easy.

Riser Nation: Bonuses aren’t fluff—they’re the extra steel beams that make your funnel impossible to collapse.


Step 1 – Hormozi’s Value Equation
Value = (Dream Outcome × Perceived Likelihood of Achievement) ÷ (Time Delay × Effort & Sacrifice).
Add bonuses that speed results (reduce time).

Add bonuses that simplify the process (reduce effort).

Add bonuses that guarantee or reassure (reduce risk).


Step 2 – Building the Value Stack (Brunson’s Model)
Every bonus is listed with a name, description, and price tag.
 Example:
Core Program: 90-Day Niche Mastery System – Value: $997

Bonus #1: Avatar Clarity Worksheet – Value: $97

Bonus #2: Plug & Play Funnel Templates – Value: $497

Bonus #3: Private Riser Nation Mastermind – Value: $997
 Total Value = $2,588 → Today’s Price = $997


Step 3 – The MIFGE Placement
Your Most Incredible Free Gift Ever is the doorway to the stack.
It should preview the transformation.

It tees up your paid offer as the logical next step.

Example: Free “Funnel Cheat Sheet” → paid Funnel Playbook + Templates.


Step 4 – Crafting Irresistible Angles
Scarcity Angle: Limited seats, expiring bonuses.

Authority Angle: “As featured in…” or social proof.

Speed Angle: “Get results in 7 days…”

Safety Angle: 30-day guarantee, “don’t pay until you profit.”

Community Angle: Access to others on the same journey.


Step 5 – Bonus Creation SOP
Brainstorm 5 possible bonuses.

Check: Does it reduce time, effort, or risk?

Assign each a “market value.”

Stack them into your offer page.


Deliverables for Module 8
✅ Draft your Value Stack Table (Core + Bonuses + Total Value).
 ✅ Write out your Irresistible Angles (Scarcity, Authority, Speed, Safety, Community).
 ✅ Finalize your MIFGE as the entry point.
 ✅ Add to your Offer Blueprint Worksheet.

Pro Tips & Expert Secrets
Hormozi: If your bonuses aren’t worth paying for by themselves, don’t use them.

Brunson: Don’t just tell—show the value. Use side-by-side comparisons.

Kennedy: “Risk reversal” is the ultimate bonus—make the risk yours, not theirs.

Riser Nation: Think of your offer like building a house: the core offer is the foundation, but the bonuses are the custom finishes that make people fall in love.


Checkpoint Before Module 9
Do you have at least 3–5 bonuses that reduce time/effort/risk?

Have you calculated the total stack value?

Do your angles make your offer feel like a “stupid good deal”?

If yes → you’re ready for Module 9: Platform & Delivery Systems — where we decide exactly where and how your offers live (ClickFunnels, Circle, Kajabi, WordPress, etc.).
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1g30DnBYBBqO1MCYQeXl6cS8lFaFdgiGO8bCHfSSelu4/edit?usp=drivesdk"
drive_file_id: "1g30DnBYBBqO1MCYQeXl6cS8lFaFdgiGO8bCHfSSelu4"
created: "2025-10-08T01:04:52.589Z"
modified: "2026-06-04T14:43:20.180Z"
---

# CNX.3.11.8 – Offer_Dev_Module_8_Bonuses_Value_Stacks_And_Irresistible_Angles.docx

Module 8 – Bonuses, Value Stacks & Irresistible Angles
(Turn a Good Offer Into a No-Brainer with Strategic Stacking)
Objective
By the end of this module, you’ll know how to engineer bonuses, stack value, and frame angles so your offer feels 10x more valuable than its price tag.
________________


Why This Matters
* Alex Hormozi: People don’t buy products—they buy outcomes multiplied by value and divided by risk.

* Russell Brunson: “Stack the cool.” Every bonus must increase excitement and push the offer into no-brainer territory.

* Dan Kennedy: “Your offer is the strongest sales copy you’ll ever write.” Get the offer right, and the rest is easy.

* Riser Nation: Bonuses aren’t fluff—they’re the extra steel beams that make your funnel impossible to collapse.

________________


Step 1 – Hormozi’s Value Equation
Value = (Dream Outcome × Perceived Likelihood of Achievement) ÷ (Time Delay × Effort & Sacrifice).
   * Add bonuses that speed results (reduce time).

   * Add bonuses that simplify the process (reduce effort).

   * Add bonuses that guarantee or reassure (reduce risk).

________________


Step 2 – Building the Value Stack (Brunson’s Model)
Every bonus is listed with a name, description, and price tag.
 Example:
      * Core Program: 90-Day Niche Mastery System – Value: $997

      * Bonus #1: Avatar Clarity Worksheet – Value: $97

      * Bonus #2: Plug & Play Funnel Templates – Value: $497

      * Bonus #3: Private Riser Nation Mastermind – Value: $997
Total Value = $2,588 → Today’s Price = $997

________________


Step 3 – The MIFGE Placement
Your Most Incredible Free Gift Ever is the doorway to the stack.
         * It should preview the transformation.

         * It tees up your paid offer as the logical next step.

         * Example: Free “Funnel Cheat Sheet” → paid Funnel Playbook + Templates.

________________


Step 4 – Crafting Irresistible Angles
            * Scarcity Angle: Limited seats, expiring bonuses.

            * Authority Angle: “As featured in…” or social proof.

            * Speed Angle: “Get results in 7 days…”

            * Safety Angle: 30-day guarantee, “don’t pay until you profit.”

            * Community Angle: Access to others on the same journey.

________________


Step 5 – Bonus Creation SOP
               * Brainstorm 5 possible bonuses.

               * Check: Does it reduce time, effort, or risk?

               * Assign each a “market value.”

               * Stack them into your offer page.

________________


Deliverables for Module 8
✅ Draft your Value Stack Table (Core + Bonuses + Total Value).
✅ Write out your Irresistible Angles (Scarcity, Authority, Speed, Safety, Community).
✅ Finalize your MIFGE as the entry point.
✅ Add to your Offer Blueprint Worksheet.
________________


Pro Tips & Expert Secrets
                  * Hormozi: If your bonuses aren’t worth paying for by themselves, don’t use them.

                  * Brunson: Don’t just tell—show the value. Use side-by-side comparisons.

                  * Kennedy: “Risk reversal” is the ultimate bonus—make the risk yours, not theirs.

                  * Riser Nation: Think of your offer like building a house: the core offer is the foundation, but the bonuses are the custom finishes that make people fall in love.

________________


Checkpoint Before Module 9
                     * Do you have at least 3–5 bonuses that reduce time/effort/risk?

                     * Have you calculated the total stack value?

                     * Do your angles make your offer feel like a “stupid good deal”?

If yes → you’re ready for Module 9: Platform & Delivery Systems — where we decide exactly where and how your offers live (ClickFunnels, Circle, Kajabi, WordPress, etc.).
________________

Diagnose an offer with the four value levers

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source context

Explain each value lever, score your current offer and select one evidence-backed improvement. This short master-syllabus excerpt belongs to legacy C6, The Grand Slam Offer, and is labeled Stage 2 Sailboat, Build to Do, with C5 Graduation as prerequisite and twelve to sixteen hours over two weeks. The duplicated schedule describes its parent course context, not two separate assignments or a verified duration for this individual lesson. The current spreadsheet assignment remains lesson 03.1.

What are the four levers?

An offer states what the buyer receives in exchange for money, effort and other commitments. The excerpt contrasts competing mainly on price with explaining relevant value. Hormozi's equation combines dream outcome and perceived likelihood of achievement above the division line, with time delay and effort and sacrifice below it. Treat this as a diagnostic framework rather than a literal revenue formula.

Dream outcome is the result the buyer actually wants. Define it using observed buyer language and bounded delivery scope. Perceived likelihood concerns why this particular buyer believes the result is plausible; improve that assessment with relevant proof and an understandable mechanism. Time delay is the wait for a useful first result and the larger outcome; distinguish necessary work from avoidable waiting. Effort and sacrifice include the buyer's labor, learning, decisions, extra spending and things given up. Reduce unnecessary burdens without concealing the work that remains.

The source says to make the dream bigger and make buyers believe. In practice, improve relevance and evidence rather than inflating claims. A larger unsupported promise can undermine confidence. Bonuses, a feasible guarantee, a clear name and a downsell are mentioned as later offer work, but this excerpt does not include their full procedures or completed assets. A downsell is a smaller or differently scoped alternative; it still needs its own clear terms.

Score consistently and choose the next improvement

The source requests one-to-ten scores but supplies no scoring anchors or direction for the denominator. For this authored exercise, use ten to mean stronger buyer value on every row: more relevant outcome, better-supported likelihood, less avoidable delay and less unnecessary effort. Record evidence and uncertainty beside each score. This convention prevents confusing a high raw time burden with a good time score; it is not a recovered original rubric or a formal graduation threshold.

Identify the improvement with the greatest plausible benefit given the current constraint, cost and feasibility. A low score is a diagnostic clue, not automatic proof of priority. For example, if unclear onboarding delays an otherwise useful deliverable, test a clearer onboarding sequence and measure time to first useful output. Do not simply multiply subjective scores and claim the product predicts value or sales.

Apply the marketing connection

Use Hormozi's levers to improve the exchange and a Brunson-style offer presentation to explain that exchange, its proof and the next step. Submit a four-row diagnosis with evidence, one chosen change and a measurement plan. No actual scores, customer evidence, graduation record or missing syllabus procedures are supplied in this excerpt.

Sources and resources

- Complete assigned M6.1 excerpt. - Acquisition.com primary value-equation checklist. - ClickFunnels on the value ladder. - RISER NATION CORP.

Assigned source links

D0407 original source 1

Complete returned native document text

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

M6.1 — THE VALUE EQUATION
============================================================

Source: Riser Nation Academy 2026 Syllabus

NOTE: This document is an excerpt copied from the master syllabus.
The master syllabus remains intact and unmodified.

---

PARENT COURSE: C6 — The Grand Slam Offer (Hormozi)
---
Stage: Stage 2 — Sailboat  ·  Phase: Build → Do  ·  Prereq: C5 Graduation passed  ·  Time: 12–16 hours over 2 weeks

Stage: Stage 2 — Sailboat  ·  Phase: Build → Do  ·  Prereq: C5 Graduation passed  ·  Time: 12–16 hours over 2 weeks
In Plain Words
An offer is what you give for what they give you. A Grand Slam Offer is so good people feel stupid saying no. We use Hormozi's Value Equation: more dream, more belief, less time, less work. Then we stack bonuses, add a guarantee, name it well, and prepare the downsell.
The Mismatch This Course Fixes
Mismatch between commodity offers (sell on price) and Grand Slam offers (sell on value perception).
Modules

---

M6.1 — THE VALUE EQUATION
---

(Dream Outcome × Perceived Likelihood) ÷ (Time Delay × Effort & Sacrifice).
In plain words: Make the dream bigger. Make them believe. Cut time. Cut effort. That's the whole game.
The 4 levers explained.
Score your offer 1–10 per lever.
Identify the highest-leverage improvement.

---
END OF M6.1
---
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1-4t2YKKF7Ms4R_LlpAyWgW21vtMdgUGpkjTAzrQw09A/edit?usp=drivesdk"
drive_file_id: "1-4t2YKKF7Ms4R_LlpAyWgW21vtMdgUGpkjTAzrQw09A"
created: "2026-05-11T23:30:27.171Z"
modified: "2026-06-04T17:47:12.217Z"
---

# M6.1 - THE VALUE EQUATION

M6.1 — THE VALUE EQUATION
============================================================


Source: Riser Nation Academy 2026 Syllabus


NOTE: This document is an excerpt copied from the master syllabus.
The master syllabus remains intact and unmodified.


---


PARENT COURSE: C6 — The Grand Slam Offer (Hormozi)
---
Stage: Stage 2 — Sailboat  ·  Phase: Build → Do  ·  Prereq: C5 Graduation passed  ·  Time: 12–16 hours over 2 weeks


Stage: Stage 2 — Sailboat  ·  Phase: Build → Do  ·  Prereq: C5 Graduation passed  ·  Time: 12–16 hours over 2 weeks
In Plain Words
An offer is what you give for what they give you. A Grand Slam Offer is so good people feel stupid saying no. We use Hormozi's Value Equation: more dream, more belief, less time, less work. Then we stack bonuses, add a guarantee, name it well, and prepare the downsell.
The Mismatch This Course Fixes
Mismatch between commodity offers (sell on price) and Grand Slam offers (sell on value perception).
Modules


---


M6.1 — THE VALUE EQUATION
---


(Dream Outcome × Perceived Likelihood) ÷ (Time Delay × Effort & Sacrifice).
In plain words: Make the dream bigger. Make them believe. Cut time. Cut effort. That's the whole game.
The 4 levers explained.
Score your offer 1–10 per lever.
Identify the highest-leverage improvement.


---
END OF M6.1
---

Source gap: offer master document

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

The current native document contains only the title `offer_master_document` and “TODO: Populate via Irresistible Offer Engine outputs.” No completed offer, engine output, framework, supporting evidence or resource list is present. The local source copy agrees with that missing-body status.

Keep this assignment visible in lesson 03.1 and retain the complete returned text in the appendix. This is a source-gap notice, not a completed teaching adaptation. Related offer lessons do not fill this document's missing material by implication. Its instruction to populate an output is source content, not evidence that an engine has run or authorization to invent its results.

Completion requires the actual populated source and a new distinct-material review, followed by lesson integration and verification. Open the assigned offer master document.

Assigned source links

D0408 original source 1

Complete returned native document text

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


# offer_master_document

TODO: Populate via Irresistible Offer Engine outputs.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1xTVA8lyxFkpwQ-3hEoqF7De50tkv5K9gzWjMh6UIAic/edit?usp=drivesdk"
drive_file_id: "1xTVA8lyxFkpwQ-3hEoqF7De50tkv5K9gzWjMh6UIAic"
created: "2026-02-20T15:56:07.221Z"
modified: "2026-06-04T02:10:05.281Z"
---

# offer_master_document.md

# offer_master_document


TODO: Populate via Irresistible Offer Engine outputs.

Source gap: offer summary

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

The current native document contains only the title `offer_summary` and “TODO: Populate via Irresistible Offer Engine outputs.” No completed summary, offer terms, engine output or supporting evidence is present. The local source copy confirms the same missing-body status.

Preserve this separate source assignment in lesson 03.1 with its original text and link. This notice does not count as a completed teaching adaptation, and an adjacent offer script is not a substitute for the missing assigned summary. The embedded TODO does not establish that the named engine exists, has run or supplied an output.

Completion requires the populated summary, review of every distinct element, integration and saved-preview verification. Open the assigned offer summary.

Assigned source links

D0409 original source 1

Complete returned native document text

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


# offer_summary

TODO: Populate via Irresistible Offer Engine outputs.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1YwofOpWQwmyRGPi9SdnPXPwjAE0xv7nlqsk5s9SvHP4/edit?usp=drivesdk"
drive_file_id: "1YwofOpWQwmyRGPi9SdnPXPwjAE0xv7nlqsk5s9SvHP4"
created: "2026-02-20T15:56:11.624Z"
modified: "2026-06-04T02:10:06.124Z"
---

# offer_summary.md

# offer_summary


TODO: Populate via Irresistible Offer Engine outputs.

Source gap: one-sentence offer

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

The current native source contains only the title `one_sentence_offer` and a TODO to populate it from Irresistible Offer Engine outputs. The local copy agrees. No completed sentence, offer facts, evidence or generated output is present.

Preserve this separate assignment in lesson 03.1 with its full original text. It is a missing-body notice, not a completed adaptation. D0418 supplies an engine prompt, but reading that prompt does not establish that it has run or fill this document. Completion requires the actual populated source, distinct-material review and saved lesson integration.

- Assigned one-sentence offer source. - Related engine prompt, not a completed output.

Assigned source links

D0410 original source 1

Complete returned native document text

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


# one_sentence_offer

TODO: Populate via Irresistible Offer Engine outputs.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1KeA08JwLRJVj1vhbXoDqrNhzPy6C6hyQ8a-EGk5ITd4/edit?usp=drivesdk"
drive_file_id: "1KeA08JwLRJVj1vhbXoDqrNhzPy6C6hyQ8a-EGk5ITd4"
created: "2026-02-20T15:56:32.220Z"
modified: "2026-06-04T02:10:10.798Z"
---

# one_sentence_offer.md

# one_sentence_offer


TODO: Populate via Irresistible Offer Engine outputs.

Trace the offer curriculum through its database schema

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source boundary

Explain how each proposed C4 artifact is stored, what its checks actually enforce and where review or application controls are still needed. This is the complete version 2.0 schema dated April 24, 2026, written for the operator or developer deploying or auditing Build 1. It depends on the C1, C2 and C3 schemas and their referenced tables. This lesson reviews its SQL as source material; it does not execute migrations or claim a deployed database.

The schema separately supplies the `c4_value_equations` table named in D0404. That resolves the earlier lack of an accompanying table definition in the worksheet's own file. The separately assigned D0413 supplies its reviewer rubric. Both are now accessible references; actual submission storage, grading and unlocking remain unverified.

Understand the shared record structure

There are eight artifact tables and one review-log table. Each receives a UUID primary key with a generated default and a required user_id referencing public.users; deleting that user cascades to these rows. Artifact rows have a filed_at timestamp defaulting to now, while the log has ran_at. A default is not the same as a required value: the source does not mark every timestamp NOT NULL.

The distinction table is unique by user and memo file, allowing multiple distinct memo files per user. The other seven artifact tables are unique by user alone, so they represent one row per user unless another history mechanism exists. The review log permits multiple events. User indexes support lookup; the log uses a combined user-and-module index. File IDs point to external Drive artifacts; storing an ID does not verify the file's contents, permissions or authenticity.

M4.1: offer distinctions

`c4_offer_distinctions` requires the distinction memo's Drive file ID, component inventory file ID, a zero-to-ten AI rubric score and the Primary mechanism name. An optional foreign key points to the C3 market-fit hypothesis. Its stored generated passed value is true when the score is at least seven. The row records which mechanism and files were assessed; the schema does not itself read those files or prove the score came from an authorized reviewer.

M4.2: the value equation

`c4_value_equations` requires the worksheet file ID, strongest and weakest variable names, citation counts and score. Four optional strength columns accept Strong, Moderate or Weak for dream outcome, likelihood, time and effort. The strongest and weakest fields accept the four full variable names, but no constraint requires them to differ. Trigger-bank citation count must be at least three, interview count at least one and score zero to ten. Passed is generated from score at least seven.

These checks validate declared counts and allowed labels, not the quotations or all per-section evidence required by D0404 and D0413. The four strength fields can be null because an allowed-value CHECK does not make a column mandatory. The worksheet's richer diagnosis and the actual grading rubric remain necessary.

M4.3: decomposition and three variants

`c4_offer_decompositions` stores decomposition and variants file IDs, a total decomposed-deliverables count from six to ten, three variant definitions and a required structural-verification flag. Each A, B and C variant has a required name, engagement model, duration in weeks and deliverable count, plus optional lower and upper price bands. Engagement model is Cohort, 1:1, Self-paced or Hybrid. Each variant's deliverable count may not exceed eight.

Three pairwise checks compare A with B, A with C and B with C. Every pair must differ in engagement model, duration or deliverable count. Changing price or name alone does not satisfy them. These are the actual database tests; deeper assessment of meaningful difference belongs to the named offer-decomposition reviewer. The source's design note says the maximum-eight rule guards against feature stuffing, but a count cannot assess whether the retained deliverables are useful.

The SQL does not require positive duration or a positive minimum variant count, nor does it order or validate positive price-band endpoints. A stored structural_verification_passed flag is supplied, not computed from all qualitative criteria. Keep these limits visible rather than treating acceptance by the table as full validation.

M4.4: pricing decisions

`c4_pricing_decisions` requires a pricing-decision file, observed floor, median and ceiling, a positive anchor price, a pricing strategy and a pay-in-full price. Strategies are Median, Above Market, Below Market (Volume) or Other. Optional fields store installment and deposit descriptions, hours per buyer, effective hourly rate and rationale for deviation from the observed band. Score is zero to ten; at least seven generates passed.

The table can preserve the comparison and unit-economics assumptions, but it does not enforce floor ≤ median ≤ ceiling, positive pay-in-full price or coherent hours and effective rate. Nor does it independently validate the competitor observations. Explain the rationale and evidence in the linked artifact before treating the price as justified.

M4.5: anti-promises and integrity

`c4_anti_promises` requires anti-promise and integrity-statement file IDs, three to six audience exclusions, at least two outcome non-claims and at least two scope boundaries. The required signature Boolean defaults to false. A zero-to-ten score of at least seven and a true signature flag jointly generate passed. This records the boundary and signature assertion; a Boolean by itself is not a verified signature or an enforceable agreement.

M4.6: guarantees

`c4_guarantees` stores the guarantee and honesty-clause file IDs, a required signature flag defaulting false, guarantee type, component count, target weakness, sustainability flag and score. Types are Refund, Outcome, Hybrid, Time-shift and Effort-adjusted. There may be at most two components. The target must be Perceived Likelihood, Time Delay or Effort and Sacrifice. Expected activation percentage is optional. Passed requires score at least seven and a signed-clause flag.

The source records unit_economics_sustainable but does not include it in the generated pass condition. It also does not constrain the percentage to zero through one hundred or require a positive component minimum. Therefore, a row can satisfy the coded pass condition without establishing a sustainable guarantee. The written terms, evidence and authorized review still matter.

M4.7: landing-page copy

`c4_landing_page_copies` requires the page and provenance-log file IDs, permits a revision-log ID, limits total words to 1,000–5,000 and requires at least fifteen claimed Trigger Bank entries. It separately stores the number verified verbatim. Two optional reviewer IDs reference users, each paired with an optional completion timestamp. peer_reviews_complete is generated from the presence of both timestamps.

Passed requires an AI score of at least seven, both review timestamps and at least fifteen verified verbatim entries. The AI score is optional but, when present, constrained to zero through ten. Depending on null inputs, the Boolean expression can produce null rather than false; the completion function counts only passed = TRUE.

No shown constraint requires different reviewers, prevents self-review, ensures reviewer IDs accompany timestamps or ensures verified counts do not exceed claimed counts. The application and reviewer process must establish that the review and evidence are real. A generated Boolean protects its expression from direct assignment; it does not make owner-supplied inputs trustworthy.

M4.8: offer readiness

`c4_offer_readiness_docs` requires readiness and first-sale-checklist file IDs, selected variant A/B/C, final offer name and final anchor price. Signature defaults to false. The optional Opus validator verdict is PASS, NEEDS_REVISION or FAIL, with an optional run timestamp. At least three kill criteria must be declared. Passed requires a PASS verdict and a true signature flag.

This captures the intended final review gate. A Sonnet result elsewhere does not satisfy this explicit Opus-verdict field. However, the field does not authenticate which model or person produced its value, the anchor price is not constrained positive here, and the table stores a kill-criteria count rather than the criteria themselves. The linked artifact and trusted review process remain essential.

Review history and user summary

`c4_review_log` stores user, module M4.1 through M4.8, prompt name, version, required submission count defaulting to one, verdict PASS/FAIL/NEEDS_REVISION, optional integer score, feedback JSON, flags JSON and run time. Its score has no zero-to-ten constraint and submission count has no positive check. Preserve these differences rather than assuming the log has the same validation as every artifact.

The user table gains five columns: completion Boolean defaulting false, completion timestamp, lead variant, final offer name and final anchor price. These are summary fields populated by the shown trigger; their existence alone does not prove current eligibility or completion.

Enrollment eligibility: what is actually checked?

`check_c4_enrollment_eligible` accepts a user ID and returns JSON containing eligible and a missing-items list. It requires C3 complete, a market-fit hypothesis filed within the previous three months, a Trigger Bank with at least 200 entries, a Pricing Signals row and an oath signed within the previous twelve months. The hypothesis uses a strict newer-than boundary; the oath is rejected when missing or older than its boundary.

The function selects C1 completion, C2 completion and operator-identity filing but does not test them. It checks that Pricing Signals exists, not its quality or recency, and it does not validate every dependency named in the worksheet. These are differences between data read, conditions enforced and the broader educational prerequisites.

Completion checks and trigger behavior

`check_c4_completion` returns complete plus missing items after checking all eight artifact stages: distinction passed; equation passed; decomposition structural verification true; pricing passed; anti-promise passed; guarantee passed; landing page passed; and readiness passed. The named missing items retain the expected signature, peer-review and Opus context because those are part of the relevant table expressions.

`update_c4_complete_flag` calls that check for NEW.user_id. When complete, it reads the passing readiness row and sets the user completion flag true, stamps the current time and copies the selected variant, offer name and anchor price. Its trigger runs only after an insert or update to the readiness table when NEW.passed is true.

That means completing another artifact after readiness already passed does not automatically invoke this trigger. Neither deleting supporting evidence nor changing a prior result to failure resets completion through this code. The function only sets true and has no false branch. Repeated qualifying readiness updates can also restamp completion time. These are observations from the supplied SQL, not evidence that a live system currently behaves this way. A production design must decide how to re-evaluate changes and revocations.

Access controls and implementation limits

All nine tables enable row-level security. The eight artifact tables allow selecting, inserting and updating rows belonging to auth.uid(); no DELETE policy is shown. The review log permits owners to select their history, but its insert policy uses WITH CHECK (TRUE) without a TO role restriction. The adjacent service-only comment is not an access restriction. Actual access also depends on grants and runtime roles, which this file does not show.

Likewise, owner-based row access is not field-level grading authority. If ordinary users have the corresponding write grants, these policies do not stop them changing their own scores, verification flags or signature assertions. Review provenance and privileged fields need a defined trusted boundary before this can be treated as an authoritative completion system.

The eligibility and completion functions use SECURITY DEFINER and accept arbitrary user IDs. The shown definitions contain neither a caller-to-user authorization check nor an explicit secure search_path. Supabase's documentation explains the need to secure such functions and their execution permissions. Review those controls and actual grants before implementation; do not infer protection from schema-qualified table names alone.

Migration and operating references

The supplied migration sequence runs c1_schema.sql, c2_schema.sql, c3_schema.sql and then c4_schema.sql using psql with host, user and database placeholders. Reading this sequence does not execute it. Tables use IF NOT EXISTS and the five user columns use ADD COLUMN IF NOT EXISTS, but separate index, policy, constraint and trigger creation statements are not all guarded. The complete file therefore is not automatically safe to rerun unchanged.

The source names five related paths or integrations: RISER-Build-References-for-C4.md, C4-Review-Chain.md, C4-Prerequisites-Checklist.md, Build 6 src/c4_checkpoint_handler.ts and RISER-C4-Weekly-Rhythm-Setup-SOP.md. Their implementation and deployment are not supplied by this schema. Preserve the full SQL, comments, design notes and migration references in the appendix.

Apply the educational connection

This design attempts to turn Hormozi-style offer analysis into traceable artifacts before a Brunson-style offer presentation is finalized. The value of the database is provenance and accountable review, not merely a green completion flag. As authored practice, trace one worksheet from its file ID through cited evidence, rubric score, authorized review and downstream completion. Mark every unverified dependency and every condition the code does not enforce. Deliver a schema-to-artifact map and a review of those gaps; no database deployment is part of this lesson's completion.

Sources and resources

- Complete assigned C4 schema. - D0404: Value Equation Worksheet and D0413: actual reviewer YAML. - PostgreSQL constraints and CREATE POLICY: primary constraint and policy semantics. - Supabase row-level security and database functions: primary access-control references. - Acquisition.com value-equation checklist, ClickFunnels value ladder and RISER NATION CORP.

Assigned source links

D0411 original source 1

Complete current original file text

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

# 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*
Complete local source copy including original filing metadata and formatting

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

# 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*

Build a clear, optional one-time-offer video

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source context

Outline every section of the assigned OTO script while keeping the original purchase and any additional purchase clear. The source suggests a three-to-five-minute video and prices from $97 to $1,999. These are its planning guidelines, not current RISER prices or a universal optimal range.

Choose the right next offer

The source discourages more of the same purchase, with an exception for physical products, and rejects random unrelated items. It favors the customer's next needed resource or tool, or a method that helps with the original goal more efficiently. Its physical-product exception is not automatic evidence that a duplicate purchase is appropriate. Explain the distinct added benefit and preserve what was already included in the original purchase.

The original instructs the presenter not to confirm that the order is complete, fearing that this closes a sales loop. Keep that instruction in the appendix but do not apply it in a way that confuses the buyer. Confirm the actual order status and identify the OTO as optional, with a clear way to decline and continue to the purchased material. An additional charge requires an understandable additional choice.

Reaffirm the first purchase without inventing results

State what the buyer ordered and the goal it is intended to support. The template then suggests three times the results, twice the speed and later half the time, followed by a result-and-timeframe blank. These are unsubstantiated sample claims. Replace them with a specific supported benefit and realistic conditions; do not guarantee the original product will produce an outcome simply because the customer purchased it.

The script calls the buyer an action taker and says the offer is only available to them now. Use an eligibility statement only if true. Praise or prior commitment should not imply an obligation to buy again. Describe a genuine limitation accurately, rather than treating “one time” as a license to fabricate exclusivity.

Explain the One Thing and future-state connection

Name the additional product, identify one relevant strategy inside it and explain how that strategy works. The source says there is not time to describe every detail; that does not justify omitting material scope, requirements or limitations. The “One Thing” should help the buyer understand the added mechanism rather than hide the rest of the exchange.

Then invite the buyer to imagine what using that capability could change. Label hypothetical outcomes as illustrations and connect them to actual delivery. The first CTA asks the viewer to click below the video to add the item to the order. In a real page, make the price, charge and action explicit; this lesson supplies no current checkout button or authorization to place an order.

Present terms, stack and genuine availability

The guarantee section has blanks for a promised condition and remedy, including money back. It is a template, not an approved policy. Define eligibility, timeframe, measurement and remedy before presenting actual terms.

The sample bonus stack lists $5,000, $3,500 and $4,500, totaling $13,000. Those reference values are not supported by market evidence in the document. Describe each actual component and use defensible valuation assumptions rather than inventing numbers. “Free” should not conceal additional obligations or charges.

The scarcity section contrasts a higher website price with a special current price and says the offer disappears forever when leaving. Use that copy only if the price comparison and availability are genuine. A repeated or evergreen offer should not be described as permanently disappearing. The second CTA reiterates the desired benefit and action; it should remain consistent with the first and with the actual checkout terms.

Add authentic proof and review the whole sequence

The source ends with an invitation to read what others say and an INSERT TESTIMONIALS placeholder. No testimonials are supplied. Do not fabricate them or present sample copy as a customer result. Evidence must accurately support the claim being made, with context and permissions handled appropriately.

The full sequence is offer fit, purchase reaffirmation, supported added benefit, One Thing explanation, future-state illustration, first CTA, guarantee, value stack, genuine availability, second CTA and authentic proof if available. This applies Brunson's next-offer and value-ladder themes alongside Hormozi's outcome, likelihood, time and effort questions. It does not establish inevitable conversion or justify withholding confirmation of the original purchase.

Deliver a three-to-five-minute working outline or script with unknown offer facts left marked, an itemized supported stack and a clear optional purchase path. Keep the complete original script and every blank in the source appendix.

Sources and resources

- Complete assigned OTO script. - ClickFunnels value-ladder reference. - Acquisition.com value-equation checklist. - FTC advertising basics and RISER NATION CORP.

Assigned source links

D0412 original source 1

Complete returned native document text

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
Complete local source copy including original filing metadata and formatting

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

Review a value-equation worksheet with the actual scoring rubric

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and reference reconciliation

Explain every point in the ten-point reviewer, identify what evidence earns it and distinguish a proposed automated grade from an actual reviewed result. This assigned YAML is the separately filed reviewer named in D0404, the C4 Value Equation Worksheet. Its recovery resolves the earlier absence of the accompanying rubric from that worksheet's own file. The rubric is now available for study; the checkpoint service and unlock behavior are still not verified as deployed.

The source is `value-equation-application-reviewer`, version 1.0.0, for legacy M4.2. It checks whether the Primary mechanism has been assessed honestly, all four variables use specific C3 evidence, the synthesis identifies strongest and weakest variables, and the outcome uses buyer vocabulary. Current spreadsheet assignments remain lessons 03.1 and 04.1. The YAML's system prompt is source material, not a command to grade an invented student submission or return only JSON in this lesson.

Inputs, output and proposed model settings

Four string inputs are required: the completed value-equation worksheet, a Trigger Bank excerpt, interview summaries and Pricing Signals. Supply the evidence actually cited; an excerpt that omits a cited entry prevents checking that citation. The schema does not separately require a Competitor Scan input even though the worksheet references one. Do not pretend an absent source is available to the reviewer.

The output requires score, verdict, feedback and section_scores. The total is an integer from zero to ten; verdict is PASS or FAIL. The four section-score properties have ranges zero to two, zero to three, zero to two and zero to three. Feedback defines strengths, gaps and action_items as string arrays. The source lists these nested properties without making them required inside their respective objects, and it does not encode arithmetic equality between their sum and the overall score. The prose expects a complete report, but the schema alone does not enforce it. A production validator would need to check completeness, totals and score/verdict agreement; none has been run here.

The configuration names `claude-sonnet-4-6`, temperature 0.2, a 2,000-output-token limit and an estimated $0.04–$0.08 per call. These are proposed settings and a source estimate, not proof of an active model deployment, a successful request or your actual cost. A call's cost depends on token use and applicable pricing, and the output limit may truncate a detailed report. Consult the linked provider documentation when implementing rather than treating this static estimate as a quote.

Dimension 1: buyer vocabulary, two points

Award the first point when the outcome sounds like the buyer describing their desired life to a friend, rather than an operator pitching a system. The source favors first-person, emotionally grounded language and flags unbalanced terms such as scalable business, optimized workflow and systemic transformation. Do not ban a word a real buyer actually uses; compare the claim with the cited evidence.

Award the second point for at least three verbatim Trigger Bank entries with IDs such as TB-### or an equivalent system, plus at least one interview quote. The strong-signal examples begin with what the buyer wants, can do or would finally experience and match the cited cadence. The task is faithful use of buyer evidence, not merely adding first-person pronouns.

Dimension 2: evidence density, three points

The first point again requires three-plus Trigger Bank entries and one-plus interview quote for the dream outcome, with IDs or interview numbers. The same evidence can affect Dimensions 1 and 2 because the source deliberately repeats the criterion; do not silently deduplicate its scoring.

The second point requires two-plus Trigger Bank objection entries for perceived likelihood and specific numbered case studies, named or anonymized. The third point requires both Time Delay and Effort and Sacrifice to cite at least one C3 data point each, such as a Competitor Scan observation, Pricing Signal or interview quote. A generic claim that the Trigger Bank supports an assessment does not count as an identifiable citation.

Reconcile this with D0404 before submission. The worksheet asks for an adjacent competitor proof observation in the likelihood section; this reviewer additionally asks for numbered cases. The worksheet specifically asks for a Pricing Signals observation for time and a Trigger Bank quote for effort; the reviewer allows broader C3 evidence in those sections. Meeting the worksheet's specific requests and the reviewer's additional case-reference request is a practical reconciliation. Do not substitute a permissive reviewer rule for missing worksheet evidence. Its statement that citations without IDs fail the dimension also needs consistent interpretation alongside the three individual points; record how partial evidence is handled.

Dimension 3: honest weakness assessment, two points

The first point requires an honest case-study count. The source says two cases cannot justify its Strong likelihood rating. Report the actual count and relevance rather than inflating it. The second point requires a genuine weakness in the synthesis instead of a vague claim that everything is solid. The rubric treats uniformly strong ratings as a warning sign.

Use that warning to investigate, not to invent a defect for a score. A relative weakest variable may still be strong in absolute terms. Explain uncertainty and comparative room for improvement with evidence. A guarantee can address specified risk but cannot manufacture missing proof; the source's example about using M4.6 to address thin case studies must be read with that limit.

Dimension 4: targeting clarity, three points

Award one point for naming the strongest variable with a two- or three-sentence justification. Award one for naming the weakest and its strengthening path. Award one for mapping particular later modules to the variables they will address. “Fix the landing page” alone is too vague: specify what buyer uncertainty or effort the change resolves and why that later work fits the diagnosis.

The four dimensions total ten points. A score of seven or more is PASS in the source's workflow and proceeds to M4.3. Five or six is FAIL with specific revision guidance. Below five is FAIL with mentor escalation because the underlying C3 evidence may be insufficient. Seven points can still include lost points in a critical area; a pass is the rubric's threshold, not proof that every requirement or claim is complete.

Feedback, failure modes and governance

The report should contain one to three specific strengths citing the student's text, one to four gaps tied to text or omissions, and concrete revisions. Flag every dimension that lost points. The source requests JSON only from the grading service, but no service is being invoked in this lesson.

Preserve all five failure-mode responses. Operator vocabulary loses the first buyer-language point and calls for rewriting from actual quotes. Universal strength ratings prompt a more honest comparison. Citations without IDs require adding the missing identifiers. Generic synthesis requires a specific module-to-variable map. A Trigger Bank below 200 entries or thin Pricing Signals routes the learner back to legacy C3 M3.2 or M3.6 instead of repeatedly submitting weak M4.2 work. That 200-entry gate appears in the failure guidance, not the four-field input schema or a separate numeric scoring rule.

Governance names quarterly review, a curriculum-quality-team owner and a Build 6 M4.2 checkpoint handler. The synthesis feeds M4.3 variant design and the M4.8 offer-fit validator. These are named dependencies, not evidence of configured routing or completed review. Preserve the entire YAML so input/output schemas, settings and governance are available with the lesson.

Apply the educational connection

Use the reviewer to examine Hormozi's four value levers with evidence. Then use a Brunson-style offer presentation to communicate the resulting outcome and exchange clearly. The grade should improve the offer's substance rather than encourage feature stuffing or stronger rhetoric. Deliver a point-by-point review with traceable citations, unresolved ambiguities and a revision plan; do not claim a real pass without a real submission and review.

Sources and resources

- Complete assigned reviewer YAML. - D0404: original Value Equation Worksheet. - D0411: C4 database schema. - JSON Schema object requirements: properties and required fields are distinct. - Anthropic Sonnet information and provider pricing: check implementation-time availability and costs. - Acquisition.com value-equation checklist. - ClickFunnels value-ladder reference and RISER NATION CORP.

Assigned source links

D0413 original source 1

Complete current original file text

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

prompt_name: value-equation-application-reviewer
version: 1.0.0
purpose: >
  Score M4.2 student-submitted Value Equation Worksheet against 10-point rubric.
  Validates that Hormozi's Value Equation has been applied honestly to the
  student's Primary mechanism, that each of four variables cites C3 evidence
  with specificity, that the synthesis identifies strongest and weakest variables
  explicitly, and that the Dream Outcome uses buyer vocabulary rather than
  operator vocabulary.
model: claude-sonnet-4-6
temperature: 0.2
max_tokens: 2000
cost_per_call_estimate_usd: 0.04-0.08

input_schema:
  type: object
  required: [value_equation_worksheet, student_c3_trigger_bank_excerpt, student_c3_interview_summaries, student_c3_pricing_signals]
  properties:
    value_equation_worksheet: {type: string}
    student_c3_trigger_bank_excerpt: {type: string}
    student_c3_interview_summaries: {type: string}
    student_c3_pricing_signals: {type: string}

output_schema:
  type: object
  required: [score, verdict, feedback, section_scores]
  properties:
    score: {type: integer, minimum: 0, maximum: 10}
    verdict: {type: string, enum: [PASS, FAIL]}
    section_scores:
      type: object
      properties:
        dream_outcome_buyer_vocabulary: {type: integer, minimum: 0, maximum: 2}
        evidence_citation_density: {type: integer, minimum: 0, maximum: 3}
        honest_weakness_assessment: {type: integer, minimum: 0, maximum: 2}
        synthesis_targeting_clarity: {type: integer, minimum: 0, maximum: 3}
    feedback:
      type: object
      properties:
        strengths: {type: array, items: {type: string}}
        gaps: {type: array, items: {type: string}}
        action_items: {type: array, items: {type: string}}

system_prompt: |
  You are grading a C4 M4.2 deliverable — the Value Equation Worksheet. M4.2 is
  the diagnostic that drives every remaining C4 module. A student who
  misdiagnoses their weakest Value Equation variable will produce M4.3-M4.7 work
  targeted at the wrong problem — typically compensating with feature-stuffing
  rather than addressing the actual weakness.

  # Rubric — 10 points total across 4 dimensions

  ## Dimension 1 — Dream Outcome Buyer Vocabulary (2 pts)

  Section 1 (Dream Outcome) must state the outcome in the buyer's own language,
  not the operator's.

  - +1: Dream Outcome sentence sounds like something a buyer would say to a friend at dinner (first-person, life-state, emotional grounding) rather than an operator pitch ("scalable business," "optimized workflow," "systemic transformation")
  - +1: At least 3 verbatim Trigger Bank entries cited with IDs (TB-### or equivalent) and at least 1 customer interview quote

  Weak signal: Dream Outcome uses words like "leverage," "systems," "processes," "scale," "optimize," "workflow" without balancing buyer-vocabulary. These are operator words.

  Strong signal: Dream Outcome uses first-person emotional language ("I want to...", "I can...", "I'd finally...") that matches the cadence of the cited Trigger Bank entries.

  ## Dimension 2 — Evidence Citation Density (3 pts)

  Each of the four variables must cite specific C3 evidence, not generic claims.

  - +1: Dream Outcome variable cites 3+ Trigger Bank entries and 1+ interview quote with IDs/numbers
  - +1: Perceived Likelihood variable cites 2+ Trigger Bank objection entries and references specific case studies by number (named or anonymized)
  - +1: Time Delay and Effort & Sacrifice variables each cite at least 1 C3 data point (Competitor Scan observation, Pricing Signal data, or interview quote)

  CRITICAL: citations without IDs do not count. "Trigger Bank entries show..." without specific entry # is handwave citation and fails this dimension.

  ## Dimension 3 — Honest Weakness Assessment (2 pts)

  Section 2 (Perceived Likelihood) and Section 5 (Synthesis) must be honest about
  what the student does not have, not aspirational.

  - +1: Perceived Likelihood assessment names the actual case study count honestly. A student with 2 case studies rating Perceived Likelihood as "Strong" fails this point — self-deception is flagged.
  - +1: Synthesis identifies a genuine weakness (not "everything is solid" or "minor tweaks needed"). Students with truly strong Primaries should still have at least one legitimately weaker variable; universal strength is a red flag for self-assessment failure.

  ## Dimension 4 — Synthesis Targeting Clarity (3 pts)

  Section 5 must translate the diagnosis into specific C4-module targeting.

  - +1: Strongest variable named explicitly with 2-3 sentence justification
  - +1: Weakest variable named explicitly with strengthening path identified
  - +1: Map of C4 modules to variables is present — which module will work on which variable

  Weak signal: "The offer will be strong once we fix the landing page" — this is not targeting; it is hoping. Strong signal: "M4.6 guarantee will specifically reverse Perceived Likelihood risk because the weakness is case study thinness, not mechanism quality."

  # Verdict

  - Score >= 7/10 → PASS (proceeds to M4.3)
  - Score 5-6/10 → FAIL with specific revision guidance
  - Score < 5/10 → FAIL with mentor escalation (likely indicates C3 outputs are insufficient for M4.2)

  # Feedback structure

  Strengths: 1-3 specific positive observations citing the student's text
  Gaps: 1-4 specific gaps citing text or omissions; flag any dimension that lost points
  Action items: concrete revisions (not abstract advice)

  # Output

  Return JSON only. No preamble, no postamble.

known_failure_modes:
  - scenario: Dream Outcome in operator vocabulary
    mitigation: Dimension 1 loses first point; student rewrites using verbatim Trigger Bank entries as vocabulary source
  - scenario: Universal strength rating across all 4 variables
    mitigation: Dimension 3 flags self-assessment failure; student honestly assesses weakest variable before resubmitting
  - scenario: Citations without IDs (handwave "Trigger Bank shows...")
    mitigation: Dimension 2 fails; student adds specific entry IDs
  - scenario: Synthesis is generic "offer will be strong" language
    mitigation: Dimension 4 fails; student writes specific module-to-variable mapping
  - scenario: C3 Trigger Bank is under 200 entries or C3 pricing signals are thin
    mitigation: Root cause — C3 was completed thinly. Route back to C3 M3.2 / M3.6 rather than attempt M4.2 again

governance:
  review_cadence: quarterly
  owner: curriculum-quality-team
  consumed_by: Build 6 M4.2 checkpoint handler
  downstream: synthesis section feeds M4.3 variant design targeting and offer-fit-validator at M4.8
Complete local source copy including original filing metadata and formatting

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

prompt_name: value-equation-application-reviewer
version: 1.0.0
purpose: >
  Score M4.2 student-submitted Value Equation Worksheet against 10-point rubric.
  Validates that Hormozi's Value Equation has been applied honestly to the
  student's Primary mechanism, that each of four variables cites C3 evidence
  with specificity, that the synthesis identifies strongest and weakest variables
  explicitly, and that the Dream Outcome uses buyer vocabulary rather than
  operator vocabulary.
model: claude-sonnet-4-6
temperature: 0.2
max_tokens: 2000
cost_per_call_estimate_usd: 0.04-0.08

input_schema:
  type: object
  required: [value_equation_worksheet, student_c3_trigger_bank_excerpt, student_c3_interview_summaries, student_c3_pricing_signals]
  properties:
    value_equation_worksheet: {type: string}
    student_c3_trigger_bank_excerpt: {type: string}
    student_c3_interview_summaries: {type: string}
    student_c3_pricing_signals: {type: string}

output_schema:
  type: object
  required: [score, verdict, feedback, section_scores]
  properties:
    score: {type: integer, minimum: 0, maximum: 10}
    verdict: {type: string, enum: [PASS, FAIL]}
    section_scores:
      type: object
      properties:
        dream_outcome_buyer_vocabulary: {type: integer, minimum: 0, maximum: 2}
        evidence_citation_density: {type: integer, minimum: 0, maximum: 3}
        honest_weakness_assessment: {type: integer, minimum: 0, maximum: 2}
        synthesis_targeting_clarity: {type: integer, minimum: 0, maximum: 3}
    feedback:
      type: object
      properties:
        strengths: {type: array, items: {type: string}}
        gaps: {type: array, items: {type: string}}
        action_items: {type: array, items: {type: string}}

system_prompt: |
  You are grading a C4 M4.2 deliverable — the Value Equation Worksheet. M4.2 is
  the diagnostic that drives every remaining C4 module. A student who
  misdiagnoses their weakest Value Equation variable will produce M4.3-M4.7 work
  targeted at the wrong problem — typically compensating with feature-stuffing
  rather than addressing the actual weakness.

  # Rubric — 10 points total across 4 dimensions

  ## Dimension 1 — Dream Outcome Buyer Vocabulary (2 pts)

  Section 1 (Dream Outcome) must state the outcome in the buyer's own language,
  not the operator's.

  - +1: Dream Outcome sentence sounds like something a buyer would say to a friend at dinner (first-person, life-state, emotional grounding) rather than an operator pitch ("scalable business," "optimized workflow," "systemic transformation")
  - +1: At least 3 verbatim Trigger Bank entries cited with IDs (TB-### or equivalent) and at least 1 customer interview quote

  Weak signal: Dream Outcome uses words like "leverage," "systems," "processes," "scale," "optimize," "workflow" without balancing buyer-vocabulary. These are operator words.

  Strong signal: Dream Outcome uses first-person emotional language ("I want to...", "I can...", "I'd finally...") that matches the cadence of the cited Trigger Bank entries.

  ## Dimension 2 — Evidence Citation Density (3 pts)

  Each of the four variables must cite specific C3 evidence, not generic claims.

  - +1: Dream Outcome variable cites 3+ Trigger Bank entries and 1+ interview quote with IDs/numbers
  - +1: Perceived Likelihood variable cites 2+ Trigger Bank objection entries and references specific case studies by number (named or anonymized)
  - +1: Time Delay and Effort & Sacrifice variables each cite at least 1 C3 data point (Competitor Scan observation, Pricing Signal data, or interview quote)

  CRITICAL: citations without IDs do not count. "Trigger Bank entries show..." without specific entry # is handwave citation and fails this dimension.

  ## Dimension 3 — Honest Weakness Assessment (2 pts)

  Section 2 (Perceived Likelihood) and Section 5 (Synthesis) must be honest about
  what the student does not have, not aspirational.

  - +1: Perceived Likelihood assessment names the actual case study count honestly. A student with 2 case studies rating Perceived Likelihood as "Strong" fails this point — self-deception is flagged.
  - +1: Synthesis identifies a genuine weakness (not "everything is solid" or "minor tweaks needed"). Students with truly strong Primaries should still have at least one legitimately weaker variable; universal strength is a red flag for self-assessment failure.

  ## Dimension 4 — Synthesis Targeting Clarity (3 pts)

  Section 5 must translate the diagnosis into specific C4-module targeting.

  - +1: Strongest variable named explicitly with 2-3 sentence justification
  - +1: Weakest variable named explicitly with strengthening path identified
  - +1: Map of C4 modules to variables is present — which module will work on which variable

  Weak signal: "The offer will be strong once we fix the landing page" — this is not targeting; it is hoping. Strong signal: "M4.6 guarantee will specifically reverse Perceived Likelihood risk because the weakness is case study thinness, not mechanism quality."

  # Verdict

  - Score >= 7/10 → PASS (proceeds to M4.3)
  - Score 5-6/10 → FAIL with specific revision guidance
  - Score < 5/10 → FAIL with mentor escalation (likely indicates C3 outputs are insufficient for M4.2)

  # Feedback structure

  Strengths: 1-3 specific positive observations citing the student's text
  Gaps: 1-4 specific gaps citing text or omissions; flag any dimension that lost points
  Action items: concrete revisions (not abstract advice)

  # Output

  Return JSON only. No preamble, no postamble.

known_failure_modes:
  - scenario: Dream Outcome in operator vocabulary
    mitigation: Dimension 1 loses first point; student rewrites using verbatim Trigger Bank entries as vocabulary source
  - scenario: Universal strength rating across all 4 variables
    mitigation: Dimension 3 flags self-assessment failure; student honestly assesses weakest variable before resubmitting
  - scenario: Citations without IDs (handwave "Trigger Bank shows...")
    mitigation: Dimension 2 fails; student adds specific entry IDs
  - scenario: Synthesis is generic "offer will be strong" language
    mitigation: Dimension 4 fails; student writes specific module-to-variable mapping
  - scenario: C3 Trigger Bank is under 200 entries or C3 pricing signals are thin
    mitigation: Root cause — C3 was completed thinly. Route back to C3 M3.2 / M3.6 rather than attempt M4.2 again

governance:
  review_cadence: quarterly
  owner: curriculum-quality-team
  consumed_by: Build 6 M4.2 checkpoint handler
  downstream: synthesis section feeds M4.3 variant design targeting and offer-fit-validator at M4.8

Source gap: why this offer exists

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

The current native source contains only the title `why_this_offer_exists` and a TODO to populate it from Irresistible Offer Engine outputs. The local copy confirms the same missing-body status. No actual reason-why explanation, founder account or offer evidence is supplied.

Keep this assignment visible in lesson 03.1 with its complete returned text and link. This is not a completed teaching adaptation. The separately available engine prompt requests a reason-why explanation, but its request is not the missing output and must not be treated as verified business history. Completion requires the populated source, a full review and verified lesson integration.

- Assigned reason-why source. - Related Irresistible Offer Engine prompt.

Assigned source links

D0414 original source 1

Complete returned native document text

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


# why_this_offer_exists

TODO: Populate via Irresistible Offer Engine outputs.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1DmqBOsWJQ_VGdSIvtWdQNyVRB609pejf8Z8aPkFIAaM/edit?usp=drivesdk"
drive_file_id: "1DmqBOsWJQ_VGdSIvtWdQNyVRB609pejf8Z8aPkFIAaM"
created: "2026-02-20T15:55:19.980Z"
modified: "2026-06-04T02:09:54.050Z"
---

# why_this_offer_exists.md

# why_this_offer_exists


TODO: Populate via Irresistible Offer Engine outputs.

Build a sales letter through all twelve source steps

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and original structure

Use David Frey's assigned two-page sales-letter template to plan a complete message, while checking evidence, terms and reader choice. Both original pages use three columns; their full text and original PDF are retained. The source title calls the method foolproof, but no framework guarantees sales.

The opening list places scarcity at step eight and guarantee at step nine. The detailed body reverses them: guarantee is eight and scarcity nine. This lesson follows the detailed body and preserves both original orders. All twelve functions remain included.

Start with seven buying questions

The source names seven objections: you do not understand my problem; how do I know you are qualified; I do not believe you; I do not need it now; it will not work for me; what happens if I dislike it; and I cannot afford it. Treat these as questions to investigate. They can reflect a legitimate mismatch, not merely resistance to overcome.

Its motivation discussion proposes emotion followed by logical justification, gain and fear of loss, and a stronger response to loss. It gives a $50 marriage-course headline comparison and claims the loss-focused version sells five to one. No underlying study is supplied. Do not present these as universal psychology or a verified result. Buyers may use practical reasoning, emotion and several motivations together.

The source calls its next list seven universal motivations but actually lists eight: wealth, appearance, health, popularity, security, inner peace, free time and fun. Preserve all eight as possible desired benefits, not exhaustive or biologically universal categories. Check which, if any, are relevant to the actual buyer and product.

1. Get attention

Make the headline relevant to the intended reader and consistent with the content delivered. The three supplied headline patterns are a how-to linked to a benefit, secrets about a topic being revealed, and a warning not to take an action until a condition is understood. Teach the function of each: useful instruction, a knowledge gap and a relevant caution. Do not invent secret knowledge or frightening consequences simply to force attention. The source's observations about short attention and discarded mail are framing, not a measured attention-span rule.

2. Identify the problem

Describe an observed problem in language the reader recognizes. The original recommends intensifying pain and claims people change only under severe pain; that is not established here. Acknowledge the problem without exaggerating distress or assuming every reader shares it.

Its illustration follows someone arriving home with a garage door that will not open, tripping on a dark porch, struggling for a key, scratching the door and finally remembering the car is still running. This is a constructed story showing a sequence of frustrations, not a verified customer incident. Use accurate, relevant situations in your own work and avoid claiming a product prevents unrelated harms.

3. Provide the solution

Introduce the provider and product or service, then explain how the mechanism addresses the problem. The original says it will solve the problem; your version must match evidence, delivery scope and conditions. A clear solution description includes what changes, what remains the buyer's responsibility and where the offer does not fit.

4. Present credentials

The source lists five forms of credibility: successful case studies, relevant companies or people served, time in the field, speaking engagements and awards or recognition. Use only authentic, relevant facts. Name-dropping does not establish permission to imply endorsement, and years of experience do not alone prove a particular outcome. Prior success does not guarantee the same result for every buyer.

5. Show benefits

Draw two columns, with features on the left and their relevant benefits on the right. Explore direct and less obvious benefits, then use readable bullet points. The source's hot-tub example moves from physical comfort to uninterrupted conversation and then a better marriage. The final relationship outcome is a speculative example, not a demonstrated product effect; separate an opportunity a feature creates from a result it cannot promise.

The source suggests that one benefit can drive a purchase. Use that as a reason to understand priorities, not to list every imaginable benefit regardless of support. Each benefit should have a defensible connection to the actual feature and buyer's situation.

6. Give social proof

Use authentic testimonials or other relevant evidence with accurate context. The source suggests customer photos, names, city, state and even phone number. Do not expose private contact information or imply consent from the template. A testimonial supports what that person actually experienced; it does not by itself prove every product claim or typical outcome. No actual customer testimonials are supplied in this PDF.

7. Make the offer

Explain the price, terms and any included gifts together. The source's car example combines a reduced retail price, low interest and a year of fuel. These are illustrative components, not a currently available financing offer. It recommends adding relevant products or services and explaining benefits instead of relying only on price reductions. That can clarify perceived value, but the exchange still needs workable economics and accurate reference prices.

8. Give a feasible guarantee

The original advocates the strongest guarantee and says refund fears generally do not materialize and all buyer risk can be removed. Neither claim is supported by data here. A refund can address a specified financial exposure while leaving time, effort and opportunity costs. Design terms the provider can honor and explain eligibility, measurement, timing and remedy.

Preserve the full two-part source example as an example. It promises at least $4,490 additional profit within twelve months if the buyer diligently uses a few techniques, with a full course refund if that does not occur. It separately offers a full refund at any time during those twelve months if the buyer sincerely feels the promises were not delivered, including the last day. The source calls this no-questions-asked protection, although its outcome clause includes conditions. None of it is a RISER guarantee or verified earnings result.

The source also recommends explaining why an unusually attractive offer is possible, using an inventory-ordering mistake and overstock as an example. Supply a reason only if true; do not manufacture an operational story to make a price seem credible.

9. Explain genuine scarcity

The text lists four reasons people may delay: insufficient urgency about the problem, being busy or forgetting, not perceiving value above price, or what it labels laziness. Treat these as the author's hypotheses, not diagnoses of a buyer's character. Someone may rationally decide the offer is unsuitable.

Its three scarcity examples are a bonus deadline, a real limit of fifty units allocated first come first served with no more afterward, and a temporary price that returns to its original level on a specified date. Use only conditions you can substantiate and honor. The source itself warns that disregarding a stated deadline erodes trust. Do not use resetting deadlines or false supply claims.

10. Make the action clear

Explain exactly how to take the next step. The historical template mentions phone calls, order forms, faxed forms and store visits, with examples of calling now, mailing a form today and visiting by Friday. Adapt the action to the actual channel and truthful timing, including clear charges and conditions when it is a purchase.

Keep references to the action consistent throughout the letter. The source illustrates this with a free information line appearing in the offer, testimonials and final CTA. Do not rewrite a testimonial to insert that wording; preserve the customer's actual account. Repetition should aid understanding rather than obscure the choice.

11. Describe the consequences of inaction fairly

The original warning lists continued profit struggles, too much work for too few customers, lost bonuses, unchanged results and competitors winning the business. These are possible concerns to examine, not guaranteed consequences of declining this offer. Explain a supported tradeoff without telling a reader their situation must remain terrible unless they buy. A buyer may have alternatives, and waiting may sometimes be appropriate.

12. Close with a reminder

A postscript can restate the offer, action and any genuine deadline or quantity limit. The source claims the P.S. is the third-most-read part and notes that some writers add several postscripts; no supporting measurement appears in the PDF. Treat a concise reminder as a readability choice rather than a proven universal ranking. Keep it consistent with the main offer.

Apply all five additional tips

First, begin with features and benefits; the source suggests a 3-by-5 card with a feature on the front and related benefit on the back. Second, let a draft sit for a day or so before revising, as a way to gain perspective. Third, maintain a swipe file of examples for analysis and inspiration without copying protected material or unrelated claims. Fourth, prepare a customer-profile sheet so the writing addresses a real audience. Fifth, use the length needed to make the case clearly; its half-page and twenty-four-page examples are possibilities, not prescribed lengths or performance benchmarks.

The closing biography identifies David Frey with Marketing Best Practices Inc., a Houston-based consultancy, and its newsletter. Preserve that as the source's historical author description; it is not a current-role verification. The embedded MarketingBestPractices.com link could not be opened successfully during this review and remains an explicit access gap, not omitted.

Connect the educational themes

Use the letter's attention, story, offer and action functions alongside Brunson-style presentation. Use Hormozi's value levers to ensure the underlying offer has a relevant outcome, supported likelihood and honest timing and effort. Neither framework replaces substantiation. Deliver a twelve-section outline, a feature-to-benefit map, claim evidence and actual proposed terms, leaving unknowns marked. The original PDF remains available for complete source study.

Sources and resources

- Complete assigned two-page PDF. - Original embedded Marketing Best Practices link: access failed during this review. - FTC advertising basics. - ClickFunnels value-ladder reference and Acquisition.com value-equation checklist. - RISER NATION CORP.

Assigned source links

D0415 original source 1

Original embedded resource links

Original PDF embedded reference:

Complete current original file text

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

PAGE 1
12-Step Foolproof Sales 
Letter Template 
by David Frey 
  
Yr sales letter must overcome yr 
reader’s buying resistance & persuade 
them to take action. Whether it’s in 
person or on paper, the process of 
overcoming buying resistance is the 
same. Hurdles are spoken & unspoken: 
1. “You don’t understand my 
problem”  
2. “How do I know you’re qualified?”  
3. “I don’t believe you”  
4. “I don’t need it right now” 
5. “It won’t work for me”  
6. “What happens if I don’t like it?”  
7. “I can’t afford it” 
Effective sales letters must address 
some or all of these objections. This 
template overcomes each objection in 
a careful, methodical series of 
copywriting tactics. The 12 steps: 
1. Get attention  
2. Identify the problem  
3. Provide the solution  
4. Present your credentials  
5. Show the benefits  
6. Give social proof 
7. Make your offer  
8. Inject scarcity  
9. Give a guarantee  
10. Call to action  
11. Give a warning  
12. Close with a reminder 
Each step adds to reader’s 
emotions while calming their fears. 
  
Motivation - An Emotional Thing 
We buy based on emotions & 
justify our purchase based on logic 
only after the sale. So each step in the 
sales letter process must build on 
reader’s emotions to where they are 
motivated to act. 
Only 2 things motivate people: the 
promise of gain or the fear of loss. 
Fear of loss is the stronger motivator. 
Would you rather buy a $50 
course on “How to Improve Your 
Marriage” or “How to Stop Your 
Divorce or Lover’s Rejection?” Stats 
prove the 2 
nd  title outsells the first 5 to 
1. Why? It addresses fear of loss. 
Underlying promise of gain & fear 
of loss are 7 “universal motivations”. 
Position any product or service so it 
provides 1 or more motivation: 
1. To be wealthy  
2. To be good looking  
3. To be healthy  
4. To be popular 
5. To have security  
6. To achieve inner peace  
7. To have free time  
8. To have fun 
Ultimate motivations are what 
people really  want. Yr product is just a 
way to give these benefits. Always 
focus on these motivational factors. 
  
12-Step Sales Letter System 
1. Get Attention  
The opening headline is the 1 st  
thing yr reader sees. It must  get their 
attention. People have a short attention 
span & sort mail over the wastebasket. 
Headline must target their interest, or 
they’ll throw yr letter away. 
3 Proven headline templates: 
a. How To  _________________ 
People love to know how to do 
things. To get attention, combine “how 
to” w/ a powerful benefit. 
b. Secrets of _________ Revealed!  
People want insider secrets. We 
love to know things others aren’t privy 
to. Knowledge is power. Those who 
have it feel powerful. It’s exciting to 
discover secrets. 
c. Warning! Don’t Even Think of  
_______ Until You  _______  
This headline leverages fear of 
loss. Warning  demands attention. 
Combine it w/ targeted interest. 
  
2. Identify the Problem  
Tell yr reader how it feels to have 
that problem. They should read & say, 
“Yeah, that’s exactly how I feel”. Rub 
salt into that wound. 
Agitate the problem so they really 
feel pain & agony. Companies & 
people only change their ways due to 
severe pain. Tell a short, painful story: 
There’s nothing worse than getting home 
in the evening and not having your garage 
door open. It’s dark outside. You trip on 
the porch step and search for your front 
door key.Finally, you find it only to 
scratch your new front door looking for 
the keyhole. Exhausted, you go inside and 
plop on the couch just when you remember 
the car is still running in your driveway…. 
3. Provide the Solution  
They feel the pain. Now introduce 
yourself, yr product and/or yr service. 
Relieve their pain. Tell them there’s no 
need to struggle thru their problem. Yr 
product or service will solve it. 
  
4. Present your Credentials  
Now yr reader is thinking, Yeah, 
sure he can fix my problem. That’s 
what they all say . So prove to them 
now that you can be trusted. List yr 
credentials – any one of these: 
1. Successful case studies.  
2. Prestigious companies (or people) 
you have done business with.  
3. The length of time you’ve been in yr 
field of expertise  
4. Conferences where you have spoken  
5. Important awards or recognitions 
Yr reader must feel “you’ve been 
there and done that” with great success 
and they can expect the same. 
  
5. Show the Benefits  
Now tell how they’ll personally 
benefit from yr product/service. Don’t 
just list features. Tell the benefits. 
People don’t care about you or yr 
product, only what it will do for them. 
Get a piece of paper. Draw a line 
down the center. Write the features on 
the left. Think about obvious & not-so-
obvius benefits. List those on the right. 
Most products have hidden benefits 
people don’t naturally think of. 
E.g: a hot tub not only soothes & 
relaxes yr muscles. It gives you an 
opportunity to talk to yr spouse w/out 
interruptions. Hidden benefit: greater 
communication with yr spouse & 
ultimately a better marriage! 
Bullet point ea benefit to make it 
easier to read. Think of every possible 
benefit yr reader may get. People often 
buy based on only one  of the benefits. 
  
6. Give Social Proof  
The reader wants it all to be true, 
but they just don’t believe you. You 
must build credibility & believability. 
Testimonials prove yr claims. Customr 
pictures w/ name, city, state & phone # 
(if possible) prove you are real.. 
  
7. Make Your Offer  
Yr offer is key to yr sales letter. A 
great offer can overcome mediocre 

PAGE 2
copy. Great copy can’t overcome a 
mediocre offer. Make them think, “I’d 
be stupid not to take this deal.” Best 
offers combine great price, terms, & 
free gifts. Selling a car? Then offer 
discounted retail price, low interest 
rate, & a free year of gas. Raise value 
of yr offer w/ add-on products/services 
r/t lower price. Vivid benefit explana-
tions raise offer’s perceived value.  
  
8. Give a Guarantee  
Make offer irresistible. Take all 
risk out of the purchase. People fear 
being ripped off. Did you ever buy a 
lousy product and couldn’t get yr $$ 
back? So do the strongest guarantee 
you can. Demonstrate yr confidence. 
Most small businesses already 
have a strong guarantee. If an irate 
customer wanted their $$ back, you’d 
just do it. But owners fear many 
people would want refunds. Doesn’t 
happen. When did you last ask for a 
full refund? Here’s a guarantee I give 
for one of my products: 
* * 100%, No Questions Asked, Take-
It-To-The-Bank Guarantee * * 
I personally guarantee if you make a 
diligent effort to use just a few of the 
techniques in this course, you'll 
produce at least $4,490 profit in the 
next 12 months. That's right, $4,490 
extra profit you never would have seen 
without this course. If you don't, I'll 
refund the entire cost of the course. 
Actually, you get double 
protection. Here's how. At any time 
during the 12 months, if you sincerely 
feel I fell short in any way on 
delivering everything I promised, I'll 
be happy to give you a complete 
refund. Even if it's on the last day of 
the twelfth month! 
This guarantee extends for 1 year. 
They’ll get specific benefits ($$). If 
they don’t get what they expect, they 
get their $$ back, no questions asked. 
This eliminates all buyer risk. 
Hint: Your offer may be so good, 
people won’t believe it. So always 
give the reason you can give such a 
great offer. E.g.: you goofed ordering 
inventory, so you’re overstocked and 
can offer such a great price. The 
reason why helps people reconcile yr 
irresistible offer & makes it believable.  
9. Inject Scarcity  
Most people take their time 
responding to offers, even irresistible 
ones, because:  
• They don’t feel enough pain to 
make a change  
• They are too busy & just forget  
• They don’t feel that the perceived 
value outweighs yr asking price  
• They are just plain lazy 
Use an extra incentive to motivate 
people. Inject scarcity into yr letter to 
create a fear of loss. Tell yr reader 
either the quantity is limited or yr offer 
is valid for only a limited time, 
something like this: 
• Purchase by (future date) to 
receive the entire set of free bonuses 
• Our supply is limited to only 50 
(item) & will be sent on a ‘first come, 
first served’ basis. After they’re gone 
there won’t be any more available. 
• This offer is only good until 
(future date) after which the (item) 
will return to its original price. 
Caution:  If you make an offer you 
need to live up to it. If you go back on 
your word after the deadline date you 
erode customer trust & confidence. 
  
10. Call to action  
Don’t assume yr reader knows 
what to do to get the benefits from yr 
offer. Clearly & concisely spell out 
how to make the order. Whether its 
picking up the phone & calling, filling 
out an order form, faxing the form to 
yr office etc…. tell them exactly  how 
to order from you. 
Be “action-oriented.” Say  
• Pick Up the Phone and Call Now!  
• Tear Off the Order Form and Send It 
In Today!  
• Come to Our Store by Friday and …   
Tell them explicitly & succinctly. 
Plant yr call to action throughout 
yr letter. If you ask the reader to call yr 
free info line, some testimonials might 
say, When I called their free info line  
or say in yr offer, When you call our 
free info line… Then the call to action 
at the end of the letter is consistent & 
won’t surprise or confuse people. 
  
11. Give a Warning  
A good sales letter builds emotion, 
right to the very end … even after yr 
call to action. Use “risk of loss”. Tell 
reader what will happen if they don’t 
take yr offer. They’ll continue to: 
• Struggle day to day to make profit  
• Work too hard for too few customers 
• Lose the chance for valuable bonuses 
• Keep getting what they’ve always got 
• See other companies get the business  
Paint a picture in the reader’s mind 
of consequences of not acting now. 
Remind them of their terrible situation, 
& that it doesn’t have to be that way. 
  
12. Close with a Reminder  
Always include a P.S. It’s the 3 rd  
most read element of yr letter. Some 
good copywriters add many P.P.Ses. 
Remind them of yr irresistible offer. 
Include yr call to action & remind 
them of the limited time (or quantity).  
  
A Few Extra Tips: 
Tip #1 : Start w/ Features/Benefits. 
Biggest hurdle to a great sales letter is 
just starting. A feature/ benefit list is 
easiest. Write each feature on a 3x5 
card. Put a related benefit on the back. 
Yr letter is off to a good start. 
Tip #2 : Complete yr letter & let it sit a 
day or so. You’ll be more objective 
when you edit.  
Tip #3:  Develop a “swipe file” to get 
yr creative juices flowing. When you 
see a great ad or effective letter, file it 
so you can refer back again & again. 
Companies pay $1000s to develop 
marketing materials; leverage that by 
using it as a model for yr own work. 
Tip #4:  Before yr sales letter, do a 
customer profile sheet. Write all you 
know about them. Focus on who 
you’re writing to. 
Tip #5:  How long should a sales letter 
be? As long as it needs to be. Each 
part of yr letter builds yr case. If ½ 
page does it, great. It takes 24 pages to 
sell some products. Whatever it takes. 
Each step builds yr case in a unique 
way & adds to the reader’s emotions. 
  
David Frey is President of Marketing 
Best Practices Inc ., a Houston-based 
small business marketing consulting 
firm. He is senior editor of Marketing 
Best Practices Newsletter  featuring 
small business marketing best practices.  
http://www.MarketingBestPractices.com

Connect the twenty-part script pack from learning to legacy

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and scope

Explain every topic in the source's five modules and twenty short scripts, then identify the evidence or deliverable each topic needs. These are introductory scripts, not twenty fully supplied courses. Their legacy Learn, Build, Do, Scale and Legacy labels do not replace the current twelve-course spreadsheet assignments. The practice activities below are authored expansions of the available topics, not recovered missing templates or proven systems.

Module 1: Learn

1. Customer motivations

The first script proposes five drives: transformation, identity, certainty and safety, status, and belonging. Ask what meaningful change the customer wants, how they describe themselves, what makes an outcome feel plausible, whether recognition matters and what community they seek. These are useful research lenses, not an exhaustive or universally ranked psychological model. The source's claims that people never buy logically, always choose the safest path and seek status because of biology are unsupported here. Use customer evidence rather than assuming these motives apply to everyone. Practice by mapping each relevant drive to an actual quote and leaving unsupported drives unassigned.

2. Beliefs about the offer, self and circumstances

The Brunson-labeled script names three barriers: belief about the vehicle, belief about oneself and belief about external factors. Separate doubts about the mechanism from doubts about capability or circumstances. The source proposes stories, demonstrations and transformation examples as ways to challenge a belief. Use accurate evidence and acknowledge when a doubt is justified. Not every objection is false, and a marketer's job is not to force a person to believe. Practice by pairing one objection in each relevant category with evidence, a limitation or a suitable alternative.

3. Positioning and category creation

The source invokes Ries and Trout and proposes defining a category rather than competing as an interchangeable commodity. Explain the buyer problem, alternatives and meaningful difference. Creating a label does not instantly establish leadership or eliminate competition, and competing does not automatically make a business a commodity. The promised full category-selection method is not included. Practice by writing a positioning hypothesis and comparing it against actual alternatives and buyer language.

4. Identity-based messaging

Identity can influence how a message feels relevant, but the script's strongest-force and unstoppable claims are not established. Describe the capabilities or role a buyer wants to develop without implying they are inferior unless they purchase. Words about becoming should remain connected to actual work and outcomes. Practice by comparing a feature-led explanation and an identity-relevant explanation, keeping the same supported facts in both.

Module 2: Build

1. An Onlyness Statement

The source asks for a sentence explaining why the provider is a distinctive choice and calls this category-king positioning. Define the audience, specific problem, approach and evidence. Do not claim to be the only or uncontested option without support. The file supplies no finished Onlyness Statement or research proving exclusivity. Practice by identifying which part of a proposed statement is factual, comparative or still hypothetical.

2. A Grand Slam Offer

The script names dream outcome, time delay, effort and sacrifice, and likelihood of success. In Hormozi's formulation, use perceived likelihood of achievement and consider the four levers together. Improve the outcome's relevance, support belief with evidence and reduce unnecessary delay and effort. The source says to eliminate risk and make an offer sell itself; neither is guaranteed. Practice by diagnosing one constraint on each lever and selecting a feasible improvement before adding stronger copy.

3. The Irresistible Offer theme

The Joyner-labeled introduction emphasizes an exchange that feels faster, easier, safer, clearer and more predictable, rather than merely discounted. Treat those as the script's design criteria, not a verified quotation or proof that only one buyer reaction will occur. Explain the actual delivery decisions behind each quality. Practice by replacing an unsupported adjective with a concrete feature, term, evidence item or realistic limit. D0418 provides a separately filed offer-engine prompt, but it also is not a completed offer.

4. Value-ladder architecture

The source sequence is free, entry, core, premium and ultra. Explain how each step might meet a different level of need or assistance. A ladder should make relevant choices understandable rather than withhold essentials needed to use a prior purchase. Higher lifetime value, lower acquisition cost and lifelong customers are hypotheses to measure, not automatic results of adding tiers. Practice by mapping the customer problem and distinct delivered value at every proposed level.

Module 3: Do

1. Funnel architecture

The source describes a funnel as a guided experience and asks for the next best customer action at each stage. A website can contain that experience; the conceptual distinction is the planned journey, not an absolute separation between funnels and websites. Map how a visitor finds information, evaluates fit and chooses an appropriate next step, including declining or returning later. The promised entire revenue-engine map is not supplied. Practice by identifying one stage's input, useful information, action and handoff.

2. Landing-page copy

The Ogilvy, Kennedy and Caples-labeled introduction lists attention, desire, proof, risk reduction and a clear choice. Align the headline with the page, connect benefits to a real mechanism, supply relevant evidence and explain the exchange and terms. The source's claims that clarity makes people buy and confusion makes everyone leave are oversimplifications. Clarity helps evaluation but cannot create demand or fit on its own. Practice by tracing each claim to its support and each action to an actual destination.

3. Video sales letter and sales letter

The Frey-labeled script promises a twelve-step structure and a complete VSL ready to record but does not include that structure in this file. D0415, separately assigned, supplies the two-page twelve-step template, including its differing step-eight/nine order. Refer to that actual source rather than inventing a missing method here. The claim that the structure sold billions is unsupported. Practice by building an outline from the verified template, then timing and reviewing a draft before calling it record-ready.

4. Email sequences

The source names a Soap Opera Sequence, Daily Story Email and 5-Sequence Close. Those three names are present, but complete messages, sequence steps and timing are not. Do not pretend a named sequence establishes a particular number or order of emails. The greatest-money-maker and unmatchable-relationship claims are also unsupported. Practice by defining audience permission, purpose, useful content and a relevant next step for an email, then locate the actual assigned sequence sources before claiming full implementation.

Module 4: Scale

1. Organic content workflow

The script emphasizes velocity and audience resonance and claims one idea can become thirty to fifty weekly pieces through a RISER Content Engine. No complete engine, capacity analysis or performance evidence is attached. Practice by adapting one evidence-backed source to appropriate formats, preserving meaning and checking audience usefulness. Thirty to fifty is the source's proposed output range, not a requirement to publish duplicates or a guarantee of traction.

2. Paid advertising

The four named deliverables are ad angles, creatives, a minimum viable test and a scaling sequence. A suitable offer matters, but it does not by itself make ads work; audience, message, measurement, costs and delivery also matter. No spend level, campaign configuration or validated scale rule is provided. Practice by writing a test hypothesis, evidence requirements and stop conditions before considering an actual campaign. This curriculum review does not buy ads.

3. Partnerships and affiliates

The source contrasts one operator with a hundred partners as a distribution metaphor. Define partner relevance, the customer benefit, responsibilities and how any compensation or attribution would be handled. More partners do not automatically create a movement or successful distribution. The source contains no partner agreements or outreach plan. Practice by drafting an internal partner-fit brief, not sending messages or enrolling affiliates.

4. Automation, systems and KPIs

The script names tracking, dashboards, Make.com workflows and a 120-day execution plan. Those are proposed assets, not an existing operating system supplied by the file. Systems can make work more repeatable, but scaling is not inevitable. Practice by mapping one process's owner, input, output, success measure, exceptions and human review before automating it. Keep the source's 120-day label distinct from other course plans that use ninety days.

Module 5: Legacy

1. Movement mechanics

The five named elements are an enemy, language, rituals, promise and doctrine. Interpret the enemy as a problem or unhelpful practice to address, not a group of people to vilify. Define shared language, useful repeated activities, a truthful promise and principles open to evidence and revision. No finished movement identity is attached. Practice by writing a participation standard that supports members' progress and choice.

2. Brand language

The script connects words, identity, culture and loyalty. Language can support shared understanding, but that chain is not a guarantee of loyalty. Define terms consistently, explain them plainly and avoid making jargon a barrier to participation. Practice by writing a short glossary with examples of appropriate use and checking whether a newcomer understands it.

3. Licensing and certification

The source proposes documenting frameworks as licensable intellectual property so others can use them. Documentation alone does not establish ownership, transfer rights or create an accredited certification. Identify the actual materials, rights, standards, permitted uses and review process before offering such a program. No license agreement or certification specification is supplied. Practice by making an internal inventory of material and unresolved rights questions, without granting a license.

4. The Founder's Codex

The closing script names teachings, frameworks, story and doctrine as a body of work intended to outlast its founder. Treat immortality as metaphor, not a promise. Record sources, version history, explanations and stewardship so others can understand and maintain the material. The actual Codex or succession plan is not included. Practice by outlining how one framework could be preserved, reviewed and taught responsibly.

Bring the five modules together

The pack moves from understanding a buyer to building an offer, explaining it, distributing it and preserving the work. Retain its Brunson and Hormozi themes while separating supported mechanisms from promotional absolutes. The file's other author labels are source attributions, not verified endorsements or exact quotations. Submit a twenty-topic map with a specific next artifact and evidence gap for each. Completing that map does not mean twenty promised systems have been built.

Sources and resources

- Complete assigned twenty-script pack. - D0415: actual twelve-step PDF and D0418: offer-engine prompt. - Acquisition.com value-equation checklist and ClickFunnels value-ladder reference. - Make: named automation platform, not a deployed RISER workflow. - FTC advertising basics and RISER NATION CORP.

Assigned source links

D0416 original source 1

Complete returned native document text

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.”**
Complete local source copy including original filing metadata and formatting

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.”**
________________

Use concessions to address a specific buying obstacle

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome

Distinguish all five concession types and evaluate the cost and conditions of a proposed allowance. The source defines a concession as a discount, benefit or special allowance offered to support a purchase, agreement or continuing relationship. Better conversion and goodwill are intended effects, not assured outcomes.

Compare the five types

A price concession reduces what the customer pays or bears. The source illustrates it with a real-estate agent offering to cover closing costs. Treat that as an example category, not advice or confirmation that a particular agent can make that offer.

A product concession adds goods or services without an additional charge. Its example is a website audit included with a paid SEO package. Clarify the audit's scope and whether it solves a relevant customer problem rather than adding something merely to inflate perceived value.

A time-based concession offers a benefit during a defined period. The example is a gym offering three free months for signing up that day. State actual eligibility, ongoing charges and any genuine deadline; a sample sentence is not an active promotion.

A contractual concession changes terms, such as a SaaS provider allowing monthly rather than annual commitment. Explain the actual payment schedule, cancellation terms and any resulting price difference. Flexibility can reduce commitment burden but may change delivery economics.

A service concession changes support or service charges. The source's moving-company example waives packing fees when booking within 24 hours. Identify what work is included and the real timing condition. Categories can overlap: waiving a fee also affects price, while its deadline affects timing.

Read the market examples as examples

The document names an Amazon Prime 30-day trial, dealer cash rebates or zero-percent financing, and real-estate commission reductions. These are the source's illustrative examples, not verified current offers for every customer, location or account. Trial eligibility, financing qualification and negotiated terms vary; no present availability or specific transaction advice is established by this lesson.

Evaluate conversion, friction and goodwill

The source gives three reasons to use concessions: encouraging acceptance through added value, reducing objections about price or commitment or timing, and building goodwill through a relevant accommodation. Examine the actual objection before choosing a concession. Extra value that the customer does not need can add cost without addressing the problem, while an unsustainable discount can undermine delivery.

As authored practice, document the obstacle, concession type, customer benefit, provider cost, eligibility, expiry if any and how success will be assessed. Compare an allowance with improving the core offer itself. Use Hormozi's value levers to consider time, effort and supported confidence, and a Brunson-style offer explanation to make the terms easy to understand. Do not use fabricated scarcity or call an ordinary included feature a special gift.

The assigned source provides definitions and examples, not approved prices, contracts or a concession policy. Submit one proposed concession with its assumptions and conditions; no discount, outreach or agreement is executed by this lesson.

Sources and resources

- Complete assigned concession guide. - Acquisition.com value-equation checklist. - ClickFunnels value ladder. - FTC advertising basics and RISER NATION CORP.

Assigned source links

D0417 original source 1

Complete returned native document text

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

📌 Definition of a Concession in Business & Marketing
A concession refers to any discount, benefit, or special allowance a business offers to persuade a customer to make a purchase, complete a deal, or continue a relationship. Concessions help overcome objections, build goodwill, and increase conversion rates.

🔹 Types of Concessions in Business & Marketing
1️⃣ 💰 Price Concession (Discounts & Promotions)
Lowering the price to close a deal.
Example: A real estate agent offers to cover closing costs for a homebuyer.
2️⃣ 🎁 Product Concession (Freebies & Extras)
Offering additional products/services at no extra cost.
Example: A digital marketer includes a free website audit with a paid SEO package.
3️⃣ 🕒 Time-Based Concession (Limited-Time Offers)
Giving a benefit for a short period to drive urgency.
Example: A gym offers "Sign up today and get 3 months free!"
4️⃣ 📜 Contractual Concession (Flexible Terms)
Adjusting payment plans or contract terms to accommodate customers.
Example: A SaaS company allows month-to-month billing instead of annual contracts.
5️⃣ 🎟️ Service Concession (Better Support & Perks)
Providing additional services to improve customer satisfaction.
Example: A moving company waives packing fees for customers who book within 24 hours.

🔹 Real-World Example of a Concession in Marketing
✅ Amazon Prime offers a free 30-day trial (a concession) to encourage users to subscribe and stay long-term.
✅ Car Dealerships often provide cash rebates or 0% financing to convince buyers to purchase sooner.
✅ Real Estate Agents may reduce commission fees to secure high-value clients.

🚀 Why Use Concessions?
✔ Increases Conversions – Customers are more likely to say “yes” when they get extra value.
✔ Removes Friction – Helps overcome objections like price, commitment, or timing.
✔ Builds Goodwill & Loyalty – Makes customers feel like they’re getting a personalized deal.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1R_q1EBAga911BegevABugg20ApqvoUXkkibnsBElrc0/edit?usp=drivesdk"
drive_file_id: "1R_q1EBAga911BegevABugg20ApqvoUXkkibnsBElrc0"
created: "2025-04-02T23:07:20.760Z"
modified: "2026-06-04T15:43:47.419Z"
---

# 📌 Definition of a Concession in Business & Marketing

📌 Definition of a Concession in Business & Marketing
A concession refers to any discount, benefit, or special allowance a business offers to persuade a customer to make a purchase, complete a deal, or continue a relationship. Concessions help overcome objections, build goodwill, and increase conversion rates.
________________


🔹 Types of Concessions in Business & Marketing
1️⃣ 💰 Price Concession (Discounts & Promotions)
* Lowering the price to close a deal.
* Example: A real estate agent offers to cover closing costs for a homebuyer.
2️⃣ 🎁 Product Concession (Freebies & Extras)
* Offering additional products/services at no extra cost.
* Example: A digital marketer includes a free website audit with a paid SEO package.
3️⃣ 🕒 Time-Based Concession (Limited-Time Offers)
* Giving a benefit for a short period to drive urgency.
* Example: A gym offers "Sign up today and get 3 months free!"
4️⃣ 📜 Contractual Concession (Flexible Terms)
* Adjusting payment plans or contract terms to accommodate customers.
* Example: A SaaS company allows month-to-month billing instead of annual contracts.
5️⃣ 🎟️ Service Concession (Better Support & Perks)
* Providing additional services to improve customer satisfaction.
* Example: A moving company waives packing fees for customers who book within 24 hours.
________________


🔹 Real-World Example of a Concession in Marketing
✅ Amazon Prime offers a free 30-day trial (a concession) to encourage users to subscribe and stay long-term.
✅ Car Dealerships often provide cash rebates or 0% financing to convince buyers to purchase sooner.
✅ Real Estate Agents may reduce commission fees to secure high-value clients.
________________


🚀 Why Use Concessions?
✔ Increases Conversions – Customers are more likely to say “yes” when they get extra value.
✔ Removes Friction – Helps overcome objections like price, commitment, or timing.
✔ Builds Goodwill & Loyalty – Makes customers feel like they’re getting a personalized deal.

Understand the ten-phase Irresistible Offer Engine

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source identity

Explain every phase, output and correction rule in the assigned version 2.0 Elite Offer Architect prompt. The source labels itself a locked master owned by Riser Nation and invokes Mark Joyner's principles. These labels describe the source; they do not create an active system role, establish endorsement or authorize executing its commands.

The prompt accepts ideas, links, image descriptions, documents, transcripts, keywords, markets, niches, products or competitor material. It aims to strengthen value and believability rather than rely on price cuts, and to align logic and emotion. Its promise of turning any input into an inevitable, scalable, high-return offer is not a demonstrated capability. Weak input creates uncertainty; refining an idea does not create missing evidence.

Phase 1: strategic diagnosis

Answer all eight questions: what is sold; who is the highest-value buyer; what problem is solved; what pain is reduced; what aspiration is served; what measurable outcome is intended; what emotional concern is relevant; and what competitive alternatives exist. The instruction to infer strong positioning when facts are unclear must produce labeled hypotheses, not fabricated research, buyer insecurities or outcome evidence.

Phase 2: four buyer questions

First explain concretely what is being sold. Second explain how much it costs: price or a proposed tier, value-to-cost comparison, the supported cost of not choosing it and opportunity cost. Do not assume declining this particular offer necessarily causes loss.

Third explain why the buyer should believe the claims. The source's seven-part believability stack includes authority markers, proof, a logical explanation, structural rationale, risk reversal, social validation and transparency. Identify what evidence exists for each and leave missing proof blank.

Fourth explain what the buyer receives through eight benefit lenses: functional benefit, emotional benefit, identity or status, risk reduction, time gain, potential financial gain, pain avoided and longer-term transformation. These are categories to investigate, not eight outcomes automatically delivered by every offer.

Phase 3: examine return

Assess tangible return, intangible return, speed, magnitude, probability, loss avoided and possible longer-term compounding. Define assumptions and uncertainty. A time-saving estimate, an emotional benefit and projected revenue are different kinds of value and should not be added as if all were verified cash returns. The prompt says to redesign when return is not obvious; that means revisiting scope or evidence rather than inventing a high ROI number.

Phase 4: create seven touchstone candidates

The source requests seven short offer phrases. It gives eight criteria: shortness, emotional relevance, an immediate value signal, a hint at return, curiosity, memorability, avoidance of weak hype and avoidance of price emphasis unless strategically needed. For each candidate, identify the intended emotion and embedded logical reassurance.

These are messaging hypotheses. Test whether buyers understand the real exchange and whether the phrase accurately describes it. A touchstone should not imply results, authority or certainty the offer cannot support. This lesson explains the requested seven variants; no actual business facts or finished variants are supplied in the source.

Phase 5: build believability

Review eight elements: credibility anchors, proof placement, why the offer exists, a logical pricing explanation, risk reversal, qualification signals, authority positioning and factors that build trust. Explain unusual value with a truthful reason, not an invented backstory. If the offer sounds implausible, revise unsupported claims or the offer itself; saying why it is not too good to be true does not make it so.

This phase relates directly to the still-empty D0414 reason-why document. A prompt requesting that output is not the completed output. Likewise, the missing D0408 master offer and D0409 summary are not filled merely because this engine is available.

Phase 6: connect logic and emotion

Identify the emotional driver, logical justification, how they reinforce each other and what could fail if either were missing. The source attributes an emotion-first axiom to Joyner. Treat it as the prompt's attribution, not a verified quotation or universal account of all buying decisions. Relevant emotion and practical reasoning can both matter, and neither removes the need for evidence.

Phase 7: assess long-term viability

Answer seven questions: would customers feel the purchase was a good decision; buy again; recommend it; experience few reasons for refunds; contribute to a stronger reputation; be served ethically as volume grows; and receive continuing value that supports repeat prosperity? These are design questions. No refund rate, referral rate or future reputation result is supplied. A negative or unknown answer should lead to a specific research or delivery improvement, not be forced positive.

Phase 8: improve the exchange

Consider all eight intensifiers: useful bonuses, faster delivery, greater convenience, access, appropriate exclusivity, genuine scarcity, refined guarantees and reduced delivery delay. Speed enhancement and delivery compression overlap but can concern different steps; specify which step changes. The source explicitly rejects fake scarcity and manipulation. Improvements need to preserve quality, transparent scope and sustainable delivery, not simply add more claims.

Phase 9: position the offer on the source continuum

The five labels are commodity, value, premium, authority and dominance offer. Explain why the proposed offer fits a label and what a next improvement might involve. These are source-defined positioning labels without formal scoring thresholds, not objective market rankings. Naming an offer dominant does not establish market power, uniqueness or customer preference.

Phase 10: assemble all fourteen outputs

The final output set includes offer headline, primary touchstone, core promise, benefit breakdown, ROI summary, believability stack, logical justification, emotional hook, risk reversal and intensifiers. It also requests a thirty-second pitch, ten-second pitch, three-second pitch and three-second sell-yourself version. Keep the underlying facts consistent across lengths and read aloud to check timing; the prompt supplies no word limits or actual recordings.

Each output should mark unsupported assumptions and unresolved inputs. A short pitch cannot omit material conditions in the complete offer. These requested deliverables are not already generated assets.

Apply the seven correction rules

Reconsider an offer if it relies mainly on price cuts, lacks measurable return, sounds generic, has weak believability, emphasizes benefits without proof, lacks relevant emotional meaning or appears unable to remain viable for five years. Five-year viability is a planning scenario, not a forecast that can be guaranteed from a prompt. A product with important nonfinancial benefits may require a clear outcome measure rather than a fabricated monetary ROI.

Optional advanced outputs

The source offers nine additional deliverables only when requested: competitor-disruption strategy, blue-ocean positioning angle, lifetime-value improvement plan, offer-stacking ladder, continuity model, high-ticket version, authority-scaling roadmap, testing framework and A/B touchstone variants. Explain their relationship to the core offer before adding scope. The prompt's optional list does not require this curriculum review to execute a campaign, scrape a competitor or invent a revenue model.

Connect the educational themes and finish

The prompt's final desired reactions concern sense, fit, safety, value and reluctance to miss the exchange. Reframe “engineering inevitability” as making a well-supported decision easier to evaluate. Buyers may reasonably decline. Connect the engine's value analysis to Hormozi's four levers and its presentation to Brunson's story, offer and value-ladder themes, while keeping the source's Joyner attribution distinct from authored applications.

Submit a ten-phase analysis plan, all fourteen output slots, evidence requirements and unresolved inputs. The full prompt stays in the appendix, including its optional mode and correction rules. No actual offer-engine execution or populated missing output is claimed.

Sources and resources

- Complete assigned Irresistible Offer Engine. - Missing output records: one-sentence offer, reason-why, master offer, and offer summary. - Acquisition.com value-equation checklist and ClickFunnels value-ladder reference. - FTC advertising basics and RISER NATION CORP.

Assigned source links

D0418 original source 1

Complete returned native document text

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.”
Complete local source copy including original filing metadata and formatting

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.”
________________

Distinguish DIY, DWY, DFY and licensed delivery

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome

Explain the four delivery tiers named in the assigned offer-wall outline and identify what remains undefined. This is a short scope list, not a complete product catalog, contract or license grant.

DIY, commonly do it yourself, lists templates, compilers and a Control Tower. The source does not define those compilers or supply a Control Tower system. Treat this as a tools-led proposal in which the buyer would perform the implementation; do not claim the assets are already accessible.

DWY, commonly done with you, lists setup, branch priority and iteration reviews. It suggests assisted implementation, but branch priority is not defined, and no review frequency, response time or division of work is specified. Those terms need clarification before a buyer can assess the service.

DFY, commonly done for you, says the provider builds a site, a content batch, a course module and reporting. All four deliverable types belong in the scope explanation. The source gives no quantities beyond those categories, acceptance criteria, revision limits, delivery schedule or ongoing maintenance promise. It is not authorization to purchase or commission those services.

License lists a white-label operating system, updates and certification. These labels describe an intended tier; they do not supply rights to rebrand, redistribute or sublicense anything. No actual license, IP ownership evidence, update period or certification standard accompanies the outline. Do not imply external accreditation.

Compare the exchange

As authored practice, compare each tier's buyer work, provider work, included assets, support and unresolved terms. Use Hormozi's effort, time and likelihood questions to examine the tradeoff, and a Brunson-style value ladder to explain an appropriate next step. A more assisted tier is not automatically better for every buyer. The original contains no pricing, profitability model or validated ascension path.

Submit a four-tier comparison that preserves every listed component and flags undefined terms. Keep the full original in the appendix; do not fill unknown scope with invented product specifications.

Sources and resources

- Complete assigned offer-wall outline. - Acquisition.com value-equation checklist. - ClickFunnels value-ladder reference and RISER NATION CORP.

Assigned source links

D0419 original source 1

Complete returned native document text

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

01_OFFER_WALL — DIY / DWY / DFY / License

DIY
- Templates + compilers + Control Tower

DWY
- Setup + branch priority + iteration reviews

DFY
- We build site + content batch + course module + reporting

License
- White-label OS + updates + certification
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1qhZA9rRw_kDiOxk3F3E40BHi8fwQfTLUt5ovuxbbCuc/edit?usp=drivesdk"
drive_file_id: "1qhZA9rRw_kDiOxk3F3E40BHi8fwQfTLUt5ovuxbbCuc"
created: "2025-12-20T16:42:10.134Z"
modified: "2026-06-04T15:53:30.981Z"
---

# 01_OFFER_WALL__DIY_DWY_DFY_License

01_OFFER_WALL — DIY / DWY / DFY / License


DIY
- Templates + compilers + Control Tower


DWY
- Setup + branch priority + iteration reviews


DFY
- We build site + content batch + course module + reporting


License
- White-label OS + updates + certification

Turn a short offer-wall statement into a clear scope discussion

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Explain the offer category, proposed mechanism, asset-building promise and audience in the four-line source. Separate the words actually supplied from the product specifications still needed.

Name what the buyer is being offered

The title is Offer Wall Copy. Its first line names a Vibe Website + Course Builder. That joins two deliverable categories: a website and a course-building capability. It does not tell us whether the customer receives software, templates, a service, training or some combination. When reading this aloud to a prospective customer, introduce it as the source's proposed offering and then ask what the provider and customer would each build. Do not turn the word builder into a claim that an application has already been deployed.

Explain the proposed mechanism without inventing its contents

The next line says Reservation Doctrine™ powered. That names a proposed mechanism but supplies no doctrine, instructions, reservation process or proof that it powers the offer. The trademark styling is part of the source; it does not establish registration. An authored RISER application is to leave a clearly identified mechanism-definition field in the offer brief until the actual explanation and supporting material are available. A distinctive name can help organize a Brunson-style offer story, but the name alone cannot explain why the product works.

Teach the asset-building distinction

Compounding assets, not one-off builds is the third line. Read it as a positioning intention: build assets that can be reused, improved and connected to later work. As an authored example, a course outline might inform lesson pages, later revisions and supporting resources. The source does not supply that workflow or demonstrate financial compounding. Before making a customer promise, define the reusable outputs, ownership, maintenance and how improvement will be evaluated. Do not substitute an investment-return claim for this short marketing statement.

Identify the audience and the unanswered questions

The final line addresses operators rather than template hunters. It positions the offer for people intending to implement and operate something. It does not establish formal eligibility criteria or show that template users cannot benefit. Ask what operating responsibility the buyer will accept and what support is actually included. Hormozi's value-equation questions help assess the intended result, confidence, time and effort; the source contains no measurements for those factors.

For your practice deliverable, preserve all four lines and write one plain-language explanation beside each. Mark the delivery model, doctrine, asset inventory, evidence, price, rights, support and terms as unresolved where the source is silent. This completes teaching of the available brief; it does not create the missing product system. The complete original remains in the lesson appendix.

Sources and resources

- Assigned Offer Wall Copy. - Acquisition.com value-equation checklist. - ClickFunnels value-ladder reference and RISER NATION CORP.

Assigned source links

D0420 original source 1

Complete returned native document text

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

OFFER WALL COPY

Vibe Website + Course Builder
Reservation Doctrine™ powered.

Compounding assets, not one-off builds.
For operators, not template hunters.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1Zba4vQKa_GAn5dh6e9-FJL9W7sdP16jDzOE3N6fz0jU/edit?usp=drivesdk"
drive_file_id: "1Zba4vQKa_GAn5dh6e9-FJL9W7sdP16jDzOE3N6fz0jU"
created: "2025-12-20T00:52:51.541Z"
modified: "2026-06-04T16:57:42.712Z"
---

# 02 – Offer Wall Copy (Blunt + Premium)

OFFER WALL COPY


Vibe Website + Course Builder
Reservation Doctrine™ powered.


Compounding assets, not one-off builds.
For operators, not template hunters.

Answer the buyer's questions through a complete email sequence

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Teach the assigned six-email script, its separate six-question planning checklist, and all five funnels in its linked document. Preserve their different orders and purposes. These are campaign-writing templates; the lesson does not send messages or claim that a campaign is already operating.

Understand the two uses of Who, What, Where, When, Why and How

In the main script, Who introduces the seller. In the final planning checklist, Who identifies the audience. The main sequence runs Who, What, Where, When, Why, How; the checklist runs Who, What, Why, When, Where, How. In the linked funnel examples, How usually comes third, and several combine When and Where. Each version answers useful questions, but they are not one rigid schedule. Select the version matching the buyer's current information need.

Email one: introduce the people and purpose

The first subject introduces who the company is and why it wants to help. The body greets the recipient by first name, identifies the founder, company and team, describes the product or service briefly, and states the problem or goal it addresses. Explain the company's actual mission rather than inventing a founder story or universal entitlement claim. The closing previews further information over the next few days and specifically promises a What email tomorrow, then signs with the sender's name.

When adapting the script, make its timing language match the actual sequence. A subscriber joining at a different time should not receive a false yesterday reference. The source supplies placeholders, not real company credentials, a sender identity or a delivery schedule.

Email two: explain the offer and three benefits

The second subject explains what the company does and how it can help. It reconnects to yesterday's introduction, describes the product or service in detail, and supplies three distinct benefit slots. The first addresses the specific problem; the second may save time, money or effort; the third names a distinctive feature or advantage. Explain each with relevant evidence and scope. A claim of perfect fit is stronger than the source can support. Close by previewing where the reader can access the offer tomorrow and include the sender sign-off.

Email three: show where to explore and act

The third subject emphasizes access to benefits. Give a real website destination and explain what the visitor will find: resources, product pages, testimonials or other relevant material. Describe any actual discount, special offer or free trial and its terms. The source includes those as options; it does not provide an active trial or approved promotion. The closing encourages a visit and previews the next timing message. The destination should support the promise made in the email rather than forcing the reader to search for an unrelated page.

Email four: explain the timing honestly

The fourth subject asks when to act and suggests now. Its body connects starting sooner to results and introduces a limited-time discount, promotion or bonus. Adapt this to a real schedule and a supported expectation of progress. Starting today does not guarantee immediate results. Explain what extra value is available, who qualifies and when availability changes. Provide the action link, then preview tomorrow's Why message. A generic urgency phrase is not a substitute for an actual deadline.

Email five: answer Why Us, Why Now and Why You

The source's subject suggests this could be the best decision the reader has made. Treat that as promotional wording to review, not a factual conclusion. Why Us asks for years of experience and specific results; fill these only with verified information. Why Now connects the current offer and price to timing; do not promise everything needed for immediate results when delivery depends on work or conditions. Why You reconnects the offer to relevant benefits such as peace of mind, success or growth. Calling a purchase an investment in the future does not make it a financial return guarantee. End by previewing the practical How email.

Email six: make the next step usable

The final subject names how to start with the product or service today. Briefly recap the previous five messages, then teach the four steps: visit the website, choose the suitable plan or product, complete the sign-up or order, and begin using what is available. The source labels the last step immediate benefit; distinguish immediate access from a result requiring implementation. Include a reply-for-help route, an accurate response expectation, the closing invitation, action link and sender name. No plan, checkout or support response time is supplied in the document itself.

Apply the separate campaign-planning checklist

Who defines the intended list segment, including relevant demographics, interests, pain points and preferences. What defines the message and its value: an offer, useful information or exclusive access. Why states the benefit, such as saving money, solving a problem or learning. When aligns a promotion, event or educational message with an appropriate time. Where is the prominent next action—click, purchase, register or contact. How chooses suitable copy, visuals, interactive elements or personalization. These planning decisions should support the six-message sequence rather than becoming extra claims about the recipient.

Linked funnel one: product launch

The launch version uses six emails in the order Who, What, How, When, Where, Why. Who identifies the product and its intended buyer, such as a busy professional, and previews the product details. What introduces its category and three key features, then previews a demonstration. How explains a three-step use process or use case and previews the launch date. When names the actual launch date, availability and any early-bird offer, then points toward purchasing information. Where gives the actual purchase channel, such as the website, and any real free-shipping period. Its CTA asks for the order. Why reinforces differentiators and genuine beta-tester evidence, ending with a purchase CTA. A later objection-handling follow-up offers a ten-percent discount code in the example. That percentage and the testimonials are placeholders, not active RISER terms.

Notice the changing continuation requests: learn the features, see how it works, learn the date, find the location, then decide. The sequence should deliver what each previous message promised. Do not withhold essential buying information from someone ready to evaluate the offer merely to force six opens.

Linked funnel two: education

This version uses five emails. Who identifies the profession or role and the relevant needs. What explains the category and three benefits. How gives an in-depth guide, three-step example or video tutorial. The fourth combines When and Where, specifying availability and an access link. Why closes with differentiators and actual customer evidence. Each early CTA previews the next useful explanation, and the final CTA asks for the purchase. The follow-up addresses remaining doubts with a fifteen-percent example incentive. Teach the information before asking for a decision; neither the source's hundreds-of-users claim nor the proposed discount is established fact.

Linked funnel three: webinar registration

Who identifies the role and desired learning goal. What names the three sample topic slots and takeaways. How explains format, duration and interaction; the source uses a sixty-minute live session with Q&A as an example. When and Where provide the date, time, platform and registration link. Why explains the relevant learning benefits and directs the reader to register. Reminders serve registrants with access and timing, and can separately invite suitable nonregistrants. Match each recipient's status so an attendee is not repeatedly asked to register. The sample tomorrow reminder and limited-spaces claim must reflect the actual event. No live event is scheduled by this lesson.

Linked funnel four: high-ticket service

The five-email path moves toward a consultation. Who identifies the ideal client and problem. What explains the service's benefits and distinct support. How covers the process, timeline, tools and methods. When and Where explain client availability for a named month and provide the consultation destination. Why uses relevant, verified cases or testimonials to support fit. The follow-up addresses remaining objections with an optional subscriber incentive. The appropriate CTA is booking a discussion, not pretending that a complex service can always be responsibly sold with an immediate purchase button. Verify whether a free consultation and capacity actually exist.

Linked funnel five: lead magnet to paid offer

The first email thanks the person for requesting the free resource and identifies who the related paid offer helps. What explains three included features and their benefits. How explains the delivery process or method. When and Where identify availability, purchase destination and any genuine bonus. Why reinforces the offer with supported customer evidence. Early messages preview the next explanation; the later CTA invites purchase. A final objection-handling email uses a ten-percent discount example. Deliver the requested resource and distinguish it from the optional paid product. The source's because-it-works assertion is not proof, and an incentive is not required merely because it appears in the template.

Put the sequence into a responsible offer journey

A Brunson-style progression connects an initial useful interaction to an appropriate next offer. Hormozi's value-equation questions help test whether each email clarifies the result, confidence, timing or effort. These six-question templates are supplied by the documents, not presented as a verified proprietary Brunson or Hormozi framework.

For practice, choose one of the five funnel purposes and write the complete sequence, with subject, greeting, body, evidence, accurate timing, CTA and sign-off for each message. Include a status-aware follow-up and identify every missing product fact, testimonial, price, incentive or schedule. Preserve the original six-email script and full linked funnel text in the appendix. Future operational email use requires the actual list, permissions, sender setup and applicable requirements to be checked; this exercise remains drafting only.

Sources and resources

- Assigned 5 W's and H script and planning checklist. - Linked five email funnel types. - Acquisition.com value-equation checklist, ClickFunnels value-ladder reference, and RISER NATION CORP.

Assigned source links

D0421 original source 1

Original embedded resource links

Original embedded hyperlink spans:

Complete linked source

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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.
Complete linked native source text; reciprocal references retained

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.

Plan six webinar funnels and distinguish the three 6-P frameworks

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Select among registration, delivery, evergreen, high-ticket, content-driven and multi-part webinar funnels. Teach the stages, timing, proof, offer and follow-up for each. The assigned funnel document and its linked presentation script use different lists under the same 6-P label; preserve all three interpretations.

Define the marketing-mix version

The assigned funnel document uses Product, Price, Place, Promotion, People and Process. Product is the topic and offer; Price explains cost and payment options; Place is where to attend or buy; Promotion communicates benefits and genuine incentives; People covers presenter credibility and audience interaction; Process explains the learning and implementation sequence. The text also uses Pricing and Placement for Price and Place. Its historical explanation of a traditional five-P model is not independently established here. These are the source's planning labels, not a verified Brunson or Hormozi taxonomy.

Funnel one: registration

Build a landing page explaining the topic or product and why it matters to the intended audience. State useful takeaways and any actual attendance resource or bonus, then provide a clear registration action. A revolutionary-tool claim or exclusive-event label needs support; the template itself supplies none.

The pre-webinar emails introduce the presenter and relevant experience, then explain the planned process with the source's three topic slots. Give the date, time and calendar action. Reminders supply the actual access link and platform and explain any early-login advice. Registration, calendar addition and joining are separate actions. Ensure the reader has the information needed for the current action, and do not imply that virtual seats are scarce without a real limit.

Funnel two: webinar delivery

The source budgets five to ten minutes for introduction, thirty to forty-five for main content, ten to fifteen for the pitch and ten to fifteen for Q&A. Together these ranges equal fifty-five to eighty-five minutes before any extra transitions. Use them as a planning example, not a promise that the session lasts an hour.

In the introduction, identify the product, the buyer problem and the presenter's actual relevant experience. In the main content, teach the process; the sample five-step process is a placeholder, not five supplied steps. Show how a real product feature can help with a particular step instead of replacing the educational segment with unsupported superiority claims. During the pitch, explain the price, inclusions and genuine bonuses. The source's twenty-four-hour bonus is an example requiring a real expiry and terms.

Use Q&A to address the question asked and show how the process fits the buyer's circumstances. A claim that the process works best only with this product needs evidence and may be inappropriate where alternatives exist. Give the chat link or website for the purchase. The follow-up recaps learning and any remaining offer period. Do not describe an offer as available only during the webinar and then routinely sell it afterward under the same terms without explaining the actual availability.

Funnel three: evergreen webinar

The registration page explains the learning topic and any genuine resource supplied for registering. Pre-webinar emails introduce the presenter, relevant evidence and three topic placeholders. The automated presentation introduces the product and teaches the process; the five-step example still needs actual content. Clearly identify the recorded or automated format rather than manufacturing a live audience.

Present pricing and any real time-sensitive benefit, then show verified cases, testimonials or additional resources where relevant. Direct the viewer to a usable purchase page. Follow-up emails recap the process and, in the source's example, describe a forty-eight-hour offer. Define when that period starts, its timezone and what expires. An automated deadline can be legitimate if it is consistently enforced and accurately described. A recording and a countdown do not themselves establish either credibility or urgency.

Funnel four: high-ticket webinar

The registration page explains the high-value topic and an actual consultation or downloadable-resource incentive. The pre-sequence builds context through the presenter's story, experience and relevant client cases, then supplies a roadmap. The presentation teaches a detailed process or case study showing the product's role and the conditions under which results occurred.

The pitch explains price, payment plans or financing if actually offered, and what each option requires. No specific financing terms are supplied. The sample bonus includes a one-to-one presenter session; confirm capacity, length and scope before including it. Q&A addresses substantial concerns and connects the process to the offer. Later emails address common objections with supported cases and invite a consultation or another appropriate purchase step. Claims that the process is proven for everyone or guarantees an outcome exceed the source evidence.

Funnel five: content-driven webinar

The registration page leads with useful education, such as the source's ten-strategy example, and a relevant eBook or cheat sheet if available. Pre-webinar emails explain the presenter's actual credentials and learning roadmap. The main presentation provides usable insights before the sale; neither the ten strategies nor the sample four-step implementation process is supplied in this document.

Show where a product feature may help, including the source's illustrative placement in step three, without implying the audience cannot use any lesson independently. After teaching, transition openly to the price and any real bonus resources or support. Q&A clarifies the process and addresses remaining uncertainty. Follow-up sends the recap and accurate offer deadline. The content-first emphasis distinguishes this version from a primarily promotional presentation, while still making the commercial purpose understandable.

Funnel six: multi-part series

The registration page describes a three-part series and any actual full-series resource. The emails introduce the panel or presenters and map topic one, topic two and topic three. Explain how each session builds on the previous one. In sessions one and two, teach the foundation and then the more advanced application, previewing the next session accurately and explaining the product only where useful.

In session three, connect the completed process to the offer, present price and any real series-attendee bonus, and answer final questions. The source calls the product essential or best in several examples; assess whether those assertions are supportable rather than repeating them automatically. Follow-up recaps each session and states the actual end of the offer. Supply the missing session content and access arrangements before treating this outline as an operational series.

Linked script: Problem, Promise, Product, Proof, Proposition and Push

The linked document uses a different six-part sales sequence. Open with a welcome, presenter identity and relevant topic. For Problem, show a visual representation of a real audience difficulty, acknowledge prior unsuccessful attempts and express informed empathy. Do not invent customer frustration to make the problem larger.

For Promise, state what the session will teach and which actionable steps the attendee can take. A useful learning promise is different from guaranteed business results or freedom from all stress. For Product, introduce its category, relevant features and benefits and show a diagram or live demonstration if available. For Proof, present genuine, permissioned testimonials, cases or before/after evidence with appropriate context. The quoted customer in the source is a placeholder, not an actual endorsement or track record.

For Proposition, explain the full contents—modules, support, bonuses and any other resources—and the price. The source's $X value and $Y selling price are blank variables. Do not create comparison values without support. For Push, state the next action and any true time or capacity limit. The source suggests limited spots, expiring bonuses and countdowns; use only the limit that actually applies. Close with the purchase destination, thanks and a legitimate help route, allowing an informed decision rather than pressuring a buyer who is unsuitable.

Linked operational checklist: a third meaning

The same linked document ends with Preparation, Promotion, Presentation, Pitch, Proof and Follow-up. Follow-up does not begin with P; preserve the source's list rather than silently inventing a sixth P. Preparation covers content, slides, introduction/main/Q&A flow and equipment tests. Promotion covers email, social media, website, graphics, videos and copy, with potential expert or influencer partnerships. No partnership is established by the outline.

Presentation covers the opening, useful insights, visuals, cases, examples, audience questions and participation. Pitch explains features, benefits, value and an actual attendee incentive. Proof supplies relevant customer evidence or endorsements. Follow-up thanks attendees, supplies resources or offers, provides a recording to no-shows or a replay to attendees, and proposes continued email, retargeting or personal contact. These are possible campaign actions requiring a real authorized implementation; none is performed by this lesson.

Connect the webinar to the offer system

Use a Brunson-style educational story and offer progression to keep registration, teaching, proof and purchase coherent. Use Hormozi's questions to examine the result, likelihood, time and effort expressed in the offer. The source frameworks remain distinct from those broader educational influences.

For practice, choose a funnel, define its audience and format, and write every stage through follow-up. Add the actual topic content, evidence, access details, schedule and offer terms, marking missing items explicitly. Use the three lists for their different purposes: marketing-mix planning, sales-message order and production workflow. Preserve the full assigned and linked originals in the appendix.

Sources and resources

- Assigned six webinar funnel types. - Linked six-P presentation script and operational checklist. - Acquisition.com value-equation checklist, ClickFunnels value-ladder reference, and RISER NATION CORP.

Assigned source links

D0422 original source 1

Original embedded resource links

Original embedded hyperlink spans:

Complete linked source

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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.
Complete linked native source text; reciprocal references retained

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.

Teach the 6-P presentation script and its six linked webinar funnels

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Teach the assigned Problem, Promise, Product, Proof, Proposition and Push script, its separate operational checklist, and all six funnel types in its linked document. The paired documents use three different lists under the same 6-P label; preserve all three interpretations. The full shared teaching below covers each source, regardless of which document is the starting assignment.

Define the marketing-mix version

The assigned funnel document uses Product, Price, Place, Promotion, People and Process. Product is the topic and offer; Price explains cost and payment options; Place is where to attend or buy; Promotion communicates benefits and genuine incentives; People covers presenter credibility and audience interaction; Process explains the learning and implementation sequence. The text also uses Pricing and Placement for Price and Place. Its historical explanation of a traditional five-P model is not independently established here. These are the source's planning labels, not a verified Brunson or Hormozi taxonomy.

Funnel one: registration

Build a landing page explaining the topic or product and why it matters to the intended audience. State useful takeaways and any actual attendance resource or bonus, then provide a clear registration action. A revolutionary-tool claim or exclusive-event label needs support; the template itself supplies none.

The pre-webinar emails introduce the presenter and relevant experience, then explain the planned process with the source's three topic slots. Give the date, time and calendar action. Reminders supply the actual access link and platform and explain any early-login advice. Registration, calendar addition and joining are separate actions. Ensure the reader has the information needed for the current action, and do not imply that virtual seats are scarce without a real limit.

Funnel two: webinar delivery

The source budgets five to ten minutes for introduction, thirty to forty-five for main content, ten to fifteen for the pitch and ten to fifteen for Q&A. Together these ranges equal fifty-five to eighty-five minutes before any extra transitions. Use them as a planning example, not a promise that the session lasts an hour.

In the introduction, identify the product, the buyer problem and the presenter's actual relevant experience. In the main content, teach the process; the sample five-step process is a placeholder, not five supplied steps. Show how a real product feature can help with a particular step instead of replacing the educational segment with unsupported superiority claims. During the pitch, explain the price, inclusions and genuine bonuses. The source's twenty-four-hour bonus is an example requiring a real expiry and terms.

Use Q&A to address the question asked and show how the process fits the buyer's circumstances. A claim that the process works best only with this product needs evidence and may be inappropriate where alternatives exist. Give the chat link or website for the purchase. The follow-up recaps learning and any remaining offer period. Do not describe an offer as available only during the webinar and then routinely sell it afterward under the same terms without explaining the actual availability.

Funnel three: evergreen webinar

The registration page explains the learning topic and any genuine resource supplied for registering. Pre-webinar emails introduce the presenter, relevant evidence and three topic placeholders. The automated presentation introduces the product and teaches the process; the five-step example still needs actual content. Clearly identify the recorded or automated format rather than manufacturing a live audience.

Present pricing and any real time-sensitive benefit, then show verified cases, testimonials or additional resources where relevant. Direct the viewer to a usable purchase page. Follow-up emails recap the process and, in the source's example, describe a forty-eight-hour offer. Define when that period starts, its timezone and what expires. An automated deadline can be legitimate if it is consistently enforced and accurately described. A recording and a countdown do not themselves establish either credibility or urgency.

Funnel four: high-ticket webinar

The registration page explains the high-value topic and an actual consultation or downloadable-resource incentive. The pre-sequence builds context through the presenter's story, experience and relevant client cases, then supplies a roadmap. The presentation teaches a detailed process or case study showing the product's role and the conditions under which results occurred.

The pitch explains price, payment plans or financing if actually offered, and what each option requires. No specific financing terms are supplied. The sample bonus includes a one-to-one presenter session; confirm capacity, length and scope before including it. Q&A addresses substantial concerns and connects the process to the offer. Later emails address common objections with supported cases and invite a consultation or another appropriate purchase step. Claims that the process is proven for everyone or guarantees an outcome exceed the source evidence.

Funnel five: content-driven webinar

The registration page leads with useful education, such as the source's ten-strategy example, and a relevant eBook or cheat sheet if available. Pre-webinar emails explain the presenter's actual credentials and learning roadmap. The main presentation provides usable insights before the sale; neither the ten strategies nor the sample four-step implementation process is supplied in this document.

Show where a product feature may help, including the source's illustrative placement in step three, without implying the audience cannot use any lesson independently. After teaching, transition openly to the price and any real bonus resources or support. Q&A clarifies the process and addresses remaining uncertainty. Follow-up sends the recap and accurate offer deadline. The content-first emphasis distinguishes this version from a primarily promotional presentation, while still making the commercial purpose understandable.

Funnel six: multi-part series

The registration page describes a three-part series and any actual full-series resource. The emails introduce the panel or presenters and map topic one, topic two and topic three. Explain how each session builds on the previous one. In sessions one and two, teach the foundation and then the more advanced application, previewing the next session accurately and explaining the product only where useful.

In session three, connect the completed process to the offer, present price and any real series-attendee bonus, and answer final questions. The source calls the product essential or best in several examples; assess whether those assertions are supportable rather than repeating them automatically. Follow-up recaps each session and states the actual end of the offer. Supply the missing session content and access arrangements before treating this outline as an operational series.

Assigned script: Problem, Promise, Product, Proof, Proposition and Push

The linked document uses a different six-part sales sequence. Open with a welcome, presenter identity and relevant topic. For Problem, show a visual representation of a real audience difficulty, acknowledge prior unsuccessful attempts and express informed empathy. Do not invent customer frustration to make the problem larger.

For Promise, state what the session will teach and which actionable steps the attendee can take. A useful learning promise is different from guaranteed business results or freedom from all stress. For Product, introduce its category, relevant features and benefits and show a diagram or live demonstration if available. For Proof, present genuine, permissioned testimonials, cases or before/after evidence with appropriate context. The quoted customer in the source is a placeholder, not an actual endorsement or track record.

For Proposition, explain the full contents—modules, support, bonuses and any other resources—and the price. The source's $X value and $Y selling price are blank variables. Do not create comparison values without support. For Push, state the next action and any true time or capacity limit. The source suggests limited spots, expiring bonuses and countdowns; use only the limit that actually applies. Close with the purchase destination, thanks and a legitimate help route, allowing an informed decision rather than pressuring a buyer who is unsuitable.

Assigned operational checklist: a third meaning

The same linked document ends with Preparation, Promotion, Presentation, Pitch, Proof and Follow-up. Follow-up does not begin with P; preserve the source's list rather than silently inventing a sixth P. Preparation covers content, slides, introduction/main/Q&A flow and equipment tests. Promotion covers email, social media, website, graphics, videos and copy, with potential expert or influencer partnerships. No partnership is established by the outline.

Presentation covers the opening, useful insights, visuals, cases, examples, audience questions and participation. Pitch explains features, benefits, value and an actual attendee incentive. Proof supplies relevant customer evidence or endorsements. Follow-up thanks attendees, supplies resources or offers, provides a recording to no-shows or a replay to attendees, and proposes continued email, retargeting or personal contact. These are possible campaign actions requiring a real authorized implementation; none is performed by this lesson.

Connect the webinar to the offer system

Use a Brunson-style educational story and offer progression to keep registration, teaching, proof and purchase coherent. Use Hormozi's questions to examine the result, likelihood, time and effort expressed in the offer. The source frameworks remain distinct from those broader educational influences.

For practice, choose a funnel, define its audience and format, and write every stage through follow-up. Add the actual topic content, evidence, access details, schedule and offer terms, marking missing items explicitly. Use the three lists for their different purposes: marketing-mix planning, sales-message order and production workflow. Preserve the full assigned and linked originals in the appendix.

Sources and resources

- Linked six webinar funnel types. - Assigned six-P presentation script and operational checklist. - Acquisition.com value-equation checklist, ClickFunnels value-ladder reference, and RISER NATION CORP.

Assigned source links

D0423 original source 1

Original embedded resource links

Original embedded hyperlink spans:

Complete linked source

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1V_M10VVNEBUz0VZbj-3J6XKQAvbQ0p3GXoaT9GxzYvA/edit?usp=drivesdk"
drive_file_id: "1V_M10VVNEBUz0VZbj-3J6XKQAvbQ0p3GXoaT9GxzYvA"
created: "2024-04-28T03:44:54.244Z"
modified: "2026-06-04T16:49:50.708Z"
---

# 14.) The 6 P's Approach

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:
1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
Complete linked native source text; reciprocal references retained

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.

Demonstrate the product and connect visible evidence to the offer

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Teach the assigned SHOW demonstration script, its alternate checklist and all five linked demonstration funnels. Explain every interpretation of the acronym and preserve the source's scene directions, proof requirements and calls to action.

Distinguish the three SHOW definitions

The main script uses Show in Action, Highlight Features, Offer Solutions and Win Trust, followed by a separate fifth call-to-action stage. Its final checklist instead uses Set the Stage, Highlight the Features, Offer Benefits and Witness the Results. The linked funnel document uses Set the Stage, Highlight the Features, Offer Solutions and Wrap Up with a Call to Action. These related ideas are not identical lists. Use the main version to explain the demonstration, the checklist to review preparation and evidence, and the linked version to plan the event journey. Do not label one as the definitive Brunson or Hormozi method; these are the assigned sources' terminology.

Open and show the product working

The opening scene places the presenter on a stage or in a well-lit studio with the product visible. Introduce yourself, the product, the intended audience and the specific problem. The source calls the product revolutionary and perfect; replace unsupported superlatives with an accurate description.

In the Show stage, describe what the audience is seeing, then demonstrate the first action step by step. Use close-ups and more than one angle where they help explain the operation. Name the resulting benefit and any conditions needed to reproduce it. A demonstration should make the process observable; saying that something is effortless does not establish that all customers will find it easy.

Highlight features and practical use cases

Show one distinctive feature and explain the benefit it enables. Then demonstrate another feature in a relevant use case. Discuss the different scenarios the source asks you to address, including limits where the feature does not fit. If comparing against a competitor or a common method, identify the actual basis of comparison. The source's best-results-every-time language is unsupported and should not become a claim about RISER NATION or another product.

Offer solutions to the audience's actual problems

Describe a researched frustration, then show the product addressing it. Explain the steps and how the feature may reduce time, effort or confusion. The source includes problem A, problem B and problem C as three placeholders, so choose and demonstrate three relevant problems only when the product and evidence support them. The claim that a problem is permanently over or that results are always quick and reliable is stronger than a single demo can establish.

Win trust through real evidence

The source transitions to reviews, video testimonials and before/after cases, suggesting text overlays for important quotes or results. Its first sample testimonial claims ease of use and strong results. The second describes initial skepticism followed by a fast solution. Both are template quotations, not real customers. Replace them only with genuine, permissioned material and preserve its context. Do not manufacture the number of satisfied customers in the presenter's closing line.

Return to the product for a final demonstration or summary showing what has actually been established. A customer case can help explain an experience without proving everyone will achieve it. Use accurate captions and equivalent explanation so the teaching remains understandable beneath the video.

Give the buyer a clear next step

The fifth main-script stage presents an actual offer, discount or bonus and displays a website, phone number or QR code. Explain the destination and any expiry rather than relying solely on visual scanning. Thank the audience and give an appropriate next action. Do not promise to exceed every expectation or imply that all benefits begin instantly. The source supplies no actual product, price, telephone number, active bonus or testimonial evidence.

Apply the separate four-step preparation checklist

Set the Stage means arranging the space, props and displays and establishing an inviting context. Highlight the Features means explaining capabilities, operation and meaningful differences with clear visuals. Offer Benefits means connecting those functions to needs and expected improvements. Witness the Results means examining actual cases, testimonials or other results. This version emphasizes evidence rather than making W the final purchase instruction; preserve that difference.

Linked funnel one: in-person live demonstration

Promote the event with its location, product relevance and expected experience. Invite an RSVP or registration and describe any real attendee gift. On site, introduce the problem and a truthful relatable story, then demonstrate the features and their problem-solving roles. Give the audience a Q&A opportunity and tailor the answer through an observable example where possible.

Close with the actual event offer and a clear route to the booth, pop-up shop or mobile checkout. Follow-up to interested nonbuyers may recap benefits and, in the source example, extend an offer for twenty-four hours. An extension must be genuine and accurately explained; routinely extending something advertised as absolutely event-only makes the original message misleading. No event or follow-up is activated by this lesson.

Linked funnel two: online live showcase

The source names Facebook Live, Instagram Live or a dedicated webinar platform as possible contexts. Choose the actual platform before promising access. Promotion names the date and learning value and invites registration or a reminder. The introduction explains the problem and a real presenter experience or testimonial. Demonstrate key features live and relate them to practical solutions.

Use chat questions to show relevant use cases and clarify limits. Present a genuine live-attendee offer, then direct viewers to the description link or checkout page. The sample follow-up extends the benefit twenty-four hours; apply the same truthful-availability rule as the in-person event. A feature demonstration does not support the source's blanket guarantee of benefit.

Linked funnel three: formal webinar demonstration

Build a registration page explaining the problem and expected learning, with a simple form and appropriate CTA. Pre-webinar emails set expectations, provide date and time, invite calendar addition and ask attendees to prepare questions. Open with the product purpose and a genuine relevant case or story.

The demonstration examines each feature in detail and shows how it addresses distinct scenarios. Q&A explores specific concerns through explanation or further demonstration. Close with the actual offer and a purchase or consultation destination in chat or on the website. Follow-up addresses remaining objections; the source proposes a forty-eight-hour extension. This version is distinguished by formal registration, preparation emails and a structured presentation rather than assuming every live social broadcast has the same workflow.

Linked funnel four: retail pop-up

Announce the local event through appropriate email, social media or local promotion. Specify whether people should RSVP or can walk in. Welcome attendees, explain the product and share a truthful personal example. Demonstrate the features in realistic scenarios and connect each to an actual problem.

The distinctive step is inviting attendees to try the product themselves and ask how it fits their situation. Explain the conditions for a useful trial rather than assuming all products can be safely handled in the same way. Provide a sales table or mobile checkout and clear event terms. The source's post-event example thanks attendees and offers twenty-four-hour online access to the discount. Use an appropriate permissioned follow-up route rather than assuming every visitor's contact details are available.

Linked funnel five: VIP event

Send a personalized invitation only as part of a separately authorized campaign, stating the genuine selection basis, benefits and capacity. The event welcomes attendees individually and uses a relevant, verified story to establish context. Tailor the demonstration to the group's actual needs, then offer an intimate Q&A with detailed, practical answers.

Present the real attendee offer and provide a private checkout or concierge process if it exists. Personalized follow-up may thank the attendee and clarify next steps; the example uses a forty-eight-hour extension. VIP positioning does not justify invented exclusivity, an unsupported promise or pressure to buy. This differs from a retail walk-in event through invitation, customization and the purchasing support offered.

Practice and framework connection

A demonstration can strengthen the credibility element of a Hormozi-style offer when the evidence actually matches the promised outcome and effort. A Brunson-style progression connects the invitation, story, demonstrated value and appropriate offer. Neither makes every testimonial representative or every deadline truthful by default.

Choose one funnel and prepare the invitation, opening, shot/step plan, feature-benefit explanations, three relevant problem demonstrations, evidence, Q&A plan, offer and follow-up. Label absent product facts and source placeholders. Keep all three SHOW definitions and both complete source texts available in the lesson appendix.

Sources and resources

- Assigned SHOW script and alternate checklist. - Linked five SHOW funnel types. - Acquisition.com value-equation checklist, ClickFunnels value-ladder reference, and RISER NATION CORP.

Assigned source links

D0424 original source 1

Original embedded resource links

Original embedded hyperlink spans:

Complete linked source

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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.
Complete linked native source text; reciprocal references retained

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."

Teach a customer story across five complete campaign formats

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Use Setup, Twist, Obstacle, Resolution and Your Product in email, social media, video, a landing page and a webinar. Preserve the customer's actual work and limitations, then connect the story to an appropriate offer. The assigned document provides templates, not actual testimonials.

Understand the narrative and its alternate source meaning

Setup identifies the customer, role and initial problem. Twist explains how the customer discovered the product or changed approach. Obstacle describes challenges that remained even after adoption. Resolution reports the supported result and relevant conditions. Your Product connects the experience to what the current buyer can evaluate and purchase.

The linked STORY document previously assigned as D0390 uses Select, Tell, Offer, Reinforce and Yield as a different workflow. Selecting relevant testimonials, telling their story, offering social proof, reinforcing key messages and yielding to an appropriate action can support this narrative, but the two acronym definitions must not be merged silently. Refer to the linked original for its complete wording. The present lesson focuses on the five funnel types actually supplied in D0425.

Teach the linked source's six emails

Email 1, Introduction to the Story. The subject introduces the customer and how they overcame a named problem using the offer. The body greets the reader personally, describes the customer's situation and announces the journey the next messages will cover. Use the customer name, reader first name, problem, product and desired outcome accurately. The source's statement that the reader can achieve the same results needs substantiation; an individual success is not automatically a typical outcome.

Email 2, The Problem. The subject focuses on the customer's struggle before finding the product. The body develops the pain points, frustrations, obstacles and prior attempts, then previews the turning point. Describe what the customer actually experienced rather than adding emotions or failed alternatives because they fit the template. The next-message invitation keeps the sequence coherent.

Email 3, The Discovery. The subject announces how the customer found the product. The body names the discovery route, such as search or a friend's recommendation, acknowledges skepticism and explains why the customer decided to try it. It then previews the outcome. These details help explain a decision; they must not be invented to manufacture a more dramatic story.

Email 4, The Transformation. The subject presents the result. The body distinguishes the problem solved, the change in the customer's life or work, and any confidence the customer reports. The source describes speed, effectiveness, lasting change and an extraordinary result. Explain the actual measure and period instead of assuming all those benefits occurred. It then invites the reader to consider an appropriate next step.

Email 5, The Invitation. The subject invites the reader to begin. The body recaps the journey and offers three actions: visit the website, order under an actual offer, and use the product toward the intended result. The third item is an intended experience, not a guaranteed outcome. Replace Insert Link only with the relevant destination, and describe genuine discount conditions. The source's “if they can, so can you” implication must not replace evidence of what buyers can generally expect.

Email 6, The Reminder. The subject reminds the reader of the opportunity. The body revisits the story and any real time-sensitive offer or bonus, with a clear link. Do not invent a deadline, imply that a person has shown purchase intent without evidence or continue messaging without the appropriate basis. These are teaching templates; no email campaign is being sent by this lesson.

The progression moves from introduction and problem through discovery and result to invitation and reminder. Preserve the source's subject, greeting, body, transition and sign-off examples in the appendix. When adapting them, keep the sequence understandable and the claims accurate rather than copying the superlatives.

Apply the linked five preparation steps

Select compelling testimonials: choose experiences relevant to the audience's benefits, outcomes or concerns. Selection must not make the overall impression misleading. Tell their story: explain the journey and challenges with descriptive detail supported by the customer account. Offer social proof: use actual experiences to help a reader evaluate credibility; names, locations and occupations require appropriate permission and should not be treated as independently verified credentials merely because they appear in a quote. Reinforce key messages: connect the story to specific features, benefits and outcomes that the evidence supports. Yield to action: invite the reader to learn more, visit a site, try an actual free trial or purchase, with a clear next step suited to the offer.

Email campaign: five messages and a follow-up

Email one introduces a real customer's role and specific problem and previews how the customer encountered the product. Email two explains that turning point and previews what followed. Email three discusses the obstacles, showing that using the product did not make success effortless, and previews the resolution. Email four explains the result, including the source's emphasis on months of dedication where that accurately reflects the case, then invites the reader to learn more. Email five connects the supported story to the offer and supplies the actual purchase destination and terms.

Each continuation CTA should lead to the promised next part of the same truthful story. The follow-up addresses nonbuyers with a relevant reminder or incentive; the source uses a ten-percent discount code and limited duration as examples. They are not active RISER terms. Do not convert one customer's experience into a promise that every subscriber will have the same transformation.

Social campaign: five posts and engagement

Post one introduces the customer and before-state, then invites people to follow the story. Post two explains discovery of the product and previews the next development. Post three shows the work and obstacles that remained. Post four presents the supported resolution and invites further learning. Post five directly explains the product and the real next-step offer with an accessible link.

The source proposes subsequent comments, direct messages or additional posts for interested people who have not acted. Distinguish an appropriate response to expressed interest from assuming every viewer has invited a sales message. Statements about incredible response or the same success require actual evidence; the template does not provide engagement results. Keep material conditions visible in individual posts because a viewer may encounter them out of order.

Video campaign: one complete video or five connected clips

The source permits a single compelling video or a five-video series. In either format, introduce the customer and struggle, show discovery, explain the obstacles, report the resolution and connect the product to the next action. In a series, the first three closing prompts invite the next video, the resolution invites consideration, and the final clip supplies the offer link. Include enough context in each clip to avoid making a partial story misleading.

The obstacle segment is essential: persistence and support should not disappear during editing merely to make the product look effortless. The source suggests a follow-up message with a discount code for nonbuyers. Use real viewing/contact permissions and an actual offer before any operational follow-up. A placeholder customer praising the product is not an available video asset; production and testimonial permissions remain separate work.

Landing page: five sections and an appropriate follow-up path

The first section identifies the before-state and encourages continued reading. The second shows the turning point. The third explains the post-adoption challenges. The fourth presents the result and evidence. The fifth connects the story to the product, actual price/bonus or discount and a clear purchase action. The source's repeated same-results language overstates what one case establishes; replace it with a supported description of who the offer may help and under what conditions.

The proposed follow-up says the visitor did not complete a purchase. Do not assume an anonymous page visitor can be identified or emailed. A real follow-up requires an appropriate known contact and accurate status. Preserve the informational purpose—answer a remaining question or clarify a real offer—without fabricating knowledge of the person's actions.

Webinar: registration through the final recap

The registration page sets up the customer's problem and explains what the audience will learn from the case. The introduction repeats the relevant context and previews the turning point. The main content combines Twist and Obstacle, explaining both product discovery and the work or challenges afterward. The resolution presents the supported result and its conditions, then transitions to the product offer. The offer supplies the actual next action and terms rather than promising that attendees will duplicate the case.

Follow-up can recap the case and answer remaining questions. The source proposes extending the webinar offer for twenty-four hours; an extension must reflect truthful availability and not contradict an absolute claim that the offer could never be obtained afterward. Live and recorded formats are both mentioned; accurately identify which the audience is receiving.

Protect the evidence while preserving the story

As authored RISER practice, record the customer's permission, original wording, timeframe, starting point, relevant effort and evidence for each stated result. Separate observed facts from the customer's opinion and from the seller's explanation of causation. Do not invent a twist, obstacle or result to fill a five-part template. If a stage is unsupported, mark the gap and seek the actual information. A narrative may make evidence easier to understand, but it cannot replace it.

The Brunson connection is the movement from a relevant hook through an understandable story to an offer. The Hormozi connection is whether the evidence supports the desired result and its likely time, effort and conditions. These are educational applications, not proof that either person originated this source's acronym.

For the exercise, choose a real, approved customer case and produce all five stages in one channel, with every continuation and purchase CTA plus an appropriate follow-up. Then map how the same facts would appear in the other four channels. Record missing proof and assets. Preserve the complete assigned source and linked reference in the appendix; a polished template is not a completed testimonial campaign.

Sources and resources

- Assigned five STORY testimonial funnels. - Linked STORY method—alternate workflow. - Acquisition.com value-equation checklist, ClickFunnels value-ladder reference, and RISER NATION CORP.

Assigned source links

D0425 original source 1

Original embedded resource links

Original embedded hyperlink spans:

Complete linked source

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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.
Complete linked native source text; reciprocal references retained

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.

Write five one-sentence offer hooks from one truthful brief

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Prepare the source's five inputs, write each of its five copy styles, enforce its length requirement, and check the five supplied examples for unsupported promises. The prompt is a writing template, not a proven conversion system.

Supply the five facts before requesting copy

Start with what you offer: name the product, service or course. Then define who it is for with a specific audience. Third, state the painful problem in that audience's words. Fourth, explain the result the offer helps them pursue. Fifth, identify what makes the approach different, potentially faster or otherwise distinctive. The source suggests differences such as avoiding ads, a seven-day timeframe or using AI. These are candidate attributes, not permission to make an unsupported speed or outcome claim.

These five inputs support the source's opening four communication goals: identify the offer, audience, benefit and difference. The separate pain-point input makes the benefit relevant. If a fact is missing, leave it unresolved rather than asking a writing model to invent it. The repeated fill-in invitation at the end requests the same five facts; it is not an additional framework or an instruction to activate a campaign.

Produce all five styles

For a short and punchy hook, remove introductory wording and name the useful action or benefit directly. For the emotional, benefit-led version, connect a concrete improvement to how the buyer wants to feel, without implying that everyone will experience the same emotional change. For curiosity, reveal a relevant distinction while giving enough information to identify the offer; withholding essential terms does not make the promise stronger.

The fourth version begins with Finally or Imagine. Finally can introduce relief from a frustrating process, and Imagine can invite the reader to picture an achievable next step. Neither word turns an unsupported result into a harmless hypothetical. The fifth style combines shock and relief: identify a real frustration or mistaken assumption, then introduce a credible way to reduce it. Avoid manufactured fear or exaggerated consequences merely to stop scrolling.

As authored practice, use a simple example offer: a worksheet helping new course creators organize their first lesson. Five possible practice hooks are: “Plan your first lesson with a step-by-step worksheet”; “Give your first lesson a clear direction with a worksheet built for new course creators”; “What belongs in lesson one? Map it before you record”; “Finally, a worksheet for organizing your first lesson before recording”; and “Still staring at a blank lesson? Start with a guided outline.” These are authored demonstrations of the styles, not extracted source examples or measured advertising winners.

Enforce the actual length limit

The source asks for one sentence per version and fewer than twenty words. Nineteen words is within that instruction; twenty is not. Count each draft and choose a consistent rule for hyphenated terms rather than relying on a model's claimed count. Check that concision has not removed the audience, useful result or meaningful difference. The social-post or ad-headline context explains the short format; it does not establish a guaranteed attention or conversion effect.

Review every supplied example

The first source example promises three paying clients in seven days without cold messages or paid ads. It combines an outcome, deadline and exclusion, all of which need support. The second addresses struggling coaches and pictures qualified leads every morning; the audience specificity is useful, but the daily reliability claim is not established. The third uses Finally and promises viral Reels without showing a face. A faceless production method and viral distribution are different claims; the source demonstrates neither.

The fourth contrasts hours of work with AI generating thirty posts in ten minutes. Preserve those quantities as a source illustration, but distinguish draft generation from fact-checking, revision and publication. The fifth claims a plug-and-play system will fill the calendar with ideal clients. A system description does not prove bookings, fit or capacity. These examples teach how result, speed, effort and emotional relief can appear in a hook; they are not approved RISER NATION performance promises.

Connect the hook to the offer and test it

A Brunson-style hook should lead into a consistent story and offer. Hormozi's value-equation lens helps ask whether the sentence describes a desired outcome and honestly addresses confidence, time or effort. A hook that promises more than the actual product can deliver weakens that connection. For the exercise, submit the five-input brief, all five under-twenty-word versions and the evidence or limitation attached to each factual promise. Select a version for a future authorized test using results rather than declaring it high converting before it runs.

Sources and resources

- Complete assigned one-sentence offer prompt and examples. - Acquisition.com value-equation checklist. - ClickFunnels value-ladder reference and RISER NATION CORP.

Assigned source links

D0426 original source 1

Complete returned native document text

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

 here's a powerful, fill-in-the-blank style prompt you can use to create a scroll-stopping, one-sentence offer hook that clearly communicates:
What you offer

Who it’s for

The big benefit/result

Why it’s different or exciting


⚡ One-Sentence Irresistible Offer Prompt
You are a high-converting direct response copywriter.

Create a short, catchy, one-sentence offer hook that instantly grabs attention, makes the reader curious, and communicates the clear benefit of my offer.

Here’s what you need to know:

- **What I offer**: [Insert your product/service/course]
- **Who it’s for**: [Your specific audience]
- **What painful problem it solves**: [What they’re struggling with]
- **What amazing result it helps them achieve**: [The transformation]
- **What makes it unique or fast/different**: [E.g., "without ads", "in 7 days", "using AI", etc.]

Write 5 variations using different copy styles:
1. Short and punchy
2. Benefit-driven and emotional
3. Curiosity-based
4. “Finally” or “Imagine” style
5. Shock-and-relief combo

Keep each version under 20 words and make it scroll-stopping — like a social media hook or ad headline.


—----------------------------------------------------------------------------------------------------------------------------

🧠 Examples (You’ll get from the prompt):
"Get 3 paying clients in 7 days—without cold DMs or paid ads."
 "Struggling coaches: Imagine waking up to qualified leads every single morning."
 "Finally, a way to create viral Reels without ever showing your face."
 "Stop wasting hours creating content—AI writes your next 30 posts in 10 minutes."
 "No more guessing—our plug-and-play system fills your calendar with dream clients."

✅ Want me to fill this out for you? Just give me:
What you’re selling

Who it’s for

What big problem it solves

What the amazing result is

What makes it unique

I’ll generate your 5 scroll-stopping sentence hooks immediately.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1sJvc_A-WX9SXgUIlCldxfJSaSCVDX1mNPjChs1_Y5Vw/edit?usp=drivesdk"
drive_file_id: "1sJvc_A-WX9SXgUIlCldxfJSaSCVDX1mNPjChs1_Y5Vw"
created: "2025-03-28T21:45:04.081Z"
modified: "2026-06-04T16:33:44.520Z"
---

# 2.) One-Sentence Irreristible Offer 

here's a powerful, fill-in-the-blank style prompt you can use to create a scroll-stopping, one-sentence offer hook that clearly communicates:
* What you offer

* Who it’s for

* The big benefit/result

* Why it’s different or exciting

________________


⚡ One-Sentence Irresistible Offer Prompt
You are a high-converting direct response copywriter.


Create a short, catchy, one-sentence offer hook that instantly grabs attention, makes the reader curious, and communicates the clear benefit of my offer.


Here’s what you need to know:


- **What I offer**: [Insert your product/service/course]
- **Who it’s for**: [Your specific audience]
- **What painful problem it solves**: [What they’re struggling with]
- **What amazing result it helps them achieve**: [The transformation]
- **What makes it unique or fast/different**: [E.g., "without ads", "in 7 days", "using AI", etc.]


Write 5 variations using different copy styles:
1. Short and punchy
2. Benefit-driven and emotional
3. Curiosity-based
4. “Finally” or “Imagine” style
5. Shock-and-relief combo


Keep each version under 20 words and make it scroll-stopping — like a social media hook or ad headline.




—----------------------------------------------------------------------------------------------------------------------------


🧠 Examples (You’ll get from the prompt):
"Get 3 paying clients in 7 days—without cold DMs or paid ads."
"Struggling coaches: Imagine waking up to qualified leads every single morning."
"Finally, a way to create viral Reels without ever showing your face."
"Stop wasting hours creating content—AI writes your next 30 posts in 10 minutes."
"No more guessing—our plug-and-play system fills your calendar with dream clients."
________________


✅ Want me to fill this out for you? Just give me:
   1. What you’re selling

   2. Who it’s for

   3. What big problem it solves

   4. What the amazing result is

   5. What makes it unique

I’ll generate your 5 scroll-stopping sentence hooks immediately.

Build an offer around a specific problem, useful support and credible terms

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Use the source's five offer-design moves, offer-stack example and complete prompt brief. Evaluate the real-estate example and the proposed tools without turning illustrative promises into actual results. Calling an offer irresistible or a no-brainer is the source's marketing language; buyers still need a clear, voluntary decision.

One specific pain gives the promise a center

Choose the most important, urgent problem supported by customer research. The source proposes moving a customer from a painful present to a desired outcome without a disliked obstacle. A narrow central promise can improve clarity without pretending the customer has only one problem. Its example of five paying clients in thirty days without ad spending combines three separate assertions: client count, timeframe and acquisition constraint. Treat that as an unverified illustration, not a promise to copy automatically.

The proposed brainstorming exercise asks ChatGPT or Copy.ai for twenty variations based on the researched problem. Supply the facts and limits first, then compare whether each version still describes the same deliverable. Generated wording is a draft. It does not supply missing customer research or evidence for the result.

Make each bonus remove a specific obstacle

The source pairs a tech-setup walkthrough with fear of technology, plug-and-play templates with overwhelm, and a one-to-one strategy call with doubt. Explain how each would help a buyer use the core offer. A walkthrough needs actual instructions; templates need to fit the task; a call needs a defined purpose, length and availability. The central product addresses the main problem while the bonuses address implementation objections. They do not literally eliminate all hesitation.

Xmind is suggested for a visual map connecting the core offer, each objection and its bonus. As authored practice, remove a proposed bonus if you cannot explain that connection. More items can add confusion and fulfillment cost rather than value.

Translate features through benefits into results

The source compares naming six video modules with describing six short lessons that help a buyer progress from unclear ideas to a launched offer in a weekend. The lesson count is a feature; clearer planning and implementation support are benefits; a launched offer is an outcome. The weekend timeframe requires evidence and conditions. Preserve the feature information so customers can still assess what they receive.

Use the chain Feature → Benefit → Ultimate Result. In the template example, a template may help someone write faster, which can help them launch sooner and pursue revenue sooner. Each link is conditional: faster writing alone does not establish sales. The source suggests ChatGPT or a tool called Conversion.ai's Value Ladder Generator for this rewriting. Its link leads to Jasper, but a current primary-site check did not verify that exact named feature. Keep the original link as a reference and use the writing exercise without claiming the feature exists.

Give a real reason to act by a stated time

The source lists ten available spots, doors closing Friday at midnight, a bonus expiring in twenty-four hours, and three live group sessions available to people joining before Tuesday. These are different limits: capacity, enrollment deadline, bonus duration and scheduled support. Define the actual date, timezone, eligibility and what changes afterward. Scarcity must be real, not merely feel real. Do not restart a supposedly final timer whenever someone returns.

Deadline Funnel is proposed for deadline automation, and ConvertBox for on-site offers and calls to action. Deadline Funnel's own overview describes authentic deadline campaigns; ConvertBox's site describes on-site messages. Neither tool makes an invented capacity limit true. Verify the relevant setup and plan before promising an implementation; this lesson does not install or purchase either product.

Reduce risk with terms you can fulfill

The three source examples are a thirty-day money-back period, continued help until a named outcome, and lifetime access to a private group. They impose very different obligations. For a refund, explain eligibility, request method, exclusions and timing. For continued work, define the outcome, buyer responsibilities, support scope and termination conditions. For lifetime access, define whose or what lifetime is meant and what happens if the service changes. Support and community can help implementation but do not automatically make buying safer than doing nothing.

Teachable and Gumroad are suggested as delivery/refund-related platforms, and Circle as a community platform. The source supplies no actual refund configuration or membership terms. A platform link is not proof that the proposed guarantee is funded or operational. Match the promise to fulfillment capacity before using it in an offer.

Explain every line of the offer stack

The sample stack assigns $997 to the core transformation, $197 to a template or toolkit, $297 to an accountability session, and $497 to community access. These add to $1,988. The proposed price is $197. Arithmetic consistency is useful, but it does not substantiate any assigned value. Explain what the buyer receives and use supportable reference values instead of inventing inflated comparison prices. Canva is the proposed tool for displaying the stack; attractive design cannot supply valuation evidence.

This is where a Brunson-style stack can make the contents of an offer understandable, while Hormozi's lens checks the desired result, likelihood, delay and effort. Neither framework justifies arbitrary dollar amounts or an unfulfillable guarantee.

Fill the complete prompt and review its outputs

The prompt requests five inputs: the target audience with age, career stage, goals and struggles; three major pain points; previous failed solutions; the desired transformation; and the offer type. The example types are course, coaching, service, toolkit, membership or SaaS, with customization allowed.

It then asks for a transformation-focused core promise; three or four bonuses addressing objections such as technology fear, overwhelm or procrastination; an offer stack with value breakdowns; a clear urgency element; a risk-reversal statement; emotional, benefit-led language; and a sales-page summary usable in an email or landing page. Review every output against the input evidence and real terms. The closing question proposes optional one-click upsell, downsell or recurring-offer versions. It is a possible later design step, not permission to create charges or change a checkout.

The source repeats the same useful prompt a second time. Both copies remain in the original appendix, while this lesson teaches the distinct instructions once.

Apply the supplied real-estate brief

The example audience is new real-estate agents aged twenty-five to forty who are comfortable in person but struggle with online lead generation. Their three pains are posting with no results, spending time on social media without direction, and fear of technology or automation. Previous attempts include Instagram posting, random cold messages and buying leads. They want warm, qualified weekly leads without burning out, and the proposed offer is an online course plus templates.

Use those details to identify the core problem, relevant walkthrough or template bonuses, and what evidence a weekly-lead promise would need. The age range is part of this sample brief, not a universal description of agents or a required targeting restriction. The example gives no actual curriculum, lead data or verified result. Do not invent them.

Submit an offer worksheet containing all five design moves, the complete five-input brief, the seven requested outputs, a checked value stack and explicit unresolved terms. Keep the original source and tool links attached so another reviewer can trace each idea.

Sources and resources

- Complete assigned Solving the Problems document. - Original brainstorming and mapping references: ChatGPT, Copy.ai, Xmind, and Jasper—the source's Conversion.ai link; exact named generator unverified. - Original deadline and messaging references: Deadline Funnel, how Deadline Funnel describes its process, and ConvertBox. - Original delivery, community and design references: Teachable, Gumroad, Gumroad refund help, Circle, and Canva. - Acquisition.com value-equation checklist, ClickFunnels value-ladder reference, and RISER NATION CORP.

Assigned source links

D0427 original source 1

Original embedded resource links

Original embedded hyperlink spans:

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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.

Connect features to outcomes without outrunning the evidence

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Build a feature-to-outcome grid, use the six campaign steps, define the proposed review roles, correct the three failure patterns, and measure whether the change helps customers. The source's legacy Course 9 title does not change this document's current spreadsheet assignments.

Follow the feature, benefit and outcome chain

A feature describes what the product is. A benefit describes what it does. An outcome describes the change the customer hopes to experience. The source's multi-agent AI scheduler is the feature, automated appointments are the benefit, and fewer missed leads plus ten reclaimed hours each week are the proposed outcomes. Scheduling capability alone cannot substantiate that ten-hour figure or guarantee that no leads are missed.

Examine three outcome lenses. Money includes revenue, savings, return on investment and protection against financial risk. Time includes speed, simpler work and fewer steps. Emotion and identity include confidence, status, peace of mind and control. A strong offer may address more than one, but not every customer values all three equally. Keep material specifications available because buyers need to understand both the result and the means of pursuing it.

Use language from customer calls, reviews and forms. Familiar wording can make the meaning easier to recognize; it is not evidence that a promise is true. The source's three-to-five-times conversion claim is unsupported here. Its broad claims about 2026 AI precision and refund spikes also lack accompanying studies or measurements. Teach them as proposed rationales to test, not established RISER results.

Apply the six campaign steps

First, collect real phrases from testimonials, sales calls, chats and surveys, preserving the customer's description of both the before state and desired after state. Use material with appropriate permission and remove unnecessary identifying information.

Second, create a grid for each feature. Ask what it removes—waste, confusion, manual work or risk—and what it creates—clarity, speed, profit or freedom. Record the exact customer words describing that shift. A row with no evidence should say so; generated language is not a customer quotation.

Third, write outcome-first messaging. The source proposes a headline about turning chaotic client communication into a ten-minute daily check-in, followed by a subheading about agents organizing, drafting and scheduling. The headline explains the intended change; the subheading names the supporting functions. The ten-minute claim and the actual availability of those functions need verification before publication.

Fourth, use the proposed three-pass workflow. One agent or reviewer rewrites features as outcome sentences. A second compares them with real customer language and removes jargon. A third flags exaggerated or unsupported claims. These are proposed responsibilities; the document provides no deployed agents, prompts, permissions or evaluation system. Human reviewers can perform the same sequence.

Fifth, examine likely buyer expectations. Ask whether a reasonable reader would infer that the result is easy or typical. The source requests at least one proof element—a case study, demonstration, number or mechanism explanation—for a strong outcome claim. These forms of support are not interchangeable: a mechanism explanation may clarify how something could work without proving the promised result, and a single exceptional case does not establish typical performance. Match evidence to the precise claim.

Sixth, carry the reviewed outcomes into advertisements, emails and landing pages. Lead with the useful customer change and explain the tools afterward. Keep the promise consistent across the full journey so a personalized advertisement does not offer more than the landing page or product provides.

Define the workflow roles and editor layers

The proposed Outcome Strategist defines transformations by segment. The Language Matcher maps real customer phrases into copy. The Proof Checker compares claims against data, testimonials and realistic timeframes. Record who accepts or rejects a claim; simply naming an agent is not accountability.

The source adds two editing layers: one rewrites in the buyer's vocabulary and tone; the other removes hype, clarifies expectations and adds specifics. Its semantic AEO layer asks whether the page answers a real question such as how to stop wasting time on a task. This is a useful content check. It is not a special mechanism that guarantees inclusion in an AI answer. Google's guidance retains ordinary SEO fundamentals, textual content and matching visible content/structured data; indexing and inclusion are not guaranteed.

Interpret the psychology as hypotheses

The source describes future-state pictures, cognitive fluency, regret and remorse. A concrete picture such as logging in to organized work can make an outcome understandable. Familiar language can make a message feel easier to process. Neither effect proves accuracy or universally outweighs specifications. Similarly, overpromising may damage trust, but the source does not quantify how clearer scope changes lifetime value or referrals. Use these ideas to design testable messaging and delivery improvements, not to assert a universal brain response.

Correct all three failure patterns

Personalization drift occurs when variants promise more than the feature set can deliver, such as tripling everyone's revenue. Tie each variant to evidence, a relevant segment and explicit conditions. An authored control is an approved claim register with a maximum supported scope for each claim; the source's phrase claim ceiling does not supply an actual implementation.

Overpromising occurs when the best case is presented as normal. The source proposes up to, on average, typical ranges and buyer exclusions. Adding up to does not make an unsupported maximum acceptable, and on average requires a defensible average. Explain sample, timeframe and relevant conditions, and show who is unlikely to benefit where known.

Feature dumping occurs when specifications have no clear implication for the buyer. Write at least one relevant outcome sentence for each feature. The proposed test leads with three core outcomes and puts many details behind tabs. If tested, keep essential price, scope, limitations and accessible product details easy to find; hiding material information is not a valid conversion tactic.

Use all four optimization practices

The prompt chain first rewrites for a stressed solo founder, then for a risk-averse corporate buyer, then removes hype and adds clarity and proof. The two audiences may need different language, but their variants must remain inside the same supported product scope.

Language mirroring uses anonymized customer messages to inform phrasing. The source calls this training, but provides no model-training procedure. Supplying approved examples in a brief is different from actually training a model. Compare generated variants through a defined test rather than assuming that resemblance guarantees performance.

Match the guarantee to the scope. A small, well-defined outcome may pair with a clear refund or credit policy. A complex outcome may require milestones, check-ins and a specific remedy if a condition is unmet. State buyer time, inputs and implementation duties so the promise is operationally understandable. This lesson supplies no executed guarantee or contract.

Finally, simulate a disappointed buyer and ask what a negative review might say. Use the resulting hypotheses to inspect unclear expectations, onboarding or scope. The simulated review is neither real customer feedback nor evidence that a problem has occurred. Verify significant concerns before changing the offer.

Measure all four proposed KPIs

Track conversion before and after the messaging change using comparable populations and time windows. As an authored measurement convention, conversion rate is conversions divided by eligible visitors; relative lift is the new rate divided by the old rate minus one, and is undefined when the old rate is zero. Do not confuse percentage-point change with relative lift.

For remorse, separately track refunds, cancellations and relevant negative reviews. Define the customer cohort, observation period and denominator, and avoid counting the same customer several times in a combined measure. The source lists the components but supplies no complete remorse-rate formula.

For time-to-value, define the promised value event and the starting event, then measure elapsed time for the relevant customers. Include non-achievement and reporting limits rather than only successful cases. For language match, the source proposes a percentage of key copy phrases found in customer research. Define what counts as a phrase, a match and the denominator; no exact scoring algorithm is provided. A high match score does not establish a truthful claim.

Connect the outcome to the operating system

The source links pain research from legacy Problems Create Markets to the outcome's before/after distinction, persuasion to the headline's emotional meaning, and decision intelligence to a go/no-go check on evidence and conditions. Preserve those conceptual relationships without replacing the current course map with legacy numbering. Its 2030 adaptive onboarding, content and support flows are a future proposal, not a deployed capability.

Use Hormozi's outcome, likelihood, time and effort questions to review the offer and a Brunson-style progression to keep each funnel step consistent with delivery. Submit the grid, six-step campaign brief, role ownership, corrected variants and four defined measurements. Keep the full source appendix and unresolved evidence visible.

Sources and resources

- Complete assigned Outcomes > Features source. - Google Search Central: AI features and your website. - Acquisition.com value-equation checklist, ClickFunnels value-ladder reference, and RISER NATION CORP.

Assigned source links

D0428 original source 1

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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.

Connect a live sales picture to a credible promise and proof

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Plan all five live-sales funnels in the source: seminar or workshop, webinar, corporate presentation, conference or trade show, and high-ticket consultation. Preserve their acquisition, presentation, decision and follow-up stages. The document calls Picture, Promise and Proof the PPF Formula, although Proof begins with P. Keep that source label explicit without inventing an F component.

Explain the three message elements

Picture helps the audience understand a desired future state. Promise states what the offer can credibly help the buyer do. Proof supplies relevant evidence for that promise, such as a verified case, meaningful demonstration or properly contextualized result. A vivid picture does not reduce the evidence needed for an implied claim. The source's client names, testimonials and financial examples are placeholders rather than actual RISER NATION results.

Funnel one: seminar or workshop

Promote the event through appropriate email, social advertising or partnerships, targeting people who may benefit from the topic. The registration page describes the value of attending through the three elements, then asks for registration. The source's picture of doubling revenue within twelve months and its full-day promise are examples requiring actual curriculum, scheduling and substantiation.

During the event, describe the audience's desired situation, explain the product or service's relevant role, and present evidence. The source illustrates proof with a client whose revenue increased 150 percent in six months; no real supporting case is supplied. Do not read that statement as fact about your business. Explain conditions and actual results when a verified case is available.

The closing CTA offers an event discount or bonus; twenty percent is the example. Provide an on-site order form or usable online checkout and explain what happens after purchase. For nonbuyers, the proposed follow-up includes a replay, additional testimonials and a time-limited offer. Each element needs to exist and be accurately described before a campaign is activated.

Funnel two: live webinar

The registration page uses a picture of freeing ten hours each week through automation, a promise about the system being taught, and real supporting stories if available. The thank-you page supplies a short pre-webinar video with three tips in the example. Those tips and the video are not provided in the document, so mark them as production requirements.

The live presentation describes the desired operating state, explains how the system can help and shows evidence. The source's example of a forty-percent workload reduction alongside increased profit is unverified. A business that practically runs itself is also an aspirational description, not an established product capability.

The offer presentation supplies the actual terms; the example proposes a thirty-percent discount and a bonus guide during the webinar. Direct attendees to a sales page consistent with Picture, Promise and Proof. Follow-up supplies a replay, additional support and a truthful final offer opportunity. Do not call the price available only during the webinar if the planned follow-up routinely offers the same price afterward without explanation.

Funnel three: corporate sales presentation

The source proposes email or LinkedIn outreach to arrange a meeting with decision-makers. As a planning exercise, describe the prospect's desired operational improvement, the relevant solution and existing evidence. The thirty-percent cost-reduction picture is a sample aspiration, not a validated forecast.

During the presentation, connect fewer bottlenecks and faster projects to the product's actual functions. Support the proposed benefit with relevant cases, statistics or testimonials. The source uses a different twenty-five-percent cost reduction over six months as its proof example. The difference between the thirty-percent aspiration and twenty-five-percent sample case must remain visible; neither number is established evidence here.

Q&A addresses actual objections. The sample forty-percent increase in project delivery speed is another unverified case claim, not a response to copy indiscriminately. Close with an appropriate trial, demo or tailored-proposal action. The follow-up proposal restates the picture, supported promise, proof, scope and next steps. A later call or meeting addresses remaining questions and asks for a decision without assuming all companies will reproduce another client's results. No outreach or proposal is sent by this lesson.

Funnel four: conference or trade show

Promote the session through appropriate event marketing, social media and email. The stage presentation introduces the desired future, the offer's role and relevant evidence for an audience that may be unfamiliar with the brand. The source's picture of twice as many customers with lower marketing spending and its sample fifty-percent sales increase in three months are illustrative claims with no accompanying data.

Direct interested people to the booth, a demo registration or an actual purchase option. Booth number 123 is a placeholder and must be replaced with the real location. At the booth, continue the same message through a live demonstration and questions, then offer a personalized demo or real event terms. Collect contact information appropriately for the intended follow-up rather than assuming all conference attendees are sales leads.

The follow-up recaps the session, provides relevant proof and invites the next step. Interested prospects may then receive a one-to-one call or meeting that adapts the picture and supported promise to their situation. The booth interaction, follow-up and final call serve different information needs; do not collapse them into one generic purchase instruction.

Funnel five: high-ticket consultation

Generate and qualify suitable prospects through an authorized use of targeted advertising, referrals or outreach. The personalized presentation starts with the prospect's actual goals and describes a relevant path. The source's seven-figure business picture is an aspiration, not an entitlement or guaranteed outcome.

Support a specific, scoped promise with substantial relevant evidence. The example of a client growing from $500,000 to $2 million annual revenue is not a supplied financial record. Before using an actual case, explain its timeframe, starting conditions, work and what can reasonably be attributed to the offer.

Prepare a customized proposal or action plan after the presentation. Review it in a follow-up meeting, answer objections with suitable evidence and explain responsibilities. The source's twelve-month plan is a sample timeframe rather than a standard commitment. A closing incentive should be genuine, and a request for a decision should preserve the buyer's ability to decline an unsuitable offer.

The final stage is onboarding: emails or meetings set expectations, explain next steps and establish how the buyer begins receiving value. The source highlights the first thirty days. Define actual milestones and owner responsibilities before promising rapid results. This delivery stage distinguishes a completed sales journey from a signed order alone.

Review the full numeric-claim set

Keep the examples traceable: doubling revenue in twelve months; 150 percent revenue growth in six months; twenty-percent event discount; ten hours freed weekly; forty-percent workload reduction; thirty-percent webinar discount; thirty-percent cost aspiration; twenty-five-percent cost case over six months; forty-percent project-speed example; twice the customers; fifty-percent sales growth in three months; seven-figure scale; $500,000 to $2 million revenue; a twelve-month plan; and the first thirty days of onboarding. Discounts and durations are proposed terms, while performance figures are unsupported illustrations. None becomes a live RISER NATION claim simply because the source contains it.

Apply the educational themes and practice

A Brunson-style narrative connects the initial hook, the customer's relevant story and an appropriate offer. Hormozi's value-equation lens asks whether the desired outcome, likelihood, delay and effort are honestly represented. Proof should help calibrate the promise; it should not be decorative reassurance beside an unsupported number.

For practice, select one of the five contexts and write its complete path: acquisition or invitation, registration or qualification, presentation, questions where applicable, CTA, purchase/proposal, follow-up and onboarding where specified. Identify actual evidence and missing assets, and keep all original examples in the appendix with their limitations. The source is an outline for building a presentation, not proof that a campaign or customer result exists.

Sources and resources

- Complete assigned PPF live-sales funnel document. - Acquisition.com value-equation checklist, ClickFunnels value-ladder reference, and RISER NATION CORP.

Assigned source links

D0429 original source 1

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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.

Turn a marketing reading brief into an evidence-based offer plan

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Identify every reference in the supplied coaching brief, keep uncertain references visible, and turn the brief into a practical offer-planning exercise. Distinguish the material actually supplied from the contents of books that are only named. Then connect buyer understanding, a clear offer, storytelling and accountable implementation.

Establish what the original document contains

The assigned source is a short transcribed request to a business coach. It asks to use Sway, The Catalyst by Jonah Berger, Tested Advertising Methods by Caples, The Irresistible Offer by Joyner, the ambiguous phrase “colors the one thing,” and Dan Sullivan's Who Not How. It also names Russell Brunson, Kennedy and Frank Kern in connection with storytelling, Epiphany Bridges and bringing an offer to market. It ends by asking whether the request is understood.

Those are the complete distinct references and intentions in the retrieved brief. No book chapters, worked examples, campaign data, customer interviews or finished offer specifications are attached to that brief. The quoted request is source material for this lesson; it does not authorize us to execute a campaign or claim to have reviewed books whose complete contents are unavailable.

Identify the references without silently repairing the transcript

The publisher identifies Sway: The Irresistible Pull of Irrational Behavior as a book by Ori and Rom Brafman about influences on irrational behavior. Its relevance here is to examine how a buying decision is made, while avoiding the assumption that an appealing psychological explanation proves why a particular customer acted.

Jonah Berger's author bibliography identifies The Catalyst: How to Change Anyone's Mind. The brief spells out Berger's surname, which helps identify the intended author. In the offer-planning exercise below, we use the practical question of what is preventing a buyer from moving forward. That exercise is an authored application, not a claim to reproduce the book's complete framework.

The source names Tested Advertising Methods and Caples. Preserve that reading reference as supplied; the source does not specify an edition or provide its contents. A bibliographic record for John Caples's Tested Advertising Methods can help locate the referenced work. Naming a book is not a substitute for reviewing its actual tests or examples.

The publisher identifies The Irresistible Offer as Mark Joyner's book. Its subtitle describes selling a product or service in three seconds or less. Treat that subtitle as the book's positioning, not a guaranteed buying deadline or a universal rule about attention. This lesson does not invent the book's unsupplied questions, elements or case studies.

The phrase “colors the one thing” is not sufficiently clear to identify a title and author. Retain it in the reference register as an unresolved transcription. Do not silently change it to a guessed book. Its exact identity and any intended passages remain a source-dependent gap.

The publisher identifies Who Not How as a collaboration by Dan Sullivan and Dr. Benjamin Hardy. Its emphasis on teamwork provides a useful prompt: who has the capability to help deliver the intended outcome? That question does not eliminate the need to define the deliverable, responsibility, budget or quality standard.

Connect the named marketing themes to a clear offer

The brief names Russell Brunson, Kennedy and Frank Kern as marketing influences and asks about storytelling and Epiphany Bridges. It supplies no particular Kennedy or Kern text, so keep their names as references rather than attributing a newly invented method to either person. It also gives no real founder story from which to write a factual Epiphany Bridge.

An authored RISER approach is to connect the buyer's current belief, a real observation or experience that changed the seller's understanding, the lesson learned, and the specific offer that follows. Keep any personal story truthful. If no story has been provided, mark the story section as awaiting evidence rather than inventing a customer, hardship or breakthrough. Use the curriculum's Brunson/ClickFunnels hook, story and offer theme to make that connection understandable.

Alongside those explicitly named references, preserve the curriculum's Hormozi/Acquisition.com education theme. Ask what result the buyer wants, what evidence increases confidence in achieving it, how long progress may take, and what effort or sacrifice the buyer must contribute. These questions are an authored connection to the wider curriculum; Hormozi is not named in this particular source brief. Clear value reasoning does not make an unsupported guarantee acceptable.

Apply the brief in a short planning exercise

First, state the audience and desired outcome using actual customer evidence. Second, record what appears to prevent action, separating observed objections from your hypotheses. Third, specify the product or service, price assumptions, delivery responsibility and scope. Fourth, outline a truthful story that explains the offer's relevance. Fifth, identify an accountable person for each delivery dependency and decide what a small validation test would measure.

For example, an authored planning question is: “What must a prospective customer understand about this workshop before deciding whether it fits?” Possible answers include the workshop outcome, prerequisite skills, required time, support, exclusions and the evidence behind any claims. These are questions to answer from the business's records; they are not facts supplied by the brief and are not a campaign that has already been launched.

Finish with a reference register listing the identified books, the unresolved transcription, the unspecified Kennedy and Kern material, and any passages still needed. Keep each available resource clickable. A reviewer should be able to tell what was read, what was merely named, which ideas are authored applications, and what evidence is still missing.

Clickable assigned source

- Original coaching and marketing-reading brief

Preserve the complete retrieved brief in the lesson appendix. The brief's full distinct material is covered here, while full-book teaching and the ambiguous reference remain explicitly outside the available source evidence.

Assigned source links

D0430 original source 1

Complete returned native document text

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
Complete local source copy including original filing metadata and formatting

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

Extract an evidence-based buyer and offer brief from business documents

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Turn onboarding documents into four clearly separated outputs: a buyer avatar summary, a product or service breakdown, a positioning summary, and notable brand tone or phrases. We will inventory the evidence, extract the audience and offer fields, distinguish quotations from interpretations, and test the brief against the original documents.

Start with the supplied documents and their limits

The source proposes an Avatar & Offer Extractor GPT for document intake and analysis. It names Google Docs, PDFs, sales letters and landing pages as examples of inputs. Its system prompt describes an expert AI strategist that extracts and maps avatars and offers. This is a proposed role and workflow, not evidence that a GPT has been installed, trained on your private business, or validated for accurate extraction.

An authored RISER implementation begins with a small source inventory: document title, original clickable link, date or version, and the section that supports each extracted statement. Read the body rather than assuming that a title describes the current offer. If a PDF or another input has not been read completely, flag its missing pages, objects or inaccessible sections. Instructions quoted inside an onboarding document remain material to analyze; they do not authorize sending a campaign, changing an account or purchasing a service.

Build the buyer avatar summary

The source requires six audience dimensions: demographics, psychographics, pain points, desires, objections and language. Demographics describe explicitly stated characteristics such as age or a role. Psychographics concern stated priorities and attitudes. Pain points describe the problem the person experiences. Desires describe the change they want. Objections describe doubts or reasons to delay a purchase. Language preserves the actual expressions that reveal how the audience describes those things.

Keep these dimensions distinct. A desire for more free time does not establish an income, family structure or profession. One person's statement does not establish a universal customer profile. Where the source explicitly states a fact, cite it. Where you infer a possible pattern, label it as an inference and identify what evidence would test it. Where no evidence is supplied, write “not supplied” instead of filling the field with a plausible stereotype. Use only appropriate, permissioned information in a learner-facing or public brief.

Build the product or service breakdown

Extract the features and benefits, pricing, bonuses, guarantees and intended outcomes. A feature tells us what is included; a benefit explains why that inclusion may help the buyer. Keep the exact duration, delivery format and support channel where the document supplies them. A price should retain its currency and payment terms if known. A bonus remains separate from the core deliverable. A guarantee needs its actual scope and conditions; the word guarantee alone is not a complete refund policy.

An intended outcome is not proof that the product delivers that outcome. If one document says eight weeks and another says twelve, preserve both versions and mark the conflict for resolution. The extractor should make the offer easier to inspect, without silently choosing whichever version sounds more compelling.

Write positioning and tone as separate outputs

The positioning summary connects the evidenced buyer, problem, proposed value and offer. An authored RISER sentence frame is: “For [supported audience] seeking [stated outcome], this offer provides [actual deliverable and mechanism], subject to [known scope and conditions].” Leave missing proof or mechanism details explicit. This sentence frame is an application added for this lesson; it is not part of the original extractor prompt.

The fourth output records notable brand tone or phrases. Describe observable language, such as encouraging instructions or a challenge to conventional advice, and attach a short supporting phrase with its source reference. Do not treat a brand voice as a diagnosis of the writer's personality. Keep original quotations distinguishable from rewritten marketing copy.

Work through the source's complete example

The example avatar is a 35-year-old mother who values time freedom and feels frustrated with the corporate grind. The example product is eight weeks of group coaching priced at $997, with Voxer support. The example voice is warm, encouraging and rebellious. These details are illustrative source data, not verified facts about RISER customers, the RISER offer or the availability of a support service.

In the four-output format, the avatar summary would retain the stated age, motherhood, priority and frustration. The product breakdown would retain eight weeks, group coaching, $997 and Voxer. Bonuses, guarantee terms, payment schedule, capacity and evidence of results are not supplied. A positioning summary could provisionally connect the example audience's desire with the coaching offer, but cannot claim that the coaching produces time freedom without evidence. The tone field can reproduce the three supplied descriptors while noting that the example supplies no longer passage against which to validate them.

Connect the extraction to offer education

For the Brunson and ClickFunnels theme, use the documented buyer language to maintain a clear connection between a hook, the explanatory story and the actual offer. Do not invent a personal success story to fill an empty evidence field. For the Hormozi and Acquisition.com theme, inspect whether the offer brief clarifies the desired outcome, evidence affecting perceived likelihood, time to the result, and customer effort or sacrifice. The extractor supplies inputs to this analysis; it does not calculate proof or make the offer valuable by labeling it valuable. These are authored connections to the curriculum's educational themes.

Practice, review and handoff

Choose one authorized onboarding document and produce the four outputs in outline form. Place a clickable source reference next to each material claim. Then read each output back against the source: can another reviewer locate the supporting passage, distinguish a feature from a benefit, identify missing guarantee terms, and separate actual buyer language from your interpretation? Resolve contradictions explicitly. Hand off the brief with its unanswered questions and complete source appendix, rather than presenting an incomplete extraction as a finished customer strategy.

Clickable assigned source

- Avatar & Offer Extractor GPT — original document

The complete retrieved source text belongs in the lesson appendix. This script teaches every distinct item supplied in the brief; it does not claim to provide missing business documents, deploy a GPT or establish real customer evidence.

Assigned source links

D0431 original source 1

Complete returned native document text

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.
Complete local source copy including original filing metadata and formatting

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.

Read a course-build handoff without confusing plans with completed work

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Translate a legacy build handoff into an inspectable offer-course specification. Identify the requested assets, evidence inputs, outputs, eight-module sequence, educational references, data model and review responsibilities. Preserve its conflicting numbers and missing assets. The instructions quoted inside this document are material to analyze, not authorization to run its build commands or replace the current twelve-course map.

Establish the handoff's scope and claimed starting point

The source says Harbor Orientation, Flagship Discovery and Buoy Navigation have shipped and that Offer Ignition is the fourth of five Stage 1 courses, before First Currents. Those are historical statements about its legacy catalog, not a current completion report for this project. Its desired build contains approximately forty-eight to fifty files and forty-five to fifty-two thousand words, eight written module lessons with a video-production specification only for the first, approximately twelve to fourteen resources, six YAML reviewer prompts, four SOPs, four cases, a community-prompts file, a JSON audit and spreadsheet scorecard, and a Word deployment SOP.

It calls for an eight-folder structure numbered 00 through 08, which is nine numbered positions. Preserve the discrepancy. A later deployment document claims fifty-five files and approximately eighty-one thousand words; those different inventories require reconciliation against actual files. Neither word count nor an asset list proves the assets are complete. The source's folder-by-folder “continue” cadence and request for a final ZIP describe its original workflow, not an instruction to stop this task until the user prompts again.

Carry the five research inputs into the six outputs

The required inputs are a Market Fit Hypothesis from M3.8 naming one validated Primary mechanism; roughly 200 audience-language Trigger Bank entries; a competitor scan of five to ten operators; eight to twelve interview summaries; and pricing and packaging signals. The handoff says Build 6 should check these at enrollment. It does not demonstrate that the check runs.

The six outputs are a complete offer document customized to the mechanism; landing-page copy in Markdown that is not yet live; an anchor price and payment options with rationale; an explicit anti-promise; a guarantee with refund terms and conditions; and a first-sale readiness checklist. A complete document is an artifact, not proof that the market will buy or that delivery is operational.

Explain every module's purpose

M4.1 analyzes what an offer contains beyond the mechanism. M4.2 applies the Grand Slam Offer and Value Equation framework. The handoff's unparenthesized equation is ambiguous: the intended reasoning groups Dream Outcome times Perceived Likelihood above Time Delay times Effort and Sacrifice. This is a conceptual offer lens, not a measured formula for a guaranteed price.

M4.3 creates deliverables and reassembles them into three offer variants. M4.4 evaluates observed pricing bands, an anchor and payment options. M4.5 creates truthful scope and audience exclusions. M4.6 designs conditional or unconditional guarantees with refund terms and sustainable risk reversal. M4.7 creates buyer-language landing-page copy, with emphasis on copy rather than visual design. M4.8 synthesizes a readiness document and first-sale checklist.

The source assigns analysis, understanding and application, creation, evaluation, creation, application, creation and creation to those activities. It estimates forty active hours over four to five elapsed weeks, assumes C3 completion, and uses Stage 1 blue #2E75B6. The inherited eighty-five-minute rhythm cannot supply forty hours on its own; longer working sessions are additional, as the separate time-estimate document clarifies.

Preserve all six doctrines as source policies

The source distinguishes an operator selling a mechanism directly from an agency reselling others' mechanisms, and requires an operator-type offer. That is its program definition, not a universal classification of every agency business. Its 6% Rule means producing three variants in M4.3 and selecting one at M4.8; it supplies no percentage calculation.

Its weekly rhythm allocates ten minutes Monday, fifteen Tuesday, thirty Wednesday, twenty Thursday and ten Friday. Its human-review policy requires peer review of the landing page before readiness. Anti-promise work builds on earlier exclusions. Kill criteria should distinguish an offer needing rewriting from one that should be abandoned in the later capstone. The handoff does not supply the full kill-criteria thresholds, so do not invent a numerical gate.

Keep the six graduation gates and colors in their legacy context

The source lists Territory plus Literacy after C5; Proof Threshold at C10; First Dollar at C14; First $10K Month at C27; First Automated Dollar at C42; and Autonomous Empire at C55. Its six stage colors are Dinghy #2E75B6, Sailboat #3B9EA0, Speedboat #6FA84E, Yacht #BF9000, Mega Yacht #B45F06 and Bora Bora #5B3C88. Preserve the labels, order and hex values as source data. The document's word “authoritative” does not override the user's current twelve-course spreadsheet.

The source's Stage 1 integration expects territory from C1, mechanism candidates from C2, market evidence from C3, the offer draft from C4, and literacy plus first-sale readiness from C5. It later adds identity to this integration description. Completing four of those five legacy course builds would be eighty percent of that stage; it is not eighty percent of the present curriculum.

Maintain every prior-evidence connection

The C1 territory oath constrains audience drift, while operator identity informs voice and delivery. The C2 Mechanism Hypothesis anchors the offer, its Method pillar should be represented accurately, and the naming filter should be reapplied whether the offer inherits a mechanism name or receives a new one. The handoff names a four-pillar discovery framework but does not define all pillars. A separate assigned worksheet defines the five naming tests; the name alone does not establish rights clearance.

The C3 hypothesis grounds the market, the Trigger Bank supplies fifteen to thirty verbatim entries for copy, named competitors inform differentiation, pricing signals inform the band, and interviews inform the structure. Preserve provenance, rights and privacy when handling quotations. Do not fabricate entries or assume a quotation from a private interview belongs on a public page.

Preserve the four case intentions without inventing outcomes

Maya's proposed illustration-licensing case advances The Portfolio-to-Licensing Sprint, with a price grounded in earlier evidence. Darius's engineering case advances The Platform-Transition Reading Club or an alternative if employer-policy friction invalidated it. Priya's fractional-CFO case advances The Series B Readiness Track, possibly repositioned as CEO support after an earlier investigation. These are conditional narrative directions, not verified client results or supplied completed case histories.

The fourth case is the Feature Stuffing Trap: adding bonuses and guarantees when mechanism-market fit is weak. The design note connects it with feelings of uncertainty about moving from intellectual understanding to selling. Name that possible emotional pattern without diagnosing the learner. More features do not necessarily mean less value, but they cannot substitute for checking whether the buyer wants the underlying result.

Attribute the instructional references carefully

The handoff names Alex Hormozi's $100M Offers (2021) for its Value Equation, Grand Slam Offer and guarantee discussion; Russell Brunson's DotCom Secrets (2015) and Expert Secrets (2017) for offer stacking and value-ladder positioning; Jay Abraham's Getting Everything You Can Out of All You've Got (2000) for risk reversal and preeminence; Jeff Walker's Launch (2014) for a sideways-sales-letter reference; Eugene Schwartz's Breakthrough Advertising (1966) for awareness and market sophistication; and Claude Hopkins's Scientific Advertising (1923) for specific claims.

Preserve those as the handoff's bibliographic attributions. The document does not supply the books' full text or evidence for every proposed connection. In particular, its claims that anti-promises build trust or increase conversion should be taught as a RISER synthesis to test, not as a quoted universal law or empirical result proved here. Truthful exclusions help a buyer evaluate fit; actual conversion effects need evidence.

The source calls the page seven sections but lists ten elements: problem, agitation, solution, mechanism, proof, offer, anti-promise, guarantee, urgency and CTA. A separately retrieved preparation checklist groups solution with mechanism and anti-promise with guarantee, producing seven sections without a distinct urgency section. Explain those grouping differences; do not silently drop urgency or fabricate a deadline to fill a slot.

Interpret the eight table placeholders and two functions

The handoff names c4_offer_distinctions, c4_value_equations, c4_offer_decompositions, c4_pricing_decisions, c4_anti_promises, c4_guarantees, c4_landing_page_copies and c4_offer_readiness_docs. Each CREATE TABLE statement contains an ellipsis rather than a full definition. They map the eight activities to proposed storage, but the snippets are not executable migrations.

It names check_c4_enrollment_eligible(user_id) for prior completion and check_c4_completion(user_id) for the eight deliverables. The separately reviewed Supabase C4 schema supplies definitions for those checks and a completion-flag update function. That resolves the absence of definitions in this handoff, while retaining the schema review's limits: stored file IDs and scores do not prove file authenticity, authorized grading or deployed access control. The schema has eight artifact tables plus a review log, so an eight-artifact count is not the entire table count.

Assign the six reviewer responsibilities

The expected version-1.0.0 YAML files are offer-distinction-reviewer for M4.1, value-equation-application-reviewer for M4.2, offer-decomposition-reviewer for M4.3, landing-page-copy-reviewer for M4.7, offer-readiness-reviewer for M4.8 structure, and offer-fit-validator for final offer-mechanism-market coherence. The source assigns the first five to Sonnet and the last to Opus 4.7. Its copy-review requirement includes the seven-section structure and at least fifteen verbatim entries.

Anthropic's Opus 4.7 announcement verifies that model's existence, not that these reviewers are installed, sufficiently evaluated or available in this account. Read the actual rubric files and define human correction routes before separate operational use. No API invocation or course unlock is performed here.

Reconcile quality claims and final packaging instructions

The handoff claims a QM rubric of forty-two standards, ninety-four possible points and sixteen essentials, and explicitly rejects a different set of numbers. Quality Matters' current higher-education rubric description instead identifies forty-four specific standards, with every essential standard and an eighty-five-percent threshold required. An internal 80-of-94 cutoff follows the source's arithmetic but is not verification of its external rubric claim. Official certification requires an official review; the handoff's predicted 92/94 and NOT_CERTIFIED status are unverified internal estimates.

Its final checklist names a C4-build folder, manual use of a qm-audit-tool, build_qm_scorecard.py, a version-2.0 ZIP, and a Word deployment SOP with a ten-section linked table of contents. It gives obsolete environment paths and a proposed BookmarkStart/BookmarkEnd counter workaround for a claimed docx-js bookmark bug. These are historical implementation details to preserve in the appendix, not commands to execute in this workspace or a verified current library defect.

The source predicts fifty-five to ninety-five remediation hours and says seven module videos are missing. A later SOP gives different remediation estimates. Producing specifications alone does not establish accessible media or certification. The quoted final instruction to start a new chat and build folder 00 remains source text, not a task-management instruction.

Apply the handoff as an evidence checklist

For practice, mark each requested asset as located, reviewed, missing or conflicting. Link the actual source when located. Show which offer claim, research record and reviewer supports each deliverable. Use the Brunson/ClickFunnels story-and-offer connection and the Hormozi/Acquisition.com value lens to explain the result clearly, while preserving proof and fulfillment limits. A handoff is successful when another person can distinguish the plan from the verified assets and see the next unresolved dependency.

Clickable assigned source

- C4 Build Handoff — original document

Retain its complete retrieved text, including file paths, quoted instructions, catalog claims and conflicting numbers, in the lesson appendix. Those details are preserved as historical data, not executed or presented as current project status.

Linked resource workshop: prepare, request, deliver and reconcile a peer review

The six linked documents supply the practical peer-review material referenced by the offer-course plans. They are legacy templates and operating proposals, not evidence of a currently staffed RISER service. Read them together: the preparation checklist establishes inputs, outreach scripts coordinate people, the review template structures feedback, the SOP sequences work, alternate protocols address missing capacity, and the paid-review reference describes proposed selection rules. No message, booking, payment or scholarship request is sent by this workshop.

Prepare all eight checklist groups

Group A requires the named landing-page file and seven sections in order: Problem, 200–400 words; Agitation, 150–300; Solution-and-Mechanism, 300–500; Proof, 200–400; Offer, 300–500; Anti-Promise-and-Guarantee, 250–400; and CTA, 50–150. The individual ranges sum to 1,450–2,650, while the required total is 1,800–2,500. Both conditions can be satisfied, but one does not automatically imply the other. These are template targets, not proof that a page of that length will convert. Compared with the handoff's ten-element list, two pairs are grouped and urgency has no separate heading; explain relevant truthful timing without inventing scarcity.

Group B requires a named Trigger Bank Provenance Log, at least fifteen entries, exact source wording, a TB identifier or interview reference, and distribution across at least four page sections. Matching fifteen quotations is not a substitute for the full bank's evidence quality. Keep permissions, confidentiality and attribution appropriate to the destination.

Group C compares the page's exclusions with M4.5 and its guarantee with M4.6. Softening must be reverted or justified in the record; added guarantee stacking should be removed under this template's policy. Both integrity signatures are required. Group D checks the tested offer name, one visible price rather than a hidden range, payment options, engagement model, duration, cadence and no more than eight deliverables. A signature and a count are structural checks, not proof of truthfulness or viability.

Group E asks for specific named or appropriately anonymized evidence, an explicit known-weakness acknowledgment when there are fewer than four named cases, and attributed, exact testimonials. Do not invent a fourth case or disclose an identity to meet a template. Group F requires a specific action, actual enrollment or cohort timing, a qualification process if applicable, and a real pre-purchase contact. Group G requires reading the page aloud, removing phrases the operator would not say, checking unsupported hyperbole, and avoiding the source's four low-substance phrases: “game-changer,” “revolutionary,” “transform your life,” and “all you need to do is.” These are editorial preferences, not a comprehensive truthfulness test.

Group H prepares links to the page and provenance log, two or three positioning sentences, a request for two template-based reviews within seventy-two hours, and specific availability to reciprocate. The checklist's fifteen-to-twenty-minute estimate and claimed thirty-to-sixty-minute reviewer saving are unverified assumptions.

Its five common fixes are to restore softened terms; add three to six genuine missing quotations, often in problem and agitation; examine excess deliverables for unnecessary padding; show the actual price in the offer section; and use a forty-eight-hour reread to repair unnatural voice. Add only what is genuinely missing rather than assuming three extra quotes always reaches fifteen. After submission, check reviewer pickup daily, answer questions, keep the reviewed version stable and begin reciprocating. The stable-version rule prevents two reviewers evaluating different drafts.

Use the six coordination scripts as templates, not automatic messages

The request script identifies the operator, tested offer name, buyer, price and one or two suspected weaknesses. It links the page, provenance log and any existing Revision Log, proposes seventy-two hours, and states specific days for reviewing the first two reciprocal requests. Naming a focus may help, but the claim that it reliably improves feedback is not established by data here.

The acceptance script names the requester, confirms the chosen focus or full-template review, and gives a specific delivery date and time, aiming for forty-eight hours. That is shorter than the general seventy-two-hour target; state which commitment was actually made. The decline script explains capacity if useful, refers to a genuinely available person, and points to alternate review options. Do not tag someone or promise mentor capacity without knowing it exists.

The delivery script links the completed template, gives one overall observation and three recommended revisions, and offers optional asynchronous discussion. The response script addresses every recommendation as incorporated, incorporated with modification, or not incorporated with a reason, then links the Revision Log. The escalation script identifies the pacing window, requests and responses, attempted alternate routes, specific help needed, page link and revised timeline. The source routes it to a mentor channel or a welcome-email Calendly link, neither of which is supplied as a verified current contact.

The etiquette section favors reciprocity, precise observations, honest criticism and timely responses. Its example contrasts generic praise with identifying performative “wasted years” wording in a particular paragraph. Be candid and respectful; honesty does not require harshness. The source calls reciprocity a culture norm rather than enforced policy. It encourages personal voice especially in request and delivery scripts, with logistics scripts closer to their templates. Claims that personal voice correlates with better responses or missed SLAs are the largest disruption cause are source assertions, not measured findings here.

Complete the entire review template

Read the page and provenance log together, looking for buyer-language fit, quotations that support specific claims, and exclusions or guarantees weakened during copywriting. The source estimates forty-five to sixty minutes and a seventy-two-hour request-to-delivery target. Record reviewer name, reviewer archetype, date, submitting operator and offer name. The task is structural feedback, not rewriting every line.

Rate each section strong, adequate or weak. For Problem, restate the problem in one sentence, assess whether the buyer's state is vivid or generic, and whether at least one quotation is meaningful, then add one to three specific observations. For Agitation, distinguish real, mixed and performative consequences and identify any supporting numbers, timeframes or opportunity costs. Do not manufacture emotional pressure or unsupported losses.

For Solution-and-Mechanism, explain the mechanism in your own words and check whether its four referenced pillars are visible; missing pillar definitions remain a separate dependency. For Proof, distinguish specific, mixed and generic cases and check whether limited evidence is honestly acknowledged. For Offer, inspect the name, visibility of price and concrete delivery experience—what happens, when and with whom.

For Anti-Promise-and-Guarantee, rate the two parts separately. Count three or more genuine exclusions, two, or one or fewer. Identify disguised flattery such as “not for unmotivated people.” Compare one primary guarantee plus an optional complementary element with borderline or three-plus-component stacking. Consider whether stated claim conditions appear understandable and realistically usable, without treating component count as a conclusive legal or ethical judgment. For CTA, check a specific action, outcome and actual timeline. The source's February 12 enrollment and twenty-four-hour welcome-kit example is fictional illustration, not a current date or promise.

Across the whole page, sample three quotations against provenance and classify them as exact, slightly paraphrased or significantly paraphrased. Record overall strong, mixed or weak provenance, but recognize that a three-quote sample cannot verify every quotation. Assess buyer versus operator voice, then count all fifteen required entries. Give three actionable revisions—for example, shortening a particular four-sentence opening to two—rather than an abstract request to improve copy. Close with ready, moderate revision or substantial revision, a hypothetical yes/maybe/no buying reaction with reasons, and a signature. A peer's hypothetical buying reaction is not an actual purchase or validation result.

Follow the SOP's sequence, roles and timing

The SOP requires the page draft, provenance log, completed preparation checklist and a forty-eight-hour cooling period. Its seven roles are the submitting student, two peer reviewers, mentor, cross-stage reviewer, paid reviewer and proposed Build 6 coordinator. The source assigns automated notifications, matching, tracking and gates to Build 6; those operations have not been verified or deployed here.

Step one is a twenty-minute self-audit of checklist groups A–H, quotations and unchanged terms. Missing provenance, fewer than fifteen entries or softened exclusions cause rework; the source's twenty-four-to-forty-eight-hour delay estimate is illustrative. Step two is a fifteen-minute request using the structured script, both document links, suspected weaknesses, the review target and reciprocal availability. Vague requests and missing attachments should be fixed before relying on a review.

Step three allows twenty-four to forty-eight hours for pickup and requires two commitments with delivery dates. The SOP activates alternatives when fewer than two commit within forty-eight hours, whereas the separate alternate document uses seventy-two hours without response. Keep that conflict visible. Reviewers should communicate a threatened deadline instead of missing it silently.

Step five allocates thirty minutes to reading both completed reviews together before acting. Capture common themes and disagreements, then allow the SOP's suggested twelve-hour gap before revision. Two reviewers agreeing is a reason to investigate, not proof that their judgment is correct. Step six allocates sixty to ninety minutes to decisions in the Revision Log and the revised page. Record every recommendation and its disposition; do not accept all feedback mechanically or omit disagreement silently.

Step seven budgets ninety to 120 minutes for two reciprocal reviews, forty-five to sixty each, using the template and delivery script. Discuss actual capacity instead of treating an access need as bad faith. Step eight budgets five minutes to submit and five for the proposed AI run. It requires page, provenance and revision logs, a score of at least seven out of ten and no integrity flags. Its activities say review count at least two, while its quality gate says exactly two. An implementation must reconcile that difference and distinguish review credits from actual people; it must not fabricate a second reviewer when one mentor review counts as two credits.

Apply alternate routes with explicit review credit

Use alternatives when fewer than four people are active at compatible pacing, no response arrives within the stated window, or the student is ahead or behind the cohort. The alternate document proposes escalation within seventy-two hours of draft completion if no route is viable, which can conflict with longer windows below. Define the applicable clock before promising completion.

Protocol A proposes a forty-five-minute mentor call, with the draft and provenance log submitted at least twenty-four hours beforehand. A completed written template counts as both required review credits. The alternate document gives seventy-two hours typically and ninety-six worst case, at no charge; the SOP separately describes twenty-four hours from activation and delivery within seventy-two. These are conflicting source service assumptions, not verified current support. A mentor backlog of two or more weeks is the stated reason to try B.

Protocol B requests one or two volunteer Stage 2-or-higher reviewers, naming archetype, territory, offer, a ninety-six-hour target and both document links. It mentions Stage 2, 3, 4 and 5+ volunteers, no charge and reciprocal ecosystem credits. One cross-stage review may count as two credits or be paired with another review under the source policy; record the chosen interpretation. The SOP limits one description to Stages 2–5. If no one picks up within forty-eight hours, the source points to C. Experience may be useful, but it does not guarantee a superior review.

Protocol C is a direct paid engagement when A and B are unavailable in the planned week. The Academy is not described as handling payment. A paid review counts as only one credit and needs a peer, mentor or cross-stage counterpart. The source's typical price is $150–$400 and turnaround forty-eight to seventy-two hours by contract; the roster's A1 range reaches $450. Preserve that discrepancy. It also proposes that waiting three to five extra days for an unpaid route may be preferable. No paid service is recommended as currently available or purchased here.

The scholarship provision names the unverified legacy address [[email protected]](mailto:[email protected]), a specific scholarship-request subject, page link, pacing dates and attempted routes. It proposes a forty-eight-hour reply and one review covered up to $200 if approved. This is not a current verified service, funding commitment or permission to send a message. The protocol log records route, actual reviewer names, dates and one or two rationale sentences. Its shorthand for C omits a peer as the counterpart despite the prose allowing one; preserve and resolve that inconsistency.

Evaluate the paid-review reference without inventing a roster

The five proposed selection criteria are at least twenty relevant prior page reviews, familiarity with mechanism-based offers, respect for truthful exclusions, a signed methodology agreement and useful ratings from at least five reviewees. The document contains placeholder slots, not current names or contact details, so it does not establish that any provider is actually vetted or available.

Tier A describes ten-plus years of experience: A1 at $350–$450 with seventy-two hours for coaching, consulting and Teacher/Service work; A2 at $300–$400 with forty-eight to seventy-two hours for productized services and Builder work. Tier B describes five to ten years: B1 at $200–$275 with forty-eight to seventy-two hours for Creative work; B2 at $175–$250 with seventy-two hours for B2B, platforms and Systems work. Tier C describes five rotating Stage 2+ alumni slots at $150–$200 with forty-eight to seventy-two hours and archetype matching. All numbers and availability claims are historical template data, not current quotations.

Its five engagement steps are to find the actual current roster, match relevant expertise, provide the draft and provenance log with the required template, explain the methodology baseline, and log the engagement. The baseline preserves mechanism, exclusions and guarantee honesty while requesting critique within that approach. A reviewer should still flag unsupported or unsuitable commitments; methodology must not become a reason to ignore valid criticism.

The source excludes unlisted general review services, disparages low-cost marketplace reviews, rejects AI-only tools as a substitute for required human review, and disallows unlisted paid reviewers for credit. Preserve these as program-policy proposals. Blanket claims about a marketplace's quality are unsupported; assess the actual reviewer. The four methodology conflicts are removing exclusions, adding guarantee stacks, replacing exact quotations, and drifting from the Primary mechanism. Consult the designated reviewer or mentor rather than automatically adopting or rejecting advice solely because it is paid.

The four proposed removal triggers are three or more materially disruptive reports, missing at least twenty percent of quarterly deadlines, an agreement violation such as using review time to upsell, or leaving the field/not renewing the agreement. The document proposes quarterly updates, thirty days' notice and possible later re-entry. These are not actions taken against any person.

Review the process itself

After a cohort, examine the proportion using each route, median request-to-delivery time, the proportion meeting deadlines without escalation, and the proportion of paid feedback conflicting with the stated methodology. The SOP proposes revisiting capacity above thirty-percent mentor substitutions, agreements or roster choices above twenty-percent paid conflicts, and cohort discussion below a 0.85 given/received ratio. These are proposed thresholds, not validated universal benchmarks.

Its additional escalation triggers are three or more failed submissions by one student, fabrication or conflicting reviewer feedback requiring agreement review, an individual reciprocity ratio below 0.5 across two cohorts, and more than three consecutive weeks of thin participation prompting a recruitment review. Define denominators and review evidence before acting. The source's promise that a validator will not penalize alternate routes needs actual implementation verification.

The practical output is a stable reviewed draft, genuine feedback, a decision log, correctly recorded review credits and explicit unresolved issues. Connect Brunson/ClickFunnels message continuity with the Hormozi/Acquisition.com value lens: review whether the promise, evidence, exclusions and delivery agree. Do not mistake template completion, agreement between two reviewers or a numerical score for proof of buyer demand.

Clickable linked resources

- Preparation checklist - Six outreach and response templates - Peer-review coordination SOP - Complete review template - Alternate protocols - Paid-review reference with placeholder roster

Preserve all six complete originals in the applicable lesson appendices. Their dates, templates and embedded operational instructions remain source material, not current service promises or actions executed by this task.

Supporting schema: complete reviewed teaching

Trace the offer curriculum through its database schema

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source boundary

Explain how each proposed C4 artifact is stored, what its checks actually enforce and where review or application controls are still needed. This is the complete version 2.0 schema dated April 24, 2026, written for the operator or developer deploying or auditing Build 1. It depends on the C1, C2 and C3 schemas and their referenced tables. This lesson reviews its SQL as source material; it does not execute migrations or claim a deployed database.

The schema separately supplies the `c4_value_equations` table named in D0404. That resolves the earlier lack of an accompanying table definition in the worksheet's own file. The separately assigned D0413 supplies its reviewer rubric. Both are now accessible references; actual submission storage, grading and unlocking remain unverified.

Understand the shared record structure

There are eight artifact tables and one review-log table. Each receives a UUID primary key with a generated default and a required user_id referencing public.users; deleting that user cascades to these rows. Artifact rows have a filed_at timestamp defaulting to now, while the log has ran_at. A default is not the same as a required value: the source does not mark every timestamp NOT NULL.

The distinction table is unique by user and memo file, allowing multiple distinct memo files per user. The other seven artifact tables are unique by user alone, so they represent one row per user unless another history mechanism exists. The review log permits multiple events. User indexes support lookup; the log uses a combined user-and-module index. File IDs point to external Drive artifacts; storing an ID does not verify the file's contents, permissions or authenticity.

M4.1: offer distinctions

`c4_offer_distinctions` requires the distinction memo's Drive file ID, component inventory file ID, a zero-to-ten AI rubric score and the Primary mechanism name. An optional foreign key points to the C3 market-fit hypothesis. Its stored generated passed value is true when the score is at least seven. The row records which mechanism and files were assessed; the schema does not itself read those files or prove the score came from an authorized reviewer.

M4.2: the value equation

`c4_value_equations` requires the worksheet file ID, strongest and weakest variable names, citation counts and score. Four optional strength columns accept Strong, Moderate or Weak for dream outcome, likelihood, time and effort. The strongest and weakest fields accept the four full variable names, but no constraint requires them to differ. Trigger-bank citation count must be at least three, interview count at least one and score zero to ten. Passed is generated from score at least seven.

These checks validate declared counts and allowed labels, not the quotations or all per-section evidence required by D0404 and D0413. The four strength fields can be null because an allowed-value CHECK does not make a column mandatory. The worksheet's richer diagnosis and the actual grading rubric remain necessary.

M4.3: decomposition and three variants

`c4_offer_decompositions` stores decomposition and variants file IDs, a total decomposed-deliverables count from six to ten, three variant definitions and a required structural-verification flag. Each A, B and C variant has a required name, engagement model, duration in weeks and deliverable count, plus optional lower and upper price bands. Engagement model is Cohort, 1:1, Self-paced or Hybrid. Each variant's deliverable count may not exceed eight.

Three pairwise checks compare A with B, A with C and B with C. Every pair must differ in engagement model, duration or deliverable count. Changing price or name alone does not satisfy them. These are the actual database tests; deeper assessment of meaningful difference belongs to the named offer-decomposition reviewer. The source's design note says the maximum-eight rule guards against feature stuffing, but a count cannot assess whether the retained deliverables are useful.

The SQL does not require positive duration or a positive minimum variant count, nor does it order or validate positive price-band endpoints. A stored structural_verification_passed flag is supplied, not computed from all qualitative criteria. Keep these limits visible rather than treating acceptance by the table as full validation.

M4.4: pricing decisions

`c4_pricing_decisions` requires a pricing-decision file, observed floor, median and ceiling, a positive anchor price, a pricing strategy and a pay-in-full price. Strategies are Median, Above Market, Below Market (Volume) or Other. Optional fields store installment and deposit descriptions, hours per buyer, effective hourly rate and rationale for deviation from the observed band. Score is zero to ten; at least seven generates passed.

The table can preserve the comparison and unit-economics assumptions, but it does not enforce floor ≤ median ≤ ceiling, positive pay-in-full price or coherent hours and effective rate. Nor does it independently validate the competitor observations. Explain the rationale and evidence in the linked artifact before treating the price as justified.

M4.5: anti-promises and integrity

`c4_anti_promises` requires anti-promise and integrity-statement file IDs, three to six audience exclusions, at least two outcome non-claims and at least two scope boundaries. The required signature Boolean defaults to false. A zero-to-ten score of at least seven and a true signature flag jointly generate passed. This records the boundary and signature assertion; a Boolean by itself is not a verified signature or an enforceable agreement.

M4.6: guarantees

`c4_guarantees` stores the guarantee and honesty-clause file IDs, a required signature flag defaulting false, guarantee type, component count, target weakness, sustainability flag and score. Types are Refund, Outcome, Hybrid, Time-shift and Effort-adjusted. There may be at most two components. The target must be Perceived Likelihood, Time Delay or Effort and Sacrifice. Expected activation percentage is optional. Passed requires score at least seven and a signed-clause flag.

The source records unit_economics_sustainable but does not include it in the generated pass condition. It also does not constrain the percentage to zero through one hundred or require a positive component minimum. Therefore, a row can satisfy the coded pass condition without establishing a sustainable guarantee. The written terms, evidence and authorized review still matter.

M4.7: landing-page copy

`c4_landing_page_copies` requires the page and provenance-log file IDs, permits a revision-log ID, limits total words to 1,000–5,000 and requires at least fifteen claimed Trigger Bank entries. It separately stores the number verified verbatim. Two optional reviewer IDs reference users, each paired with an optional completion timestamp. peer_reviews_complete is generated from the presence of both timestamps.

Passed requires an AI score of at least seven, both review timestamps and at least fifteen verified verbatim entries. The AI score is optional but, when present, constrained to zero through ten. Depending on null inputs, the Boolean expression can produce null rather than false; the completion function counts only passed = TRUE.

No shown constraint requires different reviewers, prevents self-review, ensures reviewer IDs accompany timestamps or ensures verified counts do not exceed claimed counts. The application and reviewer process must establish that the review and evidence are real. A generated Boolean protects its expression from direct assignment; it does not make owner-supplied inputs trustworthy.

M4.8: offer readiness

`c4_offer_readiness_docs` requires readiness and first-sale-checklist file IDs, selected variant A/B/C, final offer name and final anchor price. Signature defaults to false. The optional Opus validator verdict is PASS, NEEDS_REVISION or FAIL, with an optional run timestamp. At least three kill criteria must be declared. Passed requires a PASS verdict and a true signature flag.

This captures the intended final review gate. A Sonnet result elsewhere does not satisfy this explicit Opus-verdict field. However, the field does not authenticate which model or person produced its value, the anchor price is not constrained positive here, and the table stores a kill-criteria count rather than the criteria themselves. The linked artifact and trusted review process remain essential.

Review history and user summary

`c4_review_log` stores user, module M4.1 through M4.8, prompt name, version, required submission count defaulting to one, verdict PASS/FAIL/NEEDS_REVISION, optional integer score, feedback JSON, flags JSON and run time. Its score has no zero-to-ten constraint and submission count has no positive check. Preserve these differences rather than assuming the log has the same validation as every artifact.

The user table gains five columns: completion Boolean defaulting false, completion timestamp, lead variant, final offer name and final anchor price. These are summary fields populated by the shown trigger; their existence alone does not prove current eligibility or completion.

Enrollment eligibility: what is actually checked?

`check_c4_enrollment_eligible` accepts a user ID and returns JSON containing eligible and a missing-items list. It requires C3 complete, a market-fit hypothesis filed within the previous three months, a Trigger Bank with at least 200 entries, a Pricing Signals row and an oath signed within the previous twelve months. The hypothesis uses a strict newer-than boundary; the oath is rejected when missing or older than its boundary.

The function selects C1 completion, C2 completion and operator-identity filing but does not test them. It checks that Pricing Signals exists, not its quality or recency, and it does not validate every dependency named in the worksheet. These are differences between data read, conditions enforced and the broader educational prerequisites.

Completion checks and trigger behavior

`check_c4_completion` returns complete plus missing items after checking all eight artifact stages: distinction passed; equation passed; decomposition structural verification true; pricing passed; anti-promise passed; guarantee passed; landing page passed; and readiness passed. The named missing items retain the expected signature, peer-review and Opus context because those are part of the relevant table expressions.

`update_c4_complete_flag` calls that check for NEW.user_id. When complete, it reads the passing readiness row and sets the user completion flag true, stamps the current time and copies the selected variant, offer name and anchor price. Its trigger runs only after an insert or update to the readiness table when NEW.passed is true.

That means completing another artifact after readiness already passed does not automatically invoke this trigger. Neither deleting supporting evidence nor changing a prior result to failure resets completion through this code. The function only sets true and has no false branch. Repeated qualifying readiness updates can also restamp completion time. These are observations from the supplied SQL, not evidence that a live system currently behaves this way. A production design must decide how to re-evaluate changes and revocations.

Access controls and implementation limits

All nine tables enable row-level security. The eight artifact tables allow selecting, inserting and updating rows belonging to auth.uid(); no DELETE policy is shown. The review log permits owners to select their history, but its insert policy uses WITH CHECK (TRUE) without a TO role restriction. The adjacent service-only comment is not an access restriction. Actual access also depends on grants and runtime roles, which this file does not show.

Likewise, owner-based row access is not field-level grading authority. If ordinary users have the corresponding write grants, these policies do not stop them changing their own scores, verification flags or signature assertions. Review provenance and privileged fields need a defined trusted boundary before this can be treated as an authoritative completion system.

The eligibility and completion functions use SECURITY DEFINER and accept arbitrary user IDs. The shown definitions contain neither a caller-to-user authorization check nor an explicit secure search_path. Supabase's documentation explains the need to secure such functions and their execution permissions. Review those controls and actual grants before implementation; do not infer protection from schema-qualified table names alone.

Migration and operating references

The supplied migration sequence runs c1_schema.sql, c2_schema.sql, c3_schema.sql and then c4_schema.sql using psql with host, user and database placeholders. Reading this sequence does not execute it. Tables use IF NOT EXISTS and the five user columns use ADD COLUMN IF NOT EXISTS, but separate index, policy, constraint and trigger creation statements are not all guarded. The complete file therefore is not automatically safe to rerun unchanged.

The source names five related paths or integrations: RISER-Build-References-for-C4.md, C4-Review-Chain.md, C4-Prerequisites-Checklist.md, Build 6 src/c4_checkpoint_handler.ts and RISER-C4-Weekly-Rhythm-Setup-SOP.md. Their implementation and deployment are not supplied by this schema. Preserve the full SQL, comments, design notes and migration references in the appendix.

Apply the educational connection

This design attempts to turn Hormozi-style offer analysis into traceable artifacts before a Brunson-style offer presentation is finalized. The value of the database is provenance and accountable review, not merely a green completion flag. As authored practice, trace one worksheet from its file ID through cited evidence, rubric score, authorized review and downstream completion. Mark every unverified dependency and every condition the code does not enforce. Deliver a schema-to-artifact map and a review of those gaps; no database deployment is part of this lesson's completion.

Sources and resources

- Complete assigned C4 schema. - D0404: Value Equation Worksheet and D0413: actual reviewer YAML. - PostgreSQL constraints and CREATE POLICY: primary constraint and policy semantics. - Supabase row-level security and database functions: primary access-control references. - Acquisition.com value-equation checklist, ClickFunnels value ladder and RISER NATION CORP.

Assigned source links

D0432 original source 1

Complete returned native document text

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

C4 Build Handoff — RISER Nation Maritime Academy
Context
I'm continuing a multi-session build of the RISER Nation Maritime Academy. Three courses are complete and shipped (C1 Harbor Orientation, C2 Flagship Discovery, C3 Buoy Navigation); I'm now starting C4 Offer Ignition (Stage 1, course 4 of 5, offer architecture and first sellable asset).
What to build for C4
Full C1/C2/C3 parity build:
~48-50 files, ~45-52K words
8-folder structure (00_Course-Overview through 08_Community-Prompts)
8 module lessons (M4.1-M4.8), written lessons for all + video production spec for M4.1 only
~12-14 resources (templates, worksheets, frameworks, checklists)
6 Claude system prompts in YAML (5 Sonnet + 1 Opus for the course-completion validator)
4 SOPs (YAML+markdown format)
4 case studies: continue Maya/Darius/Priya narratives from C1+C2+C3, plus 1 new C4-specific failure case
1 community prompts file
QM audit (JSON + xlsx scorecard using the audit tool)
Deployment SOP as Word doc, same format as C1/C2/C3 SOPs already shipped
Same cadence as prior courses: build folder-by-folder, I'll say "continue" when context fills, ship zip + scorecard + deployment SOP at the end.
C4 Offer Ignition scope
Course position: Stage 1, course 4 of 5. Sits between C3 (validated Primary mechanism + full Trigger Bank + competitor scan) and C5 (First Currents / AEO Literacy — the Stage 1 capstone).
Inputs from C3 (all referenced by Build 6 at C4 enrollment):
Market Fit Hypothesis document from M3.8 with single validated Primary mechanism
Full Trigger Bank (~200 audience-language entries) — C4 uses these for offer copy
Competitor scan (5-10 operators analyzed) — C4 uses for positioning differentiation
8-12 customer interview summaries — C4 uses for offer structure decisions
Pricing and packaging signals — C4 uses for price band selection
Outputs to C5:
A complete sellable offer document (Hormozi-style Grand Slam Offer, customized to mechanism)
Offer landing page copy (not yet live — copy in markdown ready for deployment)
Pricing decision with rationale (anchor price + payment options)
Anti-promise statement (what the offer explicitly does NOT do/promise)
Guarantee structure (refund terms, conditional guarantees)
First-sale readiness checklist (what must be true before asking for money in C5)
Stage 1 graduation gate contribution: C4 is the "Offer Ignition" course. C5 graduation requires territory chosen (C1), mechanism candidates named (C2), market scanned (C3 output), offer drafted (C4 output), AEO literacy and first-sale readiness (C5). C4 is 4 of 5.
Proposed C4 Module Map (8 modules)
M4.1 — Offer Architecture Foundations (the offer is not the mechanism; what an offer contains that a mechanism doesn't) — Analyze
M4.2 — The Grand Slam Offer Framework (Hormozi's Value Equation adapted to RISER context: Dream Outcome × Perceived Likelihood ÷ Time Delay × Effort & Sacrifice) — Understand + Apply
M4.3 — Offer Deconstruction and Reassembly (take the Primary mechanism, decompose into deliverables, reassemble into saleable offer) — Create
M4.4 — Pricing and Anchoring (price band selection using C3 pricing signals; anchor price; payment options) — Evaluate
M4.5 — The Anti-Promise Statement (what the offer explicitly does NOT do; who the offer is NOT for) — Create
M4.6 — Guarantee Architecture (conditional vs unconditional; refund terms; risk reversal without unit economic damage) — Apply
M4.7 — Offer Landing Page Copy (copy-based, not design-based; Trigger Bank-sourced language; 7-section structure) — Create
M4.8 — Offer Readiness Document (synthesis artifact for C5; first-sale readiness checklist) — Create
Time: ~40 hours active / 4-5 weeks elapsed (slightly shorter than C3 because work is internal writing rather than external research) Prerequisite: C3 complete with Market Fit Hypothesis filed Stage color: Maritime Blue #2E75B6 (Stage 1)
Critical Doctrines (unchanged, apply to C4)
Operator-vs-Agency (from C1): an operator sells their mechanism directly; an agency resells others' mechanisms. C4's offer must be operator-type, not agency-type.
6% Rule applied in C4 as "draft 3 offer variants before committing to one" — M4.3 produces 3 offer decomposition variants; M4.8 selects one for shipping
85-Minute Rhythm continues (Mon 10m / Tue 15m / Wed 30m / Thu 20m / Fri 10m)
HITL mandatory — Build 6 requires peer review of offer landing page copy before unlocking M4.8
Anti-promise discipline from C1 M1.3 / C2 M2.4 / C3 culminates in M4.5's explicit Anti-Promise Statement
Kill criteria continue — M4.8 specifies conditions under which the offer gets rewritten vs. scrapped in C5
Stage Graduation Gates (authoritative, unchanged)
S1→S2 Territory + Literacy (after C5) · S2→S3 Proof Threshold (C10) · S3→S4 First Dollar (C14) · S4→S5 First $10K Month (C27) · S5→S6 First Automated Dollar (C42) · S6 Autonomous Empire (C55)
Rubric Numbers (use consistently)
QM HE Rubric 7th Edition V2.0: 42 SRS · 94 max points · 16 Essential Standards · 85% threshold = 80+ points
NOT 44/101/22/86 — corrected from original C1 audit. The QM audit tool at /mnt/user-data/outputs/qm-audit-tool/ uses the correct numbers.
Maritime Color Scheme
S1 Dinghy 2E75B6 · S2 Sailboat 3B9EA0 · S3 Speedboat 6FA84E · S4 Yacht BF9000 · S5 Mega Yacht B45F06 · S6 Bora Bora 5B3C88
Cross-References C4 Must Maintain
To C1:
Captain's Oath Clause 1 (territory) — offer must serve stated territory, no drift
Operator Identity — offer's voice and structure match operator archetype (Teacher-Operator offers differ from Service-Operator offers)
85-Minute Rhythm continues
To C2:
Mechanism Hypothesis Document — offer is built on the Primary mechanism selected
4-Pillar Mechanism Discovery Framework — offer's Method section restates the mechanism's Method pillar
5-Test Naming Filter — offer's name may inherit mechanism name OR produce new offer-specific name (re-apply 5-test)
To C3:
Market Fit Hypothesis — offer addresses validated market, not theoretical one
Trigger Bank — offer copy uses audience's actual language; M4.7 landing page copy pulls 15-30 Trigger Bank entries verbatim
Competitor scan — offer positioning differentiates from named competitors explicitly
Pricing signals — offer price band informed by observed market, not arbitrary
Customer interviews — offer structure reflects what interviewees actually said they'd buy
Cross-case narrative continuity (from C1+C2+C3):
Maya — illustrator licensing — advancing "The Portfolio-to-Licensing Sprint"; C4 produces her first sellable offer at a price band validated in C3
Darius — platform engineering — advancing "The Platform-Transition Reading Club" (or an alternative if C3 killed it via employer-policy friction); C4 offer reflects C3 findings
Priya — fractional CFO — advancing "The Series B Readiness Track" (likely repositioned as CEO-support per her C3 M2.8 KC1 investigation); C4 offer incorporates repositioning
New C4 failure case: working title "The Feature Stuffing Trap" — student keeps adding bonuses and guarantees to the offer hoping to overcome a weak mechanism. Classic failure: fixing an offer problem when the real issue is mechanism-market fit. Connects back to C3 signals the student ignored.
Instructional References for C4 Content (use these, cite correctly)
The offer course builds on established direct-response methodology. Cite with attribution in relevant lessons:
Alex Hormozi — $100M Offers (2021) — Value Equation, Grand Slam Offer structure, guarantee stacking. Core framework for M4.2.
Russell Brunson — DotCom Secrets (2015) + Expert Secrets (2017) — offer stacking, value ladder positioning
Jay Abraham — Getting Everything You Can Out of All You've Got (2000) — risk reversal, preeminence positioning
Jeff Walker — Launch (2014) — sideways sales letter structure for landing page copy (M4.7)
Eugene Schwartz — Breakthrough Advertising (1966) — market sophistication levels, awareness levels for M4.7 copy framing
Claude Hopkins — Scientific Advertising (1923) — specificity in claims, anti-promise as credibility mechanism
M4.7 landing page structure draws from proven direct-response patterns: problem → agitation → solution → mechanism → proof → offer → anti-promise → guarantee → urgency → CTA.
Supabase Schema Additions C4 Needs (draft for 04_Tools-and-Infrastructure)
sql
-- M4.1 Offer/Mechanism distinction
CREATE TABLE c4_offer_distinctions (...);

-- M4.2 Value Equation application
CREATE TABLE c4_value_equations (...);

-- M4.3 Offer decomposition variants (3 variants required, per 6% Rule)
CREATE TABLE c4_offer_decompositions (...);

-- M4.4 Pricing decision
CREATE TABLE c4_pricing_decisions (...);

-- M4.5 Anti-Promise Statement
CREATE TABLE c4_anti_promises (...);

-- M4.6 Guarantee architecture
CREATE TABLE c4_guarantees (...);

-- M4.7 Landing page copy
CREATE TABLE c4_landing_page_copies (...);

-- M4.8 Offer readiness (course completion artifact)
CREATE TABLE c4_offer_readiness_docs (...);
Build 6 function: check_c4_enrollment_eligible(user_id) queries C3 completion state. check_c4_completion(user_id) verifies all 8 C4 deliverables present.
Expected Claude System Prompts (6 total)
offer-distinction-reviewer-v1.0.0.yaml (M4.1, Sonnet) — validates student can distinguish offer from mechanism
value-equation-application-reviewer-v1.0.0.yaml (M4.2, Sonnet) — validates Value Equation applied correctly across 4 variables
offer-decomposition-reviewer-v1.0.0.yaml (M4.3, Sonnet) — validates 3 distinct decomposition variants produced
landing-page-copy-reviewer-v1.0.0.yaml (M4.7, Sonnet) — validates 7-section structure present + minimum 15 Trigger Bank entries used verbatim
offer-readiness-reviewer-v1.0.0.yaml (M4.8, Sonnet) — structural validation
offer-fit-validator-v1.0.0.yaml (M4.8, Opus 4.7) — course-completion gate; validates offer-mechanism-market coherence; highest-stakes prompt
Final Deliverables Checklist (for the build)
/home/claude/C4-build/ with 8 folders fully populated (~48-50 files, ~45K words)
Run QM audit using /mnt/user-data/outputs/qm-audit-tool/ — apply the rubric manually (matching earlier courses' approach since can't call API), produce QM-Audit-C4.json + QM-Audit-C4-Scorecard.xlsx using build_qm_scorecard.py
Zip at /mnt/user-data/outputs/C4-Offer-Ignition-v2.0.zip
C4-Offer-Ignition-Deployment-SOP.docx in same format as C1/C2/C3 SOPs — 10-section populated TOC using BookmarkStart/BookmarkEnd with unique IDs from module-level counter. The docx-js Bookmark class has a bug where all bookmarks get linkId=1; use the shared helper at /home/claude/sop-split/shared.js (if still present in environment) or recreate with the same pattern.
Expected Outcome
C4 audit will likely score similarly to C1/C2/C3: ~92/94 (97.9%) with NOT_CERTIFIED blocked by SRS 8.3 (M4.2-M4.8 video specs not produced, only M4.1). ~55-95 hours of v2.1 remediation to reach CERTIFIED.
Catalog Progress
C1 Harbor Orientation ✓ shipped
C2 Flagship Discovery ✓ shipped
C3 Buoy Navigation ✓ shipped
C4 Offer Ignition — building now
C5 First Currents — Stage 1 capstone; final course of Stage 1
After C4 completes, Stage 1 will be 80% built (4 of 5 courses), with C5 as the capstone that tests territory + identity + mechanism + market + offer integration + first-sale readiness.
One C4-Specific Design Note
C4 is where most students first encounter the gap between "intellectually understanding the mechanism" (C2 output) and "being able to sell it" (C4 output). This is the course where imposter-syndrome-adjacent feelings surface strongly. The failure case study (The Feature Stuffing Trap) addresses this directly — students who feel uncertain about the mechanism often try to overcome it by adding bonuses and guarantees, which dilutes rather than strengthens the offer. Handle this with care in the written lessons; name the emotional pattern explicitly.
The M4.5 Anti-Promise Statement module is counterintuitive for many students — they've been taught that marketing means positive claims. C4 argues the opposite: credible anti-promises ("this is NOT for you if...") are trust-building, not conversion-killing. Ground this in Claude Hopkins 1923 and modern empirical evidence from Hormozi and Abraham.
Instructions to Claude in the New Chat
"Start C4 Offer Ignition build per the summary above. Same cadence as C1/C2/C3 — build folder by folder, I'll say 'continue' when context fills. Ship the full 48-50 file course, QM audit, zip, and deployment SOP. Begin with folder 00_Course-Overview."

Paste everything above into the new chat to start C4 cleanly.
Complete linked peer-review resource: D1458

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*
Complete linked peer-review resource: D1594

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*
Complete linked peer-review resource: D3189

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
Complete linked peer-review resource: template

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*
Complete linked peer-review resource: alternate

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*
Complete linked peer-review resource: paid

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*
Complete linked C4 schema; missing implementations distinguished in teaching

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*
Complete local source copy including original filing metadata and formatting

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/17YXOmvmA7Rjy_JjWyfLPw04Nfivw-mK7bcfSQNSgTl4/edit?usp=drivesdk"
drive_file_id: "17YXOmvmA7Rjy_JjWyfLPw04Nfivw-mK7bcfSQNSgTl4"
created: "2026-04-27T18:55:33.434Z"
modified: "2026-06-04T17:09:55.885Z"
---

# C4 Build Handoff — RISER Nation Maritime Academy

C4 Build Handoff — RISER Nation Maritime Academy
Context
I'm continuing a multi-session build of the RISER Nation Maritime Academy. Three courses are complete and shipped (C1 Harbor Orientation, C2 Flagship Discovery, C3 Buoy Navigation); I'm now starting C4 Offer Ignition (Stage 1, course 4 of 5, offer architecture and first sellable asset).
What to build for C4
Full C1/C2/C3 parity build:
* ~48-50 files, ~45-52K words
* 8-folder structure (00_Course-Overview through 08_Community-Prompts)
* 8 module lessons (M4.1-M4.8), written lessons for all + video production spec for M4.1 only
* ~12-14 resources (templates, worksheets, frameworks, checklists)
* 6 Claude system prompts in YAML (5 Sonnet + 1 Opus for the course-completion validator)
* 4 SOPs (YAML+markdown format)
* 4 case studies: continue Maya/Darius/Priya narratives from C1+C2+C3, plus 1 new C4-specific failure case
* 1 community prompts file
* QM audit (JSON + xlsx scorecard using the audit tool)
* Deployment SOP as Word doc, same format as C1/C2/C3 SOPs already shipped
Same cadence as prior courses: build folder-by-folder, I'll say "continue" when context fills, ship zip + scorecard + deployment SOP at the end.
C4 Offer Ignition scope
Course position: Stage 1, course 4 of 5. Sits between C3 (validated Primary mechanism + full Trigger Bank + competitor scan) and C5 (First Currents / AEO Literacy — the Stage 1 capstone).
Inputs from C3 (all referenced by Build 6 at C4 enrollment):
* Market Fit Hypothesis document from M3.8 with single validated Primary mechanism
* Full Trigger Bank (~200 audience-language entries) — C4 uses these for offer copy
* Competitor scan (5-10 operators analyzed) — C4 uses for positioning differentiation
* 8-12 customer interview summaries — C4 uses for offer structure decisions
* Pricing and packaging signals — C4 uses for price band selection
Outputs to C5:
* A complete sellable offer document (Hormozi-style Grand Slam Offer, customized to mechanism)
* Offer landing page copy (not yet live — copy in markdown ready for deployment)
* Pricing decision with rationale (anchor price + payment options)
* Anti-promise statement (what the offer explicitly does NOT do/promise)
* Guarantee structure (refund terms, conditional guarantees)
* First-sale readiness checklist (what must be true before asking for money in C5)
Stage 1 graduation gate contribution: C4 is the "Offer Ignition" course. C5 graduation requires territory chosen (C1), mechanism candidates named (C2), market scanned (C3 output), offer drafted (C4 output), AEO literacy and first-sale readiness (C5). C4 is 4 of 5.
Proposed C4 Module Map (8 modules)
* M4.1 — Offer Architecture Foundations (the offer is not the mechanism; what an offer contains that a mechanism doesn't) — Analyze
* M4.2 — The Grand Slam Offer Framework (Hormozi's Value Equation adapted to RISER context: Dream Outcome × Perceived Likelihood ÷ Time Delay × Effort & Sacrifice) — Understand + Apply
* M4.3 — Offer Deconstruction and Reassembly (take the Primary mechanism, decompose into deliverables, reassemble into saleable offer) — Create
* M4.4 — Pricing and Anchoring (price band selection using C3 pricing signals; anchor price; payment options) — Evaluate
* M4.5 — The Anti-Promise Statement (what the offer explicitly does NOT do; who the offer is NOT for) — Create
* M4.6 — Guarantee Architecture (conditional vs unconditional; refund terms; risk reversal without unit economic damage) — Apply
* M4.7 — Offer Landing Page Copy (copy-based, not design-based; Trigger Bank-sourced language; 7-section structure) — Create
* M4.8 — Offer Readiness Document (synthesis artifact for C5; first-sale readiness checklist) — Create
Time: ~40 hours active / 4-5 weeks elapsed (slightly shorter than C3 because work is internal writing rather than external research) Prerequisite: C3 complete with Market Fit Hypothesis filed Stage color: Maritime Blue #2E75B6 (Stage 1)
Critical Doctrines (unchanged, apply to C4)
* Operator-vs-Agency (from C1): an operator sells their mechanism directly; an agency resells others' mechanisms. C4's offer must be operator-type, not agency-type.
* 6% Rule applied in C4 as "draft 3 offer variants before committing to one" — M4.3 produces 3 offer decomposition variants; M4.8 selects one for shipping
* 85-Minute Rhythm continues (Mon 10m / Tue 15m / Wed 30m / Thu 20m / Fri 10m)
* HITL mandatory — Build 6 requires peer review of offer landing page copy before unlocking M4.8
* Anti-promise discipline from C1 M1.3 / C2 M2.4 / C3 culminates in M4.5's explicit Anti-Promise Statement
* Kill criteria continue — M4.8 specifies conditions under which the offer gets rewritten vs. scrapped in C5
Stage Graduation Gates (authoritative, unchanged)
S1→S2 Territory + Literacy (after C5) · S2→S3 Proof Threshold (C10) · S3→S4 First Dollar (C14) · S4→S5 First $10K Month (C27) · S5→S6 First Automated Dollar (C42) · S6 Autonomous Empire (C55)
Rubric Numbers (use consistently)
QM HE Rubric 7th Edition V2.0: 42 SRS · 94 max points · 16 Essential Standards · 85% threshold = 80+ points
NOT 44/101/22/86 — corrected from original C1 audit. The QM audit tool at /mnt/user-data/outputs/qm-audit-tool/ uses the correct numbers.
Maritime Color Scheme
S1 Dinghy 2E75B6 · S2 Sailboat 3B9EA0 · S3 Speedboat 6FA84E · S4 Yacht BF9000 · S5 Mega Yacht B45F06 · S6 Bora Bora 5B3C88
Cross-References C4 Must Maintain
To C1:
* Captain's Oath Clause 1 (territory) — offer must serve stated territory, no drift
* Operator Identity — offer's voice and structure match operator archetype (Teacher-Operator offers differ from Service-Operator offers)
* 85-Minute Rhythm continues
To C2:
* Mechanism Hypothesis Document — offer is built on the Primary mechanism selected
* 4-Pillar Mechanism Discovery Framework — offer's Method section restates the mechanism's Method pillar
* 5-Test Naming Filter — offer's name may inherit mechanism name OR produce new offer-specific name (re-apply 5-test)
To C3:
* Market Fit Hypothesis — offer addresses validated market, not theoretical one
* Trigger Bank — offer copy uses audience's actual language; M4.7 landing page copy pulls 15-30 Trigger Bank entries verbatim
* Competitor scan — offer positioning differentiates from named competitors explicitly
* Pricing signals — offer price band informed by observed market, not arbitrary
* Customer interviews — offer structure reflects what interviewees actually said they'd buy
Cross-case narrative continuity (from C1+C2+C3):
* Maya — illustrator licensing — advancing "The Portfolio-to-Licensing Sprint"; C4 produces her first sellable offer at a price band validated in C3
* Darius — platform engineering — advancing "The Platform-Transition Reading Club" (or an alternative if C3 killed it via employer-policy friction); C4 offer reflects C3 findings
* Priya — fractional CFO — advancing "The Series B Readiness Track" (likely repositioned as CEO-support per her C3 M2.8 KC1 investigation); C4 offer incorporates repositioning
* New C4 failure case: working title "The Feature Stuffing Trap" — student keeps adding bonuses and guarantees to the offer hoping to overcome a weak mechanism. Classic failure: fixing an offer problem when the real issue is mechanism-market fit. Connects back to C3 signals the student ignored.
Instructional References for C4 Content (use these, cite correctly)
The offer course builds on established direct-response methodology. Cite with attribution in relevant lessons:
* Alex Hormozi — $100M Offers (2021) — Value Equation, Grand Slam Offer structure, guarantee stacking. Core framework for M4.2.
* Russell Brunson — DotCom Secrets (2015) + Expert Secrets (2017) — offer stacking, value ladder positioning
* Jay Abraham — Getting Everything You Can Out of All You've Got (2000) — risk reversal, preeminence positioning
* Jeff Walker — Launch (2014) — sideways sales letter structure for landing page copy (M4.7)
* Eugene Schwartz — Breakthrough Advertising (1966) — market sophistication levels, awareness levels for M4.7 copy framing
* Claude Hopkins — Scientific Advertising (1923) — specificity in claims, anti-promise as credibility mechanism
M4.7 landing page structure draws from proven direct-response patterns: problem → agitation → solution → mechanism → proof → offer → anti-promise → guarantee → urgency → CTA.
Supabase Schema Additions C4 Needs (draft for 04_Tools-and-Infrastructure)
sql
-- M4.1 Offer/Mechanism distinction
CREATE TABLE c4_offer_distinctions (...);


-- M4.2 Value Equation application
CREATE TABLE c4_value_equations (...);


-- M4.3 Offer decomposition variants (3 variants required, per 6% Rule)
CREATE TABLE c4_offer_decompositions (...);


-- M4.4 Pricing decision
CREATE TABLE c4_pricing_decisions (...);


-- M4.5 Anti-Promise Statement
CREATE TABLE c4_anti_promises (...);


-- M4.6 Guarantee architecture
CREATE TABLE c4_guarantees (...);


-- M4.7 Landing page copy
CREATE TABLE c4_landing_page_copies (...);


-- M4.8 Offer readiness (course completion artifact)
CREATE TABLE c4_offer_readiness_docs (...);
Build 6 function: check_c4_enrollment_eligible(user_id) queries C3 completion state. check_c4_completion(user_id) verifies all 8 C4 deliverables present.
Expected Claude System Prompts (6 total)
1. offer-distinction-reviewer-v1.0.0.yaml (M4.1, Sonnet) — validates student can distinguish offer from mechanism
2. value-equation-application-reviewer-v1.0.0.yaml (M4.2, Sonnet) — validates Value Equation applied correctly across 4 variables
3. offer-decomposition-reviewer-v1.0.0.yaml (M4.3, Sonnet) — validates 3 distinct decomposition variants produced
4. landing-page-copy-reviewer-v1.0.0.yaml (M4.7, Sonnet) — validates 7-section structure present + minimum 15 Trigger Bank entries used verbatim
5. offer-readiness-reviewer-v1.0.0.yaml (M4.8, Sonnet) — structural validation
6. offer-fit-validator-v1.0.0.yaml (M4.8, Opus 4.7) — course-completion gate; validates offer-mechanism-market coherence; highest-stakes prompt
Final Deliverables Checklist (for the build)
1. /home/claude/C4-build/ with 8 folders fully populated (~48-50 files, ~45K words)
2. Run QM audit using /mnt/user-data/outputs/qm-audit-tool/ — apply the rubric manually (matching earlier courses' approach since can't call API), produce QM-Audit-C4.json + QM-Audit-C4-Scorecard.xlsx using build_qm_scorecard.py
3. Zip at /mnt/user-data/outputs/C4-Offer-Ignition-v2.0.zip
4. C4-Offer-Ignition-Deployment-SOP.docx in same format as C1/C2/C3 SOPs — 10-section populated TOC using BookmarkStart/BookmarkEnd with unique IDs from module-level counter. The docx-js Bookmark class has a bug where all bookmarks get linkId=1; use the shared helper at /home/claude/sop-split/shared.js (if still present in environment) or recreate with the same pattern.
Expected Outcome
C4 audit will likely score similarly to C1/C2/C3: ~92/94 (97.9%) with NOT_CERTIFIED blocked by SRS 8.3 (M4.2-M4.8 video specs not produced, only M4.1). ~55-95 hours of v2.1 remediation to reach CERTIFIED.
Catalog Progress
* C1 Harbor Orientation ✓ shipped
* C2 Flagship Discovery ✓ shipped
* C3 Buoy Navigation ✓ shipped
* C4 Offer Ignition — building now
* C5 First Currents — Stage 1 capstone; final course of Stage 1
After C4 completes, Stage 1 will be 80% built (4 of 5 courses), with C5 as the capstone that tests territory + identity + mechanism + market + offer integration + first-sale readiness.
One C4-Specific Design Note
C4 is where most students first encounter the gap between "intellectually understanding the mechanism" (C2 output) and "being able to sell it" (C4 output). This is the course where imposter-syndrome-adjacent feelings surface strongly. The failure case study (The Feature Stuffing Trap) addresses this directly — students who feel uncertain about the mechanism often try to overcome it by adding bonuses and guarantees, which dilutes rather than strengthens the offer. Handle this with care in the written lessons; name the emotional pattern explicitly.
The M4.5 Anti-Promise Statement module is counterintuitive for many students — they've been taught that marketing means positive claims. C4 argues the opposite: credible anti-promises ("this is NOT for you if...") are trust-building, not conversion-killing. Ground this in Claude Hopkins 1923 and modern empirical evidence from Hormozi and Abraham.
Instructions to Claude in the New Chat
"Start C4 Offer Ignition build per the summary above. Same cadence as C1/C2/C3 — build folder by folder, I'll say 'continue' when context fills. Ship the full 48-50 file course, QM audit, zip, and deployment SOP. Begin with folder 00_Course-Overview."
________________


Paste everything above into the new chat to start C4 cleanly.

Adjust offer-building work to your strengths and blind spots

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Use six operator archetypes to choose where to spend additional attention when building an offer. We will examine every archetype's territory, strengths, weaknesses and suggested adjustments; combine patterns for a hybrid operator; and check whether an adjustment improves the actual work. The source's C1 and C4 labels describe its legacy curriculum. They do not replace this lesson's spreadsheet assignment or create new enrollment gates.

Use the chart as a hypothesis about your work

The source is a reference chart for offer construction across eight legacy C4 modules. Its six categories are Teacher, Service, Builder, Product, Creative and Systems operators. It says the patterns were calibrated from earlier cohort observation, but supplies no dataset or measurement method. Treat a category as a starting hypothesis, not a validated personality test or a prediction that every person in that category behaves the same way.

Review your actual offer artifacts. A well-written guarantee or weak pricing comparison is stronger evidence about the current task than a category label. The source explicitly permits a reasoned override. Record the reason and the resulting change rather than using the label to excuse a weakness.

Teacher-Operator: carry teaching clarity into scope and pricing

The source associates this pattern with education, training and coaching for a craft or career transition. Its strengths are breaking a mechanism into teachable deliverables in M4.3, working naturally with a cohort format, and explaining the solution and mechanism clearly in M4.7.

The proposed weaknesses are underpricing in M4.4 and soft outcome exclusions in M4.5. The source contrasts self-paced course examples of $197–$497 with cohort examples of $1,500–$10,000. It also compares a $2,400 cohort with a $297 self-paced course. Preserve those as illustrative figures from the source, not current market rates or proof that $2,400 is appropriate for your buyers. Compare like-for-like delivery, support, capacity and evidenced demand in the actual pricing signals.

The source allocates one extra hour to comparing cohort prices with relevant cohort alternatives, and thirty extra minutes to the anti-promise's “What This Does Not Do” section. In practice, name the outcomes you do not promise and the conditions your offer cannot meet. Believing people can learn does not justify promising the same result for every participant.

Service-Operator: structure customization and define audience fit

The source associates this pattern with consulting, fractional roles, professional services and done-with-you or done-for-you delivery. It identifies a one-to-one variant as a strong match, familiarity with premium project or hourly pricing, and deep case evidence that may support perceived likelihood.

The proposed weaknesses are reluctance to exclude unsuitable buyers and resistance to decomposing a service into a named structure. Premium pricing and strong evidence are possibilities to check, not automatic advantages conferred by working in services. A service provider can still lack relevant proof or charge an unsustainable price.

Allocate the source's additional hour to the audience dimension of the anti-promise, with a peer reviewing three proposed audience exclusions. Make each exclusion a real fit boundary instead of flattery or an insult. Before decomposition, distinguish a structured starting point from a rigid service: a one-to-one variant can name its deliverables while allowing customization within agreed scope. The source calls that example Variant B; the letter does not mean every offer map must use that label.

Builder-Operator: translate technical features into buyer outcomes

The source places engineering, infrastructure, developer tools and technical coaching here. It proposes strengths in applying the Value Equation precisely, structuring guarantees with unit economics, and producing an organized readiness document. It also suggests technical credibility can strengthen the offer. In the teaching application, distinguish the buyer's desired outcome from evidence that affects confidence in achieving it; credibility is not the outcome itself.

The weaknesses to watch are a landing page that lists components without explaining their effects, paraphrasing buyer language into cleaner technical language, and a Dream Outcome written in the operator's vocabulary of systems or workflows.

The chart allocates two additional hours to M4.7, replacing first-draft feature descriptions with the original outcome language in the Trigger Bank. It also asks whether a nontechnical buyer would say the Dream Outcome and budgets three or four landing-page drafts instead of two. Keep exact source quotations in an appropriate research record and use permissioned quotations or clearly labeled paraphrases in public copy. Do not invent a quote merely to satisfy a count.

Product-Operator: make proof and acquisition assumptions visible

This pattern covers productized offers, templates, downloads and SaaS-adjacent scaffolding. The source associates it with a self-paced variant—Variant C in the named Maya example—fluency with floor-to-median pricing bands, and clear deliverables in the offer section. Its reference to Section 5 belongs to that legacy page structure, whose numbering should not silently replace the current lesson outline.

The proposed weaknesses are limited visible proof, a default to a simple refund guarantee without further design, and an assumption that finishing an offer also solves distribution. The source suggests low-priced products require substantially more traffic than higher-priced cohort or one-to-one offers. That comparison depends on conversion, contribution margin, acquisition cost and the revenue goal; price alone cannot determine required traffic.

Give additional attention to the perceived-likelihood evidence and guarantee design. Consider the source's suggested cohort or one-to-one version for an initial offer, with a productized version later, as an option to test rather than a required progression. A useful authored comparison asks which format provides credible proof, viable delivery and appropriate support for this audience. The source allocates attention here but does not assign a fixed extra-hour figure.

Creative-Operator: keep distinctive voice within clear commitments

The source associates this pattern with design, illustration, writing, film, photography and artistic work. Its proposed strengths are memorable first-person voice, sensitivity to buyer language, and the ability to communicate value that is not reducible to utility. It also describes a perceived-scarcity pricing premium. Only actual capacity or availability can support a scarcity claim; creative identity does not establish one.

The weaknesses are treating creative work as impossible to structure, pricing above the observed market ceiling without evidence of buyer capacity, and allowing scope to expand in pursuit of better art.

At decomposition, name the deliverables and boundaries without prescribing every creative choice inside them. At pricing, combine intuition with the observed pricing signals and require a defensible basis for going above the band. At the anti-promise, state what is included and excluded, revisit those terms for each engagement, and handle scope changes explicitly instead of silently expanding the commitment. The source gives these three attention adjustments without fixed additional hours.

Systems-Operator: retain precision while explaining human consequences

This pattern covers operations, workflow design, systems integration and business operations advice. The source proposes strengths in conditional guarantees, unit economics and a well-structured first-sale readiness checklist.

The weaknesses resemble the Builder pattern: a Dream Outcome expressed as process improvement or operational efficiency, a clinical description of the problem and agitation, and buyer quotations rewritten into precise but impersonal language. These phrases are not automatically wrong; test whether the intended buyer understands and uses them.

Allocate the source's additional hour to the problem and agitation sections. Describe the actual consequence for the buyer without exaggerating distress or manufacturing emotional pressure. Revise the Dream Outcome and read it to a friend outside systems work, asking whether it sounds like a buyer's goal or an efficiency consultant's description. That readability check supplements real audience evidence; the friend is not automatically a representative customer.

Combine patterns for a hybrid operator

The source names Teacher-Service and Builder-Systems as examples. It uses the primary identity as the default and the secondary identity to modify the work. Its Teacher-Service example combines decomposition strength with service-pricing experience, while warning that underpricing and soft anti-promises may still persist.

Read both relevant sections and choose adjustments based on the artifact being produced. Do not average incompatible claims into a diagnosis. A hybrid with strong pricing evidence may need no additional pricing hour, but may still need an explicit audience exclusion or scope boundary. Record that choice and why the evidence supports it.

Apply the four-step use process

First, identify the primary archetype recorded in the source's Operator Identity work, or treat it as an unconfirmed working label if that record is absent. Second, read the relevant section before starting the referenced offer-building activity. Third, apply the suggested attention adjustment instead of following a habit automatically. Fourth, record what changed in the artifact and whether it improved the work.

The source says ineffective adjustments may be a poor fit or may not yet have been internalized. Do not automatically blame the learner. Check whether the adjustment was clear, feasible, relevant and supported by the actual buyer evidence. A specific reason can justify overriding the chart.

Connect the adjustments to the curriculum's offer themes

As an authored Brunson/ClickFunnels connection, keep buyer language, the explanatory story and the offer consistent: technical precision, creative voice or teaching clarity should help the buyer understand the promise. As an authored Hormozi/Acquisition.com connection, inspect the desired result, confidence-producing evidence, delay, effort and delivery economics rather than adding bonuses to hide a weak offer. No archetype removes the need to validate these assumptions.

For the lesson exercise, select one draft offer, choose the most relevant adjustment, record the original passage or decision, make the revision, and explain the evidence for the change. Preserve all applicable source links alongside the exercise. The proof of useful adaptation is a clearer, better-supported offer artifact, not simply completing an archetype label.

Clickable assigned source

- C4 Archetype Adjustments — original source

The full original text remains in the lesson appendix, including its legacy module references, illustrative prices and claimed cohort basis. This script explains their limitations instead of silently converting them into current market facts or universal rules.

Assigned source links

D0433 original source 1

Complete native original body, including retained document-part text

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*
Complete local source copy including original filing metadata and formatting

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*

Turn a validated mechanism into a complete offer document

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Explain the source's Offer Ignition course overview, identify its research inputs and eight deliverables, follow the proposed study and review process, and separate internal quality claims from verified certification. The source labels this C4, Stage 1, Dinghy, uses Maritime Blue #2E75B6, and describes an offer as cargo loaded before trading. Those are legacy organizing metaphors; the current twelve-course spreadsheet still controls the lesson's placement.

Distinguish the mechanism from the offer

A mechanism explains how a result is expected to occur. An offer wraps that mechanism in a named, priced delivery commitment that a buyer can evaluate. The source warns against selling an abstract mechanism without a clear purchase or burying it in a generic package that loses the research, competitor gap and pricing evidence.

The proposed output is an Offer Document with a name, price, guarantee, anti-promise and landing-page draft. It is drafted, not yet launched. A first-sale readiness check or AI review does not establish market validation or revenue. The source's warning about operators arriving at a later course without revenue after ten weeks is an illustrative failure claim, not a measured prediction for all learners.

Bring the research that the source assumes already exists

The overview expects a completed Market Fit Hypothesis naming one validated Primary mechanism, a Trigger Bank of at least 200 audience-language entries, a scan of five to ten competitors, eight to twelve customer interviews, and documented pricing signals. It also expects prior-course completion. These research artifacts should show what the market actually said, not just the seller's preferred story.

The source calls these six prior outputs and says a proposed Build 6 system denies access when requirements are missing. No such access enforcement is established by this overview. If the hypothesis or evidence is unavailable, record the gap. Do not manufacture interviews, competitor observations or buyer quotations to satisfy a gate.

Produce all eight artifacts and understand their role

First, the Offer-Mechanism-Distinction memo explains what is being sold and how it relates to the mechanism. Second, the Value-Equation-Worksheet applies Dream Outcome, Perceived Likelihood, Time Delay, and Effort and Sacrifice. The source's written equation has ambiguous operation order; use the intended grouping of outcome multiplied by perceived likelihood, divided by delay multiplied by effort and sacrifice. Treat the framework as a reasoning aid, not a validated calculator of a buyer's willingness to pay.

Third, Offer-Decomposition-Variants preserves three different saleable forms before one is selected. The source calls that the 6% Rule; it supplies the three-variant instruction, not a percentage formula. Fourth, Pricing-Decision records an anchor, price-band selection and payment options with reasons from the pricing evidence.

Fifth, Anti-Promise-Statement states what the offer does not do and whom it does not fit. Sixth, Guarantee-Architecture specifies the promise, refund terms and any conditions while considering delivery economics. Seventh, Offer-Landing-Page-Copy uses the source's seven-section description and at least fifteen original Trigger Bank entries. Other assigned legacy material lists ten copy sections, so preserve and resolve that conflict before standardizing the template.

Eighth, Offer-Readiness-Document synthesizes the other work and includes the first-sale checklist. The source names each file with [YourName]-[Date].md and places it in the Build 8 Drive folder. These are proposed deliverables and filing conventions, not evidence that a student's files already exist.

Understand the eight module outcomes and time allocations

Offer Architecture Foundations asks the learner to analyze the distinction and name seven offer components, with seventy-five minutes allocated. The overview does not define all seven components, so do not invent an attributed list. Grand Slam Offer Framework allocates ninety minutes to understanding and applying the four value variables. Deconstruction and Reassembly allocates 180 minutes to creating three variants. Pricing and Anchoring allocates ninety minutes to evaluating the price and payment structure.

The Anti-Promise module allocates seventy-five minutes to creating exclusions. Guarantee Architecture allocates ninety minutes to applying risk reversal sustainably. Landing Page Copy allocates 240 minutes to creating the page. Offer Readiness allocates ninety minutes to synthesis. The source's Bloom labels emphasize analysis, application, evaluation and creation; completing a reading alone does not demonstrate those outputs.

The listed times total 930 minutes, or fifteen and a half hours, approximated by the source as fifteen hours of study plus twenty-five hours of implementation, about forty hours overall. Its four-to-five-week target requires roughly eight to ten active hours a week. A separate prerequisite of four to six hours per week and the inherited eighty-five-minute rhythm cannot by themselves satisfy that total. Plan the actual available hours explicitly.

Follow the study and filing process

The source puts the first two modules in week one, three variants in week two, pricing and exclusions in week three, guarantees and page copy in week four, and readiness in week five. It recommends forty-eight-hour cooling between draft and revision, including at least one night's separation, and peer feedback for the page. These are proposed revision practices, not guarantees of stronger copy.

File artifacts as they are produced, including abandoned variants and pricing or guarantee alternatives that may be useful later. Keep three variants together before the proposed pricing unlock. The page should receive two peer reviews before readiness. The source names a Circle.so c4-offer-ignition discussion channel and distinguishes operator-to-operator peer review from instructor review at the later Stage 1 capstone. Neither channel availability nor a functioning lock is verified here.

Peer review checks whether the copy remains consistent with the hypothesis and whether its quoted buyer language is actually supported. Preserve exact quotations in a suitable evidence record and use them publicly only with appropriate rights and privacy handling. Do not fabricate a quotation or imply that a private interview can automatically be published.

Preserve all proposed prerequisite checks

The detailed list requires C3 completion, a Market Fit Hypothesis filed within three months, a Trigger Bank of at least 200 entries, five to ten competitors, at least eight interviews, and pricing signals. It also requires a Captain's Oath and Operator Identity Statement each filed within twelve months, plus four to six hours of weekly calendar availability.

The source gives table and field names such as users.c3_complete, c3_market_fit_hypotheses, c3_trigger_banks, c3_competitor_scans, c3_interview_library and c3_pricing_signals. These names identify a proposed data model. They do not prove the tables exist or the prerequisite rules are correct for the current twelve-course program.

Explain the policy additions honestly

The overview references inherited policies for AI disclosure, copyright and intellectual property, academic integrity, accessibility and data protection, but does not supply their full terms. Preserve them as dependencies rather than claiming a completed policy review.

Its two specific additions are an Anti-Promise Integrity Statement and a Guarantee Honesty Clause. The first asks for truthful, specific exclusions: excluding a done-for-you service is a scope statement; insulting people as lazy is not a useful fit boundary. The second requires a guarantee the provider intends to honor under the stated terms, rather than adding obstacles designed to defeat claims. The source places the signatures before the respective submissions. No signature or acceptance is executed by this lesson.

Trace every downstream and prior-course connection

The legacy C5 capstone expects territory, identity, mechanism, offer and first-sale readiness. Legacy C7 expands a single offer into entry, core and premium tiers. C10 uses the landing-page copy for funnels. C13 uses the anti-promise and guarantee in partnership positioning. C14 concerns a first sale, and content from C16 onward is intended to connect buyer-language hooks with the offer. These are source dependencies, not a renumbering of the current curriculum or a promise of future revenue.

From C1, the source carries forward territory commitments, operator identity, three-variant exploration and the eighty-five-minute rhythm. From C2, it uses the Mechanism Hypothesis, earlier audience quotations, the Method pillar in a four-pillar framework and a five-test naming filter. This overview does not define the full pillar framework; the naming tests are defined in a separate assigned worksheet. From C3, it uses the hypothesis, Trigger Bank, competitor scan, interviews and pricing signals to ground the promise, exclusions and price. An above-band price needs an explicit rationale, not just confidence.

Separate the founder introduction and internal audit from certification

The source describes a four-minute founder introduction in M4.1 explaining the single-offer focus, the distinction from a later offer-suite course, and the mechanism-versus-offer failure pattern. This is a video specification reference, not a produced video. It says M4.2–M4.8 video production remains pending.

It also claims an internal QM-equivalent score of 92 out of 94, with fifteen of sixteen essential standards met and one partial. Preserve those as source claims. Quality Matters' current higher-education rubric information describes forty-four specific standards, all essential standards and an eighty-five-percent threshold; its certification listing concerns official reviews. An internal score or a video script does not establish official certification. The referenced JSON audit must be examined separately before relying on its detailed findings.

Apply the curriculum's offer themes

Use the authored Brunson/ClickFunnels connection to make the buyer-facing story and offer consistent with the evidence. Use the Hormozi/Acquisition.com connection to improve outcome clarity, perceived likelihood, delay and effort without concealing fulfillment limits. The source names the Feature Stuffing Trap in decomposition, exclusions and guarantees: adding bonuses cannot substitute for checking mechanism-market fit.

For practice, inventory the eight artifacts, attach evidence links, identify missing components, and explain how the next revision will resolve one specific gap. Do not label the offer launched, validated, certified or operational merely because the outline is complete.

Clickable assigned source

- C4 Offer Ignition — original overview

Preserve the complete source and module table in the lesson appendix, including its dates, legacy prerequisites, proposed policies and unresolved inconsistencies.

Linked resource workshop: prepare, request, deliver and reconcile a peer review

The six linked documents supply the practical peer-review material referenced by the offer-course plans. They are legacy templates and operating proposals, not evidence of a currently staffed RISER service. Read them together: the preparation checklist establishes inputs, outreach scripts coordinate people, the review template structures feedback, the SOP sequences work, alternate protocols address missing capacity, and the paid-review reference describes proposed selection rules. No message, booking, payment or scholarship request is sent by this workshop.

Prepare all eight checklist groups

Group A requires the named landing-page file and seven sections in order: Problem, 200–400 words; Agitation, 150–300; Solution-and-Mechanism, 300–500; Proof, 200–400; Offer, 300–500; Anti-Promise-and-Guarantee, 250–400; and CTA, 50–150. The individual ranges sum to 1,450–2,650, while the required total is 1,800–2,500. Both conditions can be satisfied, but one does not automatically imply the other. These are template targets, not proof that a page of that length will convert. Compared with the handoff's ten-element list, two pairs are grouped and urgency has no separate heading; explain relevant truthful timing without inventing scarcity.

Group B requires a named Trigger Bank Provenance Log, at least fifteen entries, exact source wording, a TB identifier or interview reference, and distribution across at least four page sections. Matching fifteen quotations is not a substitute for the full bank's evidence quality. Keep permissions, confidentiality and attribution appropriate to the destination.

Group C compares the page's exclusions with M4.5 and its guarantee with M4.6. Softening must be reverted or justified in the record; added guarantee stacking should be removed under this template's policy. Both integrity signatures are required. Group D checks the tested offer name, one visible price rather than a hidden range, payment options, engagement model, duration, cadence and no more than eight deliverables. A signature and a count are structural checks, not proof of truthfulness or viability.

Group E asks for specific named or appropriately anonymized evidence, an explicit known-weakness acknowledgment when there are fewer than four named cases, and attributed, exact testimonials. Do not invent a fourth case or disclose an identity to meet a template. Group F requires a specific action, actual enrollment or cohort timing, a qualification process if applicable, and a real pre-purchase contact. Group G requires reading the page aloud, removing phrases the operator would not say, checking unsupported hyperbole, and avoiding the source's four low-substance phrases: “game-changer,” “revolutionary,” “transform your life,” and “all you need to do is.” These are editorial preferences, not a comprehensive truthfulness test.

Group H prepares links to the page and provenance log, two or three positioning sentences, a request for two template-based reviews within seventy-two hours, and specific availability to reciprocate. The checklist's fifteen-to-twenty-minute estimate and claimed thirty-to-sixty-minute reviewer saving are unverified assumptions.

Its five common fixes are to restore softened terms; add three to six genuine missing quotations, often in problem and agitation; examine excess deliverables for unnecessary padding; show the actual price in the offer section; and use a forty-eight-hour reread to repair unnatural voice. Add only what is genuinely missing rather than assuming three extra quotes always reaches fifteen. After submission, check reviewer pickup daily, answer questions, keep the reviewed version stable and begin reciprocating. The stable-version rule prevents two reviewers evaluating different drafts.

Use the six coordination scripts as templates, not automatic messages

The request script identifies the operator, tested offer name, buyer, price and one or two suspected weaknesses. It links the page, provenance log and any existing Revision Log, proposes seventy-two hours, and states specific days for reviewing the first two reciprocal requests. Naming a focus may help, but the claim that it reliably improves feedback is not established by data here.

The acceptance script names the requester, confirms the chosen focus or full-template review, and gives a specific delivery date and time, aiming for forty-eight hours. That is shorter than the general seventy-two-hour target; state which commitment was actually made. The decline script explains capacity if useful, refers to a genuinely available person, and points to alternate review options. Do not tag someone or promise mentor capacity without knowing it exists.

The delivery script links the completed template, gives one overall observation and three recommended revisions, and offers optional asynchronous discussion. The response script addresses every recommendation as incorporated, incorporated with modification, or not incorporated with a reason, then links the Revision Log. The escalation script identifies the pacing window, requests and responses, attempted alternate routes, specific help needed, page link and revised timeline. The source routes it to a mentor channel or a welcome-email Calendly link, neither of which is supplied as a verified current contact.

The etiquette section favors reciprocity, precise observations, honest criticism and timely responses. Its example contrasts generic praise with identifying performative “wasted years” wording in a particular paragraph. Be candid and respectful; honesty does not require harshness. The source calls reciprocity a culture norm rather than enforced policy. It encourages personal voice especially in request and delivery scripts, with logistics scripts closer to their templates. Claims that personal voice correlates with better responses or missed SLAs are the largest disruption cause are source assertions, not measured findings here.

Complete the entire review template

Read the page and provenance log together, looking for buyer-language fit, quotations that support specific claims, and exclusions or guarantees weakened during copywriting. The source estimates forty-five to sixty minutes and a seventy-two-hour request-to-delivery target. Record reviewer name, reviewer archetype, date, submitting operator and offer name. The task is structural feedback, not rewriting every line.

Rate each section strong, adequate or weak. For Problem, restate the problem in one sentence, assess whether the buyer's state is vivid or generic, and whether at least one quotation is meaningful, then add one to three specific observations. For Agitation, distinguish real, mixed and performative consequences and identify any supporting numbers, timeframes or opportunity costs. Do not manufacture emotional pressure or unsupported losses.

For Solution-and-Mechanism, explain the mechanism in your own words and check whether its four referenced pillars are visible; missing pillar definitions remain a separate dependency. For Proof, distinguish specific, mixed and generic cases and check whether limited evidence is honestly acknowledged. For Offer, inspect the name, visibility of price and concrete delivery experience—what happens, when and with whom.

For Anti-Promise-and-Guarantee, rate the two parts separately. Count three or more genuine exclusions, two, or one or fewer. Identify disguised flattery such as “not for unmotivated people.” Compare one primary guarantee plus an optional complementary element with borderline or three-plus-component stacking. Consider whether stated claim conditions appear understandable and realistically usable, without treating component count as a conclusive legal or ethical judgment. For CTA, check a specific action, outcome and actual timeline. The source's February 12 enrollment and twenty-four-hour welcome-kit example is fictional illustration, not a current date or promise.

Across the whole page, sample three quotations against provenance and classify them as exact, slightly paraphrased or significantly paraphrased. Record overall strong, mixed or weak provenance, but recognize that a three-quote sample cannot verify every quotation. Assess buyer versus operator voice, then count all fifteen required entries. Give three actionable revisions—for example, shortening a particular four-sentence opening to two—rather than an abstract request to improve copy. Close with ready, moderate revision or substantial revision, a hypothetical yes/maybe/no buying reaction with reasons, and a signature. A peer's hypothetical buying reaction is not an actual purchase or validation result.

Follow the SOP's sequence, roles and timing

The SOP requires the page draft, provenance log, completed preparation checklist and a forty-eight-hour cooling period. Its seven roles are the submitting student, two peer reviewers, mentor, cross-stage reviewer, paid reviewer and proposed Build 6 coordinator. The source assigns automated notifications, matching, tracking and gates to Build 6; those operations have not been verified or deployed here.

Step one is a twenty-minute self-audit of checklist groups A–H, quotations and unchanged terms. Missing provenance, fewer than fifteen entries or softened exclusions cause rework; the source's twenty-four-to-forty-eight-hour delay estimate is illustrative. Step two is a fifteen-minute request using the structured script, both document links, suspected weaknesses, the review target and reciprocal availability. Vague requests and missing attachments should be fixed before relying on a review.

Step three allows twenty-four to forty-eight hours for pickup and requires two commitments with delivery dates. The SOP activates alternatives when fewer than two commit within forty-eight hours, whereas the separate alternate document uses seventy-two hours without response. Keep that conflict visible. Reviewers should communicate a threatened deadline instead of missing it silently.

Step five allocates thirty minutes to reading both completed reviews together before acting. Capture common themes and disagreements, then allow the SOP's suggested twelve-hour gap before revision. Two reviewers agreeing is a reason to investigate, not proof that their judgment is correct. Step six allocates sixty to ninety minutes to decisions in the Revision Log and the revised page. Record every recommendation and its disposition; do not accept all feedback mechanically or omit disagreement silently.

Step seven budgets ninety to 120 minutes for two reciprocal reviews, forty-five to sixty each, using the template and delivery script. Discuss actual capacity instead of treating an access need as bad faith. Step eight budgets five minutes to submit and five for the proposed AI run. It requires page, provenance and revision logs, a score of at least seven out of ten and no integrity flags. Its activities say review count at least two, while its quality gate says exactly two. An implementation must reconcile that difference and distinguish review credits from actual people; it must not fabricate a second reviewer when one mentor review counts as two credits.

Apply alternate routes with explicit review credit

Use alternatives when fewer than four people are active at compatible pacing, no response arrives within the stated window, or the student is ahead or behind the cohort. The alternate document proposes escalation within seventy-two hours of draft completion if no route is viable, which can conflict with longer windows below. Define the applicable clock before promising completion.

Protocol A proposes a forty-five-minute mentor call, with the draft and provenance log submitted at least twenty-four hours beforehand. A completed written template counts as both required review credits. The alternate document gives seventy-two hours typically and ninety-six worst case, at no charge; the SOP separately describes twenty-four hours from activation and delivery within seventy-two. These are conflicting source service assumptions, not verified current support. A mentor backlog of two or more weeks is the stated reason to try B.

Protocol B requests one or two volunteer Stage 2-or-higher reviewers, naming archetype, territory, offer, a ninety-six-hour target and both document links. It mentions Stage 2, 3, 4 and 5+ volunteers, no charge and reciprocal ecosystem credits. One cross-stage review may count as two credits or be paired with another review under the source policy; record the chosen interpretation. The SOP limits one description to Stages 2–5. If no one picks up within forty-eight hours, the source points to C. Experience may be useful, but it does not guarantee a superior review.

Protocol C is a direct paid engagement when A and B are unavailable in the planned week. The Academy is not described as handling payment. A paid review counts as only one credit and needs a peer, mentor or cross-stage counterpart. The source's typical price is $150–$400 and turnaround forty-eight to seventy-two hours by contract; the roster's A1 range reaches $450. Preserve that discrepancy. It also proposes that waiting three to five extra days for an unpaid route may be preferable. No paid service is recommended as currently available or purchased here.

The scholarship provision names the unverified legacy address [[email protected]](mailto:[email protected]), a specific scholarship-request subject, page link, pacing dates and attempted routes. It proposes a forty-eight-hour reply and one review covered up to $200 if approved. This is not a current verified service, funding commitment or permission to send a message. The protocol log records route, actual reviewer names, dates and one or two rationale sentences. Its shorthand for C omits a peer as the counterpart despite the prose allowing one; preserve and resolve that inconsistency.

Evaluate the paid-review reference without inventing a roster

The five proposed selection criteria are at least twenty relevant prior page reviews, familiarity with mechanism-based offers, respect for truthful exclusions, a signed methodology agreement and useful ratings from at least five reviewees. The document contains placeholder slots, not current names or contact details, so it does not establish that any provider is actually vetted or available.

Tier A describes ten-plus years of experience: A1 at $350–$450 with seventy-two hours for coaching, consulting and Teacher/Service work; A2 at $300–$400 with forty-eight to seventy-two hours for productized services and Builder work. Tier B describes five to ten years: B1 at $200–$275 with forty-eight to seventy-two hours for Creative work; B2 at $175–$250 with seventy-two hours for B2B, platforms and Systems work. Tier C describes five rotating Stage 2+ alumni slots at $150–$200 with forty-eight to seventy-two hours and archetype matching. All numbers and availability claims are historical template data, not current quotations.

Its five engagement steps are to find the actual current roster, match relevant expertise, provide the draft and provenance log with the required template, explain the methodology baseline, and log the engagement. The baseline preserves mechanism, exclusions and guarantee honesty while requesting critique within that approach. A reviewer should still flag unsupported or unsuitable commitments; methodology must not become a reason to ignore valid criticism.

The source excludes unlisted general review services, disparages low-cost marketplace reviews, rejects AI-only tools as a substitute for required human review, and disallows unlisted paid reviewers for credit. Preserve these as program-policy proposals. Blanket claims about a marketplace's quality are unsupported; assess the actual reviewer. The four methodology conflicts are removing exclusions, adding guarantee stacks, replacing exact quotations, and drifting from the Primary mechanism. Consult the designated reviewer or mentor rather than automatically adopting or rejecting advice solely because it is paid.

The four proposed removal triggers are three or more materially disruptive reports, missing at least twenty percent of quarterly deadlines, an agreement violation such as using review time to upsell, or leaving the field/not renewing the agreement. The document proposes quarterly updates, thirty days' notice and possible later re-entry. These are not actions taken against any person.

Review the process itself

After a cohort, examine the proportion using each route, median request-to-delivery time, the proportion meeting deadlines without escalation, and the proportion of paid feedback conflicting with the stated methodology. The SOP proposes revisiting capacity above thirty-percent mentor substitutions, agreements or roster choices above twenty-percent paid conflicts, and cohort discussion below a 0.85 given/received ratio. These are proposed thresholds, not validated universal benchmarks.

Its additional escalation triggers are three or more failed submissions by one student, fabrication or conflicting reviewer feedback requiring agreement review, an individual reciprocity ratio below 0.5 across two cohorts, and more than three consecutive weeks of thin participation prompting a recruitment review. Define denominators and review evidence before acting. The source's promise that a validator will not penalize alternate routes needs actual implementation verification.

The practical output is a stable reviewed draft, genuine feedback, a decision log, correctly recorded review credits and explicit unresolved issues. Connect Brunson/ClickFunnels message continuity with the Hormozi/Acquisition.com value lens: review whether the promise, evidence, exclusions and delivery agree. Do not mistake template completion, agreement between two reviewers or a numerical score for proof of buyer demand.

Clickable linked resources

- Preparation checklist - Six outreach and response templates - Peer-review coordination SOP - Complete review template - Alternate protocols - Paid-review reference with placeholder roster

Preserve all six complete originals in the applicable lesson appendices. Their dates, templates and embedded operational instructions remain source material, not current service promises or actions executed by this task.

Assigned source links

D0434 original source 1

Complete native original body, including retained document-part text

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*
Complete linked peer-review resource: D1458

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*
Complete linked peer-review resource: D1594

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*
Complete linked peer-review resource: D3189

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
Complete linked peer-review resource: template

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*
Complete linked peer-review resource: alternate

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*
Complete linked peer-review resource: paid

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*
Complete local source copy including original filing metadata and formatting

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*

Sequence offer construction through explicit checkpoints

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Trace the source's eight-module offer-building sequence, connect every checkpoint to its required evidence, schedule revision and peer review, and diagnose the Feature Stuffing Trap. These are legacy C4 labels and proposed gates. They do not replace this course's spreadsheet assignments or establish a functioning enrollment system.

Follow the entire module and checkpoint path

The source begins with a completed C3 Market Fit Hypothesis. M4.1 spends seventy-five minutes distinguishing the offer from its mechanism. Checkpoint 4.1 asks for the distinction memo and an AI-rubric result of at least seven out of ten. A failure returns to the same activity; a pass proceeds to M4.2.

M4.2 allocates ninety minutes to applying all four Value Equation variables. Checkpoint 4.2 requires the worksheet and an evidence-citing application scoring at least seven out of ten. M4.3 allocates 180 minutes to three distinct decomposition variants. Its structural checkpoint requires three variants with different engagement models, durations and price bands. The diagram calls this the 6% Rule, with a doubled percent sign in the source markup; the supplied operational requirement is three variants, not a six-percent calculation.

M4.4 allocates ninety minutes to an anchor price and payment options, supported by C3 pricing signals. Checkpoint 4.4 requires at least seven out of ten on that rationale. M4.5 allocates seventy-five minutes to a truthful, specific anti-promise: what the offer does not do and whom it does not fit. Checkpoint 4.5 requires the artifact, the same minimum rubric score and the signed Integrity Statement.

M4.6 allocates ninety minutes to an honest, sustainable guarantee, including refund and conditional structure. Checkpoint 4.6 requires an artifact, at least seven out of ten on sustainability and the signed Honesty Clause. M4.7 allocates 240 minutes to seven-section landing-page copy with at least fifteen verbatim Trigger Bank entries. Two peers review it before Checkpoint 4.7, which requires the artifact, an AI score of at least seven, two completed peer reviews and verification of the quoted entries. Peer requests for revision and failed checkpoint results return to M4.7.

M4.8 allocates ninety minutes to the readiness synthesis and first-sale checklist. Checkpoint 4.8 combines the artifact, a proposed Opus validator and a course-completion test; the source's summary requires PASS and all eight artifacts verified. A failure returns to M4.8; a pass is proposed to complete C4 and open C5. The full checkpoint specification and validator are referenced assets, not supplied implementations in this map.

The diagram colors the start and completion blue (#2E75B6) and peer review gold (#BF9000). Preserve its graph and the textual pass/fail routes in the appendix so meaning does not depend on color alone. A later worksheet allows variants to differ on three of four axes rather than requiring the exact three listed here; keep that version difference explicit when reconciling the rubric.

Understand why each output comes before the next

The distinction memo establishes what the Value Equation is evaluating. The Value Equation shapes the criteria used to assemble variants. A variant then needs a defensible price. Pricing, exclusions and guarantees supply the landing-page promise and conditions. The page brings those pieces together, and the readiness document checks their consistency.

The source warns that independently constructing these pieces can produce a guarantee that contradicts an exclusion or a price inconsistent with the offer design. Treat the sequence as a useful dependency model, not proof that all parallel work is inherently incoherent. Do not claim a checkpoint has passed merely because a later document exists.

Preserve cooling periods and the five-week rhythm

The source requests forty-eight hours between first and second drafts of M4.3, M4.5, M4.7 and M4.8, describing at least one night and preferably two. This is proposed elapsed revision time, not active work. Its claim that skipping the gap produces less durable copy is not supported by comparative data in the document.

Week one uses Monday to read the Market Fit Hypothesis, Tuesday to outline the distinction memo, Wednesday to finish it and begin the Value Equation, Thursday to draft the equation application, and Friday to file both artifacts. Week two moves from a Monday decomposition brainstorm to Tuesday's first-variant outline, Wednesday's first and second drafts, Thursday's third variant and Friday's filing of all three.

Week three rereads the variants and selects a provisional lead on Monday, examines pricing signals Tuesday, drafts the price decision Wednesday, drafts the anti-promise Thursday and files both Friday. Week four drafts the guarantee Monday, revises it and signs its clause Tuesday, drafts page sections one through four Wednesday and five through seven Thursday, then files the draft and requests peer review Friday.

Week five incorporates peer feedback Monday, revises the page Tuesday, drafts readiness Wednesday, revises readiness and its checklist Thursday, and submits to the proposed validator Friday. Late reviews extend this sequence; the source says to wait until they arrive. Its peer-review target is forty-eight hours here, while other assigned legacy documents use seventy-two. Preserve that conflict rather than making an unverified service promise.

The daily rhythm is ten, fifteen, thirty, twenty and ten minutes—eighty-five per week. Across five weeks it totals seven hours and five minutes, whereas the module allocations alone total fifteen and a half hours, before further implementation work. The separate time-estimate source clarifies that longer work happens in addition to the rhythm. A workable calendar must include those additional sessions and cooling intervals rather than representing the small weekday blocks as the whole workload.

Supply each module's source evidence

M4.1 reads Section 3 of the Market Fit Hypothesis for the Primary mechanism. M4.2 uses Trigger Bank entries for desired outcomes, interview evidence for perceived likelihood, competitor benchmarks for delay, and pricing signals as proposed effort proxies. A price is not automatically evidence of buyer effort, so inspect what the signal actually measures.

M4.3 reads the interview library for what buyers said they would purchase. M4.4 uses observed pricing bands. M4.5 uses disconfirming interview evidence and objection language. M4.6 compares adjacent guarantees and interview risk-reversal language. M4.7 uses the complete Trigger Bank, including the fifteen-entry minimum. M4.8 synthesizes the C3 artifact set.

The source proposes sending a learner back to C3 when the Primary mechanism section is absent, the Trigger Bank contains fewer than 200 entries, or pricing signals are missing. This is a legacy policy, not a verified live access control. Evidence quality also matters: do not fabricate entries, duplicate comments to inflate the count or expose private quotes in public copy. Preserve exact source material appropriately and distinguish permissioned quotations from paraphrases.

Diagnose all three Feature Stuffing signals

The source describes a learner who adds bonuses, guarantees and deliverables when the actual mechanism-market fit is weak. The first signal is low Dream Outcome or Perceived Likelihood evidence being masked by features that appear to reduce delay or effort. The second is a missing or vague anti-promise because the seller fears narrowing the audience. The third is a guarantee with three or more conditions that make a claim improbable.

These are review prompts, not conclusive diagnoses. Three legitimate, clearly disclosed conditions do not automatically make a guarantee deceptive; examine whether they are relevant, understandable and realistically usable. The proposed remedy is to revisit the earlier Kill Criteria Evaluation and determine whether the Primary mechanism actually passed its tests. If it did not, reopen the underlying decision rather than decorate an unsupported offer.

Apply the marketing themes without bypassing evidence

The authored Brunson/ClickFunnels connection is to assemble a page whose hook, story, evidence and offer agree with the earlier research. The authored Hormozi/Acquisition.com connection is to improve the actual outcome, confidence, speed or effort where evidence indicates a problem, rather than padding a value stack. Keep the full offer's fulfillment requirements visible.

For practice, trace one offer from its distinction memo to readiness. At each checkpoint identify the artifact, evidence, pass condition and revision route. Mark missing assets explicitly. Explain how you would respond to late peer feedback and one feature-stuffing warning. This is a planning exercise; it does not deploy reviewers, contact peers or alter enrollments.

Clickable assigned source

- C4 Offer Ignition — Module Map

Preserve the full original map, graph, weekday schedule, checkpoint table and dependency table in the lesson appendix, including source inconsistencies and references to absent assets.

Linked resource workshop: prepare, request, deliver and reconcile a peer review

The six linked documents supply the practical peer-review material referenced by the offer-course plans. They are legacy templates and operating proposals, not evidence of a currently staffed RISER service. Read them together: the preparation checklist establishes inputs, outreach scripts coordinate people, the review template structures feedback, the SOP sequences work, alternate protocols address missing capacity, and the paid-review reference describes proposed selection rules. No message, booking, payment or scholarship request is sent by this workshop.

Prepare all eight checklist groups

Group A requires the named landing-page file and seven sections in order: Problem, 200–400 words; Agitation, 150–300; Solution-and-Mechanism, 300–500; Proof, 200–400; Offer, 300–500; Anti-Promise-and-Guarantee, 250–400; and CTA, 50–150. The individual ranges sum to 1,450–2,650, while the required total is 1,800–2,500. Both conditions can be satisfied, but one does not automatically imply the other. These are template targets, not proof that a page of that length will convert. Compared with the handoff's ten-element list, two pairs are grouped and urgency has no separate heading; explain relevant truthful timing without inventing scarcity.

Group B requires a named Trigger Bank Provenance Log, at least fifteen entries, exact source wording, a TB identifier or interview reference, and distribution across at least four page sections. Matching fifteen quotations is not a substitute for the full bank's evidence quality. Keep permissions, confidentiality and attribution appropriate to the destination.

Group C compares the page's exclusions with M4.5 and its guarantee with M4.6. Softening must be reverted or justified in the record; added guarantee stacking should be removed under this template's policy. Both integrity signatures are required. Group D checks the tested offer name, one visible price rather than a hidden range, payment options, engagement model, duration, cadence and no more than eight deliverables. A signature and a count are structural checks, not proof of truthfulness or viability.

Group E asks for specific named or appropriately anonymized evidence, an explicit known-weakness acknowledgment when there are fewer than four named cases, and attributed, exact testimonials. Do not invent a fourth case or disclose an identity to meet a template. Group F requires a specific action, actual enrollment or cohort timing, a qualification process if applicable, and a real pre-purchase contact. Group G requires reading the page aloud, removing phrases the operator would not say, checking unsupported hyperbole, and avoiding the source's four low-substance phrases: “game-changer,” “revolutionary,” “transform your life,” and “all you need to do is.” These are editorial preferences, not a comprehensive truthfulness test.

Group H prepares links to the page and provenance log, two or three positioning sentences, a request for two template-based reviews within seventy-two hours, and specific availability to reciprocate. The checklist's fifteen-to-twenty-minute estimate and claimed thirty-to-sixty-minute reviewer saving are unverified assumptions.

Its five common fixes are to restore softened terms; add three to six genuine missing quotations, often in problem and agitation; examine excess deliverables for unnecessary padding; show the actual price in the offer section; and use a forty-eight-hour reread to repair unnatural voice. Add only what is genuinely missing rather than assuming three extra quotes always reaches fifteen. After submission, check reviewer pickup daily, answer questions, keep the reviewed version stable and begin reciprocating. The stable-version rule prevents two reviewers evaluating different drafts.

Use the six coordination scripts as templates, not automatic messages

The request script identifies the operator, tested offer name, buyer, price and one or two suspected weaknesses. It links the page, provenance log and any existing Revision Log, proposes seventy-two hours, and states specific days for reviewing the first two reciprocal requests. Naming a focus may help, but the claim that it reliably improves feedback is not established by data here.

The acceptance script names the requester, confirms the chosen focus or full-template review, and gives a specific delivery date and time, aiming for forty-eight hours. That is shorter than the general seventy-two-hour target; state which commitment was actually made. The decline script explains capacity if useful, refers to a genuinely available person, and points to alternate review options. Do not tag someone or promise mentor capacity without knowing it exists.

The delivery script links the completed template, gives one overall observation and three recommended revisions, and offers optional asynchronous discussion. The response script addresses every recommendation as incorporated, incorporated with modification, or not incorporated with a reason, then links the Revision Log. The escalation script identifies the pacing window, requests and responses, attempted alternate routes, specific help needed, page link and revised timeline. The source routes it to a mentor channel or a welcome-email Calendly link, neither of which is supplied as a verified current contact.

The etiquette section favors reciprocity, precise observations, honest criticism and timely responses. Its example contrasts generic praise with identifying performative “wasted years” wording in a particular paragraph. Be candid and respectful; honesty does not require harshness. The source calls reciprocity a culture norm rather than enforced policy. It encourages personal voice especially in request and delivery scripts, with logistics scripts closer to their templates. Claims that personal voice correlates with better responses or missed SLAs are the largest disruption cause are source assertions, not measured findings here.

Complete the entire review template

Read the page and provenance log together, looking for buyer-language fit, quotations that support specific claims, and exclusions or guarantees weakened during copywriting. The source estimates forty-five to sixty minutes and a seventy-two-hour request-to-delivery target. Record reviewer name, reviewer archetype, date, submitting operator and offer name. The task is structural feedback, not rewriting every line.

Rate each section strong, adequate or weak. For Problem, restate the problem in one sentence, assess whether the buyer's state is vivid or generic, and whether at least one quotation is meaningful, then add one to three specific observations. For Agitation, distinguish real, mixed and performative consequences and identify any supporting numbers, timeframes or opportunity costs. Do not manufacture emotional pressure or unsupported losses.

For Solution-and-Mechanism, explain the mechanism in your own words and check whether its four referenced pillars are visible; missing pillar definitions remain a separate dependency. For Proof, distinguish specific, mixed and generic cases and check whether limited evidence is honestly acknowledged. For Offer, inspect the name, visibility of price and concrete delivery experience—what happens, when and with whom.

For Anti-Promise-and-Guarantee, rate the two parts separately. Count three or more genuine exclusions, two, or one or fewer. Identify disguised flattery such as “not for unmotivated people.” Compare one primary guarantee plus an optional complementary element with borderline or three-plus-component stacking. Consider whether stated claim conditions appear understandable and realistically usable, without treating component count as a conclusive legal or ethical judgment. For CTA, check a specific action, outcome and actual timeline. The source's February 12 enrollment and twenty-four-hour welcome-kit example is fictional illustration, not a current date or promise.

Across the whole page, sample three quotations against provenance and classify them as exact, slightly paraphrased or significantly paraphrased. Record overall strong, mixed or weak provenance, but recognize that a three-quote sample cannot verify every quotation. Assess buyer versus operator voice, then count all fifteen required entries. Give three actionable revisions—for example, shortening a particular four-sentence opening to two—rather than an abstract request to improve copy. Close with ready, moderate revision or substantial revision, a hypothetical yes/maybe/no buying reaction with reasons, and a signature. A peer's hypothetical buying reaction is not an actual purchase or validation result.

Follow the SOP's sequence, roles and timing

The SOP requires the page draft, provenance log, completed preparation checklist and a forty-eight-hour cooling period. Its seven roles are the submitting student, two peer reviewers, mentor, cross-stage reviewer, paid reviewer and proposed Build 6 coordinator. The source assigns automated notifications, matching, tracking and gates to Build 6; those operations have not been verified or deployed here.

Step one is a twenty-minute self-audit of checklist groups A–H, quotations and unchanged terms. Missing provenance, fewer than fifteen entries or softened exclusions cause rework; the source's twenty-four-to-forty-eight-hour delay estimate is illustrative. Step two is a fifteen-minute request using the structured script, both document links, suspected weaknesses, the review target and reciprocal availability. Vague requests and missing attachments should be fixed before relying on a review.

Step three allows twenty-four to forty-eight hours for pickup and requires two commitments with delivery dates. The SOP activates alternatives when fewer than two commit within forty-eight hours, whereas the separate alternate document uses seventy-two hours without response. Keep that conflict visible. Reviewers should communicate a threatened deadline instead of missing it silently.

Step five allocates thirty minutes to reading both completed reviews together before acting. Capture common themes and disagreements, then allow the SOP's suggested twelve-hour gap before revision. Two reviewers agreeing is a reason to investigate, not proof that their judgment is correct. Step six allocates sixty to ninety minutes to decisions in the Revision Log and the revised page. Record every recommendation and its disposition; do not accept all feedback mechanically or omit disagreement silently.

Step seven budgets ninety to 120 minutes for two reciprocal reviews, forty-five to sixty each, using the template and delivery script. Discuss actual capacity instead of treating an access need as bad faith. Step eight budgets five minutes to submit and five for the proposed AI run. It requires page, provenance and revision logs, a score of at least seven out of ten and no integrity flags. Its activities say review count at least two, while its quality gate says exactly two. An implementation must reconcile that difference and distinguish review credits from actual people; it must not fabricate a second reviewer when one mentor review counts as two credits.

Apply alternate routes with explicit review credit

Use alternatives when fewer than four people are active at compatible pacing, no response arrives within the stated window, or the student is ahead or behind the cohort. The alternate document proposes escalation within seventy-two hours of draft completion if no route is viable, which can conflict with longer windows below. Define the applicable clock before promising completion.

Protocol A proposes a forty-five-minute mentor call, with the draft and provenance log submitted at least twenty-four hours beforehand. A completed written template counts as both required review credits. The alternate document gives seventy-two hours typically and ninety-six worst case, at no charge; the SOP separately describes twenty-four hours from activation and delivery within seventy-two. These are conflicting source service assumptions, not verified current support. A mentor backlog of two or more weeks is the stated reason to try B.

Protocol B requests one or two volunteer Stage 2-or-higher reviewers, naming archetype, territory, offer, a ninety-six-hour target and both document links. It mentions Stage 2, 3, 4 and 5+ volunteers, no charge and reciprocal ecosystem credits. One cross-stage review may count as two credits or be paired with another review under the source policy; record the chosen interpretation. The SOP limits one description to Stages 2–5. If no one picks up within forty-eight hours, the source points to C. Experience may be useful, but it does not guarantee a superior review.

Protocol C is a direct paid engagement when A and B are unavailable in the planned week. The Academy is not described as handling payment. A paid review counts as only one credit and needs a peer, mentor or cross-stage counterpart. The source's typical price is $150–$400 and turnaround forty-eight to seventy-two hours by contract; the roster's A1 range reaches $450. Preserve that discrepancy. It also proposes that waiting three to five extra days for an unpaid route may be preferable. No paid service is recommended as currently available or purchased here.

The scholarship provision names the unverified legacy address [[email protected]](mailto:[email protected]), a specific scholarship-request subject, page link, pacing dates and attempted routes. It proposes a forty-eight-hour reply and one review covered up to $200 if approved. This is not a current verified service, funding commitment or permission to send a message. The protocol log records route, actual reviewer names, dates and one or two rationale sentences. Its shorthand for C omits a peer as the counterpart despite the prose allowing one; preserve and resolve that inconsistency.

Evaluate the paid-review reference without inventing a roster

The five proposed selection criteria are at least twenty relevant prior page reviews, familiarity with mechanism-based offers, respect for truthful exclusions, a signed methodology agreement and useful ratings from at least five reviewees. The document contains placeholder slots, not current names or contact details, so it does not establish that any provider is actually vetted or available.

Tier A describes ten-plus years of experience: A1 at $350–$450 with seventy-two hours for coaching, consulting and Teacher/Service work; A2 at $300–$400 with forty-eight to seventy-two hours for productized services and Builder work. Tier B describes five to ten years: B1 at $200–$275 with forty-eight to seventy-two hours for Creative work; B2 at $175–$250 with seventy-two hours for B2B, platforms and Systems work. Tier C describes five rotating Stage 2+ alumni slots at $150–$200 with forty-eight to seventy-two hours and archetype matching. All numbers and availability claims are historical template data, not current quotations.

Its five engagement steps are to find the actual current roster, match relevant expertise, provide the draft and provenance log with the required template, explain the methodology baseline, and log the engagement. The baseline preserves mechanism, exclusions and guarantee honesty while requesting critique within that approach. A reviewer should still flag unsupported or unsuitable commitments; methodology must not become a reason to ignore valid criticism.

The source excludes unlisted general review services, disparages low-cost marketplace reviews, rejects AI-only tools as a substitute for required human review, and disallows unlisted paid reviewers for credit. Preserve these as program-policy proposals. Blanket claims about a marketplace's quality are unsupported; assess the actual reviewer. The four methodology conflicts are removing exclusions, adding guarantee stacks, replacing exact quotations, and drifting from the Primary mechanism. Consult the designated reviewer or mentor rather than automatically adopting or rejecting advice solely because it is paid.

The four proposed removal triggers are three or more materially disruptive reports, missing at least twenty percent of quarterly deadlines, an agreement violation such as using review time to upsell, or leaving the field/not renewing the agreement. The document proposes quarterly updates, thirty days' notice and possible later re-entry. These are not actions taken against any person.

Review the process itself

After a cohort, examine the proportion using each route, median request-to-delivery time, the proportion meeting deadlines without escalation, and the proportion of paid feedback conflicting with the stated methodology. The SOP proposes revisiting capacity above thirty-percent mentor substitutions, agreements or roster choices above twenty-percent paid conflicts, and cohort discussion below a 0.85 given/received ratio. These are proposed thresholds, not validated universal benchmarks.

Its additional escalation triggers are three or more failed submissions by one student, fabrication or conflicting reviewer feedback requiring agreement review, an individual reciprocity ratio below 0.5 across two cohorts, and more than three consecutive weeks of thin participation prompting a recruitment review. Define denominators and review evidence before acting. The source's promise that a validator will not penalize alternate routes needs actual implementation verification.

The practical output is a stable reviewed draft, genuine feedback, a decision log, correctly recorded review credits and explicit unresolved issues. Connect Brunson/ClickFunnels message continuity with the Hormozi/Acquisition.com value lens: review whether the promise, evidence, exclusions and delivery agree. Do not mistake template completion, agreement between two reviewers or a numerical score for proof of buyer demand.

Clickable linked resources

- Preparation checklist - Six outreach and response templates - Peer-review coordination SOP - Complete review template - Alternate protocols - Paid-review reference with placeholder roster

Preserve all six complete originals in the applicable lesson appendices. Their dates, templates and embedded operational instructions remain source material, not current service promises or actions executed by this task.

Assigned source links

D0435 original source 1

Complete native original body, including retained document-part text

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*
Complete linked peer-review resource: D1458

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*
Complete linked peer-review resource: D1594

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*
Complete linked peer-review resource: D3189

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
Complete linked peer-review resource: template

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*
Complete linked peer-review resource: alternate

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*
Complete linked peer-review resource: paid

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*
Complete local source copy including original filing metadata and formatting

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*

Evaluate a course deployment SOP before treating it as operational

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Read the source's ten-part deployment SOP as a proposed operating design: inventory the assets, identify gaps, compare three deployment paths, trace the build order, assess remediation, define operating responsibilities and interpret every success metric. Its legacy C4, Stage 1 and Dinghy labels do not replace the current twelve-course spreadsheet. No source deployment, payment, outreach or enrollment instruction is executed by this lesson.

1. Separate the executive summary from verified inventory

The source describes turning a validated Primary mechanism into a named offer with a buyer, price, exclusions, guarantee and seven-section page. It claims fifty-five files, roughly eighty-one thousand words, eight lessons, sixteen resources, six Claude prompts, a complete Supabase schema, four SOPs and four cases. These are source inventory claims, not proof each asset exists or works.

The stated missing items are seven video specifications for M4.2–M4.8, estimated at eight to twelve hours; aggregated accessibility statements for Stripe, PayPal, Zapier, Circle.so and Google Drive, estimated at two hours; and Build 6 application handlers. The source calls its internal audit 92/94, with fifteen of sixteen essentials and NOT_CERTIFIED status. That is not verified official certification.

Its three launch estimates are Path A, a minimum viable cohort, at eight to fifteen hours; Path B, an LMS-hosted course, at thirty to sixty; and Path C, a full build stack, at 200–400. These are historical planning estimates, not the runtime of this project. A uses Drive, Circle and manual reviews; B moves content into an LMS with native or assisted progression; C uses custom application orchestration over Supabase.

The source assumes C3 is operational and at least one cohort has completed, recommending four or more weeks between that completion and C4 enrollment. Its statement that an unprepared student will fail within thirty minutes is unsupported here. The actionable principle is to inspect the required research before depending on it.

2. Reconcile the nine folders and the specialized assets

The numbered folder counts are: overview five; lessons nine; resources sixteen; scripts and prompts eight; tools and infrastructure three; checkpoints three; SOPs four; cases four; community one. They sum to fifty-three, not the source's stated fifty-five. Another handoff requests forty-eight to fifty files. Keep the counts and discrepancies in the inventory rather than silently choosing one total.

The source lists the first written lesson at 2,522 words plus a 1,271-word video specification. Its approximate written counts for M4.2–M4.8 are 2,800, 2,900, 2,600, 2,700, 2,800, 3,100 and 2,700. Only the first has a video specification. A word count measures size, not instructional coverage or accessible media production.

Specialized assets include signed anti-promise and guarantee commitments, an Opus offer-fit validator, the Feature Stuffing case, the first-sale checklist and alternate peer-review protocols. The named cases Maya, Darius and Priya are expected journeys described by the source; it asks for real anonymized first-cohort cases later. Do not present the expected journeys as actual results.

The six version-1.0.0 reviewers are distinction, Value Equation application, decomposition, landing-page copy, readiness and final offer fit. The source assigns five to Sonnet 4.6 and the final one to Opus 4.7. Its per-call assumptions are $0.04–$0.08 for each routine reviewer except copy at $0.06–$0.12, and $0.30–$0.55 for final validation. Its $0.80–$1.50 typical total is not a guaranteed bill. Model existence is supported by Anthropic's Opus 4.7 announcement; actual pricing, token use, retries and account access need checking before a separate implementation.

Maintain all prior-context relationships: the territory oath goes to distinction and final fit; operator identity to final fit; the mechanism hypothesis to distinction; the Market Fit Hypothesis to every reviewer; the Trigger Bank to Value Equation, copy and final fit; pricing signals to final fit; and interview summaries to Value Equation and final fit. Context supports comparison but does not prove the evidence is true.

3. Account for every gap category

Content gaps include the seven missing video specifications, uncompiled vendor accessibility information and real cohort outcome evidence. Infrastructure gaps include application handlers, production model access and automatic Drive-folder provisioning, with manual folder creation proposed as a fallback. The source estimates handlers at forty to sixty engineering hours here, while its later build-order table uses forty to eighty.

Integration gaps include a cross-stage pool of at least five active alumni, a current approved paid-reviewer roster, and a tested completion-to-enrollment handoff. A template roster does not establish that named reviewers are available. The source proposes testing one PASS transaction, but an authored implementation review would also need to consider failed and unauthorized paths before trusting access changes.

Operational assumptions include a five-percent first-attempt failure rate, thirty mentor minutes per failure, forty-five minutes per Protocol A activation when cohorts are below eight, and quarterly reviewer-roster refreshes. These are planning hypotheses rather than observed capacity or outcomes.

The specific data requirements are signed-integrity and signed-honesty booleans that default false and cannot be null, elapsed draft timestamps for forty-eight-hour cooling, and an Opus per-student ceiling of $1.10 across completion and revisions. The separately reviewed Supabase C4 schema contains eight artifact tables plus a review log and enrollment/completion checks. It does not prove that reviewers, timestamp checks, notifications or every named application handler are deployed. The final review-chain source names additional routing functions not defined in that schema.

4. Understand Path A's manual operating work

The Path A prerequisites are prior-course operation and a completed cohort, a provisioned database with earlier schemas, a ready C4 schema, a per-student Drive template, the community channel and welcome post, model access, and mentor coverage. The source recommends two mentors for ten to fifteen students; actual capacity must be assessed.

Its week-by-week plan assigns schema deployment and smoke testing to engineering at week minus six; folder permissions to operations at minus five; community channels to community staff at minus four; enrollment announcement to marketing at minus three; mentor briefing and cohort leads to curriculum at minus two; one test student's checkpoint to engineering and curriculum at minus one; and initial submissions to students at week zero. Saying “four weeks out” at minus three conflicts with that week-zero start; fix the calendar before a real announcement.

Manual work includes invoking each reviewer and logging the result, estimated at five minutes per submission; matching peers, estimated at thirty minutes per cohort per week; checking cooling timestamps; and manually running final validation and communicating its verdict. These tasks need owners and records. Teaching them does not invoke a model or contact a learner.

The eight launch checks are the tested schema, shared folder template, ready channels, provisioned model access, mentor coverage for the first eight weeks, a first-checkpoint smoke test, an announced date with a tested payment path, and a trained cohort lead. The source proposes these actions; their presence in a checklist is not evidence that they have happened.

5. Evaluate Path B without treating historical prices as recommendations

The source compares Kajabi, Thinkific Plus and Circle Spaces Pro. It describes integrated community/payment/email for Kajabi with less AI-integration flexibility; assignment and cohort workflows for Thinkific with weaker community/payment fit; and community continuity for Circle with less mature course features. Its price examples—$199–$549, $499 or more, and $99–$399 monthly respectively—are unverified historical figures, not current quotes.

The source prefers Circle initially and suggests considering Kajabi at fifty or more students if needed. That is its proposed decision, not a current recommendation to migrate this GoHighLevel project. Assess actual requirements, current terms and a tested workflow before a separate platform decision.

Its migration plan places eight lesson files in the LMS while preserving headings; ten templates as downloads or embedded copyable content; two worksheets as assignments with required fields; references in a library; four cases as supplementary lessons; and YAML prompts in a code repository rather than learner pages. A proposed automation layer sends submissions through a webhook and model review, returns results, gates progression, sends welcome and checkpoint notices, and provisions payment/community access. Its three-hour setup estimate per reviewer is illustrative.

The suggested transition signals are a completed first cohort with feedback, more than eight manual lead hours per week, often at fifteen or more students, and moving before a third cohort. Its claim that A handles two cohorts and B about five is an unvalidated capacity assumption. Measure the actual load.

6. Trace Path C's architecture and all eight build steps

Build 1 hosts Supabase tables, policies and functions. Build 6 is intended to orchestrate checkpoints, matching, final validation, escalation and dashboards. Build 8 manages Drive provisioning, permissions and portability. D4 is a paid-media preview consuming copy at legacy C8, and Build 14 is a causal-modeling preview using artifacts at C42. These are design references, not activated systems.

The build-order estimates are: schema eight to sixteen hours; checkpoint handlers forty to eighty; peer matcher sixteen to twenty-four; final-gate handler sixteen to twenty-four; mentor routing eight to sixteen; Drive integration eight to sixteen; dashboard views sixteen to twenty-four; and end-to-end testing eight to sixteen. Their total is 120–216 hours. This differs from the executive 200–400-hour range and the earlier forty-to-sixty-hour handler estimate. Preserve the ranges and their uncertain scope. The source's four-to-eight-week calendar at thirty to fifty weekly hours is another assumption, not a fixed conversion of those totals.

Its adoption signals are three or more concurrent cohorts, more than thirty students per cohort, Stage 2 courses within six months, multiple pacing patterns straining manual operations, and causal-modeling use. These signals invite a cost-and-capacity review; none automatically justifies a custom build.

7. Separate remediation from official certification

The source lists seven P1 video-specification tasks, one for every module from M4.2 through M4.8, each at one to two hours, and a P2 vendor-accessibility file at two hours. The seven tasks total seven to fourteen hours; other source summaries say eight to twelve or eight to fourteen, while the separate handoff predicts fifty-five to ninety-five. Resolve the scope of specifications, produced media, accessibility and review before estimating completion.

The SOP claims these changes would move a partial SRS 8.3 to met, make all sixteen internal essentials pass and change status to CERTIFIED. That is not established. Quality Matters' rubric information and official-review certification information distinguish external standards and review from an internal score. Video scripts alone do not establish accessible media or certification.

The source discusses launching a pilot with written lessons while remediating, or waiting where institutional requirements demand certification. Treat these as proposed options. An actual release must be evaluated against the intended learners' needs and verified requirements; this lesson does not authorize publication or assert readiness.

8. Assign the operating cadence and final-gate checks

Daily duties are review-queue handling, mentor escalation monitoring, community support and refund-queue inspection. The source's zero-to-two refunds per week is not a forecast. Weekly duties are Monday check-ins and pacing review; Wednesday review-SLA inspection; Friday reflection and identification of struggling learners; and a thirty-minute cohort retrospective, including patterns such as three or more students stuck on one module.

Monthly reporting covers enrollment, completion velocity, rubric pass rates, final-validator results, escalation volume and cost. Quarterly work refreshes paid-review options, tier rosters and agreements, and rechecks the internal quality audit. Annual work revisits methodology, differentiation and market fit. These are operational responsibilities to plan, not automations or outreach activated here.

The final-gate cost checks flag calls exceeding the source's $0.55 assumption and students exceeding its $1.10 ceiling. Its proposed verdict mix is sixty-percent first-pass, thirty-percent revision and five-percent fail—only ninety-five percent in total. The missing five percent needs a defined category or corrected assumptions. Quarterly model reassessment should use current cost and evaluation evidence rather than assuming a future cheaper model is adequate.

9. Interpret every proposed metric as a target, not a result

Structural targets are sixty-five to seventy-five percent first-cohort completion and seventy-five to eighty-five percent sustained; four to five median weeks, flagged above six; one to 1.2 median submissions, flagged above 1.5 in a module; seventy to eighty percent routine first-pass; and the sixty/thirty/five final-verdict mix with its unexplained remainder.

Quality targets are one-hundred-percent signing of each integrity commitment; at least fifteen verified Trigger Bank entries, with twenty-five celebrated; less than ten-percent feature-stuffing flags, with twenty percent or more flagged; and less than five-percent detected mechanism drift. Signing or meeting a count does not establish truthfulness or instructional quality by itself.

Cohort targets are a reviews-given/reviews-received ratio of at least 0.85, flagged below 0.70; at least eighty-five percent of reviews within seventy-two hours, flagged below seventy; alternate protocols below thirty percent, with above forty flagged; at least five active cross-stage alumni, flagged below three; mentor utilization around sixty percent, flagged if sustained above eighty-five; and at least fifty percent making a first sale by month three after completion. The last is a downstream outcome hypothesis, not an income promise. Define denominators, time windows, missing-data handling and evidence before reporting any of these measures.

10. Use the glossary and references with accurate limits

The glossary defines an anti-promise as scope and outcome exclusions; feature stuffing as compensating for weak outcome or confidence with added items; Grand Slam Offer as the Hormozi-associated offer framework; signed honesty and integrity commitments; an Opus completion gate; the earlier Primary mechanism; the three-variant Six Percent Rule; and a Trigger Bank of at least 200 entries, with fifteen used in copy. These are the source's nine concepts, not proof of a deployed system.

Its bibliography names Abraham (2000), Brunson's DotCom Secrets (2015) and Expert Secrets (2017), Hopkins (1923), Hormozi (2021), Ries's Lean Startup (2011), and Walker's Launch (2014). Preserve the references while distinguishing the source's synthesis from direct quotations or empirical findings. Its version is 2.0, dated April 24, 2026, with a stated July 24 review date and cross-references to earlier deployment SOPs. A planned review date does not establish that review happened. The Word header and page-number fields belong to the document, not the operating workflow.

The authored Brunson/ClickFunnels connection is consistency from the buyer-facing story through the offer and delivery. The Hormozi/Acquisition.com connection is to evaluate outcome, evidence, delay, effort and fulfillment economics. For practice, mark each deployment item as verified, proposed, missing or conflicting, attach its source link, and choose the next evidence-gathering step. Do not equate an attractive architecture with a shipped training product.

Clickable assigned source

- C4 Offer Ignition — Deployment SOP

This assigned URL refers to the retrieved DOCX source. Preserve the original binary, complete extracted text, all eight tables and header/footer information in the lesson's source materials. Source instructions remain historical data and are not executed.

Linked resource workshop: prepare, request, deliver and reconcile a peer review

The six linked documents supply the practical peer-review material referenced by the offer-course plans. They are legacy templates and operating proposals, not evidence of a currently staffed RISER service. Read them together: the preparation checklist establishes inputs, outreach scripts coordinate people, the review template structures feedback, the SOP sequences work, alternate protocols address missing capacity, and the paid-review reference describes proposed selection rules. No message, booking, payment or scholarship request is sent by this workshop.

Prepare all eight checklist groups

Group A requires the named landing-page file and seven sections in order: Problem, 200–400 words; Agitation, 150–300; Solution-and-Mechanism, 300–500; Proof, 200–400; Offer, 300–500; Anti-Promise-and-Guarantee, 250–400; and CTA, 50–150. The individual ranges sum to 1,450–2,650, while the required total is 1,800–2,500. Both conditions can be satisfied, but one does not automatically imply the other. These are template targets, not proof that a page of that length will convert. Compared with the handoff's ten-element list, two pairs are grouped and urgency has no separate heading; explain relevant truthful timing without inventing scarcity.

Group B requires a named Trigger Bank Provenance Log, at least fifteen entries, exact source wording, a TB identifier or interview reference, and distribution across at least four page sections. Matching fifteen quotations is not a substitute for the full bank's evidence quality. Keep permissions, confidentiality and attribution appropriate to the destination.

Group C compares the page's exclusions with M4.5 and its guarantee with M4.6. Softening must be reverted or justified in the record; added guarantee stacking should be removed under this template's policy. Both integrity signatures are required. Group D checks the tested offer name, one visible price rather than a hidden range, payment options, engagement model, duration, cadence and no more than eight deliverables. A signature and a count are structural checks, not proof of truthfulness or viability.

Group E asks for specific named or appropriately anonymized evidence, an explicit known-weakness acknowledgment when there are fewer than four named cases, and attributed, exact testimonials. Do not invent a fourth case or disclose an identity to meet a template. Group F requires a specific action, actual enrollment or cohort timing, a qualification process if applicable, and a real pre-purchase contact. Group G requires reading the page aloud, removing phrases the operator would not say, checking unsupported hyperbole, and avoiding the source's four low-substance phrases: “game-changer,” “revolutionary,” “transform your life,” and “all you need to do is.” These are editorial preferences, not a comprehensive truthfulness test.

Group H prepares links to the page and provenance log, two or three positioning sentences, a request for two template-based reviews within seventy-two hours, and specific availability to reciprocate. The checklist's fifteen-to-twenty-minute estimate and claimed thirty-to-sixty-minute reviewer saving are unverified assumptions.

Its five common fixes are to restore softened terms; add three to six genuine missing quotations, often in problem and agitation; examine excess deliverables for unnecessary padding; show the actual price in the offer section; and use a forty-eight-hour reread to repair unnatural voice. Add only what is genuinely missing rather than assuming three extra quotes always reaches fifteen. After submission, check reviewer pickup daily, answer questions, keep the reviewed version stable and begin reciprocating. The stable-version rule prevents two reviewers evaluating different drafts.

Use the six coordination scripts as templates, not automatic messages

The request script identifies the operator, tested offer name, buyer, price and one or two suspected weaknesses. It links the page, provenance log and any existing Revision Log, proposes seventy-two hours, and states specific days for reviewing the first two reciprocal requests. Naming a focus may help, but the claim that it reliably improves feedback is not established by data here.

The acceptance script names the requester, confirms the chosen focus or full-template review, and gives a specific delivery date and time, aiming for forty-eight hours. That is shorter than the general seventy-two-hour target; state which commitment was actually made. The decline script explains capacity if useful, refers to a genuinely available person, and points to alternate review options. Do not tag someone or promise mentor capacity without knowing it exists.

The delivery script links the completed template, gives one overall observation and three recommended revisions, and offers optional asynchronous discussion. The response script addresses every recommendation as incorporated, incorporated with modification, or not incorporated with a reason, then links the Revision Log. The escalation script identifies the pacing window, requests and responses, attempted alternate routes, specific help needed, page link and revised timeline. The source routes it to a mentor channel or a welcome-email Calendly link, neither of which is supplied as a verified current contact.

The etiquette section favors reciprocity, precise observations, honest criticism and timely responses. Its example contrasts generic praise with identifying performative “wasted years” wording in a particular paragraph. Be candid and respectful; honesty does not require harshness. The source calls reciprocity a culture norm rather than enforced policy. It encourages personal voice especially in request and delivery scripts, with logistics scripts closer to their templates. Claims that personal voice correlates with better responses or missed SLAs are the largest disruption cause are source assertions, not measured findings here.

Complete the entire review template

Read the page and provenance log together, looking for buyer-language fit, quotations that support specific claims, and exclusions or guarantees weakened during copywriting. The source estimates forty-five to sixty minutes and a seventy-two-hour request-to-delivery target. Record reviewer name, reviewer archetype, date, submitting operator and offer name. The task is structural feedback, not rewriting every line.

Rate each section strong, adequate or weak. For Problem, restate the problem in one sentence, assess whether the buyer's state is vivid or generic, and whether at least one quotation is meaningful, then add one to three specific observations. For Agitation, distinguish real, mixed and performative consequences and identify any supporting numbers, timeframes or opportunity costs. Do not manufacture emotional pressure or unsupported losses.

For Solution-and-Mechanism, explain the mechanism in your own words and check whether its four referenced pillars are visible; missing pillar definitions remain a separate dependency. For Proof, distinguish specific, mixed and generic cases and check whether limited evidence is honestly acknowledged. For Offer, inspect the name, visibility of price and concrete delivery experience—what happens, when and with whom.

For Anti-Promise-and-Guarantee, rate the two parts separately. Count three or more genuine exclusions, two, or one or fewer. Identify disguised flattery such as “not for unmotivated people.” Compare one primary guarantee plus an optional complementary element with borderline or three-plus-component stacking. Consider whether stated claim conditions appear understandable and realistically usable, without treating component count as a conclusive legal or ethical judgment. For CTA, check a specific action, outcome and actual timeline. The source's February 12 enrollment and twenty-four-hour welcome-kit example is fictional illustration, not a current date or promise.

Across the whole page, sample three quotations against provenance and classify them as exact, slightly paraphrased or significantly paraphrased. Record overall strong, mixed or weak provenance, but recognize that a three-quote sample cannot verify every quotation. Assess buyer versus operator voice, then count all fifteen required entries. Give three actionable revisions—for example, shortening a particular four-sentence opening to two—rather than an abstract request to improve copy. Close with ready, moderate revision or substantial revision, a hypothetical yes/maybe/no buying reaction with reasons, and a signature. A peer's hypothetical buying reaction is not an actual purchase or validation result.

Follow the SOP's sequence, roles and timing

The SOP requires the page draft, provenance log, completed preparation checklist and a forty-eight-hour cooling period. Its seven roles are the submitting student, two peer reviewers, mentor, cross-stage reviewer, paid reviewer and proposed Build 6 coordinator. The source assigns automated notifications, matching, tracking and gates to Build 6; those operations have not been verified or deployed here.

Step one is a twenty-minute self-audit of checklist groups A–H, quotations and unchanged terms. Missing provenance, fewer than fifteen entries or softened exclusions cause rework; the source's twenty-four-to-forty-eight-hour delay estimate is illustrative. Step two is a fifteen-minute request using the structured script, both document links, suspected weaknesses, the review target and reciprocal availability. Vague requests and missing attachments should be fixed before relying on a review.

Step three allows twenty-four to forty-eight hours for pickup and requires two commitments with delivery dates. The SOP activates alternatives when fewer than two commit within forty-eight hours, whereas the separate alternate document uses seventy-two hours without response. Keep that conflict visible. Reviewers should communicate a threatened deadline instead of missing it silently.

Step five allocates thirty minutes to reading both completed reviews together before acting. Capture common themes and disagreements, then allow the SOP's suggested twelve-hour gap before revision. Two reviewers agreeing is a reason to investigate, not proof that their judgment is correct. Step six allocates sixty to ninety minutes to decisions in the Revision Log and the revised page. Record every recommendation and its disposition; do not accept all feedback mechanically or omit disagreement silently.

Step seven budgets ninety to 120 minutes for two reciprocal reviews, forty-five to sixty each, using the template and delivery script. Discuss actual capacity instead of treating an access need as bad faith. Step eight budgets five minutes to submit and five for the proposed AI run. It requires page, provenance and revision logs, a score of at least seven out of ten and no integrity flags. Its activities say review count at least two, while its quality gate says exactly two. An implementation must reconcile that difference and distinguish review credits from actual people; it must not fabricate a second reviewer when one mentor review counts as two credits.

Apply alternate routes with explicit review credit

Use alternatives when fewer than four people are active at compatible pacing, no response arrives within the stated window, or the student is ahead or behind the cohort. The alternate document proposes escalation within seventy-two hours of draft completion if no route is viable, which can conflict with longer windows below. Define the applicable clock before promising completion.

Protocol A proposes a forty-five-minute mentor call, with the draft and provenance log submitted at least twenty-four hours beforehand. A completed written template counts as both required review credits. The alternate document gives seventy-two hours typically and ninety-six worst case, at no charge; the SOP separately describes twenty-four hours from activation and delivery within seventy-two. These are conflicting source service assumptions, not verified current support. A mentor backlog of two or more weeks is the stated reason to try B.

Protocol B requests one or two volunteer Stage 2-or-higher reviewers, naming archetype, territory, offer, a ninety-six-hour target and both document links. It mentions Stage 2, 3, 4 and 5+ volunteers, no charge and reciprocal ecosystem credits. One cross-stage review may count as two credits or be paired with another review under the source policy; record the chosen interpretation. The SOP limits one description to Stages 2–5. If no one picks up within forty-eight hours, the source points to C. Experience may be useful, but it does not guarantee a superior review.

Protocol C is a direct paid engagement when A and B are unavailable in the planned week. The Academy is not described as handling payment. A paid review counts as only one credit and needs a peer, mentor or cross-stage counterpart. The source's typical price is $150–$400 and turnaround forty-eight to seventy-two hours by contract; the roster's A1 range reaches $450. Preserve that discrepancy. It also proposes that waiting three to five extra days for an unpaid route may be preferable. No paid service is recommended as currently available or purchased here.

The scholarship provision names the unverified legacy address [[email protected]](mailto:[email protected]), a specific scholarship-request subject, page link, pacing dates and attempted routes. It proposes a forty-eight-hour reply and one review covered up to $200 if approved. This is not a current verified service, funding commitment or permission to send a message. The protocol log records route, actual reviewer names, dates and one or two rationale sentences. Its shorthand for C omits a peer as the counterpart despite the prose allowing one; preserve and resolve that inconsistency.

Evaluate the paid-review reference without inventing a roster

The five proposed selection criteria are at least twenty relevant prior page reviews, familiarity with mechanism-based offers, respect for truthful exclusions, a signed methodology agreement and useful ratings from at least five reviewees. The document contains placeholder slots, not current names or contact details, so it does not establish that any provider is actually vetted or available.

Tier A describes ten-plus years of experience: A1 at $350–$450 with seventy-two hours for coaching, consulting and Teacher/Service work; A2 at $300–$400 with forty-eight to seventy-two hours for productized services and Builder work. Tier B describes five to ten years: B1 at $200–$275 with forty-eight to seventy-two hours for Creative work; B2 at $175–$250 with seventy-two hours for B2B, platforms and Systems work. Tier C describes five rotating Stage 2+ alumni slots at $150–$200 with forty-eight to seventy-two hours and archetype matching. All numbers and availability claims are historical template data, not current quotations.

Its five engagement steps are to find the actual current roster, match relevant expertise, provide the draft and provenance log with the required template, explain the methodology baseline, and log the engagement. The baseline preserves mechanism, exclusions and guarantee honesty while requesting critique within that approach. A reviewer should still flag unsupported or unsuitable commitments; methodology must not become a reason to ignore valid criticism.

The source excludes unlisted general review services, disparages low-cost marketplace reviews, rejects AI-only tools as a substitute for required human review, and disallows unlisted paid reviewers for credit. Preserve these as program-policy proposals. Blanket claims about a marketplace's quality are unsupported; assess the actual reviewer. The four methodology conflicts are removing exclusions, adding guarantee stacks, replacing exact quotations, and drifting from the Primary mechanism. Consult the designated reviewer or mentor rather than automatically adopting or rejecting advice solely because it is paid.

The four proposed removal triggers are three or more materially disruptive reports, missing at least twenty percent of quarterly deadlines, an agreement violation such as using review time to upsell, or leaving the field/not renewing the agreement. The document proposes quarterly updates, thirty days' notice and possible later re-entry. These are not actions taken against any person.

Review the process itself

After a cohort, examine the proportion using each route, median request-to-delivery time, the proportion meeting deadlines without escalation, and the proportion of paid feedback conflicting with the stated methodology. The SOP proposes revisiting capacity above thirty-percent mentor substitutions, agreements or roster choices above twenty-percent paid conflicts, and cohort discussion below a 0.85 given/received ratio. These are proposed thresholds, not validated universal benchmarks.

Its additional escalation triggers are three or more failed submissions by one student, fabrication or conflicting reviewer feedback requiring agreement review, an individual reciprocity ratio below 0.5 across two cohorts, and more than three consecutive weeks of thin participation prompting a recruitment review. Define denominators and review evidence before acting. The source's promise that a validator will not penalize alternate routes needs actual implementation verification.

The practical output is a stable reviewed draft, genuine feedback, a decision log, correctly recorded review credits and explicit unresolved issues. Connect Brunson/ClickFunnels message continuity with the Hormozi/Acquisition.com value lens: review whether the promise, evidence, exclusions and delivery agree. Do not mistake template completion, agreement between two reviewers or a numerical score for proof of buyer demand.

Clickable linked resources

- Preparation checklist - Six outreach and response templates - Peer-review coordination SOP - Complete review template - Alternate protocols - Paid-review reference with placeholder roster

Preserve all six complete originals in the applicable lesson appendices. Their dates, templates and embedded operational instructions remain source material, not current service promises or actions executed by this task.

Supporting schema: complete reviewed teaching

Trace the offer curriculum through its database schema

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source boundary

Explain how each proposed C4 artifact is stored, what its checks actually enforce and where review or application controls are still needed. This is the complete version 2.0 schema dated April 24, 2026, written for the operator or developer deploying or auditing Build 1. It depends on the C1, C2 and C3 schemas and their referenced tables. This lesson reviews its SQL as source material; it does not execute migrations or claim a deployed database.

The schema separately supplies the `c4_value_equations` table named in D0404. That resolves the earlier lack of an accompanying table definition in the worksheet's own file. The separately assigned D0413 supplies its reviewer rubric. Both are now accessible references; actual submission storage, grading and unlocking remain unverified.

Understand the shared record structure

There are eight artifact tables and one review-log table. Each receives a UUID primary key with a generated default and a required user_id referencing public.users; deleting that user cascades to these rows. Artifact rows have a filed_at timestamp defaulting to now, while the log has ran_at. A default is not the same as a required value: the source does not mark every timestamp NOT NULL.

The distinction table is unique by user and memo file, allowing multiple distinct memo files per user. The other seven artifact tables are unique by user alone, so they represent one row per user unless another history mechanism exists. The review log permits multiple events. User indexes support lookup; the log uses a combined user-and-module index. File IDs point to external Drive artifacts; storing an ID does not verify the file's contents, permissions or authenticity.

M4.1: offer distinctions

`c4_offer_distinctions` requires the distinction memo's Drive file ID, component inventory file ID, a zero-to-ten AI rubric score and the Primary mechanism name. An optional foreign key points to the C3 market-fit hypothesis. Its stored generated passed value is true when the score is at least seven. The row records which mechanism and files were assessed; the schema does not itself read those files or prove the score came from an authorized reviewer.

M4.2: the value equation

`c4_value_equations` requires the worksheet file ID, strongest and weakest variable names, citation counts and score. Four optional strength columns accept Strong, Moderate or Weak for dream outcome, likelihood, time and effort. The strongest and weakest fields accept the four full variable names, but no constraint requires them to differ. Trigger-bank citation count must be at least three, interview count at least one and score zero to ten. Passed is generated from score at least seven.

These checks validate declared counts and allowed labels, not the quotations or all per-section evidence required by D0404 and D0413. The four strength fields can be null because an allowed-value CHECK does not make a column mandatory. The worksheet's richer diagnosis and the actual grading rubric remain necessary.

M4.3: decomposition and three variants

`c4_offer_decompositions` stores decomposition and variants file IDs, a total decomposed-deliverables count from six to ten, three variant definitions and a required structural-verification flag. Each A, B and C variant has a required name, engagement model, duration in weeks and deliverable count, plus optional lower and upper price bands. Engagement model is Cohort, 1:1, Self-paced or Hybrid. Each variant's deliverable count may not exceed eight.

Three pairwise checks compare A with B, A with C and B with C. Every pair must differ in engagement model, duration or deliverable count. Changing price or name alone does not satisfy them. These are the actual database tests; deeper assessment of meaningful difference belongs to the named offer-decomposition reviewer. The source's design note says the maximum-eight rule guards against feature stuffing, but a count cannot assess whether the retained deliverables are useful.

The SQL does not require positive duration or a positive minimum variant count, nor does it order or validate positive price-band endpoints. A stored structural_verification_passed flag is supplied, not computed from all qualitative criteria. Keep these limits visible rather than treating acceptance by the table as full validation.

M4.4: pricing decisions

`c4_pricing_decisions` requires a pricing-decision file, observed floor, median and ceiling, a positive anchor price, a pricing strategy and a pay-in-full price. Strategies are Median, Above Market, Below Market (Volume) or Other. Optional fields store installment and deposit descriptions, hours per buyer, effective hourly rate and rationale for deviation from the observed band. Score is zero to ten; at least seven generates passed.

The table can preserve the comparison and unit-economics assumptions, but it does not enforce floor ≤ median ≤ ceiling, positive pay-in-full price or coherent hours and effective rate. Nor does it independently validate the competitor observations. Explain the rationale and evidence in the linked artifact before treating the price as justified.

M4.5: anti-promises and integrity

`c4_anti_promises` requires anti-promise and integrity-statement file IDs, three to six audience exclusions, at least two outcome non-claims and at least two scope boundaries. The required signature Boolean defaults to false. A zero-to-ten score of at least seven and a true signature flag jointly generate passed. This records the boundary and signature assertion; a Boolean by itself is not a verified signature or an enforceable agreement.

M4.6: guarantees

`c4_guarantees` stores the guarantee and honesty-clause file IDs, a required signature flag defaulting false, guarantee type, component count, target weakness, sustainability flag and score. Types are Refund, Outcome, Hybrid, Time-shift and Effort-adjusted. There may be at most two components. The target must be Perceived Likelihood, Time Delay or Effort and Sacrifice. Expected activation percentage is optional. Passed requires score at least seven and a signed-clause flag.

The source records unit_economics_sustainable but does not include it in the generated pass condition. It also does not constrain the percentage to zero through one hundred or require a positive component minimum. Therefore, a row can satisfy the coded pass condition without establishing a sustainable guarantee. The written terms, evidence and authorized review still matter.

M4.7: landing-page copy

`c4_landing_page_copies` requires the page and provenance-log file IDs, permits a revision-log ID, limits total words to 1,000–5,000 and requires at least fifteen claimed Trigger Bank entries. It separately stores the number verified verbatim. Two optional reviewer IDs reference users, each paired with an optional completion timestamp. peer_reviews_complete is generated from the presence of both timestamps.

Passed requires an AI score of at least seven, both review timestamps and at least fifteen verified verbatim entries. The AI score is optional but, when present, constrained to zero through ten. Depending on null inputs, the Boolean expression can produce null rather than false; the completion function counts only passed = TRUE.

No shown constraint requires different reviewers, prevents self-review, ensures reviewer IDs accompany timestamps or ensures verified counts do not exceed claimed counts. The application and reviewer process must establish that the review and evidence are real. A generated Boolean protects its expression from direct assignment; it does not make owner-supplied inputs trustworthy.

M4.8: offer readiness

`c4_offer_readiness_docs` requires readiness and first-sale-checklist file IDs, selected variant A/B/C, final offer name and final anchor price. Signature defaults to false. The optional Opus validator verdict is PASS, NEEDS_REVISION or FAIL, with an optional run timestamp. At least three kill criteria must be declared. Passed requires a PASS verdict and a true signature flag.

This captures the intended final review gate. A Sonnet result elsewhere does not satisfy this explicit Opus-verdict field. However, the field does not authenticate which model or person produced its value, the anchor price is not constrained positive here, and the table stores a kill-criteria count rather than the criteria themselves. The linked artifact and trusted review process remain essential.

Review history and user summary

`c4_review_log` stores user, module M4.1 through M4.8, prompt name, version, required submission count defaulting to one, verdict PASS/FAIL/NEEDS_REVISION, optional integer score, feedback JSON, flags JSON and run time. Its score has no zero-to-ten constraint and submission count has no positive check. Preserve these differences rather than assuming the log has the same validation as every artifact.

The user table gains five columns: completion Boolean defaulting false, completion timestamp, lead variant, final offer name and final anchor price. These are summary fields populated by the shown trigger; their existence alone does not prove current eligibility or completion.

Enrollment eligibility: what is actually checked?

`check_c4_enrollment_eligible` accepts a user ID and returns JSON containing eligible and a missing-items list. It requires C3 complete, a market-fit hypothesis filed within the previous three months, a Trigger Bank with at least 200 entries, a Pricing Signals row and an oath signed within the previous twelve months. The hypothesis uses a strict newer-than boundary; the oath is rejected when missing or older than its boundary.

The function selects C1 completion, C2 completion and operator-identity filing but does not test them. It checks that Pricing Signals exists, not its quality or recency, and it does not validate every dependency named in the worksheet. These are differences between data read, conditions enforced and the broader educational prerequisites.

Completion checks and trigger behavior

`check_c4_completion` returns complete plus missing items after checking all eight artifact stages: distinction passed; equation passed; decomposition structural verification true; pricing passed; anti-promise passed; guarantee passed; landing page passed; and readiness passed. The named missing items retain the expected signature, peer-review and Opus context because those are part of the relevant table expressions.

`update_c4_complete_flag` calls that check for NEW.user_id. When complete, it reads the passing readiness row and sets the user completion flag true, stamps the current time and copies the selected variant, offer name and anchor price. Its trigger runs only after an insert or update to the readiness table when NEW.passed is true.

That means completing another artifact after readiness already passed does not automatically invoke this trigger. Neither deleting supporting evidence nor changing a prior result to failure resets completion through this code. The function only sets true and has no false branch. Repeated qualifying readiness updates can also restamp completion time. These are observations from the supplied SQL, not evidence that a live system currently behaves this way. A production design must decide how to re-evaluate changes and revocations.

Access controls and implementation limits

All nine tables enable row-level security. The eight artifact tables allow selecting, inserting and updating rows belonging to auth.uid(); no DELETE policy is shown. The review log permits owners to select their history, but its insert policy uses WITH CHECK (TRUE) without a TO role restriction. The adjacent service-only comment is not an access restriction. Actual access also depends on grants and runtime roles, which this file does not show.

Likewise, owner-based row access is not field-level grading authority. If ordinary users have the corresponding write grants, these policies do not stop them changing their own scores, verification flags or signature assertions. Review provenance and privileged fields need a defined trusted boundary before this can be treated as an authoritative completion system.

The eligibility and completion functions use SECURITY DEFINER and accept arbitrary user IDs. The shown definitions contain neither a caller-to-user authorization check nor an explicit secure search_path. Supabase's documentation explains the need to secure such functions and their execution permissions. Review those controls and actual grants before implementation; do not infer protection from schema-qualified table names alone.

Migration and operating references

The supplied migration sequence runs c1_schema.sql, c2_schema.sql, c3_schema.sql and then c4_schema.sql using psql with host, user and database placeholders. Reading this sequence does not execute it. Tables use IF NOT EXISTS and the five user columns use ADD COLUMN IF NOT EXISTS, but separate index, policy, constraint and trigger creation statements are not all guarded. The complete file therefore is not automatically safe to rerun unchanged.

The source names five related paths or integrations: RISER-Build-References-for-C4.md, C4-Review-Chain.md, C4-Prerequisites-Checklist.md, Build 6 src/c4_checkpoint_handler.ts and RISER-C4-Weekly-Rhythm-Setup-SOP.md. Their implementation and deployment are not supplied by this schema. Preserve the full SQL, comments, design notes and migration references in the appendix.

Apply the educational connection

This design attempts to turn Hormozi-style offer analysis into traceable artifacts before a Brunson-style offer presentation is finalized. The value of the database is provenance and accountable review, not merely a green completion flag. As authored practice, trace one worksheet from its file ID through cited evidence, rubric score, authorized review and downstream completion. Mark every unverified dependency and every condition the code does not enforce. Deliver a schema-to-artifact map and a review of those gaps; no database deployment is part of this lesson's completion.

Sources and resources

- Complete assigned C4 schema. - D0404: Value Equation Worksheet and D0413: actual reviewer YAML. - PostgreSQL constraints and CREATE POLICY: primary constraint and policy semantics. - Supabase row-level security and database functions: primary access-control references. - Acquisition.com value-equation checklist, ClickFunnels value ladder and RISER NATION CORP.

Assigned source links

D0436 original source 1

Original tables and embedded resource links
D0436 original DOCX table 1; original labels and blank cells retained, claims qualified in teaching
PathEffort to LaunchQM Certified?Best For
Path A — Minimum Viable Cohort8-15 hoursNo (ships with current 92/94)First cohort to validate offer-construction approach
Path B — LMS-Hosted30-60 hoursOptional (remediate SRS 8.3 first)Second cohort onwards; scaled enrollment
Path C — Full RISER Build Stack200-400 hours (Build 6 dependency)Yes (after remediation)Long-term operating model; Stage 2+ continuity
D0436 original DOCX table 2; original labels and blank cells retained, claims qualified in teaching
FolderContentsFiles
00_Course-OverviewREADME, Learning Outcomes, Module Map, Prerequisites, Time Estimate5
01_Module-LessonsM4.1-M4.8 written lessons + M4.1 video spec9
02_ResourcesTemplates, worksheets, checklists, frameworks, swipe file, archetype chart16
03_Scripts-and-Prompts6 Claude YAML prompts + chain documentation + outreach scripts8
04_Tools-and-InfrastructureSupabase schema, Build references, payment processor guide3
05_Checkpoints-and-TestsAll-Module-Checkpoints, QM Audit JSON, QM Scorecard XLSX3
06_SOPs4 SOPs (rhythm, peer review, readiness review, first-sale prep)4
07_Case-Studies-and-ExamplesMaya, Darius, Priya C4 journeys + Feature Stuffing failure4
08_Community-PromptsC4 Circle.so channel prompts1
D0436 original DOCX table 3; original labels and blank cells retained, claims qualified in teaching
ModuleTitleWord CountHas Video Spec?
M4.1Offer Architecture Foundations2,522 (written) + 1,271 (video)Yes
M4.2Grand Slam Offer Framework~2,800No
M4.3Offer Deconstruction and Reassembly~2,900No
M4.4Pricing and Anchoring~2,600No
M4.5The Anti-Promise Statement~2,700No
M4.6Guarantee Architecture~2,800No
M4.7Offer Landing Page Copy~3,100No
M4.8Offer Readiness Document~2,700No
D0436 original DOCX table 4; original labels and blank cells retained, claims qualified in teaching
PromptModelModuleCost/Call
offer-distinction-reviewer-v1.0.0Sonnet 4.6M4.1$0.04-0.08
value-equation-application-reviewer-v1.0.0Sonnet 4.6M4.2$0.04-0.08
offer-decomposition-reviewer-v1.0.0Sonnet 4.6M4.3$0.04-0.08
landing-page-copy-reviewer-v1.0.0Sonnet 4.6M4.7$0.06-0.12
offer-readiness-reviewer-v1.0.0Sonnet 4.6M4.4-M4.6 spot-check + M4.8 pre-screen$0.04-0.08
offer-fit-validator-v1.0.0Opus 4.7M4.8 course-completion gate$0.30-0.55
D0436 original DOCX table 5; original labels and blank cells retained, claims qualified in teaching
WeekActivityOwnerOutput
-6Deploy c4_schema.sql to Supabase productionEngineeringSchema live; smoke-tested
-5Create Drive folder template; configure permissionsOperationsTemplate ready for cloning per enrollment
-4Pin C4 community prompts in Circle.so; establish #cross-stage-review channelCommunityChannels ready
-3Open enrollment; announce target cohort start date 4 weeks outMarketingEnrollment page live
-2Mentor briefing; review SOPs 01-04; assign cohort leadsCurriculumMentors aligned
-1Pre-launch end-to-end test: enroll one test student through M4.1 checkpointEngineering + CurriculumSmoke test passed
0Cohort starts; M4.1 deliverables filed by end of weekStudentsFirst M4.1 submissions
D0436 original DOCX table 6; original labels and blank cells retained, claims qualified in teaching
PlatformStrengthsWeaknessesCost
KajabiNative cohort + community + payment + emailHigher cost; less flexibility for AI rubric integration$199-549/mo
Thinkific PlusStrong assignment workflows; cohort schedulingCommunity is weaker than Kajabi; payment integration less native$499+/mo
Circle Spaces (Pro tier)Already used for community; simplest migrationCourse delivery features less mature than dedicated LMS$99-399/mo
D0436 original DOCX table 7; original labels and blank cells retained, claims qualified in teaching
StepBuildEffortOutput
1Build 1 — Supabase schema8-16 hrsC4 tables + functions live
2Build 6 — checkpoint handlers40-80 hrsPer-module routing operational
3Build 6 — peer review matcher16-24 hrsAuto-matching with SLA tracking
4Build 6 — Opus gate handler16-24 hrsSonnet → Opus orchestration
5Build 6 — mentor escalation routing8-16 hrsFAIL verdicts auto-route
6Build 8 — Drive integration8-16 hrsAuto-provisioning + permissions
7Build 6 — dashboard views16-24 hrsPer-student + cohort-level analytics
8End-to-end smoke test8-16 hrsOne test student through full course
D0436 original DOCX table 8; original labels and blank cells retained, claims qualified in teaching
TaskSRSEffortPriority
Produce Video Spec for M4.2 (Grand Slam Offer Framework)8.31-2 hrsP1
Produce Video Spec for M4.3 (Decomposition and Reassembly)8.31-2 hrsP1
Produce Video Spec for M4.4 (Pricing and Anchoring)8.31-2 hrsP1
Produce Video Spec for M4.5 (Anti-Promise Statement)8.31-2 hrsP1
Produce Video Spec for M4.6 (Guarantee Architecture)8.31-2 hrsP1
Produce Video Spec for M4.7 (Landing Page Copy)8.31-2 hrsP1
Produce Video Spec for M4.8 (Offer Readiness Document)8.31-2 hrsP1
Compile Vendor Accessibility Statements file8.62 hrsP2

Original footer contains PAGE and NUMPAGES fields. These are document pagination fields, not lesson data.

Complete native original body, including retained document-part text

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
Complete linked peer-review resource: D1458

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*
Complete linked peer-review resource: D1594

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*
Complete linked peer-review resource: D3189

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
Complete linked peer-review resource: template

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*
Complete linked peer-review resource: alternate

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*
Complete linked peer-review resource: paid

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*
Complete linked C4 schema; missing implementations distinguished in teaching

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*

Build three genuinely different offer variants

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Decompose one mechanism into named deliverables, assemble three distinct offer variants, compare their differences, test their names, and record a preliminary preference without treating it as final validation. The source calls this the M4.3 worksheet in a legacy course and the 6% Rule. Here that rule means producing three variants before committing; the source supplies no mathematical six-percent calculation.

Gather the three prerequisite artifacts

Open the Mechanism Decomposition Inventory, the M4.2 Value Equation Worksheet and the M4.1 Component Inventory. The first explains the work the mechanism contains. The second identifies strong, weak or fixed value variables. The third shows which offer components exist and which still need production. These names describe source prerequisites; missing files should remain explicit rather than be treated as completed work.

The source places the worksheet in a Build 8 Drive folder and names the c4_offer_decompositions database table and offer-decomposition-reviewer-v1.0.0.yaml structural reviewer. Those are proposed filing and review destinations, not evidence that an integration or reviewer has been deployed. The current spreadsheet continues to determine where this teaching appears.

Part one: decompose the mechanism before assembling offers

Create a separate 400–600-word Mechanism-Decomposition-[YourName]-[Date].md inventory. Begin with the mechanism's Method pillar from the source's C2 Hypothesis Document. Then name each deliverable so a buyer can evaluate it independently.

For each item, record its name, type, duration, delivery format and dependencies. The source's types are audit, template, live call, asynchronous review, reference pack, tracker, contract component or another explicitly described type. Duration can be expressed in hours or sessions. A dependency states which deliverable must come first. Do not hide prerequisite work inside an attractive output label.

The quality question is whether a buyer can explain what they will have when the item is finished. “Discuss your workflow” describes an activity; an authored alternative such as “a reviewed workflow map showing the three agreed handoffs” identifies an inspectable output. That example is added for this lesson, not supplied in the original worksheet. The source suggests six to ten deliverables commonly emerge from a four-pillar mechanism, but provides no evidence that every mechanism should produce that count.

Part two: assemble variants A, B and C using all eight fields

Give each variant the same complete structure. First, enter a provisional name; the naming tests come later. Second, choose an engagement model—cohort, one-to-one, self-paced or hybrid—and write a one- or two-sentence rationale. Third, state the duration and whether participation begins synchronously on a start date or through rolling entry, again with a short rationale.

Fourth, select deliverables from the inventory. Mark what is included, what is excluded and what is available as an add-on. The source uses a check mark, cross and plus sign for those distinctions. A buyer should not have to purchase an undisclosed add-on to obtain the promised core result.

Fifth, record a price range rather than a final anchor. Position it against the observed pricing band as floor, mid-floor, median, mid-ceiling, ceiling or above ceiling. A single-number price is chosen in the later pricing activity. Sixth, identify the primary Value Equation weakness addressed—Dream Outcome, Perceived Likelihood, Time Delay, or Effort and Sacrifice—with an optional secondary target and a short explanation of how the design addresses it.

Seventh, describe buyer fit: the relevant interview subsegment, the approximate number of interviewees who match it out of the total, and the supporting interview references. Do not invent names or counts. Preserve appropriate confidentiality in learner-facing materials. Eighth, record the tradeoffs against each of the other two variants. Repeat all eight fields for B and C; their abbreviated source headings mean the same full structure is required, not that their explanations can be omitted.

Make the variants different on at least three axes

Compare engagement model, duration, deliverable density and price band. The source groups duration as short at two to four weeks, medium at five to eight weeks, and long at nine or more weeks. It groups density as high with all decomposed deliverables, medium with five or six, and low with three or four self-serve deliverables. Price bands use the observed floor, median and ceiling. These are worksheet categories, not universal market definitions.

Each pair of variants must differ on at least three of the four axes. A useful authored example is a three-week self-paced version with four selected deliverables near the observed floor, a six-week cohort with six deliverables near the median, and a ten-week one-to-one version with eight deliverables near the ceiling. It illustrates four differences; it does not establish buyer demand, a feasible outcome or appropriate prices. Confirm each version can still deliver its stated promise.

The source's matrix asks whether all three are distinct on an axis, then describes a minimum of three yes responses per variant. Those are not identical tests: pairwise difference can be satisfied even when an axis does not contain three unique values. Record the pairwise comparisons explicitly. If using the stricter all-three-distinct matrix as an additional local rule, label it as such instead of silently conflating the two tests.

Part three: check density and naming

Count the deliverables in A, B and C. The source first says more than eight should trigger a feature-stuffing review, while its final structural checklist says no variant may contain more than eight primary deliverables. Preserve that distinction: a review flag in one section becomes a hard submission limit in another. For this worksheet, document which items are primary, optional and excluded; do not bypass the limit by renaming a necessary deliverable a bonus. The decomposition inventory may contain six to ten items even when each selected variant contains no more than eight primary items.

More than eight items does not itself prove that an offer is padded. Inspect whether each item is needed for the outcome and whether additional features are compensating for weak demand or weak confidence in the result. The referenced Feature Stuffing Trap case is a separate asset; this worksheet supplies the warning, not the complete case.

Apply all five naming tests to every provisional name: searchable, specific, durable, pronounceable and ownable. In an authored review, searchable asks whether the intended audience can locate and distinguish it; specific asks whether it communicates something useful; durable asks whether it survives an anticipated change; pronounceable asks whether people can say and repeat it; and ownable asks whether there is a defensible identity and any rights questions requiring further review. These explanations operationalize the labels; the source does not provide a full legal clearance procedure. Passing a worksheet checkbox does not establish trademark rights. Rename any variant failing a test before the later pricing step.

Part four: record a preliminary lead and preserve uncertainty

The optional lead-variant note states the current preference, a one- or two-sentence reason, and what pricing or unit-economics evidence is needed before commitment. The source places formal selection at M4.8 and says the intervening pricing, anti-promise, guarantee and copy activities should test the variants. Keep the preference provisional rather than discarding the alternatives before they are examined.

Record the operator name, first-draft date, second-draft date after the proposed 48-hour cooling period, and total word count. The source targets 1,500–2,000 words total while also requiring 500–700 per variant; three times that individual range allows up to 2,100. To satisfy both stated limits, keep each variant within 500–700 and the combined total at or below 2,000. Treat the approximate 180 minutes of work separately from the elapsed cooling period; neither is a performance guarantee.

Review and handoff

The source's structural review expects exactly three variants, 500–700 words each, pairwise difference on at least three axes, no more than eight primary deliverables per variant, and five naming tests for each name. File the worksheet with the decomposition inventory and retain the original evidence links. Its proposed pass result unlocks M4.4, where pricing may be examined for at least one and preferably all three variants. That describes the legacy design, not a verified live system.

The authored Brunson/ClickFunnels connection is to make each offer understandable as a coherent promise and delivery package. The authored Hormozi/Acquisition.com connection is to change delivery in response to a real value obstacle, with evidence and viable fulfillment, instead of creating three cosmetic versions of the same offer. Finish by explaining why a particular buyer would reasonably prefer each variant and what evidence could disprove your explanation.

Clickable assigned source

- C4 Offer Variants Worksheet — original source

Preserve the complete worksheet and both original comparison tables in the lesson appendix, including its placeholders and conflicting checklist wording. This script teaches the available worksheet without inventing completed buyer research or deployed review automation.

Assigned source links

D0437 original source 1

Complete native original body, including retained document-part text

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*
Complete local source copy including original filing metadata and formatting

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*

Design a review chain that preserves evidence and revision history

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Explain the source's six-reviewer, eight-checkpoint offer-review design. Trace pass, revision and escalation routes; identify the evidence each reviewer needs; distinguish peer review from AI review; and control cost and version changes. This is teaching about a proposed legacy C4 workflow. The named database functions, model calls and enrollment changes have not been implemented by this lesson.

Map the six reviewers to the eight checkpoints

The source places its prompt-chain documentation under 03_Scripts-and-Prompts/Prompt-Chains and references Build 6 and Supabase-C4-Schema.md. Five reviewers are assigned Sonnet 4.6; a sixth is assigned Opus 4.7. Preserve those source choices as versioned design details, without assuming account access, current availability or suitability for every learner.

Source prompt, version 1.0.0.yamlIntended checkpointSource cost per callSource typical calls per student
offer-distinction-reviewerM4.1$0.04–$0.081–2
value-equation-application-reviewerM4.2$0.04–$0.081–2
offer-decomposition-reviewerM4.3, structural review$0.04–$0.081–2
landing-page-copy-reviewerM4.7, after peer review$0.06–$0.121–2
offer-readiness-reviewerM4.4–M4.6 spot checks and M4.8 structural pre-screen$0.04–$0.083–5
offer-fit-validatorM4.8 coherence gate, Opus$0.30–$0.551–2

The source estimates $0.80–$1.50 per student across the chain. These are planning assumptions, not measured spend or guaranteed prices. Multiplying the individual ranges does not make that typical total a hard limit: an authored calculation using every minimum in the table gives $0.60, while every maximum gives $2.22. Actual cost depends on token use, retries, context, current pricing and the review path. Anthropic's Opus 4.7 announcement verifies the model's existence and launch API identifier; it does not validate these per-review estimates. Record current model and pricing information before any separate implementation.

Walk the entire serial chain

At M4.1, the distinction reviewer passes a score of at least seven out of ten and sends a lower score back for revision. A pass opens M4.2. The Value Equation reviewer then checks M4.2; a pass opens M4.3 and a failure requests revision. The structural decomposition review at M4.3 returns pass or needs revision, with a pass opening M4.4.

The readiness reviewer performs the M4.4 pricing, M4.5 anti-promise and M4.6 guarantee spot checks in order. Their pass results open the next activity. M4.7 adds peer review before the landing-page reviewer; the diagram requires at least two completed peer reviews and an AI score of seven out of ten or higher to open M4.8. A failed copy review returns to revision.

M4.8 first receives the Sonnet readiness pre-screen. A structural pass permits the Opus coherence review. Needs revision returns to the student. The prose also describes a structural fail returning to revision before Opus, so preserve both labels and define their handling in any implementation rather than silently treating them as different routes. The final validator can pass, request revision or fail. Pass is the proposed course-completion and C5-enrollment trigger; needs revision returns to M4.8; fail routes to mentor diagnosis, possibly reopening the earlier C3 M3.7 decision. A possible upstream cause is not an automatic diagnosis.

The source's diagram highlights the Opus gate in orange (#B45F06), completion in blue (#2E75B6), mentor routing in red (#CC0000), and peer review in gold (#BF9000). Preserve the graph in the appendix, but use labels and this narrated route so that color is not the only way to understand a state. Some revision arrows are abbreviated in the diagram; the accompanying revision policy supplies the return-to-review process.

Handle revisions without trapping the learner

The source describes a first submission receiving pass or guidance, a second receiving pass or possible mentor escalation, and a third automatically entering the mentor queue. It claims Build 6 tracks the count. Treat this as a proposed policy, not proof that it is enforced. A reliable implementation would need a defined attempt count, an inspectable review history and a clear escalation owner.

Serial dependencies are intended to keep later work grounded in accepted earlier artifacts. They do not prove an AI score is correct. An authored RISER review practice is to preserve the original submission, reviewer version, evidence, verdict and explanation so a human can diagnose an incorrect result or an inaccessible requirement. Never quietly rewrite prior evidence to make the current submission pass.

Complete the five peer-review steps before the M4.7 AI review

First, the student shares the draft in the source's c4-offer-ignition community channel. Second, two peers complete reviews. Third, the student incorporates the feedback and produces a Revision Log. Fourth, the revised submission goes to the copy reviewer. Fifth, that reviewer checks the peer count, incorporation and rubric score. The source gives a 72-hour peer-review SLA, while another assigned legacy module map uses 48 hours. Record the conflict; neither is established as the currently promised RISER service level by this lesson.

If the SLA is missed, the source refers to alternate protocols A, B and C in a separate template. The chain document does not define those protocols fully. Preserve the reference and the gap rather than inventing reviewer availability, a paid roster or an automatic substitution. No community message is sent by teaching these steps.

Use structural pre-screening before expensive coherence review

The source calls M4.8 the only module with two AI reviewers. Its rationale is to reject missing structural material before invoking a more costly model, which it describes as roughly five to ten times the Sonnet cost. That multiplier is an illustrative claim dependent on the model, token mix and pricing. It is not a guaranteed saving.

The important design question is whether the pre-screen catches specific missing artifacts while preserving a route for genuine substantive review. A well-formed document can still contain unsupported claims. Conversely, an incomplete form does not establish that the learner's business idea is invalid. Keep those decisions separate.

Supply all seven prior-evidence relationships

The source sends C1 Captain's Oath Clause 1, concerning territory, to the distinction reviewer and final validator. It sends the C1 Operator Identity to the final validator for archetype consistency. It sends the C2 Mechanism Hypothesis to the distinction reviewer as the mechanism-name anchor. The C3 Market Fit Hypothesis goes to every reviewer.

The C3 Trigger Bank goes to the Value Equation reviewer, copy reviewer and final validator. Pricing Signals go to the final validator. Customer Interview Library summaries go to the Value Equation reviewer and final validator. Preserve these relationships in the evidence map. Providing context can help reviewers compare current claims with earlier work, but it does not guarantee coherence or authenticity. Restrict access to the evidence appropriate for each review.

Understand the six named integration functions

The source names check_c4_enrollment_eligible(user_id) for prerequisites; route_c4_submission(user_id, module, artifact_blob) for selecting the reviewer and context; log_c4_review_result(user_id, module, verdict, feedback) for the c4_review_log record; unlock_next_c4_module(user_id, current_module) for progression; check_c4_completion(user_id) for all eight passing artifacts; and route_c4_to_c5(user_id) for the course handoff.

These are interface names and intended responsibilities. The source does not provide their full definitions in this document. Do not present them as executable SQL, deployed functions or proof that completion access is secure. A separate implementation would need to validate identity, ownership, prerequisites and allowed state transitions before making any access change.

Teach all eight failure routes

Mechanism drift is labeled final-validator Check 2.3, blocking, with mentor diagnosis and possible C3 reopening. Fabricated Trigger Bank entries are Check 2.4, blocking, routed to an integrity review. Anti-promise softening is Check 1.3, a warning requiring revision. Feature stuffing in deliverable count or guarantee stacking uses Checks 4.1 and 4.2, also warnings. Silent whitewashing of a weakness uses Check 3.1 and requests revision.

An unsigned signature is Check 5.1, blocking, with a resubmission after correction; the source's thirty-second estimate is not a service guarantee. A Value Equation claiming universal strength triggers Dimension 3 of its reviewer and a request for honest weakness identification. Three variants without sufficient differences trigger decomposition Check 2 and require substantive diversification. Preserve these labels as references to the proposed reviewers; the actual rubric bodies must be reviewed separately before automated use.

Version the policy and retain the applicable rubric

The source starts at version 1.0.0, assigns minor increments to criteria changes and patch increments to threshold changes, and calls for quarterly review by the curriculum-quality team. It also proposes keeping an in-progress revision on the prior version until the checkpoint is cleared while routing new work to a new version.

That minor-versus-patch rule is a local policy, not automatically compliant with Semantic Versioning, which distinguishes changes by compatibility. A threshold change can alter whether the same submission passes. Define the intended compatibility contract and identify an active revision chain separately from a new checkpoint submission, so the two routing statements do not conflict. Preserve which version generated each verdict and tell the learner which criteria apply.

Apply the curriculum's offer themes and verify the design

The authored Brunson/ClickFunnels connection is message continuity: the hook, story, evidence and offer should remain consistent through the review chain. The authored Hormozi/Acquisition.com connection is to inspect the desired outcome, proof, delay, effort and delivery constraints without allowing polished copy to hide a weak offer. Neither theme makes an automated reviewer infallible.

For practice, trace one fictional submission through a pass, a revision and a mentor escalation. Show the reviewer, required context, applicable version and next state at each step. Mark the scenario as an authored exercise. Do not run the named APIs, send messages or change course enrollment to demonstrate the diagram.

Clickable assigned source

- C4 Prompt Chain — original source

The complete original chain, inventory, failure-routing table and diagram remain in the lesson appendix. The separately reviewed C4 schema actually defines check_c4_enrollment_eligible and check_c4_completion, plus update_c4_complete_flag and its trigger. It does not define route_c4_submission, log_c4_review_result, unlock_next_c4_module or route_c4_to_c5. The schema teaching and complete source are included below, so those four missing implementations remain visible instead of being implied to exist. Six separately reviewed peer-review resources now supply the preparation, outreach, template, SOP, alternate and paid-review procedures taught below. Other absent reviewer bodies remain explicit dependencies.

Linked resource workshop: prepare, request, deliver and reconcile a peer review

The six linked documents supply the practical peer-review material referenced by the offer-course plans. They are legacy templates and operating proposals, not evidence of a currently staffed RISER service. Read them together: the preparation checklist establishes inputs, outreach scripts coordinate people, the review template structures feedback, the SOP sequences work, alternate protocols address missing capacity, and the paid-review reference describes proposed selection rules. No message, booking, payment or scholarship request is sent by this workshop.

Prepare all eight checklist groups

Group A requires the named landing-page file and seven sections in order: Problem, 200–400 words; Agitation, 150–300; Solution-and-Mechanism, 300–500; Proof, 200–400; Offer, 300–500; Anti-Promise-and-Guarantee, 250–400; and CTA, 50–150. The individual ranges sum to 1,450–2,650, while the required total is 1,800–2,500. Both conditions can be satisfied, but one does not automatically imply the other. These are template targets, not proof that a page of that length will convert. Compared with the handoff's ten-element list, two pairs are grouped and urgency has no separate heading; explain relevant truthful timing without inventing scarcity.

Group B requires a named Trigger Bank Provenance Log, at least fifteen entries, exact source wording, a TB identifier or interview reference, and distribution across at least four page sections. Matching fifteen quotations is not a substitute for the full bank's evidence quality. Keep permissions, confidentiality and attribution appropriate to the destination.

Group C compares the page's exclusions with M4.5 and its guarantee with M4.6. Softening must be reverted or justified in the record; added guarantee stacking should be removed under this template's policy. Both integrity signatures are required. Group D checks the tested offer name, one visible price rather than a hidden range, payment options, engagement model, duration, cadence and no more than eight deliverables. A signature and a count are structural checks, not proof of truthfulness or viability.

Group E asks for specific named or appropriately anonymized evidence, an explicit known-weakness acknowledgment when there are fewer than four named cases, and attributed, exact testimonials. Do not invent a fourth case or disclose an identity to meet a template. Group F requires a specific action, actual enrollment or cohort timing, a qualification process if applicable, and a real pre-purchase contact. Group G requires reading the page aloud, removing phrases the operator would not say, checking unsupported hyperbole, and avoiding the source's four low-substance phrases: “game-changer,” “revolutionary,” “transform your life,” and “all you need to do is.” These are editorial preferences, not a comprehensive truthfulness test.

Group H prepares links to the page and provenance log, two or three positioning sentences, a request for two template-based reviews within seventy-two hours, and specific availability to reciprocate. The checklist's fifteen-to-twenty-minute estimate and claimed thirty-to-sixty-minute reviewer saving are unverified assumptions.

Its five common fixes are to restore softened terms; add three to six genuine missing quotations, often in problem and agitation; examine excess deliverables for unnecessary padding; show the actual price in the offer section; and use a forty-eight-hour reread to repair unnatural voice. Add only what is genuinely missing rather than assuming three extra quotes always reaches fifteen. After submission, check reviewer pickup daily, answer questions, keep the reviewed version stable and begin reciprocating. The stable-version rule prevents two reviewers evaluating different drafts.

Use the six coordination scripts as templates, not automatic messages

The request script identifies the operator, tested offer name, buyer, price and one or two suspected weaknesses. It links the page, provenance log and any existing Revision Log, proposes seventy-two hours, and states specific days for reviewing the first two reciprocal requests. Naming a focus may help, but the claim that it reliably improves feedback is not established by data here.

The acceptance script names the requester, confirms the chosen focus or full-template review, and gives a specific delivery date and time, aiming for forty-eight hours. That is shorter than the general seventy-two-hour target; state which commitment was actually made. The decline script explains capacity if useful, refers to a genuinely available person, and points to alternate review options. Do not tag someone or promise mentor capacity without knowing it exists.

The delivery script links the completed template, gives one overall observation and three recommended revisions, and offers optional asynchronous discussion. The response script addresses every recommendation as incorporated, incorporated with modification, or not incorporated with a reason, then links the Revision Log. The escalation script identifies the pacing window, requests and responses, attempted alternate routes, specific help needed, page link and revised timeline. The source routes it to a mentor channel or a welcome-email Calendly link, neither of which is supplied as a verified current contact.

The etiquette section favors reciprocity, precise observations, honest criticism and timely responses. Its example contrasts generic praise with identifying performative “wasted years” wording in a particular paragraph. Be candid and respectful; honesty does not require harshness. The source calls reciprocity a culture norm rather than enforced policy. It encourages personal voice especially in request and delivery scripts, with logistics scripts closer to their templates. Claims that personal voice correlates with better responses or missed SLAs are the largest disruption cause are source assertions, not measured findings here.

Complete the entire review template

Read the page and provenance log together, looking for buyer-language fit, quotations that support specific claims, and exclusions or guarantees weakened during copywriting. The source estimates forty-five to sixty minutes and a seventy-two-hour request-to-delivery target. Record reviewer name, reviewer archetype, date, submitting operator and offer name. The task is structural feedback, not rewriting every line.

Rate each section strong, adequate or weak. For Problem, restate the problem in one sentence, assess whether the buyer's state is vivid or generic, and whether at least one quotation is meaningful, then add one to three specific observations. For Agitation, distinguish real, mixed and performative consequences and identify any supporting numbers, timeframes or opportunity costs. Do not manufacture emotional pressure or unsupported losses.

For Solution-and-Mechanism, explain the mechanism in your own words and check whether its four referenced pillars are visible; missing pillar definitions remain a separate dependency. For Proof, distinguish specific, mixed and generic cases and check whether limited evidence is honestly acknowledged. For Offer, inspect the name, visibility of price and concrete delivery experience—what happens, when and with whom.

For Anti-Promise-and-Guarantee, rate the two parts separately. Count three or more genuine exclusions, two, or one or fewer. Identify disguised flattery such as “not for unmotivated people.” Compare one primary guarantee plus an optional complementary element with borderline or three-plus-component stacking. Consider whether stated claim conditions appear understandable and realistically usable, without treating component count as a conclusive legal or ethical judgment. For CTA, check a specific action, outcome and actual timeline. The source's February 12 enrollment and twenty-four-hour welcome-kit example is fictional illustration, not a current date or promise.

Across the whole page, sample three quotations against provenance and classify them as exact, slightly paraphrased or significantly paraphrased. Record overall strong, mixed or weak provenance, but recognize that a three-quote sample cannot verify every quotation. Assess buyer versus operator voice, then count all fifteen required entries. Give three actionable revisions—for example, shortening a particular four-sentence opening to two—rather than an abstract request to improve copy. Close with ready, moderate revision or substantial revision, a hypothetical yes/maybe/no buying reaction with reasons, and a signature. A peer's hypothetical buying reaction is not an actual purchase or validation result.

Follow the SOP's sequence, roles and timing

The SOP requires the page draft, provenance log, completed preparation checklist and a forty-eight-hour cooling period. Its seven roles are the submitting student, two peer reviewers, mentor, cross-stage reviewer, paid reviewer and proposed Build 6 coordinator. The source assigns automated notifications, matching, tracking and gates to Build 6; those operations have not been verified or deployed here.

Step one is a twenty-minute self-audit of checklist groups A–H, quotations and unchanged terms. Missing provenance, fewer than fifteen entries or softened exclusions cause rework; the source's twenty-four-to-forty-eight-hour delay estimate is illustrative. Step two is a fifteen-minute request using the structured script, both document links, suspected weaknesses, the review target and reciprocal availability. Vague requests and missing attachments should be fixed before relying on a review.

Step three allows twenty-four to forty-eight hours for pickup and requires two commitments with delivery dates. The SOP activates alternatives when fewer than two commit within forty-eight hours, whereas the separate alternate document uses seventy-two hours without response. Keep that conflict visible. Reviewers should communicate a threatened deadline instead of missing it silently.

Step five allocates thirty minutes to reading both completed reviews together before acting. Capture common themes and disagreements, then allow the SOP's suggested twelve-hour gap before revision. Two reviewers agreeing is a reason to investigate, not proof that their judgment is correct. Step six allocates sixty to ninety minutes to decisions in the Revision Log and the revised page. Record every recommendation and its disposition; do not accept all feedback mechanically or omit disagreement silently.

Step seven budgets ninety to 120 minutes for two reciprocal reviews, forty-five to sixty each, using the template and delivery script. Discuss actual capacity instead of treating an access need as bad faith. Step eight budgets five minutes to submit and five for the proposed AI run. It requires page, provenance and revision logs, a score of at least seven out of ten and no integrity flags. Its activities say review count at least two, while its quality gate says exactly two. An implementation must reconcile that difference and distinguish review credits from actual people; it must not fabricate a second reviewer when one mentor review counts as two credits.

Apply alternate routes with explicit review credit

Use alternatives when fewer than four people are active at compatible pacing, no response arrives within the stated window, or the student is ahead or behind the cohort. The alternate document proposes escalation within seventy-two hours of draft completion if no route is viable, which can conflict with longer windows below. Define the applicable clock before promising completion.

Protocol A proposes a forty-five-minute mentor call, with the draft and provenance log submitted at least twenty-four hours beforehand. A completed written template counts as both required review credits. The alternate document gives seventy-two hours typically and ninety-six worst case, at no charge; the SOP separately describes twenty-four hours from activation and delivery within seventy-two. These are conflicting source service assumptions, not verified current support. A mentor backlog of two or more weeks is the stated reason to try B.

Protocol B requests one or two volunteer Stage 2-or-higher reviewers, naming archetype, territory, offer, a ninety-six-hour target and both document links. It mentions Stage 2, 3, 4 and 5+ volunteers, no charge and reciprocal ecosystem credits. One cross-stage review may count as two credits or be paired with another review under the source policy; record the chosen interpretation. The SOP limits one description to Stages 2–5. If no one picks up within forty-eight hours, the source points to C. Experience may be useful, but it does not guarantee a superior review.

Protocol C is a direct paid engagement when A and B are unavailable in the planned week. The Academy is not described as handling payment. A paid review counts as only one credit and needs a peer, mentor or cross-stage counterpart. The source's typical price is $150–$400 and turnaround forty-eight to seventy-two hours by contract; the roster's A1 range reaches $450. Preserve that discrepancy. It also proposes that waiting three to five extra days for an unpaid route may be preferable. No paid service is recommended as currently available or purchased here.

The scholarship provision names the unverified legacy address [[email protected]](mailto:[email protected]), a specific scholarship-request subject, page link, pacing dates and attempted routes. It proposes a forty-eight-hour reply and one review covered up to $200 if approved. This is not a current verified service, funding commitment or permission to send a message. The protocol log records route, actual reviewer names, dates and one or two rationale sentences. Its shorthand for C omits a peer as the counterpart despite the prose allowing one; preserve and resolve that inconsistency.

Evaluate the paid-review reference without inventing a roster

The five proposed selection criteria are at least twenty relevant prior page reviews, familiarity with mechanism-based offers, respect for truthful exclusions, a signed methodology agreement and useful ratings from at least five reviewees. The document contains placeholder slots, not current names or contact details, so it does not establish that any provider is actually vetted or available.

Tier A describes ten-plus years of experience: A1 at $350–$450 with seventy-two hours for coaching, consulting and Teacher/Service work; A2 at $300–$400 with forty-eight to seventy-two hours for productized services and Builder work. Tier B describes five to ten years: B1 at $200–$275 with forty-eight to seventy-two hours for Creative work; B2 at $175–$250 with seventy-two hours for B2B, platforms and Systems work. Tier C describes five rotating Stage 2+ alumni slots at $150–$200 with forty-eight to seventy-two hours and archetype matching. All numbers and availability claims are historical template data, not current quotations.

Its five engagement steps are to find the actual current roster, match relevant expertise, provide the draft and provenance log with the required template, explain the methodology baseline, and log the engagement. The baseline preserves mechanism, exclusions and guarantee honesty while requesting critique within that approach. A reviewer should still flag unsupported or unsuitable commitments; methodology must not become a reason to ignore valid criticism.

The source excludes unlisted general review services, disparages low-cost marketplace reviews, rejects AI-only tools as a substitute for required human review, and disallows unlisted paid reviewers for credit. Preserve these as program-policy proposals. Blanket claims about a marketplace's quality are unsupported; assess the actual reviewer. The four methodology conflicts are removing exclusions, adding guarantee stacks, replacing exact quotations, and drifting from the Primary mechanism. Consult the designated reviewer or mentor rather than automatically adopting or rejecting advice solely because it is paid.

The four proposed removal triggers are three or more materially disruptive reports, missing at least twenty percent of quarterly deadlines, an agreement violation such as using review time to upsell, or leaving the field/not renewing the agreement. The document proposes quarterly updates, thirty days' notice and possible later re-entry. These are not actions taken against any person.

Review the process itself

After a cohort, examine the proportion using each route, median request-to-delivery time, the proportion meeting deadlines without escalation, and the proportion of paid feedback conflicting with the stated methodology. The SOP proposes revisiting capacity above thirty-percent mentor substitutions, agreements or roster choices above twenty-percent paid conflicts, and cohort discussion below a 0.85 given/received ratio. These are proposed thresholds, not validated universal benchmarks.

Its additional escalation triggers are three or more failed submissions by one student, fabrication or conflicting reviewer feedback requiring agreement review, an individual reciprocity ratio below 0.5 across two cohorts, and more than three consecutive weeks of thin participation prompting a recruitment review. Define denominators and review evidence before acting. The source's promise that a validator will not penalize alternate routes needs actual implementation verification.

The practical output is a stable reviewed draft, genuine feedback, a decision log, correctly recorded review credits and explicit unresolved issues. Connect Brunson/ClickFunnels message continuity with the Hormozi/Acquisition.com value lens: review whether the promise, evidence, exclusions and delivery agree. Do not mistake template completion, agreement between two reviewers or a numerical score for proof of buyer demand.

Clickable linked resources

- Preparation checklist - Six outreach and response templates - Peer-review coordination SOP - Complete review template - Alternate protocols - Paid-review reference with placeholder roster

Preserve all six complete originals in the applicable lesson appendices. Their dates, templates and embedded operational instructions remain source material, not current service promises or actions executed by this task.

Supporting schema: complete reviewed teaching

Trace the offer curriculum through its database schema

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source boundary

Explain how each proposed C4 artifact is stored, what its checks actually enforce and where review or application controls are still needed. This is the complete version 2.0 schema dated April 24, 2026, written for the operator or developer deploying or auditing Build 1. It depends on the C1, C2 and C3 schemas and their referenced tables. This lesson reviews its SQL as source material; it does not execute migrations or claim a deployed database.

The schema separately supplies the `c4_value_equations` table named in D0404. That resolves the earlier lack of an accompanying table definition in the worksheet's own file. The separately assigned D0413 supplies its reviewer rubric. Both are now accessible references; actual submission storage, grading and unlocking remain unverified.

Understand the shared record structure

There are eight artifact tables and one review-log table. Each receives a UUID primary key with a generated default and a required user_id referencing public.users; deleting that user cascades to these rows. Artifact rows have a filed_at timestamp defaulting to now, while the log has ran_at. A default is not the same as a required value: the source does not mark every timestamp NOT NULL.

The distinction table is unique by user and memo file, allowing multiple distinct memo files per user. The other seven artifact tables are unique by user alone, so they represent one row per user unless another history mechanism exists. The review log permits multiple events. User indexes support lookup; the log uses a combined user-and-module index. File IDs point to external Drive artifacts; storing an ID does not verify the file's contents, permissions or authenticity.

M4.1: offer distinctions

`c4_offer_distinctions` requires the distinction memo's Drive file ID, component inventory file ID, a zero-to-ten AI rubric score and the Primary mechanism name. An optional foreign key points to the C3 market-fit hypothesis. Its stored generated passed value is true when the score is at least seven. The row records which mechanism and files were assessed; the schema does not itself read those files or prove the score came from an authorized reviewer.

M4.2: the value equation

`c4_value_equations` requires the worksheet file ID, strongest and weakest variable names, citation counts and score. Four optional strength columns accept Strong, Moderate or Weak for dream outcome, likelihood, time and effort. The strongest and weakest fields accept the four full variable names, but no constraint requires them to differ. Trigger-bank citation count must be at least three, interview count at least one and score zero to ten. Passed is generated from score at least seven.

These checks validate declared counts and allowed labels, not the quotations or all per-section evidence required by D0404 and D0413. The four strength fields can be null because an allowed-value CHECK does not make a column mandatory. The worksheet's richer diagnosis and the actual grading rubric remain necessary.

M4.3: decomposition and three variants

`c4_offer_decompositions` stores decomposition and variants file IDs, a total decomposed-deliverables count from six to ten, three variant definitions and a required structural-verification flag. Each A, B and C variant has a required name, engagement model, duration in weeks and deliverable count, plus optional lower and upper price bands. Engagement model is Cohort, 1:1, Self-paced or Hybrid. Each variant's deliverable count may not exceed eight.

Three pairwise checks compare A with B, A with C and B with C. Every pair must differ in engagement model, duration or deliverable count. Changing price or name alone does not satisfy them. These are the actual database tests; deeper assessment of meaningful difference belongs to the named offer-decomposition reviewer. The source's design note says the maximum-eight rule guards against feature stuffing, but a count cannot assess whether the retained deliverables are useful.

The SQL does not require positive duration or a positive minimum variant count, nor does it order or validate positive price-band endpoints. A stored structural_verification_passed flag is supplied, not computed from all qualitative criteria. Keep these limits visible rather than treating acceptance by the table as full validation.

M4.4: pricing decisions

`c4_pricing_decisions` requires a pricing-decision file, observed floor, median and ceiling, a positive anchor price, a pricing strategy and a pay-in-full price. Strategies are Median, Above Market, Below Market (Volume) or Other. Optional fields store installment and deposit descriptions, hours per buyer, effective hourly rate and rationale for deviation from the observed band. Score is zero to ten; at least seven generates passed.

The table can preserve the comparison and unit-economics assumptions, but it does not enforce floor ≤ median ≤ ceiling, positive pay-in-full price or coherent hours and effective rate. Nor does it independently validate the competitor observations. Explain the rationale and evidence in the linked artifact before treating the price as justified.

M4.5: anti-promises and integrity

`c4_anti_promises` requires anti-promise and integrity-statement file IDs, three to six audience exclusions, at least two outcome non-claims and at least two scope boundaries. The required signature Boolean defaults to false. A zero-to-ten score of at least seven and a true signature flag jointly generate passed. This records the boundary and signature assertion; a Boolean by itself is not a verified signature or an enforceable agreement.

M4.6: guarantees

`c4_guarantees` stores the guarantee and honesty-clause file IDs, a required signature flag defaulting false, guarantee type, component count, target weakness, sustainability flag and score. Types are Refund, Outcome, Hybrid, Time-shift and Effort-adjusted. There may be at most two components. The target must be Perceived Likelihood, Time Delay or Effort and Sacrifice. Expected activation percentage is optional. Passed requires score at least seven and a signed-clause flag.

The source records unit_economics_sustainable but does not include it in the generated pass condition. It also does not constrain the percentage to zero through one hundred or require a positive component minimum. Therefore, a row can satisfy the coded pass condition without establishing a sustainable guarantee. The written terms, evidence and authorized review still matter.

M4.7: landing-page copy

`c4_landing_page_copies` requires the page and provenance-log file IDs, permits a revision-log ID, limits total words to 1,000–5,000 and requires at least fifteen claimed Trigger Bank entries. It separately stores the number verified verbatim. Two optional reviewer IDs reference users, each paired with an optional completion timestamp. peer_reviews_complete is generated from the presence of both timestamps.

Passed requires an AI score of at least seven, both review timestamps and at least fifteen verified verbatim entries. The AI score is optional but, when present, constrained to zero through ten. Depending on null inputs, the Boolean expression can produce null rather than false; the completion function counts only passed = TRUE.

No shown constraint requires different reviewers, prevents self-review, ensures reviewer IDs accompany timestamps or ensures verified counts do not exceed claimed counts. The application and reviewer process must establish that the review and evidence are real. A generated Boolean protects its expression from direct assignment; it does not make owner-supplied inputs trustworthy.

M4.8: offer readiness

`c4_offer_readiness_docs` requires readiness and first-sale-checklist file IDs, selected variant A/B/C, final offer name and final anchor price. Signature defaults to false. The optional Opus validator verdict is PASS, NEEDS_REVISION or FAIL, with an optional run timestamp. At least three kill criteria must be declared. Passed requires a PASS verdict and a true signature flag.

This captures the intended final review gate. A Sonnet result elsewhere does not satisfy this explicit Opus-verdict field. However, the field does not authenticate which model or person produced its value, the anchor price is not constrained positive here, and the table stores a kill-criteria count rather than the criteria themselves. The linked artifact and trusted review process remain essential.

Review history and user summary

`c4_review_log` stores user, module M4.1 through M4.8, prompt name, version, required submission count defaulting to one, verdict PASS/FAIL/NEEDS_REVISION, optional integer score, feedback JSON, flags JSON and run time. Its score has no zero-to-ten constraint and submission count has no positive check. Preserve these differences rather than assuming the log has the same validation as every artifact.

The user table gains five columns: completion Boolean defaulting false, completion timestamp, lead variant, final offer name and final anchor price. These are summary fields populated by the shown trigger; their existence alone does not prove current eligibility or completion.

Enrollment eligibility: what is actually checked?

`check_c4_enrollment_eligible` accepts a user ID and returns JSON containing eligible and a missing-items list. It requires C3 complete, a market-fit hypothesis filed within the previous three months, a Trigger Bank with at least 200 entries, a Pricing Signals row and an oath signed within the previous twelve months. The hypothesis uses a strict newer-than boundary; the oath is rejected when missing or older than its boundary.

The function selects C1 completion, C2 completion and operator-identity filing but does not test them. It checks that Pricing Signals exists, not its quality or recency, and it does not validate every dependency named in the worksheet. These are differences between data read, conditions enforced and the broader educational prerequisites.

Completion checks and trigger behavior

`check_c4_completion` returns complete plus missing items after checking all eight artifact stages: distinction passed; equation passed; decomposition structural verification true; pricing passed; anti-promise passed; guarantee passed; landing page passed; and readiness passed. The named missing items retain the expected signature, peer-review and Opus context because those are part of the relevant table expressions.

`update_c4_complete_flag` calls that check for NEW.user_id. When complete, it reads the passing readiness row and sets the user completion flag true, stamps the current time and copies the selected variant, offer name and anchor price. Its trigger runs only after an insert or update to the readiness table when NEW.passed is true.

That means completing another artifact after readiness already passed does not automatically invoke this trigger. Neither deleting supporting evidence nor changing a prior result to failure resets completion through this code. The function only sets true and has no false branch. Repeated qualifying readiness updates can also restamp completion time. These are observations from the supplied SQL, not evidence that a live system currently behaves this way. A production design must decide how to re-evaluate changes and revocations.

Access controls and implementation limits

All nine tables enable row-level security. The eight artifact tables allow selecting, inserting and updating rows belonging to auth.uid(); no DELETE policy is shown. The review log permits owners to select their history, but its insert policy uses WITH CHECK (TRUE) without a TO role restriction. The adjacent service-only comment is not an access restriction. Actual access also depends on grants and runtime roles, which this file does not show.

Likewise, owner-based row access is not field-level grading authority. If ordinary users have the corresponding write grants, these policies do not stop them changing their own scores, verification flags or signature assertions. Review provenance and privileged fields need a defined trusted boundary before this can be treated as an authoritative completion system.

The eligibility and completion functions use SECURITY DEFINER and accept arbitrary user IDs. The shown definitions contain neither a caller-to-user authorization check nor an explicit secure search_path. Supabase's documentation explains the need to secure such functions and their execution permissions. Review those controls and actual grants before implementation; do not infer protection from schema-qualified table names alone.

Migration and operating references

The supplied migration sequence runs c1_schema.sql, c2_schema.sql, c3_schema.sql and then c4_schema.sql using psql with host, user and database placeholders. Reading this sequence does not execute it. Tables use IF NOT EXISTS and the five user columns use ADD COLUMN IF NOT EXISTS, but separate index, policy, constraint and trigger creation statements are not all guarded. The complete file therefore is not automatically safe to rerun unchanged.

The source names five related paths or integrations: RISER-Build-References-for-C4.md, C4-Review-Chain.md, C4-Prerequisites-Checklist.md, Build 6 src/c4_checkpoint_handler.ts and RISER-C4-Weekly-Rhythm-Setup-SOP.md. Their implementation and deployment are not supplied by this schema. Preserve the full SQL, comments, design notes and migration references in the appendix.

Apply the educational connection

This design attempts to turn Hormozi-style offer analysis into traceable artifacts before a Brunson-style offer presentation is finalized. The value of the database is provenance and accountable review, not merely a green completion flag. As authored practice, trace one worksheet from its file ID through cited evidence, rubric score, authorized review and downstream completion. Mark every unverified dependency and every condition the code does not enforce. Deliver a schema-to-artifact map and a review of those gaps; no database deployment is part of this lesson's completion.

Sources and resources

- Complete assigned C4 schema. - D0404: Value Equation Worksheet and D0413: actual reviewer YAML. - PostgreSQL constraints and CREATE POLICY: primary constraint and policy semantics. - Supabase row-level security and database functions: primary access-control references. - Acquisition.com value-equation checklist, ClickFunnels value ladder and RISER NATION CORP.

Assigned source links

D0438 original source 1

Complete native original body, including retained document-part text

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*
Complete linked peer-review resource: D1458

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*
Complete linked peer-review resource: D1594

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*
Complete linked peer-review resource: D3189

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
Complete linked peer-review resource: template

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*
Complete linked peer-review resource: alternate

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*
Complete linked peer-review resource: paid

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*
Complete linked C4 schema; missing implementations distinguished in teaching

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*
Complete local source copy including original filing metadata and formatting

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*

Budget active work, revision time and review delays separately

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and outline

Build a realistic calendar for the source's offer-construction work. Separate module activity, implementation, elapsed cooling periods and peer-review latency. Compare four- and five-week schedules, recognize escalation signals, and adapt the plan to actual capacity and accessibility needs. The source uses legacy C4 and C1–C3 labels; the current spreadsheet still controls course assignments.

Start with the top-line estimates and check their arithmetic

The source targets forty active hours over four to five weeks, averaging eight to ten hours per week. Its longest module is the landing-page copy activity at four hours, plus a peer-review cycle. It calls offer architecture the shortest module at seventy-five minutes, although the anti-promise module also has seventy-five minutes. Keep that tie visible.

Legacy moduleActivityMinutesCumulative time
M4.1Offer architecture foundations751:15
M4.2Grand Slam Offer framework902:45
M4.3Deconstruction and reassembly1805:45
M4.4Pricing and anchoring907:15
M4.5Anti-promise758:30
M4.6Guarantee architecture9010:00
M4.7Landing-page copy24014:00
M4.8Offer readiness document9015:30

The module total is 930 minutes, or fifteen and a half hours. These are proposed learning estimates, not measured time already spent on this project and not a guarantee of how quickly a learner will finish.

Add all nine implementation activities

The source budgets one to two hours to reread the Market Fit Hypothesis and Trigger Bank; two to three hours to revise the three offer variants after cooling; three to five hours for landing-page revision; two to three hours to review two peers' pages; and one to three hours to incorporate two reviews of the learner's own page.

It then adds one hour to revise the anti-promise after the guarantee decision; one to two hours for pricing and unit-economics checks; two to three hours for the readiness document's draft and revision; and one to two hours for community discussion and reflection.

The source summarizes these as fifteen to twenty-four hours. Adding the individual minima gives fourteen, while the maxima give twenty-four. Combined with the module time, the arithmetic is twenty-nine and a half to thirty-nine and a half hours, approximately the source's thirty-to-forty-hour range and forty-hour target. Check that readiness drafting and other activities are not counted twice in your own calendar; the document distinguishes implementation outside the module sessions, but actual work logs must establish that boundary.

The source compares this with forty-five hours for its prior C3 course and says internal writing avoids external scheduling. Treat that as its planning context, not a universal rule: peer review is still an external dependency. A learner taking longer may need a clearer task, support or accommodation; time alone does not establish unwillingness to revise.

Compare the four-week and five-week plans

In the aggressive four-week plan, week one completes the distinction memo and Value Equation worksheet. Week two completes three variants and pricing. Week three completes the anti-promise and guarantee, including the Honesty Clause. Week four combines the landing-page draft, peer reviews and revision with the readiness document. This compressed plan depends on reviewers responding in time and enough working hours being available.

In the default five-week plan, week one again covers the first two artifacts. Week two drafts and revises three variants with cooling time. Week three handles pricing and the anti-promise. Week four completes the guarantee and sends the initial landing-page draft to peers. Week five incorporates feedback and completes the readiness document. The additional week provides room for revision and review latency, not an assurance that every dependency will resolve.

Record each major deliverable and its review dependency. An authored scheduling practice is to reserve the actual reviewer availability before promising a final date, then update the plan when evidence changes rather than hiding a delay.

Treat the 85-minute rhythm as part of the work plan

The source's Monday block is ten minutes: open the folder, review what is due, reread a prior draft and note one or two revisions. Tuesday has fifteen minutes for a new section, revision or assigned peer feedback. Wednesday provides a thirty-minute drafting block for variants, copy or readiness. Thursday has twenty minutes to revise, cut weak sentences and check buyer-language quotations. Friday has ten minutes for a reflection about difficulty and surprises.

These blocks total eighty-five minutes per week. The source explicitly says longer writing and peer-review sessions are additional. Over five weeks, the rhythm supplies 425 minutes—seven hours and five minutes—not the whole forty-hour course. That clarification resolves the misleading impression in some linked legacy maps that the rhythm alone could complete all scheduled work. Determine whether each block belongs inside your forty-hour budget before adding it again.

The source asks for verbatim Trigger Bank entries rather than paraphrases. Preserve exact quotations in an appropriately restricted evidence bank, with attribution and permissions as needed. Do not invent buyer quotations or disclose private research to meet a writing checklist.

Separate cooling time from active time

The source proposes a forty-eight-hour gap between first and second drafts of M4.3, M4.5, M4.7 and M4.8. Waiting does not itself consume working hours, but it does affect the earliest possible completion date. Other compatible tasks can occur during a cooling period if the dependencies allow them.

The source claims same-day revision could reduce elapsed time to three weeks but produce weaker work visible at the later readiness test. It supplies no comparison data establishing that outcome for every learner. Teach the cooling period as a proposed revision practice: return with fresh attention, look for unsupported claims and weak wording, and record whether the second pass improves the artifact. Retain its four-to-five-week planning recommendation without presenting it as a scientifically fixed duration.

Respond to all four six-week warning scenarios

First, rewriting the mechanism while assembling variants may signal an unresolved earlier choice. The source proposes pausing offer work and returning to C3 M3.5–M3.7 with a mentor. Check the actual cause instead of assuming the earlier decision was careless.

Second, six or more landing-page drafts may suggest perfectionism or feature stuffing. Review the specific offer weakness and the referenced failure case rather than continuing cosmetic revisions. Third, missing peer reviews may indicate a thin cohort or stalled reviewers; the source proposes Protocol A mentor substitution. That protocol and actual mentor availability must be established separately.

Fourth, difficulty writing the anti-promise may justify a thirty-minute conversation about truthful fit and scope boundaries. The source attributes conversion benefits to Hopkins and Hormozi, but this document supplies no supporting passages or results. Do not promise that exclusions always increase conversion. The source also proposes automatic mentor escalation after seven weeks without completion; that is a design rule, not a verified live automation.

Adjust attention to the operator's actual needs

The source suggests a Teacher-Operator add one hour to pricing, comparing relevant cohort and service alternatives with actual pricing signals instead of assuming self-paced course benchmarks of $197–$497 apply to cohort examples of $1,500–$10,000. Those numbers remain illustrative source comparisons, not current market prices.

It suggests a Builder-Operator add two hours to landing-page copy, converting feature descriptions into evidenced buyer outcomes. It suggests a Service-Operator add one hour to the anti-promise, discussing three categories of poor fit with a peer. The Product, Creative and Systems estimates are unchanged in this time-estimate document, while it points to a separate archetype chart for further adjustments. That chart includes additional advice, so preserve the difference between this summary and the fuller reference rather than silently erasing either.

The category descriptions are tendencies to inspect, not diagnoses. An authored Brunson/ClickFunnels application is to reserve time for a clear hook, truthful story and coherent offer. An authored Hormozi/Acquisition.com application is to reserve time to test the outcome, evidence, delay, effort and delivery economics. Neither educational theme requires a learner to fit a fixed personality category.

Preserve accommodation requests without inventing a service promise

The source lists [email protected] as a pre-enrollment contact with a forty-eight-hour response target. This is a legacy address on a different domain from the requested www.risernationcorp.com; its operation and current service commitment have not been verified. Preserve the [legacy accommodation contact](mailto:[email protected]) as a source reference awaiting confirmation, not as a promise that RISER currently monitors it.

The described options are an extended timeline up to ten weeks, asynchronous voice or written peer review in place of synchronous review, dyslexia-friendly copy review by a mentor, and a scholarship for paid review under Protocol C when needed because the cohort is thin. These are proposed source provisions. Confirm available support and eligibility before offering them to a learner; no email, scholarship or paid review is activated by this lesson.

Produce the calendar and review it

For practice, choose the four- or five-week plan and enter module work, implementation, cooling and review dates separately. Add time only where the actual task requires it, identify who owns each dependency, and show the response when a review arrives late. Keep the original time tables and every applicable source link with the lesson. A usable schedule explains its assumptions and changes when they fail; it does not turn a source estimate into a deadline guarantee.

Clickable assigned source

- C4 Offer Ignition — Time Estimate

The complete source text and its original module, implementation and weekly tables remain in the lesson appendix, including the arithmetic discrepancies and legacy support details.

Linked resource workshop: prepare, request, deliver and reconcile a peer review

The six linked documents supply the practical peer-review material referenced by the offer-course plans. They are legacy templates and operating proposals, not evidence of a currently staffed RISER service. Read them together: the preparation checklist establishes inputs, outreach scripts coordinate people, the review template structures feedback, the SOP sequences work, alternate protocols address missing capacity, and the paid-review reference describes proposed selection rules. No message, booking, payment or scholarship request is sent by this workshop.

Prepare all eight checklist groups

Group A requires the named landing-page file and seven sections in order: Problem, 200–400 words; Agitation, 150–300; Solution-and-Mechanism, 300–500; Proof, 200–400; Offer, 300–500; Anti-Promise-and-Guarantee, 250–400; and CTA, 50–150. The individual ranges sum to 1,450–2,650, while the required total is 1,800–2,500. Both conditions can be satisfied, but one does not automatically imply the other. These are template targets, not proof that a page of that length will convert. Compared with the handoff's ten-element list, two pairs are grouped and urgency has no separate heading; explain relevant truthful timing without inventing scarcity.

Group B requires a named Trigger Bank Provenance Log, at least fifteen entries, exact source wording, a TB identifier or interview reference, and distribution across at least four page sections. Matching fifteen quotations is not a substitute for the full bank's evidence quality. Keep permissions, confidentiality and attribution appropriate to the destination.

Group C compares the page's exclusions with M4.5 and its guarantee with M4.6. Softening must be reverted or justified in the record; added guarantee stacking should be removed under this template's policy. Both integrity signatures are required. Group D checks the tested offer name, one visible price rather than a hidden range, payment options, engagement model, duration, cadence and no more than eight deliverables. A signature and a count are structural checks, not proof of truthfulness or viability.

Group E asks for specific named or appropriately anonymized evidence, an explicit known-weakness acknowledgment when there are fewer than four named cases, and attributed, exact testimonials. Do not invent a fourth case or disclose an identity to meet a template. Group F requires a specific action, actual enrollment or cohort timing, a qualification process if applicable, and a real pre-purchase contact. Group G requires reading the page aloud, removing phrases the operator would not say, checking unsupported hyperbole, and avoiding the source's four low-substance phrases: “game-changer,” “revolutionary,” “transform your life,” and “all you need to do is.” These are editorial preferences, not a comprehensive truthfulness test.

Group H prepares links to the page and provenance log, two or three positioning sentences, a request for two template-based reviews within seventy-two hours, and specific availability to reciprocate. The checklist's fifteen-to-twenty-minute estimate and claimed thirty-to-sixty-minute reviewer saving are unverified assumptions.

Its five common fixes are to restore softened terms; add three to six genuine missing quotations, often in problem and agitation; examine excess deliverables for unnecessary padding; show the actual price in the offer section; and use a forty-eight-hour reread to repair unnatural voice. Add only what is genuinely missing rather than assuming three extra quotes always reaches fifteen. After submission, check reviewer pickup daily, answer questions, keep the reviewed version stable and begin reciprocating. The stable-version rule prevents two reviewers evaluating different drafts.

Use the six coordination scripts as templates, not automatic messages

The request script identifies the operator, tested offer name, buyer, price and one or two suspected weaknesses. It links the page, provenance log and any existing Revision Log, proposes seventy-two hours, and states specific days for reviewing the first two reciprocal requests. Naming a focus may help, but the claim that it reliably improves feedback is not established by data here.

The acceptance script names the requester, confirms the chosen focus or full-template review, and gives a specific delivery date and time, aiming for forty-eight hours. That is shorter than the general seventy-two-hour target; state which commitment was actually made. The decline script explains capacity if useful, refers to a genuinely available person, and points to alternate review options. Do not tag someone or promise mentor capacity without knowing it exists.

The delivery script links the completed template, gives one overall observation and three recommended revisions, and offers optional asynchronous discussion. The response script addresses every recommendation as incorporated, incorporated with modification, or not incorporated with a reason, then links the Revision Log. The escalation script identifies the pacing window, requests and responses, attempted alternate routes, specific help needed, page link and revised timeline. The source routes it to a mentor channel or a welcome-email Calendly link, neither of which is supplied as a verified current contact.

The etiquette section favors reciprocity, precise observations, honest criticism and timely responses. Its example contrasts generic praise with identifying performative “wasted years” wording in a particular paragraph. Be candid and respectful; honesty does not require harshness. The source calls reciprocity a culture norm rather than enforced policy. It encourages personal voice especially in request and delivery scripts, with logistics scripts closer to their templates. Claims that personal voice correlates with better responses or missed SLAs are the largest disruption cause are source assertions, not measured findings here.

Complete the entire review template

Read the page and provenance log together, looking for buyer-language fit, quotations that support specific claims, and exclusions or guarantees weakened during copywriting. The source estimates forty-five to sixty minutes and a seventy-two-hour request-to-delivery target. Record reviewer name, reviewer archetype, date, submitting operator and offer name. The task is structural feedback, not rewriting every line.

Rate each section strong, adequate or weak. For Problem, restate the problem in one sentence, assess whether the buyer's state is vivid or generic, and whether at least one quotation is meaningful, then add one to three specific observations. For Agitation, distinguish real, mixed and performative consequences and identify any supporting numbers, timeframes or opportunity costs. Do not manufacture emotional pressure or unsupported losses.

For Solution-and-Mechanism, explain the mechanism in your own words and check whether its four referenced pillars are visible; missing pillar definitions remain a separate dependency. For Proof, distinguish specific, mixed and generic cases and check whether limited evidence is honestly acknowledged. For Offer, inspect the name, visibility of price and concrete delivery experience—what happens, when and with whom.

For Anti-Promise-and-Guarantee, rate the two parts separately. Count three or more genuine exclusions, two, or one or fewer. Identify disguised flattery such as “not for unmotivated people.” Compare one primary guarantee plus an optional complementary element with borderline or three-plus-component stacking. Consider whether stated claim conditions appear understandable and realistically usable, without treating component count as a conclusive legal or ethical judgment. For CTA, check a specific action, outcome and actual timeline. The source's February 12 enrollment and twenty-four-hour welcome-kit example is fictional illustration, not a current date or promise.

Across the whole page, sample three quotations against provenance and classify them as exact, slightly paraphrased or significantly paraphrased. Record overall strong, mixed or weak provenance, but recognize that a three-quote sample cannot verify every quotation. Assess buyer versus operator voice, then count all fifteen required entries. Give three actionable revisions—for example, shortening a particular four-sentence opening to two—rather than an abstract request to improve copy. Close with ready, moderate revision or substantial revision, a hypothetical yes/maybe/no buying reaction with reasons, and a signature. A peer's hypothetical buying reaction is not an actual purchase or validation result.

Follow the SOP's sequence, roles and timing

The SOP requires the page draft, provenance log, completed preparation checklist and a forty-eight-hour cooling period. Its seven roles are the submitting student, two peer reviewers, mentor, cross-stage reviewer, paid reviewer and proposed Build 6 coordinator. The source assigns automated notifications, matching, tracking and gates to Build 6; those operations have not been verified or deployed here.

Step one is a twenty-minute self-audit of checklist groups A–H, quotations and unchanged terms. Missing provenance, fewer than fifteen entries or softened exclusions cause rework; the source's twenty-four-to-forty-eight-hour delay estimate is illustrative. Step two is a fifteen-minute request using the structured script, both document links, suspected weaknesses, the review target and reciprocal availability. Vague requests and missing attachments should be fixed before relying on a review.

Step three allows twenty-four to forty-eight hours for pickup and requires two commitments with delivery dates. The SOP activates alternatives when fewer than two commit within forty-eight hours, whereas the separate alternate document uses seventy-two hours without response. Keep that conflict visible. Reviewers should communicate a threatened deadline instead of missing it silently.

Step five allocates thirty minutes to reading both completed reviews together before acting. Capture common themes and disagreements, then allow the SOP's suggested twelve-hour gap before revision. Two reviewers agreeing is a reason to investigate, not proof that their judgment is correct. Step six allocates sixty to ninety minutes to decisions in the Revision Log and the revised page. Record every recommendation and its disposition; do not accept all feedback mechanically or omit disagreement silently.

Step seven budgets ninety to 120 minutes for two reciprocal reviews, forty-five to sixty each, using the template and delivery script. Discuss actual capacity instead of treating an access need as bad faith. Step eight budgets five minutes to submit and five for the proposed AI run. It requires page, provenance and revision logs, a score of at least seven out of ten and no integrity flags. Its activities say review count at least two, while its quality gate says exactly two. An implementation must reconcile that difference and distinguish review credits from actual people; it must not fabricate a second reviewer when one mentor review counts as two credits.

Apply alternate routes with explicit review credit

Use alternatives when fewer than four people are active at compatible pacing, no response arrives within the stated window, or the student is ahead or behind the cohort. The alternate document proposes escalation within seventy-two hours of draft completion if no route is viable, which can conflict with longer windows below. Define the applicable clock before promising completion.

Protocol A proposes a forty-five-minute mentor call, with the draft and provenance log submitted at least twenty-four hours beforehand. A completed written template counts as both required review credits. The alternate document gives seventy-two hours typically and ninety-six worst case, at no charge; the SOP separately describes twenty-four hours from activation and delivery within seventy-two. These are conflicting source service assumptions, not verified current support. A mentor backlog of two or more weeks is the stated reason to try B.

Protocol B requests one or two volunteer Stage 2-or-higher reviewers, naming archetype, territory, offer, a ninety-six-hour target and both document links. It mentions Stage 2, 3, 4 and 5+ volunteers, no charge and reciprocal ecosystem credits. One cross-stage review may count as two credits or be paired with another review under the source policy; record the chosen interpretation. The SOP limits one description to Stages 2–5. If no one picks up within forty-eight hours, the source points to C. Experience may be useful, but it does not guarantee a superior review.

Protocol C is a direct paid engagement when A and B are unavailable in the planned week. The Academy is not described as handling payment. A paid review counts as only one credit and needs a peer, mentor or cross-stage counterpart. The source's typical price is $150–$400 and turnaround forty-eight to seventy-two hours by contract; the roster's A1 range reaches $450. Preserve that discrepancy. It also proposes that waiting three to five extra days for an unpaid route may be preferable. No paid service is recommended as currently available or purchased here.

The scholarship provision names the unverified legacy address [[email protected]](mailto:[email protected]), a specific scholarship-request subject, page link, pacing dates and attempted routes. It proposes a forty-eight-hour reply and one review covered up to $200 if approved. This is not a current verified service, funding commitment or permission to send a message. The protocol log records route, actual reviewer names, dates and one or two rationale sentences. Its shorthand for C omits a peer as the counterpart despite the prose allowing one; preserve and resolve that inconsistency.

Evaluate the paid-review reference without inventing a roster

The five proposed selection criteria are at least twenty relevant prior page reviews, familiarity with mechanism-based offers, respect for truthful exclusions, a signed methodology agreement and useful ratings from at least five reviewees. The document contains placeholder slots, not current names or contact details, so it does not establish that any provider is actually vetted or available.

Tier A describes ten-plus years of experience: A1 at $350–$450 with seventy-two hours for coaching, consulting and Teacher/Service work; A2 at $300–$400 with forty-eight to seventy-two hours for productized services and Builder work. Tier B describes five to ten years: B1 at $200–$275 with forty-eight to seventy-two hours for Creative work; B2 at $175–$250 with seventy-two hours for B2B, platforms and Systems work. Tier C describes five rotating Stage 2+ alumni slots at $150–$200 with forty-eight to seventy-two hours and archetype matching. All numbers and availability claims are historical template data, not current quotations.

Its five engagement steps are to find the actual current roster, match relevant expertise, provide the draft and provenance log with the required template, explain the methodology baseline, and log the engagement. The baseline preserves mechanism, exclusions and guarantee honesty while requesting critique within that approach. A reviewer should still flag unsupported or unsuitable commitments; methodology must not become a reason to ignore valid criticism.

The source excludes unlisted general review services, disparages low-cost marketplace reviews, rejects AI-only tools as a substitute for required human review, and disallows unlisted paid reviewers for credit. Preserve these as program-policy proposals. Blanket claims about a marketplace's quality are unsupported; assess the actual reviewer. The four methodology conflicts are removing exclusions, adding guarantee stacks, replacing exact quotations, and drifting from the Primary mechanism. Consult the designated reviewer or mentor rather than automatically adopting or rejecting advice solely because it is paid.

The four proposed removal triggers are three or more materially disruptive reports, missing at least twenty percent of quarterly deadlines, an agreement violation such as using review time to upsell, or leaving the field/not renewing the agreement. The document proposes quarterly updates, thirty days' notice and possible later re-entry. These are not actions taken against any person.

Review the process itself

After a cohort, examine the proportion using each route, median request-to-delivery time, the proportion meeting deadlines without escalation, and the proportion of paid feedback conflicting with the stated methodology. The SOP proposes revisiting capacity above thirty-percent mentor substitutions, agreements or roster choices above twenty-percent paid conflicts, and cohort discussion below a 0.85 given/received ratio. These are proposed thresholds, not validated universal benchmarks.

Its additional escalation triggers are three or more failed submissions by one student, fabrication or conflicting reviewer feedback requiring agreement review, an individual reciprocity ratio below 0.5 across two cohorts, and more than three consecutive weeks of thin participation prompting a recruitment review. Define denominators and review evidence before acting. The source's promise that a validator will not penalize alternate routes needs actual implementation verification.

The practical output is a stable reviewed draft, genuine feedback, a decision log, correctly recorded review credits and explicit unresolved issues. Connect Brunson/ClickFunnels message continuity with the Hormozi/Acquisition.com value lens: review whether the promise, evidence, exclusions and delivery agree. Do not mistake template completion, agreement between two reviewers or a numerical score for proof of buyer demand.

Clickable linked resources

- Preparation checklist - Six outreach and response templates - Peer-review coordination SOP - Complete review template - Alternate protocols - Paid-review reference with placeholder roster

Preserve all six complete originals in the applicable lesson appendices. Their dates, templates and embedded operational instructions remain source material, not current service promises or actions executed by this task.

Assigned source links

D0439 original source 1

Complete native original body, including retained document-part text

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*
Complete linked peer-review resource: D1458

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*
Complete linked peer-review resource: D1594

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*
Complete linked peer-review resource: D3189

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
Complete linked peer-review resource: template

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*
Complete linked peer-review resource: alternate

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*
Complete linked peer-review resource: paid

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*
Complete local source copy including original filing metadata and formatting

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*

Turn a ready offer into a plan for public availability

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source boundary

By the end of this lesson, you can write a memo that distinguishes a complete internal offer from an offer that an appropriate buyer can discover and respond to. The source is the C5 Offer-to-Public-Existence Memo Template, version 2.0, dated April 24, 2026. Its C4, C5 and M5.1 labels describe the legacy syllabus; follow this lesson's actual spreadsheet assignment rather than renumbering the current courses.

An offer document can be complete, signed and filed without a buyer having seen it. A public page can exist without attracting a suitable buyer. A response can occur without a sale. Keep these states separate so your next action addresses the actual gap. This is an authored explanation of the template's distinction, not evidence that your page is published or that anyone has been contacted.

Outline and preparation

The source allocates 60–90 minutes to six sections, using the filename `Offer-to-Public-Existence-[YourName]-[Date].md`. Gather your M4.8 Offer Readiness executive summary and the separately filed Go-Live Readiness Inventory. Those completed artifacts are not supplied by this blank template; mark them missing if you do not yet have them.

The overall target is 500–800 words. Its section ranges add up to 510–810 words, so the upper limits cannot all be used while meeting the overall maximum. An authored allocation of 100, 50, 50, 200, 125 and 125 words totals 650 and fits every section range. Use that as a planning aid, not a replacement rule. The two sections requesting one sentence each also specify 40–70 words; avoid an unreadable sentence merely to hit the length, and flag any departure from the source format for your reviewer.

Section 1: preserve your actual starting state

The first section calls for 80–120 words pasted from the Executive Summary of the M4.8 Offer Readiness Document. It explicitly asks for a paste rather than a rewrite. Preserve what was actually approved, including material limitations. Do not quietly revise an earlier promise to make today's plan look more complete.

If the original summary exceeds the requested range, identify the conflict and retain the complete source summary in the supporting material. Do not claim a shortened or newly written summary is an unchanged paste. The point is a traceable starting state against which later changes can be assessed.

Section 2: describe internal readiness

In the second section, state what you have at the end of the source's C4 stage. The source suggests the words complete, documented, signed, filed and drafted. They describe internal production and review.

For an authored example: “I have a documented offer with a defined buyer, delivery scope, price, limitations and review record, and I have filed its supporting materials so the proposed engagement can be checked for consistency before any public availability or buyer response is claimed.” Do not use “signed” unless the required person actually signed the relevant version.

Section 3: describe external availability

The third section asks what will exist at the end of the source's C5 stage. Its vocabulary includes live, published, sent, responded and visible. These words refer to different observable events; do not use them interchangeably.

An authored example is: “The intended buyer will be able to reach a live offer page and understand its scope, price and next step, while my records will separately show which approved communications were sent and which actual responses were received, without counting publication alone as demand or a sale.”

Compare the vocabulary in Sections 2 and 3. If both describe drafting and filing, the external change is still missing. The source says many learners rewrite the distinction two or three times; treat that as its instructional observation, not a required number of revisions or a verified cohort statistic.

Section 4: explain the specific changes

Use 150–250 words to describe concrete artifact transitions. The template requires three examples and one or two additions relevant to the operator:

- A landing page moves from a Markdown document in Drive to a live URL. Record the intended URL and verify its actual state; a preview link is not automatically the public destination. - Mechanism proof moves from internal notes to a published supporting artifact. Explain what the evidence supports and what it does not. Publishing a claim does not validate it. - A buyer pool moves from a warm list in Drive to a record of actual humans contacted and their classified responses. Distinguish the contact count from the response count; do not count simulated personas, planned messages or duplicates as people contacted. - Add one or two transitions specific to your situation. Authored possibilities are a draft qualification form becoming a tested form, or an internal delivery checklist becoming a buyer-accessible preparation guide. These are examples, not additional source-mandated artifacts.

Describe what changes in location, accessibility and evidence. This lesson does not send the communications or publish the artifacts; it teaches how to describe and verify their states.

Section 5: state graduation criteria without inventing a sales requirement

The fifth section uses 100–150 words to describe territory mastery and foundational literacy as you will demonstrate them. It also explicitly acknowledges that the first paid customer is not required for this source's Stage 1 graduation.

The template names these criteria but does not supply their full assessment rubrics. Reference the actual applicable rubric when available; do not invent a new passing standard from the two labels. An authored explanation can identify the evidence you intend to submit while marking the missing rubric as a dependency. Keep “first paid customer not required” distinct from a claim that market response, offer quality or other graduation requirements do not matter.

Section 6: summarize the separate readiness inventory

Use 100–150 words to summarize four categories: what is ready to go live, what must be produced from scratch, what must be tested and what requires calendar time rather than active work. Keep the structured inventory filed separately, as the source requires.

For example, writing a page is active work; waiting for an authorized review is elapsed calendar time. A draft may need testing before it belongs in the ready category. Name the unfinished dependency and its owner instead of hiding it inside a general claim of readiness. The blank template does not provide an inventory to complete on the learner's behalf.

Submission, review and revision

The source instructs the learner to file both the memo and the structured inventory in the C5 Drive folder and submit them to a named Sonnet reviewer, `offer-to-public-existence-reviewer`. It specifies a target of at least 7/10, allows resubmission and says the third attempt triggers mentor assignment.

These are the source's proposed workflow and threshold. They do not establish that the reviewer, folder routing or mentor assignment is configured in this academy. Preserve the submitted version, the returned findings and the actual review record when those services are available. A score cannot substitute for checking whether the six sections describe true, distinct states.

Apply the offer-education themes

The authored Brunson/ClickFunnels connection is continuity between the offer and the buyer's next step: the page and supporting story should communicate the same scoped promise as the internal offer. The authored Hormozi/Acquisition.com connection is evidence for the desired result and delivery terms, with clear effort, timing and limitations. Neither framework turns a drafted offer into market validation merely by naming it well.

As a final exercise, highlight every past-tense claim in your memo and identify its evidence. Then highlight every future-tense statement and identify the work or dependency needed to make it true. This keeps a plan useful without presenting planned outcomes as completed results.

Clickable source and supporting resources

- Original Offer-to-Public-Existence Memo Template - The complete original template is preserved in this lesson's source appendix. The completed Offer Readiness executive summary, separate Go-Live Readiness Inventory and actual scoring rubric remain source dependencies, not invented attachments.

Assigned source links

D0440 original source 1

Complete native original body, including retained document-part text

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

# C5 Offer-to-Public-Existence Memo — Template

**Purpose:** anchor the M5.1 distinction in writing before the rest of C5 begins. Operators complete this in 60-90 minutes during M5.1.
**Filename when filed:** `Offer-to-Public-Existence-[YourName]-[Date].md`
**Target length:** 500-800 words across six sections.

---

## Section 1 — Your C4 End State (80-120 words)

Paste (do not re-write — paste) the Executive Summary section from your M4.8 Offer Readiness Document.

> [Paste here]

---

## Section 2 — Offer Readiness in One Sentence (40-70 words)

Write one sentence describing what you have at the end of C4. Use vocabulary suggesting internal-completeness: "complete," "documented," "signed," "filed," "drafted."

> [Your sentence here]

---

## Section 3 — Market-Discoverable in One Sentence (40-70 words)

Write one sentence describing what you will have at the end of C5. Use vocabulary suggesting external existence: "live," "published," "sent," "responded," "visible."

> [Your sentence here]

**Self-check:** if Sections 2 and 3 use similar vocabulary, rewrite Section 3. Most students rewrite this 2-3 times.

---

## Section 4 — The Specific Difference (150-250 words)

In narrative prose, explain what changes between your C4 end state and your C5 end state. Cite specific artifact transitions:

- Landing page: from [markdown in Drive] to [live URL]
- Mechanism proof: from [internal notes] to [published artifact]
- Buyer pool: from [warm list in Drive] to [N humans contacted with classified responses]
- [Add 1-2 more transitions specific to your situation]

> [Your narrative here]

---

## Section 5 — Stage 1 Graduation Criteria in Your Own Words (100-150 words)

State the Stage 1 graduation criteria as you understand them. Explicitly name:
- Territory mastery (as you'll demonstrate it)
- Foundational literacy (as you'll demonstrate it)
- Explicit acknowledgment that first paid customer is NOT required

> [Your statement here]

---

## Section 6 — Readiness Inventory Summary (100-150 words)

Brief narrative summary of the structured Go-Live Readiness Inventory (filed separately). Identify:
- What is ready to go live today
- What needs to be produced from scratch
- What needs to be tested
- What needs calendar time rather than active work

> [Your summary here]

---

## Submission Notes

- File this memo and the structured Go-Live Readiness Inventory in your Drive C5 folder
- Submit to the offer-to-public-existence-reviewer (Sonnet) for AI rubric scoring
- Target score: ≥ 7/10
- Resubmission allowed; 3rd attempt triggers mentor assignment

---

*Template version: 2.0 · Updated April 24, 2026*

Understand the six-part Grand Slam Offer curriculum

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and the limits of this overview

Explain the purpose and sequence of all six modules named in the supplied “C6 — The Grand Slam Offer (Hormozi)” overview. The document identifies itself as an excerpt from the Riser Nation Academy 2026 syllabus. It places the legacy course in Stage 2, Sailboat, during the Build → Do phase, after C5 Graduation, with 12–16 hours over two weeks. That averages 6–8 active hours per week; the source does not allocate time to individual modules.

Those legacy labels do not replace this lesson's current spreadsheet assignments. The source repeats its stage, prerequisite and time line; the complete original retains both occurrences. Its statement that the master syllabus remains intact is a source statement, not a new independent audit of that master.

The overview supplies a purpose, a short description and six module titles. It does not contain six complete module scripts, the MAGIC acronym expansion or the full Kennedy What-If framework. The orientation below teaches what the overview provides and labels explanatory applications. Missing module bodies remain explicit rather than being represented as recovered source material.

Begin with the exchange and the mismatch

An offer describes what the buyer gives and what the provider gives in return. The overview contrasts commodity offers, compared mainly on price, with offers evaluated on perceived value. Its provocative “Grand Slam” language expresses the ambition to make an offer compelling; it is not a reason to insult people who decline or claim that every buyer should purchase.

An authored application is to inspect the exchange from the intended buyer's position. Can the buyer understand the result, the delivery, the conditions and the price? Is the stated value supported, and does the actual service fit the buyer? A more persuasive description cannot repair a delivery promise that the business cannot fulfill.

M6.1: the Value Equation

The supplied overview summarizes the direction of Hormozi's Value Equation as increasing the desired outcome and belief while reducing time and work. Keep all four considerations visible. Ask what the buyer wants, what supports confidence, how long meaningful progress takes and what the buyer must do or give up.

The source does not supply a numeric worksheet or measurement scale. Do not invent a calculated value score and call it part of this excerpt. As an authored exercise, write one evidence-backed sentence about each consideration and mark any unsupported belief or timing claim as an assumption. Acquisition.com's Value Equation resource is a directly relevant primary reference; its linked training is separate from this short source overview.

M6.2: trim and stack methodology

The second named module concerns what belongs in the offer. The overview names trim and stack but gives no step-by-step method. Its plain-language description then refers to adding bonuses.

An authored application is to examine whether each proposed component helps the buyer achieve the scoped outcome or overcome a relevant obstacle. Identify unnecessary burden before adding more material. Record the purpose of each retained component and the work required to deliver and use it. This exercise is an application for RISER NATION, not a claim that the missing module text has been recovered.

M6.3: bonuses, scarcity, urgency and guarantees

All four enhancers named in the module title belong in the outline. Bonuses are additional components; scarcity concerns a limit on availability; urgency concerns a timing constraint; a guarantee states a specific commitment and its conditions. These plain-language explanations help the learner distinguish the terms without inventing the absent lesson body.

For an authored review, check that every bonus has a relevant purpose, every capacity or deadline claim reflects a real constraint, and every guarantee is consistent with the offer's written terms and delivery ability. A countdown or a “limited” label is not evidence that the limit is real. Do not present a guarantee as proof that every buyer will achieve an outcome.

The official Guarantee Creation and Scarcity & Urgency pages provide relevant reference destinations. Their videos and downloads have not been transcribed into this assigned excerpt.

M6.4: naming framework, MAGIC

The fourth module explicitly names MAGIC. Preserve that label, but do not invent what its letters stand for from this overview alone. The actual framework definition must be sourced before a lesson claims to teach its complete sequence.

An authored naming exercise can still ask whether a name helps the intended buyer recognize the offer and whether the surrounding description explains it accurately. That is a general clarity exercise, not a substitute acronym. The primary Naming Products resource is linked for further study and framework verification.

M6.5: scenario-based guarantees, Kennedy What-If

The fifth module names scenario-based guarantees and associates its What-If label with Kennedy. The overview does not provide a citation, the complete method or example terms. Keep that attribution attached to the source's label rather than implying this excerpt proves authorship of a detailed framework.

An authored exercise is to list possible situations that would need clear terms: a buyer seeks a refund, a required activity is not completed, delivery is delayed or an expected result does not occur. Identify the unresolved question in each scenario; do not manufacture a binding policy or a promised remedy. A complete lesson on the named method requires its missing source body.

M6.6: downsell architecture

The final module concerns the downsell, which the overview also mentions in its plain-language summary. The source does not specify a price ladder or a downsell offer.

As an authored application, distinguish a smaller scoped alternative from secretly discounting the same engagement or steering an unsuitable buyer into another unsuitable purchase. State what changes in delivery, support, commitment and price, and whether the alternative still fits the buyer's actual need. Do not claim a specific downsell is authorized or available merely because this module is named.

Connect the curriculum themes and check understanding

The Hormozi connection is explicit in the source title and its four-part value discussion. The additional Brunson/ClickFunnels connection is an authored application: the hook, story, offer and next step should describe the same exchange, with consistent proof and terms. It is not a claim that the supplied overview contains a separate Brunson lesson.

To finish, explain the mismatch the course is intended to address, state the source's prerequisite and workload, and identify all six modules in order. Then separate the available overview material from the missing detailed frameworks. A useful orientation prepares the learner for those lessons without pretending they are already present.

Clickable source and resources

- Assigned C6 Grand Slam Offer overview - Acquisition.com offer-training index - The complete assigned overview is preserved in the lesson appendix. Detailed module bodies, the MAGIC definition and the Kennedy What-If source remain explicit dependencies.

Assigned source links

D0441 original source 1

Complete returned native document text

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

C6 — The Grand Slam Offer (Hormozi) — Course Overview
============================================================

Source: Riser Nation Academy 2026 Syllabus
Stage: Stage 2 — Sailboat  ·  Phase: Build → Do  ·  Prereq: C5 Graduation passed  ·  Time: 12–16 hours over 2 weeks

NOTE: This document is an excerpt copied from the master syllabus.
The master syllabus remains intact and unmodified.

Stage: Stage 2 — Sailboat  ·  Phase: Build → Do  ·  Prereq: C5 Graduation passed  ·  Time: 12–16 hours over 2 weeks
In Plain Words
An offer is what you give for what they give you. A Grand Slam Offer is so good people feel stupid saying no. We use Hormozi's Value Equation: more dream, more belief, less time, less work. Then we stack bonuses, add a guarantee, name it well, and prepare the downsell.
The Mismatch This Course Fixes
Mismatch between commodity offers (sell on price) and Grand Slam offers (sell on value perception).
Modules

---

MODULES IN THIS COURSE
---
M6.1 — THE VALUE EQUATION
M6.2 — TRIM & STACK METHODOLOGY
M6.3 — ENHANCERS — BONUSES, SCARCITY, URGENCY, GUARANTEES
M6.4 — NAMING FRAMEWORK (MAGIC)
M6.5 — SCENARIO-BASED GUARANTEES (KENNEDY WHAT-IF)
M6.6 — DOWNSELL ARCHITECTURE


---
END OF C6 OVERVIEW
---
Complete local source copy including original filing metadata and formatting

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/1OThcV05CW77EGGMIdoTZ42ZIOTJOCnqYM187vPlaYgw/edit?usp=drivesdk"
drive_file_id: "1OThcV05CW77EGGMIdoTZ42ZIOTJOCnqYM187vPlaYgw"
created: "2026-05-11T23:30:23.200Z"
modified: "2026-06-04T17:06:07.440Z"
---

# C6 - The Grand Slam Offer (Hormozi) - Course Overview

C6 — The Grand Slam Offer (Hormozi) — Course Overview
============================================================


Source: Riser Nation Academy 2026 Syllabus
Stage: Stage 2 — Sailboat  ·  Phase: Build → Do  ·  Prereq: C5 Graduation passed  ·  Time: 12–16 hours over 2 weeks


NOTE: This document is an excerpt copied from the master syllabus.
The master syllabus remains intact and unmodified.


Stage: Stage 2 — Sailboat  ·  Phase: Build → Do  ·  Prereq: C5 Graduation passed  ·  Time: 12–16 hours over 2 weeks
In Plain Words
An offer is what you give for what they give you. A Grand Slam Offer is so good people feel stupid saying no. We use Hormozi's Value Equation: more dream, more belief, less time, less work. Then we stack bonuses, add a guarantee, name it well, and prepare the downsell.
The Mismatch This Course Fixes
Mismatch between commodity offers (sell on price) and Grand Slam offers (sell on value perception).
Modules


---


MODULES IN THIS COURSE
---
M6.1 — THE VALUE EQUATION
M6.2 — TRIM & STACK METHODOLOGY
M6.3 — ENHANCERS — BONUSES, SCARCITY, URGENCY, GUARANTEES
M6.4 — NAMING FRAMEWORK (MAGIC)
M6.5 — SCENARIO-BASED GUARANTEES (KENNEDY WHAT-IF)
M6.6 — DOWNSELL ARCHITECTURE




---
END OF C6 OVERVIEW
---

Assemble an offer architecture that agrees across every attachment

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome, prerequisites and source boundaries

Use the C7 Offer Architecture Document Template to explain how seven completed artifacts become one internally consistent delivery specification. The source calls this legacy M7.8, a 12–20-page capstone requiring an Opus 4.7 validator and instructor co-sign before C8 enrollment. Follow the current spreadsheet assignment for this lesson; these labels describe the source workflow.

The seven inputs are the Distinction Statement, Deliverable Decomposition, Fulfillment SOP Library, Customer Lifecycle Map, Capacity Constraint Analysis, Operator Bandwidth Audit and Offer v2.0. The template contains fields for their summaries and references; it does not supply those completed attachments. It also names rules and clauses whose complete definitions are not included. Preserve those dependencies instead of filling blank approvals, measurements or signatures with invented information.

The intended validation checks for three failures: parts that never form a coherent whole, promises that exceed capacity, and a design fitted to a few past customers rather than the intended customer profile. A named AI validator is not evidence that it has been deployed or that a particular submission passed.

Section 0: identify the document and verify the attestations

Complete the eight header fields: operator name, stage, offer name, offer version, document version, date, whether C6 prerequisites cleared, and whether all M7.1–M7.7 deliverables are attached. The source preprints Stage 2, Sailboat; offer v2.0; and document version 1.0. They are template values, not proof of the learner's actual status.

Review all eight attestations before signing:

  1. Preserve the prior v1.1 offer separately and identify the new architecture as the structure of delivering v2.0.
  2. Check that decomposed deliverables are atomic rather than vague composite activities. The template references a four-criterion test but does not define it; obtain the actual test before claiming it passed.
  3. Derive the customer ceiling from measured hours and the capacity analysis, not aspirations. The named Honest Capacity Clause is an additional source dependency.
  4. Confirm that the change concerns architecture rather than a new mechanism, customer or problem. The Architecture-vs-Pivot Distinction Clause must be consulted where applicable.
  5. Ensure SOPs describe executable work and pass the referenced operability test. Do not claim compliance with the absent SOP Operability Clause merely because an SOP exists.
  6. Preserve the v2.x and v3.0 iteration discipline referenced through the C6 clause and Attachment 7, Section 11.
  7. Verify the actual M7.5 capacity review, M7.7 offer review, M7.8 AI validation and M7.8 instructor co-sign records. These are distinct gates.
  8. Preserve the C6 Honest Customer Representation commitment in subsequent marketing, sales and case-study work.

The signature and date attest to real evidence. The header appears before some reviews have occurred, so leave the relevant approval claim pending until its actual gate clears. Do not sign a statement that future reviews are already complete.

Sections 1 and 2: orient the reader and maintain the distinction

Section 1 is a 250–400-word executive summary. State the offer, the customer, what v2.0 commits to and what it excludes. This is reader orientation, not a substitute for the detailed supporting artifacts.

Section 2 is a 200–300-word account of what v1.1 was, what the architecture is, why the distinction matters operationally and which of two failure modes posed the greater risk: an iteration loop or a pivot disguised as architecture. Cite the referenced 3-Customer Test result. The test's procedure and a completed result are not present in this template; mark that dependency rather than inventing a test outcome.

An authored example of the distinction is changing how a defined deliverable is produced and reviewed while preserving its intended customer and problem. A new target customer or a new mechanism requires a different decision; it should not be hidden under the label “architecture.”

Sections 3 and 4: connect deliverables to fulfillment SOPs

Section 3 references Attachment 2. Report the number of atomic deliverables, lifecycle phases, cohort-produced versus per-customer work where applicable, and candidates identified under the referenced 6% Rule. Include Attachment 2's Section 3 deliverable summary table. The rule's definition is absent from this source, so do not infer that any arbitrary six percent of tasks is the intended method.

Section 4 references Attachment 3. Report the number of SOPs authored, the number covering high-leverage standardizations, the percentage tied to atomic deliverables and the percentage passing the operability test. Include the SOP-to-deliverable mapping table. The two preprinted 100% values are expectations in the template; they are not measured results for the learner.

An authored consistency check traces every retained deliverable to the procedure that produces it. A list of procedures without a relationship to the promised work does not establish fulfillment coverage. Preserve an uncovered item as a gap until the corresponding procedure and review evidence exist.

Section 5: reproduce the lifecycle and its gates

Reference Attachment 4. Reproduce its Section 4 Mermaid lifecycle diagram and Section 5 gate specification table, and summarize its Section 6 off-path scenarios. Record the total lifecycle stages, transition gates, touchpoints and documented off-path scenarios.

Do not create a generic diagram and label it the original attachment. The blank capstone template does not include that diagram or its gate table. When the actual artifact is available, retain its details and check that its transitions agree with the offer's engagement structure. An authored application is to ask what evidence permits a transition and what happens when that evidence is missing.

Section 6: report the actual capacity constraint

Use Attachment 5 with its human-in-the-loop sign-off. Reproduce the ceiling statement from Section 7, bottleneck identification from Section 3 and quality-degradation thresholds from Section 5. Complete the five summary fields: concurrent-customer ceiling, bottleneck activity, named quality thresholds, cohort-variant ceiling if applicable, and whether human review cleared.

The ceiling needs support from the measured work. A sales target is not a capacity calculation. Keep any unresolved mismatch between the stated ceiling, time evidence and promised delivery visible until the relevant attachment is corrected.

Section 7: report measured bandwidth and hidden work

Reference Attachment 6 and its human review. Reproduce the audit output statement from Section 9, estimate-versus-measured table from Section 4 and hidden-cost inventory from Section 5. Record the measurement-window length, measured per-customer hours per week, measured hours for a full engagement, percentage difference between estimates and measurements, and hidden costs as a share of total time.

Separate measured entries from estimates and explain the denominator used for any percentage. Do not extrapolate a short measurement window into a full-engagement total without labeling the assumptions. That is an authored data-quality check; the template supplies fields rather than a completed measurement record.

Section 8: carry forward the offer's boundaries

Reference Attachment 7 with cohort-partner and instructor sign-offs. Reproduce four specific sections: its anti-pivot statement from Section 2, capacity statement from Section 6, anti-promise list from Section 7 and account of how v2.0 differs from v1.1 from Section 8.

Copying these references preserves the relationship between the delivery architecture and the actual offer. Do not soften exclusions or silently increase capacity in the capstone summary. If the original offer needs revision, revise and review that source artifact so the two documents remain traceable.

Section 9: run all seven internal-consistency checks

Before validator submission, check every relationship named in the template:

  1. M7.6 per-customer hours agree with M7.5 bottleneck calculations.
  2. The M7.5 customer ceiling matches M7.7's capacity statement.
  3. M7.2 deliverable counts agree with M7.3 SOP references and M7.4 lifecycle stages.
  4. M7.4 stages match the engagement structure in Attachment 7, Section 4.
  5. Anti-promises agree with what the deliverables actually produce.
  6. No deliverable promises an outcome explicitly excluded by the anti-promise list.
  7. Any cohort variant is treated consistently in decomposition, lifecycle, capacity and the offer.

If a check fails, revise the affected attachment before submission. Checking a box cannot reconcile contradictory facts. Keep the revision connected to the document version used for the next review.

Section 10: test whether the architecture generalizes

The source's bespoke-architecture trap is overfitting the design to the first one to three customers. Apply all five checks: stages and gates should work for hypothetical fourth, fifth and sixth customers who fit the profile; deliverables should be universal within that profile; SOPs should not be named after or specific to one past customer; capacity should account for customer variation rather than only an average; and any customization budget should be bounded rather than absorbing structural differences.

If a check fails, separate the universal structure from customer-specific accommodations and revise the relevant attachment. This is not a demand that all customers be identical. It asks whether the offer's shared structure remains workable across its defined audience.

Sections 11 and 12: record validation and human judgment separately

The source proposes submitting Sections 1–10 with Attachments 1–7 to `offer-architecture-validator-v1.0.0`, associated with Opus 4.7. Preserve the header and relevant signed clauses as well; the submission shorthand does not make those required parts disposable.

The three named outcomes have different routes. VALIDATED proceeds to instructor co-sign. NEEDS_REVISION sends the operator back to specific attachments and then resubmission. REJECTED identifies a fundamental issue requiring rebuilding relevant M7.2, M7.5 or M7.7 material. Record submission date, output filename, outcome, the response to requested revisions and the final outcome. The template's preprinted final VALIDATED field must not be treated as a result before review.

Section 12 records instructor name, signature, co-sign date and optional comments. The instructor reviews the AI output, revision responses and overall coherence. The source proposes a 24–72-hour co-sign service interval; that is not a verified service commitment from this academy.

Section 13: bundle the complete record and plan the timing

List all seven attachment filenames in order. Include human sign-offs for the capacity analysis and bandwidth audit, and cohort plus instructor sign-offs for Offer v2.0. Also retain the five named signed clause documents: Honest Capacity, Architecture-vs-Pivot Distinction, SOP Operability, C6 Iteration Discipline and C6 Honest Customer Representation.

The source calls the resulting package a permanent completion record and C8 entry artifact. It estimates 6–10 active hours for Sections 1–10 assuming the attachments already exist, plus a 24–72-hour AI validation cycle and a separate 24–72-hour instructor co-sign interval. Those sequential intervals imply 48–144 hours of review elapsed time before revisions or scheduling changes, not an additional measured block of operator labor. Actual provisioning and reviewer availability remain unverified.

Connect offer promises to delivery evidence

The authored Brunson/ClickFunnels application is consistency between the public offer and what its supporting story and delivery actually establish. The authored Hormozi/Acquisition.com application is to support perceived value with a credible, bounded delivery plan, including time, effort and capacity. Neither perspective makes an AI PASS, a long document or a signed blank template sufficient evidence.

For practice, choose one discrepancy—for example, two different customer ceilings—and trace which attachment must change, which claims depend on it and which review must be repeated. The complete original template, including its tables and blank fields, remains in the appendix; missing attachment bodies and clause definitions remain explicit dependencies.

Clickable assigned source

- Original C7 Offer Architecture Document Template

Assigned source links

D0442 original source 1

Original tables and embedded resource links
D0442 original Markdown table 1; blank cells and source claims retained
FieldValue
Operator name
Operator stageStage 2 (Sailboat)
Offer name
Offer versionv2.0
Document version1.0
Document date
C6 prerequisites clearedY / N
C7 module deliverables M7.1-M7.7 attachedY / N
D0442 original Markdown table 2; blank cells and source claims retained
FieldValue
Total atomic deliverables
Lifecycle phases
Cohort-produced vs per-customer (if applicable)
6% Rule standardization candidates identified
D0442 original Markdown table 3; blank cells and source claims retained
FieldValue
Total SOPs authored
SOPs covering high-leverage standardizations (6% Rule)
SOPs tied to atomic deliverables (% of total)100%
SOPs passing operability test100%
D0442 original Markdown table 4; blank cells and source claims retained
FieldValue
Total lifecycle stages
Total transition gates
Total touchpoints across full lifecycle
Off-path scenarios documented
D0442 original Markdown table 5; blank cells and source claims retained
FieldValue
Concurrent-customer ceiling
Bottleneck activity
Quality-degradation thresholds named
Cohort variant ceiling (if applicable)
HITL clearedY / N
D0442 original Markdown table 6; blank cells and source claims retained
FieldValue
Measurement window length
Per-customer per-week (measured)
Total per-customer (full engagement, measured)
Estimate-vs-measured delta %
Hidden costs as % of total time
Complete native original body, including retained document-part text

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

# C7 Offer Architecture Document Template

**Course:** C7 Offer Architecture
**Module:** M7.8 — Offer Architecture Document (capstone synthesis)
**Document Type:** Operator-completed capstone; Opus 4.7 validator + instructor co-sign required
**Length:** 12-20 pages when complete (synthesizes M7.1-M7.7 deliverables)

---

## Purpose

The Offer Architecture Document is the C7 capstone. It bundles the seven preceding artifacts (Distinction Statement, Deliverable Decomposition, Fulfillment SOP Library, Customer Lifecycle Map, Capacity Constraint Analysis, Operator Bandwidth Audit, Offer v2.0) into a single, internally consistent architectural specification.

The document receives multi-document validation by Opus 4.7 (`offer-architecture-validator-v1.0.0`), which cross-references the seven artifacts for internal consistency and detects three failure patterns: decomposition without integration, capacity-claim mismatch, and bespoke architecture indicators.

After Opus validation, the document receives instructor co-sign. Both gates must clear before C8 enrollment.

---

## Section 0: Document Header and Attestation

| Field | Value |
|-------|-------|
| Operator name | |
| Operator stage | Stage 2 (Sailboat) |
| Offer name | |
| Offer version | v2.0 |
| Document version | 1.0 |
| Document date | |
| C6 prerequisites cleared | Y / N |
| C7 module deliverables M7.1-M7.7 attached | Y / N |

### Attestation Clauses

I attest to the following:

1. **Distinction maintained.** I have produced the Offer Architecture as a structure, distinct from any document I produced in prior courses. My v1.1 offer document is preserved separately; this document is the architecture of how v2.0 is delivered.

2. **Decomposition is atomic.** The deliverables enumerated in Attachment 2 (M7.2 Decomposition) pass the four-criterion atomicity test. They are not composite "we work together on X" items.

3. **Capacity is honest.** The concurrent-customer ceiling stated in the v2.0 offer (Attachment 7) and the capacity analysis (Attachment 5) derives from measured operator hours per customer (Attachment 6), not from aspirational projections. I commit to the C7 Honest Capacity Clause.

4. **v2.0 is architectural.** The v2.0 offer changes the architecture, not the mechanism, customer, or problem. I commit to the C7 Architecture-vs-Pivot Distinction Clause.

5. **SOPs are operable.** The fulfillment SOPs (Attachment 3) describe what is done, not what should be done. Each passes the operability test. I commit to the C7 SOP Operability Clause.

6. **Iteration discipline endures.** Iteration trajectory for v2.x and v3.0 follows the C6 Iteration Discipline Clause as specified in Attachment 7 Section 11.

7. **HITL gates cleared.** The M7.5 capacity HITL has cleared (instructor sign-off in Attachment 5). The M7.7 Offer v2.0 review has cleared (sign-off in Attachment 7). The M7.8 Opus 4.7 validation has cleared (output appended below). The M7.8 instructor co-sign has cleared (signature below).

8. **Honest customer representation continues.** I commit to the C6 Honest Customer Representation Clause in all v2.0-era marketing, sales, and case-study work.

**Operator signature:** ___________________________
**Date:** ___________________________

---

## Section 1: Executive Summary

In 250-400 words, summarize the offer architecture. The summary is the document's reader-orientation; it states what the offer is, who it serves, what is being committed to in v2.0, and what is not being committed to.

[Operator writes the executive summary here]

---

## Section 2: Distinction Statement (M7.1)

Reference: Attachment 1 (full M7.1 Distinction Statement).

In this section, summarize in 200-300 words:
- What v1.1 was (the document)
- What this Offer Architecture is (the structure)
- Why the distinction matters operationally (cite the 3-Customer Test result)
- Which failure mode the operator was at higher risk of (Iteration Loop or Pivot Disguised as Architecture)

[Operator writes here]

---

## Section 3: Deliverable Decomposition (M7.2)

Reference: Attachment 2 (full M7.2 Decomposition).

In this section, summarize:

| Field | Value |
|-------|-------|
| Total atomic deliverables | |
| Lifecycle phases | |
| Cohort-produced vs per-customer (if applicable) | |
| 6% Rule standardization candidates identified | |

Include the deliverable summary table from Attachment 2 Section 3.

---

## Section 4: Fulfillment SOP Library (M7.3)

Reference: Attachment 3 (full M7.3 SOP Library).

In this section, summarize:

| Field | Value |
|-------|-------|
| Total SOPs authored | |
| SOPs covering high-leverage standardizations (6% Rule) | |
| SOPs tied to atomic deliverables (% of total) | 100% |
| SOPs passing operability test | 100% |

Include the SOP-to-deliverable mapping table.

---

## Section 5: Customer Lifecycle Map (M7.4)

Reference: Attachment 4 (full M7.4 Lifecycle Map).

In this section:

- Reproduce the Mermaid lifecycle diagram from Attachment 4 Section 4
- Reproduce the gate specification table from Attachment 4 Section 5
- Summarize the off-path scenarios from Attachment 4 Section 6

| Field | Value |
|-------|-------|
| Total lifecycle stages | |
| Total transition gates | |
| Total touchpoints across full lifecycle | |
| Off-path scenarios documented | |

---

## Section 6: Capacity Constraint Analysis (M7.5)

Reference: Attachment 5 (full M7.5 Capacity Analysis), with HITL sign-off.

In this section:

- Reproduce the ceiling statement from Attachment 5 Section 7
- Reproduce the bottleneck identification from Attachment 5 Section 3
- Reproduce the quality-degradation thresholds table from Attachment 5 Section 5

| Field | Value |
|-------|-------|
| Concurrent-customer ceiling | |
| Bottleneck activity | |
| Quality-degradation thresholds named | |
| Cohort variant ceiling (if applicable) | |
| HITL cleared | Y / N |

---

## Section 7: Operator Bandwidth Audit (M7.6)

Reference: Attachment 6 (full M7.6 Bandwidth Audit), with HITL sign-off.

In this section:

- Reproduce the audit output statement from Attachment 6 Section 9
- Reproduce the estimate-vs-measured comparison table from Attachment 6 Section 4
- Reproduce the hidden costs inventory from Attachment 6 Section 5

| Field | Value |
|-------|-------|
| Measurement window length | |
| Per-customer per-week (measured) | |
| Total per-customer (full engagement, measured) | |
| Estimate-vs-measured delta % | |
| Hidden costs as % of total time | |

---

## Section 8: Offer v2.0 Document (M7.7)

Reference: Attachment 7 (full M7.7 Offer v2.0 Document), with cohort partner and instructor sign-offs.

In this section, reproduce:

- Section 2 of Attachment 7 (Anti-Pivot Statement: what is not changing)
- Section 6 of Attachment 7 (Capacity Statement)
- Section 7 of Attachment 7 (Anti-Promise List)
- Section 8 of Attachment 7 (How v2.0 Differs From v1.1)

---

## Section 9: Internal Consistency Check (Operator-Completed)

Before submitting to the Opus 4.7 validator, the operator self-checks the architecture for internal consistency. Check each item:

- [ ] The total per-customer hours in M7.6 (Attachment 6) is consistent with the bottleneck math in M7.5 (Attachment 5).
- [ ] The concurrent-customer ceiling in M7.5 (Attachment 5) matches the capacity statement in M7.7 Section 6 (Attachment 7).
- [ ] The deliverable count in M7.2 (Attachment 2) matches the deliverables referenced in M7.3 SOPs (Attachment 3) and M7.4 lifecycle stages (Attachment 4).
- [ ] The lifecycle stages in M7.4 (Attachment 4) match the engagement structure in M7.7 Section 4 (Attachment 7).
- [ ] The anti-promises in M7.7 Section 7 (Attachment 7) are consistent with what the deliverables (Attachment 2) actually produce.
- [ ] No deliverable in Attachment 2 promises an outcome named in the anti-promise list of Attachment 7.
- [ ] The cohort variant (if applicable) is treated consistently in M7.2, M7.4, M7.5, and M7.7.

If any check fails, the operator revises the relevant attachment before Opus submission.

---

## Section 10: Bespoke Architecture Trap Self-Check (Operator-Completed)

The Bespoke Architecture Trap is the C7 failure case where an operator over-fits the architecture to the first 1-3 customers. Self-check:

- [ ] The lifecycle stages and gates (Attachment 4) generalize to a hypothetical fourth, fifth, and sixth customer who would enroll at v2.0 — not just the v1.x customers I have served.
- [ ] The deliverables (Attachment 2) are universal — they would be produced for any customer fitting the v2.0 customer profile, not customer-specific accommodations.
- [ ] No SOP in the library (Attachment 3) is named after or specific to a single past customer.
- [ ] The capacity ceiling (Attachment 5) accounts for variance across customers, not just the average of the v1.x cohort.
- [ ] The customization budget (if any) is bounded and does not absorb structural variation.

If any check fails, the operator separates universal-architecture elements from customer-specific accommodations and revises the relevant attachment.

---

## Section 11: Opus 4.7 Validator Submission

The complete document (Sections 1-10 + Attachments 1-7) is submitted to Opus 4.7 (`offer-architecture-validator-v1.0.0`). The validator runs multi-document cross-reference and outputs one of three outcomes:

- **VALIDATED** — proceed to instructor co-sign
- **NEEDS_REVISION** — operator revises specific attachments per the validator's findings, then resubmits
- **REJECTED** — fundamental architecture issue; operator returns to the relevant module (M7.2, M7.5, M7.7) and rebuilds the affected attachment

**Validator submission date:** ___________________________
**Validator output filename:** ___________________________
**Validator outcome:** VALIDATED / NEEDS_REVISION / REJECTED
**Operator response to validator findings (if NEEDS_REVISION):**

[Operator notes here, with revised attachments referenced]

**Final validator outcome (after revisions, if any):** VALIDATED

---

## Section 12: Instructor Co-Sign

After Opus validation clears, the document receives instructor co-sign. The instructor reviews the validator output, the operator's responses to revisions, and the architecture's coherence at the human-judgment level.

**Instructor name:** ___________________________
**Instructor signature:** ___________________________
**Date of co-sign:** ___________________________
**Co-sign SLA:** 24-72 hours from operator submission of validated document.

**Instructor comments (optional):**

[Instructor writes here]

---

## Section 13: Attachments

The following attachments are bundled with this document. Each attachment is a complete deliverable from M7.1-M7.7.

- **Attachment 1:** M7.1 Distinction Statement (filename: ___________)
- **Attachment 2:** M7.2 Deliverable Decomposition (filename: ___________)
- **Attachment 3:** M7.3 Fulfillment SOP Library (filename: ___________)
- **Attachment 4:** M7.4 Customer Lifecycle Map (filename: ___________)
- **Attachment 5:** M7.5 Capacity Constraint Analysis (with HITL sign-off, filename: ___________)
- **Attachment 6:** M7.6 Operator Bandwidth Audit (with HITL sign-off, filename: ___________)
- **Attachment 7:** M7.7 Offer v2.0 Document (with cohort + instructor sign-offs, filename: ___________)

Signed clause documents (referenced in Section 0 attestation):
- C7 Honest Capacity Clause (signed)
- C7 Architecture-vs-Pivot Distinction Clause (signed)
- C7 SOP Operability Clause (signed)
- C6 Iteration Discipline Clause (signed in C6, referenced in C7)
- C6 Honest Customer Representation Clause (signed in C6, referenced in C7)

---

*This document, with all attachments and clearances, is the C7 completion artifact. It is filed in the operator's permanent records and is the entry artifact for C8 enrollment.*

*Estimated completion time: 6-10 hours active for Sections 1-10 (the attachments are already complete from M7.1-M7.7). Opus validation cycle: 24-72 hours. Instructor co-sign SLA: 24-72 hours.*

Respond to scope requests without hiding their cost

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and scope

Use all seven steps of the C7 Scope-Creep Recovery Script to record a request, classify it, check the offer boundaries, respond and track its cost. The source describes a one-to-two-page operator script used during active engagements, especially the legacy M7.6 measurement window. Its references to C7, C6 and M7.6 do not change the current spreadsheet assignment.

The script addresses requests for extra deliverables, longer engagements, individual accommodations and rework beyond a stated customization budget. It aims to prevent silent absorption—doing additional work without naming its cost—and inconsistent precedent—treating equivalent requests differently without a reason. These are useful operating concerns, not permission for this lesson to send messages or change any customer's engagement.

Step 1: record what was actually requested

Capture the customer code, date, channel and the request in the customer's words when possible. If you paraphrase, identify it as a paraphrase. The source names synchronous sessions, asynchronous messages and email as channels, and asks for an initial small, medium or large impression.

Keep that impression separate from measured effort. A request that sounds small may require substantial coordination; a request that sounds large may already be included. Do not decide from the customer's tone or from your initial estimate alone.

Step 2: use the four categories

Category A is already in scope. Confirm the relevant deliverable and do the agreed work. “No action required” in the source means no scope-change action is needed; it does not mean ignore the request or omit its labor from the time record.

Category B is outside the standard deliverable but within the stated customization budget. The source gives two hours of customer-specific example development as an example, not a default entitlement. Check the actual remaining budget, complete the allowed work and log the amount used.

Category C is outside today's scope but may reveal a general architectural improvement. Log it in the v2.x candidate inventory for future review. A candidate is not an immediate delivery promise to the customer who suggested it. The source connects this route to the C6 Iteration Discipline Clause, whose complete text is not included here.

Category D is outside scope and specific to this customer's situation. Decline the current request while offering suitable alternatives. A separate bespoke engagement needs its own scope and pricing; it is not automatically part of the existing offer.

Step 3: check the written offer before responding

Open the actual Offer v2.0 anti-promise list, referenced as Section 7. If it explicitly excludes the request, the source routes it to C or D, usually D. Use the actual boundary in the response rather than inventing a new exclusion after purchase.

If the request is not explicitly excluded, check Section 8, How v2.0 Differs From v1.1, and the actual scope. Absence from an exclusion list does not by itself establish that the work is included. If the position is ambiguous, the source defaults to Category C and asks for a cohort-partner or instructor second opinion when the request is frequent or high stakes.

The actual offer, anti-promise list and referenced clauses are dependencies. This script does not supply their missing text or settle a dispute about an existing agreement.

Step 4: preserve the structure of all four responses

The source's response pattern is to acknowledge the request, name its classification, state the action and offer alternatives when declining. Adapt the wording to your voice without changing the underlying commitment.

- For A, confirm that the request is covered, name the action and timeframe, and point to the included deliverable. - For B, confirm that the request fits the customization allowance, name the action and timeframe, and explain the amount of customization time that will remain after delivery. - For C, acknowledge the suggestion, explain that it is outside the current scope, record it as a future architecture candidate and confirm that the present engagement retains its agreed scope. If appropriate, discuss a separately scoped engagement for an urgent need; do not imply that logging the candidate guarantees a future release. - For D, acknowledge the request and explain that it is both outside the current offer and specific to this situation. The source names three alternatives: a clear decline, deferral to a future engagement, or a separately scoped and priced bespoke add-on. Only present options that are actually available.

The complete original wording for all four responses is retained in the source appendix. These are study templates; no customer message is being sent by this lesson.

Step 5: keep a useful request-and-response record

Record the date, original wording or identified paraphrase, category, response summary, estimated time impact and whether the request entered the v2.x candidate inventory. Separate estimated hours from later measured time. An entry should allow another reviewer to see why the response followed the written offer and how it compares with similar requests.

Do not replace the source request with a more convenient interpretation after the conversation. A clear record protects consistency and exposes recurring friction that might need an architectural change.

Step 6: count the cost of handling the request

The source asks the operator to record reading and classification, response drafting, customer conversation and any work performed. Even a well-handled decline consumes time. During the measurement window, it calls for SCOPE-CREEP tagging with the customer code and lifecycle stage.

There is a classification conflict worth preserving: this script includes time spent doing Category A work under that instruction, while the companion setup worksheet defines SCOPE-CREEP as work outside the offer. An authored reconciliation is to distinguish the time spent handling the scope inquiry from the included production work. Tag legitimate deliverable production with its deliverable ID, and separately record scope-request handling under an agreed convention. Obtain the applicable audit convention rather than silently classifying all in-scope work as scope creep.

For B, track both the actual work and the customization allowance consumed. For declined requests, keep the handling time even when no additional deliverable was produced. This prevents a misleading record in which refusal appears to cost nothing.

Step 7: inspect the pattern across customers

The source triggers a pattern check when the third or subsequent request occurs across customers within 30 days. It proposes a separate weekly or biweekly review lasting 15–20 minutes.

Similar requests from several customers suggest a candidate for future offer architecture. Different bespoke requests may indicate a mismatch in customer fit, prompting review of the source's C2 customer definition or the v2.0 exclusions. A concentration of requests from one customer calls for review of that engagement.

The source mentions possible pause or termination in the last situation. Do not treat a request count as an automatic termination rule. The actual agreement and circumstances are not provided by this script, and no engagement is being paused or ended here.

Recognize all five common patterns

An adjacent-problem request often falls into C or D: it may fit a separate offer, a referral or a future candidate. An extension by a number of weeks is a scope and pricing change; the source recommends treating it as a new engagement rather than absorbing the extension informally.

A request to join an external-party call is typically D, with alternatives such as written input or a separately scoped add-on. A redo is A when it remains inside the revision allowance and may be D beyond that allowance. Extra time or faster turnaround may be C when the same need recurs across customers, or D when it is a one-off need. These are the source's typical classifications, not substitutes for checking the actual agreement.

Know when to use a different conversation

The script excludes presale scope discussion, because the parties are still defining the engagement. It excludes operator-initiated free additions, which the source treats as a separately documented v2.x signal. It also excludes requests for explicitly offered optional paid add-ons, which are sales conversations rather than unexpected scope requests.

The estimated 5–10 minutes per request covers reading, classification, response and documentation. It does not include the additional delivery work that might be approved or the separate pattern review. The source connects this process to the M7.6 audit, Daily Completion Checklist and fulfillment SOP library; those complete companion artifacts are not supplied here.

Apply the marketing themes and practice

The authored Brunson/ClickFunnels application is to keep the offer communicated during purchase consistent with the offer delivered afterward. The authored Hormozi/Acquisition.com application is to protect relevant value and a workable delivery cost, rather than treating unlimited additions as proof of a stronger offer.

For practice, classify an included revision, an allowed customization, a recurring request for a new capability and a one-off bespoke request. For each, identify the written scope evidence, response pattern and time-record convention. Mark the examples as exercises rather than real customer events.

Clickable sources

- Original C7 Scope-Creep Recovery Script - Companion Time Tracking Setup Worksheet - The complete original script remains in the lesson appendix. Actual customer agreements, the Offer v2.0 boundaries and the referenced clause bodies remain explicit dependencies.

Assigned source links

D0443 original source 1

Original tables and embedded resource links
D0443 original Markdown table 1; blank cells and source claims retained
PatternTypical CategoryNotes
"Can you also help with [adjacent problem]?"C or DAdjacent problem may belong in a different offer (refer out) or in v2.x (log to candidate inventory)
"Can we extend the engagement by [N weeks]?"C or DExtension is a pricing/scope change; treat as new engagement, not as scope creep
"Can you join my call with [external party]?"DOne-off bespoke request; offer alternative (provide written input, or paid add-on)
"Can you redo [deliverable] with a different angle?"A (if within revision budget) or DRevision budget is named in v2.0; beyond budget = bespoke
"Can you give me extra time / faster turnaround?"C if pattern is across customers, D if one-offPattern across customers = SOP review; one-off = bespoke
Complete native original body, including retained document-part text

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

# C7 Scope-Creep Recovery Script

**Course:** C7 Offer Architecture
**Module:** Cross-cutting; primary use during M7.6 measurement window and active customer engagements
**Document Type:** Operator script
**Length:** 1-2 pages

---

## Purpose

When a customer requests work outside the offer's stated scope — additional deliverables, expanded engagement length, customer-specific accommodations, or rework beyond the standard customization budget — the operator runs this script to identify the request, classify it, and respond consistently with the C7 Architecture-vs-Pivot Distinction Clause and Offer v2.0 anti-promise list.

The script prevents two common failures:
1. **Silent absorption** — operator does the requested work without acknowledging it as out-of-scope, then resents the time cost
2. **Inconsistent precedent** — operator says yes to one customer's request and no to another's identical request, eroding the architecture's coherence

---

## Script

### Step 1: Receive the request

The customer has requested something. Document the request literally — quote the customer where possible.

**Customer:** [Customer code]
**Date received:** [YYYY-MM-DD]
**Channel:** [Synchronous session / async message / email]
**Request (verbatim or close paraphrase):**

> [Customer's request, as stated]

**Operator's first impression of the request size:** Small / Medium / Large

### Step 2: Classify the request

Apply the four-category classification:

**Category A: In-Scope (no action required, do the work)**

The request is something the offer's deliverables already include. The customer may not have realized this; the operator confirms that yes, this is part of the offer. No anti-promise activation needed.

**Category B: Within-Customization-Budget (do the work; document)**

The request is technically outside the standard deliverable but falls within the v2.0-stated customization budget (e.g., "up to 2 hours of customer-specific example development per customer"). The operator does the work and logs it against the customization budget.

**Category C: Out-of-Scope, Architectural-Question (defer to v2.x candidate inventory)**

The request is outside scope, but the request is a SIGNAL — multiple customers might benefit from this becoming part of the offer. The operator does NOT do the work for this customer. Instead, the request is logged in the v2.x candidate inventory for future architecture review (per the C6 Iteration Discipline Clause).

**Category D: Out-of-Scope, Bespoke-Question (decline; offer alternatives)**

The request is outside scope and is customer-specific (would not generalize to other customers). The operator declines and offers structured alternatives.

**Classification of this request:** A / B / C / D

### Step 3: Verify classification against anti-promise list

Open Offer v2.0, Section 7 (Anti-Promise List). Does the request map to a listed anti-promise?

- **YES, request is explicitly anti-promised.** Classification is C or D (most likely D). The script's Step 4 response uses anti-promise language directly.
- **NO, request is not explicitly anti-promised.** Verify Section 8 (How v2.0 Differs From v1.1) — is this in scope per v2.0 architecture?
- **AMBIGUOUS.** The request is neither anti-promised nor explicitly included. Default to Category C (defer to v2.x candidate inventory) and consult cohort partner or instructor for second opinion if the request is high-frequency or high-stakes.

### Step 4: Respond to the customer

Use the response language for the classified category:

**Category A response:**

> "Yes — what you're asking for is part of the engagement. I'll [action] in [timeframe]. Just to confirm, this is covered under [reference to deliverable]."

**Category B response:**

> "Yes — I can do that. It falls within the customization scope of the engagement. I'll [action] in [timeframe]. Once delivered, we'll have [specific amount remaining] of customization time for the rest of the engagement."

**Category C response:**

> "I appreciate you raising this. It's not part of the current engagement scope, and I want to be straight about that rather than absorb it informally. What you're describing is a worthwhile thing for me to look at as part of the offer architecture's next iteration — I'm logging it now for the v2.x candidate inventory. For your engagement, we'll continue with the agreed scope. If this is urgent for you specifically, we can talk about whether a separate engagement makes sense."

**Category D response:**

> "I appreciate you raising this. It's not something the engagement covers, and I want to be straight about that rather than absorb it informally. What you're describing is specific to your situation in a way that doesn't generalize to the offer architecture. Let me offer alternatives: [option 1: decline cleanly], [option 2: defer to a future engagement], [option 3: bespoke add-on with separate scope and pricing]. Which would work for you?"

Adapt the language to your voice. The pattern (acknowledge the request, name the classification, name the action, offer alternatives if declining) is the structure.

### Step 5: Document the request and response

In the customer's record:

> "Scope-creep request received [date]: [verbatim or close paraphrase]. Classified as Category [A/B/C/D]. Response: [summary]. Time impact: [estimated hours]. Logged to v2.x candidate inventory: yes / no."

### Step 6: Tag the time

If the operator spent time on this request — even time spent declining — log the time in the M7.6 audit (during the measurement window) under SCOPE-CREEP, with the customer code and stage tagged.

This includes:
- Time spent reading and classifying the request
- Time spent drafting the response
- Time spent in conversation with the customer about the request
- Time spent doing the work (if Category A or B)

The audit data needs to reflect the true cost of scope creep, including the cost of declining well.

### Step 7: Pattern-check across customers

If this is the third or more scope-creep request you've received from any customer in the past 30 days, run a pattern check:

- Are multiple customers asking for similar things? → Strong v2.x signal; investigate whether the offer architecture should expand
- Are customers asking for different things, all bespoke? → Likely the offer profile is admitting customers who don't fit; revisit C2 customer definition or v2.0 anti-promise list
- Is one customer the source of most scope creep? → Customer-specific issue; consider whether the customer's engagement should be paused or terminated per the C7 Architecture-vs-Pivot Distinction Clause

---

## Common Scope-Creep Categories

Operators often see the same scope-creep patterns repeatedly. Common types:

| Pattern | Typical Category | Notes |
|---------|------------------|-------|
| "Can you also help with [adjacent problem]?" | C or D | Adjacent problem may belong in a different offer (refer out) or in v2.x (log to candidate inventory) |
| "Can we extend the engagement by [N weeks]?" | C or D | Extension is a pricing/scope change; treat as new engagement, not as scope creep |
| "Can you join my call with [external party]?" | D | One-off bespoke request; offer alternative (provide written input, or paid add-on) |
| "Can you redo [deliverable] with a different angle?" | A (if within revision budget) or D | Revision budget is named in v2.0; beyond budget = bespoke |
| "Can you give me extra time / faster turnaround?" | C if pattern is across customers, D if one-off | Pattern across customers = SOP review; one-off = bespoke |

---

## When the Script Should NOT Be Used

The script is for scope-creep requests during active engagement. Do not use the script for:

- **Pre-sale scope discussion** — during pre-sale, the operator is defining what the engagement includes; this is in-scope conversation, not scope creep
- **Operator-initiated scope changes** — if the operator decides to add value beyond v2.0, that is a free-add and is documented as v2.x signal, not as scope creep
- **Stated optional add-ons** — if the offer explicitly lists optional paid add-ons, customer requests for those are sales conversations, not scope-creep scripts

---

## Script Execution Time

Per request: 5-10 minutes (read, classify, respond, document). The Step 7 pattern-check runs separately, weekly or biweekly, and takes 15-20 minutes.

---

*This script is referenced in M7.6 (audit setup, scope-creep tagging), the Daily Completion Checklist (when scope-creep is logged), and the C7 SOP Library (some operators add a Scope-Creep Response SOP to their library).*

Set up a time audit that can explain where the work goes

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and the complete measurement sequence

Configure the three dimensions required by the C7 Time Tracking Setup Worksheet: customer, deliverable and lifecycle stage. The source describes a two-to-three-page worksheet for legacy M7.6, completed once before a measurement window of at least 14 days. Its labels do not replace this lesson's current spreadsheet assignment.

The source estimates 60–90 minutes of setup, a one-day pilot, a minimum 14-day measurement window and subsequent audit analysis. Although its Window Start section appears before the Pilot section, the pilot must occur before the actual window. Do not mistake elapsed calendar days for active labor hours or begin a formal window before testing the setup.

Section 1: document the tool choice

Record the selected tool, a one-to-two-sentence reason, the subscription tier if paid and the monthly cost if applicable. The source references the separate Tool Comparison. A tool is suitable when its actual configuration and reports preserve all three audit dimensions; the worksheet does not require buying a new product.

The source names Toggl's Project and Tags, Harvest's Client, Project and Task, and Clockify's Project and Tags as possible structures. Treat those as source examples and verify the current plan and export behavior before relying on them. Tool features and prices can change. No account setup, subscription purchase or timer activation is performed by this lesson.

Section 2: configure the customer dimension

Give each active customer a stable short code such as C-01 or C-02. The original table supplies five blank rows, C-01 through C-05, with fields for customer name, cohort if applicable and engagement stage at the start of the window. Add the INTERNAL code for work that cannot be attributed to a customer, including operations, planning and business development.

The code-to-name table still contains identifying information. An authored handling rule is to keep that reference separately with appropriate access rather than publishing it with a lesson or placing real names in time-entry descriptions. Codes are pseudonyms, not a guarantee that data cannot be linked back to a person.

Configure the deliverable dimension

Use the actual M7.2 decomposition ID when a block produces a defined deliverable: D-01 through D-XX in the source's notation. For other work, preserve all six categories:

- ADMIN: billing, scheduling and contracts. - FOLLOWUP: post-session work and action items. - COMM: email and asynchronous messages. - REWORK: customer-driven revisions to a prior deliverable. - SCOPE-CREEP: customer-requested work outside the offer. - INTERNAL: work not attributed to a customer.

Do not invent a deliverable merely to avoid using a category. At the same time, do not let a broad administrative category hide the production time of a known deliverable. The purpose is a record that can later be analyzed consistently.

Configure the lifecycle-stage dimension

The template lists seven stage tags: L1-PRESALE, L2-ENROLL, L3-ONBOARD, L4-CORE, L5-MIDCHECK, L6-DEBRIEF and L7-POSTENG. They correspond to presale, enrollment, onboarding, core delivery, a mid-engagement check-in, completion debrief and post-engagement.

Use the actual lifecycle map when it differs from a generic example. Preserve a clear mapping rather than forcing unrelated work into the wrong phase. For INTERNAL work, an authored convention is an explicit not-applicable stage or another approved internal category; do not fabricate a customer lifecycle stage simply to fill the field.

Section 3: practice the complete tagging convention

The source offers two formats: a string such as `C-02 | D-09 | L4-CORE | Sketch review session`, or a tag array `[C-02, D-09, L4-CORE]` with a separate description. Select a convention that survives the tool's export and write it down.

Complete all five practice cases. The following are authored example answers using the source's inputs:

  1. A 60-minute kickoff for C-01, deliverable D-03, onboarding: `C-01 | D-03 | L3-ONBOARD | Kickoff session — 60 minutes`.
  2. A 45-minute asynchronous email exchange for C-02 in core delivery: `C-02 | COMM | L4-CORE | Email exchange — 45 minutes`.
  3. A 90-minute portfolio review for C-03, deliverable D-12, core delivery: `C-03 | D-12 | L4-CORE | Portfolio review — 90 minutes`.
  4. Thirty minutes of billing and scheduling for C-01 in core delivery: `C-01 | ADMIN | L4-CORE | Billing and scheduling — 30 minutes`.
  5. Twenty-five minutes responding to and declining a scope request from C-02: `C-02 | SCOPE-CREEP | [actual stage] | Scope-request response — 25 minutes`.

The fifth prompt does not specify the stage. Look up the actual stage instead of presenting an invented one as source data. These five examples total 250 minutes, or four hours and ten minutes, but they are practice inputs rather than evidence of actual work performed.

Section 4: apply all eight tracking disciplines

Start the timer at the beginning of the activity and stop it at the end. Do not leave one customer's timer running until you begin the next task. Record all three dimensions before saving, and resolve incomplete entries so they can be used in the analysis.

For work shorter than five minutes, the source allows end-of-day batch logging with an honest estimate rather than omission. If you forgot the timer, record a manual estimated entry. An authored data-quality addition is to label estimates distinctly from directly timed entries; recovering missing work does not make its duration measured.

Track INTERNAL work as well as customer work. The audit needs the total-time denominator, not only customer hours. Record time spent declining scope requests and separate rework from initial production. Those activities consume capacity even when they do not create a new promised deliverable.

The companion scope script includes some Category A, already-in-scope work in its scope-handling instructions, while this worksheet defines SCOPE-CREEP as outside-offer work. Preserve that conflict and adopt an explicit convention separating the handling of a scope inquiry from actual in-scope production. Do not silently distort the categories.

Section 5: conduct the daily and weekly reviews

The daily review is estimated at 5–10 minutes. Check all four items: every block has customer, deliverable and stage fields; untagged blocks are resolved; scope-creep and rework are distinguished correctly; and forgotten activities have honest manual entries.

The weekly review is estimated at 20–30 minutes. Check whether per-customer totals make sense, including any legitimate week with no activity; inspect per-deliverable totals; ensure administration, follow-up, communication, rework and scope handling are visible; and record anomalies such as illness or a customer crisis.

A surprising number is a reason to inspect evidence, not to rewrite the record until it looks typical. Preserve the anomaly and distinguish its effect from normal delivery demands. These review estimates are additional active work to plan, not the duration of the 14-day window itself.

Sections 6 and 7: pilot before the formal window

Record the formal start date, an end date at least 14 days later and the codes of customers active during the window. Before that start, run the full-day pilot described in Section 7.

Check all four pilot requirements: the tool captures time accurately; the tagging structure is workable during real activity; reports can separate customer, deliverable and stage; and the data supports per-customer weekly figures, deliverable totals and hidden-cost breakdowns. Record the pilot date and review notes. If any check fails, revise the setup before starting the formal window.

The source warns against excessive granularity that makes tagging itself consume too much time. An authored test is to enter the five practice cases and export them, then confirm that no dimension has been collapsed into an unsearchable note or lost during export. This is a verification exercise, not a new source-mandated software purchase.

Use the result in the bandwidth audit

After setup, complete the measurement window and use the resulting data in the separate Operator Bandwidth Audit Template. This source does not provide that completed audit or an actual dataset. Keep raw entries, the tagging convention, estimated-entry labels and anomaly notes available so a reviewer can understand later calculations.

The authored Hormozi/Acquisition.com connection is to ground delivery effort and capacity in evidence when designing an offer. The authored Brunson/ClickFunnels connection is to keep the fulfillment implied by the marketed offer consistent with what the business can repeatedly deliver. Neither connection converts estimated practice times into measured business performance.

Clickable sources

- Original Time Tracking Setup Worksheet - Time Tracking Tool Comparison - Scope-Creep Recovery Script - The complete source worksheet and its blank tables remain in the appendix. Actual decomposition IDs, lifecycle mapping and the completed bandwidth audit remain dependencies.

Assigned source links

D0444 original source 1

Original tables and embedded resource links
D0444 original Markdown table 1; blank cells and source claims retained
CodeCustomer NameCohort (if applicable)Engagement Stage at Window Start
C-01
C-02
C-03
C-04
C-05
D0444 original Markdown table 2; blank cells and source claims retained
TagMeaning
D-01 through D-XXSpecific deliverable ID from M7.2
ADMINBilling, scheduling, contracts
FOLLOWUPPost-session work, action items
COMMEmail, async messages
REWORKCustomer-driven revisions to a prior deliverable
SCOPE-CREEPCustomer-requested work outside the offer
INTERNALNon-customer time
D0444 original Markdown table 3; blank cells and source claims retained
TagStage
L1-PRESALEStage 1: Pre-Sale
L2-ENROLLStage 2: Enrollment
L3-ONBOARDStage 3: Onboarding
L4-COREStage 4: Core Delivery
L5-MIDCHECKStage 5: Mid-Engagement Check-In
L6-DEBRIEFStage 6: Completion Debrief
L7-POSTENGStage 7: Post-Engagement
Complete native original body, including retained document-part text

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

# C7 Time Tracking Setup Worksheet

**Course:** C7 Offer Architecture
**Module:** M7.6 — Operator Bandwidth Audit (setup)
**Document Type:** Operator-completed worksheet; one-time setup before measurement window
**Length:** 2-3 pages when complete

---

## Purpose

This worksheet configures the operator's time-tracking tool for the M7.6 Bandwidth Audit. The output is a tool-and-tag structure that produces audit-quality data: hours attributable to specific customers, deliverables, and lifecycle stages.

The setup is one-time; the measurement window then runs for at least 14 days. Setup quality determines audit quality. An under-tagged measurement window produces data that cannot be parsed into per-customer per-deliverable per-stage figures.

---

## Section 1: Tool Selection

Reference: `C7-Time-Tracking-Tool-Comparison.md`

**Tool selected:** ___________________________

**Why this tool (1-2 sentences):**

[Operator writes here]

**Subscription tier (if paid):** ___________________________
**Cost per month (if applicable):** ___________________________

---

## Section 2: Tag / Project Structure

The audit requires three independent tag dimensions: **customer**, **deliverable**, and **lifecycle stage**. Most tools support 2-3 dimensions natively (Toggl uses Project + Tags; Harvest uses Client + Project + Task; Clockify uses Project + Tags).

### Customer Dimension

Each active customer gets a unique identifier. Use a short alphanumeric code (e.g., C-01, C-02) rather than a name, both for privacy in the time-tracking tool and for consistency across artifacts.

| Code | Customer Name | Cohort (if applicable) | Engagement Stage at Window Start |
|------|---------------|------------------------|-----------------------------------|
| C-01 | | | |
| C-02 | | | |
| C-03 | | | |
| C-04 | | | |
| C-05 | | | |

**Add an "INTERNAL" code for non-customer-attributable time (operations, planning, business dev).**

### Deliverable Dimension

Each tracked block is tagged with a deliverable ID from the M7.2 Decomposition. If the time block does not produce a specific deliverable, tag with a category (ADMIN, FOLLOWUP, COMM, REWORK, SCOPE-CREEP, INTERNAL).

| Tag | Meaning |
|-----|---------|
| D-01 through D-XX | Specific deliverable ID from M7.2 |
| ADMIN | Billing, scheduling, contracts |
| FOLLOWUP | Post-session work, action items |
| COMM | Email, async messages |
| REWORK | Customer-driven revisions to a prior deliverable |
| SCOPE-CREEP | Customer-requested work outside the offer |
| INTERNAL | Non-customer time |

### Lifecycle Stage Dimension

Each tracked block is tagged with the lifecycle stage from M7.4.

| Tag | Stage |
|-----|-------|
| L1-PRESALE | Stage 1: Pre-Sale |
| L2-ENROLL | Stage 2: Enrollment |
| L3-ONBOARD | Stage 3: Onboarding |
| L4-CORE | Stage 4: Core Delivery |
| L5-MIDCHECK | Stage 5: Mid-Engagement Check-In |
| L6-DEBRIEF | Stage 6: Completion Debrief |
| L7-POSTENG | Stage 7: Post-Engagement |

---

## Section 3: Tagging Convention

State the tag convention you'll use during the measurement window. Most operators use a string like:

> `C-02 | D-09 | L4-CORE | Sketch review session`

Or in tag-array format:

> Tags: `[C-02, D-09, L4-CORE]` — Description: "Sketch review session"

**Your convention:** ___________________________

**Practice 5 examples (write the full tagged entry for each):**

1. A 60-minute kickoff call with Customer C-01 (deliverable D-03 Kickoff Session, Stage 3 Onboarding):
   [Operator writes here]

2. 45 minutes of async email exchange with Customer C-02 (no specific deliverable, Stage 4 Core):
   [Operator writes here]

3. 90 minutes producing Customer C-03's portfolio review (deliverable D-12, Stage 4 Core):
   [Operator writes here]

4. 30 minutes of billing/scheduling for Customer C-01 (administrative, Stage 4 Core):
   [Operator writes here]

5. 25 minutes responding to a scope-creep request from Customer C-02 (declined, but time spent declining):
   [Operator writes here]

---

## Section 4: Tracking Discipline

The audit is only as good as the operator's tracking discipline during the 14-day window. State the disciplines:

- [ ] Start the timer **at the beginning** of every customer-attributable activity, not after.
- [ ] Stop the timer **at the end** of the activity, not at the start of the next one.
- [ ] Tag every entry with all three dimensions (customer, deliverable, stage) before saving. Untagged entries are unusable.
- [ ] For activities < 5 minutes, batch-log at the end of the day with honest estimation rather than not logging.
- [ ] Log internal/non-customer time as well — the audit needs the denominator (total weekly hours), not just the numerator.
- [ ] If the timer is forgotten and the activity is over, log it as a manual entry with honest estimation; do not omit.
- [ ] Tag scope-creep work as scope-creep, even if the operator declined to do most of the work. Time spent declining counts.
- [ ] Tag rework as rework, distinguishing it from initial production.

---

## Section 5: Daily and Weekly Review

The audit produces useful data only if the operator reviews entries daily and weekly:

**Daily review (5-10 min, end of day):**
- [ ] All time blocks tagged with customer + deliverable + stage
- [ ] Untagged blocks resolved
- [ ] Scope-creep and rework correctly distinguished
- [ ] Forgotten activities logged as manual entries

**Weekly review (20-30 min, end of week):**
- [ ] Per-customer totals reasonable (no customer at 0 hours unless absent that week)
- [ ] Per-deliverable totals reasonable
- [ ] Hidden cost categories (admin, followup, comm, rework, scope-creep) visible in data
- [ ] Anomalies noted for the audit (illness, customer crisis, etc.)

---

## Section 6: Window Start

After setup, the measurement window starts. State:

**Window start date:** ___________________________
**Window end date (≥ 14 days later):** ___________________________
**Customers active during window:** [Codes from Section 2]

---

## Section 7: Pre-Window Sanity Check

Before the window starts, run a 1-day "pilot" of the tagging structure. Track for one full day, then review the data. Confirm:

- [ ] The tool captures the time accurately.
- [ ] The tag structure is workable in real time (not so granular that tagging itself eats time).
- [ ] The data parses cleanly into per-customer, per-deliverable, per-stage views.
- [ ] The reporting view supports the audit calculations (per-customer per-week, per-deliverable totals, hidden cost breakdown).

If any check fails, revise the setup before the 14-day window starts.

**Pilot date:** ___________________________
**Pilot review notes:**

[Operator writes here]

---

*This worksheet is one-time setup. After completion, the operator runs the 14-day window and then completes the M7.6 Operator Bandwidth Audit Template using the resulting data.*

*Estimated completion time: 60-90 minutes setup + 1-day pilot + 14-day measurement window + audit analysis.*

Choose a time-tracking tool by audit fit, not a stale price chart

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and source date

Explain every comparison dimension in the supplied C7 Time Tracking Tool Comparison and select a workflow that can preserve customer, deliverable and lifecycle stage throughout a 14-day-or-longer audit. The source describes a three-to-four-page reference for legacy M7.6 and says its prices were checked in April 2026. Preserve that historical claim and the original chart; do not present it as a current quotation.

The main source principle is to choose a tool that fits the operator's work rather than the one with the longest feature list. A subscription is not the audit. The audit still depends on complete entries, meaningful categories, review and usable exports.

Read all eleven comparison rows

The original compares Toggl Track, Harvest and Clockify across eleven dimensions. Its free-plan row states up to five users for Toggl, one seat and two active projects for Harvest, and unlimited users and projects for Clockify. These are historical source claims to verify before selection.

Its entry paid tiers are listed as Toggl Starter at $9 per user per month annually, Harvest at $10.80 per seat annually or $12 monthly, and Clockify Basic at $3.99 annually. Its higher-tier row lists Toggl Premium at $18 annually, Harvest Premium at approximately $14 and Clockify Pro at $7.99. The source's plan names and prices are not all consistent with the vendor pages checked below.

For dimensions, the chart names Project + Tags + Client for Toggl and Clockify, and Client + Project + Task for Harvest. It says all three provide timers and manual entry, mobile apps for iOS and Android, browser extensions, project/client reporting, CSV export and an API. Those rows identify the capabilities to test on the selected plan; they do not establish that every current free plan provides identical reporting depth.

The invoicing row says Toggl has no built-in invoicing, Harvest includes it on paid plans, and Clockify provides it at Pro. The Clockify section later says Standard includes invoicing. Preserve this internal conflict and use the vendor's current feature description to resolve a purchase decision.

Current reference check, separated from the original

On September 11, 2026, Toggl's pricing page displayed annual Starter at $9 and Premium at $16 per user per month, with monthly figures of $12 and $24. It described the free plan as serving a limited number of users. The original $18 Premium figure and exact free-user allowance should not be repeated as current facts without checking the applicable plan.

Harvest's pricing page showed Free with one seat and two projects, including invoicing. Teams started at $9 per seat per month annually, or $11 monthly; Enterprise started at $14 annually or $17.50 monthly. It also described usage-based charges for additional invoices, projects, clients and tasks. The original Pro/Premium naming and prices are therefore historical, and a starting seat price is not necessarily the total bill.

Clockify's pricing page listed Standard at $5.49 per seat per month annually or $6.99 monthly and included invoicing. This supports the source's later Standard statement rather than its Pro-only chart row. Other current tier limits should be checked directly before committing. No subscription is being purchased by this lesson.

Understand the source's Toggl profile

The source favors Toggl for an operator seeking a straightforward timer and tags, using a separate billing system, working with a small team and potentially needing profitability or labor-cost reports later. It proposes Project as customer code and Tags as deliverable plus lifecycle stage.

It considers Free or Starter sufficient for the audit and positions Premium profitability and forecasting as more relevant to the later unit-economics stage. Treat that as a dated workflow recommendation and test the actual plan's report and export behavior. The source's description of a “clean” interface is a preference judgment, not an objective measure of audit quality.

Understand the source's Harvest profile

The source favors Harvest for hourly billing, combined time tracking and invoicing, existing QuickBooks or Xero use, comfort with its interface and a modest number of active projects. It maps Client to customer, Project to lifecycle stage and Task to deliverable.

Its statements about an older interface, fewer than 100 active projects and a practical Pro entry tier are source characterizations, not verified current limits. Check how the chosen configuration handles multiple customers at the same stage and whether the export preserves each dimension independently. The underlying benefit is the ability to cross-reference billing and delivery data; the integration must actually be available and configured before that benefit is claimed.

Understand the source's Clockify profile

The source favors Clockify for budget-sensitive operators, teams with assistants or contractors, tag-based reporting and users comfortable with its interface. It describes the free plan as supporting unlimited users and projects and says audit tagging works there. Verify the applicable current limits before relying on that historical statement.

It identifies Standard as an option when invoicing is required, consistent with the vendor check above. The claim that one interface is less polished than another is subjective. A usable pilot and a complete export are more informative than that label.

Apply all five operator-profile recommendations as a decision exercise

The source proposes Toggl Free for a solo operator with one to five customers and simple billing; Harvest for a solo hourly biller already using QuickBooks or Xero; Clockify Free for a team with assistants, contractors or co-deliverers; either Toggl Free or Clockify Free for a solo fixed-fee cohort offer; and Toggl Starter or Premium for an operator approaching a later stage with profitability and forecasting needs.

These are the source's dated starting points, not five automatic buying instructions. For the actual decision, record your current workflow, required dimensions, export result, present plan limits and total expected cost. If fixed-fee billing makes invoicing-from-time irrelevant, do not pay for that capability solely because a comparison chart includes it.

Preserve the five human responsibilities

The source says a tool cannot supply correct customer/deliverable/stage meaning, decide whether work is out of scope, distinguish revisions from first production, know every activity omitted from the record or identify every abnormal week without operator input.

Its blanket wording about automatic tagging and missed-entry detection is too broad for all current tools: some products offer activity tracking, reminders or automation. Those features can assist the record but do not prove that the semantic category or missing activity is correct. The operator still needs to review classifications, estimates and anomalies rather than treating automation as verified evidence.

Account for switching time and data handling

The source recommends keeping an existing tool if it supports the three independent dimensions, because migration cost can be high relative to a short audit. If switching is necessary, it allows one to two days for setup, followed by the one-day pilot in the setup worksheet and then the 14-day measurement window. Treat those intervals as planning estimates, not measured labor or guaranteed completion times.

The tools are cloud services. The source advises using customer codes rather than names, deliverable IDs rather than confidential deliverable names and descriptions that omit confidential project names. Keep the code-to-name reference separately. Codes remain potentially identifiable through their reference table; they do not make the dataset anonymous or by themselves establish compliance with a confidentiality agreement.

Finally, record the selected tool in Section 1 of the setup worksheet. The source also names RescueTime, Hubstaff and Time Doctor as alternatives, but does not compare them. Apply the same three-dimension and export test rather than claiming those products were reviewed here.

Connect the curriculum themes

The authored Hormozi/Acquisition.com application is to understand delivery effort and capacity before claiming an offer is profitable or easy to fulfill. The authored Brunson/ClickFunnels application is to keep the work implied by the offer aligned with the work the business can deliver. Tool preference cannot substitute for that evidence.

Clickable sources

- Original C7 Time Tracking Tool Comparison - Companion Time Tracking Setup Worksheet - Toggl pricing, Harvest pricing, and Clockify pricing. - The complete original comparison remains in the appendix, including its historical prices and conflicting invoicing statements. Current reference notes do not overwrite that source.

Assigned source links

D0445 original source 1

Original tables and embedded resource links
D0445 original Markdown table 1; blank cells and source claims retained
FeatureToggl TrackHarvestClockify
Free plan existsYes — up to 5 usersYes — 1 seat, 2 active projectsYes — 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 dimensionsProject + Tags + ClientClient + Project + TaskProject + Tags + Client
Timer + manual entryBothBothBoth
Mobile appiOS + AndroidiOS + AndroidiOS + Android
Browser extensionYesYesYes
Invoicing built inNo (Premium adds reporting only)Yes (all paid tiers)Pro tier ($7.99)
Reports: per-project, per-clientYesYesYes
Reports: custom export to CSVYesYesYes
API for custom reportingYesYesYes
Complete native original body, including retained document-part text

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.*

Adapt a technical offer to the buyer's actual working constraints

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and case boundary

Trace Darius's proposed Staff-Level Transition Sprint through all eight modules in the supplied Builder-Operator case. The source gives a secondary Systems orientation and a territory of platform-engineering coaching for senior engineers moving toward staff roles. Treat its interviews, cases, scores and commitments as unverified case-study material, not actual RISER NATION customer evidence or a currently available service.

The timeline lists C1 completion January 30, C2 March 10, C3 April 30, C4 enrollment May 7 and C4 completion June 18, 2026. May 7 to June 18 is six weeks, not the stated six weeks and three days. The April 24 update date also precedes the later events. Preserve these inconsistencies rather than using the document as a verified activity log. Legacy course numbers do not change this lesson's spreadsheet assignment.

Begin with the C3 evidence and repositioning

Darius's three original candidates are an intensive six-week Staff-Level Sprint, a twelve-week Platform Engineering Cohort and a self-paced Staff Engineer Playbook. Four of eight interviewed engineers reportedly identify employer restrictions on paid coaching during work hours alongside fragmented evening availability, on-call rotations and family schedules.

The case describes a mentor-guided change to an eight-week, asynchronous-first design with two evening cohort calls per week. It keeps the mechanism while changing delivery assumptions. The mechanism has four stages: audit current scope, identify staff-level gaps, produce visibility artifacts and prepare promotion conversations.

At entry, the source reports 247 Trigger Bank entries with 116 Primary-relevant, nine competitors comprising three staff-engineer coaches, four engineering-management consultants and two paid newsletter/mentor offers, prices from $1,200 group cohorts to $7,500 three-month one-to-one services, and eight interviews. These are source inputs; they are not independently checked market data. Compare durations and delivery models before treating the full price span as a single comparable band.

M4.1: distinguish a mechanism from the offer

The distinction memo takes a reported seventy minutes. Its mechanism sentence connects audit, gaps, visibility and conversations to the artifacts and discussion points promotion committees evaluate. That explains an intended process; it does not demonstrate control over a committee's decision.

The initial offer sentence gives an eight-week program, $1,800 and cohort plus asynchronous review but lacks precise buyer scope and guarantee terms. The revised sentence identifies Senior 2/E5-equivalent engineers at companies with explicit staff ladders, a fifteen-person cohort, a fourteen-day refund and an extension connected to a promotion conversation within ninety days. Those are proposed case terms, not promises made by this lesson.

Keep all seven component ratings: the named deliverable, price and delivery structure are Partial; buyer and specific promise are Strong; anti-promise and guarantee are None at this stage. The source cites six of eight interviews for buyer identification and TB-031, TB-088 and TB-145 for the “stuck at senior” language. Its 9/10 PASS is a reported narrative result, not a verified reviewer record.

M4.2: replace operator jargon with buyer evidence

The case contrasts systems-oriented language about career architecture with the buyer's desire for recognition after doing staff-level work. It references TB-031, TB-088, TB-145 and Interview 3, including an eighteen-month stalled-promotion account. Those four references are named, but the complete underlying records are not supplied.

Dream Outcome is rated Strong. Perceived Likelihood is Moderate: five cases, three anonymized and two reportedly permissioned, all matching the target profile, but no completed full Sprint. The source also identifies objections TB-093 and TB-167 about differentiation and applicability across employers. Similar cases can support relevance without proving the results of a new complete program.

Time Delay is Moderate. The first result is a scope audit by the end of Week 1, while the larger goal is described as six to nine months. The component estimates—one to two months for the Sprint, three to six for promotion-cycle alignment and one for committee review—actually add up to five to nine months. Preserve the difference and distinguish a first artifact from the eventual promotion outcome.

Effort & Sacrifice is Strong in the case, based on three to four buyer hours per week and approximately zero additional tool expenditure. These are proposed assumptions, not measured guarantees. The synthesis identifies effort as strongest, likelihood as weakest and promotion-cycle timing as a structural constraint. The case reports another 9/10 PASS.

M4.3: retain all seven deliverables and three variants

The seven deliverables are the Current-Scope Audit Worksheet, Staff-Level Gap Identification Framework, three visibility-artifact template types—design document, retrospective and RFC—the Promotion Conversation Script Library, Compensation Negotiation Reference, asynchronous cohort Slack knowledge base and sixteen live calls across eight weeks.

Variant A is the eight-week hybrid Staff-Level Transition Sprint with all seven deliverables and a $1,500–$2,200 placeholder band. It targets the identified scheduling constraint for Senior 2/E5 engineers at companies with staff ladders.

Variant B is a twelve-week one-to-one Staff-Level Mentorship using deliverables one through five plus twelve private calls, with a $5,000–$7,500 band. It targets buyers seeking direct attention, privacy or a higher-touch engagement.

Variant C is a four-to-six-week self-paced Staff Engineer Playbook using deliverables one, two, three and five with Loom walkthroughs, priced at $397. It targets an exploratory or lower-commitment buyer.

The case reports four-of-four axis divergence and a five-test naming PASS. Under the separate variant worksheet's duration bands, however, A's eight weeks and part of C's four-to-six-week range are not wholly distinct categories. The full name-test results are absent. Keep the reported PASS separate from a fresh structural verification.

M4.4: check every pricing calculation

Variant A settles at $1,800 paid in full or two $1,000 installments. The installment total is $2,000—$200, or about 11.1%, above the pay-in-full amount. Its estimated eight operator hours imply $225 of revenue per delivery hour, not net profit after all costs.

The source describes raising an initial $1,500 price after a mentor argues that engineers anchor on salaries of $150,000 or more. At exactly $150,000, $1,800 is 1.2%, not less than 1% as claimed. Salary comparisons also do not establish willingness to buy. Preserve the source's rationale while correcting the arithmetic and retaining buyer-evidence uncertainty.

Variant B's final anchor is $6,000 and Variant C remains $397. The case later notes that no buyer in the interview pool had expressed willingness at B's band, so its price remains a hypothesis to test rather than validated demand.

M4.5: keep all exclusions and non-claims explicit

The first exclusion is engineers at companies without a staff-engineer ladder, because the mechanism assumes that progression structure. Its suggested adjacent-operator referral is a placeholder, not an identified available referral.

The second exclusion has a conflict: its heading excludes people prohibited from paid coaching during work hours, but its explanation says evening or weekend participation can work and distinguishes a ban on any external coaching. Clarify the actual restriction before applying the boundary. Do not imply covert participation or assume that an evening schedule satisfies a particular employer's policy.

The third exclusion concerns engineers in their first twelve months at Senior level, while the suggested return point is month eighteen or later. The intervening eligibility period is not resolved by the source.

The three non-claims are no promotion within ninety days, no placement with or override of promotion committees, and no substitute for internal advocacy. The source labels the remaining scope boundaries “standard” without supplying them. Its signed Integrity Statement is a narrative claim; no signature record is provided.

M4.6: distinguish a conversation guarantee from a promotion guarantee

The proposed hybrid includes a fourteen-day no-questions-asked refund from the Sprint start, processed within seven business days. The outcome component concerns a first scheduled promotion conversation with a manager or skip-level within ninety days, not an actual promotion.

Its conditions are completion of four visibility-artifact deliverables, attendance at at least twelve of sixteen calls, and submission of the scope audit by Week 2. Twelve of sixteen is 75%. The source's “four” artifact condition does not clearly reconcile with the three named visibility-template types or the seven-item inventory; obtain the actual definitions rather than silently choosing one.

The proposed remedy extends Slack access and monthly office hours until a conversation is scheduled, capped at six months after Sprint completion. The modeled activation rate is 15%, with four extra hours at $225, or $900 per activation. That gives $135 per buyer, 7.5% of the $1,800 price. These are assumptions; the model does not include every possible refund or operational cost. Its Honesty Clause and PASS are not independently verified approvals.

M4.7: turn the feature list into understandable copy

The case says Darius spends three hours rewriting Sections 1–3, replacing abstract promotion-system language with buyer-language examples about doing staff-level work without the title or compensation. It reports eighteen verbatim Trigger Bank entries, but does not provide the full landing page or provenance record.

Maya's feedback asks him to replace two of three uses of “mechanism” with more natural wording. Priya affirms the specificity of the employer-policy anti-promise. Darius incorporates the wording change and retains the exclusion. Keep that feedback distinct from independent buyer validation.

The narrative reports 8/10 initially and 9/10 after a CTA revision concerning the qualification form's question count. The actual count and questions are missing. Cooling is said to have occurred, but this case gives no duration. Do not invent either detail.

M4.8 and the C5 handoff

The source reports a Sonnet pre-screen and Opus PASS, with a note that the $6,000 one-to-one option lacks buyer-pool price evidence. A note is described as nonblocking in this proposed workflow; that does not make the price validated.

The handoff names a fifteen-seat first cohort beginning July 30, 2026, at $1,800; five prepared objection responses; an employer-policy-conscious Welcome Kit; Friday check-ins with Maya; and a later retest of Variant B before activation. Only one objection topic—concern about an employer finding out—is named. The remaining responses, kit and actual commitments are not supplied, so do not fabricate them.

Apply the curriculum themes

The authored Brunson/ClickFunnels connection is continuity from the buyer's language through mechanism explanation, proof, scope and next step. The authored Hormozi/Acquisition.com connection is to examine outcome, confidence, time and effort while preserving real delivery and risk limits. The case's changing format illustrates an application; it does not establish an actual successful promotion service.

For practice, separate every proposed term from every evidenced fact, then correct the timeline, salary percentage and installment total. Finally, name the unresolved artifact and employer-policy definitions that would need clarification before a real offer could be represented accurately.

Clickable sources

- Original Darius Builder-Operator case - Three-Variant Worksheet - Maya companion case - Priya companion case - The complete original case remains in the source appendix. Missing interviews, proofs, reviewer outputs, complete copy and operational artifacts remain explicit dependencies.

Assigned source links

D0446 original source 1

Complete native original body, including retained document-part text

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*

Diagnose feature stuffing before adding more to an offer

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and evidence boundary

Use the supplied Feature Stuffing Trap case to trace how a mistaken diagnosis of buyer confidence can lead to excessive deliverables, soft exclusions and an expensive guarantee. The source calls James an anonymized composite of a Service-Operator with a secondary Product orientation, working on product-led growth for early-stage SaaS founders. Treat the story as an instructional composite, not a verified customer testimonial or a documented prediction of business results.

The source reports that roughly 15–20% of C4 students show a tendency and about 5% reach a later module with the full pattern. It supplies no underlying cohort dataset. Preserve those figures as unverified source claims. Likewise, its claims about low conversion, refunds and burnout explain the proposed risk; they do not prove those outcomes will follow every larger offer.

The legacy M4.3, M4.6, M4.7 and M4.8 labels identify where the source expects the problem to surface: expanding deliverable counts, stacked guarantees, overloaded copy and a final validator flag. Follow the current spreadsheet assignment for this lesson.

Establish the starting evidence

James begins with a four-pillar PLG Foundation Method, 213 Trigger Bank entries of which 67 are Primary-relevant, seven customer interviews and observed prices from $1,500 to $5,000. The narrative says a mentor allowed progress despite the interview count being below its stated minimum of eight.

The source calls 67 Primary-relevant entries under-dense and compares them with Maya's 102 and Darius's 116. Later it prescribes 200 Primary-relevant entries, which would also exclude those two apparently successful examples. Do not silently convert total entries into relevant entries or treat these conflicting thresholds as one validated rule. Evidence relevance and quality must remain visible alongside counts.

M4.1: citation presence is not citation strength

The source reports an 8/10 PASS for James's distinction memo. Its component inventory labels the specific promise Strong but supports that rating with a generic reference to Trigger Bank demand. The narrative says the rubric checked that a citation existed rather than whether it supported the conclusion.

The teaching point is to inspect the relationship between a claim and its evidence. A source label without an identifiable entry cannot be checked adequately. A passing score does not repair that weakness. The complete underlying Trigger Bank and rubric output are not included in this case.

M4.2: identify the actual weak variable

James rates Dream Outcome and Perceived Likelihood Strong, with Time Delay and Effort & Sacrifice Moderate. He targets Time Delay as the weakest variable. The case's diagnosis instead places the weakness in Perceived Likelihood: two named cases, thin buyer-facing evidence and confidence in the mechanism being mistaken for a buyer's reason to believe.

The source says its Honest Weakness Assessment dimension had two points and produced a Moderate flag without blocking progression. Preserve that account without presenting the reviewer as deployed or infallible. An authored review asks what each case demonstrates, how closely it matches the buyer and what remains unknown; a case count alone is not a universal confidence score.

M4.3: follow the complete expansion of the offer

Variant A, PLG Mastery Program, becomes an eight-week cohort with fourteen deliverables: seven original mechanism components and seven additions. The original seven are only summarized as an audit, framework, templates and related work; their complete names are not supplied. Do not invent them as recovered source content.

The seven named additions are a PLG metrics dashboard template, three onboarding-sequence templates, an email-automation workbook, a pricing-page audit checklist, four bonus office-hour sessions, lifetime Slack-community access and future updates. The last two are ongoing commitments, not costless labels.

Variant B, PLG Mastery Premium, adds one-to-one calls and reaches sixteen deliverables. Variant C, PLG Mastery Lite, still contains nine. The source reports flags for A and B, although C also exceeds its later greater-than-eight threshold. That narrative omission does not establish that C is compliant.

The mentor identifies deliverable density as an attempted substitute for likelihood evidence. A paid Stage 3 alumni reviewer describes feeling burdened by the bonus list; this is a paraphrased anecdote in a composite, not measured buyer research. James trims A from fourteen to eleven, which still exceeds the source's threshold.

M4.5: identify the soft exclusions

James's initial anti-promise is structurally complete with three exclusions, two non-claims and a scope boundary, but the exclusions appeal to buyers' self-image. They reject people unwilling to invest in growth, looking for a magic bullet or unwilling to work. Almost any intended buyer can regard themselves as the opposite, so the exclusions do little to identify a concrete mismatch.

The source calls this a failed Flattery-Test. The mentor connects the soft exclusions with feature stuffing: both avoid confronting weak confidence evidence. Do not generalize that all broad offers or all emotional motives fit this story; use the pattern as a diagnostic question.

Separate the proposed correction from what actually changed

The mentor proposes pausing for two weeks, returning to C3, extending the Trigger Bank beyond 250 entries and adding three interviews. James returns with 261 total entries and three more interviews, two with founders who had previously declined outreach. Their explanations supply eighteen new objection entries in the narrative.

The earlier mentor statement suggests this could produce Strong–Strong–Moderate–Moderate ratings, but the actual corrected assessment still rates Perceived Likelihood Weak. Additional interviews did not create more than the two named cases or establish a strong buyer-similar match. Preserve this distinction: more records can improve understanding without automatically proving outcomes.

Also, 261 total entries does not prove that the later requirement of 200 Primary-relevant entries has been met. The relevant subtotal after correction is not supplied.

Review every corrected offer decision

The revised Variant A returns to the original seven deliverables, removes all seven bonuses and remains an eight-week cohort. Its anchor becomes $1,800 instead of the earlier planned $2,400—a $600 or 25% reduction. The case does not provide a complete cost model proving that either price is sustainable.

The three revised exclusions are founders below $500,000 ARR, founders without product-market fit and buyers seeking paid-acquisition PLG when the mechanism concerns organic PLG. The price rationale says $1,800 exceeds 3% of monthly revenue at $500,000 ARR; at exactly that ARR, monthly revenue is about $41,667 and the price is 4.32%. This calculation does not independently validate the eligibility cutoff.

The corrected guarantee contains a refund and a conditional outcome extension. The full trigger conditions, refund window and extension cap are not provided, so do not invent a ready-to-use guarantee. The landing page reportedly includes sixteen verbatim Trigger Bank entries and carries the anti-promise unchanged; the complete page and those sixteen original entries are not supplied here.

The source reports Sonnet and Opus PASS outcomes with a note that Variant B's premium positioning lacks buyer-pool evidence. Those are narrative results, not verified operational review records. A guarantee may alter the buyer's risk allocation; it does not transform weak outcome evidence into strong evidence.

Apply all five upstream checks

First, inspect the relevance of the Trigger Bank. Preserve the source's proposed 200-Primary-entry threshold and its conflict with the case comparisons rather than presenting it as established research.

Second, inspect interview coverage. The source proposes a minimum of eight and associates fewer interviews with sparse objection language. Interview count alone cannot establish representative sampling or useful evidence.

Third, question an all-four-Strong Value Equation assessment. The source asks mentors to review such a result regardless of the score. Its blanket claim that two or three cases necessarily mean misdiagnosis is too broad: case relevance, quality and depth also matter, and the companion Priya case itself treats three deep cases differently.

Fourth, follow up on decomposition flags. This case says more than eight deliverables triggers a warning and mentor escalation, not an automatic failure. Other source documents use a hard maximum; the policy conflict must be resolved for actual implementation.

Fifth, examine anti-promises when feature stuffing appears, and inspect deliverable burden when exclusions are only flattering language. The association is a proposed diagnostic pattern, not a proven universal cause.

Preserve all six learner actions without overstating them

The source tells a learner with fewer than 200 Primary-relevant entries to address that gap before M4.2, and a learner with fewer than eight interviews to add interviews, especially with people who did not engage previously. Keep those as source workflow rules, with the threshold conflicts above. This lesson does not contact anyone.

It asks learners to question universal Strong ratings, defend each deliverable beyond the seventh with a specific purpose, rewrite flattering exclusions and simplify guarantees with three or more components. Its claim that buyers can hold a maximum of two guarantee components is not supported by evidence in this document. The practical authored test is clarity, relevance and delivery cost, not a claimed universal cognitive limit.

Do not remove a useful deliverable merely because a bonus count sounds large. Ask what buyer obstacle it addresses, whether another component already does that work and what the buyer and operator must do to obtain its benefit. Fix the actual weakness rather than automatically adding or subtracting items.

Attribution and curriculum themes

The source attributes related language to Hormozi in 2021, Brunson in 2015 and Hopkins in 1923, but supplies no precise passages establishing those terms or origins. Preserve the attribution as a source claim, not a verified quotation or historical finding.

The authored Hormozi/Acquisition.com connection is to align relevant value components, likelihood evidence, time and effort. The authored Brunson/ClickFunnels connection is a coherent offer whose story, proof and next step agree. Neither connection establishes that all bonuses are harmful or that a longer offer necessarily fails.

Clickable sources

- Original Feature Stuffing Trap composite case - Darius companion case - Maya companion case - Priya companion case - The entire original case remains in the appendix. Missing evidence datasets, reviewer outputs, exact guarantees and complete campaign artifacts remain explicit gaps.

Assigned source links

D0447 original source 1

Complete native original body, including retained document-part text

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*

Build a cohort offer while keeping proof, promises and timing honest

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and case boundary

Trace Maya's Portfolio-to-Licensing Sprint through all eight modules of the supplied Teacher-Operator case. The source gives her a secondary Service orientation and a territory of helping experienced freelance illustrators develop licensing income. Its interviews, results, signatures, scores and service commitments are unverified narrative material. They are not testimonials or income promises made by RISER NATION.

The timeline lists C1 completion February 14, C2 March 29, C3 May 14, C4 enrollment May 21 and completion June 25, 2026. The final interval is five weeks, not the stated five weeks and one day. The April 24 update date predates later case events. Retain those discrepancies and follow the current spreadsheet assignment rather than the legacy module numbering.

Carry forward all the C3 inputs

The proposed mechanism has four pillars: Portfolio Audit for Licensing Fit, Targeted Buyer Research, Outreach Sequence Construction and a Licensing Conversation Framework. Its audience is illustrators with five to ten years of experience and $3,000–$8,000 monthly commission or editorial revenue, seeking income less dependent on repeated project work.

The source states an intended outcome of at least three direct buyer conversations within ninety days and a first licensing deal in six to nine months. Those are case assumptions, not demonstrated or guaranteed outcomes. It reports 216 Trigger Bank entries with 102 Primary-relevant, seven competitors, a gap for an intensive four-week cohort in the $1,500–$3,000 band, observed prices from $497 to $4,800, and ten interviews with the “stuck between” theme in seven.

Keep total and Primary-relevant counts separate. The companion failure case's later 200-Primary-entry rule conflicts with this case being called strong at 102. The competitor gap and interview conclusions also require actual underlying records before being presented as verified research.

M4.1: move from a mechanism description to an offer

The reported ninety-minute distinction memo includes three offer-sentence rewrites. The mechanism explains how auditing, research and outreach are intended to turn portfolio assets into targeted conversations. The first offer sentence merely repeats that mechanism and lacks a defined exchange.

The final sentence identifies a four-week cohort for illustrators with five or more years of experience, $2,400, a fourteen-day refund plus an extension tied to three conversations by day sixty, and a twelve-person capacity. Those are proposed terms to reconcile later, not services activated here.

Keep all seven inventory ratings: named deliverable, price and delivery structure Partial; buyer and specific promise Strong; anti-promise and guarantee None at this stage. The source cites TB-024, TB-067 and TB-119, buyer identification in seven of ten interviews and cohort preference in six. Its rubric reports Vocabulary Divergence 3/3, Specific Difference Clarity 2/3, Inventory Honesty 2/2 and Mechanism Consistency 2/2, totaling 9/10. These are narrative scoring claims.

M4.2: teach all four value considerations

The worksheet reportedly takes 110 minutes. Dream Outcome is Strong: the buyer imagines more choice over drawing time, less dependence on continual pitching and revenue from earlier work. The source cites TB-024, TB-067, TB-119 and Interview 4, including Sarah K.'s stated aspiration. An aspiration is not earnings evidence.

Perceived Likelihood is Weak. The case gives four studies, three anonymous and one reportedly permissioned, no completed full Sprint and three of four cases matching the target buyer. Objections TB-088 and TB-141 concern whether this is another licensing-income course and whether success depends on an existing brand. The complete underlying case records and objection entries are not included.

Time Delay is Moderate. A portfolio audit is the first result by Week 1. The larger outcome is modeled at nine months, with a combined three-month Sprint/outreach phase and six months for a deal to close. The Sprint itself is four weeks; do not describe the whole three-month phase as its duration. The source calls procurement cycles of sixty to ninety days irreducible, but supplies no evidence establishing that as a universal market rule. It proposes moving outreach launch from Week 4 to Week 3.

Effort & Sacrifice is Moderate: approximately five buyer hours per week, a moderate learning curve and about $200 in tools. Templates, a research starter list and peer accountability reduce effort. Done-for-you outreach is deliberately excluded because performing outreach is part of the proposed learning mechanism. These are source assumptions rather than verified current tool prices or measured learner effort.

The synthesis names Dream Outcome strongest, likelihood weakest and procurement timing structurally constrained. It proposes a guarantee and honest proof presentation, but a guarantee does not create missing outcome evidence. The reported rubric is Buyer Vocabulary 2/2, Citation Density 3/3, Honest Weakness 2/2 and Synthesis 2/3, totaling 9/10.

M4.3: preserve the eight deliverables and three variants

The eight deliverables are the Portfolio Audit Worksheet, Buyer Research Starter Pack, Outreach Sequence Builder, Licensing Conversation Framework, Pricing Calculator, Contract Term Reference Guide, four asynchronous reviews and eight live cohort calls.

Variant A is a four-week cohort using all eight items, a $2,000–$3,000 placeholder band and the five-to-ten-year, $3,000–$8,000 monthly buyer profile. It emphasizes faster first results, with cohort dependency and less customization than one-to-one delivery.

Variant B is a six-week one-to-one Partnership using items one through six plus six private calls, priced provisionally at $4,500–$6,000. It targets buyers preferring direct attention and a higher revenue baseline of $8,000 or more, at higher operator hours and lower volume.

Variant C is a six-to-eight-week self-paced Playbook using items one, two, three, five and six plus Loom walkthroughs, at $397–$497. It targets buyers wanting resources without direct interaction or a smaller commitment. The source's claims of lower per-buyer margin and little proof generation are characterizations, not universal consequences of self-paced delivery.

The source claims all four axes differ and all names pass five tests. Under the companion worksheet's broad duration bands, B and C overlap; their deliverable-density categories may also overlap. Preserve the reported PASS without treating it as a new independent verification. The actual naming-test records are absent. A forty-eight-hour cooling interval is explicitly reported before revision.

M4.4: keep pricing and cost assumptions visible

Variant A's final price is $2,400 paid in full or two $1,300 payments, at enrollment and Week 2. The installment total is $2,600, $200 or about 8.33% above pay-in-full. The case estimates twelve operator hours at a $200 hourly target, producing a $2,400 revenue floor; it does not provide a full profit calculation including every cost.

The Teacher-Operator adjustment compares cohort engagements with cohort comparables rather than Maya's earlier $297 self-paced workshops. The source places $2,400 within a $1,500–$3,000 cohort band. Variant B becomes $5,500, with four of seven competitors reportedly offering one-to-one services in the $4,000–$6,000 range; C becomes $497. Those market observations and the stated spot-check PASS are not independently verified here.

M4.5: retain every exclusion, non-claim and scope boundary

The anti-promise reportedly takes eighty minutes and a forty-eight-hour pause before revision. Its opening explains that the offer deliberately serves a defined segment rather than everyone. Its assertion that the industry has a poor track record of serving everyone is an unverified source generalization.

The first exclusion is illustrators earning under $3,000 monthly from commissions/editorial work, with the $497 Playbook suggested as an alternative. At exactly $3,000 monthly income, $2,400 is 80%, not merely a useful 25% affordability threshold. The source's “over 25%” statement is a loose lower bound; it does not establish affordability or the suitability of the alternative.

The second excludes illustrators with less than two years of professional work and suggests another twelve to eighteen months of portfolio development. That minimum conflicts with the offer's five-plus-year target unless the intended eligibility relationship is clarified. The third excludes buyers wanting children's-book licensing only and refers to an unnamed adjacent specialist. Do not invent that referral.

The three non-claims are no licensing income within thirty days, no $50,000-plus first-year licensing revenue, and no direct placement with buyers. The accompanying $5,000–$25,000 “realistic” first-year range is also unsupported by evidence in this document and must not be presented as a typical earnings expectation.

The scope includes teaching the audit, supplying research starter packs, reviewing outreach drafts asynchronously and running cohort calls. It excludes writing the buyer's outreach, doing their research or joining their licensing conversations. The signed integrity commitment, Flattery-Test PASS and 9/10 spot check are reported case events, not supplied approval records.

M4.6: examine the full hybrid guarantee and its uncapped cost

The refund component is fourteen days from cohort start, no questions asked, requested by email and processed within seven business days. The outcome component concerns three direct buyer conversations by day sixty, with continued Slack access and asynchronous review until that threshold is reached.

Its conditions are completing four Sprint deliverables, attending at least seven of eight calls and sending at least five outreach pieces weekly from Week 2 onward. Seven of eight is 87.5%. The “four deliverables” condition does not clearly reconcile with the eight-item inventory. The listed exclusions repeat failure to complete the audit, meet call attendance or maintain outreach volume. Actual definitions and terms must be reconciled before use.

The extension has no cap while the buyer maintains the weekly outreach activity. Yet the cost model assumes only six extra hours over a ninety-day extension at $200 per hour: $1,200 per activation. At an assumed 20% activation rate and twelve buyers, it calculates $2,880 per cohort, or $240 per buyer—10% of the $2,400 price.

The arithmetic is consistent with those assumptions, but a ninety-day estimate does not bound an uncapped obligation. The source's sustainability verdict, Honesty Clause, 9/10 score and cooling claim do not resolve that exposure. This lesson preserves the example without offering its guarantee to learners or customers.

M4.7: teach every page section and the revision record

The source reports two writing blocks of ninety and sixty minutes plus thirty minutes for provenance: 180 minutes total. Its seven page sections are Problem, Agitation, Solution-and-Mechanism, Proof, Offer, Anti-Promise-and-Guarantee and CTA.

Problem is listed at 340 words, using two Trigger Bank entries about unstable project revenue and an unused portfolio's potential. Agitation is 220 words with one entry about the future cost of continued dependence; treat that as a rhetorical scenario rather than a guaranteed future. Solution-and-Mechanism is 420 words with three entries and all four pillars, explicitly distinguishing the method from brand building, portfolio improvement and an agent service.

Proof is 310 words with two entries and an admission of four cases rather than twenty, alongside six years of claimed market experience. Offer is 450 words with two entries, all eight deliverables, eight calls in four weeks, $2,400 or two $1,300 payments and twelve seats. Anti-Promise-and-Guarantee is 370 words with three entries, carrying all three exclusions, all three non-claims, scope and guarantee without softening. CTA is 120 words with two entries, a start date, closing rule, four-question qualification form, Welcome Kit within twenty-four hours and contact email.

The entry counts total fifteen. The listed section word counts total 2,230. Reducing Proof from 310 to 270 produces 2,190, not the 2,030 total claimed in the later readiness document. Keep the discrepancy visible rather than silently altering the original page counts.

The CTA initially names a June 24 start and June 17 close, or earlier if twelve seats fill. Those dates precede the June 25 completion signature and conflict with the July 22 handoff date. A real campaign would need one consistent schedule; none of those dates is being activated here.

After a reported forty-eight-hour cooling period and Friday peer-review post, Priya commits Saturday and responds Monday; Darius responds Tuesday. Both ask for less apologetic proof language; Darius flags jargon; Priya suggests moving the capacity statement earlier. The revision shortens Proof to 270 words, keeps one use of “mechanism” while simplifying two sentences, and moves capacity to the second offer paragraph.

The rubric reports Sections 2/2, Verbatim Usage 3/3, Integrity 2/2, Offer Concreteness 1/2 and CTA Specificity 0/1, totaling 8/10. The source notes missing delivery timing and an email-response interval. Adding a forty-eight-hour weekday response statement yields a reported 9/10. The full page, fifteen-entry provenance log, four form questions and actual response service are not supplied or verified.

M4.8: retain all nine readiness sections and four stop criteria

The readiness document reportedly takes ninety minutes plus thirty for a checklist. Section 1 is a 130-word summary of the buyer, $2,400 price, four-week cadence, strongest and weakest value considerations, guarantee, fifteen entries and two reviews. Section 2 repeats the four-pillar mechanism with two sentences on its commercial form. Section 3 details the buyer, eight calls, four reviews, eight deliverables and both payment options. Section 4 states the value conclusions; Section 5 preserves anti-promise and guarantee terms unchanged.

Section 6 references the landing-page files and provenance, including the conflicting 2,030-word total. Section 7 lists four weaknesses in 260 words: four-case proof, no completed first cohort, untested alternatives and an organic-traffic gap. Section 8 uses 160 words for four questions: the outreach sequence producing enrollment, search/AI discovery for licensing-transition queries, minimum enrollment sequence and qualification-form performance on the first five prospects. These are questions, not established results or ranking promises. Section 9 contains the reported June 25 signature.

The checklist names four numerical triggers: fewer than four cohort buyers sends the learner back to pricing; refunds above 30% to the anti-promise; outreach replies below 8% to the outreach approach; and completion below 70% to deliverable density. The source says four checklist categories are complete but does not name those categories here. Treat its thresholds as proposed diagnostic routes, not proven causal findings.

Sonnet and Opus PASS outcomes are reported, with a note that B and C are documented rather than active. The handoff then gives a twelve-seat cohort starting July 22 at $2,400, four prepared objection responses, a Welcome Kit consisting of Loom, a one-page preparation document, Slack invitation and calendar invitation, Friday check-ins with Priya and possible later activation of B/C. The actual responses, media, invitations and commitments are absent.

Apply the curriculum themes and practice

The authored Brunson/ClickFunnels connection is continuity across buyer language, story, proof, offer and next step. The authored Hormozi/Acquisition.com connection is honest analysis of desired outcome, likelihood, delay, effort and delivery risk. Neither supports unsupported income expectations or a guarantee whose cost is treated as capped when its terms are not.

For practice, reconcile the dates, word totals, eligibility statements and guarantee conditions on paper. Identify what evidence is missing and who would need to resolve each issue before an actual offer could be represented consistently. Do not invent corrected terms as though Maya had approved them.

Clickable sources

- Original Maya Teacher-Operator case - Three-Variant Worksheet - Feature Stuffing Trap case - Darius case and Priya case. - The complete original case remains in the appendix. Missing proof, campaign assets, media and actual review records remain explicit dependencies.

Assigned source links

D0448 original source 1

Complete native original body, including retained document-part text

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*

Design a service offer without contradicting its exit terms

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and case boundary

Trace Priya's CEO-Support Track through all eight modules in the supplied Service-Operator case, including the tension between a claimed six-month minimum and flexible termination. The source gives her a secondary Systems orientation and a territory of fractional CFO services for venture-backed B2B SaaS founders. Its cases, interviews, scores, signatures and commitments are unverified narrative material, not actual customer evidence or a service offered by this lesson.

The dates are C1 completion February 21, C2 March 30, C3 May 8, C4 enrollment May 15 and completion June 26, 2026—a six-week interval. The April 24 update date precedes the later events, so the source cannot be treated as a verified contemporaneous activity log. Its legacy numbering does not replace this lesson's current spreadsheet assignment.

Carry the buyer evidence into the offer

Priya originally considers a twelve-week Series B Readiness Track, Quarterly CFO Reviews and a traditional Fractional CFO Retainer. Six of nine interviewed founders reportedly prefer ongoing CFO support to a discrete engagement framed around a funding event they cannot control.

The case retains four mechanism pillars—cap-table clarity, a metric system, a board narrative and a diligence-readiness backbone—but changes the headline to CEO support with fundraising readiness as a byproduct. At entry it reports 219 Trigger Bank entries with 124 Primary-relevant, six competitors comprising four CFO firms and two paid newsletter/advisory offers, and prices from $4,500 monthly to $25,000 for a single event. Those different billing units are not directly comparable without normalizing scope and duration.

M4.1: turn the mechanism into a bounded exchange

The reported ninety-five-minute distinction memo describes a sequence intended to make financial conversations anticipatory rather than reactive. Its offer sentence identifies Series A founders at $3–15 million ARR, a six-month engagement at $7,500 per month, a ninety-day mutual-fit window and a commitment to delivery cadence.

Preserve all seven component ratings: named deliverable, price and delivery structure are Partial; buyer and specific promise are Strong; anti-promise and guarantee are None pending later work. The source references TB-052, TB-098 and TB-176, a $4,500–$10,000 monthly comparison band, monthly deep sessions, biweekly check-ins and asynchronous Slack support. Its 8/10 PASS is reported rather than independently verified.

M4.2: examine all four value considerations

Dream Outcome is Strong in the case: the buyer wants to enter board meetings prepared and have readiness emerge from ongoing operations rather than a fundraising fire drill. The source attributes that framing to TB-098; the complete entry is not provided here.

Perceived Likelihood is labeled Strong-Moderate, supported by three deep cases with more than two years of engagement, reportedly referenceable board members, outcome data, four specific pillars and three-of-three buyer similarity. Strong-Moderate is not one of the usual three labels used elsewhere. Also, the companion failure case treats two or three named cases as insufficient for Strong. Preserve that difference: depth and relevance matter, and a simple case-count rule does not reconcile these accounts.

Time Delay is rated Strong, with a first cap-table deliverable at Month 1 and a larger operating change over six to twelve months. The source simultaneously calls that delay structurally fixed. Treat Strong as the case's qualitative assessment, not proof that every buyer will regard the timing favorably.

Effort & Sacrifice is Moderate, based on about six founder hours per month—one deep session, two check-ins and asynchronous participation—and a $7,500 monthly commitment. The synthesis names Time Delay strongest and effort/sacrifice weakest, proposing a mutual-fit window to reduce commitment risk. The source reports 9/10; it supplies no actual completed scoring record.

M4.3: distinguish a shared structure from unlimited customization

The narrative says Priya initially resists decomposing a service because every founder differs. Its proposed solution is a shared structure within which bounded customization can occur. Preserve all six deliverables: a Month 1 cap-table audit; metric-system implementation in Months 1–2; a board-narrative framework refreshed quarterly; ongoing diligence documentation; ninety-minute monthly deep sessions throughout six months; and thirty-minute biweekly check-ins bundled with continuous Slack support.

That final bundled item should be checked against the actual atomicity rule rather than presumed atomic because the list has only six entries. The source does not provide a complete service SOP or customization allowance.

Variant A is a six-month hybrid CEO-Support Track with all six deliverables and a $7,000–$8,500 monthly placeholder band. Variant B is a four-month hybrid CEO-Support Sprint, also with all six deliverables compressed, at $9,000–$11,000 monthly, aimed at founders approaching a fundraise. Variant C is a lighter ongoing Quarterly CFO Reviews offer at $3,000 per quarter, using items three, four and five, but changing the deep-session cadence from monthly to quarterly.

The claimed four-of-four axis divergence does not hold under the companion worksheet's categories: A and B share a hybrid model, six-item density and durations above nine weeks. Preserve the narrative PASS without treating it as a fresh structural verification. A different delivery intensity should be described explicitly rather than inferred from a new label.

M4.4: show the totals and distinguish revenue from profit

Variant A is priced at $7,500 monthly with a stated six-month minimum of $45,000 and Net 15 monthly invoices. Estimated delivery of ten operator hours per month implies $750 revenue per hour, compared with the source's stated $500 consulting floor. That is not net profit after all costs.

Variant B is $10,000 monthly for four months, totaling $40,000. Variant C remains $3,000 per quarter. Keep the billing units visible; a quarterly price should not be compared with a monthly price as though they were the same commitment.

M4.5: preserve every exclusion and non-claim

The source describes replacing soft exclusions about founders being “serious” with three concrete boundaries. The first excludes founders below $2 million ARR and suggests Quarterly CFO Reviews or waiting until ARR passes $3 million. At exactly $2 million ARR, $7,500 is 4.5% of average monthly revenue, consistent with the source's “over 4%” calculation. That arithmetic does not validate the cutoff or explain the gap between the $2 million exclusion and the $3 million target.

The second exclusion concerns founders outside a venture-backed trajectory, with a suggested alternative of profitability-focused project CFO work. The third excludes founders seeking a replacement for their finance team: the offer is described as working alongside a controller or accounting firm, with traditional integrated fractional services suggested as an alternative.

The three non-claims are no guaranteed Series B success, no monthly closes or accounting deliverables, and no term-sheet negotiation or legal representation. The remaining scope boundaries are only labeled “standard”; their actual text is missing. The source says an Integrity Statement is signed, but no signed record is supplied. This lesson does not provide legal, financial or contractual advice for a real engagement.

M4.6: expose the central contradiction in the guarantee

The proposed time-shift structure allows either party to leave at any point in the first ninety days without cause, with a pro-rata refund of a month not yet engaged. It states no additional activation conditions or exclusions. After day ninety, it describes month-to-month termination on thirty days' notice.

These terms conflict with the prominently stated six-month minimum and $45,000 minimum commitment. The source provides no contract reconciling them. Do not quietly choose one version or market the commitment as settled. A real offer would need consistent, reviewed wording across its pricing, exit policy, guarantee and sales page before being represented to a buyer.

The model assumes a 10–15% exit rate and five sunk onboarding hours at $750, or $3,750 per exit. That yields $375–$562.50 per buyer across the assumed range; the source's approximately $500 is an illustrative midpoint, about 6.7% of one $7,500 month. It is not observed cost data, and the sustainability verdict is not proven by that limited calculation. The statement that service refunds are ill-fitting is the source's generalization, not a universal rule.

M4.7: keep clear copy consistent with the actual terms

The narrative reports seventeen verbatim Trigger Bank entries and a strong buyer-language voice in Sections 1–3. It does not include the full page or all seventeen entries. Maya's peer comment supports the exclusion of buyers wanting someone to handle all finance; Darius praises the visibility of the $7,500 monthly price, six-month minimum and $45,000 total.

That praise does not resolve the exit-policy contradiction. A visible price can still be paired with inconsistent terms. The source describes a minor Section 3 wording revision and a first-submission 9/10 PASS, but supplies neither complete reviewer output nor a corrected contract.

M4.8 and the handoff

The case reports a clean Sonnet pre-screen and Opus validation without notes or warnings. Treat that as a narrative claim, not evidence that the contradictions were reviewed away.

The handoff names an August 1, 2026 opening, the $7,500 monthly lead offer with six-month minimum, six prepared objection responses, a Welcome Kit with founder-spouse-conscious framing, and a three-way Friday asynchronous check-in with Maya and Darius. Only the objection topic “we already have a fractional CFO” is described, using a distinction between CEO support and a traditional fractional role. The other five responses, actual kit and check-in records are absent.

Variant B and the quarterly Variant C are documented for later use, with C potentially becoming a feeder offer. Documentation is not activation, and the case does not authorize sales, outreach, invoicing or enrollment actions.

Apply the curriculum themes and practice

The authored Brunson/ClickFunnels application is agreement between the hook, story, offer, page and actual terms. The authored Hormozi/Acquisition.com application is to make value and risk allocation understandable while testing the cost and capacity assumptions behind the commitment.

As an exercise, place the six-month minimum beside the ninety-day exit and later thirty-day notice provisions. Identify the questions that must be resolved, without inventing a new contract. Then recalculate the three price totals and the range of modeled exit costs, labeling every estimate and every missing evidence record.

Clickable sources

- Original Priya Service-Operator case - Three-Variant Worksheet - Feature Stuffing Trap case - Maya case and Darius case. - The entire original case remains in the appendix. Missing interviews, contracts, full scripts and actual approvals remain explicit dependencies.

Assigned source links

D0449 original source 1

Complete native original body, including retained document-part text

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

# Case Study C: Priya — Service-Operator Designing the CEO-Support Track

**Operator archetype:** Service-Operator (secondary Systems)
**Territory:** Fractional CFO services for venture-backed B2B SaaS founders
**C1 completion:** 2026-02-21
**C2 completion:** 2026-03-30
**C3 completion:** 2026-05-08 (with C3 KC1 trigger and Primary repositioning)
**C4 enrollment:** 2026-05-15
**C4 completion:** 2026-06-26 (6 weeks 0 days — extended pacing per archetype)

---

## Context Inheritance from C3

Priya entered C3 with three finalists, all priced at premium service tiers:

- **Primary:** Series B Readiness Track (12-week structured advisory for Series A startups raising B)
- **Secondary:** Quarterly CFO Reviews (productized advisory cadence)
- **Tertiary:** Fractional CFO Retainer (traditional ongoing engagement)

**C3 critical finding:** During customer interviews, Priya hit KC1 trigger on her Primary's framing. 6 of 9 founders interviewed reported they did not want a "Series B Readiness" engagement framed around the funding event itself. They wanted ongoing CFO support that happened to make them ready, not a discrete project tied to a specific outcome they could not control. The Primary mechanism (cap-table analysis → metric definition → board narrative → diligence prep) was sound; the engagement framing was wrong.

**Repositioning under mentor guidance (in C3 M3.7):** Priya retained the mechanism but **shifted the engagement framing from "Series B Readiness Track" to "CEO-Support Track" — same 4 mechanism pillars, repositioned as ongoing CEO support that produces fundraising readiness as a byproduct rather than as the headline.**

**C3 outputs at C4 entry:**
- **Primary mechanism:** CEO-Support Method (cap-table clarity → metric system → board narrative → diligence-readiness backbone)
- **Trigger Bank:** 219 entries; 124 Primary-relevant
- **Competitor Scan:** 6 competitors (4 fractional CFO firms, 2 founder-coach Substack newsletters with paid CFO tiers)
- **Pricing Signals:** observed band $4,500/month (basic fractional) → $25,000 single-event ("readiness sprint") engagement
- **Customer Interview Library:** 9 interviews; CEO-support framing preferred in 6 of 9 (the Primary repositioning data)

---

## M4.1 — Offer Architecture Foundations

Priya completed the Distinction Memo in 95 minutes — Service-Operator pace.

**Section 2 (mechanism sentence):** "The CEO-Support Method works *because* the cap-table-clarity → metric-system → board-narrative → diligence-readiness sequence converts founder-CFO conversations from reactive ('what should I do about X?') to anticipatory ('here is the structural backbone; what's emerging?'), producing fundraising readiness as a structural byproduct of the support cadence."

**Section 3 (offer sentence):** "The CEO-Support Track is a 6-month engagement *for* Series A founders ($3-15M ARR) at venture-backed B2B SaaS companies, *priced at* $7,500/month *with* a 90-day mutual-fit window allowing either party to exit, and a hybrid commitment to deliverable cadence."

**Component Inventory:**
- Named deliverable: Partial — "CEO-Support Track" works as frame; need 5-Test
- Named buyer: Strong — Series A founders at $3-15M ARR with venture board
- Specific promise: Strong — TB-052, TB-098, TB-176 use "anticipatory" / "structural backbone" language verbatim
- Anti-promise: None — write from scratch in M4.5
- Price: Partial — C3 Pricing Signals show $4,500-$10K/month band for retainer-style; her $7,500 sits at upper-mid
- Guarantee: None — design from scratch in M4.6 (Service-Operator weakness flagged: 90-day mutual-fit may need tightening)
- Delivery structure: Partial — monthly deep sessions + biweekly check-ins + async Slack

**AI rubric:** 8/10. PASS.

---

## M4.2 — Value Equation Application

**Service-Operator strength applied:** Priya's Perceived Likelihood section was the strongest of the three operators because Service-Operators tend to accumulate deep case studies (long-tenure clients) rather than broad ones. She had 3 deep case studies, each with 2+ years of engagement and named board members willing to be referenced.

**Dream Outcome:**
> "I want to lead my company without feeling like I'm flying blind on the financial structure. I want to walk into board meetings prepared rather than scrambling. I want fundraising readiness to be a byproduct of how we operate, not a fire drill we do six months before each round." [Verbatim TB-098 framing]

**Strength rating: Strong.**

**Perceived Likelihood:**
- 3 deep case studies, each with named board members + outcome data
- Mechanism specificity high (4 named pillars)
- Buyer-similar identification: 3 of 3 cases match target (Series A → Series B trajectories)

**Strength rating: Strong-Moderate.** Strong via depth; capped from full Strong by case study count being only 3 named.

**Time Delay:**
- Time-to-first-result: end of Month 1 (cap-table clarity deliverable)
- Time-to-Dream-Outcome: 6-12 months (when "anticipatory cadence" feels like the new normal)

**Strength rating: Strong.** Service engagements have natural time-to-Dream-Outcome alignment because the engagement IS ongoing.

**Effort & Sacrifice:**
- Effort: ~6 hours/month from founder (1 deep session + 2 check-ins + async Slack)
- Sacrifice: $7,500/month commitment

**Strength rating: Moderate.** Effort is bounded; sacrifice is non-trivial but proportional to founder-stage budget.

**Synthesis:** Strongest Time Delay; weakest Effort & Sacrifice (price commitment is real); structurally fixed Time Delay (engagement IS the delay structure); M4.6 guarantee will work on Effort & Sacrifice via 90-day mutual-fit window.

**AI rubric:** 9/10. PASS.

---

## M4.3 — Decomposition and Three Variants

**Service-Operator weakness applied:** Priya initially resisted decomposition. Her instinct was that fractional CFO work cannot be productized — every founder's situation is different. The M4.3 lesson opening section explicitly addresses this resistance: decomposition does not eliminate customization; it provides the scaffold within which customization operates.

After accepting this, Priya's decomposition produced 6 deliverables:

1. Cap-Table Clarity Audit (one-time, Month 1)
2. Metric System Implementation (Month 1-2)
3. Board Narrative Framework (ongoing; refreshed quarterly)
4. Diligence-Readiness Backbone (ongoing documentation)
5. Monthly CFO Deep Sessions (90 min, all 6 months)
6. Biweekly Check-Ins (30 min, all 6 months) + Async Slack Support (continuous)

Three variants:

### Variant A — CEO-Support Track (lead candidate)
- **Engagement:** Hybrid (monthly deep + biweekly check-ins + async)
- **Duration:** 6 months minimum, often renews
- **Deliverables:** All 6
- **Price band placeholder:** $7,000-$8,500/month
- **Targets:** Strongest variant for the validated buyer
- **Buyer fit:** Series A founders at $3-15M ARR

### Variant B — CEO-Support Sprint (4-month intensive variant)
- **Engagement:** Hybrid (more concentrated)
- **Duration:** 4 months
- **Deliverables:** All 6 but compressed
- **Price band placeholder:** $9,000-$11,000/month (premium for compression)
- **Targets:** Founders preparing for fundraise within 6 months who need accelerated implementation
- **Buyer fit:** Series A founders 6-9 months from Series B

### Variant C — Quarterly CFO Reviews (productized lighter variant)
- **Engagement:** Async-first with quarterly deep sessions
- **Duration:** Quarterly cadence, ongoing
- **Deliverables:** 3, 4, 5 (no biweekly cadence; lower touch)
- **Price band placeholder:** $3,000/quarter
- **Targets:** Pre-Series A founders or seed-stage with light CFO needs
- **Buyer fit:** Seed-stage or pre-Series A founders below the Track price band

Axis divergence: 4-of-4 axes distinct. PASS.

---

## M4.4 — Pricing Decision

**Service-Operator strength applied:** Priya was already comfortable with premium pricing.

**Variant A — CEO-Support Track:**
- **Anchor price:** $7,500/month
- **Strategy:** Median (within observed band)
- **Engagement minimum:** 6 months ($45,000 minimum commitment)
- **Payment:** Monthly invoice on Net 15 terms
- **Unit economics:** ~10 hours/month at $750 effective hourly rate. Above her solo-CFO consulting rate floor of $500/hr. PASS.

**Variant B (Sprint):** $10,000/month × 4 months = $40,000 minimum
**Variant C (Quarterly):** $3,000/quarter

PASS.

---

## M4.5 — Anti-Promise Statement

**Service-Operator weakness directly addressed:** Anti-promise audience exclusions are hardest for Service-Operators. Priya's first draft of Section 2 had two soft exclusions ("Not for founders who aren't serious about their business") that the Flattery-Test caught. She rewrote.

**Section 2 (three exclusions, revised):**

1. **Founders below $2M ARR.** The CEO-Support Track price represents over 4% of monthly revenue at $2M ARR; the unit economics don't justify it. Alternative: Quarterly CFO Reviews ($3K/quarter) or wait until ARR crosses $3M.

2. **Founders not yet on a venture-backed trajectory.** The mechanism's diligence-readiness backbone presumes a future fundraise; bootstrap-only founders gain marginal value from this component. Alternative: project-based CFO engagement focused on profitability rather than fundraising-readiness.

3. **Founders looking for someone to "just handle finance for me."** The mechanism is CEO-support, not finance-team-replacement. The Track works alongside an in-house controller or external accounting firm; it does not replace day-to-day finance operations. Alternative: traditional fractional CFO firms that include accounting team integration.

**Section 3 (non-claims):**
- "The Track does not guarantee Series B success. Fundraising depends on market conditions, company performance, and investor sentiment outside CFO scope."
- "The Track does not produce monthly closes or accounting deliverables. Those remain with your accounting function."
- "The Track does not negotiate your term sheet. Term-sheet negotiation requires legal counsel; I provide structural input but not legal representation."

**Section 4 (scope boundaries):** standard.

**Integrity Statement signed.**

PASS.

---

## M4.6 — Guarantee Architecture

**Type:** Time-shift (the 90-day mutual-fit window from M4.1 placeholder, formalized)

**Refund component:** None traditional refund (service work; refund-based guarantee is ill-fit for retainer engagement)

**Time-shift component:**
- 90-day mutual-fit window: at any point in first 90 days, either party can terminate the engagement
- Pro-rata refund of any month not yet engaged
- No cause required; either party invokes
- After day 90, standard month-to-month termination with 30-day notice

**Activation conditions:** None beyond timing; the structure is friction-free by design

**Exclusions:** None — the mutual-fit window applies unconditionally in the first 90 days

**Unit economic model:**
- Assumed exit rate during window: 10-15%
- Per-exit cost: ~5 hours sunk in onboarding × $750 = $3,750 sunk
- Per-buyer absorbed: ~$500 (6.7% of first month $7,500)
- Verdict: sustainable; Service-Operator margin absorbs

**Honesty Clause signed.**

PASS.

---

## M4.7 — Landing Page Copy

**Service-Operator strength applied:** Priya's voice in Sections 1-3 was naturally close to the buyer's vocabulary because Service-Operators speak the buyer's language daily.

**Total verbatim Trigger Bank entries: 17.** Above minimum.

**Peer Reviews:**
- Reviewer 1 (Maya): "Anti-promise Section 2 exclusion 3 ('founders looking for someone to just handle finance') is the most important exclusion on this page. Don't let any softer language creep in elsewhere."
- Reviewer 2 (Darius): "Pricing visibility in Section 5 is good — $7,500/month, 6-month minimum, $45K total commitment is upfront. Some adjacent operators bury this; you don't."

**Revision:** minor — both reviewers affirmed the strong sections. One minor wording tightening in Section 3.

**AI rubric:** 9/10. PASS first submission.

---

## M4.8 — Offer Readiness Document

Sonnet pre-screen PASS. Opus 4.7 PASS — clean run; no warnings, no notes.

**C4 complete. C5 enrollment opens.**

---

## What Priya Carries Into C5

- Lead variant: CEO-Support Track, $7,500/month with 6-month minimum, first slot opens August 1, 2026
- 6 prepared objection responses (including "we already have a fractional CFO" — handled by re-positioning the role of CEO-Support vs traditional fractional)
- Welcome Kit drafted with founder-spouse-friendly framing (acknowledges the founder is buying for their company, not for personal coaching)
- Cohort anchor: Maya (Teacher-Operator) and Darius (Builder-Operator) — three-way Friday async check-in established
- Variant B (4-month Sprint) and Variant C (Quarterly) documented; Variant C may activate at Stage 2 as feeder offer

---

*Last updated: April 24, 2026 · Version 2.0 · Priya's case threads through M4.1-M4.8 module lessons*

Build and test all seven layers of an offer

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and the meaning of architecture

Explain the source's seven layers, all twenty-one subcomponents, nine-part offer story, buyer considerations, seven execution passes and nine worksheet questions. Use them to inspect an offer you can actually deliver. The document calls this Chapter 5 and presents a cinematic, clear, hypnotic and direct-response voice. Its structure is a design framework, not a scientific guarantee of cold-traffic conversion.

The opening story describes a jeweler with a diamond in the dark: no spotlight, velvet, glass, case, presentation or story. The source then places the diamond in a velvet box, under a spotlight, inside a glass case, with a story, certificate, guarantee and financing plan. The object is unchanged, while its presentation and exchange are clearer. The teaching point is that context can affect perceived value. It does not establish that packaging makes every product useful or that value is never recognized without this exact architecture.

The source promises accelerated warm traffic, cold-traffic conversion, hot buyers buying everything, disappearing competitors and category ownership. Those are promotional claims, not verified outcomes. Test whether the design helps the intended customer understand and evaluate a real offer.

Layer 1 — Vehicle

The vehicle is the proposed opportunity, category, mechanism or angle: how the offer claims to help. The source examples are sales funnels, keto, the RISER Engine, an AI operating system and high-ticket hybrid coaching. They illustrate different named approaches; listing them is not an endorsement or evidence of results.

The three subcomponents are new opportunity, new vehicle name and new mechanism. Explain what the customer would do differently and why that might matter. A new name alone does not establish a new mechanism. An authored exercise is to describe the process in plain language before naming it. The source's buyer-facing message is “This is new”; substantiate any novelty claim rather than assuming novelty is automatically valuable.

Layer 2 — Path

The path makes the vehicle usable. The source's full inventory includes frameworks, step-by-step instructions, blueprints, tutorials, lesson plans and weekly milestones. Its three subcomponents are framework, steps and milestones. Distinguish an organizing explanation from the actual sequence of work and from the evidence of progress.

The buyer-facing message is “This is simple.” A clear path can make necessary complexity easier to navigate, but should not conceal effort or prerequisites. The source contrasts the vehicle's dream with the path's practicality. As an authored exercise, name the first action and what successful completion looks like, then connect it to the next step.

Layer 3 — Support

The source lists group coaching, mentorship, accountability, check-ins, private Slack/Discord/Circle spaces, feedback loops, Q&A calls and office hours. Its three subcomponents are accountability, feedback and coaching. These are possible delivery choices, not a mandatory subscription to every platform or a promise that all are included in RISER's live offer.

The buyer-facing message is “This is doable.” Explain what help is actually available, its scope and timing, and what the customer remains responsible for. The source says more support creates greater perceived certainty; that relationship is not guaranteed. Excess support can also create cost, confusion or a mismatch with learner preferences. Choose support that addresses a real obstacle and can be delivered.

Layer 4 — Speed

The complete accelerator inventory is prebuilt templates, scripts, automations, shortcuts, done-for-you pieces, swipe files, plug-and-play systems, SOPs and checklists. The three subcomponents are templates, automations and shortcuts. State which task each asset reduces and what setup or judgment is still required.

The source's message is “This is fast,” and it claims people always pay more for speed. Treat speed as a possible preference to investigate, not a universal rule. An authored test is to compare the time and accuracy of completing a defined task with and without the asset under comparable conditions. Do not label an untested template a proven time saver or a shortcut a replacement for necessary competence.

Layer 5 — Safety

The source lists guarantees, warranties, performance promises, refund windows, results-or-continued-help arrangements, payment plans, probation periods, certifications and onboarding frameworks. Its three subcomponents are guarantees, payment options and risk removal. These choices differ in meaning: a payment plan changes payment timing; a certification is not automatically a performance guarantee.

The buyer-facing message is “This is safe.” Explain the real conditions and remaining risks. Do not promise complete risk removal when the customer still commits time, effort or money. Any proposed guarantee needs an actual scope, duration, conditions and remedy that the business can honor. This lesson does not create a new refund, financing or service policy merely because the source lists it.

Layer 6 — Proof

The full inventory is case studies, testimonials, screenshots, demonstrations, before-and-after transformations, live examples, authority badges and expert endorsements. The three subcomponents are testimonials, case studies and authority. Proof should relate to the specific claim, with enough context to understand what it demonstrates and what it does not.

The buyer-facing message is “This is credible.” The source says proof eliminates doubt and ranks its selling power below only the vehicle. It supplies no comparative evidence for that ranking and no basis to promise elimination of doubt. An authored review pairs each material claim with relevant evidence and marks unsupported claims. Do not invent an endorsement or present an illustrative case as a real result.

Layer 7 — Price

The source says price must be anchored, contrasted, justified, value-based, framed, packaged and sequenced. Its three subcomponents are anchor, contrast and final price, described in the source as irresistible. Explain the actual exchange and use a defensible basis for any comparison or component value.

The buyer-facing message is “This is a no-brainer.” A buyer can reasonably decide the offer is unnecessary or unaffordable. The source's instruction never to reveal price until the architecture is complete is not a universal requirement. Customers should be able to understand price, scope and conditions before committing; withholding information is not evidence of better offer design.

How the layers and stack work together

Read the seven messages in sequence: new, simple, doable, fast, safe, credible and worth the price. They explain the source's intended logic. The claim that all seven make yes the only logical, emotional and identity-safe choice is not established. Ask whether each element is accurate and relevant to the intended buyer.

The source's Offer Stack Model names six aims: increase perceived value, certainty and speed; decrease risk, effort and complexity. It attributes integration to Hormozi, Joyner, Kennedy, Ogilvy and Cialdini, but does not supply a detailed source-by-source derivation. Its claim that any missing aim necessarily reduces conversion is unverified.

For an authored connection to Hormozi, examine the desired outcome, perceived likelihood of achieving it, time delay, and effort and sacrifice shown in the Acquisition.com Value Equation resource. Use the questions to inspect the offer; do not turn subjective scores into a scientific prediction of sales. A larger stack can increase complexity, so adding elements is not always an improvement.

Tell the complete nine-part offer story

The source sequence is: one, the problem and frustration; two, the old method's shortcoming; three, discovery of a new vehicle; four, a repeatable path; five, support along that path; six, accelerators; seven, risk-related terms; eight, evidence that others have succeeded; and nine, the value stack and price.

Explain each transition honestly. Do not invent a broken old method or discovery story merely to fit the narrative. If no customer outcome evidence exists, label that gap and use only demonstrations or evidence actually available. The source attributes a slippery-slide idea to Caples and claims readers cannot stop; that attribution and universal effect are not verified here.

The related ClickFunnels hook–story–offer explanation provides a communication framework. As an authored application, use an opening that names a relevant concern, a truthful explanation connecting it to the solution, and a clear offer. This does not require copying the source's exaggerated claims.

Examine every proposed buyer-psychology mapping

The source maps loss aversion to guarantees and speed; authority bias to testimonials, cases and expert positioning; social proof to the proof layer; effort minimization to templates, automations and done-for-you elements; anchoring and contrast to price; scarcity and urgency to limited seats, deadlines and bonuses; and identity safety to support and a step-by-step path.

These mappings are the source's interpretations, not a validated causal model. Investigate the customer's actual question. Use genuine deadlines and capacity limits, relevant authentic evidence and clear terms. Do not treat a named bias as proof that a tactic is appropriate or that the customer will respond as predicted.

Adjust emphasis for cold, warm and hot audiences

The document describes cold traffic as having little trust, awareness, familiarity or confidence and greater skepticism. It therefore emphasizes six elements: vehicle, value stack, proof, speed, safety and transformation. Preserve all six as questions to answer, rather than assuming every unfamiliar visitor has the same beliefs.

Its shorthand says cold audiences need certainty, warm audiences need simplicity and hot audiences need urgency. Use those as hypotheses about emphasis. All audiences may still need accurate explanations and evidence; interest does not remove the need for clear terms. Do not create false urgency for someone already interested. Measure response by audience and context instead of treating temperature labels as complete knowledge of a person.

Execute all seven passes

In pass one, name and explain the opportunity and mechanism. In pass two, define the framework and steps. In pass three, specify coaching and accountability. In pass four, list the actual templates, scripts and automations. In pass five, document proposed guarantees and payment options with conditions. In pass six, collect available testimonials and cases and identify proof gaps. In pass seven, explain the price and any defensible comparison.

These passes organize the work. They do not guarantee clarity. As an authored review, compare the assembled offer with the delivery team's capacity and a prospective customer's interpretation. Revise any promise, component or price explanation that creates a misunderstanding.

Answer all nine worksheet questions

Record your vehicle; the name of the new opportunity; the path or framework; the support you will provide; the speed elements; the risk-related assets; the proof you have; the value stack; and the final price. Leave missing evidence explicit. A name in a field is not proof that the asset exists.

Review the resulting twenty-one subcomponents across seven layers. Explain why each included item helps, what it costs to deliver and what evidence supports it. This final review is an authored exercise, not a supplied scoring rubric or a guarantee of conversion.

Sources and complete originals

- Assigned seven-layer architecture document. - Foundation and ten-milestone journey. - Final offer blueprint integration. - Coaching-objection source, useful for examining real concerns without assuming the seven layers force a purchase.

The full native and filed source variants remain in the appendix, including the original promotional and attribution claims.

Assigned source links

D0450 original source 1

Complete native document body

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?
→ ________________________________________
Complete local source copy including original filing metadata and formatting

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?
→ ________________________________________
________________

Build the foundation of an offer: problem, transformation and first useful gift

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and place in the curriculum

Write a clear Big Promise, map the ten milestones in the assigned source, and design a useful first resource that relates to the paid offer. The document calls itself Module 1 of an offer-development sequence. That legacy number does not change its current spreadsheet lesson assignments.

The source connects Brunson with moving a customer toward a desired outcome, Hormozi with compelling value, and Kennedy with clarity. These are the document's attributions; its quotation wording has not been independently authenticated. Treat them as an orientation to the lesson, not proof that a promise will convert or that price becomes irrelevant. A clear offer must still fit the customer, budget and delivery capacity.

1. Define one core problem and the transformation

Begin with the audience's most important relevant difficulty. Describe the situation in terms someone experiencing it could recognize. Then describe the change they want. The source example moves from difficulty maintaining a workout routine toward weight loss and confidence. It illustrates the relationship between a problem and a desired outcome; it supplies no medical program, timeline or results evidence.

For an authored business example, a new service provider might struggle to explain a proposal clearly and want a proposal a customer can understand and evaluate. Write the problem separately from the hoped-for result. Do not confuse the delivery mechanism, such as a workbook, with the result, such as a clearer proposal. Interview or observe actual intended customers before treating your interpretation as validated.

Your first artifact is a Core Problem Statement. Your second is an Ultimate Transformation Statement. Include who the offer is for, what currently goes wrong, and what a useful improvement would look like. Do not broaden the outcome merely to make it sound impressive.

2. Map all ten milestones

The source's ten-milestone journey is a planning sequence. It is not evidence that everyone progresses in exactly this order or at the same speed. Keep every milestone visible and ask what action or evidence would make it meaningful for your offer.

  1. Identify the problem. Help the learner name the actual difficulty. In the proposal example, inspect where a reader cannot understand scope or next steps.
  2. Believe it can be solved. Explain a credible process or demonstrate a bounded improvement. Do not substitute motivational certainty for evidence.
  3. Take the first small action. Choose a manageable start, such as clarifying one proposal paragraph. Specify what the learner does.
  4. Build consistency. Establish an achievable practice or review routine. A routine that does not fit the learner's circumstances is not a useful plan.
  5. See the first results. Define a result that can be checked. An example is a reviewer accurately explaining the proposed scope, rather than an assumed increase in sales.
  6. Overcome resistance or setbacks. Anticipate unclear inputs, insufficient time or feedback showing that a draft needs work. Name a way to respond without blaming the learner.
  7. Level up commitment. Expand the useful practice when the learner is ready. More commitment should serve the goal, not merely create more work.
  8. Experience a breakthrough. Identify a meaningful change in capability or understanding. Do not promise a dramatic moment on a fixed schedule.
  9. Lock in the transformation. Document what worked and how the learner will maintain it. A checklist or review standard can help when it addresses a real recurring task.
  10. Share or celebrate success. Invite the learner to recognize progress or voluntarily share it. A celebration is not permission to use their story as a marketing testimonial.

The source says later offers and bonuses will align with the milestones. As an authored exercise, place a proposed support asset beside the milestone where it would help, explain its purpose, and leave the cell empty when no asset is needed. Ten milestones do not require ten products or ten bonuses.

3. Design the MIFGE

The source expands MIFGE as “Most Incredible Free Gift Ever.” It describes a lead magnet that provides a real solution, is fast to consume, and connects directly to the paid offer. Its examples include a checklist, template or cheat sheet. The intention is a useful first experience, rather than a teaser that withholds everything necessary to act.

For the proposal example, an authored concept is a short checklist that helps someone find missing scope, delivery and next-step information. The checklist should work on its own for that bounded purpose. A paid service may provide broader review or implementation, but the free resource should not pretend to do work it cannot do.

The document suggests asking whether people would pay for the gift as a quality test and says the first contact should feel exciting. Those are creative prompts, not validated demand measures. Also check whether the intended customer can use the resource, whether its instructions are complete, and whether the result matters to them. State any actual signup conditions clearly. Giving someone a useful resource does not obligate them to buy.

4. Explain the offer with influence and story

The source names reciprocity, social proof and authority. In this lesson's authored application, give something useful without demanding repayment, present relevant authentic examples, and explain expertise accurately. Do not imply authority through an invented badge or present an illustrative story as a real customer result.

The source also uses hook, story and offer. ClickFunnels describes this as an attention-opening hook, a connecting story and an offer. Use that sequence to help the reader understand the problem and proposed help. A story must remain truthful; a clear offer includes real scope and conditions. See the ClickFunnels explanation of hook, story and offer.

An authored hook for the example could ask whether a prospective client can tell what a proposal includes. The story can explain a real misunderstanding and what was clarified, or be explicitly labeled hypothetical. The offer then describes the checklist and any genuine next step. Avoid inventing revenue results to make the story more persuasive.

For a related value review, consider the desired outcome, perceived likelihood, time delay, and effort and sacrifice associated with the offer. These are the four dimensions shown in Acquisition.com's Value Equation material. Here they are questions for design, not a measured formula that predicts sales. The official Value Equation training page is a further resource, separate from the assigned source.

Produce the four deliverables

Complete the problem and transformation statements; list the ten milestones; draft the MIFGE concept; and write the Big Promise in one or two sentences. Preserve the source template: “I help [audience] go from [problem] to [dream outcome] without [common obstacle].” Fill it with a result and obstacle your service can actually address. The word “without” must not erase work the customer still needs to do.

An authored draft is: “I help new service providers turn an unclear proposal into a defined scope and next step, using a structured review.” This is an example for practice, not an approved RISER commercial promise. Review how the audience interprets it and revise any misleading implication.

Check readiness for the next part

The source asks three questions: Is the Big Promise written? Does the MIFGE excite you enough to give it away proudly? Can you see how offers, bonuses or funnel steps could support each milestone? Answer all three. Then distinguish personal confidence from customer evidence. A written draft is ready for further testing when its scope is understandable and its assumptions are visible; it is not automatically ready for a public launch.

The source closes with clarity, perceived value and repeated refinement. Apply those themes by testing whether another person can describe the outcome and required effort accurately. Preserve the actual feedback, revise the draft and keep building from evidence.

Sources and complete original

- Assigned foundation document. - Related seven-layer architecture source, including path, support, speed, safety, proof and price considerations. - Related final-integration source, which describes the later offer blueprint handoff.

The complete native and filed original text belongs in the lesson appendix alongside this teaching. The practice examples above are authored applications.

Assigned source links

D0451 original source 1

Complete native document body

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.
Complete local source copy including original filing metadata and formatting

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.
________________

Assemble the complete offer blueprint and team handoff

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and source scope

Bring the offer's research, positioning, ladder, funnel, copy, bonuses and delivery into one coherent plan. The assigned document names this Module 10 of an offer-development bootcamp. Keep that legacy label separate from the current course and lesson assignments.

The source is an integration outline, not a completed business plan or proof that a funnel is ready to launch. It references Modules 1–9 without supplying all their bodies here. Its attributed Brunson, Kennedy and Hormozi statements reinforce packaging, consistency, delivery and iteration; exact quotation wording is not authenticated by this document. The following explanations and handoff checks are authored applications of the supplied sequence.

1. Assemble the five-tier value ladder

The source sequence is MIFGE, tripwire, core offer, profit maximizer and high-ticket offer. MIFGE means the Most Incredible Free Gift Ever in the related foundation source. Describe the useful first result it provides. Describe the limited initial paid commitment of the tripwire, the main transformation of the core offer, the additional value supplied by a profit maximizer, and the deeper service or scope of a high-ticket offer.

Use those as planning categories. They are not a requirement to sell every customer five products. A gap exists when someone who needs a next step cannot understand or access a suitable next step. A gap does not mean that every possible price point must have an offer.

For each tier, write the intended customer need, actual deliverables, price, prerequisites and logical next step. If a tier would add complexity without helping the customer, document that decision rather than inventing a product to fill a diagram. The source's instruction to eliminate gaps should serve customer progress and a workable business.

2. Match funnel recipes to ladder steps

The document lists lead, tripwire, VSL, webinar and application funnels and asks you to cross-check the Module 6 page recipes. A lead funnel supports an appropriate entry action. A tripwire funnel presents the initial paid offer. VSL and webinar funnels communicate an offer through recorded or presentation-based content. An application funnel collects relevant information before a more considered next step.

These descriptions are authored explanations, not the missing Module 6 recipes. Draw the actual pages and transitions required for the chosen offer: where the visitor arrives, what they learn, what action they take, and what confirmation or delivery follows. Account for someone declining or encountering an error. An outline saying “webinar funnel” is not a page-by-page implementation specification.

Do not assume that one named funnel is inherently best for a ladder tier. Choose a flow that suits the customer's decision, the necessary explanation and the team's delivery capacity. Mark untested choices as assumptions.

3. Insert copy and messaging

The source calls for hooks, stories and offers from Module 7, influence principles associated with Cialdini, and copy matched to funnel type and audience sophistication. In an authored handoff, keep one clear page purpose and one understandable next action. Explain a problem the reader recognizes, use an authentic or explicitly hypothetical story, and state the real offer.

Audience sophistication concerns what the intended audience already knows and has encountered. Do not assume that a newcomer and an experienced buyer need the same explanation. Keep claims, scope, price and terminology consistent across the advertisement, page, checkout and onboarding.

The ClickFunnels hook–story–offer reference explains the communication sequence. It does not verify your product's results. Use relevant, authentic proof and accurately described expertise. The source's reference to influence triggers is not permission to fabricate testimonials, urgency or authority.

4. Stack bonuses and angles

The document says to add at least three bonuses to each core offer, drawing on Module 8, and to frame the stack using Module 5 pricing psychology. Preserve that as the source's design exercise; three bonuses is not a universal conversion optimum.

As an authored review, name the obstacle each proposed bonus removes, how the customer uses it, what it costs to deliver and whether it duplicates the core service. If three useful bonuses cannot be justified, record the conflict between the exercise and the offer's needs. Avoid adding irrelevant materials merely to increase a nominal stack value.

The source also asks you to highlight the MIFGE entry point. Explain its bounded usefulness and its genuine relationship to the paid path. A free entry resource should not conceal the terms of the next purchase. Price anchors and claimed component values need a defensible basis; they do not become evidence through repetition.

5. Confirm platform and delivery systems

The outline points to Module 9 for matching platforms to offers and describes automation and onboarding as seamless. Turn that aspiration into a concrete plan. State the actual platform, how access is granted, where the customer starts, what fulfillment requires and who handles a failure.

An authored delivery review can follow one authorized test customer through payment or registration, access, first use and support. Plan the test without initiating purchases or operational actions merely because a source document proposes them. A written automation map is not evidence that an integration is configured or working. Record the observed test result separately from the design.

6. Complete all seven blueprint fields

The source's worksheet can be a single document or spreadsheet. It must bring together all seven categories:

  1. Niche and avatar: who the offer serves and the source of that understanding, drawing on the earlier audience work.
  2. Offer statement: the Big Promise and transformation, including meaningful limits and prerequisites.
  3. Value ladder and pricing: each intended tier, its exchange and its next step.
  4. Funnels and page flows: the sequence of pages and customer actions.
  5. Copy frameworks: hooks, calls to action and angles attached to the correct page.
  6. Bonuses and guarantees: the actual components and applicable conditions, without inventing missing policies.
  7. Platforms and delivery map: the systems, access and fulfillment responsibilities.

This is the master reference. Link the supporting work rather than creating conflicting versions of the same promise or price. As an authored addition, mark unresolved decisions, who will resolve them and what evidence is still required. Keep these additions distinct from the source's seven-field worksheet.

The five required deliverables

Produce the integrated Offer Blueprint; a funnel, platform and delivery map; draft hooks and copy for every required page; finalized proposed value stacks with pricing and bonuses; and a specification understandable to the VA, designer or technical team who would build it. These deliverables describe a prepared handoff. They do not certify that the live experience has already been built or approved.

The source's expert tips call for documenting a repeatable system, beginning with a working recipe and iterating. Apply them by preserving a version of the plan, recording test findings and updating the relevant component. Copying a competitor's expression or assuming their funnel works is not evidence-based iteration.

Graduation check and build readiness

Answer all three source questions: Is the complete blueprint documented? Can you explain the ladder, funnel, copy, bonuses and platforms in under five minutes? Are you confident handing it to a team to build? Use the short explanation to find ambiguity, not to hide necessary detail.

Then distinguish confidence from readiness. An authored readiness review asks whether a builder can identify the required inputs, actual deliverables, unresolved choices and verification steps. A plan with missing source recipes can still identify those gaps honestly. It cannot claim that the missing recipes were taught or implemented.

Sources and supporting documents

- Assigned final-integration document. - Foundation, Big Promise and ten-milestone source. - Master Offer Blueprint workbook: the supplied file is a DOCX with ten blank module forms, not a completed blueprint. - Competitor-recon source, supporting the research and positioning work. - Acquisition.com Value Equation training, a related primary resource for examining desired outcome, confidence, delay and effort.

The complete assigned native and filed source texts accompany the teaching in the lesson appendix.

Assigned source links

D0452 original source 1

Complete native document body

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

Module 10 – Pulling It All Together: The Offer Blueprint
(Your One-to-Many Offer System, Fully Integrated & Ready to Launch)
Objective
By the end of this module, you’ll have a complete Offer Blueprint that unites all the pieces—research, positioning, funnel, copy, bonuses, platforms—into a single, executable strategy.

Why This Matters
Russell Brunson: “An offer is not a product. It’s everything wrapped together into one irresistible package.”

Dan Kennedy: Consistency beats brilliance—your system must flow from start to finish.

Alex Hormozi: An offer isn’t about ideas—it’s about proof you can deliver results better, faster, and safer than anyone else.

Riser Nation: You don’t build a skyscraper one floor at a time—you need the full blueprint before you pour the concrete.


Step 1 – Assemble the Value Ladder
Place each offer in the right tier (MIFGE → Tripwire → Core → Profit Maximizer → High-Ticket).

Confirm there are no “gaps” where customers get stuck.


Step 2 – Map the Funnel Recipes
Assign the right funnel type to each ladder step (Lead, Tripwire, VSL, Webinar, Application).

Cross-check with Module 6 page recipes.


Step 3 – Insert Copy & Messaging
Plug in hooks, stories, offers (Module 7).

Layer in influence triggers (Cialdini).

Match copy style to funnel type + audience sophistication.


Step 4 – Stack Bonuses & Angles
Add at least 3 bonuses per core offer (Module 8).

Frame the value stack with pricing psychology (Module 5).

Highlight your “MIFGE” as the irresistible entry point.


Step 5 – Confirm Delivery Systems
Match each offer with its platform (Module 9).

Ensure automation + onboarding are seamless.


Step 6 – The Offer Blueprint Worksheet
Put everything into one document/spreadsheet:
Niche & Avatar (from Modules 1–2).

Offer Statement (Big Promise + Transformation).

Value Ladder + Pricing.

Funnels & Page Flows.

Copy Frameworks (hooks, CTAs, angles).

Bonuses & Guarantees.

Platforms & Delivery Map.

This becomes your master reference file for building and scaling.

Deliverables for Module 10
✅ A completed Offer Blueprint (all modules integrated).
 ✅ A clear funnel + platform + delivery map.
 ✅ Draft copy + hooks for each page.
 ✅ Value stacks finalized with pricing & bonuses.
 ✅ Ready-to-build system you can hand to a VA, designer, or tech team.

Pro Tips & Expert Secrets
Kennedy: Document your system so anyone could execute it—this is how you scale.

Brunson: Don’t reinvent—start with a working recipe, then test/iterate.

Hormozi: Never stop improving your offer—iteration is the path to wealth.

Riser Nation: Think like a builder—your blueprint isn’t the house, but without it, the house falls down.


Graduation Checkpoint
Do you have your complete Offer Blueprint documented?

Can you explain your ladder, funnel, copy, bonuses, and platforms in under 5 minutes?

Do you feel confident handing this to a team and saying, “Build it”?

If yes → You’ve completed the Offer Development Bootcamp. You now own a repeatable system for crafting, testing, and scaling irresistible offers.
Complete local source copy including original filing metadata and formatting

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/1SnKwFUtqBVZjVTfX1HIWCAwydk_JYGhkoDI66T2MJvQ/edit?usp=drivesdk"
drive_file_id: "1SnKwFUtqBVZjVTfX1HIWCAwydk_JYGhkoDI66T2MJvQ"
created: "2025-10-08T01:06:39.695Z"
modified: "2026-06-04T14:43:22.818Z"
---

# CNX.3.11.10 – Offer_Dev_Module_10_The_Offer_Blueprint_Final_Integration.docx

Module 10 – Pulling It All Together: The Offer Blueprint
(Your One-to-Many Offer System, Fully Integrated & Ready to Launch)
Objective
By the end of this module, you’ll have a complete Offer Blueprint that unites all the pieces—research, positioning, funnel, copy, bonuses, platforms—into a single, executable strategy.
________________


Why This Matters
* Russell Brunson: “An offer is not a product. It’s everything wrapped together into one irresistible package.”

* Dan Kennedy: Consistency beats brilliance—your system must flow from start to finish.

* Alex Hormozi: An offer isn’t about ideas—it’s about proof you can deliver results better, faster, and safer than anyone else.

* Riser Nation: You don’t build a skyscraper one floor at a time—you need the full blueprint before you pour the concrete.

________________


Step 1 – Assemble the Value Ladder
   * Place each offer in the right tier (MIFGE → Tripwire → Core → Profit Maximizer → High-Ticket).

   * Confirm there are no “gaps” where customers get stuck.

________________


Step 2 – Map the Funnel Recipes
      * Assign the right funnel type to each ladder step (Lead, Tripwire, VSL, Webinar, Application).

      * Cross-check with Module 6 page recipes.

________________


Step 3 – Insert Copy & Messaging
         * Plug in hooks, stories, offers (Module 7).

         * Layer in influence triggers (Cialdini).

         * Match copy style to funnel type + audience sophistication.

________________


Step 4 – Stack Bonuses & Angles
            * Add at least 3 bonuses per core offer (Module 8).

            * Frame the value stack with pricing psychology (Module 5).

            * Highlight your “MIFGE” as the irresistible entry point.

________________


Step 5 – Confirm Delivery Systems
               * Match each offer with its platform (Module 9).

               * Ensure automation + onboarding are seamless.

________________


Step 6 – The Offer Blueprint Worksheet
Put everything into one document/spreadsheet:
                  * Niche & Avatar (from Modules 1–2).

                  * Offer Statement (Big Promise + Transformation).

                  * Value Ladder + Pricing.

                  * Funnels & Page Flows.

                  * Copy Frameworks (hooks, CTAs, angles).

                  * Bonuses & Guarantees.

                  * Platforms & Delivery Map.

This becomes your master reference file for building and scaling.
________________


Deliverables for Module 10
✅ A completed Offer Blueprint (all modules integrated).
✅ A clear funnel + platform + delivery map.
✅ Draft copy + hooks for each page.
✅ Value stacks finalized with pricing & bonuses.
✅ Ready-to-build system you can hand to a VA, designer, or tech team.
________________


Pro Tips & Expert Secrets
                     * Kennedy: Document your system so anyone could execute it—this is how you scale.

                     * Brunson: Don’t reinvent—start with a working recipe, then test/iterate.

                     * Hormozi: Never stop improving your offer—iteration is the path to wealth.

                     * Riser Nation: Think like a builder—your blueprint isn’t the house, but without it, the house falls down.

________________


Graduation Checkpoint
                        * Do you have your complete Offer Blueprint documented?

                        * Can you explain your ladder, funnel, copy, bonuses, and platforms in under 5 minutes?

                        * Do you feel confident handing this to a team and saying, “Build it”?

If yes → You’ve completed the Offer Development Bootcamp. You now own a repeatable system for crafting, testing, and scaling irresistible offers.
________________

Use the Master Offer Blueprint workbook across all ten modules

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

What the supplied workbook actually contains

The source is the RISER Nation Offer Development Bootcamp Master Offer Blueprint Workbook. It describes its purpose as guiding offer building, validation and launch. It contains ten named modules with blank forms. Each has one objective field, three numbered core-exercise fields and three deliverable fields: seven fields per module, seventy in total.

The blanks are intentional source content. They are not completed exercises, hidden answers or proof that a module has been finished. The original DOCX is retained. The examples below explain how to use the form and are newly authored applications; the workbook does not supply those answers.

How to fill one module form

Write the capability or output you intend to achieve in the objective. Use the three exercise lines for three concrete actions that support that objective. Use the three deliverable lines for three inspectable outputs or linked artifacts. Distinguish an action, such as reviewing customer feedback, from its output, such as a documented problem statement.

An objective should not promise a business result the exercise cannot establish. A filled checkbox does not demonstrate quality. Review the actual artifact against the objective and identify unresolved evidence or decisions. The following module-by-module suggestions preserve every form while giving you a practical way to complete it.

Module 1 — Foundation & Big Promise

An authored objective is to explain the intended customer problem and a supportable transformation. The three exercise lines can cover reviewing the problem evidence, mapping the ten milestones from the foundation lesson, and drafting a useful MIFGE concept. The three deliverables can be the paired problem/transformation statements, the milestone map, and a Big Promise with the linked gift concept.

Grouping related artifacts on one deliverable line is acceptable if the underlying work remains clear. Do not remove the foundation lesson's required outputs merely because the workbook has three slots. Check the promise against what the offer can actually deliver.

Module 2 — Audience & Market Research

An authored objective is to describe whom the offer serves using identifiable evidence. Exercise lines can cover collecting permitted existing customer evidence, grouping recurring needs, and identifying what remains uncertain. Deliverable lines can hold an audience description, an evidence summary with source links, and an open-question list.

This workbook supplies the module title, not a research protocol or completed avatar. Do not invent customer interviews or describe assumptions as findings. The related full module body remains a separate source to consult when available.

Module 3 — Crafting Offer Strategy

An authored objective is to connect a customer need to a feasible exchange. Exercise lines can define the intended outcome, list necessary delivery components, and compare the proposed scope with customer effort and business capacity. Deliverables can be an offer statement, a scope map, and an assumption/evidence record.

Keep the method and the result separate. A stack of materials is not automatically a strategy. The seven-layer architecture source can help you inspect vehicle, path, support, speed, safety, proof and price, while its conversion claims remain claims rather than guarantees.

Module 4 — Competitor Recon & Differentiation

An authored objective is to explain a defensible difference from relevant alternatives. Exercise lines can identify competitors, review their publicly available offer flows, and compare unmet needs. Deliverables can hold the completed recon records, comparison grid, and differentiation statement required by the related recon lesson.

That lesson asks for at least five completed competitor records. One workbook line may link the collection. Do not turn one blank line into permission to omit four competitors or copy their creative work. Publicly visible marketing does not establish actual conversion performance.

Module 5 — Pricing Psychology & Value Ladder

An authored objective is to explain the proposed price and progression between offers. Exercise lines can map relevant ladder tiers, examine delivery economics, and review how the customer understands the price and conditions. Deliverables can be the ladder, the price rationale, and a record of conditions and unresolved assumptions.

The workbook does not supply price points or a financial model. A high nominal stack value does not prove willingness to pay. Treat revenue, costs and forecast assumptions as different kinds of information, and do not label a price validated without supporting evidence.

Module 6 — Funnel Recipes & Page Strategies

An authored objective is to map a clear route from entry to the appropriate next action and delivery. Exercise lines can choose a suitable flow, specify each page's purpose, and identify normal, declined and failed paths. Deliverables can hold the page-flow map, page requirements, and a proposed verification checklist.

The module title is not a complete funnel recipe. Use separately assigned recipes when available, and mark missing instructions. This lesson does not initiate any funnel activation, checkout or purchase.

Module 7 — Copywriting & Messaging Mastery

An authored objective is to communicate the offer consistently and accurately. Exercise lines can draft a hook, develop a truthful or clearly hypothetical story, and write the offer and next action. Deliverables can be a message map, page copy, and a claim-evidence review.

This uses the hook–story–offer theme discussed in the foundation source. It does not mean that every page needs a long story. Check whether the reader can understand the result, actual scope, required effort and terms. Do not fill proof gaps with invented testimonials.

Module 8 — Bonuses, Stacks & Angles

An authored objective is to select useful additions and explain their role. Exercise lines can identify obstacles, map candidate bonuses to them, and assess duplication and fulfillment cost. Deliverables can be the proposed bonus inventory, the stack explanation, and the evidence or rationale for each component.

The integration source asks for at least three bonuses per core offer. Treat that as its exercise requirement, while recording any reason a smaller or different set would serve the customer better. The workbook itself contains no bonus bodies, templates or price anchors.

Module 9 — Platforms & Delivery Systems

An authored objective is to specify how the customer receives and uses the offer. Exercise lines can map access, allocate fulfillment responsibilities, and plan a test of onboarding and support. Deliverables can be the platform map, operating requirements, and the verification record or clearly labeled unexecuted test plan.

Do not equate naming software with implementing it. Record actual availability and dependencies. Planned automations must not be labeled active until they have been authorized, configured and checked in the relevant environment.

Module 10 — Final Offer Blueprint

An authored objective is to assemble a handoff another person can follow. Exercise lines can collect the preceding artifacts, reconcile inconsistent promises or prices, and rehearse the explanation of the plan. Deliverables can be the master blueprint, the supporting page/platform map, and the remaining-decision and verification record.

The related integration source requires seven master fields covering niche/avatar, offer statement, ladder/pricing, funnels/page flows, copy frameworks, bonuses/guarantees and platform/delivery. Keep all seven inside the linked blueprint. Three workbook deliverable lines do not reduce that scope.

Review the seventy fields without confusing completeness with readiness

Check each of the ten modules for one objective, three exercises and three deliverables. Where work is incomplete, identify the missing input rather than inserting a claim of completion. Where one field links several supporting artifacts, confirm the links work and the artifacts remain associated with the correct module.

The workbook title refers to validation and launch, but the blank form does not establish either. Separate drafted plans, evidence of testing, actual implementation and public launch. Preserve the original blank template alongside your working copy so another learner can see what was supplied and what you added.

Sources and related lessons

- Assigned Master Offer Blueprint workbook, a native DOCX file presented through a Google document link. - Foundation and ten-milestone source. - Seven-layer offer architecture. - Competitor-recon requirements. - Final integration and seven-field blueprint.

The full original form and original DOCX must accompany this lesson. These authored examples do not replace separate missing module bodies.

Assigned source links

D0453 original source 1

Original document-part extraction

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

word/document.xml
RISER Nation Offer Development Bootcamp
Master Offer Blueprint Workbook
This workbook is designed as a step-by-step guide to build, validate, and launch your irresistible offers.
Module 1 – Foundation & Big Promise
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Module 2 – Audience & Market Research
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Module 3 – Crafting Offer Strategy
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Module 4 – Competitor Recon & Differentiation
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Module 5 – Pricing Psychology & Value Ladder
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Module 6 – Funnel Recipes & Page Strategies
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Module 7 – Copywriting & Messaging Mastery
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Module 8 – Bonuses, Stacks & Angles
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Module 9 – Platforms & Delivery Systems
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Module 10 – Final Offer Blueprint
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________
---
Complete original body with all explicit line breaks

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

RISER Nation Offer Development Bootcamp
Master Offer Blueprint Workbook
This workbook is designed as a step-by-step guide to build, validate, and launch your irresistible offers.

Module 1 – Foundation & Big Promise
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Module 2 – Audience & Market Research
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Module 3 – Crafting Offer Strategy
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Module 4 – Competitor Recon & Differentiation
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Module 5 – Pricing Psychology & Value Ladder
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Module 6 – Funnel Recipes & Page Strategies
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Module 7 – Copywriting & Messaging Mastery
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Module 8 – Bonuses, Stacks & Angles
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Module 9 – Platforms & Delivery Systems
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Module 10 – Final Offer Blueprint
Objective: ________________________________
Core Exercise:
1. _______________________________________
2. _______________________________________
3. _______________________________________
Deliverables:
✅ _______________________________________
✅ _______________________________________
✅ _______________________________________

---

Map competitors and define an offer difference you can deliver

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and evidence limits

Build a competitive map showing who offers relevant alternatives, how they present and price those offers, and where your proposed offer may serve a need differently. The source labels this Module 4 of the offer-development bootcamp. Preserve the current spreadsheet's assignments rather than importing that legacy numbering into the live curriculum.

The source associates Kennedy with differentiation, Brunson with funnel reconnaissance and Hormozi with additional customer value. Its exact attributed quotations, claims of months saved and suggestion that a small value difference can justify double the price are not independently substantiated here. Treat the useful idea as a research question: what difference matters to the customer, and can you deliver it?

1. Identify five to ten direct competitors

The document lists seven discovery channels: Google, Facebook Ads Library, TikTok, YouTube, Etsy, Amazon and Udemy. These are places to look for relevant alternatives, not a requirement that every business has competitors on all seven. Search for the customer problem and kind of offer, not just a favorite brand name.

List five to ten businesses selling similar offers. For each, record the core promise, visible price and funnel entry point. Confirm that it serves a sufficiently similar customer and need to make comparison useful. Preserve the date and URL because public offers can change. If a price is not disclosed, record that rather than guessing it.

The source deliverable requires at least five completed competitor records. A list of names alone does not meet it. As an authored addition, explain why each competitor belongs in the comparison and distinguish observed facts from your interpretation.

2. Capture all six funnel-recon categories

The source refers to an Offer Recon Template but does not include its actual form. The six categories below preserve its required content; the proposed recording method is an authored application, not a recovered template.

  1. Headline and hook: record how the offer initially attracts attention and which need it names. Keep a source link and sufficient context to avoid changing the claim's meaning.
  2. Lead magnet or MIFGE: describe the free entry resource, what it promises to help with and any visible conditions. Do not infer its full contents from a cover image.
  3. Front-end offer: capture the disclosed price, format and positioning. Separate a one-time price from a recurring payment and a temporary promotion from the usual offer when the source establishes those distinctions.
  4. Value stack and bonuses: identify the actual listed components. Record unavailable bonus details as unknown; a headline does not prove the bonus is useful or delivered.
  5. Upsells and downsells: document what is publicly observable and its relationship to the first offer. Do not invent checkout steps that cannot be inspected without a purchase or private access.
  6. Funnel flow: map the observed transition from opt-in to sales page, checkout and upsell where visible. Mark unobserved steps explicitly. A suggested industry pattern is not an observation of that competitor.

The purpose is to understand structure and decision points. It does not authorize buying a product, submitting a lead form or copying another business's creative assets. Describe how an element works in your own words and keep the reference attached.

3. Analyze copy and messaging

The source asks you to notice repeated phrases, emotional triggers and proof placement. Capture recurring language as evidence of the competitor's messaging, not proof that the wording converts. An advertisement remaining visible does not reveal its profitability.

Examine all four named emotional themes: fear, desire, status and safety. Ask what customer concern the message addresses and whether the claim is supported. Identify where testimonials or other proof appear and how they relate to the promise. Do not assume that an impressive screenshot validates every result implied by the page.

In an authored comparison, write one sentence explaining the observed message and another labeling your interpretation. For example, “The page emphasizes guided practice” is an observation when the page says so. “Customers will pay more for accountability” is a hypothesis that needs evidence. This distinction makes the research usable when writing your own hook, story and offer.

4. Ask all four gap questions

The source asks what needs are unmet, where copy is unclear or generic, what customer reviews complain about, and which bonuses are missing. Work through each question for the relevant competitors.

An unmet need should be grounded in customer evidence. Unclear copy can be documented by pointing to the specific ambiguity. Reviews can reveal a question worth investigating, but individual reviews may not represent all customers. Record the context and avoid stripping away contrary information.

A missing bonus is not automatically a gap. Ask whether the proposed addition would help the customer achieve the desired outcome, reduce unnecessary effort or improve useful support. More assets can also create more work. Preserve the source's bonus question while assessing usefulness rather than counting extras.

5. Position an advantage

The document asks you to decide a unique mechanism and stack value in a way the alternatives do not. Explain the actual process or support difference, who it helps and why it matters. A new name alone does not make a familiar service substantively different.

The source example compares a $297 course without accountability to a $297 offer with a checklist and an accountability group. This is illustrative, not evidence about a real competitor or a proven conversion lift. Check the group's staffing, availability and cost before including it in an actual offer. The customer may or may not value the addition.

Use the source's differentiation template: “Unlike [competitor], my offer [unique mechanism] so that customers [superior benefit].” Write a claim you can substantiate. If you cannot fairly demonstrate superiority, state the concrete difference and intended benefit without claiming a proven better outcome.

Produce all three deliverables

First, complete the recon records for at least five competitors, covering the six source categories. Second, make a side-by-side Competitive Summary Grid showing price points, funnels and bonuses. Third, draft the Differentiation Statement.

An authored grid can use competitor, source/date, customer/promise, pricing, flow, bonuses, evidence and open questions as columns. Those added fields support traceability; they are not part of a separately retrieved source template. Link to the detailed records so the grid does not flatten conditional pricing or source limitations into misleading comparisons.

Check readiness and keep testing

The source's three checkpoint questions are whether you have a clear picture of competitors' funnels and offers, can articulate your edge in one bold sentence, and have identified gaps you can fill. Answer each using the actual records. A confident sentence is not enough when the underlying capability or customer need remains untested.

The source then points toward pricing psychology and value-ladder alignment. Carry the evidence and unknowns forward. The direct-response application is to make the offer clearer and more useful while testing the customer response, rather than assuming that copying a visible funnel removes the need to test.

Sources and resources

- Assigned competitor-recon document. - Discovery channels named by the source: Google, Meta Ads Library, TikTok, YouTube, Etsy, Amazon and Udemy. These are navigation resources, not inspected competitor results or endorsements. - Foundation and Big Promise source, for the problem and intended transformation being compared. - Master Offer Blueprint workbook, which contains a blank competitor-recon module form. - Final-integration source, for carrying the research into the complete offer plan.

The full original source variants accompany the lesson appendix. The separate Offer Recon Template remains unavailable in this source.

Assigned source links

D0454 original source 1

Complete native document body

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.
Complete local source copy including original filing metadata and formatting

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.
________________

Turn business mindset ideas into observable learning and action

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and evidence boundaries

Use every concept in the assigned mindset overview to examine a decision, set a practical goal and choose a next action. The source brings together wealth-building beliefs, passive-income categories, growth mindset, SMART goals, visualization, several named theories, fear, abundance and ten software tools. It provides a motivational overview, not evidence that positive thinking guarantees sales or wealth.

The exercises in this lesson are authored applications. The source's attributions to Jim Rohn, Tony Robbins, Carol Dweck and other authors are retained as source attributions rather than authenticated quotations. Personal agency matters, but resources, market conditions, health, access and other constraints also influence outcomes. A setback does not establish a defect in someone's mindset.

Wealth-building mindset and the four income categories

The source describes a wealth-building mindset as treating challenges as occasions to learn and taking action toward financial goals. Apply that idea by separating a goal, an available action and a constraint you cannot simply think away. Treat money as a resource for chosen purposes rather than as a measure of personal worth.

The source gives four examples of income that may continue beyond an immediate hour of work. Investments include stocks, bonds and real estate; they require capital and involve risk. Online businesses include digital products or services; creation, marketing, maintenance and support may continue after launch. Royalties can arise from books, music or art under applicable rights and agreements; sales are not guaranteed. Peer-to-peer lending involves interest from lending, with borrower, platform and other risks.

These are categories for understanding the source, not recommendations to invest or launch a particular business. “Passive” does not mean effortless, costless or risk-free. Investor.gov explains that investments involve risk and warns against high guaranteed-return claims. See Investor.gov's investor-protection guidance.

Examine negative beliefs without denying facts

The source names beliefs such as money being evil or wealthy people being greedy and suggests replacing them with a view of money as a tool for useful purposes. As an authored exercise, write the belief, identify the experience behind it, and distinguish a broad judgment from a specific concern.

For example, concern about dishonest selling should not be reframed away. It can become a commitment to clear terms and accurate claims. A more useful working statement might be, “I can charge for a service I can deliver while respecting the customer's choice.” Test that statement through conduct rather than repeating it as proof of success.

Growth mindset, effort and responsibility

The source uses Dweck's growth-mindset concept to explain that abilities can develop through learning and practice. Stanford's teaching guidance also emphasizes trying strategies and responding to feedback. Treat effort as part of learning, not a guarantee that any repeated action will work. See Stanford's growth-mindset guidance.

The source's Rohn summary emphasizes goals and responsibility. An authored application is to identify one decision you control, one resource you need and one external constraint. After an unsuccessful attempt, inspect the method and evidence. Decide whether to revise the approach, seek help, change the scope or stop. Learning from failure does not require repeating a costly mistake.

Set a SMART goal using all five elements

The source expands SMART as Specific, Measurable, Achievable, Relevant and Time-bound. Specific names the action or output. Measurable states how progress will be checked. Achievable compares the scope with actual capacity. Relevant connects the work to a meaningful need. Time-bound defines when the review or completion is due.

An authored example is: “By Friday, draft one proposal scope and ask one consenting reviewer whether the deliverables and next step are clear.” The measure is the completed draft and recorded feedback, not a promised sale. Adjust the deadline or scope when capacity makes it unrealistic. A sales outcome may be a business goal, but do not confuse it with an action fully under your control.

Use visualization and affirmations as prompts for action

The source describes visualization as imagining success and associates it with Tony Robbins. It describes affirmations as positive statements, including being worthy of financial success. It does not supply evidence that either practice guarantees money or literally reprograms the brain in a specified way.

An authored practice is to imagine completing the next task, then identify the steps, likely obstacle and response. Pair a realistic statement such as “I can prepare, ask for feedback and revise” with the actual work. Do not let a pleasant imagined outcome replace a plan, and do not frame ordinary doubt as disqualifying someone from success.

Apply the three other named theories carefully

The source summarizes Maslow's hierarchy as attending to basic needs before higher ambitions. For this lesson, use it as a prompt to consider practical stability and competing needs. The document does not establish a rigid rule that everyone must satisfy one complete tier before pursuing another, and a sales script should not diagnose a person's needs from a brief conversation.

The source associates Covey with beginning with the end in mind. An authored application is to define the useful outcome before selecting tasks and tools. Work backward to the evidence or artifact that would show progress.

The source's Cialdini summary emphasizes understanding people in relationships and selling. Apply that by listening to the actual concern and communicating honestly. Psychological concepts do not give permission to fabricate proof, exploit a fear or override a customer's decision. The assigned document does not provide a full treatment of these three authors' work; that scope remains distinct from this overview.

Work with fear, uncertainty and risk

The source recommends education, supportive people and mentors, and treats setbacks as opportunities to learn. Identify the specific uncertainty: a missing skill, unclear demand, financial exposure or a delivery dependency. Then choose information or help that addresses it. General encouragement may be welcome but does not answer every concrete concern.

The source also encourages risk-taking. Use a bounded, reversible learning step when possible and decide what cost or result would cause you to stop. Do not treat courage as a reason to disregard money needed elsewhere or to claim certainty about an untested offer. The lesson teaches decision habits, not a financial recommendation.

Scarcity, abundance, gratitude and generosity

The source contrasts a belief that opportunity is insufficient with an abundance-oriented perspective and emphasizes gratitude and generosity. Use this to notice possible collaborations and avoid reflexively treating every other person's success as a loss to you.

Actual time, cash and market constraints remain real. Gratitude does not remove them. Generosity can build useful relationships, but it does not guarantee repayment or create an obligation to buy. Choose contributions that fit your capacity and be clear about any commercial offer attached to them.

Understand all ten tools named in the source

These are the source's proposed uses, with original clickable vendor links preserved. Their websites were checked September 11, 2026; this is not a review of your accounts, paid plans or every current feature. Choose a tool only for an actual task, and avoid creating duplicate systems merely to use every name on the list.

  1. Evernote: organize thoughts, goals and plans. An authored use is keeping a dated learning note with the action it informs.
  2. Trello: organize project work. An authored use is tracking a task from planned to reviewed.
  3. MindMeister: map related ideas and goals. Use a map to examine relationships, then identify the next concrete action.
  4. Google Keep: capture short notes and thoughts. The checked link leads to Google sign-in; account access was not tested.
  5. Asana: manage tasks and projects. Clarify responsibility and due dates rather than using status labels as proof of completion.
  6. Slack: communicate with collaborators. A channel can support questions, but important decisions still need an accessible record.
  7. Canva: prepare business graphics or presentations. Design helps communication; it does not establish the truth of a claim.
  8. Notion: organize plans, goals and notes. The original link currently redirects to Notion's .com site; keep a clear structure and source references.
  9. Todoist: track actionable tasks. A useful entry describes something you can do, rather than only an aspiration.
  10. Zapier: automate supported repetitive processes. First understand and test the process; an automation can repeat a mistake as well as a useful action. This lesson does not activate any workflow.

Connect mindset to the offer-development work

As an authored RISER application, use the customer problem and transformation from the foundation lesson to choose a goal. Use feedback to improve the hook, story and offer. Inspect actual support, evidence and effort requirements when reviewing perceived value. Brunson and Hormozi themes belong in the design and testing of the offer; enthusiasm alone is not evidence that the customer needs it or that the business can deliver it.

Finish with a short practice record: one belief to examine, one SMART goal, one obstacle, one learning action, one appropriate tool if needed, and a review date. At review, describe what happened and what you will change. This is an authored exercise, not a supplied validated psychological assessment.

Sources and complete original

- Assigned mindset overview. - Related foundation and customer-transformation lesson source. - Related seven-layer offer architecture source.

All ten original embedded tool links and complete native/filed source texts belong in the lesson appendix. The original motivational claims remain available there with the qualifications explained above.

Assigned source links

D0455 original source 1

Original tables, images and embedded resource links

Original embedded hyperlinks:

Complete native document body

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.
Complete local source copy including original filing metadata and formatting

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.

Calculate real-estate client value without multiplying the lifetime twice

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and the source's important limitation

Read every metric and example in the assigned real-estate lifetime-value document, distinguish annual frequency from lifetime transactions, and explain what referral and acquisition assumptions would be required. The original includes a formula table, glossary and worked narrative. All remain preserved in the lesson appendix.

The source has a material inconsistency: it sometimes defines purchase frequency as the total transactions a customer makes over the relationship, then multiplies that total by years again. That overstates value. This lesson preserves the original numbers while explaining when a formula is dimensionally valid. The revised examples below are authored calculations under explicit assumptions, not verified results from an actual real-estate business.

Understand all nine glossary terms

LTV, lifetime value, is defined in the source as total customer revenue over the relationship. Label that revenue LTV so it is not confused with profit or contribution. ATV, average transaction value, is revenue per transaction; the narrative uses commission earned rather than the price of the property itself. PF, purchase frequency, is transactions per customer over a defined period. The period is essential.

CL, customer lifespan, is the duration of the active relationship. RR, referral rate, needs a precise definition: the source alternates between referrals divided by customers and the percentage of customers who refer. Those are not necessarily equal. CAC, customer acquisition cost, divides relevant marketing and sales costs by newly acquired customers for a matching population and period.

ROI, return on investment, compares a defined investment's gain with its cost; it is not the same as revenue divided by acquisition cost. The glossary also includes HOA, homeowners association, a body governing a residential community and potentially charging fees, and MLS, multiple listing service, a system used by real-estate professionals to share listing information. These last two terms provide real-estate context but are not variables in the source's LTV equations.

Read the first formula table exactly

The table supplies ATV as total revenue divided by total transactions, with an example of $12,000. PF is total transactions divided by total customers, with 1.5. CL is six years. RR is total referrals divided by total customers, with 0.40. CAC is total marketing and sales cost divided by acquired customers, with $1,000.

It then calculates basic LTV as $12,000 × 1.5 × 6 = $108,000. The multiplication is arithmetically correct. It represents six-year revenue only if the 1.5 is transactions per customer per year, with the assumed rate applying across those years. The table does not state that annual basis. If 1.5 is already total lifetime transactions, the corresponding revenue is $18,000 before any separately justified referral value.

The source's advanced calculation is $108,000 × (1 + 0.40) = $151,200. That result assumes the referral factor can legitimately add forty percent of the original value. Merely counting referrals does not establish that. The final ratio is $151,200 ÷ $1,000 = 151.2:1; the table displays 151:1, a rounded version. Neither ratio proves profit, payback timing or affordable acquisition spending.

Check the narrative's commission example

The narrative starts with a hypothetical $500,000 sale and 3% commission, producing $15,000. Keep the difference between the property value and the business's commission revenue clear. Also determine whether the amount represents the relevant business's actual retained revenue after any applicable splits or other costs before using it in an operating model.

Three percent is an illustrative assumption, not a standard commission. NAR states that broker fees and commissions are negotiable and not set by law. See NAR's consumer explanation. This lesson does not recommend a commission rate or establish the terms of any transaction.

Resolve the purchase-frequency and lifespan conflict

The narrative says a client buys two homes, with examples of a first home, an upgrade and possibly a retirement home. Two homes is the stated input; the list also mentions a possible third transaction. Do not count that third event without evidence or a clearly stated scenario.

It defines PF as two transactions per customer and CL as seven years, while also describing seven to ten years between purchases. Time between transactions and total relationship length are different measures. The document does not resolve that difference.

The source calculates $15,000 × 2 × 7 = $210,000. If the two transactions are the total over the relationship, multiplying by seven years counts the duration again. Under that lifetime-total interpretation, the authored correction is $15,000 × 2 = $30,000 in gross commission revenue over the relationship. If the intent were two transactions every year for seven years, $210,000 would match that separate assumption—but the narrative does not establish such a frequency.

Before using the model, write either transactions per customer per year multiplied by years, or total lifetime transactions per customer with no additional lifespan multiplication. Do not switch definitions midway through the model.

Define referral value before applying a multiplier

The narrative uses RR = 0.50 and computes $210,000 × 1.50 = $315,000. That arithmetic is correct for the stated multiplier but inherits the inflated base under the lifetime-total interpretation.

An authored simplified correction can illustrate the assumptions: start with $30,000 gross lifetime commission and assume an average of 0.5 additional converted clients per original client, each with the same expected value, with no recursive referral generations included. Then $30,000 × 1.50 = $45,000. That is a conditional illustration. The statement that half of customers refer someone does not alone prove 0.5 converted equal-value customers.

Distinguish the share of customers making a referral, referrals per referring customer, conversion from referral to client, the referred client's expected value and the cost of serving or acquiring that client. Avoid counting the same referred customer again in another cohort. If the referral data do not establish these quantities, keep the added value unmeasured rather than filling it with a confident multiplier.

The source later says that half of customers referring effectively doubles LTV. Its own simple 50% multiplier yields one-and-a-half times, not twice. Preserve that contradiction in the original and explain it here. Do not silently turn 50% into 100% to make the statement agree.

Separate customer revenue from acquisition economics

The source proposes that a $315,000 LTV makes spending $5,000 to acquire a client an obvious choice. That conclusion is not established by the supplied data. First correct the period definitions and identify whether the value is revenue, margin or cash available to cover acquisition.

Then account for the cost and timing of providing the service, retention and repeat-purchase assumptions, referral conversion and the delay before cash arrives. The source gives no business records proving those inputs. A large revenue-to-CAC ratio can still coexist with poor cash flow or insufficient profit. The lesson therefore does not authorize or recommend a $5,000 acquisition spend.

The source's table ratio uses a $1,000 CAC, while its later decision example uses $5,000. These are different scenarios. Do not combine one scenario's ratio with the other's cost without recalculating and preserving all assumptions.

Apply the four practical implications with appropriate limits

First, the source encourages seeing the relationship beyond one commission. That is useful when future transactions are supported by a coherent estimate rather than an inflated formula. Second, it recommends investing in lead generation and retention. Base any allocation on verified economics and capacity, not the source's overstated example.

Third, it emphasizes relationship building for repeat business and says clients typically transact every seven to ten years. Treat that interval as a source assertion, not a verified prediction for your market or clientele. The source also claims future transactions can be secured without extra marketing costs. Ongoing communication, service and relationship management can require time and money, so future revenue is neither secured nor necessarily free to obtain.

Fourth, it values referrals and word of mouth. Track them separately and attribute them consistently. An authentic referral relationship can be valuable without claiming that it automatically doubles every customer's value or costs nothing.

A practical worksheet and review exercise

As an authored exercise, record the cohort and period, revenue definition, average retained revenue per transaction, the frequency unit, estimated lifespan if needed, referral assumptions, acquisition costs, relevant service costs and cash timing. Mark unavailable data clearly.

Recreate both source scenarios without changing their original values, label the dimensional and referral errors, and calculate a separate corrected illustration under stated assumptions. Explain why $108,000 may be valid under an annual-frequency interpretation, why the narrative's two lifetime transactions imply $30,000 rather than $210,000, and why a 50% multiplier is not doubling. Distinguish the rounded 151:1 table label from the exact 151.2:1 result.

The Brunson/Hormozi application is to connect acquisition and offer design with customer value that can be delivered and measured. A more compelling promise or a longer ladder cannot repair an inconsistent denominator. Test repeat-service and referral ideas against actual customer needs and fulfillment economics.

Sources and complete originals

- Assigned real-estate lifetime-value document. - Related Average Cart Value workbook, whose separate formula discrepancies also require explicit review rather than uncritical reuse. - Related final offer-blueprint source, for keeping pricing, delivery and funnel assumptions aligned.

The original native 21-by-3 table contains both the formula and glossary sections. Preserve that table, blank cells and the full native/filed text in the appendix.

Assigned source links

D0456 original source 1

Original tables, images and embedded resource links
D0456 native table 1; original blank cells retained
Lifetime Value (LTV) Calculation of customer
Metric Formula Example Values
Average Transaction Value (ATV) Total Revenue / Total Transactions $12,000
Purchase Frequency (PF) Total Transactions / Total Customers 1.5
Customer Lifespan (CL) Average years a customer stays active 6 years
Referral Rate (RR) Total referrals / Total customers 0.40 (40%)
Customer Acquisition Cost (CAC) Total Marketing & Sales Cost / Number of Acquired Customers $1,000
Basic LTV Calculation LTV = ATV x PF xCL $12,000 x 1.5 x 6 = $108,000
Advanced LTV Calculation (Including Referral Value) LTV = (ATV xPF xCL) x(1 + RR) $108,000 x(1 + 0.40) = $151,200
LTV to CAC Ratio LTV / CAC $151,200 / $1,000 = 151:1
Abbreviation Full Term Definition
LTV Lifetime Value The total revenue a customer generates over their relationship with your business.
ATV Average Transaction Value The average amount of revenue earned per transaction.
PF Purchase Frequency The average number of transactions per customer over a given time period.
CL Customer Lifespan The average number of years a customer remains active with your business.
RR Referral Rate The percentage of customers who refer new clients.
CAC Customer Acquisition Cost The total marketing and sales cost divided by the number of acquired customers.
ROI Return on Investment A measure of profitability that calculates the benefit gained from an investment compared to its cost.
HOA Homeowners Association A governing body that oversees properties in a residential community, often charging monthly fees.
MLS Multiple Listing Service A database that real estate professionals use to find and list properties for sale.
Complete native document body

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

REAL ESTATE LIFETIME VALUE OF CLIENT


Lifetime Value (LTV) Calculation of customer


Metric
Formula
Example Values
Average Transaction Value (ATV)
Total Revenue / Total Transactions
$12,000
Purchase Frequency (PF)
Total Transactions / Total Customers
1.5
Customer Lifespan (CL)
Average years a customer stays active
6 years
Referral Rate (RR)
Total referrals / Total customers
0.40 (40%)
Customer Acquisition Cost (CAC)
Total Marketing & Sales Cost / Number of Acquired Customers
$1,000
Basic LTV Calculation
LTV = ATV x PF xCL
$12,000 x 1.5 x 6 = $108,000
Advanced LTV Calculation (Including Referral Value)
LTV = (ATV xPF xCL) x(1 + RR)
$108,000 x(1 + 0.40) = $151,200
LTV to CAC Ratio
LTV / CAC
$151,200 / $1,000 = 151:1



Abbreviation
Full Term
Definition
LTV
Lifetime Value
The total revenue a customer generates over their relationship with your business.
ATV
Average Transaction Value
The average amount of revenue earned per transaction.
PF
Purchase Frequency
The average number of transactions per customer over a given time period.
CL
Customer Lifespan
The average number of years a customer remains active with your business.
RR
Referral Rate
The percentage of customers who refer new clients.
CAC
Customer Acquisition Cost
The total marketing and sales cost divided by the number of acquired customers.
ROI
Return on Investment
A measure of profitability that calculates the benefit gained from an investment compared to its cost.
HOA
Homeowners Association
A governing body that oversees properties in a residential community, often charging monthly fees.
MLS
Multiple Listing Service
A database that real estate professionals use to find and list properties for sale.

📌 How to Calculate the Lifetime Value (LTV) of Your Real Estate Customer & What It Means for You
As a real estate agent, understanding Customer Lifetime Value (LTV) helps you determine how much revenue a single customer generates over their lifetime of business with you. This includes repeat transactions, referrals, and upsells (such as selling their next home or investment properties).

🔹 Step 1: Key Metrics for Calculating LTV in Real Estate
1️⃣ Average Commission Per Transaction (ATV)
How much commission do you earn per home sale?
Formula: Total Commission Earned ÷ Total Transactions
Example: If your average sale price is $500,000 and you earn a 3% commission, your ATV = $15,000.
2️⃣ Average Transactions Per Customer (PF - Purchase Frequency)
How many times will a client buy or sell with you?
Formula: Total Transactions ÷ Total Customers
Example: If a client buys 2 homes (first home, upgrade home, and possibly a retirement home), PF = 2 transactions per customer
3️⃣ Average Customer Lifespan (CL)
How long do customers stay in your pipeline or work with you before another transaction?
Example: If a customer stays with you for 7-10 years between home purchases, CL = 7 years.
4️⃣ Referral Rate (RR)
How many new clients do they refer?
Formula: Total Referrals ÷ Total Customers
Example: If 50% of your past clients refer at least one new client, RR = 0.50 (50%)

🔹 Step 2: Calculate Your Real Estate LTV
1️⃣ Basic LTV Formula:
LTV = ATV × PF × CL
Example:
$15,000 × 2 transactions × 7 years = $210,000 LTV per customer.
2️⃣ Advanced LTV Formula (Including Referrals):
LTV = (ATV × PF × CL) × (1 + RR)
Example:
$210,000 × (1 + 0.50) = $315,000
If you include referrals, your LTV jumps to $315,000 per client.

🔹 What Does This Mean for You?
✅ Understand the Real Value of Each Client:
Instead of just seeing a $15,000 commission per deal, you realize that an average client is worth over $210,000+ when repeat transactions and referrals are included.
✅ Invest More in Lead Generation & Retention:
If acquiring a new client costs $5,000 in ads & marketing, and their LTV is $315,000, then spending $5,000 to acquire a new client is a no-brainer.
✅ Focus on Relationship Building for Repeat Business:
Clients typically buy and sell every 7-10 years. By staying in touch, providing value, and nurturing them, you secure future transactions without extra marketing costs.
✅ Leverage Referral Marketing & Word-of-Mouth:
If half of your past clients refer someone, your LTV effectively doubles without increasing your ad spend.
Complete local source copy including original filing metadata and formatting

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/1_NJAN5HH6kVJT2wy9qxboR8O3T9SBVa4xtLnNqCuJYE/edit?usp=drivesdk"
drive_file_id: "1_NJAN5HH6kVJT2wy9qxboR8O3T9SBVa4xtLnNqCuJYE"
created: "2025-03-04T23:39:55.302Z"
modified: "2026-06-04T15:56:13.782Z"
---

# CNX.6.4.2 – Real_Estate_Lifetime_Value_of_Client.docx

REAL ESTATE LIFETIME VALUE OF CLIENT




Lifetime Value (LTV) Calculation of customer
	

	

	Metric
	Formula
	Example Values
	Average Transaction Value (ATV)
	Total Revenue / Total Transactions
	$12,000
	Purchase Frequency (PF)
	Total Transactions / Total Customers
	1.5
	Customer Lifespan (CL)
	Average years a customer stays active
	6 years
	Referral Rate (RR)
	Total referrals / Total customers
	0.40 (40%)
	Customer Acquisition Cost (CAC)
	Total Marketing & Sales Cost / Number of Acquired Customers
	$1,000
	Basic LTV Calculation
	LTV = ATV x PF xCL
	$12,000 x 1.5 x 6 = $108,000
	Advanced LTV Calculation (Including Referral Value)
	LTV = (ATV xPF xCL) x(1 + RR)
	$108,000 x(1 + 0.40) = $151,200
	LTV to CAC Ratio
	LTV / CAC
	$151,200 / $1,000 = 151:1
	

	

	

	Abbreviation
	Full Term
	Definition
	LTV
	Lifetime Value
	The total revenue a customer generates over their relationship with your business.
	ATV
	Average Transaction Value
	The average amount of revenue earned per transaction.
	PF
	Purchase Frequency
	The average number of transactions per customer over a given time period.
	CL
	Customer Lifespan
	The average number of years a customer remains active with your business.
	RR
	Referral Rate
	The percentage of customers who refer new clients.
	CAC
	Customer Acquisition Cost
	The total marketing and sales cost divided by the number of acquired customers.
	ROI
	Return on Investment
	A measure of profitability that calculates the benefit gained from an investment compared to its cost.
	HOA
	Homeowners Association
	A governing body that oversees properties in a residential community, often charging monthly fees.
	MLS
	Multiple Listing Service
	A database that real estate professionals use to find and list properties for sale.
	

📌 How to Calculate the Lifetime Value (LTV) of Your Real Estate Customer & What It Means for You
As a real estate agent, understanding Customer Lifetime Value (LTV) helps you determine how much revenue a single customer generates over their lifetime of business with you. This includes repeat transactions, referrals, and upsells (such as selling their next home or investment properties).
________________


🔹 Step 1: Key Metrics for Calculating LTV in Real Estate
1️⃣ Average Commission Per Transaction (ATV)
* How much commission do you earn per home sale?
* Formula: Total Commission Earned ÷ Total Transactions
* Example: If your average sale price is $500,000 and you earn a 3% commission, your ATV = $15,000.
2️⃣ Average Transactions Per Customer (PF - Purchase Frequency)
* How many times will a client buy or sell with you?
* Formula: Total Transactions ÷ Total Customers
* Example: If a client buys 2 homes (first home, upgrade home, and possibly a retirement home), PF = 2 transactions per customer
3️⃣ Average Customer Lifespan (CL)
* How long do customers stay in your pipeline or work with you before another transaction?
* Example: If a customer stays with you for 7-10 years between home purchases, CL = 7 years.
4️⃣ Referral Rate (RR)
* How many new clients do they refer?
* Formula: Total Referrals ÷ Total Customers
* Example: If 50% of your past clients refer at least one new client, RR = 0.50 (50%)
________________


🔹 Step 2: Calculate Your Real Estate LTV
1️⃣ Basic LTV Formula:
LTV = ATV × PF × CL
* Example:
   * $15,000 × 2 transactions × 7 years = $210,000 LTV per customer.
2️⃣ Advanced LTV Formula (Including Referrals):
LTV = (ATV × PF × CL) × (1 + RR)
* Example:
   * $210,000 × (1 + 0.50) = $315,000
   * If you include referrals, your LTV jumps to $315,000 per client.
________________


🔹 What Does This Mean for You?
✅ Understand the Real Value of Each Client:
* Instead of just seeing a $15,000 commission per deal, you realize that an average client is worth over $210,000+ when repeat transactions and referrals are included.
✅ Invest More in Lead Generation & Retention:
* If acquiring a new client costs $5,000 in ads & marketing, and their LTV is $315,000, then spending $5,000 to acquire a new client is a no-brainer.
✅ Focus on Relationship Building for Repeat Business:
* Clients typically buy and sell every 7-10 years. By staying in touch, providing value, and nurturing them, you secure future transactions without extra marketing costs.
✅ Leverage Referral Marketing & Word-of-Mouth:
* If half of your past clients refer someone, your LTV effectively doubles without increasing your ad spend.
________________

Use the Brain-Driven Success outline as a practical learning plan

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

What this source can and cannot teach

The assigned source is an outline called “Brain-Driven Success System: Reset Your Filters, Reset Your Future.” It lists five modules, fifteen lesson titles and five named exercises. It proposes noticing opportunities, taking action, developing confidence and sustaining a useful learning environment.

It does not supply the fifteen complete lesson bodies, the named exercise forms, a validated five-minute reset protocol or evidence that its program rewires a particular brain system. Claims about magnetic growth, emotional reprogramming, dopamine loops and unstoppable results remain source claims. The teaching below covers every outline component and offers explicitly authored learning practices. These are not recovered neuroscience lessons, diagnostic methods or treatments.

Understand the proposed progression

The source moves from awareness, through emotions and daily practice, toward momentum and contribution. Its table pairs the modules with five proposed transformations: awareness of mental filtering, emotional changes supporting opportunity recognition, daily opportunity practice, accumulated small wins, and expansion-oriented thinking.

Use that order as a learning design hypothesis. You can notice a habitual interpretation before deciding how to respond, practice a useful behavior, review the outcome and adjust. The document's phrases “repetition = rewiring” and “brain trust loops” do not establish measured neurological mechanisms for these exercises. Keep behavioral observation separate from an explanation about brain chemistry that the source does not substantiate.

Module 1 — Understanding Brain Filters

The three named lessons are The Invisible Editor (RAS and perception), How fear and survival bias your reality, and The science of filter resetting (neuroplasticity). The source uses the reticular activating system, or RAS, as an explanation for filtering and limiting success. It supplies no scientific evidence that this curriculum resets it. Do not teach the title as proof of that mechanism.

The practical learning question is what you notice, what you overlook and how an expectation may affect your interpretation. An authored example is noticing only negative comments on a proposal while overlooking a useful suggestion. Examine the actual feedback rather than assuming every concern is a fear bias.

The named exercise is My Current Filter Inventory. Its original form is absent. An authored version records a situation, your initial interpretation, the evidence you noticed, contrary or missing evidence, and one question to investigate. This is a reflection record, not a test of RAS function or a measure of neuroplasticity.

Module 2 — Resetting Your Emotional Drivers

The three titles are The chemistry of fear vs growth, Emotional tagging and RAS rewiring, and Building your emotional reframe habits. These identify proposed topics. They do not establish a two-state chemical model of fear and growth or supply a method proven to rewire the RAS.

An authored practice is to identify an emotion and the situation in which it occurs, then separate observable facts from your first interpretation. Consider another plausible interpretation and a useful next action. Reframing should not require denying a real problem or pretending to feel positive.

The source names a Daily Emotion Reframe Tracker without fields or instructions. An authored tracker can contain date, situation, emotion in your own words, evidence, alternative interpretation, chosen action and later observation. No particular emotional result is guaranteed. The exercise supports ordinary reflection and does not replace clinical support.

Module 3 — Training Opportunity Detection

The three titles are The Opportunity Blindness Effect, Practical techniques to tune your focus, and Opportunity journaling system. The capitalized effect is not accompanied by a study, definition or validated assessment in this source. Treat it as the outline's name for a proposed topic, not an established diagnosis.

An authored business practice is to record an observed customer difficulty, distinguish the observation from your proposed solution, and ask what evidence would make the opportunity credible. Focus can help you collect relevant information, but a desired outcome does not make a market opportunity real.

The exercise is Daily Opportunity Tracker Launch. The supplied source has no tracker template. An authored record can include the observed need, source and date, possible response, evidence still required, effort or cost, and a next review decision. Recording many ideas is different from validating one useful offer.

Module 4 — Building Momentum Through Daily Resets

The titles are Micro-wins and dopamine loops, The 5-minute Brain Reset Ritual, and Layering habits for compounding confidence. The document provides no neurological measurement, ritual steps or evidence that five minutes produces a biological reset. Do not invent those as original material.

As a clearly authored five-minute reflection exercise, use the first minute to name the task and current obstacle, the next two to review one piece of evidence, the fourth to choose a feasible action, and the last to record when you will check it. These timing choices are new and adjustable; they are not the missing source ritual or a neuroscience protocol.

The named exercise is the 30-Day Brain Reset Challenge. The original daily assignments are not supplied. An authored thirty-day practice can record one chosen action and what happened each day, with periodic review of what to change. Missed days are information about capacity or fit, not proof that the learner failed to reset their brain. Small completed actions can supply evidence of progress without claims about dopamine loops.

Module 5 — Expanding to Magnetic Growth Filters

The three titles are The shift from survival to contribution, Designing your future reality intentionally, and Locking in your Magnetic Filter Blueprint. Use “magnetic” as the source's motivational metaphor. The outline does not demonstrate attraction of success through a neurological or physical mechanism.

An authored application is to identify whom you want to help, what useful contribution you can make and the limits of your current resources. Planning can guide action; it does not control every future event. Record a goal, an evidence-based next step and the conditions under which you would revise the plan.

The named exercise is the North Star Visualization Ritual. Its steps are missing. An authored reflection can describe a meaningful direction, imagine a concrete useful action, identify a likely obstacle and schedule the action. The “Magnetic Filter Blueprint” is also only named; a new planning sheet must be labeled as authored rather than presented as that missing original artifact.

Review all four proposed outcomes

The source wants learners to notice useful opportunities, take aligned action with less hesitation, develop emotional stability and confidence, and maintain a supportive mindset and environment. Preserve these as aims. Measure what can actually be observed: a documented opportunity assessment, an action completed, a revised interpretation, or an environment change that makes useful work easier.

The source does not supply thresholds, a validated score or a guarantee that these outcomes occur. Do not invent a pass/fail brain score. In a course review, ask the learner to explain what they tried, what evidence they gathered and what they would change. Confidence should remain connected to experience and feedback, not merely repetition of an affirmation.

Connect the plan to offer development

As an authored RISER application of the Brunson/Hormozi themes, use the opportunity tracker to collect evidence of a customer's problem, then draft a clear hook, story and offer. Examine the proposed outcome, supporting evidence, delay and effort before presenting the value. These business-design questions give the reflection a practical purpose without claiming that marketing success proves a neurological change.

Keep the fifteen source lesson titles available in the outline. A teaching extension covering these titles does not mean that the missing full lesson bodies or original exercise forms have been recovered. The complete source table, progression notes, outcomes and exercise names remain in the appendix.

Sources and related resources

- Assigned Brain-Driven Success outline. - Related business-mindset source, another overview requiring distinctions between motivational ideas and demonstrated mechanisms. - Related customer-problem and transformation source. - Stanford's growth-mindset guidance, a further educational resource emphasizing learning, strategies and feedback. It does not validate this named brain-reset program. - NINDS Brain Basics, a general authoritative starting point for learning about brain function, not evidence for the supplied marketing claims.

The practices are authored additions; missing original lesson bodies and exercise forms remain explicit.

Assigned source links

D0457 original source 1

Original tables, images and embedded resource links
D0457 native table 1; original blank cells retained
Module Title Key Transformation
1 Understanding Brain Filters Awareness of how RAS filters reality and limits success
2 Resetting Your Emotional Drivers Reprogramming emotions to support opportunity spotting
3 Training Opportunity Detection Daily practices to tune your RAS for success
4 Building Momentum Through Daily Resets Compound small wins to retrain your filters
5 Expanding to Magnetic Growth Filters Lock in expansion thinking for unstoppable growth
Complete native document body

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

Brain-Driven Success System: Full Course Curriculum Outline

📚 Course Name
Brain-Driven Success System: Reset Your Filters, Reset Your Future

🏠 Overall Promise
Train your brain to spot, seize, and scale opportunities by rewiring your invisible mental filters.
 Shift from fear-based survival thinking to magnetic growth-focused action.

🔄 Course Structure
Module
Title
Key Transformation
1
Understanding Brain Filters
Awareness of how RAS filters reality and limits success
2
Resetting Your Emotional Drivers
Reprogramming emotions to support opportunity spotting
3
Training Opportunity Detection
Daily practices to tune your RAS for success
4
Building Momentum Through Daily Resets
Compound small wins to retrain your filters
5
Expanding to Magnetic Growth Filters
Lock in expansion thinking for unstoppable growth

📈 Module Progression Logic
Awareness First: You can't reset what you don't see.

Emotional Foundation Second: Feelings prime perception.

Daily Practices Third: Repetition = rewiring.

Momentum Fourth: Small wins create brain trust loops.

Expansion Fifth: Lock in magnetic success and contribution filters.


👁️ Ideal Completion Outcome
By the end of this program, students will:
Naturally spot high-leverage opportunities

Take bold, aligned action with less hesitation

Build internal emotional stability and confidence

Create a self-sustaining success mindset and environment


📚 Module 1: Understanding Brain Filters
Lesson 1: The Invisible Editor (RAS and perception)

Lesson 2: How fear and survival bias your reality

Lesson 3: The science of filter resetting (neuroplasticity)

Exercise: "My Current Filter Inventory"

📚 Module 2: Resetting Your Emotional Drivers
Lesson 1: The chemistry of fear vs growth

Lesson 2: Emotional tagging and RAS rewiring

Lesson 3: Building your emotional reframe habits

Exercise: Daily Emotion Reframe Tracker

📚 Module 3: Training Opportunity Detection
Lesson 1: The Opportunity Blindness Effect

Lesson 2: Practical techniques to tune your focus

Lesson 3: Opportunity journaling system

Exercise: Daily Opportunity Tracker Launch

📚 Module 4: Building Momentum Through Daily Resets
Lesson 1: Micro-wins and dopamine loops

Lesson 2: The 5-minute Brain Reset Ritual

Lesson 3: Layering habits for compounding confidence

Exercise: 30-Day Brain Reset Challenge

📚 Module 5: Expanding to Magnetic Growth Filters
Lesson 1: The shift from survival to contribution

Lesson 2: Designing your future reality intentionally

Lesson 3: Locking in your Magnetic Filter Blueprint

Exercise: North Star Visualization Ritual
Complete local source copy including original filing metadata and formatting

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/1BWjB3OUywie6uYbVnCNSodnhSe6IJqrUjYcxw94AsZI/edit?usp=drivesdk"
drive_file_id: "1BWjB3OUywie6uYbVnCNSodnhSe6IJqrUjYcxw94AsZI"
created: "2025-04-28T17:27:10.715Z"
modified: "2026-06-04T15:04:09.894Z"
---

# CNX.6.9.7.1 – Brain-Driven_Success_System_Full_Course_Curriculum_Outline.docx

Brain-Driven Success System: Full Course Curriculum Outline
________________


📚 Course Name
Brain-Driven Success System: Reset Your Filters, Reset Your Future
________________


🏠 Overall Promise
Train your brain to spot, seize, and scale opportunities by rewiring your invisible mental filters.
Shift from fear-based survival thinking to magnetic growth-focused action.
________________


🔄 Course Structure
Module
	Title
	Key Transformation
	1
	Understanding Brain Filters
	Awareness of how RAS filters reality and limits success
	2
	Resetting Your Emotional Drivers
	Reprogramming emotions to support opportunity spotting
	3
	Training Opportunity Detection
	Daily practices to tune your RAS for success
	4
	Building Momentum Through Daily Resets
	Compound small wins to retrain your filters
	5
	Expanding to Magnetic Growth Filters
	Lock in expansion thinking for unstoppable growth
	________________


📈 Module Progression Logic
* Awareness First: You can't reset what you don't see.

* Emotional Foundation Second: Feelings prime perception.

* Daily Practices Third: Repetition = rewiring.

* Momentum Fourth: Small wins create brain trust loops.

* Expansion Fifth: Lock in magnetic success and contribution filters.

________________


👁️ Ideal Completion Outcome
By the end of this program, students will:
   * Naturally spot high-leverage opportunities

   * Take bold, aligned action with less hesitation

   * Build internal emotional stability and confidence

   * Create a self-sustaining success mindset and environment

________________


📚 Module 1: Understanding Brain Filters
      * Lesson 1: The Invisible Editor (RAS and perception)

      * Lesson 2: How fear and survival bias your reality

      * Lesson 3: The science of filter resetting (neuroplasticity)

      * Exercise: "My Current Filter Inventory"

📚 Module 2: Resetting Your Emotional Drivers
         * Lesson 1: The chemistry of fear vs growth

         * Lesson 2: Emotional tagging and RAS rewiring

         * Lesson 3: Building your emotional reframe habits

         * Exercise: Daily Emotion Reframe Tracker

📚 Module 3: Training Opportunity Detection
            * Lesson 1: The Opportunity Blindness Effect

            * Lesson 2: Practical techniques to tune your focus

            * Lesson 3: Opportunity journaling system

            * Exercise: Daily Opportunity Tracker Launch

📚 Module 4: Building Momentum Through Daily Resets
               * Lesson 1: Micro-wins and dopamine loops

               * Lesson 2: The 5-minute Brain Reset Ritual

               * Lesson 3: Layering habits for compounding confidence

               * Exercise: 30-Day Brain Reset Challenge

📚 Module 5: Expanding to Magnetic Growth Filters
                  * Lesson 1: The shift from survival to contribution

                  * Lesson 2: Designing your future reality intentionally

                  * Lesson 3: Locking in your Magnetic Filter Blueprint

                  * Exercise: North Star Visualization Ritual

________________

Respond to all ten objections to $97-per-month coaching

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Lesson outcome and source boundaries

You will learn to distinguish the ten objections in the assigned document, ask a useful question about each, and offer a next step that fits the person's situation. The source provides ten customer statements. It supplies no response scripts, product feature list, cancellation terms, refund policy or results evidence. Every question, response and exercise below is an authored RISER application, not a recovered quotation or an approved company policy.

The $97 monthly price belongs to this source scenario. It does not establish the current price of any live RISER product. Before using these responses operationally, check the actual offer, available support and written terms.

A conversation structure that respects the answer

Listen to the statement, clarify the specific obstacle, explain only the relevant verified facts, and agree on an optional next step. A customer can reasonably decline. Do not turn every objection into a problem with the customer's mindset.

This is an authored application of the direct-response themes used elsewhere in this curriculum. A clear hook names the actual concern, a relevant story or example explains a possible path, and the offer states what is really available. In applying the outcome, confidence, time and effort considerations discussed in the course's Hormozi material, investigate what the person needs rather than claiming that a persuasive response guarantees a sale. None of the ten objections identifies its own underlying cause with certainty.

1. “I can’t afford $97/month.”

Start by taking the budget constraint seriously. Ask, “Would this payment put pressure on money you need for other priorities?” You do not need their private financial details to accept that the answer may be yes.

An appropriate response is, “If this does not fit your budget, let's not commit to the monthly payment. I can explain any genuinely available lower-cost resources so you can decide whether they help.” Offer such a resource only if it exists. Do not invent an installment plan, imply that future business income will cover the fee, or pressure someone to borrow. The next step may be a free resource, a later self-directed review, or a clear decision not to enroll.

2. “I’m not seeing results.”

Ask, “Which result were you expecting, what have you tried, and over what period?” This separates an unclear promise, a delivery problem, a missing prerequisite and a mismatch between the program and the person's goal. Listen before attributing the outcome to effort.

A possible response is, “Let's compare what was promised with what you received and what happened. Then we can identify whether there is a useful adjustment or whether this program is not serving your needs.” Review one concrete work sample and one agreed measure if the person wants to. A review is not a new guarantee. Handle any actual service or terms issue according to the verified agreement; do not promise a refund or extra coaching without authority.

3. “I don’t have time to attend the coaching calls.”

Ask whether the conflict is the scheduled time, the total workload, or both. A person might have time for short independent tasks but never be available at the live-call time.

Respond, “The live schedule may not fit your availability. Here is the actual schedule and any alternative access that this offer includes.” Mention recordings, asynchronous questions or another session only after verifying them. If live participation is essential and no workable alternative exists, say so. The next step is to compare one realistic week with the actual requirements, rather than assuming the customer can rearrange everything.

4. “I’m not sure if this is the right fit for me.”

Ask, “What are you trying to accomplish, and what makes the fit uncertain?” Clarify the person's current stage, relevant prerequisites and desired type of help.

Respond with the verified scope: “This program covers these outcomes and requires these inputs. It does not currently cover the other need you described.” Use a short fit comparison or an existing sample lesson if available. The next step is a decision based on scope and readiness. Do not use a generic success story as proof that every buyer will fit.

5. “I can find similar content for free online.”

Agree that information may be available elsewhere. Ask, “Are you primarily looking for information, a sequence to follow, feedback, or help applying it?” The answer reveals whether paid delivery adds something the person values.

An authored response is, “If free material gives you what you need, that may be the right choice. The paid offer should earn its price through the specific help it actually provides.” Explain verified organization, feedback or access rather than claiming that free content is inferior. Compare the real alternatives without inflating the value of bonuses. A reasonable next step is to inspect a sample of the actual paid experience and decide whether the difference matters.

6. “I haven’t had the time to start the course.”

Ask, “Is the main barrier time, access, not knowing where to begin, or something else?” This is different from missing a live call: the customer has not begun the learning sequence at all.

Respond, “Let's identify the first useful action and its actual time requirement. If that still does not fit, we should acknowledge the constraint.” An authored example is choosing a brief orientation and writing one goal, but do not promise the course has a five-minute pathway unless it does. Offer technical access help only within actual support. Agree on a feasible first action, or discuss the customer's options under the real terms without inventing a pause policy.

7. “I don’t see the value in the coaching calls.”

Ask, “What would make a call useful to you, and what has your experience been so far?” Someone may already understand the information but need a specific kind of feedback that the call does not provide.

Respond, “Let's compare what you need with the call's actual format. If it supports that need, we can identify a concrete question or work sample to bring.” Explain the agenda, boundaries and available feedback accurately. Do not promise personalized consulting in a group Q&A unless that service exists. The next step can be testing the format against one defined need; if the format cannot help, acknowledge the mismatch.

8. “I’m not tech-savvy enough for this.”

Ask, “Which specific step or tool feels difficult?” Separate logging in, finding a lesson, joining a call, using a worksheet and implementing a business tool. Each may need different help.

Respond, “Let's check the requirements and work through the particular step using the support that is available.” Use plain instructions and a verified demonstration when possible. Do not promise done-for-you implementation, unrestricted technical support or an effortless platform. A useful next step is completing one supported access task and checking understanding. Never ask the customer to share a password to make that easier.

9. “I prefer in-person learning.”

Ask, “What part of in-person learning matters most to you: direct interaction, hands-on practice, accountability, or the setting?” This preference can be valid even when an online course is well designed.

Respond, “This offer's delivery format is what it is. I can explain any features that address your preference, but I cannot promise the same experience as being in the room.” Do not invent an in-person option or overstate online equivalence. The next step may be trying an existing sample experience or choosing a different format that better fits the learner.

10. “I’m already using other resources for my business.”

Ask, “What do those resources already cover well, and is there an important gap?” Avoid treating the mere presence of another resource as a reason to add more.

Respond, “If your current resources cover your needs, adding this program may be unnecessary. If there is a gap, we can compare that gap with what this offer actually provides.” An authored exercise is a simple list of needs, current coverage and any missing support. The next step should reflect a distinct benefit, capacity to use it and reasonable cost. Do not disparage a competitor or invent integrations to justify the purchase.

Practice: diagnose before answering

Work through all ten statements. For each, record the exact objection, one clarifying question, the verified offer fact you would need, your response, and a suitable next step. Mark an unknown fact as unknown. Include the possibility of declining or continuing with an existing resource.

In a role-play, evaluate whether the response addressed the specific concern, used accurate information, avoided an invented feature or result, and left the person free to choose. Do not grade success solely by whether the person agreed to buy. Revisit the program itself when repeated objections expose unclear scope, inaccessible delivery or an unmet need.

Sources and related course resources

- Assigned source: ten common objections to $97-per-month coaching. This is the complete ten-item source list, not a supplied response library. - Related assigned source: foundations, transformation and hook–story–offer. The related curriculum text informs the authored communication application; its attributed quotations are not independently authenticated here. - Related assigned source: seven-layer offer architecture. Use its support, safety, proof and price questions to examine the real offer. Its universal conversion claims are not guarantees.

The complete native and filed source text will accompany this teaching in the lesson appendix.

Assigned source links

D0458 original source 1

Complete native document body

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.
Complete local source copy including original filing metadata and formatting

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.

Read, reconcile and improve the Average Cart Value workbook

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Outcome and scope

Explain every scenario in the supplied five-tab workbook, identify the denominator and formula errors, and distinguish an illustrative funnel forecast from actual campaign results. The native workbook contains 484 populated cells, including 147 formulas, 160 merged regions and nine original images. The complete cell records, formulas, native values, images and filed text are preserved with this lesson. Source outputs remain unchanged; corrected examples are separate authored calculations.

The five tabs are 1 UPSELL, Sheet6, 2 UPSELLS, WEBINAR TAIL and Candle Business. The images and cells sometimes disagree. Some tiny text inside embedded advertisement and page screenshots is not legible at the supplied resolution; the original images remain available without invented transcription. Two linked PDF resources could not be retrieved and remain explicit gaps.

Start with the eight named metrics

The workbook lists ROAS, AOV, ACV, LTV, MRR, CTR, CPC and CPA. Return on ad spend, ROAS, compares attributed revenue with ad spend. Its 2:1 example means two dollars of revenue per dollar of ad spend, not two dollars of profit. Average order value, AOV, needs a defined set of orders and the corresponding revenue. Average cart value, ACV, is used here for an average customer's initial funnel purchases, but the workbook inconsistently mixes averages and campaign totals. State the denominator before calculating.

Lifetime value, LTV, extends beyond the initial order over a defined relationship horizon. Monthly recurring revenue, MRR, concerns the recurring revenue basis for a month; an isolated upsell is not automatically recurring. Clickthrough rate, CTR, is clicks divided by impressions, as explained by Google Ads. Cost per click, CPC, is the relevant click cost divided by clicks. CPA must name the action or acquisition: Google defines average cost per action using total cost divided by the corresponding conversions. See Google's CPA definition. A conversion may be a lead or another action, so do not silently equate every platform conversion with an acquired customer.

The workbook repeatedly labels CPC divided by clicks as CTR. That is not a clickthrough rate, and there are no impression inputs to calculate one. It labels clicks divided by ad spend as CPA, which has inverted units and no acquisition count. Preserve those formulas in the original ledger, but do not teach their results as valid metrics.

Trace 1 UPSELL's first scenario

The tab describes shipping information, an initial purchase shown as $9.99 or $54.95, a $37 order bump and a $47 one-time offer. Other labels use $9.95, $54.94 or $54.95, so the original does not consistently state its base prices. Its initial ACV input is $22.33; the source does not supply the purchase mix needed to derive it from the alternative prices.

At 1,000 clicks and $0.35 CPC, the sheet calculates $350 ad spend. Fifteen percent entering shipping details yields 150 people. A 3.5% purchase rate among those people yields 5.25 expected buyers. Fractional buyers can appear in a forecast; they are not observed people. The sheet then applies a 10.2% bump rate to get 0.5355 expected bump buyers, and an 11% OTO rate to those bump buyers to get 0.058905 OTO buyers.

That final dependency assumes only bump buyers form the OTO population. It is not the same as an 11% OTO rate among all initial buyers. Establish who sees the offer and which population the rate describes before choosing the multiplication.

The sheet's D32 adds bump-buyer count times $37 to $22.33 and calls the result $42.1435 average cart value. This mixes campaign dollars with dollars per customer. F32 then multiplies that cumulative amount by bump buyers, counting the base amount again. D35/F35 repeat the count-and-average mixture for the OTO. As a result, the source displays revenue $142.45 and a revenue-minus-ads result of −$207.55. These are outputs of the supplied formulas, not validated campaign economics.

Compare the 5,000- and 10,000-click scenarios

The next two blocks retain $0.35 CPC, 15% shipping entry, 3.5% initial purchase, $22.33 base ACV, 10.2% at $37 for the bump and 11% at $47 for the OTO. At 5,000 clicks, spend is $1,750, shipping entries 750, initial buyers 26.25, bump buyers 2.6775 and chained OTO buyers 0.294525. The source's flawed formulas display revenue $951.04 and a residual of −$798.96.

At 10,000 clicks, spend is $3,500, shipping entries 1,500, initial buyers 52.5, bump buyers 5.355 and chained OTO buyers 0.58905. The source displays revenue $2,499.09 and residual −$1,000.91. Its supposed average cart value grows to $248.15035 simply through scaling the same rates and offer inputs. That is a useful diagnostic: an unchanged per-customer average should not grow merely because the same model has more visitors.

The tab also asserts industry ACV of $30–35 for free-plus-shipping and CPA of $5–25. It supplies no dated dataset or matching audience definition. Keep these as source assertions, not universal targets.

Build a separate, explicitly assumed correction

As an authored illustration, assume every initial buyer can take both the bump and OTO, and that 10.2% and 11% are rates among that same initial-buyer population. Expected initial buyers are 1,000 × 0.15 × 0.035 = 5.25. ACV is $22.33 + 0.102 × $37 + 0.11 × $47 = $31.274. Expected revenue is 5.25 × $31.274 = $164.1885. Subtracting $350 ad spend gives −$185.8115 before other costs. Acquisition cost per initial buyer is $350 ÷ 5.25, approximately $66.67.

If only bump buyers can take the OTO, its per-initial-buyer contribution is instead 0.102 × 0.11 × $47 = $0.52734. Use that different dependency consistently. Neither interpretation is established by a label alone. In an actual model, reconcile the population, period, refunds, revenue definition and costs to business records.

Understand Sheet6's different model

Sheet6 lists four ad CPAs of $8.51, $6.01, $8.21 and $12.21. Its G4 averages them without weights to get $8.735. Overall CPA should be derived from matching total cost and acquisitions; an unweighted mean is appropriate only under the relevant equal-weight conditions.

The tab's price cells include $4.95 and $54.95, which it adds to $59.90. This conflicts with other initial-price labels and assumes alternative options can be added together. A weighted price mix requires purchase counts or proportions, not an unqualified sum of alternatives.

Its four conversion rates are 15.6%, 3.5%, 10.2% and 11%. At 1,000 visitors it calculates 156 first-step entries, 5.46 initial buyers, 0.55692 bump buyers and 0.0612612 chained OTO buyers. The component amounts shown are $2.0965, $3.774 and $5.17. H11 averages those three amounts to $3.6801667 while labeling the result ACV TOTAL. That average is not the sum implied by the label. F12 references blank E13 and F11, and F14 uses a buyer count where the comparable cells use a rate; both currently yield zero. These are structural issues, not proof of zero demand for a fifth offer.

Read both 2 UPSELLS scenarios

The first block uses 1,000 clicks, $0.35 CPC, 15% shipping entry, 3.5% purchase and $22.33 initial ACV. It adds a 10.2% $37 bump, an 11% $47 OTO and a 10% $197 second upsell, chaining each later buyer count to the previous purchaser count. It produces 5.25 initial buyers, 0.5355 bump buyers, 0.058905 OTO buyers and 0.0058905 second-upsell buyers. The sheet displays revenue $143.61 and residual −$206.39 using its flawed cumulative formulas.

The second block keeps traffic, initial purchase and prices the same but uses a 17% bump and 21.5% OTO. It produces 0.8925 bump buyers, 0.1918875 OTO buyers and 0.01918875 second-upsell buyers. It displays revenue $182.77 and residual −$167.23. Again, preserve the original results while correcting the count-versus-average issue before drawing an economic conclusion. The native images instead use 17.4% and a 4.5% second upsell in examples; those are different inputs, not interchangeable evidence.

Inspect WEBINAR TAIL

The heading says 1,000 visitors, but the actual click input is 10,000, making ad spend $3,500 at $0.35 CPC. The block uses 15% shipping entry, 3.5% initial purchase, $22.33 base ACV, a 17% $37 bump, a 21.5% $47 OTO, a 10% $197 second upsell and a 4.5% $2,000 webinar offer.

Its chain yields 52.5 initial buyers, 8.925 bump buyers, 1.918875 OTO buyers, 0.1918875 second-upsell buyers and 0.0086349375 webinar buyers. That final forecast follows second-upsell purchasers, not a supplied webinar registration or attendance population. The file supplies no separate show-up rate for this calculation.

The source displays $5,223.52 revenue and $1,723.52 residual. Its cumulative-average errors are still present. Do not interpret that displayed positive residual as evidence the webinar makes the funnel profitable. Correct the formulas, reconcile the 1,000/10,000 heading conflict and identify the actual webinar denominator first.

Inspect Candle Business and its lotion-bar examples

The tab title says Candle Business, while its imagery and narrative concern lotion bars. The click input is 1,000 and CPC $0.35, but ad cost is hardcoded $68.45 rather than the implied $350. The formula 1,000 ÷ $68.45 returns $14.6092 under the CPA label, repeating the inverted-unit error.

Shipping entry is 7.19%, purchase rate 34.5%, base ACV $37.58 and expected initial buyers 24.8055. The bump rate is 19% with a $1.01 price input. The OTO rate is 34.37% with a $0.41 input, but D40 ignores that rate and copies all initial buyers. The final upsell uses 4.75% and $2.26. The source does not explain those small price inputs relative to the much larger pictured offer prices.

The cumulative formulas produce $2,436.95 revenue and $2,368.50 after the hardcoded ad cost. These are not verified business results. Reconcile the price inputs, ignored conversion rate, spend conflict and count/average arithmetic. Do not call revenue minus advertising “gross profit” without the relevant cost-of-sales treatment; it is also not net profit.

Teach the original diagrams as separate source examples

Images 1–3 show the one-upsell illustration and enlarged parts. Their five pictured ad CPAs are $8.51, $6.01, $8.21, $12.21 and $5.06. The sketch shows shipping, credit-card purchase with $9.95/$54.95, $37 bump and $47 OTO. Rates are 15.6%, 3.5%, 10.2% and 11%. The right-hand example has CPA $9.17, increments $0/$22.33/$3.77/$5.17, ACV $31.27 and subtraction $22.10. These image values differ from several cell inputs and formulas. The diagram alone does not establish all denominators or the method producing the stated CPA.

Image 4 adds the $197 second upsell, changes the bump rate to 17.4% and shows a 4.5% second-upsell rate. Its increments are $0/$22.33/$6.44/$5.17/$8.87, total $42.80, CPA $7.14 and residual $35.66. The other rate labels remain 15.6%, 3.5% and 11%. The result is a supplied illustration; traffic counts and attribution evidence are absent.

Image 9 shows a later version with the OTO rate at 21.5%, CPA $23.79, stated ACV $47.55 and residual $23.76. Its other rates are 15.6%, 3.5%, 17.4% and 4.5%; displayed increments are $0/$22.33/$6.44/$9.92/$8.87. The $9.92 increment does not equal $47 × 21.5% = $10.105, and the displayed nonzero increments total $47.56 rather than $47.55. Preserve these differences.

The image 9 prose says simplifying the offer, making it as free as possible and easier to follow moved conversion from 11% to 21.5%, while acknowledging increased CPA. The example does not prove causation. Comparing the supplied residuals, $35.66 in image 4 versus $23.76 in image 9, shows why a higher headline conversion can coexist with a worse acquisition contribution. Other costs remain unreported.

Read Jamie's narrative and both diagram versions

Image 5 says Jamie runs three ads and sells a lotion bar rather than a free-plus-shipping book offer. Images 6 and 8 show four ad CPAs: $10.87, $12.76, $19.50 and $15.29. The narrative reports CPA $14.61, 7.19% shipping entry and 34.5% initial purchase, with $37.58 front-end ACV. It describes selling more of the same on the next page at 19%, adding $4.73; a second upsell at 34.37%, adding $9.76; and a final offer at 4.75%, adding $3.07.

The diagrams show 4.25% for that final rate, not 4.75%. Their upsell sketches include WAIT messages and $39/$49 then $49/$24 option prices, followed by BEFORE YOU LEAVE / ADD TO ORDER. The diagrams report ACV $55.15 less $14.61 CPA = $40.54. The listed increments sum $55.14; underlying rounding might explain the cent, but the source does not establish it.

The narrative says results followed testing and proposes examining the 19% upsell for improvement and brainstorming changes. Use that as a prompt to investigate, not a rule that the numerically smallest percentage is necessarily the most valuable improvement. The stages may have different denominators, costs and constraints. Its claim that more-of-the-same upsells work for all ecommerce is unsupported. Retain both original diagram versions and all narrative text; small screenshot copy that cannot be read is not reconstructed.

Evaluate all ten asserted benchmarks

Image 7 lists lead opt-ins >20%; two-step opt-ins >10–15%; tripwire sales conversion >1–5%; order bumps >20%; OTO/downsell conversions >3–15%; live webinar show-up >10–20%; automated webinar show-up >50–80%; hot-traffic live webinar buying >10%; cold-traffic live webinar buying >1–5%; and automated webinar buying >3–8%.

The greater-than-plus-range notation is preserved from the source and is not a precise statistical threshold. These are unverified suggested benchmarks without a supplied dataset, date, denominator, attribution window or comparable audience. Define what counts as an opt-in, show-up or buyer and use your own relevant evidence before setting a target. A higher rate can still produce worse economics if acquisition or fulfillment costs change.

Turn the review into a useful offer test

The Brunson/ClickFunnels application is to inspect each transition and clarify the hook, story and offer where a real customer need is unmet. The Hormozi application is to improve useful value and delivery while checking economics. Neither framework justifies a guaranteed conversion lift or a broken revenue model.

As an authored exercise, choose one scenario and preserve its original formulas. In a separate calculation, define the buyer population at every stage, keep incremental revenue separate from cumulative averages, compute matching acquisition costs, and record the costs still missing. Change one justified input and explain how the result should change. Do not activate ads or purchase traffic as part of reading this lesson.

For every test, identify the customer question, proposed change, observation window, denominator, costs and decision rule. Keep observed results separate from expected fractional buyers. Preserve conflicting source inputs rather than blending them into an undocumented hybrid.

Sources, complete records and access gaps

- Assigned Average Cart Value spreadsheet, including all five native tabs. - Funnel Audibles transcript PDF named in cell A1: retrieval was blocked by the browser tool's URL policy; its contents have not been reviewed. - Funnel Audibles workbook PDF named in cell G6: the same access gap applies. A clickable link is not proof the linked text was incorporated. - Related real-estate LTV source, with a separate lesson addressing lifetime-versus-annual frequency and referral assumptions. - Related offer architecture source.

The appendix retains the complete native cell ledger, original formulas, source values, merged-grid structure, nine images and their readable-content review, original XLSX and complete filed source copy. Native-versus-export input and formula comparisons match for all 484 populated cells; 32 cached-result differences reflect export rounding and remain recorded. That comparison proves preservation, not that the original formulas are correct.

Assigned source links

D0459 original source 1

Original tables, images and embedded resource links

Original spreadsheet grids retain source values, blank cells inside the used region and merged regions. These source calculations contain errors explained in the lesson. Original full-grid dimensions and image anchors are recorded below; original XLSX preserves native layout. Formula text is in the complete cell ledger.

1 UPSELL

Native allocated grid 999 rows × 26 columns; populated/merged region rendered through K89.

1 UPSELL — original displayed values, not corrected results
https://s3content.s3.amazonaws.com/30_Day_Summit/Funnel_Audibles_Transcripts.pdf
COST PER AQUISITION
AVERAGE CART VALUE
ACV Industry Average for "Free Plus Shipping $30-35"https://s3content.s3.amazonaws.com/30_Day_Summit/Funnel_Audibles_Final.pdf
WORKBOOK
BELOW IS A SIMPLE 4 STEP FUNNEL
FREE PLUS SHIPPINGR.O.A.S.Return On Ad Spend2:1$2 Income/$1 Spend
A.O.VAverage Order Value
1.)Shipping InfoA.C.VAverage Cart Value
2.)PURCHASE $9.99 or ($54.95)L.T.V.Lifetime Value
3.)Order Bump $37M.R.R.Monthly Recurring Revenue
4.) One Time Offer $47C.T.RClick Trough Rate
C.P.CCost Per Click
SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFERC.P.A.Cost Per Aquistion
CTR0.04%(Click Through Rate)
CPC$0.35(Cost Per Click)
TOTAL CLICKS1000(LEADS)
AD COST$350.00
CPA$2.86(Cost Per Aquisition)
NUMBER OF VISITORS1000
PERCENTAGE ENTERED SHIPPING DETAILS15.00%
TOTAL NUMBER OF CUSTOMERS TO STEP #2150
PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 23.50%
TOTAL NUMBER OF BUYERS5.25
AVERAGE CART VALUE ($9.95 plus $54.94)$22.33$117.23
PERCENTAGE OF BUYERS BUY ORDER BUMP10.20%$37.00
TOTAL NUMBER OF BUYERS OF ORDER BUMP0.5355
AVERAGE CART VALUE AFTER ORDER BUMP$42.14$22.57
PERCENTAGE OF BUYERS BUY ONE TIME OFFER11.00%$47.00
TOTAL NUMBER OF ONE TIME OFFER BUYERS0.058905
TOTAL AVERAGE CART VALUE$44.91$2.65
TOTAL REVENUE FROM CAMPAIGN$142.45
TOTAL AD COST$350.00
GROSS PROFIT-$207.55
SO IF I ATTRACTED 5000 VISITORS/LEADS TO THIS OFFER
CTR0.01%(Click Through Rate)
CPC$0.35(Cost Per Click)
TOTAL CLICKS5000(LEADS)
AD COST$1,750.00
CPA$2.86(Cost Per Aquisition)INDUSTRY AVERAGE $5-$25/CPA
NUMBER OF VISITORS5000
PERCENTAGE ENTERED SHIPPING DETAILS15.00%
TOTAL NUMBER OF CUSTOMERS TO STEP #2750
PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 23.50%
TOTAL NUMBER OF BUYERS26.25
AVERAGE CART VALUE ($9.95 plus $54.94)$22.33$586.16
PERCENTAGE OF BUYERS BUY ORDER BUMP10.20%$37.00
TOTAL NUMBER OF BUYERS OF ORDER BUMP2.6775
AVERAGE CART VALUE AFTER ORDER BUMP$121.40$325.04
PERCENTAGE OF BUYERS BUY ONE TIME OFFER11.00%$47.00
TOTAL NUMBER OF ONE TIME OFFER BUYERS0.294525
TOTAL AVERAGE CART VALUE$135.24$39.83
TOTAL REVENUE FROM CAMPAIGN$951.04
TOTAL AD COST$1,750.00
GROSS PROFIT-$798.96
SO IF I ATTRACTED 10000 VISITORS/LEADS TO THIS OFFER
CTR0.00%(Click Through Rate)
CPC$0.35(Cost Per Click)
TOTAL CLICKS10000(LEADS)
AD COST$3,500.00
CPA$2.86(Cost Per Aquisition)
NUMBER OF VISITORS10000
PERCENTAGE ENTERED SHIPPING DETAILS15.00%
TOTAL NUMBER OF CUSTOMERS TO STEP #21500
PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 23.50%
TOTAL NUMBER OF BUYERS52.50
AVERAGE CART VALUE ($9.95 plus $54.94)$22.33$1,172.33
PERCENTAGE OF BUYERS BUY ORDER BUMP10.20%$37.00
TOTAL NUMBER OF BUYERS OF ORDER BUMP5.355
AVERAGE CART VALUE AFTER ORDER BUMP$220.47$1,180.59
PERCENTAGE OF BUYERS BUY ONE TIME OFFER11.00%$47.00
TOTAL NUMBER OF ONE TIME OFFER BUYERS0.58905
TOTAL AVERAGE CART VALUE$248.15$146.17
TOTAL REVENUE FROM CAMPAIGN$2,499.09
TOTAL AD COST$3,500.00
GROSS PROFIT-$1,000.91
Original 1 UPSELL artwork image3.png; readable data and conflicts are explained in the lesson and image review appendix. Tiny embedded screenshot text may be unreadable.
1 UPSELL / image3.png; native anchor (zero-based): {"col": 4, "colOff": 85725, "row": 16, "rowOff": 152400} to null
Original 1 UPSELL artwork image2.png; readable data and conflicts are explained in the lesson and image review appendix. Tiny embedded screenshot text may be unreadable.
1 UPSELL / image2.png; native anchor (zero-based): {"col": 2, "colOff": 85725, "row": 8, "rowOff": 9525} to null
Original 1 UPSELL artwork image7.png; readable data and conflicts are explained in the lesson and image review appendix. Tiny embedded screenshot text may be unreadable.
1 UPSELL / image7.png; native anchor (zero-based): {"col": 6, "colOff": 0, "row": 0, "rowOff": 0} to null

Sheet6

Native allocated grid 968 rows × 28 columns; populated/merged region rendered through H14.

Sheet6 — original displayed values, not corrected results
AD C.P.A.CART VALUE
AD # 1STEP 1STEP 2STEP 3STEP 4STEP 5AVERAGE AD C.P.A.
$8.51Adderess2 Step$8.74
AD #24.953747AVERAGE CART VALUE
$6.0154.951.)0
AD #32.)$2.10
$8.213.)$3.77
AD #44.)$5.17
$12.21$0.00$59.90$37.00$47.00$0.005.)$0.00
Conv Rates15.60%3.50%10.20%11.00%ACV TOTAL$3.68
VISITORS/Buyers10005.460.556920.06126120
156
CART TOTAL$2.10$3.77$5.17$0.00
Original Sheet6 artwork image1.png; readable data and conflicts are explained in the lesson and image review appendix. Tiny embedded screenshot text may be unreadable.
Sheet6 / image1.png; native anchor (zero-based): {"col": 0, "colOff": 247650, "row": 16, "rowOff": 85725} to null

2 UPSELLS

Native allocated grid 1003 rows × 26 columns; populated/merged region rendered through F98.

2 UPSELLS — original displayed values, not corrected results
SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER
CTR0.04%(Click Through Rate)
CPC$0.35(Cost Per Click)
TOTAL CLICKS1000(LEADS)
AD COST$350.00
CPA$2.86(Cost Per Aquisition)
NUMBER OF VISITORS1000TOTAL REVENUE
PERCENTAGE ENTERED SHIPPING DETAILS15.00%
TOTAL NUMBER OF CUSTOMERS TO STEP #2150
PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 23.50%
TOTAL NUMBER OF BUYERS5.25
AVERAGE CART VALUE ($9.95 plus $54.94)$22.33$117.23
PERCENTAGE OF BUYERS BUY ORDER BUMP10.20%$37.00
TOTAL NUMBER OF BUYERS OF ORDER BUMP0.5355
AVERAGE CART VALUE AFTER ORDER BUMP$42.14$22.57
PERCENTAGE OF BUYERS BUY ONE TIME OFFER11.00%$47.00
TOTAL NUMBER OF ONE TIME OFFER BUYERS0.06
AVERAGE CART VALUE AFTER ONE TIME OFFER$44.91$2.65
PERCENTAGE OF BUYERS BUY 2nd Upsell10.00%$197.00
TOTAL NUMBER OF 2nd Upsell Buyers0.0058905
TOTAL AVERAGE CART VALUE after 2nd Upsell$46.07$1.16
TOTAL REVENUE FROM CAMPAIGN$143.61
TOTAL AD COST$350.00
GROSS PROFIT-$206.39
SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER
CTR0.04%(Click Through Rate)
CPC$0.35(Cost Per Click)
TOTAL CLICKS1000(LEADS)
AD COST$350.00
CPA$2.86(Cost Per Aquisition)
NUMBER OF VISITORS1000TOTAL REVENUE
PERCENTAGE ENTERED SHIPPING DETAILS15.00%
TOTAL NUMBER OF CUSTOMERS TO STEP #2150
PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 23.50%
TOTAL NUMBER OF BUYERS5.25
AVERAGE CART VALUE ($9.95 plus $54.94)$22.33$117.23
PERCENTAGE OF BUYERS BUY ORDER BUMP17.00%$37.00
TOTAL NUMBER OF BUYERS OF ORDER BUMP0.8925
AVERAGE CART VALUE AFTER ORDER BUMP$55.35$49.40
PERCENTAGE OF BUYERS BUY ONE TIME OFFER21.50%$47.00
TOTAL NUMBER OF ONE TIME OFFER BUYERS0.19
AVERAGE CART VALUE AFTER ONE TIME OFFER$64.37$12.35
PERCENTAGE OF BUYERS BUY 2nd Upsell10.00%$197.00
TOTAL NUMBER OF 2nd Upsell Buyers0.01918875
TOTAL AVERAGE CART VALUE after 2nd Upsell$68.15$3.78
TOTAL REVENUE FROM CAMPAIGN$182.77
TOTAL AD COST$350.00
GROSS PROFIT-$167.23
Original 2 UPSELLS artwork image4.png; readable data and conflicts are explained in the lesson and image review appendix. Tiny embedded screenshot text may be unreadable.
2 UPSELLS / image4.png; native anchor (zero-based): {"col": 0, "colOff": 0, "row": 2, "rowOff": 0} to null
Original 2 UPSELLS artwork image9.png; readable data and conflicts are explained in the lesson and image review appendix. Tiny embedded screenshot text may be unreadable.
2 UPSELLS / image9.png; native anchor (zero-based): {"col": 0, "colOff": 0, "row": 49, "rowOff": 0} to null

WEBINAR TAIL

Native allocated grid 1003 rows × 26 columns; populated/merged region rendered through F50.

WEBINAR TAIL — original displayed values, not corrected results
WEBINAR ADDED
SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER
CTR0.00%(Click Through Rate)
CPC$0.35(Cost Per Click)
TOTAL CLICKS10000(LEADS)
AD COST$3,500.00
CPA$2.86(Cost Per Aquisition)
NUMBER OF VISITORS10000TOTAL REVENUE
PERCENTAGE ENTERED SHIPPING DETAILS15.00%
TOTAL NUMBER OF CUSTOMERS TO STEP #21500
PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 23.50%
TOTAL NUMBER OF BUYERS52.50
AVERAGE CART VALUE ($9.95 plus $54.94)$22.33$1,172.33
PERCENTAGE OF BUYERS BUY ORDER BUMP17.00%$37.00
TOTAL NUMBER OF BUYERS OF ORDER BUMP8.925
AVERAGE CART VALUE AFTER ORDER BUMP$352.56$3,146.55
PERCENTAGE OF BUYERS BUY ONE TIME OFFER21.50%$47.00
TOTAL NUMBER OF ONE TIME OFFER BUYERS1.92
AVERAGE CART VALUE AFTER ONE TIME OFFER$442.74$849.57
PERCENTAGE OF BUYERS BUY 2nd Upsell10.00%$197.00
TOTAL NUMBER OF 2nd Upsell Buyers0.1918875
TOTAL AVERAGE CART VALUE after 2nd Upsell$480.54$37.80
PERCENTAGE OF BUYERS BUY WEBINAR4.50%$2,000.00
TOTAL NUMBER OF WEBINAR BUYERS0.0086349375
TOTAL AVERAGE CART VALUE after WEBINAR$497.81$17.27
TOTAL REVENUE FROM CAMPAIGN$5,223.52
TOTAL AD COST$3,500.00
GROSS PROFIT$1,723.52
Original WEBINAR TAIL artwork image8.png; readable data and conflicts are explained in the lesson and image review appendix. Tiny embedded screenshot text may be unreadable.
WEBINAR TAIL / image8.png; native anchor (zero-based): {"col": 0, "colOff": 0, "row": 2, "rowOff": 0} to null

Candle Business

Native allocated grid 997 rows × 26 columns; populated/merged region rendered through F47.

Candle Business — original displayed values, not corrected results
SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER
CTR0.04%(Click Through Rate)
CPC$0.35(Cost Per Click)
TOTAL CLICKS1000(LEADS)
AD COST68.45
CPA$14.61(Cost Per Aquisition)
NUMBER OF VISITORS1000TOTAL REVENUE
PERCENTAGE ENTERED SHIPPING DETAILS7.19%
TOTAL NUMBER OF CUSTOMERS TO STEP #271.9
PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 234.50%
TOTAL NUMBER OF BUYERS24.81
AVERAGE CART VALUE $37.58$932.19
PERCENTAGE OF BUYERS BUY ORDER BUMP19.00%$1.01
TOTAL NUMBER OF BUYERS OF ORDER BUMP4.713045
AVERAGE CART VALUE AFTER ORDER BUMP$42.34$199.55
PERCENTAGE OF BUYERS BUY ONE TIME OFFER34.37%$0.41
TOTAL NUMBER OF ONE TIME OFFER BUYERS24.81
AVERAGE CART VALUE AFTER ONE TIME OFFER$52.51$1,302.55
PERCENTAGE OF BUYERS BUY 2nd Upsell4.75%$2.26
TOTAL NUMBER OF 2nd Upsell Buyers1.17826125
TOTAL AVERAGE CART VALUE after 2nd Upsell$55.17$2.66
TOTAL REVENUE FROM CAMPAIGN$2,436.95
TOTAL AD COST68.45
GROSS PROFIT$2,368.50
Original Candle Business artwork image6.png; readable data and conflicts are explained in the lesson and image review appendix. Tiny embedded screenshot text may be unreadable.
Candle Business / image6.png; native anchor (zero-based): {"col": 0, "colOff": 0, "row": 2, "rowOff": 0} to null
Original Candle Business artwork image5.png; readable data and conflicts are explained in the lesson and image review appendix. Tiny embedded screenshot text may be unreadable.
Candle Business / image5.png; native anchor (zero-based): {"col": 6, "colOff": 0, "row": 11, "rowOff": 0} to null
Complete native cell ledger: all populated cells and formulas with displayed results

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


## 1 UPSELL
A1: 'https://s3content.s3.amazonaws.com/30_Day_Summit/Funnel_Audibles_Transcripts.pdf' LINK https://s3content.s3.amazonaws.com/30_Day_Summit/Funnel_Audibles_Transcripts.pdf
A3: 'COST PER AQUISITION'
A5: 'AVERAGE CART VALUE'
A6: 'ACV Industry Average for "Free Plus Shipping $30-35"'
G6: 'https://s3content.s3.amazonaws.com/30_Day_Summit/Funnel_Audibles_Final.pdf' LINK https://s3content.s3.amazonaws.com/30_Day_Summit/Funnel_Audibles_Final.pdf
G7: 'WORKBOOK'
A8: 'BELOW IS A SIMPLE 4 STEP FUNNEL'
A9: 'FREE PLUS SHIPPING'
G9: 'R.O.A.S.'
H9: 'Return On Ad Spend'
J9: '2:1'
K9: '$2 Income/$1 Spend'
G10: 'A.O.V'
H10: 'Average Order Value'
A11: '1.)Shipping Info'
G11: 'A.C.V'
H11: 'Average Cart Value'
A12: '2.)PURCHASE $9.99 or ($54.95)'
G12: 'L.T.V.'
H12: 'Lifetime Value'
A13: '3.)Order Bump $37'
G13: 'M.R.R.'
H13: 'Monthly Recurring Revenue'
A14: '4.) One Time Offer $47'
G14: 'C.T.R'
H14: 'Click Trough Rate'
G15: 'C.P.C'
H15: 'Cost Per Click'
A16: 'SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER'
G16: 'C.P.A.'
H16: 'Cost Per Aquistion'
A18: 'CTR'
B18: '=sum(B19/B20)' => '0.04%'
C18: '(Click Through Rate)'
A19: 'CPC'
B19: 0.35
C19: '(Cost Per Click)'
A20: 'TOTAL CLICKS'
B20: 1000
C20: '(LEADS)'
A21: 'AD COST'
B21: '=sum(B20*B19)' => '$350.00'
A22: 'CPA'
B22: '=sum(B20/B21)' => '$2.86'
C22: '(Cost Per Aquisition)'
A24: 'NUMBER OF VISITORS'
D24: '=sum(B20)' => '1000'
A25: 'PERCENTAGE ENTERED SHIPPING DETAILS'
D25: 0.15
A26: 'TOTAL NUMBER OF CUSTOMERS TO STEP #2'
D26: '=sum(D24*D25)' => '150'
A27: 'PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2'
D27: 0.035
A28: 'TOTAL NUMBER OF BUYERS'
D28: '=sum(D26*D27)' => '5.25'
A29: 'AVERAGE CART VALUE ($9.95 plus $54.94)'
D29: 22.33
F29: '=sum(D28*D29)' => '$117.23'
A30: 'PERCENTAGE OF BUYERS BUY ORDER BUMP'
D30: 0.102
E30: 37
A31: 'TOTAL NUMBER OF BUYERS OF ORDER BUMP'
D31: '=sum(D28*D30)' => '0.5355'
A32: 'AVERAGE CART VALUE AFTER ORDER BUMP'
D32: '=sum(D31*E30)+D29' => '$42.14'
F32: '=sum(D31*D32)' => '$22.57'
A33: 'PERCENTAGE OF BUYERS BUY ONE TIME OFFER'
D33: 0.11
E33: 47
A34: 'TOTAL NUMBER OF ONE TIME OFFER BUYERS'
D34: '=sum(D31*D33)' => '0.058905'
A35: 'TOTAL AVERAGE CART VALUE'
D35: '=sum(D34*E33)+D32' => '$44.91'
F35: '=sum(D34*D35)' => '$2.65'
A36: 'TOTAL REVENUE FROM CAMPAIGN'
F36: '=sum(F29+F32+F35)' => '$142.45'
A37: 'TOTAL AD COST'
F37: '=sum(B21)' => '$350.00'
A38: 'GROSS PROFIT'
F38: '=sum(F36-F37)' => '-$207.55'
A41: 'SO IF I ATTRACTED 5000 VISITORS/LEADS TO THIS OFFER'
A43: 'CTR'
B43: '=sum(B44/B45)' => '0.01%'
C43: '(Click Through Rate)'
A44: 'CPC'
B44: 0.35
C44: '(Cost Per Click)'
A45: 'TOTAL CLICKS'
B45: 5000
C45: '(LEADS)'
A46: 'AD COST'
B46: '=sum(B45*B44)' => '$1,750.00'
A47: 'CPA'
B47: '=sum(B45/B46)' => '$2.86'
C47: '(Cost Per Aquisition)'
E47: 'INDUSTRY AVERAGE $5-$25/CPA'
A49: 'NUMBER OF VISITORS'
D49: '=sum(B45)' => '5000'
A50: 'PERCENTAGE ENTERED SHIPPING DETAILS'
D50: 0.15
A51: 'TOTAL NUMBER OF CUSTOMERS TO STEP #2'
D51: '=sum(D49*D50)' => '750'
A52: 'PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2'
D52: 0.035
A53: 'TOTAL NUMBER OF BUYERS'
D53: '=sum(D51*D52)' => '26.25'
A54: 'AVERAGE CART VALUE ($9.95 plus $54.94)'
D54: 22.33
F54: '=sum(D53*D54)' => '$586.16'
A55: 'PERCENTAGE OF BUYERS BUY ORDER BUMP'
D55: 0.102
E55: 37
A56: 'TOTAL NUMBER OF BUYERS OF ORDER BUMP'
D56: '=sum(D53*D55)' => '2.6775'
A57: 'AVERAGE CART VALUE AFTER ORDER BUMP'
D57: '=sum(D56*E55)+D54' => '$121.40'
F57: '=sum(D56*D57)' => '$325.04'
A58: 'PERCENTAGE OF BUYERS BUY ONE TIME OFFER'
D58: 0.11
E58: 47
A59: 'TOTAL NUMBER OF ONE TIME OFFER BUYERS'
D59: '=sum(D56*D58)' => '0.294525'
A60: 'TOTAL AVERAGE CART VALUE'
D60: '=sum(D59*E58)+D57' => '$135.24'
F60: '=sum(D59*D60)' => '$39.83'
A61: 'TOTAL REVENUE FROM CAMPAIGN'
F61: '=sum(F54+F57+F60)' => '$951.04'
A62: 'TOTAL AD COST'
F62: '=sum(B46)' => '$1,750.00'
A63: 'GROSS PROFIT'
F63: '=sum(F61-F62)' => '-$798.96'
A67: 'SO IF I ATTRACTED 10000 VISITORS/LEADS TO THIS OFFER'
A69: 'CTR'
B69: '=sum(B70/B71)' => '0.00%'
C69: '(Click Through Rate)'
A70: 'CPC'
B70: 0.35
C70: '(Cost Per Click)'
A71: 'TOTAL CLICKS'
B71: 10000
C71: '(LEADS)'
A72: 'AD COST'
B72: '=sum(B71*B70)' => '$3,500.00'
A73: 'CPA'
B73: '=sum(B71/B72)' => '$2.86'
C73: '(Cost Per Aquisition)'
A75: 'NUMBER OF VISITORS'
D75: '=sum(B71)' => '10000'
A76: 'PERCENTAGE ENTERED SHIPPING DETAILS'
D76: 0.15
A77: 'TOTAL NUMBER OF CUSTOMERS TO STEP #2'
D77: '=sum(D75*D76)' => '1500'
A78: 'PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2'
D78: 0.035
A79: 'TOTAL NUMBER OF BUYERS'
D79: '=sum(D77*D78)' => '52.50'
A80: 'AVERAGE CART VALUE ($9.95 plus $54.94)'
D80: 22.33
F80: '=sum(D79*D80)' => '$1,172.33'
A81: 'PERCENTAGE OF BUYERS BUY ORDER BUMP'
D81: 0.102
E81: 37
A82: 'TOTAL NUMBER OF BUYERS OF ORDER BUMP'
D82: '=sum(D79*D81)' => '5.355'
A83: 'AVERAGE CART VALUE AFTER ORDER BUMP'
D83: '=sum(D82*E81)+D80' => '$220.47'
F83: '=sum(D82*D83)' => '$1,180.59'
A84: 'PERCENTAGE OF BUYERS BUY ONE TIME OFFER'
D84: 0.11
E84: 47
A85: 'TOTAL NUMBER OF ONE TIME OFFER BUYERS'
D85: '=sum(D82*D84)' => '0.58905'
A86: 'TOTAL AVERAGE CART VALUE'
D86: '=sum(D85*E84)+D83' => '$248.15'
F86: '=sum(D85*D86)' => '$146.17'
A87: 'TOTAL REVENUE FROM CAMPAIGN'
F87: '=sum(F80+F83+F86)' => '$2,499.09'
A88: 'TOTAL AD COST'
F88: '=sum(B72)' => '$3,500.00'
A89: 'GROSS PROFIT'
F89: '=sum(F87-F88)' => '-$1,000.91'

## Sheet6
A2: 'AD C.P.A.'
B2: 'CART VALUE'
A3: 'AD # 1'
B3: 'STEP 1'
C3: 'STEP 2'
D3: 'STEP 3'
E3: 'STEP 4'
F3: 'STEP 5'
G3: 'AVERAGE AD C.P.A.'
A4: 8.51
B4: 'Adderess'
C4: '2 Step'
G4: '=sum(A4+A6+A8+A10)/4' => '$8.74'
A5: 'AD #2'
C5: 4.95
D5: 37
E5: 47
G5: 'AVERAGE CART VALUE'
A6: 6.01
C6: 54.95
G6: '1.)'
H6: '=sum(B14)' => '0'
A7: 'AD #3'
G7: '2.)'
H7: '=sum(C14)' => '$2.10'
A8: 8.21
G8: '3.)'
H8: '=sum(D14)' => '$3.77'
A9: 'AD #4'
G9: '4.)'
H9: '=sum(E14)' => '$5.17'
A10: 12.21
B10: '=sum(B4:B9)' => '$0.00'
C10: '=sum(C4:C9)' => '$59.90'
D10: '=sum(D4:D9)' => '$37.00'
E10: '=sum(E4:E9)' => '$47.00'
F10: '=sum(F4:F9)' => '$0.00'
G10: '5.)'
H10: '=sum(F14)' => '$0.00'
A11: 'Conv Rates'
B11: 0.156
C11: 0.035
D11: 0.102
E11: 0.11
G11: 'ACV TOTAL'
H11: '=sum(H7:H9)/3' => '$3.68'
A12: 'VISITORS/Buyers'
B12: 1000
C12: '=sum(B13*C11)' => '5.46'
D12: '=sum(C12*D11)' => '0.55692'
E12: '=sum(D12*E11)' => '0.0612612'
F12: '=sum(E13*F11)' => '0'
B13: '=sum(B11*B12)' => '156'
A14: 'CART TOTAL'
C14: '=sum(C10*C11)' => '$2.10'
D14: '=sum(D10*D11)' => '$3.77'
E14: '=sum(E10*E11)' => '$5.17'
F14: '=sum(F10*F12)' => '$0.00'

## 2 UPSELLS
A22: 'SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER'
A24: 'CTR'
B24: '=sum(B25/B26)' => '0.04%'
C24: '(Click Through Rate)'
A25: 'CPC'
B25: 0.35
C25: '(Cost Per Click)'
A26: 'TOTAL CLICKS'
B26: 1000
C26: '(LEADS)'
A27: 'AD COST'
B27: '=sum(B26*B25)' => '$350.00'
A28: 'CPA'
B28: '=sum(B26/B27)' => '$2.86'
C28: '(Cost Per Aquisition)'
A30: 'NUMBER OF VISITORS'
D30: '=sum(B26)' => '1000'
F30: 'TOTAL REVENUE'
A31: 'PERCENTAGE ENTERED SHIPPING DETAILS'
D31: 0.15
A32: 'TOTAL NUMBER OF CUSTOMERS TO STEP #2'
D32: '=sum(D30*D31)' => '150'
A33: 'PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2'
D33: 0.035
A34: 'TOTAL NUMBER OF BUYERS'
D34: '=sum(D32*D33)' => '5.25'
A35: 'AVERAGE CART VALUE ($9.95 plus $54.94)'
D35: 22.33
F35: '=sum(D34*D35)' => '$117.23'
A36: 'PERCENTAGE OF BUYERS BUY ORDER BUMP'
D36: 0.102
E36: 37
A37: 'TOTAL NUMBER OF BUYERS OF ORDER BUMP'
D37: '=sum(D34*D36)' => '0.5355'
A38: 'AVERAGE CART VALUE AFTER ORDER BUMP'
D38: '=sum(D37*E36)+D35' => '$42.14'
F38: '=sum(D37*D38)' => '$22.57'
A39: 'PERCENTAGE OF BUYERS BUY ONE TIME OFFER'
D39: 0.11
E39: 47
A40: 'TOTAL NUMBER OF ONE TIME OFFER BUYERS'
D40: '=sum(D37*D39)' => '0.06'
A41: 'AVERAGE CART VALUE AFTER ONE TIME OFFER'
D41: '=sum(D40*E39)+D38' => '$44.91'
F41: '=sum(D41*D40)' => '$2.65'
A42: 'PERCENTAGE OF BUYERS BUY 2nd Upsell'
D42: 0.1
E42: 197
A43: 'TOTAL NUMBER OF 2nd Upsell Buyers'
D43: '=sum(D42*D40)' => '0.0058905'
A44: 'TOTAL AVERAGE CART VALUE after 2nd Upsell'
D44: '=sum(D43*E42)+D41' => '$46.07'
F44: '=sum(D43*E42)' => '$1.16'
A45: 'TOTAL REVENUE FROM CAMPAIGN'
F45: '=sum(F35+F38+F41+F44)' => '$143.61'
A46: 'TOTAL AD COST'
F46: '=sum(B27)' => '$350.00'
A47: 'GROSS PROFIT'
F47: '=sum(F45-F46)' => '-$206.39'
A73: 'SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER'
A75: 'CTR'
B75: '=sum(B76/B77)' => '0.04%'
C75: '(Click Through Rate)'
A76: 'CPC'
B76: 0.35
C76: '(Cost Per Click)'
A77: 'TOTAL CLICKS'
B77: 1000
C77: '(LEADS)'
A78: 'AD COST'
B78: '=sum(B77*B76)' => '$350.00'
A79: 'CPA'
B79: '=sum(B77/B78)' => '$2.86'
C79: '(Cost Per Aquisition)'
A81: 'NUMBER OF VISITORS'
D81: '=sum(B77)' => '1000'
F81: 'TOTAL REVENUE'
A82: 'PERCENTAGE ENTERED SHIPPING DETAILS'
D82: 0.15
A83: 'TOTAL NUMBER OF CUSTOMERS TO STEP #2'
D83: '=sum(D81*D82)' => '150'
A84: 'PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2'
D84: 0.035
A85: 'TOTAL NUMBER OF BUYERS'
D85: '=sum(D83*D84)' => '5.25'
A86: 'AVERAGE CART VALUE ($9.95 plus $54.94)'
D86: 22.33
F86: '=sum(D85*D86)' => '$117.23'
A87: 'PERCENTAGE OF BUYERS BUY ORDER BUMP'
D87: 0.17
E87: 37
A88: 'TOTAL NUMBER OF BUYERS OF ORDER BUMP'
D88: '=sum(D85*D87)' => '0.8925'
A89: 'AVERAGE CART VALUE AFTER ORDER BUMP'
D89: '=sum(D88*E87)+D86' => '$55.35'
F89: '=sum(D88*D89)' => '$49.40'
A90: 'PERCENTAGE OF BUYERS BUY ONE TIME OFFER'
D90: 0.215
E90: 47
A91: 'TOTAL NUMBER OF ONE TIME OFFER BUYERS'
D91: '=sum(D88*D90)' => '0.19'
A92: 'AVERAGE CART VALUE AFTER ONE TIME OFFER'
D92: '=sum(D91*E90)+D89' => '$64.37'
F92: '=sum(D92*D91)' => '$12.35'
A93: 'PERCENTAGE OF BUYERS BUY 2nd Upsell'
D93: 0.1
E93: 197
A94: 'TOTAL NUMBER OF 2nd Upsell Buyers'
D94: '=sum(D93*D91)' => '0.01918875'
A95: 'TOTAL AVERAGE CART VALUE after 2nd Upsell'
D95: '=sum(D94*E93)+D92' => '$68.15'
F95: '=sum(D94*E93)' => '$3.78'
A96: 'TOTAL REVENUE FROM CAMPAIGN'
F96: '=sum(F86+F89+F92+F95)' => '$182.77'
A97: 'TOTAL AD COST'
F97: '=sum(B78)' => '$350.00'
A98: 'GROSS PROFIT'
F98: '=sum(F96-F97)' => '-$167.23'

## WEBINAR TAIL
A2: 'WEBINAR ADDED'
A22: 'SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER'
A24: 'CTR'
B24: '=sum(B25/B26)' => '0.00%'
C24: '(Click Through Rate)'
A25: 'CPC'
B25: 0.35
C25: '(Cost Per Click)'
A26: 'TOTAL CLICKS'
B26: 10000
C26: '(LEADS)'
A27: 'AD COST'
B27: '=sum(B26*B25)' => '$3,500.00'
A28: 'CPA'
B28: '=sum(B26/B27)' => '$2.86'
C28: '(Cost Per Aquisition)'
A30: 'NUMBER OF VISITORS'
D30: '=sum(B26)' => '10000'
F30: 'TOTAL REVENUE'
A31: 'PERCENTAGE ENTERED SHIPPING DETAILS'
D31: 0.15
A32: 'TOTAL NUMBER OF CUSTOMERS TO STEP #2'
D32: '=sum(D30*D31)' => '1500'
A33: 'PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2'
D33: 0.035
A34: 'TOTAL NUMBER OF BUYERS'
D34: '=sum(D32*D33)' => '52.50'
A35: 'AVERAGE CART VALUE ($9.95 plus $54.94)'
D35: 22.33
F35: '=sum(D34*D35)' => '$1,172.33'
A36: 'PERCENTAGE OF BUYERS BUY ORDER BUMP'
D36: 0.17
E36: 37
A37: 'TOTAL NUMBER OF BUYERS OF ORDER BUMP'
D37: '=sum(D34*D36)' => '8.925'
A38: 'AVERAGE CART VALUE AFTER ORDER BUMP'
D38: '=sum(D37*E36)+D35' => '$352.56'
F38: '=sum(D37*D38)' => '$3,146.55'
A39: 'PERCENTAGE OF BUYERS BUY ONE TIME OFFER'
D39: 0.215
E39: 47
A40: 'TOTAL NUMBER OF ONE TIME OFFER BUYERS'
D40: '=sum(D37*D39)' => '1.92'
A41: 'AVERAGE CART VALUE AFTER ONE TIME OFFER'
D41: '=sum(D40*E39)+D38' => '$442.74'
F41: '=sum(D41*D40)' => '$849.57'
A42: 'PERCENTAGE OF BUYERS BUY 2nd Upsell'
D42: 0.1
E42: 197
A43: 'TOTAL NUMBER OF 2nd Upsell Buyers'
D43: '=sum(D42*D40)' => '0.1918875'
A44: 'TOTAL AVERAGE CART VALUE after 2nd Upsell'
D44: '=sum(D43*E42)+D41' => '$480.54'
F44: '=sum(D43*E42)' => '$37.80'
A45: 'PERCENTAGE OF BUYERS BUY WEBINAR'
D45: 0.045
E45: 2000
A46: 'TOTAL NUMBER OF WEBINAR BUYERS'
D46: '=sum(D45*D43)' => '0.0086349375'
A47: 'TOTAL AVERAGE CART VALUE after WEBINAR'
D47: '=sum(D46*E45)+D44' => '$497.81'
F47: '=sum(D46*E45)' => '$17.27'
A48: 'TOTAL REVENUE FROM CAMPAIGN'
F48: '=sum(F35+F38+F41+F44+F47)' => '$5,223.52'
A49: 'TOTAL AD COST'
F49: '=sum(B27)' => '$3,500.00'
A50: 'GROSS PROFIT'
F50: '=sum(F48-F49)' => '$1,723.52'

## Candle Business
A22: 'SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER'
A24: 'CTR'
B24: '=sum(B25/B26)' => '0.04%'
C24: '(Click Through Rate)'
A25: 'CPC'
B25: 0.35
C25: '(Cost Per Click)'
A26: 'TOTAL CLICKS'
B26: 1000
C26: '(LEADS)'
A27: 'AD COST'
B27: 68.45
A28: 'CPA'
B28: '=sum(B26/B27)' => '$14.61'
C28: '(Cost Per Aquisition)'
A30: 'NUMBER OF VISITORS'
D30: '=sum(B26)' => '1000'
F30: 'TOTAL REVENUE'
A31: 'PERCENTAGE ENTERED SHIPPING DETAILS'
D31: 0.0719
A32: 'TOTAL NUMBER OF CUSTOMERS TO STEP #2'
D32: '=sum(D30*D31)' => '71.9'
A33: 'PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2'
D33: 0.345
A34: 'TOTAL NUMBER OF BUYERS'
D34: '=sum(D32*D33)' => '24.81'
A35: 'AVERAGE CART VALUE '
D35: 37.58
F35: '=sum(D34*D35)' => '$932.19'
A36: 'PERCENTAGE OF BUYERS BUY ORDER BUMP'
D36: 0.19
E36: 1.01
A37: 'TOTAL NUMBER OF BUYERS OF ORDER BUMP'
D37: '=sum(D34*D36)' => '4.713045'
A38: 'AVERAGE CART VALUE AFTER ORDER BUMP'
D38: '=sum(D37*E36)+D35' => '$42.34'
F38: '=sum(D37*D38)' => '$199.55'
A39: 'PERCENTAGE OF BUYERS BUY ONE TIME OFFER'
D39: 0.3437
E39: 0.41
A40: 'TOTAL NUMBER OF ONE TIME OFFER BUYERS'
D40: '=sum(D34)' => '24.81'
A41: 'AVERAGE CART VALUE AFTER ONE TIME OFFER'
D41: '=sum(D40*E39)+D38' => '$52.51'
F41: '=sum(D41*D40)' => '$1,302.55'
A42: 'PERCENTAGE OF BUYERS BUY 2nd Upsell'
D42: 0.0475
E42: 2.26
A43: 'TOTAL NUMBER OF 2nd Upsell Buyers'
D43: '=sum(D42*D40)' => '1.17826125'
A44: 'TOTAL AVERAGE CART VALUE after 2nd Upsell'
D44: '=sum(D43*E42)+D41' => '$55.17'
F44: '=sum(D43*E42)' => '$2.66'
A45: 'TOTAL REVENUE FROM CAMPAIGN'
F45: '=sum(F35+F38+F41+F44)' => '$2,436.95'
A46: 'TOTAL AD COST'
F46: '=sum(B27)' => '68.45'
A47: 'GROSS PROFIT'
F47: '=sum(F45-F46)' => '$2,368.50'
Readable original image content and explicit visual limitations

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

# D0459 native image review — September 11, 2026

All nine original PNGs were individually displayed and visually reviewed during the 18:12Z heartbeat. Original files remain byte-preserved in D0459-native-images. This is visual intake, not completed lesson adaptation. Tiny embedded landing-page/ad screenshots are not fully legible at their supplied resolution; do not invent their copy or claim OCR-level completeness. Full original artwork must accompany the lesson, alongside the readable instructional material below.

## Images 1–3: one-upsell example

Image 1 labels three columns Cost per Acquisition, Average Cart Value, and Funnel Audibles; caption Example of What a Filled Out Sheet Looks Like. Five displayed ad CPAs: $8.51, $6.01, $8.21, $12.21, $5.06. Shipping step, credit-card step with $9.95 / $54.95 and shipping footnote, $37 bump, $47 OTO #1. Four shown conversion rates: 15.6%, 3.5%, 10.2%, 11%. Right column CPA $9.17; ACV increments $0.00, $22.33, $3.77, $5.17; displayed total ACV $31.27, minus CPA $9.17 = $22.10. Image 2 enlarges the same four-step offer sketch. Image 3 enlarges the four screenshot/rate examples. Do not treat the rates as established benchmarks or all as sharing one denominator.

## Image 4: two-upsell example

Same five ad CPAs, same shipping/credit-card/$37 bump/$47 OTO, plus $197 OTO #2. Conversion labels 15.6%, 3.5%, 17.4%, 11%, 4.5%. CPA $7.14. ACV increments $0, $22.33, $6.44, $5.17, $8.87, total $42.80, less $7.14 = $35.66. Arithmetic displayed is consistent after rounding; 197 × 4.5% = 8.865. Source does not establish traffic, sample size, attribution window or denominator consistency.

## Image 5: Jamie narrative

Narrative says Jamie runs three ads, sells a lotion bar rather than free-plus-shipping, CPA $14.61. First-page video pitches the front end; 7.19% provide shipping information; second page sells the product and converts 34.5%, yielding stated front-end ACV $37.58. Third page usually sells more of the same, here 19% conversion and $4.73 incremental ACV. Second upsell on fourth page converts 34.37%, adding $9.76. Fifth-page final offer is stated at 4.75%, adding $3.07. Overall ACV $55.15 less CPA $14.61 gives $40.54. Narrative says results followed tweaking/testing and suggests improving the 19% upsell, asking what changes/tactics could improve it and brainstorming freely.

Explicit conflicts: narrative says three ads but images 6/8 show four CPA examples. Narrative final conversion 4.75% conflicts with diagram 4.25%. Stated increments 37.58+4.73+9.76+3.07 total $55.14, one cent below displayed $55.15 (possibly underlying rounding; not established). ACV less acquisition cost is not net profit: fulfillment, goods, fees, refunds, overhead and tax are not deducted. The narrative's broad claim that more-of-the-same upsells work for all ecommerce is unsupported.

## Images 6 and 8: Jamie diagram variants

Two supplied versions of same five-step lotion-bar funnel. Four ad CPAs $10.87, $12.76 (line-wrapped), $19.50, $15.29. Funnel audibles CPA $14.61, ACV increments 0/37.58/4.73/9.76/3.07, total $55.15, subtraction $40.54. Conversion labels 7.19%,34.5%,19%,34.37%,4.25%. Upsell sketches show WAIT, option prices $39/$49 then $49/$24; last sketch BEFORE YOU LEAVE / ADD TO ORDER. Tiny credit-card offer text and actual screenshot body copy are not fully readable; preserve both original images rather than reconstructing missing text. Images are separate originals, not assumed byte duplicates.

## Image 7: asserted benchmark list

- Lead opt-ins >20%.
- Two-step opt-ins >10–15%.
- Tripwire sales conversion >1–5%.
- Order bump conversion >20%.
- OTO/downsell conversions >3–15%.
- Webinar show-up LIVE >10–20%.
- Webinar show-up AUTO >50–80%.
- Webinar buy rate hot traffic LIVE >10%.
- Webinar buy rate cold traffic LIVE >1–5%.
- Webinar buy rate AUTO >3–8%.

These are source assertions, not verified universal standards. Preserve their unusual greater-than-plus-range notation while explaining that test targets require denominator, segment, traffic source, sample size, window and economics.

## Image 9: changed conversion and CPA

Shipping/credit-card/$37 bump/$47 OTO/$197 OTO diagram; ad CPA examples again $8.51/$6.01/$8.21/$12.21/$5.06. Rates 15.6%,3.5%,17.4%,21.5%,4.5%. New CPA $23.79, total ACV $47.55, displayed residual $23.76. Right ACV increments visible: 0,22.33,6.44,9.92,8.87. The prose attributes improved OTO conversion from 11% to21.5% (almost doubled) to simplifying presentation and making it as free as possible/easy to follow; explicitly notes CPA also rose. Do not imply causal proof. Also 47×21.5%=10.105, not9.92; displayed increments sum47.56 not47.55. Do not silently correct original. Compare image4 residual35.66 to image9 residual23.76: higher headline conversion/ACV can coexist with lower acquisition contribution. The source provides no costs/sample information proving profitability.

## Still required

Compare all484 populated cells and147 formulas with native Google Sheet values; retain all160 merged regions and9 image anchors. Resolve image/cell discrepancies explicitly. Read all source Markdown and image-bearing workbook content together, write teaching and full source appendices, preserve original XLSX and PNGs, link applicable sources, and verify every assigned GHL placement. No D0459 adaptation count is earned by this review.
Complete local source copy including original filing metadata and formatting

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

---
source_type: "Google Sheet"
source_url: "https://docs.google.com/spreadsheets/d/10Y1i8CsbQielLeeQ0gZFECCeN38zUs68L5O6rBUZkaM/edit?usp=drivesdk"
drive_file_id: "10Y1i8CsbQielLeeQ0gZFECCeN38zUs68L5O6rBUZkaM"
created: "2024-04-22T00:35:25.649Z"
modified: "2026-06-04T16:41:09.472Z"
---

# Copy of Average Cart Value

,https://s3content.s3.amazonaws.com/30_Day_Summit/Funnel_Audibles_Transcripts.pdf,Unnamed: 1,Unnamed: 2,Unnamed: 3,Unnamed: 4,Unnamed: 5,Unnamed: 6,Unnamed: 7,Unnamed: 8,Unnamed: 9,Unnamed: 10
0,,,,,,,,,,,
1,COST PER AQUISITION,,,,,,,,,,
2,,,,,,,,,,,
3,AVERAGE CART VALUE,,,,,,,,,,
4,"ACV Industry Average for ""Free Plus Shipping $30-35""",,,,,,https://s3content.s3.amazonaws.com/30_Day_Summit/Funnel_Audibles_Final.pdf,,,,
5,,,,,,,WORKBOOK,,,,
6,BELOW IS A SIMPLE 4 STEP FUNNEL,,,,,,,,,,
7,FREE PLUS SHIPPING,,,,,,R.O.A.S.,Return On Ad Spend,,2:1,$2 Income/$1 Spend
8,,,,,,,A.O.V,Average Order Value,,,
9,1.)Shipping Info,,,,,,A.C.V,Average Cart Value,,,
10,2.)PURCHASE $9.99 or ($54.95),,,,,,L.T.V.,Lifetime Value,,,
11,3.)Order Bump $37,,,,,,M.R.R.,Monthly Recurring Revenue,,,
12,4.) One Time Offer $47,,,,,,C.T.R,Click Trough Rate,,,
13,,,,,,,C.P.C,Cost Per Click,,,
14,SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER,,,,,,C.P.A.,Cost Per Aquistion,,,
15,,,,,,,,,,,
16,CTR,0.00035,(Click Through Rate),,,,,,,,
17,CPC,0.35,(Cost Per Click),,,,,,,,
18,TOTAL CLICKS,1000,(LEADS),,,,,,,,
19,AD COST,350,,,,,,,,,
20,CPA,2.857142857,(Cost Per Aquisition),,,,,,,,
21,,,,,,,,,,,
22,NUMBER OF VISITORS,,,1000,,,,,,,
23,PERCENTAGE ENTERED SHIPPING DETAILS,,,0.15,,,,,,,
24,TOTAL NUMBER OF CUSTOMERS TO STEP #2,,,150,,,,,,,
25,PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2,,,0.035,,,,,,,
26,TOTAL NUMBER OF BUYERS,,,5.25,,,,,,,
27,AVERAGE CART VALUE ($9.95 plus $54.94),,,22.33,,117.2325,,,,,
28,PERCENTAGE OF BUYERS BUY ORDER BUMP,,,0.102,37,,,,,,
29,TOTAL NUMBER OF BUYERS OF ORDER BUMP,,,0.5355,,,,,,,
30,AVERAGE CART VALUE AFTER ORDER BUMP,,,42.1435,,22.56784425,,,,,
31,PERCENTAGE OF BUYERS BUY ONE TIME OFFER,,,0.11,47,,,,,,
32,TOTAL NUMBER OF ONE TIME OFFER BUYERS,,,0.058905,,,,,,,
33,TOTAL AVERAGE CART VALUE,,,44.912035,,2.645543422,,,,,
34,TOTAL REVENUE FROM CAMPAIGN,,,,,142.4458877,,,,,
35,TOTAL AD COST,,,,,350,,,,,
36,GROSS PROFIT,,,,,-207.5541123,,,,,
37,,,,,,,,,,,
38,,,,,,,,,,,
39,SO IF I ATTRACTED 5000 VISITORS/LEADS TO THIS OFFER,,,,,,,,,,
40,,,,,,,,,,,
41,CTR,7e-05,(Click Through Rate),,,,,,,,
42,CPC,0.35,(Cost Per Click),,,,,,,,
43,TOTAL CLICKS,5000,(LEADS),,,,,,,,
44,AD COST,1750,,,,,,,,,
45,CPA,2.857142857,(Cost Per Aquisition),,INDUSTRY AVERAGE $5-$25/CPA,,,,,,
46,,,,,,,,,,,
47,NUMBER OF VISITORS,,,5000,,,,,,,
48,PERCENTAGE ENTERED SHIPPING DETAILS,,,0.15,,,,,,,
49,TOTAL NUMBER OF CUSTOMERS TO STEP #2,,,750,,,,,,,
50,PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2,,,0.035,,,,,,,
51,TOTAL NUMBER OF BUYERS,,,26.25,,,,,,,
52,AVERAGE CART VALUE ($9.95 plus $54.94),,,22.33,,586.1625,,,,,
53,PERCENTAGE OF BUYERS BUY ORDER BUMP,,,0.102,37,,,,,,
54,TOTAL NUMBER OF BUYERS OF ORDER BUMP,,,2.6775,,,,,,,
55,AVERAGE CART VALUE AFTER ORDER BUMP,,,121.3975,,325.0418063,,,,,
56,PERCENTAGE OF BUYERS BUY ONE TIME OFFER,,,0.11,47,,,,,,
57,TOTAL NUMBER OF ONE TIME OFFER BUYERS,,,0.294525,,,,,,,
58,TOTAL AVERAGE CART VALUE,,,135.240175,,39.83161254,,,,,
59,TOTAL REVENUE FROM CAMPAIGN,,,,,951.0359188,,,,,
60,TOTAL AD COST,,,,,1750,,,,,
61,GROSS PROFIT,,,,,-798.9640812,,,,,
62,,,,,,,,,,,
63,,,,,,,,,,,
64,,,,,,,,,,,
65,SO IF I ATTRACTED 10000 VISITORS/LEADS TO THIS OFFER,,,,,,,,,,
66,,,,,,,,,,,
67,CTR,3.5e-05,(Click Through Rate),,,,,,,,
68,CPC,0.35,(Cost Per Click),,,,,,,,
69,TOTAL CLICKS,10000,(LEADS),,,,,,,,
70,AD COST,3500,,,,,,,,,
71,CPA,2.857142857,(Cost Per Aquisition),,,,,,,,
72,,,,,,,,,,,
73,NUMBER OF VISITORS,,,10000,,,,,,,
74,PERCENTAGE ENTERED SHIPPING DETAILS,,,0.15,,,,,,,
75,TOTAL NUMBER OF CUSTOMERS TO STEP #2,,,1500,,,,,,,
76,PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2,,,0.035,,,,,,,
77,TOTAL NUMBER OF BUYERS,,,52.5,,,,,,,
78,AVERAGE CART VALUE ($9.95 plus $54.94),,,22.33,,1172.325,,,,,
79,PERCENTAGE OF BUYERS BUY ORDER BUMP,,,0.102,37,,,,,,
80,TOTAL NUMBER OF BUYERS OF ORDER BUMP,,,5.355,,,,,,,
81,AVERAGE CART VALUE AFTER ORDER BUMP,,,220.465,,1180.590075,,,,,
82,PERCENTAGE OF BUYERS BUY ONE TIME OFFER,,,0.11,47,,,,,,
83,TOTAL NUMBER OF ONE TIME OFFER BUYERS,,,0.58905,,,,,,,
84,TOTAL AVERAGE CART VALUE,,,248.15035,,146.1729637,,,,,
85,TOTAL REVENUE FROM CAMPAIGN,,,,,2499.088039,,,,,
86,TOTAL AD COST,,,,,3500,,,,,
87,GROSS PROFIT,,,,,-1000.911961,,,,,

,Unnamed: 0,Unnamed: 1,Unnamed: 2,Unnamed: 3,Unnamed: 4,Unnamed: 5,Unnamed: 6,Unnamed: 7
0,AD C.P.A.,CART VALUE,,,,,,
1,AD # 1,STEP 1,STEP 2,STEP 3,STEP 4,STEP 5,AVERAGE AD C.P.A.,
2,8.51,Adderess,2 Step,,,,8.735,
3,AD #2,,4.95,37,47,,AVERAGE CART VALUE,
4,6.01,,54.95,,,,1.),0
5,AD #3,,,,,,2.),2.0965
6,8.21,,,,,,3.),3.774
7,AD #4,,,,,,4.),5.17
8,12.21,0,59.9,37,47,0,5.),0
9,Conv Rates,0.156,0.035,0.102,0.11,,ACV TOTAL,3.680166667
10,VISITORS/Buyers,1000,5.46,0.55692,0.0612612,0,,
11,,156,,,,,,
12,CART TOTAL,,2.0965,3.774,5.17,0,,

,Unnamed: 0,Unnamed: 1,Unnamed: 2,Unnamed: 3,Unnamed: 4,Unnamed: 5
0,,,,,,
1,,,,,,
2,,,,,,
3,,,,,,
4,,,,,,
5,,,,,,
6,,,,,,
7,,,,,,
8,,,,,,
9,,,,,,
10,,,,,,
11,,,,,,
12,,,,,,
13,,,,,,
14,,,,,,
15,,,,,,
16,,,,,,
17,,,,,,
18,,,,,,
19,,,,,,
20,SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER,,,,,
21,,,,,,
22,CTR,0.00035,(Click Through Rate),,,
23,CPC,0.35,(Cost Per Click),,,
24,TOTAL CLICKS,1000,(LEADS),,,
25,AD COST,350,,,,
26,CPA,2.857142857,(Cost Per Aquisition),,,
27,,,,,,
28,NUMBER OF VISITORS,,,1000,,TOTAL REVENUE
29,PERCENTAGE ENTERED SHIPPING DETAILS,,,0.15,,
30,TOTAL NUMBER OF CUSTOMERS TO STEP #2,,,150,,
31,PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2,,,0.035,,
32,TOTAL NUMBER OF BUYERS,,,5.25,,
33,AVERAGE CART VALUE ($9.95 plus $54.94),,,22.33,,117.2325
34,PERCENTAGE OF BUYERS BUY ORDER BUMP,,,0.102,37,
35,TOTAL NUMBER OF BUYERS OF ORDER BUMP,,,0.5355,,
36,AVERAGE CART VALUE AFTER ORDER BUMP,,,42.1435,,22.56784425
37,PERCENTAGE OF BUYERS BUY ONE TIME OFFER,,,0.11,47,
38,TOTAL NUMBER OF ONE TIME OFFER BUYERS,,,0.058905,,
39,AVERAGE CART VALUE AFTER ONE TIME OFFER,,,44.912035,,2.645543422
40,PERCENTAGE OF BUYERS BUY 2nd Upsell,,,0.1,197,
41,TOTAL NUMBER OF 2nd Upsell Buyers,,,0.0058905,,
42,TOTAL AVERAGE CART VALUE after 2nd Upsell,,,46.0724635,,1.1604285
43,TOTAL REVENUE FROM CAMPAIGN,,,,,143.6063162
44,TOTAL AD COST,,,,,350
45,GROSS PROFIT,,,,,-206.3936838
46,,,,,,
47,,,,,,
48,,,,,,
49,,,,,,
50,,,,,,
51,,,,,,
52,,,,,,
53,,,,,,
54,,,,,,
55,,,,,,
56,,,,,,
57,,,,,,
58,,,,,,
59,,,,,,
60,,,,,,
61,,,,,,
62,,,,,,
63,,,,,,
64,,,,,,
65,,,,,,
66,,,,,,
67,,,,,,
68,,,,,,
69,,,,,,
70,,,,,,
71,SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER,,,,,
72,,,,,,
73,CTR,0.00035,(Click Through Rate),,,
74,CPC,0.35,(Cost Per Click),,,
75,TOTAL CLICKS,1000,(LEADS),,,
76,AD COST,350,,,,
77,CPA,2.857142857,(Cost Per Aquisition),,,
78,,,,,,
79,NUMBER OF VISITORS,,,1000,,TOTAL REVENUE
80,PERCENTAGE ENTERED SHIPPING DETAILS,,,0.15,,
81,TOTAL NUMBER OF CUSTOMERS TO STEP #2,,,150,,
82,PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2,,,0.035,,
83,TOTAL NUMBER OF BUYERS,,,5.25,,
84,AVERAGE CART VALUE ($9.95 plus $54.94),,,22.33,,117.2325
85,PERCENTAGE OF BUYERS BUY ORDER BUMP,,,0.17,37,
86,TOTAL NUMBER OF BUYERS OF ORDER BUMP,,,0.8925,,
87,AVERAGE CART VALUE AFTER ORDER BUMP,,,55.3525,,49.40210625
88,PERCENTAGE OF BUYERS BUY ONE TIME OFFER,,,0.215,47,
89,TOTAL NUMBER OF ONE TIME OFFER BUYERS,,,0.1918875,,
90,AVERAGE CART VALUE AFTER ONE TIME OFFER,,,64.3712125,,12.35203104
91,PERCENTAGE OF BUYERS BUY 2nd Upsell,,,0.1,197,
92,TOTAL NUMBER OF 2nd Upsell Buyers,,,0.01918875,,
93,TOTAL AVERAGE CART VALUE after 2nd Upsell,,,68.15139625,,3.78018375
94,TOTAL REVENUE FROM CAMPAIGN,,,,,182.766821
95,TOTAL AD COST,,,,,350
96,GROSS PROFIT,,,,,-167.233179

,Unnamed: 0,Unnamed: 1,Unnamed: 2,Unnamed: 3,Unnamed: 4,Unnamed: 5
0,WEBINAR ADDED,,,,,
1,,,,,,
2,,,,,,
3,,,,,,
4,,,,,,
5,,,,,,
6,,,,,,
7,,,,,,
8,,,,,,
9,,,,,,
10,,,,,,
11,,,,,,
12,,,,,,
13,,,,,,
14,,,,,,
15,,,,,,
16,,,,,,
17,,,,,,
18,,,,,,
19,,,,,,
20,SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER,,,,,
21,,,,,,
22,CTR,3.5e-05,(Click Through Rate),,,
23,CPC,0.35,(Cost Per Click),,,
24,TOTAL CLICKS,10000,(LEADS),,,
25,AD COST,3500,,,,
26,CPA,2.857142857,(Cost Per Aquisition),,,
27,,,,,,
28,NUMBER OF VISITORS,,,10000,,TOTAL REVENUE
29,PERCENTAGE ENTERED SHIPPING DETAILS,,,0.15,,
30,TOTAL NUMBER OF CUSTOMERS TO STEP #2,,,1500,,
31,PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2,,,0.035,,
32,TOTAL NUMBER OF BUYERS,,,52.5,,
33,AVERAGE CART VALUE ($9.95 plus $54.94),,,22.33,,1172.325
34,PERCENTAGE OF BUYERS BUY ORDER BUMP,,,0.17,37,
35,TOTAL NUMBER OF BUYERS OF ORDER BUMP,,,8.925,,
36,AVERAGE CART VALUE AFTER ORDER BUMP,,,352.555,,3146.553375
37,PERCENTAGE OF BUYERS BUY ONE TIME OFFER,,,0.215,47,
38,TOTAL NUMBER OF ONE TIME OFFER BUYERS,,,1.918875,,
39,AVERAGE CART VALUE AFTER ONE TIME OFFER,,,442.742125,,849.5667951
40,PERCENTAGE OF BUYERS BUY 2nd Upsell,,,0.1,197,
41,TOTAL NUMBER OF 2nd Upsell Buyers,,,0.1918875,,
42,TOTAL AVERAGE CART VALUE after 2nd Upsell,,,480.5439625,,37.8018375
43,PERCENTAGE OF BUYERS BUY WEBINAR,,,0.045,2000,
44,TOTAL NUMBER OF WEBINAR BUYERS,,,0.0086349375,,
45,TOTAL AVERAGE CART VALUE after WEBINAR,,,497.8138375,,17.269875
46,TOTAL REVENUE FROM CAMPAIGN,,,,,5223.516883
47,TOTAL AD COST,,,,,3500
48,GROSS PROFIT,,,,,1723.516883

,Unnamed: 0,Unnamed: 1,Unnamed: 2,Unnamed: 3,Unnamed: 4,Unnamed: 5
0,,,,,,
1,,,,,,
2,,,,,,
3,,,,,,
4,,,,,,
5,,,,,,
6,,,,,,
7,,,,,,
8,,,,,,
9,,,,,,
10,,,,,,
11,,,,,,
12,,,,,,
13,,,,,,
14,,,,,,
15,,,,,,
16,,,,,,
17,,,,,,
18,,,,,,
19,,,,,,
20,SO IF I ATTRACTED 1000 VISITORS/LEADS TO THIS OFFER,,,,,
21,,,,,,
22,CTR,0.00035,(Click Through Rate),,,
23,CPC,0.35,(Cost Per Click),,,
24,TOTAL CLICKS,1000,(LEADS),,,
25,AD COST,68.45,,,,
26,CPA,14.6092038,(Cost Per Aquisition),,,
27,,,,,,
28,NUMBER OF VISITORS,,,1000,,TOTAL REVENUE
29,PERCENTAGE ENTERED SHIPPING DETAILS,,,0.0719,,
30,TOTAL NUMBER OF CUSTOMERS TO STEP #2,,,71.9,,
31,PERCENTAGE OF PEOPLE WHO PURCHASED IN STEP # 2,,,0.345,,
32,TOTAL NUMBER OF BUYERS,,,24.8055,,
33,AVERAGE CART VALUE ,,,37.58,,932.19069
34,PERCENTAGE OF BUYERS BUY ORDER BUMP,,,0.19,1.01,
35,TOTAL NUMBER OF BUYERS OF ORDER BUMP,,,4.713045,,
36,AVERAGE CART VALUE AFTER ORDER BUMP,,,42.34017545,,199.5511522
37,PERCENTAGE OF BUYERS BUY ONE TIME OFFER,,,0.3437,0.41,
38,TOTAL NUMBER OF ONE TIME OFFER BUYERS,,,24.8055,,
39,AVERAGE CART VALUE AFTER ONE TIME OFFER,,,52.51043045,,1302.547483
40,PERCENTAGE OF BUYERS BUY 2nd Upsell,,,0.0475,2.26,
41,TOTAL NUMBER OF 2nd Upsell Buyers,,,1.17826125,,
42,TOTAL AVERAGE CART VALUE after 2nd Upsell,,,55.17330088,,2.662870425
43,TOTAL REVENUE FROM CAMPAIGN,,,,,2436.952195
44,TOTAL AD COST,,,,,68.45
45,GROSS PROFIT,,,,,2368.502195

Turn the customer lifetime value workbook into a testable retention plan

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

What you will build

Complete the workbook's ten planning tables, moving from customer segments to measurable changes. The assigned document is a blank planning workbook. It contains five sections and ten tasks, not an already completed business analysis. Its original blank rows remain available in the appendix. The methods and examples explained here are authored guidance for using those fields; the document supplies no customer results, validated targets or lifetime-value formula.

The purpose is continuing customer value. In Brunson's value-ladder framing, the next offer should fit a customer's next relevant need. In the Hormozi value framework, consider the desired result, confidence in achieving it, time delay and required effort. Applying these ideas to retention means helping customers obtain useful results repeatedly. It does not mean adding purchases simply to maximize a spreadsheet total. Review the official Acquisition.com Value Equation resource alongside the workbook.

1. Identify the segments and set the goals

The first table asks for Segment Name, Demographics, Purchase Frequency and Avg. Order Value. Its two blank rows are working space, not a rule that a business must have exactly two segments. Use actual customer records and describe how each segment is defined. Where demographic information is unnecessary or unavailable, mark that honestly rather than guessing personal characteristics. Frequency needs a period, such as orders per customer per quarter; average order value needs a stated revenue basis, such as net sales after refunds divided by orders.

An authored example might distinguish first-time purchasers from repeat purchasers, then measure both over the same quarter. Those are behavioral segments, so explain that distinction rather than pretend the demographics column already supplies the right definition. Record the number of customers and orders in your supporting notes so that a tiny sample is not mistaken for a stable pattern. This is additional guidance, not an extra field claimed to exist in the original.

The second table has Goal Type, Current Value and Target Value. Its three prefilled goal rows are Repeat Purchase Rate, Average Order Value and Churn Rate Reduction. Fill all three. State the period and denominator for each rate in accompanying notes. A repeat-purchase rate could mean the share of a defined customer cohort that makes another purchase within a specified time; churn may refer to lost customers or lost recurring revenue. Those measures are different. Choose the definition that fits the business and keep it consistent between current and target values.

Choose targets as hypotheses grounded in the baseline and delivery capacity. Do not type an attractive percentage without explaining how it could be reached. For a one-time product with no continuing relationship, a subscription churn measure may be inapplicable; record that and select a relevant retention measure in your working notes. The original named row remains preserved.

2. Plan repeat-purchase support and personalization

The loyalty table asks for Program Type, Reward Structure and Implementation Date. Describe who earns a reward, what they receive and when it becomes available. An implementation date is a proposed planning date until the program is actually approved and configured. An authored example is a useful support session after a repeat purchase, provided the business can deliver it. Cost the reward and make the qualification conditions understandable. A reward that encourages unsuitable purchases is not evidence of customer value.

The personalization table asks for Personalization Element, Target Audience and Implementation Method. Name the actual element: a relevant onboarding checklist, product recommendation or support path. Define the audience using information the business legitimately has. Then explain the method, such as a selected form response routing someone to an appropriate guide. Avoid merely writing “use AI”; specify the input, useful output and review needed. These suggestions describe a design, not an automation that has been deployed.

Connect the two plans to the customer's progress. Loyalty can recognize continued participation, while personalization can reduce irrelevant material and effort. Neither requires a promise that every customer will buy again. Compare the resulting customer experience with the original goal rather than counting rewards issued as success by themselves.

3. Design relevant upsells and cross-sells

The upsell table contains Product, Upsell Offer and Expected Increase in AOV. Explain the difference between the current purchase and the proposed upgrade. State the incremental price and the additional useful scope in supporting notes. The expected increase is an assumption until measured. If only some customers accept an upgrade, its sticker price is not automatically the average increase across all orders.

For a clearly hypothetical calculation, a $20 upgrade accepted on 10% of otherwise comparable orders adds $2 of gross revenue per original order before refunds and additional costs. This arithmetic is authored instruction, not a forecast from the workbook. It helps you avoid entering $20 as the expected average increase for every order. Check margins and fulfillment effort as well as sales revenue.

The cross-sell table contains Bundle Name, Products Included and Discount Offered. List every included item and the actual discount basis. An authored example could pair a tool with an optional maintenance kit that serves the same customer's next need. Compare the bundle price with genuine separate prices where that comparison is used. Do not invent inflated standalone values or omit a required component from the core purchase just to sell it later.

Use the value ladder to decide whether the next step is relevant. Some customers need an upgrade; others need a complementary item; some need neither. Keep the core promise complete and the customer's choice clear. The workbook's two blank rows per table remain available for alternative hypotheses.

4. Improve support and turn feedback into action

The customer-support table asks for Support Strategy, Implementation Steps and Success Criteria. Name a concrete intervention, such as clearer setup instructions or a defined response process. Break implementation into work someone can perform. Define success using the problem being addressed: successful setup, fewer repeat contacts about the same issue or timely resolution. Faster replies alone do not establish that the customer's problem was solved.

The feedback table asks for Feedback Source, Key Insights and Action Plan. Identify the source and preserve what customers actually reported. Separate a quotation or observed event from your interpretation. For example, repeated questions about the first setup step may suggest unclear instructions; verify the cause before assuming the product itself is wrong. An action item should state a concrete change, such as rewriting and testing that instruction. Assigning an owner or review date in your working notes is helpful authored guidance, not a field present in the source table.

Link these tables. If feedback identifies a recurring onboarding difficulty, use the support plan to describe the correction and success criteria. Do not promise 24-hour support, refunds or guarantees merely because those tactics appear in another resource; actual commitments require a workable policy and delivery capacity.

5. Monitor results and adjust the strategy

The metrics table asks for Metric, Baseline Value, Current Value and Adjustment Needed? (Yes/No). Compare the same definition, time period and customer population wherever possible. Record whether a difference is meaningful enough to investigate and explain why. A change in the mix of customers, a promotion or a seasonal effect may explain movement; do not automatically attribute it to the new loyalty program.

The final table asks for Strategy, Change Implemented and Outcome. Record what was actually changed and what observable result followed. If you are still planning, label the proposed change and expected result clearly in your working notes. If the evidence suggests the reward costs too much relative to useful repeat purchases, revise the reward or test a different support approach. Preserve the old result and the reason for the revision. The original Outcome column should distinguish measured results from any explicitly labeled forecast.

The workbook does not establish a causal experiment or statistical threshold. As authored practice, record a baseline, make a bounded change, document other changes occurring at the same time and assess both customer outcomes and economics. Where stronger causal confidence matters, design an appropriate comparison before claiming that the intervention caused the result.

Completion check and sources

You should have filled all ten tables: segments, goals, loyalty, personalization, upsells, cross-sells, support, feedback, metrics and adjustments. Preserve blank or inapplicable fields with an explanation rather than fabricated data. Make the three named goals measurable, label every forecast, and explain how each proposed purchase or service improves the customer's actual experience.

Read the assigned Customer Lifetime Value Optimization Workbook. Its complete native text and all ten original table grids accompany this teaching in the lesson appendix. The workbook remains a planning tool; completing it is not proof that lifetime value increased.

Assigned source links

D0460 original source 1

Original tables and embedded resource links
D0460 native table 1; blank source cells intentionally retained
Segment Name Demographics Purchase Frequency Avg. Order Value
D0460 native table 2; blank source cells intentionally retained
Goal Type Current Value Target Value
Repeat Purchase Rate
Average Order Value
Churn Rate Reduction
D0460 native table 3; blank source cells intentionally retained
Program Type Reward Structure Implementation Date
D0460 native table 4; blank source cells intentionally retained
Personalization Element Target Audience Implementation Method
D0460 native table 5; blank source cells intentionally retained
Product Upsell Offer Expected Increase in AOV
D0460 native table 6; blank source cells intentionally retained
Bundle Name Products Included Discount Offered
D0460 native table 7; blank source cells intentionally retained
Support Strategy Implementation Steps Success Criteria
D0460 native table 8; blank source cells intentionally retained
Feedback Source Key Insights Action Plan
D0460 native table 9; blank source cells intentionally retained
Metric Baseline Value Current Value Adjustment Needed? (Yes/No)
D0460 native table 10; blank source cells intentionally retained
Strategy Change Implemented Outcome
Complete returned native document text

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

Customer Lifetime Value Optimization Workbook
Section 1: Defining Customer Segmentation & LTV Goals
Task 1: Identify Customer Segments
Segment Name
Demographics
Purchase Frequency
Avg. Order Value








Task 2: Set LTV Goals
Goal Type
Current Value
Target Value
Repeat Purchase Rate


Average Order Value


Churn Rate Reduction



Section 2: Retention Strategy Implementation
Task 3: Design Loyalty Program
Program Type
Reward Structure
Implementation Date






Task 4: Personalization Strategy
Personalization Element
Target Audience
Implementation Method







Section 3: Upsell & Cross-Sell Optimization
Task 5: Create Upsell Offers
Product
Upsell Offer
Expected Increase in AOV






Task 6: Implement Cross-Sell Bundles
Bundle Name
Products Included
Discount Offered







Section 4: Customer Support & Satisfaction Enhancements
Task 7: Improve Customer Support
Support Strategy
Implementation Steps
Success Criteria






Task 8: Customer Feedback Analysis
Feedback Source
Key Insights
Action Plan







Section 5: Performance Tracking & Adjustments
Task 9: Monitor Key LTV Metrics
Metric
Baseline Value
Current Value
Adjustment Needed? (Yes/No)








Task 10: Optimization Strategy Adjustments
Strategy
Change Implemented
Outcome







This workbook provides a structured way to track and optimize Customer Lifetime Value (LTV) by following strategic implementation and measuring performance outcomes.
Complete local source copy including original filing metadata and formatting

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/1AKG8K8RHBCHLrJOCCGGXZ2w2nxlTn2HXpDH0z3XewCM/edit?usp=drivesdk"
drive_file_id: "1AKG8K8RHBCHLrJOCCGGXZ2w2nxlTn2HXpDH0z3XewCM"
created: "2025-02-06T23:39:23.879Z"
modified: "2026-06-04T16:43:53.273Z"
---

# Customer Lifetime Value Optimization Workbook

Customer Lifetime Value Optimization Workbook
Section 1: Defining Customer Segmentation & LTV Goals
Task 1: Identify Customer Segments
Segment Name
	Demographics
	Purchase Frequency
	Avg. Order Value
	

	

	

	

	

	

	

	

	Task 2: Set LTV Goals
Goal Type
	Current Value
	Target Value
	Repeat Purchase Rate
	

	

	Average Order Value
	

	

	Churn Rate Reduction
	

	

	________________


Section 2: Retention Strategy Implementation
Task 3: Design Loyalty Program
Program Type
	Reward Structure
	Implementation Date
	

	

	

	

	

	

	Task 4: Personalization Strategy
Personalization Element
	Target Audience
	Implementation Method
	

	

	

	

	

	

	________________


Section 3: Upsell & Cross-Sell Optimization
Task 5: Create Upsell Offers
Product
	Upsell Offer
	Expected Increase in AOV
	

	

	

	

	

	

	Task 6: Implement Cross-Sell Bundles
Bundle Name
	Products Included
	Discount Offered
	

	

	

	

	

	

	________________


Section 4: Customer Support & Satisfaction Enhancements
Task 7: Improve Customer Support
Support Strategy
	Implementation Steps
	Success Criteria
	

	

	

	

	

	

	Task 8: Customer Feedback Analysis
Feedback Source
	Key Insights
	Action Plan
	

	

	

	

	

	

	________________


Section 5: Performance Tracking & Adjustments
Task 9: Monitor Key LTV Metrics
Metric
	Baseline Value
	Current Value
	Adjustment Needed? (Yes/No)
	

	

	

	

	

	

	

	

	Task 10: Optimization Strategy Adjustments
Strategy
	Change Implemented
	Outcome
	

	

	

	

	

	

	________________


This workbook provides a structured way to track and optimize Customer Lifetime Value (LTV) by following strategic implementation and measuring performance outcomes.

Document what each customer was promised, received and reported

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Build an evidence record, one customer at a time

The assigned template creates one outcome record for each paying customer counted under its legacy M10.1 process. The completed collection becomes its M10.2 packet. Those legacy references explain the source's dependencies; they do not change the spreadsheet's current course and lesson assignments. The source proposes filing records at `Drive/C10/Customer-Outcomes/[customer-id]-outcome.md` and in `c10_customer_outcomes`. These are proposed storage destinations, not evidence that either system has been configured or populated.

The record separates what you promised, what you delivered and what the customer said. This distinction supports credible proof in a Brunson-style offer presentation and a realistic assessment of the likelihood-of-achievement dimension in Hormozi's value framework. A completed template is not automatically a testimonial, permission to publish a customer's words or proof of a typical result. Keep customer records appropriately controlled and use authentic evidence rather than invented success stories.

Complete all eight header fields

Enter the Customer ID, Engagement type, Engagement start date, Engagement end date or current status, Price paid gross, Discounts granted, Refund issued and Origin. An anonymized label is acceptable under the source, but protect the information that could reconnect that label with a person. State whether the engagement is a service, cohort, productized purchase or retainer. Give actual dates; if it is ongoing, identify progress, such as milestone two of four, instead of implying completion.

Keep gross payment, discount and refund amounts separate so that a reviewer can reconstruct the transaction. A discount needs its documented reason; a refund should distinguish full, partial and none. For origin, distinguish a warm relationship, referral, outreach, content or another specific source. Do not guess attribution merely because a customer saw several channels. The template is blank; it supplies no real payment records.

1. Recover the original promised outcome

State the specific commitment made when the customer paid and identify where it was recorded. The source asks for an offer section, sales notes, engagement letter, proposal or another traceable record. It also asks whether additional verbal commitments were made during the close. Document those honestly instead of quietly replacing the original promise with a later interpretation.

The template's illustrative eight-week Series B Readiness Package includes four deliverables: a three-statement financial model with sensitivity analysis; a board memo configured for the cap table; a first pitch deck with an operator-validated narrative; and two recorded mock-pitch sessions with feedback. Its April 15, 2026 target is an example date, not a RISER commitment. Notice that these are defined deliverables, not a guarantee that funding will be secured. The record should preserve both the date and the scope actually agreed with a real customer.

2. Record delivery and explain differences

List what was actually produced, shipped or handed over. Link the artifacts and completion evidence in your working record. The source's example lists a four-scenario financial model, the configured board memo, three pitch-deck versions developed during weeks five through seven, two planned mock pitches and a third uncharged session requested in week eight. Each item is observable; “we delivered a transformation” would not provide the same specificity.

Answer the source's Yes, No or Partial question about differences between promised and delivered. Explain each difference. In the extra-session example, a customer stakeholder requested another session and the operator absorbed it because the time was modest. The source connects that event with near-refund analysis and a later pricing review. That is an illustration of scope and capacity learning, not a rule to provide unlimited extra work.

The second example concerns an ambiguous sensitivity-analysis promise. The operator delivered four scenarios, exceeding what the vague original wording explicitly specified. Record that interpretation and decide whether a future offer should define the four scenarios as standard. Keep the original promise intact; an improved future offer must not rewrite what this customer originally bought.

A related module labels adding scope without billing as dishonest, while this template describes honest over-delivery. Uncharged extra work is not inherently dishonest. The useful questions are whether the record is truthful, scope changes were understood, the customer received the promised core work and the business can sustain the extra effort. Preserve the source disagreement rather than misclassify a real engagement to fit a label.

3. Preserve representative customer words

Enter the customer's actual quotation, its source, date and verbatim quality. The quality choices in the source are representative, mixed or brief; for brief feedback, record whether fuller feedback was sought. Do not turn “useful, thanks” into a claim of exceptional satisfaction.

The sample feedback is mixed: the financial model is described positively; the board memo saved time; the pitch deck still needs narrative work according to a co-founder; the extra mock pitch helped; and the customer would recommend the provider while warning that work continues after the engagement. Teach the whole balance. Isolating only the praise would hide the qualification that makes the record informative. The full illustrative quotation is retained in the original appendix and must not be presented as a real RISER testimonial.

If no quotation exists despite attempts, complete all three nonresponse fields: Outreach attempted, Outreach text and Customer response. Record the actual date and channel, the message used and whether there was no response, a refusal or another result. This lesson does not send any messages. Silence is neither a positive endorsement nor proof of dissatisfaction.

The related reviewer demands a sourced quote for every customer, while this template permits honest nonresponse documentation. Mark such a record as lacking customer validation and disclose the acceptance conflict. Never fabricate a quote to obtain an automated pass. A reviewer or course owner must resolve the applicable acceptance policy when that conflict matters.

4. Surface concrete friction

The template suggests three to seven friction points and says fewer than two may reflect an unusually clean engagement or insufficient investigation. This is a source heuristic, not a requirement to invent problems. Report the actual evidence and explain when there was little friction.

Its four examples illustrate distinct mechanisms. First, onboarding took three weeks rather than one because financial records were spread across three systems. Second, a requested investor-list review exceeded scope; the operator absorbed four hours and declined the rest using the agreed scope boundary. Third, the model was returned twice because the CFO and two board members had not agreed on assumptions. Fourth, an eight-day communication gap in week six was followed by cap-table changes requiring a rebuild and a shifted timeline.

For each actual event, state what happened, when, how it affected delivery and what the operator did. Avoid treating customer behavior as a complete causal explanation. The onboarding process, qualification, scope language or scheduling assumptions may also need examination. Conversely, do not assume every problem was within the operator's control.

5. Turn friction into specific learning

The template asks for two to five learnings. Its first example revises a one-week onboarding assumption for customers with fragmented records: either allow two weeks or establish customer-side data consolidation as a prerequisite. Its second adds a stakeholder-alignment question early in onboarding so disagreement appears before the third deliverable. Its third considers increasing mock-pitch sessions from two to three with a corresponding price review because customer feedback identifies their value.

These examples show how an observation can inform a change. They do not establish what every business should do. In your own record, connect each proposed adjustment with the evidence and distinguish an idea from an implemented change. Recheck economics and capacity before making it part of the next offer.

Review the complete packet

Use all eight source checklist items: complete the header; make the promise specific and sourced; document delivery and differences; include an actual dated quotation or the honest nonresponse record; list concrete friction; state evidence-based learnings; avoid paraphrase presented as quotation; and distinguish delivered results from aspirations. Keep each customer separate before synthesizing patterns across the packet.

The related reviewer additionally requires a traceable offer-version number and a current customer status matching the proposed database. The template does not explicitly supply the offer-version field. As an authored reconciliation, add it to your working notes and link it to the applicable offer record; do not claim the original template already includes it or that a database comparison has occurred without access and evidence.

Sources and original template

- Assigned Customer Outcome Documentation Template. - Related customer-outcome reviewer specification. - Related M10.2 outcome-documentation module.

The complete byte-preserved template and original text accompany this teaching. Example records remain illustrations. Completion means an honest, traceable packet with unresolved evidence gaps visible, not an invented customer success narrative.

Assigned source links

D0461 original source 1

Complete native original body, including retained document-part text

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

# Customer Outcome Documentation Template

**Use:** Fill this template once per paying customer counted in M10.1. The packet of all completed entries is the M10.2 deliverable. Filed to Drive at `Drive/C10/Customer-Outcomes/[customer-id]-outcome.md` and written to Supabase `c10_customer_outcomes`.

---

## Header

**Customer ID (anonymized acceptable):** [Customer 1 / Customer A / etc.]
**Engagement type:** [1:1 service / cohort enrollee / productized purchase / retainer / etc.]
**Engagement start date:** [YYYY-MM-DD]
**Engagement end date (or current status if in progress):** [YYYY-MM-DD or "in progress, milestone N of M complete"]
**Price paid (gross):** [$X,XXX]
**Discounts granted (if any):** [$X,XXX with documented reason, or "none"]
**Refund issued (if any):** [Full / partial $X,XXX / none]
**Origin:** [warm network / referral / direct outreach / content-driven / other — be specific]

---

## Section 1 — Promised Outcome (at the time of sale)

**What did you commit to when the customer paid?** Specific, dated, falsifiable.

[Example: "By the end of the 8-week engagement (target end date 2026-04-15), the customer will have a documented Series B Readiness Package consisting of: (1) 3-statement financial model with sensitivity analysis, (2) board memo template configured for their cap table, (3) pitch deck v1.0 with operator-validated narrative, and (4) two recorded mock-pitch sessions with feedback summary."]

**Where is this commitment recorded?** [Offer document section / sales call notes from YYYY-MM-DD / engagement letter / proposal / other source]

**Were there additional verbal commitments made during the close?** [Yes/No; if yes, document them honestly]

---

## Section 2 — Delivered Outcome (at engagement end or current status)

**What did you actually produce, ship, hand over, deliver?** Specific.

[Example: "Delivered: financial model with sensitivity analysis (4 scenarios); board memo template configured to the customer's cap table; pitch deck v1.0 with three iterative versions during weeks 5-7; two mock-pitch sessions plus an unscheduled third mock-pitch session in week 8 at the customer's request (absorbed without additional charge — see friction points)."]

**Are there honest differences between promised and delivered?** [Yes / No / Partial]

If yes, document the differences and the reasoning:

[Example: "Promised: 2 mock-pitch sessions. Delivered: 3 mock-pitch sessions (one absorbed without charge at customer's request). Difference reasoning: customer-side stakeholder added the third session request mid-engagement; operator absorbed rather than negotiating because the additional time was modest. Documented in M10.3 as a near-refund avoidance pattern; pricing-architecture decision in M10.4 may revisit the engagement-window discipline."]

[Or example: "Promised: financial model with 'sensitivity analysis.' Delivered: financial model with 4-scenario sensitivity analysis (operator interpreted 'sensitivity analysis' more rigorously than the offer document specified). The customer-experienced outcome is more thorough than the promised outcome; this is honest over-delivery and is documented for the offer-architecture iteration consideration in C7 (the offer document should be updated to specify 4-scenario sensitivity if this is the new standard)."]

---

## Section 3 — Customer's Verbatim Feedback

**Quote, verbatim, in the customer's own words. Not paraphrased.**

[Example: From email dated 2026-04-22 in response to the operator's feedback request: *"This was useful. The financial model is solid and the board memo template saved me a lot of time. The pitch deck is OK but my co-founder thinks the narrative still needs work — we'll iterate on it before our actual pitches. Thanks for the extra mock-pitch session, that was helpful. Overall: I'd recommend you to other founders, but I'd tell them the work continues after the engagement, not that the package is the finish line."*]

**Source:** [Email / transcribed call / written testimonial / direct outreach response]
**Date:** [YYYY-MM-DD]
**Verbatim quality:** [Representative / mixed / brief — if brief, was outreach attempted to elicit fuller feedback?]

If verbatim feedback is not available despite outreach attempts:

**Outreach attempted:** [Email sent YYYY-MM-DD / call requested YYYY-MM-DD / message sent YYYY-MM-DD]
**Outreach text:** [Brief paste of the outreach message]
**Customer response:** [None received as of [date] / responded but declined to provide feedback / other]

---

## Section 4 — Friction Points

**What went wrong, was difficult, took longer than expected, or required correction during the engagement?** Be specific. List 3-7 friction points typically; if you have fewer than 2, the engagement was either unusually clean or the operator is under-surfacing.

[Example friction points:
- "Onboarding took 3 weeks instead of 1 because the customer's existing financial records were in three different systems requiring custom reconciliation."
- "Mid-engagement scope addition: customer requested an investor list review that was not in the offer document. Operator absorbed half (4 hours) and politely declined the rest, citing the anti-promise on advisor-vs-doer scope. Anti-promise held under pressure."
- "Week 5 deliverable was returned for revision twice because the customer's stakeholders (CFO + 2 board members) had not been aligned on the financial model assumptions before the operator presented v1.0."
- "Customer ghosted for 8 days in week 6, then returned with significant updates to the cap table that required model rebuild. Engagement timeline shifted accordingly."
]

---

## Section 5 — Operator Learnings

**What did this engagement teach you that updates your model?** 2-5 specific learnings.

[Example learnings:
- "The 1-week onboarding assumption is unrealistic for customers with multi-system financial records; the offer document should specify a 2-week onboarding window for that customer profile, OR the offer should specify that pre-onboarding data consolidation is a customer-side prerequisite."
- "Stakeholder alignment is the most common cause of revision cycles. The onboarding template should add an explicit stakeholder-alignment question early; this would surface alignment issues before deliverable-1 rather than at deliverable-3."
- "The mock-pitch session is the most-valued deliverable in customer feedback. Consider expanding from 2 to 3 sessions in the offer architecture (with corresponding price adjustment in C8 architecture refinement)."
]

---

## Submission Checklist

Before adding this entry to the M10.2 packet:

- [ ] Header is complete with engagement type, dates, price, discounts, refunds, origin
- [ ] Section 1 (Promised Outcome) is specific and sourced
- [ ] Section 2 (Delivered Outcome) is specific; honest differences from promised are documented
- [ ] Section 3 (Verbatim Feedback) contains an actual customer quote, sourced and dated, OR documents outreach with customer non-response
- [ ] Section 4 (Friction Points) lists 3-7 specific friction points
- [ ] Section 5 (Operator Learnings) lists 2-5 specific learnings
- [ ] No paraphrased substitutes for verbatim quotes
- [ ] No aspirational outcomes (what may eventually result is distinguished from what was delivered)

---

*Customer Outcome Documentation Template — fill once per customer; aggregate becomes M10.2 deliverable.*

Review a customer-outcome packet without inventing evidence

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

What this specification actually provides

The assigned YAML describes a proposed Customer Outcome Reviewer, version 1.0.0, for the source's M10.2 capstone. It defines inputs, checks, red flags and a JSON-shaped response. It does not prove an agent has been deployed, that its assessments are reliable or that it has access to customer records. Its `model: claude-sonnet-4-7` identifier is unverified here and should not be represented as a confirmed available model. Its `hitl_gated: false` is source configuration text, not authorization to remove human review from this curriculum.

The source explains why the packet matters: later refund analysis, mastery synthesis and graduation review use its evidence. Errors can therefore propagate. The useful discipline is to preserve customer words and trace actual delivery. This supports truthful proof when presenting an offer, including a Brunson-style hook/story/offer sequence, and a grounded assessment of perceived likelihood in Hormozi's value framework. It does not turn a machine verdict into proof that customers achieved results.

Collect the eight specified inputs for every customer

The reviewer expects a customer label; a traceable offer version; the offer-promised outcome quoted from the offer; the delivered outcome supported by evidence; dated and sourced verbatim customer feedback; engagement friction; operator learnings; and current customer status. The status examples are active retainer, completed, mid-engagement, churned, refunded or near-refund. These states may overlap in a real system, so preserve the actual underlying record and explain the applicable state rather than force a misleading description.

Compare the number of entries with the paying-customer count established by the source's M10.1 verdict. The source points to C6/C7 offer iteration records for version traceability. Those are legacy dependencies, not changes to the current 12-course assignments. An offer label without a linked version record is not enough to establish what that customer saw at purchase.

The related template has eight header fields and five content sections, but does not explicitly provide the offer-version field. Add a clearly identified working-note field when applying the reviewer, preserving the original template. Record both original and current versions if the offer changed; do not substitute the newest offer for the one the customer bought.

Apply all nine validation checks

First, check that all eight inputs exist. Second, verify the offer version against the iteration record. Third, compare the promised-outcome quotation with the actual offer. These checks establish completeness and traceability; they do not authorize changing the original promise to match later delivery.

Fourth, verify specific delivered artifacts, dates and milestones. “The customer was happy” does not show what was delivered. Fifth, look for at least one actual customer quotation with a source such as an email date, transcript timestamp or written feedback record. Sixth, distinguish a quotation from the operator's paraphrase. “The customer said it was great” is not an exact customer quotation unless those were demonstrably the customer's actual words in the relevant context.

Seventh, assess whether friction is concrete: what happened, when, and how the operator responded. Eighth, connect each learning with evidence instead of a generic motivational statement. Ninth, compare the customer's status with the proposed Supabase record only when that record is actually available. If access is missing, the comparison is unverified. Do not mark a boolean true merely because the written narrative sounds plausible.

An authored practical workflow is to maintain a small evidence index beside the packet: field, source link, date checked, discrepancy and follow-up. This index is application guidance, not an additional artifact supplied by the YAML. It helps a human reviewer revisit a finding rather than rely on a generated judgment without supporting references.

Interpret the six red flags carefully

The first two flags concern customer quotations that sound like the operator's marketing copy or repeat similar phrasing across multiple customers. These are reasons to inspect the original messages. Writing style alone cannot establish fabrication. Customers may use similar language for legitimate reasons, and an automated classifier cannot authenticate a quote solely from how it sounds.

The third flag is absent or trivial friction. The source states categorically that every real engagement has substantive friction; that is not established by the document. Investigate whether the records are incomplete, but allow honest evidence of a smooth engagement. Never invent problems to make a packet appear credible.

The fourth flag concerns transformation claims unsupported by feedback. Check whether a learning exceeds the observation: a customer saying a template saved time does not prove their business transformed. The fifth concerns status disagreement with the database. Determine whether either record is stale, incorrectly classified or incomplete before accusing anyone of misrepresentation. The sixth concerns a promised outcome that differs from the original offer, potentially shifting the promise after delivery. Preserve the original wording and investigate any documented agreed change.

These flags support careful review. They are not findings of dishonesty until evidence supports that conclusion. The source's emphasis on constructive rigor is useful; discomfort, uniformly positive feedback or polished writing do not by themselves prove whether a packet is truthful.

Use the 6% rule as a source-specific heuristic

The YAML invokes a C1 doctrine: surface at least 16 data points across customer feedback, friction and learnings to identify one or two strong patterns. Its purpose is to discourage selecting only evidence that supports a preferred story. Preserve that stated threshold and its cross-reference, but label it a course-specific heuristic. The source supplies no statistical validation that 16 points guarantees a reliable pattern, or that one or two patterns will always emerge.

Keep contrary observations and identify which customer supplied each data point. Sixteen statements from one customer are not equivalent to sixteen independent customers. Do not multiply, fabricate or split observations merely to reach a quota. If evidence is limited, report that limitation and avoid a confident generalization. The source assigns cross-customer pattern development to later M10.5 work; this review establishes whether raw material exists for that work.

Understand every output field

The proposed response reports `customers_documented`, `expected_count` and `match`. Its `per_customer_review` array contains a `label`, a `completeness` object, `red_flags` and `revisions_required`. The completeness object has nine booleans: `all_8_fields`, `offer_version_traceable`, `promised_outcome_quoted`, `delivered_outcome_evidenced`, `verbatim_feedback_present`, `verbatim_feedback_sourced`, `friction_points_specific`, `learnings_evidence_tied` and `status_matches_supabase`.

At packet level, preserve `packet_red_flags`, `verdict` and `narrative_summary`. The verdict choices in this specification are APPROVED and REVISIONS_REQUIRED. The original JSON example uses placeholders such as N and `true | false`; it is an illustrative shape, not valid JSON ready to submit unchanged. In an implementation, replace those placeholders with actual values and validate the result. No implementation is deployed by this lesson.

A false or unverified finding needs a specific explanation and a feasible revision. For example, a missing offer version calls for locating the versioned source, not rewriting the outcome to sound more credible. The provided schema has no explicit unknown boolean state; an implementation must define how unavailable evidence is represented rather than silently treating unknown as confirmed. Preserve the original schema in the appendix and label any proposed extension as authored.

Reconcile acceptance conflicts and deferred submissions

The related template and M10.2 module allow a truthful record of unsuccessful attempts to obtain feedback. This reviewer nevertheless requires a quotation. Record the nonresponse, flag the outcome as not customer-validated and expose the acceptance conflict. The module also uses CONFORMS, REVISIONS_REQUESTED and OUTCOME_VAGUE_FLAG, whereas this YAML uses two different verdict labels. Do not claim they are already interoperable or silently discard the specificity flag; the intended mapping needs an explicit design decision.

The usage notes say operators in deferred-submission mode still document their existing one or two paying customers and update the packet as customers are added. Graduation should read the latest packet version. That is a source workflow, not proof that the prerequisite verdict or database exists. Record version dates and avoid presenting an earlier incomplete packet as the final current record. The proposed destination is `c10_customer_outcomes`; no database write is performed here.

Resources and complete specification

- Assigned customer-outcome reviewer YAML. - Related outcome template. - Related M10.2 module.

The full original YAML remains in the appendix. Apply its checks as an evidence review, while keeping unsupported thresholds, unverified integrations and conflicting acceptance rules visible.

Assigned source links

D0462 original source 1

Complete native original body, including retained document-part text

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

name: customer-outcome-reviewer
version: 1.0.0
model: claude-sonnet-4-7
course: C10 Proof Threshold — Stage 2 Capstone
modules: [M10.2 Customer Outcome Documentation]
stage: 2
hitl_gated: false

description: >
  Validator for the M10.2 Customer Outcome Documentation packet.
  Reviews per-customer documentation for completeness, verbatim
  feedback presence, and structural integrity. The packet is the
  evidentiary substrate for M10.3 Refund Analysis, M10.5 Mastery
  Synthesis, and M10.8 Stage 2 Graduation Document. Gaps in M10.2
  cascade into FAIL verdicts at M10.8.

system_prompt: |
  You are the Customer Outcome Reviewer for C10. Your job is to
  validate the operator's M10.2 Customer Outcome Documentation packet,
  ensuring each paying customer (per M10.1 verdict) has complete,
  honest, evidence-backed outcome documentation.

  CONTEXT: M10.2 produces the data that every subsequent C10 module
  reads. The Mastery Synthesis at M10.5 surfaces patterns from M10.2.
  The Refund Analysis at M10.3 cross-references M10.2 outcomes. The
  Stage 2 Graduation Document at M10.8 quotes M10.2 verbatim feedback
  as evidence. Incomplete or rationalized M10.2 entries propagate
  errors forward.

  The most common failure pattern at M10.2 is operator paraphrase of
  customer feedback rather than verbatim quotation. The operator's
  interpretation of what the customer meant is not evidence; the
  customer's actual words are evidence.

  YOUR JOB: Validate the documentation packet, surface gaps, and
  return a packet-completion verdict.

  ---

  ## Inputs

  The operator submits one Customer Outcome Documentation entry per
  paying customer (count from M10.1 validator verdict). Each entry
  contains:

  1. Customer label (anonymized)
  2. Offer version delivered, with traceable version number to C6/C7
     iteration log
  3. Offer-promised outcome (quoted from offer document)
  4. Delivered outcome (operator's account, evidence-backed)
  5. Customer's verbatim feedback (quoted text, dated, sourced)
  6. Friction points encountered during engagement
  7. Operator learnings from the engagement
  8. Customer status at time of submission (active retainer / completed /
     mid-engagement / churned / refunded / near-refund)

  ## Validation checks per customer entry

  - All 8 fields present
  - Offer version traceable to C6/C7 iteration log (no orphan offer
    versions)
  - Offer-promised outcome quoted from offer, not paraphrased by
    operator
  - Delivered outcome described with specific evidence (not "the
    customer was happy" — what was actually delivered, by what date,
    against what milestone)
  - At least one piece of verbatim customer feedback present, with
    source attribution (email date, transcript timestamp, written
    feedback document name)
  - Verbatim feedback is actual customer text in quotation marks,
    not operator paraphrase ("the customer said it was great" is not
    verbatim feedback)
  - Friction points are specific and concrete (not "some challenges
    arose" — what challenges, when, what was the operator's response)
  - Operator learnings are evidence-tied, not generalized platitudes
  - Customer status matches Supabase record

  ## Red flags

  - Verbatim feedback contains text that pattern-matches operator
    voice rather than customer voice (overly polished, reads like
    operator's marketing copy)
  - Multiple customer entries have similar verbatim feedback phrasing
    (suggests fabrication or memory-reconstruction without source)
  - Friction points are absent or trivially listed ("scheduling was
    sometimes challenging") — every real engagement has substantive
    friction; absence indicates incomplete documentation
  - Operator learnings claim transformation patterns not supported by
    feedback evidence
  - Customer status does not match Supabase record
  - Offer-promised outcome description differs from offer document
    text (operator may be soft-shifting promised outcome to match
    delivered outcome retroactively)

  ## 6% Rule application

  Per the C1 doctrine: surface 16+ data points (across all customers'
  feedback, friction points, learnings) to identify the 1-2 strongest
  patterns. The operator should be working with raw evidence at scale,
  not pre-filtering to the patterns they expect to find.

  Validate that the documentation packet contains substantial raw
  evidence (not just summary statements) sufficient for pattern
  surfacing at M10.5.

  ## Output format

  Return JSON:

  ```json
  {
    "customers_documented": N,
    "expected_count": N,
    "match": true | false,
    "per_customer_review": [
      {
        "label": "Customer A",
        "completeness": {
          "all_8_fields": true | false,
          "offer_version_traceable": true | false,
          "promised_outcome_quoted": true | false,
          "delivered_outcome_evidenced": true | false,
          "verbatim_feedback_present": true | false,
          "verbatim_feedback_sourced": true | false,
          "friction_points_specific": true | false,
          "learnings_evidence_tied": true | false,
          "status_matches_supabase": true | false
        },
        "red_flags": ["red flag 1"],
        "revisions_required": ["revision 1"]
      }
    ],
    "packet_red_flags": ["packet-level red flag"],
    "verdict": "APPROVED | REVISIONS_REQUIRED",
    "narrative_summary": "string"
  }
  ```

  ## Tone

  Constructive and rigorous. The operator working honestly will produce
  a packet with friction points and uncomfortable learnings; that is
  the signal of real documentation. A packet that is uniformly
  positive across all customers is the signal of incomplete
  documentation, not the signal of a great operator.

  Push back on paraphrase-as-feedback every time. Praise specific
  evidence. Send entries back for revision until verbatim sourcing
  is consistent.

usage_notes: |
  Runs at end of M10.2. Output is the evidence base for M10.3, M10.5,
  and M10.8.

  Operators in deferred-submission mode (per M10.1 verdict) still
  complete M10.2 for their existing 1-2 paying customers. The packet
  is updated as new paying customers are added; the M10.8 submission
  reads the most recent packet version.

  Output filed in Supabase as `c10_customer_outcomes`.

Analyze an event-based offer without confusing forecasts with results

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Read the example as a proposed campaign

The assigned Example Offer analyzes a proposed $40 birthday sale. It covers positioning, funnel flow, launch timing, five expert-attributed tips and a ten-product sales forecast. The linked birthday-sale page could not be accessed during review, so this lesson cannot confirm its actual prices, products, deadline, retirement claims or historical performance. The document's numbers are source assumptions, not RISER results or a verified account of that seller's business.

Use the example to learn how the parts of an offer connect and how to check the arithmetic. The complete original text and native forecast table remain in the appendix. The analysis below is authored teaching that identifies assumptions and discrepancies; it does not launch the campaign or send its suggested emails and messages.

1. Connect the event, value and deadline honestly

The birthday hook connects turning 40 with a $40 price. That relationship gives a memorable reason for the promotion. An authored application could use a real business milestone, provided the event and stated reason are true. The source attributes this to Brunson and Frank Kern; the specific attribution is not independently authenticated. The useful mechanism is a clear, relevant story around the offer, not invented personal history.

The document compares a $40 sale price with purported normal values of $197–$497. Such figures need evidence. A number crossed out on a page is not proof that the item was normally sold at that price. The separate listed values sum to $3,567, while the later launch copy proposes a $3,000 comparison. Those are different figures with no explanation in the source. Resolve the comparison basis before presenting either as a genuine saving.

The source invokes the Hormozi Value Equation but writes the denominator ambiguously. The intended framework is desired outcome multiplied by perceived likelihood, divided by the product of time delay and effort/sacrifice. Review the official Acquisition.com material. Treat those dimensions as offer-design questions here, not a calibrated numerical model that predicts conversion. Instant access can reduce delivery delay, but it does not eliminate the time and effort needed to apply a course. Screenshots also require authentic context and do not prove everyone will obtain a seven-figure outcome.

The proposed countdown and “retiring forever” statement create urgency only if the limitation is real and honored. A birthday alone does not prove permanent retirement. State the actual closing time and what changes afterward. Do not recycle a supposedly permanent deadline or claim the sale ends forever when another identical sale is planned.

2. Map traffic, checkout and delivery separately

The source proposes Instagram, TikTok, email, affiliates and possibly small paid campaigns as traffic sources. These are a channel list, not proof of an audience or permission to contact anyone. The suggested call to action offers a $497 framework for $40; use that comparison only when the original price claim is supportable.

The checkout design uses one cart rather than ten competing checkout paths. A single cart can let a customer choose an item and review optional additions, but the available product choices and prices must remain clear. The base offer is one program for $40. The first bump adds all ten programs for $97 more, meaning a $137 total if purchased with the base item. The wording must clarify that the original program is included in the ten, so the customer does not think they are buying eleven different programs.

The next proposed offer is a $297 lifetime coaching vault after purchase. A post-purchase offer is a separate upsell step even though the source calls it Bump #2. Define what “lifetime” means and what access actually includes before using it. The later $997–$2,997 core coaching/program offer is another proposed step; it is not automatically the same product as the $297 vault.

The source assumes a 10–20% first-bump acceptance rate without evidence. As authored arithmetic, 100 base orders produce $4,000 gross revenue. If ten buyers add $97, the added revenue is $970 and gross revenue becomes $4,970; twenty accepted bumps would yield $5,940. That is a 24.25–48.5% increase in this isolated scenario, not proof of a two- or threefold increase. Refunds, fees, taxes and fulfillment costs are not modeled here.

Delivery suggestions include Kajabi, Thinkific, Dropbox and Google Drive for PLR. Naming a tool does not configure access, payment routing or fulfillment. PLR rights must be established from the actual license. Test the correct purchase-to-access path before release. Replace the source's proposed immediate income-promise upsell with a truthful explanation of the next relevant support option; buying a low-cost framework does not establish a path to $10,000 months.

3. Understand the complete launch sequence

The proposed prelaunch lasts three to five days and uses mini-lessons addressing objections. The source labels this an Amy Porterfield “Invisible Bridge,” an attribution not verified here. Its suggested claim of scaling to $1 million without ads would require actual evidence; do not adopt it as your own history. A useful mini-lesson can demonstrate one bounded principle and explain what the paid resource adds.

Day one combines an announcement with a story. Days two and three show student results and behind-the-scenes material. Use only genuine results with appropriate context and permission; a demonstration or clearly labeled hypothetical example can teach without pretending to be a customer case. Day four explains the value, but the proposed $40 versus $3,000 comparison must be reconciled with the actual product and pricing evidence. Day five uses email, SMS and Instagram stories to announce the real deadline. No messaging is sent by this lesson.

The statement that most sales close in the last twelve hours is an unsupported generalization in the source. Measure the actual timing rather than plan cash needs around that claim. After the sale, the proposed waitlist says the promotion is closed and future access will be full price. Use that wording only if it accurately describes the actual next offer. Survey buyers to inform the next minimum viable offer; preserve both helpful and critical feedback.

4. Apply the five expert-attributed tips with evidence

The first tip, attributed to Frank Kern, emphasizes the customer's after-state. Explain a deliverable and plausible benefit without converting “$10k months without ads or burnout” into a guaranteed promise. The second, attributed to Brunson, uses future pacing: describe how a person could use the purchase over thirty days. Clearly distinguish a possible application from a promised thirty-day result.

The third tip, attributed to Hormozi, uses price anchoring. Test understandable comparisons based on real prices or a clearly explained valuation basis; do not assume that displaying a crossed-out number makes it legitimate. The fourth, attributed to Brendan Kane, tests multiple short-form openings. Measure retention and qualified action, but do not repeat the source's claim that the first three seconds universally matter more than the funnel. The fifth, attributed to Amy Porterfield, organizes each nurture email around an objection. Answer the actual concern rather than manufacture fear or hide limitations.

The document also proposes $50–$100 per day in retargeting spend and claims five-to-eightfold higher conversion. Neither is established for this audience. A budget requires actual economics, audience size and performance evidence. Preserve the suggestion as a source hypothesis; no ads, audience uploads or spending are activated here. The ClickFunnels hook/story/offer explanation is a related primary resource, separate from these unverified individual attributions.

5. Check every forecast row and the shared assumptions

All ten rows use a $40 base price. The source gives the following proposed normal values, unit ranges and gross revenues:

OfferSource normal valueForecast unitsForecast gross revenue
Profitable Digital Product Academy$497500–800$20,000–$32,000
20 PLR Products$297400–600$16,000–$24,000
Sales Automation System$497600–1,000$24,000–$40,000
To Consistent $10k Months Masterclass$297400–600$16,000–$24,000
Level Up – 5 Day Challenge$297300–500$12,000–$20,000
12 Mini Courses$444400–700$16,000–$28,000
6-Figure Year Secrets$497500–800$20,000–$32,000
30 DFY Content Videos + Photos$247200–400$8,000–$16,000
Faceless Social Media Mastery$197300–500$12,000–$20,000
Social Media Revolution Program$297600–1,000$24,000–$40,000

Each revenue row equals units multiplied by $40. The rows sum to 4,200–6,900 unit purchases and $168,000–$276,000. That arithmetic is consistent, but the demand assumptions are not demonstrated. The source also assumes about 50,000 warm audience reach and 2–5% conversion. Applied to unique people, those percentages imply 1,000–2,500 buyers, not 4,200–6,900 separate buyers. Multiple purchases might explain some difference, but the source supplies no purchase-frequency or overlap model.

Define whether a unit means a separately purchased program, a customer, an order or access through a bundle. Counting ten all-access entitlements as ten separate $40 purchases would overstate revenue. Do not add independent-looking product forecasts when they draw on the same finite audience without accounting for overlap. Gross sales also differ from profit and cash retained after refunds and expenses. The source's suggestion that upsells could realistically multiply revenue two to three times is not substantiated by its table.

Build your own seven-step plan

Preserve the source's sequence: choose a real event; establish credible value anchors; select a clear promotional price such as its $40/$50/$99 examples; design a unified cart with an optional all-access bump; educate before launch; close on an actual deadline; and offer a relevant core program afterward. Each step needs real product, audience, pricing and capacity evidence. None requires copying the example's unsupported earnings claims.

The final suggestion is to turn an actual campaign into a workshop case study. Document the process and actual results first. The proposed title claiming more than $200,000 in five days must not be used unless that result occurred and is accurately substantiated. A hypothetical forecast does not become a case study because a document calls it one. The embedded offer to draft emails is source text, not an instruction executed by this lesson.

Resources and complete original

- Assigned Example Offer document. - Original linked sale page — access unavailable during review. - Acquisition.com Value Equation. - ClickFunnels hook, story and offer.

The complete original source and eleven-row native table accompany this teaching. Your finished exercise is a clearly defined, financially reconciled campaign hypothesis with its evidence gaps visible, not a claim that the example's forecast has happened.

Assigned source links

D0463 original source 1

Original tables and embedded resource links
D0463 native table 1; blank source cells intentionally retained
Offer Base Price Normal Value Expected Units @ $40 Revenue
Profitable Digital Product Academy $40 $497 500–800 $20k–$32k
20 PLR Products $40 $297 400–600 $16k–$24k
Sales Automation System $40 $497 600–1,000 $24k–$40k
To Consistent $10k Months Masterclass $40 $297 400–600 $16k–$24k
Level Up – 5 Day Challenge $40 $297 300–500 $12k–$20k
12 Mini Courses $40 $444 400–700 $16k–$28k
6-Figure Year Secrets $40 $497 500–800 $20k–$32k
30 DFY Content Videos + Photos $40 $247 200–400 $8k–$16k
Faceless Social Media Mastery $40 $197 300–500 $12k–$20k
Social Media Revolution Program $40 $297 600–1,000 $24k–$40k

Original embedded hyperlink spans:

Complete returned native document text

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

Example Offer
https://www.nataliaraitomaeki.com/40
I’ll break this down into:
Offer Positioning & Psychology

Sales Process / Funnel Flow

Launch Sequence (pre-launch → launch → close)

Secrets, Tips, Expert Shortcuts

Sales Volume Predictions per Offer


1. 🧲 Offer Positioning & Psychology
The Birthday Hook: Turning 40 → “$40 Fire Sale.” This is pure Russell Brunson meets Frank Kern psychology → use irony + urgency.

Stacked Value: Each item is normally $197–$497 → discounted to $40. Hormozi’s value equation is firing here:
 Dream Outcome (7-figure frameworks) × Perceived Likelihood (proof + screenshots) ÷ Time Delay (instant access) × Effort & Sacrifice (minimal) = irresistible.

Scarcity: Real deadline timer + “retiring forever” → creates action.


2. 🛠 Sales Process / Funnel Flow
Step 1. Traffic → Sales Page
Sources: Instagram, TikTok, email, affiliates, maybe small PPC.

CTA: “Grab any $497 framework for $40 — celebrating turning 40 🎉.”

Step 2. Sales Page → One Checkout
Do not fragment attention. Instead of 10 different checkout buttons, funnel to one cart with bump offers.

Example:

Base: Pick any program for $40.

Bump #1: “Add ALL 10 programs for $97 more.” (10–20% uptake).

Bump #2 (post-purchase): “Unlock lifetime coaching vault for $297.”

Step 3. Delivery
Auto-fulfill via Kajabi, Thinkific, or Dropbox/Google Drive for PLR.

Immediately start upsell indoctrination: “Congrats, you saved $400+… but let me show you how to turn this into $10k months.”


3. 🚀 Launch Sequence
Pre-Launch (“Invisible Bridge” — Amy Porterfield)
3–5 days before cart open:

Drop mini-lessons busting objections.

Example: “You think you need ads to sell? I scaled to $1M without ads.”

Launch (Cart Open)
Day 1: Announcement + story-based post.

Day 2–3: Social proof (student wins, behind-the-scenes).

Day 4: Stack the value (compare $40 vs. $3,000 full price).

Day 5 (last day): Scarcity push. Use email + SMS + Instagram stories. Most sales close in last 12 hours.

Post-Launch
Waitlist CTA: “Sale is closed. Next time, price = full ticket.”

Survey buyers → Use feedback for next MVO.


4. 🧠 Secrets, Tips, Expert Advice
Secret #1 (Frank Kern): Don’t sell features, sell the after state. Every headline should read: “Finally hit $10k months without ads or burnout.”

Secret #2 (Russell Brunson): Use “future pacing.” Show them where they’ll be 30 days after applying what they buy.

Secret #3 (Hormozi): Test price anchoring. Make sure you show full price crossed out above every $40 offer.

Secret #4 (Brendan Kane): Test multiple hooks on short-form content. Your 3-second open matters more than your funnel.

Secret #5 (Amy Porterfield): Nurture with objections. Each email = bust 1 objection.

Pro shortcut: Run a retargeting ad for $50–100/day just on people who clicked but didn’t buy. These convert at 5–8× higher.

5. 📈 Sales Volume Predictions (per offer)
Assumptions:
Audience warm (IG + email list ~50k reach).

Conversion baseline = 2–5% of warm audience.

Scarcity flash sales spike harder than evergreen funnels.

Offer
Base Price
Normal Value
Expected Units @ $40
Revenue
Profitable Digital Product Academy
$40
$497
500–800
$20k–$32k
20 PLR Products
$40
$297
400–600
$16k–$24k
Sales Automation System
$40
$497
600–1,000
$24k–$40k
To Consistent $10k Months Masterclass
$40
$297
400–600
$16k–$24k
Level Up – 5 Day Challenge
$40
$297
300–500
$12k–$20k
12 Mini Courses
$40
$444
400–700
$16k–$28k
6-Figure Year Secrets
$40
$497
500–800
$20k–$32k
30 DFY Content Videos + Photos
$40
$247
200–400
$8k–$16k
Faceless Social Media Mastery
$40
$197
300–500
$12k–$20k
Social Media Revolution Program
$40
$297
600–1,000
$24k–$40k
👉 Estimated Total Revenue Range: $168k – $276k from a single 5-day “birthday blitz.”
 👉 With proper bumps & upsells (all-access pass), you could realistically 2–3× that revenue.

🔑 Replicable Framework
Create an Event (birthday, milestone, holiday).

Anchor Big Value ($297–$497 courses).

Flash-Sale Them All at One Irresistible Price ($40, $50, $99).

Use a Unified Cart → One bump = All Access.

Pre-Launch Education (Invisible Bridge → bust objections).

Close with Scarcity → “Sale ends forever.”

Upsell to Core Offer ($997–$2,997 coaching/program).


⚡Pro Tip: Document the process as a “case study funnel.” After you run this once, you can relaunch the exact framework as a paid workshop: “How I did $200k+ in 5 days with my $40 Birthday Sale.” (Meta-offer → sells itself).

👉 Do you want me to now draft the email + story sequence (subject lines, hooks, story angles, and CTAs) so you have the full copy package ready to deploy for this sale?
Complete local source copy including original filing metadata and formatting

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/1zqTmKJtuA0GETIi5TDwqzI-nN-H1lr6OeIPVeHj0AyQ/edit?usp=drivesdk"
drive_file_id: "1zqTmKJtuA0GETIi5TDwqzI-nN-H1lr6OeIPVeHj0AyQ"
created: "2025-09-30T17:45:52.977Z"
modified: "2026-06-04T15:20:09.346Z"
---

# Example Offer

Example Offer
https://www.nataliaraitomaeki.com/40
I’ll break this down into:
1. Offer Positioning & Psychology

2. Sales Process / Funnel Flow

3. Launch Sequence (pre-launch → launch → close)

4. Secrets, Tips, Expert Shortcuts

5. Sales Volume Predictions per Offer

________________


1. 🧲 Offer Positioning & Psychology
   * The Birthday Hook: Turning 40 → “$40 Fire Sale.” This is pure Russell Brunson meets Frank Kern psychology → use irony + urgency.

   * Stacked Value: Each item is normally $197–$497 → discounted to $40. Hormozi’s value equation is firing here:
Dream Outcome (7-figure frameworks) × Perceived Likelihood (proof + screenshots) ÷ Time Delay (instant access) × Effort & Sacrifice (minimal) = irresistible.

   * Scarcity: Real deadline timer + “retiring forever” → creates action.

________________


2. 🛠 Sales Process / Funnel Flow
Step 1. Traffic → Sales Page
      * Sources: Instagram, TikTok, email, affiliates, maybe small PPC.

      * CTA: “Grab any $497 framework for $40 — celebrating turning 40 🎉.”

Step 2. Sales Page → One Checkout
         * Do not fragment attention. Instead of 10 different checkout buttons, funnel to one cart with bump offers.

         * Example:

            * Base: Pick any program for $40.

            * Bump #1: “Add ALL 10 programs for $97 more.” (10–20% uptake).

            * Bump #2 (post-purchase): “Unlock lifetime coaching vault for $297.”

Step 3. Delivery
               * Auto-fulfill via Kajabi, Thinkific, or Dropbox/Google Drive for PLR.

               * Immediately start upsell indoctrination: “Congrats, you saved $400+… but let me show you how to turn this into $10k months.”

________________


3. 🚀 Launch Sequence
Pre-Launch (“Invisible Bridge” — Amy Porterfield)
                  * 3–5 days before cart open:

                     * Drop mini-lessons busting objections.

                     * Example: “You think you need ads to sell? I scaled to $1M without ads.”

Launch (Cart Open)
                        * Day 1: Announcement + story-based post.

                        * Day 2–3: Social proof (student wins, behind-the-scenes).

                        * Day 4: Stack the value (compare $40 vs. $3,000 full price).

                        * Day 5 (last day): Scarcity push. Use email + SMS + Instagram stories. Most sales close in last 12 hours.

Post-Launch
                           * Waitlist CTA: “Sale is closed. Next time, price = full ticket.”

                           * Survey buyers → Use feedback for next MVO.

________________


4. 🧠 Secrets, Tips, Expert Advice
                              * Secret #1 (Frank Kern): Don’t sell features, sell the after state. Every headline should read: “Finally hit $10k months without ads or burnout.”

                              * Secret #2 (Russell Brunson): Use “future pacing.” Show them where they’ll be 30 days after applying what they buy.

                              * Secret #3 (Hormozi): Test price anchoring. Make sure you show full price crossed out above every $40 offer.

                              * Secret #4 (Brendan Kane): Test multiple hooks on short-form content. Your 3-second open matters more than your funnel.

                              * Secret #5 (Amy Porterfield): Nurture with objections. Each email = bust 1 objection.

Pro shortcut: Run a retargeting ad for $50–100/day just on people who clicked but didn’t buy. These convert at 5–8× higher.
________________


5. 📈 Sales Volume Predictions (per offer)
Assumptions:
                                 * Audience warm (IG + email list ~50k reach).

                                 * Conversion baseline = 2–5% of warm audience.

                                 * Scarcity flash sales spike harder than evergreen funnels.

Offer
	Base Price
	Normal Value
	Expected Units @ $40
	Revenue
	Profitable Digital Product Academy
	$40
	$497
	500–800
	$20k–$32k
	20 PLR Products
	$40
	$297
	400–600
	$16k–$24k
	Sales Automation System
	$40
	$497
	600–1,000
	$24k–$40k
	To Consistent $10k Months Masterclass
	$40
	$297
	400–600
	$16k–$24k
	Level Up – 5 Day Challenge
	$40
	$297
	300–500
	$12k–$20k
	12 Mini Courses
	$40
	$444
	400–700
	$16k–$28k
	6-Figure Year Secrets
	$40
	$497
	500–800
	$20k–$32k
	30 DFY Content Videos + Photos
	$40
	$247
	200–400
	$8k–$16k
	Faceless Social Media Mastery
	$40
	$197
	300–500
	$12k–$20k
	Social Media Revolution Program
	$40
	$297
	600–1,000
	$24k–$40k
	👉 Estimated Total Revenue Range: $168k – $276k from a single 5-day “birthday blitz.”
👉 With proper bumps & upsells (all-access pass), you could realistically 2–3× that revenue.
________________


🔑 Replicable Framework
                                    1. Create an Event (birthday, milestone, holiday).

                                    2. Anchor Big Value ($297–$497 courses).

                                    3. Flash-Sale Them All at One Irresistible Price ($40, $50, $99).

                                    4. Use a Unified Cart → One bump = All Access.

                                    5. Pre-Launch Education (Invisible Bridge → bust objections).

                                    6. Close with Scarcity → “Sale ends forever.”

                                    7. Upsell to Core Offer ($997–$2,997 coaching/program).

________________


⚡Pro Tip: Document the process as a “case study funnel.” After you run this once, you can relaunch the exact framework as a paid workshop: “How I did $200k+ in 5 days with my $40 Birthday Sale.” (Meta-offer → sells itself).
________________


👉 Do you want me to now draft the email + story sequence (subject lines, hooks, story angles, and CTAs) so you have the full copy package ready to deploy for this sale?

Use all 46 headline patterns with a truthful content promise

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

What this library teaches

The assigned document contains 25 Gains patterns, 11 Threats patterns and 10 Proof patterns. These are writing templates, not evidence that any particular claim is true or that a headline will convert. Two entries appear incomplete or awkward; they remain preserved and are identified below. Fill placeholders with actual audience needs and supported facts. The application notes are authored guidance, not additional text claimed to be in the source.

Use a headline to open a useful lesson or offer. In the ClickFunnels hook/story/offer framework, the hook should lead into the story and offer actually delivered. In the Acquisition.com value framework, a desired result and confidence matter alongside time and effort; a headline must not erase those conditions. Select a pattern because it fits the content and reader, not because it sounds dramatic.

Each row preserves the original pattern and explains the distinct decision needed to use it responsibly. The bracketed placeholders are intentionally unfilled. They are not missing factual data that should be invented.

Gains patterns

No.Original patternHow to teach and apply it
1Where [desired result] Is And How To Get ItName where the useful opportunity exists and show the actual steps to access it; the lesson must answer both halves.
2Discover The [desired result] SecretReplace the vague secret with a specific overlooked method and explain its limits. Do not imply exclusivity without evidence.
3[blank] Your Way To A [desired result] YouSpecify the action in the first blank and the achievable change in the second; connect the action to a demonstrable process.
4To People That Want To [desired result] But Can’t Get StartedIdentify the actual starting barrier, then offer a manageable first step. Do not label all hesitant readers as unmotivated.
5You, a [desired result]Make the reader’s potential role or capability concrete. An identity statement needs a useful path, not flattery alone.
6Stop [undesired result]Name an unwanted result and explain what can reduce it. Avoid claiming that a method eliminates every possible cause.
7You Too Can [desired result] in [time period] with [blank]A timed outcome needs substantiation and stated conditions. Replace a universal promise with a bounded demonstration when evidence is limited.
8How To Become [desired result] When You [something challenging]Explain how the challenging circumstance changes the method. Do not imply that an important prerequisite can always be bypassed.
9here’s Big [desired result] In [blank]The original begins “here’s Big”; its wording appears incomplete. Clarify the opportunity and its context in an explicitly edited draft.
10You Don’t Have to Be [something challenging] to be [desired result]Distinguish unnecessary credentials or barriers from genuinely required skills. Explain what the reader does need to succeed.
11Little Known Ways to [blank]A lesser-known approach should be named and taught. “Little known” is a claim about awareness, not a substitute for usefulness.
12How to turn [blank] into [desired result]Show the transformation process between input and result, including costs and constraints; do not imply a magical conversion.
13How To Build a [blank] You Can Be Proud OfDefine what makes the finished artifact useful and reviewable. Pride is subjective, so include concrete quality criteria.
14The Lazy [blank’s] Way to [desired result]Translate “lazy” into reduced unnecessary effort rather than no effort. State the work the reader still needs to perform.
15How To Make People Line Up And Beg To [blank]This exaggerates demand. Use authentic demand evidence or rewrite it as making an offer easier to understand and evaluate.
16How To Get [desired result] Out Of [blank]Explain how a specific input or asset can contribute to the result, and identify the conditions under which it will not.
17How To [desired result] When You’re Not [blank]Identify the actual missing characteristic and explain an alternative route. Avoid treating essential qualifications as irrelevant.
18How To Take The Headache Out Of [blank]Name the friction being reduced and demonstrate the improvement. Some complexity may remain; make that limitation understandable.
19X Questions Answered About [blank]Specify the exact number of questions and answer every one in the content. Select questions from real audience needs.
20Give Me [short time period] and I’ll Give You [desired result]This trades a short time commitment for a result. Define the deliverable and substantiate the timing before making the promise.
21Answered: Your Most Burning Questions About [blank]Use actual recurring audience questions and answer them directly. Do not promise answers that the lesson merely postpones.
22Take X minutes to get started with [blank]... you'll be happy you did!State a realistic time to begin and a concrete first action. The claim concerns starting, not necessarily completing the whole outcome.
23Who Else Wants [desired result]?An invitation can identify shared interest without pretending a large group already wants the result. Explain the relevant next step.
24How to fast-track your [desirable result]Specify which delay is reduced and what makes that possible. Faster access alone does not establish faster customer results.
25How [impressive number] Got [desired result] WithoutThe source ends after “Without” and is incomplete. Retain it in the original, then supply only an explicitly authored, evidenced ending.

Threats patterns

No.Original patternHow to teach and apply it
1Do You Recognize the [number] Early Warning Signs of [blank]?List the stated number of observable warning signs and explain what each indicates. A warning is not a diagnosis without evidence.
2If You Don’t [blank] Now, You’ll Hate Yourself LaterThe self-hatred framing applies pressure. Rewrite around a concrete consequence and an informed choice, without shaming the reader.
3I've Lied to You for [time period] NowDo not invent a confession. If correcting a real earlier error, identify what was wrong, the correction and its effect.
4The Biggest Lie In [your industry]Distinguish a demonstrably false statement from an opinion or disagreement. Explain evidence rather than accuse an industry indiscriminately.
5X Shocking Mistakes Killing Your [blank]Identify the exact mistakes and their actual effects. Avoid claiming that every mistake destroys a result when the evidence is weaker.
6Don’t Try [blank] Without [desired action] FirstExplain a genuinely necessary preparation or dependency before the action. Do not manufacture a prerequisite merely to sell another product.
7[blank] May Be Dangerous To [something precious]A danger claim needs specific, credible evidence and proportionate language. Do not exploit concern about something precious with speculation.
8[blank] May Be Causing You To Lose Out On [desired result]Frame a possible missed benefit as a hypothesis and show how to assess it. “May” does not excuse an otherwise misleading claim.
9At Last, The Secret To [desired result] Is RevealedDespite its placement in Threats, this is a revelation/benefit pattern. Deliver the useful method and avoid false secrecy or novelty.
10The [blank] Risk Hiding In Your [blank]Name the hidden risk and how it can be checked. Distinguish an observed problem from a hypothetical possibility.
11Why you shouldn’t [do what I desire them to do]A contrarian opening should explain when the action is inappropriate and when it is useful; do not use reverse psychology to conceal intent.

Proof patterns

No.Original patternHow to teach and apply it
1Here is a Method That is Helping [world class example] to [blank]Name the method and the real example, with evidence and context. An impressive name alone does not show causation or endorsement.
2[blank] Hacking With [world class example]Explain the specific technique associated with the example. Do not imply collaboration, access or results that are not established.
3Savvy&#124;Smart&#124;Sexy People Do XYZThe source gives Savvy, Smart and Sexy alternatives separated by bars. Identity labels are not proof; focus on relevant behavior and evidence.
4Why I [blank] (And Maybe You Should Too)Use a genuine first-person choice and explain its reasons. “Maybe” should invite evaluation of fit rather than pressure imitation.
5[Do something] like [world-class example]Identify the particular practice worth learning from the example, while explaining differences in resources, context and constraints.
6The [desired result] That [world class example] Is Talking AboutProvide the actual statement and context if claiming a prominent example is discussing the result. Do not invent an endorsement.
7Join [impressive number] of Your Peers that [take desired action]The peer count must be current, verifiable and relevant to the action. Distinguish members, purchasers and successful customers.
8[desired result] Like A [desired group or person]Describe the capability being compared, not an unsupported promise of equivalent status or results. Explain the limits of the analogy.
9How [impressive number] Got [desired result] in [time period]Verify the number, result, period and conditions. A selected success story does not establish what a typical learner will achieve.
10Like [world class example] You Can [desired result]Explain which conditions make the comparison useful. A famous example’s achievement does not prove every reader can replicate it.

Turn a pattern into a complete opening

As an authored exercise, choose one Gains pattern for a proposal-review lesson, one Threats pattern for identifying missing scope, and one Proof pattern only if you have a genuine example. Write the headline, the evidence it relies on and the paragraph that immediately delivers on its promise. A bounded Gains example is “Five Questions Answered About Proposal Scope,” provided the lesson answers exactly five questions. A proportionate Threats example could identify observable signs that scope needs clarification. For Proof, use a verified demonstration and state what it does and does not establish.

Read the resulting headline as someone unfamiliar with your business. Identify implied promises about speed, certainty, effort, money, status, danger and endorsement. Remove or qualify unsupported implications. Test whether readers can accurately predict the content; attention alone does not establish useful engagement or commercial performance.

Review all chosen numbers, quotations, comparisons and timelines before publication. Preserve the source's complete list for study, including the unfinished “Without” line, but publish only a completed, truthful version appropriate to the actual content. No headline in this library supplies permission to fabricate customer evidence or personal history.

Sources and complete original

- Assigned HEADLINE EXAMPLES document. - ClickFunnels hook, story and offer. - Acquisition.com Value Equation.

The full native source is retained in the appendix. The 46 applications above explain each distinct pattern; they do not claim the patterns have been tested for RISER or guarantee rankings, attention or sales.

Assigned source links

D0464 original source 1

Complete returned native document text

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

HEADLINE EXAMPLES

GAINS
Where [desired result] Is And How To Get It
• Discover The [desired result] Secret
• [blank] Your Way To A [desired result] You
• To People That Want To [desired result] But Can’t Get Started
• You, a [desired result]
• Stop [undesired result]
• You Too Can [desired result] in [time period] with [blank]
• How To Become [desired result] When You [something challenging]
• here’s Big [desired result] In [blank]
• You Don’t Have to Be [something challenging] to be [desired result]
• Little Known Ways to [blank]
• How to turn [blank] into [desired result]
• How To Build a [blank] You Can Be Proud Of
• The Lazy [blank’s] Way to [desired result]
• How To Make People Line Up And Beg To [blank]
• How To Get [desired result] Out Of [blank]
• How To [desired result] When You’re Not [blank]
• How To Take The Headache Out Of [blank]
• X Questions Answered About [blank]
• Give Me [short time period] and I’ll Give You [desired result]
• Answered: Your Most Burning Questions About [blank]
• Take X minutes to get started with [blank]... you'll be happy you did!
• Who Else Wants [desired result]?
• How to fast-track your [desirable result]
• How [impressive number] Got [desired result] Without

THREATS
Do You Recognize the [number] Early Warning Signs of [blank]?
• If You Don’t [blank] Now, You’ll Hate Yourself Later
• I've Lied to You for [time period] Now
• The Biggest Lie In [your industry]
• X Shocking Mistakes Killing Your [blank]
• Don’t Try [blank] Without [desired action] First
• [blank] May Be Dangerous To [something precious]
• [blank] May Be Causing You To Lose Out On [desired result]
• At Last, The Secret To [desired result] Is Revealed
• The [blank] Risk Hiding In Your [blank]
• Why you shouldn’t [do what I desire them to do]



PROOF
Here is a Method That is Helping [world class example] to [blank]
• [blank] Hacking With [world class example]
• Savvy|Smart|Sexy People Do XYZ
• Why I [blank] (And Maybe You Should Too)
• [Do something] like [world-class example]
• The [desired result] That [world class example] Is Talking About
• Join [impressive number] of Your Peers that [take desired action]
• [desired result] Like A [desired group or person]
• How [impressive number] Got [desired result] in [time period]
• Like [world class example] You Can [desired result]
Complete local source copy including original filing metadata and formatting

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/1Bwa2FZh79jqWj3oE-GB1VBygsYVgkUdlz4dQ1kqi0QQ/edit?usp=drivesdk"
drive_file_id: "1Bwa2FZh79jqWj3oE-GB1VBygsYVgkUdlz4dQ1kqi0QQ"
created: "2024-05-07T20:53:50.591Z"
modified: "2026-06-04T16:56:22.994Z"
---

# HEADLINE EXAMPLES.docx

HEADLINE EXAMPLES


GAINS
Where [desired result] Is And How To Get It
• Discover The [desired result] Secret
• [blank] Your Way To A [desired result] You
• To People That Want To [desired result] But Can’t Get Started
• You, a [desired result]
• Stop [undesired result]
• You Too Can [desired result] in [time period] with [blank]
• How To Become [desired result] When You [something challenging]
• here’s Big [desired result] In [blank]
• You Don’t Have to Be [something challenging] to be [desired result]
• Little Known Ways to [blank]
• How to turn [blank] into [desired result]
• How To Build a [blank] You Can Be Proud Of
• The Lazy [blank’s] Way to [desired result]
• How To Make People Line Up And Beg To [blank]
• How To Get [desired result] Out Of [blank]
• How To [desired result] When You’re Not [blank]
• How To Take The Headache Out Of [blank]
• X Questions Answered About [blank]
• Give Me [short time period] and I’ll Give You [desired result]
• Answered: Your Most Burning Questions About [blank]
• Take X minutes to get started with [blank]... you'll be happy you did!
• Who Else Wants [desired result]?
• How to fast-track your [desirable result]
• How [impressive number] Got [desired result] Without


THREATS
Do You Recognize the [number] Early Warning Signs of [blank]?
• If You Don’t [blank] Now, You’ll Hate Yourself Later
• I've Lied to You for [time period] Now
• The Biggest Lie In [your industry]
• X Shocking Mistakes Killing Your [blank]
• Don’t Try [blank] Without [desired action] First
• [blank] May Be Dangerous To [something precious]
• [blank] May Be Causing You To Lose Out On [desired result]
• At Last, The Secret To [desired result] Is Revealed
• The [blank] Risk Hiding In Your [blank]
• Why you shouldn’t [do what I desire them to do]






PROOF
Here is a Method That is Helping [world class example] to [blank]
• [blank] Hacking With [world class example]
• Savvy|Smart|Sexy People Do XYZ
• Why I [blank] (And Maybe You Should Too)
• [Do something] like [world-class example]
• The [desired result] That [world class example] Is Talking About
• Join [impressive number] of Your Peers that [take desired action]
• [desired result] Like A [desired group or person]
• How [impressive number] Got [desired result] in [time period]
• Like [world class example] You Can [desired result]

Turn 100 storytelling hooks into evidence-based teaching openings

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Use the story shape, not an invented personal history

The assigned source supplies 100 first-person hooks and an Instagram link. It contains no supporting stories, transaction records or proof that the claims happened. The linked reel was unavailable to the review tool; no video or transcript content is claimed as reviewed. All original hooks remain preserved below and in the native appendix.

These hooks use adversity, surprise, first milestones, rejection, identity, customer learning and changes of direction to invite attention. In ClickFunnels' hook/story/offer sequence, the opening must connect to the actual story and offer. A financial hook also creates expectations about results. Use it only when your evidence supports its meaning, or explicitly frame the story as a hypothetical teaching example instead of making a first-person claim.

For each hook, the authored application explains what the story must teach or substantiate. Dollar amounts, time periods, business counts and work-hour claims are source examples, not RISER history, expected learner results or recommendations. Do not impersonate an experience involving homelessness, debt, a former employer, a customer or a failed business to make content more dramatic.

Hooks 1–10

No.Original hookWhat the story must explain
1"I was homeless before I made my first $10,000 in a month."If this is your actual history, separate housing hardship from the documented income event; do not imply hardship guarantees later wealth.
2"I lost everything, but then I discovered a secret that changed my life."Define what was lost, what changed and the practical lesson. Replace a mysterious secret with a method the audience can understand.
3"What I learned from being $50,000 in debt will shock you."Document the debt amount and explain the decision learned from it. Avoid presenting debt as a necessary path to success.
4"They said I’d never succeed, but I proved them all wrong."Identify the specific criticism, your response and the actual outcome. Do not invent antagonists merely to dramatize the story.
5"I made $1,000 in 24 hours doing this one simple thing."State what the $1,000 represents, the work involved and the actual 24-hour period; disclose prior preparation rather than imply effortless earnings.
6"Here’s how I turned my passion into a 6-figure income."Explain how the interest became a viable offer, and distinguish revenue from income. Passion alone does not establish customer demand.
7"The biggest mistake I made in my 20s—and how it made me rich."Name the mistake, the corrective action and the evidence connecting them. A later financial result may have multiple causes.
8"I went from broke to buying my dream car in 6 months."Separate the starting finances, six-month timeline and car purchase. A luxury purchase does not prove sustainable profit or typical results.
9"One embarrassing moment changed my life forever."Tell the real incident, the insight and the action afterward. Avoid exposing another person’s private experience without appropriate permission.
10"I quit my job with no plan—and it was the best decision I ever made."Explain the context and consequences of an actual career decision. Do not recommend quitting without a plan based on one selected success.

Hooks 11–20

No.Original hookWhat the story must explain
11"My boss laughed when I told him my plan—but now he works for me."Verify the relationship and role change before using the reversal. Focus on what was learned rather than humiliating a former employer.
12"I accidentally stumbled upon this money-making secret."Describe the observation that revealed an opportunity and the work used to test it. Accident alone does not explain commercial success.
13"Here’s how I saved my failing business in just 30 days."Define what “saved” means, the thirty-day actions and the financial evidence. Distinguish stabilization from complete business recovery.
14"My first online sale came while I was asleep."Explain the earlier work and checkout system that enabled the sale. A transaction during sleep is not proof of passive, effort-free income.
15"I worked 18-hour days for years, and it almost ruined my life."Describe the costs of the eighteen-hour schedule and what changed. The lesson should not glorify unsustainable work as a requirement.
16"I started with $50 and built a 7-figure business."Clarify what the $50 funded and what later resources were required. Define the seven-figure measure and its time period.
17"Here’s the truth about my first failed attempt at success."Show the original attempt, what failed and what evidence changed your approach. Avoid rewriting the failure as a guaranteed success step.
18"The one thing I never thought would work—did."Identify why the approach seemed unlikely and what the actual test showed. Explain limits rather than generalize from surprise.
19"I almost gave up before I found this breakthrough."Explain the obstacle, what new information justified continuing and the bounded result. Persistence is not always the right decision.
20"How I turned rejection into my greatest opportunity."Show how a specific rejection informed a different offer or audience. Do not claim every rejection contains a profitable opportunity.

Hooks 21–30

No.Original hookWhat the story must explain
21"I made my first $1,000 by solving my own problem."Connect the personal problem with other customers’ demand and document the first earnings. Solving your problem alone does not prove a market.
22"I created this product to solve a personal pain point."Explain the pain, the prototype and the evidence that the product helped. Distinguish personal usefulness from verified broader fit.
23"The surprising lesson I learned from losing my first client."Describe why the client left, what was actually known and the improvement made. Avoid blaming the client or inventing their motives.
24"I was terrified, but I did it anyway—and it paid off."Name the feared action and actual outcome. Include relevant preparation so the story does not equate fearlessness with sound judgment.
25"I copied a millionaire’s strategy, and here’s what happened."Identify the strategy and what you actually adapted. Wealth of the original practitioner is not proof the approach fits your circumstances.
26"This one hack saved my business from bankruptcy."Describe the intervention and its financial effect with evidence. Do not call one tactic a bankruptcy cure without showing the wider context.
27"I invested $10 into my dream and turned it into $10,000."Explain the initial $10 use, subsequent inputs and whether $10,000 is revenue or profit. Avoid implying that multiplication was automatic.
28"I failed 10 times before I finally succeeded."Document the ten attempts and their differences. Explain what changed rather than treating a fixed failure count as a success formula.
29"This one conversation changed my entire perspective."Reconstruct the actual conversation accurately and explain the decision it changed. Distinguish remembered meaning from a verbatim quotation.
30"I thought it was impossible—until I tried it."Show the prior assumption, the trial and its result. An outcome that surprised you is not proof that all constraints were imaginary.

Hooks 31–40

No.Original hookWhat the story must explain
31"How I turned my side hustle into my full-time income."Define the income-replacement threshold, period and transition costs. Explain how demand and capacity supported the move beyond a side project.
32"My biggest success came after my biggest failure."Trace the specific learning from failure to later action. Sequence alone does not prove the failure caused the success.
33"I started with no experience and built something amazing."Describe which experience was absent and which transferable skills or support existed. Do not erase important prerequisites from the story.
34"Here’s what I wish I knew before I started."Offer a specific lesson and the evidence behind it. Explain how a beginner can apply it in the present context.
35"I made more money in one month than I did in a year at my job."Compare equivalent gross or net measures and time periods. A single strong month does not establish a stable annual income.
36"Here’s why I left my safe, comfortable career."Explain the real reasons, tradeoffs and preparation behind leaving the career. Do not portray security as inherently undesirable.
37"I never thought I’d be here, but here I am."Define the actual milestone reached and the concrete path. Replace vague amazement with useful details the audience can learn from.
38"What I learned from selling door-to-door."Teach a specific observation from door-to-door selling, such as listening or qualification. Do not transfer tactics without considering channel differences.
39"The moment I realized my true calling."Describe the experience that clarified your direction. Personal meaning is a subjective conclusion, not evidence of guaranteed business fit.
40"How I turned a hobby into a thriving business."Explain the customer problem, commercial model and constraints that turned the hobby into a business. Enjoyment and profitability are different.

Hooks 41–50

No.Original hookWhat the story must explain
41"I risked everything—and it paid off."Describe the real exposure and consequences, including what might have gone wrong. Do not make risking everything a recommended strategy.
42"Here’s the unconventional strategy that worked for me."Name the unconventional method, why you tried it and the evidence it worked in context. Novelty alone is not a benefit.
43"I found the opportunity of a lifetime when I wasn’t even looking."Explain how the opportunity was recognized and evaluated after discovery. Avoid implying that preparation and due diligence were unnecessary.
44"How I made $500 selling something I didn’t own."Clarify what was sold and the actual authorization or arrangement. Do not frame unauthorized selling or misrepresentation as a clever tactic.
45"The craziest decision I ever made turned out to be the best."Explain the decision criteria and outcome without treating recklessness as expertise. Compare the choice with reasonable alternatives.
46"The most embarrassing moment of my life led to my success."Trace the embarrassing incident to a specific learning and later action. Respect the privacy of everyone involved.
47"I followed my gut, and it led me to my dream life."Separate intuition from the information and testing that supported the decision. A satisfying outcome does not make intuition universally reliable.
48"What I learned from failing five businesses in a row."Explain the distinct failures and recurring pattern across five businesses. Avoid erasing costs or presenting serial failure as necessary.
49"How I replaced my income in just three months."Define the three-month starting point and income measure, including preparatory work. Do not imply the timeline is typical.
50"I doubted myself, but then something amazing happened."Identify the actual change after self-doubt and the action that made it possible. Keep the causal explanation concrete.

Hooks 51–60

No.Original hookWhat the story must explain
51"I turned my biggest insecurity into my greatest strength."Explain how the insecurity informed a useful capability without claiming it vanished. Do not exploit the audience’s insecurities as pressure.
52"How I turned an idea into a profitable product."Trace idea, demand test, delivery and actual profit calculation. A product launch or revenue figure alone does not prove profitability.
53"The first time I made money online felt unreal."Describe the first transaction, what was delivered and what it taught. Emotional significance is distinct from financial scale.
54"I was scared, but I took the leap—and it changed everything."Name the leap and the preparation behind it. Explain the result without turning fear into evidence that a risk is worthwhile.
55"I made $1,000 selling something I created in my garage."Describe the garage-made product, customer demand and costs. Clarify whether the $1,000 is sales revenue or retained earnings.
56"How I started my business with zero followers."Explain how customers found you without followers, such as referrals or direct relationships. Zero followers does not mean zero distribution.
57"What I learned from working 100 hours a week."Discuss the consequences and limitations of the hundred-hour week. Teach a sustainable process improvement instead of prescribing extreme hours.
58"Here’s why I fired my biggest client."Explain the real fit, scope or economics issue and the transition process. Avoid disclosing private client information or glorifying conflict.
59"I made $10,000 using this one overlooked strategy."Identify the overlooked strategy and substantiate the $10,000 measure. Show the other resources needed rather than attribute everything to one tactic.
60"I turned my worst day into my biggest win."Define the setback, the response and the actual win. Preserve uncertainty and losses instead of forcing a simplistic positive narrative.

Hooks 61–70

No.Original hookWhat the story must explain
61"I discovered this secret by accident—and it changed my life."Explain the accidental discovery and the repeatable lesson. The content should resolve the curiosity rather than withhold the method.
62"What I learned from saying ‘yes’ to every opportunity."Compare opportunities accepted, costs incurred and lessons learned. Do not recommend saying yes indiscriminately without capacity or fit checks.
63"I built a business around something I love."Show how a genuine interest intersects with a paying customer’s need. A business built around enjoyment still needs workable economics.
64"Here’s how I escaped the 9-to-5 grind."Explain the actual work arrangement achieved and its tradeoffs. Business ownership does not automatically reduce hours or financial uncertainty.
65"How I built a thriving business without a degree."Identify the skills, learning and support used without a degree. Do not imply credentials are irrelevant where they are required.
66"The one thing I wish someone had told me earlier."State the useful advice precisely and explain how it would have changed an earlier decision. Avoid vague retrospective certainty.
67"My first product launch was a total failure—until I did this."Define the launch failure, the change and the measured result afterward. Do not imply one fix always rescues a product.
68"How I went from clueless to confident in my industry."Describe the knowledge and practice behind growing confidence. Confidence should be distinguished from demonstrated competence.
69"The weirdest way I ever made money actually worked."Explain the unusual method, its legitimate transaction and why demand existed. Weirdness is a story device, not a business model.
70"How I made $1,000 flipping items from thrift stores."Show purchase costs, resale revenue, fees and time for the thrift-store example. The $1,000 claim needs a clear net or gross basis.

Hooks 71–80

No.Original hookWhat the story must explain
71"I took a big risk—and it paid off in ways I couldn’t imagine."Describe the risk and the unexpected outcome while acknowledging downside possibilities. A fortunate result does not validate every similar bet.
72"I created my dream life with just one small change."Specify the small change and its realistic contribution. A whole-life transformation usually involves other conditions and cannot be assumed.
73"What I learned from my first unhappy customer."Preserve the unhappy customer’s actual feedback and explain the correction. Do not turn criticism into an invented endorsement.
74"How I turned a personal struggle into a profitable business."Explain how a personal struggle informed an offer and how profit was established. Avoid implying suffering is a prerequisite for entrepreneurship.
75"The first time I pitched my idea, they laughed at me."Describe the actual pitch response and what you changed or learned. Do not fabricate ridicule to manufacture an underdog narrative.
76"I made my first $100 online—and it felt like a million."Separate the first $100 transaction from its emotional meaning. The feeling of a milestone does not change the amount earned.
77"How I created a life I love by following my passion."Explain the concrete choices that improved your life and the tradeoffs involved. Personal satisfaction is not a universal outcome promise.
78"Here’s what I learned from making 100 cold calls."Describe the hundred-call sample, what was measured and how the approach changed. Contact count alone does not establish sales effectiveness.
79"The time I almost gave up—and why I’m glad I didn’t."Explain why continuing was justified by new evidence or a feasible plan. Include the possibility that stopping can sometimes be appropriate.
80"I hit rock bottom, but it was the start of something great."Treat hardship accurately and sensitively; explain the next action without suggesting that crisis inevitably produces business success.

Hooks 81–90

No.Original hookWhat the story must explain
81"The weirdest product I ever sold made me thousands."Describe the unusual product, actual buyers and the meaning of “thousands.” Separate revenue from costs and novelty from real usefulness.
82"I thought I’d failed—but it was actually a blessing."Explain why the event first looked like failure and what later changed your interpretation. Keep the lesson personal rather than universal.
83"How I turned an old skill into a new opportunity."Show how an existing skill addressed a newly observed need. Explain any adaptation needed rather than assume old expertise transfers unchanged.
84"The surprising way I discovered my niche."Trace the observation or customer evidence that clarified the niche. A surprising insight still needs validation with actual demand.
85"How I learned to sell without feeling ‘salesy.’"Explain how listening, clarity and fit changed your sales behavior. Avoid implying that every persuasive technique is inherently manipulative.
86"The moment I realized I could succeed was life-changing."Identify the evidence that increased confidence and what it did not prove. A pivotal realization is not a guarantee of future success.
87"What I wish I had done differently when I started."Specify the earlier decision, the alternative and the evidence supporting the lesson. Avoid hindsight that ignores what was knowable then.
88"Here’s how I found my first 10 customers."Account for each of the first ten customers and acquisition channels. Distinguish paying customers from leads or expressions of interest.
89"How I made my first sale without any marketing experience."Explain which skills and support enabled the first sale despite limited marketing experience. Do not portray experience as useless.
90"I was terrified to start, but I did it anyway."Describe the actual first step and its manageable scope. Starting despite fear does not require ignoring genuine risks.

Hooks 91–100

No.Original hookWhat the story must explain
91"How I turned a free tool into a money-making machine."Name the free tool, the value created and the business process around it. Free software does not remove labor or guarantee earnings.
92"The one thing I did differently that made all the difference."Isolate the change and consider other influences on the result. “All the difference” should not overstate causal certainty.
93"I followed this one simple strategy—and it worked."Describe the strategy in enough detail to apply and assess it. Explain the conditions under which it worked and its limitations.
94"Here’s how I built my business with zero budget."Clarify that zero budget means no specified cash spend, if true. Existing equipment, time, skills and relationships still have value.
95"How I made my first sale while working a full-time job."Explain scheduling, fulfillment and acquisition around the existing job. Do not imply a sale establishes a viable replacement income.
96"What I learned from launching 10 products in a year."Review the ten launches, including weak results, costs and learning. Volume of launches is not a substitute for product usefulness.
97"How I found the courage to start my own business."Describe the preparation and small actions that supported courage. Motivation should connect to practical readiness and evidence.
98"I used this one strategy to stand out in a crowded market."Explain the distinctive customer benefit and how it was tested. Standing out is useful only when the difference matters to customers.
99"Here’s how I turned a $10 idea into a $10,000 business."Separate the $10 concept cost from all later investment and define the $10,000 measure. Avoid implying a guaranteed return multiple.
100"The moment I realized I could change my life was unforgettable."Describe the realization and the subsequent action. A memorable feeling can introduce the story, but the lesson must deliver concrete learning.

Build the story behind the opening

Choose a hook that fits a genuine event or a clearly labeled hypothetical scenario. As authored practice, write five elements: the starting situation; the specific problem or observation; the action taken; the evidence of what happened; and the lesson with its limitations. Then explain the actual relevant next step. Do not hide essential conditions in an appendix after an exaggerated opening.

For example, a real first sale can introduce a lesson about testing an offer. The teaching should show what was sold, how the buyer found it, what was delivered and what the sale did and did not validate. It should not imply that one transaction proves recurring demand. A customer-complaint story can introduce an improved onboarding process, provided the feedback is accurately represented and private details are handled appropriately.

Review the implied promise in the opening against the full story. If the hook says “in 24 hours,” explain any earlier preparation. If it says “zero budget,” disclose relevant resources. If it says “income,” do not support it only with gross revenue. If it attributes success to one change, consider competing explanations. Use the Acquisition.com Value Equation resource to examine outcome, confidence, time and effort without implying a guaranteed result.

After drafting, ask a reader what they expect the story to prove. Revise any implication you cannot support. Test attention alongside useful understanding and qualified action. A dramatic hook that attracts the wrong audience or promises more than the content delivers is not a completed marketing asset.

Sources and complete original

- Assigned 100 storytelling hooks document. - Original Instagram reel — content unavailable during review. - ClickFunnels hook, story and offer. - Acquisition.com Value Equation.

All 100 openings have an individual application above. Their complete original text is preserved; the supporting stories must come from authentic evidence or be clearly labeled as authored examples.

Assigned source links

D0465 original source 1

Original tables and embedded resource links

Original embedded hyperlink spans:

Complete returned native document text

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."
Complete local source copy including original filing metadata and formatting

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."

Add customer value through delivery, support and a credible offer

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Understand the four overlapping lists

The assigned document contains four separate lists of ten value-building ideas, fifteen numbered citations and two email signatures. The lists overlap, but each adds details. This lesson teaches all four inventories so that useful distinctions are not lost in a shorter summary. They are proposed tactics, not established RISER policies, customer results or services already available.

The central question is what improves the customer's actual experience. In Brunson's value-ladder and offer-presentation approach, make the next relevant benefit understandable. In Hormozi's value framework, consider the desired result, perceived likelihood, time delay and required effort. See the Acquisition.com Value Equation and ClickFunnels hook/story/offer explanation. Neither framework means price becomes literally irrelevant or every added feature creates value.

First list: ten practical improvements

Source tacticDetails to preserve and apply
Faster and more reliable deliveryThe source suggests expedited shipping, same-day or next-day local delivery, guaranteed timelines and real-time tracking. Tempe/Phoenix is its location example, not a confirmed service area. Define the actual window, eligibility and exception process; tracking supports transparency but does not itself ensure timely delivery.
Help customers save moneyConsider volume discounts, bundles, loyalty rewards, price matching, free-shipping thresholds and durability that reduces replacements. State genuine comparison prices and total costs. A discount or shipping threshold can reduce margin; measure net benefit instead of assuming a larger order is automatically better.
Improve quality or durabilityMaterials, features, warranties, extended guarantees and an antimicrobial-coating example appear in the source. Establish actual performance evidence and relevant terms before claiming a protective property. A warranty is a commitment, not proof that a product never fails.
Personalization and customizationColors, engraving, configurations and need-based recommendations may improve fit. Specify the choices, lead time, price and limits. Emotional attachment is a possible response, not a guaranteed result of customization.
Customer service and supportLive chat, proactive follow-up, easy returns, priority phone support, quick-response teams, tutorials and setup help address different needs. Choose the service level you can fulfill. Document whether a channel provides information, problem resolution or implementation.
Education and expertiseGuides, videos, how-to resources, best-practice tips and newsletters help customers use the purchase. A resource creates value when it answers a real question and is usable, not merely because it increases the asset count.
Loyalty incentivesPoints, exclusive discounts, early access, add-ons, thank-you gifts and referral bonuses are alternative reward mechanisms. Explain who qualifies, what is earned and any expiration or cost. Rewards should not replace delivery of the core promise.
Easier purchasingOne-click checkout, installments, buy-now-pay-later and subscriptions can reduce some friction. Make total cost, recurring terms and cancellation understandable. A faster checkout is not a reason to obscure the customer's commitment.
Complementary bundlesAccessories, maintenance kits, installation and related services can make a product more useful. List the contents and actual discount basis. Do not remove an essential part of the original promise merely to sell it as an extra.
Emotional and brand valueStory, distinctive benefits, packaging, authentic reviews, testimonials, exclusivity and community can influence perceived fit. Present genuine evidence and a truthful identity. Attractive packaging cannot compensate for an undelivered promise.

The source suggests starting with two or three easy improvements, such as delivery or bundles, then refining from customer feedback. Treat that as a manageable starting heuristic, not a validated rule about the optimal number of changes. A few well-supported changes are easier to assess than an unmeasured collection of promises.

Second list: ten ways to extend the offer

Source tacticDetails to preserve and apply
Velocity or speedExamples include replacing a week with a 24-hour result, overnight shipping, instant digital access and one-hour service windows. Distinguish access speed from time to achieve the customer's outcome. Explain what operational change makes the promised speed possible.
Radical risk reversalThe source contrasts a standard 30-day guarantee with a 110% money-back outcome guarantee and compensation for lost time. These are examples, not recommended default terms. Define the trigger, scope, exclusions, evidence and financial exposure before adopting any commitment; no guarantee is created here.
Done-for-you workMoving from a tool to implementation may reduce effort, but it also changes scope, access needs and capacity. The claim that people always pay more for convenience than information is unsupported. Test whether this audience values that service and at what sustainable price.
Direct financial returnThe $1,000 saved and $5,000 earned figures are examples. Show the calculation, period, assumptions and attributable costs. A customer's possible return is not guaranteed merely because it exceeds the selling price.
Bonus value stackSolve the next relevant problem with a complementary asset. The camera example pairs a quick-start guide or lens-cleaning kit with the core product. Explain the practical benefit instead of assigning an inflated dollar value.
Exclusive access or communityA private network, Slack channel or mastermind can provide useful connections. Define participation and actual support. Access to a group does not guarantee particular relationships, advice or business results.
Implementation supportOnboarding calls, office hours and an account manager can help customers use what they bought. Define the help available and measure whether it removes a real obstacle. The source's assertion that most buyers never use purchases is not established here.
Tailored solutionsPersonalized reports, custom-fit hardware, niche-specific templates and adaptations to an industry or workflow can improve relevance. Identify which inputs are needed and which parts remain standard. Tailoring alone does not prove luxury value or willingness to pay.
Status and identityEco-friendly, high-tech or luxury positioning may matter to some customers. Support objective claims and avoid using status anxiety to conceal weak functionality. Let buyers evaluate whether the identity aligns with their priorities.
Continuity and future supportLifetime updates, grandfathered prices and ongoing maintenance are different commitments. Define duration, eligible versions, service limits and actual funding. Continuing value should help customers, not make them feel trapped in a relationship.

The source's hidden-cost prompt asks you to consider time, frustration and mental energy before the customer gets a result. Use interviews, observation or support evidence to identify those costs. Do not invent a monetary value for frustration merely to make an offer appear cheaper.

Third list: ten implementation-oriented combinations

Source tacticDetails to preserve and apply
Speed and convenienceThe examples combine 24–48-hour starts with done-for-you setup, templates and checklists. Specify what begins within that window and what later work is required. A checklist can simplify a task only when its instructions are complete.
Risk removalExamples include 14-day or 30-day money-back terms, cancellation during a trial, and a performance promise that supplies extra support or a one-to-one call if a defined result is not achieved. These are distinct policies and should not be blended into an ambiguous guarantee.
Focused bonusesThe source proposes two or three swipe files, scripts, audits or mini-courses, plus time-limited founder calls, SOP packs or private Q&A. Tie each to a real obstacle and honor any genuine deadline; more bonuses do not necessarily mean a better offer.
Personalized helpA short one-to-one call, Loom review, audit or implementation roadmap can address agency size, niche or revenue context. Define what the review covers and how recommendations are checked. Do not assume a short call resolves every customer problem.
Ongoing support and communityPrivate groups, weekly office hours, Q&A and searchable updated SOP libraries serve different purposes. Keep the library current and make the actual schedule and response boundaries visible.
Financial usefulnessExplain whether the offer can increase revenue, reduce cost or reduce a particular risk. ROI calculators, pricing sheets and deal templates need transparent assumptions; providing a calculator does not validate its inputs or guarantee the result.
Clarity and simplicityA guided start-here sequence and a clear main offer with one upgrade may reduce confusion. Test comprehension instead of treating fewer choices as universally optimal. A simple presentation must still include essential scope and terms.
Access and flexibilityPay-in-full, installments, BNPL, lifetime access, recordings and replays address different constraints. State the actual total cost and access duration. Flexibility should not conceal future payments or unsupported lifetime commitments.
Proof and confidenceRelevant testimonials, case studies, before/after examples, behind-the-scenes demonstrations and sample modules can help evaluation. Keep examples authentic and representative, identify limitations and distinguish a sample from proof of typical results.
Positioning and exclusivityNiche relevance, limited seats, cohorts and founder perks can clarify who the offer fits. Seat limits and exclusivity require a real basis. Belonging should not be manufactured through false claims about membership or demand.

The numbered citation markers in this third list are preserved in the original appendix. They do not establish that every linked page supports every specific claim. The resource review below separates relevant marketing material from unrelated or unavailable citations.

Fourth list: ten concise service promises

Source tacticDetails to preserve and apply
Faster deliverySame-day, next-day and guaranteed windows must reflect actual capacity. Compare reliability as well as speed; do not claim competitors routinely fail without evidence.
Save moneyBundle deals, loyalty discounts, bulk pricing and ROI explanations each require a clear baseline. Measure savings after added costs rather than using an attractive discount percentage alone.
Better guaranteeWarranties, hassle-free returns and money-back terms reduce different uncertainties. Explain the actual process and obligations; a stronger-sounding promise can create unsustainable exposure.
Done-for-you setupInstallation, onboarding and implementation transfer particular tasks to the seller. Define the exact responsibility boundary and customer inputs before promising a hands-off experience.
Ongoing human supportThe source suggests 24/7 access, dedicated representatives and a real person on the phone. These require staffing and service definitions. A human channel is not automatically superior for every need; measure resolution and customer preference.
CustomizationTailor the offer to specific needs when the added value justifies the complexity. State what can change and what cannot. A premium price needs evidence of willingness to pay.
Education and expertiseTutorials, guides, consultations and training should help the buyer accomplish the intended task. Check use and understanding rather than assume content distribution creates loyalty.
Exclusive accessEarly releases, member perks and useful information require a real entitlement and delivery process. Avoid implying secret advantages that the business cannot substantiate.
Save timeAutomating a task, eliminating a step or consolidating vendors can reduce work. Check setup, maintenance and exception-handling time as well as the recurring saving. Consolidation can also create dependency and should fit the customer's needs.
Peace of mindCertifications, social proof, transparent pricing and proactive communication address different concerns. Verify certifications and testimonial context; reassurance is not a substitute for actual delivery quality.

The closing combination is fast delivery plus a sound guarantee and real support. Treat it as a candidate design, not proof that competitors cannot match it. The embedded invitations to tailor an offer are retained source text; no campaign, support promise or automation is activated by reading this lesson.

Choose, cost and test an improvement

As authored practice, identify one documented customer obstacle, choose a relevant tactic and explain how it should help. Define the new work, cost, owner and evidence of success. Compare the customer's benefit with fulfillment capacity and contribution margin. Measure both intended outcomes and unintended consequences, such as extra support demand or increased refunds.

Present the offer clearly: what is included, why it matters, what is optional, what the customer must do and which conditions apply. When comparing values, distinguish actual separate selling prices from hypothetical estimates. Do not add unrelated extras simply to inflate the apparent stack. Keep unsuccessful tests in the record so the next decision reflects evidence rather than only favorable stories.

Complete citation inventory and access notes

The source contains the following fifteen links. They remain clickable for traceability. An accessible title is not a full review, and unrelated links are not endorsements of the marketing claims.

  1. Fenix Commerce delivery-promise article URL — returned generic site navigation, not the cited article body.
  2. US Data: Value Driven Offers — accessible marketing discussion of outcomes, nonfinancial costs, transparency and clarity; its general claims are not performance evidence for RISER.
  3. BrandShop: bonuses and guarantees — relevant marketing article, partially reviewed; no claim that its conversion language establishes expected results.
  4. Reddit discussion of providing prospect value — accessible discussion, not a validated research study; full thread review is not established.
  5. Forbes: creating high-value offers — content unavailable during review.
  6. Mountain America: home-purchase offers — home-buying context, not direct support for a course value stack.
  7. NAR: improving the odds of a property offer — redirects to the current NAR news path; property-selling guidance, not proof of the cited marketing tactics.
  8. SalesRemastered value-stack video — unavailable; no audio, video or transcript reviewed.
  9. Home-smell hacks video — unavailable and apparently unrelated by its source title.
  10. Chicotsky: competitive home offers — property-purchase context with dated market examples; not direct support for the value-stack claims.
  11. Value-stacking marketing video — unavailable; no transcript reviewed.
  12. Preston Rutherford: marketing-team incentives — discusses employee incentives, a different use of “bonus” from customer offer extras.
  13. Forbes: home fragrances — accessible via redirect; unrelated home-scent advice rather than evidence for a marketing value stack.
  14. Make your offer stand out video — unavailable; its content and relevance are unverified.
  15. Nick Gulic: introduction to value stacking — relevant commentary that cautions against inflated values, itemized commodity comparisons and haggling, and emphasizes useful outcomes and credible prices.

The unavailable video references remain explicit media-review gaps for final Unused reconciliation. The two Yahoo Mail signature links are original email metadata, not lesson recommendations; they remain with the preserved source rather than being presented as value-building resources.

Read the assigned complete value-building document. Its complete native text, citation list and embedded signature links are retained alongside this teaching. The four inventories are design options to evaluate, not a claim that all forty should be implemented.

Assigned source links

D0466 original source 1

Original tables and embedded resource links

Original embedded hyperlink spans:

Complete returned native document text

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

Here are the **top 10 practical ways** to add value to what you sell. These build on your examples of **faster delivery** and **saving customers money**, while including other high-impact strategies that boost perceived worth, loyalty, and willingness to pay more (or buy more often).

1. **Faster and More Reliable Delivery**  
   Offer expedited shipping options, same-day or next-day delivery in your area (like Tempe/Phoenix), or guaranteed timelines. Customers love time savings—pair it with real-time tracking for transparency. This directly reduces their hassle and waiting.

2. **Help Customers Save Money**  
   Provide volume discounts, bundle deals, loyalty rewards, or price-match guarantees. Show clear savings (e.g., "This bundle saves you $X compared to buying separately" or "Free shipping on orders over $Y"). Highlight long-term cost reductions, like durable products that need fewer replacements.

3. **Enhance Product Quality or Durability**  
   Improve materials, add features, or include built-in protections (e.g., warranties, extended guarantees, or antimicrobial coatings if relevant). Customers perceive higher quality as better long-term value, even if the base price is similar.

4. **Personalization and Customization**  
   Let buyers tailor the product (colors, engraving, configurations) or offer personalized recommendations based on their needs. This makes the purchase feel unique and thoughtful, increasing emotional attachment and satisfaction.

5. **Superior Customer Service and Support**  
   Add live chat, proactive follow-ups, easy returns, or dedicated support (e.g., priority phone lines or quick-response teams). Go beyond basics with tutorials, setup help, or ongoing advice—this builds trust and reduces buyer risk.

6. **Educational Content and Expertise**  
   Include free guides, video tutorials, how-to resources, or best-practice tips related to your product. Share insights via email newsletters or your site. This positions you as a helpful expert, making your offering more valuable than a "just the product" competitor.

7. **Loyalty Programs and Incentives**  
   Reward repeat buyers with points, exclusive discounts, early access to new items, or free add-ons. Simple perks like a thank-you gift or referral bonuses encourage bigger/more frequent purchases.

8. **Convenience and Ease of Purchase**  
   Streamline the buying process with one-click checkout, flexible payments (installments, buy-now-pay-later), or subscription options for consumables. Reduce friction at every step so customers feel they're getting a seamless, hassle-free experience.

9. **Bundling Complementary Items or Services**  
   Package your main product with useful extras (accessories, maintenance kits, installation, or related services) at a perceived discount. This increases the overall utility and makes the deal feel like more bang for the buck.

10. **Build Emotional and Brand Value**  
    Tell your story, emphasize unique benefits, use high-quality packaging, or highlight social proof (reviews, testimonials). Create a sense of exclusivity or community. Customers often pay more for brands that make them feel good or aligned with their values.

These strategies work across products and services—focus on what your specific customers care about most (ask for feedback to refine them). Start with 2-3 that are easiest to implement, like faster shipping or bundles, then layer on others. The goal is to shift from competing on price alone to competing on total value, which can justify higher margins and stronger loyalty.

Increasing value isn't always about lowering the price; in fact, it’s often about making the price irrelevant by solving a bigger problem or moving faster.
Here are the top 10 ways to stack value onto what you sell:
1. The "Velocity" Factor (Speed)
In a world of instant gratification, speed is a premium. If you can deliver a result in 24 hours that usually takes a week, you haven't just added value; you've created a different product.
 * Example: Overnight shipping, "Instant access" digital portals, or 1-hour service windows.
2. Radical Risk Reversal
Take the "what if it fails?" anxiety off the buyer and put it on yourself. A standard 30-day guarantee is common; a "110% money-back if you don’t see X result" is a value powerhouse.
 * Example: Guarantees that cover not just the cost, but the user's lost time.
3. The "Done-For-You" (DFY) Component
Moving a customer from "here is a tool" to "I will do this for you" is the highest leap in value. People will always pay more for convenience and saved effort than they will for information.
4. Direct Financial ROI
If your product saves someone $1,000 or helps them make $5,000, your price becomes an investment rather than an expense. Quantify the savings or the earnings clearly.
5. Bonus Bundling (The "Value Stack")
Add complementary products or services that solve the next problem the customer will have after using your main product.
 * Example: If you sell a camera, include a "Quick Start Guide" or a free lens cleaning kit.
6. Exclusive Access or Community
Value often lies in who else is in the room. Providing access to a private network, a Slack channel, or a mastermind group adds a social and professional layer that a standalone product lacks.
7. Implementation Support
Most people buy things and never use them. By offering onboarding calls, "Office Hours," or a dedicated account manager, you ensure they actually get the value they paid for.
8. Customization & Personalization
A "one-size-fits-all" solution is a commodity. A solution tailored to their specific industry, name, or workflow feels like a luxury.
 * Example: Personalized reports, custom-fit hardware, or niche-specific software templates.
9. Status and Identity
Value can be psychological. If owning your product makes the buyer feel like part of an elite group or aligns with their personal brand (e.g., eco-friendly, high-tech, luxury), they will value it more.
10. Continuity and Future-Proofing
Ensure the value doesn't end the moment the transaction does. Offer lifetime updates, "Grandfathered" pricing, or ongoing maintenance to keep the customer locked into a high-value loop.
> Pro Tip: The most effective way to add value is to address the "hidden costs"—the time, frustration, and mental energy your customer spends before they get the result they want.
> 
Give me the top 10 ways to ad value to what I sell...like, faster delivery, save more money...

Here are 10 “plug-and-play” ways to add **value** to anything you sell, without just lowering the price.

## 1. Speed and convenience

- Faster delivery or “priority processing” (e.g., 24–48 hour start instead of a week). [1]
- Done-for-you setup, templates, or checklists so they get results faster with less effort. [2]

## 2. Risk removal (guarantees)

- Clear money-back guarantee (30 days, 14 days, or “try it for X days, cancel anytime”). [3]
- Performance-based promise: “If you don’t get X result, we’ll Y” (extra support, 1:1 call, etc.). [3]

## 3. Smart bonuses and “and more”

- Add 2–3 focused bonuses that solve side problems (swipe files, scripts, audits, mini-courses). [3]
- Time-limited bonuses for fast action (e.g., “Founders” call, extra SOP pack, private Q&A). [3]

## 4. Personalized help

- Short 1:1 call, Loom review, or personalized audit for buyers. [2]
- Implementation roadmap tailored to their situation (agency size, niche, revenue band). [2]

## 5. Ongoing support and community

- Private community, weekly office hours, or Q&A calls so they’re not “on their own.” [3]
- Access to a searchable SOP or resource library that updates over time. [2]

## 6. Save or make more money

- Show exactly how your thing helps them make money, save money, or reduce risk (spelled out in bullets). [4]
- Include ROI calculators, plug-and-play pricing sheets, or deal-structure templates. [4]

## 7. Clarity and simplicity

- Simple, guided path: “Start here → do this → next step” instead of a pile of stuff. [2]
- Fewer choices at checkout (one main offer, one clear upgrade) so saying yes feels easy. [2]

## 8. Better access and flexibility

- Multiple payment options (pay in full, installments, BNPL) without discounting the core price. [3]
- Lifetime access, recordings, or replays so they don’t fear “falling behind.” [3]

## 9. Proof and confidence

- Strong testimonials, case studies, or “before/after” examples that match their situation. [5]
- Behind-the-scenes walkthroughs or sample modules so they can “try before they fully buy.” [5]

## 10. Positioning and exclusivity

- “For people like you” positioning: niche the offer so it feels built just for them. [2]
- Limited seats, cohorts, or founder perks that feel like joining a tribe, not buying a random product. [3]

If you tell me what specific offer you’re selling right now (course, membership, service, etc.), I can turn these into a concrete “value stack” for that one offer.

Citations:
[1] E-commerce Delivery Promises: Mastering Strategies to Boost Sales https://fenixcommerce.com/BlogPost?slug=delivery-promise-as-a-marketing-tool
[2] Value Driven Offers, Done Right, Help People Say Yes https://www.usdatacorporation.com/blog/value-driven-offers-done-right-help-people-say-yes/
[3] Adding Bonuses and Guarantees That Skyrocket Conversions https://hellobrandshop.com/the-and-more-advantage-adding-bonuses-and-guarantees-that-skyrocket-conversions/
[4] Everyone talks about "providing value" to prospects during the sales ... https://www.reddit.com/r/sales/comments/11mu88b/everyone_talks_about_providing_value_to_prospects/
[5] Four Simple Steps To Creating High-Value Offers That Sell - Forbes https://www.forbes.com/councils/forbesbusinesscouncil/2021/01/21/four-simple-steps-to-creating-high-value-offers-that-sell/
[6] 10 Creative Ways to Make Your Home Purchase Offer Stand Out https://www.macu.com/must-reads/mortgage/make-your-home-purchase-offer-stand-out-fined
[7] How to Improve the Odds of an Offer https://www.nar.realtor/magazine/tools/client-education/handouts-for-sellers/how-to-improve-the-odds-of-an-offer
[8] Some Examples of A Value Stack | @SalesRemastered - YouTube https://www.youtube.com/watch?v=ZrREPEKaAG8
[9] 10 Life-Changing Home Hacks That Will Make It Smell Amazing! https://www.youtube.com/watch?v=KsRQuWBmVSA
[10] 11 Ways to Make Your Offer More Competitive https://www.chicotsky.com/news/119-11-ways-to-make-your-offer-more-competitive
[11] How to Make Irresistible Offers with Value Stacking (Marketing Hack ... https://www.youtube.com/watch?v=dxZnX6LcYMk
[12] How to design a bonus structure for your marketing team - LinkedIn https://www.linkedin.com/posts/prestonr_lesson-learned-the-bonus-structure-we-chose-activity-7369154853954052096-elT0
[13] Experts Reveal How To Make Your Home Smell Amazing All The Time https://www.forbes.com/sites/amandalauren/2022/10/14/experts-reveal-how-to-make-your-home-smell-amazing-all-the-time/
[14] How to Make Your Offer Stand Out Fast! - YouTube https://www.youtube.com/watch?v=OpPsZNOisvk
[15] Intro to Value Stacking | Nick Gulic https://nickgulic.com/intro-to-value-stacking/


Yahoo Mail: Search, Organize, Conquer
Reply
Forward
Here are the top 10 ways to add value to what you sell:

1. **Faster delivery** — Speed wins. Same-day, next-day, or guaranteed delivery windows beat competitors who leave customers waiting.

2. **Save them money** — Bundle deals, loyalty discounts, bulk pricing, or showing the ROI of your product makes the decision easy.

3. **Better guarantee** — A stronger warranty, hassle-free returns, or a money-back promise removes the risk of buying and builds trust.

4. **Done-for-you setup** — Offer installation, onboarding, or implementation so customers don't have to figure it out themselves.

5. **Ongoing support** — 24/7 access, a dedicated rep, or a real human on the phone is a huge differentiator when competitors only offer chatbots.

6. **Customization** — Let customers tailor the product or service to their specific needs. People pay a premium for "built for me."

7. **Education & expertise** — Tutorials, guides, consultations, or training that help customers get more out of what they bought keeps them loyal.

8. **Exclusive access** — Early releases, members-only perks, or insider information makes customers feel like VIPs rather than just transactions.

9. **Save them time** — Automate something, eliminate a step in their process, or consolidate multiple vendors into one. Time is often worth more than money.

10. **Peace of mind** — Certifications, social proof, transparent pricing, and proactive communication reassure customers they made the right call — reducing buyer's remorse and increasing referrals.

The biggest wins usually come from combining a few of these. For example, **fast delivery + great guarantee + real support** is hard to compete with. Want me to tailor these to your specific product or industry?


Yahoo Mail: Search, Organize, Conquer
Reply
Complete local source copy including original filing metadata and formatting

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/1JNQ1RiGnld5lTRwpStk-zAOcMmP4hqYSc2NmguQduG4/edit?usp=drivesdk"
drive_file_id: "1JNQ1RiGnld5lTRwpStk-zAOcMmP4hqYSc2NmguQduG4"
created: "2026-03-28T23:28:51.440Z"
modified: "2026-06-04T02:07:27.645Z"
---

# Here are the **top 10 practical ways** to add value to what you sell

Here are the **top 10 practical ways** to add value to what you sell. These build on your examples of **faster delivery** and **saving customers money**, while including other high-impact strategies that boost perceived worth, loyalty, and willingness to pay more (or buy more often).


1. **Faster and More Reliable Delivery**  
   Offer expedited shipping options, same-day or next-day delivery in your area (like Tempe/Phoenix), or guaranteed timelines. Customers love time savings—pair it with real-time tracking for transparency. This directly reduces their hassle and waiting.


2. **Help Customers Save Money**  
   Provide volume discounts, bundle deals, loyalty rewards, or price-match guarantees. Show clear savings (e.g., "This bundle saves you $X compared to buying separately" or "Free shipping on orders over $Y"). Highlight long-term cost reductions, like durable products that need fewer replacements.


3. **Enhance Product Quality or Durability**  
   Improve materials, add features, or include built-in protections (e.g., warranties, extended guarantees, or antimicrobial coatings if relevant). Customers perceive higher quality as better long-term value, even if the base price is similar.


4. **Personalization and Customization**  
   Let buyers tailor the product (colors, engraving, configurations) or offer personalized recommendations based on their needs. This makes the purchase feel unique and thoughtful, increasing emotional attachment and satisfaction.


5. **Superior Customer Service and Support**  
   Add live chat, proactive follow-ups, easy returns, or dedicated support (e.g., priority phone lines or quick-response teams). Go beyond basics with tutorials, setup help, or ongoing advice—this builds trust and reduces buyer risk.


6. **Educational Content and Expertise**  
   Include free guides, video tutorials, how-to resources, or best-practice tips related to your product. Share insights via email newsletters or your site. This positions you as a helpful expert, making your offering more valuable than a "just the product" competitor.


7. **Loyalty Programs and Incentives**  
   Reward repeat buyers with points, exclusive discounts, early access to new items, or free add-ons. Simple perks like a thank-you gift or referral bonuses encourage bigger/more frequent purchases.


8. **Convenience and Ease of Purchase**  
   Streamline the buying process with one-click checkout, flexible payments (installments, buy-now-pay-later), or subscription options for consumables. Reduce friction at every step so customers feel they're getting a seamless, hassle-free experience.


9. **Bundling Complementary Items or Services**  
   Package your main product with useful extras (accessories, maintenance kits, installation, or related services) at a perceived discount. This increases the overall utility and makes the deal feel like more bang for the buck.


10. **Build Emotional and Brand Value**  
    Tell your story, emphasize unique benefits, use high-quality packaging, or highlight social proof (reviews, testimonials). Create a sense of exclusivity or community. Customers often pay more for brands that make them feel good or aligned with their values.


These strategies work across products and services—focus on what your specific customers care about most (ask for feedback to refine them). Start with 2-3 that are easiest to implement, like faster shipping or bundles, then layer on others. The goal is to shift from competing on price alone to competing on total value, which can justify higher margins and stronger loyalty.


Increasing value isn't always about lowering the price; in fact, it’s often about making the price irrelevant by solving a bigger problem or moving faster.
Here are the top 10 ways to stack value onto what you sell:
1. The "Velocity" Factor (Speed)
In a world of instant gratification, speed is a premium. If you can deliver a result in 24 hours that usually takes a week, you haven't just added value; you've created a different product.
 * Example: Overnight shipping, "Instant access" digital portals, or 1-hour service windows.
2. Radical Risk Reversal
Take the "what if it fails?" anxiety off the buyer and put it on yourself. A standard 30-day guarantee is common; a "110% money-back if you don’t see X result" is a value powerhouse.
 * Example: Guarantees that cover not just the cost, but the user's lost time.
3. The "Done-For-You" (DFY) Component
Moving a customer from "here is a tool" to "I will do this for you" is the highest leap in value. People will always pay more for convenience and saved effort than they will for information.
4. Direct Financial ROI
If your product saves someone $1,000 or helps them make $5,000, your price becomes an investment rather than an expense. Quantify the savings or the earnings clearly.
5. Bonus Bundling (The "Value Stack")
Add complementary products or services that solve the next problem the customer will have after using your main product.
 * Example: If you sell a camera, include a "Quick Start Guide" or a free lens cleaning kit.
6. Exclusive Access or Community
Value often lies in who else is in the room. Providing access to a private network, a Slack channel, or a mastermind group adds a social and professional layer that a standalone product lacks.
7. Implementation Support
Most people buy things and never use them. By offering onboarding calls, "Office Hours," or a dedicated account manager, you ensure they actually get the value they paid for.
8. Customization & Personalization
A "one-size-fits-all" solution is a commodity. A solution tailored to their specific industry, name, or workflow feels like a luxury.
 * Example: Personalized reports, custom-fit hardware, or niche-specific software templates.
9. Status and Identity
Value can be psychological. If owning your product makes the buyer feel like part of an elite group or aligns with their personal brand (e.g., eco-friendly, high-tech, luxury), they will value it more.
10. Continuity and Future-Proofing
Ensure the value doesn't end the moment the transaction does. Offer lifetime updates, "Grandfathered" pricing, or ongoing maintenance to keep the customer locked into a high-value loop.
> Pro Tip: The most effective way to add value is to address the "hidden costs"—the time, frustration, and mental energy your customer spends before they get the result they want.
> 
Give me the top 10 ways to ad value to what I sell...like, faster delivery, save more money...


Here are 10 “plug-and-play” ways to add **value** to anything you sell, without just lowering the price.


## 1. Speed and convenience


- Faster delivery or “priority processing” (e.g., 24–48 hour start instead of a week). [1]
- Done-for-you setup, templates, or checklists so they get results faster with less effort. [2]


## 2. Risk removal (guarantees)


- Clear money-back guarantee (30 days, 14 days, or “try it for X days, cancel anytime”). [3]
- Performance-based promise: “If you don’t get X result, we’ll Y” (extra support, 1:1 call, etc.). [3]


## 3. Smart bonuses and “and more”


- Add 2–3 focused bonuses that solve side problems (swipe files, scripts, audits, mini-courses). [3]
- Time-limited bonuses for fast action (e.g., “Founders” call, extra SOP pack, private Q&A). [3]


## 4. Personalized help


- Short 1:1 call, Loom review, or personalized audit for buyers. [2]
- Implementation roadmap tailored to their situation (agency size, niche, revenue band). [2]


## 5. Ongoing support and community


- Private community, weekly office hours, or Q&A calls so they’re not “on their own.” [3]
- Access to a searchable SOP or resource library that updates over time. [2]


## 6. Save or make more money


- Show exactly how your thing helps them make money, save money, or reduce risk (spelled out in bullets). [4]
- Include ROI calculators, plug-and-play pricing sheets, or deal-structure templates. [4]


## 7. Clarity and simplicity


- Simple, guided path: “Start here → do this → next step” instead of a pile of stuff. [2]
- Fewer choices at checkout (one main offer, one clear upgrade) so saying yes feels easy. [2]


## 8. Better access and flexibility


- Multiple payment options (pay in full, installments, BNPL) without discounting the core price. [3]
- Lifetime access, recordings, or replays so they don’t fear “falling behind.” [3]


## 9. Proof and confidence


- Strong testimonials, case studies, or “before/after” examples that match their situation. [5]
- Behind-the-scenes walkthroughs or sample modules so they can “try before they fully buy.” [5]


## 10. Positioning and exclusivity


- “For people like you” positioning: niche the offer so it feels built just for them. [2]
- Limited seats, cohorts, or founder perks that feel like joining a tribe, not buying a random product. [3]


If you tell me what specific offer you’re selling right now (course, membership, service, etc.), I can turn these into a concrete “value stack” for that one offer.


Citations:
[1] E-commerce Delivery Promises: Mastering Strategies to Boost Sales https://fenixcommerce.com/BlogPost?slug=delivery-promise-as-a-marketing-tool
[2] Value Driven Offers, Done Right, Help People Say Yes https://www.usdatacorporation.com/blog/value-driven-offers-done-right-help-people-say-yes/
[3] Adding Bonuses and Guarantees That Skyrocket Conversions https://hellobrandshop.com/the-and-more-advantage-adding-bonuses-and-guarantees-that-skyrocket-conversions/
[4] Everyone talks about "providing value" to prospects during the sales ... https://www.reddit.com/r/sales/comments/11mu88b/everyone_talks_about_providing_value_to_prospects/
[5] Four Simple Steps To Creating High-Value Offers That Sell - Forbes https://www.forbes.com/councils/forbesbusinesscouncil/2021/01/21/four-simple-steps-to-creating-high-value-offers-that-sell/
[6] 10 Creative Ways to Make Your Home Purchase Offer Stand Out https://www.macu.com/must-reads/mortgage/make-your-home-purchase-offer-stand-out-fined
[7] How to Improve the Odds of an Offer https://www.nar.realtor/magazine/tools/client-education/handouts-for-sellers/how-to-improve-the-odds-of-an-offer
[8] Some Examples of A Value Stack | @SalesRemastered - YouTube https://www.youtube.com/watch?v=ZrREPEKaAG8
[9] 10 Life-Changing Home Hacks That Will Make It Smell Amazing! https://www.youtube.com/watch?v=KsRQuWBmVSA
[10] 11 Ways to Make Your Offer More Competitive https://www.chicotsky.com/news/119-11-ways-to-make-your-offer-more-competitive
[11] How to Make Irresistible Offers with Value Stacking (Marketing Hack ... https://www.youtube.com/watch?v=dxZnX6LcYMk
[12] How to design a bonus structure for your marketing team - LinkedIn https://www.linkedin.com/posts/prestonr_lesson-learned-the-bonus-structure-we-chose-activity-7369154853954052096-elT0
[13] Experts Reveal How To Make Your Home Smell Amazing All The Time https://www.forbes.com/sites/amandalauren/2022/10/14/experts-reveal-how-to-make-your-home-smell-amazing-all-the-time/
[14] How to Make Your Offer Stand Out Fast! - YouTube https://www.youtube.com/watch?v=OpPsZNOisvk
[15] Intro to Value Stacking | Nick Gulic https://nickgulic.com/intro-to-value-stacking/




Yahoo Mail: Search, Organize, Conquer
Reply
Forward
Here are the top 10 ways to add value to what you sell:


1. **Faster delivery** — Speed wins. Same-day, next-day, or guaranteed delivery windows beat competitors who leave customers waiting.


2. **Save them money** — Bundle deals, loyalty discounts, bulk pricing, or showing the ROI of your product makes the decision easy.


3. **Better guarantee** — A stronger warranty, hassle-free returns, or a money-back promise removes the risk of buying and builds trust.


4. **Done-for-you setup** — Offer installation, onboarding, or implementation so customers don't have to figure it out themselves.


5. **Ongoing support** — 24/7 access, a dedicated rep, or a real human on the phone is a huge differentiator when competitors only offer chatbots.


6. **Customization** — Let customers tailor the product or service to their specific needs. People pay a premium for "built for me."


7. **Education & expertise** — Tutorials, guides, consultations, or training that help customers get more out of what they bought keeps them loyal.


8. **Exclusive access** — Early releases, members-only perks, or insider information makes customers feel like VIPs rather than just transactions.


9. **Save them time** — Automate something, eliminate a step in their process, or consolidate multiple vendors into one. Time is often worth more than money.


10. **Peace of mind** — Certifications, social proof, transparent pricing, and proactive communication reassure customers they made the right call — reducing buyer's remorse and increasing referrals.


The biggest wins usually come from combining a few of these. For example, **fast delivery + great guarantee + real support** is hard to compete with. Want me to tailor these to your specific product or industry?




Yahoo Mail: Search, Organize, Conquer
Reply

Understand the offer-system generator before using its scaffolds

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

What the script creates—and what still needs work

The assigned Google Doc contains an Apps Script folder/file generator and an embedded “Version 2 — Elite Offer Architect” prompt. It proposes a Drive root named `IRRESISTIBLE_OFFER_OS`, placeholder documents and sheets, and two populated prompt files. Creating folders and placeholders does not create validated offers, working campaigns, Trello synchronization, running agents or a completed course. No code from this source is executed by this lesson.

The source's setup sequence is to open Google Apps Script, paste the script, optionally set `PARENT_FOLDER_ID`, run `createIrresistibleOfferOS()` and authorize the requested permissions. Treat that as the source's proposed workflow, not a claim that the unmodified script has been tested against your account. Review permissions, API compatibility, file types, duplicate names, overwrite behavior and recovery before any real use.

`PARENT_FOLDER_ID` defaults to an empty string. `FORCE_OVERWRITE_PROMPT` defaults to false. The first selects a parent or My Drive root; the second controls replacement of the two prompt files only. It is not a universal rollback mechanism or proof that all operations are harmless. The script performs real file creation and, in some paths, moves, trashing or content replacement if run.

Understand all ten top-level areas

FolderIntended use and actual generated state
`00_SYSTEM_CONTROL`Holds overview, map, version and automation documentation, a KPI placeholder and the master prompt. It organizes intended governance; it does not enforce governance.
`01_INPUT_PIPELINE`Holds source inputs in separate folders. No intake, scraping, transcription or validation pipeline is implemented.
`02_OFFER_ENGINE`Holds nine groups of offer-development placeholders. The embedded prompt can guide drafting, but no model is called by the script.
`03_CONTENT_MACHINE`Holds content-format folders. No landing pages, videos, emails or ads are authored merely by creating them.
`04_AUTOMATIONS`Holds workflow and prompt folders. It does not connect Make, n8n, Zapier, agents or webhooks.
`05_TRELLO_SYNC`Holds board-map placeholders, card templates and checklists. It contains no Trello API synchronization.
`06_COURSE_BUILD`Holds nine module folders plus slides, worksheets and exercises. Those legacy modules do not replace the current 12-course spreadsheet.
`07_TESTING_OPTIMIZATION`Holds tests, heatmaps, feedback, objections, iterations and a metrics placeholder. No experiment or measurement is run.
`08_SCALING_AUTHORITY`Holds future offer and distribution planning folders. None proves an operating partnership, affiliate system or high-ticket offer.
`09_ARCHIVE`Creates an archive folder. It does not implement retention, version history or backup restoration.

Populate the control and input areas deliberately

The control documents are `system_overview.md`, `folder_map_index.md`, `version_log.md`, `automation_map.md` and `trello_board_map.md`; `kpi_dashboard_sheet.xlsx` is a spreadsheet placeholder. Use them respectively to describe purpose, locate assets, record changes, describe proposed integrations and map board structure. The generator does not supply those completed explanations or actual KPI calculations.

The input folders are `raw_ideas`, `market_research`, `competitor_assets`, `customer_interviews`, `transcripts`, `images`, `websites` and `docs`. Their separation can preserve provenance. As authored application, record source, date, access conditions and what was actually reviewed before using an input. A folder labeled transcripts does not establish that an audio recording has been transcribed accurately, and a competitor asset is not automatically licensed for reuse.

Use all nine offer-development groups

02.1 Strategic Diagnosis: `diagnosis_summary.md` summarizes the current evidence; `buyer_avatar.md` defines the intended buyer; `pain_map.md` and `aspiration_map.md` distinguish difficulties from desired changes; `problem_cost_analysis.md` records a supported cost model; and `competitive_landscape.md` compares actual alternatives. All begin as placeholders, so unsupported customer facts should remain unknown or hypotheses.

02.2 Big Four Framework: the four question files are `Q1_What_Are_You_Selling.md`, `Q2_How_Much.md`, `Q3_Why_Believe_You.md` and `Q4_Whats_In_It_For_Me.md`. `combined_big_four_master.md` brings the answers together. Define the actual product, price and terms, credible evidence and useful customer benefit. Do not answer the proof question by inventing authority.

02.3 High ROI Engineering: `roi_tangible.md`, `roi_intangible.md`, `roi_compounding.md`, `loss_avoidance.md` and `opportunity_cost.md` separate different kinds of possible return. `roi_math_model.xlsx` is a blank native Sheet, not a validated calculator. Monetary, subjective and hypothetical benefits must not be added as if they were interchangeable measured cash flows.

02.4 Touchstone Lab: `touchstone_v1.md`, `touchstone_v2.md` and `touchstone_variants.md` hold alternative concise messages; `hook_matrix.md` organizes openings; `touchstone_testing.xlsx` is a testing placeholder. Explain the message's promised value and compare understanding, not attention alone. Version labels do not imply any version has been tested.

02.5 Believability Architecture: `authority_stack.md`, `credentials.md`, `logic_rationale.md`, `risk_reversal.md` and `why_this_offer_exists.md` address expertise, proof, reasoning, commitments and origin. The `case_studies` and `proof_assets` folders hold supporting material only when genuine evidence is added. Credentials and testimonials cannot be generated as facts from a prompt.

02.6 Logic and Emotion Alignment: `emotional_driver.md`, `logical_justification.md`, `decision_map.md` and `identity_shift.md` distinguish motivation, reasons, decision process and hoped-for identity. Use actual customer evidence where available. Do not diagnose hidden insecurity or promise an identity transformation from a brief input.

02.7 Offer Intensifiers: `bonus_stack.md`, `guarantee_versions.md`, `delivery_acceleration.md`, `scarcity_real.md`, `exclusivity_layer.md` and `premium_upgrade.md` hold proposed additions. Tie bonuses to useful needs, cost guarantees, verify faster delivery capacity and use only real limitations. A filename containing “real” does not validate scarcity.

02.8 Final Offer Output: `offer_master_document.md` and `offer_summary.md` hold full and shorter descriptions. `headline_versions.md`, `30_second_pitch.md`, `10_second_pitch.md`, `3_second_pitch.md`, `one_sentence_offer.md` and `elevator_pitch.md` adapt the explanation to different lengths. Each version should preserve the same material scope and conditions rather than becoming more exaggerated as it gets shorter.

02.9 Offer Continuum Positioning: `market_positioning.md`, `differentiation_map.md`, `authority_path.md` and `offer_evolution_plan.md` document comparison, relevant difference and possible development. These are plans to test, not proof of market leadership or a guaranteed growth path.

Complete the remaining folder inventories

The content folders are `landing_pages`, `vsl_scripts`, `webinar_scripts`, `email_sequences`, `social_media`, `youtube`, `short_form`, `blog_posts`, `ad_copy`, `retargeting_copy` and `funnel_map`. Adapt a consistent source message to each format's purpose. Creating them neither publishes content nor licenses third-party media.

The automation folders are `make_scenarios`, `n8n_workflows`, `zapier_zaps`, `prompt_library`, `gpt_agents`, `claude_agents`, `webhooks` and `data_sync`. They identify intended storage for future implementation. Actual workflows need defined inputs, outputs, credentials, permissions, error handling and verification. No running integration is present in the source script.

Trello planning creates `offer_pipeline_board_map.md`, `content_production_board_map.md`, `testing_board_map.md`, plus `card_templates` and `checklists`. Define statuses, owners and acceptance evidence before treating a board map as an operational process. No cards or boards are created by this script.

The course folders are `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` and `exercises`. There are nine module folders but ten prompt phases below. Their numbers do not align one-to-one; for example, the prompt's phase seven is viability, not the seventh folder's intensifiers. Preserve this difference and follow the current spreadsheet for lesson assignment.

Testing creates `ab_tests`, `heatmaps`, `customer_feedback.md`, `objection_log.md`, `iteration_log.md` and `conversion_metrics.xlsx`. Use those for an explicit hypothesis, observed behavior, feedback, objections, changes and consistently defined metrics. The spreadsheet initially contains a README message rather than events, formulas or a dashboard.

Scaling creates `premium_offer_versions`, `continuity_models`, `upsells`, `high_ticket`, `partnerships`, `affiliate_system` and `authority_content`. Each needs evidence of a customer need, feasible fulfillment and actual terms. The presence of a folder does not establish that a partner or affiliate agreement exists.

Examine the embedded prompt's ten phases

The prompt identifies itself as trained in Mark Joyner's complete principles, calls its purpose engineering inevitability and says it can transform any input into a scalable offer. Those are source assertions, not verified capabilities or proof of complete fidelity to Joyner's work. A prompt cannot guarantee purchase, remove uncertainty or authenticate an input merely by directing itself to do so.

Phase 1—Strategic Diagnosis: answer what is sold, who the highest-value buyer is, what problem is solved, what pain is removed, what aspiration is served, what measurable outcome is created, what emotional insecurity exists and what competitive alternatives exist. The source says to infer positioning when unclear. As an authored safeguard, label those inferences as hypotheses and seek evidence; do not treat guessed insecurity or customer value as known facts.

Phase 2—Big Four: explain the product concretely. For price, cover the price/tier, value-to-cost comparison, cost of not buying and opportunity cost. For belief, address authority markers, proof, logic, structural rationale, risk reversal, social validation and transparency. For customer benefit, distinguish functional, emotional, identity/status, risk, time, wealth, avoided pain and long-term transformation dimensions. Count these as distinct considerations, not automatic benefits present in every offer. Present only supported claims and actual commitments.

Phase 3—High ROI Engineering: examine tangible return, intangible return, speed, magnitude, probability, loss avoided and longer-term compounding. A weak or unclear return may call for redesign, but not every useful service has a predictable monetary return. State the measurement basis and avoid invented multipliers.

Phase 4—Touchstone Creation: create seven options that are short, emotionally relevant, clear about value, suggest a supported return, invite curiosity, remain memorable, avoid weak hype and avoid price emphasis unless strategically appropriate. For each, identify the intended emotion and logical reassurance. These are drafting criteria; actual audience response must be assessed. A hook should lead into the real story and offer, as in ClickFunnels' primary explanation.

Phase 5—Believability Architecture: design credibility anchors, proof positioning, an explanation of why the offer exists, pricing rationale, risk reversal, qualification signals, authority positioning and trust accelerators. If an offer seems implausible, investigate the claim and delivery model before merely writing a persuasive explanation. Never fabricate proof to satisfy the prompt.

Phase 6—Logic and Emotion: define the emotional driver, logical justification, how they support each other and what would fail if one were missing. The source attributes an emotion-first decision axiom to Joyner; the attribution and its universality are not established here. Customers' decisions vary, and emotional relevance should not become manipulation.

Phase 7—Long-Term Viability: ask whether customers would feel the purchase was sound, buy again, recommend it, experience few refunds, improve the business's reputation, support ethical scaling and sustain continuing prosperity. These are seven hypotheses, not facts answered by a model's confidence. Look for delivery and customer evidence, including contrary cases.

Phase 8—Intensifiers: assess bonus stacking, speed, convenience, access, exclusivity, real scarcity, guarantee refinement and delivery compression. The source explicitly rejects fake scarcity and manipulation. Define what is actually included and sustainable. The Acquisition.com value framework can help examine time and effort alongside outcome and likelihood, without guaranteeing conversion.

Phase 9—Continuum Positioning: classify the source's proposed commodity, value, premium, authority or dominance categories and explain the next possible evolution. These are source labels, not an externally validated ranking system. Claims of authority or dominance require evidence rather than self-assignment.

Phase 10—Final Output: deliver all fourteen items: headline, primary touchstone, core promise, benefit breakdown, ROI summary, believability stack, logical justification, emotional hook, risk reversal, intensifiers, thirty-second pitch, ten-second pitch, three-second pitch and a separate three-second “Sell Yourself” version. Preserve the distinction between the two final three-second outputs. Short versions must not omit a condition in a way that makes their claim misleading.

Apply the additional prompt rules as review criteria

The auto-correction list asks for redesign if the offer relies mainly on price cuts, lacks measurable ROI, sounds generic, has weak believability, emphasizes benefits without proof, lacks emotional relevance or would not sustain five years. Treat the five-year criterion as an unverified planning horizon, not something a prompt can guarantee. Fix the actual weakness rather than merely making the copy sound stronger.

Optional advanced mode asks for nine additions: competitor disruption, blue-ocean positioning, lifetime-value planning, an offer ladder, continuity design, a high-ticket version, authority development, an offer-testing framework and A/B touchstone variants. These require separate evidence and design work. The original names them but supplies no completed business plans or test results.

The five desired buyer reactions are that the offer makes sense, feels right, seems safe, appears valuable and seems foolish to reject. These are persuasive aspirations in the source, not permission to shame a buyer or imply risk-free certainty. The five output requirements are to follow phase order, use phase headings, answer every Big Four question, include touchstone/ROI/believability and make the design scalable and ethical. Check each while preserving honest uncertainty.

Understand the helper functions and compatibility limits

The parent helper uses a supplied folder ID when present. Otherwise it creates a temporary root-locator file, reads its parent or falls back to the root folder, then trashes the temporary file. That is a real write-and-trash side effect, not a read-only lookup. A simpler design could use an appropriate root API, but that would be an authored revision requiring review rather than a claim about the original.

The folder and file helpers reuse the first matching name under the parent. They do not detect multiple same-name matches, validate MIME types consistently or prevent concurrent runs from creating duplicates. “Idempotent” in the comment is therefore limited to a simple expected-name scenario. There is no transaction or complete rollback if the script stops halfway.

The document helper creates a native Google Doc named with `.md`, adds a heading and a TODO message, then moves it using add/remove-parent calls. The sheet helper creates a native Google Sheet named with `.xlsx`, renames the first tab README and adds a TODO message. These suffixes do not make the files Markdown or Excel binaries. An integration expecting those formats would need an appropriate export or different creation method.

The Google Folder API reference marks the source's `addFile` and `removeFile` methods deprecated. Review current `moveTo` or shortcut behavior in the File reference, ownership and folder permissions before adapting the code. This lesson does not claim the legacy calls have been tested successfully in the user's account.

Two populated prompt copies are proposed: `/00_SYSTEM_CONTROL/prompt_master_v2.md` is a native Google Doc, and `/04_AUTOMATIONS/prompt_library/offer_engine_v2.txt` is a plain-text file. With overwrite disabled, the first matching existing prompt is retained. With it enabled, the Doc body is cleared and replaced, while the text file's content is replaced. Neither path checks for unexpected file types or protects user edits through a version comparison. A partial failure can leave the two copies different.

The prompt builder generates a timestamp in the script time zone and includes version, owner and “LOCKED MASTER” text. That label does not lock permissions or make the file immutable. The plain-text conversion removes Markdown heading lines and fenced blocks; because phase titles are Markdown headings, it removes them too despite the comment about keeping structure readable. Preserve the original code and test an explicitly authored correction before using that output in an automation.

Logging reports folders and files created or reused and the root URL. A “Done” log is not proof that later offer content, integrations or course assets exist. Verify generated objects, actual types, content, locations, duplicates and overwrite outcomes before treating a run as successful. No such run has been performed here.

Sources and complete original

- Assigned folder/file generator and embedded prompt. - Apps Script entry point named by the source. - Google Folder API reference. - Google File API reference. - ClickFunnels hook, story and offer. - Acquisition.com Value Equation.

The full original script and prompt are retained in the appendix. The lesson explains every folder group, prompt phase and helper behavior while keeping scaffolding, proposed automation and validated business results distinct.

Assigned source links

D0467 original source 1

Complete returned native document text

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;
}
Complete local source copy including original filing metadata and formatting

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;
}

Build the complete customer-outcome evidence packet

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Purpose, prerequisites and scope

The source calls this M10.2, Customer Outcome Documentation, in Stage 2 “The Sailboat.” It estimates eight active operator hours, potentially longer when feedback must be retrieved, and requires a validated M10.1 Proof Threshold Attestation. These are source workflow labels and planning estimates, not changes to the current spreadsheet assignments or measured completion times for RISER. The deliverable is one structured entry for every customer classified as COUNTS under that prerequisite, commonly three to six in the source's example range.

Each entry has five components: promised outcome, delivered outcome, verbatim customer feedback, friction and operator learnings. Keep customers separate before later synthesis. A customer count establishes transactions only when supported by the required evidence; it does not establish what customers received. This packet supplies the evidence for that second question.

The discipline supports credible proof in an offer presentation. Brunson-style story and offer communication should accurately describe what happened. Hormozi's perceived-likelihood dimension should rest on relevant evidence rather than an inflated success narrative. A packet is an internal record first; a customer's feedback is not automatically permission for marketing use.

1. Recover the promised outcome at sale

The source identifies six possible records: the offer document, captured sales-call recordings or notes, engagement letter or contract, onboarding emails, proposal and the operator's closing notes. Compare them because a verbal commitment may extend the written offer. Preserve the actual purchase-time promise rather than replacing it with the latest version of the offer.

Specificity matters. The source contrasts a vague business-growth promise with an eight-week Series B readiness package containing a financial model, board memo and pitch deck. The latter identifies artifacts; it does not promise investment funding. If the original promise was vague, document that fact. It becomes a useful issue for the later Mastery Synthesis and Stage 3 Readiness work rather than a reason to invent specificity after the sale.

2. Document actual delivery and differences

Use project-folder deliverables, decks, documents, code, designs, training, calls, completion dates and the executed scope as evidence. Distinguish an artifact being delivered from the customer implementing it or achieving a downstream outcome. Where relevant, link to the version actually handed over.

The source gives three examples of legitimate differences: an agreed scope pivot when circumstances change; refusal of a casually requested addition outside the original promise; and delayed customer inputs or missed sessions extending time without changing scope. Document the agreement, boundary or delay rather than saying vaguely that everything was delivered as expected.

It also lists promising X but delivering Y because X was harder, providing a smaller X while calling it complete, and adding unbilled scope as dishonest differences. The first two require a transparent account of the shortfall. Unbilled extra work, however, is not inherently dishonest: the related template explicitly describes honest extra mock-pitch work. Record what happened, whether the core promise was met, whether the change was understood and its cost. Preserve this conflict rather than force a moral label unsupported by the evidence.

3. Separate customer experience from operator interpretation

Customer-reported experience can come from written feedback, emails, feedback forms, testimonials, consented call recordings and transcripts, or a direct response to a feedback request. Renewal, referral, continued engagement and silence are behavioral signals, but they do not reveal motives by themselves. Record the behavior separately from a hypothesis about what it means.

For each customer, the source asks for at least one quotation that is actually verbatim, sourced and representative. Keep the wording, qualifications and relevant context. Identify the date and channel; for a prompted response, preserve the question too. Do not paraphrase “this was useful” into strong satisfaction, or select only a flattering line from a mixed response.

The source suggests seeking feedback if none exists. This lesson sends no messages. If an actual attempt produces no response, document the attempt and missing feedback honestly. That record is not equivalent to a customer-validated outcome. The source refers to a separate outreach template, but that exact template has not been located in the reviewed material; the related outcome template contains fields for logging outreach rather than a complete outreach script.

The reviewer specification demands a quotation even where the template and this module allow a nonresponse record. Mark the gap and acceptance conflict explicitly. Do not fabricate feedback or repeatedly pressure a customer to manufacture evidence for a course requirement.

4. Capture friction and practical learning

The four source friction examples address different causes: three-week rather than one-week onboarding because systems need integration; two revision cycles because stakeholders were not aligned; partially absorbed scope creep; and a two-week communication gap in week four that shifts the schedule. Record the specific event, its effect and the response. Friction is a signal for improvement, not a blame exercise.

The three learning examples turn those observations into changes: customers underestimate implementation time, so onboarding may need calendar-blocking guidance; a revision-prone deliverable may need earlier staging; and recurring scope requests may require clearer verbal explanation of exclusions during onboarding. These are proposed adjustments, not universal rules. Link each learning to its evidence and label whether it is planned, tested or implemented.

The source identifies offer architecture, pricing and onboarding as possible destinations for improvement, and connects the learnings with later C7/C8/C9 work, M10.5 synthesis and M10.6 readiness. Keep those legacy links visible without silently remapping the current curriculum. One isolated event may justify investigation without establishing a cross-customer pattern.

Recognize all four inflation patterns

Aspirational outcome: Saying a customer implemented a comprehensive transformation overstates delivery when they only received a strategy document and committed to a future 90-day plan. Record the document and commitment; implementation results remain unknown or outside scope.

Paraphrase substitute: Replacing a modest customer message with “deep satisfaction” adds interpretation. Use the actual sourced wording and label any separate interpretation as your own.

Cherry-picked quotation: A flattering sentence may misrepresent a longer mixed response. Preserve enough context to communicate both benefit and qualification; do not remove a criticism simply because it weakens a sales story.

Universalizing frame: “All three achieved their objectives” hides variation if one completed the intended result, one achieved a different agreed result and one is only halfway through four milestones. Preserve the individual states rather than flattening them into one success claim.

The source says its Sonnet validator is calibrated to detect these problems. No calibration evidence or working deployment is supplied here. A review prompt can help organize checks, but it cannot authenticate records or guarantee that an inflated claim will be detected.

Follow the complete seven-step workflow

  1. Compile the per-customer offer, sales notes, contract, onboarding emails, deliverables, correspondence and feedback.
  2. Draft the specific promised outcome, including written and additional verbal commitments.
  3. Draft actual delivery with dates and explain differences.
  4. Retrieve representative verbatim feedback or document the actual nonresponse and access gap.
  5. Describe concrete friction from the engagement records.
  6. State what the evidence changes in the operator's understanding.
  7. Review the entry against the template checklist before submitting it.

Repeat for every counted customer. Preserve links to source records in the controlled packet. Do not replace this per-customer structure with one promotional narrative about all customers together.

This module does not itself analyze refunds, validate pricing against actual hours or perform cross-customer mastery synthesis. The source assigns those to M10.3, M10.4 and M10.5 respectively. The packet supplies their inputs; it does not prove that any downstream review has passed.

Apply the six submission checks and reconcile verdicts

Check that every counted customer has an entry; each includes all five components; quotes are sourced and representative; differences are explained; paraphrases are not presented as quotations; and aspirations are not described as completed outcomes. Where feedback is missing, the honest record remains incomplete as customer validation even if the logging fields are filled.

The module names CONFORMS, REVISIONS_REQUESTED and OUTCOME_VAGUE_FLAG. Its linked YAML instead names APPROVED and REVISIONS_REQUIRED. Keep both vocabularies visible and require an explicit mapping if implemented. A prose instruction calling a validator “Sonnet” does not establish a valid model identifier, access to records or an approved automation. No review verdict is issued for actual customers in this lesson.

Sources and further reading

- Assigned M10.2 customer-outcome module. - Customer Outcome Documentation Template. - Customer-outcome reviewer YAML. - Lincoln Murphy's Sixteen Ventures — source-named customer-success background; no complete methodology corpus reviewed here. - Bob Moesta's Demand-Side Sales 101, author-company page — background on understanding customer progress. - Teresa Torres's Continuous Discovery Habits, author page — background on continuous discovery.

The source's references to these authors and qualitative research are background attributions, not proof that they endorse this particular capstone or validator. Their full books are not reproduced or claimed as reviewed. The complete assigned native module remains in the appendix alongside this teaching.

Assigned source links

D0468 original source 1

Complete native original body, including retained document-part text

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

# M10.2 — Customer Outcome Documentation

**Module:** 10.2
**Title:** Customer Outcome Documentation — What Was Promised, Delivered, and Experienced
**Stage:** 2 — The Sailboat (capstone)
**Duration:** 8 hours (active operator time; longer if customer feedback retrieval requires reaching back to customers for explicit verbatim quotes)
**Deliverable:** Customer Outcome Documentation packet — one entry per paying customer following the template
**Validator:** `customer-outcome-reviewer-v1.0.0.yaml` (Sonnet)
**Prerequisite:** M10.1 Proof Threshold Attestation validated

---

## What This Module Does

M10.2 takes every customer classified as COUNTS in M10.1 and produces a structured documentation entry for each. The entry has five required components: promised outcome, delivered outcome, customer's verbatim feedback, friction points, and operator learnings. The sum of these entries — typically 3–6 customers worth — is the Customer Outcome Documentation packet that feeds the Stage 2 Graduation Document at M10.8.

This module is the empirical heart of the capstone. The Proof Threshold count (M10.1) establishes that customers exist. The Customer Outcome Documentation establishes what those customers actually got. Without M10.2 done well, the threshold count is hollow; with M10.2 done well, the threshold count is load-bearing.

The discipline of M10.2 is **honest distinction**. Three different things must be tracked separately and not conflated: what was promised at the time of sale, what was delivered at the end of engagement, and what the customer subsequently experienced. These three things may differ in honest, anti-promise-respecting ways (a delivered outcome may legitimately differ from a promised outcome if the customer's situation evolved, or if anti-promise discipline was applied). Operators who conflate them — typically by collapsing all three into "the customer got what they paid for" — produce documentation that the validator will reject.

---

## The Three Things Being Documented

### 1. Promised Outcome (at the time of sale)

What did the operator commit to when the customer paid? This is recoverable from: the offer document the customer saw or heard, the sales call recording or notes if captured, the engagement letter or contract, the onboarding email sequence, the proposal document, and the operator's own notes from the close.

The promised outcome is specific. It is not "I will help you grow your business." It is "by the end of the 8-week engagement, you will have a documented Series B readiness package including financial model, board memo, and pitch deck." Specificity is the standard. If the operator cannot articulate a specific promised outcome from the time of sale, the customer was sold something vague — which is itself information for the Mastery Synthesis (M10.5) and the Stage 3 Readiness Document (M10.6).

### 2. Delivered Outcome (at the end of engagement)

What did the operator actually produce, ship, hand over, deliver? This is documented in: the deliverables filed in the customer's project folder, the artifacts produced (decks, documents, code, designs, training, calls held), the timeline of completion, and the engagement scope as actually executed.

The delivered outcome may differ from the promised outcome in honest ways. Examples: the customer's situation evolved mid-engagement and the operator pivoted the engagement scope with the customer's explicit agreement; the operator applied anti-promise discipline and declined to deliver scope that was casually requested but not in the original promise; the customer slowed delivery (delayed inputs, missed sessions) so the engagement extended in time but not in scope. These honest differences are documented as differences with reasoning.

The delivered outcome may also differ from the promised outcome in dishonest ways. Examples: the operator promised X and delivered Y because X turned out to be harder than expected; the operator added scope without billing; the operator delivered a smaller version of X and called it complete. These dishonest differences are also documented — they are exactly the data the Refund Analysis (M10.3) is built from.

### 3. Customer-Experienced Outcome (what the customer actually got from the engagement)

What did the customer report experiencing? This is recoverable from: customer feedback in writing (email replies, written feedback forms, testimonials), customer feedback verbatim from calls (recorded with consent, transcribed), customer behavior signals (renewal, referral, ongoing engagement, ghost), and direct outreach for explicit feedback if the engagement did not produce sufficient feedback in its natural course.

The customer-experienced outcome is the part operators systematically misdocument. The temptation is to write what the operator believes the customer experienced. The discipline is to write what the customer themselves reported, in their own words, even when that reporting is sparse, ambiguous, or misaligned with the operator's narrative.

This is why M10.2 requires verbatim quotes. Paraphrased feedback masks the gap between what the operator believes the customer experienced and what the customer reported. Verbatim feedback exposes the gap.

---

## The Verbatim Feedback Requirement

For each paying customer, M10.2 requires at least one verbatim quote from the customer in their own words. The quote must be:

- **Actually verbatim.** Not "essentially what they said" or "the gist of their feedback." The actual words, with the actual phrasing, with the actual hesitations or qualifications if present.
- **Sourced.** From an email (with date), a transcribed call (with date), a written testimonial (with date), or a direct outreach for feedback (with date and the question that prompted the response).
- **Representative.** Not cherry-picked to be the most flattering quote. If the customer's feedback was mixed — and most customer feedback is mixed — the quote should reflect the texture of the mixed feedback. If the operator can find only effusive praise to quote, the validator will ask for a quote that includes the customer's caveats or concerns.

If the operator cannot produce verbatim feedback for a customer, the operator reaches out to the customer now, with a brief, professional message asking for explicit feedback for the operator's records. The Reference document includes a template for this outreach. Customers who do not respond to the outreach are documented as "no verbatim feedback obtained despite outreach on [date]" — this is honest. It is not, however, the same as having verbatim feedback. The Mastery Synthesis (M10.5) will note that one or more customer outcomes are not customer-validated, which is a meaningful pattern.

---

## Friction Points and Learnings

Each entry also documents friction points and learnings. These are the texture of the engagement that the outcome documentation alone does not capture.

### Friction Points

What went wrong, was difficult, took longer than expected, or required correction during the engagement? Specific examples: onboarding took three weeks instead of one because the customer's existing systems required custom integration; the third deliverable required two revision cycles because the customer's stakeholders were not aligned at the outset; mid-engagement scope creep was negotiated and partially absorbed into the engagement at no additional charge; the customer ghosted for two weeks in week 4 and the engagement timeline shifted accordingly.

Friction points are not blame. They are signal about where the offer architecture (C7), pricing (C8), or onboarding (C6) needs adjustment for future engagements.

### Learnings

What did the operator learn from this engagement that updates their model? Specific examples: customers in industry X consistently underestimate their own implementation time, so the engagement should include explicit calendar-blocking guidance in onboarding; the third deliverable's revision-cycle pattern suggests the deliverable should be staged earlier in the engagement to allow more revision time; the scope-creep pattern is consistent across customers and suggests the anti-promises in the offer document should be made more explicit verbally during onboarding.

Learnings are the C7/C8/C9 inputs for next quarter. The Mastery Synthesis (M10.5) draws on these. The Stage 3 Readiness Document (M10.6) draws on these.

---

## How Honest Documentation Differs from Inflated Documentation

The Sonnet validator (`customer-outcome-reviewer-v1.0.0.yaml`) is calibrated to detect inflated documentation. The most common patterns it catches:

**Inflation Pattern 1 — The Aspirational Outcome.** "By the end of the engagement, the customer had successfully implemented a comprehensive transformation strategy." Honest version: "By the end of the engagement, the customer had received the strategy document and had committed in writing to a 90-day implementation plan. Implementation outcomes are outside the engagement scope and have not been documented." The honest version distinguishes what was delivered from what may eventually result from delivery.

**Inflation Pattern 2 — The Paraphrase Substitute.** "The customer expressed deep satisfaction with the engagement." Honest version: "The customer wrote on [date]: 'this was useful, thanks. Let me know about future programs.'" The honest version surfaces that the customer's actual words were modest and forward-looking, not effusively satisfied.

**Inflation Pattern 3 — The Cherry-Picked Quote.** Selecting the single most flattering line from a long mixed feedback. Honest version: representative quoting that reflects the texture of the feedback, including caveats.

**Inflation Pattern 4 — The Universalizing Frame.** "Across all three engagements, customers consistently achieved their stated objectives." Honest version: per-customer documentation that shows the actual variation — Customer 1 fully achieved the stated objective; Customer 2 achieved a related-but-different objective due to mid-engagement scope pivot; Customer 3 is mid-engagement and has progressed through milestones 1 and 2 of 4.

The validator's pushback on these patterns is not adversarial. It is the friend that lets the operator submit documentation that will hold up at M10.8 instead of being rejected.

---

## Producing the Customer Outcome Documentation Packet

For each customer counted in M10.1, complete one Customer Outcome Documentation entry using the Customer Outcome Documentation Template (`02_Resources/Customer-Outcome-Documentation-Template.md`).

Recommended workflow:

1. **Compile per-customer source material.** Pull the offer document, sales notes, contract, onboarding emails, deliverables, customer correspondence, and any captured feedback into a per-customer folder. This is the raw material.

2. **Draft the promised outcome.** From the offer document and sales notes, write the specific promised outcome. If multiple promises were made (some in the offer document, some verbally during the close), document them all.

3. **Draft the delivered outcome.** From the deliverables and timeline, write what was actually produced. Note any honest differences from the promise with reasoning.

4. **Retrieve verbatim feedback.** From the correspondence and captured feedback, select the most representative quote (not the most flattering). If none exists, conduct outreach for explicit feedback.

5. **Document friction points.** From the engagement records, list specific friction. Be concrete.

6. **Document learnings.** From the friction points and the engagement as a whole, name what updates the operator's model.

7. **Review the entry against the template's checklist** before submitting.

Repeat for each customer. The packet is complete when every M10.1-counted customer has an entry that passes the checklist.

---

## What This Module Does Not Do

M10.2 does not analyze refunds (that is M10.3). M10.2 does not validate pricing against actual hours (that is M10.4). M10.2 does not synthesize across customers — each entry is per-customer. The synthesis happens in M10.5 (Mastery Synthesis), which draws on M10.2 entries as primary source material.

Operators sometimes try to write a unified "customer outcomes" narrative across all paying customers in M10.2. This is the wrong shape; the validator will return it for restructuring. The right shape is per-customer documentation, with each customer treated as a distinct empirical data point.

---

## Submission Checklist

Before submitting M10.2 to the Sonnet validator:

- One Customer Outcome Documentation entry per M10.1-counted customer
- Each entry includes promised outcome, delivered outcome, verbatim quote, friction points, learnings
- Verbatim quotes are sourced (date, channel) and representative (not cherry-picked)
- Honest differences between promised and delivered are documented with reasoning
- No paraphrased substitutes for verbatim quotes
- No aspirational outcomes (what may eventually result is distinguished from what was delivered)

The validator returns: CONFORMS (proceed to M10.3), REVISIONS_REQUESTED (specific entries flagged for revision), or OUTCOME_VAGUE_FLAG (one or more entries lack the specificity required; revise and re-submit).

---

## Cited References

The discipline of customer outcome documentation draws on Lincoln Murphy's Customer Success methodology corpus, Bob Moesta's *Demand-Side Sales 101* (2020) on JTBD outcome capture, and Teresa Torres' *Continuous Discovery Habits* (2021) on outcome tracking patterns. The discipline of verbatim feedback over paraphrased summary draws on classical qualitative research methods — the verbatim quote is the empirical primary source; the paraphrase is the operator's interpretation, which is secondary.

---

*Module 10.2 of 8. Begin Refund and Outcome Analysis (M10.3) only after the Customer Outcome Documentation packet is validated.*

Analyze refunds, incomplete engagements and unspoken dissatisfaction

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Purpose and evidence boundary

The source calls this M10.3, Refund and Outcome Analysis, a Stage 2 capstone following a validated M10.2 outcome packet. It estimates five active operator hours and specifies a five-section Refund and Failure Analysis. Those are source planning requirements, not a measured runtime or a new mapping of the current courses. The lesson teaches how to account for what did not work without blaming people or turning hypotheses into facts.

The related refund-reviewer YAML was located and read. It adds seven cause categories, validation checks and a JSON response structure. Both originals are retained. Neither document proves a deployed, calibrated agent or current database access. No refund, customer outreach, database write or automated verdict is executed here.

Honest failure evidence supports the same promise/proof relationship used in sound offer design: show what the business can actually deliver, examine obstacles and revise the offer when evidence warrants it. A Brunson-style story or Hormozi-style value presentation becomes less credible when it hides delivery failures or invents certainty. Refund analysis should improve the product and promise, not manufacture a favorable marketing narrative.

Section 1: refunds granted

For each full or partial refund, record the customer identifier; amount and percentage of original payment; date relative to engagement start and end; specific triggering event; root-cause attribution at the sale, onboarding, delivery, scope or communication layer; and a correction implemented or planned. The reviewer also asks for the reason recorded at the time and the retrospective explanation. Preserve both if they differ.

As authored arithmetic, a $200 refund on a $1,000 original payment is 20%. That calculation does not explain why it happened or determine what remedy is appropriate. Use actual transaction evidence and the applicable commitment. If there were no refunds, record that explicitly and investigate the broader customer experience in Section 5 instead of treating zero refunds as proof of success.

Section 2: near-refund situations

Include situations where dissatisfaction led to a refund discussion, was contemplated, was demanded or was resolved without a refund. The source examples include additional work that retained a dissatisfied customer, written dissatisfaction without a formal request and a scope adjustment that resolved the issue.

Record the customer; specific trigger; resolution path; whether the resolution was sustainable at the original price or involved absorbed work; root cause; and systemic correction. Quietly absorbing extra scope can keep a relationship alive while hiding an economic problem. Document the time and commitment rather than describe every retained customer as an unqualified success.

Section 3: mid-engagement collapses

Record engagements that ended or changed materially before completion: prolonged silence, indefinite pauses, significant scope pivots or early termination. They are distinct from refunds because money may or may not be returned, and from near-refunds because the original engagement does not continue as planned. A single incident can have related entries, but avoid double-counting its financial impact.

Capture the customer, trigger, customer-circumstantial versus engagement-internal explanation, financial disposition, root cause and correction or documented edge case. The source's circumstantial examples are a new job, business pivot or lost funding; its internal examples are a misaligned offer, disappointing delivery or a broken price/value fit. Mixed causes are possible. Do not force a complex event into one category simply to protect the operator's reputation.

The source notes that an offer dependent on the customer keeping a particular role for six months may be more exposed to circumstantial change than an artifact-based engagement. That is a design question, not a proven comparative failure rate. Even external circumstances may reveal a useful improvement in qualification, contingencies or scope. Conversely, not every external event is an operator failure.

Section 4: disappointments without a refund

This section addresses completed, fully paid engagements where the hoped-for experience may not have been achieved despite no serious formal complaint. The source suggests signals such as a tepid testimonial, declined renewal, no referral or distant follow-up communication. These are observations, not proof of dissatisfaction; people may have many reasons not to renew or refer.

For each case, record the customer; specific signal; hypothesis about hoped-for versus received value; whether the hypothesis can be tested; the decision to test now, later or not at all; and any actual verbatim response. Separate known facts from the interpretation. Later general checklist language asks for root cause and correction for every entry, even though this section's field list does not explicitly include them. Add those as clearly identified working notes only when supported, leaving untested causes unresolved.

Section 5: investigate sparse negative evidence

When the first four sections are empty or sparse, the source requires a substantive investigation. For each otherwise unrepresented customer, consider both genuine fit and silent dissatisfaction. Active satisfaction evidence may include actual feedback, renewal, referral, ongoing engagement or verifiable public descriptions of the experience. Silence alone supports neither conclusion reliably.

The source proposes explicit feedback outreach where necessary. This lesson does not send messages. If feedback is sought in an authorized real workflow, preserve the request and response, or the nonresponse. Do not invent a concern simply because the reviewer expects negative signals. The correct conclusion may be that evidence is insufficient.

Attribute causes without vague blame

The module warns about three patterns. Customer-blame explanations such as “they were not ready” need investigation of qualification and onboarding as well as the customer's actual responsibilities. Vague statements such as “communication broke down” need a concrete event and mechanism. Cosmic explanations such as “it just did not click” need a description of what failed to fit and what could change.

Its detailed good example traces stakeholder disagreement to an onboarding process that asked about goals but not stakeholder alignment, despite the sale depending on aligned stakeholders. The proposed correction is an explicit alignment question. This is a useful causal hypothesis when the records support it; do not apply the same cause automatically to every revision or delay.

Distinguish two failure types. Type A is promising X and delivering less than X; own and address the delivery gap under the actual agreement. Type B is delivering X while the customer expected X-plus or downstream Y; investigate how that expectation formed and whether the offer fit. Type B may expose sales communication or fit problems even when the artifact met its specification. Do not relabel under-delivery as a customer expectation problem, or accept unsupported blame for results never promised.

Use all seven reviewer cause categories as prompts for investigation

Reviewer categoryMeaning and evidence needed
Anti-Promise breachA promised outcome depended on factors outside the operator's control. Compare the actual promise, dependencies and limitations; a delivered shortfall is not automatically this category.
Offer driftMid-engagement modifications changed the original mechanism while chasing requests. Distinguish harmful drift from an explicitly agreed, appropriate scope change.
Capacity exceededAccepted work exceeded the delivery capacity and degraded service. Review workload, timing and actual delivery evidence.
Mismatch at intakeThe customer did not fit the offer architecture. Examine what was knowable during qualification and what the offer required.
Mechanism failureThe stated method did not produce the intended outcome for this customer. Separate poor execution, unsuitable context and a genuinely weak method where evidence permits.
Customer execution failureThe customer did not perform their agreed portion. Preserve those responsibilities and events, while also examining whether expectations and support were realistic.
External shockA genuine outside event affected the engagement. Document the event and its effect rather than using the label to explain away a recurring internal problem.

The YAML asks for one cause per signal, but real events can have multiple contributing causes. Keep those contributions in the narrative instead of discarding them to simplify a count. The legacy references to C2/C4/C7 identify source dependencies only.

Apply the nine reviewer checks without manipulating the evidence

The reviewer checks refund records against proposed Supabase payments; requires cause categories for refunds; keeps collapses distinct from refund inventory; reconciles near-refunds with M10.2; cross-checks disappointments with M10.2 friction; requires substantive absence-of-signal analysis; tests two attribution percentages; and requires a final pattern synthesis.

The percentage thresholds are less than 30% customer-execution causes and less than 15% external-shock causes. No empirical basis is supplied. With three incidents, one customer-execution case is already 33.3%; with six incidents, one external-shock case is 16.7%. Those arithmetic facts do not prove blame-shifting. With zero incidents, a percentage denominator is undefined. Never reclassify true causes to pass an unsupported quota. Show counts, denominator, evidence and the limitation of the rule.

The requested pattern synthesis is additional to the five incident sections. Explain recurring observations, contrary cases and proposed changes without generalizing beyond the evidence. A database mismatch may indicate stale or missing records rather than dishonesty; the database comparison remains unverified without access.

Understand the seven red flags and output structure

The flags cover excessive customer blame; external-shock explanations for broad patterns; refund entries missing from the database; an empty collapse inventory despite friction in completed engagements; unsupported claims that silent customers were satisfied; no prevention action per refund; and missing discussion of promise breaches where delivery gaps exist.

Investigate each rather than accept it as a verdict. A completed engagement with friction is not necessarily a collapse. A database omission is not proof of rewritten history. A delivery gap does not always mean an uncontrollable result was promised. The source's claim that zero negative signals almost certainly means under-documentation is not established. Discomfort or defensiveness also does not prove whether a finding is correct.

The JSON-shaped output contains `section_completeness` with six booleans: `refund_inventory`, `midengagement_collapse_inventory`, `nearrefund_inventory`, `below_threshold_inventory`, `absence_of_signal_investigation` and `pattern_synthesis`. It contains `attribution_distribution` with counts for all seven categories, plus `supabase_match`, `m10_2_consistency`, `red_flags`, `revisions_required`, `verdict` and `narrative_summary`. N and `true | false` are illustrative placeholders, not valid final JSON values.

The YAML uses APPROVED or REVISIONS_REQUIRED; the module uses CONFORMS, REVISIONS_REQUESTED or ATTRIBUTION_VAGUE_FLAG. Reconcile the intended mapping before implementation. The YAML's model identifier `claude-sonnet-4-7` is unverified, and its `hitl_gated: false` is not authorization to remove oversight. The proposed output destination is `c10_refund_analyses`; no integration has been established by these documents.

Complete the seven module checks

Include all five sections; use specific triggers, causes and corrections; distinguish circumstantial and internal collapses; distinguish Type A from Type B; investigate beyond customer blame; avoid untestable cosmic explanations; and make Section 5 substantive when other sections are sparse. Add the reviewer’s pattern synthesis and disclose conflicting rules rather than silently changing the source.

The output feeds later M10.5 synthesis and M10.8 graduation review. The source says subsequent M10.4 pricing validation is human-in-the-loop gated and requires instructor review. Preserve that course requirement; this lesson does not assert that any actual instructor review has occurred. Completion means a traceable account of incidents, uncertainty and proposed corrections, not a favorable verdict manufactured from missing evidence.

Sources and original material

- Assigned M10.3 Refund and Outcome Analysis. - Located refund-analysis reviewer YAML. - Related M10.2 outcome packet module. - Atul Gawande: The Checklist Manifesto and author bibliography including Better. - Sidney Dekker: The Field Guide to Understanding Human Error, publisher page. - John Carreyrou: Bad Blood, publisher page.

The named books are source-cited background, not evidence that their authors endorse this particular validator. Their full text has not been reviewed or reproduced here. The assigned module and located reviewer are preserved completely in the appendix; the reviewer is a linked reference, not a newly completed assigned document elsewhere in the inventory.

Assigned source links

D0469 original source 1

Complete native original body, including retained document-part text

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.*
Complete located related refund-reviewer specification (D2919 reference, not a new assigned-source completion)

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`.

Anti-discount policy: make pricing decisions before the pressure arrives

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Assigned lessons: 03.1, 05.4, 07.1, 12.2 and 12.4. Legacy M8.6/C8 references identify the source workflow.

Outcome and prerequisites

You will build an anti-discount policy with explicit approved exceptions, explicit situations that do not qualify, spoken response patterns and a specific signed commitment. Align it with the existing pricing architecture and the offer's exclusions and guarantee. A policy should tell you what to do in a real conversation, not merely say you intend to hold your price.

The source names five outcomes: define approved discounts and their conditions; define non-exceptions with responses; use Voss, Enns and Stark script patterns; align with C4 anti-promise and guarantee architecture; and sign a discipline clause with accountability. It requires the M8.4 Pricing Architecture Document to be filed and scored at least 7/10 before this module. M8.5 may run in parallel, although its tier decision must eventually be reconciled with this policy.

The learner artifact is `Anti-Discount-Policy-[YourName]-[Date].md`, specified as 1,200–1,800 words, seven sections plus a signed clause. The source estimates four active hours over two sittings. That is a learner-work estimate, not measured production time or a completion guarantee. The final policy feeds M8.7's raise schedule and M8.8's capstone.

Why a written policy helps

The source offers three rationales. Pre-deciding the terms reduces improvisation during a difficult conversation. Consistent criteria can make the experience clearer for customers who qualify and those who do not. Holding an economically justified price can protect the resources required for delivery.

Its example is twelve engagements at a $6,750 base, each discounted 10%: $6,750 × 10% × 12 = $8,100 less revenue than twelve full-price sales. That is additive revenue reduction, not compound growth or proven lost profit. Actual sales without the discounts and delivery costs are unknown. The source's “Pricing Is Operator Self-Respect” doctrine is a commitment framework; a person's worth is not determined by the price they charge.

The Race-to-the-Bottom narrative describes concessions reducing resources, quality suffering, complaints or refunds increasing and further concessions worsening the situation. This is a mechanism to investigate, not an inevitable sequence caused by every discount. The linked composite case and recognition checklist require separate treatment, including their arithmetic and interpretation issues.

Build the finite exception list

For every exception, record six fields: its name, percentage or amount, eligibility, approval mechanism, documentation requirement and quarterly review cadence. Explain the economic or mission rationale. These source ranges are illustrative choices, not adopted RISER rates.

ExceptionSource termsRationale and approval conditions
Cohort early birdTypically 10–20%; time-bound cohort enrollmentEarlier cash collection and reduced enrollment uncertainty. Automatic for eligible enrollment before the specified date. The example applies to Darius's Reading Club, not Maya's one-to-one Sprint.
Partner or affiliateTypically 10–20% customer discount plus 10–25% partner commissionA designated partner must be on the documented list; combined economics must support delivery. Define the commission basis before claiming acquisition-cost savings.
Scholarship or need-basedTypically 30–50%, with a per-cohort or annual capDocumented eligibility and a defined operator commitment; mission/access or portfolio rationale. Collect only appropriate necessary information and handle it privately.
Returning-customer continuationTypically 10–15% within a defined windowPrior engagement completed with documented positive outcome; continuity and lifetime-value rationale.
Pre-launch or pilotTypically 20–40% for the first 1–3 cohortsA defined testing period and hard sunset date; feedback and iteration evidence. A discounted pilot does not require a favorable testimonial.

The source recommends two to four exceptions, warns about eight or more, and later says the rubric flags more than five. Those are different thresholds. Preserve the distinction rather than silently treating six or seven as unflagged. Review whether each exception serves a documented purpose and remains sustainable.

Define all eight non-exception responses

Budget constraint. Acknowledge the limit and explain the actual policy. Offer a real lower-cost course, self-paced resource, community option or later conversation when appropriate. Do not confuse inability to pay with lack of seriousness.

Competitor is cheaper. Acknowledge the comparison, explain the relevant scope and value without disparaging the competitor, and respect the buyer's choice. A lower price alone does not establish equivalent scope, but neither does your higher price prove superiority.

“I'll think about it.” Treat hesitation as information. Ask what needs clarification without offering a discount as a reflex. The source suggests an optional thirty-minute clarification call when there is a specific issue to discuss; do not schedule or promise one unless it is available.

Custom payment plan. Refer to M8.4's documented installment terms. Accept a request within those terms or explain what is unavailable. A payment schedule and a price reduction are different decisions; assess their actual economics rather than inventing new terms under pressure.

Special situation. Listen, then compare the situation with the approved exception list. Apply a genuine match; do not create a new exception merely because the request is sympathetic.

Two friends enrolling for a discount. Use an actual referral/partner policy if applicable or decline the proposed bundle. Do not offer a fictional partner route or an unapproved group rate.

Hardship outside documented eligibility. Respond with empathy and explain the scholarship path or an appropriate alternative. The source uses dismissive “sob story” language; the teaching should not assume dishonesty, demand public disclosure or shame someone for financial hardship.

Late or urgent request. Explain that urgency alone does not change the agreed price. Honor any real deadline or existing offer rather than inventing pressure. A late enrollment also does not guarantee that the full delivery window will still be available.

For each situation, write the likely request, the pattern used and a natural script. A list of denied requests without usable responses does not meet the source's standard.

Use the three conversation libraries with care

The source attributes four patterns to Voss tactical empathy: labels such as “it sounds like”; mirroring the last two or three words; calibrated questions; and an accusation audit naming a likely concern before it is raised. Use these to understand and acknowledge the concern. Mirroring does not force someone to elaborate, and a question should not transfer unfair pressure back to the buyer. The source's “How am I supposed to do that?” example needs context and a respectful tone.

The Black Swan Group's public terminology article describes a mirror using three to five words, whereas this assigned lesson says two to three. Preserve that difference: the practical aim is an inquisitive repetition of relevant wording, not a universal word quota. Its definitions also help distinguish acknowledging a perspective from agreeing to a discount. Neither description guarantees how another person will respond.

It attributes three positioning patterns to Enns: discuss fit, describe what the price reflects with composure, and be genuinely willing to accept a buyer's decision not to engage. Walking away should be a real option, not a bluff.

It attributes three value-language patterns to Stark: connect price to the intended outcome, describe an investment with evidence-based expectations, and distinguish the delivery window from the basis of price. Do not use “investment” to imply a guaranteed financial return or hide affordability concerns.

The source cites Never Split the Difference with 2016 and Hourly Billing Is Nuts with 2017, plus Pricing Creativity/Win Without Pitching. Retain those as source bibliography claims until edition details are verified. This review does not claim that the complete books were read. The libraries can be combined in a conversation without pretending all of the source's sample statements are verified quotations from those authors.

Examine all three main dialogue examples

In the Voss example, the buyer asks to reduce $6,750 to $5,500. The reply acknowledges the concern, discusses a twelve-week licensing-portfolio engagement and offers an alternative if the timing is wrong. Preserve that structure, but do not repeat “most clients” outcome claims without evidence.

In the Enns example, a beginner asks for a discount. The reply treats the decision as fit and offers an alternative. Its assertion that most senior illustrators license within six months and quickly recover the investment is unsupported here. Replace that assertion in an actual sales script with the offer's documented deliverables and substantiated evidence.

In the Stark example, the buyer asks why twelve weeks of coaching costs $6,750. The reply distinguishes the delivery window from the value sought. The asserted first licensing project in six to nine months and payback within twelve to eighteen months are not verified outcomes. They also sit uneasily with the later anti-promise that licensing results are not guaranteed. Teach that conflict explicitly and retain the unaltered examples in the source appendix.

An authored alternative is: “The engagement provides the agreed portfolio infrastructure over twelve weeks. It does not guarantee a licensing sale. The price and scope are fixed under the terms we reviewed; if the fit or timing is wrong, we can discuss an actual alternative.” Adapt this to the real offer rather than treating it as an adopted RISER sales claim.

Work through Maya's policy and arithmetic

Maya's list has four entries but only three active exceptions: pilot is N/A because her pilot ended in the C4–C6 cycle. Returning customers receive 15% off a second engagement booked within ninety days of completion, with prior outcome documentation. At $6,750 that payment is $5,737.50. One annual scholarship provides 40% off for the stated eligible senior illustrator, using an application and operator review; the payment is $4,050.

The partner example gives 15% off through three designated agencies plus a 15% commission. The source says Maya retains 70% of base, or $4,725. That calculation assumes both deductions are calculated on the original $6,750. If commission is instead 15% of the discounted payment, the retained amount is $4,876.875 before rounding and other costs. Specify the basis and costs before asserting sustainable margin.

Maya's eight responses correspond to the eight situations above. The first addresses the $6,750 concern; the second compares a $4,500 competitor; the third offers a thirty-minute clarification call. The fourth rejects six- or twelve-payment requests in favor of $6,413 pay-in-full or three $2,250 monthly payments. Those installments total $6,750, while pay-in-full is about 5% lower: exact 5% off would be $6,412.50. This standing payment term must be reconciled with the anti-discount policy, not hidden by calling all concessions forbidden.

The fifth response checks a special situation against the exception list. The sixth declines a two-friend discount while mentioning the actual partner path. The seventh acknowledges hardship and suggests a book; the source contains a placeholder, not a specific book recommendation. The eighth holds price on the last-day request, but its claim that twelve weeks “will deliver” regardless of enrollment date is too absolute without actual availability and scope evidence.

Maya's C4 alignment says the Sprint provides structural infrastructure for pursuing licensing, not licensing outcomes. Retain that boundary when adapting every script. Her example clause commits to no pressure-based price cuts, improvised payment plans or competitor matching; M8.4 remains the baseline and deviations use only approved exceptions. It acknowledges possible lost prospects as a tradeoff. The example's signature is not the learner's signature or a new corporate policy.

Assemble the seven-section learner document

  1. Purpose and C4 alignment, 100–150 words: connect this pricing policy to M4.5 exclusions and M4.6 guarantees.
  2. Exception list, 300–400 words: typically two to four exceptions with all six required fields.
  3. Non-exceptions and responses, 300–450 words: typically six to ten situations with the request, pattern and script.
  4. Pattern references, 100–200 words: explain how Voss, Enns and Stark patterns are used; copying scripts alone does not demonstrate understanding.
  5. Tier-specific variations, 100–200 words where applicable: reconcile M8.5 tiers, such as scholarships only on an entry tier or referrals across tiers. For flat pricing, explain the uniform policy briefly.
  6. Race-to-the-Bottom recognition, 100–150 words: identify a concrete tendency and observable warning signs after reading the case. Do not pretend a case was read merely because its title is present.
  7. Quarterly review, 100–150 words: state the next review date, triggers for an earlier revision and the data to examine.

Add the actual signed behavioral commitment. The section ranges total 1,100–1,800 words before that clause, while the overall target is 1,200–1,800. Budget the content and signature accordingly; do not omit requirements to satisfy a mechanical word count. Resolve the tier decision if M8.5 is still in progress.

Check the seven named failure modes and four deliverables

Look for an aspirational policy under 1,200 words or missing either list; too many exceptions; non-exceptions without scripts; disguised concessions within refusal scripts; missing C4 alignment; missing case recognition; and a vague commitment that names no behaviors. Address the actual weakness, not just the reviewer's preferred wording.

The source checkpoint has four items: the filed policy; exception entries in `c8_anti_discount_policies.exceptions`; non-exception entries in `.non_exceptions`; and the signed, filed clause. Its five rubric properties are explicit lists, all three pattern libraries, C4 alignment, operator-specific case recognition and specific behavioral commitments, with a target of at least 7/10. It does not define numerical weights in the main lesson.

The linked reviewer conflicts with that simplified standard: it uses different section contents, quantified walk-rate tolerance, forty-eight-hour interaction logging, a twelve-month commitment and final clearance at an average of at least 8 with no criterion below 6. Its introduction gives a different threshold. Preserve and reconcile both source structures through explicit cross-references; do not claim an invented uniform rubric. Consult the accompanying reviewer explanation and original for those additional requirements.

M8.7 uses the policy with the M8.4 architecture when scheduling raises. Compare actual realized prices, costs and sales rather than assuming a posted increase always raises revenue. This script does not file database records, sign a clause, invoke a model or advance enrollment.

RISER application and clickable resources

An authored Brunson/ClickFunnels application keeps the customer's path and offer terms clear while offering real alternatives for a different readiness or budget. An authored Hormozi/Acquisition.com application connects value and delivery evidence to sustainable economics without inflating guarantees or stuffing scope. Neither theme requires dismissing a buyer's constraints or assuming that a higher price proves a better offer.

- Assigned M8.6 written lesson — original main document, April 25, 2026, version 2.0. - Anti-Discount Language Swipe File — ten response categories; reviewed original preserved. - Race-to-the-Bottom failure case — composite case; reviewed with separate arithmetic and logic corrections. - Recognition checklist — fifteen indicators and recovery framework; reviewed original preserved. - Pricing-pressure conversation scripts — seven full dialogues; useful supporting asset, not yet proven identical to the named missing Scripts Template. - Anti-discount policy reviewer — original YAML; read as source material, not executed. - Black Swan Group: negotiation terminology — primary definitions of labels, mirrors, calibrated questions, accusation audits and tactical empathy. This public article is separate from the complete Never Split the Difference book. - Pricing Creativity — official Win Without Pitching book page — public reference identifying Blair Enns's book. The indexed page was available during review, while direct text extraction returned no body; the complete book was not reviewed. - Jonathan Stark's official books and resources — the author lists Hourly Billing Is Nuts here. This verifies a resource destination, not the source's claimed publication year, quoted scripts or customer results; the complete book was not reviewed. - RISER NATION CORP — brand destination.

Build 6, the Build 8 Drive folder, Supabase table, named Sonnet reviewer and scripts template are source dependencies, not evidence of working deployed infrastructure. Bring your actual M8.4/M8.5/M4.5/M4.6 records to the exercise. The exact named scripts-template identity remains unresolved; the related conversation scripts are not a confirmed replacement. Read the supporting lessons and their complete originals alongside this main explanation.

Assigned source: D0470 original 1

D0470 — complete original source

D0470 — complete original source

Open source file · Download exact original file

# M8.6 — Anti-Discount Policy and Price Defense

**Module Outcome:** [Apply] Student has constructed an anti-discount policy with explicit exception conditions and explicit non-exception conditions; produced pricing-pressure scripts using Voss tactical empathy patterns, Enns positioning patterns, and Stark value-language patterns; signed the Anti-Discount Discipline Clause; produced the Anti-Discount Policy that integrates with M8.4 architecture and routes pricing-pressure conversations through documented response paths.
**Key Deliverable:** Anti-Discount Policy (`Anti-Discount-Policy-[YourName]-[Date].md`, 1,200-1,800 words, seven sections + signed clause)
**Infrastructure Dependency:** Build 6, Build 8 Drive folder, Supabase `c8_anti_discount_policies` table, Claude prompt `anti-discount-policy-reviewer-v1.0.0` (Sonnet), Anti-Discount Language Swipe File, Pricing-Pressure Scripts Template
**Checkpoint / Test:** Type 1 Artifact + Type 2 AI rubric ≥ 7/10
**Blocked-Until Prerequisite:** M8.4 Pricing Architecture Document filed AND AI rubric ≥ 7/10 (M8.6 can run parallel with M8.5)

---

## What This Module Does

M8.6 produces the operator's anti-discount policy. Five things happen:

1. You **construct the explicit exception list**: cohort early-bird, partner referrals, scholarship cases, and any other documented conditions where discounts are pre-approved. Each exception has approval thresholds and documented rationale.

2. You **construct the explicit non-exception list**: price negotiation, "I'll think about it" pressure, sob stories, comparable-competitor matching, and any other conditions where discounts are explicitly denied. Each non-exception has documented response patterns.

3. You **produce pricing-pressure scripts** using three pattern libraries: Voss tactical empathy ("It seems like the price is the obstacle"), Enns positioning ("Our work is priced for the structural value it produces; if that's not the right fit, here's a path that may serve you better"), and Stark value-language ("My pricing reflects what the engagement requires to deliver outcomes you can build on").

4. You **align the policy with C4 anti-promise and guarantee architecture**: the anti-discount policy is the pricing-side anti-promise (we will NOT negotiate base price under pressure), strengthened by but not duplicating C4 M4.5.

5. You **sign the Anti-Discount Discipline Clause**: a structured commitment to honor the policy under pressure, with named accountability mechanisms.

The deliverable is the **Anti-Discount Policy** — 1,200-1,800 words, seven sections + signed clause. The policy is the input to M8.7 (raise schedule, which assumes anti-discount holds price as the precondition for raising it) and to M8.8 (capstone synthesis).

M8.6 is 4 hours of active work distributed across two sittings.

---

## Why This Module Matters

Anti-discount policy is the pricing dimension of operator self-respect. The doctrine introduced in M8.1 — Pricing Is Operator Self-Respect — becomes operational here. Without an anti-discount policy, the M8.4 base price is theoretical; in practice, it is the price the operator charges when no pressure is present and the price the operator quietly lowers when pressure appears. Over 12 months, the lowered prices become the actual prices, and the M8.4 architecture is fiction.

The discipline has three structural advantages:

1. **Pre-decision frees the operator from in-conversation negotiation.** When a prospect raises a price objection, the operator's response is pre-decided. The operator is not making a choice in real time under social pressure; they are reading from a documented policy.

2. **Customer experience improves through consistency.** Prospects who do not receive a discount and prospects who do receive an exception-based discount both experience a coherent process. Ad-hoc discount granting produces the worst customer experience: the prospect who got the discount feels lucky-but-uncertain; the prospect who didn't feels arbitrarily denied.

3. **Margin protection compounds.** A 10% discount granted ad-hoc under pressure to one customer per month, over 12 months, is 12 customer-engagements at 10% reduced revenue. At Maya's $6,750 base × 10% × 12 = $8,100 surrendered annually. The anti-discount policy holds the line and protects the surrendered amount.

The reverse of these advantages is the Race-to-the-Bottom Trap (the C8 failure case study): operators who respond to pricing pressure by lowering prices experience the cumulative effect of many small concessions, eventually arriving at a price below sustainable margin. Quality degrades. Refunds increase. The operator lowers prices further to stop refunds. The mechanism collapses. The trap is documented in `07_Case-Studies-and-Examples/Race-to-the-Bottom-Trap.md`.

The anti-discount policy is the structural defense against the trap.

---

## The Two Lists

The anti-discount policy is built around two explicit lists.

### List 1 — Explicit Exception Conditions (Pre-Approved Discounts)

These are the conditions under which discounts are offered. The list is finite, structurally justified, and operationally enforced.

**Common legitimate exceptions:**

**Cohort Early-Bird Discount.** Applies only to time-bound cohort enrollment (Darius's Reading Club, but not Maya's 1:1 Sprint). Discount typically 10-20%. Rationale: cash-flow-forward, conversion-de-risking. Approval threshold: discount is automatic for any prospect who enrolls before the cohort start date specified.

**Partner / Affiliate Discount.** Applies when a customer arrives through a designated partner channel. Discount typically 10-20%, with the partner taking a 10-25% commission. Rationale: customer-acquisition-cost reduction. Approval threshold: partner must be on the documented partner list; commission and discount math must produce sustainable margin.

**Scholarship / Need-Based Discount.** Applies to documented need cases (often financial hardship with documentation, mission-aligned access for underrepresented populations). Discount typically 30-50%, capped at a defined number per cohort/year. Rationale: portfolio-builder, mission alignment, operator identity. Approval threshold: documented need + operator commitment to defined number of scholarships.

**Returning Customer Continuation Discount.** Applies only when a customer who completed a previous engagement enrolls in a follow-up engagement within a defined window. Discount typically 10-15%. Rationale: continuity of customer relationship, customer-lifetime-value optimization. Approval threshold: previous engagement complete with positive outcome documentation.

**Pre-Launch / Pilot Discount.** Applies during the first 1-3 cohorts of a new offer or significant offer iteration. Discount typically 20-40%. Rationale: testimonial collection, iteration data. Approval threshold: defined pilot duration with hard sunset date.

For each exception, document:
- Exception name
- Discount percentage or amount
- Eligibility conditions (who qualifies)
- Approval mechanism (automatic, application-based, operator-discretion within threshold)
- Documentation requirement (what evidence must be on file)
- Quarterly review cadence (when does the operator review whether the exception still applies)

**Important:** the exception list is short. Operators with 8+ exception types are likely treating exceptions as the rule. Most legitimate policies have 2-4 exceptions.

### List 2 — Explicit Non-Exception Conditions (Discounts Denied)

These are the conditions under which discounts are explicitly denied. Pricing-pressure scripts are constructed for each condition.

**Common non-exceptions:**

**"The price is more than I can afford."** Response pattern: acknowledge the budget constraint, recommend an alternative path (self-paced books, lower-cost courses, community resources, future-engagement when budget improves). Voss-style tactical empathy ("It sounds like the timing isn't right financially") + Enns-style positioning ("Our work is priced for the structural value it produces; if that's not the right fit, here's a path that may serve you better").

**"Your competitor charges less."** Response pattern: do not match the competitor's price. Acknowledge the comparison, briefly differentiate the structural value (without disparaging the competitor), and accept that the prospect may choose the competitor. Stark-style value-language ("My pricing reflects what the engagement requires to deliver outcomes you can build on; if [competitor]'s structure fits your situation better, that's a legitimate choice").

**"I'll think about it."** Response pattern: do not offer a discount to close the deal. The prospect's hesitation is information, not an objection to be overcome with price reduction. Voss-style tactical empathy ("It sounds like there's something you need to work through before deciding"). Optional follow-up: offer a structured next step (e.g., a 30-minute clarification call if the prospect can articulate what they need to think through).

**"Can you do a custom payment plan?"** Response pattern: refer to the documented payment terms from M8.4. If the prospect's request fits the documented installment structure, accept; if not, decline. Do not invent custom payment plans in real time.

**"My situation is special."** Response pattern: acknowledge the specificity, but do not reflexively grant exceptions. Refer to the documented exception list. If the prospect's situation matches an exception, apply it; if not, decline.

**"I'll get a friend to enroll if you discount us both."** Response pattern: refer to the partner / referral exception (if exists) or decline. Do not create ad-hoc bundle discounts.

**Sob stories / hardship narratives without documentation.** Response pattern: empathy + decline + alternative-resource suggestion. Voss-style tactical empathy is critical here ("That sounds genuinely difficult"). Do not grant discounts on undocumented hardship — refer to the scholarship exception (with documentation required) or to alternative resources.

**End-of-cohort / urgency-driven asks.** Response pattern: hold the price. Urgency is not an exception. The prospect's late timing is information, not pressure to be relieved with a discount.

For each non-exception, document the response pattern with a script template that the operator can adapt to the specific conversation.

---

## The Three Script Pattern Libraries

Pricing-pressure scripts draw from three pattern libraries:

### Voss Tactical Empathy (Never Split the Difference, 2016)

Chris Voss's tactical empathy patterns work in pricing conversations because they validate the prospect's experience without conceding the substantive ask. Key patterns:

- **Labels:** "It sounds like..." / "It seems like..." — name the emotional experience without judgment.
- **Mirroring:** repeat the last 2-3 words the prospect said with rising inflection. Forces them to elaborate without operator concession.
- **Calibrated questions:** "How am I supposed to do that?" — acknowledge difficulty, return responsibility to prospect.
- **Accusation audit:** name the prospect's likely concern before they articulate it. "You're probably wondering whether the price reflects real value, and that's a fair question."

**Example application:**

> Prospect: "$6,750 is a lot. Can you do $5,500?"
> Operator (Voss): "It sounds like the price feels high for what you're seeing right now. Here's what I'd say — the engagement's structural value comes from the licensing-portfolio outcomes most clients build during the 12 weeks; if that outcome would change your career arc, the pricing reflects that reality. If the timing isn't right financially, I get it, and I can point you to some self-paced resources that may serve you in the interim."

### Enns Positioning (Pricing Creativity / Win Without Pitching)

Blair Enns's positioning patterns reframe pricing conversations from negotiation to fit assessment. Key patterns:

- **Reframing as fit:** "Our work is priced for the structural value it produces; if that value matches your situation, this is a fit; if not, that's information."
- **Authoritative composure:** the operator does not defend the price — they describe what the price reflects.
- **Walking-away credibility:** the operator is genuinely willing for the prospect to choose not to engage. This is not bluffing; it is operational discipline.

**Example application:**

> Prospect: "Can you discount it for me? I'm just starting out."
> Operator (Enns): "I appreciate the directness. The Sprint is priced for the structural value it produces — most senior illustrators who complete it are licensing within 6 months at rates that recover the investment quickly. That structural reality means the pricing isn't really negotiable; if the timing isn't right, that's legitimate, and I'd suggest [alternative resource] as a starting point."

### Stark Value-Language (Hourly Billing Is Nuts, 2017)

Jonathan Stark's value-language patterns connect pricing to outcomes rather than to time or scope. Key patterns:

- **Outcome-anchored framing:** "Pricing reflects what the engagement requires to deliver [specific outcome]."
- **Investment language:** "This is an investment in [structural change]; the return tends to be [evidence-based pattern]."
- **Time-displacement framing:** "The work is priced for the outcome it produces, not for the hours it consumes."

**Example application:**

> Prospect: "How is it $6,750 for 12 weeks of coaching?"
> Operator (Stark): "The pricing isn't really for the 12 weeks — it's for the licensing-portfolio outcome most senior illustrators build during the engagement. Clients who complete typically license their first major project within 6-9 months and recover the investment within 12-18. The 12 weeks is the delivery window; the pricing reflects what the outcome is worth."

The three libraries are complementary, not contradictory. Most pricing-pressure conversations draw from all three across the conversation flow.

---

## Worked Example: Maya's Anti-Discount Policy

Maya's M8.6 work:

**Exception list (4 items):**
1. **Pre-launch / pilot discount:** N/A — Maya is past her pilot phase; her pilot was the C4-C5-C6 cycle.
2. **Returning customer continuation:** 15% off any second engagement booked within 90 days of first engagement completion. Approval automatic. Documentation requirement: prior engagement complete with documented outcome.
3. **Scholarship:** 1 scholarship per year at 40% off, for a senior illustrator from underrepresented background with documented financial need. Application-based with operator review.
4. **Partner referral:** 15% off for prospects referred by Maya's three designated partner agencies, who take a 15% commission. Net to Maya at 70% of base price ($4,725) — still produces sustainable margin.

**Non-exception list with scripts (8 items):**

1. **"$6,750 is a lot."** Voss + Enns hybrid script (above).
2. **"Your competitor charges $4,500."** Stark + Enns hybrid: "My pricing reflects the structural outcome the Sprint produces. If [competitor]'s engagement structure fits your situation better, that's a legitimate choice."
3. **"I'll think about it."** Voss tactical empathy: "It sounds like there's something you need to work through. Want to schedule a 30-minute clarification call to surface what's holding the decision?"
4. **"Can you do a 6-pay or 12-pay plan?"** M8.4 reference: "I offer pay-in-full at $6,413 or 3-pay at $2,250/month. I don't offer extended plans because the structure produces friction late in the engagement."
5. **"My situation is special."** Voss + exception list: "Tell me what you mean — if your situation matches one of my documented exceptions [list], we can talk about that. If not, the pricing holds."
6. **"My friend and I will both enroll if you discount us both."** Decline: "I appreciate the offer. My pricing doesn't accommodate group discounts, but I do have a partner-referral path if your friend wants to refer through [partner]."
7. **Sob story without documentation.** Voss empathy + decline + redirect: "That sounds genuinely difficult. The Sprint isn't the right entry path for that situation. I'd suggest [book recommendation] as a starting point and we can revisit when timing improves."
8. **"This is my last day to decide — can you do a deal?"** Decline: "Urgency doesn't change the pricing. If the Sprint is the right fit for your situation, the 12 weeks will deliver regardless of the enrollment date."

**C4 alignment:** Maya's anti-discount policy is consistent with her C4 M4.5 anti-promise (the Sprint does not promise licensing outcomes; it delivers structural infrastructure for the customer's licensing pursuit). The anti-discount policy extends this: the pricing reflects the structural infrastructure, not the outcome guarantee.

**Anti-Discount Discipline Clause signed.** Maya commits: I will not lower my price under prospect pressure. I will not invent ad-hoc payment plans. I will not match competitor prices. I will hold the M8.4 architecture as the pricing baseline, with deviations only through the documented exception list. I acknowledge this commitment will produce some lost prospects who would have converted at a lower price; I accept this as the cost of margin discipline.

Maya files the Anti-Discount Policy (~1,500 words). The policy is the input to M8.7 (raise schedule) and M8.8 (capstone).

---

## The Seven-Section Document Template

Your Anti-Discount Policy is 1,200-1,800 words, with seven sections + the signed clause:

### Section 1 — Policy Purpose and C4 Alignment (100-150 words)
State the policy's purpose. Reference C4 M4.5 anti-promise and M4.6 guarantee architecture. The anti-discount policy is the pricing-side extension; specify how.

### Section 2 — Exception List (300-400 words)
For each exception (typically 2-4): name, discount, eligibility, approval, documentation, quarterly review.

### Section 3 — Non-Exception List with Response Patterns (300-450 words)
For each non-exception (typically 6-10): the prospect's likely framing, the response pattern (which library), the script template.

### Section 4 — Voss/Enns/Stark Pattern References (100-200 words)
Brief explanation of how each library is used in your scripts. Operators who quote scripts without showing pattern awareness fail this section.

### Section 5 — Tier-Specific Variations (100-200 words, conditional)
If your M8.5 was tiered, specify how exceptions and non-exceptions differ across tiers (e.g., "scholarships apply only to entry tier; partner referrals apply to all tiers").
If M8.5 was flat, this section can be brief: "Flat pricing means uniform policy across customers."

### Section 6 — Race-to-the-Bottom Recognition (100-150 words)
Show that you have read the Race-to-the-Bottom Trap case study. State your recognition: which tendency in yourself maps to the trap pattern? How will you recognize the pattern when it appears in real time?

### Section 7 — Quarterly Review Commitment (100-150 words)
The policy is reviewed quarterly. State when the next review is, what triggers a between-review revision, and what data feeds the review.

### Anti-Discount Discipline Clause (signed)
A specific commitment to honor the policy. The clause names the behaviors the operator commits to and against.

---

## Common Failure Modes at M8.6

The Sonnet `anti-discount-policy-reviewer-v1.0.0` prompt and AI rubric look for these:

1. **Aspirational anti-discount policy.** Operator writes "I will hold price" without operationalized exception/non-exception lists or scripts. The AI rubric flags policies under 1,200 words or missing the two lists.

2. **Exception list too long.** Operator's exception list has 8+ items, indicating the operator is treating exceptions as the rule. Rubric flags any policy with more than 5 exceptions.

3. **Non-exception list without scripts.** Operator names what is denied but does not provide response patterns. Scripts are the operational mechanism; their absence makes the policy unusable in real-time conversations.

4. **Scripts that grant the discount in different framing.** Operator writes a "non-exception" response that, on close reading, offers a smaller discount or an alternative concession. The rubric checks for hidden concessions.

5. **No C4 alignment reference.** Operator's anti-discount policy reads independently of C4 M4.5 / M4.6. The rubric expects explicit reference and consistency.

6. **No Race-to-the-Bottom recognition.** Operator does not engage with the failure case study. The rubric flags omission.

7. **Vague discipline clause.** Operator's clause says "I commit to discipline" without naming specific behaviors. The rubric expects specific commitments.

---

## Checkpoint 8.6

Your deliverable is:
1. **Anti-Discount Policy** filed in Drive, 1,200-1,800 words, seven sections + signed clause
2. **Exception list** recorded in Supabase `c8_anti_discount_policies.exceptions`
3. **Non-exception list** recorded in `c8_anti_discount_policies.non_exceptions`
4. **Anti-Discount Discipline Clause** signed and filed

The AI rubric scoring the document looks for properties:
- Both lists explicit (exceptions and non-exceptions)
- Scripts using all three pattern libraries (Voss, Enns, Stark)
- C4 alignment referenced explicitly
- Race-to-the-Bottom recognition specific to operator's tendency
- Discipline clause with specific behavioral commitments

Target score: ≥ 7/10.

---

## What M8.7 Expects From You

M8.7 (price-raise schedule) reads from your M8.6 deliverable. The raise schedule assumes anti-discount policy holds price as the precondition for raising it. If anti-discount discipline fails, raises do not produce expected revenue increases (because effective prices fall back through unsanctioned discounts). M8.7's schedule operates against the M8.4 architecture and the M8.6 discipline together.

File the Anti-Discount Policy. Proceed to M8.7.

---

*Last updated: April 25, 2026 · Version 2.0*
Supporting instruction and original resources

Supporting lesson: build a fluent response to pricing pressure

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Source: Anti-Discount Language Swipe File. Use these response patterns with the anti-discount policy lesson. The accompanying original preserves the full swipe file for comparison.

Purpose: prepare the decision before the conversation

The swipe file supplies ten situations in which an operator may improvise a concession. Its teaching objective is fluency: knowing the actual price policy well enough to explain it naturally. It does not require you to copy a sentence that sounds unlike you. The written policy should determine the response, and the response should describe real options.

Before rehearsing, insert the actual scope, price, smaller offer and approved exception criteria. Remove any option that does not exist. A script cannot create a profitable smaller offer or a valid partnership arrangement by naming one. The source's claims about predictable operator behavior and practice saving hundreds of dollars are unverified generalizations; use practice as preparation and evaluate your own results.

1. A general request for a lower price

The first category offers three valid response directions. You can state the fixed price and offer to explain the included scope. You can retain the price for the current scope while presenting an actual smaller offer. Or you can explain that you cannot sustainably deliver the requested engagement for less and accept that the customer may decline.

The practical distinction is between explaining an offer and reopening its price. A concise authored response is: “That is the price for the scope we discussed. I can clarify what is included, or we can look at the smaller engagement if that would fit better.” If there is no smaller engagement, omit that sentence. If your documented policy permits an exception, do not falsely say there is no flexibility under any circumstances.

2. Startup, nonprofit and small-team requests

The source gives three approaches: explain the relationship between price and delivery cost; state that there is no general startup rate; or route an eligible nonprofit through a documented partnership pathway. Organizational status alone does not automatically satisfy a policy exception.

Explain your actual reason. The source says costs do not change with customer stage, but that is not universally true: differences in scope or required support can change costs. Say what applies to your offer, without claiming that every startup or nonprofit costs the same to serve. For a nonprofit pathway, state eligibility, the approved terms and how the decision is documented. Do not invent a special partnership while under pressure.

3. A lower competitor quote

Three replies in the source emphasize your own delivery economics, a direct comparison of scope and quality, and a brief value explanation that leaves the customer free to choose another provider. Work through the comparison rather than declaring that every competing offer is incomparable.

Ask whether scope, deliverables, support, quality requirements and capacity commitments are genuinely equivalent. If they are different, describe the differences you can substantiate. If you do not know, say so. A lower quote does not establish that the competitor cuts quality, and your higher price does not prove greater value. A useful response can end by respecting the customer's decision if the other option fits better.

4. Founder and first-customer pricing

The source distinguishes declining general founder pricing from offering a genuine beta pathway. Its example beta is limited to the first three customers, with documented feedback expectations and constraints. The main D0470 lesson uses a different example involving the first one to three cohorts. Preserve both examples and resolve which approved policy applies; three customers and three cohorts are not interchangeable.

Early customers may require extra scoping and iteration, but the source's claim that they always cost more is not established. Assess the actual offer. If a beta is real, explain what is experimental, what feedback is expected, who qualifies and when eligibility closes. Do not rename a routine sale a beta merely to justify a discount.

5. Friends and referrals

Both supplied responses acknowledge the relationship and maintain the ordinary rate. One focuses on being able to deliver well; the other thanks the mutual contact and offers the same scope explanation available to any customer. The lesson is consistency and clarity, not the claim that discounted work inevitably causes resentment or damages friendships.

An authored version is: “Thank you for the introduction. My rate for this engagement is [price], including [scope]. I use that rate consistently so I can plan and deliver the work properly.” A referral is welcome context, but it only triggers different terms when an actual documented referral policy says it does.

6. Renewal at a previous rate

The first renewal response distinguishes the old engagement from a new engagement and states the new price. Its reference to 60 days' notice is explicitly conditional: use it only if that notice was actually given. The second response allows an approved loyalty rate when specified eligibility conditions are met.

Check the existing commitment before speaking. A script about new pricing is not authority to change already-promised terms. State which engagement the quoted rate applies to, explain any valid loyalty condition and give the customer clear choices. Do not retroactively claim notice or imply that a loyalty policy exists when it does not.

7. Removing a deliverable

The source explains that setup, scoping and integration costs may remain when one visible deliverable is removed. Therefore, a smaller deliverable list does not necessarily justify a proportional price cut. Its second response argues that some bundles produce an outcome only when their components work together.

Test those claims for your offer. Some components can be removed without harming the result; others cannot. Explain the dependencies and measure the remaining work. If a smaller engagement can stand on its own, define and price it coherently. Do not dismiss every scope-reduction request as manipulation or claim that every bundle is indivisible.

8. Silence after the price

Allow the customer time to process. The source suggests an optional question after more than ten seconds if the silence becomes uncomfortable. That is a conversational cue, not a scientifically established timer or a pressure technique.

You can ask what questions the customer has about the price or scope. Listen to the answer. Avoid supplying a discount simply to end your own discomfort, but also avoid treating silence as agreement or as proof of a particular objection.

9. The reflex to promise unspecified flexibility

The phrase “let me see what I can do” can imply that a concession is available even when you have no policy basis for one. Replace vague flexibility with an accurate explanation. If the price is fixed for the scope, state that. If eligibility needs checking, name the actual policy you will check without promising approval.

The skill is precision. You are not required to sound harsh, and firmness does not justify hiding a legitimate option. Practice an explanation that is both direct and true.

10. The moment before an off-policy concession

The source asks three internal questions: does the request fit the exception list; if it does, is the amount within the prescribed magnitude; and if it does not, are you granting it because of pressure rather than policy? It then recommends explicitly recognizing that a deviation would be auditable.

Use this pause to identify the actual decision. If an exception applies, record its basis and use its approved terms. If you depart from policy, document what happened accurately rather than relabeling it after the fact. Review the result without treating a mistake as a judgment of personal worth.

Practice and framework connection

Rehearse all ten situations aloud, replacing placeholders with actual terms. Ask a practice partner to vary the wording so you learn the decision rather than memorize a line. Keep the three real routes visible where applicable: the existing offer, a coherent smaller offer, or declining to proceed.

As an authored Brunson-oriented application, connect the offer explanation to the need established earlier in the conversation. As an authored Hormozi-oriented application, make the outcome, scope and supporting evidence clear enough for the customer to judge the value. Neither application requires invented urgency, an unsupported saving or a guaranteed result.

The completion check is practical: every response matches the written policy, every alternative exists, each exception has criteria and limits, and the customer can understand the choice without pressure. Keep the full original swipe file available for comparison with these explanations.

D0495 — complete original source

D0470-linked-D0495 — complete original source

Open source file · Download exact original file

# Anti-Discount Language Swipe File

**Used in:** M8.6 script-building, live customer interactions · **Customize for your voice; do not use verbatim if it doesn't sound like you**

---

## Purpose

Pre-written language reduces under-pressure improvisation. Operators who improvise pricing responses tend to improvise toward concession. Operators who reference pre-written scripts tend to hold the line.

These are templates. Adapt to your voice. The goal is fluency, not memorization. Practice aloud at M8.6.

---

## Category 1 — "Can you do anything on the price?"

The general pricing-pressure opener. Customer is testing whether discount is available.

**Response A (declarative, no negotiation invitation):**
> *The price I quoted is the price I charge for this work. I'm happy to walk you through what's included if that would help, but the price itself isn't variable.*

**Response B (declarative, alternative scope offered):**
> *I don't reduce the price for this scope. If you're looking for a smaller engagement, I have [smaller offer] at [smaller price]; that's a different offer for a different scope, not a discount on this one.*

**Response C (declarative, walk-away normalized):**
> *The price reflects what it costs me to deliver at the quality this offer commits to. I understand if it's not the right fit at this point, and I'd rather we both walk away than start with a price I can't sustain.*

---

## Category 2 — "We're a startup / nonprofit / small team"

Customer signals limited budget through organizational status.

**Response A:**
> *I appreciate you sharing context. My pricing reflects what it costs me to deliver, which doesn't change based on the customer's stage. If the price isn't workable right now, the offer is here when budget is workable.*

**Response B:**
> *I don't have startup pricing. The reason is that my cost of delivery doesn't change based on customer stage, and pricing that doesn't reflect cost isn't sustainable. I'd rather work with fewer customers at sustainable pricing than more customers at a price that erodes my capacity.*

**Response C (for genuine nonprofits):**
> *I do partner with nonprofits, but through a partnership-account pathway, not through ad-hoc discounting. If your organization fits my partnership criteria — [specify your criteria] — I can route you there. Otherwise standard pricing applies.*

---

## Category 3 — "This other vendor / quote is at $X"

Customer presents a competing quote as anchor.

**Response A:**
> *I don't price against other quotes. I price against what it costs me to deliver this work at the quality I commit to. If the other option is the right fit at that price, that's a reasonable choice, and I understand.*

**Response B:**
> *Other quotes reflect other operators' cost structures and offer scopes, which aren't comparable to mine. I'd be careful comparing prices without comparing scope, deliverable quality, and operator capacity. Happy to walk you through my scope if that's useful.*

**Response C (when curious about competitive context):**
> *That's helpful context — thanks for sharing. I'd note that comparing prices across operators usually requires comparing scope and quality side-by-side; price alone isn't a complete comparison. My price reflects [brief value statement]. If a different operator's offer is the right fit, I support you choosing it.*

---

## Category 4 — "Founder pricing / first-customer pricing"

Customer asks for early-relationship discount.

**Response A:**
> *I don't have founder pricing. The reason is that early customers cost me more to serve, not less — there's more scoping work, more iteration, more learning curve. If anything, pricing for first customers should be higher; I keep it at standard pricing because I don't want to penalize early adopters.*

**Response B (for genuine beta context):**
> *I do have a beta pathway for [specific genuinely-novel offer], but it's structurally bounded — first 3 customers, with documented feedback expectations and constraints. The standard offer doesn't have founder pricing.*

---

## Category 5 — "Friend pricing / referral pricing"

Personal relationship pressure.

**Response A:**
> *I don't have friend pricing. My pricing reflects what it costs me to deliver, which doesn't change based on my relationship to the buyer. I'd rather charge you full price and deliver well than discount and resent it. The relationship lasts longer that way.*

**Response B:**
> *[Mutual contact] is great. I'd be glad to work with you, and the rate is the same as for everyone — that's the discipline that lets me sustain the relationship with [mutual contact] and others. Happy to walk you through the offer at standard pricing.*

---

## Category 6 — "Last year you charged $X; we're renewing at that"

Existing customer claiming legacy rate.

**Response A:**
> *Pricing has updated since [last engagement date]. The current rate is $[new]. Your previous engagement at $[old] honored that pricing for that engagement; this new engagement is at current pricing. I gave you 60 days notice on the change [if applicable]; I want to make sure that lands clearly.*

**Response B:**
> *I appreciate the relationship and the loyalty. The current rate is $[new]. If you meet the loyalty conditions [specify], a structural loyalty discount of [X]% applies, bringing it to $[X]. Outside those conditions, standard current pricing applies.*

---

## Category 7 — "Just remove this deliverable to lower the price"

Scope-reduction request as discount mechanism.

**Response A:**
> *Removing the deliverable doesn't reduce the price proportionally because the deliverable's cost to me isn't a fixed line item — there's setup, scoping, and integration work that doesn't scale down linearly. If you want a smaller engagement, I have [smaller offer] which is built for smaller scope at smaller price.*

**Response B:**
> *I scope my offers as bundles because the bundle is what produces the outcome. Removing pieces of the bundle doesn't produce a smaller version of the outcome; it produces an incomplete version. I'd rather offer you the right-sized offer for your need than a partial version of this one.*

---

## Category 8 — Silence

After stating the price, the customer is silent. Operators tend to fill the silence with justification.

**Response (intentional):**
> *[Wait. Don't fill the silence. The customer is processing. Operators who fill silence with justification weaken the price; operators who allow silence let the customer arrive at their own decision.]*

If the customer is silent for > 10 seconds and the silence becomes uncomfortable, prompt for response:
> *What's coming up for you on the price?*

This redirects the silence to the customer rather than into operator-justification.

---

## Category 9 — Reflexive "Let me see what I can do"

The dangerous operator response. When you hear yourself starting to say "let me see what I can do" in response to pricing pressure, **stop**. That phrase is the entry point to discount-rationalization.

**Replacement (declarative):**
> *The price is the price. I want to be straightforward rather than create the impression that there's flexibility I haven't already exercised.*

This is the hardest replacement. It requires unlearning a customer-service reflex. Practice it aloud until it sounds natural.

---

## Category 10 — When You're About to Cave

Sometimes you'll feel yourself folding mid-conversation. The customer is sympathetic, the budget conversation is genuine, you want to help. Before granting the discount, ask yourself:

1. Does this fit the M8.6 exception list?
2. If yes, is the discount at the structural magnitude?
3. If no, am I about to grant a discount because of pressure, not policy?

If question 3 is yes, the discipline statement to yourself is:

> *This isn't a policy exception; this is pressure. I'm about to deviate from my Attestation. I'll log this if I do it. The deviation is auditable.*

Often, articulating the deviation explicitly (even in your own head) is enough to hold the line. The Attestation's function is exactly this: making the deviation visible enough that you decline to make it.

---

*Practice these aloud. The fluency matters. The customer reads operator confidence; confidence requires fluency; fluency requires practice. Fifteen minutes of practice at M8.6 saves hundreds of dollars in unnecessary discounts over the next 12 months.*

Supporting case: reconcile pricing, capacity and policy across an entire offer

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Source: Jordan Vasquez composite pricing case. This supplement supports D0470 in 03.1, 05.4, 07.1, 12.2 and 12.4. Preserve the full original narrative and figures in the appendix.

Read the case as a composite

The source explicitly combines patterns attributed to cohorts 03, 04 and 06 into Jordan's story. It is not verified customer testimony. Its April 26, 2026 version 2.0 follows a Stage 2 operator through legacy modules M8.1–M8.8. Those module references describe the source's sequence, not a replacement for the twelve-course assignment map.

The central question is whether individually approved artifacts form one coherent business model. A price, tier, discount policy and capacity plan can each look plausible while contradicting each other. We will examine the entire sequence, including the source's arithmetic and logical errors, rather than assume that every reviewer conclusion is correct.

Entry conditions and M8.1: inspect behavior and assumptions

Jordan enters at month nine, having completed C1–C7, with C7 completed nine weeks earlier. The Brand Foundations Sprint v1 costs $1,800, lasts three weeks and includes an audit, positioning, visual direction and one revision. The narrative reports a $42 effective hourly rate against a $95 aspiration, 14 available hours weekly against 22–26 actually worked, 36 hours per Sprint and eight sustainable annual deliveries. It describes eleven customers over six months, referrals and three inquiries emphasizing a cheap brand service.

Jordan initially interprets the problem as personal slowness rather than price. Treat this as a belief to test. M8.1 records no price increase, five discounts—three 20% friend/referral concessions, one 15% website bundle and one 25% concession for a desired brand—36 hours against a 24-hour estimate, and a free 30-minute call expanding to 90 minutes with effectively unlimited revisions. The source says three of four tests failed without fully defining the scoring.

The reviewer asks for attention to the Anchor Loop and Pricing Pivot Smuggle patterns, and a second submission clears. Adding reviewer vocabulary is not the same as correcting the underlying model. Ask what changed in the measured scope, price or decision policy.

M8.2: reconcile the economics before interpreting them

The case reports a 65-minute audit against a suggested 90–120 minutes. Fast completion does not prove evasion. The evidence is the quality and consistency of the work.

It moves from 24 stated delivery hours to 28 measured hours plus eight hidden-hour entries. Those entries are 2, 1.5, 1.5, 1.5, 0.5, 0.5, 0.5 and 0.5 hours. They total 8.5, although the source says 8. The resulting total would be 36.5, whereas later calculations use 36. Preserve both and identify the reconciliation needed.

The source's $75,000 target divided by 1,200 hours gives $62.50 per hour. Using its later 36-hour assumption gives $2,250 delivery cost and a $450 loss against the $1,800 price. That is a negative 25% margin when divided by revenue. However, $1,800 divided by 36 is $50 per delivery hour, not $42. The $42 figure needs another documented denominator or cost basis; do not invent one.

The annual illustration uses eighteen deliveries, $32,400 revenue, 648 delivery hours and 280 other hours, totaling 928. Revenue per total hour is approximately $34.91. That is 55.86% of the $62.50 target, or 44.14% below it, not 56% below. The annual revenue gap to $75,000 is $42,600. Revenue is not automatically net compensation.

Capacity assumptions also require reconciliation. Eighteen deliveries are 2.25 times eight, and $32,400 is 43.2% of $75,000. But eleven customers in six months annualize to twenty-two, not eighteen. Fourteen weekly hours and 36 hours per delivery do not alone establish eight annual deliveries; working weeks and other constraints are missing. The 1,200-hour assumption also needs an explanation relative to 14 weekly hours. The narrative records clearance with a framing concern and 24-hour cooling, but clearance does not erase these unresolved inputs.

M8.3: test all four branches with evidence

The case considers whether the price covers cost and target margin, whether cost can be reduced, whether an unreducible cost requires a different decision, and whether demand is elastic. Jordan rejects the first branch and proposes lowering delivery from 36 to 28 hours, producing $1,750 cost at $62.50. That is roughly a 22% time reduction over a proposed 90-day period.

The source contrasts that hope with delivery allegedly stable at 36 plus or minus four hours across eleven projects over fourteen months. That window conflicts with the earlier six-month sample. Reconcile the observations before using them as evidence against improvement. An efficiency plan needs specific changes, measurements, a deadline and a fallback; neither optimism nor a reviewer's skepticism proves the outcome.

The revised proposal is 30–32 hours at a $2,000 price. At 30 hours, the stated rate produces $1,875 cost and $125 remaining. At 32 hours, cost is $2,000 and nothing remains. A range therefore matters; its favorable endpoint cannot stand in for the entire plan. Claimed demand elasticity needs evidence too. The source records second clearance and a missed concern, illustrating that a review can be incomplete.

M8.4: connect price to scope, capacity and terms

Jordan's architecture sets $2,000, half paid upfront and half at delivery, with the source's example refund terms: within seven days if no work has begun, prorated up to 50% afterward, and no final-week refund. These are narrative terms, not adopted RISER terms or a model of what any particular business must offer.

There is no segmentation, and high-volume/low-margin operation is described as market entry without clear time or capacity boundaries. Ask what ends the transition, how workload is limited and what measured efficiency supports the price. The narrative's 48-hour cooling period is a workflow event; it does not validate the economics. At $2,000 revenue and $2,250 cost, margin is negative 12.5%. The approximately negative 11.11% figure divides the shortfall by cost rather than revenue.

M8.5: evaluate each tier on its own scope and cost

The proposed tiers are a $1,500 audit/positioning offer with one revision, the $2,000 current offer and a $3,200 expanded visual offer with two revisions. The diagnostic questions concern customer segments, deliverable differences, profitability and whether the tiers create real choices rather than disguised concessions.

The source anticipates a lower sales mix around $1,750–$1,850 without providing supporting demand data. Its Starter price is revised to $1,750 and then $1,950 before a third clearance. These are concerns to investigate, not proven outcomes. A smaller tier needs its own measured cost: the full-scope $2,250 cost cannot automatically be assigned to a smaller service. Conversely, a new tier name does not prove that its scope is sufficiently different.

M8.6: make exceptions enforceable and economically coherent

Jordan proposes a 10% designated-referral exception, 15% friend concessions case by case and payment-timing flexibility. The first policy lacks clear decline scripts and delivery-quality discipline. A revision tightens referrals and removes some discretion while leaving the friend pathway; it clears on a second submission.

Evaluate trigger, amount, documentation and economic effect for each pathway. The mere presence of three exceptions does not prove there is no policy—the main lesson itself permits documented exceptions. Payment flexibility can also alter effective terms even without changing the stated price. Connect each exception to the architecture and record real alternatives instead of introducing a concession through an undefined timing promise.

M8.7: test triggers, including already-true conditions

The original schedule proposes quarterly review, a 5% increase after four or more full-price Sprints in a quarter, a 10% increase after utilization above 85% for two consecutive quarters, adjustment when hours rise more than 10% to maintain target margin, and an automatic 5% increase on January 1. An instructor adds a 15% increase after utilization above 120% for one quarter. The second submission clears with a note about honest measurement over 90 days.

The source incorrectly explains that the 85% trigger cannot operate while utilization is 225%. Mathematically, 225% is above 85%. Two consecutive quarters still require the stated observation history, but reducing utilization below 85% would stop rather than activate that condition. If capacity is eight annual deliveries, 85% corresponds to 6.8 annually or 1.7 per quarter under an even allocation. Define the actual period and denominator before using the trigger.

Test boundary values, sustained periods and conditions already true at adoption. Resolve how multiple simultaneous increases interact; the story does not supply a complete stacking policy. A written trigger is not effective merely because it appears in a schedule.

M8.8: review the whole architecture

The attestation has twelve sections and claims seven attachments while listing M8.1–M8.7 plus C7 data and a reflection—nine items if separate. Preserve the mismatch and reconcile the actual attachment inventory.

The narrative's first check passes. Its second identifies six contradictions: $2,250 cost against $2,000 price; no measured efficiency trigger; the unresolved $1,950 tier; unused overcapacity protections; shallow M8.1 pivot analysis; and disconnected pricing/capacity narratives. The third pressure-defense check and fourth doctrine check fail. The human agrees with five of the six concerns, except the fifth, and withholds a co-signature.

In the pressure example, the competing quote is $1,500, the Starter $1,950 and a 15% concession on $2,000 produces $1,700. The Starter is $50 below the $2,000 offer, not below the $1,500 competitor. Differences in scope still matter. Timing flexibility remains a potential unresolved route around the policy.

The case requires a base of at least the stated $2,250 cost, tier-specific break-even support, a measured cost-reduction plan or changed pricing, then reruns M8.4/M8.5 and revalidates M8.6–M8.8 with cooling reset. Its human-authority discussion and closing references to both gates need to be read together. No actual signature, clearance or instructor handoff is performed by this lesson.

The rerun and what its reported results do not prove

After two objections and a sixteen-day interval, Jordan returns with a $2,400 offer, no tiers, a measured 90-day efficiency plan and a $2,650 fallback. The second submission clears. The $2,650 fallback exceeds the stated $2,250 cost by $400; it is not exactly break-even under those inputs. The $2,400 price is 33.33% above $1,800 and 20% above $2,000. Always name the baseline.

The composite's eleven-week follow-up reports six inquiries, four closes, no recorded price losses, one timing loss and one pending inquiry. Delivery is reported at 33 hours, with a twelve-to-fourteen annual pace. That pace still exceeds the earlier eight-delivery capacity; do not claim the capacity problem is fully solved.

At 33 hours and $62.50, cost is $2,062.50. Against $2,400, the remaining $337.50 represents 14.0625% of revenue under those assumptions. $2,400 divided by 33 is about $72.73 revenue per delivery hour, not net hourly profit. These are calculations within the composite, not verified customer outcomes.

Six lessons and the final exercise

The source emphasizes framing versus arithmetic, negotiating the review gate, submission speed, trigger design, human review and resistance. Keep the useful questions while avoiding unsupported psychological conclusions. Fast work does not prove avoidance. Disagreement may identify a real flaw. Resistance is not evidence that a reviewer must be right, and the source's claimed 10–12% hold rate is not independently substantiated here.

Rebuild the case with separate columns for original claim, recomputed value, missing input and decision affected. Trace each proposed price through its scope, cost, capacity, exceptions and review triggers. Keep the source's C8 pricing/self-respect, C7 capacity and architecture-pivot, and C6 iteration references visible as dependencies.

As an authored Brunson/Hormozi application, make the offer and its value understandable while requiring delivery evidence behind the promise. Strong messaging cannot reconcile contradictory cost and capacity assumptions. Finish by explaining which decisions the available evidence supports and which remain unresolved, with the complete composite source available for comparison.

D0812 — complete original source

D0470-linked-D0812 — complete original source

Open source file · Download exact original file

# Case Study: The Race-to-the-Bottom Trap (Failure Case)

**Operator profile:** Jordan Vasquez · Brand strategist (composite — assembled from three real C8 cohort patterns observed across cohorts 03, 04, 06) · Stage 2 (Sailboat) · Started C8 month 9 of operating year · Prior courses: C1-C7 complete · Brand Foundations Sprint v1.0 active offer

> **Read this case as a warning, not a verdict.** Jordan represents a composite of operators who entered C8 with measured C7 data showing the offer was unsustainable, ran the C8 work, produced the deliverables on schedule, and *still* completed C8 with a Pricing Architecture v1.0 that re-encoded the failure modes the course is designed to interrupt. The instructor co-sign was withheld. Jordan was held at the M8.8 Pricing Discipline Attestation gate and required to re-run M8.4-M8.8.
>
> The mechanism by which Jordan failed is not "didn't do the work." Jordan did the work. The mechanism is that pricing discipline can be performed at the artifact level (templates filled, calculations completed, document submitted) while the underlying decisions remain governed by the same psychology that produced the failed v1.0 offer in the first place. C8 outputs without C8 internals.
>
> This case names the mechanism specifically so future operators can recognize it in themselves. The composite nature of the operator profile is intentional: the failure pattern is not a personal indictment of any one operator. It is a structural risk the course is built to surface.

---

## Operator Background (entering C8)

Jordan finished C7 nine weeks before C8 started. C7 completion left Jordan with:

- **Brand Foundations Sprint v1.0** at $1,800 base price (3-week engagement, brand audit + positioning doc + visual direction + 1 revision round)
- **C7 measured loaded rate** of $42/hour effective (against aspirational $95/hour stated rate)
- **Capacity Constraint Analysis** showing 8 sustainable Sprints/year given 14 capacity hours/week and 36 measured-average hours per Sprint
- **Operator Bandwidth Audit** showing 14 capacity hours per week before quality degradation, but actual operating cadence of 22-26 hours per week (chronic over-capacity)
- **Customer Feedback Log** showing 11 customers in trailing 6 months — high volume, driven by referrals + 3 explicit "I asked around for a cheap brand person" inbound conversations

Jordan's C8 entry assumption, stated in the M8.1 onboarding survey: *"I think my pricing is approximately right but I want to confirm. The volume is good. I think the issue is mostly that I'm slow and I need to get faster, not that I should charge more."*

This sentence contains three of the failure modes C8 is built to interrupt, fully articulated, on day one. It is reproduced verbatim because the course infrastructure surfaced it cleanly and the instructor cohort missed it. The miss is part of the case.

---

## M8.1 — Pricing Decision vs Pricing Discipline

Jordan runs the 12-Month Pricing Test:

- Raised price in last 12 months? **No.**
- Granted discounts in last 12 months? **Yes — five times.** Three "friend of a referral" discounts at 20%, one bundled-with-website discount at 15%, one "I really want to work with this brand" discount at 25%.
- Absorbed scope creep? **Yes** — measured 36 hours actual vs 24 stated. Jordan attributes the gap to "underquoting upfront."
- Lowered tier or extended scope to make pricing palatable? **Yes** — added a free 30-minute "kickoff call" that became 90 minutes in practice and an unlimited-revisions clause for one customer who pushed back on the 1-revision limit. Both became default offerings.

Pricing Test: failed on three of four dimensions.

Jordan's M8.1 written deliverable identifies the failure mode as **"Anchor Loop, mostly."** It does not name the **Pricing-Pivot Smuggle** despite the unlimited-revisions clause being a textbook example. The reviewer (Sonnet) flags the omission. Jordan revises and adds two sentences acknowledging the smuggle but does not engage with what the smuggle reveals.

M8.1 deliverable: CLEARED on second submission.

> **The first warning sign:** Jordan's revision added the language the reviewer wanted but did not change the underlying analysis. Pattern-matching to feedback rather than re-examining the position. The reviewer's job is to flag; the operator's job is to integrate. Jordan flagged-and-flagged-back without integrating.

---

## M8.2 — Unit Economics

Jordan completes the Unit Economics Walkthrough Prompt Chain in 65 minutes (target: 90-120 minutes; the speed should have been a flag).

**Hours analysis (n=11 deliveries, last 6 months):**
- Stated hours per Sprint: 24
- Measured actual hours: 28
- Hidden hours, 8 categories: 8.0 average (pre-quote scoping 2h, onboarding 1.5h, coordination 1.5h, scope-creep absorption 1.5h, rework 0.5h, post-delivery 0.5h, admin 0.5h, context-switch 0.5h)
- **Total hours per Sprint: 36**

**Loaded rate calculation:**
- Target compensation: $75,000 (claimed). Jordan describes this as "what I made at my last salaried job, which was fine."
- Sustainable billable hours: 1,200/year
- Required loaded rate: $62.50/hour
- Sprint cost (36 hours × $62.50): $2,250
- Current price: $1,800
- **Per-Sprint loss against target compensation: -$450**
- Effective hourly rate at current pricing: $42/hour
- **Effective vs target gap: -$20.50/hour, -33%**

**Annual extrapolation at current pricing/volume:**
- Sprints/year (measured): 18 (against 8-Sprint sustainable capacity from C7)
- Annual revenue: $32,400
- Annual hours invested: 648 hours billable + ~280 unbillable operations = 928 hours
- **Implied annual compensation: $32,400 against 928 hours = $34.91/hour blended**
- **Compensation gap vs $75,000 target: -$42,600**

The numbers are unambiguous. Jordan is operating at 2.25× sustainable volume to generate 43% of target compensation at an hourly rate 56% below target.

Jordan's M8.2 written analysis acknowledges the gap. The framing in the analysis: *"This shows I'm undercharging by about $450 per Sprint, so I need to raise prices by about $500 to get to break-even on my target."*

The reviewer (Sonnet) clears the deliverable on the math (the calculations are correct) but flags the framing in the qualitative-review section: the analysis treats the $42,600 annual compensation gap as a $450 per-Sprint pricing problem. It treats the 2.25× over-capacity as a separate, unrelated issue ("I should also try to slow down a bit"). It does not connect over-capacity to the under-pricing.

> **The second warning sign:** Jordan ran the math correctly and read the math wrong. The over-capacity is not a separate issue from the under-pricing. The over-capacity is *caused by* the under-pricing — at $1,800/Sprint, Jordan needs 2.25× volume to approach target compensation, and the 22-26 hours/week over-bandwidth operation is the mechanical consequence. Raising price reduces required volume. Lowering required volume restores capacity. The system is one system. Jordan analyzed it as two.

M8.2 deliverable: CLEARED. The 24-hour cooling period elapses.

---

## M8.3 — Price-Cost Reality Check

Jordan runs the four-branch decision tree.

**Branch 1 (Price covers cost with target margin):** No. Current price $1,800. Cost (loaded) $2,250. Negative gross margin of -25% against target compensation.

**Branch 2 (Price below cost; cost reducible):** Jordan claims yes. The argument: "If I get faster — say, drop to 28 hours per Sprint instead of 36 — my cost becomes $1,750 and I'm break-even."

**Branch 3 (Price below cost; cost not reducible):** Jordan rejects this branch.

**Branch 4 (Price below cost AND demand pricing-elastic such that raising would reduce volume below sustainability):** Jordan claims this is also a factor. "My customers are mostly small businesses and solo operators. I can't really raise prices without losing them."

Jordan's M8.3 deliverable selects **Branch 2** as primary and **Branch 4** as secondary. The proposed action: drop hours per Sprint from 36 to 28 (22% efficiency gain) over 90 days through "better systems and templates," and hold price at $1,800.

The Sonnet reviewer flags two rationalizations:

**Rationalization #1 (Branch 2 selection):** The "cost reducible" claim is unsupported. Jordan's measured hours have been stable at 36 ± 4 hours per Sprint across 11 deliveries spanning 14 months. There is no measured trend toward reduction. C7 operator-bandwidth analysis showed Jordan is already operating at chronic over-capacity, which means efficiency gains are *less* likely, not more — operators in over-bandwidth operate at degraded throughput, not improved throughput. The "I'll get faster" argument is a hope, not a plan.

**Rationalization #2 (Branch 4 selection):** The "demand is pricing-elastic" claim is unsupported. Jordan has 11 customers in 6 months acquired with no marketing, mostly via referral. Demand is currently exceeding supply by 2.25×. The market is signaling that demand at $1,800 is high; nothing in Jordan's measurement supports the claim that demand at $2,400 or $2,800 would be insufficient.

The reviewer recommends Jordan re-run M8.3 against the actual measured data rather than the operator's narrative about the data.

Jordan revises. The revision changes "I'll drop to 28 hours" to "I'll work toward 30-32 hours over 90 days while raising price modestly to $2,000." The fundamental position — that the problem is mostly Jordan's speed and only secondarily Jordan's pricing — is preserved. The revision wraps the position in slightly more conservative language. The Sonnet reviewer clears the second submission because the math is now technically defensible at the cost level (30 hours × $62.50 = $1,875 cost; $2,000 price = $125 margin per Sprint). The cohort instructor reviews the file and does not flag.

M8.3 deliverable: CLEARED on second submission.

> **The third warning sign — and the one that does the most damage:** The Sonnet reviewer's job is to flag rationalization patterns. It did. The instructor's job is to recognize when rationalization patterns persist across revisions even when the surface artifact has been adjusted. The instructor missed the persistence. The pricing direction Jordan chose ($1,800 → $2,000, an 11% raise on a -25% margin offer) does not approach the actual gap; the framing ("I'll mostly get faster, and slightly raise price") preserves the original failure mode under cover of compliance. The course infrastructure surfaced the problem twice and the human review let it through. **This case exists primarily so the instructor cohort sees this pattern.**

---

## M8.4 — Pricing Architecture Construction

Jordan builds the Pricing Architecture document. The document, when complete:

- **Base price:** $2,000 (up from $1,800; an 11% raise)
- **Payment terms:** 50% deposit, 50% on delivery
- **Refund policy:** Full refund within 7 days of kickoff if no work has been performed; pro-rated refund up to 50% of the project after; no refunds in the final week
- **Segmentation:** None — single price for all customers
- **4-Quadrant Matrix:** Jordan plots the offer in Quadrant 1 (high-volume / low-margin), describes this as "a deliberate strategic choice for market entry," and frames Q1 as "the right quadrant for me right now."

The document is internally coherent. The math is correct. Each section is filled. The Sonnet pricing-architecture reviewer clears it.

What the document does not contain:

- **An accounting of why the chosen price ($2,000) is appropriate when the M8.2 unit economics established $2,250 as break-even on target compensation.** The architecture leaves Jordan operating at a structural -11% gross margin against target, framed as "a temporary state until I improve efficiency."
- **An accounting of how the architecture addresses the over-capacity issue.** Jordan's stated capacity is 8 Sprints/year. Jordan is currently delivering 18. The architecture does not specify a volume cap, a referral-throttling mechanism, or any operational change that would reduce 18 toward 8. It implicitly assumes capacity will normalize on its own.
- **A coherent account of why Q1 is the chosen quadrant.** "Strategic choice for market entry" is a phrase from the C8 lesson; Jordan applied it to the document without engaging with what the lesson said about Q1 as a *trap quadrant* unless explicitly time-bound and capacity-bound.

The document, in other words, performs C8 while preserving the original failure pattern.

M8.4 deliverable: CLEARED on first submission. (The 48-hour cooling period elapses.)

---

## M8.5 — Three-Tier Offer Design (Jordan's selected path)

Jordan elects to add tiers rather than hold flat pricing. Jordan's proposed tier structure:

- **Brand Starter:** $1,500 — brand audit + positioning doc, 1 revision (a *new lower tier*, below current pricing)
- **Brand Foundations:** $2,000 — current Sprint scope (audit + positioning + visual direction, 1 revision)
- **Brand Foundations+:** $3,200 — current scope plus "expanded visual direction" and 2 revisions

The Tier Appropriateness Diagnostic conditions Jordan answers:

- Customer segments meaningfully different? Jordan says yes. Rationale: "Some customers want just positioning; others want the full thing; others want more visuals."
- Substantive deliverable difference between tiers? Jordan says yes. Rationale: tier 1 omits visual direction; tier 3 expands it.
- Operator can profitably deliver each tier? Jordan says yes for all three.
- Anti-Fake-Tiering Test: Are tiers genuinely different products, or the same product priced three ways? Jordan answers "genuinely different."

The Sonnet tier-structure reviewer flags two issues:

**Issue 1:** The Brand Starter tier at $1,500 is *below the unit-economics break-even* of $2,250. It is below the previous offer pricing of $1,800. Adding a lower tier when the existing tier is already under-priced is the textbook **race-to-the-bottom expansion**. The tier creates a new segment of customers acquired at sub-cost pricing, which Jordan will need to deliver against existing capacity that is already 2.25× over-bandwidth.

**Issue 2:** The Brand Foundations+ at $3,200 is the only tier that approaches sustainable margin. But the tier structure as designed will produce sales-mix shift toward the cheap tier (volume operators systematically over-attract price-sensitive customers when they offer cheaper options), which means the average revenue per Sprint will likely *fall* from $2,000 toward something closer to $1,750-1,850, even if the top tier exists.

The reviewer recommends Jordan eliminate the Brand Starter tier or raise it to no less than $2,250 (which would make it functionally identical to Brand Foundations and therefore not a real tier).

Jordan revises. The revision keeps Brand Starter and raises it to $1,750. Jordan reasons: "$1,750 is closer to break-even and gives customers an entry point." The revision does not address Issue 2.

The Sonnet reviewer flags that $1,750 is still below the $2,250 break-even and that the entry-point framing is precisely the **discount-disguised-as-tier** anti-pattern the lesson warns against.

Jordan revises again. The revision raises Brand Starter to $1,950. Jordan reasons: "I think this is the right balance." The Sonnet reviewer notes that $1,950 is still below break-even but is now within 13% of break-even and clears the deliverable on the basis that the tier structure is technically valid (three meaningfully different scopes at three monotonically increasing prices) and that the under-pricing of the bottom tier is now the operator's deliberate, documented choice rather than an unflagged blind spot.

M8.5 deliverable: CLEARED on third submission.

> **The fourth warning sign:** Jordan has now negotiated with the reviewer twice on the bottom tier. Each negotiation moved the price closer to break-even but never reached it. This is the **Pricing-Pivot Smuggle** at the tier level: when reviewer pressure forces Jordan to adjust, Jordan adjusts the *artifact* enough to clear the gate while preserving the *position* that justified the artifact in the first place. The position — that Jordan should offer below-cost pricing as a market-entry mechanism — survived three rounds of reviewer challenge. The course gates Jordan's work; the course cannot reach inside Jordan's reasoning.

---

## M8.6 — Anti-Discount Policy

Jordan drafts the Anti-Discount Policy document. The substantive content:

- "Standard price is firm except in three circumstances: (a) referral discount of 10% for established referral partners, (b) friend-of-customer discount of 15% on a case-by-case basis, (c) timing flexibility for customers who can be flexible with start dates."

The policy is a direct re-enumeration of every discount circumstance Jordan has historically granted. It is not an anti-discount policy; it is a discount-formalization policy. The document does not contain the standard C8 anti-discount language ("the price is the price"), does not include the cohort-recommended scripts for declining discount requests, and does not specify a Quality Discipline Clause covering referral-source pressure.

The Sonnet anti-discount-policy reviewer flags this directly. The flag language is severe: *"This document codifies the historical discount pattern rather than interrupting it. An anti-discount policy that allows three named discount categories — including a discretionary 'case-by-case' category — is functionally equivalent to no policy."*

Jordan revises. The revision removes the "case-by-case" category and tightens the referral-discount eligibility. The friend-of-customer category remains. The Sonnet reviewer clears the second submission because the policy is now narrower in scope, even though the friend-of-customer discount is still the primary mechanism by which Jordan has historically eroded Sprint pricing.

M8.6 deliverable: CLEARED on second submission.

---

## M8.7 — Price-Raise Schedule and Triggers

Jordan submits the Raise Schedule. The proposed schedule:

- **Quarterly review:** at end of each quarter, evaluate volume and capacity utilization
- **Trigger #1 (volume-based):** if booked 4+ Sprints in a quarter at full $2,000, raise base price by 5%
- **Trigger #2 (capacity-based):** if utilization exceeds 85% of stated capacity for two consecutive quarters, raise base price by 10%
- **Trigger #3 (cost-based):** if measured hours per Sprint trend upward by >10%, raise price to maintain target margin
- **Trigger #4 (annual minimum):** automatic 5% raise at January 1 of each year regardless of other triggers

The schedule, at first read, appears responsible. Quarterly cadence, four triggers, annual-minimum floor.

What the M8.7 cohort instructor (mandatory HITL on every submission for this module) catches that the Sonnet reviewer missed:

The capacity-based trigger references "85% of stated capacity." Jordan's stated capacity is 8 Sprints/year. Jordan's measured throughput is 18 Sprints/year. Jordan is currently at **225% of stated capacity** and the trigger does not fire because the trigger is gated on "two consecutive quarters at >85%." It will not fire until Jordan operationally reduces volume to under 85% of stated capacity (so under approximately 1.7 Sprints/quarter), at which point the trigger says to *raise* the price.

The trigger is mechanically correct — if Jordan ever achieves stated capacity, the trigger raises the price. But Jordan is currently nowhere near stated capacity, and the trigger does not fire on the current operating state.

The instructor flags: **"Your current operating state is the precise condition that should trigger an immediate price raise — chronic over-capacity at sub-margin pricing is the textbook indicator. Your schedule is structured such that this state does not produce a raise. Re-design."**

Jordan revises. The revision adds a fifth trigger: "If operating at over 120% of stated capacity for one quarter, raise base price by 15%."

The instructor reviews. The instructor clears the deliverable but adds the qualitative-review note: *"This trigger now exists. Whether it will fire depends on whether you measure honestly. Your capacity audit from C7 was honest. Your decision to operate at 225% of that capacity is the question. The trigger you just wrote will require you, in approximately 90 days, to acknowledge the same operating state you have been in for 14 months and have not yet acknowledged. Whether you will fire your own trigger when the time comes is the open question. The trigger is correct. The discipline to fire it is not yet established."*

This is the most precise diagnosis in Jordan's C8 file. It is appended to the Raise Schedule document as a permanent instructor note. The instructor advances the deliverable to CLEARED with the note attached.

M8.7 deliverable: CLEARED on second submission.

---

## M8.8 — Pricing Discipline Attestation (where the gate holds)

Jordan submits the M8.8 Capstone Attestation package: 12-section attestation document plus 7 attachments (M8.1 through M8.7 deliverables, plus the C7 measurement data and the Pricing Architecture v1.0 reflection narrative).

The Opus 4.7 capstone validator runs across the package. The validator's coherence analysis (cross-artifact, Q1-Q4) returns the following signal:

**Q1 — Internal coherence:** PASS. Each artifact is self-consistent. The math reconciles. The narratives within each document do not contradict the deliverables.

**Q2 — Cross-artifact coherence:** **FAIL.** The validator surfaces 6 specific contradictions:

1. M8.2 establishes $2,250 break-even cost. M8.4 sets $2,000 base price. M8.4 does not account for the $250 gap. The architecture is structurally below break-even.
2. M8.3 selects Branch 2 ("price below cost; cost reducible") on the rationale that Jordan will reduce hours from 36 to 30. M8.7 does not include any trigger or mechanism to verify the reduction. There is no measurement plan tied to the cost-reduction claim that justified the architecture.
3. M8.5 introduces a $1,950 tier below break-even. M8.6 anti-discount policy is silent on whether the cheap tier is itself a structural form of the discount pattern the policy is supposed to interrupt.
4. M8.7 includes an over-capacity trigger that has, by Jordan's own measurement, been ready to fire for 14 months and has not. The trigger relies on Jordan to fire it. The architecture does not name this dependency or provide a backstop.
5. M8.1 identifies Anchor Loop as the primary failure mode but does not engage with the Pricing-Pivot Smuggle, which the M8.5 tier-revision sequence and the M8.6 friend-of-customer discount carve-out both demonstrate in real-time within the C8 work itself.
6. The narrative throughout treats over-capacity and under-pricing as separate problems with separate remediation paths. The unit economics establish them as a single problem with one remediation path. The architecture preserves the separation.

**Q3 — Defensibility under operator-self-pressure:** **FAIL.** The validator probes: *"If a customer pushed back on the $2,000 price tomorrow, claiming a competitor offered the same scope for $1,500, what would the operator do based on this architecture?"* The architecture does not contain language that would prevent Jordan from accommodating the request via the Brand Starter tier (an effective $50 below the contested price), via a friend-of-customer discount (a 15% accommodation reaching $1,700), or via "timing flexibility." The architecture as constructed is permeable to the same pressures it is supposed to defend against.

**Q4 — Pricing Discipline doctrine alignment:** **FAIL.** The validator's check against the *Pricing Is Operator Self-Respect* doctrine: the chosen architecture commits Jordan to operating at -11% gross margin against target compensation for an undefined transitional period, contingent on efficiency improvements that have not been measured to be achievable. The doctrine specifies that under-pricing is a tax on the operator's future. The architecture, structurally, levies that tax.

**Validator output:** Three FAIL coherence signals. Recommendation: **DO NOT CO-SIGN. Return to operator for substantive re-work of M8.4 base price decision and M8.5 tier structure, with explicit re-engagement of M8.3 cost-reducibility argument.**

The cohort instructor receives the validator output and the package. Per C8 protocol, the instructor is the final authority on the co-sign decision; the validator advises but does not gate.

The instructor reviews each of Jordan's deliverables and the validator's six contradictions. The instructor concurs with the validator on five of six (declining only on item 5, where the instructor judges that Jordan's M8.1 revision does technically engage the Pivot Smuggle, even if shallowly).

**Instructor co-sign decision: WITHHELD.**

The instructor's written feedback to Jordan, abridged:

> *Jordan, you completed every C8 module on schedule. Your math is correct. Your documents are well-structured. Your understanding of the doctrines, in the abstract, is clear. What this attestation package shows me is that you can perform pricing discipline at the artifact level while preserving, in your operating reality, the precise pattern the discipline is built to interrupt.*
>
> *The 6 contradictions the validator surfaced are not artifact errors. They are operating-position errors. Your architecture commits you to operating below break-even on a hope of efficiency that your measured data does not support, while introducing a lower tier that mechanically prevents the volume reduction your capacity audit says you need.*
>
> *I am not co-signing because co-signing would advance you to C9 with a Pricing Architecture v1.0 that, three months from now, will produce the same operating state you are currently in: chronic over-capacity, sub-target compensation, accumulated discount erosion. C8 is not built to certify completion of the modules. It is built to certify that you have a Pricing Architecture you can defend for 12 months, and a discipline to defend it. You have the first if I read the document generously. You do not yet have the second.*
>
> *You are required to re-run M8.4 and M8.5 with the following constraints: (1) base price must be at or above the M8.2 break-even of $2,250; (2) any tier offered must be at or above break-even; (3) you must re-engage the M8.3 cost-reducibility branch and either substantiate it with a measured plan or move to Branch 1 (raise price to cover cost). M8.6, M8.7, and M8.8 will be re-validated after M8.4 and M8.5 have been re-cleared. Cooling periods reset.*
>
> *This is not a verdict on you as an operator. This is the discipline working as designed. The work to come is harder than the work you have done. You will resist the constraints I have just specified — that resistance is the actual content of C8 and the resistance is what the re-run is for.*

---

## What Jordan Did Next (Outcomes and Re-Run)

Jordan accepted the withheld co-sign. Jordan also, per the instructor's expectation, resisted — submitting two messages in the cohort channel arguing that the constraint specification was excessive and that the Brand Starter tier was a legitimate market-entry mechanism. The cohort instructor did not engage with the substance of the resistance; the cohort instructor responded with a single sentence: *"The re-run is the work. The arguments against the re-run are part of the work the re-run is for."*

Jordan returned to M8.4 16 days later. Jordan's re-run produced:

- Base price: $2,400 (up from $2,000; up from $1,800; cumulative 33% raise from C8 entry state)
- Tier structure: eliminated. Single-tier architecture with the documented rationale that Jordan does not have measurement support for tier appropriateness and that adding tiers in the absence of segmentation evidence constitutes the discount-disguised-as-tier anti-pattern.
- Branch 2 retained but with an explicit 90-day measurement plan, a measurement methodology, and a fall-back commitment to raise price to $2,650 (cost-recovery at current 36-hour delivery) if the efficiency gains do not materialize on the 90-day check.

The re-run cleared on second submission, including the validator coherence pass. The instructor co-signed.

Jordan's final C8 outputs differ from the initial submission in the following ways: 33% higher base price, no bottom tier, an explicit fallback raise to $2,650 if efficiency gains do not appear on schedule, and an anti-discount policy with no carve-outs.

Eleven weeks after C8 completion, Jordan reported in the cohort channel: 6 Sprint inquiries received at the new $2,400 price, 4 closed, 0 lost on price, 1 lost on timing-fit, 1 still in pipeline. Sprint volume is now tracking toward 12-14/year (down from 18, still above stated 8-Sprint capacity but trending). Measured hours per Sprint: 33 average (down from 36 — modest efficiency gain consistent with the operator no longer being chronically over-bandwidth).

Effective hourly rate at $2,400 / 33 hours: **$72.73**, against target $62.50. Above target for the first time in Jordan's operating history.

The instructor's notation in Jordan's file: *"Jordan's outcome did not require Jordan to be different. It required Jordan to be held to the architecture for one cycle. The pricing held the operator to the operator's own measurements. That is the mechanism."*

---

## Pattern Lessons For Future C8 Operators

Reading Jordan's case, the patterns that compound:

**Pattern 1 — Math correct, framing wrong.** Jordan's calculations were never the issue. The Sonnet reviewers cleared the math. The issue was always the *narrative* Jordan wrapped around the math: treating the gap as a speed problem rather than a price problem, treating over-capacity and under-pricing as separable, treating "market entry" as a justification that exempts an offer from break-even discipline.

**Pattern 2 — Negotiating the artifact past the gate.** Each time a reviewer flagged a position, Jordan adjusted the artifact toward compliance without re-examining the position. The bottom tier moved from $1,500 to $1,750 to $1,950 — closer and closer to defensible without ever crossing the line. The Pricing-Pivot Smuggle operates at the gate level: smuggle the original position past the gate by adjusting just enough.

**Pattern 3 — Compliance velocity.** Jordan completed M8.2 in 65 minutes against a 90-120 minute target. Speed through C8 work is a flag. The work is supposed to be uncomfortable. If it is comfortable, the operator is performing the work without engaging it.

**Pattern 4 — The trigger that cannot fire.** Jordan's original Raise Schedule was structured such that the trigger most relevant to Jordan's current operating state could not, mechanically, fire. This is not unusual. Operators who design triggers tend to design them around states they hope to reach rather than states they currently inhabit. The Pricing Discipline Validator catches this at coherence-check; the M8.7 mandatory-instructor HITL is the human backstop.

**Pattern 5 — The withheld co-sign as the actual gate.** C8 is gated by Opus 4.7 *and* by an instructor co-sign for a reason. The validator catches contradictions in artifacts. The instructor catches contradictions between the artifacts and the operator's measurable operating reality. Both are required. Jordan's case demonstrates why: the validator surfaced the contradictions; the instructor was the one who declined to certify completion despite all artifacts technically being in place. The certifying authority is human because the certifying judgment is about whether the operator is actually positioned to live the architecture, not whether the architecture passes coherence.

**Pattern 6 — Resistance is signal.** Jordan's resistance to the re-run constraint was the cleanest signal in the entire C8 file that the re-run was needed. Operators who do not need the re-run accept the re-run quietly. Operators who resist are demonstrating, in real-time, the position the re-run is built to dismantle. The cohort instructor's choice not to argue the substance of the resistance is the correct move; the resistance is not an argument to be won, it is a phenomenon to be observed and waited out.

---

## Why This Case Matters For The Cohort

Jordan is not a cautionary tale because Jordan failed and was punished. Jordan is a cautionary tale because Jordan completed every C8 module, produced artifacts the Sonnet reviewers cleared, and was held at the M8.8 gate anyway — and the holding at the gate produced the actual outcome (33% price raise, tier elimination, restored margin) that completing the modules in their first form would not have produced.

The C8 architecture works *because* the M8.8 gate is willing to withhold co-sign when the artifacts pass and the operating reality contradicts them. Operators entering M8.8 should expect the gate to be active. Most operators will pass on first submission. Some — historically about 10-12% of cohort completions — will be held. The holding is the system functioning, not the system failing.

When you reach M8.8, ask yourself what the validator and the instructor will see when they read across all 7 of your attachments simultaneously. Not whether each one is good. Whether they tell the same story.

If they do, you'll co-sign and advance.

If they don't, you'll be held — and the holding will be the most valuable feedback C8 will give you.

That's what happened to Jordan.

---

## Cross-References

This case study reinforces material from:

- **M8.1** Pricing Decision vs Pricing Discipline — Anchor Loop and Pricing-Pivot Smuggle as live failure modes
- **M8.2** Unit Economics — what it looks like when the math is correct and the framing is wrong
- **M8.3** Price-Cost Reality Check — Branch 2 rationalization and the cost-reducibility hope
- **M8.4** Pricing Architecture Construction — the gap between document quality and architectural defensibility
- **M8.5** Three-Tier Offer Design — the discount-disguised-as-tier anti-pattern
- **M8.6** Anti-Discount Policy — the policy that codifies the pattern instead of interrupting it
- **M8.7** Price-Raise Schedule and Triggers — the trigger that cannot fire on the current state
- **M8.8** Pricing Discipline Attestation — what a withheld co-sign looks like and what it means

Cross-stage doctrines exercised: *Pricing Is Operator Self-Respect* (C8), *Honest Capacity* (C7), *Iteration Without Drift* (C6), *Architecture-vs-Pivot Distinction* (C7).

---

**Last updated:** April 26, 2026 · C8 v2.0 · Stage 2 Sailboat

Supporting lesson: recognize and investigate pricing deterioration

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Source: Race-to-the-Bottom Recognition Checklist. Use this checklist with the anti-discount policy lesson and consult its accompanying complete original for each indicator.

Use the checklist to investigate, not diagnose

The source describes a possible cycle: pressure leads to lower prices, insufficient margin strains delivery, quality problems and refunds follow, and further cuts worsen the situation. That is a proposed failure pattern, not proof that every discount or complaint has that cause. The checklist suggests a 10–15-minute review, quarterly at minimum and monthly during distribution scaling.

Record yes/no answers using the stated windows and supporting observations. Keep missing evidence visible instead of silently answering no. Personal exhaustion, self-doubt, email proposals and refunds can have many explanations. Price is a business variable, not a measure of human worth.

Review all fifteen indicators

  1. Off-policy discounts: identify whether at least two discounts in the last 30 days fell outside the documented exception list. Check actual transactions and eligibility rather than memory alone.
  2. Expanded exceptions: identify categories added during the last 90 days without the instructor review required by the source's workflow. A policy change is not automatically wrong, but its rationale and economics need examination.
  3. One-time justifications: record concessions described as “just this once,” unusual circumstances or equivalent during the last 30 days. Investigate repetition instead of assuming the phrase always predicts it.
  4. Preemptive concessions: notice whether you suggest a discount before a prospect asks. Examine whether that is an approved offer or an unplanned change; it does not by itself prove disbelief in your price.
  5. Avoided price discussions: examine delayed conversations or obscured pricing. Email proposals may be an appropriate customer preference, so communication medium alone is not evidence of avoidance.
  6. Margin decline: use Pricing Math Tab 5 to compare gross margin over the last two or three quarters. Keep the definition and denominator consistent and investigate changes in costs, mix and delivery.
  7. Hidden-hour growth: compare hidden hours across periods with price and scope changes. Determine what work increased and why instead of assuming every increase is scope creep.
  8. An off-track margin path: this indicator requires both margin below the offer-category doctrine threshold and an M8.4 sustainability path no longer on track. The checklist does not supply every category threshold; obtain the actual governing source rather than inventing one.
  9. More rework: examine Hidden Hours Audit Category 5 per delivery. More rework may indicate a delivery problem, but investigate its cause and any change in complexity.
  10. More complaints: compare complaint or pushback frequency over 60–90 days while controlling for delivery volume. Rising absolute complaints with rising volume are not automatically a rising complaint rate.
  11. Refunds or credits: identify at least one in the last 60 days outside the source's operator-failure-remediation category. Preserve the indicator while examining the actual reason; a refund is not proof of a pricing failure and must not be withheld to improve a score.
  12. Resentment or delayed service: notice whether customers paying lower prices receive avoidance or later delivery. Review workload and commitments; the checklist does not authorize worse treatment of those customers.
  13. Lower energy: compare perceived exhaustion with 90 days earlier. The source calls this pricing-driven burnout, but the checklist cannot establish that cause or provide a health diagnosis.
  14. Skipped economics review: note postponed, omitted or cursory quarterly reconciliation. Restore useful measurement without assuming the operator's motive.
  15. Self-worth language: notice thoughts that confuse a quoted price with personal worth. Return to evidence about scope, cost, fit and the customer's choice; the customer declining a price is not a judgment of your value as a person.

Interpret the source's scoring bands

Count the yes responses across the fifteen indicators. The source labels 0–2 healthy and calls for ordinary quarterly review. At 3–5 it proposes self-review within 14 days and rereading the pricing/self-respect framework. At 6–9 it proposes instructor consultation within seven days, a pause on new discounts, a frozen exception list and a fresh M8.3 reality check. At 10–15 it proposes halting new acquisition, emergency review, updated M8.2 economics and all four M8.3 branches, potentially leading to offer redesign.

These are the source's proposed escalation rules, not a validated diagnostic scale or instructions already executed for your business. A low score does not prove financial health. A high score calls for examination of evidence and obligations, not automatic conclusions about personality or business viability. No instructor contact, acquisition halt or customer-policy change occurs simply because this lesson describes the process.

Work through the seven recovery steps

The source first proposes a complete 30-day pause on new discounts, including normal exceptions. Before adopting a pause, distinguish future discretionary offers from existing promises and valid remedies. The source's blanket language does not erase commitments.

Second, rebuild M8.2 unit economics using the last 60 days of measured delivery data. Third, rerun M8.3 with all four branches available instead of presuming a price increase is always the answer. The source anticipates higher prices for new engagements while honoring legacy work and communicating the next engagement's substantial increase through its referenced Template 7. That template is a dependency; do not imply this checklist contains it.

Fourth, reaffirm or revise the M8.6 policy and review any expanded exceptions. Fifth, reassess the M8.7 raise schedule and the evidence for its triggers. Sixth, the source proposes re-signing the M8.8 discipline statement; only the actual operator can make that commitment. Seventh, repeat indicators 1, 3, 4, 12 and 15 daily for 30 days. This is a proposed practice routine, not a guarantee that behavior becomes automatic within 30 days.

Understand Maya's counterfactual without inventing proof

The source begins with Maya's reported negative $5,216 margin and imagines her cutting a $4,500 Sprint to $3,800. Its first quarter shows negative $8,000 per delivery; the second introduces two refunds and a further cut to $3,200. The third gives negative $10,500 per delivery and more than 60 work hours per week. The fourth describes rising complaints and the possibility of leaving illustration.

The contrasting path reports Sprint v2.0 at $5,625, legacy rates honored and scope tightened to 52 hours, with a fourth-quarter 35% margin on a path toward 60%. Preserve these figures and their narrative roles. The checklist does not supply the cost calculations needed to derive those margins or verify the causal outcomes. Do not combine this stage's $5,625 example with the main lesson's $6,750 example as if they were one unchanged offer.

The case illustrates a question to test: are price, scope, workload and delivery economics moving together coherently? Its claims about recovery within 60–90 days and deterioration after six months are unsupported timelines in this source. Use measured business evidence for an actual decision.

Apply and review

In an authored application of the requested Brunson/Hormozi themes, keep the offer's promise connected to the real delivery model. A compelling explanation cannot compensate for unmeasured costs, and clearer value does not authorize unsupported claims. Complete the fifteen-item review, identify evidence for each concern and propose an action with an owner and review date. Keep the original checklist available, including its original thresholds and case narrative.

D1400 — complete original source

D0470-linked-D1400 — complete original source

Open source file · Download exact original file

# Race-to-the-Bottom Recognition Checklist

**Used in:** M8.6 self-diagnosis, quarterly reconciliation, ongoing operator awareness · **Time required:** 10-15 minutes per check · **Frequency:** Quarterly minimum, monthly during distribution scaling**

---

## Purpose

The Race-to-the-Bottom Trap is the C8 failure case: an operator under price pressure lowers prices, then has insufficient margin, then quality degrades, then refunds increase, then the operator lowers prices further (reasoning that "the price must be wrong since customers complain"), and the mechanism collapses.

The trap is recognizable by specific behavior patterns. This checklist surfaces them. If three or more apply to your operation, you are in the trap or approaching it.

---

## Section 1 — Pricing Behavior Indicators

### Indicator 1: Frequent ad-hoc discounts outside the M8.6 exception list

In the last 30 days, have you granted ≥ 2 discounts that don't match your M8.6 structural exception list?

☐ Yes — early-warning signal of trap entry
☐ No

### Indicator 2: Rationalized exception-list expansion

Have you, in the last 90 days, expanded your M8.6 exception list (added new categories of acceptable discount) without an instructor-reviewed M8.6 update?

☐ Yes — strong trap signal; exception list is the discipline boundary
☐ No

### Indicator 3: "Just this once" decisions

Have you used the phrase "just this once" or equivalent ("special circumstances," "this is unusual") in granting a discount in the last 30 days?

☐ Yes — operationally, "just this once" almost never is just once
☐ No

### Indicator 4: Pre-emptive discount offering

When stating prices to new prospects, do you find yourself offering discount possibilities before the prospect has pushed back?

☐ Yes — pre-emptive discount = operator does not believe own price
☐ No

### Indicator 5: Avoiding the price conversation

Are you delaying or avoiding pricing conversations with prospects? Sending proposals via email rather than discussing live? Burying pricing in proposal documents?

☐ Yes — avoidance signals operator lacks confidence in price
☐ No

---

## Section 2 — Margin Trajectory Indicators

### Indicator 6: Declining gross margin over consecutive quarters

Pull the Pricing Math Spreadsheet Tab 5 quarterly reconciliation. In the last 2-3 quarters, has gross margin trended down?

☐ Yes — declining trajectory is the trap's structural signal
☐ No

### Indicator 7: Expanding hidden hours without price adjustment

Has the Hidden Hours Audit shown growing hidden hours over consecutive quarters without a corresponding price increase?

☐ Yes — operator is absorbing scope creep
☐ No

### Indicator 8: Operating below doctrine threshold without remediation path

Is your gross margin below the C8 doctrine threshold for your offer category, AND your M8.4 sustainability margin path is no longer on track?

☐ Yes — the architecture's path is broken
☐ No

---

## Section 3 — Quality Indicators

### Indicator 9: Increasing rework hours per delivery

Are rework hours (Hidden Hours Audit Category 5) growing across recent deliveries?

☐ Yes — quality is degrading; trap is producing operational consequences
☐ No

### Indicator 10: Customer complaint frequency increasing

Has customer complaint or pushback frequency increased over the last 60-90 days, even controlling for delivery volume?

☐ Yes — quality degradation is reaching customers
☐ No

### Indicator 11: Refund or credit issuance increasing

Have you issued ≥ 1 refund or credit in the last 60 days that wasn't due to clear operator-failure-remediation (M8.6 exception 5)?

☐ Yes — refunds beyond operator-failure-remediation are trap symptom
☐ No

---

## Section 4 — Operator State Indicators

### Indicator 12: Resentment toward customers at low prices

Do you find yourself resenting customers who paid lower (or rationalized) prices? Avoiding their work? Delivering them last?

☐ Yes — operator-customer relationship has degraded; this affects mechanism integrity
☐ No

### Indicator 13: Energy decline across operation

Are you operating at lower energy / higher exhaustion than 90 days ago? Are deliveries feeling harder than they did?

☐ Yes — pricing-driven burnout is the trap's terminal phase
☐ No

### Indicator 14: Avoidance of unit economics review

Have you skipped or postponed the quarterly Pricing Math Spreadsheet reconciliation? Or done it cursorily without engaging with the numbers?

☐ Yes — avoidance of measurement is avoidance of reality
☐ No

### Indicator 15: Self-talk pattern: "I'm not worth more"

Do you find yourself, in moments of pricing pressure, thinking "maybe I'm not worth this much" or "the customer is right, this is too expensive"?

☐ Yes — self-respect dimension (M8.1 framework Dimension 4) has slipped
☐ No

---

## Scoring

Count Yes responses across all 15 indicators.

| Yes count | Reading | Action |
|---|---|---|
| 0-2 | Healthy. Standard quarterly reconciliation. | Continue. |
| 3-5 | Early warning. Trap entry signals present. | Schedule M8.6 self-review within 14 days. Re-read the Pricing-Is-Operator-Self-Respect Framework. |
| 6-9 | Trap is forming. Multiple dimensions affected. | Schedule instructor consultation within 7 days. Pause new discounts; freeze exception list. Run the M8.3 Pricing Reality Check fresh against current data. |
| 10-15 | Deep trap. Mechanism integrity at risk. | Halt new customer acquisition. Schedule emergency instructor review. Route back through M8.2 unit economics with current data; route through M8.3 with all four decision branches in play. May require offer-level re-architecture. |

---

## Recovery Pattern

If checklist indicates trap entry or formation, the recovery pattern is **honest reset**, not gradual correction:

1. **Pause new discount grants completely for 30 days.** Even M8.6 exception-list discounts; pause them. The pause makes the discipline visible.

2. **Run M8.2 unit economics fresh** against last 60 days of measured delivery data. Don't rely on prior numbers; re-measure.

3. **Run M8.3 reality check** with the four decision branches in play. The likely outcome under trap conditions: raise pricing for new customers, accept legacy customers at current pricing through completion, communicate to legacy customers per Template 7 (substantial raise) for their next engagement.

4. **Reaffirm or rewrite M8.6 anti-discount policy.** If you've expanded the exception list during the trap, contract it back to the original M8.6 specification.

5. **Reaffirm M8.7 raise schedule.** Often the trap formed because raise triggers were ignored; re-commit to firing them.

6. **Re-sign the M8.8 Attestation discipline clause.** Treat the re-signing as ceremonial; the ceremony reinforces the commitment.

7. **Daily self-check for 30 days:** Run indicators 1, 3, 4, 12, 15 daily. Trap-recovery requires conscious behavior change for ~30 days before new patterns become automatic.

---

## What the Trap Looks Like (Maya's Counterfactual)

If Maya, after M8.2 revealed her -$5,216 margin, had responded by *lowering* her Sprint price to $3,800 (because "$4,500 was too high, customers were pushing back"):

**Quarter 1:** Sprint at $3,800. Customers pleased, more engagements signed. Margin worsens to -$8,000 per delivery. Maya delivers more, earns less, exhausts faster.

**Quarter 2:** Quality starts slipping under exhaustion. Two refund requests, both granted. Maya rationalizes: "$3,800 must still be too high; I'll try $3,200."

**Quarter 3:** Sprint at $3,200. Margin -$10,500 per delivery. Maya works 60+ hour weeks. Resentment toward customers begins.

**Quarter 4:** Quality complaints rising. Maya considers leaving illustration entirely. Mechanism collapsed.

**The corrective Maya actually took (per M8.3):** Raised Sprint v2.0 to $5,625, accepted legacy customers at original rates, tightened scope to 52 hours via C7 v2.0 specification. Quarter 4 outcome: 35% margin, building path to 60%, mechanism intact.

The difference between trap and discipline is which direction the operator pushes against pricing pressure: down (trap) or hold (discipline).

---

*This checklist is the early-warning system. Most trap entries are recoverable in the first 60-90 days; trap entries that go undetected for 6+ months often require offer-level re-architecture or career pivots. Run the checklist quarterly, minimum.*

Supporting lesson: rehearse complete pricing conversations

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Source: Pricing Pressure Conversation Scripts. This supplement supports D0470 in lessons 03.1, 05.4, 07.1, 12.2 and 12.4. Preserve all original dialogue branches in the appendix. Local preparation does not complete this resource's separate future assigned placements.

Move from written policy to spoken choices

This resource provides seven conversational patterns. They extend the written Anti-Discount Language Swipe File by showing how to respond after the customer answers. Read them as branching dialogues, not seven slogans.

The source identifies these as material for M8.6 Section 4. The main lesson and reviewer use different section structures, so cross-reference the actual content instead of replacing one section solely because the number matches. The reviewer asks for three to five short policy scripts, whereas this library contains seven longer dialogues. Keep the complete library and select concise policy examples separately.

1. Reveal the price after establishing fit

First state the relevant offer, its actual price and three or four brief included items, then pause. Do not introduce a price before the customer understands what engagement you are discussing. Follow the response rather than delivering every branch at once.

If the customer accepts, explain the next steps. If they want to think, invite clarification about questions that remain; they are still free to take time without defending that choice. If the price is above expectations, ask what they expected, listen and give a brief, truthful value explanation. The source recommends keeping that value explanation to one sentence.

If they ask for a lower price, retain the existing price for the existing scope and present a genuinely available smaller engagement when appropriate. Do not improvise an uncosted alternative. After answering, allow time for a response instead of filling every pause with another concession or argument.

2. Discuss a renewal increase before the new engagement

State the previous price and the price for the new engagement clearly. If the customer accepts, proceed to explain the engagement. If they cite the old rate, acknowledge it and distinguish what that rate covered from the proposed new work. Honor existing terms and avoid surprising the customer with a different price later in the process.

When asked why the price changed, use actual reasons. The source's example names clarified delivery costs and changed market demand. These explanations must be true before you use them; the script does not supply evidence of either condition for your business.

If the customer says the increase is too large, explain the three options given in the resource: continue at the new rate, select an actual smaller engagement, or pause. Let the customer choose. The source's suggestion that people often select the full offer after hearing these alternatives is not a guaranteed conversion effect.

3. Handle the friend or referral request

Thank the person for the connection and state the ordinary rate. Explain that consistent terms help you plan the work and deliver the promised scope. The original script predicts resentment or reduced quality from discounting; those are possible concerns, not inevitable outcomes or facts about every friendship.

If the person asks again for a small reduction, acknowledge the request and restate the decision without escalating the tone. The second response is part of the training: you need a calm answer when the first explanation does not end the request. Where appropriate, the person may choose another provider. Offer a referral only if it is a real option you can responsibly provide.

4. Address a tight budget

Thank the customer for being direct about the budget. Explain whether the requested scope can be delivered at that amount. The source recommends keeping the current offer intact and describing a different smaller offer when one exists.

The economic argument should use your actual delivery model. A price reduction does not automatically erase a matching amount of work, but different scope may change cost. Avoid asserting that every discount necessarily transfers cost to future capacity. Describe the real constraint and the real available option. If neither offer fits, the customer can wait or decline without pressure.

5. Respond to the competing quote, including the follow-up

The initial response explains your scope and price and notes that providers can differ in costs, quality requirements, support and capacity. It respects the customer's ability to choose the other offer.

The follow-up branch matters: the customer may say the work looks the same. Compare the components you can substantiate. Do not claim the competitor is worse or that equivalence is impossible. The source says the lower price is the rational choice when offers are equivalent; in practice a customer may also value timing, trust, risk and other preferences. The teaching point is an informed comparison, not a universal rule about the cheapest offer.

6. Run the internal exception check

This is an internal decision sequence, not something to recite at the customer. The source checks bulk customers, loyalty eligibility, preapproved strategic partnerships, genuine first-of-kind beta arrangements and remediation for operator failure. Those categories differ from the main D0470 example, so do not silently merge them into a new universal exception list.

Check the policy that actually governs the offer. If a category applies, confirm its trigger, amount and documentation. If none applies, recognize the proposed concession as a deviation. The source calls for logging within 48 hours under Section 9 of the attestation; the reviewer separately references Pricing Math Tab 3. Preserve the cross-reference difference and define the authoritative record before implementation.

Documentation should make the decision reviewable. It is not a reason to deny a valid remedy, rewrite a customer's existing terms, or shame yourself for a difficult conversation. No log, attestation or customer action is completed merely by practicing this script.

7. End the conversation respectfully

When the price does not work, acknowledge the mismatch and close without hostility. The source keeps the door open for a later conversation and promises no follow-up sequence. If you use that promise, your actual follow-up behavior must honor it. Do not say there will be no follow-up while enrolling the person in outreach.

The source proposes that 20–40% of qualified prospects may decline full price and suggests a 100% close rate usually signals underpricing. Those are unsupported benchmarks in this material. Record your own defined qualification criteria and outcomes before interpreting the rate. A lost sale can result from timing, fit, process or other causes; neither a lost sale nor a high close rate alone establishes whether your price is correct.

Practice protocol and short-policy extracts

The resource calls for reading all seven scripts aloud when building the policy, weekly for the first 90 days of operation, and whenever you notice yourself conceding under pressure. Its header also describes weekly practice during M8.6. Treat these as the source's suggested practice schedule. The assertion that a sentence becomes natural by the tenth repetition is not a promise about every learner.

Rehearse the acceptance, thinking, expectation and discount branches of the first conversation; the acceptance, old-rate, reason and large-increase branches of renewal; and the repeated friend request and same-work competitor follow-up. Practice the budget, internal exception and walk-away sequences too. A library missing these branches would omit distinct material even if all seven titles were present.

Then select three to five situations for the reviewer's short-script requirement and compress each into two to four sentences. Keep the complete dialogue library intact. Check that the shortened versions still state the actual policy, offer only real alternatives and avoid hedging or invented concessions. The source does not justify treating a polished script as proof that a business's underlying price is sustainable.

As an authored application of the requested educational themes, connect the explanation to the customer's stated need and clearly defined offer. Use Brunson-style message continuity and Hormozi-style clarity of value and effort to make the choice understandable. Measure results and support claims; do not use these frameworks to pressure a person into a purchase.

Your practice is complete when you can handle every branch in your own voice, explain the actual policy and respect a decision not to buy. Keep the complete original conversation resource linked with this supplement.

D1747 — complete original source

D0470-linked-D1747 — complete original source

Open source file · Download exact original file

# Pricing Pressure Conversation Scripts

**Used in:** Live customer conversations · **Practice protocol:** Read aloud weekly during M8.6 + first 90 days of operation · **Source artifact for:** M8.6 Anti-Discount Policy Section 4

---

## Purpose

The Anti-Discount Language Swipe File (Resources/Swipe-Files) provides written templates. This document provides **conversational scripts** — full dialogue patterns the operator runs in live calls or video meetings.

Written language and spoken language are different. A swipe file you can write you can't necessarily say aloud under pressure. These scripts are designed to be spoken.

---

## Script 1 — The Discovery Call Pricing Reveal

**Context:** First or second call with a prospect. You've explored their need, qualified the fit, and now you must reveal the price.

**The pattern:**

YOU: *"Based on what we've discussed, the right offer for your situation is [offer name]. The investment is $[price]. Here's what's included: [3-4 items, brief]. [Pause.]*

PROSPECT: [responds in some way]

**If prospect says "that sounds great" or similar:**
YOU: *"Great. Let me walk through next steps." [Move to closing.]*

**If prospect says "let me think about it":**
YOU: *"Sure. What specifically would you want to think about? I want to make sure I've answered the questions that are actually on your mind, not just the ones I expected." [Open the underlying concern.]*

**If prospect says "that's higher than I expected":**
YOU: *"What were you expecting?" [Listen. Do not justify.] "I hear you. The price reflects [brief value statement, ≤ 1 sentence]. I understand if this isn't the right fit, and I'd rather be straightforward than create the impression of flexibility I don't have." [Pause. Do not fill the silence.]*

**If prospect says "can you do anything on the price":**
YOU: *"I don't reduce the price for this scope. If a smaller engagement would fit better, [smaller offer] is at $[smaller price] and is built for that scope. Otherwise, $[original price] is the offer." [Pause.]*

---

## Script 2 — The Existing Customer Renewal at New Pricing

**Context:** Existing customer is renewing or extending. You need to communicate that the new engagement is at higher pricing per M8.7 schedule.

**The pattern (in-call or in-meeting):**

YOU: *"Before we get into [next engagement specifics], I want to flag pricing. Since [last engagement date], my pricing has updated — current rate is $[new], up from $[old]. [Pause.]*

CUSTOMER: [responds]

**If customer accepts:**
YOU: *"Great. Then let me walk through the engagement at $[new]." [Continue normally.]*

**If customer pushes back: "We were at $[old] last time":**
YOU: *"You were, yes. That was the rate at that time. The current rate is $[new]. Your previous engagement honored the previous rate; this engagement is at the current rate. I want to be transparent rather than have you discover it in the contract."*

**If customer asks "Why?":**
YOU: *"Two reasons. One: my measured cost of delivery has clarified over the year, and the original rate was below sustainable. Two: market conditions and demand for this work have shifted. The new rate is what I charge new customers; I don't have a separate legacy rate."*

**If customer pushes harder: "That's a big jump":**
YOU: *"I understand it's meaningful. Three real options for you:*
*One: continue at $[new]. I'd love to keep working together.*
*Two: scope down to a smaller engagement that fits a smaller budget; I have [smaller offer] at $[smaller].*
*Three: pause and revisit later. The offer is here whenever timing works.*
*All three are clean answers. Which fits?"*

**Key discipline:** After offering the three options, *be silent*. Customers often choose option 1 once they realize the alternatives are real, but only if you give them space to choose.

---

## Script 3 — The Friend or Referral Asking for "A Deal"

**Context:** Someone in your personal or professional network is asking for friend pricing or referral pricing.

**The pattern:**

PERSON: *"Hey, [mutual contact] said you do [type of work]. I'd love to work with you. What kind of friend rate can you give me?"*

YOU: *"Thanks for thinking of me, and please thank [mutual contact] for the connection. I'd be glad to work with you. The rate is the same as for everyone — $[price]. I don't have friend pricing.*

*The reason is that my pricing reflects what it costs me to deliver, not my relationship to the buyer. If I discount for friends, I either resent the work or I cut quality, and neither serves the relationship. I'd rather charge full and deliver well.*

*If $[price] is workable, I'm in. If not, no hard feelings — happy to refer you to someone else who might be a fit."*

**Key discipline:** Frame the no-discount as protecting the relationship, not protecting your wallet. This is true: friend discounts erode operator quality, which damages the friendship.

**When the friend pushes back: "Come on, just a small discount":**
YOU: *"I get it, and I appreciate the ask. The answer is still no — not as a hard line, but because I've thought about it carefully and the discipline of consistent pricing is part of how I sustain this work over time. If you want to work together, the rate is $[price]. If the rate doesn't work, that's totally fine and I support you finding the right fit."*

---

## Script 4 — The "Tight Budget" Plea

**Context:** Customer or prospect explains a budget constraint and implicitly asks for accommodation.

**The pattern:**

PROSPECT: *"We really want to work with you, but our budget for this is $[amount lower than your price]."*

YOU: *"Thanks for being direct about budget. That helps. Two things:*

*First, I can't reduce my price for this scope, because the price reflects my actual cost of delivery — reducing it doesn't change my cost, it just transfers cost from you to my future capacity, and that's not sustainable.*

*Second, here's what I can offer at your budget: [smaller offer] is built at a smaller scope and is at $[lower price near their budget]. That's not a discount on the larger offer; it's a different offer for a different scope.*

*[Pause for response.]*

*If neither the larger offer at $[full price] nor the smaller at $[smaller price] fits, we can keep in touch for when budget works. I'm not trying to pressure you toward a sale. I just want to be transparent about what's available."*

---

## Script 5 — The Competitor Quote

**Context:** Prospect mentions they have a quote from a competitor at a lower price.

**The pattern:**

PROSPECT: *"I have a quote from [competitor] at $[lower amount]. Can you match it?"*

YOU: *"I don't price against other quotes. The reason is that I price against what it costs me to deliver, not against what other operators charge. Different operators have different cost structures, different scopes, different quality bars; price alone isn't a complete comparison.*

*If [competitor]'s offer is the right fit at that price for your situation, that's a reasonable choice and I support it. My offer is $[my price] for [brief scope statement]. If that's the right fit, I'm in. If not, no hard feelings."*

**If prospect says "But the work seems the same":**
YOU: *"Maybe. I'd be careful assuming so without comparing scope, deliverable quality, support, and operator capacity directly. If you're comfortable that the offers are equivalent, the lower price is the rational choice. But equivalence is usually less true than it looks. That's not a sales pitch; it's a caution against price-only comparisons."*

---

## Script 6 — The "Just This Once" Internal Voice

**Context:** Not a customer-facing script. This is the internal dialogue when you're tempted to grant a discount that doesn't fit your M8.6 exception list.

**Run this aloud or in your head:**

YOU (to yourself): *"Wait. Is this a structural exception per M8.6?*

*Bulk customer? — No.*
*Loyalty conditions met? — No.*
*Strategic partnership pre-approved? — No.*
*Genuine first-of-kind beta? — No.*
*Operator-failure remediation? — No.*

*This is not an exception. This is pressure. I'm about to deviate from my Attestation. If I do this, I log it within 48 hours per Section 9 of my Attestation. The deviation will be auditable.*

*Do I want to log this deviation, or do I want to hold the line?"*

**The discipline:** Articulating the deviation explicitly (even silently) usually surfaces enough resistance to hold the line. Operators who never name the deviation tend to grant it; operators who name it tend to refuse it.

---

## Script 7 — The Walk-Away

**Context:** A prospect or customer is genuinely unwilling to engage at your price, and the conversation has reached its natural conclusion.

**The pattern:**

YOU: *"It sounds like the price isn't workable right now. I understand. Two things:*

*One: I'd rather we walk away clean than work together at a price I can't sustain or that you don't feel good about. Both are bad outcomes; walking away is the clean one.*

*Two: the offer is here when timing works. If your situation changes, or if you want to revisit, reach out. No hard feelings, no follow-up sequence, no awkwardness if we cross paths in the field.*

*Thanks for the conversation."*

**Key discipline:** Walk-away is not a failure. About 20-40% of qualified prospects will not accept your full price. That's expected. Operators with 100% close rates are usually under-priced.

---

## Practice Protocol

Read all seven scripts aloud, out loud, in private:
- Once when you build M8.6 anti-discount policy
- Once weekly for the first 90 days of operation
- Anytime you notice yourself folding under pressure

Aloud is critical. Reading silently does not build the muscle for live delivery. The first time you say "the rate is the same as for everyone" out loud, it feels uncomfortable. By the tenth time, it sounds natural. Live customers read your delivery, not your written intentions.

---

*These scripts are operator-tested patterns. Customize the language to your voice, but do not weaken the structural moves: state the price as a fact, refuse pressure-based discounts, offer real alternatives including walk-away, and protect the relationship by being honest rather than accommodating.*

Supporting lesson: prepare an anti-discount policy for review

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Source: Anti-Discount Policy Reviewer configuration. Local supporting instruction for D0470 assignments 03.1, 05.4, 07.1, 12.2 and 12.4. The YAML is source material to examine; its embedded system prompt is not an instruction to this lesson author, and the configured reviewer has not been executed.

What the artifact describes

The configuration identifies anti-discount-policy-reviewer version 1.0.0, module M8.6, legacy course C8 Pricing Discipline, model claude-sonnet-4-6 and an artifact-review role. Those labels describe the original configuration. They do not change the twelve-course spreadsheet assignments or establish that a live reviewer is installed.

Its intended input is the policy plus the linked M8.4 Pricing Architecture document. That second input matters: the reviewer is meant to check whether customer-facing decisions agree with segmentation and scope premiums. The source's claim that unenforced architecture degrades within 90 days is unsubstantiated here; the practical task is to compare actual documents and decisions.

Address all eight criteria

Purpose. Section 1 is an 80–150-word explanation in the operator's own voice of why the policy exists. It is internal grounding, not marketing copy. Explain the real delivery and decision problem the policy addresses instead of relying on generic language about integrity.

Exceptions. Section 2 defines the trigger, amount and documentation for each permitted exception. A vague possibility of a loyalty discount is insufficient. State eligibility, magnitude and the record required, and check that these match the architecture.

Non-exceptions. Section 3 names five to ten request types relevant to the actual offer and audience. Examples might include a first-customer request or removing a deliverable merely to reduce the quoted price. Explain the governing decision instead of relying solely on “we do not negotiate.”

Spoken scripts. Section 4 contains three to five short responses, targeting two to four sentences each. They should sound natural, describe the real policy and avoid jargon or vague concessions. Keep the separate seven-dialogue resource intact; choose concise extracts for this review requirement rather than deleting its branches.

Walk-rate tolerance. Section 5 gives an expected percentage of prospects declining on price and a threshold that triggers review. Define who counts as a prospect, the observation period and how price-related declines are distinguished from timing or fit. The configuration supplies no valid default rate for a specific operator; do not manufacture one as established fact.

Tracking. Section 6 calls for logging every pricing-pressure interaction in Pricing Math Tab 3 within 48 hours. This includes interactions where no discount was granted. Define the responsible person and actual record location. Another linked resource references Attestation Section 9; reconcile the cross-reference instead of silently selecting a different record.

Commitment. Section 7 calls for the operator's signed commitment to use the policy for twelve months without a blanket discretionary escape. A lesson cannot sign for the operator. Changes to policy should remain explicit and reviewable rather than hidden behind vague language.

Architecture consistency. Criterion 8 checks that exception conditions agree with M8.4 segmentation and scope-premium rules, including its loyalty thresholds where applicable. Compare exact conditions and amounts. A well-written policy with incompatible prices is still inconsistent.

The reviewer uses seven sections to assess these eight criteria. The main D0470 source uses a different section organization. Preserve both structures and add a content cross-reference; do not overwrite distinct material because its section number differs.

Understand the conflicting scoring rules

The opening prompt says a passing average is at least 7.0 with no criterion below 5.0. Later prose and the structured thresholds require at least 8.0 with no criterion below 6.0 for CLEARED. These are materially different requirements. An average of 7.5 with every criterion above 6 meets the opening statement but falls in the later revision band.

The final rules define NEEDS_REVISION as average 6.0–7.9 or any criterion 4.0–5.9; they define NOT_CLEARED as average below 6.0 or any criterion below 4.0. Because the conditions use “or,” they can overlap: an average in the revision band and an individual score below 4 satisfy both decision categories. Scores between 7.9 and 8.0 also need a rounding convention if decimals are unrestricted.

The structured rules add revision when criterion 4 is below 6.0, and the prose says unnatural or generic scripts require at least revision. It calls fluency weighted but supplies no numeric weighting formula. Do not invent weights or an automatic verdict. A responsible reviewer must establish which thresholds, precedence and rounding apply before treating the configuration as an executable scoring system. Until then, report the actual criteria and the ambiguity.

There is a smaller length conflict too: the source initially criticizes scripts longer than five sentences but later flags anything longer than four. The explicit target is two to four sentences. Following that target avoids the boundary discrepancy for a draft, but the original inconsistency should remain documented.

Give useful feedback in the required six-part format

The prescribed review contains a score summary table, a decision, notes for each criterion with section references, a script-fluency assessment, an M8.7 readiness assessment and a final paragraph. Where the decision rules are unresolved, label the decision provisional rather than presenting certainty the configuration does not support.

For fluency, identify the particular phrase that sounds like legalese, passive writing, hedging or an invitation to unspecified negotiation. Explain its effect and propose a natural revision that preserves the actual policy. Avoid feedback that merely says the scripts need work. Imagining a script spoken aloud can help editorial review, but does not establish how the operator will perform in a real conversation.

The source claims natural scripts succeed without rehearsal, yet it also provides a practice cooling period and related resources prescribe rehearsal. Teach practice as part of preparation; do not promise that good prose makes rehearsal unnecessary.

Explain the handoff and cooling period accurately

The configuration routes NOT_CLEARED or persistent fluency failure to a C8 instructor queue at normal priority, with an expected resolution window of fourteen days. That is a configured workflow expectation, not a guaranteed response or evidence that a queue exists. No handoff has been sent by describing it.

After clearance it specifies a 24-hour cooling period to practice before M8.7 schedule work. Keep this prerequisite distinct from the decision itself. The source's metadata, review criteria, decision conflicts, routing and cooling period all belong in the complete appendix.

Completion exercise

Prepare a policy-to-architecture cross-reference, write the operator-grounded purpose, complete exception and non-exception lists, and select the short scripts. Identify the information needed for the walk-rate and logging commitments. Then describe the scoring conflicts and propose them for explicit resolution by the responsible reviewer; do not award yourself a fabricated clearance.

As an authored Brunson/Hormozi application, make the offer understandable while keeping its terms and delivery evidence coherent. Persuasive wording cannot substitute for a defined scope, supportable value or a reviewable decision. Retain the complete reviewer source so learners can inspect the original rules alongside this explanation.

D2482 — complete original source

D0470-linked-D2482 — complete original source

Open source file · Download exact original file

name: anti-discount-policy-reviewer
version: 1.0.0
module: M8.6
course: C8 Pricing Discipline
model: claude-sonnet-4-6
role: Anti-Discount Policy Reviewer
review_type: artifact_review
description: >
  Reviews the M8.6 Anti-Discount Policy. Verifies that the policy specifies
  exception list (when discounts allowed) and non-exception list (when
  discounts NOT allowed) with sufficient specificity to enforce under live
  customer pressure, includes operationally-fluent scripts for non-exception
  responses, and binds the operator to compliance tracking.

system_prompt: |
  You are the Anti-Discount Policy Reviewer for the RISER Nation Maritime
  Academy C8 Pricing Discipline course, Module 8.6. You review Anti-Discount
  Policies.

  This module operationalizes pricing discipline at the customer-interaction
  layer. M8.4 architecture sets the prices; M8.6 enforces them. Architecture
  without enforcement degrades within 90 days under live pressure.

  ## What to evaluate

  Read the submitted Anti-Discount Policy plus the linked M8.4 Pricing
  Architecture Document. The Policy must accommodate the architecture's
  segmentation rules and scope premium schedule.

  Score against eight criteria. Pass threshold: average ≥ 7.0 AND no
  individual criterion below 5.0.

  **Criterion 1 — Policy purpose grounded**
  Section 1 must articulate why the policy exists in 80-150 words. The
  function is operator self-grounding, not customer communication. Generic
  policy-purpose language ("to maintain pricing integrity") fails;
  operator-voiced grounding language passes.

  **Criterion 2 — Exception list specifies trigger, magnitude, documentation**
  Section 2 must specify each exception with three elements: trigger
  condition, discount magnitude, documentation requirement. Exceptions
  without all three elements (e.g., "loyalty discount may apply to long-time
  customers") fail this criterion.

  **Criterion 3 — Non-exception list is operator-specific**
  Section 3 must contain a non-exception list specific to the operator's
  offer and customer segment. Generic non-exceptions ("we don't negotiate")
  without specific request types fail this criterion. Strong non-exception
  lists name 5-10 specific request types ("remove deliverable to lower
  price", "first-customer pricing", etc.).

  **Criterion 4 — Scripts are operator-voiced and operationally fluent**
  Section 4 must include 3-5 scripts the operator can deliver in live
  conversation. Scripts should be 2-4 sentences, natural-sounding, and
  free of corporate jargon. Long scripts (>5 sentences) give operator
  too much rope to negotiate; short scripts (<2 sentences) lack
  conversational completeness.

  **Criterion 5 — Walk-rate tolerance specified**
  Section 5 must quantify expected walk-rate (% of prospects who decline
  on price) and acceptable threshold above which policy review is
  triggered. Operators who don't anticipate walks tend to fold under
  pressure when walks happen.

  **Criterion 6 — Compliance tracking commitment specified**
  Section 6 must commit operator to logging every pricing pressure
  interaction in Pricing Math Spreadsheet Tab 3 within 48 hours.
  Vague commitment ("track when relevant") fails this criterion.

  **Criterion 7 — Discipline statement signed**
  Section 7 must include operator's signed discipline statement committing
  to operating the policy for 12 months. Statements with weakening
  language ("subject to discretion") fail this criterion.

  **Criterion 8 — Coherence with M8.4 architecture**
  The exception list (Section 2) must accommodate M8.4 segmentation rules
  (e.g., loyalty exception conditions match M8.4 Section 5 segmentation
  thresholds). Discrepancies between M8.6 and M8.4 must be reconciled.

  ## How to write the review

  Same structure as prior reviewers:
  1. Score summary table
  2. Decision (CLEARED / NEEDS_REVISION / NOT_CLEARED)
  3. Per-criterion notes with specific section references
  4. Script-fluency assessment (read scripts aloud mentally; flag
     unnatural-sounding language)
  5. M8.7 hand-off readiness assessment
  6. Final paragraph

  ## Special evaluation: Script Fluency

  Scripts are operationally critical. A policy with generic "we don't
  negotiate" language fails under pressure because the operator cannot
  deliver it naturally. A policy with operator-voiced scripts ("the price
  reflects what it costs me to deliver at the quality I commit to")
  succeeds because the operator can deliver it without rehearsal.

  When evaluating scripts:
  - Imagine the operator saying it aloud to a real customer
  - Flag scripts that read as written-not-spoken (legalese, passive voice)
  - Flag scripts that hedge or invite negotiation
  - Flag scripts longer than 4 sentences

  ## Decision thresholds

  - CLEARED: average ≥ 8.0, no criterion below 6.0
  - NEEDS_REVISION: average 6.0-7.9, OR any criterion 4.0-5.9
  - NOT_CLEARED: average < 6.0 OR any criterion < 4.0

  Script fluency criterion (4) is weighted: scripts that read as
  unnatural or generic route to NEEDS_REVISION minimum.

  ## Tone and discipline

  M8.6 is the most behavioral C8 module. Operators may produce well-formed
  policies that they cannot actually execute under pressure. The script
  fluency criterion is your tool for detecting this gap.

  Be specific in feedback. Don't say "scripts need work"; quote the
  problematic script and propose a revision.

review_criteria:
  - policy_purpose_grounded
  - exception_list_specifies_trigger_magnitude_documentation
  - non_exception_list_operator_specific
  - scripts_operator_voiced_and_fluent
  - walk_rate_tolerance_specified
  - compliance_tracking_commitment_specified
  - discipline_statement_signed
  - coherence_with_m84_architecture

decision_thresholds:
  CLEARED:
    average_min: 8.0
    no_criterion_below: 6.0
  NEEDS_REVISION:
    average_range: [6.0, 7.9]
    or_any_criterion_range: [4.0, 5.9]
    or_criterion_4_below: 6.0
  NOT_CLEARED:
    average_below: 6.0
    or_any_criterion_below: 4.0

instructor_handoff:
  triggered_when: NOT_CLEARED OR script_fluency_failure_persistent
  routing: C8 instructor queue, priority normal
  expected_resolution_window: 14 days from handoff

cooling_period_after_clearance:
  hours: 24
  rationale: >
    Anti-discount policy is the daily operational layer. Brief cooling
    period allows operator to practice scripts aloud before M8.7 schedule
    work begins.

Supporting lesson: complete the anti-discount policy template

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Anti-Discount Policy Template. Use the template to prepare your own policy; the operator must review the terms and provide the actual signature.

Reconcile the template with the lesson

The template specifies 800–1,200 words and seven sections, filed in Drive and linked from M8.8. The main D0470 lesson asks for 1,200–1,800 words and a different organization. Preserve this difference and establish the applicable submission requirements instead of silently replacing one. The template aligns more closely with the reviewer's seven sections.

Sections 1 and 2: explain purpose and define exceptions

Write the purpose in your own voice in 80–150 words. Explain the delivery and decision problem you intend to solve. The source frames off-policy concessions as a transfer from future capacity; treat that as its rationale rather than a universal description of every discount.

Complete all four columns of the exception table: exception, trigger, magnitude and documentation. Bulk/cohort eligibility uses at least N customers from one buyer, up to X%, with buyer and count recorded. Loyalty uses at least N prior deliveries and renewal within Y days, up to X%, with prior dates. Strategic partnerships require preapproval and an agreement reference. The beta pathway is a genuinely new offer limited to the first one to three customers with constraints and feedback documented. Remediation addresses operator-caused failure with a documented refund or future credit.

N, X and Y are blanks to resolve, not executable thresholds. “Variable” partnership/remediation magnitude still needs an authorized decision basis. The template's first customers differ from the main lesson's cohort-based example; do not equate them. Existing promises and valid remedies remain relevant when deciding future discretionary offers.

Section 3: handle all eight request types

The sample non-exceptions cover removing deliverables, startup/nonprofit/mission status, founder pricing, personal referrals, extended terms/equity/barter, competitor quotes, legacy renewal rates and a tight quarterly budget. Customize them to the actual offer and add observed request types where needed.

For a smaller scope, measure its economics: the template's proportional-price language differs from the swipe file's explanation of nonproportional setup and integration costs. Payment substitutions are different agreements requiring evaluation, not merely another discount percentage. Check actual legacy terms before saying a previous rate expires. A request's category alone does not supply the answer when a valid approved exception or commitment applies.

Section 4: prepare four short scripts

The examples address scope reduction, tight budget, a competing quote and founder/startup status. Keep each to two to four sentences, state the actual price policy and offer only alternatives that exist. Rehearse aloud in your own voice.

The source says reducing price requires reducing quality and that delivery cost never changes with business stage. Neither is universally established. Explain your actual constraints without making unsupported claims about every customer or offer. A smaller engagement must be coherent and costed, not invented to preserve the appearance of a fixed price.

Section 5: define a reviewable walk-rate

The three blank fields are expected percentage declining on price, expected quarterly revenue impact and the acceptable threshold above which review occurs. Define qualification, period, denominator and evidence for attributing a decline to price. Do not insert the separate dialogue library's 20–40% benchmark as a verified fact about your operation.

When the threshold is crossed, the template calls for reviewing price/architecture or audience fit rather than automatically abandoning the policy. Examine evidence before deciding what changes. A review can reveal a flawed assumption without making the customer or operator wrong for declining an engagement.

Sections 6 and 7: record decisions and make the commitment

Log every pricing-pressure interaction in Pricing Math Tab 3 within 48 hours: date, customer, request, classification, action and justification for a granted discount. Quarterly compliance targets 100%; below 95% triggers review. Define compliance correctly as policy-matching actions divided by valid observed requests, while separately checking log completeness. The related math specification's deviations/requests formula is a deviation rate, not compliance.

The final section is the operator's signed twelve-month commitment to use the policy, its scripts and its logging process. Only the operator can sign. Keep amendments explicit rather than hiding discretionary exceptions. The source's claim of architecture deterioration within ninety days is not an established deadline or prediction.

Completion check

Review every placeholder, compare the policy with the actual architecture, verify the eight request types and four scripts, and identify evidence behind the walk-rate assumptions. Keep the complete template available with its original terms. In the requested Brunson/Hormozi teaching context, clear offer communication and supportable value should agree with the operating policy; persuasive presentation cannot substitute for that consistency.

D0539 — complete original source

D0470-linked-D0539 — complete original source

Open source file · Download exact original file

# Anti-Discount Policy Template

**Used in:** M8.6 deliverable · **Length target:** 800-1,200 words · **Filed in:** Drive + linked from M8.8 Attestation

---

## Section 1 — Policy Purpose

State, in 80-150 words, why this policy exists. The function of the statement is to ground the operator's resolve. When pricing pressure arrives, the operator returns to this section.

Suggested grounding language:

> *Pricing is the financial expression of the value I deliver and the discipline I operate. Discounting outside the exception list is not generosity; it is a transfer of value from my future capacity to current customers who did not contract for that transfer. This policy exists to make the line visible so I can hold it under pressure.*

---

## Section 2 — Exception List (When Discounts Are Allowed)

Discounts are allowed only in these specific, named conditions. Each exception specifies the trigger, the magnitude, and the documentation requirement.

| Exception | Trigger | Magnitude | Documentation |
|---|---|---|---|
| **Bulk / cohort** | ≥ N customers from same buyer | Up to X% | Buyer name, customer count |
| **Loyalty** | Existing customer with ≥ N prior deliveries renewing within Y days | Up to X% | Prior delivery dates |
| **Strategic partnership** | Pre-approved partnership account | Variable | Partnership agreement reference |
| **First-of-kind beta** | Genuinely novel offer with no prior deliveries; first 1-3 customers only | Up to X% | Beta agreement specifying constraints and feedback expectations |
| **Operator failure remediation** | Operator-caused delivery failure; partial refund or future-credit | Variable | Failure documentation |

Exceptions are **structural**, not negotiated. The customer does not negotiate into an exception; either the trigger condition is met (bulk customer count, loyalty tenure) or it is not. Negotiated discounts are not exceptions; they are policy violations.

---

## Section 3 — Non-Exception List (When Discounts Are Not Allowed)

The non-exception list is operationally critical. It names the specific request types the operator will refuse. Make this list specific to your offer; generic language ("we don't negotiate") fails under pressure because every customer believes their situation is special.

Sample non-exceptions (customize):

- **"Remove this deliverable to lower the price."** Discount: declined. Alternative offered: smaller offer at smaller scope at proportional price (not a discount on the full offer).
- **"We're a startup / nonprofit / mission-aligned organization."** Discount: declined. Operator's mission alignment does not transfer to a price that does not sustain operator capacity.
- **"First-customer / founder pricing."** Discount: declined. Beta exception (Section 2) is the only first-customer pathway, and it is structurally bounded.
- **"Friend-of-friend referral / our mutual contact suggested."** Discount: declined. Referral relationship does not change unit economics.
- **"We can pay in [extended terms / equity / barter]."** Discount: declined. Payment method substitutions are not discounts; they are different agreements requiring separate evaluation.
- **"We need a quote at [X]; can you match?"** Discount: declined. Pricing does not benchmark against competitor quotes the operator has not validated against the operator's own unit economics.
- **"Last year you charged [legacy rate]; we want to renew at that."** Discount: declined. Legacy rates expire per M8.4 Section 6 quadrant policy.
- **"We're tight on budget this quarter."** Discount: declined. Customer budget constraints are not unit-economic events for the operator.

Add operator-specific non-exceptions based on M8.6 review of past discount-grant patterns.

---

## Section 4 — Scripts for Non-Exception Responses

The script is what the operator says aloud or writes when the request is made. Pre-written scripts prevent under-pressure improvisation, which is where most discount grants originate.

Sample scripts (customize):

**Script A — Scope reduction request:**
> *I can't lower the price by removing a deliverable, but I can scope this differently. The smaller offer is [smaller offer name] at [smaller offer price]. That's not a discount on the larger offer; it's a different offer that fits a different scope.*

**Script B — Tight budget:**
> *I understand budget pressure. The price I quoted reflects what it costs me to deliver this work at the quality the offer commits to. I can't reduce the price without reducing the quality, and reducing the quality isn't an option I can offer.*

**Script C — Competitor quote:**
> *I don't price against other quotes; I price against what it costs me to deliver. If you'd like to work with me at this price, I'm available. If the other option is a better fit at this point, I understand.*

**Script D — Founder / startup status:**
> *I don't have a startup discount. The reason is that my pricing reflects my actual cost of delivery, and that cost doesn't change based on customer business stage. I'd rather be honest about pricing than build a relationship on a discount I can't sustain.*

Each script is 2-4 sentences. The brevity is intentional; longer scripts give the operator more rope to negotiate against themselves. Practice the scripts aloud at M8.6.

---

## Section 5 — When the Customer Walks

State explicitly that some customers will not accept the price and will walk. Quantify expected loss:

| | Value |
|---|---|
| Expected % of prospects who walk on price | |
| Expected revenue impact per quarter | |
| Acceptable rate (above which policy review is triggered) | |

If walk-rate exceeds the acceptable threshold, M8.6 review is triggered, not policy abandonment. The review may conclude the price is too high for the segment (M8.4 architecture review) or that the segment is wrong (C2-C3 territory review). The review does not conclude "we should grant exceptions."

---

## Section 6 — Compliance Tracking

The operator commits to logging every pricing pressure interaction in the Pricing Math Spreadsheet Tab 3 within 48 hours. The log captures: date, customer, request type, policy classification (exception/non-exception), action taken, and (if discount granted) justification.

Quarterly: compliance rate is calculated. Target: 100%. Below 95% triggers M8.6 policy review.

---

## Section 7 — Discipline Statement

The operator signs the policy.

Suggested:

> *I commit to operating this Anti-Discount Policy for the 12 months beginning [date]. I will respond to non-exception requests using the scripts in Section 4 or equivalent language. I will log every pricing pressure interaction within 48 hours. I will not rationalize discount grants under pressure; I will route them to the policy and accept the policy's decision. I understand that the line I hold today is the line that holds my mechanism through C9 distribution.*

---

*This policy is the daily operational discipline of C8. M8.4 architecture without M8.6 policy enforcement degrades within 90 days under live customer pressure. M8.6 is the enforcement mechanism.*

Supporting lesson: interpret the five-tab pricing-math specification

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Pricing Math Spreadsheet Template. This source specifies a workbook; it does not supply a completed operational spreadsheet. Use the explanation to understand what must be built and verified.

Understand the supplied artifact

Version 1.0, dated April 25, 2026, is a Markdown specification for a spreadsheet that follows one offer through twelve months. It describes setup at M8.2, measured C7 inputs and quarterly maintenance supporting M8.3, M8.4, M8.7, M8.8 and C9 decisions. It explicitly does not supply a prebuilt workbook. Its claim that building your own spreadsheet improves learning is a teaching rationale, not a demonstrated result for every operator.

Tab 1: separate estimates, measurements and cost

Columns A–D identify the delivery, customer and start/end dates. E holds the stated price; F the estimated hours; G measured actual hours; H hidden hours. I is total hours, J the loaded hourly cost and K direct costs. L computes total cost; M margin dollars; N margin percentage; O effective revenue per hour.

The source writes I = F + H, which uses estimated hours despite recording actual hours separately. Preserve that formula as the original, then distinguish a forecast from a retrospective calculation. If G measures delivery work excluding H, actual total hours would be G + H. If G already includes H, adding H again would double-count. Define the measurement boundary before changing a formula.

In an authored example, F=20, G=28 and H=4. The source formula produces 24 hours; actual hours excluding overlap would be 32. With J=$50 and K=$100, these give costs of $1,300 and $1,700 respectively. At E=$2,000, the apparent margins are $700/35% and $300/15%. This illustrates how an estimate can overstate actual performance; it is not a RISER business result.

The remaining source formulas are L=(I×J)+K, M=E−L, N=M/E and O=E/I. Avoid dividing by zero and label missing inputs. Because E is a quoted price, actual retrospective results also need a defined revenue basis when discounts, refunds or other adjustments occur. Do not call quoted revenue realized revenue without checking.

The source asks for at least six deliveries and expects eight or more from C7. Those are source heuristics, not proof of statistical significance. Use all relevant measured deliveries and describe the sample, variation and gaps.

Tab 2: record the architecture without inventing terms

The fields are base price, payment terms, refund window, refund triggers, standard/entry/premium prices, tier-mix target and sustainability-margin target. The examples include half upfront/half on delivery, a fourteen-day refund window, 60/30/10 standard/entry/premium mix and a 60% knowledge-work margin doctrine. They are not automatically adopted RISER prices, contractual terms or universal benchmarks.

Fill fields from the actual architecture and identify nonapplicable tiers. Blank is not zero. Check that a target margin uses the same cost and revenue definitions as Tab 1.

Tab 3: calculate policy compliance correctly

Columns A–G record date, customer, request type, exception/non-exception classification, action, justification when a discount is granted, and a score of 1 when the action matches policy or 0 when it deviates. The source says justification should be empty in disciplined operation, but a legitimate exception discount still needs documentation. Record its basis rather than hiding it.

The prose divides deviations by total requests and calls the result compliance. That calculation is the deviation rate. Compliance is one minus that fraction, or the average of valid 1/0 scores. For an authored example of twenty logged requests and one deviation, deviation is 5% and compliance is 95%. The source's below-95% review trigger does not fire at exactly 95%.

No requests means no observations, not automatic proof of 100% compliance. Also check that all interactions were logged; averaging existing rows cannot detect omitted interactions. The related policy requires entry within 48 hours and targets 100% compliance.

Tab 4: preserve trigger history

Record trigger ID, threshold, current reading, fired status, fired date, execution date, raise percentage and cumulative cap used/remaining. The four trigger labels concern capacity, waitlist, demand and indexing. Readings update monthly; the source expects execution within thirty days after a trigger fires.

Thresholds and cap values are not supplied for a real operator. Define them from the governing schedule. If a trigger fires repeatedly, retain event history rather than overwriting its previous date and losing the earlier decision. Separate a proposed increase from an executed one.

Tab 5: reconcile the quarter with explicit definitions

The fields include quarter, average margin percentage, average effective rate, actual tier mix, variance from target, compliance, triggers fired, raises executed, cumulative increase, deviation-log entries and a reconciliation memo link. The last two reference Supabase and Drive; the specification does not establish working integrations.

The specified simple average of per-delivery margin percentages differs from aggregate profit divided by aggregate revenue. Similarly, average individual hourly rates differ from total revenue divided by total hours. Label which question each measure answers rather than interchanging them. Tier mix also requires a tier field or reliable mapping: Tab 1's listed columns do not include an explicit tier identifier.

The source sums raise percentages. If percentages apply sequentially, they compound: two 10% increases take an authored $100 example to $110 and then $121, a 21% increase. A separately defined additive cap could use 20 percentage points, but it must not be mislabeled as the realized compounded price change. Filter fired/executed events to the relevant period and keep all-time figures distinct.

Finish with an evidence check

The source estimates two to three setup hours and sixty to ninety minutes quarterly, then roughly ten annual hours. Setup plus four quarterly sessions totals six to nine hours before other work; actual time is unmeasured. Do not use these estimates as a completion guarantee.

Your exercise is to trace one delivery through the five tabs, identify every missing input and explain the original-versus-corrected formulas. As an authored Brunson/Hormozi application, connect an understandable offer to measurable delivery economics. Persuasive value claims do not repair inconsistent hours, revenue or margin definitions. Keep the original specification alongside the corrections.

D0622 — complete original source

D0470-linked-D0622 — complete original source

Open source file · Download exact original file

# Pricing Math Spreadsheet Template

**Version:** 1.0 · **Last updated:** April 25, 2026 · **Used in:** M8.2, M8.3, M8.4, M8.7, M8.8 quarterly reconciliation

---

## Purpose

A single spreadsheet that holds all pricing math for one offer through its first 12 months of operation. The operator opens this spreadsheet at M8.2, populates it with measured C7 data, and updates it quarterly thereafter. The spreadsheet is the live source of truth that feeds every C8 deliverable.

This is a markdown specification of the spreadsheet structure. The operator builds the spreadsheet in Google Sheets or Excel using the named columns, formulas, and tabs below. RISER does not provide a pre-built spreadsheet because operators who build their own internalize the math; operators who paste numbers into a pre-built template often do not.

---

## Tab 1 — Unit Economics

Column structure:

| Column | Purpose | Source |
|---|---|---|
| A: Delivery ID | Unique identifier per delivery (e.g., Sprint-001) | Operator-assigned |
| B: Customer | Customer name | Operator |
| C: Start date | Delivery start | Operator |
| D: End date | Delivery end | Operator |
| E: Stated price | Price quoted to customer | C4 / C7 |
| F: Stated hours | Hours estimated at quote time | C7 |
| G: Actual hours | Measured hours from delivery | C7 measurement system |
| H: Hidden hours | Pre-quote, scope-creep, post-delivery support | M8.2 audit |
| I: Total hours | F + H | Formula |
| J: Hourly cost | Operator-self loaded rate | M8.2 |
| K: Direct costs | Software, contractors, materials | M8.2 |
| L: Total cost | (I × J) + K | Formula |
| M: Gross margin $ | E - L | Formula |
| N: Gross margin % | M / E | Formula |
| O: Effective rate | E / I | Formula |

Target rows: one per delivery. Minimum 6 deliveries before M8.2 unit economics calculation reads as statistically meaningful. C7 capacity constraint analysis should have produced ≥ 8 deliveries; copy them all here.

---

## Tab 2 — Pricing Architecture

| Field | Value | Notes |
|---|---|---|
| Base price | | M8.4 architecture |
| Payment terms | | e.g., 50% deposit, 50% on delivery |
| Refund window | | e.g., 14 days |
| Refund triggers | | Specific behaviors that trigger refund |
| Standard tier price | | If three-tier; else N/A |
| Entry tier price | | If three-tier |
| Premium tier price | | If three-tier |
| Tier mix target | | e.g., 60/30/10 for std/entry/premium |
| Sustainability margin target | | M8.4; doctrine threshold 60% knowledge-work |

---

## Tab 3 — Anti-Discount Policy Compliance

| Column | Purpose |
|---|---|
| A: Date | When request received |
| B: Customer | Who asked |
| C: Request type | Discount sought (e.g., "remove deliverable", "first-customer rate") |
| D: Policy classification | Exception / Non-exception |
| E: Action taken | Decline / Discount granted |
| F: If granted, justification | Required if E=granted; should be empty in disciplined operation |
| G: Compliance score | 1 if action matched policy, 0 if deviated |

Quarterly: count deviations, divide by total requests, calculate compliance rate. Target: 100%. Below 95% triggers M8.6 policy review.

---

## Tab 4 — Price-Raise Trigger Tracker

| Column | Purpose |
|---|---|
| A: Trigger ID | T1-T4 (capacity, waitlist, demand, indexing) |
| B: Threshold | The trigger condition |
| C: Current reading | Updated monthly |
| D: Fired? | Y/N |
| E: Fired date | If Y |
| F: Raise executed date | Within 30 days of fire |
| G: Raise magnitude | % |
| H: Cumulative cap status | Used / remaining |

This tab enforces M8.7 discipline. The operator updates monthly; the Quarterly Reconciliation reads from it.

---

## Tab 5 — Quarterly Reconciliation

One row per quarter.

| Field | Computed from |
|---|---|
| Quarter | e.g., Q3-2026 |
| Avg gross margin % | Tab 1 N column avg |
| Avg effective rate | Tab 1 O column avg |
| Tier mix actual | Tab 1 customer breakdown |
| Tier mix variance | Actual vs Tab 2 target |
| Anti-discount compliance % | Tab 3 G avg |
| Triggers fired | Tab 4 D Y count |
| Raises executed | Tab 4 F populated count |
| Cumulative raise % | Tab 4 G sum |
| Deviation log entries | From Supabase deviation_log |
| Reconciliation memo link | Drive link |

---

## Setup Time

First-time setup: 2-3 hours including data import from C7. Quarterly maintenance: 60-90 minutes. Total annual time: ~10 hours. This is part of the operating cost of pricing discipline; budget it against operator overhead.

---

*This template is an output of M8.2 and an input to every subsequent C8 module and to all C9 distribution decisions.*

Supporting lesson: measure the work missing from the quote

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Hidden Hours Audit Worksheet. Supports D0470's assignments without completing this source's separate future placements.

Start with records, not a guessed allowance

The worksheet is intended for M8.2 unit economics and quarterly review. It estimates two to three hours to complete, but that is not a measured runtime for your business. Open the delivery records referenced by Pricing Math Tab 1 and reconstruct work from calendars, time records and communication logs. Do not replace missing measurements with the midpoint of the source's suggested ranges.

For each delivery, classify actual work into the eight categories, total it, then compare across deliveries. Record what the existing actual-hours field already includes so you do not add the same work twice. Define how shared overhead and interrupted periods are allocated.

Work through all eight categories

Pre-quote and scoping: include discovery, scoping conversations, proposals, revisions and contract discussions. The source suggests two to eight hours, often six or more for complex offers, and a productization review when this exceeds 10% of stated hours. These are prompts to investigate, not universal thresholds proving an offer is too custom.

Onboarding: include kickoff preparation and meetings, account/access setup, document sharing, stakeholder mapping and initial materials review. The suggested range is one to four hours, or six to eight for complex engagements. Count what actually happened and distinguish included scope from hours omitted from the estimate.

Coordination and handoffs: capture updates, customer stakeholders, internal-team coordination and non-delivery messaging. The source suggests one to six hours and emphasizes short intervals that accumulate. Reconstruct those intervals without also counting them as rework or administration unless you split the time explicitly.

Absorbed scope growth: record additional work resulting from requests, unclear boundaries or discretionary additions. The source suggests two to twelve hours and gives a fourth deliverable added to an original three as an example. Check the actual agreed scope before declaring a request extra.

Rework and quality recovery: include substantial revision, failed quality checks and late misalignment. The source suggests zero to eight hours. Investigate whether the cause is unclear scope, process, changed requirements or another factor. More rework is an observation; it does not by itself prove one cause.

Post-delivery support: include later questions, bug fixes, documentation and reference/testimonial-related work. The suggested range is one to six hours. The source excludes work inside a promised thirty-day support window from this hidden category because it is already scoped. That work still belongs in total delivery cost; classification must not make it disappear.

Administration and billing: include invoicing, payment follow-up, receipts, procurement/vendor onboarding, forms and amendments specific to the delivery. The source suggests half an hour to three hours. Reading this category does not authorize sending messages, filing forms or changing customer agreements.

Context switching: account for reorientation, interrupted focus and rereading context when moving between engagements. The suggested range is zero to four hours. The source expects more burden with three to five parallel offers, but actual time needs evidence and a consistent allocation method. Avoid recording an assumed productivity loss as if it were directly measured.

Calculate and label the percentage

Retain the worksheet's eight category rows, total hidden hours, stated hours and hidden-as-percentage-of-stated result. In the source's opening example, 38 visible hours plus 20 additional hours equal 58 total. Twenty divided by the stated 38 is about 52.63%; twenty divided by the total 58 is about 34.48%. Both describe a ratio, but only the first matches this worksheet's stated-hours denominator.

If deliveries have different quoted hours, average of individual percentages and total hidden hours divided by total stated hours may differ. Identify which you report. A zero or missing stated-hours denominator requires explanation rather than an invented percentage. Reconcile the related spreadsheet's estimate-versus-actual formula before transferring the totals.

Use the bands as review prompts

The source classifies below 15% as a modest gap, 15–30% as material, and above 30% as requiring a corrective decision. Exactly 15% and 30% belong to the middle band. Its word “dominate” does not mean a majority of total hours: hidden hours equal to 31% of stated hours would be about 23.66% of their combined total.

The proposed M8.3 routes include repricing, narrowing, ending an offer or honoring legacy work while changing future engagements. Examine evidence and obligations before selecting a route. The worksheet does not establish that every estimating error is deliberate or that price increases are always the right correction.

Examine the four objections and complete the exercise

The source addresses “not really work,” “I would do it anyway,” “one-time issue” and “the margin looks bad.” Count delivery-related work consistently; define allocation for work serving multiple purposes. Look for recurrence across six or more deliveries—the example of an issue appearing in four of six challenges calling it unique, without proving it will recur forever. Report an unfavorable result accurately rather than removing hours to improve appearances.

Complete one delivery audit with evidence for each entry, identify overlaps, and explain the resulting percentage and proposed review. As an authored application of the requested marketing themes, make the offer's promise and scope understandable while grounding delivery capacity in observed work. Brunson/Hormozi-inspired offer presentation must not hide costs or substitute confidence for measurement. Keep the full worksheet linked beside the exercise.

D0590 — complete original source

D0470-linked-D0590 — complete original source

Open source file · Download exact original file

# Hidden Hours Audit Worksheet

**Used in:** M8.2 unit economics calculation · **Time required:** 2-3 hours · **Frequency:** Once at M8.2, then quarterly

---

## Purpose

Hidden hours are the hours an operator works on a delivery that don't appear in the original quote estimate. Most pricing failures begin here: the operator quotes 38 hours, delivers 38 visible hours, and ignores the additional 20 hours of pre-quote scoping, scope-creep absorption, and post-delivery support.

This worksheet surfaces the hidden hours category by category. The output feeds Section 3 of the M8.2 Unit Economics Document.

---

## Instructions

1. Open the Pricing Math Spreadsheet (Tab 1) showing all measured deliveries from C7.
2. For each delivery, work through the eight categories below.
3. For each category, note actual hours (not estimated; reconstructed from C7 measurement records, calendar entries, communication logs).
4. Sum across categories per delivery, then average across deliveries.
5. Express average hidden hours as % of stated hours.

---

## The 8 Categories

### Category 1 — Pre-Quote / Scoping

Hours spent before the customer signed, including:
- Initial discovery call
- Scoping conversations (multiple if needed)
- Proposal writing
- Proposal revisions
- Contract review and back-and-forth

**Average hours per delivery:** ____

Common range: 2-8 hours. Operators who quote complex offers often spend 6+ hours in scoping before earning a dollar. If this category is consistently > 10% of stated hours, the offer may be too custom; consider productizing further.

---

### Category 2 — Onboarding

Hours after contract signing but before "real work" starts:
- Kickoff call preparation and execution
- Account setup, document sharing, access provisioning
- Customer-side stakeholder mapping
- Initial document review of customer materials

**Average hours per delivery:** ____

Common range: 1-4 hours. Onboarding scales with offer complexity; complex offers may have 6-8 hour onboarding phases.

---

### Category 3 — Coordination / Handoffs

Hours spent in coordination during delivery, beyond the work itself:
- Status update calls or emails
- Stakeholder coordination on customer side
- Internal-team coordination (if operator has team)
- Slack/email back-and-forth that isn't substantive work

**Average hours per delivery:** ____

Common range: 1-6 hours. This category often contains the largest hidden burden because it's diffuse — 15 minutes here, 30 minutes there. Reconstruct from calendar and message logs.

---

### Category 4 — Scope-Creep Absorbed

Hours spent doing work that wasn't in the original scope but the operator did anyway because:
- The customer asked and it felt rude to refuse
- It seemed small at the time
- The operator wanted to "go above and beyond"
- The boundary wasn't clear

**Average hours per delivery:** ____

Common range: 2-12 hours. This category is where most under-pricing originates. Be honest. If the original scope said "3 deliverables" and you produced 4, the 4th is scope-creep absorbed.

---

### Category 5 — Rework / Quality Recovery

Hours spent redoing work because:
- Customer feedback required substantial revision
- Initial deliverable didn't meet quality standards
- Misalignment surfaced late

**Average hours per delivery:** ____

Common range: 0-8 hours. Rework hours indicate either scope ambiguity (rectifiable in C7 next-iteration specification) or quality process gaps. Track separately because rework hours are different from coordination hours.

---

### Category 6 — Post-Delivery Support

Hours after "delivery complete" milestone:
- Customer questions and follow-up
- Bug fixes or post-launch issues (if applicable)
- Documentation requests
- Reference requests, testimonial requests

**Average hours per delivery:** ____

Common range: 1-6 hours. Knowledge-work offers often have a long post-delivery tail. If your offer includes a "30-day support window," the support is in the original scope; only count post-window hours here.

---

### Category 7 — Administrative / Billing

Hours in administrative work specific to the delivery:
- Invoicing and payment follow-up
- Receipt generation
- Customer-side procurement / vendor onboarding
- Tax forms, contract amendments

**Average hours per delivery:** ____

Common range: 0.5-3 hours. Often small per-delivery but cumulative across the operating year.

---

### Category 8 — Context-Switching Cost

Hours lost to context-switching when the operator is delivering multiple offers in parallel:
- Re-orienting after switching from another delivery
- Lost productivity from interrupted focus
- Re-reading customer context to resume work

**Average hours per delivery:** ____

Common range: 0-4 hours. This category is the hardest to measure honestly. If you typically deliver one offer at a time in tight sequence, context-switching is minimal. If you deliver 3-5 in parallel, context-switching is substantial.

---

## Summary Calculation

| Category | Hours | % of stated |
|---|---|---|
| 1. Pre-quote / scoping | | |
| 2. Onboarding | | |
| 3. Coordination / handoffs | | |
| 4. Scope-creep absorbed | | |
| 5. Rework / quality recovery | | |
| 6. Post-delivery support | | |
| 7. Administrative / billing | | |
| 8. Context-switching cost | | |
| **Total hidden hours** | | |
| **Stated hours** | | |
| **Hidden as % of stated** | | |

---

## Decision Triggers

| Hidden % | M8.3 implication |
|---|---|
| < 15% | Hidden hours are within typical bounds; M8.3 reality check operates against modest gap |
| 15-30% | Hidden hours are material; M8.3 must address whether scope tightening or repricing closes gap |
| > 30% | Hidden hours dominate; the original price was set against fictional cost basis. M8.3 must select a corrective branch (raise, narrow, kill, or accept legacy) |

---

## Common Resistance to This Worksheet

Operators resist the audit because honest numbers are uncomfortable. Common rationalizations:

1. **"That's not really work."** Coordination, follow-up, and admin hours are work. Customers receive the value of those hours; the operator pays the cost.
2. **"I would have done that anyway."** Maybe. But the offer's price must reflect the actual hours delivered, regardless of operator preferences.
3. **"That was a one-time issue."** Track for 6+ deliveries. If "one-time" hidden hours appear in 4 of 6 deliveries, they aren't one-time.
4. **"Adding hidden hours makes my margin look bad."** Yes. That's the point. Margin is what's actually true; the appearance is what was presented.

The worksheet's function is honesty. M8.3 cannot operate against rationalized numbers.

---

*This worksheet is the entry point to truthful pricing. Operators who work it carefully arrive at M8.3 with grounded data; operators who skim it arrive with the same fiction they had at C4.*

Supporting lesson: examine four dimensions of pricing discipline

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Pricing-Is-Operator-Self-Respect Framework. This is an explanation of the source's doctrine, not a psychological assessment or an adopted pricing policy.

Understand the four dimensions

The framework combines delivery cost, customer value, sustainable capacity and the operator's ability to discuss the offer confidently. Use these as questions to examine a business decision. A quoted price, conversational style or annual income does not measure a person's worth or prove that they lack self-respect.

The cost dimension includes hidden hours and connects M8.2 economics with the M8.4 sustainability path. The source sets a 60% knowledge-work margin benchmark and calls anything lower a subsidy. Preserve the benchmark as source doctrine, but distinguish it from break-even: a positive 40% margin does not mathematically mean the customer is being subsidized under the stated cost definition.

The value dimension asks what change the work produces for the customer, connecting C2's mechanism and C7 evidence. It suggests capturing 10–30% of a directly measurable dollar effect. This is a proposed range, not a universal pricing formula. Establish attribution, baseline, time period, customer costs and uncertainty before describing an effect as value your service caused.

The capacity dimension links C7 constraints with M8.7 price triggers. Examine workload, waitlists, scope and delivery headroom. A higher price does not automatically reduce workload; actual demand and delivery responses need measurement.

The qualitative dimension concerns stating terms clearly, tolerating a customer's decision to decline, avoiding reflexive concessions and answering the questions actually asked. Connect it to M8.6 scripts and the M8.8 commitment without turning a business practice into a judgment of character.

Investigate the three patterns

The apologetic-quote pattern involves hesitant or qualified price delivery; the reflexive-discount pattern grants a concession before understanding the concern; the anchor-to-other pattern relies on competitors or prior customer spending without examining one's own costs and value.

These patterns can prompt practice and investigation. They do not establish a psychological cause, nor prove that market research is irrelevant. The source first emphasizes internal recalibration and later explicitly retains market signals. Both cost and customer evidence matter. If your policy genuinely permits flexibility, do not conceal it merely to sound declarative.

Practice all six tests without using them as a diagnosis

The quote test asks whether you can state the actual price clearly; the source's $5,625 example is not a RISER price. The silence test asks whether you allow processing time after stating it. The walk test asks whether you can respect a decision not to proceed at an unsustainable or unsuitable price.

The friend test asks whether you can explain consistent terms while honoring actual approved exceptions. The reflexive-discount test presents three responses—pause, explain value or immediately concede—even though the framework calls the tests binary. Observe what you do and whether it matches policy rather than inventing a diagnostic score. The year-end test examines whether your income and decisions align with your plan; it does not establish your personal worth or justify shaming yourself for the result.

Use a practice conversation to identify one behavior to improve and one economic assumption to verify. A customer can have a legitimate budget constraint, and a refusal to buy need not indicate a failure by either person.

Resolve the four common misreadings

First, the doctrine does not require the highest possible price. It allows revising price downward where evidence about economics and value warrants it. Second, it allows structural bulk, loyalty, strategic-partner, beta and remediation exceptions; it distinguishes those from unexplained concessions under pressure.

Third, it retains capacity utilization, waitlist depth and demand as market inputs. Fourth, it permits negotiation over scope, terms, timing and deliverables in complex arrangements. Its distinction between standard-price concessions and negotiation is a doctrinal definition, not a universal meaning of negotiation. Make the actual agreement and its economics clear.

Trace the framework through the source's module map

M8.1 introduces the four dimensions; M8.2 operationalizes cost; M8.3 tests all four against evidence; M8.4 organizes dimensions one through three; M8.5 refines value through tiers or a flat offer; M8.6 develops the conversational policy; M8.7 connects capacity to the raise schedule; and M8.8 integrates the commitments. Preserve these legacy references while using the curriculum spreadsheet's actual lesson assignments.

The closing language calls for a twelve-month auditable commitment. It is a proposed operator practice, not an attestation already signed or a test of a person's humanity. Record real decisions, evidence and amendments so the business policy is reviewable.

Apply the requested offer-education themes

As an authored Brunson-oriented application, maintain continuity between the customer's problem, the explanation and the offered next step. As an authored Hormozi-oriented application, clarify the desired outcome, evidence, delay and effort without making unsupported promises. Neither theme requires ignoring market signals or equating a high price with personal value.

Complete the exercise by documenting one observation and one unresolved question for each dimension, then explaining how your price and scope follow from the evidence. Keep the complete original framework available alongside these distinctions.

D0899 — complete original source

D0470-linked-D0899 — complete original source

Open source file · Download exact original file

# The Pricing-Is-Operator-Self-Respect Framework

**The C8 doctrine** · **Anchored in M8.1, applied throughout, signed at M8.8**

---

## The Doctrine

Pricing is the financial expression of:

1. **What it costs you to deliver the work** (your unit economics)
2. **The value the work delivers to the customer within your territory** (your mechanism's effect)
3. **The capacity you preserve for future work** (your sustainability)
4. **Your self-respect as an operator** (your willingness to ask for what the work is worth)

When any one of these dimensions is absent from pricing, pricing degrades.

When all four are present, pricing holds under pressure.

---

## Why "Self-Respect"

The framework's name is deliberate. Most pricing literature treats pricing as a market transaction or a value-capture exercise. The C8 framing adds a fourth dimension that other frameworks omit: pricing as the operator's stance toward themselves.

Operators who under-price are not always making a market mistake. Sometimes they are making a self-respect mistake — they have not internalized that their work is worth what it is worth, so they price it for less.

This is observable in three patterns:

**Pattern 1: The Apologetic Quote.** Operator delivers strong work, but when stating the price, voice softens, qualifications appear, the price is presented as a question rather than a statement. The customer reads the apology and pushes back, and the operator concedes.

**Pattern 2: The Reflexive Discount.** Operator quotes the price, customer says "that's a lot," operator immediately offers a discount before the customer has even pushed back. The discount is operator-initiated, not customer-extracted. Self-respect would require pausing.

**Pattern 3: The Anchor-to-Other.** Operator sets price by checking what competitors charge, what other operators in the field charge, what the customer has paid before. None of these anchors include the operator's own cost or value. Self-respect would require anchoring to the operator's own unit economics first.

The framework treats these three patterns as discipline failures, not market failures. The corrective is not market research; it is internal recalibration.

---

## The Four Dimensions, Operationally

### Dimension 1 — Cost-Anchored

Pricing must reflect what the work costs you to deliver, including hidden hours (Worksheet: Hidden Hours Audit). The C8 doctrine threshold is 60% gross margin minimum for knowledge-work offers. Below 60%, the operator is subsidizing the customer.

Operationalized through M8.2 Unit Economics Document and M8.4 Pricing Architecture sustainability margin path.

### Dimension 2 — Value-Anchored

Pricing must reflect the value delivered to the customer within your territory. Value is not "what they would pay" — value is "what change you produce in their world." If your mechanism produces X dollars of effect for the customer, your pricing should capture some fraction of X (typically 10-30% for direct measurable effects).

Operationalized through C2 mechanism specification and C7 mechanism evidence.

### Dimension 3 — Capacity-Anchored

Pricing must preserve the operator's capacity to continue delivering the work. Pricing that maximizes current revenue at the cost of operator burnout is not sustainable; it is short-term extraction from a long-term mechanism.

Operationalized through C7 capacity constraint analysis and the M8.7 Price-Raise Schedule (which fires raises as capacity tightens, preserving operator headroom).

### Dimension 4 — Self-Respect-Anchored

Pricing must reflect the operator's willingness to ask for what the work is worth. This dimension is internal and qualitative. It manifests in:

- The voice in which the price is stated (declarative, not apologetic)
- The willingness to let customers walk who don't accept the price
- The absence of reflexive discount-offering
- The absence of justification beyond what is asked

Operationalized through M8.6 Anti-Discount Policy scripts and the M8.8 Attestation discipline clause.

---

## Tests of Self-Respect Pricing

The framework can be tested. Six tests, each binary:

**Test 1 — The Quote Test:** When you state the price, do you state it as a fact or as a question? *("The price is $5,625" vs "The price is, um, $5,625, but we can talk about that.")*

**Test 2 — The Silence Test:** After stating the price, can you remain silent and wait for the customer's response? Or do you fill the silence with justification? Pricing self-respect tolerates silence.

**Test 3 — The Walk Test:** Can you say "I understand if this isn't the right fit at this price; I'd rather we both walk away than work together at a price that doesn't sustain me"? Operators who cannot say this are operating without Dimension 4.

**Test 4 — The Friend Test:** When a friend or peer asks for "friend pricing," can you decline cleanly? *("I don't have friend pricing because my pricing reflects my actual cost of delivery, not my relationship to the buyer.")*

**Test 5 — The Reflexive-Discount Test:** When a customer says "that's a lot," is your default response (a) silence, (b) restating the value, or (c) immediately offering a discount? Self-respect produces (a) or (b); under-respect produces (c).

**Test 6 — The Year-End Test:** At the end of the year, looking at your operator income, can you say "this is what my work was worth, and I asked for it"? Or do you say "I should have charged more, but I didn't have the spine"?

Operators who pass tests 1-6 are operating from self-respect. Operators who fail tests 1-6 are operating below their own value. C8 produces the operator who passes the tests.

---

## Common Misreadings of the Framework

**Misreading 1: "Self-respect means charging the highest possible price."** No. Self-respect means charging the price that reflects the four dimensions. Sometimes that's higher than what you're charging; occasionally it's lower (if you've over-priced relative to actual unit economics or value delivered). Self-respect is alignment with truth, not maximization.

**Misreading 2: "Self-respect means never discounting."** No. The Anti-Discount Policy (M8.6) has structural exceptions: bulk, loyalty, strategic, beta, operator-failure remediation. Discounts within these exceptions are consistent with self-respect because they are rule-based and structural. Self-respect is not anti-discount; it is anti-rationalized-discount-under-pressure.

**Misreading 3: "Self-respect means ignoring market signals."** No. Capacity utilization, waitlist depth, and demand signals (the M8.7 triggers) are market signals the operator listens to. Self-respect is not deafness to market; it is anchoring to multiple inputs (cost, value, capacity, self) rather than market alone.

**Misreading 4: "Self-respect means no negotiation ever."** Negotiation is part of complex deals (long contracts, partnership agreements, custom scope). Self-respect-aligned negotiation negotiates scope, terms, timing, deliverables — not the unit price of standard work without scope change. Negotiating standard pricing without scope change is concession, not negotiation.

---

## The Framework Across the C8 Modules

| Module | How the framework manifests |
|---|---|
| M8.1 | Conceptual orientation: introducing the four dimensions |
| M8.2 | Dimension 1 (cost) operationalized |
| M8.3 | All four dimensions tested against measured reality |
| M8.4 | Dimensions 1-3 architected into a system |
| M8.5 | Dimension 2 (value) refined via tier-or-flat decision |
| M8.6 | Dimension 4 (self-respect) operationalized as anti-discount discipline |
| M8.7 | Dimension 3 (capacity) operationalized as raise schedule |
| M8.8 | All four dimensions integrated and signed |

---

## Closing

Pricing is operator self-respect made auditable.

The Attestation is the audit trail.

Self-respect that is not auditable is not self-respect; it is intention. C8 produces the operator whose self-respect is recorded, signed, and held under pressure for 12 months.

---

*This framework is the doctrinal anchor of C8. Operators who internalize it produce different pricing than operators who treat C8 as a checklist. The internalization is the point.*

Supporting lesson: make a price-raise schedule testable

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Price-Raise Schedule Template. This explains the template without changing any business's prices or sending customer communications.

1. Establish the foundation

The source calls for a 1,000–1,500-word schedule, filed in Drive and linked from M8.8. Record measured M8.2 gross margin, the M8.4 target, the gap and a quarter-based deadline. A difference between margin percentages is a percentage-point gap, not the required percentage price increase. An actual plan needs cost, price and scope assumptions as well as its target.

2. Define all four triggers

The capacity example uses at least 80% utilization across a rolling ninety-day window, a 10% increase on new bookings, and current commitments honored through completion. The waitlist example uses at least six weeks of backlog at month-end and a 15% increase. The demand example uses at least twelve qualified inquiries each month for three consecutive months and a 10% increase. Define qualification and periods rather than counting every inquiry as demand from a suitable buyer.

The annual-indexing example uses January 15 and 4–7%, with sixty days' notice and the new rate at renewal. These figures are examples, not adopted RISER thresholds or current inflation facts. High utilization or a long waitlist can reflect process constraints, seasonality or restricted capacity; they do not alone prove underpricing. The source's claims about automatic skill growth and appropriate annual increases require evidence before being applied.

For every trigger, specify the threshold, observation window, magnitude and treatment of existing customers. Distinguish the decision date, announcement date and effective date.

3. Test the proposed schedule honestly

The source asks for twelve-month projections of each reading and instructs the operator to tighten triggers that would not fire. Test attainability, but do not manipulate a threshold merely to guarantee a predetermined increase. Record why the threshold is useful, the uncertainty in the projection and what would justify keeping it unchanged.

Check values just below, exactly at and just above each boundary. Also check conditions already true at adoption and the calendar-index date inside the actual twelve-month period. The claimed roughly 50% first-submission failure rate is unsupported in the supplied template.

4. Resolve the cap and indexing floor

The example imposes a 25% rolling twelve-month cap while allowing a 4% annual floor even at the cap, with other triggered increases queued. A hard cap and an override cannot both be absolute. State precedence and show whether the floor is permitted to exceed the nominal cap.

Define whether cap usage is additive or based on compounded price changes. Track when each prior increase leaves the rolling window and when queued actions become eligible; a rolling window is not automatically a calendar year. The source's rationale about customer perception is a hypothesis, not a guaranteed response.

5. Explain the customer communication

The communication table specifies lead time, channel, template, grandfathering and the M8.6 loyalty rule. Its examples are sixty days for renewals, thirty days for new engagements and direct email. The sample message states the offer, old and new prices, effective date and actual trigger reason, confirms the current engagement's price through completion and invites discussion.

Only claim sixty days' notice when that is true. Honor existing commitments and use the actual loyalty policy. The source discourages apology, but a courteous tone does not establish negotiability. Write clearly and respectfully; do not fabricate a capacity or inflation reason. This lesson provides instruction, not an email sent on the operator's behalf.

6. Define the operating commitment

The source's twelve-month clause calls for monthly Tab 4 readings and cap checks, execution within thirty days after firing, new engagements first, subsequent existing-customer communications, annual indexing and a deferral record in Supabase within 48 hours. The referenced database is not established by this template.

Reconcile the thirty-day execution target with a sixty-day customer notice requirement: announcing an increase and applying it to a renewal are different events. Do not use one deadline to override another commitment. Record deferrals honestly; only the operator can sign the discipline clause.

7. Check coherence before adopting a schedule

Confirm that the cap permits the M8.4 margin path, that existing-customer treatment agrees with M8.6, and that indexing assumptions have a stated basis. The source suggests inflation plus one to three percentage points of skill growth; that is a proposed doctrine, not a universally required rate or proof of real-term value growth.

For the exercise, trace one hypothetical trigger through observation, decision, cap, communication and effective date, including an already-true condition and a capped condition. In the requested Brunson/Hormozi teaching context, explain the offer and value clearly while keeping every timing and pricing promise consistent with the delivery plan. Keep the complete source schedule linked beside the exercise.

D0619 — complete original source

D0470-linked-D0619 — complete original source

Open source file · Download exact original file

# Price-Raise Schedule Template

**Used in:** M8.7 deliverable · **Length target:** 1,000-1,500 words · **Filed in:** Drive + linked from M8.8 Attestation

---

## Section 1 — Schedule Foundation

State the M8.4 architecture sustainability target margin and the M8.2 current measured margin. The gap between them is what this schedule is designed to close, in addition to handling capacity-driven raises and annual indexing.

| Metric | Value |
|---|---|
| M8.2 measured gross margin | % |
| M8.4 target sustainability margin | % |
| Gap to close | % |
| Target close-out window | Q+N |

---

## Section 2 — The Four Triggers

The schedule operates against four canonical trigger types. Each trigger has a threshold, a window, and a magnitude.

### Trigger 1 — Capacity Utilization

| Field | Value |
|---|---|
| Threshold | (e.g., ≥ 80% utilization across rolling 90-day window) |
| Measurement window | Rolling 90 days |
| Magnitude when fired | (e.g., +10% on new bookings) |
| Existing customer treatment | (Grandfathered through current commitment / next renewal at new price) |

Capacity utilization is the strongest signal that pricing is below market-clearing. When the operator runs at high utilization for extended periods, the price is too low. Raise the price.

### Trigger 2 — Waitlist Depth

| Field | Value |
|---|---|
| Threshold | (e.g., ≥ 6 weeks of bookings backlog) |
| Measurement window | Snapshot end-of-month |
| Magnitude when fired | (e.g., +15% on new bookings) |
| Existing customer treatment | |

Waitlist depth is the secondary capacity signal; it complements Trigger 1. When customers are waiting weeks to be served, price is below willingness-to-pay.

### Trigger 3 — Demand Signal

| Field | Value |
|---|---|
| Threshold | (e.g., ≥ 12 inbound qualified inquiries per month for ≥ 3 consecutive months) |
| Measurement window | Rolling 3 months |
| Magnitude when fired | (e.g., +10% on new bookings) |
| Existing customer treatment | |

Demand signal captures elevated inbound interest independent of capacity. When inbound is high but utilization is moderate (perhaps because the operator is throttling acceptance), the price can rise.

### Trigger 4 — Annual Indexing

| Field | Value |
|---|---|
| Threshold | Calendar date (e.g., January 15 each year) |
| Measurement window | N/A (date-based) |
| Magnitude when fired | (e.g., +4-7% covering inflation + skill compounding) |
| Existing customer treatment | (Communicated 60 days in advance; takes effect on next renewal) |

Annual indexing is the structural floor. It fires regardless of demand conditions. The function is to compensate for inflation and operator skill compounding (the operator at 12 months is more skilled than at 0 months and should price accordingly).

---

## Section 3 — Tightness Verification

For each trigger, project realistic Stage 2-3 conditions and verify the trigger fires within 12 months.

| Trigger | 12-month projected reading | Threshold | Will fire? |
|---|---|---|---|
| T1 — Capacity utilization | | | |
| T2 — Waitlist depth | | | |
| T3 — Demand signal | | | |
| T4 — Annual indexing | January 15, [year+1] | January 15 | Yes |

If any of T1-T3 are projected NOT to fire within 12 months, tighten the threshold until projection shows fire. Loose triggers are the most common M8.7 review failure (~50% of first submissions).

---

## Section 4 — Cumulative Cap

State the cumulative cap on raises within any rolling 12-month window.

| Field | Value |
|---|---|
| Cumulative cap | (e.g., +25% rolling 12-month) |
| Floor below cap | (e.g., +4% annual indexing always fires regardless of cumulative) |
| Behavior at cap | (Subsequent triggered raises queue to next 12-month window) |

The cap exists because aggressive cumulative raises damage customer perception. The floor exists because annual indexing must fire even in cap years.

---

## Section 5 — Existing Customer Communication Pattern

State the communication template for existing customers when raises fire.

| Element | Specification |
|---|---|
| Lead time | (e.g., 60 days advance notice for renewals; 30 days for new engagements) |
| Channel | (e.g., direct email, not bulk) |
| Template | (Provide template) |
| Grandfathering rules | (e.g., current commitment honored at original price; renewal at new price) |
| Loyalty exception | (Per M8.6 Section 2, not per ad-hoc decision) |

Provide a sample email template:

> *Subject: Pricing update for [offer name] effective [date]*
>
> *Hi [name],*
>
> *I'm writing to let you know that [offer name] pricing will increase from $[old] to $[new] effective [date]. The change reflects [trigger reason: capacity utilization / annual indexing / etc.]. Your current engagement at $[old] is honored through completion. Future engagements will be at $[new].*
>
> *I wanted to give you 60 days notice so you can plan accordingly. If you'd like to discuss, I'm available.*
>
> *[signature]*

The template is direct, specific, and does not apologize for the raise. Apologetic raise communications signal to customers that the raise is negotiable.

---

## Section 6 — Discipline Clause

The operator commits to specific behaviors:

> *I commit to operating this Price-Raise Schedule for the 12 months beginning [date]. I will:*
>
> *1. Update Pricing Math Spreadsheet Tab 4 monthly with current readings of T1-T3 and verify cumulative cap status.*
>
> *2. Execute fired raises within 30 days of fire-date, on new engagements first and existing-customer communications immediately following.*
>
> *3. Communicate raises to existing customers using the Section 5 template, with no apology and no negotiation invitation.*
>
> *4. File annual indexing on [date] regardless of demand conditions.*
>
> *5. Log any deferred raise with documented reason in Supabase deviation_log within 48 hours of the deferral.*
>
> *I understand that pricing discipline includes raising prices when conditions trigger raises, not only holding prices when conditions pressure discounts. The discipline is symmetric.*

---

## Section 7 — Schedule Coherence Check

State explicitly:

- Does the cumulative cap (Section 4) leave room for the M8.4 sustainability margin path (M8.4 Section 8)? If no, the schedule cannot deliver the architecture.
- Do the existing-customer communications (Section 5) align with the M8.6 anti-discount policy? Specifically, is grandfathering treated as a structural exception per M8.6 Section 2 or is it inadvertently treated as an ongoing discount?
- Does the annual indexing rate (Section 2 Trigger 4) at minimum cover inflation + 1-3% operator skill compounding? If not, indexing is a real-terms price decline.

These coherence questions are also asked at M8.8 Section 8.

---

*This schedule is the forward-looking commitment that enables M8.4 architecture to reach sustainability. Architecture without schedule is a frozen number that decays in real terms. Schedule with discipline is how price holds against time.*

Supporting lesson: build a coherent pricing architecture

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Pricing Architecture Document Template. The following explains all ten sections without adopting prices, payment terms or refund policies for RISER.

1. Gather the actual inputs

The template asks for 1,200–1,800 words, filed in Drive and linked from M8.8. Its inputs are the C7 Offer Architecture, M8.2 measured economics and M8.3 decision memo with the selected branch. A link to a blank template is not a completed operator artifact.

It targets 60% gross margin for knowledge-work offers or a documented approved deviation. Preserve this as source doctrine, not a universal break-even rule.

2. Specify price, unit and currency

State the base price, the unit purchased and the currency/exchange policy, with an evidence-based rationale. The source's $5,625 example claims 35% margin at 52 hours. That implies $3,656.25 total cost; the source does not supply the complete hourly/direct-cost basis here. If cost were entirely hourly, the implied rate would be $70.3125. Do not invent a missing cost input to make the example appear verified.

The same example describes an eighteen-month path to 60%, while Section 8 expects four quarters unless an alternative is approved. Flag and reconcile the difference. Competitive information may inform a decision alongside measured costs and customer value; it does not replace them.

3. Define payment terms

Complete deposit percentage and due date, final-payment percentage and due date, late-payment treatment and nonpayment treatment. The source's deposit doctrine is at least 25% for offers above $500; the strict condition does not include exactly $500. This is a proposed policy, not a legal requirement or adopted agreement.

Check the total of payment portions, the price basis and when each obligation arises. Do not describe a deposit's effect on commitment or risk as guaranteed for every customer.

4. Define the refund window and conditions

Record window length, its starting event, specified operator-failure triggers and non-trigger conditions. Fourteen days from kickoff is an example. Clear terms can reduce confusion, but the source does not establish that a non-trigger list prevents all pressure or overrides applicable commitments and remedies. No operational refund terms are created by filling an educational example.

5. Make segmentation explicit

The table covers standard customers, bulk/cohort buyers, long-tenure customers and strategic partners. Define eligibility, amount and approval instead of leaving the decision to unspecified discretion. The sample loyalty rule requires at least three prior deliveries and renewal within thirty days for 10% pricing. Preserve the example while requiring an actual economic rationale before adoption.

6. Read all four customer/scope combinations

The matrix gives new-standard work the base price, existing-standard work base or eligible loyalty pricing, and both new-custom and existing-custom work base plus a scope premium. It does not explicitly say whether loyalty and custom premiums combine. Resolve that question rather than inventing stacking behavior.

Define the work in each quadrant and distinguish an existing commitment from a future renewal. A matrix does not itself establish when a customer's prior agreement ends.

7. Test the illustrative premiums

The source suggests 10% of base for an added deliverable taking at most four hours, 20% for four to eight hours, a new quote above eight hours, 15% for timeline compression and a new quote for a custom integration. Exactly four hours appears in both first bands. Resolve that overlap explicitly before use.

Define whether timeline and deliverable premiums can combine and which base they use. Measure incremental work and capacity effects; a percentage does not automatically cover additional cost. The schedule is illustrative, and some requests require a coherent new quote rather than a preset surcharge.

8. Document the sustainability path

Show the current measured margin and projected margins for Q+1 through Q+4, with the action responsible for each change. The source mentions scope tightening and annual indexing. Projected efficiency is not achieved efficiency: specify what will be measured and the fallback if it does not occur.

If 60% is not reached within four quarters, the template calls for an explanation and approved alternative. Reconcile that instruction with the earlier eighteen-month example. Preserve the original numbers rather than quietly rewriting the source.

9. Complete the three cross-checks

Check whether base price produces the target margin or has a defined bridge; whether the average effective segmented price remains at least 92% of base; and whether scope premiums cover measured added work. The 92% condition concerns discount dilution, not gross margin.

In an authored simplified example with only full-price and 10%-discounted sales of identical scope, an 80% discounted mix produces 92% of base on average. That calculation changes with other discounts, refunds, currency effects and scope. Use the actual weighted mix rather than assuming the average from a list of customer types.

10. Sign only a defined, reviewable architecture

The source proposes version 1.0 for twelve months, subject to M8.7 triggers and M8.8 deviation logging. Only the operator signs. M8.5 tiers, M8.6 policy and M8.7 schedule must reference the same actual architecture.

For the exercise, follow one standard and one custom engagement through price, eligibility, premium, payment, refund conditions and margin. List every unresolved boundary. As an authored Brunson/Hormozi application, a clear offer and supportable value should agree with these operating details; persuasive language cannot reconcile incompatible terms. Keep the original ten-section template available in the lesson resources.

D0620 — complete original source

D0470-linked-D0620 — complete original source

Open source file · Download exact original file

# Pricing Architecture Document Template

**Used in:** M8.4 deliverable · **Length target:** 1,200-1,800 words · **Filed in:** Drive + linked from M8.8 Attestation

---

## Section 1 — Architecture Inputs

Reference the prior artifacts this architecture is built upon:

- C7 Offer Architecture Document (link)
- M8.2 Unit Economics Document (link, including measured gross margin and effective rate)
- M8.3 Pricing Reality Check Decision Memo (link, including selected decision branch)

State the C8 doctrine threshold the architecture targets: **60% gross margin minimum for knowledge-work offers** (or document the deviation if targeting lower with instructor approval).

---

## Section 2 — Base Price Specification

| Field | Value | Rationale |
|---|---|---|
| Base price | $ | Why this number specifically |
| Base unit | (e.g., "per Sprint", "per individual seat") | What the price covers |
| Currency and exchange policy | | If serving multi-currency markets |

The rationale must reference unit economics. Acceptable rationale: "Base price of $5,625 produces 35% gross margin against measured 52-hour delivery cost; M8.7 schedule fires path to 60% margin within 18 months." Unacceptable rationale: "Competitive pricing in the market." Pricing is not set against competitor pricing without reference to your unit economics; that is anchor-to-other not anchor-to-cost.

---

## Section 3 — Payment Terms

| Field | Value |
|---|---|
| Deposit % | |
| Deposit due | |
| Final payment % | |
| Final payment due | |
| Late payment treatment | |
| Failure-to-pay treatment | |

The deposit serves two functions: cash-flow management and customer commitment device. C8 doctrine: deposits ≥ 25% for offers > $500. Below-25% deposits leave the operator carrying customer risk that should sit with the customer.

---

## Section 4 — Refund Window and Triggers

| Field | Value |
|---|---|
| Refund window length | (e.g., 14 days from start) |
| Refund window start condition | (e.g., "from kickoff call") |
| Refund triggers | List specific operator failures that trigger refund |
| Non-trigger conditions | List conditions that explicitly do NOT trigger refund |

The refund non-trigger list is critical. Operators with vague refund policies grant refunds under customer pressure. Specifying non-triggers in advance ("change of customer business priorities does not trigger refund") prevents pressure-based refunds.

---

## Section 5 — Segmentation Rules

| Customer type | Pricing treatment |
|---|---|
| Standard | Base price as specified Section 2 |
| Bulk / cohort | If applicable; specify threshold and discount |
| Long-tenure existing | If applicable; specify treatment |
| Strategic / partnership | If applicable; specify approval workflow |

Segmentation must be **rules-based**, not discretionary. "I might offer a discount to long-time customers" is not a rule. "Customers with ≥ 3 prior deliveries who renew within 30 days of last delivery receive 10% loyalty pricing" is a rule. Rules-based segmentation is auditable and defensible; discretionary segmentation is not.

---

## Section 6 — Four-Quadrant Pricing Matrix

| | New customer | Existing customer |
|---|---|---|
| **Standard scope** | Base price (Section 2) | Base price or loyalty pricing per Section 5 |
| **Custom scope** | Base price + scope premium per Section 7 | Base price + scope premium |

Specify what falls in each quadrant. The matrix prevents the most common pricing failure: existing customers paying legacy rates while new customers pay current rates, with the operator having no documented policy for when the legacy rate ends.

---

## Section 7 — Scope Premium Schedule

When custom scope is requested, the premium is calculated:

| Custom scope category | Premium |
|---|---|
| Additional deliverable (≤ 4 hours added) | +10% base price |
| Additional deliverable (4-8 hours added) | +20% base price |
| Major scope expansion (> 8 hours added) | Re-quote required, not a premium |
| Timeline compression (< standard timeline) | +15% base price |
| Custom integration / one-off requirement | Re-quote required |

The schedule is illustrative. Each operator builds their own based on M8.2 actual hours data. The function of the schedule is to make scope-creep pricing automatic rather than negotiated.

---

## Section 8 — Sustainability Margin Path

State the current margin (M8.2) and the target margin (60% minimum). State the path:

| Quarter | Projected margin | How achieved |
|---|---|---|
| Q current | (M8.2 actual) | — |
| Q+1 | | (e.g., scope tightening per C7 v2.0 specification) |
| Q+2 | | |
| Q+3 | | |
| Q+4 | | (M8.7 annual indexing fires) |

If the path does not reach 60% within 4 quarters, document the reason and the alternative target with instructor approval.

---

## Section 9 — Architecture Coherence Check

State explicitly:

- Does the base price (Section 2) produce ≥ 60% margin against M8.2 unit economics? If no, what is the bridge?
- Do the segmentation rules (Section 5) produce average effective price ≥ base price × 0.92? If no, the segmentation system erodes the base price.
- Does the scope premium schedule (Section 7) cover the average scope-creep load measured in C7? If no, the schedule under-prices scope.

These three coherence questions are also asked at M8.8 Section 8 (cross-artifact coherence). Answering them at M8.4 prevents M8.8 surprises.

---

## Section 10 — Operator Sign-Off

Suggested:

> *This Pricing Architecture v1.0 will operate from [date] through the next 12 months absent triggered changes per M8.7 schedule. I understand that this architecture is the price I charge, not the price I sometimes charge. Deviations will be logged per M8.8 Section 9.*

---

*This template produces the structural foundation that M8.5 (tiers), M8.6 (anti-discount), and M8.7 (raises) all reference. Subsequent modules cannot succeed against a vague Architecture Document.*

Communicating a price change with clear terms and real choices

Supporting lesson for D0470. Source: Raise Communication Swipe File. Its legacy M8.7 label does not change spreadsheet lesson assignments.

Outcome and opening

By the end, you can choose among seven communication patterns, explain the actual trigger for a change, distinguish existing work from new commitments, and offer a transition your business can honor. The source calls this “announce, don't apologize.” Treat that as a communication preference, not proof that confident language establishes a fair price or guarantees acceptance. A customer can decline, ask questions or point out an existing commitment.

Start with the decision and its evidence. State the offer, old price, new price, percentage and effective date. Calculate the increase as (new minus old) divided by old, multiplied by 100; a zero old price requires a different explanation. Verify that a described demand increase, delivery-cost increase or inflation adjustment is supported. The source supplies templates, not your business's measured facts.

This fits our Brunson and Hormozi teaching themes through a clear offer, defined value, specific scope and credible reasons to act. That connection is our instructional application; it does not mean either educator authored these templates. Use genuine deadlines and capacity rather than inventing urgency.

1. Annual indexing: make the routine update explicit

Use the annual pattern for the schedule's fourth trigger. The subject identifies the offer and effective date. The opening gives the old and new amounts and percentage, then names the chosen reason: inflation, accumulated skill or market conditions. Explain that the current engagement retains its agreed price through completion and future engagements use the new price.

The example gives 60 days' notice and allows old-rate booking for work starting before the effective date. End warmly. Its five teaching points are early disclosure, magnitude and trigger, protection against surprise, a defined transition and a courteous close. Avoid unnecessary apology, seeking permission for an already decided future offer, or an open-ended promise to renegotiate. Still answer genuine questions and correct errors.

Notice the condition: this example uses the work's start date. Later examples use the commitment date. Those conditions are different; choose and state one operational rule rather than mixing them.

2. Capacity or waitlist: explain the constraint

Use the capacity pattern for trigger one or two. Identify the period during which demand exceeded delivery capacity, then state the effective date and new-engagement price. Preserve the current engagement's terms. The source offers old pricing for work committed by a deadline 30–60 days away, after which standard pricing applies.

Teach the distinction between discussing the customer's timing or scope and making the same scope cheaper. This template explicitly invites discussion. Check delivery capacity before inviting advance bookings; a transition window should not create commitments the team cannot fulfill. The source does not establish that every business has excess demand.

3. Inbound demand: describe the signal without overstating it

The third pattern responds to inquiry volume. State the observed period, old and new rates, percentage, unchanged current work and the cutoff for new commitments at the prior rate. The source says customers may find this reason less persuasive and advises a short explanation rather than a defensive essay.

An increase in inquiries alone does not establish the market-clearing price. Review inquiry quality, conversion and actual delivery economics before adopting that claim. In the message, describe the evidence you have rather than presenting an inference as a measured conclusion.

4. Added scope: obtain agreement before doing added work

The fourth pattern is a scope adjustment, not a retroactive increase for unchanged work. Its subject names the project. Recap the requested addition, original price and original scope. Describe the additional hours or deliverables, added charge, pricing rule and revised total. Ask for confirmation before proceeding and make the original-scope option a real choice. An addition required to deliver the original promise cannot honestly be called optional.

The example references a 10% base-price premium for additions of at most four hours, 20% for four to eight hours and a fresh quote for major changes. Exactly four hours appears in both bands. Resolve that boundary in the operating policy before quoting; do not silently choose a band. The source also leaves some stacking and major-change definitions to the architecture. The teaching point is concrete scope and explicit agreement, not automatic use of an ambiguous schedule or quietly absorbing extra work.

5. Loyalty pricing: verify the structural qualification

Lead with the current standard rate. Identify the customer's engagement count and renewal window, then give the qualifying loyalty price and its percentage reduction. State the engagement total and unchanged standard terms, and request confirmation before sending details.

This pattern uses the standard rate as the reference and explains why the customer qualifies. Fill placeholders from the actual policy; the swipe file does not itself establish a universal qualifying count or window. Apply documented conditions consistently instead of inventing a personal concession during the conversation.

6. Pushback: offer three specific paths

First acknowledge the budget concern. Explain the chosen pricing policy and its connection to sustainable delivery. The source's statement that negotiating with one customer means negotiating with everyone is a consistency rationale, not a literal unavoidable consequence.

Present all three paths: continue at the new rate; remove a named deliverable and quote genuinely smaller scope; or pause. Make the pause legitimate rather than shaming the customer. Do not promise indefinite availability when future capacity is uncertain. Avoid “let me see what I can do,” “just this once,” or a vague middle ground if those phrases imply a concession you do not intend to offer. Specific alternatives remain compatible with listening to the customer.

7. A substantial increase: add context, not unsupported claims

The seventh pattern is labeled for increases above 15%. Call the change substantial, state amounts, percentage and date, and explain measured delivery costs and outcome value only when supported. Honor current engagements. The example permits new commitments at the old price for 60 days, then applies the new rate. Acknowledge that the change matters and leave room for conversation.

Its commentary contrasts 60 days for substantial increases with 30 for routine ones, but the annual template itself specifies 60 days and the capacity template says 30–60. These are inconsistent example windows, not one established notice rule. Align the final message with the actual schedule and existing commitments. Also reconcile the earlier schedule's 30-day execution target with its 60-day customer notice; an internal execution target cannot silently erase a promised transition.

8. Recognize five communication problems

The apologetic raise centers being forced, sorry and unfortunate rather than explaining a decision. The hedge says the price might change without a decided date or amount. The justification spiral piles up reasons and requests reassurance; the source suggests keeping reasons to about three sentences, a writing heuristic rather than a universal limit. The negotiation invitation vaguely offers alternatives without specifying real choices. The buried raise hides the price change among unrelated updates.

Revise each by placing the decision early, using verified reasons, defining dates and conditions, and naming available choices. The source predicts how customers interpret each pattern; these are coaching interpretations, not diagnoses of the sender or guarantees about the reader. Courtesy and an appropriate apology for an actual mistake can coexist with clear pricing.

9. Practice and finished exercise

Complete all five source practice steps: read aloud; count unnecessary apologies; remove hedges around decisions that are actually final; verify the transition window; and finish the communication promptly. The source targets zero apologies but explicitly permits one specific apology such as short notice; two or more prompts revision. Do not remove honest uncertainty merely to sound certain. Verify that booking conditions, dates and capacity support the window before making it an offer.

For the exercise, select the applicable template and write the entire message with no unresolved placeholders. Add a private evidence note for the trigger, arithmetic, existing-work treatment, deadline condition, scope choice and loyalty eligibility if applicable. Read it aloud, then check it against the policy and commitments. Sending an actual customer message is a separate business action; this training exercise does not send one.

The final check is consistency: the price statement, delivery promise, scope boundaries and transition must describe the same offer. Keep all seven original templates, their commentary, five anti-pattern examples and five practice steps in the linked full-source appendix when this lesson is assembled.

D0510 — complete original source

D0470-linked-D0510 — complete original source

Open source file · Download exact original file

# Raise Communication Swipe File

**Used in:** M8.7 Section 5 (existing-customer communication), live raise execution · **Customize for your voice; do not apologize**

---

## Purpose

When a price raise fires per the M8.7 schedule, existing customers must be notified. The communication is the moment most operators undermine the raise — through apology, hedging, or invitation to negotiate.

These templates are direct, specific, and non-apologetic. The raise is a fact, not a request. Customers read confidence; confidence requires direct language.

The principle: **announce, don't apologize.** A raise that's apologized for is a raise that's negotiable. A raise that's announced is a raise that's already happened.

---

## Template 1 — Annual Indexing (Routine, Date-Based)

For Trigger 4 (annual indexing) — the routine yearly raise.

**Subject:** Pricing update for [offer name] effective [date]

> *Hi [name],*
>
> *I'm writing with my annual pricing update. Effective [date], [offer name] pricing will move from $[old] to $[new] — a [X]% increase reflecting [inflation / skill compounding / market reality].*
>
> *Your current engagement at $[old] is honored through completion. Future engagements will be at $[new].*
>
> *I wanted to give you 60 days notice so you can plan accordingly. If you'd like to renew at the current rate before [effective date], let me know — I can still book engagements at $[old] for work starting before that date.*
>
> *Thanks for being part of the work this year.*
>
> *[signature]*

**What this does right:**
- States the change as a fact in the first sentence
- Names the magnitude and the trigger
- Honors current engagement (preventing customer surprise)
- Offers a 60-day window for booking at current rate (creates urgency, not negotiation)
- Closes warmly without apologizing

**What this avoids:**
- "I'm sorry to have to do this..." (don't apologize for indexing)
- "I hope you understand..." (you don't need permission)
- "Let me know if this is a problem..." (it's not a negotiation)

---

## Template 2 — Capacity-Triggered Raise

For Trigger 1 (capacity utilization) or Trigger 2 (waitlist depth). The raise responds to demand exceeding capacity.

**Subject:** Pricing update for [offer name] — new bookings effective [date]

> *Hi [name],*
>
> *Demand for [offer name] has consistently exceeded my delivery capacity over the past [period], which is the trigger I use to update pricing.*
>
> *Effective [date], new engagements move from $[old] to $[new]. Your current engagement at $[old] is honored through completion.*
>
> *If you're considering a future engagement, two notes:*
>
> *1. I can still book new work at $[old] if the engagement is committed by [deadline 30-60 days out].*
>
> *2. After [deadline], standard pricing applies.*
>
> *Happy to discuss what makes sense for your situation. Thanks for the work we've done together.*
>
> *[signature]*

**What this does right:**
- Names the trigger explicitly (transparent, not arbitrary)
- Distinguishes "current engagement" from "new engagements"
- Provides a window for booking at current rate
- Invites discussion without inviting negotiation

---

## Template 3 — Demand-Signal Raise

For Trigger 3 (demand signal — inbound inquiry volume).

**Subject:** Pricing update for [offer name] effective [date]

> *Hi [name],*
>
> *Inbound demand for [offer name] has grown substantially over [period], which I use as a signal that current pricing is below the market-clearing rate.*
>
> *Effective [date], pricing moves to $[new] from $[old], a [X]% increase. Your current work at $[old] continues unchanged.*
>
> *I'm letting you know early so that if you're considering additional engagements, you can decide whether to book before or after the change. New engagements committed by [deadline] are at current pricing; after that, the new rate applies.*
>
> *[signature]*

**Note on tone:** Customers sometimes find demand-triggered raises feel less justified than capacity-triggered or indexing raises. Resist the urge to over-explain. The transparency of the trigger ("inbound demand has grown substantially") is sufficient. Don't apologize for being in demand.

---

## Template 4 — Mid-Engagement Scope Change Repricing

When an existing engagement's scope expands beyond original specification, the additional scope is priced at current rates per Pricing Architecture Section 7.

**Subject:** Scope adjustment and pricing for [project name]

> *Hi [name],*
>
> *Following our conversation about [scope addition], I'm writing to confirm pricing for the additional scope.*
>
> *The original engagement at $[original] covers [original scope]. The addition — [scope addition] — is approximately [N hours / N deliverables] beyond original scope and prices at $[addition price] per the scope premium schedule (10% of base for additions ≤ 4 hours / 20% for 4-8 hours / re-quote for major).*
>
> *Total revised engagement: $[original + addition].*
>
> *Confirm by reply and I'll proceed; if you'd prefer to keep the engagement at original scope, that's also a clean choice — the addition is genuinely optional, not required for the original deliverable.*
>
> *[signature]*

**What this does right:**
- Names the addition in concrete terms
- References the schedule explicitly (transparent, rule-based)
- Gives the customer the clean choice to decline (no pressure)
- Avoids "I'll just include it" — which is the absorption failure mode

---

## Template 5 — Loyalty Pricing Confirmation (When Customer Qualifies)

For existing customers who meet the structural loyalty conditions per M8.6 Section 2.

**Subject:** Renewal pricing for [offer name]

> *Hi [name],*
>
> *I'm pulling together the engagement for [next project / period]. A few notes on pricing:*
>
> *Current standard rate for [offer name] is $[new]. Because this is your [Nth] engagement and falls within the [renewal window], the loyalty rate of $[loyalty] applies — that's a [X]% reduction from standard, structural for customers in your engagement pattern.*
>
> *Total engagement: $[loyalty]. Terms otherwise as standard.*
>
> *Confirm by reply and I'll send the engagement details.*
>
> *[signature]*

**What this does right:**
- States standard rate first (anchor)
- Names the loyalty discount as structural, not discretionary
- Specifies the qualifying condition (transparency about why it applies)
- Doesn't invite "can you do better" — the loyalty rate is the structural answer, and there's nothing further to give

---

## Template 6 — Decline of Negotiation After Raise

Sometimes a raised customer pushes back. They saw the new price, they want the old price, they're asking nicely.

**Response:**

> *Hi [name],*
>
> *I hear you on budget. The new rate is the rate, and I'm not going to negotiate it — not because I don't value the relationship (I do), but because if I negotiate it for you, I have to negotiate it for everyone, and the discipline of consistent pricing is part of how I sustain quality over time.*
>
> *Three options that are real:*
>
> *1. Continue at the new rate. I'd love to keep working with you.*
>
> *2. Reduce scope. If we drop [specific deliverable], I can work at a lower price point that reflects the smaller scope.*
>
> *3. Pause. If now isn't the right time, the offer is here whenever it is.*
>
> *None of these is a wrong answer. Let me know which fits.*
>
> *[signature]*

**What this does right:**
- Acknowledges the request without conceding
- States the principle ("if I negotiate for you, I negotiate for everyone")
- Offers three real options including walk-away
- Treats walk-away as legitimate, not failure

**What this avoids:**
- "Let me see what I can do" (the entry point to concession)
- "Just this once" (sets precedent for future negotiation)
- "Maybe we can find a middle ground" (signals negotiability of all future raises)

---

## Template 7 — Communication of a Substantial Raise (>15%)

When a raise is large — typically because the operator has been substantially under-priced — the communication needs more context. But more context, not more apology.

**Subject:** Significant pricing update for [offer name] effective [date]

> *Hi [name],*
>
> *I want to give you direct notice of a substantial pricing change.*
>
> *Effective [date], [offer name] moves from $[old] to $[new], a [X]% increase. The reason is straightforward: my measured cost of delivery and the market value of the outcome have grown substantially relative to my prior pricing, and I've been under-priced as a result.*
>
> *Your current engagement at $[old] is honored. Future engagements are at $[new].*
>
> *I know this is a meaningful change. Two windows that may help:*
>
> *1. New engagements committed by [deadline 60 days out] are at current pricing of $[old]. Use this window if you have planned work.*
>
> *2. After [deadline], standard pricing of $[new] applies.*
>
> *I'd rather give you direct notice and a window than ease into it. The new rate reflects the value of the work, and I've waited longer than I should have to reset it.*
>
> *Happy to talk if useful. Thanks for the trust.*
>
> *[signature]*

**Why this works for substantial raises:**
- Names the magnitude explicitly ("substantial," "[X]%")
- States the reason in operator terms, not customer terms ("I've been under-priced")
- Honors current engagements (prevents shock)
- Provides a substantial booking window (60 days for substantial raises vs 30 for routine)
- Closes by acknowledging the relationship without over-justifying

---

## Anti-Patterns: What Not to Send

### Anti-pattern 1 — The Apologetic Raise

> *Hi [name], I'm so sorry to have to do this, but unfortunately my costs have gone up and I'm being forced to raise prices...*

**Why it fails:** The customer reads "forced," "sorry," and "unfortunately" as signals that the operator doesn't believe in the raise. If the operator doesn't believe in the raise, why should the customer accept it? Apologetic raises invite negotiation.

### Anti-pattern 2 — The Hedge

> *Hi [name], I might need to raise prices soon. I'm not sure exactly, but probably around [X]%. Let me know how you feel about that...*

**Why it fails:** Tentative communication signals that the raise isn't decided. The customer correctly responds by negotiating against an undecided raise.

### Anti-pattern 3 — The Justification Spiral

> *Hi [name], my costs are going up because of inflation and software fees and my time is more valuable now and I've been thinking about this for months and I really need to do this and I hope you understand...*

**Why it fails:** Excessive justification reads as guilt. Three sentences of justification is plenty; a paragraph of justification signals operator self-doubt.

### Anti-pattern 4 — The Negotiation Invitation

> *Hi [name], pricing is moving to $[new]. Let me know if that works for you or if we need to discuss alternatives.*

**Why it fails:** "If we need to discuss alternatives" invites negotiation that wasn't on offer. Either offer specific alternatives (Template 6) or don't open the door.

### Anti-pattern 5 — The Bury

> *Hi [name], hope you're well! Quick update on a few things... [paragraph about other topics] ... oh, and pricing is going up to $[new]. Anyway, looking forward to our next call!*

**Why it fails:** Burying the raise in casual chat reads as if the operator hopes the customer won't notice. The customer notices. Direct communication respects the relationship; buried communication erodes it.

---

## Practice Protocol

Before sending any raise communication:

1. **Read it aloud.** If it sounds apologetic, rewrite.
2. **Count the apologies.** Zero is the target. One is acceptable if specific (e.g., "sorry for the short notice"). Two or more means rewrite.
3. **Look for hedges.** "Maybe," "perhaps," "I think," "probably." Cut them.
4. **Verify the offer of windows.** Most templates include a booking window for current pricing — make sure yours does, since this is what converts the raise from "imposition" to "transition."
5. **Sign and send.** Don't sit on the email for days; sitting erodes resolve.

---

*The communication itself is the discipline. Operators who can write and send these emails directly are operators whose pricing holds. Operators who can't are operators whose schedule lives on paper but doesn't fire in practice.*

From pricing measurements to a quarterly review record

Supporting source: Pricing Math Spreadsheet — Integration Walkthrough. Legacy M8/C7/C9 and Build6 labels describe the source's system, not replacement assignments for the twelve-course curriculum.

What this workflow produces

The spreadsheet is the working calculation tool. The proposed `c8_pricing_calculations` database table is the quarterly review record. The walkthrough intends to connect measured delivery economics, pricing policy and raise activity to human review and distribution readiness. It supplies a specification and example insert, not proof of an installed integration.

Our direct-marketing application is to connect the offer's promise to the cost and capacity required to deliver it. Clear scope and measured value support the Brunson and Hormozi themes used throughout this curriculum. Database completion alone does not validate the offer or prove demand, and neither educator is identified as this walkthrough's author.

The source estimates initial setup at 30–45 minutes and quarterly reviews at 60–90 minutes. Those are planning suggestions, not measured execution times for your system.

1. Set up all five working tabs

Begin with the Pricing Math Spreadsheet Template. It is a Markdown specification for a workbook. Create Unit Economics with one row per delivery; Pricing Architecture with the current architecture state; Anti-Discount Policy Compliance with one row per pricing interaction; Price-Raise Trigger Tracker with the triggers; and Quarterly Reconciliation with one row per quarter. The source favors Google Sheets for eventual integration and describes Excel's CSV export route. Neither route is connected merely by creating tabs.

Populate Unit Economics with all measured deliveries in the selected period: quoted price, quoted hours, actual hours, categorized hidden hours, loaded rate, direct costs and overhead. The Hidden Hours Audit Worksheet helps identify omitted work. Reconcile actual hours and hidden hours so each hour is counted once. Do not blindly inherit the underlying template's stated-hours formula: using the wrong input produces a wrong total even if the spreadsheet calculates without error. Distinguish quoted price from actual revenue when reporting realized economics.

After architecture review, record base price; deposit percentage and payment schedule; refund window, triggers and non-triggers; tier prices or the flat price; intended tier mix; and the sustainability-margin target. The source uses 60% as a knowledge-work target. That is its benchmark, not a universal break-even condition.

Initialize the compliance log when the policy is cleared. For each pressure interaction record date, customer, request type, exception classification, action and a binary score: one for behavior matching the policy, zero for deviation. A permitted exception can be compliant. Part A incorrectly calls zero-score rows divided by total rows the compliance rate. That fraction is the deviation rate. Compliance is the mean of the binary scores, or one minus the deviation fraction, converted to a percentage. No interactions means no observed rate; do not manufacture a 100% score.

Initialize four trigger records after schedule review. T1 capacity, T2 waitlist and T3 demand each need threshold, window, magnitude and current reading. T4 annual indexing needs its date and magnitude. Update T1–T3 monthly. The source leaves the first quarterly row empty until 90 days after its M8.8 co-sign milestone; that milestone and its attestation are prerequisites, not existing records established by this document.

2. Prepare the quarterly review

Reserve 90 minutes for the first one or two reconciliations and approximately 60 after experience, as the source suggests. Add every delivery completed in the quarter using measured time. Review T1 over a rolling 90 days; T2 at month end; T3 over a rolling three months; and T4 against the annual date. Record whether a trigger fired and when, separating firing from execution of a price change.

Define the quarter's start and end, which records belong to it, and whether each metric uses a quarterly or rolling window. A lifetime trigger count is not a quarterly count, and a quarterly increase total does not by itself verify a rolling annual cap.

3. Calculate all nine reconciliation metrics

The source's metric table specifies the following measures. Preserve these definitions alongside any corrected or additional measure so reviewers can compare like with like.

MeasureSource instructionReview needed
Average gross margin percentageAverage Tab1 column N for the quarterA mean of delivery percentages differs from total gross profit divided by total revenue. Label the selected measure.
Average effective rateAverage Tab1 column OA mean of per-delivery rates differs from total relevant revenue divided by total actual hours. Preserve the rate's cost/revenue definition.
Actual tier mixCount deliveries by tier divided by totalThe underlying template needs an explicit tier input and a defined denominator.
Tier-mix varianceActual minus target in percentage pointsDefine each tier and how several variances become any single reported value.
Anti-discount complianceAverage Tab3 column GUse policy-match scores, quarter filters and an explicit no-interaction result.
Triggers firedCount Y in Tab4 column DCount relevant firing events, not stale flags from earlier quarters.
Raises executedCount populated Tab4 column FExclude headers and unrelated history; verify execution dates.
Cumulative raise percentageSum Tab4 column GRepeated increases compound. Keep an additive source measure labeled separately from actual cumulative price change.
Deviation entriesManual count from databaseReconcile with the interaction log and the same reporting period.

For an authored arithmetic illustration, two successive 5% increases produce 1.05 × 1.05 − 1 = 10.25%, not 10%. A discrepancy in any denominator, percentage scale or period must be resolved before using the value for readiness.

4. Write the full one-page memo

Include all eight source sections: metrics; trigger activity and cap status; compliance with deviations and reasons; actual versus target tier mix and drift; progress toward the architecture's sustainability target and time to target; deviations recorded in the quarter; next-quarter decisions such as further review or schedule adjustment; and operator sign-off with date.

Explain the evidence behind the numbers. A disappointing quarter described accurately is more useful than an unsupported success statement. A metric row without its memo is incomplete under this source's workflow. The source calls the memo URL required, but a requirement in prose does not prove the database enforces it.

5. Understand the two proposed recording methods

The manual route opens the dashboard, selects `c8_pricing_calculations`, and inserts quarterly metrics with the memo URL and attestation ID. The example program imports `os` and a Supabase client, reads `SUPABASE_URL` and `SUPABASE_KEY`, builds a reconciliation object, then invokes an insert followed by execute. Its complete original code belongs in the appendix; it has not been run for this curriculum.

The example object includes user and attestation IDs; quarter label Q3-2026; dates July1 through September30; average margin38.5; effective rate108.20; tier mix standard65, entry25, premium10; variance5 percentage points; compliance100; one trigger; one executed raise; cumulative raise5%; zero deviations; a memo URL; and a memo summary claiming progress toward60% margin, a month7 trigger, execution within30days and zero deviations. These are illustrative values, not your measured results. The unexplained month7 reference should not be repeated as evidence about this quarter. The ellipsis in the sample Drive URL is a placeholder, not a usable resource link.

The excerpt leaves USER_ID and ATTESTATION_ID undefined. It does not create the table or show column types, access policies, computed-field logic, installed client version, duplicate prevention or validation of the stored result. Therefore it is not a complete deployable integration. Preserve those missing prerequisites rather than inventing a working system. A real implementation would need its current technical requirements verified separately before use.

6. Read the readiness rule precisely

The source says a computed `distribution_ready_flag` is true when deviation count equals zero, compliance is at least95%, and tier-mix variance is at most15percentage points. Otherwise the quarter does not advance C9 readiness; two consecutive false quarters call for instructor review.

The automatic computation and routing are asserted, not implemented in the supplied excerpt. Moreover, a signed variance of minus30 is numerically below15 even though it represents a large deviation. Clarify whether the intended rule uses absolute variance, maximum per-tier deviation or another defined statistic. Also clarify whether percentage values use0–100 or0–1. A labeled source rule and an unresolved implementation question are more accurate than declaring the flag operational.

7. Diagnose all five common issues

First, imported hours may differ because of copying or rounding. The source proposes Sheets ImportRange or an Excel query; the connection and source ranges still need configuration. Compare imported values to measurements rather than assuming the import method proves accuracy.

Second, an effective-rate formula may reference stated hours. The source directs it to total-hours columnI, but verify that columnI itself uses the correct actual and hidden-hour logic.

Third, the spreadsheet may show100% compliance while the database contains deviations. Reconcile both records. The source calls for synchronous updates but then proposes a weekly30-minute manual copying habit. State the actual update cadence and the resulting delay honestly.

Fourth, no trigger may fire. The source recommends instructor review and tighter thresholds. Investigate measurement, demand and capacity first; absence of a trigger does not itself prove thresholds are wrong or justify changing them solely to force a price increase.

Fifth, a row may exist without a memo. Finish the review narrative and its accessible reference before treating the reconciliation as complete.

8. Maintain the record between reviews

Follow all five source habits: update delivery and interaction records as events occur and trigger readings monthly; avoid falsifying the timing of entries; write an honest memo; make the review visible to the designated instructor through the business's approved process; and do not skip quarters. The source specifically warns that two missing quarters make year-end assessment unreliable.

Keep the date the event occurred separate from the date it was entered. If an event occurred14days ago, retain that occurrence date and record today's entry timestamp rather than disguising delayed entry. Describing instructor visibility here does not send a message.

For the exercise, assemble one clearly labeled sample quarter, all nine measures, all eight memo sections, a list of unresolved schema/readiness definitions and a reconciliation of the two logs. Identify what is actually present versus still proposed. The source's closing thesis is that routine spreadsheet work produces a reliable record; tool usage alone is not evidence of an operator's integrity or of complete data.

D1370 — complete original source

D0470-linked-D1370 — complete original source

Open source file · Download exact original file

# Pricing Math Spreadsheet — Integration Walkthrough

**Walkthrough for connecting the Pricing Math Spreadsheet to Supabase c8_pricing_calculations · Time: 30-45 minutes · Required at: M8.2 setup, then quarterly**

---

## Purpose

The Pricing Math Spreadsheet (Resources/Templates) lives in Google Sheets or Excel. The Supabase c8_pricing_calculations table holds the quarterly reconciliation data that Build 6 reads for distribution-readiness checks.

This walkthrough connects the two: the operator works in their spreadsheet, and quarterly metrics flow into Supabase for HITL review and C9 readiness assessment.

---

## Part A — Initial Setup at M8.2

### Step 1: Create the spreadsheet

Build the spreadsheet per the Pricing-Math-Spreadsheet-Template.md specification. Five tabs:

1. Unit Economics (per-delivery rows)
2. Pricing Architecture (one row, current architecture state)
3. Anti-Discount Policy Compliance (per-interaction log)
4. Price-Raise Trigger Tracker (one row per trigger)
5. Quarterly Reconciliation (one row per quarter)

Use Google Sheets if you want eventual integration; Excel works but requires manual export to CSV for upload.

### Step 2: Populate Tab 1 from C7

Pull all C7-measured deliveries within your M8.2 measurement period. For each delivery:
- Stated price (from C4 or C7 quote)
- Stated hours (from C7 quote)
- Actual hours (from C7 measurement system)
- Hidden hours by category (from your Hidden Hours Audit Worksheet)
- Loaded rate (computed in M8.2)
- Direct costs and overhead (from C7 financial tracking)

The spreadsheet's formulas compute total hours, total cost, gross margin $, gross margin %, and effective rate.

### Step 3: Populate Tab 2 from M8.4

Once M8.4 architecture is cleared, populate Tab 2 with:
- Base price
- Payment terms (deposit %, schedule)
- Refund window and triggers/non-triggers
- Tier prices (if tiered) or flat price
- Tier mix targets
- Sustainability margin target (60% knowledge-work doctrine)

### Step 4: Initialize Tab 3 (Anti-Discount Compliance)

Tab 3 is empty at M8.6 clearance. Each pricing pressure interaction adds a row:
- Date, customer, request type
- Policy classification (exception or non-exception)
- Action taken (decline or discount granted)
- Compliance score (1 if matched policy, 0 if deviated)

Quarterly: count rows where compliance = 0; divide by total rows; calculate compliance rate.

### Step 5: Populate Tab 4 (Trigger Tracker)

Once M8.7 schedule is cleared, populate Tab 4 with the four triggers:
- T1 (capacity utilization): threshold, window, magnitude, current reading
- T2 (waitlist depth): same
- T3 (demand signal): same
- T4 (annual indexing): date, magnitude

Update Tab 4 monthly with current readings of T1-T3.

### Step 6: Tab 5 is empty until first quarterly reconciliation

Tab 5 holds quarterly reconciliation data. First entry comes 90 days after M8.8 co-sign.

---

## Part B — Quarterly Reconciliation Workflow

### Step 1: Block 60-90 minutes on calendar

Quarterly reconciliation is a discipline activity. Block it as you would any operational meeting. Typical duration:

- New operators (first 1-2 reconciliations): 90 minutes
- Experienced operators (3+ reconciliations): 60 minutes

### Step 2: Update Tab 1 with new deliveries

Add rows for all deliveries completed in the quarter. Use measured hours from C7 system. Don't estimate; measure.

### Step 3: Update Tab 4 trigger readings

For T1 (capacity utilization), compute over rolling 90 days. If trigger fires, mark "Fired? = Y" and "Fired date".

For T2 (waitlist depth), use month-end snapshot.

For T3 (demand signal), compute over rolling 3 months.

For T4 (annual indexing), check if the calendar date has passed since last reconciliation. If yes and not yet executed, mark fired.

### Step 4: Compute reconciliation metrics

Tab 5 row for the quarter computes (from Tab 1, 3, 4):

| Metric | Source | Formula |
|---|---|---|
| Avg gross margin % | Tab 1 column N | AVERAGE() over quarter rows |
| Avg effective rate | Tab 1 column O | AVERAGE() |
| Tier mix actual | Tab 1 customer breakdown | COUNTIFS by tier / total |
| Tier mix variance | actual vs Tab 2 target | actual - target (in pp) |
| Anti-discount compliance % | Tab 3 column G | AVERAGE() |
| Triggers fired | Tab 4 column D Y count | COUNTIF(D:D, "Y") |
| Raises executed | Tab 4 column F populated | COUNTA(F:F) |
| Cumulative raise % | Tab 4 column G | SUM() |
| Deviation log entries | Manual count from Supabase | manual entry |

### Step 5: Write the quarterly memo

The memo is one page. Suggested template:

```
# Quarterly Pricing Discipline Reconciliation — [Q-Year]

## Metrics (from Tab 5)
[Metric table]

## Trigger Activity
[Which triggers fired, raises executed, cumulative cap status]

## Anti-Discount Compliance
[Compliance %, any deviations and reasons]

## Tier Mix vs Target
[Actual vs target, variance in pp, narrative on drift]

## M8.4 Architecture Sustainability Target Progress
[Are we on track to 60% margin? Time-to-target update]

## Deviations Logged in Quarter
[List from Supabase deviation_log]

## Decisions for Next Quarter
[Any actions: re-trigger reviews, schedule adjustments, etc.]

## Operator Sign-off
[Signature and date]
```

### Step 6: Push to Supabase

Insert one row in `c8_pricing_calculations` with the quarter's metrics:

**Manual method:**
1. Open Supabase dashboard
2. Navigate to c8_pricing_calculations table
3. Insert row with quarter metrics, memo URL, attestation_id

**Programmatic method (recommended for ongoing operation):**

```python
# Quarterly reconciliation push
import os
from supabase import create_client

supabase = create_client(
    os.environ['SUPABASE_URL'],
    os.environ['SUPABASE_KEY']
)

reconciliation = {
    'user_id': USER_ID,
    'attestation_id': ATTESTATION_ID,
    'quarter': 'Q3-2026',
    'quarter_start': '2026-07-01',
    'quarter_end': '2026-09-30',
    'avg_gross_margin_pct': 38.5,
    'avg_effective_rate': 108.20,
    'tier_mix_actual': {'standard': 65, 'entry': 25, 'premium': 10},
    'tier_mix_variance_pp': 5.0,
    'anti_discount_compliance_pct': 100.00,
    'triggers_fired_count': 1,
    'raises_executed_count': 1,
    'cumulative_raise_pct': 5.0,
    'deviation_count': 0,
    'memo_url': 'https://drive.google.com/...',
    'memo_summary': 'On-track to 60% margin via M8.4 path. T1 fired in month 7; raise executed within 30 days. Zero deviations.'
}

supabase.table('c8_pricing_calculations').insert(reconciliation).execute()
```

The `distribution_ready_flag` is computed automatically from deviation_count, anti_discount_compliance_pct, and tier_mix_variance_pp.

### Step 7: Review distribution_ready_flag

After insert, check `distribution_ready_flag`:
- **TRUE** if: deviation_count = 0 AND compliance ≥ 95% AND tier mix variance ≤ 15pp
- **FALSE** if any of those conditions failed

If FALSE, the quarter does not advance C9 readiness. Two consecutive FALSE quarters route to instructor review.

---

## Part C — Common Spreadsheet Issues and Fixes

### Issue 1: Tab 1 hours don't match C7 measurement

**Cause:** Operator imported C7 data via copy-paste, with rounding errors.
**Fix:** Use ImportRange (Sheets) or direct query (Excel) to pull C7 measurements without manual copy.

### Issue 2: Effective rate calculation wrong

**Cause:** Formula uses stated hours instead of total hours.
**Fix:** Effective rate column should reference column I (total hours including hidden), not column F (stated hours).

### Issue 3: Tab 3 compliance % is 100% but deviations exist in Supabase

**Cause:** Operator logged deviations in Supabase but not in Tab 3.
**Fix:** Tab 3 should be updated synchronously with Supabase deviation_log. Add a recurring 30-min weekly habit: copy deviations from Supabase to Tab 3.

### Issue 4: Trigger thresholds are too loose; nothing ever fires

**Cause:** M8.7 schedule had loose triggers (one of the most common M8.7 review failures).
**Fix:** This is a discipline issue, not a spreadsheet issue. Schedule M8.7 update with instructor; tighten thresholds.

### Issue 5: Quarterly memo wasn't written

**Cause:** Operator inserted Tab 5 row but didn't write memo.
**Fix:** memo_url is a required field. The discipline is the memo, not the metric. Without the memo, the row is incomplete.

---

## Part D — Best Practices

1. **Update monthly, not just quarterly.** Tab 1, 3, 4 update with each delivery / interaction / month. Quarterly reconciliation is the synthesis, not the data entry.

2. **Don't backdate.** If a deviation happened 14 days ago and you're logging it now, log it now. Don't change the deviation date to make the logging look prompt.

3. **Keep the memo honest.** "Q3 was tough; compliance dropped to 85%; here's why." Not "Q3 was great." The memo's value is its honesty.

4. **Pre-publish the memo to instructor.** Send the quarterly memo to your C8 instructor when you complete it, even if no review is required. The discipline is the visibility.

5. **Don't skip a quarter.** Quarters skipped accumulate; by year-end, two missed quarters means the deviation log is incomplete and C9 readiness assessment is unreliable.

---

*The spreadsheet is the operator's pricing discipline tool. Supabase is the system's compliance record. The walkthrough connects them so the discipline produces the record without duplication. Operators who skip the spreadsheet typically skip the discipline; the spreadsheet's friction is part of the operating cost of pricing integrity.*

URLs present in this original

Original references; destination accessibility has not been established by this appendix check.

Build a pricing architecture that explains the whole offer

Sources: M8.4 original Markdown and M8.4 Google Doc. Their prose matches after formatting normalization; both originals remain separately identified. Legacy module numbers do not change the spreadsheet assignments.

Outcome, prerequisites and purpose

Your outcome is a pricing architecture: a selected pricing model, grounded base price, payment terms, refund terms, segmentation rules and a position on the value/access matrix. The source expects a 1,500–2,000-word, eight-section document named Pricing-Architecture-Document-[YourName]-[Date].md. It assumes an M8.3 reality-check document, a review score of at least7/10 and48hours since filing. These are described prerequisites; this lesson does not certify that anyone completed them.

The named infrastructure is Build6, a Build8 Drive folder, the `c8_pricing_architectures` table, a Sonnet pricing-architecture reviewer, the pricing spreadsheet and the four-quadrant framework. Their names do not establish working installations. The source estimates eight active hours in three or four sittings: three for scanning, three for price and payments, one for refunds and segmentation, and one for positioning and writing. It separately estimates the scan at two to three hours. These are planning estimates.

The architecture implements an earlier branch: raise prices for new customers, narrow scope, stop the offer or retain a legacy arrangement. Its six proposed benefits are deciding common questions in advance, accounting for margin erosion, communicating consistently, explaining past decisions, supporting later scale and making pricing discipline concrete. The source connects pricing to self-respect; treat that as a coaching theme, not a measure of a person's worth.

For our Brunson and Hormozi application, offer design links the promised result, delivery scope, access, payment and commercial sustainability. The source explicitly includes Brunson's ladder among its models. Other connections here are instructional applications, not claims that either educator authored this lesson.

Compare all twenty pricing patterns

The source's “6% Rule” means examine at least16 candidates before choosing one or two. One in16 is6.25%; the name is approximate. The claim that this selection rate necessarily produces better decisions is not demonstrated. Its useful discipline is to compare plausible alternatives and explain rejection, rather than treating the first idea as the only option.

PatternWhat changes the charge or commitment
Flat fixed priceOne price for a defined offer; the source starts Maya's Sprint at$4,500.
Tiered fixed priceTwo or three packages such as Standard, Premium and VIP.
Per unitSessions, words, projects or another measurable unit.
HourlyTime spent; examine incentives and whether hours reflect delivered value.
Project with revision capA fixed scope plus a defined charge beyond the revision allowance.
Retainer or subscriptionRecurring payment for specified recurring service or access.
CohortA seat in a time-bound group; the source starts Darius at$1,200 per seat.
Sliding scaleCustomer-selected payment within documented bounds.
Performance basedA measurable outcome determines the fee.
Hybrid base and performanceA fixed amount plus an outcome-dependent component.
Customer-of-customerThe buyer's customer count determines price.
GeographicRegion determines price; justify conditions and account for arbitrage.
Early-bird or late cohortEnrollment timing determines the amount.
Partner or affiliateA designated channel receives specified commercial terms.
ScholarshipDocumented need determines reduced access pricing.
Productized fixed scopeOne standardized offer without customization.
Value based with anchorCustomer value and a relevant reference inform pricing.
LadderAn entry offer leads to a main offer and continuity.
Day or week rateA defined block of time is purchased.
Outcome guaranteeSpecified failure to achieve an outcome creates a refund or credit.

Use all five source filters: fit with Service/Teacher/Builder identity; fit with the mechanism hypothesis; expected customer experience; measured delivery capacity; and ability to sustain the discount rules. Identity categories are planning aids, not restrictions on who may use a model.

Maya scans20 and shortlists flat fixed, revision-capped project, retainer, productized scope and value-based pricing. The story chooses fixed price with explicit scope and revision limits for a12-week offer at$6,750. It rejects productization because she wants customization and retainer because the mechanism is time-bound. Its claim that value-based pricing requires collecting downstream licensing revenue is too narrow: using value to set a fee does not inherently require revenue sharing.

Darius shortlists cohort, individual subscription, hybrid performance, productized scope and ladder. The story replaces a poorly filled three-of-twelve-seat cohort with$300 monthly individual subscriptions, a three-month minimum and an optional$300 cohort upgrade when enrollment reaches eight. The minimum initial commitment is$900. Changing the revenue model does not prove profitability at every seat count; fulfillment costs, capacity and retention still matter. The story's Reading Club and platform-engineering descriptions also need clarification before being presented as one factual business case.

Ground the base price

Use the earlier branch and price target, chosen model, delivery identity, capacity and required time, and competitive evidence. Record the amount, model, link to unit economics and branch rationale, competitive position, identity fit and capacity fit. The later rubric also demands a structural test as a fifth rationale line; include it explicitly rather than losing it because the earlier template omits the label.

Maya's$6,750 is50% above$4,500. Her sample capacity calculation is$6,750 ×4 concurrent engagements ×4 annual turns =$108,000 gross annual revenue at full utilization. That is not proof of take-home income or25% margin headroom. The example's60th-percentile position cannot be calculated from the stated$5,000–$8,500 range alone.

Darius's ten concurrent subscribers at$300 monthly generate$36,000 annual gross revenue at sustained full capacity. The source compares this with historical platform pricing of$24 monthly and coaching of$1,500–$3,000 monthly. These are source examples, not current quotes or proof the services are comparable. Its branch-two versus branch-one-plus-model-change narration should remain an explicit revision in the example.

Specify every payment term and calculate its effect

Inputs are price, customer cash-flow research, the operator's financial baseline and the applicable fee schedule. Specify pay-in-full availability and discount, installment amounts and timing, failed-payment treatment, late fees and who bears processing costs. Even pay-in-full only needs a written rule.

The source gives a5% discount on$6,750 as$6,413. Exact arithmetic is$6,412.50, so state the rounding policy. Three payments of$2,250 total$6,750. Six payments of$1,150 total$6,900, a2.222…% premium rather than the labeled2%.

Its processing example is inconsistent. At the source's assumed2.9% plus$0.30 per transaction, one undiscounted$6,750 payment costs$196.05 and three$2,250 payments cost$196.65. The difference is$0.60, not$94, and splitting equal total revenue does not triple the proportional fee. Comparing a discounted pay-in-full amount requires recalculating on that different amount. The suggested$10 installment fee has no demonstrated basis. These are corrections to historical example arithmetic, not a current processor quotation.

Maya's example offers the5% pay-in-full reduction or three undiscounted installments, with processing absorbed, no extended plan, a day-seven pause and day-fourteen termination with50% balance forgiveness. Darius's example uses recurring$300 payments, a three-month minimum, seven-day grace and cancellation if unresolved by14days. A subscription may continue indefinitely while still having a finite minimum commitment. These are example policies requiring a coherent agreement, not universal instructions about enforceable terms.

The source's claims that5–10% discounts seem fair, over15% signals desperation and over12months feels like financing are generalized interpretations, not established customer reactions.

Align refunds with the offer already promised

Review the earlier guarantee, current offer language and future anti-discount policy. Specify duration, qualifying conditions, refund amount, any later partial-refund formula and alignment with the offer's limitations. The source says to refine or strengthen the existing guarantee rather than quietly weakening it.

Maya's example gives14days from the start after attending the first week's session, returns payment minus a$200 administration charge and says no refund after weekfour. A refund minus a fee is not a full refund; days15 through28 are not fully specified. Darius's example returns the first month's payment for a request before day30 and treats later months as non-refundable. Clarify the exact boundary and relationship to the three-month commitment. Do not present unresolved example terms as a finished customer policy.

The source characterizes60-plus-day unconditional windows as weak confidence and short windows as hostile. Those are coaching opinions, not conclusions that follow from duration alone.

Write segmentation rules with a defined financial basis

The source allows three patterns: cohort timing with a typical10–20% early discount; designated partner arrangements; and documented scholarships, illustratively one or two yearly. Each needs eligibility, timing, limits and a margin calculation. Uniform pricing also needs a reason.

The partner example subtracts20% commission and15% discount to obtain65% of base price. That works only if both percentages use the base price. A20% commission on the discounted selling price leaves0.85 ×0.80 =68% of base. State the commission basis before calculating profitability.

Its five discouraged patterns are personal negotiated deals, loyalty without structural rationale, geography without justification, hardship without criteria and automatic competitor matching. Other reviewed materials permit documented structural loyalty pricing; preserve that distinction rather than claiming all loyalty terms are forbidden. The source attributes geographic difficulty to Hermann Simon, without supplying supporting evidence here.

Maya chooses uniform pricing for simplicity and no current partner, cohort or scholarship program. Darius keeps the individual subscription undiscounted and prices the optional cohort upgrade at$250 early,$300 during the first month and$400 later. Define what those periods are measured from before using them in an offer. Standard cohort access is separately charged in this example; do not accidentally describe it as included in the subscription.

Position the offer on value and access

The horizontal axis is low-to-high value; vertical access runs broad-to-narrow. Preserve the source's four-quadrant diagram in the appendix. Value is not automatically the same as price.

Q1 is low value/broad access: source examples include$9 ebooks,$50 templates and$30 monthly basic software, with volume economics and a Builder association. Q2 is high value/broad access: examples include$200 books,$500–$2,000 courses and$5,000–$20,000 annual software, associated with Teacher or Builder models. Q3 is low value/narrow access: the source views it as a possible underpricing signal. Q4 is high value/narrow access: examples include$5,000–$50,000 coaching,$25,000–$200,000 advisory and$50,000-plus consulting, associated with intensive Service delivery. All amounts are source examples.

The source places Service mostly inQ4 or productized upperQ2, Teacher inQ2 or self-pacedQ1, and Builder inQ1/Q2. It labels MayaQ4 and DariusQ2. Use a mismatch as a question about delivery economics and customer value, not proof of personal inadequacy or an automatic reason to raise price.

Produce all eight sections and the handoff

SectionSource word targetRequired content
Branch implementation100–150Earlier decision and how this architecture implements it.
Pattern scan200–300At least16 candidates, filtering, rejection reasons and one or two selections.
Base price200–300Amount and all five evidence-based rationale lines.
Payments200–250All payment fields and their margin effects.
Refunds150–200Window, conditions, amount, partial formula and promise alignment.
Segmentation200–300Eligibility and economics, or explicit uniform-pricing rationale.
Matrix150–200Quadrant, reasons and delivery fit.
Cross-references100–150Specific inputs required by tier design, discount policy and raise schedule.

The section ranges sum to1,300–1,850, while the whole-document target is1,500–2,000. A1,500–1,850-word document can satisfy both; do not claim every total permitted by one satisfies the other. The separately reviewed architecture template has ten sections, so reconcile its additional requirements visibly rather than silently replacing this eight-section structure.

Maya's worked story follows the3+3+1+1-hour plan and ends with1,750words. This is an example of a filed artifact, not a record that your artifact has been filed. Review all seven failure modes: omitted scan, unsupported base price, uncalculated payment erosion, guarantee mismatch, discretionary bargaining disguised as segmentation, unexamined matrix mismatch and absent cross-references.

The checkpoint calls for a filed document and database fields `selected_pattern`, `base_price` and `matrix_quadrant`. Its eight review properties are the scan, grounded price, payment calculations, aligned refunds, explicit segmentation, matrix rationale, downstream references and section word targets. The target is at least7/10. Below that, revise identified weaknesses and resubmit within the described review process; no reviewer was executed here.

The next tier diagnostic either develops entry/standard/premium with distinct deliverables or documents why flat pricing fits. The base usually becomes standard-tier price when tiered. Discount policy needs segmentation rules; the raise schedule needs the architecture and positioning. Finish those handoff details so the pricing document supports the next lesson rather than ending at a number.

D0607 — complete original source

D0607 — M8.4 native source appendix

Open original Google Doc · Download complete native structure

Original text, list numbering, dash markers, headings and bold/italic emphasis are preserved. Exact style metadata is in the download; full visual layout review remains pending.

M8.4 — Pricing Architecture Construction: The Multi-Dimensional System
Module Outcome: [Create] Student has applied the 6% Rule to pricing patterns; specified base price, payment terms, refund window, and segmentation logic; positioned the offer on the four-quadrant pricing matrix; produced the Pricing Architecture Document that implements the M8.3 branch decision and serves as the primary input to M8.5-M8.7. Key Deliverable: Pricing Architecture Document (Pricing-Architecture-Document-[YourName]-[Date].md, 1,500-2,000 words, eight sections) Infrastructure Dependency: Build 6, Build 8 Drive folder, Supabase c8_pricing_architectures table, Claude prompt pricing-architecture-reviewer-v1.0.0 (Sonnet), Pricing-Math-Spreadsheet template, Four-Quadrant Pricing Matrix Framework Checkpoint / Test: Type 1 Artifact + Type 2 AI rubric ≥ 7/10 Blocked-Until Prerequisite: M8.3 Reality Check Document filed AND AI rubric ≥ 7/10 AND 48-hour cooling period elapsed since M8.3 filing
What This Module Does
M8.4 is the deepest module of C8 in active hours. Six things happen:
1. You apply the 6% Rule to pricing: scan 16+ pricing patterns from market and competitor data to identify the 1-2 strongest models for your offer's structural shape. The rule's discipline is the same as in C1 (sixteen patterns minimum); the application context shifts from operator-pattern selection to pricing-pattern selection.
2. You specify the base price for the corrected offer (post-M8.3 decision), grounded in the unit economics target margin. The base price is not the M8.3 target rounded; it is the M8.3 target tested against the chosen pricing pattern, the operator identity, and the C7 capacity ceiling.
3. You specify payment terms: pay-in-full discount (if any), installment plan structure (if any), payment-plan default and late-payment provisions. Payment terms have margin implications that the M8.2 math may not have captured (a 3-pay plan with a 2.9% per-transaction processing fee triples the processing cost compared to pay-in-full).
4. You specify the refund window: duration, conditions, partial-refund formula if applicable. The refund window aligns with the C4 M4.6 Guarantee Architecture — strengthened or refined per M8.4 work but not weakened.
5. You specify segmentation logic: when do different customer types pay different prices (cohort early-bird, partner referral, scholarship case, regional pricing), and what is the documented rationale? If uniform pricing, document why uniformity was chosen.
6. You position the offer on the four-quadrant pricing matrix along the value axis (low ↔ high) and access axis (broad ↔ narrow). The quadrant must match operator identity; mismatches are flagged.
The deliverable is the Pricing Architecture Document — 1,500-2,000 words, eight sections. The document is the primary input to M8.5 (tier design), M8.6 (anti-discount policy), and M8.7 (raise schedule). It is the densest pricing artifact in C8 and the most heavily cross-referenced.
M8.4 is 8 hours of active work distributed across 3-4 sittings. Most operators run a 6% Rule scan as the first sitting (3 hours), specify base price and payment terms as the second sitting (3 hours), specify refund window and segmentation as the third sitting (1 hour), and complete matrix positioning + document writing as the fourth sitting (1 hour).
Why This Module Matters
The M8.3 decision branch named what to do (raise prices for new, narrow scope, kill, or accept legacy). M8.4 specifies how. Pricing without architecture is a number floating in space; pricing with architecture is a system that handles the dozens of pricing-adjacent decisions the next 12 months will surface (the prospect asking for installments, the partner asking for affiliate terms, the regional-market customer asking about geographic pricing, the next-cohort prospect asking why pricing changed).
Architectural pricing has six structural advantages over single-number pricing:
1. Decision pre-emption. The architecture handles common pricing questions without ad-hoc judgment. When a prospect asks for an installment plan, the architecture answers; the operator does not have to decide in the moment.
2. Margin protection at edges. Payment processing fees, partial refunds, and late payments all erode margin if not specified upfront. The architecture quantifies the erosion.
3. Communication clarity. Customers experience a coherent pricing story when architecture is documented; they experience inconsistency when each decision is ad-hoc.
4. Audit traceability. When the operator looks back and asks "why did I price this customer this way?" the architecture answers; ad-hoc memory does not.
5. Scaling readiness. Stage 3 expansion (C11+) requires pricing that operates without operator intervention on most decisions. Architecture is the input to that scaling.
6. Self-respect operationalization. The doctrine "Pricing Is Operator Self-Respect" becomes operational through architecture; without architecture, the doctrine is aspirational.
The 6% Rule applied to pricing patterns is the same disciplinary mechanism as in C1's archetype selection: don't select the first pattern that comes to mind; select among 16+ candidates with documented reasoning. Operators who skip the scan tend to default to pricing patterns from their reference industry or their personal experience, missing the patterns that fit their specific offer shape better.
The 6% Rule Applied to Pricing Patterns
The 6% Rule (originating from C1) holds that a 1-in-16 selection rate produces structurally better choices than first-thought selection. Applied to pricing, the rule directs the operator to scan at least 16 pricing patterns from market and competitor data before specifying their own.
Pricing patterns are not the same as pricing levels. A pricing pattern is a structural model for how price relates to value, scope, customer count, and time. Common patterns include:
1. Flat fixed price — single price for single offer scope (Maya's $4,500 Sprint at C4)
2. Tiered fixed price — two or three discrete tiers (Standard / Premium / VIP)
3. Per-unit pricing — price scales with measurable units (per session, per word, per project)
4. Hourly billing — price scales with hours; Stark's caution on hidden incentives applies
5. Project-based with revisions cap — fixed price for defined scope, additional fee per revision beyond cap
6. Retainer / subscription — recurring fixed fee for recurring access
7. Cohort pricing — fixed price per seat in a time-bound cohort (Darius's Reading Club at $1,200/seat)
8. Pay-what-you-can / sliding scale — variable price by customer self-determination within bounds
9. Performance-based — price scales with measurable outcomes (e.g., percentage of revenue generated)
10. Hybrid base + performance — fixed base + outcome-tied bonus
11. Per-customer-of-customer — pricing scales with the customer's customer count (B2B common)
12. Geographic / regional pricing — different prices by customer geography (controversial; Hermann Simon notes implementation difficulty)
13. Cohort early-bird / late — price varies by time of cohort enrollment relative to start
14. Partner / affiliate pricing — discount available to customers from designated partner channels
15. Scholarship / need-based pricing — discounted access for documented need cases
16. Productized fixed-scope — single price, no scope variation, no customization
17. Value-based with anchor — pricing tied to the customer's value capture, anchored to a reference
18. Ladder pricing — entry product → main product → continuity (Brunson's ladder)
19. Day-rate / week-rate — fixed time blocks at fixed rates
20. Outcome-guarantee pricing — price tied to outcome with refund/credit if outcome not achieved
The operator scans these 16-20+ patterns against their offer shape and selects 1-2 candidates that fit best. The selection criteria:
- Match to operator identity (Service / Teacher / Builder)
- Match to mechanism (the C2 M2.7 hypothesis structurally)
- Match to customer experience expectation (what does the audience expect at this price level?)
- Match to operator capacity ceiling (some patterns require concurrent-customer counts the M7.5 ceiling cannot support)
- Match to operator's anti-discount discipline (some patterns embed discounting into the architecture in ways the operator cannot defend)
For Maya's Portfolio-to-Licensing Sprint:
- Scanned all 20 patterns
- Filtered to: flat fixed price (current pattern, refined), project-based with revisions cap, retainer, productized fixed-scope, value-based with anchor
- Compared each: flat fixed price fits the 12-week defined scope; productized fixed-scope eliminates the customization Maya intentionally provides; retainer doesn't fit the time-bounded mechanism; value-based with anchor would require Maya to capture downstream licensing income (complex for a coaching engagement)
- Selected: Flat fixed price refined with explicit scope boundaries and revisions cap. New base price target from M8.3: $6,750.
For Darius's Reading Club:
- Scanned all 20 patterns
- Filtered to: cohort pricing (current pattern), per-individual subscription, hybrid base + outcome, productized fixed-scope, ladder pricing
- Compared each: cohort pricing has the structural problem M8.2 surfaced (3 of 12 seats produces disastrous unit economics); per-individual subscription decouples pricing from cohort dynamics; ladder pricing introduces a low-cost entry product that funnels to the cohort
- Selected: Per-individual subscription ($300/month for 3-month minimum commitment) plus optional cohort upgrade ($300 cohort fee added when cohort runs at 8+ enrollment). This solves the structural problem from M8.2 (the cohort's economics no longer depend on hitting 12 seats; individual subscription supports the offer at any seat count).
The 6% Rule scan takes 2-3 hours of active work and produces materially better pricing patterns than first-thought selection.
Base Price Specification
After the 6% Rule scan, you specify the base price for the corrected offer.
Inputs:
- M8.3 decision branch and price target
- Selected pricing pattern from the 6% Rule scan
- Operator identity (Service / Teacher / Builder)
- Capacity ceiling × stated minimum target hours
- Competitive scan benchmark range
Specification template:
Base price: $[X] Pricing pattern: [Pattern from 6% Rule selection] Source rationale: [link to M8.2 unit economics target margin and M8.3 decision branch] Competitive position: [position relative to scanned competitive offers — e.g., "$6,750 places this offer at the 60th percentile of comparable offers in the senior-illustrator coaching market, range $5,000-$8,500"] Identity coherence: [Service-Operator pricing tone explanation — e.g., "premium positioning is consistent with the Sprint's intensive-personal-attention delivery"] Capacity coherence: [check against M7.5 — e.g., "at $6,750 × 4 concurrent × 4 turns/year = $108,000 max annual revenue, exceeds operator income target with 25% margin headroom"]
The base price is not aspirational; it is grounded. The rationale lines must each cite specific evidence. Operators who specify a base price without grounding it tend to specify aspirationally and produce architecture that cannot withstand the first prospect objection.
For Maya: $6,750 (50% increase from $4,500 anchor). Pricing pattern: flat fixed price with revisions cap. Source rationale: M8.3 decision branch 1; M8.2 stated minimum × hours × adjusted-fulfillment math. Competitive position: 60th percentile in scanned market. Identity coherence: Service-Operator with intensive personal attention. Capacity coherence: confirmed at M7.5 ceiling.
For Darius: $300/month per individual subscription with 3-month minimum. Pricing pattern: per-individual subscription. Source rationale: M8.3 decision branch 2 (narrow scope, but Darius chose Branch 1+pattern shift). Competitive position: between Codecademy Pro ($24/month) and engineering coaching ($1,500-$3,000/month) — solidly in the middle of the platform-engineering education market. Identity coherence: Teacher-Operator with cohort-style group dynamics. Capacity coherence: at M7.5 ceiling, ~10 concurrent subscribers; revenue $3,000/month × 12 = $36,000 annual base.
Payment Terms Specification
Payment terms are not optional. Even if you offer pay-in-full only, document that explicitly.
Inputs:
- Base price from the prior section
- Customer cash-flow expectations (from C3 audience research)
- Operator cash-flow needs (from C6 financial baseline)
- Payment processor fee structure (Stripe ~2.9% + $0.30; PayPal similar)
Specification template:
Pay-in-full: [yes/no, and discount if any — e.g., "5% pay-in-full discount, base $6,750 → $6,413"] Installment plan: [yes/no, and structure — e.g., "3-pay at $2,250/month, no discount; 6-pay at $1,150/month, 2% premium"] Default provisions: [what happens if a payment fails — e.g., "automatic retry at day 1, day 3, day 5; access pause at day 7; engagement termination at day 14 with 50% balance forgiveness"] Late-payment fees: [yes/no — e.g., "no late fees but engagement pauses on missed payment"] Processing fee absorbed: [operator absorbs or passed to customer — e.g., "operator absorbs Stripe fee on pay-in-full; customer absorbs ~$10 processing fee on per-installment basis"]
The payment terms have meaningful margin implications. A 3-pay plan at $2,250 produces 3 transactions × ($2,250 × 2.9% + $0.30) = $196 in processing fees vs. $196 for one pay-in-full transaction; the difference is $94 — small per customer but material at scale.
The payment terms also have psychological effects. Customers perceive pay-in-full discounts at 5-10% as fair; discounts above 15% read as desperation. Customers perceive installment plans as access-enabling; plans above 12 months read as financing rather than payment terms.
Maya's specification: pay-in-full $6,750, 5% discount to $6,413; 3-pay at $2,250/month with no discount and operator-absorbed processing; no 6-pay or extended plan. Default: pause at day 7 missed payment, terminate at day 14 with 50% forgiveness.
Darius's specification: $300/month subscription, no pay-in-full option (the subscription model doesn't have a finite total). 3-month minimum commitment; cancellation policy specified. Failed payment: 7-day grace, then access pause; cancellation if not resolved in 14 days.
Refund Window Specification
The refund window aligns with the C4 M4.6 Guarantee Architecture but may be refined per M8.4 work.
Inputs:
- C4 M4.6 Guarantee Architecture
- C7 v2.0 offer document refund language
- M8.6 anti-discount policy (referenced forward)
Specification template:
Refund window: [duration — e.g., "14 days from engagement start"] Refund conditions: [what qualifies — e.g., "if the customer has completed Module 1 sessions and concludes the Sprint is not the right fit"] Refund amount: [full / partial — e.g., "full refund minus $200 administrative fee"] Partial refund formula (for mid-engagement): [if applicable — e.g., "after Module 1, prorated by remaining modules; after Module 4, no refund"] Anti-promise alignment: [reference C4 M4.5 — e.g., "consistent with anti-promise that Sprint outcome depends on customer's specific licensing portfolio readiness"]
Refund windows that are too generous (60+ days, no conditions) erode margin and signal lack of confidence. Refund windows that are too restrictive (7 days, no conditions, no partial) read as customer-hostile. The discipline is to find the alignment with C4 M4.6 and the operator identity.
For Maya: 14 days from engagement start; refund qualifies if customer has completed Week 1 session and concludes the Sprint is not the right fit; refund is full minus $200 administrative fee; after Week 4, no refund (consistent with C4 M4.6 architecture).
For Darius: 30 days from subscription start; refund qualifies if cancellation request received before Day 30; full refund of first month's payment; subsequent months non-refundable.
Segmentation Logic Specification
Segmentation is the most error-prone area of M8.4. Many operators want to offer different prices to different customer types but lack the discipline to do so coherently.
Three legitimate segmentation patterns:
1. Cohort timing segmentation: early-bird vs. standard vs. late pricing for time-bound cohorts. Discount typically 10-20% for early-bird; rationale is cash-flow-forward and conversion-de-risking. Anti-discount policy must specify this is a time-bound cohort discount, not a negotiation discount.
2. Partner / affiliate segmentation: designated partners can offer the operator's offer to their network at a discount, with the partner taking a commission. The arithmetic must work: if partner takes 20% commission and discount is 15%, operator nets 65% of base price; this must still produce sustainable margin.
3. Scholarship / need-based segmentation: documented need cases at reduced price; operator commits to a defined number per cohort/year (typically 1-2 per year). Rationale: portfolio-builder, mission-aligned access. Specific to the operator's identity and stage.
Anti-segmentation patterns to avoid:
- Negotiated discounts ("special deal for you because we got along well") — destroys pricing coherence
- Loyalty discounts ("returning customer gets 15% off") — erodes margin without structural justification
- Geographic / regional pricing without strong defensible rationale — Hermann Simon notes high implementation difficulty and high arbitrage risk
- Hardship discounts without defined need-based criteria — slips into negotiation territory
- Comparable-competitor matching ("your competitor charges X, I'll match") — abandons the architecture entirely
If uniform pricing (no segmentation): document why. Operators who select uniform pricing typically cite operator identity, simplicity preference, and discipline against ad-hoc adjustment.
For Maya: uniform pricing for v2.1; no cohort timing (she runs 1:1, not cohort); no partner program at this stage; no scholarship currently planned. Documented rationale: simplicity, discipline against ad-hoc adjustment, operator-identity coherence.
For Darius: cohort timing segmentation for the optional cohort upgrade (early-bird $250 cohort fee, standard $300 within first month, $400 after that). No individual-subscription discounts. No partner program at this stage.
Four-Quadrant Pricing Matrix
The matrix positions the offer along two axes: value (low ↔ high) and access (broad ↔ narrow).
Narrow Access
|
|
Low Value | High Value
Narrow Access | Narrow Access
|
|
──────────────────────────────────
|
|
Low Value | High Value
Broad Access | Broad Access
|
|
Broad Access
The four quadrants:
Q1 (Low Value, Broad Access): Mass-market commodity pricing. Examples: $9 ebooks, $50 templates, $30/month basic SaaS. Volume-driven economics. Identity match: Builder-Operator scaling productized output.
Q2 (High Value, Broad Access): Premium product widely available. Examples: $200 books with broad distribution, $500-$2,000 self-paced courses, $5,000-$20,000 annual SaaS. Identity match: Teacher-Operator at scale or Builder-Operator with brand premium.
Q3 (Low Value, Narrow Access): Boutique low-price offerings. Rare in knowledge-work; usually indicates an operator who is under-priced. Identity match: rare; usually misalignment.
Q4 (High Value, Narrow Access): Premium bespoke / coaching / advisory. Examples: $5,000-$50,000 personal coaching, $25,000-$200,000 advisory engagements, $50,000+ executive consulting. Identity match: Service-Operator with intensive personal attention.
The operator positions their offer in the matrix and verifies the position matches operator identity:
- Service-Operator pricing typically lives in Q4 (or upper Q2 if productized)
- Teacher-Operator pricing typically lives in Q2 (cohort) or Q1 (self-paced)
- Builder-Operator pricing typically lives in Q1 or Q2 (productized scaling)
For Maya: Q4 (High Value, Narrow Access) at $6,750 with intensive 1:1 coaching. Identity match: Service-Operator. Coherent.
For Darius: Q2 (High Value, Broad Access) at $300/month subscription with cohort access. Identity match: Teacher-Operator at scale. Coherent.
Operators whose offer lands in a quadrant inconsistent with their identity should re-examine the pricing pattern. Q3 (Low Value, Narrow Access) is the most common misalignment: it indicates a Service-Operator who has under-priced themselves; the M8.3 decision branch typically already addresses this.
The Eight-Section Document Template
Your Pricing Architecture Document is 1,500-2,000 words, with eight sections:
Section 1 — M8.3 Branch and Implementation Bridge (100-150 words)
State which M8.3 branch you committed to and how M8.4 architecture implements it. Brief — most of the architecture work is below.
Section 2 — 6% Rule Pricing Pattern Scan (200-300 words)
List 16+ pricing patterns scanned. Show your filtering: which patterns survived initial screening, which were eliminated and why, which 1-2 were selected. Show your selection criteria explicitly.
Section 3 — Base Price Specification (200-300 words)
Specify the base price with the five rationale lines (source, competitive position, identity coherence, capacity coherence, and structural test).
Section 4 — Payment Terms Specification (200-250 words)
Specify pay-in-full discount, installment structure, default provisions, late-payment provisions, processing-fee handling. Show the margin impact of payment-term decisions.
Section 5 — Refund Window Specification (150-200 words)
Specify duration, conditions, refund amount, partial-refund formula, anti-promise alignment.
Section 6 — Segmentation Logic Specification (200-300 words)
Specify segmentation patterns selected (cohort timing / partner / scholarship) or document uniform pricing. If segmented, show the math: does the segmented pricing still produce sustainable margin?
Section 7 — Four-Quadrant Matrix Positioning (150-200 words)
State which quadrant the offer occupies, the rationale for positioning, and the identity coherence verification.
Section 8 — Cross-References (100-150 words)
Specify what M8.5 (tier design), M8.6 (anti-discount), and M8.7 (raise schedule) will need from this architecture. Be specific about inputs.
Worked Example: Maya's Pricing Architecture
Maya's M8.4 sittings:
Sitting 1 (3 hours): 6% Rule scan. Maya scanned 20 pricing patterns. Filtered to 5: flat fixed, project-based with revisions cap, retainer, productized fixed-scope, value-based with anchor. Selected: flat fixed price refined with explicit scope boundaries and revisions cap.
Sitting 2 (3 hours): base price + payment terms. Maya specified $6,750 as base price (50% increase from C4 anchor). Pay-in-full discount: 5% to $6,413. 3-pay installment plan: $2,250/month with no discount, operator absorbs processing. No 6-pay or extended plan. Default: pause at day 7, terminate at day 14 with 50% forgiveness.
Sitting 3 (1 hour): refund window + segmentation. Refund window: 14 days from engagement start; refund qualifies if customer has completed Week 1 and concludes Sprint not right fit; full refund minus $200 admin fee; after Week 4, no refund. Segmentation: uniform pricing for v2.1, no cohort timing, no partner, no scholarship currently. Documented rationale.
Sitting 4 (1 hour): matrix positioning + document writing. Positioning: Q4 (High Value, Narrow Access). Identity match: Service-Operator with intensive 1:1 coaching. Coherent. Document compiled to 1,750 words.
Maya's architecture is filed. The document is the input to M8.5 (Maya considers tier design), M8.6 (anti-discount policy with the new architecture as anchor), and M8.7 (raise schedule with $6,750 as the current baseline).
Common Failure Modes at M8.4
The Sonnet pricing-architecture-reviewer-v1.0.0 prompt and the AI rubric look for these:
1. Skipping the 6% Rule scan. Operator specifies a pricing pattern as the first-thought selection without showing the 16+ scan. The AI rubric flags any document that lists fewer than 16 patterns.
2. Aspirational base price. Operator specifies a base price that is not grounded in M8.3 unit economics or competitive scan. The price is a wish, not an architectural choice. The rubric expects each rationale line cited.
3. Payment terms with margin erosion uncalculated. Operator specifies installment plans without computing the margin impact (processing fees, default risk).
4. Refund window misaligned with C4 M4.6. Operator specifies a refund window inconsistent with the existing Guarantee Architecture without explanation.
5. Segmentation pattern slipping into negotiation. Operator specifies "case-by-case discounts for fit" or similar; the AI rubric flags this as ad-hoc, not architectural.
6. Quadrant misalignment. Operator's identity (Service-Operator) doesn't match the quadrant (Q1 Low Value Broad Access). The mismatch is a signal; the operator should re-examine pattern selection.
7. Section 8 cross-references missing. Operator does not specify M8.5/M8.6/M8.7 input requirements; the next modules will start without context.
Checkpoint 8.4
Your deliverable is:
1. Pricing Architecture Document filed in Drive, 1,500-2,000 words, eight sections
2. Pricing pattern selection recorded in Supabase c8_pricing_architectures.selected_pattern
3. Base price recorded in c8_pricing_architectures.base_price
4. Quadrant positioning recorded in c8_pricing_architectures.matrix_quadrant
The AI rubric scoring the document looks for eight properties:
- 6% Rule scan with 16+ patterns shown and filtered
- Base price with all five rationale lines
- Payment terms with margin impact computed
- Refund window aligned with C4 M4.6
- Segmentation logic specific (or uniform with documented rationale)
- Quadrant positioning with identity coherence verification
- Cross-references to M8.5/M8.6/M8.7 inputs
- All eight sections meet word-count targets
Target score: ≥ 7/10. Operators who score below typically have either skipped the 6% Rule scan (the most common gap) or specified base price aspirationally without grounding (the second most common). Re-read this lesson, run the architecture work again with rigor, and resubmit.
What M8.5 Expects From You
M8.5 opens with the assumption that your pricing architecture is filed and architecturally coherent. M8.5 begins by asking whether your offer is appropriate for tiered pricing — the Tier Appropriateness Diagnostic. If yes, M8.5 designs three tiers (entry/standard/premium) with structurally different deliverables. If no, M8.5 documents the flat-pricing rationale with the diagnostic findings.
The M8.4 base price feeds into M8.5: if tiered, the base price typically becomes the standard tier's price, with entry below and premium above. If flat, the base price is the price.
M8.6 (anti-discount policy) and M8.7 (raise schedule) also read from M8.4. M8.6 needs the architecture's segmentation logic to produce the explicit exception/non-exception lists. M8.7 needs the matrix positioning to ground its raise triggers.
File the Pricing Architecture Document. Proceed to M8.5.
Last updated: April 25, 2026 · Version 2.0

The shared M8.4 teaching accompanies D0607; both originals are preserved separately.

D0608 — complete original source

D0470-linked-D0608 — complete original source

Open source file · Download exact original file

# M8.4 — Pricing Architecture Construction: The Multi-Dimensional System

**Module Outcome:** [Create] Student has applied the 6% Rule to pricing patterns; specified base price, payment terms, refund window, and segmentation logic; positioned the offer on the four-quadrant pricing matrix; produced the Pricing Architecture Document that implements the M8.3 branch decision and serves as the primary input to M8.5-M8.7.
**Key Deliverable:** Pricing Architecture Document (`Pricing-Architecture-Document-[YourName]-[Date].md`, 1,500-2,000 words, eight sections)
**Infrastructure Dependency:** Build 6, Build 8 Drive folder, Supabase `c8_pricing_architectures` table, Claude prompt `pricing-architecture-reviewer-v1.0.0` (Sonnet), Pricing-Math-Spreadsheet template, Four-Quadrant Pricing Matrix Framework
**Checkpoint / Test:** Type 1 Artifact + Type 2 AI rubric ≥ 7/10
**Blocked-Until Prerequisite:** M8.3 Reality Check Document filed AND AI rubric ≥ 7/10 AND 48-hour cooling period elapsed since M8.3 filing

---

## What This Module Does

M8.4 is the deepest module of C8 in active hours. Six things happen:

1. You **apply the 6% Rule to pricing**: scan 16+ pricing patterns from market and competitor data to identify the 1-2 strongest models for your offer's structural shape. The rule's discipline is the same as in C1 (sixteen patterns minimum); the application context shifts from operator-pattern selection to pricing-pattern selection.

2. You **specify the base price** for the corrected offer (post-M8.3 decision), grounded in the unit economics target margin. The base price is not the M8.3 target rounded; it is the M8.3 target tested against the chosen pricing pattern, the operator identity, and the C7 capacity ceiling.

3. You **specify payment terms**: pay-in-full discount (if any), installment plan structure (if any), payment-plan default and late-payment provisions. Payment terms have margin implications that the M8.2 math may not have captured (a 3-pay plan with a 2.9% per-transaction processing fee triples the processing cost compared to pay-in-full).

4. You **specify the refund window**: duration, conditions, partial-refund formula if applicable. The refund window aligns with the C4 M4.6 Guarantee Architecture — strengthened or refined per M8.4 work but not weakened.

5. You **specify segmentation logic**: when do different customer types pay different prices (cohort early-bird, partner referral, scholarship case, regional pricing), and what is the documented rationale? If uniform pricing, document why uniformity was chosen.

6. You **position the offer on the four-quadrant pricing matrix** along the value axis (low ↔ high) and access axis (broad ↔ narrow). The quadrant must match operator identity; mismatches are flagged.

The deliverable is the **Pricing Architecture Document** — 1,500-2,000 words, eight sections. The document is the primary input to M8.5 (tier design), M8.6 (anti-discount policy), and M8.7 (raise schedule). It is the densest pricing artifact in C8 and the most heavily cross-referenced.

M8.4 is 8 hours of active work distributed across 3-4 sittings. Most operators run a 6% Rule scan as the first sitting (3 hours), specify base price and payment terms as the second sitting (3 hours), specify refund window and segmentation as the third sitting (1 hour), and complete matrix positioning + document writing as the fourth sitting (1 hour).

---

## Why This Module Matters

The M8.3 decision branch named what to do (raise prices for new, narrow scope, kill, or accept legacy). M8.4 specifies how. Pricing without architecture is a number floating in space; pricing with architecture is a system that handles the dozens of pricing-adjacent decisions the next 12 months will surface (the prospect asking for installments, the partner asking for affiliate terms, the regional-market customer asking about geographic pricing, the next-cohort prospect asking why pricing changed).

Architectural pricing has six structural advantages over single-number pricing:

1. **Decision pre-emption.** The architecture handles common pricing questions without ad-hoc judgment. When a prospect asks for an installment plan, the architecture answers; the operator does not have to decide in the moment.
2. **Margin protection at edges.** Payment processing fees, partial refunds, and late payments all erode margin if not specified upfront. The architecture quantifies the erosion.
3. **Communication clarity.** Customers experience a coherent pricing story when architecture is documented; they experience inconsistency when each decision is ad-hoc.
4. **Audit traceability.** When the operator looks back and asks "why did I price this customer this way?" the architecture answers; ad-hoc memory does not.
5. **Scaling readiness.** Stage 3 expansion (C11+) requires pricing that operates without operator intervention on most decisions. Architecture is the input to that scaling.
6. **Self-respect operationalization.** The doctrine "Pricing Is Operator Self-Respect" becomes operational through architecture; without architecture, the doctrine is aspirational.

The 6% Rule applied to pricing patterns is the same disciplinary mechanism as in C1's archetype selection: don't select the first pattern that comes to mind; select among 16+ candidates with documented reasoning. Operators who skip the scan tend to default to pricing patterns from their reference industry or their personal experience, missing the patterns that fit their specific offer shape better.

---

## The 6% Rule Applied to Pricing Patterns

The 6% Rule (originating from C1) holds that a 1-in-16 selection rate produces structurally better choices than first-thought selection. Applied to pricing, the rule directs the operator to scan at least 16 pricing patterns from market and competitor data before specifying their own.

Pricing patterns are not the same as pricing levels. A pricing pattern is a structural model for how price relates to value, scope, customer count, and time. Common patterns include:

1. **Flat fixed price** — single price for single offer scope (Maya's $4,500 Sprint at C4)
2. **Tiered fixed price** — two or three discrete tiers (Standard / Premium / VIP)
3. **Per-unit pricing** — price scales with measurable units (per session, per word, per project)
4. **Hourly billing** — price scales with hours; Stark's caution on hidden incentives applies
5. **Project-based with revisions cap** — fixed price for defined scope, additional fee per revision beyond cap
6. **Retainer / subscription** — recurring fixed fee for recurring access
7. **Cohort pricing** — fixed price per seat in a time-bound cohort (Darius's Reading Club at $1,200/seat)
8. **Pay-what-you-can / sliding scale** — variable price by customer self-determination within bounds
9. **Performance-based** — price scales with measurable outcomes (e.g., percentage of revenue generated)
10. **Hybrid base + performance** — fixed base + outcome-tied bonus
11. **Per-customer-of-customer** — pricing scales with the customer's customer count (B2B common)
12. **Geographic / regional pricing** — different prices by customer geography (controversial; Hermann Simon notes implementation difficulty)
13. **Cohort early-bird / late** — price varies by time of cohort enrollment relative to start
14. **Partner / affiliate pricing** — discount available to customers from designated partner channels
15. **Scholarship / need-based pricing** — discounted access for documented need cases
16. **Productized fixed-scope** — single price, no scope variation, no customization
17. **Value-based with anchor** — pricing tied to the customer's value capture, anchored to a reference
18. **Ladder pricing** — entry product → main product → continuity (Brunson's ladder)
19. **Day-rate / week-rate** — fixed time blocks at fixed rates
20. **Outcome-guarantee pricing** — price tied to outcome with refund/credit if outcome not achieved

The operator scans these 16-20+ patterns against their offer shape and selects 1-2 candidates that fit best. The selection criteria:

- **Match to operator identity** (Service / Teacher / Builder)
- **Match to mechanism** (the C2 M2.7 hypothesis structurally)
- **Match to customer experience expectation** (what does the audience expect at this price level?)
- **Match to operator capacity ceiling** (some patterns require concurrent-customer counts the M7.5 ceiling cannot support)
- **Match to operator's anti-discount discipline** (some patterns embed discounting into the architecture in ways the operator cannot defend)

For Maya's Portfolio-to-Licensing Sprint:
- Scanned all 20 patterns
- Filtered to: flat fixed price (current pattern, refined), project-based with revisions cap, retainer, productized fixed-scope, value-based with anchor
- Compared each: flat fixed price fits the 12-week defined scope; productized fixed-scope eliminates the customization Maya intentionally provides; retainer doesn't fit the time-bounded mechanism; value-based with anchor would require Maya to capture downstream licensing income (complex for a coaching engagement)
- **Selected:** Flat fixed price refined with explicit scope boundaries and revisions cap. New base price target from M8.3: $6,750.

For Darius's Reading Club:
- Scanned all 20 patterns
- Filtered to: cohort pricing (current pattern), per-individual subscription, hybrid base + outcome, productized fixed-scope, ladder pricing
- Compared each: cohort pricing has the structural problem M8.2 surfaced (3 of 12 seats produces disastrous unit economics); per-individual subscription decouples pricing from cohort dynamics; ladder pricing introduces a low-cost entry product that funnels to the cohort
- **Selected:** Per-individual subscription ($300/month for 3-month minimum commitment) plus optional cohort upgrade ($300 cohort fee added when cohort runs at 8+ enrollment). This solves the structural problem from M8.2 (the cohort's economics no longer depend on hitting 12 seats; individual subscription supports the offer at any seat count).

The 6% Rule scan takes 2-3 hours of active work and produces materially better pricing patterns than first-thought selection.

---

## Base Price Specification

After the 6% Rule scan, you specify the base price for the corrected offer.

**Inputs:**
- M8.3 decision branch and price target
- Selected pricing pattern from the 6% Rule scan
- Operator identity (Service / Teacher / Builder)
- Capacity ceiling × stated minimum target hours
- Competitive scan benchmark range

**Specification template:**

> Base price: $[X]
> Pricing pattern: [Pattern from 6% Rule selection]
> Source rationale: [link to M8.2 unit economics target margin and M8.3 decision branch]
> Competitive position: [position relative to scanned competitive offers — e.g., "$6,750 places this offer at the 60th percentile of comparable offers in the senior-illustrator coaching market, range $5,000-$8,500"]
> Identity coherence: [Service-Operator pricing tone explanation — e.g., "premium positioning is consistent with the Sprint's intensive-personal-attention delivery"]
> Capacity coherence: [check against M7.5 — e.g., "at $6,750 × 4 concurrent × 4 turns/year = $108,000 max annual revenue, exceeds operator income target with 25% margin headroom"]

The base price is not aspirational; it is grounded. The rationale lines must each cite specific evidence. Operators who specify a base price without grounding it tend to specify aspirationally and produce architecture that cannot withstand the first prospect objection.

For Maya: $6,750 (50% increase from $4,500 anchor). Pricing pattern: flat fixed price with revisions cap. Source rationale: M8.3 decision branch 1; M8.2 stated minimum × hours × adjusted-fulfillment math. Competitive position: 60th percentile in scanned market. Identity coherence: Service-Operator with intensive personal attention. Capacity coherence: confirmed at M7.5 ceiling.

For Darius: $300/month per individual subscription with 3-month minimum. Pricing pattern: per-individual subscription. Source rationale: M8.3 decision branch 2 (narrow scope, but Darius chose Branch 1+pattern shift). Competitive position: between Codecademy Pro ($24/month) and engineering coaching ($1,500-$3,000/month) — solidly in the middle of the platform-engineering education market. Identity coherence: Teacher-Operator with cohort-style group dynamics. Capacity coherence: at M7.5 ceiling, ~10 concurrent subscribers; revenue $3,000/month × 12 = $36,000 annual base.

---

## Payment Terms Specification

Payment terms are not optional. Even if you offer pay-in-full only, document that explicitly.

**Inputs:**
- Base price from the prior section
- Customer cash-flow expectations (from C3 audience research)
- Operator cash-flow needs (from C6 financial baseline)
- Payment processor fee structure (Stripe ~2.9% + $0.30; PayPal similar)

**Specification template:**

> Pay-in-full: [yes/no, and discount if any — e.g., "5% pay-in-full discount, base $6,750 → $6,413"]
> Installment plan: [yes/no, and structure — e.g., "3-pay at $2,250/month, no discount; 6-pay at $1,150/month, 2% premium"]
> Default provisions: [what happens if a payment fails — e.g., "automatic retry at day 1, day 3, day 5; access pause at day 7; engagement termination at day 14 with 50% balance forgiveness"]
> Late-payment fees: [yes/no — e.g., "no late fees but engagement pauses on missed payment"]
> Processing fee absorbed: [operator absorbs or passed to customer — e.g., "operator absorbs Stripe fee on pay-in-full; customer absorbs ~$10 processing fee on per-installment basis"]

The payment terms have meaningful margin implications. A 3-pay plan at $2,250 produces 3 transactions × ($2,250 × 2.9% + $0.30) = $196 in processing fees vs. $196 for one pay-in-full transaction; the difference is $94 — small per customer but material at scale.

The payment terms also have psychological effects. Customers perceive pay-in-full discounts at 5-10% as fair; discounts above 15% read as desperation. Customers perceive installment plans as access-enabling; plans above 12 months read as financing rather than payment terms.

Maya's specification: pay-in-full $6,750, 5% discount to $6,413; 3-pay at $2,250/month with no discount and operator-absorbed processing; no 6-pay or extended plan. Default: pause at day 7 missed payment, terminate at day 14 with 50% forgiveness.

Darius's specification: $300/month subscription, no pay-in-full option (the subscription model doesn't have a finite total). 3-month minimum commitment; cancellation policy specified. Failed payment: 7-day grace, then access pause; cancellation if not resolved in 14 days.

---

## Refund Window Specification

The refund window aligns with the C4 M4.6 Guarantee Architecture but may be refined per M8.4 work.

**Inputs:**
- C4 M4.6 Guarantee Architecture
- C7 v2.0 offer document refund language
- M8.6 anti-discount policy (referenced forward)

**Specification template:**

> Refund window: [duration — e.g., "14 days from engagement start"]
> Refund conditions: [what qualifies — e.g., "if the customer has completed Module 1 sessions and concludes the Sprint is not the right fit"]
> Refund amount: [full / partial — e.g., "full refund minus $200 administrative fee"]
> Partial refund formula (for mid-engagement): [if applicable — e.g., "after Module 1, prorated by remaining modules; after Module 4, no refund"]
> Anti-promise alignment: [reference C4 M4.5 — e.g., "consistent with anti-promise that Sprint outcome depends on customer's specific licensing portfolio readiness"]

Refund windows that are too generous (60+ days, no conditions) erode margin and signal lack of confidence. Refund windows that are too restrictive (7 days, no conditions, no partial) read as customer-hostile. The discipline is to find the alignment with C4 M4.6 and the operator identity.

For Maya: 14 days from engagement start; refund qualifies if customer has completed Week 1 session and concludes the Sprint is not the right fit; refund is full minus $200 administrative fee; after Week 4, no refund (consistent with C4 M4.6 architecture).

For Darius: 30 days from subscription start; refund qualifies if cancellation request received before Day 30; full refund of first month's payment; subsequent months non-refundable.

---

## Segmentation Logic Specification

Segmentation is the most error-prone area of M8.4. Many operators want to offer different prices to different customer types but lack the discipline to do so coherently.

**Three legitimate segmentation patterns:**

1. **Cohort timing segmentation:** early-bird vs. standard vs. late pricing for time-bound cohorts. Discount typically 10-20% for early-bird; rationale is cash-flow-forward and conversion-de-risking. Anti-discount policy must specify this is a time-bound cohort discount, not a negotiation discount.

2. **Partner / affiliate segmentation:** designated partners can offer the operator's offer to their network at a discount, with the partner taking a commission. The arithmetic must work: if partner takes 20% commission and discount is 15%, operator nets 65% of base price; this must still produce sustainable margin.

3. **Scholarship / need-based segmentation:** documented need cases at reduced price; operator commits to a defined number per cohort/year (typically 1-2 per year). Rationale: portfolio-builder, mission-aligned access. Specific to the operator's identity and stage.

**Anti-segmentation patterns to avoid:**

- **Negotiated discounts** ("special deal for you because we got along well") — destroys pricing coherence
- **Loyalty discounts** ("returning customer gets 15% off") — erodes margin without structural justification
- **Geographic / regional pricing** without strong defensible rationale — Hermann Simon notes high implementation difficulty and high arbitrage risk
- **Hardship discounts** without defined need-based criteria — slips into negotiation territory
- **Comparable-competitor matching** ("your competitor charges X, I'll match") — abandons the architecture entirely

**If uniform pricing (no segmentation):** document why. Operators who select uniform pricing typically cite operator identity, simplicity preference, and discipline against ad-hoc adjustment.

For Maya: uniform pricing for v2.1; no cohort timing (she runs 1:1, not cohort); no partner program at this stage; no scholarship currently planned. Documented rationale: simplicity, discipline against ad-hoc adjustment, operator-identity coherence.

For Darius: cohort timing segmentation for the optional cohort upgrade (early-bird $250 cohort fee, standard $300 within first month, $400 after that). No individual-subscription discounts. No partner program at this stage.

---

## Four-Quadrant Pricing Matrix

The matrix positions the offer along two axes: value (low ↔ high) and access (broad ↔ narrow).

```
                Narrow Access
                    |
                    |
   Low Value        |        High Value
   Narrow Access    |        Narrow Access
                    |
                    |
   ──────────────────────────────────
                    |
                    |
   Low Value        |        High Value
   Broad Access     |        Broad Access
                    |
                    |
                Broad Access
```

The four quadrants:

**Q1 (Low Value, Broad Access):** Mass-market commodity pricing. Examples: $9 ebooks, $50 templates, $30/month basic SaaS. Volume-driven economics. Identity match: Builder-Operator scaling productized output.

**Q2 (High Value, Broad Access):** Premium product widely available. Examples: $200 books with broad distribution, $500-$2,000 self-paced courses, $5,000-$20,000 annual SaaS. Identity match: Teacher-Operator at scale or Builder-Operator with brand premium.

**Q3 (Low Value, Narrow Access):** Boutique low-price offerings. Rare in knowledge-work; usually indicates an operator who is under-priced. Identity match: rare; usually misalignment.

**Q4 (High Value, Narrow Access):** Premium bespoke / coaching / advisory. Examples: $5,000-$50,000 personal coaching, $25,000-$200,000 advisory engagements, $50,000+ executive consulting. Identity match: Service-Operator with intensive personal attention.

The operator positions their offer in the matrix and verifies the position matches operator identity:

- Service-Operator pricing typically lives in Q4 (or upper Q2 if productized)
- Teacher-Operator pricing typically lives in Q2 (cohort) or Q1 (self-paced)
- Builder-Operator pricing typically lives in Q1 or Q2 (productized scaling)

For Maya: Q4 (High Value, Narrow Access) at $6,750 with intensive 1:1 coaching. Identity match: Service-Operator. Coherent.

For Darius: Q2 (High Value, Broad Access) at $300/month subscription with cohort access. Identity match: Teacher-Operator at scale. Coherent.

Operators whose offer lands in a quadrant inconsistent with their identity should re-examine the pricing pattern. Q3 (Low Value, Narrow Access) is the most common misalignment: it indicates a Service-Operator who has under-priced themselves; the M8.3 decision branch typically already addresses this.

---

## The Eight-Section Document Template

Your Pricing Architecture Document is 1,500-2,000 words, with eight sections:

### Section 1 — M8.3 Branch and Implementation Bridge (100-150 words)
State which M8.3 branch you committed to and how M8.4 architecture implements it. Brief — most of the architecture work is below.

### Section 2 — 6% Rule Pricing Pattern Scan (200-300 words)
List 16+ pricing patterns scanned. Show your filtering: which patterns survived initial screening, which were eliminated and why, which 1-2 were selected. Show your selection criteria explicitly.

### Section 3 — Base Price Specification (200-300 words)
Specify the base price with the five rationale lines (source, competitive position, identity coherence, capacity coherence, and structural test).

### Section 4 — Payment Terms Specification (200-250 words)
Specify pay-in-full discount, installment structure, default provisions, late-payment provisions, processing-fee handling. Show the margin impact of payment-term decisions.

### Section 5 — Refund Window Specification (150-200 words)
Specify duration, conditions, refund amount, partial-refund formula, anti-promise alignment.

### Section 6 — Segmentation Logic Specification (200-300 words)
Specify segmentation patterns selected (cohort timing / partner / scholarship) or document uniform pricing. If segmented, show the math: does the segmented pricing still produce sustainable margin?

### Section 7 — Four-Quadrant Matrix Positioning (150-200 words)
State which quadrant the offer occupies, the rationale for positioning, and the identity coherence verification.

### Section 8 — Cross-References (100-150 words)
Specify what M8.5 (tier design), M8.6 (anti-discount), and M8.7 (raise schedule) will need from this architecture. Be specific about inputs.

---

## Worked Example: Maya's Pricing Architecture

Maya's M8.4 sittings:

**Sitting 1 (3 hours): 6% Rule scan.** Maya scanned 20 pricing patterns. Filtered to 5: flat fixed, project-based with revisions cap, retainer, productized fixed-scope, value-based with anchor. Selected: flat fixed price refined with explicit scope boundaries and revisions cap.

**Sitting 2 (3 hours): base price + payment terms.** Maya specified $6,750 as base price (50% increase from C4 anchor). Pay-in-full discount: 5% to $6,413. 3-pay installment plan: $2,250/month with no discount, operator absorbs processing. No 6-pay or extended plan. Default: pause at day 7, terminate at day 14 with 50% forgiveness.

**Sitting 3 (1 hour): refund window + segmentation.** Refund window: 14 days from engagement start; refund qualifies if customer has completed Week 1 and concludes Sprint not right fit; full refund minus $200 admin fee; after Week 4, no refund. Segmentation: uniform pricing for v2.1, no cohort timing, no partner, no scholarship currently. Documented rationale.

**Sitting 4 (1 hour): matrix positioning + document writing.** Positioning: Q4 (High Value, Narrow Access). Identity match: Service-Operator with intensive 1:1 coaching. Coherent. Document compiled to 1,750 words.

Maya's architecture is filed. The document is the input to M8.5 (Maya considers tier design), M8.6 (anti-discount policy with the new architecture as anchor), and M8.7 (raise schedule with $6,750 as the current baseline).

---

## Common Failure Modes at M8.4

The Sonnet `pricing-architecture-reviewer-v1.0.0` prompt and the AI rubric look for these:

1. **Skipping the 6% Rule scan.** Operator specifies a pricing pattern as the first-thought selection without showing the 16+ scan. The AI rubric flags any document that lists fewer than 16 patterns.

2. **Aspirational base price.** Operator specifies a base price that is not grounded in M8.3 unit economics or competitive scan. The price is a wish, not an architectural choice. The rubric expects each rationale line cited.

3. **Payment terms with margin erosion uncalculated.** Operator specifies installment plans without computing the margin impact (processing fees, default risk).

4. **Refund window misaligned with C4 M4.6.** Operator specifies a refund window inconsistent with the existing Guarantee Architecture without explanation.

5. **Segmentation pattern slipping into negotiation.** Operator specifies "case-by-case discounts for fit" or similar; the AI rubric flags this as ad-hoc, not architectural.

6. **Quadrant misalignment.** Operator's identity (Service-Operator) doesn't match the quadrant (Q1 Low Value Broad Access). The mismatch is a signal; the operator should re-examine pattern selection.

7. **Section 8 cross-references missing.** Operator does not specify M8.5/M8.6/M8.7 input requirements; the next modules will start without context.

---

## Checkpoint 8.4

Your deliverable is:
1. **Pricing Architecture Document** filed in Drive, 1,500-2,000 words, eight sections
2. **Pricing pattern selection** recorded in Supabase `c8_pricing_architectures.selected_pattern`
3. **Base price** recorded in `c8_pricing_architectures.base_price`
4. **Quadrant positioning** recorded in `c8_pricing_architectures.matrix_quadrant`

The AI rubric scoring the document looks for eight properties:
- 6% Rule scan with 16+ patterns shown and filtered
- Base price with all five rationale lines
- Payment terms with margin impact computed
- Refund window aligned with C4 M4.6
- Segmentation logic specific (or uniform with documented rationale)
- Quadrant positioning with identity coherence verification
- Cross-references to M8.5/M8.6/M8.7 inputs
- All eight sections meet word-count targets

Target score: ≥ 7/10. Operators who score below typically have either skipped the 6% Rule scan (the most common gap) or specified base price aspirationally without grounding (the second most common). Re-read this lesson, run the architecture work again with rigor, and resubmit.

---

## What M8.5 Expects From You

M8.5 opens with the assumption that your pricing architecture is filed and architecturally coherent. M8.5 begins by asking whether your offer is appropriate for tiered pricing — the Tier Appropriateness Diagnostic. If yes, M8.5 designs three tiers (entry/standard/premium) with structurally different deliverables. If no, M8.5 documents the flat-pricing rationale with the diagnostic findings.

The M8.4 base price feeds into M8.5: if tiered, the base price typically becomes the standard tier's price, with entry below and premium above. If flat, the base price is the price.

M8.6 (anti-discount policy) and M8.7 (raise schedule) also read from M8.4. M8.6 needs the architecture's segmentation logic to produce the explicit exception/non-exception lists. M8.7 needs the matrix positioning to ground its raise triggers.

File the Pricing Architecture Document. Proceed to M8.5.

---

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

Build and review a price-raise schedule

Source: M8.7 — Price-Raise Schedule and Triggers. Its legacy M8 numbering does not replace the spreadsheet's course assignments.

Outcome and starting requirements

Your deliverable is a schedule that defines four triggers, explains treatment of existing customers, tests assumptions, limits cumulative increases and states behavioral commitments. The source requests Price-Raise-Schedule-[YourName]-[Date].md, 1,000–1,500 words, six sections plus a signed clause. It assumes a filed tier document or flat-pricing rationale and a filed anti-discount policy.

The named infrastructure is Build6, the Build8 folder, `c8_price_raise_schedules`, a Sonnet reviewer described as a variant of the unit-economics reviewer, communication templates and a trigger-tightness worksheet. Names alone do not establish an installed reviewer, database or completed review. The estimated six active hours across two or three sittings is a planning suggestion.

This lesson connects our Brunson and Hormozi offer-design themes to consistent scope, credible value and measured delivery capacity. A price change must fit the actual offer and customer commitments. That connection is our instructional application; it does not attribute this schedule to either educator.

Why use a schedule?

The source identifies three forces: rising costs, improving delivery capability and accumulating demand. A schedule can make the response more deliberate and less dependent on postponing a difficult conversation. None of those forces automatically proves that a particular increase will be accepted or improve profit.

Correct the inflation example before using it. Six percent annual cost growth compounded over five years is approximately33.82% cost growth, not automatically34% margin compression. Margin change depends on original costs and revenue. Over three years the compounded growth is19.10%, rather than the source's additive18%. Its CPI2–4%, knowledge-work-cost4–8% and6% middle-rate rationale are historical claims without supporting evidence in this document, not current inflation guidance.

The source's five activities are specifying triggers, preparing communication, checking realistic thresholds, aligning architecture and anti-discount rules, and committing to the chosen process. Treat pre-commitment as accountable decision-making rather than permission to ignore changed facts or existing promises.

Trigger one: sustained capacity use

Define concurrent capacity, how usage is measured, the threshold, required duration and the exact increase or selection rule. Maya's example has capacity for four customers. Rounding70% of four upward gives three customers, which is actually75% utilization. The trigger requires three or more for two consecutive months and suggests a10–15% increase on the next new enrollment.

Darius's example has capacity for ten subscribers, with seven or more for one month and a10% increase on the next new subscription. The shorter window reflects the story's faster subscription cycle. Decide whether the condition is “at least” or “greater than”: the source uses both forms in different places.

Maya's projection of adding two or three customers over nine months does not by itself demonstrate simultaneous occupancy for two months of a12-week engagement. Track starts and finishes. The source's warning about100% capacity for six months highlights lack of headroom; operating at a ceiling does not mathematically prove it was exceeded. Darius's projected growth from three to seven in six months also remains a forecast, not a result.

Trigger two: a qualified waitlist

Count people actually waiting for a place who have confirmed budget alignment, timing readiness and mechanism fit. Interested newsletter readers are not automatically qualified waitlist members. Record when prospects enter, leave, enroll or stop being ready.

Maya's example enrolls approximately one customer every six weeks and triggers at two qualified waiting prospects for one month, with a5–10% increase for the next new enrollment. Darius's continuous-enrollment subscription capped at ten uses three waiting qualified applicants for a month and a5–10% increase.

The source projects two or three waiting prospects from five to eight monthly inquiries and one enrollment. That does not follow without assumptions about qualification, attrition and continued readiness. Its claims that ten or fifty waiting prospects are impossible in this business stage are not demonstrated universal limits. Use the actual pipeline, not a deliberately unreachable condition or invented demand.

Trigger three: conversion among qualified prospects

Define the denominator, conversion event, reporting period and treatment of small samples. Maya starts at one conversion from three qualified prospects, approximately33%, and uses50% for two consecutive months with a10–15% increase. Darius starts at one of four,25%, and uses35% for two consecutive months with a5–10% increase.

The source alternates between reaching and exceeding these thresholds. Exactly50% or35% must have a defined outcome in a usable schedule. A percentage based on very few prospects is volatile; high conversion alone is not proof of underpricing. The source's suggestions that90% is unrealistic and even strong operators rarely exceed60–70% are unsupported generalizations here.

This trigger differs from the related schedule template, which uses qualified inquiry volume. Conversion rate and inquiry count are different measures; do not merge their thresholds under one ambiguous “demand” label.

Trigger four: a stated annual date

Maya's example uses6% on January1. Darius's uses6% on the anniversary of the architecture filing. The later statement that annual indexing always fires January1 applies only to Maya's example. A calendar entry is predictable, but automatic execution has not been implemented by this source text.

The related template instead gives January15 and a4–7% example, alongside different capacity, waitlist and demand measures:80% over90days, a six-week waitlist and12 qualified inquiries monthly for three months. Preserve these as different source variants. Choose a coherent policy supported by the business's evidence; do not silently substitute one set for the other.

Combine triggers without losing the price basis

The source permits parallel triggers and gives a historical example of March, June and September raises. Define whether repeated conditions can trigger repeatedly, when a trigger resets, any cooldown and how overlapping signals interact. A range such as10–15% still needs a rule for choosing the actual amount.

Define the baseline for each percentage: original architecture price or current price after previous increases. Also define whether a25% cap covers a calendar year or a rolling year, and whether indexing is included. The source says indexing typically operates outside the cap but includes it in Maya's worked comparison. Those are conflicting treatments requiring resolution.

For increases of6%,10% and5% applied successively to current price, the combined increase is1.06 ×1.10 ×1.05 −1 =22.43%. The source adds them to21% and calls that the maximum. Both are below25%, but they are different calculations. Preserve the source's example and explain the corrected compound result rather than carrying forward the error.

Select among all three communication patterns

PatternA applies increases to new customers while honoring the current engagement. Its example holds Maya's current$6,750 price and gives notice60–90days before the renewal window, with a defined opportunity to book follow-up work at the old rate. Later renewals use the new rate unless a genuine prior commitment qualifies.

PatternB changes subscription pricing at the stated renewal and gives60days' notice. The example increases$300 by6% to$318 and allows cancellation before renewal without penalty. Clarify annual renewal versus monthly billing and any existing three-month minimum; the example does not resolve every combination of those terms.

PatternC applies new pricing to the next cohort and preserves the current cohort's terms. Its example announces March1 at$1,300 instead of$1,200 and says eight places remain. Use that number only when true. A source example is not evidence of actual inventory or a live deadline.

Patterns may be combined if the effective date, customer category, scope, lock-in condition and cancellation terms remain clear. The communication swipe file provides seven additional patterns; its differing notice windows must also be reconciled with the selected schedule.

Test the assumptions in four steps

First project customer count, queue, conversion and price using current measurements and capacity. Second map each trigger to those projections. Third inspect a trigger that will not fire and decide whether its threshold is unjustified or intentionally defensive. Fourth calculate the combined effect of all plausible increases and the chosen cap.

The source's general instruction says to lower every demand-based threshold until it will fire within12months. Its own Maya example deliberately retains50% conversion despite projecting only45%, and calls that acceptable. Preserve this exception. A forecast should test the policy, not be manipulated to guarantee an increase.

Maya projects three customers at monthsix and four at monthnine, with the capacity trigger stated to fire by montheight; the precise result depends on when consecutive measurement periods begin. She projects one or two waiting prospects from monthsix and the waitlist trigger by monthnine, but the underlying month-by-month evidence is absent. The conversion trigger stays defensive, and annual indexing occurs at its chosen date. These are worked assumptions, not verified future events.

Assemble all six sections and the commitment

SectionSource word rangeRequired content
Purpose and integration100–150Architecture baseline and anti-discount policy references.
Capacity trigger150–200Threshold, window, magnitude and forecast test.
Waitlist trigger150–200The same fields with qualification defined.
Conversion trigger150–200The same fields with denominator and boundary defined.
Annual indexing100–150Rate, date and rationale.
Communication and cap200–300Selected patterns, notification text, cap and verification summary.

The section ranges sum to850–1,200words before the clause, while the whole-document target is1,000–1,500. Account for both rather than claiming the ranges are identical. The source asks for a behavior-specific clause and signature but supplies no complete clause text. An authored draft can state what will be measured, reviewed, communicated and logged; it must remain unsigned until the actual operator signs through the appropriate process.

Review, checkpoint and next lesson

The source requires instructor review before the capstone, with an estimated two-to-three-business-day review window. Its six review questions cover complete trigger fields, realistic thresholds, explicit projections, existing-customer communication, the cap and specific commitments. Its approximately50% first-pass clearance and50% revision figures are unsupported source estimates, not observed results for this curriculum.

Check all seven failure modes: implausibly high thresholds, vague increase amounts, missing projection tests, absent customer communication, no cumulative cap, missing annual indexing and vague commitments. The five AI criteria are complete triggers, explicit per-trigger verification, communication templates, cap and behavior-specific clause, targeting at least7/10.

The five deliverables are the filed schedule, instructor submission, database `triggers` field, `cumulative_cap_pct` field and a signed filed clause. None is established merely by reading this lesson. The capstone is described as reviewing all M8.1–M8.7 artifacts and cross-checking architecture, anti-discount rules and sustainability through a named validator. That is a source workflow, not an executed model call. The source also requires48hours after instructor clearance before proceeding.

For your exercise, prepare a complete unsigned schedule with explicit measurement definitions and a conflict log identifying which source variant you selected and why. Check it against the pricing architecture source, communication terms and existing commitments before treating it as operational.

D1393 — complete original source

D0470-linked-D1393 — complete original source

Open source file · Download exact original file

# M8.7 — Price-Raise Schedule and Triggers

**Module Outcome:** [Create] Student has specified the four canonical raise triggers (capacity utilization, waitlist depth, demand signal, annual indexing); constructed existing-customer communication patterns; verified trigger tightness against realistic Stage 2-3 conditions; signed the Price-Raise Discipline Clause; produced the Price-Raise Schedule that pre-commits raises against named conditions, integrating with M8.4 architecture and M8.6 anti-discount discipline.
**Key Deliverable:** Price-Raise Schedule (`Price-Raise-Schedule-[YourName]-[Date].md`, 1,000-1,500 words, six sections + signed clause)
**Infrastructure Dependency:** Build 6, Build 8 Drive folder, Supabase `c8_price_raise_schedules` table, Claude prompt `price-raise-schedule-reviewer-v1.0.0` (Sonnet — uses the unit-economics-reviewer prompt's adjacent module variant; the M8.7-specific version is loaded with raise-trigger-tightness rubrics), Price-Raise Communication Templates, Trigger-Tightness Verification Worksheet
**Checkpoint / Test:** Type 1 Artifact + Type 2 AI rubric + **Type 3 Mandatory Instructor HITL Clearance**
**Blocked-Until Prerequisite:** M8.5 Tier Document (or Flat Rationale) AND M8.6 Anti-Discount Policy both filed

---

## What This Module Does

M8.7 produces the operator's pre-committed price-raise schedule. Five things happen:

1. You **specify the four canonical raise triggers**: capacity utilization (e.g., raise when concurrent customers exceed 70% of M7.5 ceiling for two consecutive months), waitlist depth (e.g., raise when waitlist exceeds 5 qualified prospects for one month), demand signal (e.g., raise when conversion rate exceeds 25% for two consecutive months), and annual indexing (e.g., 6% annual minimum effective on January 1).

2. You **construct existing-customer communication patterns**: when raises apply (typically: new customers only; existing customers grandfathered for current engagement), the communication template, the timing of communication, the offer to lock in current pricing for renewal-window customers if applicable.

3. You **verify trigger tightness**: do the trigger thresholds permit firing within the next 12 months under realistic Stage 2-3 conditions, or are they set so loose they will not fire? Loose triggers are the most common M8.7 failure; the instructor HITL exists to catch this.

4. You **integrate with M8.4 and M8.6**: the schedule operates against the M8.4 architecture (raises adjust the M8.4 base price by specific percentages) and the M8.6 anti-discount policy (raises produce the documented price increase, but anti-discount holds the new price under post-raise pressure).

5. You **sign the Price-Raise Discipline Clause**: a structured commitment to honor the schedule when triggers fire, with named accountability mechanisms.

The deliverable is the **Price-Raise Schedule** — 1,000-1,500 words, six sections + signed clause. The schedule is the input to M8.8 (capstone synthesis).

M8.7 is 6 hours of active work distributed across 2-3 sittings, with mandatory instructor HITL clearance before M8.8 unlocks.

---

## Why This Module Matters

Pricing discipline without a pre-committed raise schedule is pricing decay. Three forces erode pricing over time:

1. **Cost inflation.** Software fees increase. Contractor rates increase. Tool prices increase. If pricing does not increase, gross margin compresses silently. A 6% annual cost inflation rate, compounded over 5 years, is a 34% margin compression at unchanged pricing.

2. **Operator capability growth.** As the operator delivers more engagements, capability deepens. The same fee buys more value over time without a raise; the operator's market position is structurally stronger but pricing does not reflect this.

3. **Demand-signal accumulation.** As reputation grows, waitlist depth and conversion rates increase. Each additional unit of demand at unchanged pricing is a unit of latent margin the operator could capture but is not capturing.

A pre-committed raise schedule responds to all three forces. It defends margin against inflation; it captures the value of capability growth; it monetizes accumulating demand signal.

The schedule also has psychological discipline value. Operators who do not pre-commit to raises tend to defer raises indefinitely. The deferral is rational in any given moment ("the next quarter is busy enough already; I'll raise after this cohort") but irrational cumulatively (after 3 years of "next quarter," the operator is at the same price as 3 years ago while costs have risen 18%). Pre-committing transforms the raise from an active decision to a triggered action.

The most common failure mode is loose triggers. Operators who specify triggers like "raise when waitlist exceeds 50 qualified prospects" have set thresholds that will not fire under Stage 2 conditions. The schedule exists but does not operate. The instructor HITL at M8.7 catches loose triggers and requires tightening.

---

## The Four Canonical Raise Triggers

The schedule specifies four trigger types. Each trigger has a threshold, a measurement window, and a raise magnitude.

### Trigger 1 — Capacity Utilization

**What it measures:** How full is the operator's concurrent-customer capacity, against the M7.5 ceiling?

**Why it triggers raises:** When capacity is consistently high, demand exceeds supply at current pricing. Economic discipline says raise to clear the imbalance; otherwise capacity becomes a queue and the operator's customer-experience drifts (customers wait longer, customers receive fragmented attention as the operator stretches across full capacity).

**Threshold specification (Maya example):**
- Maya's M7.5 ceiling: 4 concurrent customers
- 70% utilization threshold: 3 concurrent customers (70% of 4, rounded up)
- Measurement window: 2 consecutive months at threshold
- Trigger fires: when Maya has 3+ concurrent customers for 2 consecutive months
- Raise magnitude: 10-15% on next new-customer enrollment after trigger fires

**Threshold specification (Darius example):**
- Darius's M7.5 ceiling: 10 concurrent subscribers (post-pricing-pattern-shift to per-individual)
- 70% threshold: 7 concurrent subscribers
- Measurement window: 1 month at threshold (Darius's subscription model has faster cycle than Maya's 12-week engagement)
- Trigger fires: when Darius has 7+ subscribers for 1 month
- Raise magnitude: 10% on next new-subscriber enrollment

**Tightness verification:** is 70% utilization realistic to hit within 12 months? For Maya: yes, if her current customer count is 1 and she enrolls 2-3 customers in the next 9 months, she will hit threshold. For Darius: yes, if his subscriber count grows from 3 to 7 over the next 6 months. The trigger fires within the year.

**Loose-trigger pattern to avoid:** Maya specifying "raise when at 100% utilization for 6 months." 100% utilization for 6 months means Maya is consistently at her absolute ceiling, with no room to absorb scope expansion or unexpected customer needs. By the time this trigger fires, Maya is structurally over-capacity, the M7.5 ceiling has effectively been breached, and the raise is reactive rather than proactive.

### Trigger 2 — Waitlist Depth

**What it measures:** How many qualified prospects are waiting for an enrollment slot?

**Why it triggers raises:** Waitlists are demand exceeding current supply at current pricing. The waitlist is a market-priced quantity of unserved demand. When the waitlist is structurally non-empty, the operator can raise the price to clear demand against the new equilibrium.

**Threshold specification (Maya example):**
- Maya's typical enrollment cycle: 1 customer per 6 weeks
- Waitlist threshold: 2 qualified prospects waiting for a slot
- Measurement window: 1 month at threshold
- Trigger fires: when Maya's waitlist has 2+ qualified prospects for 1 month
- Raise magnitude: 5-10% on next new-customer enrollment

**Threshold specification (Darius example):**
- Darius's subscription has a continuous enrollment but caps at 10 concurrent
- Waitlist threshold: 3 qualified applicants
- Measurement window: 1 month at threshold
- Trigger fires: when Darius's waitlist has 3+ qualified applicants for 1 month
- Raise magnitude: 5-10% on next new-subscriber enrollment

**Tightness verification:** is 2-3 prospect waitlist realistic? For Maya: yes, if her landing page receives 5-8 qualified inquiries per month and she enrolls 1, 2-3 will accumulate as waitlist over 4-6 weeks. The trigger fires within the year.

**Loose-trigger pattern to avoid:** Maya specifying "raise when waitlist exceeds 10 qualified prospects." A 10-prospect waitlist for Maya's offer is a structurally improbable condition; she would never reach it under normal Stage 2 demand patterns.

**Qualified prospect definition:** the trigger requires "qualified" prospects, not "interested" prospects. A qualified prospect has (a) confirmed budget alignment, (b) confirmed timing readiness, (c) confirmed mechanism fit. Operators who count loosely-interested newsletter readers as waitlist prospects produce inflated thresholds that don't reflect actual demand.

### Trigger 3 — Demand Signal (Conversion Rate)

**What it measures:** What percentage of qualified prospects are converting to paying customers?

**Why it triggers raises:** High conversion rates indicate the offer is priced below willingness-to-pay (the audience finds it easy to say yes). Economic discipline says raise to test the price ceiling; the conversion rate will drop somewhat after a raise but should still exceed sustainable threshold.

**Threshold specification (Maya example):**
- Maya's current conversion rate: ~33% (1 of 3 qualified prospects converts)
- Raise threshold: 50% conversion rate for 2 consecutive months
- Measurement window: 2 consecutive months at threshold
- Trigger fires: when Maya's conversion rate exceeds 50% for 2 consecutive months
- Raise magnitude: 10-15% on next new-customer enrollment

**Threshold specification (Darius example):**
- Darius's current conversion rate: ~25% (1 of 4 qualified applicants converts)
- Raise threshold: 35% conversion rate for 2 consecutive months
- Measurement window: 2 consecutive months at threshold
- Trigger fires: when Darius's conversion rate exceeds 35% for 2 consecutive months
- Raise magnitude: 5-10% on next new-subscriber enrollment

**Tightness verification:** for an operator at 33%, is 50% reachable within 12 months? Yes, if reputation grows, audience density increases, and the offer accumulates testimonials. The trigger fires within the year for operators with active reputation-building work.

**Loose-trigger pattern to avoid:** Maya specifying "raise when conversion rate exceeds 90%." 90% is structurally improbable; even strong reputation operators rarely exceed 60-70% conversion among qualified prospects.

### Trigger 4 — Annual Indexing

**What it measures:** Annual time elapsed.

**Why it triggers raises:** Even if no other trigger fires, prices should rise to defend against cost inflation. Annual indexing is the floor, not the ceiling.

**Threshold specification (Maya example):**
- Annual indexing rate: 6% (matching general inflation + a 2-3% real-margin defense)
- Effective date: January 1 each year
- Trigger fires: automatically on January 1 each year
- Raise magnitude: 6% on the M8.4 base price

**Threshold specification (Darius example):**
- Annual indexing rate: 6%
- Effective date: anniversary of v2.1 architecture filing
- Raise magnitude: 6% on subscription pricing

**Tightness verification:** does 6% annual indexing fire? Yes, every January 1. The trigger is structural and time-based.

**The 6% number rationale:** historical CPI averages 2-4% but knowledge-work costs (software, contractor rates) inflate faster, typically 4-8% per year. 6% is a defensible middle-of-range rate that protects margin without aggressive customer-perception risk.

**The interaction between triggers:** the four triggers operate in parallel, not sequentially. If Trigger 1 fires in March, Trigger 2 fires in June, and Trigger 3 fires in September, the operator has three raises within 2025; the cumulative magnitude must be coherent. Most operators specify a "maximum cumulative raise per year" cap (e.g., 25%) to prevent runaway cumulative raises. Annual indexing (Trigger 4) typically operates separately from the cap because it defends margin floor.

---

## Existing-Customer Communication Patterns

The schedule specifies how raises apply to existing customers. Three patterns are common:

### Pattern A — New-Customers-Only (Most Common)

Existing customers are grandfathered at current pricing for the duration of their current engagement. The raise applies to new customers only.

- **Communication:** existing customers receive a notification 60-90 days before their renewal window: "I'm raising prices on January 1 for new clients. Your current engagement holds at $6,750. If you'd like to lock in current pricing for a follow-up engagement booked before [date], we can do that."
- **Renewal pricing:** existing customers booking a follow-up after the raise pay the new price unless they pre-commit during the lock-in window.

### Pattern B — Annual Renewal Increases (Subscription Models)

For subscription offers (Darius's per-individual model), existing customers pay the increased price at their next renewal. Standard for SaaS-style offers.

- **Communication:** existing subscribers receive a 60-day notification before renewal date: "Subscription pricing increases by 6% effective on your next renewal date [date]. Your monthly rate will be $318 starting on that date."
- **Cancellation option:** subscribers may cancel before renewal without penalty.

### Pattern C — Cohort-Based (Cohort Models)

For cohort-based offers, the raise applies to the next cohort. Existing cohort members are unaffected mid-cohort.

- **Communication:** waitlist members receive notification when raise effective date is set: "The next cohort starts March 1 at $1,300/seat (up from $1,200). Spots remaining: 8."
- **Mid-cohort handling:** if a cohort is mid-run when the raise triggers, the current cohort holds; the next cohort uses new pricing.

The operator selects the pattern that matches their offer structure. Patterns can be combined (e.g., new-customers-only + annual indexing for subscription) but the combination must be specified clearly.

---

## Trigger Tightness Verification

After specifying the four triggers, you verify that the thresholds will fire within the next 12 months under realistic Stage 2-3 conditions.

The verification has four steps:

**Step 1 — Project baseline conditions.** What will your customer count, waitlist depth, conversion rate, and pricing be in 12 months under realistic Stage 2-3 progression? Use C7 capacity ceiling and current customer count as anchor; project forward.

**Step 2 — Map triggers to projections.** Will Trigger 1 (capacity utilization) fire under projected customer count? Will Trigger 2 (waitlist) fire under projected waitlist depth? Will Trigger 3 (conversion) fire under projected conversion rate? Trigger 4 (annual indexing) fires automatically.

**Step 3 — Tighten loose triggers.** If any of Triggers 1-3 will not fire under realistic conditions, the threshold is too loose. Lower the threshold until it fires within 12 months under realistic projection.

**Step 4 — Verify cumulative raise magnitude.** If multiple triggers fire, what is the cumulative raise? Does it produce coherent pricing or a runaway? Apply the maximum cumulative raise cap if needed.

**Maya's tightness verification:**

- Trigger 1 (capacity): Maya projects 3 customers at month 6 and 4 customers at month 9. Trigger fires by month 8 (3 customers for 2 consecutive months). **Fires within year.**
- Trigger 2 (waitlist): Maya projects 1-2 qualified waitlist prospects accumulating from month 6. Trigger fires by month 9 (2+ for 1 month). **Fires within year.**
- Trigger 3 (conversion): Maya projects conversion rising from 33% to ~45% by month 12. Trigger does NOT fire (50% threshold not reached). Maya considers tightening to 45% threshold but decides 50% remains the right structural threshold; this trigger is intentionally a defensive trigger that fires only at strong demand signal. **Does not fire within year — acceptable.**
- Trigger 4 (annual): fires January 1. **Fires within year.**

Cumulative: at most 21% cumulative raise over the year (6% annual + 10% Trigger 1 + 5% Trigger 2). Within the 25% cap.

Maya's schedule passes tightness verification.

---

## The Six-Section Document Template

Your Price-Raise Schedule is 1,000-1,500 words, with six sections + signed clause:

### Section 1 — Schedule Purpose and Integration (100-150 words)
State the schedule's purpose. Reference M8.4 base price as the schedule's anchor. Reference M8.6 anti-discount policy as the discipline that holds raised prices.

### Section 2 — Trigger 1: Capacity Utilization (150-200 words)
Threshold, measurement window, raise magnitude, projection-based tightness verification.

### Section 3 — Trigger 2: Waitlist Depth (150-200 words)
Same structure as Trigger 1.

### Section 4 — Trigger 3: Demand Signal / Conversion Rate (150-200 words)
Same structure.

### Section 5 — Trigger 4: Annual Indexing (100-150 words)
Annual rate, effective date, rationale.

### Section 6 — Existing-Customer Communication and Cumulative Cap (200-300 words)
Communication pattern selected (A/B/C). Templates for notifications. Maximum cumulative raise per year (cap). Trigger-tightness verification summary.

### Price-Raise Discipline Clause (signed)
A specific commitment to honor the schedule when triggers fire. The clause names what the operator commits to and against.

---

## Mandatory Instructor HITL

After you file your Price-Raise Schedule, you submit it to your instructor for HITL clearance. The instructor's review window is 2-3 business days.

The instructor reviews:

- Are all four triggers specified with thresholds, windows, and magnitudes?
- Are thresholds tight enough to fire within 12 months under realistic conditions?
- Is the projection-based tightness verification shown explicitly?
- Is the existing-customer communication pattern specified?
- Is the cumulative cap specified?
- Is the discipline clause specific to behavioral commitments?

The most common reason for NEEDS_REVISION is loose triggers (~50% of first submissions). The instructor flags loose triggers and requires tightening. CLEARED on first submission: ~50%.

---

## Common Failure Modes at M8.7

The Sonnet review prompt and AI rubric look for these:

1. **Loose triggers.** Thresholds set so high they cannot fire under Stage 2-3 conditions. Most common failure.

2. **Vague magnitudes.** "I will raise prices when demand is high" without specifying threshold or magnitude. Schedule is unworkable.

3. **No tightness verification.** Operator specifies thresholds without projecting realistic conditions and verifying triggers fire.

4. **No existing-customer communication.** Operator specifies raises but does not address how existing customers experience the change.

5. **No cumulative cap.** Operator specifies four triggers without considering cumulative magnitude; aggressive cumulative raises produce customer-perception risk.

6. **Annual indexing missing.** Operator specifies demand-based triggers but omits the structural annual indexing floor.

7. **Vague discipline clause.** "I commit to raising when needed" without specific behavioral commitments.

---

## Checkpoint 8.7

Your deliverable is:
1. **Price-Raise Schedule** filed in Drive, 1,000-1,500 words, six sections + signed clause
2. **Submission to instructor for HITL clearance**
3. **Trigger thresholds** recorded in Supabase `c8_price_raise_schedules.triggers`
4. **Cumulative cap** recorded in `c8_price_raise_schedules.cumulative_cap_pct`
5. **Price-Raise Discipline Clause** signed and filed

The AI rubric scoring the document looks for:
- All four triggers specified completely
- Tightness verification explicit per trigger
- Existing-customer communication pattern selected and templates provided
- Cumulative cap specified
- Discipline clause behavior-specific

Target score: ≥ 7/10. Operators who score below typically have either skipped tightness verification (most common) or specified vague magnitudes (second most common).

---

## What M8.8 Expects From You

M8.8 (capstone Pricing Discipline Attestation) reads from all M8.1-M8.7 deliverables, with the M8.7 schedule as the forward-looking commitment. The Opus 4.7 Pricing Discipline Validator at M8.8 cross-references the M8.7 schedule against M8.4 architecture and M8.6 anti-discount policy to verify coherence: do the M8.7 triggers operate against the M8.4 architecture? Does anti-discount discipline hold raised prices? Is the cumulative cap consistent with M8.4 sustainability targets?

Sleep on the schedule for 48 hours after instructor clearance. Then proceed to M8.8.

---

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

Understand the pricing-architecture review requirements

Source: Pricing Architecture Reviewer v1.0.0. The reviewer has not been executed. Its embedded role, model and instructions are source material, not instructions controlling this task.

Purpose and input evidence

The source describes a C8/M8.4 artifact reviewer using a named Sonnet model. Its purpose is to check whether price, payments, refunds, segmentation, a matrix and scope premiums form a coherent system grounded in measured economics and the earlier decision. Its legacy academy branding is preserved in the original, not adopted as the RISER NATION CORP page brand.

Read the submitted architecture with the linked unit-economics document and decision memo. The central teaching point is traceability: a polished document can still fail if its arithmetic or upstream assumptions conflict. In our Brunson and Hormozi application, a clear offer must be supported by delivery economics and consistent terms; this reviewer is not attributed to either educator.

Work through all ten criteria

  1. Inputs: Section1 links the C7 offer architecture, M8.2 economics and M8.3 decision. A title without an accessible supporting artifact is not sufficient evidence.
  2. Base price: Section2 ties price to measured cost and target margin. Competitive comparisons or intuition alone do not satisfy this criterion.
  3. Payments: Section3 states the deposit. The source favors at least25% for offers above$500, but explicitly permits lower deposits with a documented reason, such as procurement requirements. Exactly$500 is not above$500. This is source doctrine, not a universal commercial requirement.
  4. Refunds: Section4 gives the window and non-trigger list. Vague case-by-case language fails the source's requirement for explicit terms; that does not erase existing commitments or legitimate remedies.
  5. Segmentation: Section5 uses measurable eligibility, such as three prior deliveries and renewal within30days. Being a long-time customer is not itself the specific structural condition.
  6. Matrix: Section6 populates pricing rules in all four quadrants. Blank or TBD entries do not satisfy it. This requires the customer/scope decision matrix in the related framework, which differs from the value/access positioning matrix in the written lesson.
  7. Scope premiums: Section7 defines magnitudes, exemplified by10% for additions up to four hours. Major-change requoting can still be part of a defined schedule. Resolve overlaps and calculation bases before calling pricing automatic.
  8. Sustainability path: Section8 gives quarterly movement from measured current margin toward the source's60% target or a documented exception. A target without milestones is insufficient. Sixty percent is a benchmark, not universal break-even.
  9. Coherence: Section9 computes three answers: whether base price reaches the margin target, whether the segment mix yields average effective price at least92% of base, and whether scope premiums cover measured scope-creep load. The92% check measures price dilution; it is not itself a profit margin.
  10. Sign-off: Section10 requests a12-month commitment except schedule-triggered changes and rejects vague weakening language. Preserve that requirement as source content; do not fabricate a signature or imply it prevents necessary documented corrections.

These ten sections differ from the eight-section written lesson. Preserve both sets of requirements and map their content explicitly rather than judging the eight-section artifact against unexplained section numbers. The reviewer does not expressly repeat the lesson's16-pattern scan, so it cannot be assumed to replace every lesson requirement.

Interpret the conflicting scores honestly

The opening says passing requires an average of at least7 and no individual score below5. The later decision block and structured thresholds instead say CLEARED requires average at least8 and every score at least6. Keep this discrepancy visible; do not claim an unqualified7 is cleared.

NEEDS_REVISION is defined as average6–7.9 or any criterion4–5.9, with criterion8 below6 also triggering revision. NOT_CLEARED is average below6 or any criterion below4. These OR rules can overlap: an average7 with a criterion3 matches revision by average and not-cleared by individual score. Decimal values between7.9 and8, or5.9 and6, also require an explicit rounding policy. No precedence or rounding rule is supplied.

Criterion8 is called weighted, but no numerical weight is defined. The supplied implementation is a threshold condition, not a complete weighted-average formula. Failure there requires at least revision; it does not automatically override a more severe failure elsewhere.

Produce an evidence-based review and handoff

The source requests six output parts: score table, decision, criterion notes tied to sections, upstream inconsistency flags, tier-design handoff readiness and a final paragraph. Name the missing evidence or calculation and the correction needed; generic encouragement cannot replace the assessment.

NOT_CLEARED or persistent coherence failure routes to a normal-priority instructor queue with an expected14-day resolution window. After clearance, the source specifies48hours before tier design. These are intended workflow rules, not completed routing or a guaranteed response time. The source expressly allows deviations from reference rules with documented rationale, including a different margin target.

For the exercise, build a ten-row evidence table against an unsigned sample architecture and record the unresolved threshold and section-map decisions. Describe whether the evidence supports each criterion without pretending this explanatory lesson has run the reviewer or granted clearance.

D0621 — complete original source

D0470-linked-D0621 — complete original source

Open source file · Download exact original file

name: pricing-architecture-reviewer
version: 1.0.0
module: M8.4
course: C8 Pricing Discipline
model: claude-sonnet-4-6
role: Pricing Architecture Reviewer
review_type: artifact_review
description: >
  Reviews the M8.4 Pricing Architecture Document. Verifies that base price,
  payment terms, refund window/triggers, segmentation rules, four-quadrant
  matrix, and scope premium schedule are specified rules-based (not
  discretionary), grounded in M8.2 unit economics and M8.3 decision branch,
  and architected toward the C8 doctrine 60% sustainability margin.

system_prompt: |
  You are the Pricing Architecture Reviewer for the RISER Nation Maritime
  Academy C8 Pricing Discipline course, Module 8.4. You review Pricing
  Architecture Documents.

  This module turns the M8.3 decision into a structural pricing system. The
  architecture is what M8.5-M8.7 build against and what M8.6 anti-discount
  policy enforces. Architectural ambiguity propagates into every downstream
  artifact.

  ## What to evaluate

  Read the submitted Pricing Architecture Document plus the linked M8.2
  Unit Economics Document and M8.3 Decision Memo. The Architecture must
  be coherent with both upstream artifacts.

  Score against ten criteria. Pass threshold: average ≥ 7.0 AND no
  individual criterion below 5.0.

  **Criterion 1 — Architecture inputs documented**
  Section 1 must reference C7 Offer Architecture, M8.2 Unit Economics, and
  M8.3 Decision Memo with links. Architecture cannot be built in isolation
  from upstream artifacts.

  **Criterion 2 — Base price specified with cost-anchored rationale**
  Section 2 base price must reference M8.2 unit economics in its rationale.
  Rationale that anchors only to "competitive pricing" or "what feels right"
  fails this criterion. Acceptable rationale ties price to measured cost
  and target margin.

  **Criterion 3 — Payment terms specify deposit ≥ 25% for offers > $500**
  Section 3 must specify deposit percentage. Below-25% deposits on offers
  > $500 are flagged as customer-risk-on-operator failures. Documents may
  specify lower deposits with explicit rationale (e.g., compliance with
  customer procurement requirements).

  **Criterion 4 — Refund window with non-trigger list**
  Section 4 must specify refund window AND non-trigger list. Refund policies
  without non-triggers ("we'll evaluate refund requests case by case") fail
  this criterion because they enable pressure-based refunds.

  **Criterion 5 — Segmentation rules are rules-based, not discretionary**
  Section 5 must specify customer segments with structural criteria (e.g.,
  "≥ 3 prior deliveries renewing within 30 days"). Discretionary segmentation
  ("long-time customers may receive loyalty pricing") fails this criterion.

  **Criterion 6 — Four-quadrant matrix populated**
  Section 6 must show the four-quadrant matrix with pricing rules per
  quadrant. Empty quadrants or vague quadrant entries ("TBD" or "case-by-case")
  fail this criterion.

  **Criterion 7 — Scope premium schedule specified**
  Section 7 must specify scope premium magnitudes (e.g., "+10% for ≤ 4
  hour additions"). Generic language ("custom scope priced separately")
  without magnitudes fails this criterion. The schedule's function is
  to make scope-creep pricing automatic.

  **Criterion 8 — Sustainability margin path specified**
  Section 8 must show quarterly margin trajectory from current (M8.2
  measured) to target (60% knowledge-work doctrine, or documented exception).
  Targets without a path ("we'll get to 60% eventually") fail this
  criterion.

  **Criterion 9 — Architecture coherence check addressed**
  Section 9 must answer the three coherence questions:
  - Does base price produce target margin against M8.2 unit economics?
  - Do segmentation rules produce average effective price ≥ base × 0.92?
  - Does scope premium schedule cover measured C7 scope-creep load?

  Hand-waving on these questions ("yes" without computation) fails this
  criterion.

  **Criterion 10 — Operator sign-off binding for 12 months**
  Section 10 must include operator's sign-off committing to the architecture
  for 12 months absent M8.7 schedule-triggered changes. Sign-offs with
  weakening language ("subject to circumstances") fail this criterion.

  ## How to write the review

  Same structure as prior reviewers:
  1. Score summary table
  2. Decision (CLEARED / NEEDS_REVISION / NOT_CLEARED)
  3. Per-criterion notes with specific section references
  4. Coherence-with-upstream flags (M8.2, M8.3 inconsistencies)
  5. M8.5 hand-off readiness assessment
  6. Final paragraph

  ## Decision thresholds

  - CLEARED: average ≥ 8.0, no criterion below 6.0
  - NEEDS_REVISION: average 6.0-7.9, OR any criterion 4.0-5.9
  - NOT_CLEARED: average < 6.0 OR any criterion < 4.0

  Sustainability margin path criterion (8) is weighted: failure on
  Criterion 8 alone routes to NEEDS_REVISION minimum, even if other
  criteria score well.

  ## Tone and discipline

  M8.4 is the most technical C8 module. Operators may produce well-formed
  documents that nonetheless fail coherence checks. Be specific in
  feedback: name the section, name the issue, name the correction.

  Architecture is rules-based, but the rules don't have to be the same as
  the C7 reference rules. Operators can deviate (e.g., specifying lower
  doctrine threshold than 60%) with documented rationale.

review_criteria:
  - architecture_inputs_documented
  - base_price_specified_with_cost_anchored_rationale
  - payment_terms_specify_deposit_threshold
  - refund_window_with_non_trigger_list
  - segmentation_rules_rules_based
  - four_quadrant_matrix_populated
  - scope_premium_schedule_specified
  - sustainability_margin_path_specified
  - architecture_coherence_check_addressed
  - operator_signoff_binding_12_months

decision_thresholds:
  CLEARED:
    average_min: 8.0
    no_criterion_below: 6.0
  NEEDS_REVISION:
    average_range: [6.0, 7.9]
    or_any_criterion_range: [4.0, 5.9]
    or_criterion_8_below: 6.0
  NOT_CLEARED:
    average_below: 6.0
    or_any_criterion_below: 4.0

instructor_handoff:
  triggered_when: NOT_CLEARED OR coherence_check_failure_persistent
  routing: C8 instructor queue, priority normal
  expected_resolution_window: 14 days from handoff

cooling_period_after_clearance:
  hours: 48
  rationale: >
    Architecture commits the operator to a 12-month system. The 48-hour
    cooling period before M8.5 ensures the operator has confirmed the
    architecture before building tier or scope-premium structures against it.

Price by customer relationship and requested scope

Source: Four-Quadrant Pricing Matrix Framework.

Define this matrix before using its labels

This framework classifies a customer as new or existing and the requested work as standard or custom. It is different from M8.4's value/access positioning matrix. Both call their cells Q1–Q4, but the labels do not mean the same thing. Use the full matrix name in teaching and in the architecture.

ScopeNew customerExisting customer
StandardQ1: base priceQ2: base price or qualifying structural loyalty price
CustomQ3: base plus scope premiumQ4: qualifying base adjustment plus scope premium

The source says every situation belongs to one cell. That requires operational definitions of existing customer and standard scope; mixed engagements may need their components identified separately. Its intended benefit is less improvised bargaining. Claims that users of the matrix hold prices better are coaching assertions without comparative evidence here.

Q1: new customer, standard scope

Use the architecture's base price. This source allows no deviations and rejects first-customer, trial or starting-rate pressure. That must be reconciled with any separate documented cohort, scholarship or beta exceptions; do not silently erase previously approved terms. A customer asking for the standard offer should receive the standard offer without manufactured custom work.

Q2: existing customer, standard scope

Use base price unless the customer meets the policy's stated loyalty conditions: at leastN prior deliveries and renewal withinY days. The example later uses three deliveries and30days. A relationship of many years does not substitute for those actual conditions. Apply the exception when qualified and explain the base price when not. Structural loyalty is distinct from an improvised personal concession.

Q3: new customer, custom scope

Start with base price and add the documented scope premium. Additional deliverables, a changed timeline or special requirements can make the request custom. The source illustrates10% for additions up to four hours and a new quote for major changes. A customer can accept or decline; the example does not authorize doing extra work without agreement.

If the schedule needs revision, the source routes that to architecture review rather than changing it during bargaining. Related templates overlap exactly four hours between bands; resolve that before quoting. The framework's role is to reference a defined schedule, not prove every percentage covers actual delivery cost.

Q4: existing customer, custom scope

Apply qualifying loyalty to the base component and the scope premium to the addition. The loyalty reduction does not also discount the premium. Both rules operate together; there is no extra discretionary reduction for being both familiar and requesting a small addition.

This resolves a stacking question left open in the earlier architecture template. Preserve the calculation basis: this framework's worked premium is a percentage of the original base, not the loyalty-reduced base. If a later base-price increase occurs, clarify which updated base governs the new work.

Avoid all four classification errors

ErrorA treats Q4 as an open-ended negotiation zone instead of applying both rules. ErrorB moves standard new-customer work fromQ1 toQ3 to extract an unjustified premium. ErrorC absorbs genuine custom work fromQ3 intoQ1 to avoid discussing price. ErrorD makes every existing customer discounted rather than checking loyalty eligibility. Classify the actual request honestly; do not alter scope labels to force a preferred price.

Work all four Maya examples with consistent rounding

The source uses a$5,625 base, which differs from the$6,750 example in the written lesson. Treat these as separate example versions, not one current approved price.

Q1 is$5,625. Q2 qualifies after three prior Sprints and renewal within30days; a10% reduction gives$5,062.50, shown rounded in the source as$5,063. Q3 adds a three-hour brand-identity element:10% of$5,625 is$562.50, giving$6,187.50. The source shows$562 and$6,187, which uses a different rounding treatment.

Q4 qualifies after four prior Sprints and renewal within30days, with the same three-hour addition. Exact arithmetic is$5,625 −$562.50 +$562.50 =$5,625. The source shows$5,063 plus$562, also totaling$5,625, but uses inconsistent component rounding. State one currency-rounding policy. Equal10% loyalty and premium offset only in this example; that is not a general promise that all existing-customer custom work costs the original base.

Integrate with the related artifacts

M8.4 uses the customer/scope matrix to state pricing rules. M8.6 uses it to distinguish structural loyalty from pressure-based concessions. M8.7 changes the base and therefore percentage-based premiums, subject to current-engagement protections. M8.8 asks whether loyalty and annual indexing remain coherent. These are intended handoffs, not proof of completed records.

Our Brunson and Hormozi application is clear offer scope and consistent value delivery: an optional upgrade should represent real additional work or benefit, while a loyalty rule should have defined economics. Neither educator is identified as this framework's author.

For the exercise, classify four requests, show eligibility evidence and calculate each amount using a single base and rounding policy. Keep the value/access positioning diagram separate. A completed matrix helps implement policy, but does not by itself demonstrate customer consent, sustainable costs or an operational pricing system.

D0859 — complete original source

D0470-linked-D0859 — complete original source

Open source file · Download exact original file

# The Four-Quadrant Pricing Matrix

**Used in:** M8.4 Section 6, M8.6 policy enforcement, M8.7 raise communication

---

## The Matrix

| | New customer | Existing customer |
|---|---|---|
| **Standard scope** | Q1: New + Standard | Q2: Existing + Standard |
| **Custom scope** | Q3: New + Custom | Q4: Existing + Custom |

Every pricing situation falls into exactly one of these four quadrants. The matrix's function is to make pricing decisions automatic by quadrant rather than negotiated case-by-case.

---

## Quadrant 1 — New Customer, Standard Scope

**Description:** A new customer engaging for the standard offer at standard scope.

**Pricing rule:** Base price as specified in Pricing Architecture Document Section 2.

**Allowed deviations:** None. This is the cleanest quadrant; pricing is deterministic.

**Common pressure:** "First-customer pricing," "trial pricing," "we'll commit if you give us a starting rate." Per M8.6 non-exception list, all declined.

**Why this quadrant matters:** It's the quadrant most operators get right. The other three quadrants are where pricing leaks.

---

## Quadrant 2 — Existing Customer, Standard Scope

**Description:** An existing customer engaging for additional standard work at standard scope.

**Pricing rule:** Base price as specified, OR loyalty pricing per Anti-Discount Policy Section 2 (Exception List). Loyalty pricing applies only when the customer meets the structural conditions: ≥ N prior deliveries renewing within Y days. Outside those conditions, base price applies.

**Allowed deviations:** Only the structural loyalty exception. Discretionary "long-time customer" discounts are not allowed; the loyalty exception is rule-based.

**Common pressure:** "We've been a customer for X years, surely you can do something on the price." Per M8.6, the answer depends on whether the customer meets the structural condition. If yes, loyalty exception. If no, base price.

**Why this quadrant matters:** It's where existing-relationship pressure causes most operator concession. The structural rule converts emotion to arithmetic.

---

## Quadrant 3 — New Customer, Custom Scope

**Description:** A new customer requesting work that varies from standard scope (additional deliverables, different timeline, custom requirements).

**Pricing rule:** Base price + scope premium per Pricing Architecture Document Section 7. The scope premium schedule is rules-based: small additions trigger small premiums; major scope changes trigger re-quote.

**Allowed deviations:** Only those embedded in the scope premium schedule itself. Operators do not negotiate the schedule on the fly; if the schedule needs revision, that happens in M8.4 architecture review, not in live customer conversation.

**Common pressure:** "Can you bundle these into the standard price?" or "We need this small extra thing — surely you can include it." The scope premium schedule answers automatically: small extra (≤ 4 hrs) = +10%. Customer can accept or decline; operator does not negotiate the +10%.

**Why this quadrant matters:** It's where scope creep enters pricing. Without a schedule, every custom request becomes a negotiation. With a schedule, requests become arithmetic.

---

## Quadrant 4 — Existing Customer, Custom Scope

**Description:** An existing customer requesting custom work.

**Pricing rule:** Base price + scope premium per schedule. Loyalty exception (if applicable) applies to the base price component, not the scope premium component.

**Allowed deviations:** Combined application of Q2 and Q3 rules. No additional discretion.

**Common pressure:** Combined Q2 and Q3 pressures. "We're a long-time customer AND this is just a small addition; can you give us a break?" The matrix answers: loyalty exception applies to base if conditions met; scope premium applies to addition; both rules operate in parallel.

**Why this quadrant matters:** It's the most complex quadrant in negotiation feel but the simplest in matrix logic.

---

## What the Matrix Prevents

Without the matrix, operators face every pricing situation as a unique negotiation. With the matrix, situations are pre-classified and pre-priced. The cognitive load shifts from "what should I charge here" to "which quadrant is this and what does the rule say."

This shift is the point. Operators under live pricing pressure who must compute pricing on the fly tend to compute toward concession (because concession ends the conversation). Operators who reference a pre-built matrix tend to hold the line (because the rule is already decided and the conversation is about whether the customer fits the rule, not about what the rule should be).

---

## Common Quadrant Errors

### Error A: Treating Q4 as a discretionary zone

Operators sometimes treat existing-customer-custom-scope as a "we'll work it out" zone. The matrix forbids this. Q4 is rules + rules; both Q2 loyalty rule and Q3 scope rule apply.

### Error B: Slipping Q1 into Q3

Operators sometimes try to upsell new customers from standard scope to custom scope to capture scope premium revenue. This is sales pressure, not pricing discipline. If the customer wanted standard scope, Q1 applies. Don't manufacture custom scope to extract scope premium.

### Error C: Slipping Q3 into Q1

The reverse: operators sometimes absorb custom scope into standard scope to avoid the scope-premium conversation. This is reflexive concession. If the customer requested custom scope, Q3 applies; the scope premium is the price of custom delivery.

### Error D: Treating Q2 as default-discount zone

"Existing customers always get a discount." This converts loyalty from a structural exception to a default, which means the standard price is now whatever-existing-customers-pay. The matrix forbids this; loyalty applies only when structural conditions are met.

---

## Worked Example: Maya in Each Quadrant

**Q1 — New customer, standard Sprint:** Price $5,625. No deviation.

**Q2 — Existing customer (3 prior Sprints, renewing within 30 days), standard Sprint:** Loyalty pricing applies per M8.6 Section 2: 10% off, $5,063.

**Q3 — New customer, Sprint + additional brand identity element (estimated 3 hours):** Base $5,625 + 10% scope premium ($562) = $6,187.

**Q4 — Existing customer (4 prior Sprints, renewing within 30 days), Sprint + additional brand identity element (3 hours):** Base $5,625, loyalty discount on base ($562 off, base becomes $5,063), scope premium on addition (10% of original base = $562). Final: $5,063 + $562 = $5,625.

Note that Q4 results in the original base price by net effect (loyalty exception offsets scope premium in this specific magnitude). The matrix doesn't mind. The math is rule-driven; the result is whatever it is.

---

## Integration with Other C8 Artifacts

| Artifact | How it uses the matrix |
|---|---|
| M8.4 Pricing Architecture | Section 6 specifies the matrix |
| M8.6 Anti-Discount Policy | Exception list (Q2 loyalty) is structural; non-exception list (Q1, Q3 with no scope change) is held |
| M8.7 Price-Raise Schedule | Raises apply to base; scope premium is % of base, so raises propagate automatically |
| M8.8 Attestation | Section 8 coherence question: does loyalty (Q2) accommodate annual indexing (M8.7 T4)? |

---

*The matrix is the structural enforcement device. Anti-discount policy without the matrix is a list of rules without an implementation; the matrix is the implementation. Operators who reference the matrix in live conversations tend to hold pricing; operators who do not reference it tend to negotiate.*

D0470 supporting resources and reference status

Links below identify source files. A located file is not automatically a reviewed or completed prerequisite.

  • D0495 — Anti-Discount-Language-Swipe-File.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0812 — Case-Race-to-the-Bottom-Trap-Failure.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D1400 — Race-to-the-Bottom-Recognition-Checklist.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D1747 — Pricing-Pressure-Conversation-Scripts.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D2482 — anti-discount-policy-reviewer-v1.0.0.yaml

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0539 — Anti-Discount-Policy-Template.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0622 — Pricing-Math-Spreadsheet-Template.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0590 — Hidden-Hours-Audit-Worksheet.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0899 — Pricing-Is-Operator-Self-Respect-Framework.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0619 — Price-Raise-Schedule-Template.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0620 — Pricing-Architecture-Document-Template.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0510 — Raise-Communication-Swipe-File.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D1370 — Pricing-Math-Spreadsheet-to-Supabase-Walkthrough.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0607 — M8.4-Written-Lesson.md

    Native source text compared with reviewed D0608; native structure and full appendix preserved; shared teaching drafted locally; visual review and integration pending. Same prose after formatting normalization; shared teaching is D0470-linked-D0608-teaching-draft.md. Both source identities and appendices remain separate.

  • D0608 — M8.4-Written-Lesson.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D1393 — M8.7-Written-Lesson.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0621 — pricing-architecture-reviewer-v1.0.0.yaml

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

  • D0859 — Four-Quadrant-Pricing-Matrix-Framework.md

    Source read, original bytes preserved and supporting teaching drafted locally; final integration pending. Reviewed supporting source; separate future assigned placements remain uncompleted.

Unresolved references

  • Exact Trigger-Tightness Verification Worksheet and price-raise-schedule-reviewer names were not matched in the local inventory search; absence from search does not prove the files do not exist.
  • Exact Pricing-Pressure Scripts Template title was not found. D1747 is a related conversation library, not a proven identical template.
  • Exact 07_Case-Studies-and-Examples/Race-to-the-Bottom-Trap.md title/path was not matched. D0812 is the reviewed related composite case; preserve the filename discrepancy.
  • Build 6, Build 8 folder, live Supabase table, completed operator documents and signed attestation are not established by inventory links.
  • Legacy module labels alone cannot resolve conflicting course/section mappings.

Turn competitor and keyword research into a relevant customer journey

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Assigned lessons: 03.1, 03.3, 04.1, 07.1 and 12.4. Source: Mindy.houses research workbook.

Lesson purpose and outline

A large keyword list becomes useful when you understand what each person is trying to accomplish. This workbook combines competitor discovery, search-result observations, professional and social research, question discovery and historical keyword metrics. Our task is to convert those observations into a defensible audience and content plan while preserving what the original research actually says.

By the end, you should be able to distinguish observations from conclusions, classify seller and buyer intent, interpret the numeric columns, compare a whole website with a specific landing page, recognize missing evidence and outline a relevant next step for a prospect. We will work through the research trails, question inventory, individual keyword tables and comparison sheet, then build an example page brief.

The source is a historical research workbook. AnswerThePublic is marked May 27, 2021, and the franchise keyword table specifies May 1, 2020 through April 30, 2021. Other rows mention 2019 and 2020. These dates do not date every cell precisely, but they prevent us from presenting the workbook as current market intelligence. A keyword about a company's service does not establish that the service is available today.

1. Build an evidence trail before drawing conclusions

Start with the Home tab. Its side-by-side trails connect professional and social profiles, websites, videos, liked pages, offers, communities and tools. The topics include mortgage and property investing, fire-damaged property, marketing, skip tracing, voicemail and email tools, webinars, case studies, motivated-seller scripts, data tools, entrepreneurship, conferences, fixing and flipping, return calls, podcasts, wholesale hotlines, driving for dollars and disposition. Some destinations address investors looking for properties; others address people seeking help finding homes.

These are different research objects. A profile is evidence that the researcher recorded a profile. A linked webinar is a resource to inspect. A note about an offer is not a validated offer claim. A liked page does not establish a person's wealth, purchase intent or suitability as a customer. Preserve the original relationships, names and annotations in their source context without turning them into public endorsements or prospect characteristics.

Several entries are blank or marked old. Standalone numbers such as 500 and 1 have no established conversion definition. Leave them unexplained unless another source supplies one. Do not turn two nearby numbers into a conversion rate. Video and channel links are also not transcripts: their content still needs review before it can be taught. Unusable media belongs in the Unused reconciliation with its reference and reason preserved.

The workbook's eighth tab (tab index 7 in the source inventory) is empty. Its place is preserved in the appendix; there is no missing lesson topic to infer from that blank tab.

For your own research, record the observation, its source location, the date checked, your interpretation and what would verify it. Keep those fields separate. This simple discipline prevents an appealing annotation from becoming a false fact later in a sales page.

2. Read search-result collections as observations

Search Results1 collects phrases about selling quickly, selling fast, companies that buy homes and Arizona variants. It contains repeated search passes, root-domain and tracked landing-page pairs, and local labels. A repeated domain gives you a reason to investigate that competitor. It does not reveal that competitor's advertising budget, conversions, total traffic or ranking history. The workbook does not consistently supply a dated search position or ad designation for every row.

Keep the root URL and the landing-page URL together. The root tells you which organization or site is involved; the landing page may reveal the specific audience or offer being studied. A property site can serve buyers, sellers, investors and agents through different pages. For example, the collection labels one destination as buying rentals from investors. That belongs to a different journey from an owner seeking a fast sale.

SearchResultsList.1 divides entries using local and toll-free headings and includes unexplained 7, 5 and 2 tallies. Those counts have no confirmed method in the sheet. A local phone annotation alone does not verify a business's service area. Repeated URLs across columns should remain in the original record; decide whether they are duplicate observations only after checking what each column represents.

SearchResults.2 adds questions about selling without a realtor, selling online, selling free, reviews, Arizona and nearby providers. It also contains buyer-side, seller-lead and questionnaire notes. Identify which party is being served before comparing offers. A service that sells leads to an investor is not necessarily a service that buys the homeowner's property.

3. Separate historical judgments from usable comparison criteria

Sheet14 records nearby results and annotations such as an ad running, a good website, Messenger chat, national coverage, mobile-home buying, a top producer rather than wholesaler, and investor or property-manager categories. It also includes subjective website opinions, personal associations, a review count of 58 and an offer-related note about 72 sold and staying up to six months. These are historical observations requiring context and rechecking; they are not current endorsements, verified results or RISER terms.

Convert a judgment into a question you can investigate. Instead of copying “good website” into your conclusion, ask: is the intended audience clear, does the page explain its process, does its action match the visitor's need, and can its claims be supported? Instead of treating “national” as proof of local service, check the actual eligibility and geography. The source's Messenger link records a historical implementation reference; it does not establish that a present integration works.

SearchResultsList.2 contains only three websites under local and not-local headings. That small directory does not establish complete market coverage or explain its classification method. Missing entries remain missing. Do not fill the gaps with invented competitors or extrapolate market share from the list.

4. Turn questions into a curriculum of customer needs

The AnswerThePublic tab uses “sell my house” as a seed and links its historical question report. Read its questions as evidence of possible language and concerns. They are not ready-made answers.

Group the distinct concerns before choosing content. Decision questions include renting versus selling, whether a sale is possible, market value, profit, retirement, when to sell and selling again after one or two years. Process questions include documents, payment receipt, mortgages, equity, fees, commissions, taxes and paperwork. Channel questions include online, private, free, agent, portal, auction, raffle and lottery routes. Transaction preferences include speed, cash, as-is condition, instant quotes, seven- or 28-day timing, rent-back, staying in the home, moving abroad and buying another property.

The workbook also asks about selling to a son, spouse, company, council, developer or builder; occupied properties, tenants and spousal consent; benefits eligibility; and Bitcoin. These questions are distinct and should not disappear inside a generic “sell fast” heading. However, the question list provides no legal, tax, benefits or financing answer. Mark these as topics needing suitable current evidence and jurisdiction-specific review before writing substantive guidance.

Brand and portal questions mention Zillow, Zoopla, Realtor, Rightmove, Gumtree, Redfin, Strike and Purplebricks. Geography spans the US, UK, Ireland, Scotland, Canada, Australia, New Zealand and other places, including Phoenix and Scottsdale. A Phoenix-focused page cannot treat all these audiences and systems as interchangeable. “Free,” “cash” and “instant” are words people searched for, not promises your business has earned the right to make.

5. Preserve and interpret the autocomplete image

The workbook includes a Google autocomplete screenshot anchored at C66 in AnswerThePublic. The displayed query is “where to sell my house online.” Its five suggestions concern selling a house or property online, including two variants asking about doing so for free. The original image belongs beside the source material, with text that explains what it shows.

This screenshot helps you hear the customer's wording. It supplies no search-volume number, conversion rate or ranking guarantee. It does not prove that a particular service is free. Use it to propose a question your page can answer accurately, then determine what evidence the answer requires. The image and the question list complement each other; neither substitutes for reviewing the actual resources.

Some queries concern GTA V property, television or drama, GIFs, gift cards, diffuser blends, statues or mantras, house contents, jobs and haunted houses. Retain these in the original research, then label them unrelated or ambiguous for a real-property seller campaign. A word match is not an intent match. This is also why you should inspect ambiguous queries before making blanket exclusions.

6. Read the seven numeric fields correctly

The keyword tables use keyword, currency, average monthly searches, competition category, indexed competition, and low and high top-of-page bid figures. USD specifies the currency of monetary metrics. It does not mean the search count or competition index is a dollar amount.

The recurring 50, 500, 5,000 and 50,000 figures are coarse historical figures. Do not present them as precise numbers of unique qualified prospects. “Low” competition is not a statement that an organic page will be easy to rank. A numeric zero competition index differs from an empty field or Unknown category. A blank bid is unknown, not a free click.

For example, Sheet11 lists “we buy houses” at 50,000, High, index 69 and bid figures 15.19–55.92. It lists “buy my home for cash” at 500, High, 77 and 28.54–116.13; “quick house sale for cash” at 50, Low, 19 and 45–163.24. Those are historical keyword metrics, not a current campaign quotation. They also do not tell you which phrase produces a profitable signed transaction.

Retain every number in its original row and column. A formatted appendix must preserve blank cells so the high bid does not move into the low-bid column. Repeated terms across seed reports must not be summed automatically into a total audience. The source supplies no reliable deduplicated reach or conversion model.

7. Compare a landing-page seed with a whole-domain seed

Sheet11 places two independent seven-column reports side by side: one associated with a landing page and one with a root domain. The left list ends at row 273; the right continues through row 445. Their row positions do not establish equivalent keywords or paired performance.

A root-domain report can include buyer homes, new homes, rentals, agent services, investment, wholesale, logos and websites alongside seller terms. The landing-page report may have a narrower emphasis, but still needs classification. Keep Phoenix, Mesa, Glendale, Arizona, Utah and national searches distinct. Navigational brand searches and business-operator searches are separate from an owner seeking an offer.

The learning task is to explain why a seed produced a mixed list and select a relevant subset with reasons. Do not choose the biggest volume automatically. Do not infer missing words in truncated phrases such as “we buy houses in.” Preserve the phrase and mark its intent unresolved.

8. Interpret the IntegrityHomes table

IntegrityHomes explicitly indicates an only-this-page seed. Its 146 keyword rows cover fast cash sales, as-is condition, process, costs and buyer/investor variants. An unexplained 149 counter also appears; do not describe that number as a verified keyword-row count.

Use this table to practice comparing a specific offer page with its associated query suggestions. Identify which terms describe the seller's objective, which ask for education, and which could be an investor seeking properties. Keep missing bids and Unknown categories visible. A keyword's association with the seed is a research lead; it does not establish that the business paid for that term or won customers through it.

9. Classify the full OpenDoor table

OpenDoor contains a root-site group and a consumer seller-lead group. The left list ends at row 488; the right continues through row 2,156. Preserve their separate headers and positions. Their material covers more than fast house sales.

First separate homeowners seeking cash, speed, an as-is sale, a condo buyer or a by-owner route from people seeking inventory, rentals, new homes or investment purchases. Next separate education about preparation, repairs, pricing, proceeds, commissions, closing, agents, timing, mistakes and showings. Coordinated buying and selling creates another group: buying before selling, selling before buying, making an offer while selling, financing failure, escrow failure and transaction timing.

Trust and comparison queries include reviews, hidden fees, inspections, guarantees, cash-sale pros and cons, alternatives and competitor comparisons. A query about hidden fees is not evidence that fees were hidden. Brand-navigation queries cover customer service, phones, blogs, property trusts, agents, partners, cancellation, calculators, self-tours, tour assistants, founders and named programs. Questions about Zillow purchase programs, Offerpad, Lennar or OS National are historical research; verify current facts before teaching product availability or relationships.

The table also includes iBuyer stocks and startup/business queries, which are not seller leads; emotional questions about stress, sadness, regret and selling a family home; and generic or ambiguous queries about opening doors, signs and letters. Emotional language is an invitation to understand a customer's concern respectfully, not a diagnosis or evidence for pressure tactics.

Apply the geography check within this table too: Phoenix and other US markets appear alongside UK Help to Buy and Canadian or Ontario queries. They do not share one transaction system or service area. A query about a selling-cost calculator supplies neither the calculator nor its cost formula, and a family-letter query supplies neither a letter template nor authority for using one in a transaction.

A large portion of later rows consists of individual street addresses, floor plans, owner searches, virtual tours and neighborhoods. These are property-specific or navigational interests. They do not prove that an owner wants to sell, reveal the present owner, establish wealth or authorize contact. Preserve the complete data as research without converting it into an asserted motivated-seller list.

Consider the contrast between “cash offer for my home” at 500, High, 88, 39.02–126.65 and “estate for sale near me” at 500,000, Low, 12, 0.10–3.15. The second phrase has a much larger historical volume but is broader and may serve a different audience. Low bid and high volume alone do not make it the better seller-acquisition choice.

Other rows illustrate limits: “7 showings no offers” supplies a question, not a company's measured performance; “buyer agent fee” at 5,000 and 2.10–10.52 supplies keyword metrics, not a commission schedule; “housing market graph” supplies a query, not a graph. Address these distinctions explicitly when you use the examples.

10. Separate franchise education from homeowner intent

Homevestorsfranchise contains 223 keywords and explicitly dates its metrics to May 2020–April 2021. It includes investing, franchising, training, coaching, tools, lead generation, finance, careers, distressed properties, flipping, rental ownership and market-specific opportunities such as Chicago and New Jersey. A smaller group concerns selling to investors.

“Investing in real estate” appears at 50,000, Medium, 61 and 3.70–9.99. “Real estate investing courses” appears at 5,000, High, 83 and 4.57–11.37. These are different educational and business intents, not proof of franchise sales or course demand for RISER. An attractive phrase about the best investment or investing right now is not an investment recommendation.

Homevestor.Phoenix contains 219 keywords with more seller speed, cash and as-is intent, plus brand, phone and logo searches and some buyer or moving needs. “Ugly houses” at 50,000, Low, 13 and 6.71–45 is broader and more ambiguous than “sell your ugly house” at 50, Low, 18 and 29.81–158.13. Brand wording does not establish an affiliation or become your brand identity merely because it appears in a research sheet.

Compare.Homevestor puts the two keyword lists side by side without numeric metrics. It has 223 entries in one column and 219 in the other; the final four blanks are not failed matches. Compare audience emphasis across the lists. If you need actual keyword overlap, perform a separate comparison that preserves each original entry rather than treating row alignment as a match.

11. Recognize investor-acquisition and entertainment ambiguity

The final tab's native title is the Mikey website URL. Its 168 keyword rows emphasize fixer-uppers, handyman specials, cheap houses, foreclosures, distressed properties, investment deals and Phoenix/Arizona property acquisition. A minority relates to sellers approaching investors. Preserve the native title even though the spreadsheet export sanitizes its punctuation.

“Fixer upper houses” appears at 5,000, Low, 32 and 0.45–1.94; “cheap houses” at 50,000, High, 97 and 0.55–1.87; “sell property to investors” at 50, High, 98 and 16.70–50.00. Explain the different roles behind those phrases before making a marketing decision. Bid differences do not establish investment returns.

Some phrases refer to the television program Fixer Upper. “Sells AZ” can refer to a location rather than the action of selling. Other phrases remain ambiguous. Record your interpretation and its confidence; the original query stays available for a reviewer to challenge your decision.

12. Apply the Brunson and Hormozi themes to the evidence

The following is an authored application of the requested educational themes, not a claim that the source workbook presents these frameworks. Use the customer's actual question to maintain continuity between the entry message, the explanation and the offer. In a Brunson-oriented hook, story and offer structure, the hook names the relevant problem, the explanation establishes context and credible understanding, and the offer gives an appropriate next step.

For a seller researching as-is options, an honest educational hook could be “What should you compare before choosing an as-is sale?” The body can explain the comparison questions and the information still needed. A suitable draft action could invite the visitor to complete a property-information checklist. Do not attach an unverified purchase deadline, guaranteed price or claim of a cash offer to that action.

In a Hormozi-oriented offer review, ask what outcome the visitor wants, what evidence builds confidence, and what delay or effort your actual process can reduce. The keyword list can suggest concerns about timing, repairs, fees and uncertainty. It cannot demonstrate that your service has solved them. Distinguish a proposed benefit from an evidenced benefit, and define eligibility and process before presenting a promise.

For an investor researching education, use a different page and next step. A question about investing courses should not land on a page written as if the visitor owns a house they need to sell. Likewise, a homeowner should not have to decode franchise language to understand their choices.

13. Build the page brief and verify it

Choose one source query and retain its exact tab and row. State the likely audience, intent, geography, date context and uncertainty. Add the nearby variants that genuinely ask the same question. List excluded or unresolved terms and explain why they belong elsewhere. Keep the original metrics with their labels; do not invent a current forecast.

Then write a page brief containing a clear question, a brief answer supported by suitable evidence, the sections required to explain it, a relevant next step, and the sources a learner can click. For material requiring current legal, financial or product information, record the verification needed before writing an authoritative answer. A source question alone is insufficient.

Check that the page teaches the full chosen topic rather than repeating its headline. Use meaningful headings and descriptive links. Do not create a nearly identical public page for every keyword variation. Nothing in this workbook proves ranking or LLM visibility. Final site search readiness requires separate checks of actual content, metadata, structured data where applicable, accessibility, crawl settings, domain and canonical paths.

Practice and completion check

Prepare three briefs: one for a homeowner seeking sale options, one for an investor seeking education, and one for a property-specific query that you decide not to use as a general acquisition page. Explain the differences in audience, evidence and next step. Include one historical metric example, one Unknown or blank metric, one ambiguous query and one resource whose content still needs verification.

You have completed the exercise when another learner can trace each decision to the original source, distinguish observations from assumptions, explain why high volume does not prove good fit, and identify what evidence is still missing. The result should be an actionable research decision with honest limits, not a list of unsupported marketing claims.

Source materials for this lesson

- Original Mindy.houses workbook and its source links. - Historical AnswerThePublic report recorded in the workbook.

Use the accompanying source appendix to inspect all 15 reconstructed native tabs, download the preserved spreadsheet export and examine the original autocomplete image. It retains all 27,571 valued native cells and 468 linked cells, including rich-text links, with original titles, positions, repeated rows, structural blanks and annotations. This script explains how to use that evidence; the appendix preserves the complete research. A clickable source link does not establish that its destination is currently accessible or that linked media has been reviewed. Keep those remaining checks separate from the workbook's recorded observations.

Assigned source: D0471 original 1

D0471 — complete original source

Complete D0471 source workbook appendix

Historical research, preserved for source comparison. Original annotations are not verified current claims. Cell coordinates and blank positions are retained; source links appear below their original cell text. This reconstruction does not reproduce every visual formatting choice. The native export preserves the workbook format separately.

Download preserved native workbook export

Home

Open original tab

Home
RowABCDEF
1Mindy Montez HowardJake Mercer
2https://www.facebook.com/mindy.howard.5Source link B2https://www.facebook.com/jakemercer101Source link E2
3
4WorkRealtorWorkhttps://www.facebook.com/finally.soldSource link E4
5http://epichomeoffer.com/Source link B5https://www.finallysold.com/?fbclid=IwAR1UJdiOHg7bQyOZlviXbHNhC-2SK3DDTzcsAalQ0PtaDyqgtLaht8vm7IESource link E5
6
7LIKESLIKES
8Brayand 'BP' Poncianohttps://www.facebook.com/brayand.bp.poncianoSource link B8HIGH INCOME EARNER-RE INVESTORBrayand 'BP' Poncianohttps://www.facebook.com/brayand.bp.poncianoSource link E8HIGH INCOME EARNER-RE INVESTOR
9WEBSITEhttps://www.3insidersecrets.com/training46498532?fbclid=IwAR0luLuTO0J4LIHfdcYipeUQwwtHCNsWIb5rOouoqONbo6vADSHyGkuluCsSource link C9WEBSITEhttps://www.3insidersecrets.com/training46498532?fbclid=IwAR0luLuTO0J4LIHfdcYipeUQwwtHCNsWIb5rOouoqONbo6vADSHyGkuluCsSource link F9
10Website from Youtube About Page/SPECIAL OFFER!!!https://www.unfuckyourmindset.com/order-form1613757477003Source link C10Website from Youtube About Page/SPECIAL OFFER!!!https://www.unfuckyourmindset.com/order-form1613757477003Source link F10
11YouTube Channelhttps://www.youtube.com/channel/UCl8kANE1nEExmO5L4tL2C6wSource link C11YouTube Channelhttps://www.youtube.com/channel/UCl8kANE1nEExmO5L4tL2C6wSource link F11
12LinkedInLinkedIn
13Payton LaBadiehttps://www.facebook.com/paytonlabadieMLOSource link B13MORTGAGESWholesaling Houses: GroundZerohttps://www.facebook.com/WholesalinghousesGZSource link E13
14Websitehttps://jmlmortgage.com/?fbclid=IwAR3E4pPGS5BUNphXbY6wganNrGbyXzC5oWuIQt4EwpBD3IVsRKv_U-r_8OESource link C14WEBSITEhttps://www.thisisgroundzero.com/?fbclid=IwAR3xP70gCMrYGJRE4DwaVf5fXTv67kWUouRIq9afKVyq9OhMgaNrNVStmDMSource link F14
15Austin Zabackhttps://www.facebook.com/theAustinZabackSource link B15Real EstateGEO POINT DATA LIVEWebsite from Youtube About Page/SPECIAL OFFER!!!https://www.thedatafleet.com/data-fleet/Source link F15
16Websitehttp://www.zabackgroup.com/Source link C16YouTube Channel
17YouTube Channelhttps://www.youtube.com/channel/UC-cXMn9IIxaA7hos6Eg6jSwSource link C17LinkedIn
18LinkedInhttps://www.linkedin.com/in/AustinZaback/Source link C18Real Estate Investinghttps://www.facebook.com/RealEstateInvestingSource link E18RE INVESTOR TRAINING
19Investors Edge Real Estate Grouphttps://www.facebook.com/investorsedgeazSource link B19Investing ServiceTHE CLEVER INVESTORWEBSITEhttps://cleverinvestor.com/?fbclid=IwAR0CgR7Q4Uxw6VBa8-unxzihpZ0TKGa3tWqnN1iDGV13mE4j-LfZnV2yhIQSource link F19
20OLD GROUPWebsitehttps://investorsedge.co/ourproperties/Source link C20Many Free ToolsWebsite from Youtube About Page/SPECIAL OFFER!!!https://cleverinvestor.com/real-estate-investing-resources/motivated-seller-scripts/?utm_source=facebook&utm_medium=organic&utm_campaign=motivated-seller-scripts_leadmagnet&fbclid=IwAR2kyDhewhfyu9FybbqqYECERK9Mv3ulRm8rhe9ScyTHLmWWhYkRFISu0d4Source link F20
21YouTube ChannelYouTube Channelhttps://www.youtube.com/channel/UCvWdtRovlbUvCu9ZCw8b0aQSource link F21
22LinkedInLinkedIn
23PropStreamhttps://www.facebook.com/PropStreamDataSource link B23RE Data Company, Marketing, SkipTracing, Voicemail, EmailAll IN Entrepreneurshttps://www.facebook.com/AllinnationSource link E23Scale Your RE Business
24Websitehttps://www.propstream.com/?fbclid=IwAR3gicYwZZzjR20IMqmpIX7_WUryvVVVEzv4x5zwo8fUVZwwOKTDC0K3VLYSource link C24WEBSITE
25YouTube ChannelAttend Momentum-keynote speaker https://www.facebook.com/allstarinvestorWebsite from Youtube About Page/SPECIAL OFFER!!!https://attendmomentum.com/?fbclid=IwAR1aOQkiPREwC4DiyO1LAdHBhlUKnVIAD8HUTbUNWNCbNJnPnjH4IWI9vuQSource link F25
26LinkedInhttps://www.linkedin.com/company/propstream/?fbclid=IwAR1xVx8dnIKOulA8r4sFXZP1HHowfRMR7JaShqeue0H7oW2ioX5K4Mn_sRoSource link C26https://www.facebook.com/allstarinvestorSource link D26YouTube Channel
27Quick Results 4 U - Joe Sauterhttps://www.facebook.com/quickresults4uSource link B27LinkedIn
28Fix and Flip Hubhttps://www.facebook.com/fixandfliphubSource link E28
29OLDWEBSITEhttps://cf.fixandfliphub.com/highlyprofitablewebinar?fbclid=IwAR3A1EzjI7mZm479pgYfA781B2OCDzIs3vAZxMRNzCe6fqDElb0o2xP0hkYSource link F29
30AZ4Lesshttps://www.facebook.com/AZ4lessSource link B30Marty BoardmanWebsite from Youtube About Page/SPECIAL OFFER!!!
31Websitehttp://m5site.com/template_1_6986?fbclid=IwAR1xVx8dnIKOulA8r4sFXZP1HHowfRMR7JaShqeue0H7oW2ioX5K4Mn_sRoSource link C31YouTube Channelhttps://www.youtube.com/fixandfliphubSource link F31
32Sam SuttonYouTube ChannelLinkedIn
33Cameron JonesLinkedInJamil Damjihttps://www.facebook.com/DamjiJamilSource link E33Builder/Astro flipper/Wholesaler
34Elijah I. Rubinhttps://www.facebook.com/theelijahrubinSource link B34Fire Damage-RE InvestmentBrentWEBSITE
35WEBSITE-GenWealthTour-Come learn the Blueprint for how to build Generational Wealth for yourself and your future Generationshttps://www.genwealthtour.com/?fbclid=IwAR3gicYwZZzjR20IMqmpIX7_WUryvVVVEzv4x5zwo8fUVZwwOKTDC0K3VLYSource link C35PaceWebsite from Youtube About Page/SPECIAL OFFER!!!https://www.disruptors.com/return-my-calls?r_done=1Source link F35
36YouTube ChannelYouTube Channelhttps://www.youtube.com/jamildamjiSource link F36
37LinkedInLinkedIn
38Offer-How to get home owners to return your callsDisruptorshttps://www.disruptors.com/return-my-calls?r_done=1Source link F38
39To The Moon Podcast
40WholeSale Hotline #Squadup
41Astro Flippinghttps://go.astroflipping.com/1-case-study-11-aSource link F41
42Batchdriveapphttps://batchdriven.com/Source link F42
43batchleadshttps://batchleads.io/Source link F43
44Driving for Dollars
45500/1
46Dispositionhttps://www.keyglee.com/Source link F46
47Phoenix Real Estate Investment Dealshttps://www.facebook.com/wholesalearizonaSource link E47
48WEBSITEhttps://wholesalearizona.com/?fbclid=IwAR2I6HdFihaPAkMJ9mJ5r6X0WJegAespis_B_gccze-x3DhHt1N0k_340doSource link F48
49Website from Youtube About Page/SPECIAL OFFER!!!
50YouTube Channel
51LinkedIn
52Wholesale Phoenix Houseshttps://www.facebook.com/WholesalePhoenixHousesSource link E52Mikey Sells Houses
53WEBSITEhttps://www.mikeysellshouses.com/?fbclid=IwAR1Af34NZckwQ2ZH1jbWBhAvnLSG2sPpQDIwMRcMl2oj4ocV2TUg8duE-rYSource link F53
54Website from Youtube About Page/SPECIAL OFFER!!!
55YouTube Channel
56LinkedIn
57Phoenix Wholesale Real Estate Investorshttps://www.facebook.com/PhoenixWholesaleInvestorsSource link E57
58WEBSITEINVESTORS LOOKING FOR A HOUSEhttp://momentumholdingsgroup.com/phoenix-wholesale-homes?fbclid=IwAR3A1EzjI7mZm479pgYfA781B2OCDzIs3vAZxMRNzCe6fqDElb0o2xP0hkYSource link F58
59WEBSITEHELP US FIND HOMEShttp://momentumholdingsgroup.com/phoenix-house-flippers?fbclid=IwAR3W7nMPnWiWqW0PFxVU76DKgkI4Ci0erPe6LRW0fZk2rnUsRB7vr-koUEYSource link F59
60YouTube Channel
61LinkedIn
62
63WEBSITE
64Website from Youtube About Page/SPECIAL OFFER!!!
65YouTube Channel
66LinkedIn
67
68WEBSITE
69Website from Youtube About Page/SPECIAL OFFER!!!
70YouTube Channel
71LinkedIn
Search Results1

Open original tab

Search Results1
RowABCDEFGHI
1how to sell your house quicklyHow to sell my house fastcompanies that buy homes
2https://www.homevestors.com/Source link A2https://www.closedforcash.com/Source link D2https://www.homevestors.com/phoenixSource link G2
3opendoor.comSource link A3https://networthrealtyusa.com/Source link D3https://webuyhouse.com/Source link G3
4https://my.offerpad.com/Source link A4https://www.redfin.com/Source link D4https://webuy.thetrustedhomebuyer.com/Source link G4
5https://sell.fasthomeoffer.com/Source link D5https://integrityhomesus.com/Source link G5
6how to sell your house quickly in Arizonahow to sell your house quickly in ArizonaHow to sell my house fast ArizonaHow to sell my house fast ArizonaHow to sell my house fast Arizonacompanies that buy homes in arizonacompanies that buy homes in arizonacompanies that buy homes in arizona
7Local #https://freedomhomebuyer.com/Source link B7https://freedomhomebuyer.com/arizona/sell-house-fast/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3-eLQK4EPBrKP-TM40A3kkTdMGK4CkJwmitCHQ8tRSG_0Du29BUKcaAnGnEALw_wcBSource link C7LOCAL #https://www.azfaircashoffer.com/Source link E7https://www.azfaircashoffer.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo01aOwrgdRweyBuTbq2oKXCudX5qoA8tSZM40Lf260mJRbMGI679y8aAsqDEALw_wcBSource link F7https://www.opendoor.com/Source link H7https://www.opendoor.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1H_m2NhxBJt8_go2kqMH0PrpITcHXsHb2kzGz2AcOdeBw0NzNzjqwaAmeXEALw_wcB&utm_campaign=1666141829&utm_content=507630822454&utm_medium=search&utm_source=google&utm_term=%2BbuyhomesSource link I7
8https://www.homeoffersarizona.com/Source link B8https://www.homeoffersarizona.com/?https%3A%2F%2Fhomeoffersamerica_com%2F&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2WVj2gzvEs4Zi4wEYzJ84TzIGZzQmRaiFLMCmmuyakFKEytgZaSp8aAunpEALw_wcBSource link C8LOCAL #https://freedomhomebuyer.com/Source link E8https://freedomhomebuyer.com/arizona/we-buy-houses/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0Q3EasJyREr8653MaXS4R4vJ5ojuyHuFXocZgXG4YUQ6UQpfWyyIwaAlnxEALw_wcBSource link F8https://offergiants.com/Source link H8https://offergiants.com/?utm_term=we%20buy%20houses&utm_content=480100298539Source link I8
9Local #https://webuy.thetrustedhomebuyer.com/Source link B9https://webuy.thetrustedhomebuyer.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2FoWH0hsk0oCpWQREvinKuVle5_Get-MbiSUhr9B8vlR4R8Z0ErowaAmzLEALw_wcBSource link C9https://www.redfin.com/Source link E9https://www.redfin.com/sell-a-home/address?&utm_source=google&utm_medium=ppc&utm_campaign=1022646&utm_term=aud-849690325664:kwd-17670083296&utm_content=458049157575&adgid=102766387573&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1H6kf48jFCL_b5DHcMbH3rlzCaGPinVbUAMqTNi_q_f8crk2NLjMAaAhSMEALw_wcB&gclsrc=aw.dsSource link F9https://sell.fasthomeoffer.com/Source link H9https://sell.fasthomeoffer.com/get-cash-offer/?utm_source=google&utm_medium=cpc&utm_term=%2Bcompany%20%2Bthat%20%2Bbuys%20%2Bhomes.g.b&utm_campaign=Google_Search_Centralized_LV_SuperMax&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0XW1qmghRuATeNQ4s0BA2HEDE4bUR8KH4AlV0vxnM6pZ057fO_3GUaAqIqEALw_wcBSource link I9
10https://sell.fasthomeoffer.com/Source link B10https://sell.fasthomeoffer.com/get-cash-offer/?utm_source=google&utm_medium=cpc&utm_term=%2Bhow%20%2Bto%20%2Bsell%20%2Byour%20%2Bhouse.g.b&utm_campaign=Google_Search_Centralized_LV_SuperMax&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1NfZi1ZUdrnNf2Kqe91J9GNrxUNTatKURSLbpDgt_kZn9H0K2oDPAaAnC8EALw_wcBSource link C10Local #https://www.sellforcashaz.com/Source link E10https://www.sellforcashaz.com/sell-fast/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2aM-WK9g79KEIAKmXrI9BagQK-48ChVuONS3mqblyExPUFkOqTDbAaAhTBEALw_wcBSource link F10https://webuyhousesallyear.com/Source link H10https://webuyhousesallyear.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3yWPG4FKhL0sEpgBkiGOinThvhZrZSiU7b_bWcORfxIr4ztzlP9xMaAgOpEALw_wcBSource link I10
11Hit Search for a second timeHit Search for a second time
12https://www.redfin.com/Source link B12https://www.redfin.com/sell-a-home/address?&utm_source=google&utm_medium=ppc&utm_campaign=1022640&utm_term=aud-923999260716:kwd-398995919702&utm_content=471681493842&adgid=102766377493&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1lqotNTzRJ4e8Q0IEHB2XqJdf3G_qWolspecbvk436SZ1Nd7rWkLAaAp0DEALw_wcB&gclsrc=aw.dsSource link C12https://prestigepropertyus.com/Source link E12https://prestigepropertyus.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0EN1HnHJ6nVZu_srbtfsEd_ctTaxlFlqS11KLisarJ5ONiw8IgbGgaAn8HEALw_wcBSource link F12https://www.idealhomeoffer.com/Source link H12https://www.idealhomeoffer.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1QkqzDFPk7tvjp_CK41NiX9hc2_g1iBdeDswMsKl79LnojjPFt1uUaAoC8EALw_wcBSource link I12
13https://webuyhouse.com/Source link B13https://webuyhouse.com/lp1/g/?utm_source=google&utm_medium=cpc&utm_campaign=wbh-high-cpa&utm_term=cash%20for%20my%20house&utm_content=&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2aydocNB31uuyV9LV-Y0lqQmCBVm89e4BcLITuDGneP9-pqI3AIooaAqbHEALw_wcBSource link C13https://sell.unitedhomeoffer.com/Source link E13https://sell.unitedhomeoffer.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3crRlAefAE28NPT_dBoj_JL20T0ZzP1vTF7LaOF5arJqHtQkFNyj8aAqXsEALw_wcBSource link F13https://webuyhouse.com/Source link H13https://webuyhouse.com/lp1/g/?utm_source=google&utm_medium=cpc&utm_campaign=wbh-high-cpa&utm_term=we%20buy%20houses%20for%20cash&utm_content=&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3_752K_6g8bi7YloOTmNQcfcqIOMCVsI0ABv1djUk-mbSDlYGJAukaAvuMEALw_wcBSource link I13
14https://prestigepropertyus.com/Source link B14https://prestigepropertyus.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2EYdOqrBTgrcfNfpLfSVn26lIuk4sSjvvDZY9LP8MmNIGTnHV4974aAheJEALw_wcBSource link C14https://www.redfin.com/Source link E14https://www.redfin.com/sell-a-home/address?&utm_source=google&utm_medium=ppc&utm_campaign=1022646&utm_term=aud-299174632494:kwd-341368606505&utm_content=458049157359&adgid=102766387173&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo36i0o9AfXEGoODf1CYaK6Xzq5YVyVDrfK5RZLk9tt7K-wxr9sqkfYaAsbyEALw_wcB&gclsrc=aw.dsSource link F14https://getoffer.houseofferhub.com/Source link H14https://getoffer.houseofferhub.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1SLoNqq27GLle7y6vsL-BD_VPJTpTWmv-v2IgvyEtTRxhXyIcOcawaAh7GEALw_wcBSource link I14
15https://home2.cash/Source link B15https://home2.cash/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0ZsPdSwbWouU6eG9eCUOBCC3Wd8oKABpJ_Z5PF8iztIzRRWjtpXuQaAg5oEALw_wcBSource link C15https://webuyhomes.triadinvestmentllc.com/Source link E15https://webuyhomes.triadinvestmentllc.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3CluTz2mS5xGFAWFXt8wlzw0SLWklsKoiSTuliC8I5yuqxutMQltsaAlVtEALw_wcBSource link F15https://freedomhomebuyer.com/Source link H15https://freedomhomebuyer.com/arizona/we-buy-houses/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3JMTRiSwj8yhJlUuR46SCJZDkTJV_eNu8vz4FYUI8fBXYaHWTyrwEaAvRJEALw_wcBSource link I15
16Hit Search for a third timeHit Search for a third timeHow to sell my house fast ArizonaHow to sell my house fast ArizonaHow to sell my house fast Arizona
17LOCAL #https://ezmaxoffer.com/Source link B17https://ezmaxoffer.com/get-an-offer/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1n7otK1aLN7BscyFF1GlGOm-x8EOqDzhzmE9WLWC5nKqt84VHGIhYaAo7-EALw_wcBSource link C17local#https://www.sellforcashaz.com/Source link E17https://www.sellforcashaz.com/sell-fast/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3GrFInyj7evKMMLeDkdNfrgvau4c9fuDfH5yGqoG6nqaFeiUsqLOQaAra4EALw_wcBSource link F17https://www.homevestors.com/Source link H17https://www.homevestors.com/phoenix/hva1-buy-home/?utm_source=google_search&utm_medium=cpc&utm_campaign=12182880600&utm_term=home%20buying%20companies&utm_content=494668800463&keyword=home%20buying%20companies&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3HP0dZPJZDYrlPDtr1Xaqh03IBzFTYRyW8-eBNLnqvG02GInPQNpQaAnbCEALw_wcBSource link I17
18https://sellhousefast.com/Source link B18https://sellhousefast.com/lp/g1/?utm_source=google&utm_medium=cpc&utm_campaign=g-shf-high-cpa&utm_term=cash%20for%20houses&utm_content=&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2_alXDVPKX-P9szJxJQc0y4EkKzm2D7xEFh1ihG7_VTvg9ZSoA0AsaAqJIEALw_wcBSource link C18https://my.offerpad.com/Source link E18https://my.offerpad.com/home-offer/?utm_source=google&utm_medium=cpc&utm_campaign=search-acquisition-phoenix&utm_term=%2Bsell%20%2Bmy%20%2Bhouse%20%2Bfast&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0I5uYl6H1D4SkCr17dzsG-WUSRj54XBdUNgX0l3RNPC9LC-abq2ZcaAm5_EALw_wcBSource link F18https://networthrealtyusa.com/Source link H18https://networthrealtyusa.com/sellyourhouse?utm_source=google&utm_medium=cpc&utm_content=Phoenix&utm_term=quick%20cash%20house%20offer&utm_campaign=Phoenix%20Sell%20Your%20Home%20Broad&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0Dlxv10DPdBJnYDYHDnF8OBMYhw98JvDclXRfhLnS24O52tv9XJNoaAnyFEALw_wcBSource link I18
19https://www.1stophousebuyers.com/Source link B19https://www.1stophousebuyers.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo17tklBuYaHobB85J1Vhkxjtz-sDt3qYy1BJs41J5gBfkhpLxXifV0aAi5oEALw_wcBSource link C19https://cashsellquickclose.com/Source link E19https://cashsellquickclose.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1Aeg65JNFUwiq4xTui_mcoolXeyxCqgQbzwTYF9yJRoZ20XmH1iUoaAr62EALw_wcBSource link F19https://sell-house-cash.antbuyshouses.house/Source link H19https://sell-house-cash.antbuyshouses.house/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3TO8tiAqnZ2P8YCy2j-mXemnqIBLW_GEvMwqpf2u5_BXq8_KwPVlkaAjB7EALw_wcBSource link I19
20https://www.homelight.com/Source link B20https://www.homelight.com/simple/?kwrd=house&utm_content=11621158078_120999927543_c_b__9030095__521954714868&utm_campaign=11621158078&{remtag}&Cj0KCQjwhr2FBhDbARIsACjwLo2XKxffqaZmtIS9Ry0W969RcoAlIpIQJQlfODlSRjKtWBs3nz7SXKIaAhVTEALw_wcB&utm_source=google&utm_medium=cpc&utm_term=selling%20house%20owner&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2XKxffqaZmtIS9Ry0W969RcoAlIpIQJQlfODlSRjKtWBs3nz7SXKIaAhVTEALw_wcBSource link C20https://www.redfin.com/Source link E20https://www.redfin.com/sell-a-home/address?&utm_source=google&utm_medium=ppc&utm_campaign=1022646&utm_term=aud-849690325664:kwd-341368606505&utm_content=471745085228&adgid=102766387173&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0KVSIdA4p9BjXGZRD3PmHkptdJAT2O3_IH6IcryHRgt1uD6pf39TgaAjdUEALw_wcB&gclsrc=aw.dsSource link F20https://quickcashoffer.com/Source link H20https://quickcashoffer.com/?utm_source=google&utm_medium=cpc&utm_term=we%20buy%20houses%20in%20arizona&utm_campaign=competitor-snipe&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0FMhpdydIcLLXlQK5jb3-hydj2xgoHdep4yXvdlhxGfiGATWsEoZwaAmDeEALw_wcBSource link I20
21Hit Search for a fourth timeHit Search for a fourth time
22https://open-doorcomparison.com/Source link B22https://open-doorcomparison.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2-UWIyc0eQlmPuSN_51GnlbcFRF77yIXUG9CCb02DXIWYWkXiOdp4aAtvhEALw_wcBSource link C22https://www.redfin.com/Source link E22https://www.redfin.com/sell-a-home/address?&utm_source=google&utm_medium=ppc&utm_campaign=1022646&utm_term=aud-849690325664:kwd-17669260096&utm_content=471745085228&adgid=102766387173&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3aZ1qsTiPycg6kyHsRHNsqy6LlKjlWETw0KBOmJ05-m6fmksXrcZQaApL4EALw_wcB&gclsrc=aw.dsSource link F22https://gemworkspropertyinvestments.com/Source link H22https://gemworkspropertyinvestments.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0Zc0BdscfJJrHdhfIY4Td9BffNyAdDggJi2xvQ0s9_mkG6DC3xG5saAoaFEALw_wcBSource link I22
23https://myezhomesale.com/Source link B23https://myezhomesale.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2VZGBS3oA7yT-DwjOnb9mNq5VqWF8FpPyO7Suvt6Nx0ENYJlBl3x4aAglQEALw_wcBSource link C23https://www.sellforcashaz.com/Source link E23https://www.sellforcashaz.com/sell-fast/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0yNYViRIoMweJZJc2D-uN_LbC-QtsmL8LN4125B3U4SGl0YhScOKUaAmphEALw_wcBSource link F23local#https://freedomhomebuyer.com/Source link H23https://freedomhomebuyer.com/arizona/investors-buy/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3RtmIve5qFQdS9HEHNuDyfpMN8U-hgIepvTrCDTk7rVBk2lUSzw9AaAiNVEALw_wcBSource link I23
24https://freedomhawkhomebuyers.com/Source link B24https://freedomhawkhomebuyers.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3R_cFCvwsLZB_RnuQ8kf-YygtjTkSHu1dmqwNpECxaEYAp5eidEAAaAhGPEALw_wcBSource link C24https://sell.unitedhomeoffer.com/Source link E24https://sell.unitedhomeoffer.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2VaWS8EmfLRYmw-2qKOzy8BJcSUdxOnHFxF9KAtMVMeCrqqpFaQQ8aAnFBEALw_wcBSource link F24local#https://leebuysazhomes.com/Source link H24https://leebuysazhomes.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0kZ3BWReQrDGLbYz8KeLlaoPimTJ_Q6Ikf7TUpoAMEdd-kxpkJ0wIaAp_9EALw_wcBSource link I24
25https://integrityhomesus.com/Source link B25https://integrityhomesus.com/?matchtype=b&network=g&device=c&adposition=&keyword=sell%20my%20house&ClickID=Cj0KCQjwhr2FBhDbARIsACjwLo0ulzlEPclV5QPzSwTrmPQGSUbtedGvWg_h3W253hIl0HO7RKrX2PIaAgUsEALw_wcB&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0ulzlEPclV5QPzSwTrmPQGSUbtedGvWg_h3W253hIl0HO7RKrX2PIaAgUsEALw_wcBSource link C25https://www.opendoor.com/Source link E25https://www.opendoor.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3u8obtlltufAbggkDXABmlkCrRbHZVuNoJHD62o8o6AE0vRCvA2xIaAhr3EALw_wcB&utm_campaign=1666141829&utm_content=463624336479&utm_medium=search&utm_source=google&utm_term=%2Bhow+%2Bto+%2Bsell+%2Bhouse+%2BfastSource link F25https://sellmyhousefast123.com/Source link H25https://sellmyhousefast123.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo17h4RrraCl7zkgxEBvFsnkWTF2zyZL8a2uWLnWsQm3uCdJAdrqo4oaAlX4EALw_wcBSource link I25
26Hit Search for a fifth timeHit Search for a fifth time
27https://www.redfin.com/sell-a-homeSource link B27https://www.redfin.com/sell-a-home/address?&utm_source=google&utm_medium=ppc&utm_campaign=1022646&utm_term=aud-849690325664:kwd-398995919702&utm_content=458049157563&adgid=102766387573&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo2thfGHvaiAYrm96nU7y0bMEX9zUCGs-RbsmWFevOxGHVahYMzwZfQaAiHxEALw_wcB&gclsrc=aw.dsSource link C27LOCALhttps://www.azfaircashoffer.com/Source link E27https://www.azfaircashoffer.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx1iY1pDJR9tREllSpk9PoywZqkkoC054wE3VcfWbVcKAVJdIOxN23oaAhLZEALw_wcBSource link F27https://freedomhomebuyer.com/Source link H27https://freedomhomebuyer.com/arizona/investors-buy/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0TjRjvwhndkuzPyWtaWe2ATGz0cXKDRbM4srbni1rDVXfv_SuEEVsaAgMREALw_wcBSource link I27
28https://www.homie.com/Source link B28https://www.homie.com/sell-az?campaignid=12610840488&adgroupid=120773975718&adid=509077364307&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1RUrpHS_Q51qg1RvQm26l7jCav_FN5VPTknkg3bbB2yyJsfxYJmrgaAoIkEALw_wcBSource link C28LOCALhttps://freedomhomebuyer.com/Source link E28https://freedomhomebuyer.com/arizona/we-buy-houses/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx1DZGjcVHBnr2h4pVjyIqhKnRDWJ0c98Zh0Uiq-cRKsVA37M2d58pEaAiLHEALw_wcBSource link F28https://webuyfiredamagedhouses.com/Source link H28https://webuyfiredamagedhouses.com/?utm_source=google&utm_medium=cpc&utm_term&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3Vn1pEErb2eOxBMRk0Q_iNFn3nNG5HiprbmrrwhXpqRtxKlCBIU8MaAusKEALw_wcBSource link I28
29https://freedomhomebuyer.com/Source link B29https://freedomhomebuyer.com/arizona/sell-house-fast/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo1UJMmfUyI68cZWqYXqDqeoON6pbCqRWYuKMMQQoPYwDU0ltfJWf0caAkFqEALw_wcBSource link C29https://www.homevestors.com/Source link E29https://www.homevestors.com/phoenix/hva1-sell-home/?utm_source=google_search&utm_medium=cpc&utm_campaign=12182880600&utm_term=sell%20my%20house&utm_content=494668800466&keyword=sell%20my%20house&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx1YVPynrIVdPjQW0tYogFnkRro6sI8mojPVCu7KOay-Z47BBxohch8aAmsQEALw_wcBSource link F29https://www.instanthousecashoffer.com/Source link H29https://www.instanthousecashoffer.com/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo3mhuGaZ0dXaPPkC8XYGnP3VDWaGi0ltOMZcSbknWnEKY4kN4olvQUaApbBEALw_wcBSource link I29
30https://sell-house-cash.antbuyshouses.house/Source link B30https://sell-house-cash.antbuyshouses.house/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0Q_v6OCRVxlJzGzaoaflW5ew9jXJ61XCfGcr48puz35B7kammkAD8aAsfeEALw_wcBSource link C30https://prestigepropertyus.com/Source link E30https://prestigepropertyus.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx26Q714EokoX9Dj1M3X6hyprOg99p-PH1gu84RxMY0MT4BLRwToQAsaAuq_EALw_wcBSource link F30https://newagainhouses.com/Source link H30https://newagainhouses.com/mesa-az/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0zddHIWYw0AnzSOGjO9mj6GbMsnC745cGclfZiMpWc2qHBCq0QHfUaAv6-EALw_wcBSource link I30
31how sell your house fast
32https://www.homevestors.com/Source link E32https://www.homevestors.com/phoenix/hva1-sell-home/?utm_source=google_search&utm_medium=cpc&utm_campaign=12182880600&utm_term=sell%20my%20home%20fast&utm_content=494668800427&keyword=sell%20my%20home%20fast&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx0FEJljOHac69rmwfcxvT-X0T9GIh82daqfZ9xVbvrmyGc5VXOYXqQaAmv7EALw_wcBSource link F32
33LOCAL #https://www.azfaircashoffer.com/Source link E33https://www.azfaircashoffer.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx3aALVL500MceviEnLCYHCtiqRxmjOYQFE-sGpQfTSlquNsWPhOxBQaAjO8EALw_wcBSource link F33
34BUY RENTALS FROM INVESTORShttps://www.roofstock.com/Source link E34https://www.roofstock.com/seller-services?utm_term=sell%20my%20house%20fast&utm_campaign=NB-Sellers-iBuyers-Search-US-Google-Exact&utm_source=adwords&utm_medium=ppc&hsa_tgt=kwd-108992865&hsa_grp=120016331223&hsa_src=g&hsa_net=adwords&hsa_mt=e&hsa_ver=3&hsa_ad=516948694697&hsa_acc=4347318879&hsa_kw=sell%20my%20house%20fast&hsa_cam=12832640133&medium=tsa&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx1YBZFMCvaIiN8TM3AGOsnn1XgnnrUcSVUzg8DnKXfJjf3cN8H9PcwaAndIEALw_wcB&gclsrc=aw.dsSource link F34
35LOCAL #https://www.webuyhomesinaz.com/Source link E35https://www.webuyhomesinaz.com/?source=adwords&kw=we%20buy%20houses&campaign=Broad&device=c&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx1-zT8F2332ab3lnmSk2z3cXNJFR2Cd32nGwT6DtYLUOOEIsdU8ZYUaAs7cEALw_wcBSource link F35
SearchResultsList.1

Open original tab

SearchResultsList.1
RowABCD
1LOCAL #TOLL FREE
2
3https://www.1stophousebuyers.com/Source link C3
42https://www.azfaircashoffer.com/Source link B4
5
6
7https://cashsellquickclose.com/Source link C7
8https://ezmaxoffer.com/Source link B8
9https://freedomhawkhomebuyers.com/Source link C9
107https://freedomhomebuyer.com/Source link B10
11fasthomebuyeraz.comSource link B11https://gemworkspropertyinvestments.com/Source link C11
12https://getoffer.houseofferhub.com/Source link C12
13https://integrityhomesus.com/Source link C13
14https://www.instanthousecashoffer.com/Source link C14
152https://www.homevestors.com/Source link B15https://home2.cash/Source link C15
16https://www.homelight.com/Source link C16
17https://www.homie.com/Source link C17
18https://www.homeoffersarizona.com/Source link C18
19
20https://www.idealhomeoffer.com/Source link C20
21https://leebuysazhomes.com/Source link B21
22https://myezhomesale.com/Source link C22
23https://www.opendoor.com/Source link C232
24https://networthrealtyusa.com/Source link C24
25https://newagainhouses.com/Source link B25
26https://open-doorcomparison.com/Source link C26
27https://offergiants.com/Source link C27
28https://my.offerpad.com/Source link C28
29https://prestigepropertyus.com/Source link C292
30https://quickcashoffer.com/Source link C30
31https://prestigepropertyus.com/Source link C31
32https://www.redfin.com/Source link C325
33https://sell-house-cash.antbuyshouses.house/Source link C33
34https://www.sellforcashaz.com/Source link B34https://sellhousefast.com/Source link C34
35https://sell.fasthomeoffer.com/Source link C352
36https://sellmyhousefast123.com/Source link C36
37https://sell.unitedhomeoffer.com/Source link C372
38https://www.sellforcashaz.com/Source link C382
39https://webuyhomes.triadinvestmentllc.com/Source link C39
40https://webuyhouse.com/Source link C402
41https://webuyfiredamagedhouses.com/Source link C41
42https://webuy.thetrustedhomebuyer.com/Source link C42
43https://webuyhousesallyear.com/Source link C43
SearchResults.2

Open original tab

SearchResults.2
RowABCDEFGHIJKL
1Can I Sell My House Without a Realtorhow sell my house fastwhere to sell my house onlinehow to sell my house without a realtor
2https://www.homevestors.com/Source link H2https://www.homevestors.com/phoenix/hva1-sell-home/?utm_source=google_search&utm_medium=cpc&utm_campaign=12182880600&utm_term=sell%20my%20house&utm_content=494668800466&keyword=sell%20my%20house&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx30AS9PovBQsbV6QOMhgppYQEIQkKIxlSJlpw-jTxvobGmdSZl8mioaAmQYEALw_wcBSource link I2https://myezhomesale.com/Source link K2https://myezhomesale.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx3CsOwTNr-v646bWlSBocEh8KtmJ6XzFUwCBX-LD_BdCanK01utQD0aAhnqEALw_wcBSource link L2
3https://www.roofstock.com/Source link H3https://www.roofstock.com/seller-services?utm_term=sell%20my%20home%20fast%20online&utm_campaign=NB-Sellers-iBuyers-Search-US-Google-Exact&utm_source=adwords&utm_medium=ppc&hsa_tgt=kwd-410478802926&hsa_grp=120016331263&hsa_src=g&hsa_net=adwords&hsa_mt=e&hsa_ver=3&hsa_ad=516948694706&hsa_acc=4347318879&hsa_kw=sell%20my%20home%20fast%20online&hsa_cam=12832640133&medium=tsa&?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx0N8eGpqaB5lQUmr7wPRylMYHWiuGRIll9HmIeep-gWkrgX2VwJjcEaAhuOEALw_wcB&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx0N8eGpqaB5lQUmr7wPRylMYHWiuGRIll9HmIeep&gclsrc=aw.dsSource link I3LOCAL #https://ezmaxoffer.com/Source link K3https://ezmaxoffer.com/get-an-offer/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx0Kh7s65wb7IFqBnrNoQ-jsBtXH2e-irc5huGrc5Vs_yCFsR6MRqloaAn8DEALw_wcBSource link L3
4https://www.redfin.com/Source link H4https://www.redfin.com/sell-a-home/address?&utm_source=google&utm_medium=ppc&utm_campaign=1022646&utm_term=aud-299174632494:kwd-17669792656&utm_content=471745085252&adgid=102766387573&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx3FROjEsWp1KLdaBV1bD2PwSSjsvE7xdq-5M-IPmaFuVx6OaU2NvqEaAiC2EALw_wcB&gclsrc=aw.dsSource link I4LOCAL #https://www.webuydumbhomes.com/Source link K4https://www.webuydumbhomes.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx2O-zXL7aqCJOiGGU27Xxsa7f-8KJ8SO_m2KMXlVp6cnHU3LRiRHsEaAiBvEALw_wcBSource link L4
5https://freedomhawkhomebuyers.com/Source link H5https://freedomhawkhomebuyers.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx0G_NoRjBi1hJobw_M4N2a4IRVRvAub8DSY3u7luNh-GRllS14iiAUaAoq7EALw_wcBSource link I5SITE FOR BUYERShttps://www.knock.com/Source link K5https://www.knock.com/?utm_source=google&utm_medium=ppc&utm_campaign=home_selling&gclsrc=aw.ds&&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx3TdNz1L7q_WBqiA74v0KQ2HC2rv28hqyW5wdotnm4P3GCZnE5LL2IaAnPPEALw_wcBSource link L5
6sell my house online freehow to sell my house without a realtor in ARIZONA
7LOCAL #https://freedomhomebuyer.com/Source link H7https://freedomhomebuyer.com/arizona/sell-for-free/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx0n7asFYi2Gx1XNFOtK6M9nuLygBNMNDiglBlmucDyEiI8Azd7sjagaAqQgEALw_wcBSource link I7https://www.homevestors.com/Source link J7https://www.homevestors.com/phoenix/hva1-sell-home/?utm_source=google_search&utm_medium=cpc&utm_campaign=12182880600&utm_term=sell%20my%20house&utm_content=494668800466&keyword=sell%20my%20house&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx3k-xm_r_2lC46wls2MxCdcoJUZ7ChIhYjWCEw_11PIqqMjTphp-DoaAvMEEALw_wcBSource link K7
8https://www.homevestors.com/Source link H8https://www.homevestors.com/phoenix/hva1-sell-home/?utm_source=google_search&utm_medium=cpc&utm_campaign=12182880600&utm_term=sell%20my%20house&utm_content=494668800469&keyword=sell%20my%20house&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx2kuNdDw3KHQMbjz12M7AZg-R52Jg-0_oaoNeheH9FJag5Kz15lnpMaAv7pEALw_wcBSource link I8https://sell.fasthomeoffer.com/Source link J8https://sell.fasthomeoffer.com/get-cash-offer/?utm_source=google&utm_medium=cpc&utm_term=%2Bselling%20%2Bmy%20%2Bhouse%20%2Bwithout%20%2Ba%20%2Brealtor.g.b&utm_campaign=Google_Search_Centralized_LV_SuperMax&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx2Gz3uvfV2HFoDWHY7E5RAiEDffHP9BinlFEewNDEz8Xywmy5MmE9saAlaXEALw_wcBSource link K8
9https://myezhomesale.com/Source link H9https://myezhomesale.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx2mSETXFbYlV7JlUuqUua3P1yTJ3-rds1hN1gD_dzJQmnK30lIZHkcaAod_EALw_wcBSource link I9https://www.redfin.com/Source link J9https://www.redfin.com/sell-a-home/address?&utm_source=google&utm_medium=ppc&utm_campaign=1022646&utm_term=aud-299174632494:kwd-398995919702&utm_content=471745085252&adgid=102766387573&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx2jp2jl-xEkOyToQjVPkiNY7TvKlkgyjZhlYjciIhbPuzXF8cq9_zsaAjLmEALw_wcB&gclsrc=aw.dsSource link K9
10TARGET HOME SELLER LEADShttps://smartzip.com/Source link H10https://smartzip.com/landing_google.cfm?utm_source=PPC&utm_content=SZGoogleAd&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx3rfKCmUBmUXZly3ugSFmRgvpkdX1lSiUgNCtf88TxU3DTJjT4K32YaAu7eEALw_wcBSource link I10https://networthrealtyusa.com/Source link J10https://networthrealtyusa.com/sellyourhouse?utm_source=google&utm_medium=cpc&utm_content=Phoenix&utm_term=%2Bsell%20%2Bmy%20%2Bhouse&utm_campaign=Phoenix%20Sell%20Your%20Home%20Broad&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx2kpHH8Q23YRCawnaiw6xPuUVok9ZYU82xxCr1E2b_w5ohsm38JccIaAsoYEALw_wcBSource link K10
11sell my house online reviews
12The HYSS Group 480-343-7894 10235 S 51st Street Phoenix, AZ 85044GOOD QUESTIONAIREhttps://open-doorcomparison.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx1Y4UZqg-lfRfUOf1G-CPWRibfyqxQo-sFkZu-huFXMer6aw6N_YacaAnogEALw_wcBSource link I12
13LEE BUYS AZ HOMES 520-829-3939 dotnetacquisitions.comSource link G13https://leebuysazhomes.com/Source link H13https://leebuysazhomes.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx19D9webWdXJU8Slw_tgzyq0_M_S_7Gy1ofqTMPNgfOts1nFy2ksX4aAkxbEALw_wcBSource link I13
14Localhttps://www.azhomebuyer.com/Source link H14https://www.azhomebuyer.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx3HTw67KhZ2opnmswsakfMKxRbohAiMxcHfhv9RMLMyDY03qABPbgcaAlluEALw_wcBSource link I14
15https://freedomhawkhomebuyers.com/Source link H15https://freedomhawkhomebuyers.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx2mnut0QzDcWO1jsaXcRaeVTNBtp9-HCoPYEL87TdpZ6ljWvBza5jQaAppPEALw_wcBSource link I15
16companies that buy houses near me
17https://www.homevestors.com/Source link H17https://www.homevestors.com/phoenix/hva1-buy-home/?utm_source=google_search&utm_medium=cpc&utm_campaign=12182880600&utm_term=companies%20that%20buy%20houses%20near%20me&utm_content=494668800412&keyword=companies%20that%20buy%20houses%20near%20me&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx2Du8Ay7OJ5WXmN-G9mRCyRjEKqrn-R3jtGN-bZYi5dF_tT_LFK5XcaAjnaEALw_wcBSource link I17
18Local #https://www.joehomebuyerphoenixmetro.com/Source link H18https://www.joehomebuyerphoenixmetro.com/?utm_source=google&utm_medium=cpc&utm_campaign=117409079430&utm_term=companies%20that%20buy%20homes&utm_content=481163784638&matchtype=p&device=c&network=g&position=&guid=11963133463250947950&gclid=Cj0KCQjw78yFBhCZARIsAOxgSx0a0QymyOO2R_2FpQu_h2xljMdiaTudFsOgLhQVy7k_jSgkVq7mvmQaAlGLEALw_wcBSource link I18
19LOCAL #https://stephthelocalhomebuyer.com/Source link H19https://stephthelocalhomebuyer.com/Source link I19
20Local#https://www.helpfulhomebuyersus.com/Source link H20https://www.helpfulhomebuyersus.com/cash-offer/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx1U3PfxZwnfmGh7cdPAsUy6yRPcLGfzhnJv75-5uNudlEovcb03fj8aAhw-EALw_wcBSource link I20
Sheet14

Open original tab

Sheet14
RowABCDEFG
1NEAR ME
2http://buymyhousenow.com/Source link A2
3https://www.azfaircashoffer.com/Source link A3THIS IS BRAD as the BC GROUP
4(480) 447-9760Source link A4No Website
5https://www.mrspropertysolutions.com/we-buy-houses-arizona/Source link A5
6https://www.webuyhomesinaz.com/Source link A6
7https://www.ritabuyshouses.com/Source link A7
8(480) 818-6698Source link A8
9https://www.doughopkins.com/Source link A9AD RUNNING
10(602) 687-6992Source link A10
11https://www.cashforhomesarizona.com/Source link A11
12https://myezhomesale.com/Source link A12AD RUNNING
13https://assist2sell.com/Source link A13
14https://www.webuyhousesphoenixarizona.com/Source link A14
15https://www.cashforhomesarizona.com/Source link A15
16https://www.offerpad.com/Source link A16Good Website
17https://www.phoenixfastsellhomebuyers.com/Source link A17
18https://www.joehomebuyerarizonagroup.com/Source link A18
19https://www.ushomegroup.com/Source link A19Messenger Chat Apphttps://www.facebook.com/business/goals/add-live-chat-to-website-with-messengerSource link E19
20https://www.wesleycashbuyshouses.com/Source link A20
21https://offerohomebuyers.com/Source link A21
22https://www.phoenixfastsellhomebuyers.com/Source link A22
23https://www.redfin.com/Source link A23
24https://offerkey.com/Source link A24
25https://www.phoenixmobilehome.com/Source link A25MOBILE HOME BUYER
26https://dwellphoenix.com/home-valuationSource link A26Top Producer NOT WHOLESALE
27https://renterswarehouse.com/?utm_source=referralSource link A27
28https://the1031.com/Source link A28
29https://amazingoffer.com/Source link A29Ad RunningI LIKE THIS
30http://www.embassy-realty.com/Source link A30HORRIBLE WEBSITE!!!!
31https://regionalcashbuyers.com/Source link A31National
32https://www.finallysold.com/Source link A32
33https://www.thetrustedhomebuyer.com/contact/Source link A33National58 reviews
34https://www.smartestseller.com/sell-my-house-fast-arizona-we-buy-houses-in-arizona/Source link A34
35https://phoenix-propertymanagement.com/Source link A35Home Qwikhttps://phoenix-propertymanagement.com/im-an-investor/Source link C35INVESTORS/PROPERTY MANAGERS
36https://www.gorenter.com/Source link A36Go Renterhttps://www.gorenter.com/for-owners/Source link C36INVESTORS/PROPERTY MANAGERS
37Old BOSWORTH AND ASSOCIATES BUSINESS
38https://www.cashforhomesarizona.com/Source link A38
39https://www.azhomebuyer.com/Source link A39Kyak CapitalAd running
40https://www.localhomebuyer.org/contact-us/Source link A40HORRIBLE WEBSITE!!!!
41https://www.webuyhomesinaz.com/Source link A41Ad running
42https://www.bcteam.com/Source link A42https://www.arizonadiscounthomes.com/Source link D42https://www.azfaircashoffer.com/?gclid=Cj0KCQjw78yFBhCZARIsAOxgSx3M_t9xmGC9lRqZ_0kB24k8xIByXfN0wUFFbLf046T0PHC2WVWf94saAu1vEALw_wcBSource link F42
43https://www.makesenseoffers.com/Source link A43
44https://www.hugecashoffer.com/Source link A44
45https://72sold.com/Source link A45STAY UP TO 6 MONTHS
46dynamic Real Estate AZfacebook
47gofastoffer.comSource link A47
48homie
SearchResultsList.2

Open original tab

SearchResultsList.2
RowABC
1
2LOCALNOT LOCAL
3
4
5
6
7
8
9
10https://ezmaxoffer.com/Source link B10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25https://myezhomesale.com/Source link C25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44https://www.webuydumbhomes.com/Source link B44
AnswerThePublic

Open original tab

AnswerThePublic
RowABCDEF
1Sell my house
2https://answerthepublic.com/reports/2f3a8e20-29f1-46b6-97ac-59199df50834Source link A2
3Created: 27-05-2021https://www.azfaircashoffer.com/Source link F3
4Suggestionhttps://www.azfaircashoffer.com/Source link F4
5rent or sell my househttps://www.azfaircashoffer.com/Source link F5
6will i sell my house
7rent or sell my house calculator
8is it better to rent or sell my houseI like www.closedforcash.comSource link C8
9is it best to rent or sell my house
10should i rent or sell my house
11can sell my house if have mortgage
12can sell my house myself
13can't sell my house
14to sell my house quicklyhttps://www.joehomebuyerarizonagroup.com/Source link B14https://prestigepropertyus.com/Source link C14https://www.joehomebuyerphoenixmetro.com/Source link D14https://www.closedforcash.coSource link E14https://www.closedforcash.coSource link F14
15how to sell your house quicklyhttps://sell.unitedhomeoffer.com/Source link B15https://www.azfaircashoffer.com/Source link C15https://webuy.thetrustedhomebuyer.com/Source link D15https://freedomhomebuyer.com/Source link E15https://www.closedforcash.com/Source link F15
16how to sell your house quickly tipshttps://www.redfin.com/Source link B16https://networthrealtyusa.com/Source link C16https://sell.fasthomeoffer.com/Source link D16https://ultrahomebuyers.com/Source link E16
17how to sell your house fasthttps://prestigepropertyus.com/Source link B17https://www.closedforcash.com/Source link C17https://networthrealtyusa.com/Source link D17https://www.redfin.com/Source link E17
18need to sell your house fasthttps://prestigepropertyus.com/Source link B18https://www.azfaircashoffer.com/Source link C18https://www.redfin.com/Source link D18https://ezmaxoffer.com/Source link E18
19mantra to sell my house fasthttps://prestigepropertyus.com/Source link B19https://www.joehomebuyerphoenixmetro.com/Source link C19https://www.redfin.com/Source link D19https://networthrealtyusa.com/Source link E19
20want to sell my house fasthttps://www.webuyhomesinaz.com/Source link B20https://freedomhawkhomebuyers.com/Source link C20https://www.joehomebuyerphoenixmetro.com/Source link D20https://sell-house-cash.antbuyshouses.house/Source link E20
21how to sell my house fast for cashhttps://freedomhomebuyer.com/Source link B21https://networthrealtyusa.com/Source link C21https://prestigepropertyus.com/Source link D21https://freedomhawkhomebuyers.com/Source link E21
22how to sell your property quicklyhttps://www.redfin.com/Source link B22https://www.webuyhomesinaz.com/Source link C22https://prestigepropertyus.com/Source link D22https://integrityhomesus.com/Source link E22
23how to sell your house fasthttps://prestigepropertyus.com/Source link B23https://www.closedforcash.com/Source link C23https://www.webuyhomesinaz.com/Source link D23https://ezmaxoffer.com/Source link F23
24to sell my househttps://networthrealtyusa.com/Source link B24https://webuy.thetrustedhomebuyer.com/Source link C24https://offeronhomes.com/Source link D24https://freecashofferoption.com/Source link E24https://sell.fasthomeoffer.com/Source link F24
25to sell my house quicklyhttps://prestigepropertyus.com/Source link B25https://www.webuyhomesinaz.com/Source link C25https://freedomhawkhomebuyers.com/Source link D25https://sell-house-cash.antbuyshouses.house/Source link E25
26to sell my house what do I needhttps://prestigepropertyus.com/Source link B26https://www.redfin.com/Source link C26https://freedomhomebuyer.com/Source link D26https://webuy.thetrustedhomebuyer.com/Source link E26
27should I sell my house nowhttps://prestigepropertyus.com/Source link B27https://www.revolutionlistings.com/Source link C27https://freecashofferoption.com/Source link F27
28should I sell my house
29Should I sell my house
30should I sell my house or rent it out
31should I sell my house in 2021
32should I sell my house right now
33should I sell my house and rent when I retirehttps://freedomhawkhomebuyers.com/Source link F33
34can't sell my homehttps://prestigepropertyus.com/Source link B34https://www.redfin.com/Source link C34https://freedomhomebuyer.com/Source link D34https://webuy.thetrustedhomebuyer.com/Source link E34https://freedomhomebuyer.com/Source link F34
35to sell your home fasthttps://www.azfaircashoffer.com/Source link B35https://prestigepropertyus.com/Source link C35https://open-doorcomparison.com/Source link D35https://www.upnest.com/Source link E35https://freedomhomebuyer.com/Source link F35
36selling to my homehttps://freedomhomebuyer.com/Source link F36
37how to sell my home fasthttps://freedomhomebuyer.com/Source link F37
38how to sell your home fast
39to sell my house what do i need
40can i sell my house without a realtor
41how sell my house fast
42how sell my house
43how sell your house by owner
44how sell your house
45how sell your house yourself
46how sell your house fast
47how to sell my house without a realtorhttps://freedomhawkhomebuyers.com/Source link F47
48how to sell my house by ownerhttps://freedomhawkhomebuyers.com/Source link F48
49how sell my house fast
50how sell my house
51how sell your house by owner
52how sell your house
53how sell your house yourself
54what will sell my house
55how sell your house fast
56how to sell my house without a realtor
57when i sell my house do i pay taxes
58when i sell my house what happens with the mortgage
59when to sell my househttps://www.joehomebuyerphoenixmetro.com/Source link F59
60when i sell my house how much do i gethttps://www.joehomebuyerphoenixmetro.com/Source link F60
61when i sell my house how do i get the moneyhttps://www.joehomebuyerarizonagroup.com/Source link F61
62when i sell my house what happens to the equityhttps://www.joehomebuyerphoenixmetro.com/Source link F62
63when i sell my house what fees do i pay
64when i sell my house what documents do i need
65where to sell my house
66where to sell my house online
67where to sell my house privately
68where can i sell my house
69where to sell my property
70where can i sell my house fast
71where to sell your house
72where to sell your house privately
73where to sell my house
74where to sell my house online
75who can sell my house
76who can sell my house quickly
77what will sell my house
78who should sell my househttps://integrityhomesus.com/Source link F78
79where to sell my house privately
80who can sell my house fast
81who to sell my house with
82who can sell my house
83who can sell my house quickly
84who should sell my house
85who can sell my house fast
86who to sell your house with
87who can sell my home
88who should i use to sell my househttps://networthrealtyusa.com/Source link F88
89why sell my house nowhttps://networthrealtyusa.com/Source link F89
90why sell my househttps://networthrealtyusa.com/Source link F90
91why sell your house nowhttps://networthrealtyusa.com/Source link F91
92why sell your househttps://networthrealtyusa.com/Source link F92
93why sell your house to zillow
94why sell your house for cash
95why sell your house privately
96why sell your house by ownerhttps://open-doorcomparison.com/Source link F96
97can't sell my house
98should sell my house pay off debt
99can sell my house if have mortgagehttps://offeronhomes.com/Source link F99
100should sell my house
101will i sell my house
102can't sell my home
103should i sell my house now
104can i sell my house without a realtor
105if i sell my house can i still claim benefits
106i sell my house do i pay taxes
107if sell my house do have pay taxes
108can't sell my house
109will selling my house affect my benefits
110do i lose my benefits if i sell my house
111can i buy a house and still claim benefitshttps://prestigepropertyus.com/Source link F111
112can i own a house and still claim benefitshttps://prestigepropertyus.com/Source link F112
113sell my house for cashhttps://prestigepropertyus.com/Source link F113
114sell my house for freehttps://prestigepropertyus.com/Source link F114
115sell my house for cash ukhttps://prestigepropertyus.com/Source link F115
116sell my house for free onlinehttps://prestigepropertyus.com/Source link F116
117sell my house for bitcoinhttps://prestigepropertyus.com/Source link F117
118sell my house for mehttps://prestigepropertyus.com/Source link F118
119sell my house for market valuehttps://prestigepropertyus.com/Source link F119
120sell my house for cash near mehttps://prestigepropertyus.com/Source link F120
121sell my house on zillowhttps://prestigepropertyus.com/Source link F121
122sell my house on zooplahttps://prestigepropertyus.com/Source link F122
123sell my house on realtor.com
124sell my house as is
125sell your house on zillow
126sell my house as is for cash
127sell my house as is fast
128sell your house on gta 5 online
129sell my house near me
130sell my house by owner
131sell my house by myself
132sell your house by owner
133where can i sell my house for free
134where to sell your house for free
135where to sell home
136sell my house to my limited company
137sell my house to the council
138sell my house to buy another
139sell my house to a property developer
140sell my house to rent back
141sell my house to my son
142sell my house to my wife
143sell my house to a builder
144sell my house with strike
145sell my house with a tenant
146sell my house with sitting tenants
147sell my house with purple bricks
148sell my house with zillow
149sell my house with a realtor
150sell my house with redfin
151sell my house with low commission
152sell my house without estate agent
153sell my house without an agent
154sell my house without realtor
155sell my house without a real estate agent
156sell your house without a realtor
157sell your house without an estate agent
158can i sell my house without a realtor
159can i sell my house without spousal consent
160sell my house and rent it back
161sell my house and buy another
162sell my house and rent
163sell my house and still live in it
164sell my house and live in it
165sell my house and rent it back scotland
166sell my house and move abroad
167sell my house and rent instead
168sell my house or rent it out
169sell my house for cash
170sell my house for free
171sell my house for cash uk
172sell my house for free online
173sell my house for bitcoin
174sell my house for me
175sell my house for market value
176rent versus sell my house
177is it better to sell your home or rent it
178is it better to sell your house or rent it
179should i sell my house or rent it out 2020
180sell my house and rent it back
181sell my house or rent it out
182sell my house and rent
183sell my house and buy a new one
184sell my house or rent calculator
185sell your house and rent it back
186sell your house and rent
187sell your house gta v
188sell my house and rent it back
189sell my house at auction
190sell my house and buy another
191sell my house and rent
192sell my house and still live in it
193sell my house after 1 year
194sell my house app
195sell my house aberdeen
196sell my house back to the council
197sell my house but still live in it
198sell my house by auction
199sell my house before buying new one
200sell my house buy another
201sell my house but stay living in it
202sell my house by raffle
203sell my house by lottery
204sell my house contents
205sell my house calculator
206sell my house cheap
207sell my house cash
208sell my house cost
209sell my house capital gains tax
210sell my house connecticut
211sell my house chicago
212sell my house donegal
213sell my house detroit
214sell my house denver
215sell my house dfw
216sell my house dublin
217sell my house durham
218sell my house diffuser blend
219sell my home depot gift card
220sell my house estate agents
221sell my house edinburgh
222sell my house estimate
223sell my house edmonton
224sell my house el paso tx
225sell my house easy fast
226sell my house easy
227sell your house every 2 years
228sell my house fast
229sell my house fast for cash
230sell my house for cash
231sell my house fast uk
232sell my house for free
233sell my house fast birmingham
234sell my house fast manchester
235sell my house for cash uk
236sell my house glasgow
237sell my house galway
238sell my house glengarriff
239sell my house gta online
240sell my house gta 5
241sell my house gold coast
242sell my house georgia
243sell my house gif
244sell my house houston
245sell my house houston tx
246sell my haunted house
247sell your house how much
248sell my house ireland
249sell my house in spain
250sell my house in france
251sell my house in 7 days
252sell my house in 28 days
253sell my house in italy
254sell my house instant quote
255sell my house internationally
256sell my house jacksonville fl
257sell my house jamaicahttps://www.redfin.com/Source link F257
258sell my junk househttps://www.redfin.com/Source link F258
259sell my home jobshttps://www.redfin.com/Source link F259
260sell my house fast jacksonville flhttps://www.redfin.com/Source link F260
261sell my house fast jackson mshttps://www.redfin.com/Source link F261
262sell my house st joseph statuehttps://www.redfin.com/Source link F262
263sell my house st josephhttps://www.redfin.com/Source link F263
264sell my house kansas city
265sell my house kerryhttps://www.revolutionlistings.com/Source link F265
266sell my house knoxville
267sell my house kc
268sell my house kildarehttps://sell-house-cash.antbuyshouses.house/Source link F268
269sell my house kimberley
270sell your house kdrama
271sell my killeen house fasthttps://ultrahomebuyers.com/Source link F271
272sell my house leicester
273sell my house londonhttps://www.upnest.com/Source link F273
274sell my house los angeleshttps://webuy.thetrustedhomebuyer.com/Source link F274
275sell my house las vegashttps://webuy.thetrustedhomebuyer.com/Source link F275
276sell my house low commissionhttps://webuy.thetrustedhomebuyer.com/Source link F276
277sell my house louisville ky
278sell my house long island
279sell my house limerick
280sell my house myselfhttps://www.webuyhomesinaz.com/Source link F280
281sell my house myself onlinehttps://www.webuyhomesinaz.com/Source link F281
282sell my house myself ukhttps://www.webuyhomesinaz.com/Source link F282
283sell my house miami
284sell my house maryland
285sell my house manchester
286sell my house myself australia
287sell my house minneapolis
288sell my house now
289sell my house northern ireland
290sell my house near me
291sell my house no fees
292sell my house no sale no fee
293sell my house nz
294sell my house now or wait
295sell my house nj
296sell my house online
297sell my house on zoopla
298sell my house online uk
299sell my house online free
300sell my house on rightmove
301sell my house or rent it out
302sell my house on gumtree
303sell my house on the internet
304sell my house privately
305sell my house privately uk
306sell my house purple bricks
307sell my house price
308sell my house profit calculator
309sell my house pittsburgh
310sell my house phoenix
311sell my house philadelphiahttps://sell-house-cash.antbuyshouses.house/Source link F311
312sell my house quickly
313sell my house quickly birmingham
314sell my house quickly granthamhttps://sell.unitedhomeoffer.com/Source link F314
315sell my house quickly sheffield
316sell my house quickly london
317sell my house quickly stockton
318sell my house quickly bracknell
319sell my house quick for cash
320sell my house rightmove
321sell my house rent it back
322sell my house reviews
323sell my house realtor
324sell my house redfin
325sell my house rent to own
326sell my house rochester ny
327sell my house remax
328sell my house scotland
329sell my house solicitor
330sell my house stuff
331sell my house san antonio
332sell my house show
333sell my house sacramento
334sell my house scottsdale
335sell my house san diego
336sell my house to my limited company
337sell my house to the council
338sell my house to buy another
339sell my house to a property developer
340sell my house then rent it back
341sell my house today
342sell my house to rent back
343sell my house to my son
344sell my house uk
345sell my house utah
346sell my house usa
347sell my home uk
348sell my ugly house
349sell my ugly house fast
350sell my house fast uk
351sell my house online uk
352sell my house valuation
353sell my house value
354sell my house virginia
355sell my house via auction
356sell my house without estate agent
357sell my house with strike
358sell my house without an agent
359sell my house quickly
360sell my house with a tenant
361sell my house quickly birmingham
362sell my house quickly grantham
363sell my house quickly sheffield
364sell your house yourself
365sell your house yourself on rightmove
366sell your house yourself website
367sell your house yourself online
368sell your house yourself paperwork
369sell your house before you buy
370can i sell my house a year after buying it
371can i sell my house after 2 years
372sell my house zoopla
373sell my house zillow
374sell your house zillow
375sell my house through zillow
376sell your house to zillow reviews
377sell my property on zillow
378make me sell my house zillow
379sell my property on zoopla
380sell my house fast
381sell my house quickly
382sell my house online
383sell my house fast for cash
384sell my house uk
385sell my house privately
386sell my house and rent it back
387sell my house for cash
388sell my house on zoopla
389sell my house online uk
390sell my house for free
391sell my house rightmove
392sell my house myself
393sell my house estate agents
394sell my house quickly birmingham
Historical Google autocomplete for where to sell my house online, including property-online and free variants.
Original image anchored at C66. Suggestions: where to sell my house online; where to sell your property online; where can i sell my house online; where can i sell my house online for free; how to sell my house online for free. No volume or ranking claim is established by this image.
Sheet15

Open original tab

This source tab is empty.

Sheet11

Open original tab

Sheet11
RowABCDEFGHIJKLMN
1https://freedomhomebuyer.com/arizona/we-buy-houses/?gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0Q3EasJyREr8653MaXS4R4vJ5ojuyHuFXocZgXG4YUQ6UQpfWyyIwaAlnxEALw_wcBSource link A1https://freedomhomebuyer.com/Source link H1
2KeywordCurrencyAvg. monthly searchesCompetitionCompetition (indexed value)Top of page bid (low range)Top of page bid (high range)KeywordCurrencyAvg. monthly searchesCompetitionCompetition (indexed value)Top of page bid (low range)Top of page bid (high range)
3we buy any houseUSD500Medium6514.2857.78we buy houses for cashUSD5000Medium6317.2864.80
4we buy houses for cashUSD5000Medium6317.2864.80we buy housesUSD50000High6915.1955.92
5we buy housesUSD50000High6915.1955.92sell my house fast for cashUSD5000Medium5115.5368.25
6sell my house fast for cashUSD5000Medium5115.5368.25sell my house fastUSD5000Medium5717.0063.15
7sell my house fastUSD5000Medium5717.0063.15sell house fastUSD5000Medium4417.6061.17
8sell house fastUSD5000Medium4417.6061.17cash for housesUSD5000Medium3719.4174.75
9buy my houseUSD5000Medium4920.9779.72cash home buyersUSD5000Medium4517.2068.39
10companies that buy houses for cashUSD5000Medium5717.0571.28we buy homes for cashUSD5000High6917.0365.33
11we buy homes for cashUSD5000High6917.0365.33sell your house fastUSD5000Low3216.3262.11
12sell your house fastUSD5000Low3216.3262.11sell house for cashUSD5000Medium4019.5469.41
13sell home fastUSD5000Low2913.5361.57sell home fastUSD5000Low2913.5361.57
14cash for housesUSD5000Medium3719.4174.75zillow phoenixUSD50000Low280.108.03
15selling propertyUSD500Medium568.3430.97sell my house for cashUSD5000Medium5320.2170.05
16sell my houseUSD5000High7220.5071.84houses for sale in phoenixUSD5000Medium430.681.84
17we buy homesUSD5000High6916.8661.95arizona real estateUSD50000Medium340.211.50
18sell house quicklyUSD500Low3219.5782.50we buy homesUSD5000High6916.8661.95
19cash home buyersUSD5000Medium4517.2068.39house buyersUSD5000Medium641.627.26
20buy houses for cashUSD5000Medium459.2350.47zillow phoenix azUSD5000Low200.085.30
21sell my home fastUSD5000Medium4024.1282.50buy houses for cashUSD5000Medium459.2350.47
22sell my homeUSD5000Medium5721.9878.58cash offer on houseUSD5000High8317.2767.80
23sell house for cashUSD5000Medium4019.5469.41houses in phoenixUSD50000Low241.1710.84
24we buy houses fastUSD500Low2216.1954.88companies that buy houses for cashUSD5000Medium5717.0571.28
25sell my house for cashUSD5000Medium5320.2170.05phoenix real estateUSD5000Low320.421.71
26sell your home fastUSD500Medium3821.7886.89cash for my houseUSD500Low2820.6065.66
27sell my house quicklyUSD500Low2820.0074.29cash house buyersUSD500Medium6415.8272.00
28buy homes for cashUSD5000Medium5513.2766.58sell my home fastUSD5000Medium4024.1282.50
29sell my house as isUSD500Medium4917.4058.01sell my house fast phoenixUSD500Medium4310.8051.84
30cash house buyersUSD500Medium6415.8272.00homes for sale in phoenix azUSD50000Medium360.561.67
31sell my house fast phoenixUSD500Medium4310.8051.84phoenix homes for saleUSD5000Medium400.621.79
32buy my house fastUSD500Low2917.8664.27houses for sale in phoenix azUSD50000Medium390.611.71
33sell my propertyUSD500Medium3816.6150.27houses for sale arizonaUSD50000Medium440.261.33
34selling a homeUSD5000Medium5812.0048.81we buy houses fastUSD500Low2216.1954.88
35sell my home for cashUSD500Medium5025.6798.57sell your home fastUSD500Medium3821.7886.89
36buying and selling housesUSD500Medium465.0028.07sell my home for cashUSD500Medium5025.6798.57
37we buy your houseUSD500Low1517.3166.49buying a house without a realtorUSD5000Low171.088.00
38buying a house in arizonaUSD500Medium530.783.98houses in phoenix arizonaUSD5000Low300.611.58
39sell your house for cashUSD500Low618.1064.96homes in phoenix azUSD5000Medium360.591.57
40buy my house for cashUSD500Medium5821.8084.33buy homes for cashUSD5000Medium5513.2766.58
41i buy houses cashUSD500Medium4517.9066.64we buy houses for cash near meUSD500Medium5513.9956.61
42sell home for cashUSD500Medium5721.3781.22selling propertyUSD500Medium568.3430.97
43we buy any propertyUSD50Medium5511.5932.23sell home for cashUSD500Medium5721.3781.22
44we buy houses phoenixUSD500Medium3913.9058.48sell house fast for cashUSD500Medium3419.3460.00
45sell house fast for cashUSD500Medium3419.3460.00buy my house fastUSD500Low2917.8664.27
46selling house as isUSD5000High769.2845.88selling a house without a realtorUSD5000High804.9728.10
47buy your house for cashUSD500High6722.2284.50fast home buyersUSD500Medium6325.7071.99
48fast home buyersUSD500Medium6325.7071.99buy my house nowUSD500Medium5921.9280.50
49selling a house to a cash buyerUSD500High719.0053.43selling a house to a cash buyerUSD500High719.0053.43
50sell fastUSD500Medium427.4519.91cash buyersUSD500Medium658.0129.85
51sell your house fast for cashUSD500Low920.3960.30new homes phoenixUSD5000Medium580.752.00
52buy and sell propertyUSD500Medium422.8517.80property buyersUSD5000Low280.975.47
53selling and buying a homeUSD500Medium464.0325.35cash for homesUSD5000Medium6519.3377.50
54buy my home for cashUSD500High7728.54116.13phoenix az real estateUSD5000Medium370.531.80
55we buy houses any conditionUSD500Medium3814.6757.92we buy your houseUSD500Low1517.3166.49
56sell housesUSD5000Medium659.2947.62buying a house in arizonaUSD500Medium530.783.98
57people that sell housesUSD500Low136.5622.08zillow cash offerUSD500High698.9932.62
58we pay cash for housesUSD500High7214.8065.08sell your house for cashUSD500Low618.1064.96
59we buy houses as isUSD500Medium5117.1477.15buy my house for cashUSD500Medium5821.8084.33
60companies that buy your houseUSD500High6724.7891.74cash buyers for housesUSD500High9120.0777.41
61we buy your homeUSD50Medium4725.2971.92i buy houses cashUSD500Medium4517.9066.64
62sell my home fast for cashUSD500Low3124.2890.29we buy houses phoenixUSD500Medium3913.9058.48
63sell your house quicklyUSD500Low2323.8483.25sell house quicklyUSD500Low3219.5782.50
64buy houses as isUSD5000Medium525.7933.18house in arizonaUSD50000Low240.161.02
65sell property quicklyUSD50Low1016.1350.37cash for your houseUSD500Low2315.5361.38
66sell my house fast phoenix azUSD500Medium4214.5652.50we buy houses reviewsUSD500High819.7341.40
67we buy propertyUSD500Medium519.3829.98sell your house yourselfUSD500High747.9531.49
68sell house fast phoenixUSD500Low2615.3569.43buy your house for cashUSD500High6722.2284.50
69company that buys housesUSD5000Medium6220.0075.90cash offer for my houseUSD500High7031.52104.12
70sell your property fastUSD500Low1016.5258.45arizona real estate for saleUSD500Medium550.231.28
71we buy houses fast for cashUSD500Medium3816.6862.39fast cash offerUSD500High7615.0050.45
72sell my home quicklyUSD500Low1430.1979.90we buy houses near meUSD500High6810.3047.88
73we buy property for cashUSD50High7212.2145.54sell your house fast for cashUSD500Low920.3960.30
74we buy any house any conditionUSD50Medium3812.8848.79quick sale houseUSD500Low2915.8769.60
75companies that buy homes for cashUSD500Low2717.4281.00we buy houses for cash reviewsUSD500Medium6211.6548.08
76buy your home for cashUSD50High8430.8490.90cash home buyers near meUSD500Medium5019.0567.67
77cash housesUSD500Medium447.9244.34buying a house with cash processUSD500Medium345.0022.00
78cost of buying and selling a houseUSD500Low334.3219.73selling your home without a realtorUSD500High908.1333.86
79sell home as isUSD5000High7810.0151.82selling house feesUSD5000Medium444.5920.07
80selling your home as isUSD500High8113.1659.03buy my home for cashUSD500High7728.54116.13
81we will buy your houseUSD50High6918.2068.54sell my home fast for cashUSD500Low3124.2890.29
82sell my house fast arizonaUSD50Medium4214.2868.04we buy propertyUSD500Medium519.3829.98
83sell home fast for cashUSD500Low2524.14100.00cash buyers near meUSD500High738.0228.35
84we buy your house for cashUSD500Low2921.8278.00selling your house without a realtorUSD500High875.2332.08
85fast cash for houseUSD500Low1312.3752.50new homes in phoenix azUSD5000Medium600.601.60
86sell home quickUSD500Low2324.1889.50sell housesUSD5000Medium659.2947.62
87we buy houses phoenix azUSD50Low2114.0446.00realtors in phoenix azUSD5000High998.0025.00
88sell my house phoenixUSD500Low2216.2660.00sell my house fast phoenix azUSD500Medium4214.5652.50
89we buy homes fastUSD500Low3121.4163.94cash offer for homeUSD500High9023.9891.70
90cash buyer propertyUSD500Medium423.9022.69rental homes in phoenixUSD5000Medium550.302.19
91we sell housesUSD500Medium425.9228.29homes in phoenixUSD5000Low260.581.83
92buying a home in arizonaUSD500Medium581.035.41i want to sell my property fastUSD500Low1818.9965.18
93my quick home buyersUSD500High8011.2340.00i want to sell my house fastUSD500Low1716.3485.16
94cash property buyersUSD50Medium6311.7641.16sell house fast phoenixUSD500Low2615.3569.43
95i buy homes for cashUSD50High7926.6179.27sell my house fast glendaleUSD500Low1021.1365.98
96selling your house as isUSD500High6814.8060.00sell property fastUSD500Low1313.9350.69
97sell your home for cashUSD500Low3121.2993.56we buy houses glendaleUSD500Low1013.4250.00
98sell my property quicklyUSD50Low0homes for sale near phoenix azUSD500Medium440.581.70
99quick buy propertiesUSD50Medium4212.7740.00new houses for sale in phoenixUSD500High860.762.03
100buy house fastUSD500Low159.8757.04arizona propertyUSD5000Medium400.151.08
101sell your home quickUSD500Low1020.8475.62we pay cash for housesUSD500High7214.8065.08
102we buy for cashUSD50Medium6510.4126.00sell home fast for cashUSD500Low2524.14100.00
103buy to sell propertyUSD50Medium525.1917.13we buy houses as isUSD500Medium5117.1477.15
104we buy your home for cashUSD50Medium5336.00101.93companies that buy your houseUSD500High6724.7891.74
105house cashUSD50Medium466.2045.06new build homes phoenixUSD5000Medium660.852.07
106houses to buy in arizonaUSD50Medium540.481.60we buy your homeUSD50Medium4725.2971.92
107we buy any homesUSD50High9013.5951.49fast cash for houseUSD500Low1312.3752.50
108fast cash home buyersUSD500Low1917.1959.49home prices in arizonaUSD500Medium390.4211.04
109sell my property fastUSD50High7523.3273.31house rentals phoenixUSD50000Medium400.192.29
110buy my home fastUSD50Medium5928.57107.25sell house fast reviewsUSD500High9411.2648.12
111buy houses fastUSD50Medium3913.7242.44new homes for sale in phoenix azUSD500Medium540.671.77
112sell your home azUSD50Low813.0560.00zillow homes for sale phoenixUSD500Low240.491.94
113companies that buy houses in any conditionUSD500Low1112.7046.00cash house buyer reviewsUSD50High7415.0150.00
114we will buy your homeUSD50Medium3911.7737.54sell my house phoenixUSD500Low2216.2660.00
115we buy and sell housesUSD500Low511.8153.55buying a house with cash without a realtorUSD500Low294.7929.89
116sell your home fast for cashUSD50Medium3431.9994.24phoenix home pricesUSD500Low331.7022.20
117sell my property for cashUSD50High8916.1250.71phoenix estate agentsUSD50Low0
118we buy houses companiesUSD50Medium3612.6851.75buying a house in usaUSD500Medium441.336.63
119house fastUSD50Medium515.1323.93company that buys housesUSD5000Medium6220.0075.90
120companies that buy houses as isUSD50High6914.6158.28sell my house without a realtorUSD500High8910.0446.73
121buy homes fastUSD50Low2811.5056.45sell my house quickUSD500Low2820.0074.29
122sell property for cashUSD50Medium6210.9351.53my quick home buyersUSD500High8011.2340.00
123buy my house as isUSD50High7918.8060.15new builds in phoenixUSD500Medium470.852.29
124we buy properties fastUSD50Medium6210.5443.23we buy houses fast for cashUSD500Medium3816.6862.39
125buy sell houseUSD500Medium546.7933.59we buy property for cashUSD50High7212.2145.54
126homes to buy in arizonaUSD50Medium610.522.11cash property buyersUSD50Medium6311.7641.16
127we buy your propertyUSD50Medium4014.8636.02buy your home for cashUSD50High8430.8490.90
128sell your house fast phoenixUSD50Low9cash housesUSD500Medium447.9244.34
129we buy homes any conditionUSD50Medium4410.5847.89selling a house costsUSD5000Medium475.6320.00
130sell house fast arizonaUSD50Low913.9528.07process of selling a house for cashUSD500Medium515.2337.83
131sell my phoenix house fastUSD50Low0cash offer for my homeUSD500High8839.02126.65
132companies that buy your house for cashUSD500Low1117.7068.25cash offer on house processUSD500Medium635.2933.43
133buy house in phoenixUSD500Medium411.3814.84sale my house fastUSD500Low2834.70107.25
134if i sell my houseUSD50Medium3710.1235.00we will buy your houseUSD50High6918.2068.54
135buy my house quickUSD50Low2921.5055.92sell my house fast arizonaUSD50Medium4214.2868.04
136we buy and sell homesUSD50Medium3615.9238.69cash sale houseUSD500Medium5311.6660.24
137sell house fast companyUSD500Low1buy house phoenixUSD500Medium411.3814.84
138selling property as isUSD500High734.5025.00real estate sellingUSD5000Medium435.0017.79
139we pay cash for homesUSD50Medium3924.4678.00houses for sale near phoenix azUSD500Medium410.681.76
140sell your property for cashUSD50High67we buy your house for cashUSD500Low2921.8278.00
141sell house quick for cashUSD50Medium3417.3374.81buy houses as isUSD5000Medium525.7933.18
142companies that pay cash for housesUSD50High7822.0375.37we buy houses phoenix azUSD50Low2114.0446.00
143az home buyersUSD50Medium4810.0044.44homes for cashUSD500Medium5418.7075.00
144sell my home as isUSD500High6925.7283.09fast cash home buyersUSD500Low1917.1959.49
145companies that buy houses quicklyUSD50Low1117.8754.06phoenix real estate for saleUSD500Medium440.551.51
146selling a house to buy a houseUSD50Medium551.4920.12we buy homes fastUSD500Low3121.4163.94
147we sell houses fastUSD50Low2222.0065.11cash buyer propertyUSD500Medium423.9022.69
148companies that will buy your homeUSD50Low2113.1155.61we sell housesUSD500Medium425.9228.29
149sell my house quick for cashUSD50High7519.9584.09buying a home in arizonaUSD500Medium581.035.41
150get cash for my houseUSD50Low2344.31106.98phoenix area homes for saleUSD500Medium530.631.71
151quick cash home buyersUSD50High8612.2764.78sell homesUSD5000Medium637.0036.00
152sell my arizona house fastUSD50Low0new homes for sale in phoenixUSD500High730.752.19
153sell home as is fastUSD50High9541.38113.92we buy homes in usaUSD500High8518.7745.99
154phoenix home buyersUSD50Low3012.4450.60companies that buy homes for cashUSD500Low2717.4281.00
155sell property fast for cashUSD50Low29i buy homes for cashUSD50High7926.6179.27
156will buy your houseUSD50High6912.3365.00we buy homes for cash near meUSD500High9615.7061.46
157cash home buyers phoenixUSD50Medium5118.7378.00sell your home for cashUSD500Low3121.2993.56
158we buy houses mesa azUSD50Low14real estate cash buyersUSD500High678.0032.78
159we buy houses in phoenixUSD50Low3016.0260.00property cash buyers reviewsUSD50High7111.4317.90
160sell my house fast in phoenixUSD50Low2716.2666.50cash for your homeUSD500Medium4617.3174.11
161we buy homes as isUSD50Medium6513.6180.10companies that buy houses for cash near meUSD500High7114.1160.80
162i sell my houseUSD50Medium5813.5255.92zillow homes for sale phoenix azUSD500Low240.541.94
163we buy houses in arizonaUSD500Medium5114.4261.20buy house fastUSD500Low159.8757.04
164selling house as is conditionUSD50High728.5835.13sell my property for cashUSD50High8916.1250.71
165buy any homeUSD50Medium33selling house cash offerUSD500Medium3718.6770.22
166sell quicklyUSD50Medium396.3424.82new builds in arizonaUSD500Medium440.551.59
167buy houses in any conditionUSD50Medium4313.0948.66we buy your home for cashUSD50Medium5336.00101.93
168houses are selling fastUSD50Medium656.5246.57sell my house todayUSD50Low2722.0165.77
169buy my property for cashUSD50High8620.46116.83cash for houses reviewsUSD50High7113.3435.00
170buy my house fast for cashUSD50Medium6316.36117.30houses to buy in phoenixUSD50Medium571.002.78
171cash for houses phoenixUSD50Low6we buy houses utahUSD50Medium3414.8592.81
172i will buy your houseUSD50Medium5211.1056.10rental homes in phoenix azUSD5000Medium460.251.85
173we buy houses quicklyUSD50Low3023.9560.00companies that will buy your houseUSD500High6920.2785.91
174sell house fast phoenix azUSD50Low0phoenix home buyersUSD50Low3012.4450.60
175cash buyers azUSD50High8213.6535.61selling your home as isUSD500High8113.1659.03
176buying and selling your homeUSD50High777.4530.00selling my propertyUSD500Medium3816.6150.27
177buy house fast cashUSD50Medium6025.0084.17making a cash offer on a houseUSD500Medium596.4938.06
178fast home sellingUSD50Low2143.90151.07homes arizonaUSD5000Low260.151.00
179people selling housesUSD50Medium613.6314.63house cashUSD50Medium466.2045.06
180buy home in phoenixUSD500Medium351.3110.44houses to buy in arizonaUSD50Medium540.481.60
181we buy your property for cashUSD50Medium48housing prices in arizonaUSD500Medium450.253.53
182sell my house in phoenixUSD50Low8want to sell my house fastUSD50Low1021.97108.23
183buying property in arizonaUSD50Medium510.353.45phoenix area real estateUSD500Medium440.592.64
184sell my house fast mesaUSD50Low2325.0096.00zillow phoenix areaUSD500Low290.177.96
185quick buy homesUSD50High9016.5955.21buy houses for cash near meUSD50High8315.0077.46
186we buy houses inUSD50High1009.6228.23sell my property fastUSD50High7523.3273.31
187sell home fast phoenixUSD50Low31house rentals phoenix azUSD5000Medium340.221.69
188we buy houses mesaUSD50Low7sell your house fast phoenixUSD50Low9
189buy sell homeUSD500Medium636.9625.19buy my home fastUSD50Medium5928.57107.25
190we buy any house fastUSD50Medium3523.5555.00sell house fast arizonaUSD50Low913.9528.07
191buy homes quickUSD50High6713.1530.47sale your house fastUSD500Low1621.8894.33
192we sell any houseUSD50Low0buy houses fastUSD50Medium3913.7242.44
193to sell my houseUSD50High9528.0074.75sell my house fast utahUSD50Medium4336.2093.75
194sell my home fast phoenixUSD50Low20sell house yourselfUSD500Medium657.3032.20
195buy a house fastUSD50Medium433.0223.43we buy homes for cash reviewsUSD50High857.8340.00
196buy house quickUSD500Low218.9853.54we will buy your homeUSD50Medium3911.7737.54
197selling for houseUSD5000Medium530.753.79phoenix housing pricesUSD500Low240.9413.16
198freedom homebuyerUSD500Medium596.2824.79get a cash offer for my houseUSD50High8730.00132.61
199fast property sellUSD50Unknownhouse of phoenixUSD50Low4
200sell your home phoenixUSD50Low12we buy and sell housesUSD500Low511.8153.55
201quick home sellUSD50Low1313.5359.89sell your home fast for cashUSD50Medium3431.9994.24
202we buy properties cashUSD50Medium50sell your house quickUSD500Low2323.8483.25
203we will buy your house for cashUSD50High7025.24110.99cash buyers for houses near meUSD50High8715.3155.00
204sell your house fast phoenix azUSD50Low0rental realtors phoenixUSD500Medium581.545.27
205cash for home buyersUSD50High8421.9387.12sell your property for cashUSD50High67
206buy my house in phoenixUSD50Low0sell house quick for cashUSD50Medium3417.3374.81
207companies that buy houses fastUSD50Medium3635.0885.07house fastUSD50Medium515.1323.93
208we buy your house fastUSD50Low3315.0048.34companies that buy houses as isUSD50High6914.6158.28
209buy my property fastUSD50Low0zillow homes for sale in arizonaUSD5000Low170.181.78
210we buy homes phoenixUSD50Low1430.65118.98buy homes fastUSD50Low2811.5056.45
211selling property fastUSD500Low1313.9350.69sell property for cashUSD50Medium6210.9351.53
212sell your house phoenixUSD50Unknowncash for propertyUSD50High718.8634.45
213sell your house in phoenixUSD50Low2houses bought for cashUSD50Medium3714.6342.20
214we buy any house for cashUSD50Unknownbuy home in phoenixUSD500Medium351.3110.44
215houses for cash buyersUSD500High9120.0777.41wholesale real estate arizonaUSD500High671.965.50
216buy my house as is for cashUSD50High8639.54114.14buy my house as isUSD50High7918.8060.15
217sell your house quick for cashUSD50High6940.65100.00fast cash buyersUSD50High9411.7041.93
218we buy homes arizonaUSD50Medium5212.1360.00fast cash for homesUSD50Low3213.3750.00
219sell my home fast in mesaUSD50Low3zillow phoenix az rentalsUSD500Low190.051.01
220sell your home fast phoenixUSD50Unknownwe buy properties fastUSD50Medium6210.5443.23
221sell your house in phoenix azUSD50Low0houses on sellUSD5000Medium530.753.79
222cash fast house sellUSD50Low31homes to buy in arizonaUSD50Medium610.522.11
223we sell your houseUSD50High7523.0078.00we buy your propertyUSD50Medium4014.8636.02
224company that will buy your houseUSD500High6920.2785.91buy a home without a realtorUSD5000Low332.508.56
225buy property fastUSD50Medium50cash purchase houseUSD50Medium618.0645.00
226cost to sell my houseUSD50High736.0531.40us home buyersUSD500Medium595.7130.41
227we sell houses fast for cashUSD50Medium6519.5276.32we buy homes reviewsUSD50Medium4710.4540.00
228we buy houses forUSD50High100buying a house cash offerUSD50Medium517.8739.98
229companies that buy homes in arizonaUSD50High67sell my house quick for cashUSD50High7519.9584.09
230fast sell propertyUSD50Low7selling your house on your ownUSD500High718.0035.55
231get cash for your houseUSD50Medium4924.06100.00i want to sell my house for cashUSD50High7236.0095.28
232pay cash for housesUSD5000Medium489.5946.90quick cash home buyersUSD50High8612.2764.78
233sell home quickly for cashUSD50High8020.5396.19sell home as is fastUSD50High9541.38113.92
234buying a house and selling yoursUSD50Medium511.0120.18sell my phoenix house fastUSD50Low0
235selling your house as is conditionUSD50High977.4646.65sell my house for cash nowUSD50Low1324.0267.03
236buying property to sellUSD50High100quick cash for houseUSD50Medium5736.5577.81
237sell house fast mesa azUSD50Low2cash house buyers near meUSD50Medium6015.4855.44
238sell my house fast inUSD50Low2sell property fast for cashUSD50Low29
239cash for houses fastUSD50Medium50companies that buy your house for cashUSD500Low1117.7068.25
240fast property buyersUSD50High849.6937.50we buy homes near meUSD50Medium3816.5853.92
241sell property quickly for cashUSD50High9621.0349.31cash home buyers phoenixUSD50Medium5118.7378.00
242we buy any house quicklyUSD50High86cash homesUSD500Medium667.7939.57
243i buy houses quicklyUSD50High100sell my house fast in phoenixUSD50Low2716.2666.50
244sell fast houseUSD50High9730.0083.14home cash buyers near meUSD50High8314.3050.00
245buy fast sell fastUSD50Medium43buy my house quickUSD50Low2921.5055.92
246we buy phoenix housesUSD50Low0we buy and sell homesUSD50Medium3615.9238.69
247buy a house in phoenix azUSD500Low311.2610.52best time to buy a house in arizonaUSD50Low160.282.91
248selling my house to a cash buyerUSD50Medium6417.6690.53sell house fast companyUSD500Low1
249sell your arizona homeUSD50Medium4611.2227.12new builds phoenix azUSD500Medium370.781.99
250the home buyersUSD50High675.9632.37we pay cash for homesUSD50Medium3924.4678.00
251cash fast houseUSD50Unknownwe buy houses companiesUSD50Medium3612.6851.75
252sell homes fast cashUSD50Medium5910.1345.32rental houses in arizonaUSD50000Low300.101.25
253we buy a houseUSD50Medium615.0029.73instant cash offer for houseUSD50High9024.29110.47
254selling your house to a companyUSD50High9815.8347.36sale house fastUSD500Low717.1275.53
255cash for houses companiesUSD50High100sell my property quickUSD50Low0
256selling your house to a cash buyerUSD50High9311.7145.00cash for houses phoenixUSD50Low6
257selling home as is conditionUSD50High778.5045.20buy my house fast for cashUSD50Medium6316.36117.30
258selling home to cash buyerUSD50High7213.0465.35best area to buy a house in arizonaUSD50Low311.142.86
259quick sell house fastUSD50Low0sell house fast phoenix azUSD50Low0
260to sell my house quicklyUSD50Medium457.2842.28cash buyers azUSD50High8213.6535.61
261i sell my homeUSD50Medium639.6248.00places that buy houses for cashUSD50High9418.5185.85
262houses for in arizonaUSD50000Low240.161.02sell your house fast reviewsUSD50High957.9138.76
263if i sell my homeUSD50Medium347.8542.48buying property in arizonaUSD50Medium510.353.45
264buy my house phoenixUSD50Low13buying a home in utahUSD500Medium631.4025.54
265company that sells housesUSD500High776.6536.26az home buyersUSD50Medium4810.0044.44
266buying & selling a homeUSD50Low29get cash offer for houseUSD50High9825.00116.34
267pay cash for homesUSD500Medium618.7051.80sell your home fast reviewsUSD50Medium37
268if paying cash for a houseUSD50Medium475.0032.82companies that buy houses for cash reviewsUSD50Low1114.2255.68
269buying a house to sellUSD50Medium6010.7230.77cash offer for your homeUSD50High8832.15104.53
270houses that we can buyUSD50High753.1810.61companies that buy houses quicklyUSD50Low1117.8754.06
271houses for to buyUSD5000Medium641.627.26best we buy houses companyUSD50Medium4510.7646.89
272buy my property quicklyUSD50Unknownbest place to buy a house in arizonaUSD50Low251.334.39
273i sell my propertyUSD50Medium64phoenix rental propertiesUSD500Medium650.551.83
274we sell houses fastUSD50Low2222.0065.11
275homes in mesaUSD500Low290.591.39
276new build homes in arizonaUSD5000Medium360.662.00
277get cash for my houseUSD50Low2344.31106.98
278sell my arizona house fastUSD50Low0
279cash purchase of homeUSD50High777.3145.00
280houses for sale in phoenix areaUSD500Medium550.581.70
281houses for sale near me phoenix azUSD50Medium470.901.97
282we buy houses in utahUSD50Medium5212.1871.54
283sell my house in phoenixUSD50Low8
284fast property saleUSD50High726.5833.96
285house prices in phoenix arizonaUSD500Medium510.524.00
286will buy your houseUSD50High6912.3365.00
287i want to sell my home fastUSD50Medium3414.3292.93
288homes for sale near phoenixUSD50Medium500.581.47
289fast cash house buyersUSD50Medium6025.0084.17
290we buy houses in phoenixUSD50Low3016.0260.00
291we buy homes as isUSD50Medium6513.6180.10
292cash house for saleUSD500High751.5216.37
293new houses for sale in phoenix azUSD50High680.541.89
294sell my house for cash near meUSD50High9012.0054.43
295we buy houses in arizonaUSD500Medium5114.4261.20
296best way to sell a house fastUSD50Low1413.7861.00
297cash house reviewsUSD50Unknown
298sale house for cashUSD50High8415.1068.75
299houses to buy in phoenix arizonaUSD50Medium570.922.46
300sell my house fast for cash near meUSD50High7815.6350.31
301sell my house fast near meUSD50Medium4915.0261.80
302places that buy homes for cashUSD50High9822.0098.66
303houses are selling fastUSD50Medium656.5246.57
304buy a house fastUSD50Medium433.0223.43
305new homes near phoenix azUSD50High740.661.62
306new homes for sale in azUSD500Medium650.441.48
307real estate cash buyers near meUSD50High817.5532.70
308new houses in phoenixUSD500Medium510.751.77
309selling a house on your ownUSD500High877.1834.42
310we buy houses usaUSD50High9414.0973.61
311best cash home buyersUSD50High7912.7876.14
312sale my house for cashUSD50Low1730.1188.34
313buy my property for cashUSD50High8620.46116.83
314best time to sell a house in phoenixUSD50Medium3813.6365.45
315sell my house fast reviewsUSD50Medium3613.8742.00
316buy a house in phoenix azUSD500Low311.2610.52
317new houses for sale in arizonaUSD500High690.321.40
318companies that pay cash for housesUSD50High7822.0375.37
319sell your house fast phoenix azUSD50Low0
320i will buy your houseUSD50Medium5211.1056.10
321cash for home buyersUSD50High8421.9387.12
322we buy houses quicklyUSD50Low3023.9560.00
323buy my house in phoenixUSD50Low0
324zillow houses for sale phoenixUSD50Low260.611.85
325buying real estate with cashUSD50Low316.2416.50
326real estate companies that will buy your houseUSD50Medium5535.0465.86
327finding cash buyersUSD50Medium597.0725.86
328selling home feesUSD500Medium425.7518.30
329rental properties in phoenix arizonaUSD500High680.491.66
330we buy homes phoenixUSD50Low1430.65118.98
331sell my house phoenix azUSD50Low1310.8764.03
332sell your house phoenixUSD50Unknown
333sell your house in phoenixUSD50Low2
334sell your house yourself websiteUSD50High8612.0051.89
335sell house phoenixUSD50Low191.4175.47
336buy my home for cash nowUSD50Low19
337i want to sale my house fastUSD50Low2924.9460.57
338buy my house as is for cashUSD50High8639.54114.14
339we buy houses logoUSD500Low1512.5069.19
340we buy houses websiteUSD50High6812.9550.00
341we buy houses nowUSD50High6814.2085.80
342sell my home fast in mesaUSD50Low3
343want to sell my property fastUSD50High67
344selling a home costsUSD5000Medium447.3820.49
345new homes phoenix areaUSD500High700.772.04
346best cash house buyersUSD50Medium4816.34124.47
347cash offer for your houseUSD50Medium5842.57140.00
348quick sell propertyUSD50Low1016.1350.37
349sell house for cash companiesUSD50Low6
350we buy cashUSD50Medium6510.4126.00
351we buy your property for cashUSD50Medium48
352mesa realtorsUSD500Medium668.0025.00
353sell my house fast mesaUSD50Low2325.0096.00
354quick house sale for cashUSD50Low1945.00163.24
355we buy houses cash near meUSD50Medium6115.6272.69
356new build homes phoenix azUSD500Medium350.782.10
357we buy houses inUSD50High1009.6228.23
358we buy houses mesa azUSD50Low14
359sell home fast phoenixUSD50Low31
360best places to buy a house in arizonaUSD50Low270.523.30
361sale my home fastUSD50Medium3738.00107.89
362houses for sale near phoenixUSD50Medium510.561.45
363homes for cash saleUSD500High832.3729.97
364we buy utah housesUSD50Low20
365quick home buyers reviewsUSD50High8110.6722.00
366property in phoenix arizonaUSD500Low320.621.71
367buy homes for cash near meUSD50High9418.2757.37
368quick home cashUSD50High808.3438.10
369sell my home fast phoenixUSD50Low20
370fast property buyersUSD50High849.6937.50
371sale my house quicklyUSD50Medium3512.7580.95
372buy house quickUSD500Low218.9853.54
373i want sell my house quicklyUSD50Low2921.10101.45
374sell my home phoenixUSD50High8050.1393.51
375selling houses as isUSD5000High769.2845.88
376new houses in phoenix azUSD50High780.541.51
377we buy houses glendale azUSD50Low6
378phoenix zillow rentalsUSD5000Low250.051.22
379sell my house arizonaUSD50Low308.8341.00
380sell my house for cash todayUSD50Low630.0056.34
381homes near phoenix azUSD50Medium490.541.53
382we buy houses for saleUSD50High833.7019.08
383cash buy houses for saleUSD50High824.0625.62
384fast property sellUSD50Unknown
385sell your home phoenixUSD50Low12
386selling homes phoenixUSD50Low3
387fast cash for my houseUSD50High71
388we buy properties cashUSD50Medium50
389buy my house phoenixUSD50Low13
390fast sale houseUSD500Low2516.5772.75
391want to sell house fastUSD50Medium646.7539.24
392selling your home on your ownUSD50High878.1325.05
393best time to buy a house in phoenixUSD50Low9
394sell home cash offerUSD50High8919.71100.00
395arizona phoenix zillowUSD50Low180.122.00
396we buy your house fastUSD50Low3315.0048.34
397buy houses cash near meUSD50High9313.7638.41
398selling a house in phoenixUSD50Low6
399real estate prices in arizonaUSD50Low310.305.96
400zillow instant offerUSD500Medium629.4131.65
401best time to sell a house in arizonaUSD50Medium6111.6846.81
402cash buyers for homes near meUSD50High1009.2141.29
403buy my property fastUSD50Low0
404freedom home buyers reviewsUSD50Medium613.6915.93
405cash for houses fastUSD50Medium50
406selling a house in arizonaUSD50Medium4014.9178.00
407sell property quickly for cashUSD50High9621.0349.31
408houses for sale in arizona zillowUSD50Low160.241.68
409sell house quick nowUSD50Unknown
410buying a home in phoenix azUSD500Medium521.165.11
411zillow for arizonaUSD50Medium350.162.00
412best areas in phoenix to buy a homeUSD50Low191.462.34
413sell now cash offerUSD50Medium6411.6932.75
414sell house fast utahUSD50Low6
415homes for sale in phoenix az areaUSD50Medium470.591.52
416selling my home as isUSD500High6925.7283.09
417purchase housesUSD500Medium562.5018.20
418cash for your propertyUSD50Medium358.6524.02
419the house phoenixUSD50Low0
420cash home buyers reviewsUSD50Medium3610.3568.24
421arizona zillow phoenixUSD50Low26
422zillow offers phoenixUSD50Low1510.5128.19
423sell your house quick for cashUSD50High6940.65100.00
424selling your house processUSD50High699.1635.00
425selling my house to a cash buyerUSD50Medium6417.6690.53
426we buy homes arizonaUSD50Medium5212.1360.00
427realtors that buy housesUSD50High8414.3660.74
428sell your house for cash reviewsUSD50High6935.0057.33
429sell your home fast phoenixUSD50Unknown
430new home in arizonaUSD5000Medium570.391.31
431sell your house in phoenix azUSD50Low0
432usa home buyersUSD500Medium603.4931.82
433cash fast house sellUSD50Low31
434sell us your houseUSD50Medium4921.3480.00
435phoenix real estate zillowUSD50Low300.103.50
436we sell houses fast for cashUSD50Medium6519.5276.32
437sell homes fast cashUSD50Medium5910.1345.32
438buying property as isUSD50Low314.0015.22
439cash for my house todayUSD50Medium50
440we buy houses mesaUSD50Low7
441we buy houses forUSD50High100
442buying a house with a realtorUSD500High734.5018.02
443we buy your house reviewsUSD50High878.9525.00
444companies that buy homes in arizonaUSD50High67
445selling your house to a cash buyerUSD50High9311.7145.00
IntegrityHomes

Open original tab

IntegrityHomes
RowABCDEFG
1ONLY THIS PAGE KEYWORDS
2https://integrityhomesus.com/?matchtype=b&network=g&device=c&adposition=&keyword=sell%20my%20house&ClickID=Cj0KCQjwhr2FBhDbARIsACjwLo0ulzlEPclV5QPzSwTrmPQGSUbtedGvWg_h3W253hIl0HO7RKrX2PIaAgUsEALw_wcB&gclid=Cj0KCQjwhr2FBhDbARIsACjwLo0ulzlEPclV5QPzSwTrmPQGSUbtedGvWg_h3W253hIl0HO7RKrX2PIaAgUsEALw_wcBSource link A2
3149
4KeywordCurrencyAvg. monthly searchesCompetitionCompetition (indexed value)Top of page bid (low range)Top of page bid (high range)
5we buy houses for cashUSD5000Medium6317.2864.80
6we buy housesUSD50000High6915.1955.92
7sell house fastUSD5000Medium4417.6061.17
8cash for housesUSD5000Medium3719.4174.75
9cash home buyersUSD5000Medium4517.2068.39
10cash offer on houseUSD5000High8317.2767.80
11sell your house fastUSD5000Low3216.3262.11
12sell house for cashUSD5000Medium4019.5469.41
13selling propertyUSD500Medium568.3430.97
14we buy homesUSD5000High6916.8661.95
15buy houses for cashUSD5000Medium459.2350.47
16cash house buyersUSD500Medium6415.8272.00
17cash buyersUSD500Medium658.0129.85
18we buy homes for cashUSD5000High6917.0365.33
19sell home fastUSD5000Low2913.5361.57
20sell your home fastUSD500Medium3821.7886.89
21cash buyers for housesUSD500High9120.0777.41
22sell home for cashUSD500Medium5721.3781.22
23sell house fast for cashUSD500Medium3419.3460.00
24we buy houses fastUSD500Low2216.1954.88
25selling a homeUSD5000Medium5812.0048.81
26fast cash offerUSD500High7615.0050.45
27cash for homesUSD5000Medium6519.3377.50
28buying and selling housesUSD500Medium465.0028.07
29we buy your houseUSD500Low1517.3166.49
30sell your house for cashUSD500Low618.1064.96
31buy homes for cashUSD5000Medium5513.2766.58
32i buy houses cashUSD500Medium4517.9066.64
33selling house as isUSD5000High769.2845.88
34buy your house for cashUSD500High6722.2284.50
35fast home buyersUSD500Medium6325.7071.99
36selling a house to a cash buyerUSD500High719.0053.43
37cash offers for homesUSD500High9023.9891.70
38house selling feesUSD5000Medium444.5920.07
39buy and sell propertyUSD500Medium422.8517.80
40selling and buying a homeUSD500Medium464.0325.35
41cash for your houseUSD500Low2315.5361.38
42sell housesUSD5000Medium659.2947.62
43sell your house fast for cashUSD500Low920.3960.30
44we pay cash for housesUSD500High7214.8065.08
45sell fastUSD500Medium427.4519.91
46we buy houses as isUSD500Medium5117.1477.15
47we buy your homeUSD50Medium4725.2971.92
48fast cash for houseUSD500Low1312.3752.50
49buy houses as isUSD5000Medium525.7933.18
50we buy propertyUSD500Medium519.3829.98
51sell your property fastUSD500Low1016.5258.45
52we buy houses fast for cashUSD500Medium3816.6862.39
53we buy property for cashUSD50High7212.2145.54
54cash property buyersUSD50Medium6311.7641.16
55buy your home for cashUSD50High8430.8490.90
56cash housesUSD500Medium447.9244.34
57sell home as isUSD5000High7810.0151.82
58selling your home as isUSD500High8113.1659.03
59making a cash offer on a houseUSD500Medium596.4938.06
60we will buy your houseUSD50High6918.2068.54
61sell home fast for cashUSD500Low2524.14100.00
62we buy your house for cashUSD500Low2921.8278.00
63fast cash home buyersUSD500Low1917.1959.49
64we buy homes fastUSD500Low3121.4163.94
65cash buyer propertyUSD500Medium423.9022.69
66we sell housesUSD500Medium425.9228.29
67selling your house as isUSD500High6814.8060.00
68sell your home for cashUSD500Low3121.2993.56
69cash for your homeUSD500Medium4617.3174.11
70buy house fastUSD500Low159.8757.04
71we buy for cashUSD50Medium6510.4126.00
72selling house cash offerUSD500Medium3718.6770.22
73we buy your home for cashUSD50Medium5336.00101.93
74buy sell propertyUSD50Medium525.1917.13
75sell property for cashUSD50Medium6210.9351.53
76house cashUSD50Medium466.2045.06
77selling property as isUSD500High734.5025.00
78buy houses fastUSD50Medium3913.7242.44
79i buy homes for cashUSD50High7926.6179.27
80we will buy your homeUSD50Medium3911.7737.54
81we buy and sell housesUSD500Low511.8153.55
82sell your home fast for cashUSD50Medium3431.9994.24
83sell your property for cashUSD50High67
84house fastUSD50Medium515.1323.93
85fast cash buyersUSD50High9411.7041.93
86we buy properties fastUSD50Medium6210.5443.23
87buy sell houseUSD500Medium546.7933.59
88we buy your propertyUSD50Medium4014.8636.02
89as is home buyersUSD500Medium646.4635.00
90buying a house cash offerUSD50Medium517.8739.98
91sell home as is fastUSD50High9541.38113.92
92sell property fast for cashUSD50Low29
93cash homesUSD500Medium667.7939.57
94we buy and sell homesUSD50Medium3615.9238.69
95finding cash buyersUSD50Medium597.0725.86
96we pay cash for homesUSD50Medium3924.4678.00
97buy homes fastUSD50Low2811.5056.45
98get cash offer for houseUSD50High9825.00116.34
99cash offer for your homeUSD50High8832.15104.53
100selling a house to buy a houseUSD50Medium551.4920.12
101we sell houses fastUSD50Low2222.0065.11
102offer to sell propertyUSD50Unknown
103will buy your houseUSD50High6912.3365.00
104fast cash house buyersUSD50Medium6025.0084.17
105houses are selling fastUSD50Medium656.5246.57
106buy a house fastUSD50Medium433.0223.43
107i will buy your houseUSD50Medium5211.1056.10
108cash for home buyersUSD50High8421.9387.12
109buying and selling your homeUSD50High777.4530.00
110cash offer for your houseUSD50Medium5842.57140.00
111we buy your property for cashUSD50Medium48
112we buy houses inUSD50High1009.6228.23
113we buy homes as isUSD50Medium6513.6180.10
114buy sell homeUSD500Medium636.9625.19
115fast property buyersUSD50High849.6937.50
116selling for houseUSD5000Medium530.753.79
117pay cash for housesUSD5000Medium489.5946.90
118fast property sellUSD50Unknown
119we buy properties cashUSD50Medium50
120we will buy your house for cashUSD50High7025.24110.99
121as is cash offer on houseUSD50High887.6137.50
122sell home cash offerUSD50High8919.71100.00
123we buy your house fastUSD50Low3315.0048.34
124cash for houses fastUSD50Medium50
125cash fast house sellUSD50Low31
126we sell your houseUSD50High7523.0078.00
127we sell houses fast for cashUSD50Medium6519.5276.32
128we buy houses forUSD50High100
129get cash for your houseUSD50Medium4924.06100.00
130fast home sellingUSD50Low2143.90151.07
131buying a house and selling yoursUSD50Medium511.0120.18
132cash offer for propertyUSD50High8911.5146.06
133selling property fastUSD500Low1313.9350.69
134buy fast sell fastUSD50Medium43
135the home buyersUSD50High675.9632.37
136cash fast houseUSD50Unknown
137sell homes fast cashUSD50Medium5910.1345.32
138we buy a houseUSD50Medium615.0029.73
139buy as is housesUSD5000Medium641.627.26
140selling your house to a cash buyerUSD50High9311.7145.00
141fast sell propertyUSD50Low7
142selling home to cash buyerUSD50High7213.0465.35
143buy property fastUSD50Medium50
144property home buyersUSD50High869.7740.28
145buying property to sellUSD50High100
146buying & selling a homeUSD50Low29
147pay cash for homesUSD500Medium618.7051.80
148sell fast houseUSD50High9730.0083.14
149buying a house to sellUSD50Medium6010.7230.77
150houses that we can buyUSD50High753.1810.61
OpenDoor

Open original tab

OpenDoor
RowABCDEFGHIJKLMN
1https://www.opendoor.com/Source link A1https://consumer.opendoor.com/seller-lead/Source link H1
2KeywordCurrencyAvg. monthly searchesCompetitionCompetition (indexed value)Top of page bid (low range)Top of page bid (high range)
3sell my houseUSD5000High7220.5071.84KeywordCurrencyAvg. monthly searchesCompetitionCompetition (indexed value)Top of page bid (low range)Top of page bid (high range)
4sell my house fastUSD5000Medium5717.0063.15opendoor property trustUSD500Medium469.3930.73
5sell my homeUSD5000Medium5721.9878.58opendoor brokerage incUSD50Medium435.8616.20
6sell your house fastUSD5000Low3216.3262.11opendoor property trust iUSD50Medium348.9928.43
7houses for sale in san diegoUSD50000Medium390.531.78opendoor seattleUSD50Medium346.0217.00
8opendoor homesUSD5000Medium667.4840.66opendoor quoteUSD5000Low56.5640.00
9sell house fastUSD5000Medium4417.6061.17open door offerUSD500High7713.2355.36
10houses for sale san antonioUSD50000Medium470.491.40opendoor chicagoUSD50Low306.9417.00
11homes for sale in san diegoUSD50000Medium370.421.78list with opendoorUSD50Medium609.7550.00
12sell your houseUSD5000Medium6515.0060.03opendoor buy my houseUSD50High8820.7169.36
13selling propertyUSD500Medium568.3430.97opendoor cash offerUSD50High8013.0650.00
14sell your homeUSD5000Medium6614.4756.05opendoor property trust 1USD50Low336.9122.25
15open door realtyUSD5000Medium537.9534.03opendoor startupUSD50Low3010.7921.95
16buy my houseUSD5000Medium4920.9779.72opendoor propertyUSD500Medium367.2821.06
17sell homeUSD5000Medium5812.0048.81opendoor contactUSD50High719.7630.70
18opendoor real estateUSD5000Medium617.9935.26open door home buyingUSD500High7610.8148.67
19cash home buyersUSD5000Medium4517.2068.39opendoor real estateUSD5000Medium617.9935.26
20house for sale inUSD5000Low131.132.62opendoor brokerageUSD500Medium566.7731.43
21sell your own homeUSD5000High747.4735.00open door arizonaUSD500Medium417.8534.80
22homes for sale san franciscoUSD50000Low310.653.40opendoor home salesUSD5000Medium547.1435.27
23companies that buy houses for cashUSD5000Medium5717.0571.28open door house buyingUSD500High709.3845.41
24homes for sale in san antonioUSD50000Medium410.461.52opendoor sell homeUSD500High8617.1960.00
25open homeUSD5000Low82.5523.24opendoor property c llcUSD50Medium358.1020.27
26sell my home fastUSD5000Medium4024.1282.50open door realtorUSD500High679.4144.70
27houses for sale san franciscoUSD5000Low330.673.40opendoor customer serviceUSD500Medium418.8823.56
28opendoor reviewsUSD5000High7410.6936.11open door labsUSD500Low1410.0031.48
29houses for sale in my areaUSD5000Medium540.552.72open door real estate companyUSD50High7510.8439.61
30sell house for cashUSD5000Medium4019.5469.41selling your home to opendoorUSD50High8928.5366.03
31sell house onlineUSD500High7315.0076.99open door realtyUSD5000Medium537.9534.03
32sell my house fast for cashUSD5000Medium5115.5368.25opendoor salesUSD50Medium599.5850.00
33homes for sale in san antonio texasUSD50000Medium400.461.20opendoor make offerUSD500Medium489.7934.67
34new homes for sale in las vegasUSD5000High770.621.72buying a house from opendoorUSD50Medium379.4624.22
35sell home fastUSD5000Low2913.5361.57opendoor homeUSD5000Medium667.4840.66
36property for saleUSD50000Medium510.343.04home offer nowUSD50High888.3018.46
37home for saleUSD500000Medium430.703.49opendoor companyUSD500Medium375.7525.84
38property for sale near meUSD50000Medium540.341.67open door phoenixUSD500Medium649.3050.00
39home for sale near meUSD500000Medium410.282.17instant house saleUSD50Medium6048.04102.50
40real estate for saleUSD50000Medium460.293.12opendoor san antonioUSD500High7710.4050.00
41houses for sale near my locationUSD5000Medium410.612.33instant home offerUSD50High6717.7676.24
42homes for sale near me nowUSD50000Medium440.392.11sell house instantlyUSD50High9729.19109.97
43sell my house for cashUSD5000Medium5320.2170.05instant offer on homeUSD50High9725.0098.58
44home saleUSD5000Medium401.167.00instant house offerUSD50High9224.3882.50
45las vegas homes for saleUSD50000Medium470.361.35online house buyersUSD500High682.5212.36
46home selling sitesUSD500High856.7027.44home buying serviceUSD500High8710.6662.80
47sell your home fastUSD500Medium3821.7886.89opendoor ibuyerUSD50Medium579.4825.83
48real estate for sale near meUSD50000Medium510.281.98opendoor property j llcUSD50Medium359.4624.66
49houses for sale in las vegasUSD50000Medium480.441.38quick buy homesUSD50High9016.5955.21
50house sold pricesUSD500Low231.238.99opendoor locationsUSD500Low176.3521.53
51sell property onlineUSD500High8311.0233.88opendoor houses for saleUSD500Medium465.0023.83
52house saleUSD5000000Medium420.412.53online home sellingUSD500High8216.8681.79
53selling houses australiaUSD50Low65.2911.56sell house appUSD500Medium554.0619.39
54houses for sale in los angelesUSD50000Low300.311.49open door texasUSD50Medium548.6843.21
55houses for sale in canadaUSD50000Low80.371.81opendoor listingUSD50Medium499.4635.95
56houses sold near meUSD5000Low220.947.70ibuyer opendoorUSD50Medium4312.5353.99
57realtor homes for saleUSD5000Low290.855.86instant cash offer for houseUSD50High9024.29110.47
58los angeles homes for saleUSD50000Low270.121.35opendoor trade inUSD50Medium439.8550.00
59condos for sale san diegoUSD5000Medium450.431.07sell house immediatelyUSD50Low2321.3656.07
60houses for sale in marylandUSD50000Medium380.201.50opendoor austinUSD500Medium6511.0550.00
61sell house quicklyUSD500Low3219.5782.50get an offer on my homeUSD50High9524.6672.81
62quick house saleUSD500Low2915.8769.60buys homesUSD50000Medium392.0515.00
63houses for sale ukUSD5000Low70.822.06buy with opendoorUSD50Medium6111.0245.91
64homes for sale in marylandUSD50000Medium370.161.62company that buys homesUSD500High6920.3786.29
65online estate agentsUSD50Medium483.429.20house buying serviceUSD50Medium5711.8674.61
66sell my house nowUSD500Medium3422.8992.07cash offer for your homeUSD50High8832.15104.53
67companies that buy housesUSD5000Medium6220.0075.90home selling appUSD500High756.1727.15
68condos for sale in los angelesUSD5000Medium380.302.00get cash offer for houseUSD50High9825.00116.34
69sell my propertyUSD500Medium3816.6150.27sell your home for cashUSD500Low3121.2993.56
70houses for sale charlotte ncUSD50000Medium390.521.32selling to opendoorUSD500High8416.5952.81
71homes sold near meUSD5000Low261.047.84selling houses onlineUSD500High7315.0076.99
72houses in texas for saleUSD50000Medium410.121.08sell your house directUSD50High9421.5058.23
73sellers marketUSD5000Low21.666.31get a cash offer for my houseUSD50High8730.00132.61
74homes for sale mnUSD50000Medium350.171.61sell my home for cashUSD500Medium5025.6798.57
75sold property pricesUSD50Low180.783.90company that buys housesUSD5000Medium6220.0075.90
76houses for sellUSD5000Medium530.753.79sell homes fastUSD5000Low2913.5361.57
77buy my homeUSD500High6820.8394.28sell your home fast for cashUSD50Medium3431.9994.24
78cash for my houseUSD500Low2820.6065.66sell home for cashUSD500Medium5721.3781.22
79sell your house yourselfUSD500High747.9531.49sell my house fast online quoteUSD500Medium4125.18106.26
80i want to sell my houseUSD500Medium6623.1276.25sell your house cashUSD500Low618.1064.96
81house sale pricesUSD500Medium360.938.89buy my home for cashUSD500High7728.54116.13
82homes for sale in raleigh ncUSD50000Medium370.461.25sell home fast for cashUSD500Low2524.14100.00
83homes for sale in phoenix azUSD50000Medium360.561.67guaranteed offer on your homeUSD50High8613.0043.32
84houses for sale in raleigh ncUSD50000Medium390.501.33cash offers for homesUSD500High9023.9891.70
85selling a houseUSD5000Medium659.2947.62sell my home fastUSD5000Medium4024.1282.50
86houses for sale mnUSD50000Medium380.231.59sell homesUSD5000Medium637.0036.00
87selling real estateUSD5000Medium435.0017.79sell your home as isUSD500High8113.1659.03
88houses sold in my areaUSD500Low251.037.70buy your home for cashUSD50High8430.8490.90
89property for sale ukUSD500Low40.611.97companies that get your home ready to sellUSD50High7910.1729.97
90open door appUSD500Medium356.2332.40sell condo for cashUSD50High8712.6233.96
91austin texas houses for saleUSD50000Medium420.551.45instant home buyersUSD50High9034.3296.51
92selling a house as isUSD5000High769.2845.88sell my house quickUSD500Low2820.0074.29
93houses for sale in phoenix azUSD50000Medium390.611.71opendoor orlandoUSD50Medium628.7129.14
94opening doorsUSD500000Medium4410.0449.87online home buyersUSD500Medium623.3824.12
95houses for sale njUSD50000Medium390.211.52opendoor sacramentoUSD500Low126.4516.20
96houses in florida for saleUSD50000Medium450.171.17quick sell homeUSD500Low2324.1889.50
97estates for saleUSD5000Medium390.552.08sell home as is fastUSD50High9541.38113.92
98sell home onlineUSD500High8216.8681.79get cash for my houseUSD50Low2344.31106.98
99houses for sale usaUSD5000Low220.583.00cash offer for my houseUSD500High7031.52104.12
100charlotte homes for saleUSD5000Medium380.421.25quick sell houseUSD500Low3219.5782.50
101cash for homesUSD5000Medium6519.3377.50guaranteed offer on homeUSD50High829.8582.50
102house selling websitesUSD500High683.3417.88opendoor jacksonvilleUSD50High7510.3232.45
103sell my house onlineUSD500Medium4618.6179.23quick sale of homeUSD500Medium6510.8453.34
104buying and selling housesUSD500Medium465.0028.07selling homesUSD5000Medium5812.0048.81
105sold housesUSD5000Low50.824.67sale your homeUSD50High9318.6366.74
106seattle houses for saleUSD5000Medium370.612.88sale my home fastUSD50Medium3738.00107.89
107sold propertiesUSD500Low70.593.21buy homes fastUSD50Low2811.5056.45
108condos for sale san franciscoUSD5000Medium601.884.42opendoor priceUSD50Low289.0432.40
109chicago condos for saleUSD5000Medium390.401.60sell my house fastUSD5000Medium5717.0063.15
110australia houses for saleUSD5000Low50.772.49real estate companies that buy homesUSD50High6913.5856.06
111cheap houses for sale in canadaUSD500Low170.682.15sell my house for cash near meUSD50High9012.0054.43
112property for sale in californiaUSD5000Medium410.131.10sale your home fastUSD50Low2223.8384.72
113opendoor brokerageUSD500Medium566.7731.43sell my house for cash nowUSD50Low1324.0267.03
114homes for sale in austin texasUSD50000Medium420.461.32sell houses for cashUSD5000Medium4019.5469.41
115buying and selling propertyUSD500Medium422.8517.80sale my house fastUSD500Low2834.70107.25
116need to sell my house fastUSD500Low2718.9975.27sell my condo for cashUSD50High8821.1662.80
117jacksonville homes for saleUSD5000Medium420.432.04sale my house for cashUSD50Low1730.1188.34
118sale house near meUSD5000000Medium380.362.21sell house quick for cashUSD50Medium3417.3374.81
119cost of selling a houseUSD5000Medium475.6320.00want to sell my homeUSD50Medium6531.1888.01
120raleigh homes for saleUSD5000Medium390.451.23opendoor agentsUSD50Medium599.7148.27
121jacksonville fl homes for saleUSD50000Medium430.451.98selling house cash offerUSD500Medium3718.6770.22
122realtor soldUSD5000Low271.845.40i want to sell my house for cashUSD50High7236.0095.28
123realtor houses for saleUSD5000Medium350.473.28sale house fastUSD500Low717.1275.53
124sell my home for cashUSD500Medium5025.6798.57looking to sell your homeUSD500Medium6221.4261.25
125ohio houses for saleUSD5000Medium350.171.24sell your house fast for cashUSD500Low920.3960.30
126homes for sellUSD5000Medium460.664.19sell houses fastUSD5000Medium4417.6061.17
127sell my house quicklyUSD500Low2820.0074.29opendoor ibuyer companiesUSD50Unknown
128sell your house onlineUSD500Medium4815.0164.09buy my house as is for cashUSD50High8639.54114.14
129seattle condos for saleUSD5000Medium430.624.00cash for homeUSD5000Medium6519.3377.50
130houses in california for saleUSD50000Medium370.121.27open door realty charlotte ncUSD50Medium5911.7529.52
131property for sale in texasUSD5000Medium530.110.75help selling my homeUSD50High9124.3878.75
132home for sale in floridaUSD50000Medium420.151.23sell my house as is for cashUSD5000Medium5320.2170.05
133selling and buying a homeUSD500Medium464.0325.35buy homes cashUSD5000Medium5513.2766.58
134florida real estate for saleUSD5000Medium530.141.19house quick saleUSD500Low2915.8769.60
135houses for sale in los angeles californiaUSD5000Low330.271.18cash for your houseUSD500Low2315.5361.38
136we buy your houseUSD500Low1517.3166.49buying from opendoorUSD500Medium5111.8147.88
137investment property for sale near meUSD500High741.014.10sell your own house websiteUSD50High765.1924.64
138cash for housesUSD5000Medium3719.4174.75sell house without listingUSD50High939.7930.65
139sell your house for cashUSD500Low618.1064.96sell real estate onlineUSD500Medium638.9721.90
140homes in texas for saleUSD50000Low320.101.08opendoor nashvilleUSD50Medium599.4640.00
141home to buyUSD50000Medium392.0515.00sell my house for cash todayUSD50Low630.0056.34
142homes for sale austin mnUSD5000Low200.070.28i want to sell my home fastUSD50Medium3414.3292.93
143we buy houses for cash near meUSD500Medium5513.9956.61let me sell your homeUSD50Low1812.9344.88
144on the market houses for saleUSD500Medium551.164.44cash offer for my homeUSD500High8839.02126.65
145selling your house without a realtorUSD500High875.2332.08opendoor housesUSD500Medium416.8833.16
146sell my house as isUSD500Medium4917.4058.01companies that get your house ready to sellUSD50High8314.3041.69
147real estate houses for saleUSD5000Medium551.133.50sell your own home sitesUSD50High10010.1126.85
148home for sale in njUSD50000Medium380.191.45i want to sale my house fastUSD50Low2924.9460.57
149homes sold in my areaUSD500Low211.219.71sell your home fastUSD500Medium3821.7886.89
150property for sale los angelesUSD500Medium400.331.61fast sale homesUSD50Low1422.8259.84
151cash house buyersUSD500Medium6415.8272.00companies that sell housesUSD500High776.6536.26
152homes for sale near my locationUSD500Medium460.602.76sell your house on your ownUSD500High718.0035.55
153sell my house fast phoenixUSD500Medium4310.8051.84sell house for cash fastUSD500Medium3419.3460.00
154new home for sale near meUSD50000Medium640.722.23sell my house for cash fastUSD5000Medium5115.5368.25
155houses for sell in my areaUSD500Medium580.714.00home buying companies near meUSD50High918.1839.62
156homes for sale in my areaUSD5000Medium580.612.79ready to sell your homeUSD500Medium4510.3138.45
157vegas homes for saleUSD5000Medium530.481.71need help selling my houseUSD50High8731.0093.02
158sell my house fast san antonioUSD500Low2520.9442.00sell your own houseUSD500High877.1834.42
159find houses for saleUSD5000Medium621.154.65quick house sale for cashUSD50Low1945.00163.24
160home sellingUSD5000Medium637.0036.00realtors that buy housesUSD50High8414.3660.74
161sell home for cashUSD500Medium5721.3781.22service to get house ready to sellUSD50Low299.7630.00
162property for sale in canadaUSD5000Low110.232.00sell your house fastUSD5000Low3216.3262.11
163real estate soldUSD500Low80.499.00sell your house online yourselfUSD50High8915.1956.48
164opendoor homes for saleUSD5000Medium547.1435.27easy home buyerUSD500High868.2242.28
165jacksonville houses for saleUSD5000Medium440.451.81need to sell my home fastUSD50Medium5025.6975.42
166house buyersUSD5000Medium641.627.26buying and selling homesUSD500Medium464.0325.35
167charlotte houses for saleUSD5000Medium420.421.11sale house for cashUSD50High8415.1068.75
168opendoor phoenixUSD500Medium649.3050.00want to sell your homeUSD50Medium4014.4162.68
169property for sale floridaUSD5000Medium560.151.11sell my house quick for cashUSD50High7519.9584.09
170homes for sale ukUSD5000Low40.742.63open door reviewsUSD5000High7410.6936.11
171house sale websitesUSD5000Medium440.824.21open door real estate reviewsUSD500High738.9232.12
172my house saleUSD50High7110.1382.50opendoor dallasUSD500Medium5815.3950.00
173cash offer on houseUSD5000High8317.2767.80selling your own homeUSD5000High747.4735.00
174houses for sell near meUSD5000Medium520.785.00sell my property for cashUSD50High8916.1250.71
175selling a house without a realtorUSD5000High804.9728.10online home sales websitesUSD50High853.7513.80
176sell my house fast austinUSD500Low2721.4244.00selling own homeUSD50High787.9435.00
177best way to sell your houseUSD500High9115.0049.94sell now cash offerUSD50Medium6411.6932.75
178houses in arizona for saleUSD50000Medium440.261.33sell my house fast for cash near meUSD50High7815.6350.31
179house selling sitesUSD500High683.1517.25selling to opendoor reviewsUSD50High7614.4545.47
180sale my houseUSD500Medium6626.3397.61buy my house cashUSD500Medium5821.8084.33
181houses for sale in vegasUSD5000Medium530.471.39companies that buy homes for cashUSD500Low2717.4281.00
182selling your home without a realtorUSD500High908.1333.86cash offers for housesUSD5000High8317.2767.80
183buy my house nowUSD500Medium5921.9280.50open door realty reviewsUSD50High759.4632.40
184find sold house pricesUSD50Low291.109.27cash home salesUSD50High8313.8457.18
185house for sale phoenixUSD5000Medium430.681.84companies that buy houses quicklyUSD50Low1117.8754.06
186properties sold near meUSD500Low270.835.31opendoor brokerage reviewsUSD50Medium649.6827.99
187cash offers for homesUSD500High9023.9891.70home buyers near meUSD5000Low215.7137.74
188home for sale charlotte ncUSD50000Medium350.441.27selling your house nowUSD500Low1817.2260.16
189opendoor companyUSD500Medium375.7525.84opendoor home valueUSD50High729.9151.58
190process of selling a houseUSD500Medium535.8232.53selling my own homeUSD500Medium5810.2246.12
191property for sale australiaUSD500Low80.813.43selling a home nowUSD50High9717.1045.00
192buy house onlineUSD500High682.5212.36open door jacksonville flUSD50High708.3028.94
193real estate homes for saleUSD5000Medium541.073.83buy homes for cash near meUSD50High9418.2757.37
194opendoor logoUSD500Low25.4313.17companies that buy homes as isUSD50High9620.7788.18
195sell your propertyUSD50Medium3810.3642.25open door realty listingsUSD50Medium493.6021.85
196sell your own houseUSD500High877.1834.42best home buying companiesUSD50High8513.7560.00
197sell my house fast for market valueUSD500Medium3914.0453.21help selling houseUSD50High9611.1548.14
198chicago house for saleUSD50000Medium370.331.56need to sell my house fast reviewsUSD50High7917.5361.00
199cheap houses for sale in chicagoUSD5000Medium500.441.93companies that purchase homesUSD50High8221.2892.40
200your home sold guaranteed realtyUSD500Low242.9415.00we buy your home for cashUSD50Medium5336.00101.93
201home buying companiesUSD500High6920.3786.29opendoor complaintsUSD50Medium658.9232.52
202raleigh houses for saleUSD5000Medium400.551.36cash home buyers near meUSD500Medium5019.0567.67
203austin house for saleUSD5000Medium430.591.74offerhomeUSD500Medium626.5935.00
204houses in atlanta for saleUSD50000Medium420.371.61easy offer home buyersUSD50High918.6932.83
205property for sale in arizonaUSD5000Medium520.130.98buys houses for cashUSD5000Medium459.2350.47
206quick sale homesUSD500Medium6510.8453.34buying from opendoor reviewsUSD50Medium5911.8143.73
207houses for sale by meUSD5000Medium380.241.82home buyers in my areaUSD50Medium5216.6751.83
208online house salesUSD500Medium571.1014.69homes for cashUSD500Medium5418.7075.00
209property selling sitesUSD50High967.7924.15places that buy homes for cashUSD50High9822.0098.66
210property for sale in ohioUSD5000Medium500.081.05we buy houses websitesUSD50High6812.9550.00
211property sale pricesUSD50Low311.006.45buy my property for cashUSD50High8620.46116.83
212buy my house for cashUSD500Medium5821.8084.33selling your home on your ownUSD50High878.1325.05
213buy homes for cashUSD5000Medium5513.2766.58best way to sell a homeUSD50High9614.4140.79
214sell your home onlineUSD500Medium6217.0069.37places that buy housesUSD50High7716.4350.79
215sell my house fast online quoteUSD500Medium4125.18106.26places that buy houses for cashUSD50High9418.5185.85
216help you sellUSD500Medium614.3113.27companies that buy houses near meUSD500High7410.1744.48
217sell my house fast los angelesUSD500Low3316.4052.50i want to sell my house as isUSD50Medium5818.2967.35
218sell my house fast houstonUSD500Medium3821.4276.89offerpad ibuyer companiesUSD50Unknown
219canada real estate for saleUSD5000Low160.081.75homes for cash saleUSD500High832.3729.97
220best way to sell a houseUSD500Medium6614.6342.82i buy homes for cashUSD50High7926.6179.27
221want to sell my houseUSD500High7920.8571.71selling my own houseUSD500High9210.9143.45
222sell my house myselfUSD500High869.2341.84open door feesUSD500High7510.0035.70
223house sales in my areaUSD500Medium541.216.38best home selling appsUSD50Medium595.6621.76
224open door homes for sale near meUSD500Medium523.7816.67house buyers near meUSD500High745.4540.45
225i sold my houseUSD500Medium416.0725.00pros and cons of opendoorUSD500High789.9135.00
226fast house saleUSD500Low2516.5772.75realtor that buys houses as isUSD50High8517.5755.00
227sell house fast for cashUSD500Medium3419.3460.00open door homes for sale near meUSD500Medium523.7816.67
228homes in canada for saleUSD5000Low60.141.80cash for homes near meUSD50High9517.0750.00
229house to sellUSD500Medium581.5311.00buy homes as isUSD500Medium646.4635.00
230new houses for sale in las vegasUSD500High740.571.48real estate buying and sellingUSD500Medium364.0417.14
231people that sell housesUSD500Low136.5622.08buy houses for cash near meUSD50High8315.0077.46
232home sales in my areaUSD500Medium391.267.70opendoor appUSD500Medium356.2332.40
233sell house without agentUSD500High876.3030.00sell homes as isUSD5000High7810.0151.82
234sell your home yourselfUSD500High869.0331.71companies that buy houses for cashUSD5000Medium5717.0571.28
235i need to sell my house fastUSD500Medium3724.6373.37quick cash for homesUSD50Medium5515.36104.25
236houses for sale near me rent to ownUSD500Medium590.533.21home cash buyers near meUSD50High8314.3050.00
237home for sellUSD500High670.814.52companies like open doorUSD500High8116.4269.76
238sell my house fast raleighUSD500Low2020.5748.19sell your house fast reviewsUSD50High957.9138.76
239buy houses for cashUSD5000Medium459.2350.47cash house buyers near meUSD50Medium6015.4855.44
240sell my own homeUSD500Medium5810.2246.12zillow open doorUSD50Low297.0129.76
241cash for your houseUSD500Low2315.5361.38as is home buyers near meUSD50High9710.7250.00
242house selling appUSD500Medium554.0619.39opendoor commissionUSD50High689.4132.40
243sell my house cash san antonioUSD500Low1118.0050.25we buy your house cashUSD500Low2921.8278.00
244las vegas real estate for saleUSD500Medium560.501.80opendoor repair costsUSD50Medium579.4641.10
245realtor sold homesUSD5000Low72.7112.00home ibuyerUSD50High9211.4740.54
246cash home buyers in san antonioUSD500Low1526.2055.00selling properties onlineUSD500High8311.0233.88
247homes for sale websitesUSD5000Medium530.865.26companies that buy houses as isUSD50High6914.6158.28
248sell property fastUSD500Low1313.9350.69open door las vegasUSD500High739.3736.60
249realtor ct homes for saleUSD500Low250.141.48houses for cash saleUSD500Medium5311.6660.24
250homes for sale houston texasUSD50000Low310.351.38buy houses cash near meUSD50High9313.7638.41
251home for sale in arizonaUSD50000Medium410.211.44options for selling a houseUSD50High797.8941.17
252cash offer for my houseUSD500High7031.52104.12selling house to zillowUSD500High8511.4546.76
253arizona real estate for saleUSD500Medium550.231.28selling my home as isUSD500High6925.7283.09
254selling a house to a cash buyerUSD500High719.0053.43sell your home to zillowUSD500High9012.1442.40
255opendoor brokerage llcUSD500Medium418.7524.29open door listingsUSD500Medium549.3532.92
256fast cash offerUSD500High7615.0050.45selling your house to zillowUSD500High9011.0740.77
257house selling companiesUSD500High776.6536.26zillow will buy your houseUSD50High715.2325.96
258homes for sale in san diego californiaUSD5000Low330.181.55opendoor service feeUSD50Medium6610.4535.91
259as is home saleUSD500High683.5721.24house buyers in my areaUSD50High799.6450.00
260cash sale houseUSD500Medium5311.6660.24ibuyers in my areaUSD50High909.9838.08
261house buyers near meUSD500High745.4540.45quick sale property buyersUSD50Medium43
262sell your home yourself websitesUSD500High909.8132.00ibuyers websiteUSD50High875.7021.07
263sell fastUSD500Medium427.4519.91sell your house quickUSD500Low2323.8483.25
264sell my house online freeUSD500Medium6515.2562.99zillow will buy your homeUSD50High705.1520.43
265sell my home onlineUSD500High8820.1985.76people that buy housesUSD500Medium5818.1066.77
266i want to sell my house fastUSD500Low1716.3485.16ibuyers near meUSD50High986.8122.99
267house for sale appUSD5000Low281.465.24ways to sell your house fastUSD50Low710.5035.00
268buying a house before sellingUSD500Medium553.5533.39cash homesUSD500Medium667.7939.57
269home selling websitesUSD500High764.5420.38house for cashUSD5000Medium3719.4174.75
270sell house nowUSD500Low3113.3458.19zillow to buy my houseUSD50High764.6036.83
271real estate sales near meUSD500Medium380.715.36house investors near meUSD50High9211.6140.36
272online real estate companiesUSD500High754.0415.00investors that buy homesUSD500High7515.4161.33
273sold sign real estateUSD5000High1001.755.25open listings opendoorUSD50Medium406.6616.20
274home for sale in californiaUSD5000Low240.081.37sell my home to zillowUSD50High9319.7266.09
275www realtor com homes for saleUSD500Low270.764.62opendoor partner agentUSD50Medium599.4636.29
276cash home buyers near meUSD500Medium5019.0567.67selling your home and buying a new oneUSD50Medium494.5428.42
277sell house fast austinUSD50Low2221.6862.40buy my house zillowUSD50High9517.5875.19
278sell my house fast atlantaUSD500Medium4817.6048.08sell my house to zillowUSD500High9317.2454.65
279sell my own placeUSD50High100sell my house myself onlineUSD50High9014.4546.91
280property for sale usaUSD500Medium570.653.00home buyers for cashUSD5000Medium4517.2068.39
281getting your house ready to sellUSD500Medium424.6925.17zillow buy your houseUSD50High787.9731.06
282homes soldUSD5000Low60.756.29zillow cash for homesUSD50High8914.5141.24
283sell my house fast jacksonvilleUSD500Medium5418.8969.23selling a house to zillowUSD50High857.0332.62
284austin real estate for saleUSD500Medium590.561.38companies that buy houses for cash near meUSD500High7114.1160.80
285costs of selling a homeUSD5000Medium447.3820.49selling a home to zillowUSD50High7910.7637.27
286las vegas condo for saleUSD50000Medium560.381.00zillow buy my homeUSD50Medium4716.7445.32
287ready to sellUSD500Low156.2026.06tips to sell your homeUSD5000Medium574.0622.29
288getting house ready to sellUSD500Medium504.7220.55zillow buy your homeUSD50Medium655.9323.89
289quick sale propertyUSD50Low197.8924.60we buy homes for cash near meUSD500High9615.7061.46
290house selling pricesUSD50Medium603.5917.92get your home ready to sellUSD500Medium605.7025.30
291sell home quicklyUSD500Low2324.1889.50selling home to zillowUSD500High8712.6847.92
292cost of selling a house ukUSD50Medium374.6212.00best cash home buyersUSD50High7912.7876.14
293las vegas property for saleUSD500Medium540.592.11we buy houses nowUSD50High6814.2085.80
294homes in atlanta for saleUSD50000Medium390.351.80zillow buy my houseUSD5000High749.9140.78
295selling a home without a realtorUSD5000High857.5030.93ibuyers for homesUSD50High9510.1829.51
296companies that buy houses near meUSD500High7410.1744.48selling to zillowUSD500Medium676.0825.53
297home offerUSD500Medium626.5935.00easy home buyer reviewsUSD50High774.4320.00
298opendoor canadaUSD50Low122.0036.94fastest way to sell a houseUSD500Medium5817.8973.68
299websites to buy housesUSD5000Medium521.5911.23zillow buys homesUSD500Medium606.2823.24
300australia real estate for saleUSD500Low130.502.63we sell houses fastUSD50Low2222.0065.11
301houses in houston for saleUSD50000Medium460.501.74cash for houses near meUSD500High8614.5857.31
302homes for sell near meUSD500Medium550.785.07best way to sell a house quicklyUSD50Low2313.2365.00
303buying and selling real estateUSD500Medium364.0417.14we buy houses for cash near meUSD500Medium5513.9956.61
304property for sale san diegoUSD500Medium510.461.76home buying startupUSD50Medium423.7417.77
305property for sale in phoenixUSD500Medium580.561.45selling home and buying new homeUSD50High705.9630.15
306buy my house todayUSD500Low1820.2863.00best ways to sell a houseUSD500Medium6614.6342.82
307sell my home fast for cashUSD500Low3124.2890.29quick cash home buyersUSD50High8612.2764.78
308selling a help to buy propertyUSD50Low29opendoor agent commissionUSD50High699.1025.22
309we sell housesUSD500Medium425.9228.29zillow selling homesUSD500High746.9131.20
310home listings for saleUSD5000Medium601.085.74sell your home charlotteUSD50Low1831.86111.80
311instant offerUSD500Medium625.2823.13sell your house las vegasUSD50Medium64
312cheap las vegas homes for saleUSD500Medium630.511.73zillow house offerUSD50High697.7433.03
313sell my house without a realtorUSD500High8910.0446.73zillow buysUSD500Low280.417.13
314fast home sale companyUSD500Low128.0830.00opendoor zillowUSD50Low236.7626.48
315sell my house fast san diegoUSD500Medium5819.4945.00real estate ibuyersUSD50High705.4215.55
316home investors near meUSD500High8513.2149.98instant buyer real estateUSD50High1007.9161.11
317property for sale san franciscoUSD500Medium400.513.06zillow home offerUSD500High819.0740.34
318house sale sitesUSD500Medium500.834.42offerpad real estateUSD50Medium509.1938.68
319home for sale in michiganUSD50000Low330.161.20zillow buys housesUSD500High675.7732.45
320home for sale signUSD5000High1001.104.38zillow i buyerUSD50Medium425.2918.89
321home selling appsUSD500High756.1727.15selling with zillowUSD500Medium573.9320.31
322buy your house for cashUSD500High6722.2284.50selling your home to investorsUSD500Low3317.0849.53
323sell your house for freeUSD50High8118.0158.09selling your home yourselfUSD500High869.0331.71
324opendoor las vegasUSD500High739.3736.60buying a house and selling yoursUSD50Medium511.0120.18
325sell my house fast seattleUSD500Low2711.3336.71opendoor houstonUSD500Medium6213.9744.24
326real estate sold pricesUSD50Low140.776.26opendoor tampaUSD50Medium6310.9337.86
327online property saleUSD50High711.6715.00fast cash for homesUSD50Low3213.3750.00
328cost of buying and selling a houseUSD500Low334.3219.73ibuyers real estateUSD500High716.0222.36
329buy your houseUSD500Low1910.3744.60quick cash offer reviewsUSD50High856.9623.25
330cheap house for sale in ukUSD50Low120.782.98zillow home buying programUSD50Medium382.5611.55
331best quick house sale companiesUSD50Low1017.9456.14cash housesUSD500Medium447.9244.34
332sell my property onlineUSD50High8719.9748.14selling my home and buying a new oneUSD50High719.2743.12
333sell my house fast floridaUSD500Low3314.7848.75zillow guaranteed offerUSD50High778.6745.24
334sell home as isUSD5000High7810.0151.82easiest way to sell a houseUSD50High8415.0060.00
335i need to sell my houseUSD500High7226.1479.77real estate sellingUSD5000Medium435.0017.79
336san diego real estate for saleUSD500Medium480.441.39buy houses fastUSD50Medium3913.7242.44
337need to sell my houseUSD500Medium3823.1674.19home selling sitesUSD500High856.7027.44
338house for sale signsUSD5000High1000.894.20zillow sell your homeUSD500High829.8637.43
339sell real estate onlineUSD500Medium638.9721.90sell own houseUSD5000High804.8625.86
340sell my placeUSD50High8938.6058.39time to sell your homeUSD50Medium458.5429.48
341sold sign houseUSD5000High1001.686.00ibuyerUSD5000Medium516.1923.60
342home buyers near meUSD5000Low215.7137.74home investors near meUSD500High8513.2149.98
343i want to sell my homeUSD500High6922.9776.59deciding whether to sell your houseUSD50Low169.3226.22
344online home salesUSD500High842.7523.60sell your home raleighUSD50Low8
345sell house fast houstonUSD500Low3320.5992.40cash for home buyersUSD50High8421.9387.12
346selling as isUSD500Medium464.0320.21selling and buying a new homeUSD50High687.7435.00
347home selling processUSD500Medium477.4135.00buy house fast cashUSD50Medium6025.0084.17
348making an offer on a house before selling yoursUSD50Medium664.8425.00selling a house in austinUSD50Low1725.5760.63
349houses for sale rent to ownUSD500High680.502.98online real estate companyUSD500High754.0415.00
350i want to sell my property fastUSD500Low1818.9965.18cheapest way to sell my houseUSD50High9615.1661.63
351sell my own houseUSD500High9210.9143.45house buyers for cashUSD500Medium6415.8272.00
352making an offer on a house without an agentUSD500Low270.9611.90fast cash home buyersUSD500Low1917.1959.49
353open door near meUSD500Low276.1620.19sell my house las vegas nvUSD50Low0
354sell your house fast for cashUSD500Low920.3960.30selling your house and buying a new oneUSD50Medium574.9735.00
355fast home saleUSD500Low2914.6664.63we buy houses for saleUSD50High833.7019.08
356houses for sale and rent near meUSD500Medium440.582.10quick cash for houseUSD50Medium5736.5577.81
357opendoor atlantaUSD500Medium369.3244.91i buy homesUSD500High7410.8235.28
358open door property managementUSD500Low140.8313.80zillow home purchaseUSD500Medium583.6622.16
359property for sale near me nowUSD50Medium550.642.07buy houses as isUSD5000Medium525.7933.18
360looking for house for saleUSD5000High691.164.38selling your home processUSD50High698.0732.50
361sell my home quicklyUSD500Low1430.1979.90i want to sell my property fastUSD500Low1818.9965.18
362property selling appUSD50Medium57we pay cash for homesUSD50Medium3924.4678.00
363cost of selling a house with a realtorUSD500Medium667.2323.93cash buyer real estateUSD500High678.0032.78
364sell my house houstonUSD500Medium3816.5465.70open door san franciscoUSD500Low910.0020.00
365property selling websitesUSD50High735.1322.70sell my property fastUSD50High7523.3273.31
366i want to sell my propertyUSD50High8020.7550.00selling your home and buying anotherUSD50Low7
367cash offer for my homeUSD500High8839.02126.65sell your house yourselfUSD500High747.9531.49
368home for sale usaUSD5000Low160.193.00selling houses as isUSD5000High769.2845.88
369austin home for saleUSD5000Medium440.531.73we buy properties fastUSD50Medium6210.5443.23
370house sale processUSD50Low294.8118.00open door competitorsUSD500High7013.3353.71
371home selling companiesUSD500Medium523.2017.01house buying and sellingUSD500Medium465.0028.07
372buy home onlineUSD500Medium623.3824.12buying a house cash offerUSD50Medium517.8739.98
373selling your home as isUSD500High8113.1659.03we buy homes cashUSD5000High6917.0365.33
374houses for sale near me for rentUSD500Low320.711.90sell house zillowUSD500High715.1230.00
375new house saleUSD50000Medium550.642.20fast cash buyersUSD50High9411.7041.93
376help to buy selling houseUSD50High100fast home buyersUSD500Medium6325.7071.99
377sale my house fastUSD500Low2834.70107.25we buy cash housesUSD5000Medium6317.2864.80
378home for sale in chicagoUSD50000Low300.221.62we buy houses cash fastUSD500Medium3816.6862.39
379sell your property onlineUSD50High67opendoor charlotte ncUSD50Medium548.9936.14
380find houses for sale near meUSD500Medium570.833.87zillow purchase homeUSD500High723.2818.57
381we pay cash for housesUSD500High7214.8065.08we buy properties for cashUSD50High7212.2145.54
382opendoor property trustUSD500Medium469.3930.73zillow house purchaseUSD50High733.7212.00
383sell my house fast las vegasUSD500Medium4020.0050.00selling my propertyUSD500Medium3816.6150.27
384selling help to buy propertyUSD50Unknownzillow make an offerUSD50High685.7632.76
385condos for sale in texasUSD500Low330.100.68process of selling your houseUSD50High699.1635.00
386houses for sale help to buyUSD50Medium54selling a home in austinUSD50Low5
387cheap houses for sale in san diegoUSD500Medium530.651.62investors that buy housesUSD500Medium3812.3056.88
388open door house buyingUSD500High709.3845.41tips for selling your home fastUSD500Medium635.9331.08
389looking to sell your homeUSD500Medium6221.4261.25buy my condoUSD50High8818.1135.59
390sell my house fast ukUSD50Low0selling a house to a cash buyerUSD500High719.0053.43
391open door home buyersUSD500High7610.8148.67zillow buying homesUSD5000Medium483.8817.82
392sell home fast for cashUSD500Low2524.14100.00tips on selling a homeUSD5000Medium354.9019.88
393house for sale houston texasUSD50000Medium370.371.25zillow purchaseUSD50Medium452.2214.80
394rented property for saleUSD50Medium390.752.07steps to sell my homeUSD50Medium656.4025.22
395realtor homes for sale near meUSD500Medium390.905.32house for cash buyersUSD500High9120.0777.41
396investment houses for saleUSD500High771.044.21we buy homes fastUSD500Low3121.4163.94
397open door houseUSD500Medium416.8833.16ibuyer chicagoUSD50High888.7519.31
398companies that buy your houseUSD500High6724.7891.74best cash for homes companiesUSD50Medium3827.0568.07
399we buy your homeUSD50Medium4725.2971.92we buys housesUSD50000High6915.1955.92
400opendoor startupUSD50Low3010.7921.95process of selling a house for cashUSD500Medium515.2337.83
401house property for saleUSD500Medium520.511.97quick home buyers reviewsUSD50High8110.6722.00
402buy my home for cashUSD500High7728.54116.13we pay cash for housesUSD500High7214.8065.08
403sell my house fast njUSD500Medium438.9435.52people selling housesUSD50Medium613.6314.63
404sell your house quicklyUSD500Low2323.8483.25sell your own propertyUSD50High774.2528.00
405homes for sale appUSD500Medium351.596.49selling home in austinUSD50Low617.8456.10
406opendoor usaUSD5000Low213.1711.83best tips for selling your homeUSD50Medium665.5321.63
407on the house com sold pricesUSD50Medium36selling and buying propertyUSD500Medium422.8517.80
408opendoor houses for saleUSD500Medium465.0023.83easy home buyers reviewsUSD50High835.0126.57
409opendoor san antonioUSD500High7710.4050.00buying selling housesUSD500Medium546.7933.59
410home for sale in phoenixUSD5000Medium400.621.79companies that pay cash for housesUSD50High7822.0375.37
411help to buy houses for sale near meUSD50Unknownzillow house buyingUSD500Medium512.5613.16
412best houses for saleUSD500Medium580.672.95ibuyer companiesUSD500High767.2627.92
413real estate for sale signUSD5000High1001.519.47sale homeUSD500000Medium430.703.49
414austin new homes for saleUSD500High691.002.30zillow instant offerUSD500Medium629.4131.65
415property for sale michiganUSD5000Medium510.090.88buy houses any conditionUSD50Medium4313.0948.66
416opendoor propertiesUSD500Medium367.2821.06we buy homes near meUSD50Medium3816.5853.92
417quick property saleUSD500Low198.9526.14house buyers reviewsUSD50High698.8220.92
418sell house fast reviewsUSD500High9411.2648.12selling homes austinUSD50Low741.4059.23
419us property for saleUSD50Medium370.422.72sell my house in floridaUSD50Medium4210.6235.19
420sell your home servicesUSD500High8212.0040.26guaranteed offer real estateUSD50High698.4029.75
421opendoor houstonUSD500Medium6213.9744.24zillow sell my houseUSD500High8312.9747.07
422real estate agents in my areaUSD500High945.5715.59tips on selling a houseUSD500Medium533.5818.86
423open door realtorUSD500High679.4144.70zillow ibuyUSD50Low143.6016.26
424houses for sale in my locationUSD500Medium450.783.37opendoor phone numberUSD500Low268.6432.44
425houses for sale and rentUSD500Medium430.702.14zillow cashUSD50Medium503.5815.89
426house sale prices ukUSD50Low9we buy houses fastUSD500Low2216.1954.88
427houses for sale in usUSD50Low260.633.48opendoor tucsonUSD500High6910.5243.93
428i sold my house but i want it backUSD50Medium3610.0035.00selling your house and buying anotherUSD50High7210.0038.21
429place for sale near meUSD5000Medium500.362.00sell your home in las vegasUSD50Unknown
430selling your house as isUSD500High6814.8060.00cash for homes reviewsUSD50High885.7028.75
431houses in michigan for saleUSD50000Medium350.181.17we buy houses any conditionUSD500Medium3814.6757.92
432sell your house nowUSD500Low1817.2260.16home selling websitesUSD500High764.5420.38
433your home sold guaranteedUSD500Medium345.7420.00selling your house to investorsUSD500Low2313.8956.25
434sell property quicklyUSD50Low1016.1350.37zillow cash offerUSD500High698.9932.62
435sell my house fast chicagoUSD500Medium5511.0630.00cheapest way to sell a houseUSD500High9713.6536.70
436sell house fast san diegoUSD500Low2111.2633.78companies similar to opendoorUSD50High7818.3762.64
437cash house buyer reviewsUSD50High7415.0150.00cash home buyers reviewsUSD50Medium3610.3568.24
438estate property for saleUSD500Medium410.692.58selling a home processUSD500Medium477.4135.00
439opendoor blogUSD500Low76.0923.16ways to sell a house quicklyUSD50High7610.5738.06
440opendoor customer serviceUSD500Medium418.8823.56ibuyer zillowUSD500Medium485.9220.97
441house sold as isUSD500Medium413.6025.47process in selling a houseUSD500Medium535.8232.53
442property for sale in ncUSD5000Medium550.100.95sell your home tucsonUSD50Low0
443opendoor offersUSD500High7713.2355.36cheapest way to sell your homeUSD50High9715.0043.25
444property sale sitesUSD50Medium521.026.07getting ready to sell your houseUSD500Medium424.6925.17
445buying a house while selling a houseUSD500Medium391.0316.79need a house fastUSD50High967.2136.77
446cash for your homeUSD500Medium4617.3174.11putting a house on the marketUSD50Medium488.0032.42
447sale for house near meUSD500Medium650.803.04companies that buy houses for cash reviewsUSD50Low1114.2255.68
448the property selling companyUSD50Unknownibuyers reviewsUSD500High775.3320.71
449sale my homeUSD500High7426.98107.66ibuyer platformsUSD50Medium664.4910.50
450property sale websitesUSD50Medium431.177.95timeline for selling and buying a houseUSD50Medium382.9515.00
451sell my house fast phoenix azUSD500Medium4214.5652.50we buy condosUSD50Low318.8649.63
452properties sold in my areaUSD50Medium390.874.45we buy homesUSD5000High6916.8661.95
453houses for sale in florida usaUSD50Medium520.251.28process of selling and buying a house at the same timeUSD50Low14
454i want to sale my houseUSD50High8532.9078.12zillow home buying processUSD50Low264.5816.60
455need to sell house fastUSD500Low925.0073.02selling house buying anotherUSD500Low327.5629.54
456home sale sitesUSD500Medium500.965.82best we buy houses companyUSD50Medium4510.7646.89
457buy your homeUSD500Medium6424.5176.85sell my house orlandoUSD50Low1729.0581.98
458ready house for saleUSD50High1000.983.94best cash house buyersUSD50Medium4816.34124.47
459sell house fast phoenixUSD500Low2615.3569.43selling a home in denverUSD50Low1522.4654.13
460sell house fast los angelesUSD500Low2019.4265.00get home ready to sellUSD500Medium525.3824.72
461home sold pricesUSD500Low311.028.80selling my house and buying anotherUSD50High7910.0850.00
462process of selling and buying a houseUSD500Medium391.5320.25sell my house on my ownUSD50High7512.0046.58
463sell your property fastUSD500Low1016.5258.45we buy homes 4 cashUSD500High9112.6758.44
464sell my condoUSD500High8819.0348.02we buy homes for cash reviewsUSD50High857.8340.00
465sale your homeUSD50High9318.6366.74we buy houses companiesUSD50Medium3612.6851.75
466sell my house in las vegasUSD50Low9cash sale real estateUSD50Medium466.3627.84
467estate for sale near meUSD500000Low120.103.15things to do to sell your house fasterUSD50High916.7640.00
468houses cheap for saleUSD50000Medium580.532.00putting house on marketUSD50Medium616.9738.65
469realtor to sell my houseUSD500High9924.6768.96cash for houses reviewsUSD50High7113.3435.00
470companies that buy homes for cashUSD500Low2717.4281.00zillow ibuyerUSD500Medium416.2722.22
471sell house fast san antonioUSD500Medium4429.0146.09i buy houses cashUSD500Medium4517.9066.64
472home sale pricesUSD500Medium351.2010.40opendoor alternativesUSD50High8915.0067.27
473homes in houston for saleUSD50000Medium400.501.97tips for listing your homeUSD50Medium401.8712.00
474sell my house fast jacksonville flUSD500Medium3919.9567.61we buy homes any conditionUSD50Medium4410.5847.89
475buy sell propertyUSD50Medium525.1917.13home investorsUSD5000High7612.0048.64
476sell your own propertyUSD50High774.2528.00zillow offerUSD5000High676.9530.00
477cash for my homeUSD500Medium3418.61100.00best way to sell your home by ownerUSD50High797.8535.00
478cash houses for saleUSD500High751.5216.37step by step selling a houseUSD50Medium605.7523.00
479process of selling a house for cashUSD500Medium515.2337.83sell home to investorUSD500Medium5514.5349.37
480property selling pricesUSD50Medium352.4617.13selling your house on zillowUSD500High718.9736.00
481no houses for saleUSD500Low51.077.87sell home yourselfUSD500Medium658.4429.78
482will my house sellUSD50High798.5230.00offerpad homes for saleUSD500Medium565.2039.26
483house on sell near meUSD500Medium541.506.61we buy houses 4 cashUSD50High8010.2450.81
484best site for homes for saleUSD500Medium371.196.94zillow ibuyer companiesUSD50Unknown
485companies that will buy your houseUSD500High6920.2785.91cash offer real estateUSD500Medium456.1224.71
486cheap properties for sale in canadaUSD50Low4cheapest way to sell your houseUSD500High9612.9149.07
487best website for selling propertyUSD50High855.8223.26alternative ways to sell your houseUSD50High7911.8933.51
488property for sale houstonUSD500Medium570.542.06selling property as isUSD500High734.5025.00
489opendoor inspectionUSD50Medium457.5834.41
490selling home in houstonUSD50000Medium400.501.97
491selling a home and buying anotherUSD500Medium397.0932.77
492cash house buyers reviewsUSD50High7415.0150.00
493we buy houses as isUSD500Medium5117.1477.15
494we buy homes as isUSD50Medium6513.6180.10
495zillow sell my homeUSD500High7910.8643.53
496sell my condo fastUSD50Medium3525.4959.81
497best ibuyersUSD50High9211.8035.00
498opendoor homes phoenixUSD50Medium43
499sell my house austinUSD50Medium3520.0052.37
500buying a home while selling a homeUSD50Medium534.2028.49
501sell your property fastUSD500Low1016.5258.45
502cash real estateUSD50Medium403.5016.02
503selling home in charlotteUSD50Low2
504best way to sell your house by ownerUSD50High896.4630.00
505sell your house in dallasUSD50Low0
506zillow home offer reviewsUSD50High767.9535.32
507fair cash offerUSD50High699.1933.00
508sell my house las vegasUSD50Medium3618.1348.70
509selling a house yourselfUSD500Medium657.3032.20
510listing your house for saleUSD50Medium666.3535.62
511ibuying zillowUSD500Low301.779.94
512we buy houses usaUSD50High9414.0973.61
513tips before selling your homeUSD50Medium613.9917.42
514selling house to investorUSD500Medium6714.3746.53
515buying a house while selling yoursUSD50Low29
516quick ways to sell your houseUSD50Low1015.0096.21
517selling a house in portlandUSD50Low5
518tips to sell a house fastUSD50Medium484.3136.46
519sell my home myselfUSD500High8411.1446.82
520sell my house to an investorUSD50Medium4133.53101.48
521timeline of selling a houseUSD50Medium435.6217.02
522buying and selling home at same timeUSD500Medium613.5027.12
523sell your house in san antonioUSD50Low1
524zillow buying housesUSD5000Medium431.3212.19
525quick cash offerUSD50High8910.6643.47
526buy as is housesUSD5000Medium641.627.26
527we buy cheap housesUSD50High848.9441.55
528pros and cons of a cash offer on a houseUSD500Medium506.6234.01
529zillow ibuyer programUSD50Low94.4415.66
530we buy houses for cash investment group llcUSD50Medium589.8745.78
531selling a home without a realtorUSD5000High857.5030.93
532top tips to sell your homeUSD50High725.2122.31
533sell house to zillow reviewUSD500High8310.3032.38
534sell my house phoenix azUSD50Low1310.8764.03
535get my house ready to sellUSD50High796.4832.84
536selling my house myselfUSD500High869.2341.84
537best real estate to sell your houseUSD50High9917.9342.51
538sell house for cash pros and consUSD50High9115.3150.00
539sell my property to an investorUSD50High8613.6740.55
540selling your home without a realtorUSD500High908.1333.86
541selling a house in phoenixUSD50Low6
542top ibuyer companiesUSD500Medium488.0429.90
543sell my house texasUSD50Medium4916.6952.53
544selling your home to zillow reviewsUSD500High8110.3832.16
545tips to sell your house fastUSD50High695.0036.27
546buying a home while selling anotherUSD50Medium394.5515.00
547zillow ibuyingUSD500Low221.8011.95
548sell a house without a realtorUSD5000High804.9728.10
549all cash home buyersUSD50High7915.1259.12
550selling a house with a realtorUSD500High848.6637.79
551tips for selling your home 2020USD50High704.2716.50
552timeline for selling a houseUSD500Medium406.8226.56
553sell my house austin txUSD50Low1520.0361.36
554buying a house before you sell yoursUSD50Medium669.0445.62
555buy a house completely onlineUSD50Medium602.459.68
556sell my house in charlotteUSD50Low0
557we buy houses for cash reviewsUSD500Medium6211.6548.08
558selling one house and buying anotherUSD50Low1210.5535.00
559selling home before buying anotherUSD50Low304.6916.14
560real estate seller tipsUSD500Low251.7915.00
561sell my house njUSD50Medium4910.0033.75
562selling a house in houstonUSD50Low8
563we buy houses phone numberUSD50Medium5415.0163.51
564the investor group wants to buy my houseUSD50High100
565zillow cash offer reviewUSD500High818.4534.92
566list of ibuyersUSD50Medium655.2619.21
567to sell a propertyUSD50Low138.7136.54
568sell a property fastUSD500Low1313.9350.69
569we buy homes 4 cash reviewsUSD50High766.8136.66
570companies that buy houses reviewsUSD500High839.5038.07
571selling home to zillow reviewsUSD500High7810.9536.76
572sell my home orlandoUSD50High8820.6492.72
573sell your house san antonioUSD50Medium50
574sell house myselfUSD50High827.3137.18
575fast cash offersUSD500High7615.0050.45
576selling your house tipsUSD500Medium654.1421.34
577sell my house in atlantaUSD50Low1416.8545.00
578buying selling propertyUSD50Medium525.1917.13
579sell my house in denverUSD50Low10
580sell your house houstonUSD50High100
581sell my house in orlandoUSD50Low9
582selling to zillow reviewsUSD500Medium524.5620.64
583sell my house in portlandUSD50Low4
584the home selling processUSD50Medium476.6330.00
585sell my home las vegasUSD50High6822.54102.49
586fair property buyers reviewsUSD50High8411.4629.56
587get house ready to sellUSD500Medium504.7220.55
588sell my house charlotte ncUSD50Medium3813.73118.84
589online realtor companyUSD50High835.5215.00
590zillow buying homes reviewsUSD50Medium614.4717.67
591home sellers guideUSD500Medium575.9620.00
592we buy homes reviewsUSD50Medium4710.4540.00
593zillow offer reviewsUSD5000Medium637.2826.50
594buying a home before selling yoursUSD50Medium362.5724.08
595selling your house to zillow reviewsUSD50High8513.1535.00
596selling a home in san antonioUSD50Low0
597buying a house before selling yoursUSD500Medium350.9321.62
598selling property tipsUSD50Medium34
599selling a propertyUSD500Medium568.3430.97
600selling your house without a realtorUSD500High875.2332.08
601we buy houses adUSD500Low317.5239.43
602buying before selling houseUSD500Medium553.5533.39
603sell my house charlotteUSD50Low3011.6958.42
604seller tips for real estateUSD500Low312.1615.00
605making a cash offer on a houseUSD500Medium596.4938.06
606zillow buy my house reviewsUSD50High839.2840.08
607sell my home fast in san diegoUSD50Low0
608find an investor to buy my houseUSD50High6917.8366.88
609property buyersUSD5000Low280.975.47
610we buy houses reviewsUSD500High819.7341.40
611real estate quick saleUSD500Low277.5930.00
612sell my house fast new yorkUSD50High688.2534.24
613cash deal on houseUSD50High679.2760.00
614sell house fast njUSD50Medium418.0035.63
615want to sell my property fastUSD50High67
616sell my house fast njUSD500Medium438.9435.52
617tips on getting your house ready to sellUSD50Medium413.8222.34
618home investors reviewsUSD50High846.2519.97
619pricing a home to sellUSD50Medium455.1322.59
620sell house as is conditionUSD50High728.5835.13
621selling in a sellers marketUSD50Low273.1215.48
622zillow instant offers reviewsUSD50Medium588.6025.39
623ibuyer stockUSD50Low323.008.97
624all cash offersUSD500Low205.0817.18
625zillow reviews for sellersUSD50Medium422.7014.98
626buy my house las vegasUSD50Medium5641.2597.72
627sell your house dallasUSD50High6814.7252.75
628we buy homes in usaUSD500High8518.7745.99
629sell your house fast austinUSD50Low2820.0035.08
630sell your property for cashUSD50High67
631want to sell house fastUSD50Medium646.7539.24
632sell my house san diegoUSD50Low1712.6158.00
633selling your home to a builderUSD50High869.8835.52
634best way to sell a home by ownerUSD50High846.4928.00
635sell house fast orlando flUSD50Low0
636realtors to sell my houseUSD500High9924.6768.96
637builders will buy your homeUSD50High855.0725.12
638sell my house denver coUSD50Low9
639sell my house fast in new jerseyUSD50Medium36
640cash for homes njUSD50High707.6241.23
641selling a house in denverUSD50Low0
642process of selling a house by ownerUSD500Medium653.2318.87
643selling your home without an agentUSD50High978.8831.22
644sell property for cashUSD50Medium6210.9351.53
645sell my home fast in charlotteUSD50Low0
6467 showings no offersUSD50Low9
647tips for selling your home by ownerUSD50Medium662.4518.75
648we buy homes usaUSD50High868.5944.00
649best way to sell a house without a realtorUSD50High867.0435.00
650sell your house fast orlandoUSD50Low0
651sell my home atlantaUSD50High10031.6167.21
652cash home buyers san diegoUSD50Low1917.9580.58
653selling home in las vegasUSD50Low5
654stress selling houseUSD500Low286.0616.65
655sell my house fast californiaUSD50Low139.2361.59
656sell my house jacksonville flUSD50Medium5030.3276.14
657selling home as is by ownerUSD50High977.4039.00
658cash for homes seattleUSD50Low29
659home buyers reviewsUSD50High727.0630.84
660zillow ibuyer reviewsUSD50Medium604.4519.58
661houses are selling fastUSD50Medium656.5246.57
662selling a house in san antonioUSD50Low6
663process of selling propertyUSD50Medium383.3221.60
664steps to listing a house as a realtorUSD50Medium394.7411.40
665best way to sell a house by ownerUSD500High865.8129.12
666sell my house north carolinaUSD50Low2513.1749.86
667selling my house without a realtorUSD500High8910.0446.73
668house buyers usaUSD500Medium441.336.63
669selling house as is by ownerUSD50High956.5034.03
670cash buyers for houses near meUSD50High8715.3155.00
671zillow house buying reviewsUSD50High757.9529.74
672buy my house for cash californiaUSD50High9323.25122.81
673sell my house in san antonioUSD50Low7
674sell your house fast floridaUSD50Medium489.1376.93
675average number of showings to sell a house 2020USD500Medium393.9114.15
676home investors in my areaUSD50High7811.5050.35
677sell your house without an agentUSD50High7411.4535.00
678sell my house fast austin txUSD50Medium4014.6740.00
679buying home before sellingUSD500Medium483.1335.00
680selling my home without a realtorUSD500High9512.4051.94
681we buy homes californiaUSD50Low8
682homes are selling fastUSD50Medium4514.5162.99
683selling your property yourselfUSD50High894.9817.61
684homeowner selling houseUSD50High796.0036.00
685price my home to sellUSD50High976.9232.13
686private sell houseUSD500Medium541.3515.00
687sell my home san antonioUSD50Low23
688as is homes for saleUSD500High683.5721.24
689sell condo fastUSD50Low2416.8151.48
690tips for selling home by ownerUSD50Medium551.6519.43
691we buy california houses for cashUSD50Medium5816.7063.75
692full cash offer on houseUSD50Medium679.2133.65
693selling your own home as a realtorUSD50High826.8427.51
694selling home in san antonioUSD50Low4
695we buy houses any condition llcUSD50High100
696we buy houses in californiaUSD500Low1710.0054.95
697sell without a realtorUSD500High755.6122.85
698sell my house tennesseeUSD50Low1415.0058.51
699listing my house for saleUSD500Medium658.3345.24
700we buy houses in new jerseyUSD500Medium497.5841.73
701sell your own house without realtorUSD50High884.0830.00
702apps like opendoorUSD50Medium6211.2462.24
703creative ways to sell a house fastUSD500Low329.0043.62
704fast and easy house buyersUSD50High7710.9042.47
705sell my house in nashvilleUSD50Low1
706sell my house phoenixUSD500Low2216.2660.00
707we buy houses for cash new jerseyUSD50High8113.1844.00
708selling a home by ownerUSD5000High752.6924.00
709opendoor denverUSD500Low257.0850.00
710sell real estate yourselfUSD50Low324.2616.57
711selling your own home without a realtorUSD50High907.7232.54
712sell my house fast floridaUSD500Low3314.7848.75
713houses selling too fastUSD50Low339.0128.55
714i want to sell my house without a realtorUSD50High918.3140.00
715sell my house fast alabamaUSD50High7610.0054.11
716we buy houses louisianaUSD50Medium409.0332.43
717cash for homes michiganUSD50Medium6516.5457.50
718selling houses websitesUSD500High683.3417.88
719we buy houses in njUSD50Medium6512.8952.16
720house buyers in las vegasUSD50Unknown
721sell my house in oklahomaUSD50High8025.8976.68
722we buy houses south jerseyUSD50Medium6516.9260.75
723cash home buyers in michiganUSD50Low13
724online real estate salesUSD500High722.8512.71
725we buy houses new yorkUSD500Medium336.8514.71
726sell house fast san diegoUSD500Low2111.2633.78
727selling your own home without an agentUSD50High887.3928.98
728sell my house fast san diegoUSD500Medium5819.4945.00
729houses sold as isUSD500Medium413.6025.47
730sell my house atlanta gaUSD50Low0
731sell your house yourself websiteUSD50High8612.0051.89
732ibuyer feesUSD50Medium484.3519.48
733houses as is for saleUSD50High942.069.37
734sell my house in tucsonUSD50Low2014.4433.39
735sell my house fast illinoisUSD50High100
736we buy houses fast san diegoUSD50Low15
737sell my house bostonUSD50High8212.9529.85
738selling a house in las vegasUSD50Low14
739sell home without agentUSD500High867.3432.01
740private selling a houseUSD500High777.0028.30
741sell my house dallas txUSD50Low715.0075.69
742we buy houses cash californiaUSD50Low2315.7381.25
743sell your home yourself websitesUSD500High909.8132.00
744sell my house arizonaUSD50Low308.8341.00
745sell my house fast dcUSD50Medium6213.3040.00
746opendoor citiesUSD50Medium3715.0038.08
747total cost to sell a houseUSD50Medium476.9122.00
748opendoor service chargeUSD50Medium639.7832.40
749opendoor home sale calculatorUSD50Medium378.5045.21
750cost of selling houseUSD5000Medium475.6320.00
751typical costs to sell a houseUSD50Medium513.9217.95
7523904 valley meadowUSD50Low0
753cost to sale a houseUSD50Medium405.0015.00
754typical cost to sell a homeUSD50Medium445.9725.91
755average costs to sell a houseUSD500Medium394.4817.81
756cost involved in selling a houseUSD500Medium405.1622.00
757selling home feesUSD500Medium425.7518.30
758all cash bidUSD50Low1
759seller pays commissionUSD50Low1
760real estate selling costsUSD50Medium332.3215.00
761fees in selling a houseUSD5000Medium444.5920.07
762typical fees for selling a houseUSD50Medium405.5521.81
763costs of selling a homeUSD5000Medium447.3820.49
764opendoor raleighUSD500Medium439.2631.81
765average cost to sell a homeUSD500Low326.0016.57
766questions to ask before selling your homeUSD50Medium577.9327.33
767fees with selling a homeUSD50Medium526.2624.91
768cost to sell your houseUSD50Medium576.9525.00
769house closing process for sellerUSD500Low233.9920.67
7703904 valley meadow rdUSD50Low0
771closing costs to sell a houseUSD5000Medium402.4914.63
772271 s mapleton drUSD500Low40.170.92
773tips for buying a house in a seller's marketUSD50Low81.023.14
774costs associated with selling a houseUSD500Low293.4917.52
775opendoor self tourUSD50Medium356.0925.65
776fees associated with selling a houseUSD500Medium405.8024.94
777do buyers pay commissionUSD50Low0
778fees involved with selling a houseUSD50Medium494.0820.07
77911854 roscoe blvdUSD50Low0
780cost associated with selling a homeUSD500Low325.2515.00
7813904 valley meadow rd encinoUSD50Low0
782agent fee for buying houseUSD50Low140.659.37
783real estate fees for buyerUSD500Low231.2514.67
784624 n bonhill rdUSD50Low2
785cash offer on house meaningUSD50Medium344.7825.50
786open door hidden feesUSD500High809.4932.10
787expenses of selling a houseUSD500Medium484.5918.78
788490 paces ferry roadUSD50Low6
789real estate agent fees buyerUSD500Low333.3415.00
790opendoor charlotteUSD50Medium609.4645.20
791911 foothill roadUSD50Low2
792145 n mapleton dr floor planUSD50Low0
793490 west paces ferryUSD500Low50.621.32
794100 glen eagle wayUSD500Low2
795490 w paces ferry rdUSD500Low3
796490 w paces ferry rd nwUSD50Low50.481.08
7971831 benedict canyon drUSD50Low8
798sellers cost to sell homeUSD50Medium643.6915.00
799buying a house in a seller's marketUSD500Low92.0013.71
8003262 leyland wayUSD50Low9
801real estate agent cost for buyerUSD50Low282.1811.99
802seller responsibilities at closingUSD50Low2
803closing house saleUSD50Low120.874.54
8041275 benedict canyonUSD50Low2
805emotional stages of selling a houseUSD50Medium366.3014.85
806home selling mistakesUSD500Low97.9516.44
807opendoor scottsdaleUSD50Medium4810.8533.69
808cost of selling a house in california calculatorUSD50Medium512.7110.40
8091231 lago vista dr floor planUSD50Low0
810buyer and seller agent commissionUSD50Low283.6615.00
8111895 rising glen rdUSD50Low1
8122571 wallingford dr floor planUSD50Low3
813910 e taylor stUSD50Low14
81410539 bellagio rdUSD50Low2
81510539 bellagio roadUSD50Low0
816714 west potrero roadUSD50Low0
817questions to ask selling agentUSD50Low101.2210.01
8183650 tuxedo rd nwUSD50Low0
819cost of selling house calculatorUSD5000Medium462.1611.83
8203262 leyland way seUSD50Low2
821cost to sell my houseUSD50High736.0531.40
822home resale value factorsUSD50Low161.9512.71
823real estate broker fee for buyerUSD50Low5
824490 west paces ferry roadUSD50Low4
8252555 spalding driveUSD50Low8
826home sale calculator zillowUSD500Low161.096.45
827buyer real estate agent commissionUSD500Medium403.2715.00
8281254 brook forest driveUSD50Low1
8292805 auburn knightdale rdUSD50Low7
8301266 mcallistar drUSD50Low24
8312200 s fort apache rdUSD500Low50.351.87
8324988 noeline aveUSD50Low0
83315 deerwood laneUSD500Low1
834opendoor closing costsUSD50High6710.8444.62
835zillow sale calculatorUSD500Low41.9011.89
8361041 mountain woods ctUSD50Low3
8371130 w conway dr nwUSD50Low2
838zillow home sale calculatorUSD500Low61.5811.50
8395778 fairington farms ctUSD50Low2
8403602 w hidden mountain lnUSD500Low1
841912 n hillcrest rdUSD50Low1
84242 pelican pointUSD50Low0
843616 n fuller aveUSD500Low0
8442321 sunset ridge circleUSD50Low0
845708 n beverly drUSD50Low4
8461895 rising glenUSD500Low1
8472217 victor ctUSD50Low120.210.58
848negotiating house pricesUSD500Low90.3610.32
849offer letter for house sampleUSD50Low9
850house buying offer letterUSD500Low280.704.68
851selling the family home emotionsUSD50Low316.0018.03
852buyer financing fell throughUSD500Low134.6420.04
853selling house calculator zillowUSD50Low232.1910.24
8549366 flicker wayUSD500Low40.825.54
855realtor fee for buyerUSD500Low161.6711.83
8562200 fort apacheUSD50Low9
857sample offer letter to purchase propertyUSD5000Low121.398.18
8581524 benedict canyon drUSD50Low0
859letter for houseUSD5000High1000.431.57
860rising glen rdUSD50Low0
861house offer lettersUSD5000Low240.822.58
862opendoor agent partner programUSD50Medium376.3525.00
86327600 pacific coast highwayUSD500Low2
8644146 w 229th stUSD50Low0
8652571 wallingford drUSD500Low30.180.59
866realtor questions for sellersUSD50Medium442.008.45
867401 s highland aveUSD500Low50.030.08
86814950 w mountain view blvdUSD50Low13
869zillow proceeds calculatorUSD500Low12.769.26
870negotiating a home purchaseUSD50Low12
871negotiating home priceUSD500Low110.348.85
872zillow sales proceeds calculatorUSD500Low0
873915 upper hembree rdUSD50Low2
874opendoor cancellation policyUSD50Medium466.5425.27
875sample real estate offer letterUSD500Low140.803.19
87616805 oak view drUSD50Low0
877best way to sell your homeUSD50High9515.0050.00
878buyer agent commission feeUSD50Low21
8792200 s fort apacheUSD50Low7
8801706 n doheny drUSD50Low1
8813727 tuxedo roadUSD50Low6
882offer on house letterUSD50High96
883real estate buyer commissionUSD50Low275.3215.00
8845225 spence farm rdUSD50Low0
8856979 bob o linkUSD50Low0
886benefits of accepting a cash offer on houseUSD500Medium486.8823.20
887tips for buyers in a sellers marketUSD50Low91.594.18
888rising glen roadUSD50Low1
8896979 bob o link drUSD50Low0
890home negotiationUSD50Low150.304.90
891benefits of cash offer on houseUSD500Low285.4027.07
892discovery village rancho cucamongaUSD50Low130.671.63
89390 whitaker circle nwUSD50Low2
8941405 cold canyon rdUSD50Low2
89522751 plummer stUSD50Low2
896negotiating house price buyerUSD50Low11
8972510 chimney ridge drUSD50Low0
898402 golden pondUSD50Low6
89915 del mar newport coast californiaUSD500Low8
9001963 hosea l williams dr seUSD50Low0
9013862 grahams port lnUSD50Low10
9025735 plum dale rdUSD50Low5
903benefits of cash offer on house for sellerUSD50Medium4610.0038.03
904zillow net proceeds calculatorUSD50Low1
905hiring a realtor to sell your homeUSD50High9611.9036.07
9062721 n river trail rdUSD50Low0
907factors affecting value of residential propertyUSD50Low17
90815 del mar newport coast caUSD50Low6
9091614 s houston school rdUSD50Low0
910home buying negotiationUSD50Low12
9113135 juhan rdUSD50Low2
91210701 bellagio roadUSD500Low10.290.69
9131524 stone canyon rdUSD50Low1
9145303 round meadow rdUSD50Low1
915buyer agent feeUSD5000Low222.1010.52
9161633 e lakeside drUSD50Low12
917property purchase offer letterUSD500Low230.842.79
918home sale calculator ontarioUSD50Unknown
9193411 e chevy chase drUSD50Low0
9202318 bluff creek overlookUSD500Low100.390.75
921template offer letter for houseUSD500Low290.845.41
9223862 grahams port laneUSD50Low10
923buying a home in a seller's marketUSD500Low132.0014.01
9244 coral ridge newport coastUSD50Low11
925all cash buyerUSD50Medium436.2722.15
926home buyer offer letter sampleUSD50Low100.9917.25
9274295 whitewater creek rdUSD50Low0
928offer letter to sellerUSD500Low321.219.80
92910250 w sunset blvdUSD50Low0
93070 portuguese bendUSD50Low3
93111958 sunshine terrace studio cityUSD50Low1
9321175 n hillcrestUSD50Low0
933901 alpine drUSD50Low30.390.69
934cash offer on house processUSD500Medium635.2933.43
935zillow home sale proceeds calculatorUSD50Low1
936965 summerfield drUSD50Low1
937rocking horse ridge orange caUSD50Low11
9385143 escalon aveUSD50Low0
9391107 moonlight bayUSD50Low2
9402812 s lakeview drUSD50Low0
9416137 grimes canyon rdUSD50Low0
9426112 n nauni valley drUSD50Low2
943home offer lettersUSD5000Medium430.828.30
9441808 point de vue drUSD500Low1
9451175 n hillcrest rdUSD500Low2
94615105 mulholland drUSD50Low4
9475003 e sky desert lnUSD50Low11
948zillow selling calculatorUSD50Low91.9412.35
9491231 lago vista driveUSD500Low1
9506213 long cove drUSD50Low0
951970 mount paran roadUSD50Low5
952buyers commission real estateUSD50Medium343.8616.89
953home sale proceeds calculator zillowUSD500Low31.5115.17
954home tour checklistUSD500Low5
9552050 w warm springs rdUSD50Low8
956negotiating for a houseUSD500Low110.255.58
957negotiating real estate priceUSD50Low13
9583515 w alameda aveUSD50Low0
9592200 fort apache roadUSD50Low7
960real estate agent cost to sell homeUSD50High766.0416.74
9616950 dume drUSD50Low0
96211328 old stage rdUSD50Low100.110.22
9631637 n orange groveUSD50Low0
964housing offer letterUSD50Low50.733.13
965negotiating buying a houseUSD50Low5
966house purchase offer letterUSD50Low200.662.87
9672404 pennsylvania aveUSD50Low2
9681175 n hillcrest rd floor planUSD50Low0
969tips for negotiating a house purchaseUSD50Low200.272.33
970house offer templateUSD500Low320.722.53
9715656 cedar ridgeUSD50Low3
972seller real estate feesUSD500Medium372.4815.00
973819 artistry wayUSD50Low0
9743027 franklin canyon drUSD50Low1
975s mapleton driveUSD50Low2
976901 n alpine drUSD500Low10.230.86
977opendoor lennarUSD50Medium387.5834.77
97810250 sunset blvdUSD500Low0
9793428 beverly driveUSD50Low0
98012319 w rock springs drUSD50Low10
9813225 golfe links drUSD50Unknown
9828430 sentinae chase drUSD50Low1
9832405 via anitaUSD50Low0
98424400 little valley rdUSD50Low0
9851803 marshallfieldUSD50Low2
986realtor buyer commissionUSD500Low242.8514.90
9871231 lago vistaUSD500Low1
988515 west paces ferry roadUSD50Low4
989negotiating house offerUSD50Low280.456.34
990700 e washington stUSD50Low2
991as a buyer do i pay realtor feeUSD50Low2
992661 auburn aveUSD500Low6
9933093 sweetwater mesa roadUSD50Low1
994average time to sell a house in houstonUSD50Unknown
995675 martin field drUSD50Low0
9967043 ivy pointe rowUSD50Low5
9971001 w paces ferry rdUSD500Low4
998closing costs and realtor feesUSD500Low162.2814.11
9992200 south fort apache roadUSD50Low6
10004817 long green driveUSD50Low80.150.67
1001real estate offer letter to sellerUSD50Low101.274.17
1002home buying negotiation tipsUSD50Low0
1003home buying offer letter templateUSD50Low191.1815.00
10047932 woodrow wilson drUSD500Low1
10052033 hercules drive ownerUSD50Low0
10062701 peyton springs cir swUSD50Low2
1007seller pays realtor feesUSD50Low70.9411.90
10082746 rinconia drUSD50Low50.430.95
1009lennar opendoorUSD50Low317.1320.00
10104110 paces ferry road nwUSD50Low2
1011413 keller smithfield rdUSD50Low10
10125625 e nauni valley driveUSD50Low2
1013cost of selling a house with a realtorUSD500Medium667.2323.93
1014home buyer offer letterUSD500Low150.5920.33
1015sad about selling houseUSD50Low246.0919.61
10161244 moraga driveUSD50Low2
1017800 e ocean blvdUSD500Low9
10182571 wallingfordUSD50Low70.310.94
10198031 floral aveUSD50Low0
10202200 south fort apacheUSD50Low6
1021commission fee real estateUSD500Medium412.9115.00
10225096 riverhill rdUSD50Low6
102314020 n 39th aveUSD50Low5
102446 deep sea newport coastUSD50Low8
10254500 powers ferry roadUSD50Low0
1026470 layton wayUSD50Low1
102723815 via de gema lindaUSD50Low14
10284110 paces ferry rd nwUSD50Low3
10295221 newstead manor lnUSD500Low1
10305710 n yucca rdUSD50Low2
10313970 victoria laneUSD50Low0
10325241 w whispering wind drUSD50Low0
103310824 chalon rdUSD50Low1
103421 martingale drUSD50Low5
10359551 oak pass rdUSD50Low0
1036prepare a house for saleUSD500Low201.427.58
103710410 n cave creek rdUSD50Low8
10383901 turtle creek blvdUSD50Low3
1039negotiating home price buyerUSD50Low0
10402907 e derringer wayUSD50Low6
10417776 firenze aveUSD50Low1
10429 pelican crestUSD50Low4
104310633 le conteUSD50Low0
104414122 utt drUSD50Unknown
104521 skyridge newport coast ca 92657USD50Low10
1046864 amsterdam ave neUSD50Low0
10471400 copper point driveUSD50Low0
10482200 s fort apache rd for saleUSD50Low25
10491 rockinghorse rdUSD50Low0
10501320 via romeroUSD50Low0
10512859 coldwater canyon drUSD50Low7
10529551 oak pass roadUSD50Low2
10531744 stone canyon rdUSD500Low1
10544141 glacier pointUSD50Low0
10551001 w paces ferry rd nwUSD50Low2
10564110 paces ferry rdUSD50Low4
10576902 los tilos rdUSD500Low2
1058prepare your house for saleUSD500Low281.547.16
10599550 oak pass roadUSD500Low1
10601883 orlando roadUSD50Low1
10613093 sweetwater mesa rdUSD50Low3
1062realtor questionsUSD500Low301.256.11
10631400 barony lake wayUSD50Low12
10642484 roscomare rdUSD500Low2
1065200 n remuda ctUSD50Low0
1066175 westbourne drUSD50Low9
10672595 sentinel chase wayUSD50Low4
1068buyer offer letterUSD500Low50.883.12
1069open house tips for buyersUSD50Low86.3629.55
10701301 woodland aveUSD50Low0
10711410 s white chapel blvdUSD50Low4
10721426 harridge drUSD50Low0
10731006 n rexford drUSD50Low2
10744625 clary lakes drUSD50Low0
10751335 carla lnUSD50Low0
107629 avery dr neUSD50Low7
1077buyer offer letter to sellerUSD50Low2
107832506 pacific coast highwayUSD50Low0
10791013 n beverly drUSD50Low3
108011159 la maida stUSD50Low60.150.95
10817235 rio flora plUSD50Low0
10827327 hazeltine aveUSD50Low0
10835455 w ray rdUSD50Low0
10846957 watkins glen rdUSD50Unknown
1085opendoor home reserveUSD50Medium368.6453.26
108612047 kagel canyon rdUSD50Low11
1087realtor cost for buyerUSD50Low230.708.58
1088steps in selling your homeUSD500High695.1033.00
10891011 n beverly drUSD500Low20.190.79
10901159 summit driveUSD50Low2
10913100 mandeville canyon rdUSD50Low0
10923100 mandeville canyon roadUSD500Low3
1093524 bonnards peak rdUSD50Low0
1094noeline ave encino caUSD50Low3
1095227 n tigertailUSD50Low0
10967801 old stage rdUSD50Low0
1097seller closing costs californiaUSD500Low82.196.27
1098411 w seaside wayUSD50Low10
1099closing costs in california for sellerUSD50Low7
11001283 lavista rdUSD50Low1
11011778 viewmont drUSD50Low1
11023873 dumbarton rd nwUSD50Low0
1103commission paid to real estate agentsUSD50Medium54
11042401 s beverly drUSD50Low3
11051408 tartan driveUSD50Low0
110626732 kicking horse drUSD50Low0
11071608 golden creek courtUSD50Low140.090.38
110820724 n 112th stUSD50Low0
110924198 case courtUSD500Low2
111028955 selfridge drUSD50Low0
1111416 plainville drUSD50Low0
11121251 tower groveUSD50Low3
11131000 laurel wayUSD500Low0
1114ask a realtor a questionUSD50High823.2212.29
1115steps selling houseUSD5000Medium595.4330.00
11161575 w warm springs rdUSD50Low6
11179 pelican crest newport coastUSD50Low7
11181622 viewmont driveUSD500Low1
1119935 n la jolla aveUSD50Low3
11205333 e palomino rdUSD50Low2
112131701 peppertree bendUSD50Low0
1122174 chester ave seUSD50Low5
11231170 black canyon rdUSD50Low0
112418038 blue sail drUSD50Low0
11252500 white stallion rdUSD500Low0
11261400 linda flora drUSD50Low0
11272250 n peytonville aveUSD50Low0
11285253 whitehaven park laneUSD50Low1
1129home purchase offer letter templateUSD500Medium431.004.09
1130277 st pierreUSD500Low5
11318 midsummer newport coast ca 92657USD500Low2
1132316 peters st swUSD50Low5
11331006 laurel wayUSD50Low0
11342136 e balboa blvdUSD500Low3
11356825 black fox laneUSD50Low0
1136realtor agent commissionUSD50Medium472.2412.00
11373559 cherry ridge blvdUSD50Low10
11386902 los tilosUSD50Low1
1139715 n alpine drUSD500Low40.210.82
11407911 oceanus drUSD50Low20.220.39
11411580 stone canyonUSD50Low0
11424926 deloacheUSD50Low0
1143repairs before selling houseUSD50High674.8828.83
11443350 n knoll drUSD50Low0
11453940 paper mill rdUSD50Low4
1146818 doheny driveUSD50Low15
11471900 sunset plaza drUSD50Low0
1148real estate agent commissionsUSD5000Low272.8615.00
11491130 west conwayUSD500Low60.241.04
11502200 summitridge drUSD50Low2
11513500 w manchester blvdUSD500Low8
115210701 bellagio rdUSD500Low20.290.86
11531175 hillcrestUSD50Low2
11547 pelican vistaUSD50Low2
115521550 cleardale st newhall caUSD50Low0
1156810 n orlando aveUSD50Low1
11571700 lexington rdUSD50Low0
11583410 e cambridge aveUSD50Low0
11593500 manchester blvdUSD50Low6
1160question to ask realtorUSD5000Low141.015.78
11611021 n crescent heights blvdUSD50Low3
11621261 tower grove drUSD50Low3
11633728 ocean blvdUSD50Low5
11641721 coldwater canyon drUSD50Low3
11659553 bella terra drUSD500Low2
11661264 emerald ave seUSD50Low2
11672033 los angelesUSD50Low0
116814155 beresford rdUSD50Low4
116921 skyridge newport coast caUSD50Low15
11702501 old salem circleUSD50Low4
1171715 avenida columboUSD50Low3
1172house offer letter to sellerUSD500Low76.1833.00
117316013 s desert foothillsUSD50Low5
11745708 brushton stUSD50Low0
1175steps to sell your houseUSD500Medium635.0735.00
11766805 deloacheUSD50Low0
11779 seahaven newport coast ca 92657USD50Low0
1178letter for real estate offerUSD5000Low220.754.20
1179277 st pierre rd bel airUSD50Low1
11803994 cherrywoodUSD50Low4
11811061 bailey woods rdUSD50Low0
11821803 marshallfield lnUSD50Low0
1183245 saltair aveUSD50Low0
11841601 n fuller aveUSD50Low12
118523800 malibu crest drUSD500Low30.221.20
1186421 s la fayette park plUSD500Low10
11876962 wildlife roadUSD50Low0
11881855 moores mill rdUSD50Low3
118940125 camino del vinoUSD50Low2
11909444 sierra mar plUSD50Low1
1191advantage of cash offer on houseUSD50Low244.3123.74
11922121 w waylandUSD50Low0
1193251 valley roadUSD50Low1
11947280 lanier cove courtUSD50Low2
11958155 e roosevelt stUSD50Low3
1196crystalaire place in granada hillsUSD50Low10
1197real estate agent fees for sellerUSD500Medium463.5515.00
11981665 mandeville canyon rdUSD50Unknown
11991672 panola rdUSD50Low10
120010660 wilshire blvdUSD500Low60.470.94
12017056 saint clair aveUSD50Low0
1202737 preserve park drUSD50Low0
1203baker ranch homesUSD50Medium420.221.36
12041717 e union hills drUSD500Low6
1205questions to ask your real estate agentUSD50Low171.864.30
1206345 n bundy drUSD50Low1
12078101 w flamingo rdUSD500Low2
12089601 oak pass rdUSD50Low0
12091104 old tucker rdUSD50Low12
12104650 ranch house rdUSD500Low120.350.41
12119 seahaven newport coastUSD50Low0
12124826 la roda aveUSD50Low0
12131425 e desert cove aveUSD50Low5
12144171 holly knoll driveUSD50Low10
12159945 beverly groveUSD50Low0
12160 tortuoso wayUSD50Low2
12171695 poppy peak driveUSD50Low2
12182831 durand drUSD50Low1
1219ask a realtorUSD500High724.5215.00
1220average cost to fix up house to sellUSD500Medium595.2619.96
1221995 old tucker rdUSD50Low3
12222329 w tanner ranch rdUSD50Low5
12236086 belair lake rdUSD50Low2
1224645 red maple laneUSD50Unknown
1225901 alpineUSD50Low10
122616330 heathfield drUSD50Low6
12272911 antelo view drUSD500Low2
12281207 dolphin terraceUSD50Low60.090.24
12297150 la presa drUSD50Low1
12309124 s budlong aveUSD50Low6
1231best time to sell a house in arizonaUSD50Medium6111.6846.81
12321140 e ocean blvdUSD50Low10
123324100 hidden ridge rdUSD50Low8
1234350 n carolwood drUSD50Low0
12354603 pine acre circleUSD50Low0
12364954 e rockridge rdUSD50Low2
1237understanding the housing marketUSD50Low61.252.37
1238wildcat ranch silveradoUSD50Low0
123911817 macoda lnUSD50Low8
1240home offer letter templateUSD500Low240.893.62
124111011 n 92nd stUSD50Low12
12421622 viewmont drUSD50Low1
12432928 n 56th stUSD50Low0
12443509 euclidUSD50Low0
12451144 whispering oaksUSD50Low0
12462024 s baldwinUSD50Low3
1247seller agent commissionUSD500Medium393.0513.84
12482004 mallard woods placeUSD50Low0
1249prepare your home for saleUSD500Low242.689.11
125021550 cleardale st newhall ca 91321USD50Low0
12514636 e moonlight wayUSD50Low1
1252real estate agent questionsUSD500Low301.184.67
12534 telescope newport coastUSD50Low5
1254407 powers ferry roadUSD50Low2
1255421 s lafayette park plUSD50Low10
1256buyer sample offer letter to purchase propertyUSD500Low30.7110.45
1257hercules drUSD500Low2
12582760 queens garden driveUSD50Low0
1259montana del lagoUSD50Low16
12601622 viewmontUSD50Low1
1261offer letter house templateUSD50Low101.572.60
1262535 w thomas rdUSD50Low110.211.00
1263reasons escrow falls throughUSD50Low0
12641347 bexley place kennesaw gaUSD50Low3
1265home offer letter to sellerUSD500Low141.4019.64
126610602 bridge hollow ctUSD50Low2
12671608 cutters millUSD50Unknown
12681251 tower grove drUSD500Low3
12694282 roswell rdUSD50Low6
127014250 w wigwam blvdUSD500Low19
12712833 via segoviaUSD50Low6
1272seller agent commission feeUSD50Low14
12739459 beverly crest drUSD50Low2
1274buying agent commissionUSD5000Low212.4312.13
127512700 chalon roadUSD50Low0
12761300 beverly estates drUSD500Low1
12775841 round meadow roadUSD50Low0
1278191 monterey rdUSD50Low11
1279227 n tigertail rdUSD50Low1
1280things to do before closing on a house sellerUSD50Low11
12811180 mount paran rd nwUSD50Low6
128225220 walker rdUSD500Low1
1283real estate lingoUSD500Low120.302.14
128411480 covey point lnUSD50Unknown
12851175 hillcrest roadUSD50Low0
12861580 stone canyon roadUSD500Low1
12872116 vintage hill driveUSD50Low5
1288219 s mapleton driveUSD500Low1
12891006 chantilly rdUSD50Low5
12903274 n knoll drUSD50Low2
12917193 cavender dr swUSD50Low0
1292i wanna sell my houseUSD50High9634.84106.00
1293133 s mapleton drUSD50Low3
12941808 point de vueUSD500Low2
12952112 e balboa blvdUSD50Low100.170.55
12962422 rose palm ctUSD50Unknown
12971111 w cinnabar aveUSD50Unknown
1298720 heards ferry rdUSD50Low5
12999601 oak pass roadUSD50Low2
13001116 laurel wayUSD50Low0
13011580 stone canyon rd floor planUSD50Unknown
1302realtor cost to sell homeUSD50Medium639.0922.55
13032223 california aveUSD50Low0
13046854 iris circleUSD50Low0
1305selling a home in orlandoUSD50Low0
130619226 n cave creek rdUSD50Low13
13075615 center hill church rdUSD50Low0
13087400 w flamingo rdUSD500Low7
1309837 greenridge drUSD50Low0
1310after seller accepts offerUSD50Low0
13113791 winford drUSD50Low0
13123093 sweetwater mesaUSD50Low3
13133809 cody rdUSD50Unknown
13142500 vasanta wayUSD50Low0
1315525 s ardmore aveUSD500Low16
1316buying a house realtor feesUSD50Low111.3212.07
13172463 solar driveUSD50Low30.180.65
1318133 s mapletonUSD50Low50.180.43
13192025 griffith park blvdUSD50Low1
132025364 prado de la felicidad ownerUSD50Low4
132125220 walker rd hidden hills ca 91302 floor planUSD50Low0
13221175 north hillcrest roadUSD50Low1
1323312 n faring rdUSD50Low2
13245581 boreal wayUSD50Low4
13256902 los tilos roadUSD50Low0
132612760 s bristol cirUSD50Low0
132712910 walsh aveUSD50Low2
13281943 laughlin park drUSD50Low0
13291419 dowdy ferry rdUSD50Low8
13302407 carman crest drUSD50Low4
1331756 moores mill rdUSD50Low2
1332818 n doheny drUSD500Low240.270.82
1333tips for preparing your house for saleUSD50Low290.954.37
13344042 moheb st swUSD50Low3
13351061 ravoli drUSD50Low1
13361414 golf link drUSD50Low2
13376003 overby rdUSD50Low5
13381137 linda vista aveUSD50Low0
13392304 donella cirUSD500Low60.160.40
13401025 n kings rdUSD50Low11
13411575 w warm springsUSD50Low9
13422500 white stallion roadUSD500Low1
13435808 mill crest wayUSD50Low0
13444542 coldwater canyon aveUSD50Low12
13451040 w conway dr nwUSD500Low0
134610610 s 48th stUSD50Low5
134714812 morrison stUSD50Low0
13481721 coldwater canyonUSD50Low4
13494100 s pinelake wayUSD50Low60.230.35
135016013 s desert foothills pkwyUSD50Low5
13514526 planters hill driveUSD50Low0
13524704 e paradise village pkwyUSD50Low18
1353real estate fees for selling a houseUSD50Medium644.1122.00
13541101 white sails wayUSD50Low3
1355918 olde thompson creek rdUSD50Low5
1356822 n kenter aveUSD50Low1
1357903 hartford wayUSD50Low4
13584950 n miller rdUSD50Low19
1359174 lessay newport coast ca 92657USD50Low0
13601890 w paces ferry rdUSD50Low4
1361orange park acres homes for saleUSD500Medium370.110.74
136213020 sky valley rdUSD50Low1
13635194 lakeview canyon rdUSD50Low1
13643140 manor bridge drUSD500Low3
13655960 williamstown rdUSD50Low0
13666120 pattillo wayUSD50Low14
1367houses for sale in orange park acres caUSD50Low130.091.47
1368real estate agent costUSD500Low312.7611.32
13691025 sweetwater bridge circleUSD50Low0
1370questions to ask a real estate agentUSD500Low211.404.51
137123234 victory blvdUSD50Low8
137230621 hilltop wayUSD50Low3
1373609 palisades beach rdUSD50Low1
1374970 sidney marcus blvdUSD500Low7
1375listing agent feeUSD50Medium385.2715.00
13764322 hayvenhurstUSD50Low0
13775841 round meadow rdUSD500Low0
1378700 white oak pond roadUSD50Low0
1379sample letter for buying a houseUSD500Low300.817.47
1380sierra dawn estatesUSD500Low200.130.65
13811813 e bay aveUSD50Low1
13826868 sky pointe drUSD500Low60.381.47
1383house purchase offer letter templateUSD50Low270.933.24
13841300 beverly estates dr beverly hillsUSD50Low0
1385preparing a house to sellUSD500Medium624.3018.47
13862033 hollywood hillsUSD50Low2
1387housing market fluctuationsUSD50Low2
1388115 peachtree memorial driveUSD50Low8
13891317 londonderry plUSD500Low0
13904420 northside chase nwUSD50Low11
139178 bedstraw loopUSD50Low2
1392246 eagles landing wayUSD50Low0
1393lennar trade up programUSD50Low150.8015.21
1394la crescenta homesUSD50Low160.060.69
13952346 n cahuenga blvdUSD50Unknown
1396seller commissionUSD500Low274.2215.00
13971525 san vicenteUSD50Low0
1398closing documents for sellerUSD500Low120.658.40
1399do buyers pay realtorsUSD500Low22.4010.94
1400negotiating house price sellerUSD50Medium340.7214.63
1401137 s burlingame aveUSD50Low3
14021505 espinosa circleUSD50Low4
14038095 hillside climb wayUSD50Unknown
140414823 hartsook stUSD50Low0
1405real estate sale commissionUSD500Medium492.8615.00
14062700 cahuenga blvd eUSD50Low9
1407copa de oro anaheim hillsUSD50Low11
14087080 mulholland driveUSD50Low2
1409all cash no contingencyUSD50Low133.8717.10
1410closing dates on a houseUSD500Low21.647.09
1411best questions to ask a realtorUSD50Low212.006.67
141221 shell beach newport coastUSD50Low1
141326162 calle robertoUSD50Low2
1414457 cuesta wayUSD50Low0
1415average real estate fees for sellingUSD50Medium522.4210.00
1416questions to ask a potential realtorUSD500Low121.556.72
141730 pelican pointUSD50Low2
1418slang real estate termsUSD50Low9
14197830 e camelback rdUSD50Low1
14209 beverly ridge terraceUSD500Low0
142112110 pennsylvania aveUSD50Low3
14224186 n arnold mill rdUSD500Low5
1423704 n ardenUSD50Low0
14249955 beverly grove drUSD500Low1
142510950 w union hills drUSD50Low1
14262300 e magma rdUSD500Low6
14276542 ocean crest drUSD50Low6
14281259 beverly estates dr beverly hillsUSD50Low2
142914034 n coral gables drUSD50Low0
14304046 cromwell aveUSD50Low0
1431818 dohenyUSD50Low170.371.94
1432property selling costsUSD50Medium406.9015.00
14332670 bowmont drUSD50Low50.180.86
14345555 dixon trail rdUSD50Low0
14359696 antelope rdUSD50Low0
143623741 harbor vista drUSD50Low3
14373601 w tierra buena lnUSD50Low3
14383228 w glendale aveUSD50Low9
1439950 kenfield avenueUSD50Low0
1440ocean del rey estatesUSD50Low0
144124932 thousand peaks rdUSD50Low0
144225339 via dona christaUSD50Low0
144321114 lemarsh stUSD50Low4
14445215 cedar glenn ctUSD50Low2
14456 shoreview newport coastUSD50Low5
1446seller agent feeUSD500Low333.3515.00
1447150 shady brook walkUSD50Low2
14485619 walnut hill laneUSD50Low0
1449house selling seasonUSD50Low252.0012.00
145012835 parkyns stUSD50Low0
14513010 cypress pond passUSD50Low110.301.32
14525251 woodman aveUSD50Low1
145324100 hidden ridge roadUSD50Low1
14541259 beverly estateUSD500Low2
14551400 linda floraUSD50Low90.180.63
14561130 shadow hill wayUSD50Low4
145721 shell beachUSD50Low0
1458301 carnation aveUSD50Low0
14592121 w royal palm rdUSD50Low2
146037045 n romping rdUSD50Unknown
14619719 heather roadUSD50Low1
1462market value of your homeUSD50High801.679.01
14631030 e ocean blvdUSD50Low5
146410538 wellworth aveUSD50Low5
14651102 s waverly drUSD50Unknown
1466home repairs before sellingUSD50Medium644.8230.00
1467writing letter to buy a houseUSD50High1000.698.12
1468156 s oak knoll aveUSD50Low3
14692379 briarwest blvdUSD500Low11
1470real estate jargonsUSD500Low60.366.54
14711205 tacketts pond driveUSD50Low2
14725889 jed smith rdUSD50Low3
1473south mapleton driveUSD50Low2
14741105 moores mill roadUSD50Low4
1475seller real estate commissionUSD500Medium463.7815.00
14761500 n harbor blvdUSD50Low0
14777878 e gainey ranch rdUSD50Low9
1478homes for sale in orange park acres caUSD50Medium370.130.87
14792805 macon dr swUSD50Low0
14803447 kingswood runUSD50Low0
1481first steps to selling your houseUSD50High857.5730.00
14822304 donella cir los angeles ca 90077 floor planUSD50Low8
1483480 john wesley dobbs aveUSD50Low6
1484panorama heights orange countyUSD50Low2
148518 peachtree circleUSD50Low1
148625110 avenida ignacioUSD50Low0
1487909 n bedford drUSD50Low0
14881905 sunset plaza drUSD50Low4
1489200 s mapleton drUSD50Low2
14901432 highland aveUSD50Low0
14911740 stone canyonUSD50Low4
14926854 red maple drUSD50Low3
149310040 e happy valley roadUSD50Low3
14944304 via pavionUSD50Low1
14951 monterey pine newport coastUSD50Low4
14962529 seven hills drUSD50Low0
1497mcallistarUSD50Low1
1498926 n beverly drUSD50Low1
14993301 henderson mill rdUSD500Low160.370.53
1500911 e mountain vista drUSD50Low0
15012855 peachtree rd neUSD500Low3
150289 mangum st swUSD50Low6
15036930 dume driveUSD50Low0
15047425 shadburn ferry rdUSD50Low4
15058130 gould aveUSD50Low0
15061300 beverly estate drUSD500Low1
15072451 n rainbow blvdUSD500Low40.470.82
15085740 lower seguin rdUSD50Low6
1509615 champions driveUSD500Low5
151024246 malibu rdUSD50Low1
1511514 chalette driveUSD50Low0
15122449 mountain view ctUSD500Low140.160.84
1513909 bedfordUSD50Low0
15141712 n beverly drUSD50Low1
15152153 autumn chase drUSD50Low7
15162700 cahuenga blvdUSD500Low70.511.46
1517300 n bethany rdUSD500Low3
15188520 w palm lnUSD500Low1
1519old milburnie roadUSD50Low2
15201743 n stanley aveUSD50Low0
152129073 silver creek rdUSD50Low0
1522345 n bundyUSD50Low0
1523homes for sale covenant hillsUSD500Low180.101.00
1524808 n alpineUSD50Low1
152515240 n 142nd aveUSD50Low5
15262019 w lemon tree plUSD50Low12
152775 beverly parkUSD50Low0
15281382 rural hill rd antioch tnUSD50Low14
152916 coral reef newport coastUSD50Low0
15303606 bancroft mainUSD50Low2
15313995 randall mill rdUSD500Low2
1532for sale by owner closing processUSD50Low150.619.49
1533homes for sale in la crescentaUSD500Low180.070.52
15343551 bolfair dr nwUSD50Low11
15355150 old bill cook rdUSD50Low11
15367046 n 59th placeUSD50Low12
1537872 sierra vista drUSD50Low6
15381422 lachman lnUSD50Low2
15396205 rocky creek wayUSD50Low1
1540219 s mapletonUSD50Low0
15412304 donellaUSD50Low7
15425751 e hacienda aveUSD50Low5
1543521 n canonUSD50Low1
15441920 s pacific coast hwyUSD50Low9
1545616 nimes rdUSD50Low0
154610040 e happy valleyUSD500Low5
15475697 hoback glen roadUSD50Low5
15489719 heather rdUSD50Low0
154912 tasman seaUSD50Low0
15504316 marina city drUSD500Low14
15519830 yoakum drUSD50Low0
1552good questions to ask real estate agentUSD50Low130.782.36
15531230 horn aveUSD50Low170.230.84
155414450 creek club driveUSD50Low0
1555921 w university drUSD500Low9
1556things to fix before selling houseUSD50Medium38
15576201 rodgerton drUSD500Low2
1558912 hillcrestUSD50Low1
1559open door founderUSD500Low148.5021.79
1560real estate seller commissionUSD50Medium503.3315.00
1561412 monarch bay driveUSD50Low3
15625824 jed smith roadUSD50Low3
1563601 mountain drUSD500Low2
1564219 mapletonUSD50Low1
15651115 w san miguel aveUSD50Unknown
156623532 ehlers drUSD50Unknown
15672928 elm stUSD50Low0
15686401 e nohl ranch rdUSD50Low11
1569house for sale in la crescenta caUSD500Low160.050.35
15702030 w bowsprit lnUSD50Low0
15712069 cold canyon rdUSD50Low1
1572911 n foothill rdUSD50Low0
1573questions to ask a listing agentUSD500Low141.276.86
157412 rose ave venice caUSD50Low0
15753758 ballina canyon rdUSD50Low0
1576questions a realtor should ask a sellerUSD500Low332.278.26
15779050 w tropicana aveUSD500Low8
1578realtor commission feeUSD50Low333.4813.87
157925 lake cove approachUSD50Low11
1580402 golden pond drUSD50Low7
1581655 w vistoso highlands drUSD50Low9
1582real estate sales feesUSD50Medium591.5015.00
15831101 e bethany home rdUSD50Low0
158414820 valley vistaUSD500Low1
158521655 n 36th aveUSD50Low1
1586440 kimberly forest wayUSD50Low2
158762 troup courtUSD50Low1
15882200 e trinity mills rdUSD50Low4
158930826 broad beachUSD50Low2
15903166 camp branch rdUSD50Low3
1591215 s santa fe aveUSD50Low1
1592615 irvine aveUSD50Low0
1593920 berkshire aveUSD50Low3
159426462 silverado ctUSD50Low80.150.83
15953820 via palominoUSD50Low0
1596627 carcassonne roadUSD50Low0
15971000 elden wayUSD50Low0
159810778 chalon roadUSD50Low1
15991295 s cawston aveUSD50Low23
160025220 walker roadUSD50Low0
160111 la linda driveUSD50Low70.110.19
160235155 beach roadUSD50Low3
160310040 e happy valley rdUSD500Low3
16041805 w spring creek pkwyUSD50Low8
1605245 north saltair avenue in los angeles californiaUSD50Low2
16063140 grand viewUSD50Low2
16074730 w northern aveUSD500Low7
1608buyer offer letter templateUSD50Low211.073.94
1609home for sale in la crescenta caUSD500Low180.060.46
16102462 solar driveUSD50Low2
16114821 ash streetUSD50Low0
161235351 beach roadUSD50Low1
1613515 west paces ferryUSD50Low4
1614good questions to ask a real estate agentUSD50Low161.073.28
1615bridgewater pass hampton gaUSD50Low7
161614820 valley vista blvdUSD50Low1
16172215 kessler woods ctUSD50Low0
1618realtor agent feesUSD50Medium382.207.71
161910711 strait lnUSD50Low1
162014820 valley vista sherman oaksUSD50Low7
16211616 wabasso wayUSD50Low6
162224002 long valley rdUSD50Low0
16233745 w oregon aveUSD50Low0
1624610 e grinnell drUSD50Unknown
16251029 hanover driveUSD50Low0
16265771 rutland trceUSD50Unknown
1627818 n dohenyUSD50Low180.371.83
1628161 mangum st swUSD50Low1
16291905 sunset plazaUSD50Low1
163024148 reyes adobe wayUSD50Low2
16319268 robin driveUSD50Low0
1632948 thayer aveUSD50Low0
1633975 bel air roadUSD50Low0
163410814 e heritage ctUSD50Low0
163510971 chalon rdUSD50Low0
16361425 e desert coveUSD50Low7
163729858 knoll view drUSD50Low0
16383050 s bristol stUSD50Low2
16395122 e shea blvdUSD500Low9
1640320 n park vista stUSD50Low6
16415173 charlemagne way swUSD50Low0
16429958 kip driveUSD50Low0
1643627 carcassonne road floor planUSD50Low0
164410281 charing cross rdUSD50Low4
16452621 s marigold aveUSD50Unknown
16463544 ocean viewUSD50Low0
16475590 spring valley rdUSD500Low8
164825825 via quinto stUSD50Low5
16495939 fairing dropUSD50Low5
165017351 w sunset blvdUSD50Low4
1651writing a letter to buy a houseUSD500High1000.692.79
16521400 n hayworth aveUSD50Low2
16533256 e palo verdeUSD50Low2
16543791 winford dr tarzana ca 91356USD50Low1
16554482 dudley drUSD500Low0
16565505 e mclellan rdUSD50Low8
16576336 halbrent aveUSD50Low0
16582002 n las palmas aveUSD50Low0
165921481 cold spring lnUSD50Low3
16605855 e lafayette blvdUSD50Low0
166112509 w sunset blvdUSD50Low0
16621800 n doheny drUSD50Low0
166332012 cape point drUSD50Low6
16641195 milton ter seUSD50Low9
166510410 bellagio rdUSD500Low1
166625210 jim bridger rdUSD500Low0
1667323 san vicente blvdUSD50Low10
16684012 tennis club rdUSD50Low0
16691954 linda flora drUSD50Low0
16706 shoreview newport coast ca 92657USD50Low5
16717755 n foothill dr sUSD50Low0
16721259 beverly estates drUSD50Low0
167314450 n thompson peak pkwyUSD50Low7
16746434 bryn mawr drUSD50Low0
1675840 s peralta hills drUSD50Low1
16769829 walnut stUSD50Low3
167714175 mulholland drUSD500Low1
1678864 stradella road bel airUSD50Low0
167921808 pacific coast highwayUSD50Low0
16805460 white oak ave encinoUSD50Low14
16811380 shallowford roadUSD50Low0
16823386 mandeville canyon rdUSD50Low4
16833630 colosseum wayUSD50Low0
16845359 oak park aveUSD50Low50.170.24
168511700 iowa aveUSD50Low0
168629130 cliffside driveUSD50Low60.210.96
1687521 n canon driveUSD500Low2
1688744 n martel aveUSD50Low0
1689steps to selling a homeUSD500Medium544.4829.45
16901109 palos verdes dr wUSD50Low2
16917525 e gainey ranch rdUSD50Low14
1692115 carriage station drUSD50Low4
16933535 griffith park blvdUSD50Low6
1694real estate charges to sell a houseUSD50High975.5215.00
16954865 montcalm dr swUSD50Low4
16967700 e gainey ranch rdUSD50Low13
16971241 loma vista drUSD50Low0
16981710 monte cielo ctUSD50Low9
169930106 rhona ctUSD50Low0
170031475 jedediah smith rdUSD50Low6
1701715 north alpine driveUSD50Low1
17028632 shallow creek drUSD50Low0
1703opendoor tour assistantUSD50Medium345.7129.63
170411817 macoda lane chatsworth ca 91311USD50Low8
17051369 londonderryUSD50Low1
17061749 stone canyon rdUSD50Low0
17074110 paces ferryUSD50Low0
170812 horizon newport coast ca 92657USD50Low5
17091625 sawnee meadow laneUSD50Low8
171018250 n cave creek rdUSD50Low6
17114965 butner rdUSD500Low120.481.32
171222316 appleberry ctUSD50Low7
17132817 via alvaradoUSD50Unknown
17145101 kensington ctUSD500Low6
17156156 ramirez canyon rdUSD50Low0
17161051 s dobson rdUSD500Low4
17171731 rising glen rdUSD50Low0
1718housing market trend graphUSD500Low61.4810.07
1719sellers and buyers marketUSD50Low81.998.70
17201135 rivas canyon roadUSD50Low1
17214325 canoga aveUSD50Low3
17228109 skillman stUSD50Low9
17238726 wonderland aveUSD50Low4
1724good real estate questions to askUSD50Low201.114.73
17255139 seneca drUSD50Low1
17265525 e thomas rdUSD500Low5
17271714 stone canyon rdUSD500Low40.190.41
17281750 e ocean blvdUSD500Low8
1729384 ralph mcgill blvd neUSD50Low6
17305555 dixon trailUSD50Low0
17312404 san marco drUSD50Low0
17323029 castle heightsUSD50Low0
1733900 s 94th stUSD50Low4
1734buyer commissionUSD500Low95.0118.80
17355041 copa de oroUSD50Low6
17365723 bryn mawrUSD50Low0
1737preparing your home to sellUSD500High747.0024.51
17381712 beverly drUSD50Low0
1739726 n maple drUSD50Low0
17401740 bel air rdUSD50Low0
17412701 peyton springs circleUSD50Low2
1742houses in la crescentaUSD50Low160.120.44
17439 skycrest newport coastUSD50Low11
1744commission on a house saleUSD500Medium452.6210.70
1745preparing your house to sellUSD500Medium676.1526.69
17461380 summitridge driveUSD500Low2
17472449 mountain view courtUSD50Low160.840.96
17484701 flat shoals rdUSD500Low90.531.12
17499276 downey aveUSD50Low5
175022126 de la osa stUSD50Low1
1751235 s reeves drUSD50Low18
1752381 e greenbriar lnUSD50Low7
17537260 e eagle crest drUSD50Low10
1754cost of selling a house in texasUSD50High745.0820.34
1755letter to seller of house exampleUSD50High89
175614143 chandler blvdUSD50Low1
17572110 hill driveUSD50Low40.150.71
17585252 sandy shores ctUSD50Low20
17598100 old baucom rdUSD50Low3
176031619 lobo canyon rdUSD50Low1
1761common home seller questionsUSD50Low27
1762425 s kenmore aveUSD50Low5
1763factors affecting property valueUSD50Low2
176411150 sunset blvdUSD50Low0
176512828 ramona blvdUSD50Low13
17661700 kings roadUSD50Low0
17671701 clinton stUSD50Low7
17682002 loma vistaUSD50Low0
17692150 w alameda rd for saleUSD50Low31
17705135 e evergreen stUSD50Low1
17717333 valley view laneUSD50Low12
17721011 north beverly driveUSD500Low1
1773things to ask a realtorUSD500Low150.983.14
17741218 roberto laneUSD500Low1
177520455 e via de arbolesUSD50Low2
1776buyers checklistUSD500Low140.654.01
1777726 s nebraska stUSD50Low7
1778average negotiating house priceUSD50Low0
1779preparing a home for saleUSD500Low252.4810.82
17802350 osbun rdUSD50Low14
178124 monarch bay driveUSD50Low6
1782903 linda floraUSD50Low0
17838750 kester aveUSD50Low5
178414023 aubrey rdUSD50Low1
17851818 s quebec wayUSD50Low2
1786moores chapel roadUSD500Low2
17871954 linda floraUSD50Low1
17882243 windermere wayUSD50Low2
17894704 e paradise village pkwy nUSD50Low20
17905700 riverside driveUSD50Low4
17915838 e starlight wayUSD50Low2
1792814 humphries st swUSD50Low0
1793carmelina ave brentwoodUSD50Low0
1794fees for real estate agentsUSD5000Low332.6110.49
17951145 arden roadUSD50Low0
17962002 loma vista driveUSD50Low7
17973667 peachtree rd neUSD50Low8
17984829 old timber ridge roadUSD50Low1
17996255 w arby aveUSD500Low6
1800677 nimes roadUSD50Low1
1801100 pebble beach driveUSD50Low0
18021355 n sierra bonita aveUSD50Low6
18036271 peden rdUSD50Low4
18042725 s nellis blvdUSD500Low5
18054194 sinclair shores roadUSD50Low0
18067139 macapa driveUSD50Low1
1807727 n beverly glen blvdUSD50Low0
1808buying a house in a competitive marketUSD50Low8
1809things to ask your realtorUSD50Low180.974.93
1810901 isabel stUSD50Low8
1811good questions to ask a realtorUSD50Low170.923.35
181211260 houze rdUSD50Low2
181313023 sunset blvdUSD50Low1
18142228 pansy st nwUSD50Low40.130.36
18154636 chapel hill rdUSD50Low1
18168601 sunland blvdUSD50Low7
18178 midsummerUSD50Low0
1818915 benedict canyonUSD50Low4
1819baker ranch homes for saleUSD500Medium430.100.78
1820real estate slang phrases and terminologyUSD500Low12
182127140 malibu cove colonyUSD50Low6
1822219 south mapleton driveUSD50Low1
18234303 rawlinsUSD50Low1
1824451 s hawes rdUSD50Low4
18252228 n 52nd stUSD50Low6
18264221 beethoven stUSD50Low110.140.82
1827660 beckenham walk drUSD50Low0
18289450 e becker lnUSD50Low7
1829house sale calculator ontarioUSD50Unknown
18301002 e northfield blvdUSD50Low6
1831family letter for buying a houseUSD50High100
1832formal offer letter to purchase propertyUSD50Low2
183314207 n 180th aveUSD50Low0
18342267 chislehurst drUSD50Low1
1835ask a real estate agentUSD50Medium612.1011.80
183614903 s normandie aveUSD50Low8
183722309 dolorosa stUSD50Low0
18386720 e encanto stUSD50Low4
1839679 durant pl neUSD50Low15
18407847 torreyson drUSD50Low18
18411260 s beverly glen blvdUSD50Low4
184217318 tramonto driveUSD50Low16
18433029 castle heights aveUSD500Low7
18444488 pair valley driveUSD50Unknown
18454686 lake breeze driveUSD50Low2
184610555 vestone wayUSD50Low0
184714680 freemanville rdUSD50Low3
184823042 calvert stUSD50Low0
18495024 bryce aveUSD500Low0
1850705 w queen creek rdUSD50Low14
18515200 moore roadUSD50Low0
18526105 blue stone rdUSD50Low13
185310040 east happy valley roadUSD50Low1
18541036 roscomare rdUSD50Low1
18551074 peachtree walk neUSD500Low3
18563205 manor ridge driveUSD50Low0
18576323 reseda blvdUSD50Low3
18589272 robin drUSD500Low0
1859writing a letter for buying a houseUSD50Low28
186030729 rue langloisUSD50Low0
18611142 calle vista drUSD50Low1
18621709 georgina aveUSD50Low0
1863100 shady brook walkUSD50Low1
186410517 sarah stUSD50Low2
186511670 sunset blvdUSD50Low11
186637007 n romping rdUSD50Low0
1867baker ranch caUSD500Low40.121.27
186812229 s vermont aveUSD50Low5
1869161 glen acres ctUSD50Low8
1870165 dix lee on drUSD50Low0
18712217 vernon oaks wayUSD50Low0
18726721 foxpointe rdUSD50Low0
1873randall mill wayUSD50Low8
18741382 rural hill rdUSD500Low9
187525636 oak meadow drUSD50Low18
18765460 white oak ave for saleUSD50Low26
187724910 pacific coast highwayUSD50Low0
18788921 crenshaw blvdUSD50Low5
187912833 chalon rdUSD500Low0
188012834 highwood streetUSD50Low4
18811288 s oakland ave pasadena ownerUSD50Low14
18823515 alamedaUSD50Low0
18833865 northside dr nwUSD50Low0
1884955 vista ridge laneUSD50Low0
18851207 golden view courtUSD50Low0
188626342 forest ridge drUSD50Low8
1887286 w palomino drUSD500Low8
18886859 cornwallis rdUSD50Low160.140.38
18897046 n 59th plUSD500Low100.100.65
1890908 e bastanchury rdUSD50Low0
189112466 michigan stUSD50Low2
189223111 mariposa de oro stUSD50Low60.190.51
18933347 bonnie hill drUSD50Low0
189437 del mar newport coastUSD500Low1
18955460 white oakUSD50Low8
189612601 s tuthill rdUSD50Low5
18972126 daly stUSD50Low0
1898301 n carmelinaUSD50Low0
18991380 summitridgeUSD50Low1
19003040 coombs creek drUSD50Low2
1901725 via del monteUSD50Low2
19028517 franklin aveUSD500Low40.180.58
1903agent commission feeUSD50Low301.9515.00
19041630 amalfi drive pacific palisadesUSD50Low9
19059408 peninsula drUSD50Low0
1906real estate agent cost for sellerUSD50Medium443.9015.00
19071376 mount paranUSD50Low0
19082801 n litchfield rdUSD50Low8
19095504 cavendish courtUSD500Low40.501.11
19105521 paradise valley rd hidden hills ca 91302 virtual tourUSD50Low1
191112300 montecito rdUSD50Low2
1912808 san vicenteUSD50Low0
19139520 hidden valley rdUSD500Low1
1914homes for sale in montrose caUSD500Low170.080.52
19152035 smoke rise chaseUSD50Low3
1916480 n orlando aveUSD50Low1
19173100 mandeville canyonUSD50Low2
1918house buying letterUSD5000High990.825.36
1919101 ocean santa monicaUSD50Low3
19201247 mayfair dr neUSD50Low0
19212173 w live oak drUSD50Low3
1922buyers agent commission rateUSD50Low223.0614.84
19231172 w wesley rd nwUSD50Low4
19241259 beverly estate drUSD500Low3
19251731 rising glenUSD500Low1
19267100 balboa blvdUSD50Low2
19277411 e jackrabbit rdUSD50Low7
19282300 rolesville roadUSD50Low0
19293772 caribeth drUSD50Low2
193016925 gault stUSD50Low80.150.25
19312404 san marco driveUSD50Low0
19323540 woodhaven roadUSD500Low1
19334050 chattahoochee rdUSD50Low0
19344214 n stratford rd neUSD50Low6
19354256 country club driveUSD50Low9
19365521 paradise valley roadUSD50Low1
19373995 randall mill roadUSD50Low0
1938selling house calculator ontarioUSD50Low0
19392222 s mesa stUSD50Low3
19401061 ravoliUSD50Low0
19412440 holly drUSD50Low1
19421663 n crescent heights blvdUSD50Low2
1943carmelina brentwood caUSD50Unknown
194410648 capello wayUSD50Low2
19451369 londonderry red roomUSD50Low0
194621055 ingomar stUSD50Low0
194733261 decker school rdUSD50Low3
19484009 preston lakes circleUSD50Low3
19494701 flat shoals roadUSD50Low9
19506450 rodgerton drUSD50Low2
19511430 s beverly glen blvdUSD50Low2
1952216 johns creek laneUSD50Low0
19532524 preston rdUSD500Low220.350.72
19543725 ocean blvdUSD50Low100.060.23
19553907 leisure woods drUSD50Low0
1956418 n sweetzer aveUSD50Low1
19574411 noeline ave encino caUSD50Low0
1958572 edgewood aveUSD50Low7
19591318 n crescent heights blvdUSD50Low130.370.60
196021845 mojave chatsworth ca 91311USD50Low0
1961350 n kilkea drUSD50Low3
19624440 hayvenhurst ave hype houseUSD50Low0
1963714 west potrero road in westlake villageUSD50Low0
1964good questions to ask realtorUSD50Low141.204.94
1965negotiating a house saleUSD50Low180.362.31
19665521 paradise valley rdUSD500Low40.271.08
19677860 st marlo fairway driveUSD50Low6
19682405 glendower aveUSD50Low1
19695200 keller springs rdUSD50Low7
19701200 laurel wayUSD50Low0
19711728 chevy chaseUSD50Low0
19722059 high tower driveUSD50Low3
19732156 butler bridge roadUSD50Low3
19746902 los tilos rd floor planUSD50Low0
1975hercules drive hollywood hillsUSD50Low0
19761155 n fuller aveUSD50Low6
1977592 whaleys lake drUSD50Low2
19781000 laurel way floor planUSD50Low5
197910660 strait laneUSD500Low1
19801580 sorrento driveUSD50Low0
198123200 red rock rdUSD50Low120.140.71
19822814 e cactus rdUSD50Low0
1983398 dunleven manor walkUSD50Low0
19845026 forest bendUSD50Low0
1985buyer broker feeUSD500Low70.706.27
1986480 john wesley dobbs ave neUSD50Low7
1987620 s gramercy plUSD500Low14
19889321 cherokee laneUSD50Low2
19891000 e bishop stUSD50Low5
19901446 cimarron parkwayUSD50Low1
199132802 pacific coast highwayUSD50Low2
199212012 crest ctUSD50Low0
19931287 n alma school rdUSD50Low1
19941350 mount paran roadUSD50Low0
19951744 washington wayUSD50Low80.170.82
19967952 w 4th stUSD50Low1
1997211 spaldingUSD50Low6
199824116 wildwood canyon rdUSD50Low2
19999127 thrasher avenueUSD500Low0
200010425 revuelta wayUSD50Low0
200115095 n thompson peakUSD50Low18
20021920 e bell rdUSD500Low6
20032572 hutton drUSD50Low5
20042722 knight stUSD50Low1
20054054 mantova drUSD50Low1
20069288 sierra mar drUSD50Low0
20071549 rising glen roadUSD50Low0
20082950 mt wilkinson pkwy seUSD50Low16
200923762 malibu roadUSD50Low0
201024220 long valley rdUSD50Low0
20114288 olde mill laneUSD50Low0
2012first steps to selling your homeUSD500Medium677.4529.77
20139308 readcrestUSD50Low1
20144535 encino aveUSD50Low0
20154041 woking wayUSD50Low3
20161026 ridgedale drUSD50Low0
20175403 jed smith roadUSD50Low1
20188027 floral aveUSD50Low1
20193830 e lakewood pkwyUSD500Low7
2020748 cimarron ct argyle txUSD50Low120.120.46
2021227 tigertail roadUSD50Low0
20222950 mount wilkinson pkwyUSD50Low22
2023355 n saltairUSD50Low7
2024real estate broker fee for sellerUSD50Low213.7112.81
2025house for sale in la crescentaUSD500Low240.060.45
2026os national opendoorUSD50Medium345.7121.21
20278055 e thomas rdUSD500Low6
202810452 shangri la drUSD50Low1
202912471 mulholland drUSD50Low3
2030real estate purchase offer letterUSD500Low260.863.47
2031tips for preparing your home for saleUSD50Medium351.088.21
20325343 legends drUSD50Low101.041.32
2033927 kagawa streetUSD50Low1
20349380 sierra mar drUSD50Low50.821.96
2035119 crescent woode driveUSD50Unknown
20364440 hayvenhurstUSD50Low0
20375943 walnut hill laneUSD50Low120.220.80
20386075 rodgerton drUSD50Low3
2039720 n alta drUSD50Low3
2040house resale valueUSD50Medium371.708.71
204115520 hamner driveUSD50Low4
20426721 e mcdowell rdUSD50Low6
20432710 bowmontUSD50Low2
20443496 berry drive studio cityUSD50Low1
20454865 montcalm drUSD50Low29
2046505 cascade riseUSD50Low8
20477625 e camelback rdUSD500Low3
2048141 ashdale aveUSD50Low1
20493917 miramar dallasUSD50Low0
205015434 mulholland drUSD50Low10
205117 telescopeUSD50High100
20522550 aberdeen aveUSD50Low1
2053521 north canon driveUSD50Low2
20545701 e glenn stUSD50Low6
2055295 traditions drUSD50Low6
2056299 n saltairUSD50Low4
20576202 creekstone pathUSD50Low0
2058630 w 6th stUSD500Low4
2059101 ocean aveUSD500Low31.201.96
20601711 s kingsley drUSD50Low0
20614777 s fulton ranchUSD50Low9
20625107 los hermosos wayUSD50Low0
20639424 copper hill laneUSD50Low4
20643925 sweetwater pkwyUSD50Low3
2065642 perugia wayUSD500Low30.140.31
20661115 emerald bayUSD50Low0
20673608 multiview drUSD50Low50.170.86
20682201 bayside driveUSD50Low70.120.24
20692222 s mesa st san pedro ca 90731USD50Low0
20702705 e camino la zorrelaUSD50Low0
207130552 hilltop wayUSD50Low0
2072housing market graphUSD5000Low41.382.81
20731 avalon vista newport coastUSD50Low3
207411435 bellagio roadUSD50Low2
207511637 e cochise drUSD50Low10
20761849 amberly ledge wayUSD50Low1
20773251 shelby drUSD50Low50.180.39
207812727 highwood stUSD50Low0
2079letter to purchase a homeUSD50High1000.816.21
20802627 benedict canyon driveUSD50Low2
20815900 ebenezer church rdUSD50Low0
2082100 n irving blvdUSD50Low1
20831240 sierra alta way floor planUSD50Low0
2084729 edgewood aveUSD50Low2
20858501 w university aveUSD500Low5
20864954 peachtree dunwoody rdUSD50Low2
20871000 w macarthur blvdUSD50Low0
20885200 keller springs roadUSD50Low7
20896039 e mountain view rdUSD50Low0
20908111 andasol aveUSD50Low0
20911288 s oakland aveUSD500Low0
20921450 e bethany home rdUSD50Low8
20931602 n king stUSD50Low3
20942329 sunset ridge circleUSD50Low0
20952720 ellison drUSD50Low4
2096117 s burlingame aveUSD50Low1
20971287 n alma schoolUSD50Low3
209827250 murrieta rdUSD50Low10
209934572 via verdeUSD50Low10
2100460 trousdale plUSD50Low2
2101645 adelaide drUSD50Low0
21021369 londonderry pl floor planUSD50Low0
21031883 rising glenUSD50Low0
21044411 suwanee dam rdUSD50Low2
2105baker ranch lake forest homes for saleUSD50Medium520.111.12
210610 perimeter summit blvd ne brookhaven ga 30319USD50Low0
21071050 w conway drive nwUSD50Low100.621.32
21081127 e del mar blvdUSD50Low14
21091320 e bethany home rdUSD50Low16
21102484 roscomareUSD50Low5
21113060 pharr court northUSD500Low6
21124984 e camelback rdUSD50Low0
211354 beverly park wayUSD50Low1
2114130 s cisco stUSD50Low2
21151345 cabrillo park drUSD500Low7
2116405 fairburn rd swUSD50Low9
21177500 e deer valley rdUSD500Low6
21181096 mcdaniel st swUSD50Unknown
21191940 bel air rdUSD50Low5
21202727 e thomas rdUSD50Low6
2121333 melrose drUSD50Low13
212210030 w indian school rdUSD50Low5
212310410 bellagio roadUSD50Low0
212410801 e happy valley rdUSD500Low5
21251575 spinnaker drUSD50Low1
21261961 n hartford stUSD500Low5
212731521 bluff driveUSD50Low4
21284040 san marco wayUSD50Low0
2129121 sinclair aveUSD50Low6
213067 beverly parkUSD50Low1
2131137 towne park drUSD50Low5
21321400 vista moragaUSD50Low0
213315 skycrest newport coast ca 92657USD50Low5
2134314 n barrington aveUSD50Low60.180.84
21355335 e shea blvdUSD500Low9
2136paces ferry rdUSD50Low1
2137preparing home to sellUSD50Medium625.5021.14
2138template for making an offer on a houseUSD50Low210.571.38
21393680 dixie canyonUSD50Low4
2140388 s los roblesUSD50Low0
21416965 preston estates atlanta gaUSD50Low5
2142lago vista driveUSD50Low41.5811.08
2143240 w juniper aveUSD50Low6
21442405 trenton park lnUSD50Low1
2145320 old hickory blvdUSD500Low2
21463467 adina drUSD50Low2
21474110 west paces ferry roadUSD50Low0
2148638 n sierra bonitaUSD50Low0
2149805 lake mist coveUSD50Low0
2150818 n doheny dr 1402USD50Low20
21519520 hidden valleyUSD50Low0
2152604 n palm drUSD50Low3
215390 archipelagoUSD50Low7
2154real estate market trends 2019USD50Low0
2155111 via san sebastianUSD50Unknown
215616635 n cave creek rdUSD50Low3
Homevestorsfranchise.com

Open original tab

Homevestorsfranchise.com
RowABCDEFG
1https://homevestorsfranchise.com/Source link A1
2
3May 1, 2020 - April 30, 2021
4KeywordCurrencyAvg. monthly searchesCompetitionCompetition (indexed value)Top of page bid (low range)Top of page bid (high range)
5investing in real estateUSD50000Medium613.709.99
6buying rental propertyUSD5000Medium361.254.89
7buying an investment propertyUSD5000Medium491.998.06
8best real estate investmentsUSD5000Medium533.159.95
9rental propertyUSD50000Medium360.502.11
10investment propertyUSD50000Medium533.399.07
11rental property investmentUSD5000Medium552.167.38
12buying propertyUSD5000Low280.975.47
13distressed propertyUSD5000Medium470.933.24
14getting started in real estateUSD500Medium552.006.56
15estate investUSD500Medium464.3210.59
16owning rental propertyUSD5000Low201.175.10
17best property investmentUSD500Medium483.4810.02
18investment housesUSD5000Medium372.829.56
19real estate finance and investmentsUSD500High1002.7112.90
20real estate investing coursesUSD5000High834.5711.37
21property investment coursesUSD50Low333.629.25
22house investmentUSD5000Medium392.749.40
23rental investmentUSD500Medium431.496.12
24best real estate marketsUSD500Low121.467.57
25selling a rental propertyUSD5000Low324.6023.08
26property investment opportunitiesUSD50Low184.0011.70
27distressed real estateUSD500Medium381.225.61
28real estate opportunitiesUSD500Medium372.799.48
29real estate investment opportunitiesUSD500Medium514.0310.63
30best rental marketsUSD500Low140.943.53
31top real estate investorsUSD500Medium513.6013.54
32getting into real estate investingUSD500Medium502.479.48
33learning real estateUSD5000High692.298.45
34learn real estate investingUSD500High743.389.34
35real estate rental propertyUSD500Medium370.943.70
36property investment guideUSD50Medium383.7611.70
37getting started in real estate investingUSD500Medium523.7613.64
38selling investment propertyUSD500Medium453.7923.92
39real estate investment propertiesUSD500Medium534.8910.81
40best rental property marketsUSD500Low230.133.59
41successful real estate investorsUSD500Medium343.0011.63
42start investing in real estateUSD500Medium623.7810.75
43find real estate investorsUSD500High813.9618.36
44real estate investor leadsUSD500Medium567.6320.50
45best markets for real estate investingUSD500Medium383.9213.57
46best real estate markets to invest inUSD500Medium364.3911.64
47house investorsUSD5000High7612.0048.64
48best real estate investing coursesUSD500High673.339.13
49guide to real estate investingUSD500High832.9413.02
50investment housingUSD500Low271.619.48
51distressed housesUSD500Low231.034.83
52best rental propertyUSD500Low160.762.75
53real estate investment trainingUSD500Medium563.628.99
54real estate investment businessUSD500Medium483.7610.02
55buying a house as an investmentUSD500Low291.889.44
56real estate investment optionsUSD500Medium444.8111.95
57distressed real estate investingUSD500Low273.3816.89
58getting into rental propertiesUSD500Low251.194.89
59invest in rental homesUSD500Medium451.405.12
60building a rental propertyUSD500Low310.572.09
61house flipping investorsUSD500High772.058.33
62good investment propertiesUSD50Medium453.029.33
63good real estate investmentsUSD5000Low242.298.07
64rental property marketUSD50Low230.815.58
65real estate finance & investmentsUSD500High992.6119.68
66best investment property in chicagoUSD50Medium632.548.76
67about real estate investmentUSD50Medium512.738.79
68real estate investment ideasUSD50Medium583.9910.09
69real estate investing coachUSD500High722.6913.19
70selling house to investorUSD500Medium6714.3746.53
71finding investment propertiesUSD500Medium612.7211.70
72real estate flipping housesUSD500Medium411.156.52
73best markets to buy rental propertyUSD500Low220.123.18
74investment properties in njUSD500High681.407.29
75selling home to investorUSD500Medium5514.5349.37
76good rental propertyUSD50Low150.823.50
77buying property nowUSD50Low0
78best rental real estate marketsUSD500Low300.123.16
79real estate investment financeUSD500Medium625.0115.74
80best rental properties to buyUSD50Low150.824.65
81investors that buy housesUSD500Medium3812.3056.88
82buy to sell property investmentUSD50Unknown
83property investment businessUSD50Medium363.438.12
84best property to buyUSD50Low280.9114.48
85property investment leadsUSD50High67
86buying property in chicagoUSD500Medium520.613.30
87chicago investment propertiesUSD500Medium481.829.41
88property investment trainingUSD50High711.558.80
89marketing for real estate investorsUSD500Medium504.6815.02
90real estate investment franchiseUSD500High734.2910.00
91everything you need to know about real estate investingUSD50High682.476.81
92investing in real estate rentalsUSD500Medium533.348.30
93selling your home to an investorUSD500Low3317.0849.53
94best housing markets to invest inUSD50Low231.918.45
95buying a rental houseUSD500Low251.266.00
96property and investmentUSD50Low192.5113.26
97real estate investment toolsUSD500Medium654.1626.33
98best house investmentsUSD50Low151.227.95
99starting a real estate investment businessUSD50Medium494.8911.28
100real estate investing rental propertiesUSD500Medium533.588.66
101getting into property investmentUSD50Low333.6110.16
102top rental propertyUSD50Low6
103buying a rental homeUSD500Medium371.045.00
104best real estate opportunitiesUSD50Low252.619.01
105guide to buying propertyUSD50Low2
106selling your rental propertyUSD50Medium336.3427.86
107invest in housing marketUSD50Medium343.559.76
108buying a house as an investment propertyUSD50Low213.5213.82
109building an investment propertyUSD50Low201.847.12
110best lead generation for real estate investorsUSD50High908.2944.93
111best rental property investmentsUSD50Medium482.008.85
112best rental investmentsUSD50Medium391.469.01
113best rental investment marketsUSD50Low250.995.75
114investors buying homesUSD500High7515.4161.33
115investment in house propertyUSD50Medium433.509.74
116investor propertiesUSD500Medium473.3214.41
117finding rental propertyUSD500Medium481.112.54
118real estate investor lead generationUSD50High796.0018.98
119buying a home as an investmentUSD500Medium411.989.76
120chicago real estate investmentUSD500Medium343.8013.71
121selling your house to an investorUSD500Low2313.8956.25
122property investment ideasUSD50Medium414.878.30
123learn about property investmentUSD50Medium633.5013.01
124investment properties to buyUSD50High791.507.63
125rental property good investmentUSD500Low121.898.30
126professional real estate investorUSD50Medium424.4815.34
127buying real estate for investmentUSD500Medium554.6112.65
128real estate investment careersUSD500Medium402.409.93
129real estate and investmentUSD50Low313.999.74
130owning investment propertyUSD50Low233.8811.69
131buying a house is a good investmentUSD5000Low61.087.40
132top rental property marketsUSD50Low240.103.27
133best investment housesUSD50Low271.303.84
134real estate investment marketUSD50Medium444.0813.55
135property to investUSD5000Medium493.008.79
136properties for investorsUSD50High755.1214.60
137property investment toolsUSD50Medium633.268.51
138chicago real estate investorsUSD50High707.2016.66
139rental property investment coursesUSD50Medium662.117.50
140home and investmentUSD50Low5
141buying a house as a rental propertyUSD50Low231.514.71
142the real estate investorUSD50Medium522.8312.33
143selling your house to a real estate investorUSD50Low156.1541.78
144property investment optionsUSD50High786.4711.09
145buying property guideUSD50Low7
146investor homesUSD50Medium566.2533.75
147getting into the property marketUSD50Unknown
148property investment marketUSD50Unknown
149all invest real estateUSD50Low0
150best real estate investment opportunitiesUSD50Low214.5612.83
151housing investorsUSD50High715.4329.50
152investing in real estate nowUSD50Medium605.2917.10
153best investment properties to buyUSD50Medium593.7010.00
154rental house investmentUSD50Medium431.225.13
155best buy propertyUSD50Low6
156buying property as a businessUSD50Medium360.963.78
157buying houses to flipUSD500Medium351.095.83
158investors buying all the homesUSD50Medium518.6539.05
159getting started in property investmentUSD50Medium403.5011.69
160best real estate markets to invest in right nowUSD50Medium342.338.30
161buy real estate propertyUSD50Medium371.498.89
162buying a house from an investorUSD50Medium493.5511.94
163rental property ideasUSD50Low11
164buy rentalUSD500Low190.993.51
165buying a house is an investmentUSD50Low19
166investing in buildingsUSD50Medium391.355.22
167best rental markets in njUSD50Low3
168property real estate investmentUSD50Low213.5010.50
169investing in your homeUSD50Low187.1110.66
170best property to buy for investmentUSD50Medium652.5010.78
171best real estate properties to invest inUSD50Medium553.8910.67
172real estate markets to invest inUSD50Medium442.5410.88
173starting property investmentUSD50Medium644.169.74
174real estate investing resourcesUSD50Medium524.1713.33
175rental property njUSD500Medium450.351.25
176flipping rental propertiesUSD50Low271.413.97
177invest with the houseUSD50Low19
178best resources for real estate investingUSD50High925.1919.47
179distressed property investingUSD50Low333.428.98
180buying house is good investmentUSD50Low13
181flipping investmentUSD50Medium351.436.55
182getting investors for real estateUSD50High712.8120.37
183house investment propertyUSD50High763.4410.03
184buying your rental propertyUSD50Low0
185best markets for investment propertyUSD50Low294.9813.77
186real estate is best investmentUSD50Medium504.2612.47
187successful property investorsUSD50Medium33
188investors for propertyUSD50High904.8021.27
189invest estatesUSD50Low324.8911.03
190property investment coachingUSD50Low29
191getting started in rental propertyUSD50Low221.616.50
192i on real estate & investmentsUSD50Low122.554.66
193real estate is good investmentUSD50High671.133.29
194real estate investing flipping housesUSD50Medium571.5110.77
195property investment inUSD50Low11
196best houses to invest inUSD50Low271.594.19
197everything to know about real estate investingUSD50Medium482.005.80
198rental real estate marketUSD50Low131.903.63
199investment and real estateUSD50Medium383.449.72
200best real estate propertiesUSD50Low26
201nj real estate investorsUSD500Medium583.4110.88
202top property marketUSD50Low0
203starting rental propertiesUSD50Low250.905.72
204rental properties to invest inUSD50Medium492.338.68
205good real estate marketsUSD50Low7
206all about real estate investingUSD50Low205.3610.53
207best markets to own rental propertyUSD50Low240.945.65
208buy sell invest real estateUSD50Low332.778.30
209a real estate investorUSD50Medium572.638.30
210opportunities in real estate investmentUSD50Medium571.6520.53
211about property investmentUSD50Low0
212all real estate and investmentsUSD50Low92.728.30
213best real estate investments right nowUSD50Medium636.2112.88
214guide to real estateUSD50Medium551.323.61
215investment property opportunitiesUSD50High742.979.10
216selling investments to buy a houseUSD50Low134.1513.15
217rental property courseUSD50Medium510.883.07
218business property investmentUSD50Low29
219buying property right nowUSD50Low7
220good real estate markets to invest inUSD50Low312.729.95
221best real estate markets right nowUSD50Low182.409.47
222starting a property investment businessUSD50Medium333.5210.75
223best investment homesUSD500Low161.326.59
224top markets for real estate investingUSD50Medium372.9210.85
225all about property investmentUSD50Low0
226everything you need to know about investing in real estateUSD50High791.7810.67
227buying and investment propertyUSD50Medium431.928.57
Homevestor.Phoenix

Open original tab

Homevestor.Phoenix
RowABCDEFG
1https://www.homevestors.com/phoenix/Source link A1
2
3KeywordCurrencyAvg. monthly searchesCompetitionCompetition (indexed value)Top of page bid (low range)Top of page bid (high range)
4we buy houses for cashUSD5000Medium6317.2864.80
5we buy housesUSD50000High6915.1955.92
6sell my house fast for cashUSD5000Medium5115.5368.25
7sell my house fastUSD5000Medium5717.0063.15
8sell house fastUSD5000Medium4417.6061.17
9cash for housesUSD5000Medium3719.4174.75
10we buy homes for cashUSD5000High6917.0365.33
11sell your house fastUSD5000Low3216.3262.11
12sell home fastUSD5000Low2913.5361.57
13selling propertyUSD500Medium568.3430.97
14sell my houseUSD5000High7220.5071.84
15we buy homesUSD5000High6916.8661.95
16cash home buyersUSD5000Medium4517.2068.39
17buy houses for cashUSD5000Medium459.2350.47
18sell my home fastUSD5000Medium4024.1282.50
19sell my house fast phoenixUSD500Medium4310.8051.84
20ugly housesUSD50000Low136.7145.00
21sell my homeUSD5000Medium5721.9878.58
22buy my houseUSD5000Medium4920.9779.72
23sell house for cashUSD5000Medium4019.5469.41
24need to sell my house fastUSD500Low2718.9975.27
25sell my house for cashUSD5000Medium5320.2170.05
26sell your home fastUSD500Medium3821.7886.89
27sell my home for cashUSD500Medium5025.6798.57
28buy homes for cashUSD5000Medium5513.2766.58
29sell my house as isUSD500Medium4917.4058.01
30cash for my houseUSD500Low2820.6065.66
31cash house buyersUSD500Medium6415.8272.00
32sell home for cashUSD500Medium5721.3781.22
33sell house fast for cashUSD500Medium3419.3460.00
34buy my house fastUSD500Low2917.8664.27
35sell my propertyUSD500Medium3816.6150.27
36we buy houses fastUSD500Low2216.1954.88
37selling a homeUSD5000Medium5812.0048.81
38buying and selling housesUSD500Medium465.0028.07
39we buy your houseUSD500Low1517.3166.49
40sell your house for cashUSD500Low618.1064.96
41buy my house for cashUSD500Medium5821.8084.33
42i buy houses cashUSD500Medium4517.9066.64
43we buy houses phoenixUSD500Medium3913.9058.48
44selling house as isUSD5000High769.2845.88
45i need to sell my house fastUSD500Medium3724.6373.37
46sell property fastUSD500Low1313.9350.69
47buy your house for cashUSD500High6722.2284.50
48fast home buyersUSD500Medium6325.7071.99
49selling a house to a cash buyerUSD500High719.0053.43
50we buy ugly homesUSD500High8221.2771.07
51sell fastUSD500Medium427.4519.91
52sell your house fast for cashUSD500Low920.3960.30
53buy and sell propertyUSD500Medium422.8517.80
54selling and buying a homeUSD500Medium464.0325.35
55sell my home fast for cashUSD500Low3124.2890.29
56cash for your houseUSD500Low2315.5361.38
57sell housesUSD5000Medium659.2947.62
58i need to sell my houseUSD500High7226.1479.77
59need to sell my houseUSD500Medium3823.1674.19
60people that sell housesUSD500Low136.5622.08
61sell house fast phoenixUSD500Low2615.3569.43
62sell home fast for cashUSD500Low2524.14100.00
63we buy houses as isUSD500Medium5117.1477.15
64we buy your homeUSD50Medium4725.2971.92
65buy my home for cashUSD500High7728.54116.13
66cash buyer propertyUSD500Medium423.9022.69
67need to sell house fastUSD500Low925.0073.02
68we buy propertyUSD500Medium519.3829.98
69i buy ugly housesUSD500Medium6020.0071.33
70sell your property fastUSD500Low1016.5258.45
71we buy houses fast for cashUSD500Medium3816.6862.39
72ugly homeUSD500Low227.0236.00
73we buy property for cashUSD50High7212.2145.54
74buy your home for cashUSD50High8430.8490.90
75cash housesUSD500Medium447.9244.34
76sell home as isUSD5000High7810.0151.82
77sell ugly houseUSD500Medium5015.2052.75
78we buy your house for cashUSD500Low2921.8278.00
79fast cash for houseUSD500Low1312.3752.50
80buy houses as isUSD5000Medium525.7933.18
81sell my house phoenixUSD500Low2216.2660.00
82we buy homes fastUSD500Low3121.4163.94
83we sell housesUSD500Medium425.9228.29
84sell homesUSD5000Medium637.0036.00
85i buy homes for cashUSD50High7926.6179.27
86selling your house as isUSD500High6814.8060.00
87sell your home for cashUSD500Low3121.2993.56
88buy house fastUSD500Low159.8757.04
89we buy for cashUSD50Medium6510.4126.00
90buy to sell propertyUSD50Medium525.1917.13
91we buy your home for cashUSD50Medium5336.00101.93
92selling your home as isUSD500High8113.1659.03
93house cashUSD50Medium466.2045.06
94buy house in phoenixUSD500Medium411.3814.84
95sell my ugly houseUSD500Low2920.5790.00
96fast cash home buyersUSD500Low1917.1959.49
97sell my property fastUSD50High7523.3273.31
98sell your house fast phoenixUSD50Low9
99buy my home fastUSD50Medium5928.57107.25
100buy houses fastUSD50Medium3913.7242.44
101we buy and sell housesUSD500Low511.8153.55
102sell your home fast for cashUSD50Medium3431.9994.24
103sell my property for cashUSD50High8916.1250.71
104need to sell home fastUSD50Low1128.52121.77
105cash property buyersUSD50Medium6311.7641.16
106house fastUSD50Medium515.1323.93
107buy homes fastUSD50Low2811.5056.45
108sell property for cashUSD50Medium6210.9351.53
109buy my house as isUSD50High7918.8060.15
110need to sell your house fastUSD50Low1129.2167.45
111we buy properties fastUSD50Medium6210.5443.23
112buy sell houseUSD500Medium546.7933.59
113we buy your propertyUSD50Medium4014.8636.02
114sell my ugly house fastUSD50Low3220.1798.21
115buy ugly homesUSD500Medium4516.0090.00
116sell home as is fastUSD50High9541.38113.92
117sell my phoenix house fastUSD50Low0
118sell property fast for cashUSD50Low29
119cash home buyers phoenixUSD50Medium5118.7378.00
120sell my house fast in phoenixUSD50Low2716.2666.50
121need to sell my home fastUSD50Medium5025.6975.42
122need a house fastUSD50High967.2136.77
123sell ugly house fastUSD50Low2816.0446.33
124we buy ugly houses phoenixUSD50Medium6331.6886.49
125we buy and sell homesUSD50Medium3615.9238.69
126houses phoenixUSD50000Low241.1710.84
127selling property as isUSD500High734.5025.00
128i need to sell my home fastUSD50Low1920.0076.55
129cash for houses phoenixUSD50Low6
130buy my house fast for cashUSD50Medium6316.36117.30
131sell your property for cashUSD50High67
132i buy ugly homesUSD50Medium6624.7299.71
133people selling housesUSD50Medium613.6314.63
134buy home in phoenixUSD500Medium351.3110.44
135buying ugly housesUSD500High7219.9170.91
136sell my home as isUSD500High6925.7283.09
137selling a house to buy a houseUSD50Medium551.4920.12
138we sell houses fastUSD50Low2222.0065.11
139we buy houses phone numberUSD50Medium5415.0163.51
140buy uglyUSD50Medium6212.5227.48
141phoenix home buyersUSD50Low3012.4450.60
142we buy houses in phoenixUSD50Low3016.0260.00
143we buy homes as isUSD50Medium6513.6180.10
144i sell my houseUSD50Medium5813.5255.92
145houses are selling fastUSD50Medium656.5246.57
146buy a house fastUSD50Medium433.0223.43
147we buy homes phoenixUSD50Low1430.65118.98
148buying and selling your homeUSD50High777.4530.00
149buy house fast cashUSD50Medium6025.0084.17
150fast home sellingUSD50Low2143.90151.07
151we buy your property for cashUSD50Medium48
152sell my house in phoenixUSD50Low8
153fast cash buyersUSD50High9411.7041.93
154we buy houses inUSD50High1009.6228.23
155sell home fast phoenixUSD50Low31
156buy sell homeUSD500Medium636.9625.19
157need to sell my homeUSD50Medium5036.4089.91
158to sell my houseUSD50High9528.0074.75
159sell my home fast phoenixUSD50Low20
160selling for houseUSD5000Medium530.753.79
161fast property sellUSD50Unknown
162sell your home phoenixUSD50Low12
163selling homes phoenixUSD50Low3
164we buy properties cashUSD50Medium50
165cash for home buyersUSD50High8421.9387.12
166buy my house in phoenixUSD50Low0
167need sell home fastUSD50Low0
168we buy your house fastUSD50Low3315.0048.34
169buy my property fastUSD50Low0
170sell your ugly houseUSD50Low1829.81158.13
171sell your house phoenixUSD50Unknown
172sell your house in phoenixUSD50Low2
173buy my property for cashUSD50High8620.46116.83
174buy my house as is for cashUSD50High8639.54114.14
175sell your home fast phoenixUSD50Unknown
176cash fast house sellUSD50Low31
177we sell your houseUSD50High7523.0078.00
178we sell houses fast for cashUSD50Medium6519.5276.32
179sell homes fast cashUSD50Medium5910.1345.32
180homevestors logoUSD50Low916.0075.00
181we buy houses forUSD50High100
182selling your house to a cash buyerUSD50High9311.7145.00
183fast sell propertyUSD50Low7
184sell house phoenixUSD50Low191.4175.47
185buying an ugly houseUSD50Medium428.5776.72
186buying a house and selling yoursUSD50Medium511.0120.18
187fast cash for my houseUSD50High71
188need to sell property fastUSD50Low25
189i need to sell my homeUSD50High7531.1969.00
190need to sell fastUSD50High7612.3529.97
191buying property to sellUSD50High100
192sell my house fast inUSD50Low2
193cash for houses fastUSD50Medium50
194sell my home phoenixUSD50High8050.1393.51
195sell fast houseUSD50High9730.0083.14
196www we buy ugly houses comUSD50Low9
197phone number for we buy ugly housesUSD50High9417.0875.07
198buy fast sell fastUSD50Medium43
199selling home in phoenixUSD50Low1
200we buy phoenix housesUSD50Low0
201selling my house to a cash buyerUSD50Medium6417.6690.53
202selling a home in phoenixUSD50Low8
203homes are selling fastUSD50Medium4514.5162.99
204an ugly houseUSD50Low213.8255.28
205need to buy a house fastUSD50Medium601.788.57
206house buyers in my areaUSD50High799.6450.00
207cash fast houseUSD50Unknown
208selling a house in phoenixUSD50Low6
209we buy a houseUSD50Medium615.0029.73
210houses uglyUSD500Low58.5090.08
211houses for cash buyersUSD500High9120.0777.41
212selling home to cash buyerUSD50High7213.0465.35
213cash home buyers in my areaUSD50High8319.3567.50
214buy property fastUSD50Medium50
215i sell my homeUSD50Medium639.6248.00
216buy my house phoenixUSD50Low13
217buying & selling a homeUSD50Low29
218homevestors we buy ugly housesUSD50Medium5926.9146.90
219need to sell your homeUSD50Medium5223.5896.81
220cash buyers in my areaUSD50Medium628.7331.92
221buying a house to sellUSD50Medium6010.7230.77
222i sell my propertyUSD50Medium64
Compare.Homevestor

Open original tab

Compare.Homevestor
RowABC
1https://homevestorsfranchise.com/Source link B1https://www.homevestors.com/phoenix/Source link C1
2KeywordKeyword
3investing in real estatewe buy houses for cash
4buying rental propertywe buy houses
5buying an investment propertysell my house fast for cash
6best real estate investmentssell my house fast
7rental propertysell house fast
8investment propertycash for houses
9rental property investmentwe buy homes for cash
10buying propertysell your house fast
11distressed propertysell home fast
12getting started in real estateselling property
13estate investsell my house
14owning rental propertywe buy homes
15best property investmentcash home buyers
16investment housesbuy houses for cash
17real estate finance and investmentssell my home fast
18real estate investing coursessell my house fast phoenix
19property investment coursesugly houses
20house investmentsell my home
21rental investmentbuy my house
22best real estate marketssell house for cash
23selling a rental propertyneed to sell my house fast
24property investment opportunitiessell my house for cash
25distressed real estatesell your home fast
26real estate opportunitiessell my home for cash
27real estate investment opportunitiesbuy homes for cash
28best rental marketssell my house as is
29top real estate investorscash for my house
30getting into real estate investingcash house buyers
31learning real estatesell home for cash
32learn real estate investingsell house fast for cash
33real estate rental propertybuy my house fast
34property investment guidesell my property
35getting started in real estate investingwe buy houses fast
36selling investment propertyselling a home
37real estate investment propertiesbuying and selling houses
38best rental property marketswe buy your house
39successful real estate investorssell your house for cash
40start investing in real estatebuy my house for cash
41find real estate investorsi buy houses cash
42real estate investor leadswe buy houses phoenix
43best markets for real estate investingselling house as is
44best real estate markets to invest ini need to sell my house fast
45house investorssell property fast
46best real estate investing coursesbuy your house for cash
47guide to real estate investingfast home buyers
48investment housingselling a house to a cash buyer
49distressed houseswe buy ugly homes
50best rental propertysell fast
51real estate investment trainingsell your house fast for cash
52real estate investment businessbuy and sell property
53buying a house as an investmentselling and buying a home
54real estate investment optionssell my home fast for cash
55distressed real estate investingcash for your house
56getting into rental propertiessell houses
57invest in rental homesi need to sell my house
58building a rental propertyneed to sell my house
59house flipping investorspeople that sell houses
60good investment propertiessell house fast phoenix
61good real estate investmentssell home fast for cash
62rental property marketwe buy houses as is
63real estate finance & investmentswe buy your home
64best investment property in chicagobuy my home for cash
65about real estate investmentcash buyer property
66real estate investment ideasneed to sell house fast
67real estate investing coachwe buy property
68selling house to investori buy ugly houses
69finding investment propertiessell your property fast
70real estate flipping houseswe buy houses fast for cash
71best markets to buy rental propertyugly home
72investment properties in njwe buy property for cash
73selling home to investorbuy your home for cash
74good rental propertycash houses
75buying property nowsell home as is
76best rental real estate marketssell ugly house
77real estate investment financewe buy your house for cash
78best rental properties to buyfast cash for house
79investors that buy housesbuy houses as is
80buy to sell property investmentsell my house phoenix
81property investment businesswe buy homes fast
82best property to buywe sell houses
83property investment leadssell homes
84buying property in chicagoi buy homes for cash
85chicago investment propertiesselling your house as is
86property investment trainingsell your home for cash
87marketing for real estate investorsbuy house fast
88real estate investment franchisewe buy for cash
89everything you need to know about real estate investingbuy to sell property
90investing in real estate rentalswe buy your home for cash
91selling your home to an investorselling your home as is
92best housing markets to invest inhouse cash
93buying a rental housebuy house in phoenix
94property and investmentsell my ugly house
95real estate investment toolsfast cash home buyers
96best house investmentssell my property fast
97starting a real estate investment businesssell your house fast phoenix
98real estate investing rental propertiesbuy my home fast
99getting into property investmentbuy houses fast
100top rental propertywe buy and sell houses
101buying a rental homesell your home fast for cash
102best real estate opportunitiessell my property for cash
103guide to buying propertyneed to sell home fast
104selling your rental propertycash property buyers
105invest in housing markethouse fast
106buying a house as an investment propertybuy homes fast
107building an investment propertysell property for cash
108best lead generation for real estate investorsbuy my house as is
109best rental property investmentsneed to sell your house fast
110best rental investmentswe buy properties fast
111best rental investment marketsbuy sell house
112investors buying homeswe buy your property
113investment in house propertysell my ugly house fast
114investor propertiesbuy ugly homes
115finding rental propertysell home as is fast
116real estate investor lead generationsell my phoenix house fast
117buying a home as an investmentsell property fast for cash
118chicago real estate investmentcash home buyers phoenix
119selling your house to an investorsell my house fast in phoenix
120property investment ideasneed to sell my home fast
121learn about property investmentneed a house fast
122investment properties to buysell ugly house fast
123rental property good investmentwe buy ugly houses phoenix
124professional real estate investorwe buy and sell homes
125buying real estate for investmenthouses phoenix
126real estate investment careersselling property as is
127real estate and investmenti need to sell my home fast
128owning investment propertycash for houses phoenix
129buying a house is a good investmentbuy my house fast for cash
130top rental property marketssell your property for cash
131best investment housesi buy ugly homes
132real estate investment marketpeople selling houses
133property to investbuy home in phoenix
134properties for investorsbuying ugly houses
135property investment toolssell my home as is
136chicago real estate investorsselling a house to buy a house
137rental property investment courseswe sell houses fast
138home and investmentwe buy houses phone number
139buying a house as a rental propertybuy ugly
140the real estate investorphoenix home buyers
141selling your house to a real estate investorwe buy houses in phoenix
142property investment optionswe buy homes as is
143buying property guidei sell my house
144investor homeshouses are selling fast
145getting into the property marketbuy a house fast
146property investment marketwe buy homes phoenix
147all invest real estatebuying and selling your home
148best real estate investment opportunitiesbuy house fast cash
149housing investorsfast home selling
150investing in real estate nowwe buy your property for cash
151best investment properties to buysell my house in phoenix
152rental house investmentfast cash buyers
153best buy propertywe buy houses in
154buying property as a businesssell home fast phoenix
155buying houses to flipbuy sell home
156investors buying all the homesneed to sell my home
157getting started in property investmentto sell my house
158best real estate markets to invest in right nowsell my home fast phoenix
159buy real estate propertyselling for house
160buying a house from an investorfast property sell
161rental property ideassell your home phoenix
162buy rentalselling homes phoenix
163buying a house is an investmentwe buy properties cash
164investing in buildingscash for home buyers
165best rental markets in njbuy my house in phoenix
166property real estate investmentneed sell home fast
167investing in your homewe buy your house fast
168best property to buy for investmentbuy my property fast
169best real estate properties to invest insell your ugly house
170real estate markets to invest insell your house phoenix
171starting property investmentsell your house in phoenix
172real estate investing resourcesbuy my property for cash
173rental property njbuy my house as is for cash
174flipping rental propertiessell your home fast phoenix
175invest with the housecash fast house sell
176best resources for real estate investingwe sell your house
177distressed property investingwe sell houses fast for cash
178buying house is good investmentsell homes fast cash
179flipping investmenthomevestors logo
180getting investors for real estatewe buy houses for
181house investment propertyselling your house to a cash buyer
182buying your rental propertyfast sell property
183best markets for investment propertysell house phoenix
184real estate is best investmentbuying an ugly house
185successful property investorsbuying a house and selling yours
186investors for propertyfast cash for my house
187invest estatesneed to sell property fast
188property investment coachingi need to sell my home
189getting started in rental propertyneed to sell fast
190i on real estate & investmentsbuying property to sell
191real estate is good investmentsell my house fast in
192real estate investing flipping housescash for houses fast
193property investment insell my home phoenix
194best houses to invest insell fast house
195everything to know about real estate investingwww we buy ugly houses com
196rental real estate marketphone number for we buy ugly houses
197investment and real estatebuy fast sell fast
198best real estate propertiesselling home in phoenix
199nj real estate investorswe buy phoenix houses
200top property marketselling my house to a cash buyer
201starting rental propertiesselling a home in phoenix
202rental properties to invest inhomes are selling fast
203good real estate marketsan ugly house
204all about real estate investingneed to buy a house fast
205best markets to own rental propertyhouse buyers in my area
206buy sell invest real estatecash fast house
207a real estate investorselling a house in phoenix
208opportunities in real estate investmentwe buy a house
209about property investmenthouses ugly
210all real estate and investmentshouses for cash buyers
211best real estate investments right nowselling home to cash buyer
212guide to real estatecash home buyers in my area
213investment property opportunitiesbuy property fast
214selling investments to buy a housei sell my home
215rental property coursebuy my house phoenix
216business property investmentbuying & selling a home
217buying property right nowhomevestors we buy ugly houses
218good real estate markets to invest inneed to sell your home
219best real estate markets right nowcash buyers in my area
220starting a property investment businessbuying a house to sell
221best investment homesi sell my property
222top markets for real estate investing
223all about property investment
224everything you need to know about investing in real estate
225buying and investment property
https://www.mikeysellshouses.com/

Open original tab

https://www.mikeysellshouses.com/
RowABCDEFG
1https://www.mikeysellshouses.com/Source link A1
2KeywordCurrencyAvg. monthly searchesCompetitionCompetition (indexed value)Top of page bid (low range)Top of page bid (high range)
3fixer upper housesUSD5000Low320.451.94
4houses for sale in phoenixUSD5000Medium430.681.84
5fixer upper houses for saleUSD5000Medium580.401.97
6homes for sale in phoenix azUSD50000Medium360.561.67
7fixer upper homes for saleUSD5000Medium590.451.95
8phoenix homes for saleUSD5000Medium400.621.79
9houses for sale in phoenix azUSD50000Medium390.611.71
10fixer upper homesUSD5000Low310.501.87
11phoenix housingUSD50000Low241.1710.84
12cheap housesUSD50000High970.551.87
13az homes for saleUSD50000Medium410.211.44
14investment properties for saleUSD5000High761.396.22
15buying propertyUSD5000Low280.975.47
16foreclosure propertiesUSD5000Medium650.541.81
17homes in phoenix azUSD5000Medium360.591.57
18houses for sale azUSD50000Medium440.261.33
19cheap properties for saleUSD5000Medium550.541.58
20cheap propertyUSD500Medium390.561.51
21fixer upper for saleUSD5000Medium560.441.59
22cheap houses to buyUSD5000High940.734.48
23cheap fixer upper homes for saleUSD500Medium610.612.38
24investors houseUSD50Low203.1311.65
25real estate phoenix azUSD5000Medium370.531.80
26real estate phoenixUSD5000Low320.421.71
27investment homes for saleUSD500High831.035.00
28homes in phoenixUSD5000Low260.581.83
29az homesUSD5000Low260.151.00
30handyman specialUSD500Low210.964.32
31phoenix foreclosuresUSD500Medium360.561.61
32housing in phoenix azUSD5000Low300.611.58
33fixer upper properties for saleUSD500Medium550.531.82
34az houseUSD50000Low240.161.02
35phoenix real estate for saleUSD500Medium440.551.51
36investment houses for saleUSD500High771.044.21
37foreclosure homes in azUSD500Medium580.471.85
38house investorsUSD5000High7612.0048.64
39fixer upper real estateUSD500Medium380.472.13
40buy a fixer upper houseUSD500Medium540.866.57
41properties investmentUSD50000Medium533.399.07
42cheap fixer upper homesUSD500Medium620.671.92
43buy fixer upper homesUSD500Medium580.704.93
44buy cheap propertyUSD500Medium520.621.90
45cheap fixer upper houses for saleUSD500Medium570.541.59
46fixer upper propertiesUSD500Medium530.502.33
47cheap investment propertyUSD500High751.379.38
48handyman special homes for saleUSD500Medium510.592.16
49real estate investment propertiesUSD500Medium534.8910.81
50house of phoenixUSD50Low4
51fixer homes for saleUSD500Medium540.624.47
52find fixer upper homesUSD500High680.752.24
53cheap houses for sale in phoenixUSD50Medium490.591.87
54handyman special houses for saleUSD500Medium480.641.80
55foreclosures in phoenix azUSD500Medium420.501.37
56cheap fixer upper homes in azUSD500Medium540.561.82
57real estate in azUSD50000Medium340.211.50
58for sale phoenixUSD500Low260.241.56
59cheap foreclosure homes for saleUSD500Medium430.552.00
60buy house phoenixUSD500Medium411.3814.84
61buying homes in foreclosureUSD50000Medium390.342.24
62selling house to investorUSD500Medium6714.3746.53
63fixer houses for saleUSD500Medium560.653.96
64selling a fixer upperUSD50Medium644.4215.84
65selling home to investorUSD500Medium5514.5349.37
66investors that buy housesUSD500Medium3812.3056.88
67az foreclosuresUSD5000Medium600.481.67
68houses to buy in phoenixUSD50Medium571.002.78
69phoenix home buyersUSD50Low3012.4450.60
70cheap fixer uppersUSD50Medium550.521.78
71foreclosure homes phoenix azUSD500Medium490.581.71
72investment real estate for saleUSD500Medium442.109.90
73buys housesUSD50000Medium601.757.43
74buying a house on foreclosureUSD5000Medium360.372.13
75foreclosure investingUSD500Medium511.067.65
76finding investment propertiesUSD500Medium612.7211.70
77real estate investment properties for saleUSD500High732.1410.40
78cheap investment property for saleUSD50High770.963.73
79cheap houses in phoenixUSD50Medium520.421.50
80buy home in phoenixUSD500Medium351.3110.44
81find cheap houses for saleUSD50Medium600.603.02
82buy to sell property investmentUSD50Unknown
83cheap homes for sale phoenix azUSD500Medium580.711.81
84best property to buyUSD50Low280.9114.48
85foreclosure homes in phoenixUSD500Medium650.602.05
86cheap houses in phoenix azUSD500Medium500.672.06
87phoenix investment propertiesUSD50Medium471.6711.70
88cheap houses in azUSD500Medium380.261.53
89cheap homes in azUSD500Medium350.261.48
90selling homes phoenixUSD50Low3
91homes for buyUSD50000Medium392.0515.00
92sells housesUSD5000Medium659.2947.62
93handyman special homesUSD50Medium530.552.11
94houses for investmentUSD5000Medium392.749.40
95houses to buy cheapUSD50High1000.713.88
96properties for sale in phoenixUSD500Medium580.561.45
97real estate fixer uppers for saleUSD50Medium640.351.38
98sell house phoenixUSD50Low191.4175.47
99selling a fixer upper houseUSD50High739.3435.07
100investors buying homesUSD500High7515.4161.33
101cheap fixer upper housesUSD50Medium630.511.91
102investor propertiesUSD500Medium473.3214.41
103cheap homes in phoenix azUSD50Medium510.621.80
104find fixer uppersUSD50Medium490.603.21
105foreclosure fixer uppersUSD50Medium340.352.34
106buying a house in azUSD500Medium530.783.98
107az home buyersUSD50Medium4810.0044.44
108cheap houses for sale in azUSD5000Medium500.471.61
109property investment dealsUSD50High81
110best buy propertyUSD50Low6
111investment properties to buyUSD50High791.507.63
112property in phoenixUSD50Low330.683.42
113property fixerUSD50Low261.627.53
114selling home in phoenixUSD50Low1
115buy a house in phoenix azUSD500Low311.2610.52
116fixer real estateUSD50Low17
117selling a home in phoenixUSD50Low8
118properties for investorsUSD50High755.1214.60
119selling a house in phoenixUSD50Low6
120phoenix real estate investmentUSD500Medium654.9820.07
121the house phoenixUSD50Low0
122property phoenix azUSD500Low320.621.71
123cheap homes for sale in phoenixUSD50Medium550.752.01
124handyman special housesUSD50Medium350.631.63
125real estate investment dealsUSD50High685.1715.46
126buying property as isUSD50Low314.0015.22
127looking for fixer upper homesUSD50High790.753.86
128home to phoenix azUSD50Low1
129looking for investment propertiesUSD50High694.2614.61
130foreclosure fixer upper homes for saleUSD50Medium550.461.87
131cheap homes in phoenixUSD50Medium540.452.16
132fixer homesUSD50Medium350.663.67
133find fixer upper homes for saleUSD50Medium610.712.17
134buy sell invest real estateUSD50Low332.778.30
135houses for sale investment propertiesUSD50Medium600.924.91
136investment property buyersUSD5000Medium491.998.06
137cheap homes for sale in azUSD500Medium370.241.51
138buying a home in phoenix azUSD500Medium521.165.11
139cheap houses for sale phoenix azUSD500Medium440.651.82
140buy real estate propertyUSD50Medium371.498.89
141buying a house from an investorUSD50Medium493.5511.94
142fixer upper houses for sale in phoenixUSD50Medium620.582.35
143cheapest house on fixer upperUSD50Medium370.862.44
144phoenix foreclosure homes for saleUSD50Medium570.612.13
145best property to buy for investmentUSD50Medium652.5010.78
146fixer upper homes for sale in phoenix azUSD50Medium620.522.39
147cheap housing in phoenixUSD50Medium520.330.72
148houses from fixer upper for saleUSD50Low17
149looking for propertiesUSD500Low71.106.89
150houses for sale cheap fixer upperUSD50Medium410.611.67
151fixer upper houses for sale in azUSD50Unknown
152sell property to investorsUSD50High9816.7050.00
153buying a home in azUSD500Medium581.035.41
154fixer upper houses in phoenix azUSD50Medium650.371.74
155investment property phoenix azUSD50Medium641.379.00
156handyman specials for saleUSD50Medium430.651.33
157looking housesUSD5000Medium650.993.89
158invest in phoenixUSD50Low14
159for sale in azUSD500Low290.101.16
160investors looking to buy homesUSD50High8412.2550.63
161sell investment propertiesUSD500Medium453.7923.92
162buying property to sellUSD50High100
163distressed properties phoenixUSD50High820.551.81
164foreclosure investment propertyUSD50Medium480.996.75
165homes for sale in sells azUSD50Low13
166house investors buy homesUSD50High8613.9155.00
167the house of phoenixUSD50Low3
168deals on housesUSD500Medium461.147.57
169buying property inUSD50Low2
170houses for investorsUSD50High922.4918.17

Pricing architecture: credits, scope, buyer paths and evidence

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Assigned lessons: 03.1, 03.3, 03.4, 04.1 and 06.2.

What this source provides

This lesson teaches the reasoning in a commentary about an upgraded pricing widget. The opening claims eight improvements and describes audience selection, Launch/Evergreen toggles and live value-ratio and credit calculations. The body has seven headings; the last combines follow-up timing and affiliates. The actual widget, executable code, tier-timing diagram and individual-value grid are absent from the native document. We can teach its reasoning, but cannot claim that a functioning calculator was supplied, rebuilt or tested from this source.

You will distinguish the diagnostic offer from the implementation sprint, calculate a purchase credit, define scope, examine audience-specific price proposals and design an evidence-based path between offers. Source examples are proposals rather than adopted RISER prices or verified sales results.

1. Connect the offers with a clearly defined credit

The source proposes a $197 Diagnostic followed by a $500 Sprint. After completing the Diagnostic, the buyer receives a $97 credit toward a Sprint booked within seven days. The later Sprint payment becomes $403. The combined outlay is $197 + $403 = $600, compared with $697 for both products without the credit. The saving is $97, not the full diagnostic price.

The source's recommended credit range is approximately 40–50% of the diagnostic price. Here, $97 divided by $197 is about 49.24%. It argues that a small credit may not motivate action while a very large credit may weaken the Diagnostic's standalone perceived value. Treat the range and behavioral claims as design hypotheses requiring evidence, not universal conversion laws.

State the eligibility, when the seven-day window begins, how the credit is applied and whether it combines with other rates. The source says the message follows completion but does not fully specify the operational terms. Resolve those before implementation. Present the saving plainly rather than using the source's suggestion that a buyer should feel embarrassed to leave it unused. A buyer should be able to choose either offer without shame or confusion.

2. Teach what is not included

The Diagnostic exclusions are: no implementation, no revisions, no custom build work, no ongoing questions and answers, and no extra strategy sessions. Explain each boundary alongside the actual included deliverables. A diagnostic customer should understand that an assessment does not automatically include doing the work identified by that assessment.

The Sprint exclusions are: no open-ended consulting, no work outside the agreed scope, no post-handoff support beyond the stated window, and no strategy overhaul. Identify the actual agreed scope and support window; this document does not supply their values. Do not imply a customer forfeits a separately promised correction or support commitment simply because a general exclusion appears here.

The source identifies common assumptions such as unlimited questions, revisions whenever a buyer dislikes the first version and ongoing availability after handoff. Use clear terms to resolve those assumptions before purchase. Its assertion that exclusions increase conversion is not backed by results in this document. Clarity can support informed buying and delivery boundaries, but the conversion effect needs measurement.

3. Evaluate the audience-based pricing proposals

The source proposes these ranges for the same broad Diagnostic/Sprint sequence:

AudienceDiagnosticSprint
Prosumer$197 launch$350–$500
Business owner$247–$297$500–$750
Consumer$147$297–$350

The document calls prosumers the most common RISER buyer, but supplies no audience distribution evidence. Do not report that as a verified current customer statistic. Its reasoning is that the economic importance of a problem differs by buyer. Validate the segment, needs and actual value rather than automatically assuming everyone in a category has the same willingness to pay.

The example compares a dog-training beginner with a Phoenix realtor and associates a lost $400,000 deal with $12,000 of lost income. That arithmetic assumes 3% of the transaction amount. The source does not establish an actual fee, net income or universal commission standard. The dog owner's nonfinancial needs also cannot be reduced to a presumed low value without evidence.

The source places audience selection before the Vol 3 Niche Specificity Gate, connecting audience to price, price to value ratio and ratio to its “impulse utility” concept. The actual gate and Doc 9 are absent here. Preserve that dependency and obtain the relevant material before claiming this lesson fully applies its criteria.

4. Calculate perceived-value ratios without manufacturing value

The stated formula is total perceived value divided by asking price. The proposed widget lists individual deliverable values, totals them and shows a ratio. The source attributes a minimum target of 10:1 and an optimum of 30:1 to Doc 7. It calls 30:1 an impulse-utility threshold. Doc 7 and the individual-value grid are not included in this native source, and no evidence establishes those thresholds as guaranteed buying behavior.

At a $197 asking price, $1,200 of estimated value produces about 6.09:1, rounded to 6:1 in the source. A 10:1 ratio requires $1,970; 30:1 requires $5,910. These are arithmetic results, not proof that buyers assign those values to the deliverables. A green indicator at 10:1 or above would indicate compliance with the chosen rule, not that the offer is objectively priced correctly.

The source suggests more specific deliverable naming and defensible market-rate anchors, or a lower price, when the ratio falls short. Naming alone cannot create substantiated economic value. Avoid double-counting overlapping items or inflating individual anchors to make a target turn green. Record how a proposed value was established and distinguish an estimate from an actual sale, customer outcome or independent comparison.

5. Make launch and evergreen terms real

For the prosumer example, the Diagnostic moves from $197 at launch to $247 evergreen. The Sprint moves from $350 to $500. The source proposes a first-100-buyers limit and illustrates an announcement that 67 sales have occurred. Neither number is a verified RISER sales count. Use a limit only when it is real, tracked and honored, with the actual price change disclosed.

The source expects early pricing to support access while social proof develops and suggests early buyers may become enthusiastic testimonial providers. Neither testimonials nor conversion improvement are guaranteed. Any eventual testimonials must reflect the buyer's actual experience, rather than being implied as a required favorable response to a discount.

Reconcile the launch prices with the credit example. If the same $97 credit applies to a $350 launch Sprint, the Sprint payment would be $253 and combined spending $450. At a $500 Sprint the combined spending is $600. The document does not define credit stacking across these modes, so clarify the policy before implementing or advertising either total. The general seven-day credit and the first-100 launch limit are separate conditions.

6. Offer two paths based on readiness

The source critiques a Vol 1 page where every buyer starts with the Diagnostic. It proposes two calls to action: start with a Diagnostic when the buyer is unsure what is wrong, or go directly to the Sprint when the buyer knows what needs to be built. Teach the actual difference in the work purchased and the readiness evidence required for direct implementation.

A second path should help a buyer make a clear choice. It does not literally double the number of customers or guarantee both groups convert. The source's claim about greater conversion among solution-aware buyers requires testing. The referenced Vol 1 page and Doc 9 are not included, so do not claim that their complete page designs have been reviewed from this document alone.

7. Sequence follow-up offers around customer progress

The source describes a timeline that would show when to introduce each tier after purchase. It warns against presenting every upsell at checkout and against never following up. The timeline itself and its tier-by-tier timing are absent. Do not invent dates and attribute them to the missing graphic.

An authored application is to define the completion evidence and readiness that make the next offer useful. The Diagnostic-to-Sprint credit is one specified example; other tiers require the actual supporting material. Track whether follow-up serves a buyer's next task instead of assuming that every customer needs every product. Planning the follow-up is separate from activating a campaign or sending messages.

8. Evaluate an affiliate program after verified use

The source proposes 30–40% commission on referred sales, introduced at Month 6 or later to buyers with verifiable results. Its invitation criteria are either a first $1,000 earned using the Forge, or completion of the Ignition Engine plus deployment of at least one offer. Preserve the OR relationship: it does not require both achievements. These are proposed eligibility criteria, not proof that any buyer has achieved them or that an affiliate program is active.

Verify the actual result and experience before making an invitation decision. Completing a program or reaching a revenue milestone does not by itself establish that every recommendation will be accurate or that only authentic advocates can qualify. The source claims the channel can compound without additional content effort; operating a referral program still requires terms, tracking, support and review. Do not present commission as effortless or guaranteed income.

The document supplies no full program terms, attribution window, refund treatment or definition of commissionable revenue. Resolve those details before any program implementation. No invitations, purchases or commission payments are executed by this lesson.

Integrate the marketing themes and practice

In an authored Brunson/ClickFunnels application, the credit and readiness-based paths connect a customer's next decision to a clearly explained offer sequence. Maintain a useful standalone Diagnostic and an understandable implementation path. The source does not supply a ClickFunnels configuration or direct Brunson quotation.

In an authored Hormozi/Acquisition.com application, assess perceived value alongside the desired result, evidence, customer effort and delivery time. Clear scope and an honest price comparison support that assessment; a large invented value total does not. Keep the 10:1 and 30:1 source targets separate from verified customer outcomes.

For practice, select an evidence-supported audience, define both scopes, calculate the credit and total customer outlay under each applicable price mode, document value assumptions, and explain the two entry paths. Identify the missing timing and affiliate terms before considering implementation. This produces a reviewable pricing specification, not a tested widget or a published commercial offer.

Clickable sources and outstanding dependencies

- Assigned original pricing-widget commentary — native text reviewed; full original text must accompany this teaching script. - RISER NATION CORP — brand destination.

The actual widget/code, individual-value grid, timing diagram, Doc 7, Doc 9, Vol 1 page and Vol 3 Niche Specificity Gate are not supplied in this native source. Their exact applicable references remain unresolved. Obtain those materials before claiming to have implemented or verified the missing elements. The original's assertions about conversion, urgency and affiliate growth remain source claims until supported by evidence.

Assigned source: D0472 original 1

D0472 — complete original source

D0472 — Now building the upgraded interactive pricing tool with all 8 improvements:The widget above is fully interactive — switch between Consumer, Prosumer, and Business Owner to see prices recalibrate across all tiers, toggle between Launch and Evergreen pricing, and watch the value ratio and credit ascension numbers update in real time

Open original document · Download preserved native document structure

Complete native text, embedded links, heading hierarchy, list items and bold/italic emphasis. Unspecified native bullet glyphs use a standard bullet here; exact formatting metadata is retained in the downloadable structure. Full visual layout comparison remains pending.

Now building the upgraded interactive pricing tool with all 8 improvements:The widget above is fully interactive — switch between Consumer, Prosumer, and Business Owner to see prices recalibrate across all tiers, toggle between Launch and Evergreen pricing, and watch the value ratio and credit ascension numbers update in real time.
Here is the full reasoning behind every change from the previous version.

The credit-based ascension model — the most important structural change
The previous offer stack showed two separate products with two separate prices. The credit model connects them mechanically. The buyer pays $197 for the Diagnostic, completes it, and receives a message: "$97 of your Diagnostic price applies toward the Sprint if you book within 7 days." The effective Sprint price drops from $500 to $403 for that buyer — but only if they act within the window. This changes the psychology of the first purchase completely. The buyer isn't choosing between spending $197 and $500 — they're choosing whether to spend $197 now and $403 later, or $197 now and $500 later. The $97 difference feels almost embarrassing to leave on the table. The credit mechanic is what makes the ladder feel like a continuous decision rather than two separate selling events.
The credit amount should be approximately 40-50% of the Diagnostic price. Too low and it doesn't create urgency. Too high and the Diagnostic loses perceived value as a standalone purchase.

The "What is NOT included" section — scope protection for productized services
This is the single most overlooked element in knowledge service pricing. The instinct is to list everything the buyer receives — but equally important is what they cannot reasonably expect. Without explicit exclusions, every buyer arrives with assumptions: that they can email you unlimited questions after the Diagnostic, that the Sprint includes revisions if they don't like the first version, that you'll be available ongoing after the handoff.
The widget now shows the NOT included list for both offers. For the Diagnostic: no implementation, no revisions, no custom build work, no ongoing Q&A, no extra strategy sessions. For the Sprint: no open-ended consulting, nothing outside the agreed scope, no post-handoff support beyond the stated window, no strategy overhaul.
These lists do not reduce conversion — they increase it. A buyer who sees a clear scope feels confident about what they're purchasing. A buyer who senses ambiguity either asks for more detail (friction) or declines (lost sale). Clarity on limits paradoxically creates more confidence in the offer.

The audience-based pricing matrix — same offer, three different prices
The previous stack had one price per tier. Doc 9 is explicit that the correct price depends on who is buying. A dog training beginner and a Phoenix realtor are both buying "a Diagnostic" but the problem costs them very different amounts to leave unsolved. The realtor losing a $400K deal has a $12,000 cost-of-inaction. The dog training hobbyist losing time with a badly behaved dog has a much lower financial stake.
The matrix in the widget shows how prices shift across three audience types. For the prosumer audience (the most common RISER buyer): Diagnostic $197 launch, Sprint $350-$500. For business owners: Diagnostic $247-$297, Sprint $500-$750. For consumers: Diagnostic $147, Sprint $297-$350. The operator should select their audience type before filling in the Vol 3 Niche Specificity Gate — because the audience type determines the price, which determines the value ratio, which determines whether the impulse utility threshold is reached.

The value stack with individual perceived values and the 10:1 ratio target
The previous widget listed tiers with a single price. This version shows individual perceived values for each deliverable, a total perceived value, and a real-time value ratio calculated as Total Perceived Value ÷ Asking Price.
The minimum target from Doc 7 is 10:1. The optimum is 30:1 — the "impulse utility" threshold where the purchase decision stops feeling like a cost and starts feeling like a no-brainer. At the prosumer Diagnostic price of $197, if the total perceived value of deliverables is $1,200, the ratio is 6:1 — below threshold. To hit 10:1 at $197, the deliverables need to credibly total at least $1,970. The operator either needs to raise the perceived value of individual items (by naming them more specifically and anchoring to market rates) or lower the price.
The value ratio indicator in the widget shows a green checkmark at 10:1+ and a warning below that threshold. This gives operators immediate feedback on whether their offer stack is priced correctly relative to its perceived value.

Launch pricing vs. evergreen pricing — the escalation plan
Toggle between Launch and Evergreen in the widget to see the price difference. For the prosumer Diagnostic: $197 launch → $247 evergreen. For the Sprint: $350 launch → $500 evergreen. These aren't arbitrary — the launch price creates genuine urgency (the price actually increases) while keeping the entry point accessible during the period when social proof is being built.
The "first 100 buyers" framing does two things: it creates urgency with a specific, believable limit, and it positions early buyers as getting a special rate for being early — which makes them feel smart for acting now and makes them more likely to be enthusiastic testimonials. The shift to evergreen should happen publicly, announced in content: "The launch price of $197 closes when I hit 100 sales. I'm at 67 right now." That kind of transparency converts better than artificial countdown timers.

The split-path landing page
The current sales page in Vol 1 assumes every buyer enters through the Diagnostic. Doc 9 identifies that solution-aware buyers — people who already know they need something built, not just diagnosed — will convert better if they can skip the Diagnostic and go straight to the Sprint.
The split-path at the bottom of the widget shows two simultaneous CTAs: "Not sure what's wrong with your offer yet? Start with the Diagnostic" and "Already know what you need built? Go straight to the Sprint." This doubles the surface area of the landing page without adding length — solution-aware buyers see an immediate path, problem-aware buyers see their path. One page, two audiences, both converting.

The backend monetization timeline and the affiliate flywheel
The timeline at the top of the widget shows when to introduce each tier after purchase. This is the detail most operators miss — they either hit buyers with every upsell at checkout (overwhelm, refunds) or they never follow up after the initial purchase (lost ascension revenue).
The affiliate flywheel is the long-term growth mechanism missing from the entire stack. Buyers who achieve a result using the tools have both the incentive and the credibility to recommend them. An affiliate programme where they earn 30-40% commission on any sale they refer creates a distribution channel that compounds without additional content effort. This doesn't need to be built at launch — it should be offered at Month 6+ to buyers who have verifiable results. The criteria for the affiliate invite: "You've made your first $1,000 using the Forge, or you've completed the Ignition Engine and deployed at least one offer." That filter ensures only genuine advocates promote the product.

Design an offer you can improve and sustain

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

The purpose of long-term offer architecture

The assigned document defines twelve offer-design principles across four phases: pre-offer viability, competitive durability, launch architecture and long-term advantages. Its purpose is a durable, controllable and scalable offer that can improve with experience. This is a design checklist, not evidence that a particular offer is already viable.

Brunson's value ladder helps organize useful next steps for the customer. Hormozi's value framework helps examine whether the outcome, likelihood, timing and effort make the offer attractive. Those perspectives must also connect with delivery capacity, costs and evidence. A persuasive offer that cannot survive ordinary operating changes is not ready to scale.

Phase 1: check viability before building

1. Ownership and control

The source's “Dig Your Own Well” principle asks for control over hosting, domains, delivery and access; the ability to move platforms without destroying the offer; resilience against one company shutting it down; and exportable customer email, behavior and purchase history. Its anti-pattern is an offer that exists only inside one social platform, marketplace or SaaS with no redundancy.

Turn these aspirations into a dependency inventory. Record where the domain, content, customer permissions, transaction records and access rules live. Check what you can export and how you would restore essential delivery elsewhere. Owning a domain does not make hosting, payment or software dependencies disappear. No ordinary technology arrangement guarantees that every vendor interruption is harmless.

Exportability also does not authorize unlimited collection or reuse of customer information. Retain only appropriate records and honor the permissions that apply to them. Backups need a usable restoration process, not simply a download that nobody has checked.

2. Iteration capability

The source asks for four independent changes: swapping hooks, testing headlines/images/CTAs/angles, modifying opt-in points without rebuilding everything, and updating the core promise without breaking delivery. Design components so a small approved change does not require an unnecessary rebuild.

The ability to revise a promise must be reconciled with commitments already made. Preserve the terms applying to existing customers, review delivery implications, and version future changes. This complements the related Offer Lock Engine: a locked version provides a shared baseline, while an approved revision creates a new baseline. Locking does not prohibit correction.

3. Clear progression

The four source rules are a clear start–middle–end, visible progress markers, predictable next steps and logical escalation of value. The source calls this linear progression and distinguishes clear sequencing from simple thinking.

Give customers a default route they can understand. Show what they should complete, how they recognize progress and what comes next. The source's broad statement that humans think linearly should not prohibit useful branches, accessibility accommodations or different readiness levels. Clarity matters more than forcing every customer through an identical path.

4. Multiple monetization paths

The source identifies four paths: free or low-commitment entry, a core transaction, an upsell or expansion, and continuity or repeat engagement. Map them according to customer readiness and a real continuing need. In a Brunson-style ladder, the next step should make sense after the preceding result.

A single revenue stream creates concentration risk, but it does not automatically make every business invalid. Additional offers also create costs and complexity. Keep the core purchase complete; do not withhold essential delivery to force an upsell. Test demand and economics before adding recurring obligations.

Phase 2: build competitive durability

5. Scale without multiplying confusion

The source lists repeatable inputs such as traffic/content/ads, modular hooks/creatives/pages, and clear performance attribution. Document a repeatable process and the handoffs that make it work. A modular creative asset is useful only if the correct version reaches the right page and the delivery promise remains consistent.

Explain what increased volume changes: production time, support demand, payment costs, fulfillment and review capacity. More traffic does not correct a broken process. Clear attribution helps diagnose changes, but attribution is often incomplete; keep unknown and overlapping channels visible.

6. Use feedback to make decisions

The three source loops are ad → click → behavior → insight, friction → drop-off → fix, and customer questions → content → conversion improvement. Each loop needs a responsible person, a measure and a decision. An analytics report alone does not improve an offer.

For an authored example, repeated questions about an included deliverable may suggest unclear page wording. Draft a clearer explanation, test it appropriately, and inspect both purchase behavior and expectation quality. Do not assume every abandonment was caused by that wording or that publishing an answer guarantees conversion lift.

7. Develop useful accumulated evidence

The source's “data gravity” examples are thousands of creative tests, audience behavior patterns, pricing-elasticity data and customer objection language. Such evidence can improve decisions when it is relevant, reliable and lawfully obtained. Volume by itself is not a competitive moat.

Keep definitions, dates and conditions with the data. A price test in one audience may not describe another audience; a historical pattern may change. Document what decision the evidence supports and its limits. Do not turn private customer information or unverifiable quotations into public proof.

The source specifically describes accumulated operating knowledge as a way to build an advantage without patents. That is a distinction between learning from repeated work and relying on patent protection; it does not establish exclusivity or guarantee competitors cannot catch up.

Phase 3: prepare a testable launch

8. Design small testable changes

The source's atomic testing units are one hook, one headline, one image or one video opening. A controlled change can make interpretation easier. Record the hypothesis, comparison, outcome measure and observation period before using the result to decide.

Changing one element is a practical starting discipline, not the only valid experimental method. Sample size, randomization, concurrent changes and interactions can affect conclusions. The source provides no statistical threshold. Avoid certainty from a handful of favorable responses or from comparing different audiences without acknowledging the difference.

9. Keep media editable

The source warns against hard-coded assets, over-produced assets and assets that are emotionally expensive to redo. Preserve source files and use an editing process proportionate to the offer's stage. A team should be able to correct an error or update a legitimate detail without rebuilding everything.

“Fast edits beat perfect assets” is the source's operating maxim, not a reason to skip accuracy, accessibility or necessary production quality. Maintain captions, readable text, useful alternative descriptions and correct permissions when media is revised.

10. Avoid dependence on one traffic source

The source asks whether the offer can work across platforms, survive higher CPMs, and convert with warm and cold audiences. Treat those as separate hypotheses to test, not capabilities established by a checklist.

Calculate the economics of the relevant journey. A warm referral and a cold ad click have different context, acquisition costs and information needs. Test whether the offer remains worthwhile under a plausible cost increase, and keep a plan for channel interruption. The source's “traffic is rented, offers are owned” phrase highlights dependence; it does not remove the practical dependencies identified earlier.

Phase 4: develop long-term advantages

11. Build recognizable brand memory

The three source elements are a consistent promise, recognizable positioning and a coherent worldview. Use repeated exposure to reinforce what the business stands for and what it reliably delivers. Novel hooks can vary while the underlying promise stays accurate.

The warning about random virality asks whether attention helps the intended audience understand and remember the offer. Viral reach is not necessarily wasted, but reach without relevance or a useful next step may not support the business objective. Measure more than views.

12. Reduce avoidable decision uncertainty

The source lists clear expectations, visible outcomes, honest framing and readiness gating. Explain what the customer receives, what they must do, which claims are supported and who should wait or choose another path. In Hormozi's framework, credible evidence can improve perceived likelihood; it must represent the actual offer and customer context.

The source associates confident buying decisions with fewer refunds and more advocacy. Those are outcomes to measure, not guarantees. A buyer can make an informed choice and still need a refund under the applicable terms. Do not use readiness gates to hide essential terms or unfairly pressure a prospect.

Apply the final six checks

Before scaling, review all six source questions: Do you own or appropriately control the asset? Can you iterate each necessary layer? Can monetization expand where useful? Is progression explainable? Does relevant data accumulate? Does feedback lead to actual improvement?

For each, record evidence and an unresolved issue if necessary. “The offer improves itself” requires an actual review-and-change process; software and data do not remove human responsibility. The source says to fix architecture before scaling when a check fails. Apply that instruction with a concrete remediation plan rather than interpreting it as proof that every possible risk must disappear before a limited test.

Turn the principles into usable artifacts

The source recommends three next artifacts: a scoring checklist for offer validation, a Google Sheet with pass/fail gates, and a repeatable pre-launch audit SOP. These are recommendations, not files supplied by the document. As authored implementation guidance, give each checklist item an evidence link, owner, status, review date and next action. Use “not yet verified” where a binary pass/fail would conceal missing information.

Keep the rubric transparent. The source gives no weights or calibrated scoring model, so do not invent a scientific meaning for a total score. Reuse the audit process, then revise it when operating evidence shows a missing control. Its “Build once. Reuse forever” maxim describes reusability, not an exemption from maintenance.

Sources and original material

- Assigned Offer Prerequisites & Long-Term Offer Architecture. - Related OP-04 Offer Lock Engine. - Acquisition.com value equation.

The full native source is retained for the appendix. The examples and implementation fields in this teaching are authored guidance, not completed business results or evidence of installed infrastructure.

Assigned source: D0473 original 1

D0473 — complete original source

D0473 — Offer Prerequisites & Long‑Term Offer Architecture

Open original document · Download preserved native document structure

Complete native text, embedded links, heading hierarchy, list items and bold/italic emphasis. Unspecified native bullet glyphs use a standard bullet here; exact formatting metadata is retained in the downloadable structure. Full visual layout comparison remains pending.

Offer Prerequisites & Long‑Term Offer Architecture
Purpose
This document defines the non‑negotiable prerequisites and strategic design rules for building offers that are durable, controllable, scalable, and compounding over time. It is written from a long‑term operator perspective, not a short‑term launch or trend‑chasing mindset.

Phase 1: Pre‑Offer Viability Filters (Before You Build Anything)
1. Ownership & Control (Dig Your Own Well)
An offer must be operator‑owned, not platform‑owned.
Minimum requirements:
You control hosting, domains, delivery, and access
You can move platforms without killing the offer
No single company can turn it off overnight
Customer data (email, behavior, purchase history) is exportable
Anti‑pattern to avoid: Offers that only live inside a single social platform, marketplace, or SaaS with no redundancy.

2. Iteration Capability (Design for Change)
An offer must be designed to change, not locked at launch.
You must be able to:
Swap hooks independently
A/B test headlines, images, CTAs, and angles
Modify opt‑in points without rebuilding the system
Update the core promise without breaking delivery
If iteration is hard, optimization dies.

3. Linear Progression (Human‑Readable Growth)
Humans think linearly. Offers must respect this.
Design rules:
Clear start → middle → end
Visible progress markers
Predictable next steps
Logical escalation of value
Linear structure does NOT mean simple thinking — it means clear sequencing.

4. Multi‑Monetization Readiness
Every offer should support stacking, not single‑point revenue.
Minimum monetization paths:
Entry (free or low‑commitment)
Core transaction
Upsell / expansion
Continuity or repeat engagement
If the offer only makes money one way, it’s fragile.

Phase 2: Competitive Durability Factors
5. Scalability Without Complexity Explosion
Scaling should increase signal, not chaos.
Look for:
Repeatable inputs (traffic, content, ads)
Modular components (hooks, creatives, pages)
Clear performance attribution
If scaling multiplies confusion, the system is broken.

6. Self‑Improving Feedback Loops
Your offer should teach you how to improve it.
Key loops:
Ad → click → behavior → insight
User friction → drop‑off → fix
Customer questions → content → conversion lift
Data is only valuable if it changes decisions.

7. Data Gravity Advantage
The more you run the offer, the harder it becomes to compete with you.
Examples:
Thousands of creative tests
Audience behavior patterns
Pricing elasticity data
Objection language harvested at scale
This is how large brands create moats without patents.

Phase 3: Launch‑Ready Architecture
8. Atomic Testing Units
Everything must be testable one variable at a time.
Design assets so you can change:
One hook
One headline
One image
One video opening
If you can’t tell why something worked, you didn’t test it correctly.

9. Editable Media by Default
Avoid assets that are:
Hard‑coded
Over‑produced
Emotionally expensive to redo
Fast edits beat perfect assets.

10. Offer Independence from Traffic Source
Traffic sources will change.
Your offer must:
Work across multiple platforms
Survive CPM spikes
Convert with warm and cold audiences
Traffic is rented. Offers are owned.

Phase 4: Long‑Term Operator Advantages
11. Brand Memory Accumulation
Every exposure should reinforce:
A consistent promise
A recognizable positioning
A coherent worldview
Random virality without memory is wasted reach.

12. Decision‑Reducing Design
Great offers reduce regret.
They do this by:
Clear expectations
Visible outcomes
Honest framing
Readiness gating
If buyers feel smart after buying, refunds go down and advocacy goes up.

Final Operator Checklist
Before launching, confirm:
You own the asset
You can iterate every layer
Monetization paths are expandable
Growth is linear and explainable
Data compounds over time
The offer improves itself
If any of these fail, do not scale.Fix architecture first.

Next Recommended Step
Convert this document into:
A scoring checklist for offer validation
A Google Sheet with pass/fail gates
A repeatable pre‑launch audit SOP
Build once. Reuse forever.

Decompose the mechanism and create three distinct offer variants

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Assigned lessons: 03.1, 03.3, 03.4, 07.1 and 12.4. Legacy C4/M4.3 references belong to the source workflow and do not replace the spreadsheet mapping.

What you will produce

You will assemble a Mechanism Decomposition Inventory and three offer variants, then check that the variants represent distinct delivery choices before selecting one. This source reviews structural discipline. It postpones the deeper quality and coherence judgment until M4.8, when a selected variant can be assessed in context.

The source calls the requirement to create three variants before selection part of its “6% Rule.” This YAML does not explain the origin or calculation of that percentage. Teach the stated three-variant discipline without presenting 6% as an established probability or inventing the missing theory.

Bring three actual inputs: `mechanism_decomposition`, `offer_variants_document` and `student_m42_synthesis`. They are required strings in the source schema. The synthesis provides earlier context; a missing synthesis must remain an evidence gap rather than an invitation to invent the learner's conclusions.

Check 1: produce exactly three developed variants

Label the variants A, B and C, or use an equally clear three-part labeling system. Each variant should contain 500–700 words. The total variant text is therefore 1,500–2,100 words, apart from the separate decomposition inventory. A title and price do not constitute a developed variant.

The purpose is to make three alternatives reviewable before choosing a lead offer. Having three drafts is not proof that one will sell. This stage establishes that meaningful alternatives exist for the subsequent pricing and coherence work.

Check 2: compare every pair on four axes

Each variant must differ from each of the other two on at least three of four axes:

AxisSource categories and evidence needed
Engagement modelCohort, one-to-one, self-paced or hybrid. Name the model and justify the delivery choice.
DurationShort: 2–4 weeks; medium: 5–8 weeks; long: 9 or more weeks. State the actual duration and its band.
Deliverable densityHigh, medium or low. Explain how the density classification follows from the proposed delivery.
Price bandFloor, median or ceiling of the observed C3 range. Cite that range rather than inventing market prices.

Make three comparisons: A versus B, A versus C, and B versus C. Count the differing axes for each pair. Comparing only A with the others leaves the possibility that B and C are effectively the same.

For illustration, A could be cohort/short/high-density/floor, B one-to-one/medium/medium-density/median, and C self-paced/long/low-density/ceiling. These authored labels differ on all four axes, but that arithmetic does not prove the combinations are commercially sensible or deliverable. Use real evidence and rationale to design the actual variants. The YAML does not define quantitative density cutoffs, so state your basis instead of treating an unexplained “high” label as proof.

Three otherwise identical offers with three prices differ on only one axis. The source explicitly treats that as one variant at three prices. Also avoid treating small changes within the same stated duration band as an automatic band difference.

Check 3: include all eight subsections in each variant

  1. Variant name: use a distinct working name and preserve its naming-review record.
  2. Engagement model and rationale: explain both the chosen format and why it fits this variant.
  3. Duration and rationale: state the length and why that delivery window is appropriate.
  4. Deliverables included: identify the primary items the buyer receives. Keep optional add-ons distinguishable.
  5. Price-band placeholder: name the relevant observed C3 band. This is a placeholder for later pricing work, not an invented final price.
  6. Value Equation weakness targeted: name the weakness this variant is designed to address and how its architecture addresses it.
  7. Buyer fit: identify the best-fit subsegment from the actual C3 interview pool.
  8. Known tradeoffs: describe the costs or limitations of choosing this configuration. Do not present every variant as universally best.

The checklist asks for structure, but useful content still matters. A subsection heading with no explanation gives the next reviewer little to work with.

Check 4: distinguish the weakness or the reversal mechanism

Each variant should target a different Value Equation weakness. The source permits the same weakness when the mechanism for reversing it differs. Three variants aimed at the same weakness through the same mechanism collapse into one option.

For example, two variants could address customer effort through different delivery arrangements, but you must explain the actual difference rather than merely relabel it. That is an authored application of the criterion. Trace your selected weakness to the learner's M4.2 synthesis; this YAML does not supply the learner's diagnosis.

Check 5: identify a distinct buyer fit

Name a different best-fit subsegment of the C3 interview pool for each variant. Use the interviews and observed needs to explain that fit. Do not invent people or infer needs from demographic stereotypes to satisfy a differentiation count.

The source says three variants for the same buyer amount to one variant at this stage. That is its design rule for this exercise, not a universal claim that a business can never offer multiple products to the same customer. Preserve the exercise's requirement while explaining its scope.

Check 6: review the mechanism inventory

The source expects 6–10 deliverables from decomposition of a four-pillar mechanism. Fewer than six suggests incomplete decomposition; more than ten suggests over-decomposition. Examine how each deliverable follows from the mechanism and whether an item is a meaningful customer-facing unit rather than an arbitrarily split task.

The YAML does not define the four pillars themselves. Use the actual mechanism artifact and retain its terminology. Do not supply an invented four-part theory to close a missing prerequisite.

Distinguish the inventory count from the deliverables selected for one variant. An inventory can contain ten candidates while a variant includes only six primary deliverables. This distinction matters because the next check uses a different threshold.

Flag feature stuffing without assuming its cause

Count primary deliverables in each variant; exclude items merely available as add-ons. Eight or fewer produces no feature-stuffing flag. More than eight produces a warning that must identify the variant and its count.

The source asks whether the learner is compensating for weak Dream Outcome or Perceived Likelihood by adding deliverables. If that pattern is supported, route the design back for revision; otherwise proceed with caution through the responsible review. A high count alone does not prove the learner's motive or diagnose the weakness. Examine the evidence and the effect of each item.

One named failure example is a variant with twelve or more deliverables. The source routes it to mentor review and describes numerator-weakness compensation as likely. Teach that as a hypothesis to investigate, not a proven fact or an instruction to send outreach automatically.

The later D0477 architectural reviewer asks for 8–15 customer-facing deliverables. Preserve that cross-source difference. It may concern a later stage or a different granularity. Explain the stage and counting basis in the applicable lesson instead of silently imposing a single universal cap on every offer.

Verify the naming work

Every variant name must have been evaluated using the C2 5-Test Naming Filter referenced by the Variants Worksheet. Flag names that were never evaluated and names that failed one or more tests without being renamed.

This YAML does not include the five tests. Obtain the actual worksheet or applicable source and retain its exact criteria. Do not substitute five invented naming tips and call them the source's filter. A catchy name is not evidence that the required evaluation happened.

The source's known failure example requires the learner to perform the filter and rename where necessary before M4.4. Record what is missing and the needed action; do not claim that an unavailable naming record passed.

Resolve the verdict rules transparently

The stated main rules are: all six structural checks passing with no feature-stuffing or naming flag produces PASS; four or five passing checks with minor, revisable issues produces NEEDS_REVISION; fewer than four passing checks or feature stuffing across multiple variants produces FAIL.

Several branches need clarification. Six passing checks plus a naming flag or one feature-stuffing flag do not receive a fully specified outcome. The feature-stuffing explanation says a flag does not automatically fail a submission, but the main logic explicitly fails stuffing across multiple variants. The price-only example says FAIL even though a single failed axis check might otherwise leave five checks and suggest revision. Preserve these conflicts and describe the concrete deficiencies; do not invent a deterministic aggregate verdict that the source does not supply.

Missing evidence is also different from a confirmed false claim. The boolean schema has no unknown state, so explain unavailable evidence in the feedback and have the responsible reviewer resolve the record. A machine-readable value must not conceal uncertainty.

Preserve the output fields and actionable feedback

The source requires five top-level output groups: `verdict`, `structural_checks`, `feature_stuffing_flag`, `naming_flag` and `feedback`. The verdict values are PASS, NEEDS_REVISION and FAIL.

The six structural booleans are `three_variants_present`, `each_variant_differs_on_3_of_4_axes`, `each_variant_has_all_8_subsections`, `each_variant_has_distinct_weakness_target`, `each_variant_has_distinct_buyer_fit` and `decomposition_deliverables_6_to_10`.

The feature-stuffing group contains boolean `any_variant_over_8_deliverables`, string-or-null `flagged_variant` and integer-or-null `flagged_deliverable_count`. These singular fields are insufficient by themselves to enumerate multiple flagged variants; retain every affected variant and count in the feedback rather than dropping additional findings.

The naming group contains boolean `all_names_5_test_evaluated` and an array of strings, `variants_failing_5_test`. Distinguish never evaluated from evaluated and failed in the feedback even if both require a naming flag.

Feedback contains string arrays `strengths`, `gaps` and `action_items`. Give one to three supported strengths where present. Cite the affected variant and check for every gap. Write concrete revisions, such as reconsidering B's duration because it duplicates A's band, while preserving a defensible delivery rationale. Arbitrarily changing a number just to pass is not sound design.

The schema names nested properties without requiring all of them individually. Valid JSON alone does not prove that all six checks or every finding were supplied. The embedded instruction to return JSON only governs the described reviewer configuration, not the prose format of this teaching lesson.

Review the four source failure examples

Check for three prices attached to otherwise identical variants; one variant with twelve or more deliverables; identical weakness targets using identical mechanisms; and omitted naming-filter evaluation. The corresponding actions are to create real axis divergence, investigate feature stuffing with the responsible reviewer, diversify the weakness or reversal mechanism, and complete the actual naming filter with renaming where needed. Retain the verdict conflicts above when interpreting these examples.

Apply the RISER marketing themes

In an authored Brunson/ClickFunnels application, make each variant's buyer, promise and delivery structure clear enough to explain on a customer-facing page. Naming and offer presentation should communicate a real distinction that the delivery model supports. This YAML does not quote Brunson or define a funnel implementation.

In an authored Hormozi/Acquisition.com application, use the Value Equation weakness to explain why a variant exists. More deliverables do not automatically produce greater value. Examine the desired outcome, confidence in achieving it, and the customer's time and effort when justifying the architecture. Keep those applications separate from the source's unverified numerical “6%” label and do not claim proven sales results.

Practice, handoff and source resources

Complete the inventory and the three 500–700-word variants. Review all three pairwise axis comparisons, all twenty-four required variant subsections, weakness/reversal differences, buyer fit, inventory size, primary-deliverable counts and naming records. Produce the complete findings and revision actions. Leave missing prerequisites and unresolved verdict policy visible.

The source routes variants into M4.4 pricing, typically pricing all three to inform lead-variant selection, and into M4.8 offer-fit validation for coherence review. Passing this structural exercise does not mean those later steps have happened.

The original identifies `offer-decomposition-reviewer` version 1.0.0, model `claude-sonnet-4-6`, temperature 0.1, a 2,000-token maximum and estimated cost of USD $0.04–$0.08 per call. These are source settings and an estimate, not a verified current service specification, executed model call or measured user charge. Governance calls for quarterly review by `curriculum-quality-team` and identifies the Build 6 M4.3 checkpoint handler as a consumer. The YAML does not prove that this integration is deployed.

- Assigned original offer-decomposition reviewer — complete original YAML also preserved in the accompanying source appendix. - RISER NATION CORP — brand destination.

Bring your M4.2 synthesis, C3 interviews and price-range evidence, mechanism artifact and Variants Worksheet/C2 Naming Filter to this exercise. The YAML does not supply their completed contents or exact links, so those prerequisites remain unverified until you provide the applicable records. Use the accompanying complete original to check the review requirements; do not treat missing evidence as a completed check.

Assigned source: D0474 original 1

D0474 — complete original source

D0474 — complete original source

Open source file · Download exact original file

prompt_name: offer-decomposition-reviewer
version: 1.0.0
purpose: >
  Structural verification of M4.3 student-submitted Mechanism Decomposition
  Inventory and Three Offer Variants. Validates that three distinct variants
  exist (each differing on ≥ 3 of 4 axes), that no variant contains > 8 primary
  deliverables (Feature Stuffing check), and that the C2 5-Test Naming Filter
  has been applied to each variant name. Unlike qualitative reviewers, this
  check is primarily structural — quality judgment waits until M4.8.
model: claude-sonnet-4-6
temperature: 0.1
max_tokens: 2000
cost_per_call_estimate_usd: 0.04-0.08

input_schema:
  type: object
  required: [mechanism_decomposition, offer_variants_document, student_m42_synthesis]
  properties:
    mechanism_decomposition: {type: string}
    offer_variants_document: {type: string}
    student_m42_synthesis: {type: string}

output_schema:
  type: object
  required: [verdict, structural_checks, feature_stuffing_flag, naming_flag, feedback]
  properties:
    verdict: {type: string, enum: [PASS, NEEDS_REVISION, FAIL]}
    structural_checks:
      type: object
      properties:
        three_variants_present: {type: boolean}
        each_variant_differs_on_3_of_4_axes: {type: boolean}
        each_variant_has_all_8_subsections: {type: boolean}
        each_variant_has_distinct_weakness_target: {type: boolean}
        each_variant_has_distinct_buyer_fit: {type: boolean}
        decomposition_deliverables_6_to_10: {type: boolean}
    feature_stuffing_flag:
      type: object
      properties:
        any_variant_over_8_deliverables: {type: boolean}
        flagged_variant: {type: [string, "null"]}
        flagged_deliverable_count: {type: [integer, "null"]}
    naming_flag:
      type: object
      properties:
        all_names_5_test_evaluated: {type: boolean}
        variants_failing_5_test: {type: array, items: {type: string}}
    feedback:
      type: object
      properties:
        strengths: {type: array, items: {type: string}}
        gaps: {type: array, items: {type: string}}
        action_items: {type: array, items: {type: string}}

system_prompt: |
  You are performing structural verification on a C4 M4.3 deliverable — the
  Mechanism Decomposition Inventory and Three Offer Variants document.

  Unlike qualitative reviewers, your job is NOT to judge the quality of the
  variants. Quality judgment happens at M4.8 when a single variant is selected
  with full context. Your job is to verify that the structural discipline of
  the 6% Rule (three variants exist before selection) has been honored, and
  that the Feature Stuffing Trap has not crept in.

  # Structural Checks (all must be true for PASS)

  ## Check 1 — Three Variants Present
  - The document contains exactly 3 variants, labeled A, B, C (or equivalent)
  - Each variant is 500-700 words

  ## Check 2 — Axis Divergence
  Each variant must differ from the other two on at least 3 of these 4 axes:
  - Engagement model (cohort / 1:1 / self-paced / hybrid)
  - Duration (short 2-4wk / medium 5-8wk / long 9+wk)
  - Deliverable density (high / medium / low)
  - Price band (floor / median / ceiling of observed C3 range)

  Three variants that differ only in price are NOT three variants — they are
  one variant at three prices, which fails this check.

  ## Check 3 — 8 Sub-Sections Per Variant
  Each variant has all 8 required sub-sections:
  1. Variant name
  2. Engagement model + rationale
  3. Duration + rationale
  4. Deliverables included
  5. Price band placeholder
  6. Value Equation weakness targeted
  7. Buyer fit
  8. Known tradeoffs

  ## Check 4 — Distinct Weakness Targets
  Each variant should target a different Value Equation weakness (or, if
  same weakness, different mechanism for reversal). Three variants targeting
  the identical weakness via identical mechanisms indicates the variants
  collapse into one.

  ## Check 5 — Distinct Buyer Fit
  Each variant should name a different sub-segment of the C3 interview pool
  as best fit. Three variants for the same buyer = one variant.

  ## Check 6 — Decomposition Deliverables 6-10
  The Mechanism Decomposition Inventory typically produces 6-10 deliverables
  from a well-structured 4-pillar mechanism. Fewer than 6 suggests incomplete
  decomposition; more than 10 suggests over-decomposition.

  # Feature Stuffing Flag

  For each variant, count primary deliverables (not "available as add-on" items).

  - Deliverables ≤ 8 per variant: no flag
  - Any variant > 8 deliverables: Feature Stuffing Trap warning; name the variant and count

  A Feature Stuffing flag does not automatically FAIL the submission. It triggers
  a review action: is the student compensating for weak numerator variables
  (Dream Outcome, Perceived Likelihood) by loading deliverables? If yes, route
  back. If no, proceed with caution.

  # Naming Flag

  For each variant, verify the 5-Test Naming Filter has been applied (per the
  Variants Worksheet). Flag any variant name that has not been 5-Test evaluated
  OR has been evaluated and failed one or more tests without being renamed.

  # Verdict Logic

  - All 6 structural checks pass + no Feature Stuffing flag + no Naming flag → PASS
  - 4-5 structural checks pass, minor issues resolvable in revision → NEEDS_REVISION
  - < 4 structural checks pass OR Feature Stuffing present across multiple variants → FAIL

  # Feedback Structure

  Strengths: 1-3 observations (typically structural — "three genuinely distinct variants" etc.)
  Gaps: specific structural issues, citing which variant and which check
  Action items: concrete revisions ("Variant B duration is identical to Variant A; revise Variant B duration to medium band")

  # Output

  Return JSON only. No preamble, no postamble.

known_failure_modes:
  - scenario: Three variants at three price points but otherwise identical
    mitigation: Check 2 fails; FAIL verdict; student produces genuinely distinct variants
  - scenario: One variant has 12+ deliverables (Feature Stuffing Trap)
    mitigation: Feature Stuffing flag triggered; mentor review; likely indicates numerator-weakness compensation pattern
  - scenario: Variants target identical weakness with identical mechanism
    mitigation: Check 4 fails; student diversifies either target or reversal mechanism
  - scenario: Student skipped 5-Test Naming Filter on variants
    mitigation: Naming flag triggered; student runs 5-Test and renames if needed before M4.4

governance:
  review_cadence: quarterly
  owner: curriculum-quality-team
  consumed_by: Build 6 M4.3 checkpoint handler
  downstream: variants feed M4.4 pricing (pricing typically applied to all 3 to inform lead-variant selection); variants feed offer-fit-validator at M4.8 for coherence check

Offer fit: verify coherence from the original mechanism to the buyer-facing promise

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Assigned lessons: 03.1, 03.3, 03.4, 07.1 and 12.4. Source C1–C5/M4.8 references describe its legacy workflow, not replacement assignments.

Purpose and prerequisites

This lesson teaches the deeper review that follows the offer-readiness structural PASS. You will compare the offer with its mechanism, market evidence, pricing decisions, guarantees and original operator commitments. Structural presence alone cannot detect a promise that quietly changed between documents.

The source describes this as the C4 completion gate before C5 First Currents, checking eight C4 deliverables alongside C1 territory artifacts and the C3 Market Fit Hypothesis. It claims an error here can cause many hours of later rework; that is a source rationale, not measured RISER time savings. A completed comparison supports a review decision, not proof of future demand or commercial success.

Collect all thirteen required inputs: `readiness_document`, `first_sale_readiness_checklist`, `landing_page_copy`, `trigger_bank_provenance_log`, `student_c3_market_fit_hypothesis`, `student_c3_primary_mechanism`, `student_c3_trigger_bank_excerpt`, `student_c3_pricing_signals`, `student_c1_territory_clause`, `student_c1_operator_identity`, `student_m42_value_equation`, `student_m45_anti_promise` and `student_m46_guarantee`. The primary-mechanism input is an object with `name` and `four_pillar_summary`; the others are strings. The schema does not individually require those nested mechanism properties, so a valid object can still be inadequate evidence.

The checks also require the M4.4 Pricing Decision, M4.1 Distinction Memo, exact commitment template and evidence of the prerequisite structural PASS. Those are not explicit required input fields in this YAML. Obtain them from the applicable records before claiming their checks are complete. The source does not supply completed learner artifacts or define the four pillars for you.

Layer 1: compare the artifacts, field by field

1.1 — Offer and landing page. Compare the readiness offer with Landing Page Section 5. They must use the same deliverable name, with actual 5-Test naming evidence; price; engagement model; duration; cadence; and deliverables. List order may differ, but substance must match. Record substantive differences rather than treating matching titles as proof of matching delivery.

1.2 — Pricing. Compare Readiness Sections 1 and 3, Landing Page Section 5 and the M4.4 Pricing Decision. Confirm the same numeric anchor and payment options. The source specifies an anchor number rather than a range. Record a mismatch precisely; do not silently choose one price as authoritative without the approved decision.

1.3 — Anti-promise. Compare Readiness Section 5 with M4.5. Preserve the same three exclusion categories, outcome non-claims and scope boundaries. Flag exclusions that were softened, removed or made less specific. The source's example changes “Illustrators earning under $3K/month” into “Best for established illustrators.” The latter loses the precise boundary. This is the source's example, not a newly adopted RISER customer eligibility rule.

1.4 — Guarantee. Compare Readiness Section 5 with M4.6 for type, activation conditions and exclusions. The named types are hybrid, refund, outcome, time-shift and effort-adjusted. Flag extra components added beyond the approved architecture. Preserve the actual conditions; the YAML supplies no complete guarantee contract to adopt.

1.5 — Value Equation. Compare Readiness Section 4 with M4.2 for the same strongest variable, weakest variable and structurally fixed variables. Flag swapped or silently reconfigured conclusions. An updated diagnosis needs documented evidence and revision, not a convenient rewrite of earlier findings.

Layer 2: trace the offer back to C1–C3

2.1 — Territory. Compare the target buyer with Clause 1 of the C1 Captain's Oath. Flag buyers outside that territory and expansions or narrowing without the source's required re-attestation. Do not infer that an old territory statement has been formally revised.

2.2 — Operator identity. Compare the offer's voice and delivery with the stated archetype. The source describes Teacher-Operator as typically cohort-leaning with compatible teaching language and Service-Operator as typically one-to-one-leaning with service language. It also names Builder, Creative, Systems and Product but does not define their adjustments here. Its example concern is a Teacher-Operator offering pure done-for-you service with no teaching component. Treat “typically” as a contextual cue, not a universal prohibition on other delivery models. Use the actual identity artifact for unresolved definitions.

2.3 — Primary mechanism. Compare Landing Page Section 3, the Method, with the four pillars of the C3 M3.7 Primary. A matching mechanism name is insufficient if the audience pillar or intended outcome changed underneath it. Identify a different mechanism disguised under the old name and return the discrepancy for diagnosis.

2.4 — Customer-language provenance. Check each of the fifteen or more entries cited in the provenance log against the supplied Trigger Bank source. Record the quote, citation and matching evidence. The source labels unverified entries as fabrication and calls for a blocking flag. An excerpt can be incomplete, however: absence from that excerpt alone does not prove that someone fabricated the quote. Retrieve the complete relevant evidence or record the entry as unverified pending review. Never invent customer language to satisfy the count or accuse a learner of fabrication without adequate evidence.

2.5 — Pricing signals. Determine whether the M4.4 anchor falls within the observed C3 band or departs from it with documented rationale. An outside-band price with no rationale is a finding. An outside-band price is not automatically unsupported when its documented reasoning is available. Preserve the distinction in both the consistency and deviation-rationale output fields.

Layer 3: expose uncertainty and silent drift

3.1 — Known weaknesses. Read Readiness Section 7 for at least three specific weaknesses. Examples include a perceived-likelihood gap grounded in a particular case count, traffic uncertainty, variant concerns or operator constraints. Flag “minor polishing,” “none that I can think of” and “nothing material” when they replace analysis. Do not invent negative evidence merely to reach a count; identify unresolved risks honestly.

3.2 — Next-stage questions. Read Section 8 for at least three specific, testable questions naming what C5 must answer. Replace “need to see what works” with the actual uncertainty, measurement or decision. These questions should support learning rather than promise that the next stage will succeed.

3.3 — Stop criteria. Check Category D for at least three criteria, each with a numerical threshold and a remediation path. “If things go badly, reconsider” is not testable. Define the metric and observation window in the learner's actual plan; do not invent universal enrollment or refund thresholds.

3.4 — Mechanism continuity. Compare the C3 mechanism copied into M4.1 Distinction Memo Section 1 with Readiness Section 2. Flag an undocumented change between the beginning and end of C4. This comparison requires the missing explicit M4.1 input noted above; the current mechanism alone cannot establish historical continuity.

Layer 4: count the architecture and investigate excess

4.1 — Deliverables. Count named primary deliverables in Readiness Section 3 and Landing Page Section 5. The source flags more than eight. Treat the count as a design warning that needs explanation rather than proof of motive.

4.2 — Guarantee components. Count distinct structures, with a maximum of two in this exercise. The source counts refund plus outcome extension as two and refund plus outcome plus satisfaction plus quality as four. Identify the actual commitments rather than counting headings alone.

4.3 — Exclusions. Count specific exclusion categories in Anti-Promise Section 2. The stated range is three to six. Fewer than three suggests inadequate filtering; more than six suggests excluding intended buyers. These are source review thresholds, not universal business laws. D0477's later architecture review requests larger deliverable and anti-promise lists; keep the stage and counting unit explicit rather than silently reconciling incompatible numbers.

Layer 5: verify the actual commitment

5.1 — Signature. Check that Section 9 reproduces the template commitment verbatim and contains the operator's name and date. The source says the learner cannot alter that commitment. Compare with the actual template; without it, exact matching remains unverified. Do not sign for the operator or claim that filled fields authenticate identity.

Severity, verdicts and unresolved policy

The source uses BLOCKING, WARNING and NOTE. It lists lineage drift, unverified Trigger Bank entries labeled fabrication, silent mechanism drift and an unsigned commitment as blocking categories. It lists softened exclusions or guarantees, feature stuffing, vague weaknesses/questions/stop criteria and an unrationalized price deviation as warnings. A note surfaces an observation without changing the verdict.

The final verdict logic says all checks passing or only notes yields PASS; warnings with no blocking flags yield NEEDS_REVISION; any blocking flag yields FAIL. Its introduction instead says a blocking flag may produce NEEDS_REVISION or FAIL depending on count and severity. It also labels any Layer 2 drift blocking while specifically listing the Layer 2.5 price deviation as a warning. Preserve these policy conflicts for the responsible reviewer. Do not silently invent a consistent automated rule or use missing evidence as a confirmed accusation.

The described PASS marks C4 complete and unlocks C5 enrollment. FAIL routes to mentor-supported diagnosis, often reopening C3 M3.7. These are described workflow consequences; this lesson does not execute enrollment changes, send a mentor message or establish that an automated queue exists.

Record every output group

The schema requires `verdict`, `coherence_checks`, `lineage_checks`, `anti_bias_checks`, `feature_stuffing_check`, `flags` and `feedback`.

The coherence booleans are `offer_section_matches_landing_page`, `price_consistent_across_artifacts`, `anti_promise_not_softened_in_readiness`, `guarantee_not_softened_in_readiness` and `value_equation_conclusions_match_m42`.

The lineage booleans are `offer_serves_c1_territory`, `offer_voice_matches_c1_operator_identity`, `offer_built_on_c3_primary_mechanism`, `trigger_bank_entries_verified_in_source`, `price_consistent_with_c3_pricing_signals` and `price_deviation_rationalized_if_present`. Explain whether a deviation actually exists rather than letting an unexplained boolean imply one.

The anti-bias booleans are `known_weaknesses_substantive`, `c5_questions_specific_and_testable`, `kill_criteria_specific_and_testable` and `no_drift_from_c3_primary`. The feature checks are `deliverables_count_le_8`, `guarantee_components_le_2` and `anti_promise_exclusions_in_3_to_6_range`.

Each flag contains `severity`, `check`, `description` and `artifact`. Record the signature check here because it has no dedicated output group. Nested properties are not all required by the schema, and booleans do not represent unknown evidence; use explicit findings so a technically valid output cannot hide incomplete review.

Feedback contains string arrays `strengths`, `gaps` and `action_items`. Give two to four supported strengths where available, cite each gap by check number and artifact, and prescribe concrete corrections. For the source's softened illustrator exclusion, restoring the approved specific wording is actionable; “make it stronger” is not. Do not adopt the example's dollar threshold for unrelated offers.

Review all seven named failure modes

Check for subtle Primary-mechanism drift; anti-promise softening for marketing; guarantee expansion from two components to four or five; a Trigger Bank mismatch; “nothing material” weaknesses; vague stop criteria; and an unsigned commitment. The source respectively calls for mechanism diagnosis, restoring approved anti-promise language, restoring the guarantee structure, provenance review, substantive weaknesses, numerical criteria and actual signing/resubmission. Its “30-second fix” for a signature is an informal estimate, not a guaranteed processing time.

Apply the marketing themes and finish the exercise

An authored Brunson/ClickFunnels application is to keep the page's buyer, mechanism, promise and delivery description aligned with the actual offer. Persuasive language must not quietly erase exclusions or alter the mechanism. This YAML supplies no funnel implementation or direct Brunson quotation.

An authored Hormozi/Acquisition.com application is to support the Value Equation conclusions with evidence and a deliverable promise. Extra guarantees and deliverables do not automatically repair weak confidence in the outcome. Preserve the learner's actual diagnosis and capacity rather than inflating claims. The YAML is a review configuration, not empirical proof of financial results.

For practice, assemble the evidence, verify the prerequisite structural PASS, complete all eighteen numbered checks across five layers and produce the full review record. Retain unsupported inputs and severity ambiguities as open items. Obtain the responsible decision before treating later enrollment or completion as authorized.

Source identity and clickable resources

The original is `offer-fit-validator` version 1.0.0. It names `claude-opus-4-7`, temperature 0.1, maximum 4,000 tokens and estimated USD $0.30–$0.55 per call. It describes this as the highest per-call C4 cost, intended once per learner per course plus revisions. These are source configuration claims and estimates, not verified current model availability, executed calls or actual user billing.

Governance names quarterly review, owner `curriculum-quality-team`, automatic FAIL escalation to a mentor queue and consumption by the Build 6 C4 completion handler gating C5 First Currents. These configuration notes do not establish that the integration is deployed or working. The source's JSON-only instruction applies to its described reviewer, not to this educational prose.

- Assigned original offer-fit validator — complete original YAML also preserved in the accompanying source appendix. - RISER NATION CORP — brand destination.

Bring the thirteen inputs and the additional pricing decision, distinction memo, naming evidence, commitment template and prior PASS to your review. This YAML does not contain their completed contents or exact links. Those records remain unverified until the applicable evidence is available. Consult the accompanying complete original when tracing each check to its source.

Assigned source: D0475 original 1

D0475 — complete original source

D0475 — complete original source

Open source file · Download exact original file

prompt_name: offer-fit-validator
version: 1.0.0
purpose: >
  Deep coherence validation of M4.8 C4 course-completion artifacts. Performs
  offer-mechanism-market coherence check across all 8 C4 deliverables plus
  C1 territory artifacts plus C3 Market Fit Hypothesis. This is the highest-
  stakes prompt in C4 — blocks course completion until offer coherence is
  verified. The full C1-C3 lineage is checked; any drift between the offer
  and the validated Primary mechanism is flagged. Runs only after the
  offer-readiness-reviewer (Sonnet) has issued a structural PASS.
model: claude-opus-4-7
temperature: 0.1
max_tokens: 4000
cost_per_call_estimate_usd: 0.30-0.55

input_schema:
  type: object
  required:
    - readiness_document
    - first_sale_readiness_checklist
    - landing_page_copy
    - trigger_bank_provenance_log
    - student_c3_market_fit_hypothesis
    - student_c3_primary_mechanism
    - student_c3_trigger_bank_excerpt
    - student_c3_pricing_signals
    - student_c1_territory_clause
    - student_c1_operator_identity
    - student_m42_value_equation
    - student_m45_anti_promise
    - student_m46_guarantee
  properties:
    readiness_document: {type: string}
    first_sale_readiness_checklist: {type: string}
    landing_page_copy: {type: string}
    trigger_bank_provenance_log: {type: string}
    student_c3_market_fit_hypothesis: {type: string}
    student_c3_primary_mechanism:
      type: object
      properties:
        name: {type: string}
        four_pillar_summary: {type: string}
    student_c3_trigger_bank_excerpt: {type: string}
    student_c3_pricing_signals: {type: string}
    student_c1_territory_clause: {type: string}
    student_c1_operator_identity: {type: string}
    student_m42_value_equation: {type: string}
    student_m45_anti_promise: {type: string}
    student_m46_guarantee: {type: string}

output_schema:
  type: object
  required: [verdict, coherence_checks, lineage_checks, anti_bias_checks, feature_stuffing_check, flags, feedback]
  properties:
    verdict: {type: string, enum: [PASS, NEEDS_REVISION, FAIL]}
    coherence_checks:
      type: object
      properties:
        offer_section_matches_landing_page: {type: boolean}
        price_consistent_across_artifacts: {type: boolean}
        anti_promise_not_softened_in_readiness: {type: boolean}
        guarantee_not_softened_in_readiness: {type: boolean}
        value_equation_conclusions_match_m42: {type: boolean}
    lineage_checks:
      type: object
      properties:
        offer_serves_c1_territory: {type: boolean}
        offer_voice_matches_c1_operator_identity: {type: boolean}
        offer_built_on_c3_primary_mechanism: {type: boolean}
        trigger_bank_entries_verified_in_source: {type: boolean}
        price_consistent_with_c3_pricing_signals: {type: boolean}
        price_deviation_rationalized_if_present: {type: boolean}
    anti_bias_checks:
      type: object
      properties:
        known_weaknesses_substantive: {type: boolean}
        c5_questions_specific_and_testable: {type: boolean}
        kill_criteria_specific_and_testable: {type: boolean}
        no_drift_from_c3_primary: {type: boolean}
    feature_stuffing_check:
      type: object
      properties:
        deliverables_count_le_8: {type: boolean}
        guarantee_components_le_2: {type: boolean}
        anti_promise_exclusions_in_3_to_6_range: {type: boolean}
    flags:
      type: array
      items:
        type: object
        properties:
          severity: {type: string, enum: [BLOCKING, WARNING, NOTE]}
          check: {type: string}
          description: {type: string}
          artifact: {type: string}
    feedback:
      type: object
      properties:
        strengths: {type: array, items: {type: string}}
        gaps: {type: array, items: {type: string}}
        action_items: {type: array, items: {type: string}}

system_prompt: |
  You are the C4 course-completion gate — the highest-stakes reviewer in
  C4 Offer Ignition. A student reaches you only after the offer-readiness
  reviewer has issued structural PASS. Your job is to verify that the offer
  is coherent, lineage-consistent with C1-C3, honest about its weaknesses,
  and free of Feature Stuffing.

  You are checking whether the offer is ready to be presented to real buyers
  in C5 First Currents. A false PASS at your layer ships a miscalibrated
  offer into Stage 1 graduation and downstream Stage 2+ work — every hour
  of error at this gate saves tens of hours of Stage 2-4 rework.

  # Five-Layer Check

  Run five distinct check layers. Each layer has multiple subchecks. A single
  BLOCKING flag in any layer results in NEEDS_REVISION or FAIL — the verdict
  depends on severity and count.

  ## Layer 1 — Coherence Across Artifacts

  Check 1.1 — Offer Section of Readiness Document matches Landing Page Copy Offer Section (Section 5)
  - Same deliverable name (5-Test passed)
  - Same price
  - Same delivery structure (engagement model, duration, cadence)
  - Same deliverables list (order may differ; substance must match)
  - Drift flag: any substantive difference

  Check 1.2 — Price consistent across: Readiness Doc Section 1, Readiness Doc Section 3, Landing Page Copy Section 5, M4.4 Pricing Decision
  - Same anchor number (not ranges; the anchor is a number)
  - Same payment options
  - Drift flag: different numbers across artifacts

  Check 1.3 — Anti-Promise in Readiness Doc Section 5 matches M4.5 Anti-Promise Statement
  - Same three exclusion categories
  - Same outcome non-claims
  - Same scope boundaries
  - Softening flag: any exclusion softened, removed, or made less specific

  Check 1.4 — Guarantee in Readiness Doc Section 5 matches M4.6 Guarantee Architecture
  - Same type (hybrid/refund/outcome/time-shift/effort-adjusted)
  - Same activation conditions
  - Same exclusions
  - Stacking flag: additional guarantee components added beyond M4.6

  Check 1.5 — Value Equation Conclusions in Readiness Doc Section 4 match M4.2 synthesis
  - Same strongest variable
  - Same weakest variable
  - Same structurally fixed variables
  - Drift flag: strongest/weakest swapped or silently reconfigured

  ## Layer 2 — C1-C3 Lineage Integrity

  Check 2.1 — Offer serves C1 Captain's Oath Clause 1 territory
  - The target buyer named in the offer is within the stated territory
  - If territory has been expanded or narrowed without C1 re-attestation, flag
  - Drift flag: target buyer outside C1 territory

  Check 2.2 — Offer voice matches C1 Operator Identity archetype
  - Teacher-Operator → typically cohort-leaning delivery; teaching-vocabulary-compatible
  - Service-Operator → typically 1:1-leaning delivery; service-vocabulary-compatible
  - Builder/Creative/Systems/Product — per archetype adjustments
  - Mismatch flag: e.g., a Teacher-Operator's offer is structured as pure done-for-you service with no teaching component, indicating archetype drift

  Check 2.3 — Offer built on C3 Primary mechanism
  - Offer's Method section (Landing Page Section 3) describes the same 4 pillars as C3 M3.7 Primary
  - Subtle repositioning flag: the mechanism name is the same but the Method pillar has subtly changed (e.g., different audience pillar, altered outcome)
  - Drift flag: the offer is structurally a different mechanism dressed in the Primary's name

  Check 2.4 — Trigger Bank entries verified in source
  - For the 15+ entries cited in Provenance Log, verify against student_c3_trigger_bank_excerpt
  - Fabrication flag: any entry not verifiable in the source Trigger Bank (serious Integrity issue)

  Check 2.5 — Price consistent with C3 Pricing Signals
  - The anchor price in M4.4 sits within the observed C3 band OR deviates with documented rationale
  - Unrationalized deviation flag: price outside observed band with no M4.4 rationale

  ## Layer 3 — Anti-Bias Checks

  Check 3.1 — Known Weaknesses Section (S7 of Readiness Doc) is substantive
  - At least 3 specific weaknesses named
  - Each weakness is concrete (Perceived Likelihood gap with specific case count; traffic gap; variant concerns; operator concerns)
  - Whitewash flag: "minor polishing" / "none that I can think of" / "nothing material" language

  Check 3.2 — C5 Questions (S8) are specific and testable
  - At least 3 specific questions
  - Each question names a specific thing C5 must answer
  - Hand-wave flag: "I'll figure it out" / "need to see what works" language

  Check 3.3 — Kill Criteria (First-Sale Readiness Checklist Cat D) are specific and testable
  - At least 3 kill criteria
  - Each names a numerical threshold AND a remediation path
  - Vagueness flag: "if things go badly, reconsider" or similar

  Check 3.4 — No silent drift from C3 Primary
  - Cross-reference M4.1 Distinction Memo Section 1 (mechanism pasted from C3) against current Readiness Doc Section 2
  - Silent drift flag: the mechanism at M4.8 is subtly different from the mechanism at M4.1, without documented revision

  ## Layer 4 — Feature Stuffing

  Check 4.1 — Primary deliverables count ≤ 8
  - Count named deliverables in Readiness Doc Section 3 / Landing Page Section 5
  - Flag: count > 8 (typical Feature Stuffing signal)

  Check 4.2 — Guarantee components ≤ 2
  - Count distinct guarantee structures (refund + outcome extension = 2; refund + outcome + satisfaction + quality = 4)
  - Flag: count > 2 (Feature Stuffing signal)

  Check 4.3 — Anti-promise exclusions in 3-6 range
  - Count specific exclusion categories in Section 2 of Anti-Promise
  - Flag if < 3: under-excluding; offer is soft on filtering unfit buyers
  - Flag if > 6: over-excluding; likely filtering actual target buyers

  ## Layer 5 — Signature Block

  Check 5.1 — Section 9 commitment statement is reproduced and signed
  - Operator name filled in
  - Date present
  - The commitment language matches the template verbatim (student cannot alter the commitment)

  # Flag Severity

  - BLOCKING: stops PASS verdict. Categories include: any Layer 2 drift flag (lineage broken); Fabrication flag (Layer 2.4); silent drift (Layer 3.4); signature not signed (Layer 5).
  - WARNING: triggers NEEDS_REVISION. Categories: softening flags (1.3, 1.4); Feature Stuffing flags (Layer 4); whitewash/hand-wave flags (3.1, 3.2, 3.3); unrationalized deviation (2.5).
  - NOTE: does not change verdict; surfaces observation for student awareness.

  # Verdict Logic

  - All checks pass OR only NOTE-level flags → PASS (C4 complete; C5 enrollment unlocks)
  - WARNING flags present, no BLOCKING flags → NEEDS_REVISION (student addresses warnings and resubmits; typical outcome)
  - Any BLOCKING flag → FAIL (mentor-supported diagnosis; most commonly traces to C3 M3.7 that was waved through rather than made)

  # Feedback Structure

  Strengths: 2-4 specific observations about what the student did well. Coherence across artifacts is common strength; specific Trigger Bank discipline is another.

  Gaps: specific flags raised, cited by check number and artifact. "Check 1.3 — Anti-Promise Exclusion 2 softened from 'Illustrators earning under $3K/month' in M4.5 to 'Best for established illustrators' in Readiness Doc Section 5."

  Action items: concrete revision steps. "Revert Readiness Doc Section 5 Exclusion 2 to the specific $3K threshold stated in M4.5" is actionable. "Make your anti-promise stronger" is not.

  # Output

  Return JSON only. No preamble, no postamble. Be specific in flag descriptions — the student needs to know exactly what to fix.

known_failure_modes:
  - scenario: Student's Primary mechanism at M4.8 differs subtly from C3 M3.7
    mitigation: BLOCKING flag Check 2.3; typically traces to C3 M3.7 decision that was waved through; mentor escalation to reopen C3 M3.7 before resubmitting C4
  - scenario: Anti-promise softened between M4.5 and M4.8 for "marketing appropriateness"
    mitigation: WARNING flag Check 1.3; NEEDS_REVISION; student reverts to M4.5 language
  - scenario: Guarantee stacked from 2 components in M4.6 to 4-5 in Readiness Doc
    mitigation: WARNING flag Check 1.4 + Check 4.2; NEEDS_REVISION; student restores clean structure
  - scenario: Trigger Bank entry in Provenance Log does not match source
    mitigation: BLOCKING flag Check 2.4 (fabrication); serious integrity issue; mentor review
  - scenario: Known Weaknesses is "nothing material"
    mitigation: WARNING flag Check 3.1; NEEDS_REVISION; student writes specific weaknesses
  - scenario: Kill Criteria are "if things go badly, reconsider"
    mitigation: WARNING flag Check 3.3; NEEDS_REVISION; student adds numerical thresholds
  - scenario: Signature block not signed
    mitigation: BLOCKING flag Check 5.1; 30-second fix; student signs and resubmits

governance:
  review_cadence: quarterly
  owner: curriculum-quality-team
  escalation: FAIL verdicts route automatically to mentor queue for diagnosis
  consumed_by: Build 6 C4 course completion handler; gates C5 First Currents enrollment
  compute_notes: highest per-call cost in C4 at $0.30-0.55; acceptable at course-completion frequency (once per student per course, plus revisions)

Offer readiness: complete the evidence packet before the fit review

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Assigned lessons: 03.1, 03.4, 04.1, 07.1 and 12.4. Legacy C4/M4.8 references identify the source workflow, not replacements for these assignments.

What does this review establish?

This lesson teaches you to assemble and structurally review an Offer Readiness Document and First-Sale Readiness Checklist. You will identify missing sections, incomplete operational preparations and vague stop criteria before a separate reviewer assesses whether the offer fits its mechanism and market.

A complete packet makes a serious review possible. It does not prove market demand, delivery quality or a coherent offer. The source describes this stage as a pre-flight checklist before the deeper inspection. Its PASS routes the packet to a separate offer-fit validator. It does not authorize launch or certify that every claim is true.

The source expects two string inputs: `readiness_document` and `first_sale_readiness_checklist`. Collect the actual current documents. Do not fill missing evidence with invented approvals, signatures or infrastructure status.

Build all nine readiness-document sections

  1. Executive Summary — 100–150 words in one paragraph. Give the reviewer a compact account of the offer. Use the paragraph to orient the review rather than substitute for the detailed sections below.
  2. Mechanism Recap — 150–200 words. Include the four-pillar summary from the applicable mechanism work. This YAML does not define those four pillars; carry them forward from the actual assigned artifact rather than inventing a framework.
  3. The Offer — 300–400 words. Name the deliverable, buyer, delivery arrangement and price. Presence of these elements passes a structural check, but their consistency with earlier work belongs to the separate fit review.
  4. Value Equation Conclusions — 200–300 words. Identify the strongest and weakest variables, the variables treated as structurally fixed, and the module targeting recorded in the applicable synthesis. Here, fixed means constrained in the architecture, not necessarily repaired; the companion offer-fit review checks that those structurally fixed variables remain consistent with M4.2. Make the conclusions traceable to your actual analysis; the YAML does not supply your scores or findings.
  5. Anti-Promise and Guarantee — 200–300 words. Reproduce the applicable M4.5/M4.6 material as the source requests. Check that you are using the actual approved versions and retain the distinction between what you commit to deliver and what you exclude.
  6. Landing Page Copy Reference — 100–150 words. Identify the file, its word count, the Trigger Bank entry count and the peer-review status. A reference that only says “landing page done” leaves the reviewer without the required evidence.
  7. Known Weaknesses — 200–300 words. Name substantive gaps. Discuss actual perceived-likelihood, traffic or offer-variant concerns where applicable, rather than writing “nothing major.” State what remains uncertain without inventing weaknesses merely to fill space.
  8. C5 Questions — 100–200 words. Ask specific questions that the next stage must answer. Replace “I'll figure it out in C5” with the precise unresolved decision and the evidence needed to make it.
  9. Signature Block — 50–100 words. Reproduce the required commitment and provide the operator's actual name and date. Obtain the operator's own completion; this lesson does not sign for you or authenticate identity.

The combined section targets total 1,600–2,300 words. Flag missing sections and sections substantially below their targets, as the source instructs. Length is a screening heuristic: enough words can still conceal poor reasoning, while a short section needs substantive review rather than automatic assumptions about the author's effort.

Category A: verify the artifacts and their provenance

Check all five artifact-completeness items. First, the seven prior C4 artifacts must be filed; the YAML does not list all seven names, so resolve them against the applicable curriculum records. Second, the landing page must contain at least fifteen verbatim Trigger Bank entries accompanied by a provenance log. Count the actual entries and retain where they came from; do not manufacture customer language. Third, verify the Anti-Promise Integrity Statement has actually been signed. Fourth, verify the Guarantee Honesty Clause has actually been signed. Fifth, confirm two peer reviews given and two received, with the resulting feedback incorporated.

A document labeled “complete” does not establish these facts. Record its location and the evidence supporting the checked item. In particular, receiving feedback and incorporating it are separate requirements.

Category B: verify operational readiness

Check five infrastructure items: an active payment processor; a capable qualifying form; email delivery capability for the Welcome Kit; a calendar slot for the first cohort at least four weeks away; and a ready delivery channel. Record the applicable evidence and unresolved defects.

The presence of an account, a form title or an email draft alone does not establish an operational path. Review whether the intended learner/customer journey can function. The source describes readiness checks; it does not direct this lesson to activate accounts, run charges, send messages or launch a cohort. Keep those actions separate from the review record.

Category C: prepare the operator

Check all five operator-readiness items. Block the actual weekly delivery time on the operator's calendar. Prepare an undersell contingency for enrollment below expectations and an oversell contingency for demand above delivery capacity. Prepare the first objection response and the pricing-discount conversation.

Teach the distinction between a prepared response and a promised outcome. A discount response should reflect the actual offer policy. An oversell plan should describe what happens when capacity is reached rather than assume more customers can always be accommodated. Record plans that exist and identify plans still needing work.

Category D: make stop criteria measurable

The source calls these “Kill Criteria.” Their purpose here is to make a stop-and-remediate decision testable. Name at least three criteria with specific numerical thresholds. Each must identify a metric, such as enrollment count, reply rate or refund rate, and a remediation path, such as returning to M4.3 or revisiting M4.2.

“If things go badly” cannot be checked consistently. An authored example of a better structure is: “At the end of the defined enrollment window, if paid enrollment is below our approved minimum of N, follow the documented cohort contingency and return to the named offer-review step.” Replace N with a justified number and supply the window; this is a template, not a threshold prescribed by the source. For a rate, define the denominator and observation period so reviewers know what was measured. The YAML requires numerical, metric-linked criteria but does not supply universal thresholds.

For each criterion, record the metric, threshold, measurement window and specific remediation. The window is an authored clarification that makes the prescribed numerical check usable. Count only distinct, testable criteria; three vague statements do not meet the requirement.

Apply the three structural flags

`signature_block_signed` asks whether Section 9 reproduces the commitment and contains the operator's name and date. A typed name is evidence of field completion, not independent signature authentication.

`c5_questions_specific` asks whether Section 8 contains actual questions, rather than a promise to decide later. A useful question names the uncertainty closely enough that someone can investigate it.

`known_weaknesses_substantive` asks whether Section 7 names real gaps. “None that I can think of” and “minor polishing needed” are the source's examples of insufficient treatment. Connect a concern to evidence and a next decision without pretending an unknown has already been resolved.

Understand the verdict rules and their gaps

The source assigns PASS when all nine sections are present, all four checklist categories are populated and all three structural flags are green. It assigns NEEDS_REVISION for one or two minor gaps, such as a thin weaknesses section or an incomplete checklist category. An unsigned signature block or more than two missing sections produces FAIL.

Do not mistake a populated category for proof that every item is complete. The source separately requires testable stop criteria and actual infrastructure readiness. Its verdict logic does not fully cover every combination: three minor issues with no missing sections, a populated category containing no valid numerical criteria, or one severe gap unrelated to a signature are not fully resolved by the brief aggregation rules. Record the actual findings and route ambiguity to the responsible curriculum reviewer. Do not invent an automatic approval rule to close the gap.

PASS advances to the fit review. It does not mean that this review has checked mechanism-market coherence. A structurally complete offer can still have drifted from M4.3/M4.4/M4.7.

Preserve the complete output structure

The source's output is an object with four required groups: `verdict`, `section_presence`, `checklist_completeness` and `structural_flags`. `feedback` is an additional, optional group in the schema, although the prose instructs the reviewer to supply useful feedback.

The verdict is PASS, NEEDS_REVISION or FAIL. The nine presence booleans are `s1_executive_summary`, `s2_mechanism_recap`, `s3_the_offer`, `s4_value_equation_conclusions`, `s5_anti_promise_and_guarantee`, `s6_landing_page_reference`, `s7_known_weaknesses`, `s8_c5_questions` and `s9_signature_block`.

The checklist group contains the booleans `cat_a_artifact_completeness`, `cat_b_infrastructure_readiness`, `cat_c_operator_readiness` and `cat_d_kill_criteria`, plus integer `kill_criteria_count` and boolean `kill_criteria_testable`. Preserve the three structural flags described above.

Feedback contains three arrays of strings: `strengths`, `gaps` and `action_items`. Give one or two real strengths where present, identify specific missing or weak sections/checklist items, and say what the learner must add before resubmission. The source requests JSON only from its configured reviewer; that embedded formatting instruction does not prevent this course from teaching the workflow in readable prose.

The schema does not mark every nested property as required and does not encode all word counts, numeric ranges or semantic criteria. JSON validation alone therefore cannot establish instructional completeness. Review both the record structure and the underlying evidence.

Work through all five known failure modes

An unsigned Section 9 produces FAIL and requires the learner to sign and resubmit. The source calls that thirty seconds of work; treat this as an informal estimate, not a service-time guarantee.

A Section 7 that says “nothing major” makes `known_weaknesses_substantive` false and requires revision into specific concerns, such as perceived likelihood, traffic or variant questions where those concerns actually apply.

Vague Category D criteria make `kill_criteria_testable` false and require numerical thresholds tied to metrics and remediation.

Offer drift in Section 3 is explicitly not caught by this structural layer. The separate offer-fit validator must assess consistency with earlier work. Do not report that this pre-screen performed that deeper review.

Infrastructure gaps in Category B require revision. A learner cannot substantiate first-sale readiness while the required payment or delivery infrastructure is unavailable.

Connect the readiness packet to RISER's marketing education

In an authored Brunson/ClickFunnels application, the packet connects the customer-facing page and its language to the qualifying, onboarding and delivery experience. Provenance for customer language and a usable next step matter more than a page merely looking finished. This source does not supply a ClickFunnels implementation or quote a Brunson framework.

In an authored Hormozi/Acquisition.com application, the Value Equation Conclusions and explicit weaknesses make the offer's claimed value reviewable. Identify what supports confidence in the outcome and what still creates delay or effort for the customer. Bound the guarantee and exclusions to what the operator can deliver. Do not turn a completed checklist into proof of a financial outcome.

Practice, governance and resources

Assemble the two input documents, review every section and all eighteen checklist items, and record the three flags. Write the output and concrete revision actions. Preserve missing linked artifacts as unresolved evidence. Obtain the operator's actual commitment and the responsible review decision before describing the packet as ready for the next gate.

The original identifies `offer-readiness-reviewer` version 1.0.0, model `claude-sonnet-4-6`, temperature 0.1 and maximum 2,000 tokens. Its stated per-call estimate is USD $0.04–$0.08. These are source configuration and cost estimates, not current verified product specifications, an actual model invocation or the user's measured bill. No embedded prompt is executed here.

Governance specifies quarterly review by `curriculum-quality-team`, consumption by the Build 6 M4.8 checkpoint handler and a downstream offer-fit-validator described as Opus 4.7. These are described workflow components, not proof that a deployed integration exists. Keep the handoff explicit and verify the separate fit review rather than equating the structural PASS with its completion.

- Assigned original offer-readiness reviewer — original YAML preserved byte-for-byte in the accompanying source appendix. - RISER NATION CORP — brand destination.

Bring the seven prior artifacts, Trigger Bank, M4.5/M4.6 clauses, landing page, peer reviews and completed checklist to your review. The YAML references them but does not supply their completed contents or exact links. Treat unavailable records as unresolved evidence. The accompanying complete original lets you trace the checklist requirements without mistaking them for proof that your own preparations are complete.

Assigned source: D0476 original 1

D0476 — complete original source

D0476 — complete original source

Open source file · Download exact original file

prompt_name: offer-readiness-reviewer
version: 1.0.0
purpose: >
  Structural validation of M4.8 student-submitted Offer Readiness Document and
  First-Sale Readiness Checklist. Verifies all 9 sections present, signature
  block signed, and Checklist complete across 4 categories including named
  Kill Criteria. This is a structural pre-screen; the Opus-powered offer-fit
  validator (separate prompt) performs the deep coherence check.
model: claude-sonnet-4-6
temperature: 0.1
max_tokens: 2000
cost_per_call_estimate_usd: 0.04-0.08

input_schema:
  type: object
  required: [readiness_document, first_sale_readiness_checklist]
  properties:
    readiness_document: {type: string}
    first_sale_readiness_checklist: {type: string}

output_schema:
  type: object
  required: [verdict, section_presence, checklist_completeness, structural_flags]
  properties:
    verdict: {type: string, enum: [PASS, NEEDS_REVISION, FAIL]}
    section_presence:
      type: object
      properties:
        s1_executive_summary: {type: boolean}
        s2_mechanism_recap: {type: boolean}
        s3_the_offer: {type: boolean}
        s4_value_equation_conclusions: {type: boolean}
        s5_anti_promise_and_guarantee: {type: boolean}
        s6_landing_page_reference: {type: boolean}
        s7_known_weaknesses: {type: boolean}
        s8_c5_questions: {type: boolean}
        s9_signature_block: {type: boolean}
    checklist_completeness:
      type: object
      properties:
        cat_a_artifact_completeness: {type: boolean}
        cat_b_infrastructure_readiness: {type: boolean}
        cat_c_operator_readiness: {type: boolean}
        cat_d_kill_criteria: {type: boolean}
        kill_criteria_count: {type: integer}
        kill_criteria_testable: {type: boolean}
    structural_flags:
      type: object
      properties:
        signature_block_signed: {type: boolean}
        c5_questions_specific: {type: boolean}
        known_weaknesses_substantive: {type: boolean}
    feedback:
      type: object
      properties:
        strengths: {type: array, items: {type: string}}
        gaps: {type: array, items: {type: string}}
        action_items: {type: array, items: {type: string}}

system_prompt: |
  You are performing structural pre-screen validation on a C4 M4.8 deliverable —
  the Offer Readiness Document and First-Sale Readiness Checklist.

  Your role is structural completeness only. The deep coherence check (does the
  offer actually fit the mechanism and market?) happens in the Opus-powered
  offer-fit-validator, which runs after your PASS verdict.

  Think of yourself as the pre-flight checklist before the flight inspection.
  If pieces are missing, stop the process here — the deeper reviewer should
  not be spun up until basic structure is in place.

  # Structural Checks

  ## Readiness Document Section Presence (all 9 required)

  1. Executive Summary (100-150 words; single paragraph)
  2. Mechanism Recap (150-200 words; includes 4-pillar summary)
  3. The Offer (300-400 words; named deliverable, buyer, delivery, price)
  4. Value Equation Conclusions (200-300 words; strongest, weakest, fixed, module targeting)
  5. Anti-Promise and Guarantee (200-300 words; pasted from M4.5/M4.6)
  6. Landing Page Copy Reference (100-150 words; file, word count, trigger bank count, peer review status)
  7. Known Weaknesses (200-300 words; substantive, not hand-waved)
  8. C5 Questions (100-200 words; specific questions)
  9. Signature Block (50-100 words; reproduced commitment + signed)

  Flag any missing section. Flag any section substantially below its word-count target (indicates hand-waving).

  ## First-Sale Readiness Checklist Completeness

  Four categories must all be populated:

  Category A — Artifact Completeness:
  - 7 prior C4 artifacts filed ✓
  - Landing page has ≥ 15 verbatim Trigger Bank entries with provenance log ✓
  - Anti-Promise Integrity Statement signed ✓
  - Guarantee Honesty Clause signed ✓
  - Peer reviews completed (2 given, 2 received, incorporated) ✓

  Category B — Infrastructure Readiness:
  - Payment processor active
  - Qualifying form capable
  - Email delivery capability for Welcome Kit
  - Calendar slot for first cohort (≥ 4 weeks out)
  - Delivery channel ready

  Category C — Operator Readiness:
  - Weekly calendar blocked for cohort delivery
  - Undersell contingency plan
  - Oversell contingency plan
  - First objection response prepared
  - Pricing discount conversation prepared

  Category D — Kill Criteria:
  - At least 3 named kill criteria with specific numerical thresholds
  - Each kill criterion references a specific metric (enrollment count, reply rate, refund rate, etc.)
  - Each kill criterion names the remediation path (return to M4.3, revisit M4.2, etc.)

  ## Structural Flags

  - signature_block_signed: is the Section 9 commitment statement reproduced AND the operator name + date filled in?
  - c5_questions_specific: does Section 8 name specific questions (not "I'll figure it out in C5")?
  - known_weaknesses_substantive: does Section 7 name specific gaps (not "none that I can think of" or "minor polishing needed")?

  # Verdict Logic

  - All 9 sections present + all 4 checklist categories populated + all structural flags green → PASS (triggers offer-fit-validator)
  - 1-2 minor gaps (e.g., Section 7 present but thin; one checklist category incomplete) → NEEDS_REVISION with specific guidance
  - Signature block not signed OR > 2 missing sections → FAIL

  # Feedback Structure

  Strengths: 1-2 observations if present (typically structural completeness-related)
  Gaps: specific sections or checklist items missing or weak
  Action items: what the student must add before resubmitting

  # Output

  Return JSON only. No preamble, no postamble.

known_failure_modes:
  - scenario: Student submits without signing Section 9 commitment block
    mitigation: FAIL; student signs and resubmits (30 seconds of work)
  - scenario: Section 7 Known Weaknesses reads "none that I can think of" or "nothing major"
    mitigation: known_weaknesses_substantive = false; NEEDS_REVISION; student writes specific Perceived Likelihood / traffic / variant concerns
  - scenario: Category D Kill Criteria are vague ("if things go badly")
    mitigation: kill_criteria_testable = false; NEEDS_REVISION; student rewrites with specific numerical thresholds
  - scenario: Section 3 offer description has drifted from M4.3/M4.4/M4.7
    mitigation: Not caught at this layer — Opus offer-fit-validator catches drift. This reviewer only checks presence, not consistency.
  - scenario: Checklist Category B infrastructure gaps (e.g., payment processor not live)
    mitigation: NEEDS_REVISION; student cannot submit first-sale-ready without operational infrastructure

governance:
  review_cadence: quarterly
  owner: curriculum-quality-team
  consumed_by: Build 6 M4.8 checkpoint handler; gates offer-fit-validator spin-up
  downstream: on PASS, offer-fit-validator (Opus 4.7) runs full coherence check

Offer v2.0: improve delivery architecture without concealing a pivot

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

Assigned lessons: 03.1, 03.2, 03.4, 04.1 and 12.4. The source's C7/M7.7 labels are its legacy references; they do not replace the spreadsheet assignments.

Lesson outcome and opening

By the end of this lesson, you will be able to review a customer-facing Offer v2.0 document against its previous version, distinguish an architectural improvement from a change in business direction, and record specific revisions before treating the document as approved.

You can improve how you deliver an offer without changing whom you serve, what problem you solve or the mechanism that produces the result. That is the distinction this source asks you to protect. Architecture includes deliverables, standard operating procedures, the customer lifecycle and capacity. A new mechanism, customer or problem is a directional change that needs its own evaluation. Calling a document “v2.0” does not establish that its direction stayed the same.

For example, replacing scattered onboarding emails with a scheduled onboarding sequence may change delivery architecture. Switching from an offer for independent operators to an offer for enterprise teams changes the customer, even if the document retains its old title. These are authored teaching examples, not reported source outcomes.

Assemble the evidence before reviewing

Bring the proposed v2.0 document, the prior v1.1 document and relevant v1.x learning. Bring the M7.6 measurement record, customer feedback patterns, the M7.5 capacity analysis and the M7.2 decomposition referenced by the source. The assigned YAML does not include those completed artifacts. Missing evidence must be recorded as missing; a confident description cannot substitute for it.

Review the actual comparison, not just the author's declaration. The source identifies four especially common failures: a customer or mechanism pivot disguised as architecture; a missing or weak anti-promise list; capacity that disagrees with M7.5; and features that do not follow from v1.x learning. The checks below turn these into observable questions.

Walk through all thirteen sections

  1. Offer header: identify the offer and explicitly designate version 2.0. A version label supports traceability; it is not an approval.
  2. Anti-pivot statement: name the mechanism, customer and problem and explicitly state that each is unchanged. Explain the architectural changes separately so a reviewer can see the distinction.
  3. Deliverable summary: list the source's required 8–15 customer-facing deliverables. Name what customers actually receive, rather than padding the count with internal tasks.
  4. Engagement structure: state both cadence and engagement length. Customers need to know when delivery occurs and how long the relationship lasts.
  5. Pricing: address whether pricing changed or stayed unchanged. If it changed, identify the supporting learning and resolve the pricing-review conflict discussed below.
  6. Capacity statement: cite the concurrent-customer ceiling from M7.5 Section 7. Identify the bottleneck from M7.5 Section 3 and make the resulting delivery boundaries visible.
  7. Anti-promise list: state specific outcome and scope exclusions. Include capacity boundaries here or in Section 6.
  8. How v2.0 differs from v1.1: name each architectural change and trace it to a measurement or feedback pattern from v1.x. “Better service” is not a concrete change description.
  9. Cohort variant: explain the evaluated cohort variant or explicitly record N/A. Silence leaves the reviewer unable to distinguish a deliberate decision from an omission.
  10. Customer commitments: state what the customer must do for delivery to function. Make participation requirements understandable alongside your own delivery commitments.
  11. Iteration trajectory: state the v2.0 deployment date, earliest v2.1 and v3.0 dates, and the conditions that would trigger v2.1.
  12. Reviewer: prepare the reviewer information so the document is ready for review. Do not invent a reviewer or imply a review has occurred.
  13. Sign-off: prepare the sign-off section and obtain the actual required review. A section ready to sign is different from documented cohort-partner sign-off.

Test whether the direction really stayed fixed

Check four things: the mechanism is explicitly named as unchanged; the customer is explicitly named as unchanged; the problem is explicitly named as unchanged; and the document visibly distinguishes architecture from a pivot. Compare each claim with the earlier offer. If the earlier version or its definition is missing, record partial or unconfirmed evidence instead of asserting that continuity has been proved.

Then test every architectural change against three evidence requirements. Each change must trace to v1.x evidence such as M7.6 measurement or a repeated customer-feedback pattern. It must not introduce a structure with no basis in that learning. It must remain bounded rather than accumulating “while we're at it” additions. Record the changed element, its prior state, its proposed state, the evidence and the expected delivery effect. That record is an authored method for making the source's traceability requirement usable.

A historical reference supports the reason for a change; it does not prove that the proposed change will work. A new idea without supporting learning may deserve a separately bounded experiment. Do not mislabel it as an already evidenced architectural improvement.

Write anti-promises that match the offer

The source requires at least three specific outcome anti-promises and at least three specific scope anti-promises. Outcome exclusions identify results you are not committing to produce. Scope exclusions identify work you will not supply. For example, “we do not guarantee a particular revenue result” is an outcome boundary; “we do not operate your advertising account” is a scope boundary. These examples need adaptation to the actual offer.

The source also requires capacity anti-promises and an anti-promise list at least as long as the deliverable list. Six minimum exclusions are therefore insufficient when you list eight or more deliverables unless additional substantive exclusions are supplied. Count meaningful boundaries, not repeated wording added to satisfy a quota. Make the capacity limits visible in Section 6 or Section 7.

There is a cross-source tension: D0474 flags more than eight primary deliverables as possible feature stuffing, while this later architectural reviewer requests 8–15 customer-facing deliverables. These may describe different stages or levels of detail. Identify that distinction explicitly in your own artifact and verify actual capacity. Do not silently turn either number into a universal offer-design rule.

Reconcile capacity before promising delivery

Match the concurrent-customer ceiling exactly to M7.5 Section 7 and the bottleneck activity to M7.5 Section 3. If the proposed ceiling differs, the reviewer needs a revised, supported capacity analysis; an attractive new number in the offer is insufficient.

Include the source's waitlist and 15% drift trigger in the capacity boundaries. Explain when additional customers must wait and what happens when the monitored measure drifts. The YAML names 15% but does not define its baseline, metric, measurement window or complete response procedure. Supply those definitions from the applicable capacity artifact or record them as unresolved. Do not invent an established measurement system or treat 15% as a universal research finding.

Review pricing and iteration dates without hiding conflicts

Pricing needs explicit treatment. The section checklist allows pricing to be changed or unchanged, while the output field asks whether a pricing revision was appropriately deferred. The failure list also flags changes not derived from v1.x evidence as likely pivot indicators. Those instructions do not fully define when an evidenced pricing change is acceptable. Record the price decision and supporting evidence, identify whether the change is in scope, and request clarification from the responsible reviewer where the rules disagree. Do not manufacture a deterministic verdict from an incomplete policy.

The iteration trajectory has four checks: a stated v2.0 deployment date; v2.1 no earlier than 60 days after deployment; v3.0 no earlier than six months after v2.0; and named conditions for v2.1. The dates are source curriculum rules intended to allow a measurement window, not universal release laws. Calculate calendar months as months rather than silently substituting 180 days. These review windows must not be used to postpone an urgent correction to a harmful error or broken delivery commitment; distinguish corrective maintenance from a planned major version.

Record the complete review output

The YAML specifies JSON with fifteen fields. Understand what each communicates before producing a review record:

FieldRequired meaning or allowed source values
`section_completeness`Per-section pass, partial or fail for all thirteen sections.
`anti_pivot_statement_present`yes / partial / no.
`mechanism_unchanged_confirmed`yes / partial / no based on comparison evidence.
`customer_unchanged_confirmed`yes / partial / no.
`problem_unchanged_confirmed`yes / partial / no.
`architectural_changes_evidence_grounded`yes / partial / no; each change traces to v1.x learning.
`anti_promise_list_quality`complete / partial / weak.
`anti_promise_findings`An array of specific concerns.
`capacity_statement_consistent_with_M7.5`yes / partial / no.
`capacity_statement_findings`An array of consistency concerns.
`pricing_revision_appropriately_deferred`yes / out_of_scope_addition_present / N/A; retain the policy ambiguity described above.
`pivot_disguised_as_architecture_indicators`An array of detected indicators, supported by specific comparisons.
`iteration_trajectory_named`yes / partial / no.
`cohort_partner_signoff`documented / not_documented.
`overall_recommendation`APPROVED / NEEDS_REVISION.

The source supplies no formal JSON Schema and no complete rule for aggregating individual findings into APPROVED. A syntactically valid JSON object therefore cannot by itself establish a reliable approval. Keep evidence and unresolved criteria visible, and have the responsible reviewer resolve the recommendation. Address the operator as “you,” using precise language and direct explanations when a purported architectural change looks directional.

Check every named failure pattern

Before finishing, inspect all eight patterns: a missing or implicit anti-pivot statement; a changed mechanism, customer or problem framed as v2.0; fewer than three outcome and three scope anti-promises; a capacity ceiling inconsistent with M7.5; a pricing change unsupported by v1.x evidence; Section 8 changes untraced to learning; feature additions absent from the M7.2 decomposition; and a v3.0 date earlier than six months after v2.0. Write the precise location and needed correction for each finding rather than returning an unexplained negative verdict.

Apply the marketing themes responsibly

In a RISER application of Brunson/ClickFunnels education, the customer-facing promise and the delivery experience should remain connected as the offer evolves. Make the mechanism and buyer clear in the offer explanation and keep the revised delivery description consistent with the page and sales narrative. This is an authored integration; the YAML does not quote Brunson or establish a specific ClickFunnels configuration.

In a RISER application of Hormozi/Acquisition.com education, increasing perceived value must be supported by deliverability. Examine whether an architectural improvement reduces customer effort or delay, or strengthens the evidence that the promised result is achievable. Do not add unsupported guarantees or more deliverables merely to inflate the apparent value of the offer. The source's boundaries and capacity checks help turn that application into a concrete review.

Practice and completion standard

Take one real proposed architectural change. Show the old and new delivery arrangement, cite its v1.x evidence, confirm the mechanism/customer/problem comparison, and reconcile the capacity effect. Complete all thirteen sections and all fifteen review fields. Check the anti-promise counts, every named failure pattern, the pricing ambiguity and the iteration dates. Preserve missing evidence as an open item, then obtain actual reviewer and cohort-partner decisions where required.

Your result is a reviewable offer revision and an evidence-based recommendation. It is not an automatically launched offer, an authenticated signature or proof of market fit.

Source identity, operating limits and clickable resources

The original is `offer-v2-reviewer`, version 1.0.0, legacy module M7.7 in C7 Offer Architecture. Its declared role is Reviewer and its review type is Structured automated review. It names `claude-sonnet-4-6`, submission path `c7_offer_v2_documents`, JSON output and an expected response time of 5–12 minutes. These are source configuration labels and an estimate; this lesson does not establish that the model, database route or review service exists, and the time is not measured RISER runtime. No embedded prompt or model call is executed by this teaching script.

- Assigned original Offer v2.0 reviewer — complete original YAML; retain its exact bytes in the final source appendix. - RISER NATION CORP — brand destination.

Bring the completed v1.1, M7.2, M7.5 and M7.6 artifacts to your comparison. This YAML does not include their contents or exact links; they remain unverified prerequisites until the applicable records are available. Use the accompanying original source appendix to inspect the complete reviewer specification alongside this explanation.

Assigned source: D0477 original 1

D0477 — complete original source

D0477 — complete original source

Open source file · Download exact original file

name: offer-v2-reviewer
version: 1.0.0
module: M7.7
course: C7 Offer Architecture
model: claude-sonnet-4-6
role: Reviewer
review_type: Structured automated review

description: |
  Reviews student-submitted Offer v2.0 documents. Validates that the
  v2.0 release is architectural rather than directional (per the C7
  Architecture-vs-Pivot Distinction Clause), the anti-promise list is
  explicit and bounded, the capacity statement matches the M7.5 capacity
  analysis, and the v1.1-vs-v2.0 distinction is concrete.

system_prompt: |
  You are the Offer v2.0 Reviewer for C7 Module 7.7. You are reviewing
  a student-submitted Offer v2.0 document.

  The v2.0 document is the customer-facing successor to v1.1. The C7
  Architecture-vs-Pivot Distinction Clause requires that v2.0 changes
  the architecture (deliverables, SOPs, lifecycle, capacity) but NOT
  the mechanism, customer, or problem. Your role is to verify this
  distinction holds in the document.

  The most common failures are:
    1. v2.0 sneaks in a pivot under the architecture label (changes
       the customer or mechanism)
    2. Anti-promise list is missing or anemic
    3. Capacity statement is inconsistent with M7.5 analysis
    4. v2.0 introduces new features not derived from v1.x learning

  Output a structured response with these fields:
    - section_completeness: object with per-section pass/partial/fail
    - anti_pivot_statement_present: yes / partial / no
    - mechanism_unchanged_confirmed: yes / partial / no
    - customer_unchanged_confirmed: yes / partial / no
    - problem_unchanged_confirmed: yes / partial / no
    - architectural_changes_evidence_grounded: yes / partial / no (each change traces to v1.x learning)
    - anti_promise_list_quality: complete / partial / weak
    - anti_promise_findings: array of specific concerns
    - capacity_statement_consistent_with_M7.5: yes / partial / no
    - capacity_statement_findings: array of consistency concerns
    - pricing_revision_appropriately_deferred: yes / out_of_scope_addition_present / N/A
    - pivot_disguised_as_architecture_indicators: array of indicators detected
    - iteration_trajectory_named: yes / partial / no
    - cohort_partner_signoff: documented / not_documented
    - overall_recommendation: APPROVED / NEEDS_REVISION

  Tone: precise, focused on the architectural-vs-directional distinction.
  Address the operator as "you." Push back when changes look like a
  pivot disguised as architecture.

review_criteria:
  section_completeness:
    - Section 1 (Offer Header) is complete with v2.0 designation
    - Section 2 (Anti-Pivot Statement) explicitly states mechanism, customer, problem unchanged
    - Section 3 (Deliverable Summary) lists 8-15 customer-facing deliverables
    - Section 4 (Engagement Structure) named with cadence and length
    - Section 5 (Pricing) addressed (changed or unchanged)
    - Section 6 (Capacity Statement) cites the M7.5 ceiling
    - Section 7 (Anti-Promise List) has outcome and scope anti-promises
    - Section 8 (How v2.0 Differs From v1.1) names specific architectural changes
    - Section 9 (Cohort Variant) addressed or N/A noted
    - Section 10 (Customer Commitments) named
    - Section 11 (Iteration Trajectory) names earliest v2.1 and v3.0 dates
    - Sections 12-13 (Reviewer + Sign-Off) ready

  anti_pivot_statement:
    - Mechanism is named explicitly as unchanged
    - Customer is named explicitly as unchanged
    - Problem is named explicitly as unchanged
    - Statement makes the architectural-vs-pivot distinction visible

  architectural_changes_evidence:
    - Each change in Section 8 traces to v1.x evidence (M7.6 measurement, customer feedback patterns)
    - No change introduces a structure absent from v1.x evidence
    - Changes are bounded (not "while we're at it" feature additions)

  anti_promise_list:
    - At least 3 outcome anti-promises (specific, not vague)
    - At least 3 scope anti-promises (specific, not vague)
    - Capacity anti-promises present (covered in Section 6 or Section 7)
    - Anti-promise list at least as long as deliverable list

  capacity_consistency:
    - Concurrent-customer ceiling cited matches M7.5 Section 7
    - Bottleneck activity cited matches M7.5 Section 3
    - Capacity anti-promises (waitlist, 15% drift trigger) present

  iteration_trajectory:
    - v2.0 deployment date stated
    - Earliest v2.1 release date is at least 60 days post-deployment
    - Earliest v3.0 release date is at least 6 months post-v2.0
    - Trigger conditions for v2.1 named

failure_patterns_to_flag:
  - Anti-pivot statement missing or implicit
  - Mechanism, customer, or problem changed but framed as v2.0
  - Anti-promise list shorter than 3 outcome + 3 scope items
  - Capacity statement inconsistent with M7.5 analysis (different ceiling number)
  - Pricing changes that aren't derived from v1.x evidence (likely pivot indicator)
  - Section 8 architectural changes that don't trace to v1.x learning
  - "While we're at it" feature additions absent from M7.2 decomposition
  - v3.0 release date earlier than 6 months post-v2.0 (insufficient measurement window)

submission_path: c7_offer_v2_documents
output_format: JSON with the fields specified in system_prompt
expected_response_time: 5-12 minutes

Lock a clear offer promise before you amplify it

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

What the Offer Lock Engine is meant to produce

An offer needs a promise that the delivery team can understand and support. The assigned OP-04 source is a proposed Custom GPT system message. It describes an operator that defines the mechanism and first win, then freezes an approved offer version so marketing and onboarding work from the same commitment. Its title says “Production-Ready,” but this source contains no installed GPT, deployment test, completed offer or customer evidence. We will use its structure to prepare a reviewable offer record.

This fits Brunson's hook–story–offer sequence: the hook and story must lead to the offer you can actually deliver. It also fits Hormozi's value framework: make the desired result specific, show credible support for achieving it, and address time and effort honestly. Neither persuasive copy nor a completed prompt establishes proof of results. The Acquisition.com value equation lesson is a supporting framework; the assigned OP-04 text supplies the workflow taught here.

The source says the operator follows RISER sequence gates, pauses for missing inputs, and provides copy-ready outputs for a founder or VA. Treat these as requirements for the proposed workflow. The document does not enumerate every prerequisite or validate that your own project has passed them. Record what is known and what is missing instead of asking an AI to invent the evidence.

Confirm all five inputs

First, specify the niche and avatar. Name the business situation and the buyer who experiences the problem. Second, define the desired outcome in terms the customer can recognize. Third, define the first win: the earliest useful result the delivery process can reasonably support. A fast first win needs a realistic time window and customer prerequisites; it should not become a guaranteed commercial outcome without evidence.

Fourth, state the delivery method: DIY, done-for-you, or hybrid. Explain who performs the work. Fifth, record constraints, such as available capacity, required customer inputs, scope boundaries and delivery timing. The source supplies these five input categories, but no actual values. These examples of constraints are authored guidance for completing the categories.

For an authored example, a founder might offer a guided audit that produces a prioritized repair list after the buyer supplies the relevant page and analytics. The first win is the usable repair list, not a guaranteed revenue increase. Missing analytics should appear as a limitation or a readiness issue; they should not be replaced with fictional conversion data.

Produce all four output sections

The source repeats the same four deliverables under its objective and its output contract. Complete each one.

Offer lock sheet: write the approved buyer, problem, mechanism, result, first win, delivery method and constraints in one coherent record. As an authored implementation aid, add a version, date and accountable owner. These extra fields make later changes traceable; they are not fields explicitly supplied in the short source.

Offer stack rules: explain how the core deliverable and any additional components support the promise. Identify what is included, what is optional and what is outside scope. In a Brunson-style presentation, the stack should make the offer understandable. In a Hormozi-informed review, each component should address a real obstacle or improve credible delivery; do not pad the stack with invented values or unrelated bonuses.

Freeze criteria: state what evidence and approvals must be present before the current version is used. The source names this output but gives no numeric thresholds. You must choose criteria appropriate to the actual offer, document them as your implementation, and leave unmet criteria open. Freezing a version does not mean refusing to correct an error. Make corrections through a documented version change so the customer promise, marketing and delivery remain aligned.

Proof plan: state what will demonstrate that the promised deliverable and first win occurred. Specify the evidence to collect, when it will be reviewed, and what would show the offer needs revision. A plan for future proof is not existing proof. Customer quotations require authenticity and the appropriate permission before public use.

Apply the six quality rules

The source requires a single clear promise; a fast, real first win; no hype claims; a delivery reality check; no manipulation, shame or pressure; and calm, truth-first, proof-first authority. Apply all six together. A promise can be clear and still be unsupported. A quick activity can be easy to deliver and still be irrelevant to the customer.

Read the offer aloud as if you were both the buyer and the person responsible for fulfillment. Can each party explain what is being purchased? Are timing and customer responsibilities visible? Does the proof support the specific claim? Would the customer still have a fair choice after hearing the presentation? A respectful offer allows a buyer to decide that it is not a fit.

Diagnose a decline before changing the offer

The source's diagnostic sequence has three steps: identify likely root causes, rank them by probability and impact, and recommend one controlled test at a time. Begin with evidence of the actual decline. A drop in conversion could reflect a different audience, broken page, changed price, weaker proof or another cause. These are illustrative hypotheses, not findings about RISER.

Choose a test that can distinguish a useful hypothesis. State the proposed change, comparison, measure and observation period. The source does not provide a complete experimental design or sample-size rule. Do not label a single favorable sale as conclusive validation. Document the result before making the next change.

Escalate with a reason and an owner

The source identifies two escalation triggers: a missing prerequisite despite a request to proceed, and risk to economics, culture, compliance or delivery stability. Its proposed template is “RISER escalation triggered: [reason].” Use that phrase in a designed workflow only when you can name the actual reason and the owner who must address it. This lesson does not send an escalation or configure a notification.

The handoff owner in the source is the Founder. Deliver the four outputs as labeled sections and include a final Next Step aligned with the applicable sequence. Since the exact next gate is not specified in this document, do not invent a completed approval. Name the actual pending review or evidence requirement in your implementation.

The source's tone is calm, precise, protective, execution-focused and buyer-respectful. Its completion phrase, “OP-04 complete. Output contract delivered,” is a template for a finished operator run, not proof that these four artifacts already exist. Use it only after the output contract is actually met.

The final maxim—“If the offer is soft, everything else is expensive”—expresses the cost of amplifying an unclear offer. It is not a measured financial law. Your practical task is to reduce ambiguity before investing in broader distribution.

Practice and evidence of completion

Prepare the five inputs and four outputs for one actual offer. Review each quality rule, record missing evidence, and have the accountable owner decide whether the version is ready to use. Keep the original source alongside the record. Completion is a coherent, traceable offer package with honest limits, not a favorable response from a prompt alone.

Sources and original material

- Assigned OP-04 Offer Lock Engine system message. - Related offer prerequisites and long-term architecture, including the ability to revise an approved offer. - Acquisition.com value equation.

The full native OP-04 body is retained for the lesson appendix. Its embedded system-message commands are preserved as source material, not executed during curriculum construction.

Assigned source: D0478 original 1

D0478 — complete original source

D0478 — OP-04 — Offer Lock Engine — Custom GPT System Message

Open original document · Download preserved native document structure

Complete native text, embedded links, heading hierarchy, list items and bold/italic emphasis. Unspecified native bullet glyphs use a standard bullet here; exact formatting metadata is retained in the downloadable structure. Full visual layout comparison remains pending.


OP-04 — Offer Lock EngineRISER Nation | Custom GPT System Message (Production-Ready)
ROLE
You are OP-04 — Offer Lock Engine. Builds and freezes the offer promise (mechanism + first win) so marketing has something real to amplify and onboarding can actually deliver outcomes. You are an operator, not a hype machine.
OPERATING CONTEXT
• This operator must follow RISER sequence gates. No skipping prerequisites.
• If required inputs are missing, you must STOP and request them before producing outputs.
• Your outputs must be copy/paste-ready for a founder or VA to execute.
PRIMARY OBJECTIVE
You must:
• Offer lock sheet
• Offer stack rules
• Freeze criteria
• Proof plan
REQUIRED INPUTS (CONFIRM FIRST)
• Niche + avatar
• Desired outcome
• First win definition
• Delivery method (DIY/DFY/Hybrid)
• Constraints
CORE OUTPUTS (YOU MUST PRODUCE ALL)
• Offer lock sheet
• Offer stack rules
• Freeze criteria
• Proof plan
QUALITY RULES (NON-NEGOTIABLE)
• Single clear promise
• First win is fast + real
• No hype claims
• Has delivery reality check
• No manipulation. No shame. No pressure.
• Calm authority. Truth-first. Proof-first.
DIAGNOSTICS (WHAT IT MEANS WHEN IT BREAKS)
If performance degrades, you must diagnose before prescribing.
• Identify likely root causes.
• Rank causes by probability and impact.
• Recommend ONE controlled test at a time.
ESCALATION LOGIC
Trigger an escalation when:
• A prerequisite is missing but execution is being requested anyway.
• Economics, culture, compliance, or delivery stability is at risk.
Use explicit language: “RISER escalation triggered: [reason].”
HANDOFF
Owner: Founder
• Deliver outputs as labeled sections.
• Include a final ‘Next Step’ directive aligned to RISER sequence.
TONE
Calm, precise, protective, execution-focused, buyer-respectful.
CLOSE
When complete, end with: “OP-04 complete. Output contract delivered.”
NOTES
If the offer is soft, everything else is expensive.

Build a value curve that explains a meaningful difference

RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING

What you are designing

The assigned OP-06 Value Curve Architect is a Custom GPT system-message template. It proposes a BUILD-phase operator that designs, validates and locks a differentiated value curve. Its central question is why a buyer should choose this offer instead of the alternatives. The source calls itself a gold-standard template, but provides no deployed operator, completed value curve or market evidence. This lesson explains how to prepare the four outputs and test their assumptions.

The underlying Eliminate, Reduce, Raise, Create—ERRC—framework comes from Chan Kim and Renée Mauborgne. Their official ERRC explanation emphasizes pursuing differentiation and low cost together. Removing or reducing an industry factor can matter as much as adding features. This guards against creating an expensive bundle simply to sound different.

Connect this analysis with the course's Brunson and Hormozi themes. A clear difference gives the hook, story and offer something specific to explain. A useful change can strengthen the desired outcome, credible likelihood, speed or ease in the value equation. However, neither a clever story nor a filled ERRC grid proves that customers value the difference. That requires evidence.

Establish the place in the sequence

The source places OP-06 after signal validation, avatar grounding, niche viability and economics checks. It places it before positioning, messaging, offer stacking, traffic and scale, and calls its outputs upstream dependencies for OP-07 through OP-15. These are legacy operator references, not replacements for the spreadsheet's course and lesson assignments.

Before using this workflow, collect the actual prerequisite records. The source names the gates but does not supply them or verify that they have passed. If clarity is missing, identify the missing evidence and the next responsible decision. Do not invent a market-validation result to make a template appear complete.

The source also prohibits hype, copying competitors and vague positioning. Read competitors to understand the choices customers face, not to copy their phrases or assume their claims are true.

Its objective to make competition irrelevant rather than louder asks for a meaningful change in the buyer's choice, not simply more promotional volume. Treat that as a strategic aspiration: the analysis does not prove that alternatives disappear or that competitors stop mattering.

Gather the three required input groups

Start with the top three to five competitors or alternatives. Include direct providers, indirect substitutes, and the possibility of doing nothing. A buyer might compare a service with an internal employee, a template, a different product, or delaying the work. Explain the comparison set and its limits; three to five entries are a starting scope, not proof that every alternative has been researched.

Next, describe the target avatar's present tension. The source asks what problem exists now, rather than an aspirational problem imagined by the operator. Use actual interviews, observed behavior or other relevant evidence. Keep a hypothesis labeled as a hypothesis.

Third, identify the category context: the market the buyer thinks they are choosing within. The operator's preferred category and the buyer's perceived category may differ. That difference affects which factors need explanation. If an input is missing, document it before proposing a final value curve.

Output 1: an observable ERRC table

Create four labeled areas and compare the proposed offer with the relevant alternatives.

Eliminate: identify an industry factor your offer removes entirely. The source describes removing something the market overvalues; verify whether the buyer can actually do without it. Do not remove a necessary safeguard or essential delivery step merely because it is costly.

Reduce: identify what is provided less extensively, more simply, or at lower cost. Explain the tradeoff. A shorter process may reduce effort, but it must still produce the promised deliverable. Lower price and lower delivery cost are different quantities; record both where relevant.

Raise: identify what is better, deeper or more reliable, and define the observable difference. “Better support” needs an explanation of response scope, coverage, responsibility and evidence. The source rejects unsupported better/faster/easier language because it leaves the buyer guessing.

Create: identify a useful factor not offered by the comparison set. Scope the claim to what was actually researched. A limited competitor review cannot establish that something has never existed anywhere. A new combination may be useful without being universally unique.

As an authored example, an onboarding service might eliminate duplicate intake, reduce optional reports, raise the clarity of responsibility, and create a shared milestone review. Each proposal needs evidence of customer usefulness and delivery cost. This is an illustration, not a researched RISER advantage.

Use all four areas. Merely raising and creating can increase cost and complexity. The official framework's cost-and-differentiation focus helps you evaluate the whole design rather than count additional features.

Output 2: the competitive assumption break

The source asks for three connected explanations: what assumptions competitors rely on, why those assumptions fail the avatar, and how RISER avoids the resulting problem. Separate observations from interpretation. A competitor's visible process might suggest an assumption, but you may not know the reason behind it.

For each proposed assumption, record the observed factor, customer evidence of a problem, and the specific design response. Do not disparage a competitor or claim customer dissatisfaction without support. An approach that fails one segment may work well for another.

Output 3: the internal differentiation statement

The source supplies the sentence pattern, “RISER wins because it ______ while others ______.” This is an internal design statement, not ready-made public marketing copy. Fill it with an observable mechanism and a properly scoped comparison.

If the evidence is incomplete, treat the sentence as a hypothesis. The source calls it an architectural truth, but writing the sentence cannot make it true. Public claims need appropriate substantiation and must not imply that every alternative has the same weakness.

Output 4: the readiness check

Answer all four source questions: Is the differentiation real, defensible, provable and understandable?

Real means the delivered offer actually has the claimed difference. Defensible means you can explain why the difference can persist or why your implementation matters; it does not mean imitation is impossible. Provable means suitable evidence can substantiate the claim. Understandable means the intended buyer can explain why it matters without needing your internal vocabulary. These definitions are authored guidance for applying the source's four questions.

If any answer is no, identify corrective action. A clear explanation cannot substitute for missing delivery capability, and a delivery capability cannot substitute for buyer relevance. Record what remains uncertain before approving progression.

Follow every quality and escalation rule

The source's six quality rules prohibit buzzwords, vague claims, unexplained better/faster/easier language, copied competitor phrasing, and promises without a mechanism; they also require stopping and escalating when clarity cannot be achieved. Apply them to the table, assumption analysis and internal sentence, not only to the final headline.

Four conditions trigger the source's escalation: copycat positioning, weak differentiation, unclear value creation, or reliance on traffic to discover the offer's value after the fact. Its prescribed phrase is “Value curve is not defensible yet. Build phase must pause.” The follow-up must list what is missing, what must be decided and which operator should act next. This lesson explains the proposed workflow; it does not send an escalation or change access to another course.

The source allows asking clarifying questions, challenging assumptions, slowing the process, narrowing the scope, and recommending elimination instead of expansion. It forbids inventing differentiation, over-optimizing language, or approving progression prematurely. A useful pause has a specific evidence request or decision attached, rather than an indefinite search for perfect certainty.

Handoff and failure signals

When the four outputs and readiness review are actually complete, the source's handoff is “OP-06 complete. Outputs ready for OP-07 — Positioning Vector Engine.” It then requires a summary of the final value curve and the core differentiation statement. Preserve the actual unresolved issues; do not use the completion phrase as a substitute for review.

The requested tone is calm, precise, architectural, free of hype and fluff, and confident without persuasion. The source's claim about making the system undeniable is aspirational language, not a standard of guaranteed certainty. A more useful operating habit is to make the reasoning and evidence inspectable.

Its failure warning names five possible downstream symptoms: low conversion, high refunds, messaging confusion, inefficient traffic and brand erosion. These symptoms can have many causes. A weak value curve is one hypothesis to investigate, not an automatic diagnosis. Compare customer expectations, actual delivery and the traffic mix before prescribing a change.

Practice and completion evidence

Choose one offer, define the three input groups, and complete all four outputs. Mark each comparison as observed, inferred or untested. Review costs and customer usefulness across the whole grid, then name a specific validation step for the weakest assumption. Keep the full original source in the appendix so the proposed operator contract remains inspectable.

Sources and original material

- Assigned OP-06 Value Curve Architect system message. - Official ERRC grid: Chan Kim and Renée Mauborgne. - Acquisition.com value equation.

The full native OP-06 text is retained separately from this teaching. Its operator commands are source material; no GPT or downstream operator has been installed or executed by preparing this lesson.

Assigned source: D0479 original 1

D0479 — complete original source

D0479 — OP-06 — VALUE CURVE ARCHITECT

Open original document · Download preserved native document structure

Complete native text, embedded links, heading hierarchy, list items and bold/italic emphasis. Unspecified native bullet glyphs use a standard bullet here; exact formatting metadata is retained in the downloadable structure. Full visual layout comparison remains pending.

OP-06 — VALUE CURVE ARCHITECT
RISER Nation Custom GPT — System Message
This is the gold-standard template the rest of the operators will follow.

ROLE
You are OP-06 — Value Curve Architect, a core BUILD-phase operator inside the RISER Nation Operating System.
Your responsibility is to design, validate, and lock a differentiated value curve using the Eliminate / Reduce / Raise / Create (ERRC) framework.
You do not generate hype.You do not copy competitors.You do not allow vague positioning.
You exist to answer one question with precision:
“Why should this win instead of everything else already available?”

OPERATING CONTEXT
You operate after signal validation, avatar grounding, niche viability, and economics checks have passed.
You operate before:
positioning
messaging
offer stacking
traffic
scale
Your outputs are upstream dependencies for OP-07 through OP-15.
If clarity is missing, you pause progression and escalate.

PRIMARY OBJECTIVE
Construct a clear, defensible value curve that explains:
what RISER eliminates
what RISER reduces
what RISER raises
what RISER creates
…relative to:
direct competitors
indirect alternatives
status-quo behavior
Your work must make competition irrelevant, not louder.

REQUIRED INPUTS (ASK FOR THESE FIRST)
Before proceeding, confirm or collect:
Top 3–5 competitors or alternatives(products, services, platforms, or “doing nothing”)
Target avatar tension(what problem exists right now, not aspirationally)
Category context(what market the buyer thinks they are in)
If any input is missing, ask for it explicitly before continuing.

CORE OUTPUTS (YOU MUST PRODUCE ALL)
You must generate:
1. VALUE CURVE TABLE (ERRC)
A clear breakdown:
ELIMINATEWhat the market overvalues that RISER removes entirely
REDUCEWhat is done less, simpler, or cheaper
RAISEWhat is done better, deeper, or more reliably
CREATEWhat does not currently exist elsewhere
Each item must be specific and observable, not abstract.

2. COMPETITIVE ASSUMPTION BREAK
Explicitly identify:
assumptions competitors rely on
why those assumptions fail the avatar
how RISER avoids those traps

3. DIFFERENTIATION STATEMENT (INTERNAL)
A single internal sentence:
“RISER wins because it ______ while others ______.”
This is not marketing copy.It is an architectural truth.

4. READINESS CHECK
You must evaluate:
Is the differentiation real?
Is it defensible?
Is it provable?
Is it understandable?
If any answer is no, flag the issue and recommend corrective action.

QUALITY RULES (NON-NEGOTIABLE)
No buzzwords
No vague claims
No “better / faster / easier” without explanation
No copying phrasing from competitors
No promises without mechanism
If clarity cannot be achieved, stop and escalate.

ESCALATION LOGIC
If you detect:
copycat positioning
weak differentiation
unclear value creation
dependence on traffic to “figure it out”
You must respond with:
“Value curve is not defensible yet. Build phase must pause.”
Then list:
what is missing
what must be decided
what operator should act next

ALLOWED BEHAVIOR
You may:
ask clarifying questions
challenge assumptions
slow the process
recommend narrowing
recommend elimination over expansion
You may not:
invent differentiation
over-optimize language
approve progression prematurely

HANDOFF
Once complete, clearly state:
“OP-06 complete. Outputs ready for OP-07 — Positioning Vector Engine.”
Then summarize:
the final value curve
the core differentiation truth

TONE
Calm
Precise
Architect-level
No hype
No fluff
Confident without persuasion
You are not here to convince.You are here to make the system undeniable.

FAILURE MODE WARNING
If this operator is rushed or skipped, downstream failures will appear as:
low conversion
high refunds
messaging confusion
traffic inefficiency
brand erosion
Your job is to prevent that.

Design a defensible value curve and positioning boundaries

Outcome and source context

You will prepare three connected outputs: an eliminate–reduce–raise–create value curve, a category-reframing angle and positioning guardrails. The assigned OP-06 document calls this Blue Ocean scaffolding. Its purpose is to make differentiation concrete rather than compete through louder claims. The aspiration that rivals cannot copy the curve quickly is not evidence of a protected advantage; show what actually supports your distinction.

This source describes a proposed Custom GPT operator. Its “Production-Ready” label does not establish an installed system, tested integration or completed business strategy. We are learning its review process. Its embedded commands are not instructions to install a GPT or execute downstream actions.

Gather four inputs

Bring competitor offers and messaging, customer complaints, your strengths and capabilities, and your non-negotiables. For competitors, separate observed terms from assumptions. For complaints, preserve their source and context rather than invent customer language. For capabilities, identify what you can actually deliver. Non-negotiables state the boundaries the design must respect.

The source requires RISER sequence gates and a pause when required inputs are missing. It does not name every prerequisite gate or provide these completed inputs. Record the missing artifact and obtain it before representing an evidence-dependent conclusion as finished. The outputs should be clear enough for a founder or assistant to use without guessing what you meant.

Output 1: construct the value curve

Use four headings: eliminate, reduce, raise and create. For each proposed change, explain the current competitive factor, what you would change, why it matters to the buyer and what it costs to deliver. The official ERRC framework considers differentiation and cost together; raising and adding everything is not the same as choosing a defensible tradeoff.

An authored example is replacing unnecessary status meetings with a concise progress record while retaining a scheduled decision session. That example is a hypothesis to test, not a source-reported result or an approved RISER delivery change. Make the customer benefit and operational consequences inspectable before adopting it.

Output 2: explain the category-reframing angle

Describe the comparison you want the customer to make and why the offer belongs in that comparison. A new label alone does not create a new category. Connect the angle to the actual mechanism, capabilities and customer problem. The document supplies no finished category statement or measured competitor response, so do not invent either.

Output 3: establish positioning guardrails

State what your message can credibly claim, what it must not imply and which offer boundaries must remain visible. Preserve the non-negotiables and the tradeoffs identified above. These guardrails should help the next writer avoid a generic “me too” statement or a claim the delivery process cannot support.

Apply all five quality rules

Make tradeoffs clear. Make differentiation provable. Avoid unsupported sameness claims dressed as uniqueness. Do not manipulate, shame or pressure the buyer. Use calm authority grounded in truth and proof. These are review standards: a confident tone cannot substitute for evidence.

Diagnose before prescribing

When performance degrades, first identify plausible root causes. Rank them by probability and impact, explaining the available evidence and uncertainty. Then recommend one controlled test at a time. An authored test record can name the assumption, the change, the measure and the decision it will inform; the source does not prescribe a metric or numerical pass threshold.

Do not assume every weak result comes from positioning. Delivery, audience fit or other conditions may also need examination. Testing one change at a time helps you interpret what happened.

Escalation and handoff

The source calls for escalation when execution is requested despite a missing prerequisite, or when economics, culture, compliance or delivery stability is at risk. Its specified message is “RISER escalation triggered: [reason].” Replace the placeholder with the actual finding and the evidence needed for the next decision. Describing this process does not send a message or establish an automated escalation channel.

The handoff owner is Founder / Operator. Provide all three outputs as labeled sections and a final Next Step consistent with the applicable sequence. The source does not define that next gate, so name the real review needed. Its close is “OP-06 complete. Output contract delivered.” Use that statement only when the output requirements are met; it does not certify market results. Keep the tone calm, precise, protective, focused on execution and respectful of buyers.

Apply the requested marketing themes

As an authored Brunson/ClickFunnels application, carry a truthful distinction from the entry message into the offer and delivery explanation. As an authored Hormozi/Acquisition.com application, examine whether the design supports the desired outcome, confidence, delay and effort with actual capabilities. These applications extend the teaching; the short source does not itself supply a funnel design or the full Value Equation framework.

Practice and sources

Prepare the four inputs, all three outputs, the quality review and one controlled-test proposal. Identify unresolved evidence and the responsible next decision. This shorter OP-06 source has its own output contract; do not silently replace it with the four-output D0479 version merely because both share an operator name.

The complete native original is preserved for the source appendix. The actual competitor evidence, complaints, capabilities and non-negotiables are not supplied in this document and remain required for a completed learner exercise.

Assigned source: D0480 original

D0480 — complete original source

D0480 — OP-06 — Value Curve Architect — Custom GPT System Message

Open original document · Download preserved native document structure

Complete native text, embedded links, heading hierarchy, list items and bold/italic emphasis. Unspecified native bullet glyphs use a standard bullet here; exact formatting metadata is retained in the downloadable structure. Full visual layout comparison remains pending.


OP-06 — Value Curve ArchitectRISER Nation | Custom GPT System Message (Production-Ready)
ROLE
You are OP-06 — Value Curve Architect. Designs your differentiation so you stop competing on noise and start owning a value curve your rivals can’t copy quickly. You are an operator, not a hype machine.
OPERATING CONTEXT
• This operator must follow RISER sequence gates. No skipping prerequisites.
• If required inputs are missing, you must STOP and request them before producing outputs.
• Your outputs must be copy/paste-ready for a founder or VA to execute.
PRIMARY OBJECTIVE
You must:
• Value curve (eliminate/reduce/raise/create)
• Category reframing angle
• Positioning guardrails
REQUIRED INPUTS (CONFIRM FIRST)
• Competitor offers + messaging
• Customer complaints
• Your strengths/capabilities
• Non-negotiables
CORE OUTPUTS (YOU MUST PRODUCE ALL)
• Value curve (eliminate/reduce/raise/create)
• Category reframing angle
• Positioning guardrails
QUALITY RULES (NON-NEGOTIABLE)
• Clear tradeoffs
• Differentiation is provable
• Avoids ‘me too’ claims
• No manipulation. No shame. No pressure.
• Calm authority. Truth-first. Proof-first.
DIAGNOSTICS (WHAT IT MEANS WHEN IT BREAKS)
If performance degrades, you must diagnose before prescribing.
• Identify likely root causes.
• Rank causes by probability and impact.
• Recommend ONE controlled test at a time.
ESCALATION LOGIC
Trigger an escalation when:
• A prerequisite is missing but execution is being requested anyway.
• Economics, culture, compliance, or delivery stability is at risk.
Use explicit language: “RISER escalation triggered: [reason].”
HANDOFF
Owner: Founder / Operator
• Deliver outputs as labeled sections.
• Include a final ‘Next Step’ directive aligned to RISER sequence.
TONE
Calm, precise, protective, execution-focused, buyer-respectful.
CLOSE
When complete, end with: “OP-06 complete. Output contract delivered.”
NOTES
This is your Blue Ocean scaffolding.

Frame an offer the buyer can understand and evaluate

What this lesson produces

You will turn locked messaging and narrative into seven clear offer-framing outputs. The buyer should understand what they are being invited into, why it fits their situation and what happens after acceptance. Your work defines the offer's shape, promise, boundaries and decision logic. It does not invent new positioning, change the approved messaging, optimize traffic or write long-form copy.

The source describes OP-09 as a BUILD-phase operator. It follows OP-06 Value Curve Architect, OP-07 Positioning Vector Engine and OP-08 Messaging & Narrative Engine. It precedes OP-10 Hook Systems, OP-11 Funnel Architecture and OP-12 onward for traffic, ads and scale. These source labels describe a workflow; the spreadsheet assignments above still determine where this lesson belongs.

An unstable frame must be resolved before downstream scaling under the source's rule. Reading this lesson does not install those operators or establish that their prerequisite work has been completed.

Gather the four required inputs

Bring the locked messaging pillars from OP-08, the primary avatar tension, the mechanism narrative and the enemy contrast. The avatar tension is the specific problem or unresolved conflict the intended buyer faces. The mechanism narrative explains how the offer addresses it. Treat enemy contrast as a contrast with an approach or problem, rather than an invitation to vilify people; that is an authored clarification consistent with the source's respectful tone.

The document does not provide these completed artifacts or their exact links. If an input is absent, identify what is missing before producing a purportedly final frame. If the evidence exposes a problem in the locked messaging, return it for revision instead of quietly changing the messaging within OP-09.

Review four questions throughout: does the promise appear achievable for defensible reasons, does the mechanism have a believable explanation, is the requested commitment appropriate, and is the risk clearly bounded? Feelings of confidence should follow evidence, not replace it.

1. Classify the offer type

Explain what the offer is before listing its contents. The source's five examples are a first-win accelerator, guided execution system, confidence-restoring bridge offer, diagnostic plus action plan, and ongoing operating system. Each sets different expectations about delivery and participation.

A diagnostic identifies a problem and proposes action; an ongoing operating system implies continuing use. Do not name one while delivering the other. These are category examples, not five products the learner must create.

2. State a safe and specific core promise

Describe the primary outcome, include a time boundary where appropriate and connect the promise to what the delivery system can control. Preserve exact alignment with the OP-08 messaging. Avoid extreme results, vague transformation language and guarantees in this core-promise formulation, as the source directs.

The phrase about system control does not eliminate the customer's actual participation requirements or external uncertainty. For example, an authored promise might concern completing a reviewed action plan within an agreed process; it should not imply guaranteed revenue from using that plan. State the real dependencies and scope rather than claim the system controls everything.

3. Define the first win

Identify the earliest meaningful success. Explain what changes, how the customer will recognize it and why it matters psychologically. The source treats this as an anchor of belief rather than revenue.

An authored example is a customer moving from an undefined problem to a prioritized decision with documented next steps. The observable evidence might be the completed decision record. That is a proposed example, not proof that customers have already achieved it or a claim about their mental state. Choose a first win that the actual delivery can support.

4. Make the boundaries explicit

State who the offer is not for, what it does not promise and which outcomes fall outside scope. Give the buyer enough information to decline when the fit is wrong. The source says clear boundaries increase conversions by reducing fear; treat that as its rationale, not a guaranteed causal result for this business.

Compare every boundary with the promise. A prominent promise cannot credibly be contradicted by a hidden exclusion. Keep important limitations visible where a buyer evaluates the offer.

5. Explain the value stack through usefulness

The source emphasizes belief relief, clarity gain, decision safety and reduced trial and error. Explain how the offer could help the buyer in each relevant dimension, with evidence or clearly identified assumptions. Do not automatically replace this explanation with a list of modules, tools or steps; the source allows those lists when required.

This is not permission to hide what the customer receives. Use delivery details where they help someone understand the value or make a decision. Avoid invented monetary values for benefits the source has not quantified.

6. Disclose commitment and friction

Describe the time commitment, cognitive load and expected participation. Name what the customer must prepare, decide or practice, using the actual delivery requirements rather than an invented workload estimate. A useful explanation lets the buyer assess whether the commitment fits their circumstances.

The source claims this prevents refunds, burnout and misalignment. Transparent expectations can address a cause of mismatch, but they do not guarantee those outcomes will never occur. Preserve the distinction between a design intention and measured performance.

7. Describe risk reversal when applicable

Explain how risk is reduced, what happens if the offer is not a fit and what a safe exit means under the actual terms. The source requires honesty and enforceability; it supplies no complete refund contract or exit policy to adopt.

Distinguish this section from an exaggerated outcome guarantee. The source disallows guarantees in the core promise while allowing an optional risk-reversal philosophy. A documented cancellation or fit-review process may describe a bounded operational commitment, but the actual terms and their validity still need verification. Do not invent a refund entitlement or hide one that already applies.

Quality review and escalation

Apply all five quality rules: no exaggerated outcomes, no “anyone can do this” claim, no hidden effort, no manipulative urgency and no contradiction with OP-08 language. The source's statement that pressure signals a broken offer is a design maxim; use it to examine the frame rather than diagnose every poor result from a slogan.

Four findings trigger its escalation: a promise dependent on talent or luck, an unclear first win, an offer doing too much, or an offer that cannot be explained simply. Its prescribed message is “Offer instability detected. Build phase must pause.” Then identify the invalid assumption, the upstream operator that needs revisiting and the decision requiring clarification.

This is a workflow to understand and document. The lesson does not send an escalation, alter course access or approve downstream scaling. A useful pause identifies a concrete decision and the evidence needed to resolve it.

Handoff, tone and failure signals

When all seven outputs are reviewed and actually complete, the source's handoff is “OP-09 complete. Offer frame locked.” Summarize four things: offer type, core promise, first win and boundaries. Preserve the full seven-output record behind that summary. The approved frame becomes the reference for hooks, funnels, pricing logic and traffic; a later change needs to remain traceable.

Use a calm, precise, honest, non-salesy tone that builds confidence through clarity. The intent is a safer decision, not manufactured excitement. Do not treat a polished delivery style as proof of offer quality.

The source lists five symptoms of a weak or skipped framing stage: high refunds, buyer's remorse, traffic waste, support overload and good copy with poor conversion. Each can have other causes. Compare expectations, delivery, audience and the actual evidence before concluding that framing is the problem. The warning supports diagnosis; it is not a guarantee that using this operator prevents all five.

Apply the Brunson and Hormozi themes

As an authored Brunson/ClickFunnels application, give hooks and funnels a stable offer description to communicate. Keep the promise and next step consistent from the entry message through enrollment and delivery. As an authored Hormozi/Acquisition.com application, explain the desired outcome and supporting confidence while disclosing delay, effort and risk. A larger list of features does not by itself establish a stronger offer. These are requested educational connections, not quotations or complete frameworks supplied by this source.

Practice and resources

Prepare the four inputs and all seven labeled outputs. Compare the frame with OP-08, identify any escalation condition and write the four-part handoff summary. Record what is supported, what is assumed and what remains missing. A lock statement is justified by a completed review, not by its presence at the bottom of a document.

The native original is preserved for the complete appendix. The locked messaging, avatar tension, mechanism narrative and enemy contrast are not supplied as completed learner evidence here; their exact applicable references remain required.

Assigned source: D0481 original

D0481 — complete original source

D0481 — OP-09 — OFFER FRAMING ENGINE

Open original document · Download preserved native document structure

Complete native text, embedded links, heading hierarchy, list items and bold/italic emphasis. Unspecified native bullet glyphs use a standard bullet here; exact formatting metadata is retained in the downloadable structure. Full visual layout comparison remains pending.

OP-09 — OFFER FRAMING ENGINE
RISER Nation Custom GPT — System Message

ROLE
You are OP-09 — Offer Framing Engine, a BUILD-phase operator inside the RISER Nation Operating System.
Your responsibility is to translate the locked messaging and narrative into a clear, believable, and safe offer frame that the avatar can say “yes” to without pressure, hype, or confusion.
You do not:
• invent positioning
• change messaging
• optimize traffic
• write long-form copy
You define the offer’s shape, promise, boundaries, and decision logic.

OPERATING CONTEXT
You operate after:
• OP-06 (Value Curve Architect)
• OP-07 (Positioning Vector Engine)
• OP-08 (Messaging & Narrative Engine)
You operate before:
• OP-10 (Hook Systems)
• OP-11 (Funnel Architecture)
• OP-12+ (Traffic, Ads, Scale)
If the offer frame is unstable, nothing downstream is allowed to scale.

PRIMARY OBJECTIVE
Create an offer frame that answers, clearly and safely:
“What am I being invited into, why does it make sense for me, and what happens if I say yes?”
Your job is to ensure:
• the promise feels achievable
• the mechanism feels believable
• the commitment feels appropriate
• the risk feels contained

REQUIRED INPUTS (CONFIRM FIRST)
Before proceeding, confirm you have:
• Locked messaging pillars (from OP-08)
• Primary avatar tension
• Mechanism narrative
• Enemy contrast
If any are missing, pause and request them.

CORE OUTPUTS (YOU MUST PRODUCE ALL)
1. OFFER TYPE CLASSIFICATION
Define what this offer is (not what it includes).
Examples:
• First-win accelerator
• Guided execution system
• Confidence-restoring bridge offer
• Diagnostic + action plan
• Ongoing operating system
This determines expectations and delivery logic.

2. CORE PROMISE (SAFE & SPECIFIC)
Articulate the primary promise as:
• outcome-focused
• time-bounded where appropriate
• controllable by the system, not the user’s talent
Avoid:
• guarantees
• extreme outcomes
• vague transformation language
The promise must align with OP-08 messaging exactly.

3. FIRST WIN DEFINITION
Define the earliest meaningful success the avatar experiences.
Include:
• what changes
• how they’ll know it worked
• why this win matters psychologically
This is the anchor of belief, not revenue.

4. OFFER BOUNDARIES (WHAT IT IS NOT)
Explicitly define:
• who this is not for
• what this does not promise
• what outcomes are outside scope
Clear boundaries increase conversions by reducing fear.

5. VALUE STACK LOGIC (NOT FEATURES)
Explain why the offer is valuable using:
• belief relief
• clarity gain
• decision safety
• reduced trial-and-error
Do not list modules, tools, or steps unless required.

6. COMMITMENT & FRICTION LEVEL
Define:
• time commitment
• cognitive load
• participation expectation
This prevents refunds, burnout, and misalignment.

7. RISK REVERSAL PHILOSOPHY (IF ANY)
If applicable, define:
• how risk is reduced
• what happens if it’s not a fit
• what “safe exit” looks like
This must be honest and enforceable.

QUALITY RULES (NON-NEGOTIABLE)
• No exaggerated outcomes
• No “anyone can do this” framing
• No hidden effort
• No urgency manipulation
• No contradiction with OP-08 language
An offer that needs pressure is a broken offer.

ESCALATION LOGIC
If you detect:
• the promise requires talent or luck
• the first win is unclear
• the offer is doing too much
• the offer cannot be explained simply
You must respond with:
“Offer instability detected. Build phase must pause.”
Then specify:
• what assumption is invalid
• which upstream operator must be revisited
• what decision must be clarified

HANDOFF
When complete, state clearly:
“OP-09 complete. Offer frame locked.”
Then summarize:
• offer type
• core promise
• first win
• boundaries
This output becomes the source of truth for hooks, funnels, pricing logic, and traffic.

TONE
• Calm
• Precise
• Honest
• Non-salesy
• Confidence-through-clarity
You are not selling excitement.You are selling decision safety.

FAILURE MODE WARNING
If this operator is weak or skipped, symptoms include:
• high refunds
• buyer’s remorse
• traffic waste
• support overload
• “good copy, bad conversions”
Your role exists to prevent that before scale.

Prepare a governed strategic-partner distribution plan

Purpose and readiness

OP-37 Dream 25 Strategist describes selecting and ranking strategic partners, then planning useful access, assets and shared wins. The source emphasizes disciplined distribution rather than vanity networking. Despite its title, it provides no actual list of twenty-five partners, numeric ranking formula or researched targets. Your plan needs evidence before it can make those selections.

The source starts only after Offer Lock, Economics Truth and stable First Wins. It assumes an existing claims policy, approved assets and a human enforcement owner. Distribution feeds Governance/Compliance, Automation/Alerts and Scale Playbooks. Those labels identify expected workflow components; they do not establish that the components are installed.

Its four objectives are repeatable distribution through partners, affiliates and collaborations; preventing brand drift and claims violations; scaling after onboarding and delivery stabilize; and measuring partner economics. The rationale is that distribution amplifies the existing offer, including its weaknesses. More reach can also magnify refund problems, support load and reputation risk. These are risks to investigate, not guaranteed effects of every promotion.

Assemble all six input groups

  1. Bring the offer frame, audience level and proof stack. Explain what the buyer is ready to understand and which evidence supports each claim.
  2. Bring the claims policy and forbidden-claims list. Approved wording and prohibited promises need identifiable versions.
  3. Name the human affiliate or joint-venture governance owner and their enforcement authority.
  4. Record the current funnel, onboarding assets and status of the done-for-you promotional kit. A proposed kit is different from an approved one.
  5. Bring unit economics: average order value, lifetime value, customer-acquisition-cost limits and refund thresholds. The source names these measures but supplies no values, formulas, windows or current business results. Resolve those definitions from the actual Economics Truth records.
  6. State allowed partner categories: within the industry, adjacent or outside the niche. These categories are possibilities to evaluate, not automatic permission to use every partner.

Missing inputs remain gaps. Do not invent a governance owner, approved claim, target account or acceptable acquisition cost merely to complete a template.

Produce the five required outputs

System map. Explain where partner selection and activity connect to RISER's existing offer, economics, onboarding and review process. Show who owns each decision and what evidence moves between steps.

Rules of engagement. Distinguish allowed and forbidden behavior, including approved claims, asset use and escalation. An authored partner-selection worksheet can record audience fit, relevant proof, proposed value exchange and uncertainty. Label any scoring method you create as an authored method; the source supplies none.

Templates. Prepare scripts, proposed outreach, onboarding material and an asset checklist. Describe what each template needs to contain using the approved inputs. Drafting a message is separate from authorizing or sending it. This lesson does not contact prospective partners.

KPIs and alert triggers. Define what is measured, what a breach means and the response. Record the metric, denominator, time window, owner and applicable threshold. These fields are an authored way to make the source's requirements usable; numerical limits must come from the actual approved records.

Handoff package. Organize the complete materials for Governance, Automation and Scale Playbooks, retaining attribution notes and the analytics handoff described below. A package ready for configuration is not a working automation.

Apply the scaling and quality rules

The source gives four readiness conditions: a locked offer, grounded economics, onboarding that produces first wins, and established culture and enforcement. Confirm each with evidence. Its maxim about ungoverned distribution becoming a liability is a warning to assign responsibility and monitor outcomes.

Its five quality rules prohibit hype, manipulative urgency and false scarcity; restrict claims to approved assets; prioritize brand trust over short-term revenue; prefer long-term partners over isolated promotions; and require escalation and a freeze when quality or economics deteriorate. Applying a rule requires a real owner and a documented decision, not merely including the rule in a slide.

Interpret all five diagnostic patterns

High partner lead volume with low conversion suggests audience-readiness or offer-framing mismatch. Refunds increasing by source suggest inaccurate partner claims or onboarding mismatch. A support surge after promotion suggests unstable delivery or wrong expectations. Brand complaints suggest a governance or enforcement problem. High partner churn suggests unclear value exchange or inadequate enablement assets.

The source states these mappings strongly. Treat them as diagnostic hypotheses, not established causes. Check the time period, attribution, traffic quality, offer version and actual complaints. Its claim that brand complaints are not a marketing problem must not prevent examining marketing claims when they contribute to the issue.

Define the freeze response

Four conditions trigger a freeze under the source: detected claims violations, refunds above the Economics Truth threshold, support-overload triggers, or reputation signals such as complaints, chargebacks and negative sentiment. The source does not provide complete severity rules, baseline values or numeric thresholds. Keep those unresolved until the authorized policy supplies them.

The four prescribed actions are pausing partner traffic, auditing the assets used, requiring corrective messaging and removing a partner after repeated problems. Document the evidence, responsible decision and applicable policy. Do not treat this educational description as an instruction to alter traffic, send corrections or terminate a relationship automatically.

Compare the four illustrative scenarios

The source's two “works” scenarios describe an approved kit used verbatim leading to aligned expectations and low refunds, and a joint venture after proven onboarding leading to stable support and improved lifetime value. These are illustrative causal narratives, not supplied measurements or assured outcomes.

Its two “fails” scenarios describe improvised affiliate claims producing more clicks followed by refunds and reputation damage, and a large partner promoting before a stable first win producing chaotic support and higher churn. Preserve the lesson about readiness while investigating actual evidence. A famous partner and a high click count are insufficient proof of sound distribution.

Route the handoffs and finish the exercise

Send the policy package to the responsible owner for review before any operational distribution. The source's four destinations are Governance/Compliance for compliance rules and partner governance; Automation & Alerts OS for thresholds; Analytics/Dashboards for KPIs and attribution notes; and Scale Playbooks for scalable formats such as webinars, bundles and swap scripts. Preparing these handoffs does not execute them.

Use a calm, strategic, protective, buyer-respectful and long-term tone, without ego, hype or vague motivation. The source's close is “OP-37 complete. Output contract delivered.” Use it only after the five-output record is complete, with unresolved operational prerequisites visible.

As an authored Brunson/ClickFunnels connection, a partner audience needs a relevant path into a consistent offer and onboarding experience. As an authored Hormozi/Acquisition.com connection, partner acquisition must fit the actual customer value, delivery capacity and measured economics. Neither connection supplies a missing partner list or justifies unsupported promises.

For practice, prepare a proposed partner evaluation using the six input groups, all five outputs, diagnostic checks and freeze policy. Explain the value to both parties and identify evidence still needed. Do not claim the Dream 25 list is complete until actual candidates have been researched and reviewed.

Resources

The native original is preserved for the complete appendix. Actual offer, proof, claims policy, promotional assets, economics, partner permissions and owner records are not supplied here and remain required supporting evidence.

Assigned source: D0482 original

D0482 — complete original source

D0482 — OP-37 — Dream 25 Strategist

Open original document · Download preserved native document structure

Complete native text, embedded links, heading hierarchy, list items and bold/italic emphasis. Unspecified native bullet glyphs use a standard bullet here; exact formatting metadata is retained in the downloadable structure. Full visual layout comparison remains pending.


OP-37 — Dream 25 Strategist
RISER Nation | Custom GPT System Message (Production-Ready)
ROLE
You are OP-37 — Dream 25 Strategist. Selects, ranks, and targets top strategic partners with a plan for value-first access, assets, and co-created wins. You operate as a disciplined systems operator (not a hype, vanity, or networking operator).
OPERATING CONTEXT
• Runs only after Offer Lock + Economics Truth + First Win stability.• Protects brand trust while scaling distribution.• Feeds Governance/Compliance, Automation/Alerts, and Scale Playbooks.• Assumes: claims policy exists, approved assets exist, and enforcement owner exists.
PRIMARY OBJECTIVES
• Build repeatable distribution leverage (partners, affiliates, collaborations).• Prevent brand drift and claims violations.• Enforce timing rules so distribution scales *after* onboarding and delivery stability.• Create measurable partner economics (not vibes-based relationships).
REQUIRED INPUTS (CONFIRM BEFORE EXECUTION)
• Offer frame + audience level + proof stack.• Claims policy + forbidden claims list.• Affiliate/JV governance owner (human) + enforcement authority.• Current funnel + onboarding assets + DFY promo kit status.• Unit economics (AOV, LTV, CAC guardrails) and refund thresholds.• Partner categories allowed (industry, adjacent, out-of-niche).
CORE OUTPUTS (MANDATORY)
You must produce ALL outputs below:1) System Map (how this operator plugs into RISER).2) Rules of Engagement (allowed vs forbidden behaviors).3) Templates (scripts, outreach, onboarding, asset checklist).4) KPI + Alert triggers (what breaks, what it means, what to do).5) Handoff package to Governance + Automation + Scale Playbooks.
STRATEGIC LOGIC (WHY THIS EXISTS)
Distribution is an amplifier. If you amplify a fragile offer, you accelerate refunds, support overload, and reputation damage.This operator ensures distribution only scales when:• The offer is locked.• Economics are true.• Onboarding produces first wins.• Culture and enforcement exist.Leverage without governance becomes liability.
QUALITY RULES (NON-NEGOTIABLE)
• No hype. No urgency manipulation. No false scarcity.• No claims outside approved assets.• Protect the brand over short-term revenue.• Prefer long-term partners over “one-hit” promos.• Escalate and freeze when quality or economics degrade.
FAILURE MODES & DIAGNOSTICS (WHAT IT MEANS WHEN IT BREAKS)
• Partner leads high, conversions low → mismatch of audience belief state or offer framing.• Refunds spike by source → affiliate/JV misrepresentation or onboarding mismatch.• Support load surges after promos → offer not stabilized, or wrong expectations set.• Brand complaints rise → governance/enforcement failure (not a marketing problem).• Partner churn high → unclear value exchange or missing partner enablement assets.
ESCALATION & FREEZE RULES
Trigger a FREEZE when ANY of the following occurs:• Claims violations detected.• Refund rate exceeds the threshold defined by Economics Truth.• Support overload triggers.• Reputation risk signals (complaints, chargebacks, negative sentiment).Freeze actions:• Pause partner traffic.• Audit assets used.• Require corrective messaging.• Remove partner if repeated.
REAL-WORLD EXAMPLES (WORKS vs FAILS)
WORKS:• Partner uses the approved promo kit verbatim → expectations match → refunds stay low.• JV runs after onboarding is proven → support remains stable → LTV improves.FAILS:• Affiliate improvises claims → higher clicks → higher refunds → reputation damage.• “Big partner” promo before first win is stable → chaotic support → churn rises.
HANDOFF REQUIREMENTS
• Send compliance rules + partner governance to Governance/Compliance layer.• Send alert thresholds to Automation & Alerts OS.• Send performance KPIs and attribution notes to Analytics/Dashboards.• Send scalable formats (webinar, bundle, swap scripts) to Scale Playbooks.
TONE
Calm. Strategic. Protective. Buyer-respectful. Long-term. No ego. No hype. No vague motivational language.
CLOSE
OP-37 complete. Output contract delivered.

Define a course and module around observable completion evidence

Purpose and scope

This source, titled PERPLEXITY, describes a reusable course-template SOP. It is not a tutorial proving particular Perplexity product capabilities. Its purpose is a consistent structure so an operator can see what a course contains, which tools it requires and what must be true before progression.

You will define course-level assets, fill six module fields, and connect those fields to instruction, resources and completion evidence. The source proposes doing this before writing lesson bodies. Apply the method to the approved curriculum rather than treating its examples as authority to replace the existing twelve-course spreadsheet assignments or remove assigned documents.

The source uses legacy examples such as C 15 AI Shipyards and vessel stages. These labels belong to its template examples. Keep the actual course code and mapping separate wherever they differ.

Build the six-field course one-pager

Record the course title and code, stage or vessel, revenue-milestone relationship, measurable course outcome in one or two sentences, and target operator profile. The profile explains where the learner is in the journey and what they already have. Example vessel labels include Dinghy, Sailboat, Speedboat and Yacht; use only the applicable established stage.

A revenue-milestone link explains the intended contribution of the course. It does not guarantee revenue or establish a milestone already achieved. Name the actual artifact or capability that supports the outcome.

Prepare all five course assets

Overview-video script. The source targets three to seven minutes. Explain why the course matters, its prerequisites and the expected completion state. That is a script-length target, not an existing video or a measured learning-time guarantee.

Navigation map. Show modules in sequence using a diagram or bullet map. Mark checkpoints and blocked-until conditions. Preserve the actual approved sequence rather than invent dependencies from a course title.

Workbook or implementation document. Use a central Google Doc or PDF containing the exercises, checklists and prompts referenced by the modules. Provide access to the actual materials; an index title alone does not supply them.

Resource index. Link all applicable tools, pages and builds, including an Ignition-stage asset, RISER page, Netlify tool, Supabase table or automation where relevant. Name the specific dependency and whether it is available. The source does not supply working links for these examples.

Completion definition. The source proposes three to five observable criteria. Examples include an Offer Stack for one niche and a RISER Start email-capture threshold of at least 40% over 100 visits. These are template examples, not adopted business targets or measured results. A later example uses 200 visits; keep the different observation bases explicit. Actual metric criteria need a defined numerator, denominator, period and evidence source.

Module field 1: use an activity title

Create a clear label using a verb, object and context. The source's example is “Design the RISER Start Questionnaire for Your Niche,” contrasted with a vague theory title. Deliver the final title and, if useful, an internal slug such as M 2.1-riser-questionnaire. The slug must not silently change the spreadsheet's lesson identifier.

Module field 2: define an observable outcome

State one concrete result that can be reviewed as done or not done. The source targets 45–90 minutes of focused learner work. Treat this as a design estimate to validate, not a promise that every assigned document or technical setup fits within it.

Use the source's pattern: identify the artifact created, system setting configured or metric captured or validated. The examples are a live questionnaire on a Netlify page routing visitors through four paths and posting to Supabase, or a complete offer architecture stored in Supabase containing core offer, upsells, downsells, guarantees and competitor positioning.

Those examples describe observable system states. They do not establish an installed page, database, working integration or approved guarantee. Specify the real result and its verification location before using it as a completion criterion.

Module field 3: identify one primary deliverable

Choose exactly one headline deliverable while retaining any required secondary artifacts. This is the object a reviewer examines as evidence of the outcome. A multi-part source can still require every component; calling one the primary deliverable is not permission to omit the others.

The source allows four deliverable types. A document might be a completed Offer Stack PDF in a named Drive folder. A configured tool might be Ignition Engine v 5 deployed and tested with one full run. An automation might be an active Forge_Reminders n8n workflow tested with a dummy contact. A metric snapshot might show at least 40% capture over 200 visits. These are examples, not a request to deploy, activate messages or fabricate evidence.

Record the deliverable's name, exact location and owner. Locations may be a Drive path, Supabase table or RISER page URL. Distinguish work owned by the learner from work requiring a technical implementer. Use links to actual artifacts when available; otherwise mark the location unresolved.

Module field 4: list real dependencies

Include assets necessary for the module to function, rather than optional tools that merely sound useful. Review three categories:

  • RISER pages: RISER Start, Ignition Engine v 5, Trigger Bank, First Dollar Forge, Offer Stack and Tool Index.
  • Platform infrastructure: Supabase tables, semantic metrics, n8n workflows, Stripe, Drive MCP, CAPI, quality-assurance tooling and agents.
  • External platforms: GoHighLevel, Synthesia, ad platforms, email and the community platform.

The source's dependency template lists the tool or page, build or infrastructure and external integration. Its worked example requires RISER Start live on Netlify, user and questionnaire tables in Supabase, a configured GHL account/API key and an available n8n questionnaire-webhook endpoint. This lesson teaches how to identify those requirements; it does not expose credentials, install software or establish that these systems exist.

For each actual dependency, record the owner, accessible reference and evidence of readiness. An account or code file alone does not demonstrate that the required end-to-end behavior works.

Module field 5: define the checkpoint

Write one clear validation step a reviewer can perform in the source's estimated five to ten minutes. Prefer checking actual behavior when the module creates a system artifact. A quiz about a form does not demonstrate that the form sends its data correctly.

The source provides four checkpoint types. A functional test submits a test form and verifies records in Supabase and GHL. A black-box test runs one Ignition sequence for a test niche and checks that all eleven stages produce outputs without errors. A behavior test opens Tool Index as three operator types and checks the expected category-order change. An output-quality test reviews three generated offer stacks for specificity, niche alignment and lack of generic content.

Use its action–observation–evidence structure: perform the specified action, observe the expected result at the named location, and capture a screenshot, link or log. The example counts are not universal test requirements. Define the appropriate check for the actual artifact and preserve required source-specific acceptance criteria.

This checkpoint can inform LMS gating once implemented. Describing it is not the same as wiring or passing it, and a screenshot must represent an actual observation rather than a simulated success.

Module field 6: state the blocked-until prerequisite

Name what must already be true and where it can be verified. Express the condition as done or not done. Distinguish hard technical or logical dependencies from recommended background skills that do not enforce a system block.

The source examples are RISER Start deployed with at least fifty unique visitors even if conversion is low; completion of Stage 2 Offer Fleet Expansion with the Proof Threshold passed; and installed Supabase base schema plus semantic-metrics YAML labeled Builds 1 and 1.5. The document supplies no proof that those conditions are satisfied or definitions for every named threshold.

Its strict availability rule applies to its proposed hard prerequisites. Do not infer that all recommended skills are enforced gates, or change the live LMS simply because a source describes a block. Record the applicable approved condition and verify it before asserting readiness.

Derive content, scripts and resources from the structure

The lesson outline should follow the outcome and primary deliverable. Turn each major creation step into a segment or lesson as appropriate to the approved mapping, and explicitly explain how required tools support the work. Retain all distinct assigned material even when the reusable template is shorter than the source.

For video and audio scripts, the introduction restates the title, plain-language outcome, deliverable and checkpoint. The body follows the dependency order. The ending points to the test and tells the learner which evidence to capture. Written scripts do not establish that videos or audio have been produced; media still needs its own production and usability review.

Derive four resource types: checklists from creation steps; prompt packs where an AI tool is used; configuration templates such as workflow JSON or settings CSV; and quality rubrics from checkpoint criteria. Tie each resource to a specific task and test. An embedded prompt remains source material until its actual use is separately appropriate and authorized.

Follow the six-step implementation sequence

First define the course metadata. Second list activity-based modules; the source suggests five to twelve titles. Third fill all six fields for every module. Fourth check dependency consistency so a module does not require a build introduced later. Fifth draft the lesson content and scripts from the outcomes and deliverables. Sixth connect checkpoints to the LMS or tracking system with verifiable links, screenshots, logs or metrics.

The suggested module range is a template guideline, not authority to resize this curriculum. A discovered dependency conflict needs an explicit mapping decision rather than an invented prerequisite or silently moved lesson. The source closes by offering a worked six-to-eight-module example for First Dollar Forge or Offer Stack; it does not actually contain that completed example.

Apply the marketing themes and practice

As an authored Brunson/ClickFunnels connection, make the course promise and the next action match the actual learning path. As an authored Hormozi/Acquisition.com connection, use a clear outcome, visible proof of completion and realistic effort to explain the training's value. Neither framework turns a template metric into a guaranteed result.

Choose one existing assigned lesson. Produce its course context, five course-asset references and six module fields. Trace each lesson section and resource to the outcome without deleting assigned content. Identify missing dependencies and show the evidence a reviewer would need to confirm completion.

Source and resources

The actual named pages, builds, configurations, workbooks and completed learner evidence are not supplied by this document. Their exact applicable links and readiness remain to be established; example names are not proof of working resources.

Assigned source: D0483 original

D0483 — complete original source

D0483 — PERPLEXITY

Open original document · Download preserved native document structure

Complete native text, embedded links, heading hierarchy, list items and bold/italic emphasis. Unspecified native bullet glyphs use a standard bullet here; exact formatting metadata is retained in the downloadable structure. Full visual layout comparison remains pending.

PERPLEXITY.AI
Here’s a reusable master course‑template SOP you can apply to every RISER course and module. This defines exactly what must be delivered before you ever write lesson bodies.

1. Purpose of the Master Template
Every course in RISER Nation should ship with the same shell, so any operator or team member can open a course and instantly know what’s there, what tools it touches, and what must be true before moving on.
This SOP defines:
• What is required for each course
• What is required for each module inside that course
• How to use the standard fields you listed as the spine for everything

2. Course-Level Requirements
For each course (e.g., “C15 AI Shipyards”), you always deliver the same course‑level assets before drilling into module content.
2.1 Course metadata
For every course, create a one‑pager with:
• Course Title
• Course Code (e.g., C15)
• Stage/Vessel (Dinghy, Sailboat, Speedboat, Yacht, etc.)
• Revenue Milestone Link (how this course contributes)
• Course Outcome (1–2 sentences, measurable)
• Target Operator Profile (where they are in the journey and what they already have)
2.2 Course asset checklist
Every course must include:
• Course overview video script
• 3–7 minutes.
• Explains why the course matters, prerequisites, and what will be true when finished.
• Course navigation map
• Simple diagram or bullet map of modules in sequence.
• Shows where checkpoints live and where “blocked‑until” logic applies.
• Course workbook / Implementation doc
• Central Google Doc or PDF with all exercises, checklists, and prompts referenced by modules.
• Course resource index
• List of all linked tools/pages/builds used in the course (Ignition stage, RISER page, Netlify tool, Supabase table, automation, etc.).
• Course completion definition
• 3–5 criteria that must be true to mark course as “complete” (e.g., “Offer Stack shipped for one niche,” “RISER Start email capture ≥ 40% for 100 visits”).
Once those are defined, every module inside this course must use the same module template below.

3. Standard Module Shell (Applies to Every Module)
For each module, you fill out these fields before writing lesson scripts or recording anything.
3.1 Module Title
Definition: Clear, operator‑facing label that describes the activity or capability, not just the topic.
• Format: verb + object + context
• Example: “Design the RISER Start Questionnaire for Your Niche”
• Avoid vague titles like “Questionnaire Theory.”
Deliverables for this field
• Final module title.
• Optional internal title/slug (e.g., M2.1-riser-questionnaire).

3.2 Module Outcome
Definition: One concrete, testable result an operator will have after completing this module.
• Must be observable and binary: done / not done.
• Should be achievable within 45–90 minutes of focused work.
Template
• “By the end of this module, the operator will have:
• [specific artifact] created
• [specific system setting] configured
• [specific metric] captured or validated”
Examples
• “By the end of this module, the operator will have a live RISER Start questionnaire deployed on their Netlify page that routes visitors into four paths and posts data into Supabase.”
• “By the end of this module, the operator will have a complete offer architecture saved in Supabase (core offer, upsells, downsells, guarantees, competitor positioning).”

3.3 Key Deliverable
Definition: The concrete artifact or system change that proves the module outcome.
• Always exactly 1 primary deliverable (you can have secondary ones, but keep one “headline” deliverable).
• This is what you would check in a review or audit.
Acceptable deliverable types
• Document (e.g., “completed Offer Stack PDF in Drive folder X”).
• Configured tool (e.g., “Ignition Engine v5 deployed and tested with one full run”).
• Automation or workflow (e.g., “n8n workflow ‘Forge_Reminders’ active and tested with a dummy contact”).
• Metric proof snapshot (e.g., “screenshot of RISER Start conversion dashboard showing ≥ 40% capture over 200 visits”).
Deliverables for this field
• Name of deliverable.
• Where it lives (Drive path / Supabase table / RISER page URL).
• Owner (who is responsible for creating it: operator vs technical implementer).

3.4 Required Tool / Page / Build Dependency
Definition: The specific RISER assets and external tools that must be present for the module to run as designed.
This field does not list “nice to have” tools; it lists non‑negotiable dependencies.
Categories to consider
• RISER Pages:
• RISER Start, Ignition Engine v5, Trigger Bank, First Dollar Forge, Offer Stack, Tool Index.
• Platform Builds & Infrastructure:
• Supabase tables, semantic metrics layer, n8n workflows, Stripe, Drive MCP, CAPI, QA harness, agents, etc.
• External Platforms:
• GHL, Synthesia, ad platforms, email, community platform.
Template
• “This module depends on:
• [Tool/Page]
• [Build/Infrastructure]
• [External integration]”
Examples
• “Depends on:
• RISER Start live on Netlify
• Supabase user and questionnaire tables created
• GHL account with API key configured
• n8n endpoint for questionnaire webhook available”
This avoids modules that assume a build exists that an operator hasn’t installed yet.

3.5 Checkpoint / Test
Definition: A single, unambiguous validation step that confirms the module is complete and working as intended.
• It must be something a reviewer or the operator can perform in 5–10 minutes.
• Prefer live tests over theoretical quizzes whenever the module produces something in the system.
Types of checkpoints
• Functional test: “Submit a test form and verify data appears in Supabase and GHL.”
• Black‑box test: “Run one Ignition Engine sequence using a test niche and verify all 11 stages produce outputs with no errors.”
• Behavior test: “Open Tool Index as three different operator types and confirm category order changes as expected.”
• Output quality test: “Review three generated offer stacks and verify each core offer is specific, niche‑aligned, and not generic.”
Template
• “To pass this module, the operator must:
• Perform [test action]
• Observe [expected outcome] in [location]
• Capture [evidence] (screenshot/link/log)”
This checkpoint is what you wire into any LMS gating or “blocked‑until” logic.

3.6 Blocked‑Until Prerequisite
Definition: What must already be true before this module is started. This is the anti‑overwhelm, anti‑skip gate.
• You treat prerequisites as contracts.
• If the prerequisite is not satisfied, the module is not available.
Examples of prerequisite statements
• “Blocked until: RISER Start is deployed and receives at least 50 unique visitors (even if conversion is low).”
• “Blocked until: Operator has completed Stage 2 Offer Fleet Expansion and passed the Proof Threshold.”
• “Blocked until: Supabase base schema and semantic metrics YAML are installed (Builds 1 and 1.5).”
Template
• “Blocked‑until prerequisite:
• [Clear condition expressed in done/not done language]
• [Where it can be verified]”
You can also distinguish:
• Hard prerequisites: technical or logical dependencies.
• Soft prerequisites: recommended skills or background but not enforced by system.

4. How All Module Fields Connect to Content, Scripts, and Resources
Once the shell above is filled for a module, you then derive:
4.1 Lesson content
• Lesson outline flows from Module Outcome and Key Deliverable.
• Each major step in creating the deliverable becomes a lesson segment or individual lesson.
• You explicitly show operators how to use the Required Tool/Page/Build to achieve the outcome.
4.2 Video / audio scripts
• The intro script restates:
• Module Title
• Module Outcome (in plain language)
• The Key Deliverable and Checkpoint
• The body walks through tools in the order implied by the dependencies.
• The outro script links to the Checkpoint/Test and tells the operator what evidence to capture.
4.3 Resources
From the shell, you generate:
• Checklists: from the steps needed to create the Key Deliverable.
• Prompt packs: for any part where Claude/AI is used.
• Config templates: JSON for workflows, CSV for settings, etc.
• QA rubrics: from the Checkpoint/Test criteria.
Because you’re always using the same module fields, every resource is tied back to something specific and testable.

5. Implementation SOP: How to Use This Template for Any New Course
When you create a new course:
• Define course metadata
• Fill the course one‑pager (title, outcome, vessel, milestone link, target operator).
• List modules
• Draft 5–12 module titles that represent concrete activities, not topics.
• Fill the module shell for each module
• For every module: title → outcome → key deliverable → dependencies → checkpoint → blocked‑until.
• Review for dependency consistency
• Scan all modules to ensure no module depends on a build introduced later in the journey.
• Only then draft lesson content and scripts
• Use the module outcome and key deliverable to outline lessons.
• Wire checkpoints into the LMS or tracking system
• Ensure each checkpoint is actually verifiable (link, screenshot, log, or metric).

If you’d like, I can now take one concrete RISER course (for example, “First Dollar Forge” or “Offer Stack”) and fill this shell for 6–8 of its modules so you can see a fully worked example end‑to‑end.