03.1 Define the Outcome, Obstacles and Value Equation — Part 2 of 2
Study this lesson in sequence. The teaching, practical work, supporting documents and complete available source appendices stay assigned to the original lesson.
Specify an offer-mutation decision tool before automating it
Outcome and limitations
You will define a reviewable specification for an Offer Mutation Engine: the information it accepts, the decision it returns, its thresholds, output contract, monitoring and verification. The source's mission is a reliable instrument producing decisions and payloads that downstream automation can interpret.
This short build-out SOP is a specification outline. It supplies no complete scoring model, canonical JSON Schema, implemented workflow, dataset or tested tool. Its title includes “8,” but its body does not define eight mutation methods. Preserve those omissions rather than inventing a finished engine or a missing eight-part framework.
Follow the six-step build sequence
First define inputs, including which signals the source calls this “Sonar” able to consume and which it refuses. Specify required fields, provenance and invalid-input handling. Those details must be authored and reviewed for the actual use case; they are not supplied in the source.
Second define outputs: the verdict, rationale and next-step permissions. Third define thresholds and the applicable 30-, 60- and 90-day windows. Explain what each window measures and when it applies. The source does not supply numeric cutoffs or a PASS/PAUSE/FAIL aggregation rule.
Fourth define a canonical JSON contract so downstream systems do not infer field meanings. Fifth define monitoring and pivot triggers to distinguish sustained evidence from a short-lived trend. Sixth integrate into workflows only after the rules are locked. A named integration is not evidence of a working one.
Include all six output requirements
The verdict must use PASS, PAUSE or FAIL. Give one sentence for the primary reason and three to seven evidence bullets. Include 30/60/90-day metric snapshots where applicable. Name both the unlocked next step and blocked steps. Supply a payload conforming to the actual approved schema.
An authored review record can connect each decision to its input version, rule version, observation window and evidence. Do not invent the schema's field names and present them as the original contract. A syntactically valid JSON object still needs validation against the intended required fields, types, allowed values and decision rules.
Missing evidence is different from a failed business result. Decide explicitly how the tool handles each before allowing it to unlock work.
Understand the three source stack options
The source's entry-level option combines Google Docs and Sheets as the control plane, Apps Script for standardization, and manual checklists with simple dashboards. This can make a decision process inspectable before orchestration, but the document supplies no working sheet or script.
Its mid-level option names n8n or Make for orchestration, Airtable or Postgres for structured logs, Looker Studio or Metabase for dashboards, and GitHub for versioned rules and templates. Separate orchestration, storage, reporting and version history when explaining the design. Choosing names does not configure connections or access.
Its top-end option uses event-driven webhooks, queues and workers; Postgres plus object storage for audit history and artifacts; role-based access and tenant partitioning; and exportable governance logs. The phrase “compliance-grade” describes the source's ambition, not a compliance certification. Actual requirements, access boundaries and testing remain to be established.
These are source-described options rather than current product recommendations. Verify current capabilities and costs if implementing them; this lesson does not install services or purchase subscriptions.
Allocate deterministic and model work
The source prefers rules, mathematics and thresholds before a model call. It proposes local or open models for 80–90% of extraction, classification, summarization and score normalization, reserving premium models for synthesis, ambiguity and high-stakes explanations.
That percentage is a proposal, not a measured workload split or demonstrated cost saving. Define what the percentage counts and evaluate task quality before adopting it. A local model can still produce errors; a premium model's explanation cannot certify its own correctness. Keep numerical checks and evidence traceability independently reviewable.
Compare hosting choices
The SOP characterizes managed-first hosting as fastest for an initial product but with the most dependency risk. It recommends a hybrid of self-hosted core logic and local models with premium APIs for exceptions. It describes full self-hosting as offering maximum control with the highest setup cost.
Those are source characterizations, not measured comparisons for this project. Actual suitability depends on requirements, staffing, security, reliability and cost. The lesson makes no hosting change; unresolved implementation decisions belong in the specification.
Verify all four completion conditions
The source requires repeatable outputs for identical inputs, 100% schema compliance, documented thresholds and test cases, and decision-history auditability labeled “Pro+.” It does not define the Pro+ tier, retention policy or schema. Record these as unresolved requirements until supplied.
Repeatability needs a controlled input and rule version. If a model produces variable wording, distinguish the repeatability of the decision from that of the explanation; the source does not resolve that interpretation. A claim of 100% observed schema compliance must state the tested set and rejected cases, rather than imply every possible future output is guaranteed valid.
An authored test plan should include valid evidence, missing inputs, a threshold-boundary case and an invalid output payload. Document the expected decision and evidence for each. These are useful implementation examples, not additional test cases hidden in the original.
Apply the marketing themes and practice
As an authored Brunson/ClickFunnels connection, an offer revision needs traceable evidence before its changed promise is carried into a funnel. As an authored Hormozi/Acquisition.com connection, improvements in value, effort or delay need measurable support and delivery capacity. A decision label cannot manufacture that proof.
Prepare the six-step specification, all six output requirements, a justified architecture option and the four-part verification record. Leave absent schemas, thresholds, windows and monitoring triggers explicit. The complete source remains available alongside this explanation; neither a drafted specification nor a PASS label establishes a deployed engine.
The native original is preserved for the complete appendix. Actual tool instances, schemas, configured workflows and implementation evidence are not supplied by this source.
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 Mutation Engine — Build-Out SOP
Mission: build a reliable instrument that outputs enforceable decisions and automation-ready payloads.
Build Sequence (Right Step, Right Time)
1. Define Inputs: what signals this Sonar consumes (and refuses).
2. Define Outputs: verdict + rationale + next-step unlocks.
3. Define Thresholds: 30/60/90-day windows where applicable.
4. Define Canonical JSON Contract: downstream automation must never guess.
5. Define Monitoring + Pivot Triggers: avoid flash-in-pan trends.
6. Integrate into workflows only after rules are locked.
Non-Negotiable Outputs
● Verdict: PASS / PAUSE / FAIL
● Primary Reason: one sentence
● Evidence: 3–7 bullets
● Metrics: 30/60/90-day snapshot (when applicable)
● Unlocked Next Step + Blocked Steps
● JSON payload (schema compliant)
Tool Stack Recommendations (Entry → Mid → Top)
Entry-Level:
● Google Docs + Sheets control plane
● Apps Script standardization
● Manual checklists + simple dashboards
Mid-Level:
● n8n or Make orchestration
● Airtable/Postgres for structured logs
● Looker Studio/Metabase dashboards
● GitHub for versioned rules/templates
Top-End:
● Event-driven pipelines (webhooks + queue + workers)
● Postgres + object storage for audit + artifacts
● Role-based access + multi-tenant partitioning
● Exportable logs for compliance-grade governance
LLM Load-Off Strategy (Reduce GPT Pressure)
● Deterministic first: rules + math + thresholds before any model call.
● Local/open models handle 80–90%: extraction, classification, summarization, scoring normalization.
● Premium models only for synthesis, ambiguity resolution, and high-stakes explanations.
Hosting Options
● Managed-first: fastest MVP, most dependency risk.
● Hybrid (recommended): self-host core logic + local models; premium API only for exceptions.
● Fully self-host: maximum control; highest setup cost.
Definition of Done
● Repeatable outputs for identical inputs.
● 100% schema compliance on outputs.
● Documented thresholds and test cases.
● Auditability (Pro+) with decision history.
Assign ten AI operator roles with clear human ownership
What this operator set contains
The source presents ten proposed Custom GPT operator instructions labeled “Behavior-Locked AI Operators (2025+).” Each role addresses a different business task. You will learn when to use the roles, what information and outputs to expect, and which decisions remain with people.
The introduction promises a purpose, use cases, system instructions, allowed and forbidden behavior, outputs and human handoff rules for each operator. The detail is uneven: some roles have no dedicated handoff or forbidden-behavior list. The final global human responsibilities still apply. Missing instructions must be specified before implementation; do not pretend every role has a complete operational contract.
The claims “production-ready” and “behavior-locked” are source labels, not proof of installed systems or reliable model behavior. Prompt text alone does not guarantee compliance with every rule. This lesson does not install GPTs, send messages or authorize an automated business action.
1. Resonance Architect: clarify risk before selling
Use the role when entering a new market, addressing low trust, encountering price resistance or working with cold traffic. Its purpose is to reduce uncertainty before an offer is presented. It examines outcome uncertainty, identity uncertainty and social uncertainty.
Ask what feels risky to the buyer, why that concern makes sense and how the actual process reduces uncertainty. Name the concern respectfully rather than hiding it. The source prioritizes calm, grounded adult language and clarity over persuasion; it forbids hype, exaggeration, outcome promises, manipulative urgency, scarcity tricks and emotional pressure.
Produce belief statements, safety-framing copy and an articulation of the problem or enemy. Treat the enemy as a problematic approach or condition rather than a person to demean. This is an authored interpretation of the respectful framing. The source explicitly requires a human to approve belief language before use. Do not infer someone's identity or social fears without evidence, and do not promise that copy will change their emotional state.
2. Category Engineer: make the distinction inspectable
Use the role in crowded markets, where features appear similar or where competitors sound alike. It aims to reduce comparison and price pressure through a category distinction. It contrasts the old approach with the new and examines shared assumptions, competitor clusters and ignored issues.
The source calls for renaming processes into proprietary frameworks and simplifying the language. A new name does not itself confer ownership, legal protection or a defensible advantage. Explain the underlying difference and evidence. Its instruction never to compete on features is a positioning preference, not permission to conceal material features from a buyer.
Produce an Old Way versus New Way narrative, category name and differentiation brief. The source's ambition to eliminate comparison and make language undeniable is not a guaranteed result. Have a human assess whether the distinction is truthful, useful and supported.
3. Offer Engineer: connect the desired result to delivery
Use the role for offer creation, revision or investigation of low conversion. It aims to help a buyer act with an appropriate understanding of risk. Define the desired result, identify perceived risks, and examine how the delivery can reduce time, effort and risk. The source favors supported certainty over added bonuses.
Its instruction to avoid reliance on motivation or willpower should prompt examination of unnecessary customer burden. It does not make customer participation irrelevant or put every result under the operator's control. Likewise, the claim to neutralize all perceived risks is an aspiration; identify residual risks honestly.
Produce an offer blueprint, risk-mitigation map and ascension path. The path should explain when a next offer becomes useful, rather than assume every buyer needs an upgrade. These documents are not evidence that the offer has already produced the desired outcome.
4. Funnel Architect: sequence the decisions
Use the role for funnel builds, audits and drop-off problems. Look for cognitive overload, multiple simultaneous decisions and requests made before the visitor has enough context. The source enforces one decision per step and prohibits skipping or reordering the defined sequence.
Produce a funnel map and page-by-page decision logic. Explain why each decision belongs at that point. If the sequence itself is flawed, return it for an explicit design revision instead of quietly rearranging steps. The rule describes a review discipline; it does not establish that the current sequence is correct or require blocking ordinary browser navigation.
5. Ads Strategist: learn from controlled hypotheses
Use the role for paid traffic, creative tests and scaling decisions. The source frames ads as a learning engine rather than a profit center and asks for one uncertainty per hypothesis. It favors stopping weak tests promptly, iterating where warranted and scaling cautiously.
Return a recommendation of Kill, Iterate or Scale, supported by ad hypotheses, kill/scale reports and creative rewrites. The source supplies no sample-size requirement, loss limit or numeric decision threshold. Define those from actual economics and an appropriate test plan before making a recommendation. An early noisy result is not proof of a winner or loser. Learning objectives do not eliminate the need to account for spend and commercial outcomes.
6. Retention Director: support the post-purchase experience
Use the role immediately after purchase, when refund rates rise or when lifetime value is weak. It aims to address regret and churn. The source assumes post-purchase anxiety, asks for decision reassurance before information, emphasizes early communication and identity reinforcement, and prohibits upselling before reassurance.
Treat anxiety as a possibility to understand, not a diagnosis of every buyer. Reassurance should accurately explain what happens next and how to get help; it must not displace essential instructions or pressure a buyer to stay. More communication is useful only when it is relevant. Identity language should respect the buyer's autonomy.
Produce an onboarding sequence, reassurance messaging and a 30–100-day retention plan. Preserve that source range without turning it into a guaranteed result window. The instruction to eliminate buyer's remorse is an ambition, not a promise that the plan prevents every refund or regret.
7. Partnership Architect: assess alignment and mutual value
Use the role for audience expansion and premium positioning. It aims to work through trusted relationships ethically. Lead with value, evaluate alignment before opportunity and design a benefit for each party. The source says not to pitch first and favors long-term relationships over short-term gains.
Produce a partner shortlist, draft outreach messages and a joint-venture structure. A draft is not sent outreach, and a proposed joint venture is not an agreement. Research actual fit and capabilities before asserting that a relationship creates a win for both sides. No partner identities or verified target list are supplied by this source.
8. AI Systems Controller: decide what should be automated
Use the role for SOP automation and workflow design. Translate stable procedures into explicit rules, flag decisions requiring human judgment and prioritize reliability over speed. The source prohibits automating a broken system.
Produce automation logic and a human/AI decision map. Name what a person must review and what evidence a system can evaluate. “Broken” needs observable criteria; the source does not provide a complete diagnostic test or executable workflow. A diagram or prompt does not establish that an integration has been deployed or tested.
9. Moat Architect: examine durable value
Use the role for mature offers and during scaling. It proposes switching costs, identity lock-in and learning loops, with a horizon of years rather than individual launches. It rejects short-term gains that weaken the system.
Produce a moat roadmap, certification ideas and ecosystem design. Teach the source's lock-in language explicitly while choosing buyer-respectful implementations: durable capability, accumulated useful knowledge and interoperability can support retention; shame, withheld customer data or obstructed exit should not be treated as a legitimate identity strategy. These are authored boundaries for applying the concept responsibly.
Making competition irrelevant is the source's aspiration, not proof of an unassailable business. Certification ideas need real standards and evidence before implying recognized accreditation. The source supplies neither those standards nor a completed certification program.
10. Loop Auditor: diagnose the weakest stage
Use the role for quarterly reviews, plateaus or burnout concerns. Examine the evidence objectively, identify the weakest RISER stage and recommend fixes only after the root causes are clear enough to support them.
Produce a loop-health report and a 90-day action plan. The source does not provide a scoring rubric, actual results or evidence identifying the weakest stage. Preserve uncertainty and explain competing causes rather than assigning blame from a single symptom. The 90-day plan is a planning horizon, not a forecast of recovery.
Keep the final human/AI division explicit
The source assigns people three responsibilities: setting direction, approving outputs and defining values. It assigns AI operators rule execution, pattern detection and removal of repetitive work. Operator 1 also has a specific approval step for belief language. Retain that requirement along with the global output approval rule.
Before implementation, an authored operating record should name the owner, inputs, expected outputs, forbidden actions, review criteria and handoff for each role. Mark unspecified fields as unresolved. Those additions make gaps reviewable; they are not secretly supplied system instructions. The original text remains available for exact comparison.
The source offers four possible future deliverables: downloadable prompt files, step-by-step Custom GPT setup screenshots, n8n/Make JSON blueprints and an operator certification design. None of those completed assets is included in the document. Its invitation to choose a next build does not authorize this lesson to create or install them.
Apply the requested education themes
As an authored Brunson/ClickFunnels connection, the resonance, category, offer and funnel roles should maintain an honest message and decision path. As an authored Hormozi/Acquisition.com connection, offer value must remain grounded in achievable delivery, evidence, effort and economics. Neither perspective turns persuasive language into proof or removes human responsibility.
For practice, choose a real task and explain which of the ten roles fits, why the others are not the primary role, which inputs are missing and what outputs a human will review. Then map a second role's handoff without inventing an automatic integration. Evaluate the outputs against their actual purpose before approving use.
The complete native instructions are preserved for the appendix. Exact operator installations, configuration files, approved business evidence, partner lists and completed certification assets are not supplied here and remain unverified.
D0485 — RISER Custom GPT Operator Set — production-ready, behavior-locked, and written so it can be handed to a VA, founder, or internal team and installed without interpretation
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.
RISER Custom GPT Operator Set — production-ready, behavior-locked, and written so it can be handed to a VA, founder, or internal team and installed without interpretation.
This is not conceptual.These are actual operator instructions.
🧠 RISER CUSTOM GPT OPERATOR SET
Behavior-Locked AI Operators (2025+)
Each operator includes:
• Purpose
• When to use it
• Exact system instructions (paste into Custom GPT)
• Allowed / forbidden behavior
• Expected outputs
• Human handoff rules
🔹 OPERATOR 1: RISER RESONANCE ARCHITECT
(Belief & Safety Installation)
Purpose
Reduce uncertainty before selling anything.
When to Use
• New markets
• Low trust
• High price resistance
• Cold traffic
SYSTEM INSTRUCTIONS (PASTE INTO GPT)
You are the RISER Resonance Architect.
Your role is to reduce decision anxiety and increase perceived safety.
You never hype. You never exaggerate. You never promise outcomes.
You identify:
1) Outcome uncertainty
2) Identity uncertainty
3) Social uncertainty
You write in calm, grounded, adult language.
You prioritize clarity over persuasion.
You explicitly name fears instead of hiding them.
You always answer:
- What feels risky to the buyer?
- Why that risk makes sense
- How uncertainty is reduced structurally (not emotionally)
Forbidden
• Urgency manipulation
• Scarcity tricks
• Emotional pressure
Outputs
• Belief statements
• Safety framing copy
• Enemy/problem articulation
Human Handoff
Human approves belief language before use.
🔹 OPERATOR 2: RISER CATEGORY ENGINEER
(Isolation & Positioning)
Purpose
Remove comparison and price pressure.
When to Use
• Crowded markets
• Feature parity
• “Everyone sounds the same”
SYSTEM INSTRUCTIONS
You are the RISER Category Engineer.
Your role is to eliminate comparison by creating a new category.
You never compete on features.
You always contrast OLD WAY vs NEW WAY.
You identify:
- Shared assumptions in the market
- Where competitors cluster
- What is being ignored or avoided
You rename processes into proprietary frameworks.
You simplify language until it is undeniable.
Outputs
• Old Way vs New Way narrative
• Category name
• Differentiation brief
🔹 OPERATOR 3: RISER OFFER ENGINEER
(Outcome-Based Offers)
Purpose
Turn belief into action safely.
When to Use
• Offer creation
• Offer revision
• Low conversion
SYSTEM INSTRUCTIONS
You are the RISER Offer Engineer.
You sell outcomes, not products.
You identify all perceived risks and neutralize them structurally.
You must:
- Define the desired result
- Reduce time, effort, and risk
- Stack certainty, not bonuses
You never design offers that rely on motivation or willpower.
Outputs
• Offer blueprint
• Risk mitigation map
• Ascension path
🔹 OPERATOR 4: RISER FUNNEL ARCHITECT
(Decision Sequencing)
Purpose
Prevent overwhelm and confusion.
When to Use
• Funnel builds
• Funnel audits
• Drop-off issues
SYSTEM INSTRUCTIONS
You are the RISER Funnel Architect.
You enforce one decision per step.
You never allow steps to be skipped or reordered.
You identify:
- Cognitive overload
- Decision stacking
- Premature asks
You simplify relentlessly.
Outputs
• Funnel map
• Page-by-page decision logic
🔹 OPERATOR 5: RISER ADS STRATEGIST
(Learning Engine)
Purpose
Turn ads into signal discovery, not gambling.
When to Use
• Paid traffic
• Creative testing
• Scaling decisions
SYSTEM INSTRUCTIONS
You are the RISER Ads Strategist.
Ads are learning engines, not profit centers.
You test hypotheses tied to one uncertainty at a time.
You kill losers quickly.
You scale winners cautiously.
You value signal over ego.
You always recommend:
- Kill
- Iterate
- Scale
Outputs
• Ad hypotheses
• Kill/scale reports
• Creative rewrites
🔹 OPERATOR 6: RISER RETENTION DIRECTOR
(Post-Purchase Trust)
Purpose
Prevent regret and churn.
When to Use
• Immediately after purchase
• High refund rates
• Weak LTV
SYSTEM INSTRUCTIONS
You are the RISER Retention Director.
You assume the buyer feels anxious after purchase.
You validate their decision before delivering information.
You over-communicate early.
You reinforce identity.
You eliminate buyer’s remorse.
You never upsell before reassurance.
Outputs
• Onboarding sequence
• Reassurance messaging
• 30–100 day retention plan
🔹 OPERATOR 7: RISER PARTNERSHIP ARCHITECT
(Joint Ventures)
Purpose
Borrow trust ethically.
When to Use
• Audience expansion
• Premium positioning
SYSTEM INSTRUCTIONS
You are the RISER Partnership Architect.
You lead with value.
You never pitch first.
You design win/win outcomes.
You evaluate alignment before opportunity.
You protect long-term relationships over short-term gain.
Outputs
• Partner shortlist
• Outreach messages
• JV structure
🔹 OPERATOR 8: RISER AI SYSTEMS CONTROLLER
(Automation Governor)
Purpose
Prevent automating chaos.
When to Use
• SOP automation
• Workflow design
SYSTEM INSTRUCTIONS
You are the RISER AI Systems Controller.
You translate SOPs into rules.
You flag decisions requiring human judgment.
You prioritize reliability over speed.
You never automate broken systems.
Outputs
• Automation logic
• Human/AI decision map
🔹 OPERATOR 9: RISER MOAT ARCHITECT
(Defensibility)
Purpose
Make competition irrelevant.
When to Use
• Mature offers
• Scaling phase
SYSTEM INSTRUCTIONS
You are the RISER Moat Architect.
You design switching costs, identity lock-in, and learning loops.
You think in years, not launches.
You never optimize for short-term wins that weaken the system.
Outputs
• Moat roadmap
• Certification ideas
• Ecosystem design
🔹 OPERATOR 10: RISER LOOP AUDITOR
(System Health)
Purpose
Detect weak points early.
When to Use
• Quarterly reviews
• Plateaus
• Burnout
SYSTEM INSTRUCTIONS
You are the RISER Loop Auditor.
You are objective and diagnostic.
You identify the weakest RISER stage and recommend fixes.
You do not prescribe tactics until root causes are clear.
Outputs
• Loop health report
• 90-day action plan
🔒 FINAL INSTALL RULE
Humans:
• Set direction
• Approve outputs
• Define values
AI Operators:
• Execute rules
• Detect patterns
• Remove repetition
NEXT (HIGHLY RECOMMENDED)
If you want, next I can:
• Package these into downloadable prompt files
• Create step-by-step Custom GPT setup screenshots
• Build n8n / Make JSON blueprints
• Design the RISER Operator Certification
Just tell me the next build step.
Record the offer baseline, approval and limits on change
What the workbook does
The SYS_05_OFFER_LOCK sheet records an offer's definition, delivery, evidence, approved experimentation and governance status. It contains twenty-six columns and one example offer row. It has no formulas, automatic scoring or executable freeze logic. You will learn how to interpret every field and prepare a reviewable record without treating a typed status as proof of approval.
The sample is a Weekly Money Control System for an Overwhelmed Budget Rebuilder. It is an illustrative source record, not an adopted RISER subscription, financial recommendation or verified customer result. Preserve its actual values in the complete appendix while adapting the field structure to your own evidence.
Identify the offer and its review history
Columns A–E contain Offer ID, Project ID, Date Locked, Offer Name and Primary Avatar. The example uses OF-0001, PRJ-0001 and December 15, 2025, followed by the offer and audience names above. These fields let a reviewer distinguish this record from another project or offer version. The source provides no uniqueness check, versioning formula or duplicate-prevention mechanism.
The dates are stored as text in the original. Their appearance alone does not mean the workbook has a functioning date calculation or review schedule. Preserve the original representation when inspecting the source and verify the date meaning in an actual operating record.
Define the promise, mechanism and exclusions
Column F, Core Promise (Outcome), says the sample aims to help someone feel in control of money without obsession or shame. This is proposed customer-facing language, not evidence that every user experiences that feeling.
Column G, Mechanism (How it works), describes a weekly system for awareness, planning and decisions. The sample calls aspects automated, but the workbook contains no automation proving that claim. Column H, What This Is NOT, excludes a budgeting app, financial advice and extreme frugality. Keep those distinctions visible when interpreting the promise rather than letting a broad headline override the stated scope.
For your own record, connect the promise to an actual deliverable and documented mechanism. Do not replace an unsupported result with more confident wording.
Specify the first win and its evidence
Column I, First Win Definition, says the sample user completes a ten-minute weekly money map and identifies found money. Column J, Time-to-First-Win, gives twenty-four hours. Ten minutes describes the proposed activity duration; twenty-four hours describes the separate first-win timing field. They are not interchangeable measures, and neither is verified by the example row.
Column K, Proof Mechanism, names a before/after worksheet and a bank-balance-clarity screenshot. Those are proposed evidence types, not attached completed proof. Use only appropriate evidence for the actual task and keep sensitive account information out of public lesson examples. This source is not a request to access financial accounts or provide individualized financial guidance.
Describe the included assets, delivery and price
Column L, Offer Stack (Included Assets), includes a checklist, templates, short walkthrough videos, reminder automation and community access. Column M, Delivery Method, describes digital templates, short videos and automated reminders. The lists overlap but serve different purposes: one states what is included and the other how it is delivered. Community access and the checklist remain included even though the delivery field does not repeat them.
Column N, Price Point, contains the text “$49 / month.” It is a sample monthly price, with no separate currency-code field, tax treatment, price calculation or billing integration. It is not a newly authorized charge or verified public offer.
Column O, Guarantee / Risk Reversal, says cancel anytime and a seven-day no-questions refund. Preserve those as the sample's terms. The row supplies no complete agreement, billing implementation or evidence that the policy has been applied. Do not adopt these terms for a different offer without the actual approved policy.
Separate objections, success conditions and failure modes
Column P, Primary Objections Addressed, lists lack of time, previous failure and concern that the habit will not stick. They are sample objections, not transcripts of verified customers.
Column Q, What Must Be True for Success, requires an honest weekly review and engagement once per week. Column R, Known Failure Modes, lists skipping the first win, overcomplicating setup and avoiding the numbers. These fields expose participation requirements and plausible breakdowns. They do not prove that every poor result is the customer's fault or that the proposed system removes all effort.
Compare these conditions with the core promise and delivery. A promise of a simple process still needs an accurate explanation of what the customer must do.
Bound experiments and changes
Column S, Allowed Experiments, lists messaging angles, hook tests and call-to-action wording. Column T, Disallowed Changes, lists changing the core promise, adding complexity and expanding the avatar. This sample distinguishes testing how an existing offer is explained from changing the offer itself.
A permitted hook test still needs to respect the actual promise and evidence. If learning suggests that the promise or audience should change, seek the appropriate revision decision instead of quietly treating it as a wording test. The workbook does not define a full change-approval workflow.
Interpret the governance fields
Column U, Lock Status, contains Locked in the example. Column V, Freeze Rule Trigger, states a refund rate greater than 8% OR a support-ticket spike greater than 30%. Keep the strict greater-than comparisons and the OR relationship. Exactly 8% or exactly a 30% increase does not satisfy the written greater-than condition, though a separate policy could require action for other reasons.
The source omits the refund denominator, observation window, support baseline, minimum counts and precise meaning of a spike. It does not connect the text to a formula or alert. Resolve those definitions before evaluating a real trigger, and do not invent a freeze result from the example.
Column W, Governor Approval (Y/N), contains Y. Column X, Owner (WHO), names Founder. Column Y, Last Review Date, repeats December 15, 2025. Column Z, Notes, says the offer was locked after fifteen validated signals and a successful beta. The actual signal records, validation criteria, beta results and approval evidence are not included. Y and Locked are recorded values, not authenticated review evidence or a locked spreadsheet cell.
Understand all three dropdowns
J 2:J 1000 lists nine first-win timing choices: five minutes, fifteen minutes, thirty minutes, one hour, twenty-four hours, three days, seven days, fourteen days and thirty days. These options do not replace the separate ten-minute activity description in the sample. If an actual timing does not fit, resolve the allowed representation instead of silently choosing a false value.
U 2:U 1000 lists Draft, Locked, Soft Freeze and Hard Freeze. The workbook does not define the difference between the two freeze levels or their permitted transitions. W 2:W 1000 lists Y and N for governor approval. A blank is allowed in all three validation ranges.
The file's validation settings do not enable input or error messages. Each rule is a list validation with allowBlank set to 1 and showDropDown, showInputMessage and showErrorMessage stored as 0. These are the original settings, not a completed native-application behavior test. Do not assume the dropdowns prevent every invalid entry. The visible first row is frozen for navigation. The source contains no automatic filter, conditional formatting, charts, images, comments or hyperlinks.
Review the complete record
An authored review should trace the twenty-six fields to the approved offer and supporting evidence, confirm the actual owner and decision date, distinguish missing values from No, and check that permitted experiments do not contradict disallowed changes. Keep the first-win measure, participation and proof aligned.
The original contains all fifty-two populated cells as text: twenty-six headings and twenty-six sample values. Its recorded price, dates, status and thresholds do not calculate themselves. A complete source appendix and original download let a reviewer inspect the actual data and dropdown definitions rather than relying only on this explanation.
Apply the marketing themes and practice
As an authored Brunson/ClickFunnels connection, the approved promise, first win and boundaries should remain consistent across hooks, calls to action and delivery. As an authored Hormozi/Acquisition.com connection, describe value through the desired outcome, supporting proof, delay and effort without hiding participation or risk. This workbook supplies a record format, not proof of those outcomes.
For practice, draft your offer record using the same fields, identify the evidence supporting approval, and explain one permitted message test and one change requiring renewed review. Define the missing metric windows and baselines before claiming a freeze rule is ready to operate. Do not copy the sample's Y or Locked status as a shortcut to completion.
The original workbook is preserved byte-for-byte for the complete appendix and download. The sample's videos, worksheets, automation, community, signal evidence and beta results are not supplied as linked artifacts in the workbook and remain unresolved resources.
This source has one visible sheet, twenty-six fields and one illustrative offer row. Its typed Locked and Y values are not verified approval or evidence of a functioning governance system. All fifty-two nonempty cells are retained below. The narrow reading view repeats the same data for convenience.
SYS_05_OFFER_LOCK — original A1:Z2 cell layout
Row
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
1
Offer ID
Project ID
Date Locked
Offer Name
Primary Avatar
Core Promise (Outcome)
Mechanism (How it works)
What This Is NOT
First Win Definition
Time-to-First-Win
Proof Mechanism
Offer Stack (Included Assets)
Delivery Method
Price Point
Guarantee / Risk Reversal
Primary Objections Addressed
What Must Be True for Success
Known Failure Modes
Allowed Experiments
Disallowed Changes
Lock Status
Freeze Rule Trigger
Governor Approval (Y/N)
Owner (WHO)
Last Review Date
Notes
2
OF-0001
PRJ-0001
2025-12-15
Weekly Money Control System
Overwhelmed Budget Rebuilder
Feel in control of money without obsessing or feeling shame
A simple weekly system that automates awareness, planning, and decisions
Not a budgeting app; not financial advice; not extreme frugality
User completes a 10-minute weekly money map and identifies found money
24 hours
Before/after worksheet + bank balance clarity screenshot
Checklist; templates; short walkthrough videos; reminder automation; community access
Digital templates + short videos + automated reminders
$49 / month
Cancel anytime; 7-day no-questions refund
I don’t have time; I’ve failed before; This won’t stick
User completes weekly review honestly; engages once per week
User skips first win; overcomplicates setup; avoids looking at numbers
The three lists cover J2:J1000, U2:U1000 and W2:W1000. Blank entries are allowed; the source disables input and error messages. Row one is frozen. This appendix shows the definitions but does not implement interactive dropdowns. The original has no formulas, images, charts, comments, merged cells, hyperlinks or conditional formatting in the recorded inspection. It provides no automatic approval, freeze decision or measured business results. Original styles and native behavior remain in the workbook download; visual comparison is pending.
Score an offer with evidence and choose its next improvement
See beyond sales revenue
Imagine an operator looking at a month of steady sales. This is an illustrative scene. The sales look healthy, but buyers stop halfway through the training. Few move to the next offer. A revenue total hides both problems.
The gap is between measuring sales and reviewing the whole offer. This lesson teaches the source's fifteen-dimension monthly scorecard. You will connect each score to evidence, compare the dimensions, and write a specific action. You will also learn where the source's rules conflict.
The scorecard source describes a seven-metric weekly review. The related Weekly Offer Review SOP actually lists twelve dashboard metric rows, seven preliminary data-pull steps and six timed review segments. Keep those different counts explicit. It proposes about twenty minutes for the basic review, with longer exceptions for larger portfolios, monthly review and data failures. The monthly scorecard examines fifteen dimensions. The forensic audit investigates triggered problems in depth. These are the sources' intended roles and time estimates, not measured guarantees. Run a monthly review even when the weekly numbers seem stable.
The scorecard connects to the Kill Criteria assessment, the 10× Mechanism Test, copy and asset synchronization, and Negative Avatar profile updates. Naming those resources does not mean their full procedures are supplied here. Match the actual linked sources before claiming a complete operating system.
The framework combines clear outcomes and perceived value, risk reduction and proof, and movement through an offer ladder. Those are the relevant Hormozi, Kennedy and Brunson themes. A scoring label does not establish endorsement or a result guarantee.
Apply the five scoring principles
Read each principle with its failure mode. Then point to evidence for your own offer. The complete source table is included here because its distinctions matter.
Principle
Statement
What It Prevents
Evidence-only scoring
Every dimension score must be supported by specific data or observations. Gut feel is not evidence. 'I think the mechanism is strong' is not a score. '10× Test scored 7.6 on [date]' is a score.
Optimism bias — the tendency to score your own offer higher than the data justifies because you are emotionally invested in it.
Dimension independence
Each dimension is scored on its own merits, not influenced by other dimensions. A high conversion rate does not increase the mechanism score. A low refund rate does not raise the completion rate score.
Halo effect — the tendency to rate all dimensions of a successful-feeling offer higher than they deserve.
Consistency over time
The same scoring criteria are applied to the same offer every month. Criteria do not change to make an underperforming offer look better. If the criteria were wrong, update them in the SOP and re-score all prior records.
Criterion drift — changing the definition of a score level to accommodate a declining offer rather than acknowledging the decline.
Cluster awareness
The composite score is a starting point. The cluster profile — which five dimensions cluster strong and which cluster weak — is more actionable than the total. A score of 50 with all 10 points missing from Delivery tells you something completely different from a score of 50 with all 10 points missing from Proof.
False comfort from composite scores — an average total hiding a critical cluster failure that is about to produce a refund spike or support collapse.
Action obligation
Every dimension scoring 1 or 2 is a mandatory intervention. A dimension can score 1 for one month before a targeted intervention is documented and deployed. It cannot score 1 for two consecutive months with no action taken.
Passive monitoring — scoring problems and doing nothing, which creates a false sense of measurement without the accountability of action.
Evidence means a dated test, a measured cohort or an observed record. A mechanism test of 7.6 on a known date is more useful than saying the mechanism feels strong. Keep dimensions independent: low refunds do not prove completion, and high conversion does not prove a named method works.
Keep the same criteria across months. If a criterion changes, retain the old record and record a consistent reassessment so the trend remains interpretable. The source asks to rescore prior records; silently overwriting history would hide that change.
The source's cluster-awareness sentence incorrectly refers to five dimensions per cluster. There are three. Its example of a total 50 with all 10 missing points in one cluster is also arithmetically incomplete:75 minus 50 is 25. Use actual dimension sums, not that shorthand.
Every score 1 or 2 needs an action. The opening warns against two consecutive months at 1 without action; the later protocol requires intervention within seven days. Use the explicit urgency rather than waiting a month.
Gather the evidence before scoring
The source recommends the first Tuesday of each month. Monday's weekly review supplies recent data. Plan one record per active offer. Its suggested duration is 40–60 minutes for one offer or 90 minutes for three or four. Actual effort depends on data readiness.
If a team is available, the founder and a person close to operations score independently. An operations lead, support manager or community manager can provide that second view. A difference of two or more points triggers a five-minute evidence discussion before agreement. This is a proposed working method, not proof two reviewers will always agree within one point.
Pull every item in the following table. Match dates, buyer populations and measurement windows before comparing figures.
Dimension(s)
Required Data
Where to Pull It
D1 — Dream Outcome Clarity
Last 5 exit interview transcripts. Top 5 PAIN-ACUTE phrases from buyer language mining database. Sales page promise statement verbatim.
Airtable Buyer Language Mining database, exit interview recordings, sales page
D2 — Mechanism Believability
Most recent 10× Test result (date and score). Testimonials citing the mechanism name specifically. Sales call recordings: buyer response when mechanism is named.
Airtable Mechanism Name Records, testimonial registry, sales call recordings
D3 — Speed to First Win
Onboarding survey question: 'What result did you achieve in the first 7 days?' Exit interview transcripts: earliest result mentioned. Completion data: % of buyers completing Module 1 within 72 hours.
Completion rate data for current cohort. Support ticket volume in weeks 1–2 specifically. Percentage of support tickets in first 14 days citing unexpected workload.
Course platform, support help desk, onboarding survey: 'Was the workload what you expected?'
D5 — Offer Stack Strength
Current sales page bonus stack section. Buyer survey: 'Which bonus did you find most valuable? Which was least useful?' Stack slide total stated value.
Sales page, buyer survey data, exit interview Q: 'Which component would you remove?'
D6 — Guarantee Power
Current guarantee language verbatim from sales page. Refund reasons tagged in Airtable — how many cite the guarantee as insufficient or confusing?
Sales page, Airtable Refund Records (root cause codes)
D7 — Social Proof Specificity
Count and type of current testimonials on sales page. Testimonial Version Registry — all version-current testimonials. Proof-to-promise match audit result.
Airtable Testimonial Version Registry, sales page, exit interview recordings
D8 — Cold Conversion Rate
30-day rolling cold conversion rate from GA4 and CRM.
GA4 + CRM (GoHighLevel). Weekly Offer Review Records — last 4 weeks of cold conversion data.
D9 — Refund Rate
Rolling 30-day refund rate from Stripe. Root cause code distribution from Airtable Refund Records.
Stripe, Airtable Refund Records
D10 — Unit Economics
Gross margin calculation: revenue minus all variable delivery costs. CPA from paid ad platforms (if applicable). Total fixed monthly platform costs.
Stripe + delivery cost records. Meta/Google Ads Manager. Margin Stress Test model from Fulfilment Stress Test SOP (if run).
D11 — Completion Rate
Current cohort completion rate from course platform. Trend over last 3 cohorts.
Kajabi or course platform analytics
D12 — Ascension Rate
CRM pipeline: how many buyers moved to a higher tier in the last 60 days. Divided by total buyers who completed the current tier in the same window.
CRM pipeline stage movement report (GoHighLevel or HubSpot)
D13 — Support Efficiency
Average weekly tickets per active buyer. Average first response time from support platform. Most common ticket categories.
Intercom or Help Scout analytics dashboard
D14 — Mechanism Strength
Most recent 10× Test scorecard (all 5 subtest scores). Buyer language adoption rate from last exit interview batch. GEO citation check: mechanism name cited in Perplexity/ChatGPT/Gemini.
Last sales page update date from Product Versioning Changelog. Version drift audit result. Testimonial registry — any version-specific retired testimonials flagged.
Airtable Changelog Entries, Testimonial Version Registry, current sales page vs latest Version Archive snapshot
The source assigns 1 when evidence is missing and asks for the note “data gap — cannot score accurately.” Preserve that convention separately from a measured poor result. Unknown data is not evidence of failure. Record what must be collected and who will collect it.
For D12, the data table divides upgrades by buyers who completed the tier in the same 60-day window. The rubric describes all buyers. Those denominators produce different rates. Choose and document a coherent cohort; do not compare unlike rates. For D13, first response time in the data table differs from resolution time in the rubric. Collect both or mark the missing measure.
Understand the five clusters
Each cluster adds three scores, with a range of 3–15. All fifteen scores add to 15–75. Follow the D-code membership below.
Cluster
Dimensions
What It Measures
Cluster 1 — Promise
D1 D2 D3
How compelling, clear, and credible is the transformation promise? Directly maps to the top half of Hormozi's Value Equation.
Cluster 2 — Proof
D4 D5 D6
How well is the value justified, risk reduced, and purchase decision de-risked? Kennedy's offer intensification layer.
Cluster 3 — Revenue
D7 D8 D9
How is the offer performing economically — conversion, retention, and margin? The Hormozi unit economics layer.
Cluster 4 — Delivery
D10 D11 D12
How effectively is the offer being fulfilled? Completion, ascension, and support efficiency — the delivery promise layer.
Cluster 5 — Positioning
D13 D14 D15
How sharp is the offer's market positioning? Mechanism strength, copy currency, and GEO/AEO citability.
The labels are imperfect. D7 social proof is in Revenue, D10 economics is in Delivery, and D13 support is in Positioning. Some headings describe other dimensions instead. Preserve the formulas while naming that mismatch; do not silently relocate scores and break comparison with the original.
Score every dimension using all five levels
The following is the complete source rubric, including its cluster header rows. Treat each level as an evidence claim. Read the criteria across a row before choosing a score. The blank score column is for the reviewer. The explanations after the table identify its limits; no missing boundary has been invented.
D1 checks whether buyers understand a specific result before purchase. Direction alone differs from a number or timeframe; both differ from a promise that buyers can repeat and delivery can support. Do not invent a precise outcome simply to earn a higher score.
D2 asks whether this buyer believes this method fits their situation. Naming a method is only the middle level. The stronger levels need matching proof and test scores of 7.0 or 7.5, plus buyer evidence where specified. A catchy name does not prove effectiveness.
D3 examines the first measurable win. The source moves from no win or an overstated promise to week 3+, then 5–7 days, then 48–72 hours. Its highest level also says under 72 hours but adds documentation, buyer reports and completion evidence. These timing ranges overlap. Explain all conditions instead of deciding on timing alone.
D4–D6: effort, offer components and guarantees
D4 combines workload expectations with completion bands. Read the support evidence as well as the percentage. The top level includes explicit expectations and done-with-you support. Completion alone cannot establish a perfect workload match.
D5 asks whether each offer component solves a named sub-problem. The source's stated-value multiples—below 5×,5–6×,7–9× and 10×+—need a defensible valuation method. They are not permission to fabricate prices for bonuses. At the top level, four of five avatar testers must also pass its test equivalent. Fractional gaps between some multiples and an undefined test equivalent remain source gaps.
D6 moves from absent or confusing guarantees through difficult conditions, a standard 30-day guarantee, conditional result-based terms, and stronger result- or service-based terms. Its level numbers overlap. Use feasible, clear terms and real delivery capacity. A higher score is not a reason to promise an outcome you cannot support. The full five-level guarantee framework is referenced but not defined here.
D7–D9: proof, conversion and refunds
D7 distinguishes unverifiable claims from generic testimonials, outcome accounts and exact metric/timeframe matches. Its highest criterion calls for five or more matched testimonials and at least two videos. Only genuine, appropriately used testimonials count. The source's lower testimonial counts overlap; assess specificity and format too.
D8 divides buyers by unique cold visitors. Define cold traffic and a consistent observation window. Its bands leave gaps between decimal endpoints, such as 0.9 and 1.0, unless a rounding rule is declared. D9 similarly leaves 15% unassigned and fractional gaps between bands. Retain the raw measured rate and flag the ambiguity rather than silently rounding it into a preferred grade.
Refund requests, processed refunds and refunds from different cohorts are not automatically interchangeable. D9's wording concerns buyers requesting refunds over a rolling 30 days; verify what the payment report actually counts.
D10–D12: economics, completion and advancement
D10 examines gross margin and acquisition cost relative to price. CPA means cost per acquisition. The source gives paired percentage bands, with an explicit OR at the critical level. It does not define how to combine a strong margin with a weak CPA, and exactly 50% CPA is unassigned. Keep both measurements visible. Don't invent an averaging rule based on the worked example.
D11 measures completion of the full programme or core deliverable. Preserve the cohort definition and its trend over three cohorts. Percentage bands with whole-number endpoints need a stated precision rule. Completion is evidence of participation in the defined work, not automatic proof of the promised outcome.
D12 measures movement to the next offer within 60 days. It treats an unbuilt sequence as critical even without a measured low rate. The highest level adds a documented sequence and buyers citing the prior result. Separate sequence readiness from measured results and disclose the buyer-versus-completer denominator conflict. Its whole-number bands also leave fractional gaps.
D13–D15: support, method adoption and current copy
D13 combines tickets per active buyer per week with time to resolution. Boundaries 2,3 and 5 overlap across some ticket bands. First response is not resolution. The strongest level also needs a self-service FAQ to address most common questions. State which combined conditions are actually evidenced.
D14 combines test scores, use of the method's name and an AI citation check. Adoption 50–69% versus above 70% leaves 70% undefined. Mixed adoption/test results need a declared assessment rule. AI answers vary; citations cannot be guaranteed or treated as proof of a method's effectiveness. A source calling a method proprietary does not establish ownership.
D15 checks whether the current page matches current delivery. It moves from version drift through stale copy to updates within 180 or 90 days with stronger alignment conditions. The time windows overlap. Recent editing alone does not prove current promises or testimonials are accurate.
Add the scores, then examine the grade
Use the 15 stated scores, not a feeling about the business. A=65–75;B=50–64;C=35–49;D=20–34;F=15–19 under this scale. The source says F below 20;15 is the minimum possible.
At A, the source proposes a scale event, a 2× capacity simulation before increasing buyer volume more than 50%, another traffic source this month, a targeted ascension sequence and planning the next tier. These are recommendations conditional on real capacity and individual evidence. An A total can still contain a critical individual dimension or a weak cluster. It cannot contain a cluster below 5: even with 60 points from the other four clusters, a cluster of 4 yields only 64. It does not prove every area is strong.
At B, identify the weakest cluster and its lowest dimension. Apply a targeted fix and establish at least two months of stability before considering scale. The source says 10–25 points are missing, but the correct gap to 75 is 11–25. Its claim that B means no catastrophic dimension is not implied by the sum. The intervention table is Phase 4, despite the B panel's Phase 5 reference.
At C, the source says to fix before increasing paid traffic or entering a new partner audience. Act on each 1 or 2, run the Pre-Kill Diagnostic, and rescore after 30 days. If still below 50 after targeted fixes, escalate to the separate Kill Assessment. A score is a diagnostic prompt, not an automatic shutdown command.
At D, run that separate Kill Assessment immediately. It has fifteen 0–4 scores, maximum 60, while this monthly health scorecard has fifteen 1–5 scores, maximum 75. Do not convert one to the other silently.
At F, the source recommends immediately pausing paid ads and new admissions, completing the Kill Assessment within seven days, and following its Clean Kill Process for a Kill or Pivot outcome. This lesson explains those recommendations. It does not execute ad pauses, admission changes or business decisions.
Read each cluster and supplied profile
Use the source's full band interpretations below as hypotheses to investigate. A score cannot alone prove profitability, buyer belief, competitive advantage or actual delivery results.
Cluster
Max Score
Score Interpretation
Cluster 1 — Promise (D1+D2+D3)
Max: 15
13–15: Promise is a competitive advantage. 9–12: Promise is viable, improvement opportunities. 5–8: Promise is underpowered — buyers can't feel the transformation before they buy. Below 5: Critical — the promise is repelling or confusing buyers.
Cluster 2 — Proof (D4+D5+D6)
Max: 15
13–15: Proof layer creates instant conviction. 9–12: Proof is present but not maximally persuasive. 5–8: Proof is thin — buyers are taking a faith-based purchase. Below 5: Critical — buyers have no reason to believe the promise.
Cluster 3 — Revenue (D7+D8+D9)
Max: 15
13–15: Offer is economically healthy — scale with confidence. 9–12: Viable economics, optimisation available. 5–8: Economics are marginal — find and fix the leak before scaling. Below 5: Critical — this offer is losing money or destroying reputation.
Cluster 4 — Delivery (D10+D11+D12)
Max: 15
13–15: Delivery is producing results at scale. 9–12: Delivery is adequate, completion and ascension improvements available. 5–8: Delivery is underserving buyers — results are inconsistent. Below 5: Critical — buyers are not getting what they paid for.
Cluster 5 — Positioning (D13+D14+D15)
Max: 15
13–15: Positioning is a market differentiator. 9–12: Positioning is adequate, mechanism freshness opportunity. 5–8: Positioning is eroding — the offer is blending into the category. Below 5: Critical — the offer looks like every competitor's offer.
The next table contains all five profiles actually supplied. The source calls them fourteen in its heading and database field, but nine additional profiles are absent. Do not invent them.
Profile Name
Cluster Pattern
Commercial Signature
Primary Intervention
The Strong Promise, Weak Proof
Cluster 1 (Promise): 11+. Cluster 2 (Proof): 5–8.
Offer attracts attention and interest but buyers hesitate at the decision point. High opt-in rates but low conversion. Buyers 'like the idea' but don't commit.
Immediate: upgrade guarantee (D6) and build proof library (D7). The promise is working — the buyer just needs risk removal before buying.
The Proven Offer, Broken Delivery
Clusters 1,2,3 high. Cluster 4 (Delivery): 5–8.
Offer converts well and generates revenue, but buyers are not getting consistent results. Refunds are low because the copy is strong enough to manage expectations, but completion is low and ascension is stalling.
Run Fulfilment Stress Test SOP. Check Completion Rate (D11) and Support Efficiency (D13) specifically. The funnel works — the programme does not.
Existing buyers love the programme and get results (high completion, low refunds), but cold conversion is low and the economics are struggling. Strong word-of-mouth but weak top-of-funnel.
Focus on D8 (Cold Conversion Rate) and D2 (Mechanism Believability). The delivery is the proof — extract it into better testimonials and a more compelling mechanism. Run the 10× Mechanism Test.
Offer is functionally healthy but competitively invisible. The market can't differentiate it from alternatives. Growing slowly because it blends into the category.
Run the 10× Mechanism Test (D14) immediately. Update copy with buyer language mining data (D15). The offer is good — nobody knows why it's different.
Offer converts and buyers get results, but the margin is being eroded by high support costs, high CPA, or miscalculated delivery costs. The business is working hard for thin returns.
Run the Margin Stress Test (Fulfilment Stress Test SOP Phase 4). Find where the cost is leaking: support hours, tool costs, CPA, or revision cycles.
Check the named dimensions before applying an intervention. Strong Promise, Weak Proof recommends D7 even though D7 sits outside the formal Proof cluster. Economics Leak calls D10 part of Cluster 3 even though the formulas put it in Cluster 4. These inconsistencies mean a profile name must not replace the underlying diagnosis.
The commercial descriptions propose explanations, such as strong copy keeping refunds low. Those are hypotheses, not established causes. Inspect completion, support, conversion and cost records to test them.
Assign an action for every weak dimension
This table preserves all five score-level obligations, owners and deadlines.
Dimension Score
Action Obligation
Who Assigns
Deadline
5 — Excellent
No action required. Note the strength as a potential copy asset or testimonial angle.
N/A
N/A
4 — Strong
Monitor. If score does not improve to 5 within 3 months, identify the specific gap and assign a targeted action.
Owner logs in scorecard record
Within 90 days
3 — Adequate
Identify the specific gap between current performance and the level-4 criteria. Assign a targeted action for the current or next month.
Owner logs in scorecard record + Weekly Review
Within 30 days
2 — Weak
Mandatory targeted action within the current month. Document specific action in scorecard record using the Action Definition Format from the Weekly Review SOP. Report progress in next month's scorecard.
Founder or ops lead must own directly
Within 30 days — report in next scorecard
1 — Critical
Immediate escalation. This dimension is triggering or approaching a Hard Kill threshold. Run the relevant diagnostic SOP this week. This cannot wait for the next monthly review.
Founder owns directly — not delegated
Within 7 days of scorecard completion
For a 3, record the exact gap to 4 and a targeted action. The source says current or next month but also gives 30 days; write an actual due date. For a 4, its three months and 90 days are approximate equivalents, not identical calendar periods. A 1 requires a founder-owned intervention within seven days. A 2 requires founder or operations ownership within 30 days and an update next month.
Here are all fifteen starting interventions and named connecting procedures. Read the prescribed step, then identify the actual evidence and prerequisite before assigning it.
Dimension
Score 1 or 2 — Prescribed Intervention
Connecting SOP
D1 — Dream Outcome Clarity
Rewrite the sales page promise section using the top 5 PAIN-ACUTE phrases from the buyer language mining database. Add a specific metric and timeframe to the headline promise. Test against prior version.
Post-MVO Forensic Audit Loop (Phase 3 — Buyer Language Mining)
D2 — Mechanism Believability
Run the full 10× Mechanism Test Protocol with 5 avatar-matched testers. If test score below 7.0: initiate the Rename Cadence (Phase 3 — Name Generation System).
10× Mechanism Test & Rename Cadence SOP
D3 — Speed to First Win
Audit Module 1 delivery. Design a specific Quick Win deliverable that the buyer can achieve within 72 hours. The Quick Win must produce a visible, shareable output. Deploy in the next cohort.
Fulfilment Stress Test SOP (Phase 3 — Delivery Architecture Map)
D4 — Effort Alignment
Add an explicit effort statement to the sales page ('This programme requires X hours per week for Y weeks'). Add the corresponding 'Not for you if you cannot commit X hours' bullet to the 'Not for you' section. Monitor dropout rate for improvement.
Apply Hormozi's Trim & Stack: list every sub-problem on the path to the core promise. Trim high-cost/low-value bonuses. Add 1–2 low-cost/high-value bonuses specifically solving named sub-problems. Rebuild the Stack Slide.
Review the five guarantee levels in MVO Playbook Phase 4. Move one level up from the current guarantee. Rewrite the guarantee section using Kennedy's 'bold enough to feel uncomfortable' standard.
MVO Playbook V5 (Phase 4 — Guarantee Engineering)
D7 — Social Proof Specificity
Run the Proof Harvesting Protocol from the Beta Testing Methodology SOP. Conduct exit interviews specifically requesting proof-matched testimonials. Retire any generic testimonials from the sales page.
Run the Pre-Kill Diagnostic from the Kill Criteria SOP before changing anything. Ensure all six diagnostic fixes have been applied. If diagnostic is clean: run Forensic Audit Loop Phase 4 (Conversion Funnel Diagnostic).
Process all refunds through the 5-step Refund Forensics Protocol. Identify root cause codes. If 3+ refunds share the same RC code: create or update a Negative Avatar Profile.
Run the Margin Stress Test from the Fulfilment Stress Test SOP (Phase 4). Identify the specific cost leaking the margin. If CPA is the problem: pause the worst-performing ad set before any other change.
Fulfilment Stress Test SOP (Phase 4 — Margin Stress Test)
D11 — Completion Rate
Audit the module or week where dropout is highest. Add an accountability check-in and a Quick Win for that specific point. Run the Time-and-Motion Audit (Fulfilment Stress Test Phase 3) to check whether capacity is limiting delivery quality.
Fulfilment Stress Test SOP (Phase 3 — Time-and-Motion Audit)
D12 — Ascension Rate
Verify the ascension email sequence is active in the CRM. Check trigger conditions — is it firing at the right moment? Rewrite Days 14 and 21 post-purchase emails to present the next tier offer at the buyer's win moment.
Post-MVO Forensic Audit Loop (Phase 6 — Next Problem Signal)
D13 — Support Efficiency
Identify the top 3 support ticket topics from the past 30 days. Build one self-serve FAQ or walkthrough video for each. Add to the onboarding sequence. Track whether tickets on those topics decline within 30 days.
Fulfilment Stress Test SOP (Phase 6 — Support Load Projection)
D14 — Mechanism Strength
Run the 10× Mechanism Test immediately. If no test has been run in 90+ days: Health Indicator HI-2 (no AI citation) or HI-4 (competitor adoption) may also be triggering. Run all five health indicator checks.
10× Mechanism Test & Rename Cadence SOP (Phase 2)
D15 — Copy Currency
Run the Copy & Asset Synchronisation Checklist from the Product Versioning SOP. If version drift is confirmed: trigger a Minor version update (CAT-C) and complete the 40-item sync checklist within 14 days.
The table includes specific copy tests, five-person mechanism testing, a 72-hour win, workload disclosure, Trim & Stack, guarantee review, proof harvesting, pre-kill diagnostics, refund coding, cost analysis, dropout repair, Days 14 and 21 ascension emails, three support FAQs, method-health checks and a 14-day 40-item asset update. None has been executed by this lesson.
D8 references six diagnostic fixes without listing them here. D14 references five health indicators and examples HI-2 and HI-4 without giving the whole indicator procedure. D15 references CAT-C, a 40-item checklist and a versioning procedure. D6 references a five-level guarantee model. These named dependencies require their actual sources. Do not fill the gaps with invented steps.
Track whether the offer improves
Compare months, not just totals. A flat 52 for three months differs from 44,48,52. The latter is improving, but not necessarily because of a particular intervention. Changes in traffic or cohort composition can affect scores too.
Keep the complete four-month comparison view. Blank cells are fields to fill, not measured zeros.
Field
Month 1
Month 2
Month 3
Month 4
Trend
Composite Score
↑ / → / ↓
Grade
Cluster 1 — Promise
↑ / → / ↓
Cluster 2 — Proof
↑ / → / ↓
Cluster 3 — Revenue
↑ / → / ↓
Cluster 4 — Delivery
↑ / → / ↓
Cluster 5 — Positioning
↑ / → / ↓
Lowest-scoring dimension
Dimensions at 1 (count)
Dimensions at 2 (count)
Priority action this month
Trend Pattern
Interpretation
Required Response
Composite score improving 5+ points per month for 2+ months
Active improvement cycle is working. Actions are producing measurable results.
Continue the current intervention approach. Do not change strategy mid-improvement.
Composite score flat (±3 points) for 2+ months
Offer has reached a local optimum. Current interventions are not producing gains.
Identify the single dimension with the lowest absolute score and run a deeper diagnostic on it. Consider whether a mechanism rename or a value ladder review is needed.
Composite score declining 5+ points per month
Offer is deteriorating despite or without intervention. An undiagnosed structural problem is worsening.
Escalate to Forensic Audit Loop immediately regardless of which specific trigger threshold has been crossed. Something is breaking that the monthly scorecard cannot see at this resolution.
One cluster score declining while others improve
A specific area of the offer is degrading even as the rest improves. Often indicates a delivery capacity problem (Cluster 4 declining as buyer volume grows) or a positioning erosion (Cluster 5 declining as market language shifts).
Run the cluster-specific diagnostic SOP for the declining cluster. Do not let one cluster drag the composite score into a lower grade.
All dimensions at 3 or above, but composite score stuck at B
The offer has no critical weaknesses but also no competitive strengths. Everything is adequate; nothing is excellent.
Identify the two dimensions closest to 4 and invest specifically in pushing them to 5. A B-grade offer with two 5-scoring dimensions has competitive differentiation. A B-grade offer with all 3s is a commodity.
The trend rules leave some cases undefined, including four-point changes and shorter histories. Record the observation without inventing a category. A decline of five or more points in a month triggers investigation in the trend table; the closing checklist also triggers investigation after two consecutive declining months. Preserve both signals.
The final trend row incorrectly describes fifteen scores of 3 as grade B. They total 45, which is grade C. Scores all at least 3 can also include scores of 5, so grade B does not mean nothing is excellent. Inspect the actual two dimensions you can improve; don't rely on that claim.
Store all thirty-five fields
The source says 33 fields in its checklist, but the schema contains 35. Preserve all of them. The full schema below includes four identity fields, fifteen scores, composite and grade, five clusters, and nine profile/evidence/action/history fields.
Data sources used for each score. Note any data gaps.
Mandatory Actions (score 1 or 2)
Long text
Action Definition Format for each dimension at 1 or 2
Triggered SOPs
Multiple select
Which SOPs have been triggered by this scorecard session
SOP Sessions Scheduled
Long text
Date and time blocks for each triggered SOP session
Prior Month Score
Link → Scorecard Records (self)
Link to same offer's prior month scorecard for trend view
Score Delta vs Prior Month
Formula
Composite Score minus Prior Month Composite Score
The proposed Scorecard ID type is Autonumber while its required format includes offer code and year-month. That needs a deliberate formatted-field design. Likewise, a prior-record link does not by itself supply the prior numeric score for subtraction. The source describes formulas but does not supply a working database or tested syntax. Validate score range and required evidence in any implementation.
Keep original evidence, decision notes, scheduled sessions and outcomes connected. A filled form is not proof an action was performed. Missing profiles and data belong in explicit notes.
Walk through the fictional example and correct its conclusion
The source provides a mid-tier offer ninety days after launch. It is fictional. Read every evidence row below. Ask whether the rationale actually matches the rubric, not just whether its explanation sounds plausible.
Dimension
Score
Evidence Used
Scoring Rationale
D1 — Dream Outcome Clarity
3
Exit interviews: buyers describe 'growing my audience' but rarely cite specific numbers. Sales page promise: 'Build a content engine that attracts clients.' PAIN-ACUTE top phrase: 'I post constantly but nobody buys.'
Direction is clear (content engine, client attraction) but no specific metric or timeframe on the sales page. Buyers understand the category but not the specific deliverable. Score: 3 (Adequate — specific in direction, missing metrics).
D2 — Mechanism Believability
3
10× Test run 6 weeks ago: average score 6.8. Buyers in exit interviews describe 'the content system' without naming the mechanism. 2 of 12 recent buyers cited the mechanism by name on sales call recordings.
Below the 7.0 threshold for score 4. Buyer adoption below 50%. Mechanism exists and is named but not yet landing with urgency. Score: 3.
D3 — Speed to First Win
4
Onboarding survey Q: 'What result in first 7 days?' — 11/15 respondents cited the Hook Engineering Quick Win as their first result within 72 hours. Completion data: 74% complete Module 1 within 48 hours.
Strong Quick Win in place. 74% within 48 hours exceeds the 4-score threshold. Minor gap: 26% don't complete in first 48 hours. Score: 4.
D4 — Effort Alignment
3
Support tickets weeks 1–2: 18% cite 'more work than expected.' Completion rate: 52%. Exit interview: 3 of 10 mention workload surprise in week 2 specifically.
52% completion is adequate (score 3 threshold). Effort statement on sales page is present but vague ('Invest 3–5 hours per week'). Some surprise around week 2 workload. Score: 3.
D5 — Offer Stack Strength
4
Stack Slide total stated value: $2,847 for a $497 offer (5.7× ratio). Buyer survey: 4 of 5 bonuses rated 7+ usefulness. One bonus rated 4.2 (Hook Swipe File V1 — dated).
Stack is compelling and specific. The dated Hook Swipe File is the gap keeping this from a 5. Score: 4.
D6 — Guarantee Power
3
Current guarantee: 30-day money-back, no conditions, no questions. Refund data: 6% of buyers refund between day 15–29. No clear pattern suggesting the guarantee language is the driver.
Level 1 guarantee. Functional but not differentiated. No result-based language. Score: 3.
D7 — Social Proof Specificity
3
Sales page: 8 testimonials total. 3 contain specific metrics ('47 leads in 30 days,' '3 booked calls in week 1'). 5 are directional without numbers. No video testimonials.
Has the quantity (8) and some specificity (3 with metrics) for a score of 3. Needs 2 more metric-specific testimonials and at least 1 video to reach score 4. Score: 3.
D8 — Cold Conversion Rate
3
GA4 + CRM: Rolling 30-day cold conversion: 1.4%. Trend: 1.3% → 1.4% → 1.4% for 3 consecutive months (stable).
In the 1.0–1.9% range = score 3 (viable minimum). Stable but not improving. Consistent with a B-grade offer at 90 days post-launch. Score: 3.
D9 — Refund Rate
4
Stripe rolling 30-day refund rate: 3.8%. Root cause codes: RC-3 (Expectation Gap — Timing) accounts for 60% of refunds.
3.8% is in the 2–4% band for score 4. RC-3 pattern is a signal (speed-to-result expectation gap), but the overall rate is healthy. Score: 4.
D10 — Unit Economics
3
Gross margin: 47% (revenue minus delivery costs). CPA via Meta ads: $142 for a $497 offer = 28.6% of offer price.
Course platform: 52% complete the full 4-week programme. Prior cohort: 49%. Stable at low-adequate range.
52% is in the 45–59% band for score 3. Two consecutive cohorts in the same band = structural issue, not random variation. Score: 3. FLAGGED for action.
D12 — Ascension Rate
2
CRM pipeline: 4 of 87 cohort completers (4.6%) have moved to the Core Offer within 60 days. Ascension email sequence confirmed active. Trigger point: Day 21 post-purchase.
4.6% is in the 3–5% band for score 2 (Weak). Ascension sequence is live but timing or positioning may be wrong. Score: 2. MANDATORY ACTION.
D13 — Support Efficiency
4
Intercom: average 1.4 tickets per active buyer per week. Average first response: 5.2 hours. Top ticket topics: 'Zoom link not working' and 'Can't find replay.'
1.4 tickets = score 4 (1–2 per buyer per week). Response time 5.2 hours = borderline 4/3. Top topics are technical, not content confusion — FAQ fix available. Score: 4.
D14 — Mechanism Strength
3
10× Test: T-1 average 6.8. T-5 Distinctiveness: 4/5 (strong). Buyer adoption rate: 38% use the name in exit interviews. AI citation check: 2 of 10 queries cite the mechanism.
6.8 is in the 6.0–6.9 band for score 3. 38% adoption is below 50%. Some AI citation but not dominant. Score: 3.
D15 — Copy Currency
4
Last sales page update: 47 days ago. Minor language gap: buyer mining phrase 'I post constantly but nobody buys' not yet in copy. No version drift. All testimonials version-current.
Updated within 180 days = score 4. Minor language gap is an improvement opportunity, not a problem. Score: 4.
The following is the source's original summary. Its wrong total and profile are retained for transparent comparison; the correction immediately follows.
D10(3)+D11(3)+D12(2) = 8 / 15. WEAK. D12 (Ascension Rate) is the critical gap. Delivery is working but buyers are not moving up.
Cluster 5 — Positioning
D13(4)+D14(3)+D15(4) = 11 / 15. Adequate-to-strong. Mechanism freshness is the gap.
Profile
The Delivering, Not Converting — Cluster 4 is lowest; the delivery is working but the ascension is stalling.
Mandatory Actions (D12 = score 2)
Rewrite ascension sequence Days 14 and 21. Change trigger: present Core Offer at the buyer's first measurable win (typically Day 12 based on onboarding data) rather than Day 21 calendar. Run ascension A/B test for 60 days.
Triggered SOP
Post-MVO Forensic Audit Loop — Phase 6 (Next Problem Signal). Schedule 45-minute session to audit the ascension sequence copy and trigger logic.
Add the stated scores yourself:3+3+4+3+4+3+3+3+4+3+3+2+4+3+4=49. The cluster totals 10+10+10+8+11 also equal 49. The correct grade from these stated scores is C, not the source's 51/B. Use the source's C-grade diagnostic response for this fictional case.
Several individual rationales also need review. D1 lacks a number or timeframe while its rubric 3 requires one. D5's $2,847/$497 ratio is about 5.73×, below rubric 4's 7–9×. D7's example says two more metric testimonials are needed for 4, while the rubric asks 3–4 specific testimonials and one video. D3's 74% completion within 48 hours is helpful evidence but not an explicit numeric cutoff in its rubric. D10's 47% margin and 28.6% CPA both lie in its score 3 bands, so the stated borderline/averaging explanation is unnecessary.
The D6 refund 6% during days 15–29 and D9 overall 3.8% need matching cohorts and windows before comparison. D11's 52% and 49% cohorts do not prove a structural cause. D13 uses 5.2-hour first response rather than resolution. These problems mean 49 is an arithmetic correction of the scores as written, not a fully validated rescoring.
The example calls itself Delivering, Not Converting despite Delivery being its lowest cluster at 8 and Revenue 10. That conflicts with the profile's high Delivery/weak Revenue pattern. Describe the actual D12 weakness instead. Four of 87 completers upgraded, about 4.6%. The source proposes reviewing Days 14 and 21 emails, testing a first-win trigger around its fictional Day 12, running a 60-day test, and scheduling a 45-minute forensic Phase 6 review. Those are proposed tests, not established causes or changes already made.
Use the complete operating checklist
Read each item as a requirement to verify, not a checkbox to mark because a draft exists. Correct the source's 33 to 35 fields and 14 to 5 supplied profiles while retaining the original wording below for traceability.
System Setup (One-Time) ☐ Create Offer Scorecard Records table in Airtable with all 33 fields from the schema above ☐ Set up formula fields for composite score, grade, and cluster scores — auto-calculating from dimension input ☐ Run baseline scorecard for every active offer to establish Month 1 reference scores ☐ Set recurring calendar block: first Tuesday of every month — Offer Scorecard Session (40–60 min per offer) ☐ Add formula field: Score Delta vs Prior Month — requires linking to prior month record
Every Monthly Scorecard Session ☐ Pull all required data for each dimension before opening the scorecard template ☐ Score all 15 dimensions using evidence — not gut feel ☐ Calculate composite score and grade ☐ Calculate five cluster scores and identify the weakest cluster ☐ Identify the diagnostic profile from the 14 profiles table ☐ For every dimension scoring 1: schedule the prescribed intervention SOP session within 7 days ☐ For every dimension scoring 2: document the specific action using the Action Definition Format from the Weekly Review SOP ☐ Log all triggered SOPs and block calendar time for each session before closing the scorecard ☐ Complete Offer Scorecard Record in Airtable — all 33 fields ☐ Update the Month-over-Month Comparison View — add this month's scores and calculate trend
After the Scorecard Session ☐ Execute all mandatory actions (dimensions scoring 1 or 2) within the documented deadlines ☐ Report action outcomes in next month's scorecard record under the Evidence Notes field ☐ If grade drops from B to C month-over-month: run Pre-Kill Diagnostic (Kill Criteria SOP) before next Monthly Review ☐ If composite score is declining for 2 consecutive months: escalate to Forensic Audit Loop immediately ☐ If all five clusters score 9–11 (all-adequate, nothing excellent): plan two specific dimensions to push from 3 to 5 over the next 90 days
The after-session checklist also adds a B-to-C drop trigger for the Pre-Kill Diagnostic, a two-consecutive-decline trigger for forensic review, and a 90-day plan to move two dimensions from 3 to 5 when all clusters are 9–11. Choose actual dimensions and evidence. Don't confuse a planning target with a guaranteed result.
Resources and submission
Open the assigned Offer Scorecard original. The original DOCX and its full appendix preserve source wording and table relationships. Expand the original-source appendix accompanying this lesson to inspect the full document.
Open the assigned Post-MVO Forensic Audit source for the connected audit and its additional threshold and schema conflicts. Read the related Beta Testing Methodology and Negative Avatar source. Both supporting originals have been reviewed; linking them here does not establish that every missing prerequisite is resolved or its teaching is delivered in this lesson. Read the Product Kill Criteria original; its companion teaching and complete source appendix follow alongside the weekly review. The different scoring scales and trigger conflicts remain explicit. Read Product Versioning and Offer Changelog; its companion and complete original appendix also follow. The versioning source provides 34 actual synchronization checks, which differs from this scorecard’s 40-item reference. Read the Guarantee Type Testing Protocol; its five guarantee types, eight phases, complete templates and original appendix follow. Its eligibility, testing and buyer-policy conflicts remain explicit. Read the Mechanism Test and Rename Cadence source; its full companion and local original appendix follow. Five paragraphs absent from its connected readable export are preserved locally; remote-file identity remains unconfirmed. Read the Fulfilment Stress Test; its ten-phase companion and original appendix follow. These companions preserve the available source material and flag conflicting calculations, thresholds and missing implementation assets. Final content review and complete underlying-resource resolution remain open.
RISER NATION CORP is the project brand destination. The source's legacy footer is retained in the original, not substituted for the user's domain.
Read the Weekly Offer Review original. Its companion teaching and complete appendix follow in this lesson. Its threshold conflicts and thirty-two-field documentation table are explained separately; do not substitute weekly colors for monthly dimension scores.
Turn in: one fifteen-dimension scorecard with dated evidence, all five cluster sums, the corrected grade, unresolved measurement questions and a named action owner with a due date for every 1 or 2. Keep it in your course work folder until the lesson's submission destination is confirmed. A reviewer should verify the arithmetic and evidence before using it for an operating decision.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — OFFER SCORECARD
The 15-Dimension Monthly Diagnostic That Tells You Exactly Where Every Offer Is Strong and Where It Is Bleeding
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
The Offer Scorecard is the monthly multi-dimensional health check that every active offer must pass through. It is not the real-time monitoring of the Weekly Offer Review, which scans seven metrics in 20 minutes and produces one action. It is not the deep event-triggered investigation of the Forensic Audit Loop. It is the structured evaluation instrument — the systematic, evidence-based assessment of an offer across all 15 dimensions that determine whether it is healthy, where it is weak, and what the precise intervention should be.
Most operators evaluate their offers on one or two dimensions — usually conversion rate and revenue. An offer can have a good conversion rate and still have a critical proof problem, a broken ascension sequence, a degraded mechanism name, and copy so out of date that it no longer mirrors buyer language. None of those problems appear in a conversion-rate check. They appear here.
This SOP defines the 15 scoring dimensions across five strategic clusters, the scoring criteria at each of the five levels for every dimension, the composite score and grade interpretation, the cluster profile analysis that reveals the offer's structural character, the prescribed actions by grade and profile, and the trend-tracking system that shows whether each offer is improving or declining over time.
The Scorecard's Position in the SOP Ecosystem
The Offer Scorecard sits between the Weekly Offer Review (surveillance) and the Forensic Audit Loop (investigation). It is run monthly — regardless of what the weekly review shows — and its output directly informs the Kill Criteria SOP's kill assessment, the 10× Mechanism Test, the Copy & Asset Sync from the Versioning SOP, and the Negative Avatar Modelling SOP's profile update cadence.
Scorecard Design Principles
Five design principles govern this scorecard. They are not preferences — they are constraints that make the instrument reliable.
Principle
Statement
What It Prevents
Evidence-only scoring
Every dimension score must be supported by specific data or observations. Gut feel is not evidence. 'I think the mechanism is strong' is not a score. '10× Test scored 7.6 on [date]' is a score.
Optimism bias — the tendency to score your own offer higher than the data justifies because you are emotionally invested in it.
Dimension independence
Each dimension is scored on its own merits, not influenced by other dimensions. A high conversion rate does not increase the mechanism score. A low refund rate does not raise the completion rate score.
Halo effect — the tendency to rate all dimensions of a successful-feeling offer higher than they deserve.
Consistency over time
The same scoring criteria are applied to the same offer every month. Criteria do not change to make an underperforming offer look better. If the criteria were wrong, update them in the SOP and re-score all prior records.
Criterion drift — changing the definition of a score level to accommodate a declining offer rather than acknowledging the decline.
Cluster awareness
The composite score is a starting point. The cluster profile — which five dimensions cluster strong and which cluster weak — is more actionable than the total. A score of 50 with all 10 points missing from Delivery tells you something completely different from a score of 50 with all 10 points missing from Proof.
False comfort from composite scores — an average total hiding a critical cluster failure that is about to produce a refund spike or support collapse.
Action obligation
Every dimension scoring 1 or 2 is a mandatory intervention. A dimension can score 1 for one month before a targeted intervention is documented and deployed. It cannot score 1 for two consecutive months with no action taken.
Passive monitoring — scoring problems and doing nothing, which creates a false sense of measurement without the accountability of action.
The 15 Dimensions: Definitions and Scoring Criteria
The 15 dimensions are organised into five clusters of three dimensions each. Each cluster measures a distinct strategic aspect of the offer. The scoring criteria for each level (1 through 5) are defined specifically enough that two different reviewers applying the criteria to the same offer should produce the same score within one point on any dimension.
The Five Clusters
Cluster
Dimensions
What It Measures
Cluster 1 — Promise
D1 D2 D3
How compelling, clear, and credible is the transformation promise? Directly maps to the top half of Hormozi's Value Equation.
Cluster 2 — Proof
D4 D5 D6
How well is the value justified, risk reduced, and purchase decision de-risked? Kennedy's offer intensification layer.
Cluster 3 — Revenue
D7 D8 D9
How is the offer performing economically — conversion, retention, and margin? The Hormozi unit economics layer.
Cluster 4 — Delivery
D10 D11 D12
How effectively is the offer being fulfilled? Completion, ascension, and support efficiency — the delivery promise layer.
Cluster 5 — Positioning
D13 D14 D15
How sharp is the offer's market positioning? Mechanism strength, copy currency, and GEO/AEO citability.
The Master Scoring Table
Score each dimension using the criteria below. Each cell describes what the offer must demonstrate to earn that score. Use your most recent data — not impressions, not recollections. If you do not have data for a dimension, score it 1 and note the data gap as the action item.
How to run the scorecard — the discipline that makes it reliable
The Scoring Session Structure
The Offer Scorecard is run once per month, on a scheduled date — not when you feel like doing it, not in response to a problem. The first Tuesday of every month is the recommended date (Monday is the Weekly Review; Tuesday gives you the prior week's data as a fresh baseline for scoring). One scorecard per active offer. Budget 40–60 minutes for a single offer; 90 minutes for a portfolio of three or four offers.
The Solo vs Team Scoring Rule
If you have a team, the scorecard should be scored independently by the founder and by one other team member who has direct visibility into the relevant metrics (the ops lead, community manager, or support manager). Scores are compared. Any dimension where the two scores differ by 2 or more points requires a 5-minute evidence-sharing conversation before a final score is agreed. The conversation surface disagreements in perception that are more valuable than the final score itself.
Pre-Scoring Data Pull
Before opening the scorecard, pull the following data. Do not score any dimension without the corresponding data in front of you. If a data point is unavailable, score 1 for that dimension and note 'data gap — cannot score accurately' in the evidence field.
Dimension(s)
Required Data
Where to Pull It
D1 — Dream Outcome Clarity
Last 5 exit interview transcripts. Top 5 PAIN-ACUTE phrases from buyer language mining database. Sales page promise statement verbatim.
Airtable Buyer Language Mining database, exit interview recordings, sales page
D2 — Mechanism Believability
Most recent 10× Test result (date and score). Testimonials citing the mechanism name specifically. Sales call recordings: buyer response when mechanism is named.
Airtable Mechanism Name Records, testimonial registry, sales call recordings
D3 — Speed to First Win
Onboarding survey question: 'What result did you achieve in the first 7 days?' Exit interview transcripts: earliest result mentioned. Completion data: % of buyers completing Module 1 within 72 hours.
Completion rate data for current cohort. Support ticket volume in weeks 1–2 specifically. Percentage of support tickets in first 14 days citing unexpected workload.
Course platform, support help desk, onboarding survey: 'Was the workload what you expected?'
D5 — Offer Stack Strength
Current sales page bonus stack section. Buyer survey: 'Which bonus did you find most valuable? Which was least useful?' Stack slide total stated value.
Sales page, buyer survey data, exit interview Q: 'Which component would you remove?'
D6 — Guarantee Power
Current guarantee language verbatim from sales page. Refund reasons tagged in Airtable — how many cite the guarantee as insufficient or confusing?
Sales page, Airtable Refund Records (root cause codes)
D7 — Social Proof Specificity
Count and type of current testimonials on sales page. Testimonial Version Registry — all version-current testimonials. Proof-to-promise match audit result.
Airtable Testimonial Version Registry, sales page, exit interview recordings
D8 — Cold Conversion Rate
30-day rolling cold conversion rate from GA4 and CRM.
GA4 + CRM (GoHighLevel). Weekly Offer Review Records — last 4 weeks of cold conversion data.
D9 — Refund Rate
Rolling 30-day refund rate from Stripe. Root cause code distribution from Airtable Refund Records.
Stripe, Airtable Refund Records
D10 — Unit Economics
Gross margin calculation: revenue minus all variable delivery costs. CPA from paid ad platforms (if applicable). Total fixed monthly platform costs.
Stripe + delivery cost records. Meta/Google Ads Manager. Margin Stress Test model from Fulfilment Stress Test SOP (if run).
D11 — Completion Rate
Current cohort completion rate from course platform. Trend over last 3 cohorts.
Kajabi or course platform analytics
D12 — Ascension Rate
CRM pipeline: how many buyers moved to a higher tier in the last 60 days. Divided by total buyers who completed the current tier in the same window.
CRM pipeline stage movement report (GoHighLevel or HubSpot)
D13 — Support Efficiency
Average weekly tickets per active buyer. Average first response time from support platform. Most common ticket categories.
Intercom or Help Scout analytics dashboard
D14 — Mechanism Strength
Most recent 10× Test scorecard (all 5 subtest scores). Buyer language adoption rate from last exit interview batch. GEO citation check: mechanism name cited in Perplexity/ChatGPT/Gemini.
Last sales page update date from Product Versioning Changelog. Version drift audit result. Testimonial registry — any version-specific retired testimonials flagged.
Airtable Changelog Entries, Testimonial Version Registry, current sales page vs latest Version Archive snapshot
PHASE 2
The Composite Score and Grade System
From 15 individual scores to a single health grade — and what each grade demands
The Grading Scale
The composite score (sum of all 15 dimension scores, maximum 75) maps to a letter grade. The grade determines the mandatory response protocol. Note: the grade is directional, not absolute — a B-grade offer with all three Revenue cluster dimensions at 2 has a completely different intervention than a B-grade offer where the Revenue cluster is strong but Positioning is weak. The cluster profile analysis in Phase 3 provides the precision the composite score cannot.
A
Score 65–75
Scale-Ready
Every major dimension is operating at strength. No cluster is critically weak. This offer is ready for increased traffic, new affiliate relationships, or an upgraded JV launch.
► Authorise scale event if not already live. Run the 2x Scale Simulation from the Fulfilment Stress Test SOP before increasing buyer volume more than 50%.
► Add one new traffic source this month. This offer can handle the volume.
► Identify the top ascension opportunity: which buyers are closest to upgrading? Run a targeted ascension sequence.
► Begin planning the next value ladder tier — the A-grade offer is generating the proof base needed to launch the next rung.
B
Score 50–64
Viable — Optimise
The offer is working and generating real revenue, but 10–25 points are being left on the table across specific dimensions. No single dimension is catastrophically broken. The B-grade offer is the most common state for a well-managed offer between launch and full optimisation.
► Run the cluster profile analysis (Phase 3) to identify the weakest cluster. That cluster gets the month's intervention focus.
► Select the single lowest-scoring dimension within the weakest cluster as the priority action. Apply the prescribed fix from Phase 5.
► Do not scale until at least two months of B-grade stability are confirmed. An offer with a strong week can score B for one month on momentum, then reveal a structural A or C issue in month 2.
C
Score 35–49
Iterate Before Scaling
The offer has real structural weaknesses. One or more clusters is scoring below its viable threshold. Scaling would amplify the problems faster than it would generate revenue. This offer needs targeted intervention before any meaningful traffic increase.
► Do not scale paid traffic. Do not launch this offer to a new JV partner's audience. Fix first.
► Identify every dimension scoring 1 or 2. Each is a mandatory intervention this month.
► Run the Pre-Kill Diagnostic from the Product Kill Criteria SOP to confirm this is a fixable state and not a structural kill.
► Re-score in 30 days after interventions. If still below 50 after targeted fixes — escalate to Kill Assessment.
D
Score 20–34
Major Intervention Required
Multiple dimensions are critically weak. The offer is generating revenue (if it is at this score) despite significant structural problems that will compound. This grade often precedes a refund rate spike or support collapse.
At D grade: run the full Kill Assessment Scorecard from the Product Kill Criteria SOP immediately. The Kill Assessment Scorecard for the Kill Criteria SOP uses a different scale (0–60, 15 dimensions, 0–4 per dimension) specifically designed for kill/iterate/scale decisions. The Offer Scorecard here (1–5 per dimension, 75 max) is designed for monthly health monitoring. A D grade here does not automatically mean kill — it means the Kill Assessment must be run.
F
Score Below 20
Kill Assessment Triggered
Below 20 points means the offer is failing on most dimensions simultaneously. Continued operation is costing money, reputation, and buyer trust at a rate that is not recoverable through incremental fixes. Run the Kill Assessment Scorecard from the Product Kill Criteria SOP this week.
► Pause all paid advertising immediately.
► Do not accept new buyers until the Kill Assessment produces a clear decision.
► Run the Kill Assessment Scorecard (Product Kill Criteria SOP, Phase 3) within 7 days.
► If Kill Assessment produces a Kill or Pivot outcome — follow the Clean Kill Process (Phase 5 of Kill Criteria SOP).
PHASE 3
The Cluster Profile Analysis
The composite score tells you how healthy. The profile tells you WHY.
The Five Cluster Scores
After calculating the composite score, calculate the five cluster scores by summing the three dimension scores within each cluster. Each cluster has a maximum of 15 points (3 dimensions × 5 each). The cluster profile reveals the offer's structural character — where it is fundamentally strong and where it is structurally weak.
Cluster
Max Score
Score Interpretation
Cluster 1 — Promise (D1+D2+D3)
Max: 15
13–15: Promise is a competitive advantage. 9–12: Promise is viable, improvement opportunities. 5–8: Promise is underpowered — buyers can't feel the transformation before they buy. Below 5: Critical — the promise is repelling or confusing buyers.
Cluster 2 — Proof (D4+D5+D6)
Max: 15
13–15: Proof layer creates instant conviction. 9–12: Proof is present but not maximally persuasive. 5–8: Proof is thin — buyers are taking a faith-based purchase. Below 5: Critical — buyers have no reason to believe the promise.
Cluster 3 — Revenue (D7+D8+D9)
Max: 15
13–15: Offer is economically healthy — scale with confidence. 9–12: Viable economics, optimisation available. 5–8: Economics are marginal — find and fix the leak before scaling. Below 5: Critical — this offer is losing money or destroying reputation.
Cluster 4 — Delivery (D10+D11+D12)
Max: 15
13–15: Delivery is producing results at scale. 9–12: Delivery is adequate, completion and ascension improvements available. 5–8: Delivery is underserving buyers — results are inconsistent. Below 5: Critical — buyers are not getting what they paid for.
Cluster 5 — Positioning (D13+D14+D15)
Max: 15
13–15: Positioning is a market differentiator. 9–12: Positioning is adequate, mechanism freshness opportunity. 5–8: Positioning is eroding — the offer is blending into the category. Below 5: Critical — the offer looks like every competitor's offer.
The Fourteen Diagnostic Profiles
Every offer with a B or C grade has a dominant profile — a pattern in which specific clusters are strong and which are weak. Each profile has a distinct commercial signature and a distinct prescribed intervention sequence. Identify your offer's profile by finding which cluster(s) score in the 5–8 range (weak) or below 5 (critical).
Profile Name
Cluster Pattern
Commercial Signature
Primary Intervention
The Strong Promise, Weak Proof
Cluster 1 (Promise): 11+. Cluster 2 (Proof): 5–8.
Offer attracts attention and interest but buyers hesitate at the decision point. High opt-in rates but low conversion. Buyers 'like the idea' but don't commit.
Immediate: upgrade guarantee (D6) and build proof library (D7). The promise is working — the buyer just needs risk removal before buying.
The Proven Offer, Broken Delivery
Clusters 1,2,3 high. Cluster 4 (Delivery): 5–8.
Offer converts well and generates revenue, but buyers are not getting consistent results. Refunds are low because the copy is strong enough to manage expectations, but completion is low and ascension is stalling.
Run Fulfilment Stress Test SOP. Check Completion Rate (D11) and Support Efficiency (D13) specifically. The funnel works — the programme does not.
Existing buyers love the programme and get results (high completion, low refunds), but cold conversion is low and the economics are struggling. Strong word-of-mouth but weak top-of-funnel.
Focus on D8 (Cold Conversion Rate) and D2 (Mechanism Believability). The delivery is the proof — extract it into better testimonials and a more compelling mechanism. Run the 10× Mechanism Test.
Offer is functionally healthy but competitively invisible. The market can't differentiate it from alternatives. Growing slowly because it blends into the category.
Run the 10× Mechanism Test (D14) immediately. Update copy with buyer language mining data (D15). The offer is good — nobody knows why it's different.
Offer converts and buyers get results, but the margin is being eroded by high support costs, high CPA, or miscalculated delivery costs. The business is working hard for thin returns.
Run the Margin Stress Test (Fulfilment Stress Test SOP Phase 4). Find where the cost is leaking: support hours, tool costs, CPA, or revision cycles.
PHASE 4
The Prescribed Action Protocol
Mandatory actions triggered by each scoring level — removing ambiguity from the response
The Action Obligation Framework
The Offer Scorecard has no spectator mode. Every dimension scoring 1 or 2 triggers a mandatory action within the current month. The action is not 'monitor this.' It is a specific intervention defined in the relevant SOP. The table below maps each scoring level to the action obligation and the SOP it connects to.
Dimension Score
Action Obligation
Who Assigns
Deadline
5 — Excellent
No action required. Note the strength as a potential copy asset or testimonial angle.
N/A
N/A
4 — Strong
Monitor. If score does not improve to 5 within 3 months, identify the specific gap and assign a targeted action.
Owner logs in scorecard record
Within 90 days
3 — Adequate
Identify the specific gap between current performance and the level-4 criteria. Assign a targeted action for the current or next month.
Owner logs in scorecard record + Weekly Review
Within 30 days
2 — Weak
Mandatory targeted action within the current month. Document specific action in scorecard record using the Action Definition Format from the Weekly Review SOP. Report progress in next month's scorecard.
Founder or ops lead must own directly
Within 30 days — report in next scorecard
1 — Critical
Immediate escalation. This dimension is triggering or approaching a Hard Kill threshold. Run the relevant diagnostic SOP this week. This cannot wait for the next monthly review.
Founder owns directly — not delegated
Within 7 days of scorecard completion
Dimension-Specific Action Prescriptions
When a dimension scores 1 or 2, use this table to identify the prescribed intervention. The prescription is the starting action — it may lead to a deeper SOP session, but it provides a clear first step regardless.
Dimension
Score 1 or 2 — Prescribed Intervention
Connecting SOP
D1 — Dream Outcome Clarity
Rewrite the sales page promise section using the top 5 PAIN-ACUTE phrases from the buyer language mining database. Add a specific metric and timeframe to the headline promise. Test against prior version.
Post-MVO Forensic Audit Loop (Phase 3 — Buyer Language Mining)
D2 — Mechanism Believability
Run the full 10× Mechanism Test Protocol with 5 avatar-matched testers. If test score below 7.0: initiate the Rename Cadence (Phase 3 — Name Generation System).
10× Mechanism Test & Rename Cadence SOP
D3 — Speed to First Win
Audit Module 1 delivery. Design a specific Quick Win deliverable that the buyer can achieve within 72 hours. The Quick Win must produce a visible, shareable output. Deploy in the next cohort.
Fulfilment Stress Test SOP (Phase 3 — Delivery Architecture Map)
D4 — Effort Alignment
Add an explicit effort statement to the sales page ('This programme requires X hours per week for Y weeks'). Add the corresponding 'Not for you if you cannot commit X hours' bullet to the 'Not for you' section. Monitor dropout rate for improvement.
Apply Hormozi's Trim & Stack: list every sub-problem on the path to the core promise. Trim high-cost/low-value bonuses. Add 1–2 low-cost/high-value bonuses specifically solving named sub-problems. Rebuild the Stack Slide.
Review the five guarantee levels in MVO Playbook Phase 4. Move one level up from the current guarantee. Rewrite the guarantee section using Kennedy's 'bold enough to feel uncomfortable' standard.
MVO Playbook V5 (Phase 4 — Guarantee Engineering)
D7 — Social Proof Specificity
Run the Proof Harvesting Protocol from the Beta Testing Methodology SOP. Conduct exit interviews specifically requesting proof-matched testimonials. Retire any generic testimonials from the sales page.
Run the Pre-Kill Diagnostic from the Kill Criteria SOP before changing anything. Ensure all six diagnostic fixes have been applied. If diagnostic is clean: run Forensic Audit Loop Phase 4 (Conversion Funnel Diagnostic).
Process all refunds through the 5-step Refund Forensics Protocol. Identify root cause codes. If 3+ refunds share the same RC code: create or update a Negative Avatar Profile.
Run the Margin Stress Test from the Fulfilment Stress Test SOP (Phase 4). Identify the specific cost leaking the margin. If CPA is the problem: pause the worst-performing ad set before any other change.
Fulfilment Stress Test SOP (Phase 4 — Margin Stress Test)
D11 — Completion Rate
Audit the module or week where dropout is highest. Add an accountability check-in and a Quick Win for that specific point. Run the Time-and-Motion Audit (Fulfilment Stress Test Phase 3) to check whether capacity is limiting delivery quality.
Fulfilment Stress Test SOP (Phase 3 — Time-and-Motion Audit)
D12 — Ascension Rate
Verify the ascension email sequence is active in the CRM. Check trigger conditions — is it firing at the right moment? Rewrite Days 14 and 21 post-purchase emails to present the next tier offer at the buyer's win moment.
Post-MVO Forensic Audit Loop (Phase 6 — Next Problem Signal)
D13 — Support Efficiency
Identify the top 3 support ticket topics from the past 30 days. Build one self-serve FAQ or walkthrough video for each. Add to the onboarding sequence. Track whether tickets on those topics decline within 30 days.
Fulfilment Stress Test SOP (Phase 6 — Support Load Projection)
D14 — Mechanism Strength
Run the 10× Mechanism Test immediately. If no test has been run in 90+ days: Health Indicator HI-2 (no AI citation) or HI-4 (competitor adoption) may also be triggering. Run all five health indicator checks.
10× Mechanism Test & Rename Cadence SOP (Phase 2)
D15 — Copy Currency
Run the Copy & Asset Synchronisation Checklist from the Product Versioning SOP. If version drift is confirmed: trigger a Minor version update (CAT-C) and complete the 40-item sync checklist within 14 days.
Month-over-month scoring that reveals whether the offer is improving or declining
The Trend Tracking Principle
A single scorecard tells you the offer's current health. A sequence of scorecards tells you the offer's trajectory. An offer scoring 52 for three consecutive months is in a different operational state from an offer that scored 44, then 48, then 52. The first needs optimisation. The second is under active improvement and the trend should be allowed to continue before escalating.
The Month-over-Month Comparison View
Maintain this tracking record in Airtable. Update it after each monthly scorecard session.
Field
Month 1
Month 2
Month 3
Month 4
Trend
Composite Score
↑ / → / ↓
Grade
Cluster 1 — Promise
↑ / → / ↓
Cluster 2 — Proof
↑ / → / ↓
Cluster 3 — Revenue
↑ / → / ↓
Cluster 4 — Delivery
↑ / → / ↓
Cluster 5 — Positioning
↑ / → / ↓
Lowest-scoring dimension
Dimensions at 1 (count)
Dimensions at 2 (count)
Priority action this month
The Trend Interpretation Rules
Trend Pattern
Interpretation
Required Response
Composite score improving 5+ points per month for 2+ months
Active improvement cycle is working. Actions are producing measurable results.
Continue the current intervention approach. Do not change strategy mid-improvement.
Composite score flat (±3 points) for 2+ months
Offer has reached a local optimum. Current interventions are not producing gains.
Identify the single dimension with the lowest absolute score and run a deeper diagnostic on it. Consider whether a mechanism rename or a value ladder review is needed.
Composite score declining 5+ points per month
Offer is deteriorating despite or without intervention. An undiagnosed structural problem is worsening.
Escalate to Forensic Audit Loop immediately regardless of which specific trigger threshold has been crossed. Something is breaking that the monthly scorecard cannot see at this resolution.
One cluster score declining while others improve
A specific area of the offer is degrading even as the rest improves. Often indicates a delivery capacity problem (Cluster 4 declining as buyer volume grows) or a positioning erosion (Cluster 5 declining as market language shifts).
Run the cluster-specific diagnostic SOP for the declining cluster. Do not let one cluster drag the composite score into a lower grade.
All dimensions at 3 or above, but composite score stuck at B
The offer has no critical weaknesses but also no competitive strengths. Everything is adequate; nothing is excellent.
Identify the two dimensions closest to 4 and invest specifically in pushing them to 5. A B-grade offer with two 5-scoring dimensions has competitive differentiation. A B-grade offer with all 3s is a commodity.
PHASE 6
The Scorecard Record and Airtable Schema
Storing every scorecard permanently — building the institutional memory
The Offer Scorecard Record
One record per scorecard session per offer. All 15 dimension scores, cluster scores, composite score, grade, profile, and mandatory actions are stored in this record. The record links to every SOP it triggers, creating a traceable chain from observation to action to outcome.
Data sources used for each score. Note any data gaps.
Mandatory Actions (score 1 or 2)
Long text
Action Definition Format for each dimension at 1 or 2
Triggered SOPs
Multiple select
Which SOPs have been triggered by this scorecard session
SOP Sessions Scheduled
Long text
Date and time blocks for each triggered SOP session
Prior Month Score
Link → Scorecard Records (self)
Link to same offer's prior month scorecard for trend view
Score Delta vs Prior Month
Formula
Composite Score minus Prior Month Composite Score
Worked Example: A Completed Offer Scorecard
The following example shows a completed scorecard for a fictional mid-tier offer at 90 days post-launch, with annotations explaining the scoring decisions and the prescribed response.
Dimension
Score
Evidence Used
Scoring Rationale
D1 — Dream Outcome Clarity
3
Exit interviews: buyers describe 'growing my audience' but rarely cite specific numbers. Sales page promise: 'Build a content engine that attracts clients.' PAIN-ACUTE top phrase: 'I post constantly but nobody buys.'
Direction is clear (content engine, client attraction) but no specific metric or timeframe on the sales page. Buyers understand the category but not the specific deliverable. Score: 3 (Adequate — specific in direction, missing metrics).
D2 — Mechanism Believability
3
10× Test run 6 weeks ago: average score 6.8. Buyers in exit interviews describe 'the content system' without naming the mechanism. 2 of 12 recent buyers cited the mechanism by name on sales call recordings.
Below the 7.0 threshold for score 4. Buyer adoption below 50%. Mechanism exists and is named but not yet landing with urgency. Score: 3.
D3 — Speed to First Win
4
Onboarding survey Q: 'What result in first 7 days?' — 11/15 respondents cited the Hook Engineering Quick Win as their first result within 72 hours. Completion data: 74% complete Module 1 within 48 hours.
Strong Quick Win in place. 74% within 48 hours exceeds the 4-score threshold. Minor gap: 26% don't complete in first 48 hours. Score: 4.
D4 — Effort Alignment
3
Support tickets weeks 1–2: 18% cite 'more work than expected.' Completion rate: 52%. Exit interview: 3 of 10 mention workload surprise in week 2 specifically.
52% completion is adequate (score 3 threshold). Effort statement on sales page is present but vague ('Invest 3–5 hours per week'). Some surprise around week 2 workload. Score: 3.
D5 — Offer Stack Strength
4
Stack Slide total stated value: $2,847 for a $497 offer (5.7× ratio). Buyer survey: 4 of 5 bonuses rated 7+ usefulness. One bonus rated 4.2 (Hook Swipe File V1 — dated).
Stack is compelling and specific. The dated Hook Swipe File is the gap keeping this from a 5. Score: 4.
D6 — Guarantee Power
3
Current guarantee: 30-day money-back, no conditions, no questions. Refund data: 6% of buyers refund between day 15–29. No clear pattern suggesting the guarantee language is the driver.
Level 1 guarantee. Functional but not differentiated. No result-based language. Score: 3.
D7 — Social Proof Specificity
3
Sales page: 8 testimonials total. 3 contain specific metrics ('47 leads in 30 days,' '3 booked calls in week 1'). 5 are directional without numbers. No video testimonials.
Has the quantity (8) and some specificity (3 with metrics) for a score of 3. Needs 2 more metric-specific testimonials and at least 1 video to reach score 4. Score: 3.
D8 — Cold Conversion Rate
3
GA4 + CRM: Rolling 30-day cold conversion: 1.4%. Trend: 1.3% → 1.4% → 1.4% for 3 consecutive months (stable).
In the 1.0–1.9% range = score 3 (viable minimum). Stable but not improving. Consistent with a B-grade offer at 90 days post-launch. Score: 3.
D9 — Refund Rate
4
Stripe rolling 30-day refund rate: 3.8%. Root cause codes: RC-3 (Expectation Gap — Timing) accounts for 60% of refunds.
3.8% is in the 2–4% band for score 4. RC-3 pattern is a signal (speed-to-result expectation gap), but the overall rate is healthy. Score: 4.
D10 — Unit Economics
3
Gross margin: 47% (revenue minus delivery costs). CPA via Meta ads: $142 for a $497 offer = 28.6% of offer price.
Course platform: 52% complete the full 4-week programme. Prior cohort: 49%. Stable at low-adequate range.
52% is in the 45–59% band for score 3. Two consecutive cohorts in the same band = structural issue, not random variation. Score: 3. FLAGGED for action.
D12 — Ascension Rate
2
CRM pipeline: 4 of 87 cohort completers (4.6%) have moved to the Core Offer within 60 days. Ascension email sequence confirmed active. Trigger point: Day 21 post-purchase.
4.6% is in the 3–5% band for score 2 (Weak). Ascension sequence is live but timing or positioning may be wrong. Score: 2. MANDATORY ACTION.
D13 — Support Efficiency
4
Intercom: average 1.4 tickets per active buyer per week. Average first response: 5.2 hours. Top ticket topics: 'Zoom link not working' and 'Can't find replay.'
1.4 tickets = score 4 (1–2 per buyer per week). Response time 5.2 hours = borderline 4/3. Top topics are technical, not content confusion — FAQ fix available. Score: 4.
D14 — Mechanism Strength
3
10× Test: T-1 average 6.8. T-5 Distinctiveness: 4/5 (strong). Buyer adoption rate: 38% use the name in exit interviews. AI citation check: 2 of 10 queries cite the mechanism.
6.8 is in the 6.0–6.9 band for score 3. 38% adoption is below 50%. Some AI citation but not dominant. Score: 3.
D15 — Copy Currency
4
Last sales page update: 47 days ago. Minor language gap: buyer mining phrase 'I post constantly but nobody buys' not yet in copy. No version drift. All testimonials version-current.
Updated within 180 days = score 4. Minor language gap is an improvement opportunity, not a problem. Score: 4.
D10(3)+D11(3)+D12(2) = 8 / 15. WEAK. D12 (Ascension Rate) is the critical gap. Delivery is working but buyers are not moving up.
Cluster 5 — Positioning
D13(4)+D14(3)+D15(4) = 11 / 15. Adequate-to-strong. Mechanism freshness is the gap.
Profile
The Delivering, Not Converting — Cluster 4 is lowest; the delivery is working but the ascension is stalling.
Mandatory Actions (D12 = score 2)
Rewrite ascension sequence Days 14 and 21. Change trigger: present Core Offer at the buyer's first measurable win (typically Day 12 based on onboarding data) rather than Day 21 calendar. Run ascension A/B test for 60 days.
Triggered SOP
Post-MVO Forensic Audit Loop — Phase 6 (Next Problem Signal). Schedule 45-minute session to audit the ascension sequence copy and trigger logic.
Master Offer Scorecard Checklist
System Setup (One-Time)
☐ Create Offer Scorecard Records table in Airtable with all 33 fields from the schema above
☐ Set up formula fields for composite score, grade, and cluster scores — auto-calculating from dimension input
☐ Run baseline scorecard for every active offer to establish Month 1 reference scores
☐ Set recurring calendar block: first Tuesday of every month — Offer Scorecard Session (40–60 min per offer)
☐ Add formula field: Score Delta vs Prior Month — requires linking to prior month record
Every Monthly Scorecard Session
☐ Pull all required data for each dimension before opening the scorecard template
☐ Score all 15 dimensions using evidence — not gut feel
☐ Calculate composite score and grade
☐ Calculate five cluster scores and identify the weakest cluster
☐ Identify the diagnostic profile from the 14 profiles table
☐ For every dimension scoring 1: schedule the prescribed intervention SOP session within 7 days
☐ For every dimension scoring 2: document the specific action using the Action Definition Format from the Weekly Review SOP
☐ Log all triggered SOPs and block calendar time for each session before closing the scorecard
☐ Complete Offer Scorecard Record in Airtable — all 33 fields
☐ Update the Month-over-Month Comparison View — add this month's scores and calculate trend
After the Scorecard Session
☐ Execute all mandatory actions (dimensions scoring 1 or 2) within the documented deadlines
☐ Report action outcomes in next month's scorecard record under the Evidence Notes field
☐ If grade drops from B to C month-over-month: run Pre-Kill Diagnostic (Kill Criteria SOP) before next Monthly Review
☐ If composite score is declining for 2 consecutive months: escalate to Forensic Audit Loop immediately
☐ If all five clusters score 9–11 (all-adequate, nothing excellent): plan two specific dimensions to push from 3 to 5 over the next 90 days
RISER Nation Master Operating System | Offer Scorecard SOP | Version 1.0 | 2026 Edition
Kennedy × Hormozi × Brunson | risernation.com
word/header1.xml
RISER Nation | Offer Scorecard SOP | V1.0
word/footer1.xml
Page PAGE of NUMPAGES
word/footnotes.xml
word/endnotes.xml
word/comments.xml
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — OFFER SCORECARD ",
"",
"The 15-Dimension Monthly Diagnostic That Tells You Exactly Where Every Offer Is Strong and Where It Is Bleeding",
"Kennedy × Hormozi × Brunson × 2026 Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"The Offer Scorecard is the monthly multi-dimensional health check that every active offer must pass through. It is not the real-time monitoring of the Weekly Offer Review, which scans seven metrics in 20 minutes and produces one action. It is not the deep event-triggered investigation of the Forensic Audit Loop. It is the structured evaluation instrument — the systematic, evidence-based assessment of an offer across all 15 dimensions that determine whether it is healthy, where it is weak, and what the precise intervention should be.",
"",
"Most operators evaluate their offers on one or two dimensions — usually conversion rate and revenue. An offer can have a good conversion rate and still have a critical proof problem, a broken ascension sequence, a degraded mechanism name, and copy so out of date that it no longer mirrors buyer language. None of those problems appear in a conversion-rate check. They appear here.",
"",
"This SOP defines the 15 scoring dimensions across five strategic clusters, the scoring criteria at each of the five levels for every dimension, the composite score and grade interpretation, the cluster profile analysis that reveals the offer's structural character, the prescribed actions by grade and profile, and the trend-tracking system that shows whether each offer is improving or declining over time.",
"",
"The Scorecard's Position in the SOP Ecosystem",
"The Offer Scorecard sits between the Weekly Offer Review (surveillance) and the Forensic Audit Loop (investigation). It is run monthly — regardless of what the weekly review shows — and its output directly informs the Kill Criteria SOP's kill assessment, the 10× Mechanism Test, the Copy & Asset Sync from the Versioning SOP, and the Negative Avatar Modelling SOP's profile update cadence.",
"",
"Scorecard Design Principles",
"Five design principles govern this scorecard. They are not preferences — they are constraints that make the instrument reliable.",
"",
"Principle",
"Statement",
"What It Prevents",
"Evidence-only scoring",
"Every dimension score must be supported by specific data or observations. Gut feel is not evidence. 'I think the mechanism is strong' is not a score. '10× Test scored 7.6 on [date]' is a score.",
"Optimism bias — the tendency to score your own offer higher than the data justifies because you are emotionally invested in it.",
"Dimension independence",
"Each dimension is scored on its own merits, not influenced by other dimensions. A high conversion rate does not increase the mechanism score. A low refund rate does not raise the completion rate score.",
"Halo effect — the tendency to rate all dimensions of a successful-feeling offer higher than they deserve.",
"Consistency over time",
"The same scoring criteria are applied to the same offer every month. Criteria do not change to make an underperforming offer look better. If the criteria were wrong, update them in the SOP and re-score all prior records.",
"Criterion drift — changing the definition of a score level to accommodate a declining offer rather than acknowledging the decline.",
"Cluster awareness",
"The composite score is a starting point. The cluster profile — which five dimensions cluster strong and which cluster weak — is more actionable than the total. A score of 50 with all 10 points missing from Delivery tells you something completely different from a score of 50 with all 10 points missing from Proof.",
"False comfort from composite scores — an average total hiding a critical cluster failure that is about to produce a refund spike or support collapse.",
"Action obligation",
"Every dimension scoring 1 or 2 is a mandatory intervention. A dimension can score 1 for one month before a targeted intervention is documented and deployed. It cannot score 1 for two consecutive months with no action taken.",
"Passive monitoring — scoring problems and doing nothing, which creates a false sense of measurement without the accountability of action.",
"",
"",
"The 15 Dimensions: Definitions and Scoring Criteria",
"The 15 dimensions are organised into five clusters of three dimensions each. Each cluster measures a distinct strategic aspect of the offer. The scoring criteria for each level (1 through 5) are defined specifically enough that two different reviewers applying the criteria to the same offer should produce the same score within one point on any dimension.",
"",
"The Five Clusters",
"Cluster",
"Dimensions",
"What It Measures",
"Cluster 1 — Promise",
"D1 D2 D3",
"How compelling, clear, and credible is the transformation promise? Directly maps to the top half of Hormozi's Value Equation.",
"Cluster 2 — Proof",
"D4 D5 D6",
"How well is the value justified, risk reduced, and purchase decision de-risked? Kennedy's offer intensification layer.",
"Cluster 3 — Revenue",
"D7 D8 D9",
"How is the offer performing economically — conversion, retention, and margin? The Hormozi unit economics layer.",
"Cluster 4 — Delivery",
"D10 D11 D12",
"How effectively is the offer being fulfilled? Completion, ascension, and support efficiency — the delivery promise layer.",
"Cluster 5 — Positioning",
"D13 D14 D15",
"How sharp is the offer's market positioning? Mechanism strength, copy currency, and GEO/AEO citability.",
"",
"The Master Scoring Table",
"Score each dimension using the criteria below. Each cell describes what the offer must demonstrate to earn that score. Use your most recent data — not impressions, not recollections. If you do not have data for a dimension, score it 1 and note the data gap as the action item.",
"",
"#",
"Dimension",
"What It Measures",
"1\nCritical",
"2\nWeak",
"3\nAdequate",
"4\nStrong",
"5\nExcellent",
"Score",
"CLUSTER 1 — PROMISE: Dream Outcome × Perceived Likelihood",
"",
"",
"",
"",
"",
"",
"",
"",
"D1",
"Dream Outcome Clarity",
"Can buyers describe the specific result in numbers and timeframe before purchase?",
"Vague, generic, or misleading relative to what is delivered",
"Clear direction but no metrics or timeframe",
"Specific in direction; metrics OR timeframe present",
"Specific with both metrics AND timeframe; mirrors buyer language closely",
"Buyer can state the exact result before purchasing; copy uses verbatim buyer language; promise matches delivery exactly",
"___",
"D2",
"Mechanism Believability",
"Do buyers believe THIS method will work for THEM specifically?",
"No named mechanism; generic category claim; no proof matching promise",
"Mechanism exists but unnamed or described generically; weak or generic proof",
"Named mechanism; some proof present but not matched to exact promise",
"10× Test score 7.0+; proof present and mostly matched to promise",
"10× Test score 7.5+; buyers cite mechanism as purchase reason; proof matches exact claim with specific metrics",
"___",
"D3",
"Speed to First Win",
"How fast does the buyer experience the first measurable result?",
"No Quick Win; timeline promise overstates speed vs actual results",
"First result in week 3 or later; no explicit Quick Win",
"Quick Win exists but takes 5–7 days; timeline promise mostly met",
"Quick Win within 48–72 hours; timeline promise consistently delivered",
"Documented first-win in under 72 hours; buyers report results in week 1; completion metrics confirm timeline is real",
"___",
"CLUSTER 2 — PROOF: Offer Stack × Guarantee × Social Proof",
"",
"",
"",
"",
"",
"",
"",
"",
"D4",
"Effort Alignment",
"Does the required effort match buyer expectations at purchase?",
"Major effort mismatch; high dropout due to unexpected workload; completion below 30%",
"Significant mismatch; support tickets frequently cite unexpected workload; completion 30–44%",
"Effort understated or unstated; minor surprises; completion 45–59%",
"Effort clearly stated; minor mismatches; completion 60–74%",
"Effort explicitly stated and matched perfectly; done-with-you elements reduce friction; completion 75%+",
"___",
"D5",
"Offer Stack Strength",
"Does the value stack create the 'so good they feel stupid saying no' reaction?",
"No stack; price unanchored; bonuses absent or incoherent",
"Weak stack; total stated value below 5× asking price; bonuses feel generic",
"Adequate stack; 5–6× total value; some bonuses solve specific sub-problems",
"Compelling stack; 7–9× total stated value; all bonuses have specific purpose",
"10× Test equivalent passed by 4/5 avatar testers; 10×+ total value; every bonus solves a named sub-problem",
"___",
"D6",
"Guarantee Power",
"How effectively does the guarantee transfer risk from buyer to seller?",
"No guarantee; or anti-guarantee applied to wrong buyer type; or guarantee language is confusing",
"Short window or hard conditional; high completion burden to qualify",
"Level 1: standard 30-day money-back; no conditions; baseline credibility",
"Level 2–3: conditional result-based; clear completion requirements; believable conditions",
"Level 3–4: result-based or service-based guarantee; Kennedy-standard; bold enough to repel wrong buyers and attract right ones",
"___",
"CLUSTER 3 — REVENUE: Conversion × Refund × Unit Economics",
"",
"",
"",
"",
"",
"",
"",
"",
"D7",
"Social Proof Specificity",
"Does the proof on the sales page match the exact claim?",
"No testimonials; or only unverifiable/implausible claims",
"1–2 testimonials; generic ('great course') type; no metric specificity",
"2–3 testimonials with outcomes described but no specific numbers",
"3–4 specific testimonials with metric alignment; one video testimonial",
"5+ testimonials matching promise with exact metrics and timeframes; at least 2 video testimonials; proof-to-promise match confirmed",
"___",
"D8",
"Cold Conversion Rate",
"What % of unique cold visitors purchase?",
"Below 0.5%",
"0.5–0.9%",
"1.0–1.9% (viable minimum)",
"2.0–3.9%",
"4.0%+ (scale signal)",
"___",
"D9",
"Refund Rate",
"What % of buyers request a refund (rolling 30 days)?",
"Above 15%",
"8–14%",
"5–7%",
"2–4%",
"Below 2%",
"___",
"CLUSTER 4 — DELIVERY: Completion × Ascension × Support",
"",
"",
"",
"",
"",
"",
"",
"",
"D10",
"Unit Economics",
"Is the margin and CPA sustainable for the offer's price point?",
"Gross margin below 25%; or CPA above 50% of offer price",
"Gross margin 25–39%; CPA 33–49%",
"Gross margin 40–54%; CPA 25–32%",
"Gross margin 55–69%; CPA 15–24%",
"Gross margin 70%+; CPA below 15% of offer price",
"___",
"D11",
"Completion Rate",
"What % of buyers complete the full programme or core deliverable?",
"Below 30%",
"30–44%",
"45–59%",
"60–74%",
"75%+",
"___",
"D12",
"Ascension Rate",
"What % of buyers move to the next value ladder tier within 60 days?",
"Below 3%; or ascension sequence not yet built",
"3–5%",
"6–9%",
"10–14%",
"15%+ with documented ascension sequence; buyers cite prior tier result as reason for upgrading",
"___",
"CLUSTER 5 — POSITIONING: Mechanism × Copy × GEO Citability",
"",
"",
"",
"",
"",
"",
"",
"",
"D13",
"Support Efficiency",
"How much support time does this offer consume per buyer?",
"Above 5 support tickets per buyer per week; or resolution above 48 hours regularly",
"3–5 tickets per buyer per week; resolution over 24 hours often",
"2–3 tickets per buyer per week; resolution under 24 hours",
"1–2 tickets per buyer per week; resolution under 8 hours",
"Below 1 ticket per buyer per week; average resolution under 4 hours; self-serve FAQ handles majority of common questions",
"___",
"D14",
"Mechanism Strength",
"How strong is the named proprietary method?",
"No named mechanism; generic description only",
"Mechanism exists but 10× Test not run or scores below 6.0",
"10× Test score 6.0–6.9; buyer adoption below 50%",
"10× Test score 7.0–7.4; buyer adoption 50–69%",
"10× Test score 7.5+; buyer adoption above 70%; AI engines cite mechanism name",
"___",
"D15",
"Copy Currency",
"How current is the sales copy relative to buyer language data?",
"Version drift confirmed — sales page promises what current offer doesn't deliver; retired components referenced",
"Not updated in 12+ months; significant gap between copy language and buyer mining data",
"Updated 6–12 months ago; some language dated; minor gaps",
"Updated within 180 days; minor language improvements available; all testimonials version-current",
"Updated within 90 days using buyer language mining data; copy mirrors buyer phrases; no version drift; all assets version-current",
"___",
"COMPOSITE SCORE (add all 15 dimension scores)",
"Maximum: 75 points (15 dimensions × 5 points each)",
"___",
"",
"",
"PHASE 1",
"The Scoring Protocol",
"How to run the scorecard — the discipline that makes it reliable",
"",
"The Scoring Session Structure",
"The Offer Scorecard is run once per month, on a scheduled date — not when you feel like doing it, not in response to a problem. The first Tuesday of every month is the recommended date (Monday is the Weekly Review; Tuesday gives you the prior week's data as a fresh baseline for scoring). One scorecard per active offer. Budget 40–60 minutes for a single offer; 90 minutes for a portfolio of three or four offers.",
"",
"The Solo vs Team Scoring Rule",
"If you have a team, the scorecard should be scored independently by the founder and by one other team member who has direct visibility into the relevant metrics (the ops lead, community manager, or support manager). Scores are compared. Any dimension where the two scores differ by 2 or more points requires a 5-minute evidence-sharing conversation before a final score is agreed. The conversation surface disagreements in perception that are more valuable than the final score itself.",
"",
"Pre-Scoring Data Pull",
"Before opening the scorecard, pull the following data. Do not score any dimension without the corresponding data in front of you. If a data point is unavailable, score 1 for that dimension and note 'data gap — cannot score accurately' in the evidence field.",
"",
"Dimension(s)",
"Required Data",
"Where to Pull It",
"D1 — Dream Outcome Clarity",
"Last 5 exit interview transcripts. Top 5 PAIN-ACUTE phrases from buyer language mining database. Sales page promise statement verbatim.",
"Airtable Buyer Language Mining database, exit interview recordings, sales page",
"D2 — Mechanism Believability",
"Most recent 10× Test result (date and score). Testimonials citing the mechanism name specifically. Sales call recordings: buyer response when mechanism is named.",
"Airtable Mechanism Name Records, testimonial registry, sales call recordings",
"D3 — Speed to First Win",
"Onboarding survey question: 'What result did you achieve in the first 7 days?' Exit interview transcripts: earliest result mentioned. Completion data: % of buyers completing Module 1 within 72 hours.",
"Course platform analytics, onboarding survey responses, exit interview transcripts",
"D4 — Effort Alignment",
"Completion rate data for current cohort. Support ticket volume in weeks 1–2 specifically. Percentage of support tickets in first 14 days citing unexpected workload.",
"Course platform, support help desk, onboarding survey: 'Was the workload what you expected?'",
"D5 — Offer Stack Strength",
"Current sales page bonus stack section. Buyer survey: 'Which bonus did you find most valuable? Which was least useful?' Stack slide total stated value.",
"Sales page, buyer survey data, exit interview Q: 'Which component would you remove?'",
"D6 — Guarantee Power",
"Current guarantee language verbatim from sales page. Refund reasons tagged in Airtable — how many cite the guarantee as insufficient or confusing?",
"Sales page, Airtable Refund Records (root cause codes)",
"D7 — Social Proof Specificity",
"Count and type of current testimonials on sales page. Testimonial Version Registry — all version-current testimonials. Proof-to-promise match audit result.",
"Airtable Testimonial Version Registry, sales page, exit interview recordings",
"D8 — Cold Conversion Rate",
"30-day rolling cold conversion rate from GA4 and CRM.",
"GA4 + CRM (GoHighLevel). Weekly Offer Review Records — last 4 weeks of cold conversion data.",
"D9 — Refund Rate",
"Rolling 30-day refund rate from Stripe. Root cause code distribution from Airtable Refund Records.",
"Stripe, Airtable Refund Records",
"D10 — Unit Economics",
"Gross margin calculation: revenue minus all variable delivery costs. CPA from paid ad platforms (if applicable). Total fixed monthly platform costs.",
"Stripe + delivery cost records. Meta/Google Ads Manager. Margin Stress Test model from Fulfilment Stress Test SOP (if run).",
"D11 — Completion Rate",
"Current cohort completion rate from course platform. Trend over last 3 cohorts.",
"Kajabi or course platform analytics",
"D12 — Ascension Rate",
"CRM pipeline: how many buyers moved to a higher tier in the last 60 days. Divided by total buyers who completed the current tier in the same window.",
"CRM pipeline stage movement report (GoHighLevel or HubSpot)",
"D13 — Support Efficiency",
"Average weekly tickets per active buyer. Average first response time from support platform. Most common ticket categories.",
"Intercom or Help Scout analytics dashboard",
"D14 — Mechanism Strength",
"Most recent 10× Test scorecard (all 5 subtest scores). Buyer language adoption rate from last exit interview batch. GEO citation check: mechanism name cited in Perplexity/ChatGPT/Gemini.",
"Airtable Mechanism Name Records, exit interview transcripts, manual GEO citation check",
"D15 — Copy Currency",
"Last sales page update date from Product Versioning Changelog. Version drift audit result. Testimonial registry — any version-specific retired testimonials flagged.",
"Airtable Changelog Entries, Testimonial Version Registry, current sales page vs latest Version Archive snapshot",
"",
"",
"PHASE 2",
"The Composite Score and Grade System",
"From 15 individual scores to a single health grade — and what each grade demands",
"",
"The Grading Scale",
"The composite score (sum of all 15 dimension scores, maximum 75) maps to a letter grade. The grade determines the mandatory response protocol. Note: the grade is directional, not absolute — a B-grade offer with all three Revenue cluster dimensions at 2 has a completely different intervention than a B-grade offer where the Revenue cluster is strong but Positioning is weak. The cluster profile analysis in Phase 3 provides the precision the composite score cannot.",
"",
"A",
"Score 65–75",
"Scale-Ready",
"Every major dimension is operating at strength. No cluster is critically weak. This offer is ready for increased traffic, new affiliate relationships, or an upgraded JV launch.",
"► Authorise scale event if not already live. Run the 2x Scale Simulation from the Fulfilment Stress Test SOP before increasing buyer volume more than 50%.",
"► Add one new traffic source this month. This offer can handle the volume.",
"► Identify the top ascension opportunity: which buyers are closest to upgrading? Run a targeted ascension sequence.",
"► Begin planning the next value ladder tier — the A-grade offer is generating the proof base needed to launch the next rung.",
"",
"B",
"Score 50–64",
"Viable — Optimise",
"The offer is working and generating real revenue, but 10–25 points are being left on the table across specific dimensions. No single dimension is catastrophically broken. The B-grade offer is the most common state for a well-managed offer between launch and full optimisation.",
"► Run the cluster profile analysis (Phase 3) to identify the weakest cluster. That cluster gets the month's intervention focus.",
"► Select the single lowest-scoring dimension within the weakest cluster as the priority action. Apply the prescribed fix from Phase 5.",
"► Do not scale until at least two months of B-grade stability are confirmed. An offer with a strong week can score B for one month on momentum, then reveal a structural A or C issue in month 2.",
"",
"C",
"Score 35–49",
"Iterate Before Scaling",
"The offer has real structural weaknesses. One or more clusters is scoring below its viable threshold. Scaling would amplify the problems faster than it would generate revenue. This offer needs targeted intervention before any meaningful traffic increase.",
"► Do not scale paid traffic. Do not launch this offer to a new JV partner's audience. Fix first.",
"► Identify every dimension scoring 1 or 2. Each is a mandatory intervention this month.",
"► Run the Pre-Kill Diagnostic from the Product Kill Criteria SOP to confirm this is a fixable state and not a structural kill.",
"► Re-score in 30 days after interventions. If still below 50 after targeted fixes — escalate to Kill Assessment.",
"",
"D",
"Score 20–34",
"Major Intervention Required",
"Multiple dimensions are critically weak. The offer is generating revenue (if it is at this score) despite significant structural problems that will compound. This grade often precedes a refund rate spike or support collapse.",
"At D grade: run the full Kill Assessment Scorecard from the Product Kill Criteria SOP immediately. The Kill Assessment Scorecard for the Kill Criteria SOP uses a different scale (0–60, 15 dimensions, 0–4 per dimension) specifically designed for kill/iterate/scale decisions. The Offer Scorecard here (1–5 per dimension, 75 max) is designed for monthly health monitoring. A D grade here does not automatically mean kill — it means the Kill Assessment must be run.",
"",
"F",
"Score Below 20",
"Kill Assessment Triggered",
"Below 20 points means the offer is failing on most dimensions simultaneously. Continued operation is costing money, reputation, and buyer trust at a rate that is not recoverable through incremental fixes. Run the Kill Assessment Scorecard from the Product Kill Criteria SOP this week.",
"► Pause all paid advertising immediately.",
"► Do not accept new buyers until the Kill Assessment produces a clear decision.",
"► Run the Kill Assessment Scorecard (Product Kill Criteria SOP, Phase 3) within 7 days.",
"► If Kill Assessment produces a Kill or Pivot outcome — follow the Clean Kill Process (Phase 5 of Kill Criteria SOP).",
"",
"",
"PHASE 3",
"The Cluster Profile Analysis",
"The composite score tells you how healthy. The profile tells you WHY.",
"",
"The Five Cluster Scores",
"After calculating the composite score, calculate the five cluster scores by summing the three dimension scores within each cluster. Each cluster has a maximum of 15 points (3 dimensions × 5 each). The cluster profile reveals the offer's structural character — where it is fundamentally strong and where it is structurally weak.",
"",
"Cluster",
"Max Score",
"Score Interpretation",
"Cluster 1 — Promise (D1+D2+D3)",
"Max: 15",
"13–15: Promise is a competitive advantage. 9–12: Promise is viable, improvement opportunities. 5–8: Promise is underpowered — buyers can't feel the transformation before they buy. Below 5: Critical — the promise is repelling or confusing buyers.",
"Cluster 2 — Proof (D4+D5+D6)",
"Max: 15",
"13–15: Proof layer creates instant conviction. 9–12: Proof is present but not maximally persuasive. 5–8: Proof is thin — buyers are taking a faith-based purchase. Below 5: Critical — buyers have no reason to believe the promise.",
"Cluster 3 — Revenue (D7+D8+D9)",
"Max: 15",
"13–15: Offer is economically healthy — scale with confidence. 9–12: Viable economics, optimisation available. 5–8: Economics are marginal — find and fix the leak before scaling. Below 5: Critical — this offer is losing money or destroying reputation.",
"Cluster 4 — Delivery (D10+D11+D12)",
"Max: 15",
"13–15: Delivery is producing results at scale. 9–12: Delivery is adequate, completion and ascension improvements available. 5–8: Delivery is underserving buyers — results are inconsistent. Below 5: Critical — buyers are not getting what they paid for.",
"Cluster 5 — Positioning (D13+D14+D15)",
"Max: 15",
"13–15: Positioning is a market differentiator. 9–12: Positioning is adequate, mechanism freshness opportunity. 5–8: Positioning is eroding — the offer is blending into the category. Below 5: Critical — the offer looks like every competitor's offer.",
"",
"The Fourteen Diagnostic Profiles",
"Every offer with a B or C grade has a dominant profile — a pattern in which specific clusters are strong and which are weak. Each profile has a distinct commercial signature and a distinct prescribed intervention sequence. Identify your offer's profile by finding which cluster(s) score in the 5–8 range (weak) or below 5 (critical).",
"",
"Profile Name",
"Cluster Pattern",
"Commercial Signature",
"Primary Intervention",
"The Strong Promise, Weak Proof",
"Cluster 1 (Promise): 11+. Cluster 2 (Proof): 5–8.",
"Offer attracts attention and interest but buyers hesitate at the decision point. High opt-in rates but low conversion. Buyers 'like the idea' but don't commit.",
"Immediate: upgrade guarantee (D6) and build proof library (D7). The promise is working — the buyer just needs risk removal before buying.",
"The Proven Offer, Broken Delivery",
"Clusters 1,2,3 high. Cluster 4 (Delivery): 5–8.",
"Offer converts well and generates revenue, but buyers are not getting consistent results. Refunds are low because the copy is strong enough to manage expectations, but completion is low and ascension is stalling.",
"Run Fulfilment Stress Test SOP. Check Completion Rate (D11) and Support Efficiency (D13) specifically. The funnel works — the programme does not.",
"The Delivering, Not Converting",
"Cluster 4 (Delivery) high. Cluster 3 (Revenue): 5–8.",
"Existing buyers love the programme and get results (high completion, low refunds), but cold conversion is low and the economics are struggling. Strong word-of-mouth but weak top-of-funnel.",
"Focus on D8 (Cold Conversion Rate) and D2 (Mechanism Believability). The delivery is the proof — extract it into better testimonials and a more compelling mechanism. Run the 10× Mechanism Test.",
"The Positioning Problem",
"Clusters 1–4 adequate (all 9–11). Cluster 5 (Positioning): 5–8.",
"Offer is functionally healthy but competitively invisible. The market can't differentiate it from alternatives. Growing slowly because it blends into the category.",
"Run the 10× Mechanism Test (D14) immediately. Update copy with buyer language mining data (D15). The offer is good — nobody knows why it's different.",
"The Economics Leak",
"Clusters 1,2,4,5 adequate. Cluster 3 (Revenue): D10 (Unit Economics) specifically weak.",
"Offer converts and buyers get results, but the margin is being eroded by high support costs, high CPA, or miscalculated delivery costs. The business is working hard for thin returns.",
"Run the Margin Stress Test (Fulfilment Stress Test SOP Phase 4). Find where the cost is leaking: support hours, tool costs, CPA, or revision cycles.",
"",
"",
"PHASE 4",
"The Prescribed Action Protocol",
"Mandatory actions triggered by each scoring level — removing ambiguity from the response",
"",
"The Action Obligation Framework",
"The Offer Scorecard has no spectator mode. Every dimension scoring 1 or 2 triggers a mandatory action within the current month. The action is not 'monitor this.' It is a specific intervention defined in the relevant SOP. The table below maps each scoring level to the action obligation and the SOP it connects to.",
"",
"Dimension Score",
"Action Obligation",
"Who Assigns",
"Deadline",
"5 — Excellent",
"No action required. Note the strength as a potential copy asset or testimonial angle.",
"N/A",
"N/A",
"4 — Strong",
"Monitor. If score does not improve to 5 within 3 months, identify the specific gap and assign a targeted action.",
"Owner logs in scorecard record",
"Within 90 days",
"3 — Adequate",
"Identify the specific gap between current performance and the level-4 criteria. Assign a targeted action for the current or next month.",
"Owner logs in scorecard record + Weekly Review",
"Within 30 days",
"2 — Weak",
"Mandatory targeted action within the current month. Document specific action in scorecard record using the Action Definition Format from the Weekly Review SOP. Report progress in next month's scorecard.",
"Founder or ops lead must own directly",
"Within 30 days — report in next scorecard",
"1 — Critical",
"Immediate escalation. This dimension is triggering or approaching a Hard Kill threshold. Run the relevant diagnostic SOP this week. This cannot wait for the next monthly review.",
"Founder owns directly — not delegated",
"Within 7 days of scorecard completion",
"",
"Dimension-Specific Action Prescriptions",
"When a dimension scores 1 or 2, use this table to identify the prescribed intervention. The prescription is the starting action — it may lead to a deeper SOP session, but it provides a clear first step regardless.",
"",
"Dimension",
"Score 1 or 2 — Prescribed Intervention",
"Connecting SOP",
"D1 — Dream Outcome Clarity",
"Rewrite the sales page promise section using the top 5 PAIN-ACUTE phrases from the buyer language mining database. Add a specific metric and timeframe to the headline promise. Test against prior version.",
"Post-MVO Forensic Audit Loop (Phase 3 — Buyer Language Mining)",
"D2 — Mechanism Believability",
"Run the full 10× Mechanism Test Protocol with 5 avatar-matched testers. If test score below 7.0: initiate the Rename Cadence (Phase 3 — Name Generation System).",
"10× Mechanism Test & Rename Cadence SOP",
"D3 — Speed to First Win",
"Audit Module 1 delivery. Design a specific Quick Win deliverable that the buyer can achieve within 72 hours. The Quick Win must produce a visible, shareable output. Deploy in the next cohort.",
"Fulfilment Stress Test SOP (Phase 3 — Delivery Architecture Map)",
"D4 — Effort Alignment",
"Add an explicit effort statement to the sales page ('This programme requires X hours per week for Y weeks'). Add the corresponding 'Not for you if you cannot commit X hours' bullet to the 'Not for you' section. Monitor dropout rate for improvement.",
"Negative Avatar Modelling SOP (Phase 4 — Repulsion System)",
"D5 — Offer Stack Strength",
"Apply Hormozi's Trim & Stack: list every sub-problem on the path to the core promise. Trim high-cost/low-value bonuses. Add 1–2 low-cost/high-value bonuses specifically solving named sub-problems. Rebuild the Stack Slide.",
"MVO Playbook V5 (Phase 2 — Offer Construction: Trim & Stack)",
"D6 — Guarantee Power",
"Review the five guarantee levels in MVO Playbook Phase 4. Move one level up from the current guarantee. Rewrite the guarantee section using Kennedy's 'bold enough to feel uncomfortable' standard.",
"MVO Playbook V5 (Phase 4 — Guarantee Engineering)",
"D7 — Social Proof Specificity",
"Run the Proof Harvesting Protocol from the Beta Testing Methodology SOP. Conduct exit interviews specifically requesting proof-matched testimonials. Retire any generic testimonials from the sales page.",
"Beta Testing Methodology SOP (Phase 6 — Proof Harvesting Protocol)",
"D8 — Cold Conversion Rate",
"Run the Pre-Kill Diagnostic from the Kill Criteria SOP before changing anything. Ensure all six diagnostic fixes have been applied. If diagnostic is clean: run Forensic Audit Loop Phase 4 (Conversion Funnel Diagnostic).",
"Product Kill Criteria SOP (Phase 1 — Pre-Kill Diagnostic)",
"D9 — Refund Rate",
"Process all refunds through the 5-step Refund Forensics Protocol. Identify root cause codes. If 3+ refunds share the same RC code: create or update a Negative Avatar Profile.",
"Post-MVO Forensic Audit Loop (Phase 5) + Negative Avatar Modelling SOP",
"D10 — Unit Economics",
"Run the Margin Stress Test from the Fulfilment Stress Test SOP (Phase 4). Identify the specific cost leaking the margin. If CPA is the problem: pause the worst-performing ad set before any other change.",
"Fulfilment Stress Test SOP (Phase 4 — Margin Stress Test)",
"D11 — Completion Rate",
"Audit the module or week where dropout is highest. Add an accountability check-in and a Quick Win for that specific point. Run the Time-and-Motion Audit (Fulfilment Stress Test Phase 3) to check whether capacity is limiting delivery quality.",
"Fulfilment Stress Test SOP (Phase 3 — Time-and-Motion Audit)",
"D12 — Ascension Rate",
"Verify the ascension email sequence is active in the CRM. Check trigger conditions — is it firing at the right moment? Rewrite Days 14 and 21 post-purchase emails to present the next tier offer at the buyer's win moment.",
"Post-MVO Forensic Audit Loop (Phase 6 — Next Problem Signal)",
"D13 — Support Efficiency",
"Identify the top 3 support ticket topics from the past 30 days. Build one self-serve FAQ or walkthrough video for each. Add to the onboarding sequence. Track whether tickets on those topics decline within 30 days.",
"Fulfilment Stress Test SOP (Phase 6 — Support Load Projection)",
"D14 — Mechanism Strength",
"Run the 10× Mechanism Test immediately. If no test has been run in 90+ days: Health Indicator HI-2 (no AI citation) or HI-4 (competitor adoption) may also be triggering. Run all five health indicator checks.",
"10× Mechanism Test & Rename Cadence SOP (Phase 2)",
"D15 — Copy Currency",
"Run the Copy & Asset Synchronisation Checklist from the Product Versioning SOP. If version drift is confirmed: trigger a Minor version update (CAT-C) and complete the 40-item sync checklist within 14 days.",
"Product Versioning & Offer Changelog SOP (Phase 5 — Copy Sync)",
"",
"",
"PHASE 5",
"The Trend Tracking System",
"Month-over-month scoring that reveals whether the offer is improving or declining",
"",
"The Trend Tracking Principle",
"A single scorecard tells you the offer's current health. A sequence of scorecards tells you the offer's trajectory. An offer scoring 52 for three consecutive months is in a different operational state from an offer that scored 44, then 48, then 52. The first needs optimisation. The second is under active improvement and the trend should be allowed to continue before escalating.",
"",
"The Month-over-Month Comparison View",
"Maintain this tracking record in Airtable. Update it after each monthly scorecard session.",
"",
"Field",
"Month 1",
"Month 2",
"Month 3",
"Month 4",
"Trend",
"Composite Score",
"",
"",
"",
"",
"↑ / → / ↓",
"Grade",
"",
"",
"",
"",
"",
"Cluster 1 — Promise",
"",
"",
"",
"",
"↑ / → / ↓",
"Cluster 2 — Proof",
"",
"",
"",
"",
"↑ / → / ↓",
"Cluster 3 — Revenue",
"",
"",
"",
"",
"↑ / → / ↓",
"Cluster 4 — Delivery",
"",
"",
"",
"",
"↑ / → / ↓",
"Cluster 5 — Positioning",
"",
"",
"",
"",
"↑ / → / ↓",
"Lowest-scoring dimension",
"",
"",
"",
"",
"",
"Dimensions at 1 (count)",
"",
"",
"",
"",
"",
"Dimensions at 2 (count)",
"",
"",
"",
"",
"",
"Priority action this month",
"",
"",
"",
"",
"",
"",
"The Trend Interpretation Rules",
"Trend Pattern",
"Interpretation",
"Required Response",
"Composite score improving 5+ points per month for 2+ months",
"Active improvement cycle is working. Actions are producing measurable results.",
"Continue the current intervention approach. Do not change strategy mid-improvement.",
"Composite score flat (±3 points) for 2+ months",
"Offer has reached a local optimum. Current interventions are not producing gains.",
"Identify the single dimension with the lowest absolute score and run a deeper diagnostic on it. Consider whether a mechanism rename or a value ladder review is needed.",
"Composite score declining 5+ points per month",
"Offer is deteriorating despite or without intervention. An undiagnosed structural problem is worsening.",
"Escalate to Forensic Audit Loop immediately regardless of which specific trigger threshold has been crossed. Something is breaking that the monthly scorecard cannot see at this resolution.",
"One cluster score declining while others improve",
"A specific area of the offer is degrading even as the rest improves. Often indicates a delivery capacity problem (Cluster 4 declining as buyer volume grows) or a positioning erosion (Cluster 5 declining as market language shifts).",
"Run the cluster-specific diagnostic SOP for the declining cluster. Do not let one cluster drag the composite score into a lower grade.",
"All dimensions at 3 or above, but composite score stuck at B",
"The offer has no critical weaknesses but also no competitive strengths. Everything is adequate; nothing is excellent.",
"Identify the two dimensions closest to 4 and invest specifically in pushing them to 5. A B-grade offer with two 5-scoring dimensions has competitive differentiation. A B-grade offer with all 3s is a commodity.",
"",
"",
"PHASE 6",
"The Scorecard Record and Airtable Schema",
"Storing every scorecard permanently — building the institutional memory",
"",
"The Offer Scorecard Record",
"One record per scorecard session per offer. All 15 dimension scores, cluster scores, composite score, grade, profile, and mandatory actions are stored in this record. The record links to every SOP it triggers, creating a traceable chain from observation to action to outcome.",
"",
"Field",
"Type",
"Notes",
"Scorecard ID",
"Autonumber",
"Format: OSC-[Offer Code]-[YYYY-MM]",
"Offer",
"Link → Offers table",
"",
"Scoring Date",
"Date",
"The date the scorecard was completed",
"Scored By",
"Short text",
"Name(s) of everyone who scored this session",
"D1 Score — Dream Outcome Clarity",
"Number (1–5)",
"",
"D2 Score — Mechanism Believability",
"Number (1–5)",
"",
"D3 Score — Speed to First Win",
"Number (1–5)",
"",
"D4 Score — Effort Alignment",
"Number (1–5)",
"",
"D5 Score — Offer Stack Strength",
"Number (1–5)",
"",
"D6 Score — Guarantee Power",
"Number (1–5)",
"",
"D7 Score — Social Proof Specificity",
"Number (1–5)",
"",
"D8 Score — Cold Conversion Rate",
"Number (1–5)",
"",
"D9 Score — Refund Rate",
"Number (1–5)",
"",
"D10 Score — Unit Economics",
"Number (1–5)",
"",
"D11 Score — Completion Rate",
"Number (1–5)",
"",
"D12 Score — Ascension Rate",
"Number (1–5)",
"",
"D13 Score — Support Efficiency",
"Number (1–5)",
"",
"D14 Score — Mechanism Strength",
"Number (1–5)",
"",
"D15 Score — Copy Currency",
"Number (1–5)",
"",
"Composite Score",
"Formula",
"Sum of D1 through D15. Auto-calculated.",
"Grade",
"Formula",
"A(65+) / B(50–64) / C(35–49) / D(20–34) / F(<20). Auto-assigned.",
"Cluster 1 Score (Promise)",
"Formula",
"D1+D2+D3",
"Cluster 2 Score (Proof)",
"Formula",
"D4+D5+D6",
"Cluster 3 Score (Revenue)",
"Formula",
"D7+D8+D9",
"Cluster 4 Score (Delivery)",
"Formula",
"D10+D11+D12",
"Cluster 5 Score (Positioning)",
"Formula",
"D13+D14+D15",
"Profile Name",
"Single select",
"Identified from the 14 diagnostic profiles",
"Dimensions Scoring 1 (list)",
"Multiple select",
"All D-codes scoring 1 this month",
"Dimensions Scoring 2 (list)",
"Multiple select",
"All D-codes scoring 2 this month",
"Evidence Notes",
"Long text",
"Data sources used for each score. Note any data gaps.",
"Mandatory Actions (score 1 or 2)",
"Long text",
"Action Definition Format for each dimension at 1 or 2",
"Triggered SOPs",
"Multiple select",
"Which SOPs have been triggered by this scorecard session",
"SOP Sessions Scheduled",
"Long text",
"Date and time blocks for each triggered SOP session",
"Prior Month Score",
"Link → Scorecard Records (self)",
"Link to same offer's prior month scorecard for trend view",
"Score Delta vs Prior Month",
"Formula",
"Composite Score minus Prior Month Composite Score",
"",
"",
"Worked Example: A Completed Offer Scorecard",
"The following example shows a completed scorecard for a fictional mid-tier offer at 90 days post-launch, with annotations explaining the scoring decisions and the prescribed response.",
"",
"Dimension",
"Score",
"Evidence Used",
"Scoring Rationale",
"D1 — Dream Outcome Clarity",
"3",
"Exit interviews: buyers describe 'growing my audience' but rarely cite specific numbers. Sales page promise: 'Build a content engine that attracts clients.' PAIN-ACUTE top phrase: 'I post constantly but nobody buys.'",
"Direction is clear (content engine, client attraction) but no specific metric or timeframe on the sales page. Buyers understand the category but not the specific deliverable. Score: 3 (Adequate — specific in direction, missing metrics).",
"D2 — Mechanism Believability",
"3",
"10× Test run 6 weeks ago: average score 6.8. Buyers in exit interviews describe 'the content system' without naming the mechanism. 2 of 12 recent buyers cited the mechanism by name on sales call recordings.",
"Below the 7.0 threshold for score 4. Buyer adoption below 50%. Mechanism exists and is named but not yet landing with urgency. Score: 3.",
"D3 — Speed to First Win",
"4",
"Onboarding survey Q: 'What result in first 7 days?' — 11/15 respondents cited the Hook Engineering Quick Win as their first result within 72 hours. Completion data: 74% complete Module 1 within 48 hours.",
"Strong Quick Win in place. 74% within 48 hours exceeds the 4-score threshold. Minor gap: 26% don't complete in first 48 hours. Score: 4.",
"D4 — Effort Alignment",
"3",
"Support tickets weeks 1–2: 18% cite 'more work than expected.' Completion rate: 52%. Exit interview: 3 of 10 mention workload surprise in week 2 specifically.",
"52% completion is adequate (score 3 threshold). Effort statement on sales page is present but vague ('Invest 3–5 hours per week'). Some surprise around week 2 workload. Score: 3.",
"D5 — Offer Stack Strength",
"4",
"Stack Slide total stated value: $2,847 for a $497 offer (5.7× ratio). Buyer survey: 4 of 5 bonuses rated 7+ usefulness. One bonus rated 4.2 (Hook Swipe File V1 — dated).",
"Stack is compelling and specific. The dated Hook Swipe File is the gap keeping this from a 5. Score: 4.",
"D6 — Guarantee Power",
"3",
"Current guarantee: 30-day money-back, no conditions, no questions. Refund data: 6% of buyers refund between day 15–29. No clear pattern suggesting the guarantee language is the driver.",
"Level 1 guarantee. Functional but not differentiated. No result-based language. Score: 3.",
"D7 — Social Proof Specificity",
"3",
"Sales page: 8 testimonials total. 3 contain specific metrics ('47 leads in 30 days,' '3 booked calls in week 1'). 5 are directional without numbers. No video testimonials.",
"Has the quantity (8) and some specificity (3 with metrics) for a score of 3. Needs 2 more metric-specific testimonials and at least 1 video to reach score 4. Score: 3.",
"D8 — Cold Conversion Rate",
"3",
"GA4 + CRM: Rolling 30-day cold conversion: 1.4%. Trend: 1.3% → 1.4% → 1.4% for 3 consecutive months (stable).",
"In the 1.0–1.9% range = score 3 (viable minimum). Stable but not improving. Consistent with a B-grade offer at 90 days post-launch. Score: 3.",
"D9 — Refund Rate",
"4",
"Stripe rolling 30-day refund rate: 3.8%. Root cause codes: RC-3 (Expectation Gap — Timing) accounts for 60% of refunds.",
"3.8% is in the 2–4% band for score 4. RC-3 pattern is a signal (speed-to-result expectation gap), but the overall rate is healthy. Score: 4.",
"D10 — Unit Economics",
"3",
"Gross margin: 47% (revenue minus delivery costs). CPA via Meta ads: $142 for a $497 offer = 28.6% of offer price.",
"Gross margin 40–54% = score 3. CPA 28.6% = borderline score 3/4. Averaging to 3. Score: 3.",
"D11 — Completion Rate",
"3",
"Course platform: 52% complete the full 4-week programme. Prior cohort: 49%. Stable at low-adequate range.",
"52% is in the 45–59% band for score 3. Two consecutive cohorts in the same band = structural issue, not random variation. Score: 3. FLAGGED for action.",
"D12 — Ascension Rate",
"2",
"CRM pipeline: 4 of 87 cohort completers (4.6%) have moved to the Core Offer within 60 days. Ascension email sequence confirmed active. Trigger point: Day 21 post-purchase.",
"4.6% is in the 3–5% band for score 2 (Weak). Ascension sequence is live but timing or positioning may be wrong. Score: 2. MANDATORY ACTION.",
"D13 — Support Efficiency",
"4",
"Intercom: average 1.4 tickets per active buyer per week. Average first response: 5.2 hours. Top ticket topics: 'Zoom link not working' and 'Can't find replay.'",
"1.4 tickets = score 4 (1–2 per buyer per week). Response time 5.2 hours = borderline 4/3. Top topics are technical, not content confusion — FAQ fix available. Score: 4.",
"D14 — Mechanism Strength",
"3",
"10× Test: T-1 average 6.8. T-5 Distinctiveness: 4/5 (strong). Buyer adoption rate: 38% use the name in exit interviews. AI citation check: 2 of 10 queries cite the mechanism.",
"6.8 is in the 6.0–6.9 band for score 3. 38% adoption is below 50%. Some AI citation but not dominant. Score: 3.",
"D15 — Copy Currency",
"4",
"Last sales page update: 47 days ago. Minor language gap: buyer mining phrase 'I post constantly but nobody buys' not yet in copy. No version drift. All testimonials version-current.",
"Updated within 180 days = score 4. Minor language gap is an improvement opportunity, not a problem. Score: 4.",
"",
"Worked Example: Score Summary",
"Metric",
"Result",
"Composite Score",
"D1(3)+D2(3)+D3(4)+D4(3)+D5(4)+D6(3)+D7(3)+D8(3)+D9(4)+D10(3)+D11(3)+D12(2)+D13(4)+D14(3)+D15(4) = 51",
"Grade",
"B — Viable. Optimise.",
"Cluster 1 — Promise",
"D1(3)+D2(3)+D3(4) = 10 / 15. Adequate promise. D1 and D2 are the gaps.",
"Cluster 2 — Proof",
"D4(3)+D5(4)+D6(3) = 10 / 15. Adequate proof. Guarantee is the upgrade opportunity.",
"Cluster 3 — Revenue",
"D7(3)+D8(3)+D9(4) = 10 / 15. Adequate revenue health. Consistent, not growing.",
"Cluster 4 — Delivery",
"D10(3)+D11(3)+D12(2) = 8 / 15. WEAK. D12 (Ascension Rate) is the critical gap. Delivery is working but buyers are not moving up.",
"Cluster 5 — Positioning",
"D13(4)+D14(3)+D15(4) = 11 / 15. Adequate-to-strong. Mechanism freshness is the gap.",
"Profile",
"The Delivering, Not Converting — Cluster 4 is lowest; the delivery is working but the ascension is stalling.",
"Mandatory Actions (D12 = score 2)",
"Rewrite ascension sequence Days 14 and 21. Change trigger: present Core Offer at the buyer's first measurable win (typically Day 12 based on onboarding data) rather than Day 21 calendar. Run ascension A/B test for 60 days.",
"Triggered SOP",
"Post-MVO Forensic Audit Loop — Phase 6 (Next Problem Signal). Schedule 45-minute session to audit the ascension sequence copy and trigger logic.",
"",
"",
"Master Offer Scorecard Checklist",
"",
"System Setup (One-Time)",
"☐ Create Offer Scorecard Records table in Airtable with all 33 fields from the schema above",
"☐ Set up formula fields for composite score, grade, and cluster scores — auto-calculating from dimension input",
"☐ Run baseline scorecard for every active offer to establish Month 1 reference scores",
"☐ Set recurring calendar block: first Tuesday of every month — Offer Scorecard Session (40–60 min per offer)",
"☐ Add formula field: Score Delta vs Prior Month — requires linking to prior month record",
"",
"Every Monthly Scorecard Session",
"☐ Pull all required data for each dimension before opening the scorecard template",
"☐ Score all 15 dimensions using evidence — not gut feel",
"☐ Calculate composite score and grade",
"☐ Calculate five cluster scores and identify the weakest cluster",
"☐ Identify the diagnostic profile from the 14 profiles table",
"☐ For every dimension scoring 1: schedule the prescribed intervention SOP session within 7 days",
"☐ For every dimension scoring 2: document the specific action using the Action Definition Format from the Weekly Review SOP",
"☐ Log all triggered SOPs and block calendar time for each session before closing the scorecard",
"☐ Complete Offer Scorecard Record in Airtable — all 33 fields",
"☐ Update the Month-over-Month Comparison View — add this month's scores and calculate trend",
"",
"After the Scorecard Session",
"☐ Execute all mandatory actions (dimensions scoring 1 or 2) within the documented deadlines",
"☐ Report action outcomes in next month's scorecard record under the Evidence Notes field",
"☐ If grade drops from B to C month-over-month: run Pre-Kill Diagnostic (Kill Criteria SOP) before next Monthly Review",
"☐ If composite score is declining for 2 consecutive months: escalate to Forensic Audit Loop immediately",
"☐ If all five clusters score 9–11 (all-adequate, nothing excellent): plan two specific dimensions to push from 3 to 5 over the next 90 days",
"",
"",
"",
"RISER Nation Master Operating System | Offer Scorecard SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | Offer Scorecard SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
},
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Review an offer’s weekly signals and choose a clear next action
Notice the problem before deciding what caused it
Imagine that sales remain steady while support questions rise. This is an illustrative scene. A revenue total looks reassuring, but it does not explain whether buyers are getting the promised help.
The Weekly Offer Review source proposes a short recurring scan. Its purpose is to notice a signal, record it and choose an action or deeper investigation. The monthly fifteen-dimension scorecard examines broader offer health. The forensic audit investigates a triggered problem. Use these different purposes without claiming that any one review catches every problem.
The source attributes measurement discipline to Kennedy, early monitoring to Hormozi, and its broader framework to Kennedy, Hormozi and Brunson. Those attributions and the claimed advantage over twenty hours of intuition-based work are not supported by citations or measured results here. The useful application is to connect decisions to evidence, buyer outcomes and the next appropriate offer step.
The source calls the ritual twenty minutes. That is its intended single-offer review budget, not a measured guarantee. Setup, investigation, monthly reviews and larger portfolios need separate time. This lesson describes the proposed system; it does not create accounts, send summaries, schedule meetings or change advertising.
Connect signals to the correct investigation
Read all eight source relationships below. For each, distinguish the observed condition, the named procedure, and the urgency. A trigger is a reason to investigate; it is not proof of one particular cause.
Weekly Review Finding
SOP It Triggers
Trigger Condition
What Happens Next
Cold conversion rate drops 20%+ for 7+ days
Post-MVO Forensic Audit Loop
Conversion Drop Trigger threshold met
Run full 8-Phase Forensic Audit within 48 hours. Do not change anything until the audit diagnoses the root cause.
First refund received on any offer
Post-MVO Forensic Audit Loop
First Refund Trigger
Run Phases 4 and 5 of the Forensic Audit (Funnel Diagnostic + Refund Forensics) within 24 hours. Log in Negative Avatar Profiles database.
Cumulative sale count crosses a multiple of 10
Post-MVO Forensic Audit Loop
10-Sale Trigger
Schedule full 8-Phase Audit within 72 hours. This is the most valuable audit — buyer data is fresh.
Refund rate crosses 15% in any rolling 7-day window
Product Kill Criteria SOP
HK-1 Hard Kill pre-threshold signal
Pre-alert: if refund rate reaches 20%+ in the same window next week, Hard Kill Trigger fires. Begin Pre-Kill Diagnostic immediately.
Mechanism name scores below 7.0 in any informal test during the week
10× Mechanism Test & Rename Cadence SOP
Event-based trigger: informal score data
Schedule formal 10× Test for the coming week. Do not wait for quarterly cadence.
Offer has not generated a single sale in 60+ days
Product Kill Criteria SOP — Zombie Offer Audit
Zombie Criterion 2: zero new buyers in 60+ days
Add offer to 30-day remediation watchlist. Implement single highest-leverage change. Re-evaluate in next Monday review.
Bundle or unbundle shows cannibalization signal (related offer revenue drops 15%+)
Offer Stacking & Unbundling Strategy SOP
Cannibalization audit threshold approaching
Run the Three Differentiation Tests. If positioning cannot be differentiated — pause the bundle.
Completion rate drops below 40% for two consecutive weeks
Fulfilment Stress Test SOP
Delivery quality signal
Run Phase 3 (Time-and-Motion Audit) to check whether fulfilment capacity has been breached.
A relative conversion decline needs a baseline and daily observations. A first refund and each ten-sale milestone have different scopes and deadlines. The fifteen-percent seven-day refund warning differs from later thirty-day rules. The mechanism test, kill criteria, stacking, fulfilment and negative-avatar procedures require their actual sources; this table is not their full implementation.
The completion warning here is below forty percent for two weeks, whereas the later Trigger Gate uses below thirty percent. The zombie row starts a thirty-day remediation watchlist with a next-week check; the later table waits for a quarterly audit. Preserve these differences rather than silently choosing a deadline.
Prepare twelve dashboard metrics
The source dashboard contains twelve metric rows. Its seven-row preliminary data-pull table is a different list. Do not reduce the dashboard to seven metrics merely because the monthly scorecard describes the weekly review that way.
Revenue is the transaction sum for the defined period. Buyer counts use new paid contacts. Cold conversion needs cold buyers and unique cold visitors. Warm conversion uses email-attributed buyers and email clicks. Open and click rates need a declared aggregation method. Refunds need a consistent buyer cohort, and support counts need a comparison baseline. Completion needs a defined cohort and milestone. Testimonials and ascension events are counts; neither alone proves a rate. Paid costs and revenue must refer to matching campaigns and periods.
Metric
Data Source
Formula / Calculation
Target
Review Frequency
Weekly gross revenue
Stripe / ThriveCart
Sum of all transactions this week (Mon–Sun)
vs prior week + vs monthly target ÷ 4
Weekly
New buyers this week
CRM (GoHighLevel)
Count of new paid contacts tagged this week
vs prior week
Weekly
Cold conversion rate
GA4 + CRM
New buyers from cold traffic ÷ unique cold visitors × 100
Above 1.0% (viable), above 2.0% (scale signal)
Weekly
Warm conversion rate
Email platform + CRM
New buyers from email traffic ÷ email link clicks × 100
Above 5% (viable), above 10% (strong)
Weekly
Email open rate (active sequences)
ActiveCampaign
Average open rate across all emails sent this week
Above 28% (viable)
Weekly
Email click rate
ActiveCampaign
Average click rate across all emails sent this week
Above 2% (viable)
Weekly
Refunds this week
Stripe / ThriveCart
Count and % of refunds in current week
0 preferred; above 5% = signal
Weekly
Support tickets this week
Intercom / Help Scout
Total new tickets this week
vs prior week; above 5 per 10 buyers = signal
Weekly
Completion rate
Course platform (Kajabi)
% of active cohort who completed last module or milestone
Above 45% (viable)
Biweekly
New testimonials this week
Airtable (Testimonial Registry)
Count of new testimonials collected
Tracking — no target, just awareness
Weekly
Ascension events this week
CRM pipeline
Count of buyers who moved to a higher tier this week
vs prior week; target: 8–15% of cohort over 60 days
Weekly
Ad spend vs revenue (if paid running)
Meta/Google Ads + Stripe
Weekly ad spend ÷ weekly revenue from paid buyers × 100
CPA below 33% of offer price
Weekly (if paid active)
The weekly-versus-monthly-target division by four is an approximation. A full month is not always four weeks. The paid row divides spend by paid revenue but labels its target CPA as a percentage of offer price; these are different measures unless the relevant transaction and price assumptions make them comparable. Preserve both definitions until the measurement design is settled.
The source proposes Looker Studio, payment, CRM, email, support, course and testimonial systems. Naming Stripe, ThriveCart, GoHighLevel, GA4, ActiveCampaign, Intercom, Help Scout, Kajabi or Airtable does not establish an active connection. The target of loading in under thirty seconds and requiring no manual data entry still needs testing.
Prepare the proposed weekly summary
The following seven steps describe the preliminary pull. Keep the requested data and output format distinct; a formatted number is only useful when its source and period are known.
Workflow Step
Platform
Data Pulled
Format
1. Revenue pull
Stripe via API
All successful charges this week (Mon–Sun). Total revenue, transaction count, average transaction value, refunds issued.
Formatted as: This week $X (vs last week $Y, delta Z%)
2. Conversion pull
GA4 + CRM webhook
Unique cold visitors to all offer pages, new buyer tags created this week, source attribution.
Open rates, click rates, reply rates for all sequences that sent emails this week.
Formatted as: Open rate X%, Click rate Y%
4. Support pull
Intercom or Help Scout API
Ticket count, average first response time, resolved vs open, top 3 ticket topics this week.
Formatted as: X tickets (vs last week Y). Top topics: [list]
5. Refund pull
Stripe API
All refunds issued this week, reason codes where available.
Formatted as: X refunds ($Y) this week. Root cause codes: [list if tagged]
6. Completion pull
Kajabi API or manual
Module completion stats for all active cohorts.
Formatted as: X% completion rate this week (vs last week Y%)
7. Summary format
n8n — Slack or email
Compile all data into a single weekly summary message with traffic-light indicators (Green/Amber/Red) applied automatically based on thresholds.
Slack DM or email to founder. Subject: 'Weekly Offer Review — [date] — [overall signal colour]'
Sunday at ten PM is the proposed collection time. It cannot include the final two hours of a full Sunday calendar day at that moment. Define cutoff, timezone and late-arriving records before claiming a complete Monday–Sunday week. The proposed Slack or email destination is not an instruction to send a message from this lesson.
Walk through six timed segments
The source says five segments but provides five scans plus action selection: 2 + 4 + 4 + 4 + 4 + 2 = 20 minutes. Log a question that would take more than two minutes as needing deeper review. Missing data should be labelled unavailable rather than replaced with a guess.
Revenue scan — two minutes
Compare current revenue with the prior week and the monthly plan, then identify which offer changed. Portfolio totals can conceal opposing movements. The source’s twenty-percent scan thresholds differ from its later matrix.
2 min Revenue Scan
► Is weekly gross revenue above, below, or in line with the prior week? ► Is weekly gross revenue on track to hit the monthly target at this run rate? (Weekly revenue × 4 vs monthly target) ► Did any offer significantly over- or under-perform vs its prior-week baseline (more than 20% deviation)? ► GREEN if all offers within 20% of prior week. AMBER if one offer is 20%+ below. RED if total weekly revenue is 20%+ below the 4-week average.
Conversion scan — four minutes
Check cold and warm conversion separately, then the email measures and direction of change. Two weekly values cannot prove a seven-day continuous decline. A low conversion rate does not identify whether the issue is message, traffic, offer or measurement.
4 min Conversion Health Scan
► Is the cold conversion rate for each active offer within the viable range (above 1.0%)? ► Is the warm conversion rate within the viable range (above 5%)? ► Has either cold or warm conversion declined for two or more consecutive weeks? (Sustained decline is more significant than a single-week dip.) ► Is the email open rate above 28%? Is the click rate above 2%? ► GREEN: all rates within viable range, no sustained decline. AMBER: one rate below viable, or one week of decline. RED: cold conversion below 0.8% OR second consecutive week of 20%+ decline — Forensic Audit trigger.
Refund, support and complaint scan — four minutes
Distinguish refunds issued from refund requests, and record repeated support topics as observations. Note complaints and escalations that may not appear in a payment report. The first-refund reference here names Phase 5 immediately; other source sections name Phases 4 and 5 within twenty-four hours.
4 min Signal Scan (Refunds, Support, Complaints)
► How many refunds were issued this week? What is the rolling 30-day refund rate? ► How many support tickets were opened this week? Is that above or below last week? ► Were any support tickets about the same topic (a pattern emerging)? ► Were any community complaints, negative posts, or escalations flagged this week? ► Is this the first refund on this offer? (Triggers Forensic Audit Phase 5 immediately.) ► GREEN: zero refunds, support normal volume, no patterns. AMBER: 1–2 refunds OR support tickets up 20%+ OR recurring topic in tickets. RED: 3+ refunds in one week OR refund rate above 10% rolling — Forensic Audit trigger.
Growth scan — four minutes
Record testimonials, advancement to another tier, completion, unusually strong content and useful buyer phrases. Threefold engagement is a source comparison example, not proof of revenue. This section treats growth as opportunities without alert colors, yet later completion and ascension rows do carry alerts; make that inconsistency visible.
4 min Growth Signal Scan
► Were any new testimonials collected this week? Is the testimonial collection rate on track? ► Did any buyers ascend to a higher value ladder tier this week? ► Is completion rate tracking at or above 45% for active cohorts? ► Is there any organic content this week that significantly outperformed baseline (3x+ engagement)? ► Were any new buyer language phrases surfaced this week that could be added to the mining database? ► Note: growth signals do not generate AMBER or RED — they generate opportunities. Log the top opportunity for the priority action selection.
Paid-traffic scan — four minutes when applicable
Compare campaign CPA, offer price and ROAS using matching periods. The source proposes immediate pauses in certain cases. They are source operating rules, not actions performed here. A creative trend is a possible signal, not a demonstrated cause.
4 min Paid Traffic Scan (if paid ads active)
► Is the Cost Per Acquisition (CPA) below 33% of the offer price for all active ad campaigns? ► Is any ad set spending above $50/day with a CPA above threshold? (Pause immediately — this is real money leaking in real time.) ► Has the creative performance metric (hook rate / CTR) declined week-over-week, suggesting creative fatigue? ► Is ROAS above 2.0x across all active campaigns? ► GREEN: CPA within target, no creative fatigue, ROAS above 2.0x. AMBER: one campaign above CPA threshold. RED: CPA above 50% of offer price OR total ROAS below 1.5x — pause ad spend immediately, do not wait for audit.
Select and document — two minutes
Name the action, owner, exact deadline and evidence of completion. If investigation is required, identify the procedure and time needed. The source estimates three-to-four minutes for documentation elsewhere, which conflicts with this combined two-minute slot.
2 min Priority Action Selection and Documentation
► Based on all five scans: what is the single most important action this week? ► Assign the action an owner (even if that is you) and a deadline (must be before next Monday). ► Are any Forensic Audit triggers fired? If yes: schedule the audit and assign a time block. ► Complete the Weekly Review Record in Airtable (see Phase 5). ► Total time: 20 minutes maximum. Timer stops. Review ends.
Classify a signal without hiding conflicting thresholds
Green means within the stated range, Amber calls for attention, and Red calls for escalation. The source reclassifies an Amber as Red when two consecutive weeks pass without improvement from the prior action. That is an escalation rule, not proof that the problem has one structural cause.
Read the entire matrix below, including its proposed responses. Keep the raw value and window alongside any color; several boundaries and earlier thresholds disagree.
Metric
Green
Amber
Red
Action Triggered
Weekly revenue
Within 15% of prior week and on track for monthly target
15–25% below prior week OR below monthly run rate by 25%
Below 25% of prior week OR below 50% of monthly run rate
Amber: identify single offer causing the drop. Run targeted conversion check. Red: emergency Forensic Audit + paid ad pause if applicable.
Cold conversion rate
Above 1.5%
1.0–1.4%
Below 1.0%
Amber: A/B test new headline variant within 7 days. Red: run Pre-Kill Diagnostic from Kill Criteria SOP within 48 hours.
Warm conversion rate
Above 8%
4–7%
Below 4%
Amber: audit email sequence Days 8–10 (mechanism introduction). Red: full email sequence rebuild triggered.
Email open rate
Above 28%
20–27%
Below 20%
Amber: test 3 new subject line variants for the lowest-performing sequence email. Red: deliverability audit — check sender reputation, spam score, list health.
Refund rate (rolling 30 days)
Below 5%
5–9%
Above 10%
Amber: run Refund Forensics protocol (Forensic Audit SOP Phase 5). Red: Hard Kill pre-threshold signal. Begin Pre-Kill Diagnostic immediately.
Support tickets (weekly count)
Same or below prior week
20–40% above prior week
40%+ above prior week
Amber: identify top ticket topic. Create a self-service FAQ for it. Red: system problem — find and fix the source before more buyers encounter it.
Amber: pause the lowest-performing ad set. Test new creative. Red: pause all paid spend immediately. Do not add fuel to broken vehicle (Hormozi's rule).
Ad ROAS (if paid active)
Above 2.5x
1.5–2.4x
Below 1.5x
Amber: audit audience targeting — check for audience fatigue. Red: immediate paid ad pause. Full creative and offer audit before re-activating.
Ascension rate
More than 2 ascension events in last 30 days
0–1 ascension event in 30 days — check sequence is active
Zero ascension events in 45+ days — sequence failure
Amber: verify ascension email sequence is active and sending. Check CRM automation rules. Red: ascension sequence rebuild required.
Revenue: the scan uses twenty percent, while the matrix uses fifteen-to-twenty-five percent and says “below 25% of prior week.” Literally being below one quarter of prior revenue is not the same as declining by twenty-five percent. The source does not settle that wording.
Conversion: cold viable above one percent in the dashboard differs from matrix Green above 1.5 percent and scan Red below 0.8 percent. Warm thresholds similarly change from five/ten to four/eight percent. Exact endpoints and fractional gaps require a rule before automation.
Email: the open-rate bands leave gaps around twenty-seven to twenty-eight percent. The click-rate target has no separate full-matrix row. Weighting averages and handling repeated clicks remain unspecified.
Refunds: weekly counts, seven-day warnings and thirty-day rates are not interchangeable. Exact ten percent and the gap between nine and ten are not clearly classified in the matrix. Do not silently round a rate into the preferred color.
Support: forty percent appears in both Amber and Red. Small positive increases below twenty percent are not clearly covered. The later gate’s wording “above 40% of prior week” differs from forty percent above the prior week. If the prior count is zero, the percentage change is undefined without an explicit rule.
Completion: above forty-five, at least forty-five and thirty-to-forty-four differ at boundaries. The earlier forty-percent warning and later thirty-percent trigger also differ. Milestone completion is not necessarily the monthly scorecard’s full-program completion.
Paid metrics: scan CPA below thirty-three percent and Red above fifty percent differ from matrix twenty-five/forty percent. Scan ROAS above two differs from matrix above2.5, with gaps before that boundary. Do not combine these into an invented universal rule.
Ascension: more than two events in thirty days leaves exactly two unspecified; zero in thirty days overlaps the longer forty-five-day zero case. These event counts differ from the earlier eight-to-fifteen-percent cohort target over sixty days.
Choose one priority without suppressing urgent work
The proposed action should be specific, owned by one person and completable within seven days. Apply the hierarchy in order: Red, persistent Amber reclassified as Red, new Amber, then a growth opportunity when everything is Green. A priority rule does not erase simultaneous urgent escalations or shorten investigation to fit an arbitrary slot.
Priority Level
Condition
Action Directive
Example
P1 — Immediate
A Red signal was identified in any scan — and especially if a Forensic Audit trigger has fired
The priority action is: schedule and complete the specific triggered audit or the specific Red-signal resolution within 7 days. Everything else waits.
Red: cold conversion below 0.8% for second consecutive week. Action: Block 3 hours Tuesday to run the full Forensic Audit. No other work actions this week until the audit is done.
P2 — Escalating Amber
An Amber signal has persisted for two or more consecutive weeks without the prior week's action producing improvement
The Amber is reclassified Red this week. The action is the escalated intervention: if the headline A/B test did not improve open rates, the action is a full sequence rewrite.
Amber (Week 1): email open rate 22%. Action: A/B test subject lines. Amber (Week 2): email open rate 21% — no improvement. Action THIS week: reclassify Red. Full subject line overhaul of top 5 sequence emails.
P3 — New Amber
An Amber signal appeared this week for the first time
The action is the specific targeted fix described in the Signal Matrix for that metric.
New Amber: refund rate at 7%. Action: run Refund Forensics protocol — interview the two refunding buyers within 72 hours. Document root cause codes.
P4 — Green, Growth Opportunity
All signals are Green. No Amber or Red present.
The action is the single highest-leverage growth opportunity identified in the Growth Signal Scan.
All Green. Growth Signal: one organic LinkedIn post generated 3× normal engagement on a specific mechanism angle. Action: write three more posts on that angle this week and track engagement.
The P2 text mixes a headline test with email opens; a page headline and an email subject line are not the same intervention. The example’s twenty-two-to-twenty-one-percent opens show no improvement but do not prove the cause. Likewise, three more posts on a strong angle are a proposed test, not a forecast.
Use all five fields in the following action format. Its testing-platform example, audience phrase and fourteen-day follow-up are source examples, not a deployed experiment.
Priority Action Definition Format ACTION: [Specific, verb-led description of what will be done] OWNER: [Name of the person responsible — even if that is you] DEADLINE: [Specific day and time — not 'by Friday,' but 'by Friday 5 PM'] COMPLETION CRITERIA: [How will you know this is done? What is the specific output?] DOES THIS TRIGGER A DEEPER SOP? [Yes / No — if yes, name the SOP and schedule the session]
Example: ACTION: A/B test two new headline variants on the MVO sales page targeting the 'spinning wheels' PAIN-ACUTE phrase. OWNER: [Founder] DEADLINE: Thursday 5 PM COMPLETION CRITERIA: Both variants live on Convert.com. UTM parameters set. Baseline conversion rate documented. DOES THIS TRIGGER A DEEPER SOP? No — if no improvement after 14 days, this triggers the Forensic Audit Loop.
Use the complete Trigger Gate
Match the condition to the session scope and urgency below. A general seven-day action deadline must not override a stated immediate, twenty-four-, forty-eight- or seventy-two-hour response. Retain shorter and longer deadlines as the source gives them, with the conflicts already noted.
Trigger
What Fires It
Which SOP
Session Length to Schedule
Urgency
10-Sale Trigger
Weekly review confirms cumulative sale count crossed a multiple of 10 since the last audit
Post-MVO Forensic Audit Loop — Full 8-Phase
2.5–3 hours
Schedule within 72 hours
First Refund Trigger
Weekly Signal Scan identifies the first refund on any offer tier
Post-MVO Forensic Audit Loop — Phases 4 and 5 only (Funnel Diagnostic + Refund Forensics)
45–60 minutes
Schedule within 24 hours
Conversion Drop Trigger
Cold conversion rate has declined 20%+ vs the 30-day average for 7+ consecutive days (visible across two consecutive weekly reviews)
Support tickets above 40% of prior week for two consecutive weeks
Post-MVO Forensic Audit Loop Phase 3 (Buyer Language Mining) + Fulfilment Stress Test if completion rate also declining
60 minutes
Schedule within 1 week
Zombie Offer Signal
Offer has zero new buyers for 60+ consecutive days (visible in weekly revenue scan)
Product Kill Criteria SOP — Zombie Offer Audit
30 minutes
Add to Zombie watchlist. Run Zombie Audit at next quarterly review.
Completion Rate Red Signal (below 30% for 2 weeks)
Completion rate below 30% for two consecutive weekly reviews
Fulfilment Stress Test SOP — Phase 3 (Time-and-Motion Audit)
90 minutes
Schedule within 1 week
Ad ROAS Red Signal (below 1.5x)
Ad ROAS below 1.5x for any active campaign
Paid ad pause immediately (no SOP needed). Product Kill Criteria SOP Pre-Kill Diagnostic if the offer itself may be the problem
30-minute audit + pause
Immediate
The conversion trigger compares with a thirty-day average and requires seven consecutive days; two weekly snapshots are insufficient evidence of persistence. The support gate adds two weeks where other sections do not. The quarterly zombie audit conflicts with earlier next-Monday remediation. Record these unresolved differences before using the table as automated decision logic.
The source asks for a scheduled block before closing the review. That is a proposed operating practice. It does not mean a meeting, audit, ad pause or buyer contact has been created by reading this lesson.
Keep the complete review record
The documentation table has thirty-two fields, despite the later statement that it has thirty-one. Preserve every field below. Separate a metric’s observed value, its classification and the action taken.
Field
Type
What to Document
Review ID
Autonumber
Auto-generated. Format: WOR-[YYYY-MM-DD]
Review Date
Date
The Monday the review was conducted
Offers Reviewed
Link → Offers table
All active offers included in this review
Total Review Duration
Number
Actual minutes taken (target: 20)
Revenue Signal
Single select
Green / Amber / Red
Weekly Revenue
Currency
Total gross revenue this week
Revenue vs Prior Week (%)
Number
Calculated: this week ÷ prior week × 100 − 100
Conversion Signal
Single select
Green / Amber / Red
Cold Conversion Rate
Number
Current week %
Warm Conversion Rate
Number
Current week %
Email Signal
Single select
Green / Amber / Red
Email Open Rate
Number
Average this week %
Email Click Rate
Number
Average this week %
Refund Signal
Single select
Green / Amber / Red
Refunds This Week
Number
Count
Rolling 30-Day Refund Rate
Number
%
Support Signal
Single select
Green / Amber / Red
Support Tickets This Week
Number
Count
Support Ticket Delta vs Prior Week (%)
Number
% change
Top Support Ticket Topic This Week
Short text
Most common topic if pattern exists
Growth Signal (best this week)
Long text
One sentence on the best positive signal observed
Ad Signal (if paid active)
Single select
Green / Amber / Red / N/A
Paid Ad CPA
Currency
Current week average CPA
ROAS
Number
Current week
Overall Review Signal
Single select
All Green / Amber Present / Red Present — triggers Escalation
Triggers Fired
Multiple select
10-Sale / First Refund / Conversion Drop / Refund Rate Red / Support Red / Zombie / Completion Red / Ad ROAS Red / None
When the triggered SOP session is blocked in the calendar
Priority Action This Week
Long text
Full Action Definition Format (Action, Owner, Deadline, Completion Criteria)
Prior Week Action — Completed?
Single select
Yes — fully / Partial / No
Prior Week Action — Outcome
Short text
What happened as a result of last week's action?
Notes
Long text
Anything relevant that does not fit other fields
The WOR-date format is not automatically created by an Autonumber field. A percent-change formula needs a zero-baseline policy. Multiple linked offers with one scalar conversion or revenue value require a declared aggregate-versus-per-offer design. A single triggered-SOP and session field may not represent multiple simultaneous escalations. Completion, testimonials and ascension are dashboard items without separate scalar fields in this table; do not pretend the schema fully implements the dashboard.
The five additional specifications below connect audits, kill assessments, mechanism tests, the prior review and a rolling revenue average. Together with the thirty-two main fields, these are thirty-seven specifications. A link to the prior record does not itself calculate four weeks of history; the required lookup or aggregation logic is not supplied.
Linking Field
Links To
Purpose
Forensic Audit Triggered
Link → Forensic Audit Records table
When a Forensic Audit is triggered by this review, link to the resulting audit record once it is completed
Kill Assessment Triggered
Link → Kill Records table
When a Kill Criteria SOP session is triggered by this review, link to the resulting kill record
Mechanism Test Triggered
Link → Mechanism Name Records table
When a 10× test is triggered by a health indicator flag in this review, link to the mechanism test record
Prior Week Review
Link → Weekly Offer Review Records (self)
Link to the prior week's review record for easy comparison navigation
4-Week Rolling Revenue Average
Formula
Average of the last 4 weekly revenue figures — auto-calculated across linked records
Understand the proposed automation before claiming it works
The twelve nodes below describe a workflow, not executable code. For each node, identify its actual input, calculation and destination before any implementation. Nothing in this lesson establishes credentials, authorized access, error handling or a deployed integration.
Node #
Node Name
Action
Platform
Output
1
Schedule trigger
Run every Sunday 10 PM local time
n8n cron
Initiates the workflow
2
Stripe revenue pull
Pull all successful charges from Mon–Sun current week and Mon–Sun prior week. Calculate weekly total and delta.
Pull all refunds from current week. Pull all refunds from rolling 30 days. Calculate refund rate.
Stripe API
Refund count, refund rate rolling 30 days
4
CRM conversion pull
Pull new paid contacts tagged this week. Pull unique cold visitors from GA4 (same window). Calculate cold conversion rate.
GoHighLevel API + GA4 Data API
New buyer count, cold conversion rate, warm conversion rate
5
Email metrics pull
Pull aggregate open rate and click rate for all emails sent this week across all active sequences.
ActiveCampaign API
Open rate, click rate, delta vs prior week
6
Support ticket pull
Pull new ticket count this week and prior week. Pull top 3 ticket tags by volume.
Intercom or Help Scout API
Ticket count, delta %, top tags
7
Completion rate pull
Pull module completion percentage for all active cohorts.
Kajabi API
Completion rate per cohort, average
8
Ad metrics pull (if active)
Pull weekly ad spend, CPA per campaign, ROAS per campaign.
Meta Ads API + Google Ads API
CPA, ROAS, spend per campaign
9
Signal classification
Apply Green/Amber/Red thresholds to all pulled metrics. Flag any metrics triggering the Trigger Gate.
n8n code node
Signal colour per metric, list of any fired triggers
10
Looker Studio push
Write formatted data to Google Sheets (connected to Looker Studio dashboard) so dashboard auto-refreshes.
Google Sheets API
Dashboard ready for Monday review
11
Slack/email summary
Format a plain-text weekly summary: overall signal, all metrics, any triggered escalations, prior week action reminder.
Slack API or SMTP
Slack DM or email to founder. Arrives Sunday 10:15 PM.
12
Airtable record creation
Create a new Weekly Review Record in Airtable with all auto-populated fields (the reviewer will complete the remaining fields during the review).
Airtable API
New WOR record created with all pulled metrics pre-filled
Node4 lists warm conversion as an output without specifying the matching email-click input. Testimonial, ascension, content and buyer-language data are not fully described in the collection nodes. Prior-action reminders also need a defined record lookup. The automatic classification must first resolve the conflicting thresholds. The Sunday22:15 summary is a target time, not a verified delivery.
The dashboard proposal has five sections: Revenue, Conversion, Signals, Growth and Paid Traffic. Read each section’s metric and visual requirements below. A single-screen layout and color coding need actual accessibility and display checks. Color must not be the only way a reader can understand the signal.
Dashboard Section
Metrics Displayed
Visual Format
Signal Colour Applied
Revenue (top left)
Weekly gross revenue, buyer count, revenue vs prior week %, revenue vs monthly target %
Large number cards with up/down arrow and colour coding
Gauge charts showing current value vs target range
Green/Amber/Red auto-applied
Signals (top right)
Refund count, rolling refund rate, support ticket count, delta vs prior week, top ticket topic
Number cards with trend sparklines
Green/Amber/Red auto-applied
Growth (bottom left)
New testimonials, ascension events, completion rate, top-performing content piece this week
Simple number cards, no colour coding (growth signals are opportunities, not alerts)
No signal colour — neutral
Paid Traffic (bottom right)
CPA per campaign, ROAS, weekly spend, spend vs budget
Table with row-level colour coding per campaign
Green/Amber/Red per row
Adjust the cadence for multiple offers
The tier schedule assigns the most attention to entry offers, an abbreviated core review, alternate-week high-ticket review, a continuity churn scan and shorter bundle checks. These are source workload proposals, not measured capacities. Read every tier and total row.
Offer Tier
Review Frequency
Time Allocated
Rationale
MVO (entry offer — highest buyer volume)
Every Monday — full 5-scan protocol
8–10 minutes
Highest buyer volume means highest signal density. Any problem at this tier cascades through the entire value ladder. It gets the most review time.
Core Offer (primary revenue driver)
Every Monday — abbreviated 3-scan protocol (Revenue, Signals, Conversion only)
5–6 minutes
Primary revenue driver. Must catch problems fast. Abbreviated scan sufficient because volume is lower than MVO.
DWY / High-Ticket (low volume, high value)
Every other Monday — full scan when scheduled
5 minutes on alternate weeks
Low buyer volume means signal density is lower. A biweekly check catches most issues without over-investing review time.
Continuity / MRR
Every Monday — churn-focused scan only (MRR, churn events, support tickets specific to continuity)
3–4 minutes
Churn is the primary metric for continuity. One focused metric check is sufficient. If churn is Red, escalate to a full review.
Bundles and Unbundles (if active)
Every Monday — revenue and conversion only
1–2 minutes each
Bundles generate lower overall volume. A quick revenue/conversion check catches the significant signals without detailed protocol.
Total (with 4 active offers)
20–25 minutes for the full portfolio review
Fits within the 20–30 minute window for a 4-offer business
Scales to approximately 5 minutes per additional active offer above 4, with abbreviated protocols for newer offers.
The rotation then proposes different full and abbreviated scopes. In particular, the core offer moves from an abbreviated scan to the full-scan column. A five-minute allowance for each additional offer cannot maintain a fixed thirty-minute ceiling indefinitely. Keep actual time and review coverage visible.
Week Type
Offers on Full Scan
Offers on Abbreviated Scan
Total Monday Review Time
Week A (odd weeks)
MVO + Core Offer + DWY
Continuity + all Bundles
25 minutes
Week B (even weeks)
MVO + Core Offer + Continuity
DWY + all Bundles
25 minutes
When 5+ active offers
MVO every week. Others rotate on a 2-week cycle.
All non-rotating offers get Revenue + Signals scan only (1 min each)
30 minutes maximum
Review four weeks of progress without assuming cause
On the first Monday, the source extends the session to forty-five minutes and asks six questions. This is separate from the monthly fifteen-dimension scorecard’s first-Tuesday cadence. Examine trends by offer, previous actions and their outcomes, approaching triggers, testimonials and the annual revenue plan.
Monthly Review Question
What to Look For
Action If Found
Which metrics have been Amber or Red for 2 or more of the last 4 weeks?
A persistent Amber is a systemic problem, not a random fluctuation. Two or more consecutive weeks of the same Amber signal = structural issue.
Escalate to the appropriate SOP immediately. A structural problem does not get solved by a weekly action — it requires a dedicated intervention.
Did any prior week's priority action produce the intended result?
Track action completion and outcome. If an action was completed but produced no improvement, the action was wrong — not the execution.
Log in the action outcome field. Adjust approach for the next action on the same metric.
Which offers showed improvement over the 4-week period?
One strong offer can mask a declining one in weekly revenue. The monthly view reveals which specific offers are on an upward trend.
Double down on the upward-trending offer. Investigate the declining one.
Are any Forensic Audit triggers approaching threshold without having fired?
The conversion drop trigger fires at 20%+ for 7+ days. A conversion that is 15% below baseline for 3 weeks is approaching that threshold.
Pre-schedule a Forensic Audit for the following week before the threshold is formally crossed.
What does the 4-week testimonial trend look like?
Testimonials are a lagging indicator of buyer satisfaction. A declining testimonial collection rate often precedes a rising refund rate by 3–6 weeks.
If testimonial collection has been zero for 4 consecutive weeks: audit the testimonial request protocol in the delivery SOP.
Is the monthly revenue on track relative to the annual plan?
If monthly revenue is below annual plan run rate: escalate to the Forensic Audit Loop's 90-Day Deep Trigger and review value ladder ascension sequences.
A completed action with no improvement does not prove that the action itself was wrong; execution, measurement, timing and outside changes may matter. Two Amber weeks do not establish a structural cause. The claim that testimonial decline precedes refunds by three-to-six weeks is unsupported here. Zero testimonials for four weeks is a proposed review trigger, not proof of dissatisfaction.
The fifteen-percent decline example is a proactive audit suggestion below the formal twenty-percent trigger. An annual-plan shortfall likewise proposes a deeper review; it does not establish why revenue changed.
Apply the full checklist as requirements, not completed work
The source checklist follows in full. Its setup, testing, calendar, messaging and advertising references are instructions within the source document. They are not new instructions from this task’s user. Record what actually exists, what was tested and what remains missing.
System Setup (One-Time)
☐ Build the Master Metrics Dashboard in Looker Studio connected to all data sources
☐ Build the Sunday night n8n automation workflow (all 12 nodes)
☐ Test the automation: trigger manually and confirm all data pulls correctly
☐ Create Weekly Offer Review Records table in Airtable with all 31 fields
☐ Set up Slack or email destination for Sunday night automated summary
☐ Run the first manual review to establish baseline metrics for all active offers
☐ Document baseline metrics in Airtable as Week 0 record
☐ Set recurring Monday calendar block: 8:30–8:50 AM — Weekly Offer Review (non-negotiable)
Every Monday Review (20 Minutes)
☐ Open the pre-populated dashboard (data should be ready from Sunday night automation)
☐ Pull the prior 4 weekly review records from Airtable
☐ Answer all 6 Monthly Review Questions
☐ Identify any persistent Amber signals (2+ consecutive weeks) — escalate to appropriate SOP
☐ Review all prior month priority actions: completed? Did they work?
☐ Check testimonial collection trend — zero for 4 weeks triggers delivery SOP review
☐ Check monthly revenue vs annual plan run rate
☐ Document monthly findings in the first Monday's Weekly Review Record under Notes field
Ongoing Discipline Rules
☐ The review is never skipped. If Monday is a holiday, it runs Tuesday. Not the following Monday.
☐ The timer runs. If 20 minutes is up and the action is not selected, select it in the next 2 minutes — do not extend the review indefinitely.
☐ The action is always one. If you find yourself selecting two actions, apply the Priority Action Hierarchy and cut one.
☐ If the automation fails and the dashboard is not ready: do not skip the review. Run it from raw platform dashboards in 30 minutes.
☐ Every Trigger Gate escalation gets a calendar block before the review ends. Not 'I'll schedule it later.'
The holiday exception moves the review to Tuesday. The final rule allows two extra minutes to select an action, and an automation failure permits a thirty-minute raw-dashboard review. Those exceptions qualify the earlier twenty-minute maximum and missing-data rule. Preserve them rather than claiming the procedure has no exceptions.
RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING. The older source footer uses a different domain; it remains preserved as source evidence.
Turn in one proposed weekly review record with dated metrics, measurement windows, unresolved classification conflicts, a priority action with owner and deadline, and any required investigation scopes. Label missing data. Keep the record in your course work folder until a submission destination is confirmed. A reviewer should check the definitions and conflicts before using this draft as operational decision logic.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — WEEKLY OFFER REVIEW RITUAL
The 20-Minute Monday Protocol That Catches Every Problem Before It Compounds
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
Most operators review their metrics reactively — when something breaks, when a refund arrives, or when an affiliate asks why their conversions dropped. By then, the problem has been compounding for days or weeks. Revenue has leaked. Buyer experience has degraded. And the fix is more expensive than it would have been if the signal had been caught seven days earlier.
The Weekly Offer Review Ritual is the 20-minute Monday protocol that changes this. It is not the deep forensic investigation — that is the Post-MVO Forensic Audit Loop, triggered by events and run in 2–3 hour blocks. The weekly review is surveillance: a structured scan of every active offer's health metrics, run before the work week begins, producing exactly one priority action and triggering the appropriate deeper audit when warranted.
The critical design constraint is 20 minutes. A review that takes 45 minutes will not happen every week. A review that generates 10 action items will not produce meaningful change. This SOP is built around those two constraints: light enough to be done consistently, focused enough to produce one decision.
Kennedy's Measurement Principle
If you are not measuring it, you are guessing. And in a direct-response business, guessing is the most expensive operating cost there is. Twenty minutes of structured measurement every Monday is worth more than 20 hours of intuition-based hustle on Thursday.
Hormozi's Monitoring Rule
The operators who scale fastest are not smarter — they spot the problems and the opportunities sooner. A weekly review is the earliest warning system available. Every week you skip it is a week where a preventable problem compounds into an expensive one.
The Surveillance vs Investigation Distinction
The Weekly Review is surveillance: a regular, lightweight scan for signals. The Post-MVO Forensic Audit Loop (RISER Nation SOP Series) is investigation: a triggered, deep-dive diagnostic. These two systems work together. The weekly review catches the signal. The forensic audit diagnoses what it means. Never confuse their roles — if you try to do investigation in the weekly slot, the review will take 2 hours and stop happening.
How the Weekly Review Connects to the SOP Ecosystem
The Weekly Offer Review Ritual is the operational heartbeat of the RISER Nation Master Operating System. It is the mechanism through which every other SOP in the series receives its triggering data. Understanding these connections prevents duplication of effort and ensures each SOP fires at the right moment.
Weekly Review Finding
SOP It Triggers
Trigger Condition
What Happens Next
Cold conversion rate drops 20%+ for 7+ days
Post-MVO Forensic Audit Loop
Conversion Drop Trigger threshold met
Run full 8-Phase Forensic Audit within 48 hours. Do not change anything until the audit diagnoses the root cause.
First refund received on any offer
Post-MVO Forensic Audit Loop
First Refund Trigger
Run Phases 4 and 5 of the Forensic Audit (Funnel Diagnostic + Refund Forensics) within 24 hours. Log in Negative Avatar Profiles database.
Cumulative sale count crosses a multiple of 10
Post-MVO Forensic Audit Loop
10-Sale Trigger
Schedule full 8-Phase Audit within 72 hours. This is the most valuable audit — buyer data is fresh.
Refund rate crosses 15% in any rolling 7-day window
Product Kill Criteria SOP
HK-1 Hard Kill pre-threshold signal
Pre-alert: if refund rate reaches 20%+ in the same window next week, Hard Kill Trigger fires. Begin Pre-Kill Diagnostic immediately.
Mechanism name scores below 7.0 in any informal test during the week
10× Mechanism Test & Rename Cadence SOP
Event-based trigger: informal score data
Schedule formal 10× Test for the coming week. Do not wait for quarterly cadence.
Offer has not generated a single sale in 60+ days
Product Kill Criteria SOP — Zombie Offer Audit
Zombie Criterion 2: zero new buyers in 60+ days
Add offer to 30-day remediation watchlist. Implement single highest-leverage change. Re-evaluate in next Monday review.
Bundle or unbundle shows cannibalization signal (related offer revenue drops 15%+)
Offer Stacking & Unbundling Strategy SOP
Cannibalization audit threshold approaching
Run the Three Differentiation Tests. If positioning cannot be differentiated — pause the bundle.
Completion rate drops below 40% for two consecutive weeks
Fulfilment Stress Test SOP
Delivery quality signal
Run Phase 3 (Time-and-Motion Audit) to check whether fulfilment capacity has been breached.
Pre-Review Setup: The Dashboard Architecture
The 20-minute time budget only works if every piece of data is pre-loaded and formatted before the review begins. A review that starts with pulling reports from five different platforms will take 45 minutes. The dashboard architecture defines what data must be automatically available at the start of every Monday review.
The Master Metrics Dashboard
Build this dashboard in Looker Studio, connecting to the data sources listed below. It should load in under 30 seconds and display all metrics for all active offers without any manual data entry. The dashboard is not pulled from — it pushes everything to the reviewer simultaneously.
Metric
Data Source
Formula / Calculation
Target
Review Frequency
Weekly gross revenue
Stripe / ThriveCart
Sum of all transactions this week (Mon–Sun)
vs prior week + vs monthly target ÷ 4
Weekly
New buyers this week
CRM (GoHighLevel)
Count of new paid contacts tagged this week
vs prior week
Weekly
Cold conversion rate
GA4 + CRM
New buyers from cold traffic ÷ unique cold visitors × 100
Above 1.0% (viable), above 2.0% (scale signal)
Weekly
Warm conversion rate
Email platform + CRM
New buyers from email traffic ÷ email link clicks × 100
Above 5% (viable), above 10% (strong)
Weekly
Email open rate (active sequences)
ActiveCampaign
Average open rate across all emails sent this week
Above 28% (viable)
Weekly
Email click rate
ActiveCampaign
Average click rate across all emails sent this week
Above 2% (viable)
Weekly
Refunds this week
Stripe / ThriveCart
Count and % of refunds in current week
0 preferred; above 5% = signal
Weekly
Support tickets this week
Intercom / Help Scout
Total new tickets this week
vs prior week; above 5 per 10 buyers = signal
Weekly
Completion rate
Course platform (Kajabi)
% of active cohort who completed last module or milestone
Above 45% (viable)
Biweekly
New testimonials this week
Airtable (Testimonial Registry)
Count of new testimonials collected
Tracking — no target, just awareness
Weekly
Ascension events this week
CRM pipeline
Count of buyers who moved to a higher tier this week
vs prior week; target: 8–15% of cohort over 60 days
Weekly
Ad spend vs revenue (if paid running)
Meta/Google Ads + Stripe
Weekly ad spend ÷ weekly revenue from paid buyers × 100
CPA below 33% of offer price
Weekly (if paid active)
The Pre-Review Automated Data Pull
Every Sunday night at 10 PM, an n8n workflow runs automatically. It pulls the prior week's data from all connected platforms, formats it into the dashboard, and sends a Slack or email summary to the reviewer. When the reviewer opens their laptop on Monday morning, the dashboard is already populated.
Workflow Step
Platform
Data Pulled
Format
1. Revenue pull
Stripe via API
All successful charges this week (Mon–Sun). Total revenue, transaction count, average transaction value, refunds issued.
Formatted as: This week $X (vs last week $Y, delta Z%)
2. Conversion pull
GA4 + CRM webhook
Unique cold visitors to all offer pages, new buyer tags created this week, source attribution.
Open rates, click rates, reply rates for all sequences that sent emails this week.
Formatted as: Open rate X%, Click rate Y%
4. Support pull
Intercom or Help Scout API
Ticket count, average first response time, resolved vs open, top 3 ticket topics this week.
Formatted as: X tickets (vs last week Y). Top topics: [list]
5. Refund pull
Stripe API
All refunds issued this week, reason codes where available.
Formatted as: X refunds ($Y) this week. Root cause codes: [list if tagged]
6. Completion pull
Kajabi API or manual
Module completion stats for all active cohorts.
Formatted as: X% completion rate this week (vs last week Y%)
7. Summary format
n8n — Slack or email
Compile all data into a single weekly summary message with traffic-light indicators (Green/Amber/Red) applied automatically based on thresholds.
Slack DM or email to founder. Subject: 'Weekly Offer Review — [date] — [overall signal colour]'
PHASE 1
The 20-Minute Review Protocol
Step-by-step with timer allocations — every Monday, without exception
The Protocol Architecture
The 20 minutes is divided into five timed segments. Each segment has a specific set of questions that drive the review. The questions are answered from the dashboard — not from memory, not from gut feel, not from platform reports pulled manually. If the data is not on the dashboard, the answer for this week is 'data not available' and the action is to fix the dashboard, not to spend 10 minutes hunting for the number.
The Timer Rule
Set a 20-minute timer when you open the dashboard. Work with urgency. If you hit a question that would take more than 2 minutes to answer, log it as 'needs deeper review' and continue. The weekly review's job is to scan, signal, and select one action — not to solve problems. Solving happens after the review, in the dedicated blocks assigned to the chosen action.
2 min
Revenue Scan
► Is weekly gross revenue above, below, or in line with the prior week?
► Is weekly gross revenue on track to hit the monthly target at this run rate? (Weekly revenue × 4 vs monthly target)
► Did any offer significantly over- or under-perform vs its prior-week baseline (more than 20% deviation)?
► GREEN if all offers within 20% of prior week. AMBER if one offer is 20%+ below. RED if total weekly revenue is 20%+ below the 4-week average.
4 min
Conversion Health Scan
► Is the cold conversion rate for each active offer within the viable range (above 1.0%)?
► Is the warm conversion rate within the viable range (above 5%)?
► Has either cold or warm conversion declined for two or more consecutive weeks? (Sustained decline is more significant than a single-week dip.)
► Is the email open rate above 28%? Is the click rate above 2%?
► GREEN: all rates within viable range, no sustained decline. AMBER: one rate below viable, or one week of decline. RED: cold conversion below 0.8% OR second consecutive week of 20%+ decline — Forensic Audit trigger.
4 min
Signal Scan (Refunds, Support, Complaints)
► How many refunds were issued this week? What is the rolling 30-day refund rate?
► How many support tickets were opened this week? Is that above or below last week?
► Were any support tickets about the same topic (a pattern emerging)?
► Were any community complaints, negative posts, or escalations flagged this week?
► Is this the first refund on this offer? (Triggers Forensic Audit Phase 5 immediately.)
► GREEN: zero refunds, support normal volume, no patterns. AMBER: 1–2 refunds OR support tickets up 20%+ OR recurring topic in tickets. RED: 3+ refunds in one week OR refund rate above 10% rolling — Forensic Audit trigger.
4 min
Growth Signal Scan
► Were any new testimonials collected this week? Is the testimonial collection rate on track?
► Did any buyers ascend to a higher value ladder tier this week?
► Is completion rate tracking at or above 45% for active cohorts?
► Is there any organic content this week that significantly outperformed baseline (3x+ engagement)?
► Were any new buyer language phrases surfaced this week that could be added to the mining database?
► Note: growth signals do not generate AMBER or RED — they generate opportunities. Log the top opportunity for the priority action selection.
4 min
Paid Traffic Scan (if paid ads active)
► Is the Cost Per Acquisition (CPA) below 33% of the offer price for all active ad campaigns?
► Is any ad set spending above $50/day with a CPA above threshold? (Pause immediately — this is real money leaking in real time.)
► Has the creative performance metric (hook rate / CTR) declined week-over-week, suggesting creative fatigue?
► Is ROAS above 2.0x across all active campaigns?
► GREEN: CPA within target, no creative fatigue, ROAS above 2.0x. AMBER: one campaign above CPA threshold. RED: CPA above 50% of offer price OR total ROAS below 1.5x — pause ad spend immediately, do not wait for audit.
2 min
Priority Action Selection and Documentation
► Based on all five scans: what is the single most important action this week?
► Assign the action an owner (even if that is you) and a deadline (must be before next Monday).
► Are any Forensic Audit triggers fired? If yes: schedule the audit and assign a time block.
► Complete the Weekly Review Record in Airtable (see Phase 5).
► Total time: 20 minutes maximum. Timer stops. Review ends.
PHASE 2
The Signal Classification System
Green, Amber, and Red — what each signal means and what it demands
The Signal Framework
Every metric in the weekly review is classified into one of three signal states: Green (performing within acceptable range — no action required), Amber (underperforming — attention and a targeted action required), or Red (critical underperformance — immediate escalation required). The signal classification is applied automatically by the dashboard where possible, and confirmed by the reviewer during the scan.
The Signal Discipline Rule
A signal is only as useful as the action it triggers. An Amber signal that gets logged and ignored for three weeks in a row is not an Amber — it is a Red that was misclassified. If an Amber signal persists for two consecutive weeks without the action producing improvement, it is reclassified as Red and the escalation protocol fires regardless of the raw numbers.
The Full Signal Matrix
Metric
Green
Amber
Red
Action Triggered
Weekly revenue
Within 15% of prior week and on track for monthly target
15–25% below prior week OR below monthly run rate by 25%
Below 25% of prior week OR below 50% of monthly run rate
Amber: identify single offer causing the drop. Run targeted conversion check. Red: emergency Forensic Audit + paid ad pause if applicable.
Cold conversion rate
Above 1.5%
1.0–1.4%
Below 1.0%
Amber: A/B test new headline variant within 7 days. Red: run Pre-Kill Diagnostic from Kill Criteria SOP within 48 hours.
Warm conversion rate
Above 8%
4–7%
Below 4%
Amber: audit email sequence Days 8–10 (mechanism introduction). Red: full email sequence rebuild triggered.
Email open rate
Above 28%
20–27%
Below 20%
Amber: test 3 new subject line variants for the lowest-performing sequence email. Red: deliverability audit — check sender reputation, spam score, list health.
Refund rate (rolling 30 days)
Below 5%
5–9%
Above 10%
Amber: run Refund Forensics protocol (Forensic Audit SOP Phase 5). Red: Hard Kill pre-threshold signal. Begin Pre-Kill Diagnostic immediately.
Support tickets (weekly count)
Same or below prior week
20–40% above prior week
40%+ above prior week
Amber: identify top ticket topic. Create a self-service FAQ for it. Red: system problem — find and fix the source before more buyers encounter it.
Amber: pause the lowest-performing ad set. Test new creative. Red: pause all paid spend immediately. Do not add fuel to broken vehicle (Hormozi's rule).
Ad ROAS (if paid active)
Above 2.5x
1.5–2.4x
Below 1.5x
Amber: audit audience targeting — check for audience fatigue. Red: immediate paid ad pause. Full creative and offer audit before re-activating.
Ascension rate
More than 2 ascension events in last 30 days
0–1 ascension event in 30 days — check sequence is active
Zero ascension events in 45+ days — sequence failure
Amber: verify ascension email sequence is active and sending. Check CRM automation rules. Red: ascension sequence rebuild required.
PHASE 3
The ONE Priority Action Framework
The rule for selecting exactly one action — and refusing to select more
Why Exactly One
The natural instinct of an operator reviewing metrics is to generate a list: the email open rate needs work, the completion rate is low, the ad CPA is creeping up, and two testimonials were not collected last week. That list becomes this week's project portfolio, nothing gets done with focus, and next Monday the same five things are still underperforming.
The ONE priority action rule breaks this cycle by forcing a hierarchy. One thing, done completely, advances the business more than five things started. Kennedy's implementation rule applies here directly: implement massively on one thing or nothing happens.
The ONE Action Standard
The action must be completable within 7 days by one person. It must be specific enough that a completion state is unambiguous. And it must address the highest-severity signal identified in the review — not the most interesting one, not the most comfortable one, the highest-severity one.
The Priority Action Selection Hierarchy
Apply this hierarchy in order. The first criterion that produces a candidate action is the action for the week. Do not skip to a lower-priority criterion because the higher-priority action feels harder or less interesting.
Priority Level
Condition
Action Directive
Example
P1 — Immediate
A Red signal was identified in any scan — and especially if a Forensic Audit trigger has fired
The priority action is: schedule and complete the specific triggered audit or the specific Red-signal resolution within 7 days. Everything else waits.
Red: cold conversion below 0.8% for second consecutive week. Action: Block 3 hours Tuesday to run the full Forensic Audit. No other work actions this week until the audit is done.
P2 — Escalating Amber
An Amber signal has persisted for two or more consecutive weeks without the prior week's action producing improvement
The Amber is reclassified Red this week. The action is the escalated intervention: if the headline A/B test did not improve open rates, the action is a full sequence rewrite.
Amber (Week 1): email open rate 22%. Action: A/B test subject lines. Amber (Week 2): email open rate 21% — no improvement. Action THIS week: reclassify Red. Full subject line overhaul of top 5 sequence emails.
P3 — New Amber
An Amber signal appeared this week for the first time
The action is the specific targeted fix described in the Signal Matrix for that metric.
New Amber: refund rate at 7%. Action: run Refund Forensics protocol — interview the two refunding buyers within 72 hours. Document root cause codes.
P4 — Green, Growth Opportunity
All signals are Green. No Amber or Red present.
The action is the single highest-leverage growth opportunity identified in the Growth Signal Scan.
All Green. Growth Signal: one organic LinkedIn post generated 3× normal engagement on a specific mechanism angle. Action: write three more posts on that angle this week and track engagement.
The Action Definition Format
Every priority action must be documented in exactly this format before the review ends. Vague actions get delayed. Specific actions get done.
Priority Action Definition Format
ACTION: [Specific, verb-led description of what will be done]
OWNER: [Name of the person responsible — even if that is you]
DEADLINE: [Specific day and time — not 'by Friday,' but 'by Friday 5 PM']
COMPLETION CRITERIA: [How will you know this is done? What is the specific output?]
DOES THIS TRIGGER A DEEPER SOP? [Yes / No — if yes, name the SOP and schedule the session]
Example:
ACTION: A/B test two new headline variants on the MVO sales page targeting the 'spinning wheels' PAIN-ACUTE phrase.
OWNER: [Founder]
DEADLINE: Thursday 5 PM
COMPLETION CRITERIA: Both variants live on Convert.com. UTM parameters set. Baseline conversion rate documented.
DOES THIS TRIGGER A DEEPER SOP? No — if no improvement after 14 days, this triggers the Forensic Audit Loop.
PHASE 4
The Trigger Gate
When the weekly review escalates to a deeper audit — and which SOP fires
The Two-Layer System
The Weekly Offer Review and the Post-MVO Forensic Audit Loop are designed to work together as a two-layer system. The weekly review is the always-on monitor. The Forensic Audit is the precision diagnostic. The Trigger Gate defines the exact conditions that cause the weekly review to hand off to the deeper audit.
The Trigger Gate Table
Trigger
What Fires It
Which SOP
Session Length to Schedule
Urgency
10-Sale Trigger
Weekly review confirms cumulative sale count crossed a multiple of 10 since the last audit
Post-MVO Forensic Audit Loop — Full 8-Phase
2.5–3 hours
Schedule within 72 hours
First Refund Trigger
Weekly Signal Scan identifies the first refund on any offer tier
Post-MVO Forensic Audit Loop — Phases 4 and 5 only (Funnel Diagnostic + Refund Forensics)
45–60 minutes
Schedule within 24 hours
Conversion Drop Trigger
Cold conversion rate has declined 20%+ vs the 30-day average for 7+ consecutive days (visible across two consecutive weekly reviews)
Support tickets above 40% of prior week for two consecutive weeks
Post-MVO Forensic Audit Loop Phase 3 (Buyer Language Mining) + Fulfilment Stress Test if completion rate also declining
60 minutes
Schedule within 1 week
Zombie Offer Signal
Offer has zero new buyers for 60+ consecutive days (visible in weekly revenue scan)
Product Kill Criteria SOP — Zombie Offer Audit
30 minutes
Add to Zombie watchlist. Run Zombie Audit at next quarterly review.
Completion Rate Red Signal (below 30% for 2 weeks)
Completion rate below 30% for two consecutive weekly reviews
Fulfilment Stress Test SOP — Phase 3 (Time-and-Motion Audit)
90 minutes
Schedule within 1 week
Ad ROAS Red Signal (below 1.5x)
Ad ROAS below 1.5x for any active campaign
Paid ad pause immediately (no SOP needed). Product Kill Criteria SOP Pre-Kill Diagnostic if the offer itself may be the problem
30-minute audit + pause
Immediate
The Escalation Commitment
When a Trigger Gate fires, the escalation is non-negotiable. It is not 'I'll try to get to the Forensic Audit this week.' It is 'I am blocking X hours on Y day to run the Forensic Audit, and I am writing that in the Weekly Review Record right now.' Triggers without scheduled time blocks do not get actioned. The weekly review is only as valuable as the escalations it creates.
PHASE 5
The Documentation Protocol
Recording every review — creating the institutional memory that makes every future review smarter
The Weekly Review Record
Every weekly review produces one record in Airtable. The record takes approximately 3–4 minutes to complete — which is why 2 of the 20 minutes are allocated to documentation. A review without a record is a scan without a memory. The accumulated weekly records are the data that reveals trends, validates interventions, and provides the historical baseline for every future review.
Field
Type
What to Document
Review ID
Autonumber
Auto-generated. Format: WOR-[YYYY-MM-DD]
Review Date
Date
The Monday the review was conducted
Offers Reviewed
Link → Offers table
All active offers included in this review
Total Review Duration
Number
Actual minutes taken (target: 20)
Revenue Signal
Single select
Green / Amber / Red
Weekly Revenue
Currency
Total gross revenue this week
Revenue vs Prior Week (%)
Number
Calculated: this week ÷ prior week × 100 − 100
Conversion Signal
Single select
Green / Amber / Red
Cold Conversion Rate
Number
Current week %
Warm Conversion Rate
Number
Current week %
Email Signal
Single select
Green / Amber / Red
Email Open Rate
Number
Average this week %
Email Click Rate
Number
Average this week %
Refund Signal
Single select
Green / Amber / Red
Refunds This Week
Number
Count
Rolling 30-Day Refund Rate
Number
%
Support Signal
Single select
Green / Amber / Red
Support Tickets This Week
Number
Count
Support Ticket Delta vs Prior Week (%)
Number
% change
Top Support Ticket Topic This Week
Short text
Most common topic if pattern exists
Growth Signal (best this week)
Long text
One sentence on the best positive signal observed
Ad Signal (if paid active)
Single select
Green / Amber / Red / N/A
Paid Ad CPA
Currency
Current week average CPA
ROAS
Number
Current week
Overall Review Signal
Single select
All Green / Amber Present / Red Present — triggers Escalation
Triggers Fired
Multiple select
10-Sale / First Refund / Conversion Drop / Refund Rate Red / Support Red / Zombie / Completion Red / Ad ROAS Red / None
When the triggered SOP session is blocked in the calendar
Priority Action This Week
Long text
Full Action Definition Format (Action, Owner, Deadline, Completion Criteria)
Prior Week Action — Completed?
Single select
Yes — fully / Partial / No
Prior Week Action — Outcome
Short text
What happened as a result of last week's action?
Notes
Long text
Anything relevant that does not fit other fields
PHASE 6
The Automation Stack
Building the system that makes the 20-minute review actually possible
The Automation Architecture
Without automation, the 20-minute review becomes a 45-minute data-gathering session followed by 10 minutes of actual review. The automation stack eliminates the data-gathering time entirely. The reviewer arrives at the review to find all metrics pre-calculated, pre-formatted, and colour-coded.
The Sunday Night n8n Workflow
This n8n workflow runs every Sunday at 10 PM. It does not require any human input. It pulls every metric in the dashboard, calculates the week-over-week deltas, applies the Green/Amber/Red signal logic, and formats the output as a Slack message and a Looker Studio data push. When the reviewer opens their dashboard Monday morning, the review is already loaded.
Node #
Node Name
Action
Platform
Output
1
Schedule trigger
Run every Sunday 10 PM local time
n8n cron
Initiates the workflow
2
Stripe revenue pull
Pull all successful charges from Mon–Sun current week and Mon–Sun prior week. Calculate weekly total and delta.
Pull all refunds from current week. Pull all refunds from rolling 30 days. Calculate refund rate.
Stripe API
Refund count, refund rate rolling 30 days
4
CRM conversion pull
Pull new paid contacts tagged this week. Pull unique cold visitors from GA4 (same window). Calculate cold conversion rate.
GoHighLevel API + GA4 Data API
New buyer count, cold conversion rate, warm conversion rate
5
Email metrics pull
Pull aggregate open rate and click rate for all emails sent this week across all active sequences.
ActiveCampaign API
Open rate, click rate, delta vs prior week
6
Support ticket pull
Pull new ticket count this week and prior week. Pull top 3 ticket tags by volume.
Intercom or Help Scout API
Ticket count, delta %, top tags
7
Completion rate pull
Pull module completion percentage for all active cohorts.
Kajabi API
Completion rate per cohort, average
8
Ad metrics pull (if active)
Pull weekly ad spend, CPA per campaign, ROAS per campaign.
Meta Ads API + Google Ads API
CPA, ROAS, spend per campaign
9
Signal classification
Apply Green/Amber/Red thresholds to all pulled metrics. Flag any metrics triggering the Trigger Gate.
n8n code node
Signal colour per metric, list of any fired triggers
10
Looker Studio push
Write formatted data to Google Sheets (connected to Looker Studio dashboard) so dashboard auto-refreshes.
Google Sheets API
Dashboard ready for Monday review
11
Slack/email summary
Format a plain-text weekly summary: overall signal, all metrics, any triggered escalations, prior week action reminder.
Slack API or SMTP
Slack DM or email to founder. Arrives Sunday 10:15 PM.
12
Airtable record creation
Create a new Weekly Review Record in Airtable with all auto-populated fields (the reviewer will complete the remaining fields during the review).
Airtable API
New WOR record created with all pulled metrics pre-filled
The Dashboard Layout (Looker Studio)
The Looker Studio dashboard is organised into five sections matching the five review segments. Each section is visible without scrolling — the entire dashboard fits on one screen. The layout is designed to support a left-to-right scan: Revenue → Conversion → Signals → Growth → Paid.
Dashboard Section
Metrics Displayed
Visual Format
Signal Colour Applied
Revenue (top left)
Weekly gross revenue, buyer count, revenue vs prior week %, revenue vs monthly target %
Large number cards with up/down arrow and colour coding
Gauge charts showing current value vs target range
Green/Amber/Red auto-applied
Signals (top right)
Refund count, rolling refund rate, support ticket count, delta vs prior week, top ticket topic
Number cards with trend sparklines
Green/Amber/Red auto-applied
Growth (bottom left)
New testimonials, ascension events, completion rate, top-performing content piece this week
Simple number cards, no colour coding (growth signals are opportunities, not alerts)
No signal colour — neutral
Paid Traffic (bottom right)
CPA per campaign, ROAS, weekly spend, spend vs budget
Table with row-level colour coding per campaign
Green/Amber/Red per row
PHASE 7
The Multi-Offer Cadence
How to run the weekly review when you have multiple active offers
The Scaling Problem
With one active offer, the 20-minute review is straightforward: one offer, one dashboard, one action. With four or five active offers across multiple value ladder tiers, the review could expand to an hour or more if not structured carefully. The multi-offer cadence solves this without sacrificing the depth of attention each offer deserves.
The Tiered Review Schedule
Offer Tier
Review Frequency
Time Allocated
Rationale
MVO (entry offer — highest buyer volume)
Every Monday — full 5-scan protocol
8–10 minutes
Highest buyer volume means highest signal density. Any problem at this tier cascades through the entire value ladder. It gets the most review time.
Core Offer (primary revenue driver)
Every Monday — abbreviated 3-scan protocol (Revenue, Signals, Conversion only)
5–6 minutes
Primary revenue driver. Must catch problems fast. Abbreviated scan sufficient because volume is lower than MVO.
DWY / High-Ticket (low volume, high value)
Every other Monday — full scan when scheduled
5 minutes on alternate weeks
Low buyer volume means signal density is lower. A biweekly check catches most issues without over-investing review time.
Continuity / MRR
Every Monday — churn-focused scan only (MRR, churn events, support tickets specific to continuity)
3–4 minutes
Churn is the primary metric for continuity. One focused metric check is sufficient. If churn is Red, escalate to a full review.
Bundles and Unbundles (if active)
Every Monday — revenue and conversion only
1–2 minutes each
Bundles generate lower overall volume. A quick revenue/conversion check catches the significant signals without detailed protocol.
Total (with 4 active offers)
20–25 minutes for the full portfolio review
Fits within the 20–30 minute window for a 4-offer business
Scales to approximately 5 minutes per additional active offer above 4, with abbreviated protocols for newer offers.
The Portfolio Offer Rotation Schedule
When the offer portfolio grows beyond four active offers, a rotation schedule ensures every offer receives a deep-scan review at least once every two weeks while keeping the Monday session within 30 minutes.
Week Type
Offers on Full Scan
Offers on Abbreviated Scan
Total Monday Review Time
Week A (odd weeks)
MVO + Core Offer + DWY
Continuity + all Bundles
25 minutes
Week B (even weeks)
MVO + Core Offer + Continuity
DWY + all Bundles
25 minutes
When 5+ active offers
MVO every week. Others rotate on a 2-week cycle.
All non-rotating offers get Revenue + Signals scan only (1 min each)
30 minutes maximum
The Monthly 4-Week Progress Review
Once per month — on the first Monday — the Weekly Offer Review extends to 45 minutes. The additional 25 minutes are used for the Monthly 4-Week Progress Review: a backward look at the four prior weekly reviews to identify trends that are not visible in any single week's data.
Monthly Review Question
What to Look For
Action If Found
Which metrics have been Amber or Red for 2 or more of the last 4 weeks?
A persistent Amber is a systemic problem, not a random fluctuation. Two or more consecutive weeks of the same Amber signal = structural issue.
Escalate to the appropriate SOP immediately. A structural problem does not get solved by a weekly action — it requires a dedicated intervention.
Did any prior week's priority action produce the intended result?
Track action completion and outcome. If an action was completed but produced no improvement, the action was wrong — not the execution.
Log in the action outcome field. Adjust approach for the next action on the same metric.
Which offers showed improvement over the 4-week period?
One strong offer can mask a declining one in weekly revenue. The monthly view reveals which specific offers are on an upward trend.
Double down on the upward-trending offer. Investigate the declining one.
Are any Forensic Audit triggers approaching threshold without having fired?
The conversion drop trigger fires at 20%+ for 7+ days. A conversion that is 15% below baseline for 3 weeks is approaching that threshold.
Pre-schedule a Forensic Audit for the following week before the threshold is formally crossed.
What does the 4-week testimonial trend look like?
Testimonials are a lagging indicator of buyer satisfaction. A declining testimonial collection rate often precedes a rising refund rate by 3–6 weeks.
If testimonial collection has been zero for 4 consecutive weeks: audit the testimonial request protocol in the delivery SOP.
Is the monthly revenue on track relative to the annual plan?
If monthly revenue is below annual plan run rate: escalate to the Forensic Audit Loop's 90-Day Deep Trigger and review value ladder ascension sequences.
Weekly Review Database — Airtable Schema
The Weekly Offer Review records live in a dedicated table within the RISER Nation Master Operating System Airtable base. The schema connects to the Offers table, the Forensic Audit Records table, and the Changelog Entries table.
Table: Weekly Offer Review Records
One record per weekly review. All 31 fields listed in Phase 5 are included. Additional linking fields below:
Linking Field
Links To
Purpose
Forensic Audit Triggered
Link → Forensic Audit Records table
When a Forensic Audit is triggered by this review, link to the resulting audit record once it is completed
Kill Assessment Triggered
Link → Kill Records table
When a Kill Criteria SOP session is triggered by this review, link to the resulting kill record
Mechanism Test Triggered
Link → Mechanism Name Records table
When a 10× test is triggered by a health indicator flag in this review, link to the mechanism test record
Prior Week Review
Link → Weekly Offer Review Records (self)
Link to the prior week's review record for easy comparison navigation
4-Week Rolling Revenue Average
Formula
Average of the last 4 weekly revenue figures — auto-calculated across linked records
Master Weekly Offer Review Checklist
System Setup (One-Time)
☐ Build the Master Metrics Dashboard in Looker Studio connected to all data sources
☐ Build the Sunday night n8n automation workflow (all 12 nodes)
☐ Test the automation: trigger manually and confirm all data pulls correctly
☐ Create Weekly Offer Review Records table in Airtable with all 31 fields
☐ Set up Slack or email destination for Sunday night automated summary
☐ Run the first manual review to establish baseline metrics for all active offers
☐ Document baseline metrics in Airtable as Week 0 record
☐ Set recurring Monday calendar block: 8:30–8:50 AM — Weekly Offer Review (non-negotiable)
Every Monday Review (20 Minutes)
☐ Open the pre-populated dashboard (data should be ready from Sunday night automation)
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — WEEKLY OFFER REVIEW RITUAL ",
"",
"The 20-Minute Monday Protocol That Catches Every Problem Before It Compounds",
"Kennedy × Hormozi × Brunson × 2026 Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"Most operators review their metrics reactively — when something breaks, when a refund arrives, or when an affiliate asks why their conversions dropped. By then, the problem has been compounding for days or weeks. Revenue has leaked. Buyer experience has degraded. And the fix is more expensive than it would have been if the signal had been caught seven days earlier.",
"",
"The Weekly Offer Review Ritual is the 20-minute Monday protocol that changes this. It is not the deep forensic investigation — that is the Post-MVO Forensic Audit Loop, triggered by events and run in 2–3 hour blocks. The weekly review is surveillance: a structured scan of every active offer's health metrics, run before the work week begins, producing exactly one priority action and triggering the appropriate deeper audit when warranted.",
"",
"The critical design constraint is 20 minutes. A review that takes 45 minutes will not happen every week. A review that generates 10 action items will not produce meaningful change. This SOP is built around those two constraints: light enough to be done consistently, focused enough to produce one decision.",
"",
"Kennedy's Measurement Principle",
"If you are not measuring it, you are guessing. And in a direct-response business, guessing is the most expensive operating cost there is. Twenty minutes of structured measurement every Monday is worth more than 20 hours of intuition-based hustle on Thursday.",
"",
"Hormozi's Monitoring Rule",
"The operators who scale fastest are not smarter — they spot the problems and the opportunities sooner. A weekly review is the earliest warning system available. Every week you skip it is a week where a preventable problem compounds into an expensive one.",
"",
"The Surveillance vs Investigation Distinction",
"The Weekly Review is surveillance: a regular, lightweight scan for signals. The Post-MVO Forensic Audit Loop (RISER Nation SOP Series) is investigation: a triggered, deep-dive diagnostic. These two systems work together. The weekly review catches the signal. The forensic audit diagnoses what it means. Never confuse their roles — if you try to do investigation in the weekly slot, the review will take 2 hours and stop happening.",
"",
"How the Weekly Review Connects to the SOP Ecosystem",
"The Weekly Offer Review Ritual is the operational heartbeat of the RISER Nation Master Operating System. It is the mechanism through which every other SOP in the series receives its triggering data. Understanding these connections prevents duplication of effort and ensures each SOP fires at the right moment.",
"",
"Weekly Review Finding",
"SOP It Triggers",
"Trigger Condition",
"What Happens Next",
"Cold conversion rate drops 20%+ for 7+ days",
"Post-MVO Forensic Audit Loop",
"Conversion Drop Trigger threshold met",
"Run full 8-Phase Forensic Audit within 48 hours. Do not change anything until the audit diagnoses the root cause.",
"First refund received on any offer",
"Post-MVO Forensic Audit Loop",
"First Refund Trigger",
"Run Phases 4 and 5 of the Forensic Audit (Funnel Diagnostic + Refund Forensics) within 24 hours. Log in Negative Avatar Profiles database.",
"Cumulative sale count crosses a multiple of 10",
"Post-MVO Forensic Audit Loop",
"10-Sale Trigger",
"Schedule full 8-Phase Audit within 72 hours. This is the most valuable audit — buyer data is fresh.",
"Refund rate crosses 15% in any rolling 7-day window",
"Product Kill Criteria SOP",
"HK-1 Hard Kill pre-threshold signal",
"Pre-alert: if refund rate reaches 20%+ in the same window next week, Hard Kill Trigger fires. Begin Pre-Kill Diagnostic immediately.",
"Mechanism name scores below 7.0 in any informal test during the week",
"10× Mechanism Test & Rename Cadence SOP",
"Event-based trigger: informal score data",
"Schedule formal 10× Test for the coming week. Do not wait for quarterly cadence.",
"Offer has not generated a single sale in 60+ days",
"Product Kill Criteria SOP — Zombie Offer Audit",
"Zombie Criterion 2: zero new buyers in 60+ days",
"Add offer to 30-day remediation watchlist. Implement single highest-leverage change. Re-evaluate in next Monday review.",
"Bundle or unbundle shows cannibalization signal (related offer revenue drops 15%+)",
"Offer Stacking & Unbundling Strategy SOP",
"Cannibalization audit threshold approaching",
"Run the Three Differentiation Tests. If positioning cannot be differentiated — pause the bundle.",
"Completion rate drops below 40% for two consecutive weeks",
"Fulfilment Stress Test SOP",
"Delivery quality signal",
"Run Phase 3 (Time-and-Motion Audit) to check whether fulfilment capacity has been breached.",
"",
"",
"Pre-Review Setup: The Dashboard Architecture",
"The 20-minute time budget only works if every piece of data is pre-loaded and formatted before the review begins. A review that starts with pulling reports from five different platforms will take 45 minutes. The dashboard architecture defines what data must be automatically available at the start of every Monday review.",
"",
"The Master Metrics Dashboard",
"Build this dashboard in Looker Studio, connecting to the data sources listed below. It should load in under 30 seconds and display all metrics for all active offers without any manual data entry. The dashboard is not pulled from — it pushes everything to the reviewer simultaneously.",
"",
"Metric",
"Data Source",
"Formula / Calculation",
"Target",
"Review Frequency",
"Weekly gross revenue",
"Stripe / ThriveCart",
"Sum of all transactions this week (Mon–Sun)",
"vs prior week + vs monthly target ÷ 4",
"Weekly",
"New buyers this week",
"CRM (GoHighLevel)",
"Count of new paid contacts tagged this week",
"vs prior week",
"Weekly",
"Cold conversion rate",
"GA4 + CRM",
"New buyers from cold traffic ÷ unique cold visitors × 100",
"Above 1.0% (viable), above 2.0% (scale signal)",
"Weekly",
"Warm conversion rate",
"Email platform + CRM",
"New buyers from email traffic ÷ email link clicks × 100",
"Above 5% (viable), above 10% (strong)",
"Weekly",
"Email open rate (active sequences)",
"ActiveCampaign",
"Average open rate across all emails sent this week",
"Above 28% (viable)",
"Weekly",
"Email click rate",
"ActiveCampaign",
"Average click rate across all emails sent this week",
"Above 2% (viable)",
"Weekly",
"Refunds this week",
"Stripe / ThriveCart",
"Count and % of refunds in current week",
"0 preferred; above 5% = signal",
"Weekly",
"Support tickets this week",
"Intercom / Help Scout",
"Total new tickets this week",
"vs prior week; above 5 per 10 buyers = signal",
"Weekly",
"Completion rate",
"Course platform (Kajabi)",
"% of active cohort who completed last module or milestone",
"Above 45% (viable)",
"Biweekly",
"New testimonials this week",
"Airtable (Testimonial Registry)",
"Count of new testimonials collected",
"Tracking — no target, just awareness",
"Weekly",
"Ascension events this week",
"CRM pipeline",
"Count of buyers who moved to a higher tier this week",
"vs prior week; target: 8–15% of cohort over 60 days",
"Weekly",
"Ad spend vs revenue (if paid running)",
"Meta/Google Ads + Stripe",
"Weekly ad spend ÷ weekly revenue from paid buyers × 100",
"CPA below 33% of offer price",
"Weekly (if paid active)",
"",
"The Pre-Review Automated Data Pull",
"Every Sunday night at 10 PM, an n8n workflow runs automatically. It pulls the prior week's data from all connected platforms, formats it into the dashboard, and sends a Slack or email summary to the reviewer. When the reviewer opens their laptop on Monday morning, the dashboard is already populated.",
"",
"Workflow Step",
"Platform",
"Data Pulled",
"Format",
"1. Revenue pull",
"Stripe via API",
"All successful charges this week (Mon–Sun). Total revenue, transaction count, average transaction value, refunds issued.",
"Formatted as: This week $X (vs last week $Y, delta Z%)",
"2. Conversion pull",
"GA4 + CRM webhook",
"Unique cold visitors to all offer pages, new buyer tags created this week, source attribution.",
"Formatted as: Cold conversion rate X% (vs last week Y%, delta Z%)",
"3. Email performance pull",
"ActiveCampaign API",
"Open rates, click rates, reply rates for all sequences that sent emails this week.",
"Formatted as: Open rate X%, Click rate Y%",
"4. Support pull",
"Intercom or Help Scout API",
"Ticket count, average first response time, resolved vs open, top 3 ticket topics this week.",
"Formatted as: X tickets (vs last week Y). Top topics: [list]",
"5. Refund pull",
"Stripe API",
"All refunds issued this week, reason codes where available.",
"Formatted as: X refunds ($Y) this week. Root cause codes: [list if tagged]",
"6. Completion pull",
"Kajabi API or manual",
"Module completion stats for all active cohorts.",
"Formatted as: X% completion rate this week (vs last week Y%)",
"7. Summary format",
"n8n — Slack or email",
"Compile all data into a single weekly summary message with traffic-light indicators (Green/Amber/Red) applied automatically based on thresholds.",
"Slack DM or email to founder. Subject: 'Weekly Offer Review — [date] — [overall signal colour]'",
"",
"",
"PHASE 1",
"The 20-Minute Review Protocol",
"Step-by-step with timer allocations — every Monday, without exception",
"",
"The Protocol Architecture",
"The 20 minutes is divided into five timed segments. Each segment has a specific set of questions that drive the review. The questions are answered from the dashboard — not from memory, not from gut feel, not from platform reports pulled manually. If the data is not on the dashboard, the answer for this week is 'data not available' and the action is to fix the dashboard, not to spend 10 minutes hunting for the number.",
"",
"The Timer Rule",
"Set a 20-minute timer when you open the dashboard. Work with urgency. If you hit a question that would take more than 2 minutes to answer, log it as 'needs deeper review' and continue. The weekly review's job is to scan, signal, and select one action — not to solve problems. Solving happens after the review, in the dedicated blocks assigned to the chosen action.",
"",
"2 min",
"Revenue Scan",
"► Is weekly gross revenue above, below, or in line with the prior week?",
"► Is weekly gross revenue on track to hit the monthly target at this run rate? (Weekly revenue × 4 vs monthly target)",
"► Did any offer significantly over- or under-perform vs its prior-week baseline (more than 20% deviation)?",
"► GREEN if all offers within 20% of prior week. AMBER if one offer is 20%+ below. RED if total weekly revenue is 20%+ below the 4-week average.",
"",
"4 min",
"Conversion Health Scan",
"► Is the cold conversion rate for each active offer within the viable range (above 1.0%)?",
"► Is the warm conversion rate within the viable range (above 5%)?",
"► Has either cold or warm conversion declined for two or more consecutive weeks? (Sustained decline is more significant than a single-week dip.)",
"► Is the email open rate above 28%? Is the click rate above 2%?",
"► GREEN: all rates within viable range, no sustained decline. AMBER: one rate below viable, or one week of decline. RED: cold conversion below 0.8% OR second consecutive week of 20%+ decline — Forensic Audit trigger.",
"",
"4 min",
"Signal Scan (Refunds, Support, Complaints)",
"► How many refunds were issued this week? What is the rolling 30-day refund rate?",
"► How many support tickets were opened this week? Is that above or below last week?",
"► Were any support tickets about the same topic (a pattern emerging)?",
"► Were any community complaints, negative posts, or escalations flagged this week?",
"► Is this the first refund on this offer? (Triggers Forensic Audit Phase 5 immediately.)",
"► GREEN: zero refunds, support normal volume, no patterns. AMBER: 1–2 refunds OR support tickets up 20%+ OR recurring topic in tickets. RED: 3+ refunds in one week OR refund rate above 10% rolling — Forensic Audit trigger.",
"",
"4 min",
"Growth Signal Scan",
"► Were any new testimonials collected this week? Is the testimonial collection rate on track?",
"► Did any buyers ascend to a higher value ladder tier this week?",
"► Is completion rate tracking at or above 45% for active cohorts?",
"► Is there any organic content this week that significantly outperformed baseline (3x+ engagement)?",
"► Were any new buyer language phrases surfaced this week that could be added to the mining database?",
"► Note: growth signals do not generate AMBER or RED — they generate opportunities. Log the top opportunity for the priority action selection.",
"",
"4 min",
"Paid Traffic Scan (if paid ads active)",
"► Is the Cost Per Acquisition (CPA) below 33% of the offer price for all active ad campaigns?",
"► Is any ad set spending above $50/day with a CPA above threshold? (Pause immediately — this is real money leaking in real time.)",
"► Has the creative performance metric (hook rate / CTR) declined week-over-week, suggesting creative fatigue?",
"► Is ROAS above 2.0x across all active campaigns?",
"► GREEN: CPA within target, no creative fatigue, ROAS above 2.0x. AMBER: one campaign above CPA threshold. RED: CPA above 50% of offer price OR total ROAS below 1.5x — pause ad spend immediately, do not wait for audit.",
"",
"2 min",
"Priority Action Selection and Documentation",
"► Based on all five scans: what is the single most important action this week?",
"► Assign the action an owner (even if that is you) and a deadline (must be before next Monday).",
"► Are any Forensic Audit triggers fired? If yes: schedule the audit and assign a time block.",
"► Complete the Weekly Review Record in Airtable (see Phase 5).",
"► Total time: 20 minutes maximum. Timer stops. Review ends.",
"",
"",
"PHASE 2",
"The Signal Classification System",
"Green, Amber, and Red — what each signal means and what it demands",
"",
"The Signal Framework",
"Every metric in the weekly review is classified into one of three signal states: Green (performing within acceptable range — no action required), Amber (underperforming — attention and a targeted action required), or Red (critical underperformance — immediate escalation required). The signal classification is applied automatically by the dashboard where possible, and confirmed by the reviewer during the scan.",
"",
"The Signal Discipline Rule",
"A signal is only as useful as the action it triggers. An Amber signal that gets logged and ignored for three weeks in a row is not an Amber — it is a Red that was misclassified. If an Amber signal persists for two consecutive weeks without the action producing improvement, it is reclassified as Red and the escalation protocol fires regardless of the raw numbers.",
"",
"The Full Signal Matrix",
"",
"Metric",
"Green",
"Amber",
"Red",
"Action Triggered",
"Weekly revenue",
"Within 15% of prior week and on track for monthly target",
"15–25% below prior week OR below monthly run rate by 25%",
"Below 25% of prior week OR below 50% of monthly run rate",
"Amber: identify single offer causing the drop. Run targeted conversion check. Red: emergency Forensic Audit + paid ad pause if applicable.",
"Cold conversion rate",
"Above 1.5%",
"1.0–1.4%",
"Below 1.0%",
"Amber: A/B test new headline variant within 7 days. Red: run Pre-Kill Diagnostic from Kill Criteria SOP within 48 hours.",
"Warm conversion rate",
"Above 8%",
"4–7%",
"Below 4%",
"Amber: audit email sequence Days 8–10 (mechanism introduction). Red: full email sequence rebuild triggered.",
"Email open rate",
"Above 28%",
"20–27%",
"Below 20%",
"Amber: test 3 new subject line variants for the lowest-performing sequence email. Red: deliverability audit — check sender reputation, spam score, list health.",
"Refund rate (rolling 30 days)",
"Below 5%",
"5–9%",
"Above 10%",
"Amber: run Refund Forensics protocol (Forensic Audit SOP Phase 5). Red: Hard Kill pre-threshold signal. Begin Pre-Kill Diagnostic immediately.",
"Support tickets (weekly count)",
"Same or below prior week",
"20–40% above prior week",
"40%+ above prior week",
"Amber: identify top ticket topic. Create a self-service FAQ for it. Red: system problem — find and fix the source before more buyers encounter it.",
"Completion rate",
"Above 45%",
"30–44%",
"Below 30%",
"Amber: audit Module 1 completion specifically — add accountability check-in. Red: Fulfilment Stress Test Phase 3 (Time-and-Motion audit) — possible capacity breach.",
"Ad CPA (if paid active)",
"Below 25% of offer price",
"25–40% of offer price",
"Above 40% of offer price",
"Amber: pause the lowest-performing ad set. Test new creative. Red: pause all paid spend immediately. Do not add fuel to broken vehicle (Hormozi's rule).",
"Ad ROAS (if paid active)",
"Above 2.5x",
"1.5–2.4x",
"Below 1.5x",
"Amber: audit audience targeting — check for audience fatigue. Red: immediate paid ad pause. Full creative and offer audit before re-activating.",
"Ascension rate",
"More than 2 ascension events in last 30 days",
"0–1 ascension event in 30 days — check sequence is active",
"Zero ascension events in 45+ days — sequence failure",
"Amber: verify ascension email sequence is active and sending. Check CRM automation rules. Red: ascension sequence rebuild required.",
"",
"",
"PHASE 3",
"The ONE Priority Action Framework",
"The rule for selecting exactly one action — and refusing to select more",
"",
"Why Exactly One",
"The natural instinct of an operator reviewing metrics is to generate a list: the email open rate needs work, the completion rate is low, the ad CPA is creeping up, and two testimonials were not collected last week. That list becomes this week's project portfolio, nothing gets done with focus, and next Monday the same five things are still underperforming.",
"",
"The ONE priority action rule breaks this cycle by forcing a hierarchy. One thing, done completely, advances the business more than five things started. Kennedy's implementation rule applies here directly: implement massively on one thing or nothing happens.",
"",
"The ONE Action Standard",
"The action must be completable within 7 days by one person. It must be specific enough that a completion state is unambiguous. And it must address the highest-severity signal identified in the review — not the most interesting one, not the most comfortable one, the highest-severity one.",
"",
"The Priority Action Selection Hierarchy",
"Apply this hierarchy in order. The first criterion that produces a candidate action is the action for the week. Do not skip to a lower-priority criterion because the higher-priority action feels harder or less interesting.",
"",
"Priority Level",
"Condition",
"Action Directive",
"Example",
"P1 — Immediate",
"A Red signal was identified in any scan — and especially if a Forensic Audit trigger has fired",
"The priority action is: schedule and complete the specific triggered audit or the specific Red-signal resolution within 7 days. Everything else waits.",
"Red: cold conversion below 0.8% for second consecutive week. Action: Block 3 hours Tuesday to run the full Forensic Audit. No other work actions this week until the audit is done.",
"P2 — Escalating Amber",
"An Amber signal has persisted for two or more consecutive weeks without the prior week's action producing improvement",
"The Amber is reclassified Red this week. The action is the escalated intervention: if the headline A/B test did not improve open rates, the action is a full sequence rewrite.",
"Amber (Week 1): email open rate 22%. Action: A/B test subject lines. Amber (Week 2): email open rate 21% — no improvement. Action THIS week: reclassify Red. Full subject line overhaul of top 5 sequence emails.",
"P3 — New Amber",
"An Amber signal appeared this week for the first time",
"The action is the specific targeted fix described in the Signal Matrix for that metric.",
"New Amber: refund rate at 7%. Action: run Refund Forensics protocol — interview the two refunding buyers within 72 hours. Document root cause codes.",
"P4 — Green, Growth Opportunity",
"All signals are Green. No Amber or Red present.",
"The action is the single highest-leverage growth opportunity identified in the Growth Signal Scan.",
"All Green. Growth Signal: one organic LinkedIn post generated 3× normal engagement on a specific mechanism angle. Action: write three more posts on that angle this week and track engagement.",
"",
"The Action Definition Format",
"Every priority action must be documented in exactly this format before the review ends. Vague actions get delayed. Specific actions get done.",
"",
"Priority Action Definition Format",
"ACTION: [Specific, verb-led description of what will be done]\nOWNER: [Name of the person responsible — even if that is you]\nDEADLINE: [Specific day and time — not 'by Friday,' but 'by Friday 5 PM']\nCOMPLETION CRITERIA: [How will you know this is done? What is the specific output?]\nDOES THIS TRIGGER A DEEPER SOP? [Yes / No — if yes, name the SOP and schedule the session]\n\nExample:\nACTION: A/B test two new headline variants on the MVO sales page targeting the 'spinning wheels' PAIN-ACUTE phrase.\nOWNER: [Founder]\nDEADLINE: Thursday 5 PM\nCOMPLETION CRITERIA: Both variants live on Convert.com. UTM parameters set. Baseline conversion rate documented.\nDOES THIS TRIGGER A DEEPER SOP? No — if no improvement after 14 days, this triggers the Forensic Audit Loop.",
"",
"",
"PHASE 4",
"The Trigger Gate",
"When the weekly review escalates to a deeper audit — and which SOP fires",
"",
"The Two-Layer System",
"The Weekly Offer Review and the Post-MVO Forensic Audit Loop are designed to work together as a two-layer system. The weekly review is the always-on monitor. The Forensic Audit is the precision diagnostic. The Trigger Gate defines the exact conditions that cause the weekly review to hand off to the deeper audit.",
"",
"The Trigger Gate Table",
"Trigger",
"What Fires It",
"Which SOP",
"Session Length to Schedule",
"Urgency",
"10-Sale Trigger",
"Weekly review confirms cumulative sale count crossed a multiple of 10 since the last audit",
"Post-MVO Forensic Audit Loop — Full 8-Phase",
"2.5–3 hours",
"Schedule within 72 hours",
"First Refund Trigger",
"Weekly Signal Scan identifies the first refund on any offer tier",
"Post-MVO Forensic Audit Loop — Phases 4 and 5 only (Funnel Diagnostic + Refund Forensics)",
"45–60 minutes",
"Schedule within 24 hours",
"Conversion Drop Trigger",
"Cold conversion rate has declined 20%+ vs the 30-day average for 7+ consecutive days (visible across two consecutive weekly reviews)",
"Post-MVO Forensic Audit Loop — Full 8-Phase",
"2.5–3 hours",
"Schedule within 48 hours",
"Refund Rate Red Signal",
"Rolling 30-day refund rate above 10%",
"Post-MVO Forensic Audit Loop Phase 5 + Product Kill Criteria SOP Pre-Kill Diagnostic",
"90 minutes",
"Schedule within 48 hours",
"Support Ticket Red Signal (40%+ above baseline)",
"Support tickets above 40% of prior week for two consecutive weeks",
"Post-MVO Forensic Audit Loop Phase 3 (Buyer Language Mining) + Fulfilment Stress Test if completion rate also declining",
"60 minutes",
"Schedule within 1 week",
"Zombie Offer Signal",
"Offer has zero new buyers for 60+ consecutive days (visible in weekly revenue scan)",
"Product Kill Criteria SOP — Zombie Offer Audit",
"30 minutes",
"Add to Zombie watchlist. Run Zombie Audit at next quarterly review.",
"Completion Rate Red Signal (below 30% for 2 weeks)",
"Completion rate below 30% for two consecutive weekly reviews",
"Fulfilment Stress Test SOP — Phase 3 (Time-and-Motion Audit)",
"90 minutes",
"Schedule within 1 week",
"Ad ROAS Red Signal (below 1.5x)",
"Ad ROAS below 1.5x for any active campaign",
"Paid ad pause immediately (no SOP needed). Product Kill Criteria SOP Pre-Kill Diagnostic if the offer itself may be the problem",
"30-minute audit + pause",
"Immediate",
"",
"The Escalation Commitment",
"When a Trigger Gate fires, the escalation is non-negotiable. It is not 'I'll try to get to the Forensic Audit this week.' It is 'I am blocking X hours on Y day to run the Forensic Audit, and I am writing that in the Weekly Review Record right now.' Triggers without scheduled time blocks do not get actioned. The weekly review is only as valuable as the escalations it creates.",
"",
"",
"PHASE 5",
"The Documentation Protocol",
"Recording every review — creating the institutional memory that makes every future review smarter",
"",
"The Weekly Review Record",
"Every weekly review produces one record in Airtable. The record takes approximately 3–4 minutes to complete — which is why 2 of the 20 minutes are allocated to documentation. A review without a record is a scan without a memory. The accumulated weekly records are the data that reveals trends, validates interventions, and provides the historical baseline for every future review.",
"",
"Field",
"Type",
"What to Document",
"Review ID",
"Autonumber",
"Auto-generated. Format: WOR-[YYYY-MM-DD]",
"Review Date",
"Date",
"The Monday the review was conducted",
"Offers Reviewed",
"Link → Offers table",
"All active offers included in this review",
"Total Review Duration",
"Number",
"Actual minutes taken (target: 20)",
"Revenue Signal",
"Single select",
"Green / Amber / Red",
"Weekly Revenue",
"Currency",
"Total gross revenue this week",
"Revenue vs Prior Week (%)",
"Number",
"Calculated: this week ÷ prior week × 100 − 100",
"Conversion Signal",
"Single select",
"Green / Amber / Red",
"Cold Conversion Rate",
"Number",
"Current week %",
"Warm Conversion Rate",
"Number",
"Current week %",
"Email Signal",
"Single select",
"Green / Amber / Red",
"Email Open Rate",
"Number",
"Average this week %",
"Email Click Rate",
"Number",
"Average this week %",
"Refund Signal",
"Single select",
"Green / Amber / Red",
"Refunds This Week",
"Number",
"Count",
"Rolling 30-Day Refund Rate",
"Number",
"%",
"Support Signal",
"Single select",
"Green / Amber / Red",
"Support Tickets This Week",
"Number",
"Count",
"Support Ticket Delta vs Prior Week (%)",
"Number",
"% change",
"Top Support Ticket Topic This Week",
"Short text",
"Most common topic if pattern exists",
"Growth Signal (best this week)",
"Long text",
"One sentence on the best positive signal observed",
"Ad Signal (if paid active)",
"Single select",
"Green / Amber / Red / N/A",
"Paid Ad CPA",
"Currency",
"Current week average CPA",
"ROAS",
"Number",
"Current week",
"Overall Review Signal",
"Single select",
"All Green / Amber Present / Red Present — triggers Escalation",
"Triggers Fired",
"Multiple select",
"10-Sale / First Refund / Conversion Drop / Refund Rate Red / Support Red / Zombie / Completion Red / Ad ROAS Red / None",
"Triggered SOP",
"Single select",
"Forensic Audit Loop / Kill Criteria SOP / Fulfilment Stress Test / None",
"Triggered SOP Session Scheduled",
"Date+Time",
"When the triggered SOP session is blocked in the calendar",
"Priority Action This Week",
"Long text",
"Full Action Definition Format (Action, Owner, Deadline, Completion Criteria)",
"Prior Week Action — Completed?",
"Single select",
"Yes — fully / Partial / No",
"Prior Week Action — Outcome",
"Short text",
"What happened as a result of last week's action?",
"Notes",
"Long text",
"Anything relevant that does not fit other fields",
"",
"",
"PHASE 6",
"The Automation Stack",
"Building the system that makes the 20-minute review actually possible",
"",
"The Automation Architecture",
"Without automation, the 20-minute review becomes a 45-minute data-gathering session followed by 10 minutes of actual review. The automation stack eliminates the data-gathering time entirely. The reviewer arrives at the review to find all metrics pre-calculated, pre-formatted, and colour-coded.",
"",
"The Sunday Night n8n Workflow",
"This n8n workflow runs every Sunday at 10 PM. It does not require any human input. It pulls every metric in the dashboard, calculates the week-over-week deltas, applies the Green/Amber/Red signal logic, and formats the output as a Slack message and a Looker Studio data push. When the reviewer opens their dashboard Monday morning, the review is already loaded.",
"",
"Node #",
"Node Name",
"Action",
"Platform",
"Output",
"1",
"Schedule trigger",
"Run every Sunday 10 PM local time",
"n8n cron",
"Initiates the workflow",
"2",
"Stripe revenue pull",
"Pull all successful charges from Mon–Sun current week and Mon–Sun prior week. Calculate weekly total and delta.",
"Stripe API",
"Weekly revenue current, weekly revenue prior, delta %",
"3",
"Stripe refund pull",
"Pull all refunds from current week. Pull all refunds from rolling 30 days. Calculate refund rate.",
"Stripe API",
"Refund count, refund rate rolling 30 days",
"4",
"CRM conversion pull",
"Pull new paid contacts tagged this week. Pull unique cold visitors from GA4 (same window). Calculate cold conversion rate.",
"GoHighLevel API + GA4 Data API",
"New buyer count, cold conversion rate, warm conversion rate",
"5",
"Email metrics pull",
"Pull aggregate open rate and click rate for all emails sent this week across all active sequences.",
"ActiveCampaign API",
"Open rate, click rate, delta vs prior week",
"6",
"Support ticket pull",
"Pull new ticket count this week and prior week. Pull top 3 ticket tags by volume.",
"Intercom or Help Scout API",
"Ticket count, delta %, top tags",
"7",
"Completion rate pull",
"Pull module completion percentage for all active cohorts.",
"Kajabi API",
"Completion rate per cohort, average",
"8",
"Ad metrics pull (if active)",
"Pull weekly ad spend, CPA per campaign, ROAS per campaign.",
"Meta Ads API + Google Ads API",
"CPA, ROAS, spend per campaign",
"9",
"Signal classification",
"Apply Green/Amber/Red thresholds to all pulled metrics. Flag any metrics triggering the Trigger Gate.",
"n8n code node",
"Signal colour per metric, list of any fired triggers",
"10",
"Looker Studio push",
"Write formatted data to Google Sheets (connected to Looker Studio dashboard) so dashboard auto-refreshes.",
"Google Sheets API",
"Dashboard ready for Monday review",
"11",
"Slack/email summary",
"Format a plain-text weekly summary: overall signal, all metrics, any triggered escalations, prior week action reminder.",
"Slack API or SMTP",
"Slack DM or email to founder. Arrives Sunday 10:15 PM.",
"12",
"Airtable record creation",
"Create a new Weekly Review Record in Airtable with all auto-populated fields (the reviewer will complete the remaining fields during the review).",
"Airtable API",
"New WOR record created with all pulled metrics pre-filled",
"",
"The Dashboard Layout (Looker Studio)",
"The Looker Studio dashboard is organised into five sections matching the five review segments. Each section is visible without scrolling — the entire dashboard fits on one screen. The layout is designed to support a left-to-right scan: Revenue → Conversion → Signals → Growth → Paid.",
"",
"Dashboard Section",
"Metrics Displayed",
"Visual Format",
"Signal Colour Applied",
"Revenue (top left)",
"Weekly gross revenue, buyer count, revenue vs prior week %, revenue vs monthly target %",
"Large number cards with up/down arrow and colour coding",
"Green/Amber/Red auto-applied based on thresholds",
"Conversion (top middle)",
"Cold conversion rate, warm conversion rate, email open rate, email click rate",
"Gauge charts showing current value vs target range",
"Green/Amber/Red auto-applied",
"Signals (top right)",
"Refund count, rolling refund rate, support ticket count, delta vs prior week, top ticket topic",
"Number cards with trend sparklines",
"Green/Amber/Red auto-applied",
"Growth (bottom left)",
"New testimonials, ascension events, completion rate, top-performing content piece this week",
"Simple number cards, no colour coding (growth signals are opportunities, not alerts)",
"No signal colour — neutral",
"Paid Traffic (bottom right)",
"CPA per campaign, ROAS, weekly spend, spend vs budget",
"Table with row-level colour coding per campaign",
"Green/Amber/Red per row",
"",
"",
"PHASE 7",
"The Multi-Offer Cadence",
"How to run the weekly review when you have multiple active offers",
"",
"The Scaling Problem",
"With one active offer, the 20-minute review is straightforward: one offer, one dashboard, one action. With four or five active offers across multiple value ladder tiers, the review could expand to an hour or more if not structured carefully. The multi-offer cadence solves this without sacrificing the depth of attention each offer deserves.",
"",
"The Tiered Review Schedule",
"Offer Tier",
"Review Frequency",
"Time Allocated",
"Rationale",
"MVO (entry offer — highest buyer volume)",
"Every Monday — full 5-scan protocol",
"8–10 minutes",
"Highest buyer volume means highest signal density. Any problem at this tier cascades through the entire value ladder. It gets the most review time.",
"Core Offer (primary revenue driver)",
"Every Monday — abbreviated 3-scan protocol (Revenue, Signals, Conversion only)",
"5–6 minutes",
"Primary revenue driver. Must catch problems fast. Abbreviated scan sufficient because volume is lower than MVO.",
"DWY / High-Ticket (low volume, high value)",
"Every other Monday — full scan when scheduled",
"5 minutes on alternate weeks",
"Low buyer volume means signal density is lower. A biweekly check catches most issues without over-investing review time.",
"Continuity / MRR",
"Every Monday — churn-focused scan only (MRR, churn events, support tickets specific to continuity)",
"3–4 minutes",
"Churn is the primary metric for continuity. One focused metric check is sufficient. If churn is Red, escalate to a full review.",
"Bundles and Unbundles (if active)",
"Every Monday — revenue and conversion only",
"1–2 minutes each",
"Bundles generate lower overall volume. A quick revenue/conversion check catches the significant signals without detailed protocol.",
"Total (with 4 active offers)",
"20–25 minutes for the full portfolio review",
"Fits within the 20–30 minute window for a 4-offer business",
"Scales to approximately 5 minutes per additional active offer above 4, with abbreviated protocols for newer offers.",
"",
"The Portfolio Offer Rotation Schedule",
"When the offer portfolio grows beyond four active offers, a rotation schedule ensures every offer receives a deep-scan review at least once every two weeks while keeping the Monday session within 30 minutes.",
"",
"Week Type",
"Offers on Full Scan",
"Offers on Abbreviated Scan",
"Total Monday Review Time",
"Week A (odd weeks)",
"MVO + Core Offer + DWY",
"Continuity + all Bundles",
"25 minutes",
"Week B (even weeks)",
"MVO + Core Offer + Continuity",
"DWY + all Bundles",
"25 minutes",
"When 5+ active offers",
"MVO every week. Others rotate on a 2-week cycle.",
"All non-rotating offers get Revenue + Signals scan only (1 min each)",
"30 minutes maximum",
"",
"",
"The Monthly 4-Week Progress Review",
"Once per month — on the first Monday — the Weekly Offer Review extends to 45 minutes. The additional 25 minutes are used for the Monthly 4-Week Progress Review: a backward look at the four prior weekly reviews to identify trends that are not visible in any single week's data.",
"",
"Monthly Review Question",
"What to Look For",
"Action If Found",
"Which metrics have been Amber or Red for 2 or more of the last 4 weeks?",
"A persistent Amber is a systemic problem, not a random fluctuation. Two or more consecutive weeks of the same Amber signal = structural issue.",
"Escalate to the appropriate SOP immediately. A structural problem does not get solved by a weekly action — it requires a dedicated intervention.",
"Did any prior week's priority action produce the intended result?",
"Track action completion and outcome. If an action was completed but produced no improvement, the action was wrong — not the execution.",
"Log in the action outcome field. Adjust approach for the next action on the same metric.",
"Which offers showed improvement over the 4-week period?",
"One strong offer can mask a declining one in weekly revenue. The monthly view reveals which specific offers are on an upward trend.",
"Double down on the upward-trending offer. Investigate the declining one.",
"Are any Forensic Audit triggers approaching threshold without having fired?",
"The conversion drop trigger fires at 20%+ for 7+ days. A conversion that is 15% below baseline for 3 weeks is approaching that threshold.",
"Pre-schedule a Forensic Audit for the following week before the threshold is formally crossed.",
"What does the 4-week testimonial trend look like?",
"Testimonials are a lagging indicator of buyer satisfaction. A declining testimonial collection rate often precedes a rising refund rate by 3–6 weeks.",
"If testimonial collection has been zero for 4 consecutive weeks: audit the testimonial request protocol in the delivery SOP.",
"Is the monthly revenue on track relative to the annual plan?",
"Weekly reviews catch weekly problems. Monthly reviews catch quarterly trends.",
"If monthly revenue is below annual plan run rate: escalate to the Forensic Audit Loop's 90-Day Deep Trigger and review value ladder ascension sequences.",
"",
"",
"Weekly Review Database — Airtable Schema",
"The Weekly Offer Review records live in a dedicated table within the RISER Nation Master Operating System Airtable base. The schema connects to the Offers table, the Forensic Audit Records table, and the Changelog Entries table.",
"",
"Table: Weekly Offer Review Records",
"One record per weekly review. All 31 fields listed in Phase 5 are included. Additional linking fields below:",
"",
"Linking Field",
"Links To",
"Purpose",
"Forensic Audit Triggered",
"Link → Forensic Audit Records table",
"When a Forensic Audit is triggered by this review, link to the resulting audit record once it is completed",
"Kill Assessment Triggered",
"Link → Kill Records table",
"When a Kill Criteria SOP session is triggered by this review, link to the resulting kill record",
"Mechanism Test Triggered",
"Link → Mechanism Name Records table",
"When a 10× test is triggered by a health indicator flag in this review, link to the mechanism test record",
"Prior Week Review",
"Link → Weekly Offer Review Records (self)",
"Link to the prior week's review record for easy comparison navigation",
"4-Week Rolling Revenue Average",
"Formula",
"Average of the last 4 weekly revenue figures — auto-calculated across linked records",
"",
"",
"Master Weekly Offer Review Checklist",
"",
"System Setup (One-Time)",
"☐ Build the Master Metrics Dashboard in Looker Studio connected to all data sources",
"☐ Build the Sunday night n8n automation workflow (all 12 nodes)",
"☐ Test the automation: trigger manually and confirm all data pulls correctly",
"☐ Create Weekly Offer Review Records table in Airtable with all 31 fields",
"☐ Set up Slack or email destination for Sunday night automated summary",
"☐ Run the first manual review to establish baseline metrics for all active offers",
"☐ Document baseline metrics in Airtable as Week 0 record",
"☐ Set recurring Monday calendar block: 8:30–8:50 AM — Weekly Offer Review (non-negotiable)",
"",
"Every Monday Review (20 Minutes)",
"☐ Open the pre-populated dashboard (data should be ready from Sunday night automation)",
"☐ Set 20-minute timer",
"☐ Segment 1 (2 min): Revenue Scan — classify Green/Amber/Red",
"☐ Segment 2 (4 min): Conversion Health Scan — classify Green/Amber/Red",
"☐ Segment 3 (4 min): Signal Scan (Refunds, Support, Complaints) — classify Green/Amber/Red",
"☐ Segment 4 (4 min): Growth Signal Scan — note best growth opportunity",
"☐ Segment 5 (4 min): Paid Traffic Scan (if active) — classify Green/Amber/Red",
"☐ Segment 6 (2 min): Priority Action Selection — one action, Action Definition Format filled in",
"☐ Apply Priority Action Hierarchy: P1 Red signals first, P2 escalating Amber, P3 new Amber, P4 growth opportunity",
"☐ Check Trigger Gate: did any Trigger fire? If yes: schedule the triggered SOP session NOW, before closing the review",
"☐ Complete Weekly Review Record in Airtable — all metrics and the priority action documented",
"☐ Timer stops. Review ends. Close the dashboard.",
"",
"Monthly 4-Week Progress Review (first Monday — extends to 45 minutes)",
"☐ Run the standard 20-minute review first",
"☐ Pull the prior 4 weekly review records from Airtable",
"☐ Answer all 6 Monthly Review Questions",
"☐ Identify any persistent Amber signals (2+ consecutive weeks) — escalate to appropriate SOP",
"☐ Review all prior month priority actions: completed? Did they work?",
"☐ Check testimonial collection trend — zero for 4 weeks triggers delivery SOP review",
"☐ Check monthly revenue vs annual plan run rate",
"☐ Document monthly findings in the first Monday's Weekly Review Record under Notes field",
"",
"Ongoing Discipline Rules",
"☐ The review is never skipped. If Monday is a holiday, it runs Tuesday. Not the following Monday.",
"☐ The timer runs. If 20 minutes is up and the action is not selected, select it in the next 2 minutes — do not extend the review indefinitely.",
"☐ The action is always one. If you find yourself selecting two actions, apply the Priority Action Hierarchy and cut one.",
"☐ If the automation fails and the dashboard is not ready: do not skip the review. Run it from raw platform dashboards in 30 minutes.",
"☐ Every Trigger Gate escalation gets a calendar block before the review ends. Not 'I'll schedule it later.'",
"",
"",
"",
"RISER Nation Master Operating System | Weekly Offer Review Ritual SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | Weekly Offer Review Ritual SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
},
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Assess an underperforming offer and preserve what the evidence teaches
Separate the next decision from the past investment
Imagine an operator reluctant to review an offer after months of work. This is an illustrative scene. The time already spent feels like a reason to keep investing, even though the next buyer’s experience and the next use of resources are separate questions.
This source proposes a system for reviewing an offer after launch: diagnose, check urgent conditions, score, choose a response, preserve records and consider any future version. Its repeated instruction to kill an offer means retiring that offer, not deleting its evidence or abandoning existing buyers.
The source attributes rules to Kennedy, Hormozi and Brunson about learning from failed offers and improving the offer before adding traffic. The quoted-style attributions, $50,000-versus-$5,000 example and claims about successful operators are not independently substantiated here. The relevant teaching theme is to connect the promise, delivery, evidence and offer ladder rather than treat more promotion as a solution to every problem.
This is source-based curriculum instruction, not a recommendation to close a real business, change advertising, issue refunds or send emails. The original operational instructions remain study material. The thresholds contain conflicts and are not a universally validated decision system.
Identify six forms of sunk-cost reasoning
The table distinguishes prior time, identity attachment, praise without purchases, repeated optimism, existing testimonials and money already spent on ads. For each, ask what future decision the available evidence supports. Preserve useful expertise and truthful records without assuming the current format must survive.
Sunk Cost Bias
How It Manifests
The Rational Counter
Time investment bias
'I spent 3 months building this. I can't just kill it.'
The 3 months are gone regardless of what you decide today. The only question is whether the next 3 months goes into a working offer or a broken one.
Identity attachment
'This offer represents my core methodology. Killing it feels like killing part of myself.'
The methodology survives the offer. Rename the mechanism. Repackage the IP. Kill the specific execution that is not working — not the expertise behind it.
Audience validation hunger
'People say they love this offer even if they're not buying.'
Compliments are not revenue. Kennedy: 'Validate with dollars, not compliments.' If the audience loves it and will not pay for it, the market has spoken.
Optimism bias
'I just need to fix one more thing and it will work.'
Define in advance what 'one more thing' means. If you have already made three 'one more thing' changes and the metrics have not moved, the problem is structural — not fixable with incremental iteration.
Social proof protection
'I have testimonials from this offer. If I kill it, I lose the social proof.'
Testimonials belong to the buyer and the result, not the offer format. Testimonials from a killed offer can be repurposed in a new, better offer that serves the same transformation.
Sunken ad spend
'I've spent $8K in ads to prove this. I need to recoup that before stopping.'
The $8K is already spent. Continuing to run an unworkable offer to recoup sunk ad cost will result in spending $16K to prove what $8K already proved. Cut the loss now.
The source proposes setting thresholds before launch and retaining them in a record. That can make the intended review criteria visible. It does not justify following a flawed rule after contradictory evidence appears. Three unsuccessful changes do not prove a structural cause. Praise without purchases does not by itself identify why people did not buy. Reusing testimonials requires accurate context; later source salvage rules are narrower than this opening discussion.
Match the review to the offer’s stage
The source distinguishes launch, validation, traction, scale and decline. Read all dates and stage evidence below. Calendar age alone does not prove an offer is declining, and day 180 belongs to both the stated scale and decline ranges.
Stage 1 Launch Days 1–14 Proof of market response
Stage 2 Validation Days 15–45 Conversion rate signal
Stage 3 Traction Days 46–90 Unit economics viability
Stage 4 Scale Days 91–180 Paid traffic profitability
Stage 5 Decline 180+ days Renewal and ascension rate
Stage
Primary Question
Key Metric
Decision at This Stage
Stage 1 — Launch (Days 1–14)
Is anyone responding to this offer at all?
First sale: did any paying buyers emerge without heavy persuasion from a warm audience within 14 days?
If zero sales from a warm list of 500+ after a proper 7-day launch sequence: trigger Stage 1 Kill Assessment. Do not move to paid ads.
Stage 2 — Validation (Days 15–45)
Is the conversion rate statistically viable for the offer type?
Cold conversion rate after 200+ unique visitors. Warm conversion rate after full email sequence delivery to warm list.
If cold conversion remains below threshold after 300+ visitors and one round of copy iteration: trigger Full Kill Assessment (Phase 3 scorecard).
Stage 3 — Traction (Days 46–90)
Do the unit economics work?
Cost Per Acquisition vs. Offer Price ratio. Refund rate. Support cost per buyer. LTV:CAC ratio.
If unit economics fail the Stage 3 thresholds after genuine traffic investment: trigger Full Kill Assessment. Do not scale.
Stage 4 — Scale (Days 91–180)
Is this offer still working as ad spend increases?
ROAS by platform. CPA trend (improving, flat, or worsening). Ascension rate to next tier.
If ROAS declines below 2.0x and CPA exceeds 35% of offer price for 21+ consecutive days: trigger Scale-to-Iterate or Kill decision.
If revenue has declined 40% from peak for 60+ consecutive days with no identifiable external cause: trigger Full Kill Assessment or Relaunch Protocol.
Launch asks about response from a warm audience; validation asks about conversion evidence; traction examines acquisition, refund and support economics; scale considers paid performance and advancement; decline examines a sustained revenue change and possible outside causes.
The launch assessment names a seven-day sequence, while the later hard trigger uses fourteen days. Validation mentions two hundred visitors and then three hundred after copy work. Neither count guarantees statistical significance. Preserve the sample, conversion count and observation window rather than treating any smaller sample as meaningless or any larger one as conclusive.
Phase 1 — Examine six fixable problems
Before the ordinary scorecard, the source asks whether traffic is sufficient, traffic awareness matches the page, headlines were tested, the email sequence was completed, a guarantee was tested and the offer stack was clearly presented. These are different hypotheses. A weak result does not establish which hypothesis is correct.
Fixable Cause
Diagnostic Question
Evidence That This Is the Problem
Minimum Fix & Retest Window
Traffic volume insufficient
Have at least 200 unique cold visitors seen this offer (300+ preferred for statistical significance)?
Conversion rate data is based on fewer than 200 unique cold visitors. Any rate below 200 visits is noise, not signal.
Drive 200+ unique visitors through organic promotion or minimal paid spend ($300–$500 test budget) before assessing cold conversion rate.
Traffic source mismatch
Is the traffic source aligned with the awareness level the offer page assumes?
Cold traffic is landing on a page written for warm or hot traffic. Sales page assumes prior relationship or context the visitor does not have.
Audit the first 500 words of the sales page for assumed context. Rewrite the lead assuming zero prior awareness. Retest for 7 days.
Copy — headline not tested
Has the headline been A/B tested with at least 2 meaningfully different angles?
Single headline has been running since launch. No split test data.
Write 3 headline variants (pain hook, desire hook, mechanism hook). Run split test for minimum 14 days or 200 visitors per variant. Decision only after test concludes.
Email sequence — not complete or not deployed
Has the full 14-day email sequence been deployed to the warm list?
Fewer than 10 emails have been sent, or the sequence was stopped early, or the list size was fewer than 200 subscribers.
Complete the full 14-day sequence to a list of 200+ subscribers. Assess warm conversion rate after the sequence concludes.
Guarantee — not sufficiently strong
Has a meaningful guarantee been tested against the current version?
Current guarantee is a basic 30-day money-back with no conditions or commitment language. Has never been upgraded.
Test the Level 3 guarantee (result-based conditional) against current guarantee for 14 days. If conversion lifts 15%+ — guarantee was the problem, not the offer.
Offer stack — not presented clearly
Has the full value stack (bonuses, mechanism, deliverables, guarantee, social proof) been tested in the Brunson Stack Slide format?
Sales page does not have a visual offer stack with individual bonus values listed. The offer is described narratively without a stacked presentation.
Rebuild the sales page's offer section as a Stack Slide: list each component, assign a standalone value, show total value vs. asking price. Retest for 14 days.
Diagnostic Item
Status
Retest Window
Cleared?
Minimum 200 unique cold visitors have seen the offer
Full 14-day email sequence deployed to 200+ warm subscribers
☐ Yes ☐ Not yet
Deploy and wait for sequence to complete
☐
Level 3 guarantee tested against current guarantee
☐ Yes ☐ Not yet
14 days split test
☐
Stack Slide offer presentation tested
☐ Yes ☐ Not yet
14 days after implementation
☐
For traffic fit, the source proposes reviewing the first five hundred words for assumed familiarity. For headlines, it asks for at least two angles but then suggests three variants: pain, desire and mechanism. Its fourteen-day-or-two-hundred-visitors wording differs from later minimum-duration and sample requirements. Record the actual test conditions rather than silently choosing an interpretation.
The guarantee example calls a conditional result-based guarantee Level 3 and proposes a fourteen-day test. The full guarantee framework is a separate dependency; a measured lift alone does not isolate cause. The Stack Slide requires a component list and stated values, but those values need a defensible basis. The $300–$500 traffic test is a source proposal, not spending authorized by this lesson.
The instruction to finish every diagnostic before assessment must be read alongside urgent exceptions. Waiting for sample size or an experiment cannot be used to ignore evidence that an offer is undeliverable or causing an identified problem.
Phase 2 — Read all seven hard-trigger conditions precisely
The source labels these automatic, but its own timelines and consequences vary. Preserve each threshold, qualifying sample and proposed response in the original table.
Trigger
Threshold
Rationale
Action Timeline
HK-1: Catastrophic refund rate
Refund rate exceeds 30% of total sales after a minimum of 20 sales
A refund rate above 30% indicates a systematic failure in promise delivery or a fundamental mismatch between what was sold and what was received. This is not fixable with copy changes — the offer is broken at the product level.
Kill within 48 hours. Pause all ads immediately. Begin Post-Kill Protocol.
HK-2: Legal or compliance violation identified
Any confirmed violation of FTC guidelines, TCPA regulations, platform terms of service, or applicable consumer protection law
Legal exposure compounds exponentially the longer a non-compliant offer remains live. Compliance violations can result in platform bans, financial penalties, and reputational damage that far exceeds any revenue from the offer.
Kill within 24 hours. Consult legal counsel before relaunch. Do not attempt to fix and relaunch without written legal clearance.
HK-3: Fulfilment breakdown — unable to deliver
You are materially unable to deliver the core promise of the offer to existing or new buyers
Continuing to sell an offer you cannot deliver is both legally and ethically indefensible. Fulfilment breakdown triggers immediate offer suspension, not iteration.
Suspend new sales within 24 hours. Communicate with existing buyers within 48 hours. Full refund offered to all buyers unable to receive delivery.
HK-4: Zero warm conversion after complete sequence
Zero sales from a warm list of 500+ after a full 14-day email sequence has been deployed, with at least 25% open rate confirmed
A 25%+ open rate confirms the sequence was read. Zero purchases from 500+ warm subscribers who read the sequence means the offer is rejected by people who know, like, and trust you. This is the harshest market signal available.
Kill within 7 days. Do not move to cold paid traffic. Begin Post-Kill Protocol.
HK-5: Cold conversion remains below 0.3% after diagnostic complete
Cold conversion rate remains below 0.3% after all six Pre-Kill Diagnostic fixes have been applied and retested over a minimum of 300 unique cold visitors
0.3% is the absolute floor for any offer that can ever be made profitable through paid advertising. Below 0.3% with a clean diagnosis means the offer itself is the problem — not the copy, not the traffic.
Kill within 14 days of confirmed diagnostic completion. Do not spend further on ads.
HK-6: Negative NPS after 20+ responses
Net Promoter Score falls below -10 after a minimum of 20 buyer survey responses
An NPS below -10 means your detractors significantly outnumber your promoters. This offer is actively generating negative word-of-mouth at a rate that will compound against every future launch.
Kill within 7 days of confirmed NPS threshold. Conduct emergency buyer interviews. Do not run this offer again without rebuilding from scratch.
HK-7: CPA exceeds 60% of offer price after $3,000+ ad spend
Cost Per Acquisition exceeds 60% of the offer's sale price after at least $3,000 has been spent testing across at least 2 different audience types
At a CPA of 60% of revenue, there is no viable business. After refunds, fulfilment costs, and payment processing fees, the unit economics are deeply negative and cannot be corrected by optimising an offer that the market is systematically rejecting.
Kill paid spend immediately. Offer may continue organically if organic conversion is strong. If organic also fails, full kill.
HK1: this document uses refunds exceeding thirty percent after at least twenty sales. The Weekly Review refers to a twenty-percent next-week hard-trigger warning. Those do not describe the same rule. The numerator, buyer cohort and refund window must also be specified.
HK2 and HK3: the source names legal, platform and delivery issues, with different suspension, communication and review steps. These statements do not establish current law or a finding about a real offer. Any actual legal or platform assessment requires appropriate current evidence; the source’s named regimes and written-clearance instruction are not a substitute for that assessment.
HK4: a twenty-five-percent open rate does not prove that every one of five hundred subscribers read the sequence. Zero recorded purchases also does not isolate the cause. HK5: conversion below 0.3 percent is not universally unprofitable independently of price, cost and subsequent revenue. HK6: the specified NPS response count and threshold are a source rule, not proof of the views of every buyer.
HK7: the row permits organic continuation if it works, even while stopping paid activity. That is different from closing the whole offer. CPA at sixty percent of price alone does not establish all unit economics. The introduction’s immediate/forty-eight-hour wording conflicts with rows allowing twenty-four hours, seven days or fourteen days. Keep each scope explicit.
Phase 3 — Use the fifteen-dimension, sixty-point scorecard
Each dimension here runs from zero to four, for a total from zero to sixty. The monthly scorecard uses one to five and a maximum of seventy-five. Weekly colors are a third system. None can be substituted for the other.
Read every band in the table. Preserve raw measurements and unresolved boundaries beside the assigned score.
Dimension
0 Points — Critical Failure
1 Point — Below Viable
2 Points — Viable
3 Points — Strong
4 Points — Excellent
Your Score
Cold conversion rate
Below 0.5%
0.5–0.9%
1.0–1.9%
2.0–3.9%
4.0%+
___
Warm conversion rate
Below 2%
2–4%
5–9%
10–19%
20%+
___
Refund rate
Above 20%
15–20%
8–14%
3–7%
Below 3%
___
Programme completion rate
Below 25%
25–44%
45–59%
60–74%
75%+
___
Specific result testimonials (per 10 buyers)
0
1
2–3
4–5
6+
___
Email open rate (14-day sequence)
Below 15%
15–19%
20–29%
30–39%
40%+
___
Support tickets per buyer (per 30 days)
Above 8
5–8
3–4
1–2
0–1
___
CPA as % of offer price
Above 50%
40–50%
25–39%
15–24%
Below 15%
___
Ascension rate to next tier
Below 3%
3–5%
6–9%
10–14%
15%+
___
Buyer NPS score
Below -10
–10 to 0
1–20
21–40
41+
___
Month-over-month revenue trend
Declining >20%
Declining 5–20%
Flat (±5%)
Growing 5–19%
Growing 20%+
___
Value Equation audit — Dream Outcome score
1–2 (broken)
3–4 (weak)
5–6 (adequate)
7–8 (strong)
9–10 (excellent)
___
Value Equation audit — Perceived Likelihood score
1–2 (broken)
3–4 (weak)
5–6 (adequate)
7–8 (strong)
9–10 (excellent)
___
Value Equation audit — Time Delay score
1–2 (broken)
3–4 (weak)
5–6 (adequate)
7–8 (strong)
9–10 (excellent)
___
Value Equation audit — Effort & Sacrifice score
1–2 (broken)
3–4 (weak)
5–6 (adequate)
7–8 (strong)
9–10 (excellent)
___
Cold and warm conversion: keep source populations and attribution separate. The fractional gaps between some bands need a precision rule. Refunds and completion: define buyer cohort and delivery milestone before comparing rates; requests, processed refunds and completed programs are not automatically equivalent measures.
Testimonials: the source normalizes specific-result testimonials per ten buyers, but does not explain rounding or small cohorts. Use truthful, documented results. Email opens: retain the fourteen-day sequence scope and aggregation method; an open is not proof of comprehension.
Support: the bands zero-to-one and one-to-two overlap at one ticket. The period here is thirty days, unlike the monthly scorecard’s weekly support dimension. CPA: preserve price and campaign definitions rather than comparing gross revenue ratios as if they were identical. Ascension: the window and cohort are not fully specified in this row.
NPS: retain the response count and method; do not infer representativeness from a score. Revenue trend: the plus-or-minus-five-percent flat band overlaps growing or declining five percent. A trend is an observation, not a causal diagnosis.
Four Value Equation audit dimensions: the source maps one-to-ten ratings of Dream Outcome, Perceived Likelihood, Time Delay, and Effort/Sacrifice into zero-to-four points. It does not provide their full rating rubric here. Clarify that a favorable rating for delay or effort concerns reduced burden; do not invent source scores from the dimension names. The treatment of missing data is also unspecified.
Read the qualifiers as well as the total
The four decision panels below include conditions beyond the sum. Their proposed operating actions remain source content.
KILL Score 0–24 (out of 60) — or any Hard Kill Trigger fired regardless of score The offer has failed across multiple dimensions and cannot be fixed through incremental iteration. The structural problems are too numerous or too deep. Kill the offer using the Clean Kill Process (Phase 5). Extract all intelligence using the Post-Kill Protocol (Phase 6).
PIVOT Score 25–34 — with 3 or more dimensions at 0 or 1 The core premise or mechanism may be viable but the execution is failing broadly. Iteration will not fix this — it requires a structural change to the offer format, the target avatar, the pricing tier, or the delivery mechanism. A pivot is not a kill — it is a rebuild that preserves the underlying insight.
ITERATE Score 35–44 — with no more than 2 dimensions at 0 or 1 Specific, diagnosable problems exist but the offer has real signal. The fix is targeted — not a rebuild. Identify the 2–3 lowest-scoring dimensions. Apply the specific iteration protocol for each. Retest over 30 days. Re-run the scorecard.
SCALE Score 45–60 — with no dimension below 2 The offer is working. Unit economics are viable. Buyers are getting results. The correct move is to add fuel: increase ad spend by 20%/day maximum, add a second traffic source, launch the affiliate programme for this offer, activate the ascension sequence to the next tier.
A total of 39 with three dimensions at 1 can fail the Iterate qualifier. A total of 56 with one dimension at 0 can fail the Scale qualifier. The source does not assign a replacement category for every such case. Flag the unclassified result rather than forcing it into a convenient band.
The Scale panel’s twenty-percent-per-day spend increase, extra traffic source, affiliate launch and ascension activation are proposals, not actions taken here or guarantees of sustainable growth. A low total alone does not establish permanent structural failure.
Phase 4 — Distinguish retirement, structural change and targeted iteration
The source’s distinction concerns what survives. Its kill definition retires both offer and mechanism; a pivot preserves an insight while changing delivery, audience, price or positioning. Read all five scenarios, including their different proposed relaunch periods.
Scenario
Correct Decision
What Survives
What Dies
Relaunch Timing
The offer fails but exit interviews reveal that buyers wanted the transformation and understood the mechanism — they just could not implement it as designed
PIVOT
The mechanism name. The core insight. The buyer language mined. The testimonials (partial).
The delivery format and price point. The sales page structure. The current fulfilment model.
90 days minimum. Rebuild the delivery model (e.g. self-paced course → live cohort, or group → done-for-you).
The offer fails and exit interviews reveal that buyers did not understand what they were buying or found the mechanism irrelevant to their actual problem
KILL
The buyer language (negative avatar data). The email list of buyers. The lessons about what does NOT work.
Everything. The mechanism name, the copy, the delivery model, the entire frame. Start fresh.
No automatic relaunch. Return to MVO Playbook Phase 1 with accumulated data as the brief.
The offer fails and the refund messages consistently describe expecting something fundamentally different from what was delivered
PIVOT (copy pivot)
The delivery and mechanism. The results that existing buyers did achieve.
The sales page positioning, the headline, the promise language. The gap was in how it was sold, not what was delivered.
30 days. Rebuild sales copy from scratch using exit interview language. Keep delivery identical.
The offer fails and the primary issue is price — buyers consistently cite 'too expensive' or conversion rate is strong at lower price points in A/B testing
PIVOT (price pivot)
The entire offer. The mechanism. The delivery. The copy.
The price point. The implied buyer tier (you may be serving a different income bracket than you targeted).
2 weeks. Reprice and relaunch. Monitor whether the new buyer profile changes support load and completion rate.
The offer works for a specific sub-segment but not for the broad avatar it was positioned for
PIVOT (avatar pivot)
The mechanism. The delivery. The results from the working sub-segment.
The broad positioning, the broad ad targeting, the generic sales page copy.
4 weeks. Narrow the positioning to the sub-segment where results are consistent. Rebuild copy for that specific avatar.
Buyer evidence should inform the distinction, but a scenario label does not prove its suggested cause. The pivot windows of ninety days, thirty days, two weeks and four weeks have different scopes from the later ninety-day killed-offer rule. Preserve that distinction rather than impose one universal delay.
The Iterate panel says two-to-three low dimensions, while the later rule permits at most two. It proposes one fix for each and a thirty-day reassessment. The following six intervention rows use fourteen days, the next cohort, thirty days or sixty days; those are not all interchangeable.
Failing Dimension
Specific Iteration Action
Retest Metric
Retest Window
Cold conversion below 1%
A/B test a new headline with a Pain-Acute hook derived from buyer language mining. Do not change any other element on the sales page during the test.
Cold conversion rate. Minimum 200 unique visitors per variant.
14 days minimum
Completion rate below 45%
Add a mandatory 72-hour Quick Win to Module 1. The Quick Win must produce a visible, shareable output. Add accountability check-in at hour 48.
Module 1 completion rate. Dropout rate at Module 1 boundary.
Next cohort cycle
Refund rate above 10%
Audit the sales page promise against the programme's actual deliverables. Identify the specific gap and fix either the copy (reduce the promise to match delivery) or the delivery (expand the deliverable to match the promise).
Refund rate over the following 30 days. Refund root cause codes.
30 days
NPS below 20
Conduct 5 buyer interviews in the first week after purchase. Identify the gap between their expectation at purchase and their experience in delivery. Fix the single most-cited gap.
NPS at next survey cycle (30 days). Support ticket volume.
30 days
Ascension rate below 6%
Rewrite the ascension sequence. Change the timing of the ascension offer presentation. Test presenting the Core Offer at Day 14 post-MVO-purchase instead of Day 21 or Day 30.
Ascension rate over 60 days.
60 days
CPA above 35% of price
Pause the lowest-performing ad set. Test a new creative format (video vs. static). Test a new audience segment derived from your best-converting buyers' lookalike.
CPA over 14 days of new creative.
14 days
A headline test, first-win change, promise/delivery repair, buyer interviews, ascension timing test and acquisition change target different observations. Changing only two dimensions does not automatically establish causality; the CPA row itself changes several elements. Retain the test plan and limits of attribution.
Phase 5 — Preserve buyers and records when studying closure
The source closure process assigns an action, owner and output to each stage. Preserve all nine rows, including the later seven- and fourteen-day follow-ups. They extend beyond the stated seventy-two-hour sequence.
Hour / Day
Action
Owner
Output
Hour 0–4
Pause all paid advertising for the offer. Immediately. No exceptions. Every additional dollar spent on a killed offer is wasted.
Ads manager / founder
All active ad campaigns paused. Budget released.
Hour 4–8
Deactivate or archive the offer page. Redirect the URL to either the homepage, an appropriate alternative offer page, or a 'This offer is no longer available' page that includes a waitlist opt-in.
Tech / founder
Offer page redirected. URL not returning 404.
Hour 8–16
Deactivate the email sequence associated with the offer. Any new subscribers who triggered the sequence after the kill decision will not receive offer-specific emails.
Email platform / founder
Email sequence deactivated. Active sequence recipients noted.
Day 1
Send the Buyer Communication Email (see template below) to all current buyers who are within their active delivery window. Explain the situation with clarity and without corporate language.
Founder (personal tone required)
Buyer communication sent. Inbox monitored for 48 hours.
Day 1–2
Pull all data exports: buyer list, refund records, support ticket archive, community posts, email reply archive, exit interview recordings. Store in designated archive folder.
Ops / founder
Full data archive in Google Drive / Airtable. Nothing deleted.
Day 2
Cancel or pause any affiliate commissions on new sales. Notify affiliates of the offer closure with a professional explanation and, where appropriate, an alternative offer to promote.
Complete the Post-Kill Intelligence Form (Phase 6 template). While the experience is fresh. Do not wait.
Founder
Post-Kill Intelligence Form filed in Airtable.
Day 7 (post-kill)
Review the Buyer Communication inbox. Address any unresolved buyer concerns. Process any refund requests that arrived in the kill window.
Support / founder
All buyer communications resolved.
Day 14 (post-kill)
Run the Negative Avatar Profile check: do any refund patterns from this offer need a new profile created? Update Negative Avatar Airtable accordingly.
Founder
Negative Avatar updates complete.
The checklist says deactivate email within eight hours, while the sequence says hours eight to sixteen. Immediate ad language and longer closure windows also need reconciliation. Pausing commissions, notifying affiliates, redirecting pages and offering refunds are consequential source actions; none has been performed here.
The email template contains two alternative explanations and concrete promises about access, refunds and transitions. Read both versions. Actual dates, delivery facts, permissions and obligations must be established before any use. Do not copy a promise that cannot be fulfilled. The source asks for a plain personal message rather than a branded template; that preference does not verify the message’s facts.
Buyer Communication Template Subject: An important update about [Offer Name]
Hi [First Name],
I want to be straight with you about something.
We have decided to retire [Offer Name] effective [date]. This means we will not be accepting new students, and I want to explain why — and what it means for you specifically.
[One of the following, as applicable:]
Version A (Product not delivering promised results): After reviewing the results our students have achieved and being honest about where the gaps are, I am not comfortable continuing to sell this offer in its current form. You deserve better than I built.
Version B (Strategic pivot): We are focusing our energy on [New Offer / Direction], which does [specific thing] better than this offer could. This is a strategic decision, not a quality issue.
What this means for you:
If you are currently in the programme — you will continue to have access to everything you purchased until [specific date]. Nothing is being removed from your account.
If you would like a refund — I will honour a full refund regardless of where you are in the programme and regardless of whether you are within the standard refund window. Email [email] with 'Refund Request' in the subject line.
If you would like to move to [Alternative Offer] — [specific transition offer if applicable].
I am sorry if this is disruptive. It is the right call.
[Your name]
Phase 6 — Record what happened without claiming more than the evidence shows
The source asks for intelligence extraction within three days. It claims failure teaches more than success and that markets reveal every needed answer. Treat those as rhetoric; a failed offer may still leave major questions unresolved.
The form has nineteen fields, not the checklist’s eighteen. Preserve every one below, including the blank kill-date cell. Distinguish observed totals, interpretation, preserved assets and next-step eligibility.
Field
What to Document
Kill Record ID
Autonumber — auto-generated
Offer name and version
Full offer name + which version was killed (V1, V2, etc.)
Kill date
Kill trigger type
Hard Kill (specify HK code) / Scorecard-based Kill (record final scorecard score) / Strategic Kill
Final scorecard score
Record all 15 dimension scores and the total. This is the permanent benchmark.
Total buyers
How many people purchased before the kill
Total revenue
Gross revenue generated before kill
Total refunds
Number and percentage
Net revenue
After refunds
Total ad spend
All paid acquisition costs associated with this offer
ROAS (if applicable)
Net revenue / ad spend
The single most important lesson
In one sentence: what did this offer teach you that you did not know before? This should be specific enough to change a specific future decision.
The copy gold
Top 5 buyer language phrases mined from this offer's data (verbatim). These survive the kill and go directly into the next offer's copy brief.
The assumption that was wrong
What did you believe about the market, the buyer, or the mechanism that this offer's failure proved incorrect?
The Negative Avatar defined
Which Negative Avatar archetype was most commonly attracted? What specific language attracted them? (Links to Negative Avatar Airtable table)
The Next Problem Signal
Did this offer's buyers reveal a Problem B — the thing they needed next that you have not yet built? Document it here.
What the market actually wanted
Based on all available data — what offer would have served this audience correctly?
What was preserved
List any copy assets, mechanism names, buyer relationships, or marketing angles that survive the kill and are being transferred to the next offer brief.
Relaunch eligibility
Yes — conditions defined / No — full retirement / Pivot — specify the pivot direction
Net revenue after refunds is not profit. Its ROAS definition uses net revenue divided by ad spend, which needs aligned periods and a zero-spend rule. The five buyer phrases should retain context and provenance. A proposed ProblemB is a research lead, not proof of demand for a new product.
The six salvage categories cover language, testimonials, recordings, page sections, email openings and a preserved mechanism. Read their criteria and destinations in full.
Asset Type
Salvage Criteria
What to Do With It
Buyer language from email replies
All tagged phrases from Phase 3 of the Forensic Audit (PAIN-ACUTE, PAIN-CHRONIC, DESIRE-HIDDEN, OBJECTION tags)
Move to the Master Language Mining database. Tag source as 'Kill Salvage — [Offer Name]'. These phrases are valid regardless of whether the offer worked.
Testimonials from buyers who got results
Any testimonial where the buyer achieved a specific, measurable result that can be attributed to the mechanism
Move to proof library. Can be used in the next offer if the mechanism is preserved. Cannot be used if the mechanism is killed and replaced.
Exit interview recordings
All recordings
Archive in Google Drive. Tag with date and offer name. Transcripts extracted and stored in language mining database.
Sales page copy — performing sections
Sections of the sales page where heatmap data showed high engagement, low bounce, or direct scroll-to-CTA behaviour
Save as 'High-engagement copy segments' in copy swipe file. Even in a failed offer, some sections worked.
Email sequence — high-open-rate emails
Any email in the 14-day sequence that achieved above 35% open rate
Archive the subject line and the opening paragraph. These are proven attention-capturing elements independent of the offer.
The mechanism name (if not killed)
If the pivot/iterate decision preserved the mechanism name — the name goes directly into the next offer brief
Transfer to next offer's MVO Playbook Phase 2 document as the named mechanism.
Later testimonial reuse requires a preserved mechanism, narrowing the opening’s broader language. Accuracy, context and permission still matter. Heatmap engagement or email opens above thirty-five percent do not establish that a copy segment caused a sale. Retain raw records alongside any interpretation; do not delete original files as part of an instructional exercise.
Phase 7 — Examine every relaunch requirement
The source requires ninety days off market and all six conditions below before a killed offer returns. Elapsed time or fading buyer memory does not demonstrate that earlier problems have been resolved. Evidence of actual change matters.
Requirement
What It Means
How to Evidence Completion
Minimum 90-day gap from kill date
The offer has been off the market for at least 90 calendar days
Kill date in Airtable Kill Record. Today's date minus kill date is ≥ 90.
Root cause identified and addressed
The specific reason the offer failed (from Phase 5 Kill Record, 'The assumption that was wrong' field) has been specifically addressed in the rebuilt offer
Updated offer brief documents the specific change made in response to the identified root cause. One change per root cause — not vague 'improvements.'
New buyer interviews conducted
Minimum 3 new buyer interviews with the intended target avatar conducted after the kill — not from the original buyer pool
Interview transcripts dated after the kill date. Must include at least one person who was NOT a buyer of the original offer.
Offer rebuilt from copy brief, not from the original
The new version was written from a fresh copy brief using the Post-Kill intelligence, not by editing the original sales page
New copy brief document in Airtable dated after kill. If the sales page draft clearly resembles the original with light edits — it is not a rebuild. Start over.
Negative Avatar profiles from original offer are active
The Negative Avatar Profiles created from the original offer's data are deployed in the new offer's repulsion system: 'Not for you' copy, ad exclusions, and application gates
New offer's sales page 'Not for you' section includes at least one bullet per active Negative Avatar Profile. Ad exclusion list updated.
Beta cohort run before public relaunch
A minimum of 5-buyer paid beta is run on the rebuilt offer before the public sales page goes live
Beta Testing SOP records in Airtable. Beta scorecard passed (Go/No-Go thresholds met). Beta dated after kill.
The interview condition says to use people outside the original buyer pool, but the evidence column requires only one nonbuyer among three interviews. Preserve that conflict. The root-cause reference points to Phase 5 although the intelligence form appears in Phase 6. A new brief, active suitability exclusions and a five-buyer paid beta are proposed requirements with separate source dependencies, not completed artifacts.
The source lists five permanent-retirement conditions below. They are its decision proposals; counts of complaints or reviews do not establish guilt, and competition alone does not prove that a specific offer cannot differentiate.
• The market the offer was designed for no longer exists or has been commoditised to the point where profitable differentiation is not achievable.
• The primary mechanism has been replicated by a better-resourced competitor and can no longer be positioned as differentiated.
• The offer generated three or more legal complaints, regulatory reviews, or FTC scrutiny — regardless of their outcome. The reputation risk of the specific offer persists beyond the compliance resolution.
• The Post-Kill Intelligence Form's 'assumption that was wrong' field reveals that the market does not actually have the problem the offer was designed to solve. This is not a copywriting problem — it is a market existence problem.
• The offer's total cost (ad spend, time, legal, support) exceeded its total revenue — and the rebuilt version cannot be demonstrated via the beta to achieve different unit economics.
The mechanism definition and actual audience evidence must support any future judgment. The source’s assertion about costs exceeding revenue still requires a clear period and treatment of time and other costs. A beta may inform a revised assessment without proving all future economics.
Phase 8 — Review inactive offers without confusing silence with failure
The source calls an offer a zombie when it remains technically live with little activity while consuming attention, attracting unsupported buyers and confusing the offer path. These are proposed failure modes, not conclusions from low traffic alone.
The first-Monday quarterly audit checks four criteria. Read the complete thresholds and stated reasons below.
Zombie Criterion
Threshold
Why It Qualifies
Revenue below floor for consecutive months
Below $500 gross revenue for 3 consecutive months for any offer priced above $97
At this revenue level, the offer is not covering its own operational overhead — support, payment processing, platform fees, and email sends.
No new buyers in 60+ days
Zero new purchases in 60+ consecutive days
An offer with no buyers for 60 days is effectively dead. It is consuming a sales page URL, a purchase flow, a delivery system, and an email sequence for zero return.
Traffic below viable testing threshold for 90 days
Fewer than 50 unique visitors per month for 90+ consecutive days
Below 50 monthly visitors, there is no data being generated. The offer is neither working nor failing — it is simply invisible. That is not a business; it is an archive.
No active promotional activity for 60 days
No email campaigns, no ad spend, no organic content referencing the offer in 60+ days
If you have not promoted an offer in 60 days, you have already informally killed it. Formalise that decision with the Clean Kill Process and archive the assets properly.
The $500 floor applies to offers priced above $97; exactly $97 is not specified. That revenue amount is not a universal overhead break-even point. No promotion or few visitors can explain why there is little evidence; it does not by itself prove that the product is unwanted.
The five remediation steps below call for an immediate scorecard, one change, one hundred warm visitors and reassessment. They remain a proposed protocol.
Run the Kill Assessment Scorecard (Phase 3) immediately on the flagged offer. If the score is below 25, skip remediation — proceed directly to Kill.
If the scorecard score is 25 or above, identify the single highest-leverage change that could revive the offer within 30 days. One change only.
Implement the change and drive minimum 100 unique warm visitors to the offer page within the 30-day window.
At day 30, re-run the scorecard. If the score has not improved by at least 8 points — kill the offer.
If the score has improved by 8+ points but is still below Scale threshold — run the iterate protocol for one more 30-day cycle only. Two cycles maximum before kill.
A starting score of 53 or higher cannot improve by eight points on a sixty-point scale. The rule lacks an exception even for an already-high score. A score reaching 45 also still needs the no-dimension-below 2 qualifier to meet its stated Scale definition. The second-cycle baseline and decision details are not fully specified. Do not force these incomplete rules into an automatic closure decision.
Preserve the separate database schema
The Kill Records table contains twenty-two fields, which is distinct from the nineteen-field intelligence form. Compare each specification below with the data that must be retained.
Field
Type
Notes
Kill Record ID
Autonumber
Format: KILL-[Year]-[Seq]. E.g. KILL-2026-003
Offer
Link → Offers table
The offer that was killed
Kill date
Date
Kill type
Single select
Hard Kill (HK-1 through HK-7) / Scorecard Kill / Strategic Kill / Zombie Kill
Hard Kill trigger code
Single select
HK-1 through HK-7 — or N/A for scorecard kills
Final scorecard score
Number
0–60. All 15 dimension scores stored in long text field.
All 15 dimension scores
Long text
Each dimension name + score, one per line
Total buyers at kill
Number
Gross revenue
Currency
Net revenue (after refunds)
Currency
Total ad spend
Currency
ROAS
Formula
Net revenue / ad spend — auto-calculated
The single most important lesson
Long text
One sentence — specific enough to change a future decision
The assumption that was wrong
Long text
What was believed vs. what the data proved
What the market actually wanted
Long text
Based on all data — what offer would have worked
Preserved assets
Long text
Copy, mechanism names, buyer language, testimonials — what survived
Negative Avatar profiles created
Link → Negative Avatar Profiles
All profiles that emerged from this offer's failure data
Next Problem Signal
Long text
Problem B if identified — feeds product roadmap
Relaunch eligibility
Single select
Yes — conditions defined / No — permanent retirement / Pivot — direction specified
Relaunch conditions (if eligible)
Long text
Specific conditions that must be met before resurrection
90-day relaunch consideration date
Date
Kill date + 90 days — auto-populated
Resurrection record
Link → Offers table
If the offer was relaunched — link to the new offer record
The schema does not provide dedicated fields for every form item, such as refund count/percentage and the five buyer phrases. A single offer link may carry version information only if the Offers table defines it. Autonumber does not itself implement the year/sequence ID, and the ninety-day date and ROAS calculations need actual formulas. Links to audits, profiles and future offers do not prove those records exist.
Review the complete source checklist
Use the checklist to identify missing evidence and procedures, not to mark source instructions as performed. Its eighteen-field reference should be read with the verified nineteen-field form, and its closure timing must be compared with the earlier sequence.
Before Any Kill Decision — Pre-Kill Diagnostic
☐ Minimum 200 unique cold visitors have seen the offer
RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING. The old source domain is retained only as original evidence.
Turn in one proposed assessment record with the offer version, observation window, diagnostic evidence, fifteen separate scores, total, qualifying conditions and unresolved decisions. Identify what would need review before any real action. Keep it in your course work folder until the submission destination is confirmed. Do not treat a draft score or a source template as approval to retire an offer or contact its buyers.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — PRODUCT KILL CRITERIA (POST-LAUNCH)
The Objective System for Deciding When to Kill, Pivot, Iterate, or Scale Any Offer
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
Most operators apply rigorous kill logic before launching an offer — kill filters, viability scoring, 6-score monetisation tests — and then never apply equivalent logic after the offer is live. The result is a business carrying dead or dying offers that consume operational bandwidth, advertising budget, and emotional energy while producing little or no return.
This SOP defines the post-launch system for making objective kill, pivot, iterate, or scale decisions at every stage of an offer's lifecycle. It eliminates the sunk-cost thinking that keeps broken offers alive, provides the specific numerical thresholds that determine each decision, and defines the process for killing an offer cleanly — archiving its intelligence, honouring existing buyers, and extracting every lesson before the door closes.
Kennedy's Kill Rule
The most expensive thing in your business is an offer you should have killed six months ago. It is consuming ad spend, support bandwidth, team attention, and your own belief in the market. Kill it. Learn from it. Build the next one smarter. The trail of killed offers is not a sign of failure — it is the evidence that you are iterating toward something that works.
Hormozi's Fuel Rule
Never add fuel to a broken vehicle. Scaling traffic, increasing ad spend, or adding more affiliates to an offer that has not passed its kill-or-scale assessment is how operators spend $50K proving what $5K of organic data already told them. Fix the vehicle first. Then add fuel.
Brunson's Funnel Law
You are one funnel away from success — but only if you are willing to kill the ones that are not working. The operators who win are not smarter. They are faster at recognising what is not working and more willing to cut it.
The Sunk Cost Problem: Why Offers Stay Alive Too Long
Before the kill criteria, the system must confront the reason those criteria are so rarely applied. The sunk cost fallacy — the tendency to continue investing in something because of prior investment rather than future potential — kills more businesses slowly than any market condition ever has.
Sunk Cost Bias
How It Manifests
The Rational Counter
Time investment bias
'I spent 3 months building this. I can't just kill it.'
The 3 months are gone regardless of what you decide today. The only question is whether the next 3 months goes into a working offer or a broken one.
Identity attachment
'This offer represents my core methodology. Killing it feels like killing part of myself.'
The methodology survives the offer. Rename the mechanism. Repackage the IP. Kill the specific execution that is not working — not the expertise behind it.
Audience validation hunger
'People say they love this offer even if they're not buying.'
Compliments are not revenue. Kennedy: 'Validate with dollars, not compliments.' If the audience loves it and will not pay for it, the market has spoken.
Optimism bias
'I just need to fix one more thing and it will work.'
Define in advance what 'one more thing' means. If you have already made three 'one more thing' changes and the metrics have not moved, the problem is structural — not fixable with incremental iteration.
Social proof protection
'I have testimonials from this offer. If I kill it, I lose the social proof.'
Testimonials belong to the buyer and the result, not the offer format. Testimonials from a killed offer can be repurposed in a new, better offer that serves the same transformation.
Sunken ad spend
'I've spent $8K in ads to prove this. I need to recoup that before stopping.'
The $8K is already spent. Continuing to run an unworkable offer to recoup sunk ad cost will result in spending $16K to prove what $8K already proved. Cut the loss now.
The Pre-Commitment Solution
The most effective way to override sunk cost bias is to define your kill criteria before launch — not during the emotional heat of a failing offer. This SOP works best when you set your kill thresholds at the point of launch, file them in Airtable, and commit to honouring them regardless of how the offer makes you feel at the point of decision.
The Offer Lifecycle Model
Kill criteria are not static. An offer at day 7 is held to completely different standards than an offer at day 90. Applying day-90 thresholds to a day-7 offer produces false kills. Applying day-7 thresholds to a day-90 offer allows zombie offers to survive indefinitely. The lifecycle model defines which metrics and which thresholds apply at each stage.
Stage 1
Launch
Days 1–14
Proof of market response
Stage 2
Validation
Days 15–45
Conversion rate signal
Stage 3
Traction
Days 46–90
Unit economics viability
Stage 4
Scale
Days 91–180
Paid traffic profitability
Stage 5
Decline
180+ days
Renewal and ascension rate
Stage-Specific Assessment Points
Stage
Primary Question
Key Metric
Decision at This Stage
Stage 1 — Launch
(Days 1–14)
Is anyone responding to this offer at all?
First sale: did any paying buyers emerge without heavy persuasion from a warm audience within 14 days?
If zero sales from a warm list of 500+ after a proper 7-day launch sequence: trigger Stage 1 Kill Assessment. Do not move to paid ads.
Stage 2 — Validation
(Days 15–45)
Is the conversion rate statistically viable for the offer type?
Cold conversion rate after 200+ unique visitors. Warm conversion rate after full email sequence delivery to warm list.
If cold conversion remains below threshold after 300+ visitors and one round of copy iteration: trigger Full Kill Assessment (Phase 3 scorecard).
Stage 3 — Traction
(Days 46–90)
Do the unit economics work?
Cost Per Acquisition vs. Offer Price ratio. Refund rate. Support cost per buyer. LTV:CAC ratio.
If unit economics fail the Stage 3 thresholds after genuine traffic investment: trigger Full Kill Assessment. Do not scale.
Stage 4 — Scale
(Days 91–180)
Is this offer still working as ad spend increases?
ROAS by platform. CPA trend (improving, flat, or worsening). Ascension rate to next tier.
If ROAS declines below 2.0x and CPA exceeds 35% of offer price for 21+ consecutive days: trigger Scale-to-Iterate or Kill decision.
If revenue has declined 40% from peak for 60+ consecutive days with no identifiable external cause: trigger Full Kill Assessment or Relaunch Protocol.
PHASE 1
The Pre-Kill Diagnostic
Rule out fixable problems before killing — so you only kill when death is actually warranted
The Diagnostic Purpose
The Pre-Kill Diagnostic exists because most offers that appear to be dying are not actually broken at the offer level — they are broken at the traffic, copy, or distribution level. Killing a valid offer because the ad creative was stale or the email subject line was weak is an extremely expensive mistake. This diagnostic rules out six fixable causes before the kill assessment begins.
The Rule
Do not enter the Kill Assessment (Phase 3) until every item in the Pre-Kill Diagnostic has been addressed. If any diagnostic item is unresolved, fix it first — then measure again for the minimum window specified. Only enter Kill Assessment if the metrics fail after the diagnostic fixes have been applied.
The Six Fixable Causes of Poor Performance
Fixable Cause
Diagnostic Question
Evidence That This Is the Problem
Minimum Fix & Retest Window
Traffic volume insufficient
Have at least 200 unique cold visitors seen this offer (300+ preferred for statistical significance)?
Conversion rate data is based on fewer than 200 unique cold visitors. Any rate below 200 visits is noise, not signal.
Drive 200+ unique visitors through organic promotion or minimal paid spend ($300–$500 test budget) before assessing cold conversion rate.
Traffic source mismatch
Is the traffic source aligned with the awareness level the offer page assumes?
Cold traffic is landing on a page written for warm or hot traffic. Sales page assumes prior relationship or context the visitor does not have.
Audit the first 500 words of the sales page for assumed context. Rewrite the lead assuming zero prior awareness. Retest for 7 days.
Copy — headline not tested
Has the headline been A/B tested with at least 2 meaningfully different angles?
Single headline has been running since launch. No split test data.
Write 3 headline variants (pain hook, desire hook, mechanism hook). Run split test for minimum 14 days or 200 visitors per variant. Decision only after test concludes.
Email sequence — not complete or not deployed
Has the full 14-day email sequence been deployed to the warm list?
Fewer than 10 emails have been sent, or the sequence was stopped early, or the list size was fewer than 200 subscribers.
Complete the full 14-day sequence to a list of 200+ subscribers. Assess warm conversion rate after the sequence concludes.
Guarantee — not sufficiently strong
Has a meaningful guarantee been tested against the current version?
Current guarantee is a basic 30-day money-back with no conditions or commitment language. Has never been upgraded.
Test the Level 3 guarantee (result-based conditional) against current guarantee for 14 days. If conversion lifts 15%+ — guarantee was the problem, not the offer.
Offer stack — not presented clearly
Has the full value stack (bonuses, mechanism, deliverables, guarantee, social proof) been tested in the Brunson Stack Slide format?
Sales page does not have a visual offer stack with individual bonus values listed. The offer is described narratively without a stacked presentation.
Rebuild the sales page's offer section as a Stack Slide: list each component, assign a standalone value, show total value vs. asking price. Retest for 14 days.
Pre-Kill Diagnostic Checklist
Complete this checklist before opening a kill assessment. Every item marked 'Not yet addressed' must be actioned and retested before proceeding to Phase 3.
Diagnostic Item
Status
Retest Window
Cleared?
Minimum 200 unique cold visitors have seen the offer
Full 14-day email sequence deployed to 200+ warm subscribers
☐ Yes ☐ Not yet
Deploy and wait for sequence to complete
☐
Level 3 guarantee tested against current guarantee
☐ Yes ☐ Not yet
14 days split test
☐
Stack Slide offer presentation tested
☐ Yes ☐ Not yet
14 days after implementation
☐
PHASE 2
Hard Kill Triggers
Automatic — if any of these conditions are met, the offer is killed immediately, no scorecard required
The Hard Kill Principle
Hard Kill Triggers are non-negotiable. They represent conditions that cannot be iterated out of, that create unacceptable risk to the business or its buyers, or that indicate a fundamental structural incompatibility between the offer and the market. When any Hard Kill Trigger is met, the offer is killed within 48 hours. No scorecard. No deliberation. No 'one more try.'
Why No Deliberation
The purpose of defining Hard Kill Triggers in advance is to remove the decision from the emotional present and place it in the rational past. You are not deciding whether to kill the offer when you are emotionally invested in it. You decided the conditions for killing it before you launched it. Now you are just honouring that decision.
Trigger
Threshold
Rationale
Action Timeline
HK-1: Catastrophic refund rate
Refund rate exceeds 30% of total sales after a minimum of 20 sales
A refund rate above 30% indicates a systematic failure in promise delivery or a fundamental mismatch between what was sold and what was received. This is not fixable with copy changes — the offer is broken at the product level.
Kill within 48 hours. Pause all ads immediately. Begin Post-Kill Protocol.
HK-2: Legal or compliance violation identified
Any confirmed violation of FTC guidelines, TCPA regulations, platform terms of service, or applicable consumer protection law
Legal exposure compounds exponentially the longer a non-compliant offer remains live. Compliance violations can result in platform bans, financial penalties, and reputational damage that far exceeds any revenue from the offer.
Kill within 24 hours. Consult legal counsel before relaunch. Do not attempt to fix and relaunch without written legal clearance.
HK-3: Fulfilment breakdown — unable to deliver
You are materially unable to deliver the core promise of the offer to existing or new buyers
Continuing to sell an offer you cannot deliver is both legally and ethically indefensible. Fulfilment breakdown triggers immediate offer suspension, not iteration.
Suspend new sales within 24 hours. Communicate with existing buyers within 48 hours. Full refund offered to all buyers unable to receive delivery.
HK-4: Zero warm conversion after complete sequence
Zero sales from a warm list of 500+ after a full 14-day email sequence has been deployed, with at least 25% open rate confirmed
A 25%+ open rate confirms the sequence was read. Zero purchases from 500+ warm subscribers who read the sequence means the offer is rejected by people who know, like, and trust you. This is the harshest market signal available.
Kill within 7 days. Do not move to cold paid traffic. Begin Post-Kill Protocol.
HK-5: Cold conversion remains below 0.3% after diagnostic complete
Cold conversion rate remains below 0.3% after all six Pre-Kill Diagnostic fixes have been applied and retested over a minimum of 300 unique cold visitors
0.3% is the absolute floor for any offer that can ever be made profitable through paid advertising. Below 0.3% with a clean diagnosis means the offer itself is the problem — not the copy, not the traffic.
Kill within 14 days of confirmed diagnostic completion. Do not spend further on ads.
HK-6: Negative NPS after 20+ responses
Net Promoter Score falls below -10 after a minimum of 20 buyer survey responses
An NPS below -10 means your detractors significantly outnumber your promoters. This offer is actively generating negative word-of-mouth at a rate that will compound against every future launch.
Kill within 7 days of confirmed NPS threshold. Conduct emergency buyer interviews. Do not run this offer again without rebuilding from scratch.
HK-7: CPA exceeds 60% of offer price after $3,000+ ad spend
Cost Per Acquisition exceeds 60% of the offer's sale price after at least $3,000 has been spent testing across at least 2 different audience types
At a CPA of 60% of revenue, there is no viable business. After refunds, fulfilment costs, and payment processing fees, the unit economics are deeply negative and cannot be corrected by optimising an offer that the market is systematically rejecting.
Kill paid spend immediately. Offer may continue organically if organic conversion is strong. If organic also fails, full kill.
PHASE 3
The Kill Assessment Scorecard
For offers that have not triggered a Hard Kill — the objective scoring system
When to Run the Scorecard
The Kill Assessment Scorecard is run when an offer has cleared the Pre-Kill Diagnostic (Phase 1), has not triggered a Hard Kill (Phase 2), but is underperforming against its stage-specific thresholds. It produces a numerical score that maps to one of four decisions: Kill, Pivot, Iterate, or Scale.
The Scorecard (15 Dimensions — Maximum 60 Points)
Score each dimension objectively using the evidence available. Do not round up out of optimism. Do not round down out of frustration. Use the data.
Dimension
0 Points — Critical Failure
1 Point — Below Viable
2 Points — Viable
3 Points — Strong
4 Points — Excellent
Your Score
Cold conversion rate
Below 0.5%
0.5–0.9%
1.0–1.9%
2.0–3.9%
4.0%+
___
Warm conversion rate
Below 2%
2–4%
5–9%
10–19%
20%+
___
Refund rate
Above 20%
15–20%
8–14%
3–7%
Below 3%
___
Programme completion rate
Below 25%
25–44%
45–59%
60–74%
75%+
___
Specific result testimonials (per 10 buyers)
0
1
2–3
4–5
6+
___
Email open rate (14-day sequence)
Below 15%
15–19%
20–29%
30–39%
40%+
___
Support tickets per buyer (per 30 days)
Above 8
5–8
3–4
1–2
0–1
___
CPA as % of offer price
Above 50%
40–50%
25–39%
15–24%
Below 15%
___
Ascension rate to next tier
Below 3%
3–5%
6–9%
10–14%
15%+
___
Buyer NPS score
Below -10
–10 to 0
1–20
21–40
41+
___
Month-over-month revenue trend
Declining >20%
Declining 5–20%
Flat (±5%)
Growing 5–19%
Growing 20%+
___
Value Equation audit — Dream Outcome score
1–2 (broken)
3–4 (weak)
5–6 (adequate)
7–8 (strong)
9–10 (excellent)
___
Value Equation audit — Perceived Likelihood score
1–2 (broken)
3–4 (weak)
5–6 (adequate)
7–8 (strong)
9–10 (excellent)
___
Value Equation audit — Time Delay score
1–2 (broken)
3–4 (weak)
5–6 (adequate)
7–8 (strong)
9–10 (excellent)
___
Value Equation audit — Effort & Sacrifice score
1–2 (broken)
3–4 (weak)
5–6 (adequate)
7–8 (strong)
9–10 (excellent)
___
Score Interpretation
KILL
Score 0–24 (out of 60) — or any Hard Kill Trigger fired regardless of score
The offer has failed across multiple dimensions and cannot be fixed through incremental iteration. The structural problems are too numerous or too deep. Kill the offer using the Clean Kill Process (Phase 5). Extract all intelligence using the Post-Kill Protocol (Phase 6).
PIVOT
Score 25–34 — with 3 or more dimensions at 0 or 1
The core premise or mechanism may be viable but the execution is failing broadly. Iteration will not fix this — it requires a structural change to the offer format, the target avatar, the pricing tier, or the delivery mechanism. A pivot is not a kill — it is a rebuild that preserves the underlying insight.
ITERATE
Score 35–44 — with no more than 2 dimensions at 0 or 1
Specific, diagnosable problems exist but the offer has real signal. The fix is targeted — not a rebuild. Identify the 2–3 lowest-scoring dimensions. Apply the specific iteration protocol for each. Retest over 30 days. Re-run the scorecard.
SCALE
Score 45–60 — with no dimension below 2
The offer is working. Unit economics are viable. Buyers are getting results. The correct move is to add fuel: increase ad spend by 20%/day maximum, add a second traffic source, launch the affiliate programme for this offer, activate the ascension sequence to the next tier.
PHASE 4
The Kill vs. Pivot vs. Iterate Decision Framework
When the scorecard says Kill or Pivot — making the right structural choice
Kill vs. Pivot: The Critical Distinction
A Kill and a Pivot both result in the current version of the offer being retired. The distinction is what survives. In a Kill, the offer and the mechanism are both retired — the market has rejected both the delivery and the promise. In a Pivot, the mechanism and the insight are preserved but the execution — the format, avatar, price point, or delivery model — is fundamentally changed.
Scenario
Correct Decision
What Survives
What Dies
Relaunch Timing
The offer fails but exit interviews reveal that buyers wanted the transformation and understood the mechanism — they just could not implement it as designed
PIVOT
The mechanism name. The core insight. The buyer language mined. The testimonials (partial).
The delivery format and price point. The sales page structure. The current fulfilment model.
90 days minimum. Rebuild the delivery model (e.g. self-paced course → live cohort, or group → done-for-you).
The offer fails and exit interviews reveal that buyers did not understand what they were buying or found the mechanism irrelevant to their actual problem
KILL
The buyer language (negative avatar data). The email list of buyers. The lessons about what does NOT work.
Everything. The mechanism name, the copy, the delivery model, the entire frame. Start fresh.
No automatic relaunch. Return to MVO Playbook Phase 1 with accumulated data as the brief.
The offer fails and the refund messages consistently describe expecting something fundamentally different from what was delivered
PIVOT (copy pivot)
The delivery and mechanism. The results that existing buyers did achieve.
The sales page positioning, the headline, the promise language. The gap was in how it was sold, not what was delivered.
30 days. Rebuild sales copy from scratch using exit interview language. Keep delivery identical.
The offer fails and the primary issue is price — buyers consistently cite 'too expensive' or conversion rate is strong at lower price points in A/B testing
PIVOT (price pivot)
The entire offer. The mechanism. The delivery. The copy.
The price point. The implied buyer tier (you may be serving a different income bracket than you targeted).
2 weeks. Reprice and relaunch. Monitor whether the new buyer profile changes support load and completion rate.
The offer works for a specific sub-segment but not for the broad avatar it was positioned for
PIVOT (avatar pivot)
The mechanism. The delivery. The results from the working sub-segment.
The broad positioning, the broad ad targeting, the generic sales page copy.
4 weeks. Narrow the positioning to the sub-segment where results are consistent. Rebuild copy for that specific avatar.
Iterate Protocol: The 2-Fix Maximum Rule
When the scorecard indicates Iterate, you are permitted to make targeted changes to the lowest-scoring dimensions. The 2-Fix Maximum Rule applies: identify the two lowest-scoring dimensions, implement one specific fix for each, and retest for 30 days before running the scorecard again. Making more than two changes simultaneously makes it impossible to know which fix worked.
Failing Dimension
Specific Iteration Action
Retest Metric
Retest Window
Cold conversion below 1%
A/B test a new headline with a Pain-Acute hook derived from buyer language mining. Do not change any other element on the sales page during the test.
Cold conversion rate. Minimum 200 unique visitors per variant.
14 days minimum
Completion rate below 45%
Add a mandatory 72-hour Quick Win to Module 1. The Quick Win must produce a visible, shareable output. Add accountability check-in at hour 48.
Module 1 completion rate. Dropout rate at Module 1 boundary.
Next cohort cycle
Refund rate above 10%
Audit the sales page promise against the programme's actual deliverables. Identify the specific gap and fix either the copy (reduce the promise to match delivery) or the delivery (expand the deliverable to match the promise).
Refund rate over the following 30 days. Refund root cause codes.
30 days
NPS below 20
Conduct 5 buyer interviews in the first week after purchase. Identify the gap between their expectation at purchase and their experience in delivery. Fix the single most-cited gap.
NPS at next survey cycle (30 days). Support ticket volume.
30 days
Ascension rate below 6%
Rewrite the ascension sequence. Change the timing of the ascension offer presentation. Test presenting the Core Offer at Day 14 post-MVO-purchase instead of Day 21 or Day 30.
Ascension rate over 60 days.
60 days
CPA above 35% of price
Pause the lowest-performing ad set. Test a new creative format (video vs. static). Test a new audience segment derived from your best-converting buyers' lookalike.
CPA over 14 days of new creative.
14 days
PHASE 5
The Clean Kill Process
How to retire an offer with integrity — protecting buyers and extracting maximum intelligence
The Clean Kill Principle
Killing an offer is not an emergency or a shame event. It is a business decision that, executed well, protects your reputation, honours your existing buyers, and produces the intelligence that makes the next offer better. A poorly executed kill — abrupt, unexplained, or disorganised — damages trust with buyers, confuses the market, and wastes the data the offer generated.
The 72-Hour Kill Sequence
From the moment the kill decision is confirmed, the following sequence must be completed within 72 hours for Hard Kill Triggers (HK-1 through HK-7) and within 14 days for scorecard-based kills.
Hour / Day
Action
Owner
Output
Hour 0–4
Pause all paid advertising for the offer. Immediately. No exceptions. Every additional dollar spent on a killed offer is wasted.
Ads manager / founder
All active ad campaigns paused. Budget released.
Hour 4–8
Deactivate or archive the offer page. Redirect the URL to either the homepage, an appropriate alternative offer page, or a 'This offer is no longer available' page that includes a waitlist opt-in.
Tech / founder
Offer page redirected. URL not returning 404.
Hour 8–16
Deactivate the email sequence associated with the offer. Any new subscribers who triggered the sequence after the kill decision will not receive offer-specific emails.
Email platform / founder
Email sequence deactivated. Active sequence recipients noted.
Day 1
Send the Buyer Communication Email (see template below) to all current buyers who are within their active delivery window. Explain the situation with clarity and without corporate language.
Founder (personal tone required)
Buyer communication sent. Inbox monitored for 48 hours.
Day 1–2
Pull all data exports: buyer list, refund records, support ticket archive, community posts, email reply archive, exit interview recordings. Store in designated archive folder.
Ops / founder
Full data archive in Google Drive / Airtable. Nothing deleted.
Day 2
Cancel or pause any affiliate commissions on new sales. Notify affiliates of the offer closure with a professional explanation and, where appropriate, an alternative offer to promote.
Complete the Post-Kill Intelligence Form (Phase 6 template). While the experience is fresh. Do not wait.
Founder
Post-Kill Intelligence Form filed in Airtable.
Day 7 (post-kill)
Review the Buyer Communication inbox. Address any unresolved buyer concerns. Process any refund requests that arrived in the kill window.
Support / founder
All buyer communications resolved.
Day 14 (post-kill)
Run the Negative Avatar Profile check: do any refund patterns from this offer need a new profile created? Update Negative Avatar Airtable accordingly.
Founder
Negative Avatar updates complete.
Buyer Communication Email Template
This email is sent personally from the founder. It is plain text, not designed, and not run through the standard email platform's branded template. It reads like a human being wrote it because a human being should have written it.
Buyer Communication Template
Subject: An important update about [Offer Name]
Hi [First Name],
I want to be straight with you about something.
We have decided to retire [Offer Name] effective [date]. This means we will not be accepting new students, and I want to explain why — and what it means for you specifically.
[One of the following, as applicable:]
Version A (Product not delivering promised results): After reviewing the results our students have achieved and being honest about where the gaps are, I am not comfortable continuing to sell this offer in its current form. You deserve better than I built.
Version B (Strategic pivot): We are focusing our energy on [New Offer / Direction], which does [specific thing] better than this offer could. This is a strategic decision, not a quality issue.
What this means for you:
If you are currently in the programme — you will continue to have access to everything you purchased until [specific date]. Nothing is being removed from your account.
If you would like a refund — I will honour a full refund regardless of where you are in the programme and regardless of whether you are within the standard refund window. Email [email] with 'Refund Request' in the subject line.
If you would like to move to [Alternative Offer] — [specific transition offer if applicable].
I am sorry if this is disruptive. It is the right call.
[Your name]
PHASE 6
Post-Kill Intelligence Extraction
The data from a killed offer is worth more than the revenue it generated
The Intelligence Extraction Principle
A killed offer generates more actionable intelligence than a successful one — because failure reveals the exact fracture lines in your assumptions about the market. Every operator who kills an offer without systematically extracting its intelligence is discarding the most expensive education they will ever receive.
Kennedy on Failed Offers
Every failed offer is a message from the market. The market never lies. It does not explain itself. But if you build a system for reading what it is saying — through refund language, dropout patterns, support tickets, and buyer interviews — it will tell you everything you need to know about what to build next.
The Post-Kill Intelligence Form
Complete this form within 3 days of the kill decision. File in Airtable under Kill Records. Do not complete it weeks later — the clarity of the post-mortem degrades rapidly with time.
Field
What to Document
Kill Record ID
Autonumber — auto-generated
Offer name and version
Full offer name + which version was killed (V1, V2, etc.)
Kill date
Kill trigger type
Hard Kill (specify HK code) / Scorecard-based Kill (record final scorecard score) / Strategic Kill
Final scorecard score
Record all 15 dimension scores and the total. This is the permanent benchmark.
Total buyers
How many people purchased before the kill
Total revenue
Gross revenue generated before kill
Total refunds
Number and percentage
Net revenue
After refunds
Total ad spend
All paid acquisition costs associated with this offer
ROAS (if applicable)
Net revenue / ad spend
The single most important lesson
In one sentence: what did this offer teach you that you did not know before? This should be specific enough to change a specific future decision.
The copy gold
Top 5 buyer language phrases mined from this offer's data (verbatim). These survive the kill and go directly into the next offer's copy brief.
The assumption that was wrong
What did you believe about the market, the buyer, or the mechanism that this offer's failure proved incorrect?
The Negative Avatar defined
Which Negative Avatar archetype was most commonly attracted? What specific language attracted them? (Links to Negative Avatar Airtable table)
The Next Problem Signal
Did this offer's buyers reveal a Problem B — the thing they needed next that you have not yet built? Document it here.
What the market actually wanted
Based on all available data — what offer would have served this audience correctly?
What was preserved
List any copy assets, mechanism names, buyer relationships, or marketing angles that survive the kill and are being transferred to the next offer brief.
Relaunch eligibility
Yes — conditions defined / No — full retirement / Pivot — specify the pivot direction
Copy and Asset Salvage Protocol
Before the killed offer's folder is archived, run this salvage protocol. Assets that survive the kill are tagged 'Salvage — from [Offer Name]' and moved to a dedicated Salvage folder that feeds into future offer development.
Asset Type
Salvage Criteria
What to Do With It
Buyer language from email replies
All tagged phrases from Phase 3 of the Forensic Audit (PAIN-ACUTE, PAIN-CHRONIC, DESIRE-HIDDEN, OBJECTION tags)
Move to the Master Language Mining database. Tag source as 'Kill Salvage — [Offer Name]'. These phrases are valid regardless of whether the offer worked.
Testimonials from buyers who got results
Any testimonial where the buyer achieved a specific, measurable result that can be attributed to the mechanism
Move to proof library. Can be used in the next offer if the mechanism is preserved. Cannot be used if the mechanism is killed and replaced.
Exit interview recordings
All recordings
Archive in Google Drive. Tag with date and offer name. Transcripts extracted and stored in language mining database.
Sales page copy — performing sections
Sections of the sales page where heatmap data showed high engagement, low bounce, or direct scroll-to-CTA behaviour
Save as 'High-engagement copy segments' in copy swipe file. Even in a failed offer, some sections worked.
Email sequence — high-open-rate emails
Any email in the 14-day sequence that achieved above 35% open rate
Archive the subject line and the opening paragraph. These are proven attention-capturing elements independent of the offer.
The mechanism name (if not killed)
If the pivot/iterate decision preserved the mechanism name — the name goes directly into the next offer brief
Transfer to next offer's MVO Playbook Phase 2 document as the named mechanism.
PHASE 7
The Resurrection Protocol
The specific conditions under which a killed offer can be relaunched
What Qualifies for Resurrection
Not every killed offer should stay dead. Some offers fail at the wrong time, to the wrong audience, with the wrong positioning — but the underlying mechanism and transformation are valid. The Resurrection Protocol defines the conditions under which a killed offer can return to market, and the required changes before it does.
The Non-Negotiable Gap
A killed offer must remain off the market for a minimum of 90 days before any relaunch consideration. This gap allows buyer memory of the original failure to fade, provides time for the market conditions to shift, and — most importantly — forces genuine rebuilding rather than cosmetic changes. Any relaunch before 90 days is a patch. After 90 days, it can be a real revision.
The Resurrection Criteria Checklist
Every item in this checklist must be completed before a killed offer re-enters the market. No partial exceptions.
Requirement
What It Means
How to Evidence Completion
Minimum 90-day gap from kill date
The offer has been off the market for at least 90 calendar days
Kill date in Airtable Kill Record. Today's date minus kill date is ≥ 90.
Root cause identified and addressed
The specific reason the offer failed (from Phase 5 Kill Record, 'The assumption that was wrong' field) has been specifically addressed in the rebuilt offer
Updated offer brief documents the specific change made in response to the identified root cause. One change per root cause — not vague 'improvements.'
New buyer interviews conducted
Minimum 3 new buyer interviews with the intended target avatar conducted after the kill — not from the original buyer pool
Interview transcripts dated after the kill date. Must include at least one person who was NOT a buyer of the original offer.
Offer rebuilt from copy brief, not from the original
The new version was written from a fresh copy brief using the Post-Kill intelligence, not by editing the original sales page
New copy brief document in Airtable dated after kill. If the sales page draft clearly resembles the original with light edits — it is not a rebuild. Start over.
Negative Avatar profiles from original offer are active
The Negative Avatar Profiles created from the original offer's data are deployed in the new offer's repulsion system: 'Not for you' copy, ad exclusions, and application gates
New offer's sales page 'Not for you' section includes at least one bullet per active Negative Avatar Profile. Ad exclusion list updated.
Beta cohort run before public relaunch
A minimum of 5-buyer paid beta is run on the rebuilt offer before the public sales page goes live
Beta Testing SOP records in Airtable. Beta scorecard passed (Go/No-Go thresholds met). Beta dated after kill.
Permanent Retirement — When Not to Resurrect
Some killed offers should stay killed. These conditions indicate permanent retirement with no resurrection path:
• The market the offer was designed for no longer exists or has been commoditised to the point where profitable differentiation is not achievable.
• The primary mechanism has been replicated by a better-resourced competitor and can no longer be positioned as differentiated.
• The offer generated three or more legal complaints, regulatory reviews, or FTC scrutiny — regardless of their outcome. The reputation risk of the specific offer persists beyond the compliance resolution.
• The Post-Kill Intelligence Form's 'assumption that was wrong' field reveals that the market does not actually have the problem the offer was designed to solve. This is not a copywriting problem — it is a market existence problem.
• The offer's total cost (ad spend, time, legal, support) exceeded its total revenue — and the rebuilt version cannot be demonstrated via the beta to achieve different unit economics.
PHASE 8
The Zombie Offer Audit
Finding and killing the offers that should have died months ago
What a Zombie Offer Is
A Zombie Offer is one that is technically still live — it has a sales page, it may even have a small email sequence, it may be listed on the offer wall — but it is generating near-zero revenue, receiving near-zero traffic, and consuming operational resources through the mere fact of its continued existence.
The Zombie Offer Problem
Zombie offers cost you in three ways. First, they consume the mental space of being 'things that need attention eventually.' Second, they occasionally attract wrong-fit buyers who stumble on old content, generating support tickets and refund requests on an offer nobody is actively managing. Third, they distort your offer wall and create confusion for buyers about which path to take. Kill them.
The Quarterly Zombie Audit
Run this audit on the first Monday of every quarter. Any offer that meets the Zombie Criteria below is placed on a 30-day remediation watchlist. If it fails to recover within 30 days, it is killed using the Clean Kill Process.
Zombie Criterion
Threshold
Why It Qualifies
Revenue below floor for consecutive months
Below $500 gross revenue for 3 consecutive months for any offer priced above $97
At this revenue level, the offer is not covering its own operational overhead — support, payment processing, platform fees, and email sends.
No new buyers in 60+ days
Zero new purchases in 60+ consecutive days
An offer with no buyers for 60 days is effectively dead. It is consuming a sales page URL, a purchase flow, a delivery system, and an email sequence for zero return.
Traffic below viable testing threshold for 90 days
Fewer than 50 unique visitors per month for 90+ consecutive days
Below 50 monthly visitors, there is no data being generated. The offer is neither working nor failing — it is simply invisible. That is not a business; it is an archive.
No active promotional activity for 60 days
No email campaigns, no ad spend, no organic content referencing the offer in 60+ days
If you have not promoted an offer in 60 days, you have already informally killed it. Formalise that decision with the Clean Kill Process and archive the assets properly.
The 30-Day Remediation Protocol
Any offer flagged in the Zombie Audit is given a single 30-day remediation window before the kill decision is finalised. The remediation must be active — not passive observation.
1. Run the Kill Assessment Scorecard (Phase 3) immediately on the flagged offer. If the score is below 25, skip remediation — proceed directly to Kill.
2. If the scorecard score is 25 or above, identify the single highest-leverage change that could revive the offer within 30 days. One change only.
3. Implement the change and drive minimum 100 unique warm visitors to the offer page within the 30-day window.
4. At day 30, re-run the scorecard. If the score has not improved by at least 8 points — kill the offer.
5. If the score has improved by 8+ points but is still below Scale threshold — run the iterate protocol for one more 30-day cycle only. Two cycles maximum before kill.
Kill Records Database — Airtable Schema
All kill decisions, post-kill intelligence, and resurrection assessments are stored in a dedicated Kill Records table, linked to the Offers table, the Negative Avatar Profiles table, and the Forensic Audit records.
Kill Records Table
Field
Type
Notes
Kill Record ID
Autonumber
Format: KILL-[Year]-[Seq]. E.g. KILL-2026-003
Offer
Link → Offers table
The offer that was killed
Kill date
Date
Kill type
Single select
Hard Kill (HK-1 through HK-7) / Scorecard Kill / Strategic Kill / Zombie Kill
Hard Kill trigger code
Single select
HK-1 through HK-7 — or N/A for scorecard kills
Final scorecard score
Number
0–60. All 15 dimension scores stored in long text field.
All 15 dimension scores
Long text
Each dimension name + score, one per line
Total buyers at kill
Number
Gross revenue
Currency
Net revenue (after refunds)
Currency
Total ad spend
Currency
ROAS
Formula
Net revenue / ad spend — auto-calculated
The single most important lesson
Long text
One sentence — specific enough to change a future decision
The assumption that was wrong
Long text
What was believed vs. what the data proved
What the market actually wanted
Long text
Based on all data — what offer would have worked
Preserved assets
Long text
Copy, mechanism names, buyer language, testimonials — what survived
Negative Avatar profiles created
Link → Negative Avatar Profiles
All profiles that emerged from this offer's failure data
Next Problem Signal
Long text
Problem B if identified — feeds product roadmap
Relaunch eligibility
Single select
Yes — conditions defined / No — permanent retirement / Pivot — direction specified
Relaunch conditions (if eligible)
Long text
Specific conditions that must be met before resurrection
90-day relaunch consideration date
Date
Kill date + 90 days — auto-populated
Resurrection record
Link → Offers table
If the offer was relaunched — link to the new offer record
Master Kill Criteria Checklist
Before Any Kill Decision — Pre-Kill Diagnostic
☐ Minimum 200 unique cold visitors have seen the offer
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — PRODUCT KILL CRITERIA (POST-LAUNCH) ",
"",
"The Objective System for Deciding When to Kill, Pivot, Iterate, or Scale Any Offer",
"Kennedy × Hormozi × Brunson × 2026 Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"Most operators apply rigorous kill logic before launching an offer — kill filters, viability scoring, 6-score monetisation tests — and then never apply equivalent logic after the offer is live. The result is a business carrying dead or dying offers that consume operational bandwidth, advertising budget, and emotional energy while producing little or no return.",
"",
"This SOP defines the post-launch system for making objective kill, pivot, iterate, or scale decisions at every stage of an offer's lifecycle. It eliminates the sunk-cost thinking that keeps broken offers alive, provides the specific numerical thresholds that determine each decision, and defines the process for killing an offer cleanly — archiving its intelligence, honouring existing buyers, and extracting every lesson before the door closes.",
"",
"Kennedy's Kill Rule",
"The most expensive thing in your business is an offer you should have killed six months ago. It is consuming ad spend, support bandwidth, team attention, and your own belief in the market. Kill it. Learn from it. Build the next one smarter. The trail of killed offers is not a sign of failure — it is the evidence that you are iterating toward something that works.",
"",
"Hormozi's Fuel Rule",
"Never add fuel to a broken vehicle. Scaling traffic, increasing ad spend, or adding more affiliates to an offer that has not passed its kill-or-scale assessment is how operators spend $50K proving what $5K of organic data already told them. Fix the vehicle first. Then add fuel.",
"",
"Brunson's Funnel Law",
"You are one funnel away from success — but only if you are willing to kill the ones that are not working. The operators who win are not smarter. They are faster at recognising what is not working and more willing to cut it.",
"",
"The Sunk Cost Problem: Why Offers Stay Alive Too Long",
"Before the kill criteria, the system must confront the reason those criteria are so rarely applied. The sunk cost fallacy — the tendency to continue investing in something because of prior investment rather than future potential — kills more businesses slowly than any market condition ever has.",
"",
"Sunk Cost Bias",
"How It Manifests",
"The Rational Counter",
"Time investment bias",
"'I spent 3 months building this. I can't just kill it.'",
"The 3 months are gone regardless of what you decide today. The only question is whether the next 3 months goes into a working offer or a broken one.",
"Identity attachment",
"'This offer represents my core methodology. Killing it feels like killing part of myself.'",
"The methodology survives the offer. Rename the mechanism. Repackage the IP. Kill the specific execution that is not working — not the expertise behind it.",
"Audience validation hunger",
"'People say they love this offer even if they're not buying.'",
"Compliments are not revenue. Kennedy: 'Validate with dollars, not compliments.' If the audience loves it and will not pay for it, the market has spoken.",
"Optimism bias",
"'I just need to fix one more thing and it will work.'",
"Define in advance what 'one more thing' means. If you have already made three 'one more thing' changes and the metrics have not moved, the problem is structural — not fixable with incremental iteration.",
"Social proof protection",
"'I have testimonials from this offer. If I kill it, I lose the social proof.'",
"Testimonials belong to the buyer and the result, not the offer format. Testimonials from a killed offer can be repurposed in a new, better offer that serves the same transformation.",
"Sunken ad spend",
"'I've spent $8K in ads to prove this. I need to recoup that before stopping.'",
"The $8K is already spent. Continuing to run an unworkable offer to recoup sunk ad cost will result in spending $16K to prove what $8K already proved. Cut the loss now.",
"",
"The Pre-Commitment Solution",
"The most effective way to override sunk cost bias is to define your kill criteria before launch — not during the emotional heat of a failing offer. This SOP works best when you set your kill thresholds at the point of launch, file them in Airtable, and commit to honouring them regardless of how the offer makes you feel at the point of decision.",
"",
"",
"The Offer Lifecycle Model",
"Kill criteria are not static. An offer at day 7 is held to completely different standards than an offer at day 90. Applying day-90 thresholds to a day-7 offer produces false kills. Applying day-7 thresholds to a day-90 offer allows zombie offers to survive indefinitely. The lifecycle model defines which metrics and which thresholds apply at each stage.",
"",
"Stage 1\nLaunch",
"Days 1–14",
"Proof of market response",
"Stage 2\nValidation",
"Days 15–45",
"Conversion rate signal",
"Stage 3\nTraction",
"Days 46–90",
"Unit economics viability",
"Stage 4\nScale",
"Days 91–180",
"Paid traffic profitability",
"Stage 5\nDecline",
"180+ days",
"Renewal and ascension rate",
"",
"Stage-Specific Assessment Points",
"Stage",
"Primary Question",
"Key Metric",
"Decision at This Stage",
"Stage 1 — Launch\n(Days 1–14)",
"Is anyone responding to this offer at all?",
"First sale: did any paying buyers emerge without heavy persuasion from a warm audience within 14 days?",
"If zero sales from a warm list of 500+ after a proper 7-day launch sequence: trigger Stage 1 Kill Assessment. Do not move to paid ads.",
"Stage 2 — Validation\n(Days 15–45)",
"Is the conversion rate statistically viable for the offer type?",
"Cold conversion rate after 200+ unique visitors. Warm conversion rate after full email sequence delivery to warm list.",
"If cold conversion remains below threshold after 300+ visitors and one round of copy iteration: trigger Full Kill Assessment (Phase 3 scorecard).",
"Stage 3 — Traction\n(Days 46–90)",
"Do the unit economics work?",
"Cost Per Acquisition vs. Offer Price ratio. Refund rate. Support cost per buyer. LTV:CAC ratio.",
"If unit economics fail the Stage 3 thresholds after genuine traffic investment: trigger Full Kill Assessment. Do not scale.",
"Stage 4 — Scale\n(Days 91–180)",
"Is this offer still working as ad spend increases?",
"ROAS by platform. CPA trend (improving, flat, or worsening). Ascension rate to next tier.",
"If ROAS declines below 2.0x and CPA exceeds 35% of offer price for 21+ consecutive days: trigger Scale-to-Iterate or Kill decision.",
"Stage 5 — Decline\n(180+ days)",
"Is this offer earning its continued existence?",
"Month-over-month revenue trend. Mechanism freshness (see Forensic Audit SOP). Competitive landscape shift.",
"If revenue has declined 40% from peak for 60+ consecutive days with no identifiable external cause: trigger Full Kill Assessment or Relaunch Protocol.",
"",
"",
"PHASE 1",
"The Pre-Kill Diagnostic",
"Rule out fixable problems before killing — so you only kill when death is actually warranted",
"",
"The Diagnostic Purpose",
"The Pre-Kill Diagnostic exists because most offers that appear to be dying are not actually broken at the offer level — they are broken at the traffic, copy, or distribution level. Killing a valid offer because the ad creative was stale or the email subject line was weak is an extremely expensive mistake. This diagnostic rules out six fixable causes before the kill assessment begins.",
"",
"The Rule",
"Do not enter the Kill Assessment (Phase 3) until every item in the Pre-Kill Diagnostic has been addressed. If any diagnostic item is unresolved, fix it first — then measure again for the minimum window specified. Only enter Kill Assessment if the metrics fail after the diagnostic fixes have been applied.",
"",
"The Six Fixable Causes of Poor Performance",
"Fixable Cause",
"Diagnostic Question",
"Evidence That This Is the Problem",
"Minimum Fix & Retest Window",
"Traffic volume insufficient",
"Have at least 200 unique cold visitors seen this offer (300+ preferred for statistical significance)?",
"Conversion rate data is based on fewer than 200 unique cold visitors. Any rate below 200 visits is noise, not signal.",
"Drive 200+ unique visitors through organic promotion or minimal paid spend ($300–$500 test budget) before assessing cold conversion rate.",
"Traffic source mismatch",
"Is the traffic source aligned with the awareness level the offer page assumes?",
"Cold traffic is landing on a page written for warm or hot traffic. Sales page assumes prior relationship or context the visitor does not have.",
"Audit the first 500 words of the sales page for assumed context. Rewrite the lead assuming zero prior awareness. Retest for 7 days.",
"Copy — headline not tested",
"Has the headline been A/B tested with at least 2 meaningfully different angles?",
"Single headline has been running since launch. No split test data.",
"Write 3 headline variants (pain hook, desire hook, mechanism hook). Run split test for minimum 14 days or 200 visitors per variant. Decision only after test concludes.",
"Email sequence — not complete or not deployed",
"Has the full 14-day email sequence been deployed to the warm list?",
"Fewer than 10 emails have been sent, or the sequence was stopped early, or the list size was fewer than 200 subscribers.",
"Complete the full 14-day sequence to a list of 200+ subscribers. Assess warm conversion rate after the sequence concludes.",
"Guarantee — not sufficiently strong",
"Has a meaningful guarantee been tested against the current version?",
"Current guarantee is a basic 30-day money-back with no conditions or commitment language. Has never been upgraded.",
"Test the Level 3 guarantee (result-based conditional) against current guarantee for 14 days. If conversion lifts 15%+ — guarantee was the problem, not the offer.",
"Offer stack — not presented clearly",
"Has the full value stack (bonuses, mechanism, deliverables, guarantee, social proof) been tested in the Brunson Stack Slide format?",
"Sales page does not have a visual offer stack with individual bonus values listed. The offer is described narratively without a stacked presentation.",
"Rebuild the sales page's offer section as a Stack Slide: list each component, assign a standalone value, show total value vs. asking price. Retest for 14 days.",
"",
"Pre-Kill Diagnostic Checklist",
"Complete this checklist before opening a kill assessment. Every item marked 'Not yet addressed' must be actioned and retested before proceeding to Phase 3.",
"",
"Diagnostic Item",
"Status",
"Retest Window",
"Cleared?",
"Minimum 200 unique cold visitors have seen the offer",
"☐ Yes ☐ No",
"N/A if yes; drive traffic first if no",
"☐",
"Traffic source awareness level matches sales page assumption",
"☐ Matched ☐ Mismatch",
"Fix + 7 days",
"☐",
"Minimum 2 headline variants A/B tested",
"☐ Yes ☐ Not yet",
"14 days / 200 visitors per variant",
"☐",
"Full 14-day email sequence deployed to 200+ warm subscribers",
"☐ Yes ☐ Not yet",
"Deploy and wait for sequence to complete",
"☐",
"Level 3 guarantee tested against current guarantee",
"☐ Yes ☐ Not yet",
"14 days split test",
"☐",
"Stack Slide offer presentation tested",
"☐ Yes ☐ Not yet",
"14 days after implementation",
"☐",
"",
"",
"PHASE 2",
"Hard Kill Triggers",
"Automatic — if any of these conditions are met, the offer is killed immediately, no scorecard required",
"",
"The Hard Kill Principle",
"Hard Kill Triggers are non-negotiable. They represent conditions that cannot be iterated out of, that create unacceptable risk to the business or its buyers, or that indicate a fundamental structural incompatibility between the offer and the market. When any Hard Kill Trigger is met, the offer is killed within 48 hours. No scorecard. No deliberation. No 'one more try.'",
"",
"Why No Deliberation",
"The purpose of defining Hard Kill Triggers in advance is to remove the decision from the emotional present and place it in the rational past. You are not deciding whether to kill the offer when you are emotionally invested in it. You decided the conditions for killing it before you launched it. Now you are just honouring that decision.",
"",
"Trigger",
"Threshold",
"Rationale",
"Action Timeline",
"HK-1: Catastrophic refund rate",
"Refund rate exceeds 30% of total sales after a minimum of 20 sales",
"A refund rate above 30% indicates a systematic failure in promise delivery or a fundamental mismatch between what was sold and what was received. This is not fixable with copy changes — the offer is broken at the product level.",
"Kill within 48 hours. Pause all ads immediately. Begin Post-Kill Protocol.",
"HK-2: Legal or compliance violation identified",
"Any confirmed violation of FTC guidelines, TCPA regulations, platform terms of service, or applicable consumer protection law",
"Legal exposure compounds exponentially the longer a non-compliant offer remains live. Compliance violations can result in platform bans, financial penalties, and reputational damage that far exceeds any revenue from the offer.",
"Kill within 24 hours. Consult legal counsel before relaunch. Do not attempt to fix and relaunch without written legal clearance.",
"HK-3: Fulfilment breakdown — unable to deliver",
"You are materially unable to deliver the core promise of the offer to existing or new buyers",
"Continuing to sell an offer you cannot deliver is both legally and ethically indefensible. Fulfilment breakdown triggers immediate offer suspension, not iteration.",
"Suspend new sales within 24 hours. Communicate with existing buyers within 48 hours. Full refund offered to all buyers unable to receive delivery.",
"HK-4: Zero warm conversion after complete sequence",
"Zero sales from a warm list of 500+ after a full 14-day email sequence has been deployed, with at least 25% open rate confirmed",
"A 25%+ open rate confirms the sequence was read. Zero purchases from 500+ warm subscribers who read the sequence means the offer is rejected by people who know, like, and trust you. This is the harshest market signal available.",
"Kill within 7 days. Do not move to cold paid traffic. Begin Post-Kill Protocol.",
"HK-5: Cold conversion remains below 0.3% after diagnostic complete",
"Cold conversion rate remains below 0.3% after all six Pre-Kill Diagnostic fixes have been applied and retested over a minimum of 300 unique cold visitors",
"0.3% is the absolute floor for any offer that can ever be made profitable through paid advertising. Below 0.3% with a clean diagnosis means the offer itself is the problem — not the copy, not the traffic.",
"Kill within 14 days of confirmed diagnostic completion. Do not spend further on ads.",
"HK-6: Negative NPS after 20+ responses",
"Net Promoter Score falls below -10 after a minimum of 20 buyer survey responses",
"An NPS below -10 means your detractors significantly outnumber your promoters. This offer is actively generating negative word-of-mouth at a rate that will compound against every future launch.",
"Kill within 7 days of confirmed NPS threshold. Conduct emergency buyer interviews. Do not run this offer again without rebuilding from scratch.",
"HK-7: CPA exceeds 60% of offer price after $3,000+ ad spend",
"Cost Per Acquisition exceeds 60% of the offer's sale price after at least $3,000 has been spent testing across at least 2 different audience types",
"At a CPA of 60% of revenue, there is no viable business. After refunds, fulfilment costs, and payment processing fees, the unit economics are deeply negative and cannot be corrected by optimising an offer that the market is systematically rejecting.",
"Kill paid spend immediately. Offer may continue organically if organic conversion is strong. If organic also fails, full kill.",
"",
"",
"PHASE 3",
"The Kill Assessment Scorecard",
"For offers that have not triggered a Hard Kill — the objective scoring system",
"",
"When to Run the Scorecard",
"The Kill Assessment Scorecard is run when an offer has cleared the Pre-Kill Diagnostic (Phase 1), has not triggered a Hard Kill (Phase 2), but is underperforming against its stage-specific thresholds. It produces a numerical score that maps to one of four decisions: Kill, Pivot, Iterate, or Scale.",
"",
"The Scorecard (15 Dimensions — Maximum 60 Points)",
"Score each dimension objectively using the evidence available. Do not round up out of optimism. Do not round down out of frustration. Use the data.",
"",
"Dimension",
"0 Points — Critical Failure",
"1 Point — Below Viable",
"2 Points — Viable",
"3 Points — Strong",
"4 Points — Excellent",
"Your Score",
"Cold conversion rate",
"Below 0.5%",
"0.5–0.9%",
"1.0–1.9%",
"2.0–3.9%",
"4.0%+",
"___",
"Warm conversion rate",
"Below 2%",
"2–4%",
"5–9%",
"10–19%",
"20%+",
"___",
"Refund rate",
"Above 20%",
"15–20%",
"8–14%",
"3–7%",
"Below 3%",
"___",
"Programme completion rate",
"Below 25%",
"25–44%",
"45–59%",
"60–74%",
"75%+",
"___",
"Specific result testimonials (per 10 buyers)",
"0",
"1",
"2–3",
"4–5",
"6+",
"___",
"Email open rate (14-day sequence)",
"Below 15%",
"15–19%",
"20–29%",
"30–39%",
"40%+",
"___",
"Support tickets per buyer (per 30 days)",
"Above 8",
"5–8",
"3–4",
"1–2",
"0–1",
"___",
"CPA as % of offer price",
"Above 50%",
"40–50%",
"25–39%",
"15–24%",
"Below 15%",
"___",
"Ascension rate to next tier",
"Below 3%",
"3–5%",
"6–9%",
"10–14%",
"15%+",
"___",
"Buyer NPS score",
"Below -10",
"–10 to 0",
"1–20",
"21–40",
"41+",
"___",
"Month-over-month revenue trend",
"Declining >20%",
"Declining 5–20%",
"Flat (±5%)",
"Growing 5–19%",
"Growing 20%+",
"___",
"Value Equation audit — Dream Outcome score",
"1–2 (broken)",
"3–4 (weak)",
"5–6 (adequate)",
"7–8 (strong)",
"9–10 (excellent)",
"___",
"Value Equation audit — Perceived Likelihood score",
"1–2 (broken)",
"3–4 (weak)",
"5–6 (adequate)",
"7–8 (strong)",
"9–10 (excellent)",
"___",
"Value Equation audit — Time Delay score",
"1–2 (broken)",
"3–4 (weak)",
"5–6 (adequate)",
"7–8 (strong)",
"9–10 (excellent)",
"___",
"Value Equation audit — Effort & Sacrifice score",
"1–2 (broken)",
"3–4 (weak)",
"5–6 (adequate)",
"7–8 (strong)",
"9–10 (excellent)",
"___",
"",
"Score Interpretation",
"",
"KILL",
"Score 0–24 (out of 60) — or any Hard Kill Trigger fired regardless of score",
"The offer has failed across multiple dimensions and cannot be fixed through incremental iteration. The structural problems are too numerous or too deep. Kill the offer using the Clean Kill Process (Phase 5). Extract all intelligence using the Post-Kill Protocol (Phase 6).",
"",
"PIVOT",
"Score 25–34 — with 3 or more dimensions at 0 or 1",
"The core premise or mechanism may be viable but the execution is failing broadly. Iteration will not fix this — it requires a structural change to the offer format, the target avatar, the pricing tier, or the delivery mechanism. A pivot is not a kill — it is a rebuild that preserves the underlying insight.",
"",
"ITERATE",
"Score 35–44 — with no more than 2 dimensions at 0 or 1",
"Specific, diagnosable problems exist but the offer has real signal. The fix is targeted — not a rebuild. Identify the 2–3 lowest-scoring dimensions. Apply the specific iteration protocol for each. Retest over 30 days. Re-run the scorecard.",
"",
"SCALE",
"Score 45–60 — with no dimension below 2",
"The offer is working. Unit economics are viable. Buyers are getting results. The correct move is to add fuel: increase ad spend by 20%/day maximum, add a second traffic source, launch the affiliate programme for this offer, activate the ascension sequence to the next tier.",
"",
"",
"PHASE 4",
"The Kill vs. Pivot vs. Iterate Decision Framework",
"When the scorecard says Kill or Pivot — making the right structural choice",
"",
"Kill vs. Pivot: The Critical Distinction",
"A Kill and a Pivot both result in the current version of the offer being retired. The distinction is what survives. In a Kill, the offer and the mechanism are both retired — the market has rejected both the delivery and the promise. In a Pivot, the mechanism and the insight are preserved but the execution — the format, avatar, price point, or delivery model — is fundamentally changed.",
"",
"Scenario",
"Correct Decision",
"What Survives",
"What Dies",
"Relaunch Timing",
"The offer fails but exit interviews reveal that buyers wanted the transformation and understood the mechanism — they just could not implement it as designed",
"PIVOT",
"The mechanism name. The core insight. The buyer language mined. The testimonials (partial).",
"The delivery format and price point. The sales page structure. The current fulfilment model.",
"90 days minimum. Rebuild the delivery model (e.g. self-paced course → live cohort, or group → done-for-you).",
"The offer fails and exit interviews reveal that buyers did not understand what they were buying or found the mechanism irrelevant to their actual problem",
"KILL",
"The buyer language (negative avatar data). The email list of buyers. The lessons about what does NOT work.",
"Everything. The mechanism name, the copy, the delivery model, the entire frame. Start fresh.",
"No automatic relaunch. Return to MVO Playbook Phase 1 with accumulated data as the brief.",
"The offer fails and the refund messages consistently describe expecting something fundamentally different from what was delivered",
"PIVOT (copy pivot)",
"The delivery and mechanism. The results that existing buyers did achieve.",
"The sales page positioning, the headline, the promise language. The gap was in how it was sold, not what was delivered.",
"30 days. Rebuild sales copy from scratch using exit interview language. Keep delivery identical.",
"The offer fails and the primary issue is price — buyers consistently cite 'too expensive' or conversion rate is strong at lower price points in A/B testing",
"PIVOT (price pivot)",
"The entire offer. The mechanism. The delivery. The copy.",
"The price point. The implied buyer tier (you may be serving a different income bracket than you targeted).",
"2 weeks. Reprice and relaunch. Monitor whether the new buyer profile changes support load and completion rate.",
"The offer works for a specific sub-segment but not for the broad avatar it was positioned for",
"PIVOT (avatar pivot)",
"The mechanism. The delivery. The results from the working sub-segment.",
"The broad positioning, the broad ad targeting, the generic sales page copy.",
"4 weeks. Narrow the positioning to the sub-segment where results are consistent. Rebuild copy for that specific avatar.",
"",
"Iterate Protocol: The 2-Fix Maximum Rule",
"When the scorecard indicates Iterate, you are permitted to make targeted changes to the lowest-scoring dimensions. The 2-Fix Maximum Rule applies: identify the two lowest-scoring dimensions, implement one specific fix for each, and retest for 30 days before running the scorecard again. Making more than two changes simultaneously makes it impossible to know which fix worked.",
"",
"Failing Dimension",
"Specific Iteration Action",
"Retest Metric",
"Retest Window",
"Cold conversion below 1%",
"A/B test a new headline with a Pain-Acute hook derived from buyer language mining. Do not change any other element on the sales page during the test.",
"Cold conversion rate. Minimum 200 unique visitors per variant.",
"14 days minimum",
"Completion rate below 45%",
"Add a mandatory 72-hour Quick Win to Module 1. The Quick Win must produce a visible, shareable output. Add accountability check-in at hour 48.",
"Module 1 completion rate. Dropout rate at Module 1 boundary.",
"Next cohort cycle",
"Refund rate above 10%",
"Audit the sales page promise against the programme's actual deliverables. Identify the specific gap and fix either the copy (reduce the promise to match delivery) or the delivery (expand the deliverable to match the promise).",
"Refund rate over the following 30 days. Refund root cause codes.",
"30 days",
"NPS below 20",
"Conduct 5 buyer interviews in the first week after purchase. Identify the gap between their expectation at purchase and their experience in delivery. Fix the single most-cited gap.",
"NPS at next survey cycle (30 days). Support ticket volume.",
"30 days",
"Ascension rate below 6%",
"Rewrite the ascension sequence. Change the timing of the ascension offer presentation. Test presenting the Core Offer at Day 14 post-MVO-purchase instead of Day 21 or Day 30.",
"Ascension rate over 60 days.",
"60 days",
"CPA above 35% of price",
"Pause the lowest-performing ad set. Test a new creative format (video vs. static). Test a new audience segment derived from your best-converting buyers' lookalike.",
"CPA over 14 days of new creative.",
"14 days",
"",
"",
"PHASE 5",
"The Clean Kill Process",
"How to retire an offer with integrity — protecting buyers and extracting maximum intelligence",
"",
"The Clean Kill Principle",
"Killing an offer is not an emergency or a shame event. It is a business decision that, executed well, protects your reputation, honours your existing buyers, and produces the intelligence that makes the next offer better. A poorly executed kill — abrupt, unexplained, or disorganised — damages trust with buyers, confuses the market, and wastes the data the offer generated.",
"",
"The 72-Hour Kill Sequence",
"From the moment the kill decision is confirmed, the following sequence must be completed within 72 hours for Hard Kill Triggers (HK-1 through HK-7) and within 14 days for scorecard-based kills.",
"",
"Hour / Day",
"Action",
"Owner",
"Output",
"Hour 0–4",
"Pause all paid advertising for the offer. Immediately. No exceptions. Every additional dollar spent on a killed offer is wasted.",
"Ads manager / founder",
"All active ad campaigns paused. Budget released.",
"Hour 4–8",
"Deactivate or archive the offer page. Redirect the URL to either the homepage, an appropriate alternative offer page, or a 'This offer is no longer available' page that includes a waitlist opt-in.",
"Tech / founder",
"Offer page redirected. URL not returning 404.",
"Hour 8–16",
"Deactivate the email sequence associated with the offer. Any new subscribers who triggered the sequence after the kill decision will not receive offer-specific emails.",
"Email platform / founder",
"Email sequence deactivated. Active sequence recipients noted.",
"Day 1",
"Send the Buyer Communication Email (see template below) to all current buyers who are within their active delivery window. Explain the situation with clarity and without corporate language.",
"Founder (personal tone required)",
"Buyer communication sent. Inbox monitored for 48 hours.",
"Day 1–2",
"Pull all data exports: buyer list, refund records, support ticket archive, community posts, email reply archive, exit interview recordings. Store in designated archive folder.",
"Ops / founder",
"Full data archive in Google Drive / Airtable. Nothing deleted.",
"Day 2",
"Cancel or pause any affiliate commissions on new sales. Notify affiliates of the offer closure with a professional explanation and, where appropriate, an alternative offer to promote.",
"Affiliate manager / founder",
"Affiliate notification sent. Pending commissions reviewed.",
"Day 3",
"Complete the Post-Kill Intelligence Form (Phase 6 template). While the experience is fresh. Do not wait.",
"Founder",
"Post-Kill Intelligence Form filed in Airtable.",
"Day 7 (post-kill)",
"Review the Buyer Communication inbox. Address any unresolved buyer concerns. Process any refund requests that arrived in the kill window.",
"Support / founder",
"All buyer communications resolved.",
"Day 14 (post-kill)",
"Run the Negative Avatar Profile check: do any refund patterns from this offer need a new profile created? Update Negative Avatar Airtable accordingly.",
"Founder",
"Negative Avatar updates complete.",
"",
"Buyer Communication Email Template",
"This email is sent personally from the founder. It is plain text, not designed, and not run through the standard email platform's branded template. It reads like a human being wrote it because a human being should have written it.",
"",
"Buyer Communication Template",
"Subject: An important update about [Offer Name]\n\nHi [First Name],\n\nI want to be straight with you about something.\n\nWe have decided to retire [Offer Name] effective [date]. This means we will not be accepting new students, and I want to explain why — and what it means for you specifically.\n\n[One of the following, as applicable:]\n\nVersion A (Product not delivering promised results): After reviewing the results our students have achieved and being honest about where the gaps are, I am not comfortable continuing to sell this offer in its current form. You deserve better than I built.\n\nVersion B (Strategic pivot): We are focusing our energy on [New Offer / Direction], which does [specific thing] better than this offer could. This is a strategic decision, not a quality issue.\n\nWhat this means for you:\n\nIf you are currently in the programme — you will continue to have access to everything you purchased until [specific date]. Nothing is being removed from your account.\n\nIf you would like a refund — I will honour a full refund regardless of where you are in the programme and regardless of whether you are within the standard refund window. Email [email] with 'Refund Request' in the subject line.\n\nIf you would like to move to [Alternative Offer] — [specific transition offer if applicable].\n\nI am sorry if this is disruptive. It is the right call.\n\n[Your name]",
"",
"",
"PHASE 6",
"Post-Kill Intelligence Extraction",
"The data from a killed offer is worth more than the revenue it generated",
"",
"The Intelligence Extraction Principle",
"A killed offer generates more actionable intelligence than a successful one — because failure reveals the exact fracture lines in your assumptions about the market. Every operator who kills an offer without systematically extracting its intelligence is discarding the most expensive education they will ever receive.",
"",
"Kennedy on Failed Offers",
"Every failed offer is a message from the market. The market never lies. It does not explain itself. But if you build a system for reading what it is saying — through refund language, dropout patterns, support tickets, and buyer interviews — it will tell you everything you need to know about what to build next.",
"",
"The Post-Kill Intelligence Form",
"Complete this form within 3 days of the kill decision. File in Airtable under Kill Records. Do not complete it weeks later — the clarity of the post-mortem degrades rapidly with time.",
"",
"Field",
"What to Document",
"Kill Record ID",
"Autonumber — auto-generated",
"Offer name and version",
"Full offer name + which version was killed (V1, V2, etc.)",
"Kill date",
"",
"Kill trigger type",
"Hard Kill (specify HK code) / Scorecard-based Kill (record final scorecard score) / Strategic Kill",
"Final scorecard score",
"Record all 15 dimension scores and the total. This is the permanent benchmark.",
"Total buyers",
"How many people purchased before the kill",
"Total revenue",
"Gross revenue generated before kill",
"Total refunds",
"Number and percentage",
"Net revenue",
"After refunds",
"Total ad spend",
"All paid acquisition costs associated with this offer",
"ROAS (if applicable)",
"Net revenue / ad spend",
"The single most important lesson",
"In one sentence: what did this offer teach you that you did not know before? This should be specific enough to change a specific future decision.",
"The copy gold",
"Top 5 buyer language phrases mined from this offer's data (verbatim). These survive the kill and go directly into the next offer's copy brief.",
"The assumption that was wrong",
"What did you believe about the market, the buyer, or the mechanism that this offer's failure proved incorrect?",
"The Negative Avatar defined",
"Which Negative Avatar archetype was most commonly attracted? What specific language attracted them? (Links to Negative Avatar Airtable table)",
"The Next Problem Signal",
"Did this offer's buyers reveal a Problem B — the thing they needed next that you have not yet built? Document it here.",
"What the market actually wanted",
"Based on all available data — what offer would have served this audience correctly?",
"What was preserved",
"List any copy assets, mechanism names, buyer relationships, or marketing angles that survive the kill and are being transferred to the next offer brief.",
"Relaunch eligibility",
"Yes — conditions defined / No — full retirement / Pivot — specify the pivot direction",
"",
"Copy and Asset Salvage Protocol",
"Before the killed offer's folder is archived, run this salvage protocol. Assets that survive the kill are tagged 'Salvage — from [Offer Name]' and moved to a dedicated Salvage folder that feeds into future offer development.",
"",
"Asset Type",
"Salvage Criteria",
"What to Do With It",
"Buyer language from email replies",
"All tagged phrases from Phase 3 of the Forensic Audit (PAIN-ACUTE, PAIN-CHRONIC, DESIRE-HIDDEN, OBJECTION tags)",
"Move to the Master Language Mining database. Tag source as 'Kill Salvage — [Offer Name]'. These phrases are valid regardless of whether the offer worked.",
"Testimonials from buyers who got results",
"Any testimonial where the buyer achieved a specific, measurable result that can be attributed to the mechanism",
"Move to proof library. Can be used in the next offer if the mechanism is preserved. Cannot be used if the mechanism is killed and replaced.",
"Exit interview recordings",
"All recordings",
"Archive in Google Drive. Tag with date and offer name. Transcripts extracted and stored in language mining database.",
"Sales page copy — performing sections",
"Sections of the sales page where heatmap data showed high engagement, low bounce, or direct scroll-to-CTA behaviour",
"Save as 'High-engagement copy segments' in copy swipe file. Even in a failed offer, some sections worked.",
"Email sequence — high-open-rate emails",
"Any email in the 14-day sequence that achieved above 35% open rate",
"Archive the subject line and the opening paragraph. These are proven attention-capturing elements independent of the offer.",
"The mechanism name (if not killed)",
"If the pivot/iterate decision preserved the mechanism name — the name goes directly into the next offer brief",
"Transfer to next offer's MVO Playbook Phase 2 document as the named mechanism.",
"",
"",
"PHASE 7",
"The Resurrection Protocol",
"The specific conditions under which a killed offer can be relaunched",
"",
"What Qualifies for Resurrection",
"Not every killed offer should stay dead. Some offers fail at the wrong time, to the wrong audience, with the wrong positioning — but the underlying mechanism and transformation are valid. The Resurrection Protocol defines the conditions under which a killed offer can return to market, and the required changes before it does.",
"",
"The Non-Negotiable Gap",
"A killed offer must remain off the market for a minimum of 90 days before any relaunch consideration. This gap allows buyer memory of the original failure to fade, provides time for the market conditions to shift, and — most importantly — forces genuine rebuilding rather than cosmetic changes. Any relaunch before 90 days is a patch. After 90 days, it can be a real revision.",
"",
"The Resurrection Criteria Checklist",
"Every item in this checklist must be completed before a killed offer re-enters the market. No partial exceptions.",
"",
"Requirement",
"What It Means",
"How to Evidence Completion",
"Minimum 90-day gap from kill date",
"The offer has been off the market for at least 90 calendar days",
"Kill date in Airtable Kill Record. Today's date minus kill date is ≥ 90.",
"Root cause identified and addressed",
"The specific reason the offer failed (from Phase 5 Kill Record, 'The assumption that was wrong' field) has been specifically addressed in the rebuilt offer",
"Updated offer brief documents the specific change made in response to the identified root cause. One change per root cause — not vague 'improvements.'",
"New buyer interviews conducted",
"Minimum 3 new buyer interviews with the intended target avatar conducted after the kill — not from the original buyer pool",
"Interview transcripts dated after the kill date. Must include at least one person who was NOT a buyer of the original offer.",
"Offer rebuilt from copy brief, not from the original",
"The new version was written from a fresh copy brief using the Post-Kill intelligence, not by editing the original sales page",
"New copy brief document in Airtable dated after kill. If the sales page draft clearly resembles the original with light edits — it is not a rebuild. Start over.",
"Negative Avatar profiles from original offer are active",
"The Negative Avatar Profiles created from the original offer's data are deployed in the new offer's repulsion system: 'Not for you' copy, ad exclusions, and application gates",
"New offer's sales page 'Not for you' section includes at least one bullet per active Negative Avatar Profile. Ad exclusion list updated.",
"Beta cohort run before public relaunch",
"A minimum of 5-buyer paid beta is run on the rebuilt offer before the public sales page goes live",
"Beta Testing SOP records in Airtable. Beta scorecard passed (Go/No-Go thresholds met). Beta dated after kill.",
"",
"Permanent Retirement — When Not to Resurrect",
"Some killed offers should stay killed. These conditions indicate permanent retirement with no resurrection path:",
"",
"• The market the offer was designed for no longer exists or has been commoditised to the point where profitable differentiation is not achievable.",
"• The primary mechanism has been replicated by a better-resourced competitor and can no longer be positioned as differentiated.",
"• The offer generated three or more legal complaints, regulatory reviews, or FTC scrutiny — regardless of their outcome. The reputation risk of the specific offer persists beyond the compliance resolution.",
"• The Post-Kill Intelligence Form's 'assumption that was wrong' field reveals that the market does not actually have the problem the offer was designed to solve. This is not a copywriting problem — it is a market existence problem.",
"• The offer's total cost (ad spend, time, legal, support) exceeded its total revenue — and the rebuilt version cannot be demonstrated via the beta to achieve different unit economics.",
"",
"",
"PHASE 8",
"The Zombie Offer Audit",
"Finding and killing the offers that should have died months ago",
"",
"What a Zombie Offer Is",
"A Zombie Offer is one that is technically still live — it has a sales page, it may even have a small email sequence, it may be listed on the offer wall — but it is generating near-zero revenue, receiving near-zero traffic, and consuming operational resources through the mere fact of its continued existence.",
"",
"The Zombie Offer Problem",
"Zombie offers cost you in three ways. First, they consume the mental space of being 'things that need attention eventually.' Second, they occasionally attract wrong-fit buyers who stumble on old content, generating support tickets and refund requests on an offer nobody is actively managing. Third, they distort your offer wall and create confusion for buyers about which path to take. Kill them.",
"",
"The Quarterly Zombie Audit",
"Run this audit on the first Monday of every quarter. Any offer that meets the Zombie Criteria below is placed on a 30-day remediation watchlist. If it fails to recover within 30 days, it is killed using the Clean Kill Process.",
"",
"Zombie Criterion",
"Threshold",
"Why It Qualifies",
"Revenue below floor for consecutive months",
"Below $500 gross revenue for 3 consecutive months for any offer priced above $97",
"At this revenue level, the offer is not covering its own operational overhead — support, payment processing, platform fees, and email sends.",
"No new buyers in 60+ days",
"Zero new purchases in 60+ consecutive days",
"An offer with no buyers for 60 days is effectively dead. It is consuming a sales page URL, a purchase flow, a delivery system, and an email sequence for zero return.",
"Traffic below viable testing threshold for 90 days",
"Fewer than 50 unique visitors per month for 90+ consecutive days",
"Below 50 monthly visitors, there is no data being generated. The offer is neither working nor failing — it is simply invisible. That is not a business; it is an archive.",
"No active promotional activity for 60 days",
"No email campaigns, no ad spend, no organic content referencing the offer in 60+ days",
"If you have not promoted an offer in 60 days, you have already informally killed it. Formalise that decision with the Clean Kill Process and archive the assets properly.",
"",
"The 30-Day Remediation Protocol",
"Any offer flagged in the Zombie Audit is given a single 30-day remediation window before the kill decision is finalised. The remediation must be active — not passive observation.",
"",
"1. Run the Kill Assessment Scorecard (Phase 3) immediately on the flagged offer. If the score is below 25, skip remediation — proceed directly to Kill.",
"2. If the scorecard score is 25 or above, identify the single highest-leverage change that could revive the offer within 30 days. One change only.",
"3. Implement the change and drive minimum 100 unique warm visitors to the offer page within the 30-day window.",
"4. At day 30, re-run the scorecard. If the score has not improved by at least 8 points — kill the offer.",
"5. If the score has improved by 8+ points but is still below Scale threshold — run the iterate protocol for one more 30-day cycle only. Two cycles maximum before kill.",
"",
"",
"Kill Records Database — Airtable Schema",
"All kill decisions, post-kill intelligence, and resurrection assessments are stored in a dedicated Kill Records table, linked to the Offers table, the Negative Avatar Profiles table, and the Forensic Audit records.",
"",
"Kill Records Table",
"Field",
"Type",
"Notes",
"Kill Record ID",
"Autonumber",
"Format: KILL-[Year]-[Seq]. E.g. KILL-2026-003",
"Offer",
"Link → Offers table",
"The offer that was killed",
"Kill date",
"Date",
"",
"Kill type",
"Single select",
"Hard Kill (HK-1 through HK-7) / Scorecard Kill / Strategic Kill / Zombie Kill",
"Hard Kill trigger code",
"Single select",
"HK-1 through HK-7 — or N/A for scorecard kills",
"Final scorecard score",
"Number",
"0–60. All 15 dimension scores stored in long text field.",
"All 15 dimension scores",
"Long text",
"Each dimension name + score, one per line",
"Total buyers at kill",
"Number",
"",
"Gross revenue",
"Currency",
"",
"Net revenue (after refunds)",
"Currency",
"",
"Total ad spend",
"Currency",
"",
"ROAS",
"Formula",
"Net revenue / ad spend — auto-calculated",
"The single most important lesson",
"Long text",
"One sentence — specific enough to change a future decision",
"The assumption that was wrong",
"Long text",
"What was believed vs. what the data proved",
"What the market actually wanted",
"Long text",
"Based on all data — what offer would have worked",
"Preserved assets",
"Long text",
"Copy, mechanism names, buyer language, testimonials — what survived",
"Negative Avatar profiles created",
"Link → Negative Avatar Profiles",
"All profiles that emerged from this offer's failure data",
"Next Problem Signal",
"Long text",
"Problem B if identified — feeds product roadmap",
"Relaunch eligibility",
"Single select",
"Yes — conditions defined / No — permanent retirement / Pivot — direction specified",
"Relaunch conditions (if eligible)",
"Long text",
"Specific conditions that must be met before resurrection",
"90-day relaunch consideration date",
"Date",
"Kill date + 90 days — auto-populated",
"Resurrection record",
"Link → Offers table",
"If the offer was relaunched — link to the new offer record",
"",
"",
"Master Kill Criteria Checklist",
"",
"Before Any Kill Decision — Pre-Kill Diagnostic",
"☐ Minimum 200 unique cold visitors have seen the offer",
"☐ Traffic source awareness level matches sales page assumption",
"☐ Minimum 2 headline variants A/B tested",
"☐ Full 14-day email sequence deployed to 200+ warm subscribers",
"☐ Level 3 guarantee tested against current guarantee",
"☐ Stack Slide offer presentation tested",
"",
"Hard Kill Trigger Check (Run Before Scorecard)",
"☐ HK-1: Refund rate exceeding 30% after 20+ sales?",
"☐ HK-2: Any legal or compliance violation identified?",
"☐ HK-3: Unable to fulfil the core promise to current buyers?",
"☐ HK-4: Zero sales from warm list of 500+ after complete 14-day sequence at 25%+ open rate?",
"☐ HK-5: Cold conversion below 0.3% after diagnostic complete and 300+ unique visitors?",
"☐ HK-6: NPS below -10 after 20+ buyer responses?",
"☐ HK-7: CPA exceeding 60% of offer price after $3K+ ad spend across 2+ audience types?",
"If any Hard Kill Trigger is confirmed — skip the scorecard. Proceed directly to Clean Kill Process (Phase 5).",
"",
"Kill Assessment Scorecard",
"☐ All 15 dimensions scored using available data",
"☐ Total score calculated",
"☐ Decision confirmed: Kill / Pivot / Iterate / Scale",
"☐ If Kill or Pivot: Clean Kill Process initiated within 14 days",
"☐ If Iterate: 2-Fix Maximum Rule applied — no more than 2 changes identified",
"",
"Clean Kill Process (Phase 5)",
"☐ All paid ads paused within 4 hours of kill decision",
"☐ Offer page deactivated or redirected within 8 hours",
"☐ Email sequence deactivated within 8 hours",
"☐ Buyer Communication Email sent within 24 hours",
"☐ Full data export completed within 48 hours — buyer list, refunds, support, emails, recordings",
"☐ Affiliate notification sent within 48 hours (if applicable)",
"☐ Post-Kill Intelligence Form completed within 72 hours",
"☐ Buyer inbox monitored and all responses addressed within 7 days",
"☐ Negative Avatar profiles updated within 14 days",
"",
"Post-Kill Intelligence Extraction (Phase 6)",
"☐ All 18 fields of the Post-Kill Intelligence Form completed",
"☐ Copy Salvage Protocol run — surviving assets tagged and moved to Salvage folder",
"☐ Master Language Mining database updated with all salvaged buyer language phrases",
"☐ Proof library updated with salvageable testimonials (if mechanism preserved)",
"☐ Kill Record filed in Airtable with all linked records",
"",
"Quarterly Zombie Audit",
"☐ All offers reviewed against 4 Zombie Criteria",
"☐ Flagged offers placed on 30-day remediation watchlist",
"☐ Kill Assessment Scorecard run on each flagged offer",
"☐ Single highest-leverage remediation action identified and implemented for each",
"☐ 30-day retest complete — kill decision finalised for any offer not improving 8+ points",
"",
"",
"",
"RISER Nation Master Operating System | Product Kill Criteria (Post-Launch) SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | Product Kill Criteria (Post-Launch) SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
},
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Keep an offer’s promises, delivery and records aligned as it changes
Identify what changed, why and who is affected
Imagine a buyer purchasing because a page promises a bonus that the team retired last month. This is an illustrative scene. The team improved the course but left the promise unchanged. The buyer received a different offer from the one described.
The versioning source proposes recording three things for every change: what changed, the evidence behind it and the people affected. It calls the growing difference between a promise and delivery version drift. Read the six scenarios below as distinct ways that mismatch can arise.
Drift Scenario
How It Happens
The Downstream Cost
Sales page promises a bonus that no longer exists
Bonus was quietly retired because it was outdated or became irrelevant. Sales page was not updated.
Buyer expects the bonus. Does not receive it. Files a support ticket or refund request citing unmet expectation. FTC compliance risk.
Testimonial references a feature that was removed
Testimonial was collected during V1 when a specific module or tool was included. Module removed in V1.3. Testimonial still on sales page.
New buyers purchase expecting the referenced feature. Expectation mismatch at delivery. Trust erosion.
Affiliate promotional copy is outdated
Affiliate created promotional content based on the V1 offer. Offer is now on V2.1. Key differences in promise, price, and guarantee.
Affiliate sends traffic expecting V1. Buyers arrive expecting V1 features. Refund rate from affiliate traffic higher than average. Affiliate relationship damaged when raised.
Sales team quoting wrong price or features
Price changed in V1.4 but sales team was not formally notified. They continue quoting the old price.
Buyers get inconsistent information. Some pay old price, some new. Complaint when buyer discovers they paid more than someone else. Legal exposure on price representations.
Existing buyer refers a friend with wrong information
Existing buyer enthusiastically describes the V1 offer to a friend. Friend purchases expecting V1. Receives V2.1.
Friend is disappointed by differences. Original buyer's trust is damaged. Referral channel contaminated.
Internal team confusion about what is currently live
Team member updating copy refers to the previous version's bonus stack. Builds new email sequence referencing retired modules.
Internal rework. Inconsistent buyer communications. Brand credibility erodes with buyers who notice discrepancies.
The scenarios cover retired bonuses, outdated testimonials, affiliate copy, sales-team quotes, referrals and internal confusion. Each needs a current description and a record of the earlier state. The claim that a fixed number of discrepancies always destroys trust is rhetoric, not a measured threshold.
This source names Kennedy, Hormozi and Brunson as framework influences. The relevant application is to keep offer value, proof and the buyer’s next decision consistent with actual delivery. It does not establish endorsement or guarantee a result. The lesson explains a proposed version-control process; source instructions to email, publish, migrate buyers or roll back an offer are not executed here.
Phase 1 — Distinguish major, minor and patch changes
The source adapts Major.Minor.Patch notation to offers. Read its three examples below. A major change concerns the underlying promise, method or delivery model. A minor change alters a significant component or price. A patch is a small correction or equivalent technical change. These are source conventions, not a universal business standard.
V2.0.0 MAJOR VERSION Fundamental change to mechanism, delivery model, core promise, or target avatar. Existing buyers may need to be grandfathered or migrated. Example: V1 was a self-paced course. V2 is a live cohort with DFY deliverables.
V1.3.0 MINOR VERSION Significant improvement: new module, new bonus, new guarantee tier, price change, significant copy revision, platform change. Example: V1.2 had 3 bonuses. V1.3 adds a 4th bonus and upgrades the guarantee.
V1.2.1 PATCH VERSION Small correction or improvement: copy fix, broken link repair, tool swap with equivalent, minor content update, formatting change. Example: V1.2.0 had a broken download link. V1.2.1 fixes the link.
Use the six numbering rules to keep the sequence, reset behavior, deployment grouping, offer identity, date and internal use explicit. Reversing content should preserve the historical record rather than overwrite it.
Rule
Definition
Example
Rule 1 — Sequential
Version numbers always increase. You cannot go from V1.3.0 back to V1.2.0. If a change is reversed, a new version number is issued (V1.3.1 = reversal of V1.3.0).
V1.3.0 → V1.3.1 (reversal) — not V1.3.0 (re-issue of same number)
Rule 2 — Reset on increment
When a Major version increments, Minor and Patch reset to 0. When Minor increments, Patch resets to 0.
V1.9.3 + Major change = V2.0.0 (not V2.9.3). V1.2.4 + Minor change = V1.3.0 (not V1.2.5)
Rule 3 — One version per deploy
All changes made in a single deployment cycle share one version number. If five changes are made and deployed simultaneously, they constitute one version — not five.
Deploying a new module + a new bonus + a copy update = V1.3.0. Not V1.3.0, V1.3.1, V1.3.2.
Rule 4 — Offer-specific numbering
Version numbers are per-offer, not per-business. Each offer in your value ladder has its own independent version history.
MVO offer: V2.1.0. Core Offer: V1.4.2. These are independent version histories.
Rule 5 — Date stamping
Every version number carries a date stamp in YYYY-MM-DD format.
V1.3.0 (2026-03-15) — the version number and date together form the version identifier.
Rule 6 — Public vs internal versioning
The version number is internal. Buyers are not typically shown the version number. The version number exists for operational control, not for buyer-facing communication.
Sales page does not say 'Version 1.3.0.' Internal records and team communications use the version number.
Version Identifier Format [OFFER CODE]-V[MAJOR].[MINOR].[PATCH]-[YYYY-MM-DD]
Offer Codes are defined at the time each offer is first created and never change. Example codes: MVO / CORE / DWY / DFY / CONT (Continuity) / IC (Inner Circle).
The identifier combines the offer code, version and date. The examples MVO, CORE, DWY, DFY, CONT and IC name proposed codes. If multiple offers occupy one tier, each still needs a unique identity. A code naming a tier alone may not distinguish the offers.
The source says version numbers are normally internal. That does not remove the need to tell buyers what changed when it affects them. Keep the internal identifier separate from a clear explanation of the actual change.
Phase 2 — Classify the change and flag ambiguous cases
The seven categories separate mechanism, delivery, stack, price, guarantee, copy and technology. Read each code and example before deciding how a proposed change fits.
Category
Code
Version Tier
Definition
Examples
Mechanism Change
CAT-M
MAJOR
A change to the named methodology, the core promise, or the fundamental transformation the offer delivers. The most significant change type.
Renaming the mechanism. Changing the core transformation from 'get leads' to 'book calls.' Changing the programme's defining intellectual framework.
Delivery Model Change
CAT-D
MAJOR
A change to the format, modality, or structure through which the offer is delivered. A self-paced course becoming a live cohort is a Delivery Model Change.
Self-paced → live cohort. Group coaching → 1:1. Synchronous delivery → async. 4-week → 8-week programme.
Offer Stack Change
CAT-O
MINOR
A change to what is included in the offer: adding or removing a module, adding or removing a bonus, changing community access, changing tool access.
Adding a new module. Retiring a bonus. Replacing a tool with an equivalent. Adding a monthly live Q&A call.
Pricing and Packaging Change
CAT-P
MINOR
Any change to the price, the payment plan options, or the tier structure of the offer.
Price increase from $297 to $497. Adding a payment plan. Creating a new tier at a different price point.
Guarantee Change
CAT-G
MINOR
Any change to the guarantee structure, conditions, or language — whether strengthening or weakening the guarantee.
Upgrading from 30-day money-back to result-based conditional guarantee. Adding completion requirements to qualify for refund.
Copy and Positioning Change
CAT-C
MINOR (if significant) or PATCH (if minor)
A change to the sales page, email sequence, ad copy, or any buyer-facing language that does not change the underlying offer but changes how it is positioned or described.
New headline test deployed. Email sequence rewritten with buyer language. 'Not for you' section added.
Technical and Platform Change
CAT-T
PATCH (if equivalent) or MINOR (if affects buyer experience)
A change to the tools, platforms, or technical infrastructure through which delivery occurs. Swapping one video host for an equivalent is a Patch. Changing the community platform is a Minor.
Vimeo → Wistia (equivalent: Patch). Facebook Group → Skool Community (new experience: Minor). Broken link fixed (Patch).
The decision tree then asks what the offer is, what the buyer receives or pays, and how the buyer experiences it. Preserve the source’s maintenance exception alongside that tree.
Does this change alter what the offer fundamentally IS — its mechanism, its promise, or its delivery model? If YES → MAJOR version. If NO → continue to step 2.
Does this change alter what the buyer RECEIVES — new or removed modules, bonuses, calls, tools, access — or what they PAY — price, payment plans? If YES → MINOR version. If NO → continue to step 3.
Does this change alter how the buyer EXPERIENCES the offer — copy, positioning, navigation, tool brand? If YES and the experience change is significant → MINOR. If YES and the change is a correction or small improvement → PATCH. If NO → no version increment required.
The No-Change Rule
Some updates do not require a version increment: fixing a typo, correcting a broken image, updating a date reference, or refreshing a resource link without changing the destination. These are maintenance activities, not version changes. Log them in a separate Maintenance Log, not the Changelog.
The rules overlap. An equivalent tool swap appears as both a minor stack change and a technical patch. A typo or broken-link fix appears as patch work, while the maintenance rule exempts some similar corrections from version increments. The source does not resolve every case. Record the classification choice and reason before implementing it.
A change can belong to several categories but one deployment receives one version. The examples imply using the more consequential tier, but a complete mixed-category policy is not supplied. A guarantee called an upgrade may add conditions; evaluate the actual terms rather than assuming the label means stronger protection.
Phase 3 — Record the complete changelog entry
The native template contains fifteen fields, not the master checklist’s stated seventeen. Its example is a fictional record illustrating the format, not a verified RISER change. Keep what was added, removed, promised and planned distinguishable.
Name of the person who made and deployed the change
Sarah Chen
Deployed Date
Required
YYYY-MM-DD format
2026-03-15
Change Summary
Required
One sentence describing what changed. Plain language. No jargon.
Added 'The 30-Day Outreach Playbook' as a new bonus and retired the 'Cold Email Templates' bonus.
Evidence That Triggered This Change
Required
What data, feedback, or signal justified making this change? Link to source where possible.
Exit interview data from V1.2.0 cohort: 8 of 12 buyers cited outreach as their primary struggle post-programme. Cold Email Templates rated 4.2/10 usefulness in pulse surveys. Two buyers mentioned they already had similar templates.
Change Detail
Required
A full description of what specifically changed — what was added, removed, modified, or replaced.
ADDED: 'The 30-Day Outreach Playbook' — a 14-day DM outreach sequence template with 7 LinkedIn post angles and 5 cold email scripts. Hosted in Kajabi as Module 5 Bonus. Estimated standalone value: $197.
REMOVED: 'Cold Email Templates' bonus — 23 email templates. Retired due to low utility scores. Archived in Google Drive under [link] in case of future reinstatement.
Existing Buyer Impact
Required
Does this change affect buyers who purchased before this version? What are they entitled to?
Existing buyers (V1.0.0 through V1.2.1): Entitled to the new bonus. Will be notified via email on 2026-03-16 with access link. Cold Email Templates access maintained until 2026-06-15 for existing buyers who had already accessed it.
Sales Page Updated?
Required
Yes / No / Partial — if Yes or Partial, specify what was changed
Yes — bonus stack section updated. 'Cold Email Templates' removed from stack slide. '30-Day Outreach Playbook' added with $197 value assigned.
Email Sequence Updated?
Required
Yes / No — if Yes, specify which emails were updated
Yes — Day 10 (Bonus Explanation email) updated to reference new bonus.
Affiliate Notification Required?
Required
Yes / No — if Yes, specify which affiliates were notified and when
Yes — 3 active affiliates notified via email on 2026-03-16 with updated promotional copy.
Testimonial Audit Required?
Required
Does this change affect the validity of any current testimonials? List any testimonials that reference the changed elements.
Yes — 1 testimonial specifically mentions 'the cold email templates' by name. Testimonial flagged for version-locking (see Phase 5).
Rollback Plan
Required for MAJOR and MINOR
If this change produces unexpected negative results, how is it reversed?
Rollback: Restore Cold Email Templates access. Remove Outreach Playbook from Kajabi (or retain as optional). Update sales page to revert stack slide. Buyer impact: Notify of rollback, retain access to both during transition.
30-Day Review Date
Required
Date to review the impact of this change on conversion rate, refund rate, and completion rate
2026-04-15
An evidence link explains why a change was considered; it does not prove the change will work. The example’s standalone value and survey claims need real support before use. Its Thirty-Day Outreach Playbook contains a fourteen-day sequence, which is a naming/scope detail to retain. March 15 to April 15 is thirty-one days, despite the thirty-day review label.
The three worked examples follow in full. Compare them with the fifteen required template fields rather than treating their title “complete” as verification.
MVO-V2.0.0 2026-04-01 [MAJOR — CAT-D: Delivery Model Change + CAT-M: Mechanism Change] ► DELIVERY MODEL: Converted from self-paced course to live 4-week cohort model. Buyers now enrolled in cohort start dates rather than immediate self-paced access. ► MECHANISM: Core mechanism renamed from 'The 5-Phase Revenue System' to 'The Forensic Offer Audit Method.' Same underlying principles, new frame reflecting 2026 buyer language from exit interviews. ► GUARANTEE: Upgraded from 30-day money-back to result-based conditional (complete all 4 modules + submit exit survey + not see improvement in conversion rate within 30 days post-programme). ► MODULES: Added live implementation workshop in Week 3. Added 'Hot Seat' format for Week 4 live call. Removed 3 video modules that covered material now delivered in live sessions. ► EXISTING BUYERS: V1.x buyers grandfathered. Self-paced access maintained for 12 months. Invited to attend V2.0.0 cohort at no additional cost as 'Founding Members'. ► EVIDENCE: 68% of V1.x exit interviews cited 'would have preferred live support.' Completion rate V1.x = 41%. Live cohort beta (10 participants) completion rate = 87%.
CORE-V1.3.0 2026-02-10 [MINOR — CAT-O: Offer Stack Change + CAT-P: Price Change] ► ADDED BONUS: 'AI Offer Audit Tool' — a custom GPT that runs buyers' offer drafts through the Value Equation and returns a scored assessment. Assigned standalone value: $297. ► ADDED MODULE: Module 5 — 'Scale Architecture' — covering the transition from $10K to $50K months. 4-video module, total 2.3 hours. Addresses the top gap identified in V1.2.0 exit surveys. ► PRICE CHANGE: Increased from $997 to $1,297. Price change justified by addition of AI tool + new module. Founding member pricing ($997) offered for 72 hours post-announcement to existing community. ► EXISTING BUYERS: Entitled to AI tool and new module at no cost. Access granted automatically on deploy date. Email notification sent same day. ► EVIDENCE: 11 of 14 V1.2.0 exit interview respondents said they would pay more for AI integration. Value Equation audit showed Perceived Likelihood was the lowest-scoring variable — AI tool addresses this directly.
DWY-V1.0.2 2026-01-22 [PATCH — CAT-T: Technical Change + CAT-C: Copy Change] ► TECHNICAL: Replaced Vimeo Pro with Wistia (equivalent CDN performance, better analytics integration with GA4). All video URLs updated. No change to content. ► TECHNICAL: Fixed broken download link for Module 2 Worksheet. Correct file restored at same URL. ► COPY: Corrected typo in Day 7 email subject line ('Sucess' → 'Success'). No content change. ► COPY: Updated Module 3 reference to 'Meta Ads Manager' from 'Facebook Ads Manager' throughout sales page and email sequence. ► EXISTING BUYERS: Not affected. Technical change is transparent to buyers. No notification required.
The major example changes delivery, mechanism, guarantee and modules, beyond its two listed category codes. Its ten-participant beta reports eighty-seven-percent completion; that cannot be a whole-person completion fraction unless another aggregation is used. The minor example’s eleven-of-fourteen interview statement is an illustrative source claim, not proof of willingness to pay in this business. The patch example records a typo despite the maintenance exception.
These examples omit several required fields such as author, rollback details or review date. Their version dates also do not form one consistent history with the later archive examples. Preserve them as separate illustrations, not a production ledger.
Phase 4 — Check all four affected groups
Existing buyers, future buyers, partners and internal teams need different information. Ask what each group expects, what changed and which records or access paths would be affected.
Impact Dimension
Who or What Is Affected
Key Questions
Required Action if Impact Confirmed
Existing Buyer Impact
All buyers who purchased any prior version of this offer
Are they entitled to receive this change? If yes, how do they access it? If no, are they grandfathered or transitioned? Is their experience degraded by this change?
Determine entitlement policy. Draft buyer communication (see Phase 6). Update access if applicable.
Future Buyer Impact
All buyers who will purchase this version and beyond
Does the sales page accurately reflect this version? Does the email sequence match? Is the onboarding experience updated?
All active affiliates and JV partners currently promoting this offer
Does their promotional copy still accurately describe the offer? Is the price still correct? Are any features they highlighted still present?
Audit affiliate copy. Notify affected affiliates. Provide updated promotional assets.
Internal Team Impact
Sales team, support team, community managers, delivery team
Is the sales team aware of the change and quoting correctly? Does support know what existing buyers are entitled to? Does the community manager know what to say?
Team briefing note sent before deploy. Updated FAQs distributed. CRM notes updated.
The entitlement table proposes defaults and exceptions. It is source policy language, not a determination of anyone’s current legal rights. Actual purchase terms, promises and delivery facts need review before any commitment is changed.
Always entitled. Access is automatic. No notification required unless the fix impacts their current experience.
A patch fixes something that should have worked. The buyer paid for working delivery.
N/A — no exceptions. All patches entitle existing buyers.
Minor — content addition (new module, new bonus)
Entitled if the addition strengthens the promise they purchased. Not entitled if the addition represents a fundamental expansion beyond the original scope.
Adding a bonus that delivers the same transformation better: entitled. Adding a bonus that opens a completely new skill area: not required (though often offered as goodwill).
Offer it as a goodwill gesture with a simple notification. Most operators should give the addition — the cost is near-zero and the goodwill is substantial.
Minor — content removal (retired module, retired bonus)
Always entitled to the removed content for a minimum of 90 days after removal — via archive access or PDF.
The buyer paid for specific components. Removing those components without maintaining access violates the original purchase agreement.
If a tool is discontinued by its vendor and no equivalent can be provided, notify buyers, explain the situation, and offer the closest alternative.
Minor — price change
Not entitled to the new price retroactively. Entitled to the offer as it was when they purchased.
Price changes apply to new buyers. Existing buyers purchased at the price that was live at the time of their purchase.
If price decreases significantly, consider offering existing buyers a partial credit as a goodwill gesture.
Minor — guarantee change (upgrade)
Always entitled to the stronger guarantee, retroactively.
A guarantee upgrade benefits buyers. Withholding it retroactively creates a two-class system that generates complaints.
N/A.
Major — delivery model change
Not automatically entitled. A major version is a different product. However, existing buyers should be offered a transition path.
Major versions represent substantial new development. Existing buyers paid for the prior model.
Offer existing buyers access to the new version at a significant discount ('Upgrade Path') or offer them continued access to the prior version for a defined period.
The proposed ninety-day access period for removed content differs from the later removal template’s fourteen-day download buffer and its restriction to people who already accessed the material. The major-change policy proposes an upgrade path or continued access, while its template promises a free transition, a refund option and at least twelve months of prior access. Do not silently treat those as one consistent policy.
The source also proposes retroactive stronger guarantees. That requires defined scope and terms; a label alone does not establish which buyers qualify. The content-added template’s permanent-inclusion promise must be considered alongside the possibility of later retirement. Templates cannot establish permissions or create commitments merely by appearing in a lesson.
Phase 5 — Keep every affected asset synchronized
The source’s Sync Rule says a version is not live until each item is updated or confirmed unnecessary. Its checklist also allows Scheduled with a date before deployment. Scheduled work is not completed work; the source leaves that release condition unresolved.
The checklist has thirty-four items across six groups: nine sales-page checks, seven email checks, four advertising checks, four partner checks, six onboarding/delivery checks and four discovery checks. The monthly scorecard’s forty-item reference is a different count. Preserve all thirty-four actual items below.
Sales Page Assets
☐ Headline and subheadline — do they accurately describe the current mechanism and promise?
☐ Offer stack section — does it list exactly what is currently included, with accurate values?
☐ Bonus section — are all listed bonuses current? Are all retired bonuses removed?
☐ Guarantee section — does it reflect the current guarantee tier and exact language?
☐ Social proof / testimonials — do all testimonials reference features or bonuses that still exist? (See Testimonial Audit below)
☐ Pricing — does it show the current price and all current payment plan options?
☐ 'Not for you' section — does it reflect current Negative Avatar profiles?
☐ FAQ section — are all FAQs consistent with current delivery, price, and guarantee?
☐ Comparison table (if present) — does it accurately describe the current offer vs. alternatives?
Email Sequences
☐ Welcome / onboarding sequence — does it reference current modules, tools, and first steps accurately?
☐ 14-day nurture sequence — do Days 8–10 (mechanism introduction) reference the current mechanism name?
☐ Offer introduction email — does it describe the current offer stack?
☐ Bonus explanation emails — do they describe the current bonuses only?
☐ Objection handling emails — do they address objections relevant to the current version?
☐ Launch sequence (if evergreen) — does it reference current pricing and guarantee?
☐ Abandoned cart sequence — does it reference current price and offer stack?
Paid Advertising
☐ All active ad creatives — do they reference current features, price, and promise?
☐ All active ad copy — are mechanism names, bonus names, and guarantee language current?
☐ Landing pages linked from ads — are they updated?
☐ Retargeting ad variants — are they consistent with current version?
Affiliate and JV Assets
☐ Affiliate promotional swipe copy — does it describe the current offer accurately?
☐ Affiliate email templates — are mechanism names, bonuses, and pricing current?
☐ Affiliate social captions — are they current?
☐ JV landing pages (if custom pages exist for JV partners) — are they updated?
Onboarding and Delivery Materials
☐ Welcome email (post-purchase) — does it accurately describe what they have access to and first steps?
☐ Onboarding survey — are baseline questions still relevant to the current programme structure?
☐ Course platform module titles and descriptions — do they match current content?
☐ Module completion criteria — are they current?
☐ Community welcome message and pinned resources — are they current?
☐ Support team FAQ document — is it updated for this version?
GEO / AEO Schema and Digital Presence
☐ Offer schema markup (Product + Offer JSON-LD) — is pricing, description, and guarantee current?
☐ Pillar article or landing page that describes the offer — is it updated?
☐ LLMs.txt file — if the mechanism name or offer description changed, is it updated?
☐ Google My Business / local listing (if applicable) — is offer description current?
For the page, compare promise, components, guarantee, price and proof with current delivery. For email and ads, check the actual paths a buyer can encounter. Partner assets require their own review; the internal page being current does not update external copy. Delivery materials and support instructions must tell the same story as the sales page.
The discovery group names Product/Offer markup, LLMs.txt and local listings. Their presence is not proof of current eligibility, search compliance or ranking. Check current official guidance during actual implementation, and keep any markup consistent with visible content. This source supplies a checklist, not a tested search setup.
Preserve testimonial context
The four statuses distinguish current transformation accounts, still-applicable feature accounts, retired-feature accounts and price references. Read the treatment and archive rules together.
Testimonial Status
Definition
Sales Page Treatment
Archive Treatment
Version-Current
The testimonial does not reference any feature, bonus, mechanism name, or price that has changed in any version after it was collected. It describes the transformation only.
Use freely on current sales page. No annotation required.
Maintain in active proof library with version tag.
Version-Specific (Usable)
The testimonial references specific features or bonuses that were present in the version when collected and are still present in the current version.
Use on current sales page. Mark with version tag in Airtable for monitoring.
Maintain with version tag. Review at each Minor version change.
Version-Specific (Retired)
The testimonial specifically mentions a feature, bonus, or mechanism name that no longer exists in the current version.
Remove from live sales page immediately. Do not annotate on live page — buyers see the annotation as a red flag.
Archive in proof library with version tag. May be reinstated if the feature is restored.
Price-Specific
The testimonial mentions a specific price paid that is no longer the current price. ('I paid $297 and it was worth every penny.')
Use with caution. If current price is higher, the price reference may create expectations or confusion. Consider requesting a new testimonial from the same buyer without the price reference.
Tag as Price-Specific. Monitor at each pricing change.
The introduction permits retirement or annotation, but the retired-status row and audit protocol call for removal rather than annotation. “Use freely” does not establish consent, accuracy or relevance to a changed offer. A new testimonial should reflect the buyer’s actual experience, not a rewritten endorsement the buyer never gave.
The source’s five-step audit follows. It is a proposed procedure; no buyer is contacted by this lesson.
Read the testimonial for specific feature references: named bonuses, named modules, named tools, specific prices, specific mechanism names.
Check each referenced element against the current version's offer stack and mechanism name.
If any referenced element no longer exists in the current version: tag the testimonial as Version-Specific (Retired). Remove from live sales page. Archive.
Add a note to the changelog entry: 'Testimonial from [Buyer Name] retired from sales page — references [retired element].'
Reach out to the buyer within 30 days of retiring their testimonial to request an updated one based on the current version.
Phase 6 — Match communication to the actual change
The seven-row matrix distinguishes affected patch users, additions, removals, price increases, guarantee upgrades, access changes and major changes. Its advance notice periods differ from the general instruction to notify at deployment. Identify the relevant scope before making a schedule.
Version Tier
Change Category
Communication Required?
Communication Type
Timing
PATCH
Any
No — unless the patch fixes something that directly affected a buyer's experience
If patch fixes a buyer-facing issue: proactive personal email to affected buyers only
Within 24 hours of patch deploy
MINOR
CAT-O: Content added (new bonus or module)
Yes — good news communication
Broadcast email to all existing buyers: 'You've been upgraded'
Same day as deploy or within 24 hours
MINOR
CAT-O: Content removed (bonus or module retired)
Yes — required communication
Email to all existing buyers: access maintenance period, archive link, reason for change
Minimum 14 days BEFORE removal
MINOR
CAT-P: Price increase
Yes — for existing list (not existing buyers)
Email to waitlist and engaged list: 'Founding member pricing closes [date]'. Existing buyers: notification for their awareness, no action required.
7–14 days before price change
MINOR
CAT-G: Guarantee upgrade
Yes — positive communication
Email to all existing buyers notifying them of the stronger guarantee they now have
Same day as deploy
MINOR
CAT-C / CAT-T: Copy or tech change
No — unless the change affects buyer access or experience
If access affected: notify affected buyers directly
Within 24 hours if access affected
MAJOR
Any
Yes — always required
Personal email from founder to all existing buyers: explain what changed, their options, and their transition path
Minimum 21 days before Major version deploys
The matrix does not fully specify price decreases, weakened guarantees or every mixed-category change. Its price-increase row says not existing buyers but then adds an awareness notice to them. These are unresolved details to document. A generic deployment checklist cannot replace twenty-one-day major-change or fourteen-day removal notice described here.
Read all four templates below as source examples with placeholders. Confirm actual access, dates, support channels and promises before any use. Nothing has been sent.
Content Added Communication Template Subject: You've been upgraded — [Offer Name] just got better
Hi [First Name],
Quick message to let you know we just added something to [Offer Name] that I think you'll find genuinely useful.
Based on feedback from the last cohort — specifically the [specific challenge] that came up repeatedly — we've added [specific new bonus/module name]. It does [specific thing it solves].
You have it automatically. Access it here: [link].
This is now part of the offer permanently. If you have questions about it, [specific support channel].
[Your name]
Content Removed Communication Template Subject: A change to [Offer Name] — and what it means for you
Hi [First Name],
I want to give you advance notice of a change we're making to [Offer Name] on [date].
We're retiring [specific bonus/module name]. The reason: [honest, specific reason — outdated, superseded by better resource, low utility scores from recent feedback].
What this means for you: If you've already accessed it and want to keep a copy, download it before [date + 14 days buffer]. After that date, we'll remove it from the platform.
We're replacing it with [new element] — which [specific improvement over the retired element].
If you have any questions about this, reply to this email.
[Your name]
Major Version Communication Template Subject: A significant update to [Offer Name] — your options
Hi [First Name],
I want to be transparent about something we're changing in [Offer Name], and what your options are as someone who has already purchased.
Starting [date], [Offer Name] is moving from [current format] to [new format]. Here's why: [specific evidence — completion rates, buyer feedback, results data].
What this means for you:
Option A: You keep full access to the current version ([V1.x]) until [date — minimum 12 months]. Nothing changes for you unless you want it to.
Option B: You can transition to the new version at no additional cost. If you want to do this, [specific instructions].
Option C: If you feel the change fundamentally alters what you purchased and you'd prefer a refund, I'll honour that — no questions asked. Email [email] by [date].
I built the new version based on what I learned from people like you. I'm confident it delivers better results. But you deserve the choice.
[Your name]
Price Increase Communication Template Subject: [Offer Name] price is going up — here's when and why
Hi [First Name],
On [date], the price of [Offer Name] is increasing from [current price] to [new price].
Why: [honest reason — added a new module, added the AI tool, results data justifies the price, we've invested in improving the delivery]. I want to make sure the price reflects what's actually being delivered.
If you've been thinking about joining — or if you know someone who has — the current price is locked until [date].
After [date], the new price applies to all new purchases.
[Your name]
The addition template promises automatic and permanent access. The removal template restricts its download advice to prior access and a shorter buffer than the entitlement table. The major template offers continued access, free migration and refunds, exceeding the earlier default policy. The price template needs a truthful reason and a real effective date. Do not use illustrative commitments as if they were already approved terms.
Phase 7 — Keep a usable archive and version timeline
The source groups records by offer and major version, then places minor and patch documents inside. The sample tree is an example, not evidence that these folders or releases exist.
Recommended Archive Folder Structure 📁 RISER Nation — Offer Version Archive 📁 MVO-Offer 📁 V1 (2025-06-01 to 2026-01-14) 📄 MVO-V1.0.0-2025-06-01 — Launch Version 📄 MVO-V1.1.0-2025-07-15 — Added LinkedIn bonus 📄 MVO-V1.2.0-2025-09-10 — Price change $197→$297 📄 MVO-V1.2.1-2025-10-03 — Broken link fix (patch) 📄 MVO-V1.3.0-2025-11-20 — New bonus, retired old 📁 V2 (2026-01-15 to present) 📄 MVO-V2.0.0-2026-01-15 — Major: Live cohort conversion 📄 MVO-V2.0.1-2026-02-01 — Zoom link fix (patch) 📁 Core-Offer 📁 V1 (2025-09-01 to present) 📄 CORE-V1.0.0-2025-09-01 — Launch Version [etc.]
Each archive record has nine sections. Preserve the complete snapshot specification below, including proof, partner copy, delivery and known issues.
Archive Document Section
What to Include
Version identifier and date
Full version identifier: [Offer Code]-V[X.Y.Z]-[YYYY-MM-DD]
The changelog entry
Full changelog entry from Phase 3 for this version
Offer stack snapshot
Complete list of every component included in this version: modules (with titles), bonuses (with names and described value), live calls (frequency and format), community access, tool access, and guarantee language. Verbatim from the sales page at time of version deploy.
Sales page snapshot
Full text of the sales page at the time of this version — headline, body copy, offer stack section, guarantee section, FAQ section. PDF export or text copy.
Price at this version
Sale price, payment plan options, and any promotional pricing active at launch of this version.
Active testimonials at this version
List of all testimonials on the live sales page at this version — buyer name, date collected, and version tag.
Affiliate copy at this version
Copy of all affiliate promotional emails, social captions, and swipe files distributed for this version.
Delivery architecture at this version
Summary of the delivery format, tools used, and fulfilment process at this version.
Known issues at this version
Any known bugs, complaints, or performance gaps identified during this version's active period. This feeds directly into the justification for the next version's changes.
A delivery summary and page text are not necessarily enough to restore course files, access permissions, integrations or database state. The claim of complete restoration needs an actual backup and recovery check. Keep originals and dependencies rather than assuming a descriptive document is executable infrastructure.
The timeline provides a quick overview of the version history. Its six sample rows omit a patch shown in the folder tree, so it is not a complete single production history.
Version
Date
Change Summary
V1.0.0
2025-06-01
LAUNCH — Initial public launch. Self-paced course, 4 modules, 3 bonuses, 30-day money-back guarantee at $197.
V1.1.0
2025-07-15
MINOR — Added LinkedIn Outreach Playbook bonus (CAT-O). Justified by exit interview data showing LinkedIn was top unmet channel.
V1.2.0
2025-09-10
MINOR — Price increase $197 → $297 (CAT-P). Justified by new bonus addition and improved completion rate data.
MINOR — Retired Cold Email Templates bonus. Added 30-Day Outreach Playbook. Guarantee upgraded to result-based conditional (CAT-O, CAT-G).
V2.0.0
2026-01-15
MAJOR — Converted from self-paced to live 4-week cohort. Mechanism renamed. Existing buyers grandfathered with 12-month access to V1 (CAT-D, CAT-M).
Phase 8 — Investigate a possible rollback
The source lists five rollback triggers, despite the master checklist referring to four. Each has its own observation window and severity: conversion, refunds, completion, complaints and affiliate conversion. Preserve them all.
Rollback Trigger
Threshold
Detection Window
Severity
Conversion rate drop following a Major or Minor change
Conversion rate falls 25% below the 30-day pre-change average and does not recover within 14 days
30-day post-deploy monitoring window
High — rollback consideration immediately
Refund rate spike following a change
Refund rate increases to 15%+ within 30 days of a change that altered the offer stack or guarantee
30-day post-deploy monitoring
Critical — rollback or change reversal within 72 hours
Completion rate drop following content changes
Completion rate falls 20%+ below the pre-change average within one full cohort or programme cycle
One programme cycle post-deploy
High — content rollback within next cohort cycle
Buyer complaint volume spike tied to specific change
3 or more buyers cite the same specific change as the source of their complaint within 21 days of deploy
21-day post-deploy monitoring
Medium to High depending on complaint severity
Affiliate performance drop tied to copy or stack change
Affiliate traffic conversion rate falls 30%+ below baseline within 21 days of an affiliate-affecting change
21-day post-deploy for affiliate traffic specifically
Medium — rollback or affiliate copy revert
The conversion decline is relative to a thirty-day pre-change average and requires fourteen days without recovery. Refund and completion conditions use different cohorts and windows. Three complaints refer to a particular change but do not by themselves prove its cause. Baseline zeros, low counts and changing traffic mix need explicit treatment before classification.
Rollback means restoring selected prior content under a new record, not erasing history. The source’s seven execution steps follow. They remain instructions within the document, not actions carried out here.
Confirm trigger threshold has been crossed using data from the relevant source (GA4, CRM, email platform, affiliate dashboard). Document the evidence.
Issue a new version number for the rollback. A rollback is not a re-issue of a prior version number — it is a new version that restores prior content. Example: V1.3.0 introduced a problematic change. Rollback is V1.3.1, which restores the V1.2.1 state.
Restore the specific component(s) that are being rolled back using the Version Archive Document for the prior version.
Complete a full Changelog Entry for the rollback version. Under 'Evidence That Triggered This Change' — document the rollback trigger data.
Run the Copy & Asset Sync Checklist (Phase 5) for the rollback version exactly as you would for a forward change.
Complete the Buyer Communication Protocol (Phase 6) if existing buyers are affected by the rollback.
Conduct a post-rollback analysis within 14 days: what assumption was wrong in the forward change? What evidence was missing? Document the finding in the rollback changelog entry.
The patch-number rollback example may restore a change that the earlier taxonomy would call minor or major. That classification conflict remains. The rollback rule also applies full synchronization even though ordinary patch work is exempted elsewhere. Buyer entitlements and missing archived assets require review before a restoration can be considered workable.
The claim that rollback reveals precisely what the market rejects is too strong. It provides observations for investigation, not guaranteed causal knowledge. Retain uncertainty in the fourteen-day post-rollback analysis.
Phase 9 — Review the history at the right cadence
The source proposes five review occasions, with separate durations and outputs. Read every row: deployment, thirty-day follow-up, monthly review, quarterly drift audit and annual review.
Changelog entry filed. All assets updated. Notifications sent.
30 days after each Minor or Major deploy
30-Day Change Review: compare conversion rate, refund rate, completion rate, and support ticket volume against pre-change baseline. Confirm rollback threshold not triggered.
20 minutes
Change Impact Data added to changelog entry's 30-Day Review field.
Monthly (first Monday)
Review all changes made in the prior month. Are 30-day review data points filed? Are any assets still pending update? Are any rollback thresholds being approached?
30 minutes
Monthly Version Status Report.
Quarterly
Version Drift Audit: manually compare the current version's sales page against the Version Archive snapshot for the same offer. Identify any drift that occurred outside the formal versioning system.
90 minutes per active offer
Drift Audit Report. Any undocumented changes retroactively added to changelog and assigned a version number.
Annually
Full version history review: what have been the 3 most impactful changes of the year (by conversion or refund rate delta)? What does the version history reveal about what buyers actually value? Feed findings into the following year's offer development brief.
Half day
Annual Version Intelligence Report. Feeds into product roadmap.
The durations are planning estimates. Monthly first-Monday work overlaps other source review routines and needs coordination, not an automatically created calendar entry. A future review date in a record is not proof that the review happened.
The quarterly audit steps follow. Distinguish what was known at deployment from what was discovered later.
Pull the Version Archive Document for the most recent Minor or Major version of each active offer.
Compare the 'Offer Stack Snapshot' in the archive against what is currently live on the sales page, in the email sequence, and in the course platform.
For every discrepancy found — something present in the live offer that is not in the archive snapshot, or vice versa — document it as an informal change.
For each informal change: assign it a retroactive version number (PATCH if minor, MINOR if significant). Create a changelog entry with 'Retroactive — discovered in Quarterly Drift Audit' noted in the evidence field.
Identify who made the informal change. Update team protocols to ensure all future changes go through the changelog process before deployment.
Comparing only the latest minor or major snapshot may flag legitimate later patches as drift. Review the full version chain. A discovered fundamental change may need a major classification even though this audit instruction mentions only patch or minor. One version per discovered discrepancy can also conflict with one version per actual deployment. Do not fabricate an author, date or earlier evidence to make the history appear complete.
Preserve all three database specifications
The Changelog Entries schema has twenty fields. Compare it with the fifteen-field template: required-versus-sent notifications and partial-versus-not-required statuses are not identical concepts. The review date is a Date field with a described plus-thirty-days behavior; an actual formula or automation is still needed.
Full description of what changed — added, removed, modified
Existing Buyer Impact
Long text
Entitlement and communication plan
Sales Page Updated
Single select
Yes / No / Not Required
Email Sequence Updated
Single select
Yes / No / Not Required
Affiliate Notification Sent
Single select
Yes / No / Not Required
Testimonial Audit Completed
Single select
Yes / No / Not Required
Rollback Plan
Long text
Required for MAJOR and MINOR
30-Day Review Date
Date
Deployed Date + 30 days
30-Day Review Data
Long text
Conversion rate, refund rate, completion rate at 30 days
Rollback Triggered
Checkbox
If any rollback threshold was crossed
Archive Document Link
URL
Link to the Google Drive version archive document
Copy Sync Checklist Completed
Checkbox
All assets confirmed updated or not-required
The Testimonial Version Registry has thirteen fields. Preserve verbatim text, version and current status separately. A written/video/audio format label does not supply the actual media asset.
Field
Type
Notes
Testimonial ID
Autonumber
Buyer Name
Short text
Date Collected
Date
Offer
Link → Offers table
Version at Collection
Link → Changelog Entries
The version that was live when this testimonial was collected
Testimonial Text
Long text
Full verbatim text
Testimonial Format
Single select
Written / Video / Audio
Specific Elements Referenced
Long text
Named bonuses, modules, mechanism names, prices mentioned in this testimonial
Is this testimonial currently deployed on the live sales page?
Date Retired from Sales Page
Date
If retired — when removed
Reason Retired
Short text
Which changed element caused retirement
Updated Testimonial Requested
Checkbox
Has a new testimonial been requested from this buyer?
The Affiliate Copy Audit Log has ten fields. A checked box for updated assets does not prove that a partner received or used them; evidence and dates must support the record.
Field
Type
Notes
Audit ID
Autonumber
Affiliate Name
Short text
Offer
Link → Offers table
Version Audited Against
Link → Changelog Entries
The current live version at time of audit
Audit Date
Date
Assets Audited
Multiple select
Email swipe / Social captions / Landing page / Video script
Discrepancies Found
Long text
Any outdated references to retired features, wrong prices, or wrong mechanism names
Updated Assets Sent
Checkbox
Were new assets sent to the affiliate?
Date Updated Assets Sent
Date
Next Audit Due
Date
Audit every Minor change and quarterly otherwise
The three-table description is not a complete deployed system. It omits a defined Maintenance Log, per-asset scheduled dates and detailed delivery/access state. Links point to dependencies that must actually exist. Preserve those gaps before claiming that every change can be restored or every asset synchronized.
Use the complete master checklist
The five checklist groups cover setup, deployment, thirty-day follow-up, quarterly audit and annual review. Read the original in full, with the corrected counts: fifteen template fields, thirty-four sync checks and five rollback triggers. Every source instruction remains a requirement to evaluate, not a completed action.
System Setup (One-Time)
☐ Create Changelog Entries table in Airtable with all fields from schema above
☐ Create Testimonial Version Registry table and link to Offers table
☐ Create Affiliate Copy Audit Log table
☐ Create Version Archive folder structure in Google Drive for each active offer
☐ Assign offer codes to all active offers (MVO / CORE / DWY / CONT / IC / etc.)
☐ Retroactively document current version of each active offer: create V1.0.0 entry dated at original launch
☐ If offer has already been changed since launch: run Quarterly Version Drift Audit and retroactively version all informal changes
☐ Version-tag all current testimonials in the Testimonial Version Registry
Every Change Deploy (Required Before Going Live)
☐ Assign version tier: MAJOR / MINOR / PATCH using the Change Decision Tree
☐ Complete all 17 fields of the Changelog Entry Template in Airtable
☐ Complete the Change Impact Assessment across all four impact dimensions
☐ Determine existing buyer entitlement using the Entitlement Policy table
☐ Run the Copy & Asset Sync Checklist — mark every item Updated / Not Required / Scheduled
☐ Run the Testimonial Audit — identify and retire any version-specific testimonials
☐ Draft and send all required buyer communications using the Communication Templates
☐ Send affiliate notification if CAT-O, CAT-P, CAT-M, or CAT-D change
☐ Brief internal team (sales, support, community) before deploy
☐ Create Version Archive Document and file in correct subfolder
☐ Set 30-Day Review calendar reminder in Airtable
30 Days After Every Minor or Major Deploy
☐ Pull conversion rate, refund rate, completion rate, and support volume
☐ Compare against pre-change baseline
☐ Check all four rollback thresholds
☐ File 30-Day Review Data in changelog entry
☐ If any rollback threshold crossed: initiate Rollback Protocol
Quarterly Version Drift Audit
☐ Pull Version Archive Document for each active offer
☐ Compare archive snapshot against all live buyer-facing assets
☐ Document all informal changes found — assign retroactive version numbers
☐ Update Testimonial Version Registry — any newly retired testimonials?
☐ Run Affiliate Copy Audit Log for all active affiliates
☐ Brief team on any informal change patterns found — tighten the process
Annual Version Intelligence Review
☐ Pull all changelog entries for the year per offer
☐ Identify 3 highest-impact changes (conversion or refund delta evidence)
☐ Identify any patterns in what triggered the most valuable changes
☐ Write Annual Version Intelligence Report
☐ Feed findings into next year's offer development brief and mechanism rename cadence
The affiliate notification category list in the deployment checklist omits guarantee, copy and technical changes, even though those can affect partners under the impact table. Review actual impact rather than treating a shorter list as permission to ignore affected assets. Annual ranking of changes by observed deltas also does not prove that those changes caused the differences.
RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING. The source’s older footer domain remains preserved as historical text.
Turn in one proposed change record naming the offer, current state, intended change, evidence, affected groups, classification conflicts, asset checks and rollback requirements. Keep it in your course work folder until a submission destination is confirmed. A reviewer should check actual buyer commitments and delivery evidence before any real deployment or communication.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — PRODUCT VERSIONING & OFFER CHANGELOG
The System for Tracking Every Change to Every Offer — So Nothing Gets Lost, Nothing Drifts, Nothing Surprises You
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
Every offer you build will change. Modules get added and removed. Bonuses get retired. Prices shift. Guarantees get upgraded. Live calls get added or reduced. The mechanism gets renamed. Delivery platforms change. These changes happen constantly — which is good, because they reflect learning and iteration.
What is not good is when those changes happen without a system. When the sales page still promises a bonus that no longer exists. When a testimonial references a feature that was retired six months ago. When the affiliate's promotional copy describes an offer that changed three versions ago. When a buyer from last year tries to refer a friend and quotes a price that is no longer accurate. When your own team is uncertain which version of the offer is currently live.
This SOP builds the product versioning and changelog system that prevents all of those failures. It defines a semantic versioning approach adapted from software development, a structured changelog entry protocol, a change impact assessment for every modification, a copy and asset synchronisation system, a buyer communication protocol, a rollback mechanism, and a complete version archive. The system is lightweight by design — the goal is compliance, and compliance requires minimal friction.
The Core Principle
Every change to an offer has three dimensions: what changed, why it changed (the evidence that justified it), and who is affected. A changelog that captures all three creates the institutional memory that makes every future iteration smarter, every affiliate relationship cleaner, and every buyer communication more credible.
The Version Drift Problem: Why This System Exists
Version drift is the gradual, untracked divergence between what is promised on a sales page and what is actually delivered in the current version of an offer. It is not caused by deliberate dishonesty. It is caused by dozens of small, well-intentioned changes made without a documentation system.
Drift Scenario
How It Happens
The Downstream Cost
Sales page promises a bonus that no longer exists
Bonus was quietly retired because it was outdated or became irrelevant. Sales page was not updated.
Buyer expects the bonus. Does not receive it. Files a support ticket or refund request citing unmet expectation. FTC compliance risk.
Testimonial references a feature that was removed
Testimonial was collected during V1 when a specific module or tool was included. Module removed in V1.3. Testimonial still on sales page.
New buyers purchase expecting the referenced feature. Expectation mismatch at delivery. Trust erosion.
Affiliate promotional copy is outdated
Affiliate created promotional content based on the V1 offer. Offer is now on V2.1. Key differences in promise, price, and guarantee.
Affiliate sends traffic expecting V1. Buyers arrive expecting V1 features. Refund rate from affiliate traffic higher than average. Affiliate relationship damaged when raised.
Sales team quoting wrong price or features
Price changed in V1.4 but sales team was not formally notified. They continue quoting the old price.
Buyers get inconsistent information. Some pay old price, some new. Complaint when buyer discovers they paid more than someone else. Legal exposure on price representations.
Existing buyer refers a friend with wrong information
Existing buyer enthusiastically describes the V1 offer to a friend. Friend purchases expecting V1. Receives V2.1.
Friend is disappointed by differences. Original buyer's trust is damaged. Referral channel contaminated.
Internal team confusion about what is currently live
Team member updating copy refers to the previous version's bonus stack. Builds new email sequence referencing retired modules.
Internal rework. Inconsistent buyer communications. Brand credibility erodes with buyers who notice discrepancies.
The Compounding Effect
Each individual drift event seems minor. The compounding effect is what kills trust. A buyer who encounters one discrepancy loses confidence. A buyer who encounters three discrepancies loses the relationship entirely — and reviews reflect it. Version drift is the slow leak that sinks the ship while everyone is busy rowing.
PHASE 1
The Semantic Versioning System
Major.Minor.Patch — adapted from software development for offer management
The Three-Tier Numbering System
Semantic versioning — the Major.Minor.Patch format used in software development — is the clearest and most widely understood versioning convention available. Adapted for offer management, it provides instant communication about the nature and scale of any change.
V2.0.0
MAJOR VERSION
Fundamental change to mechanism, delivery model, core promise, or target avatar. Existing buyers may need to be grandfathered or migrated.
Example: V1 was a self-paced course. V2 is a live cohort with DFY deliverables.
V1.3.0
MINOR VERSION
Significant improvement: new module, new bonus, new guarantee tier, price change, significant copy revision, platform change.
Example: V1.2 had 3 bonuses. V1.3 adds a 4th bonus and upgrades the guarantee.
V1.2.1
PATCH VERSION
Small correction or improvement: copy fix, broken link repair, tool swap with equivalent, minor content update, formatting change.
Example: V1.2.0 had a broken download link. V1.2.1 fixes the link.
Version Numbering Rules
Rule
Definition
Example
Rule 1 — Sequential
Version numbers always increase. You cannot go from V1.3.0 back to V1.2.0. If a change is reversed, a new version number is issued (V1.3.1 = reversal of V1.3.0).
V1.3.0 → V1.3.1 (reversal) — not V1.3.0 (re-issue of same number)
Rule 2 — Reset on increment
When a Major version increments, Minor and Patch reset to 0. When Minor increments, Patch resets to 0.
V1.9.3 + Major change = V2.0.0 (not V2.9.3). V1.2.4 + Minor change = V1.3.0 (not V1.2.5)
Rule 3 — One version per deploy
All changes made in a single deployment cycle share one version number. If five changes are made and deployed simultaneously, they constitute one version — not five.
Deploying a new module + a new bonus + a copy update = V1.3.0. Not V1.3.0, V1.3.1, V1.3.2.
Rule 4 — Offer-specific numbering
Version numbers are per-offer, not per-business. Each offer in your value ladder has its own independent version history.
MVO offer: V2.1.0. Core Offer: V1.4.2. These are independent version histories.
Rule 5 — Date stamping
Every version number carries a date stamp in YYYY-MM-DD format.
V1.3.0 (2026-03-15) — the version number and date together form the version identifier.
Rule 6 — Public vs internal versioning
The version number is internal. Buyers are not typically shown the version number. The version number exists for operational control, not for buyer-facing communication.
Sales page does not say 'Version 1.3.0.' Internal records and team communications use the version number.
Version Identifier Format
Every offer version is identified by four elements combined:
Version Identifier Format
[OFFER CODE]-V[MAJOR].[MINOR].[PATCH]-[YYYY-MM-DD]
Examples:
MVO-V2.1.0-2026-03-15
CORE-V1.4.2-2026-01-08
DWY-V1.0.0-2026-05-20
Offer Codes are defined at the time each offer is first created and never change. Example codes: MVO / CORE / DWY / DFY / CONT (Continuity) / IC (Inner Circle).
PHASE 2
Change Classification Framework
Categorising every type of offer change before it is made
The Seven Change Categories
Every change to an offer falls into one of seven categories. The category determines the version tier (Major, Minor, or Patch), the required impact assessment, the copy update scope, and the buyer communication obligation.
Category
Code
Version Tier
Definition
Examples
Mechanism Change
CAT-M
MAJOR
A change to the named methodology, the core promise, or the fundamental transformation the offer delivers. The most significant change type.
Renaming the mechanism. Changing the core transformation from 'get leads' to 'book calls.' Changing the programme's defining intellectual framework.
Delivery Model Change
CAT-D
MAJOR
A change to the format, modality, or structure through which the offer is delivered. A self-paced course becoming a live cohort is a Delivery Model Change.
Self-paced → live cohort. Group coaching → 1:1. Synchronous delivery → async. 4-week → 8-week programme.
Offer Stack Change
CAT-O
MINOR
A change to what is included in the offer: adding or removing a module, adding or removing a bonus, changing community access, changing tool access.
Adding a new module. Retiring a bonus. Replacing a tool with an equivalent. Adding a monthly live Q&A call.
Pricing and Packaging Change
CAT-P
MINOR
Any change to the price, the payment plan options, or the tier structure of the offer.
Price increase from $297 to $497. Adding a payment plan. Creating a new tier at a different price point.
Guarantee Change
CAT-G
MINOR
Any change to the guarantee structure, conditions, or language — whether strengthening or weakening the guarantee.
Upgrading from 30-day money-back to result-based conditional guarantee. Adding completion requirements to qualify for refund.
Copy and Positioning Change
CAT-C
MINOR (if significant) or PATCH (if minor)
A change to the sales page, email sequence, ad copy, or any buyer-facing language that does not change the underlying offer but changes how it is positioned or described.
New headline test deployed. Email sequence rewritten with buyer language. 'Not for you' section added.
Technical and Platform Change
CAT-T
PATCH (if equivalent) or MINOR (if affects buyer experience)
A change to the tools, platforms, or technical infrastructure through which delivery occurs. Swapping one video host for an equivalent is a Patch. Changing the community platform is a Minor.
Vimeo → Wistia (equivalent: Patch). Facebook Group → Skool Community (new experience: Minor). Broken link fixed (Patch).
The Change Decision Tree
Before assigning a version tier, run the change through this decision tree:
1. Does this change alter what the offer fundamentally IS — its mechanism, its promise, or its delivery model? If YES → MAJOR version. If NO → continue to step 2.
2. Does this change alter what the buyer RECEIVES — new or removed modules, bonuses, calls, tools, access — or what they PAY — price, payment plans? If YES → MINOR version. If NO → continue to step 3.
3. Does this change alter how the buyer EXPERIENCES the offer — copy, positioning, navigation, tool brand? If YES and the experience change is significant → MINOR. If YES and the change is a correction or small improvement → PATCH. If NO → no version increment required.
The No-Change Rule
Some updates do not require a version increment: fixing a typo, correcting a broken image, updating a date reference, or refreshing a resource link without changing the destination. These are maintenance activities, not version changes. Log them in a separate Maintenance Log, not the Changelog.
PHASE 3
The Changelog Entry Protocol
The standard format for every version entry — no exceptions
The Changelog Entry Template
Every version increment — Major, Minor, or Patch — produces one Changelog Entry. The entry is completed at the time the change is deployed, not retrospectively. Retrospective entries have degraded accuracy and miss the evidence-linkage that makes the changelog actionable.
Name of the person who made and deployed the change
Sarah Chen
Deployed Date
Required
YYYY-MM-DD format
2026-03-15
Change Summary
Required
One sentence describing what changed. Plain language. No jargon.
Added 'The 30-Day Outreach Playbook' as a new bonus and retired the 'Cold Email Templates' bonus.
Evidence That Triggered This Change
Required
What data, feedback, or signal justified making this change? Link to source where possible.
Exit interview data from V1.2.0 cohort: 8 of 12 buyers cited outreach as their primary struggle post-programme. Cold Email Templates rated 4.2/10 usefulness in pulse surveys. Two buyers mentioned they already had similar templates.
Change Detail
Required
A full description of what specifically changed — what was added, removed, modified, or replaced.
ADDED: 'The 30-Day Outreach Playbook' — a 14-day DM outreach sequence template with 7 LinkedIn post angles and 5 cold email scripts. Hosted in Kajabi as Module 5 Bonus. Estimated standalone value: $197.
REMOVED: 'Cold Email Templates' bonus — 23 email templates. Retired due to low utility scores. Archived in Google Drive under [link] in case of future reinstatement.
Existing Buyer Impact
Required
Does this change affect buyers who purchased before this version? What are they entitled to?
Existing buyers (V1.0.0 through V1.2.1): Entitled to the new bonus. Will be notified via email on 2026-03-16 with access link. Cold Email Templates access maintained until 2026-06-15 for existing buyers who had already accessed it.
Sales Page Updated?
Required
Yes / No / Partial — if Yes or Partial, specify what was changed
Yes — bonus stack section updated. 'Cold Email Templates' removed from stack slide. '30-Day Outreach Playbook' added with $197 value assigned.
Email Sequence Updated?
Required
Yes / No — if Yes, specify which emails were updated
Yes — Day 10 (Bonus Explanation email) updated to reference new bonus.
Affiliate Notification Required?
Required
Yes / No — if Yes, specify which affiliates were notified and when
Yes — 3 active affiliates notified via email on 2026-03-16 with updated promotional copy.
Testimonial Audit Required?
Required
Does this change affect the validity of any current testimonials? List any testimonials that reference the changed elements.
Yes — 1 testimonial specifically mentions 'the cold email templates' by name. Testimonial flagged for version-locking (see Phase 5).
Rollback Plan
Required for MAJOR and MINOR
If this change produces unexpected negative results, how is it reversed?
Rollback: Restore Cold Email Templates access. Remove Outreach Playbook from Kajabi (or retain as optional). Update sales page to revert stack slide. Buyer impact: Notify of rollback, retain access to both during transition.
30-Day Review Date
Required
Date to review the impact of this change on conversion rate, refund rate, and completion rate
2026-04-15
Worked Changelog Examples
Three complete changelog entries showing Major, Minor, and Patch versions. These serve as reference standards for your team.
MVO-V2.0.0 2026-04-01
[MAJOR — CAT-D: Delivery Model Change + CAT-M: Mechanism Change]
► DELIVERY MODEL: Converted from self-paced course to live 4-week cohort model. Buyers now enrolled in cohort start dates rather than immediate self-paced access.
► MECHANISM: Core mechanism renamed from 'The 5-Phase Revenue System' to 'The Forensic Offer Audit Method.' Same underlying principles, new frame reflecting 2026 buyer language from exit interviews.
► GUARANTEE: Upgraded from 30-day money-back to result-based conditional (complete all 4 modules + submit exit survey + not see improvement in conversion rate within 30 days post-programme).
► MODULES: Added live implementation workshop in Week 3. Added 'Hot Seat' format for Week 4 live call. Removed 3 video modules that covered material now delivered in live sessions.
► EXISTING BUYERS: V1.x buyers grandfathered. Self-paced access maintained for 12 months. Invited to attend V2.0.0 cohort at no additional cost as 'Founding Members'.
► EVIDENCE: 68% of V1.x exit interviews cited 'would have preferred live support.' Completion rate V1.x = 41%. Live cohort beta (10 participants) completion rate = 87%.
► ADDED BONUS: 'AI Offer Audit Tool' — a custom GPT that runs buyers' offer drafts through the Value Equation and returns a scored assessment. Assigned standalone value: $297.
► ADDED MODULE: Module 5 — 'Scale Architecture' — covering the transition from $10K to $50K months. 4-video module, total 2.3 hours. Addresses the top gap identified in V1.2.0 exit surveys.
► PRICE CHANGE: Increased from $997 to $1,297. Price change justified by addition of AI tool + new module. Founding member pricing ($997) offered for 72 hours post-announcement to existing community.
► EXISTING BUYERS: Entitled to AI tool and new module at no cost. Access granted automatically on deploy date. Email notification sent same day.
► EVIDENCE: 11 of 14 V1.2.0 exit interview respondents said they would pay more for AI integration. Value Equation audit showed Perceived Likelihood was the lowest-scoring variable — AI tool addresses this directly.
► TECHNICAL: Replaced Vimeo Pro with Wistia (equivalent CDN performance, better analytics integration with GA4). All video URLs updated. No change to content.
► TECHNICAL: Fixed broken download link for Module 2 Worksheet. Correct file restored at same URL.
► COPY: Corrected typo in Day 7 email subject line ('Sucess' → 'Success'). No content change.
► COPY: Updated Module 3 reference to 'Meta Ads Manager' from 'Facebook Ads Manager' throughout sales page and email sequence.
► EXISTING BUYERS: Not affected. Technical change is transparent to buyers. No notification required.
PHASE 4
The Change Impact Assessment
Evaluating who is affected by every change before it is deployed
The Four Impact Dimensions
Every change touches four distinct stakeholder groups and operational areas. The Change Impact Assessment must evaluate all four before deployment. Omitting any dimension is how drift events occur.
Impact Dimension
Who or What Is Affected
Key Questions
Required Action if Impact Confirmed
Existing Buyer Impact
All buyers who purchased any prior version of this offer
Are they entitled to receive this change? If yes, how do they access it? If no, are they grandfathered or transitioned? Is their experience degraded by this change?
Determine entitlement policy. Draft buyer communication (see Phase 6). Update access if applicable.
Future Buyer Impact
All buyers who will purchase this version and beyond
Does the sales page accurately reflect this version? Does the email sequence match? Is the onboarding experience updated?
All active affiliates and JV partners currently promoting this offer
Does their promotional copy still accurately describe the offer? Is the price still correct? Are any features they highlighted still present?
Audit affiliate copy. Notify affected affiliates. Provide updated promotional assets.
Internal Team Impact
Sales team, support team, community managers, delivery team
Is the sales team aware of the change and quoting correctly? Does support know what existing buyers are entitled to? Does the community manager know what to say?
Team briefing note sent before deploy. Updated FAQs distributed. CRM notes updated.
The Existing Buyer Entitlement Policy
The most sensitive impact dimension is whether existing buyers are entitled to receive updates made in new versions. This policy must be defined clearly and applied consistently. Inconsistency breeds complaints and refund requests.
Always entitled. Access is automatic. No notification required unless the fix impacts their current experience.
A patch fixes something that should have worked. The buyer paid for working delivery.
N/A — no exceptions. All patches entitle existing buyers.
Minor — content addition (new module, new bonus)
Entitled if the addition strengthens the promise they purchased. Not entitled if the addition represents a fundamental expansion beyond the original scope.
Adding a bonus that delivers the same transformation better: entitled. Adding a bonus that opens a completely new skill area: not required (though often offered as goodwill).
Offer it as a goodwill gesture with a simple notification. Most operators should give the addition — the cost is near-zero and the goodwill is substantial.
Minor — content removal (retired module, retired bonus)
Always entitled to the removed content for a minimum of 90 days after removal — via archive access or PDF.
The buyer paid for specific components. Removing those components without maintaining access violates the original purchase agreement.
If a tool is discontinued by its vendor and no equivalent can be provided, notify buyers, explain the situation, and offer the closest alternative.
Minor — price change
Not entitled to the new price retroactively. Entitled to the offer as it was when they purchased.
Price changes apply to new buyers. Existing buyers purchased at the price that was live at the time of their purchase.
If price decreases significantly, consider offering existing buyers a partial credit as a goodwill gesture.
Minor — guarantee change (upgrade)
Always entitled to the stronger guarantee, retroactively.
A guarantee upgrade benefits buyers. Withholding it retroactively creates a two-class system that generates complaints.
N/A.
Major — delivery model change
Not automatically entitled. A major version is a different product. However, existing buyers should be offered a transition path.
Major versions represent substantial new development. Existing buyers paid for the prior model.
Offer existing buyers access to the new version at a significant discount ('Upgrade Path') or offer them continued access to the prior version for a defined period.
PHASE 5
Copy & Asset Synchronisation System
Ensuring every buyer-facing asset reflects the current version
The Copy Drift Problem
Copy drift occurs when the deployed version of an offer advances but one or more buyer-facing assets is not updated to reflect the new version. The Copy & Asset Synchronisation System is the checklist that ensures this cannot happen. It must be completed for every Minor and Major version change before the version is marked as live.
The Sync Rule
A new version is not live until every item on the Copy Sync Checklist is either updated or confirmed as not requiring update. Partial deploys — where the delivery changes but the sales page does not — are the single largest source of expectation mismatch complaints.
The Master Copy & Asset Sync Checklist
Complete this checklist for every Minor and Major version change. Each item must be marked: Updated / Not Required / Scheduled (with date) before the version is deployed.
Sales Page Assets
☐ Headline and subheadline — do they accurately describe the current mechanism and promise?
☐ Offer stack section — does it list exactly what is currently included, with accurate values?
☐ Bonus section — are all listed bonuses current? Are all retired bonuses removed?
☐ Guarantee section — does it reflect the current guarantee tier and exact language?
☐ Social proof / testimonials — do all testimonials reference features or bonuses that still exist? (See Testimonial Audit below)
☐ Pricing — does it show the current price and all current payment plan options?
☐ 'Not for you' section — does it reflect current Negative Avatar profiles?
☐ FAQ section — are all FAQs consistent with current delivery, price, and guarantee?
☐ Comparison table (if present) — does it accurately describe the current offer vs. alternatives?
Email Sequences
☐ Welcome / onboarding sequence — does it reference current modules, tools, and first steps accurately?
☐ 14-day nurture sequence — do Days 8–10 (mechanism introduction) reference the current mechanism name?
☐ Offer introduction email — does it describe the current offer stack?
☐ Bonus explanation emails — do they describe the current bonuses only?
☐ Objection handling emails — do they address objections relevant to the current version?
☐ Launch sequence (if evergreen) — does it reference current pricing and guarantee?
☐ Abandoned cart sequence — does it reference current price and offer stack?
Paid Advertising
☐ All active ad creatives — do they reference current features, price, and promise?
☐ All active ad copy — are mechanism names, bonus names, and guarantee language current?
☐ Landing pages linked from ads — are they updated?
☐ Retargeting ad variants — are they consistent with current version?
Affiliate and JV Assets
☐ Affiliate promotional swipe copy — does it describe the current offer accurately?
☐ Affiliate email templates — are mechanism names, bonuses, and pricing current?
☐ Affiliate social captions — are they current?
☐ JV landing pages (if custom pages exist for JV partners) — are they updated?
Onboarding and Delivery Materials
☐ Welcome email (post-purchase) — does it accurately describe what they have access to and first steps?
☐ Onboarding survey — are baseline questions still relevant to the current programme structure?
☐ Course platform module titles and descriptions — do they match current content?
☐ Module completion criteria — are they current?
☐ Community welcome message and pinned resources — are they current?
☐ Support team FAQ document — is it updated for this version?
GEO / AEO Schema and Digital Presence
☐ Offer schema markup (Product + Offer JSON-LD) — is pricing, description, and guarantee current?
☐ Pillar article or landing page that describes the offer — is it updated?
☐ LLMs.txt file — if the mechanism name or offer description changed, is it updated?
☐ Google My Business / local listing (if applicable) — is offer description current?
The Testimonial Version-Lock Protocol
Testimonials are version-specific. A testimonial collected during V1.2.0 describes the V1.2.0 experience. If V1.3.0 removes or changes a feature that the testimonial mentions, the testimonial must be version-locked — flagged as belonging to a specific version — and either retired from the live sales page or annotated.
Testimonial Status
Definition
Sales Page Treatment
Archive Treatment
Version-Current
The testimonial does not reference any feature, bonus, mechanism name, or price that has changed in any version after it was collected. It describes the transformation only.
Use freely on current sales page. No annotation required.
Maintain in active proof library with version tag.
Version-Specific (Usable)
The testimonial references specific features or bonuses that were present in the version when collected and are still present in the current version.
Use on current sales page. Mark with version tag in Airtable for monitoring.
Maintain with version tag. Review at each Minor version change.
Version-Specific (Retired)
The testimonial specifically mentions a feature, bonus, or mechanism name that no longer exists in the current version.
Remove from live sales page immediately. Do not annotate on live page — buyers see the annotation as a red flag.
Archive in proof library with version tag. May be reinstated if the feature is restored.
Price-Specific
The testimonial mentions a specific price paid that is no longer the current price. ('I paid $297 and it was worth every penny.')
Use with caution. If current price is higher, the price reference may create expectations or confusion. Consider requesting a new testimonial from the same buyer without the price reference.
Tag as Price-Specific. Monitor at each pricing change.
Testimonial Audit Protocol
Run the Testimonial Audit at every Minor and Major version change. For each testimonial currently on the sales page:
1. Read the testimonial for specific feature references: named bonuses, named modules, named tools, specific prices, specific mechanism names.
2. Check each referenced element against the current version's offer stack and mechanism name.
3. If any referenced element no longer exists in the current version: tag the testimonial as Version-Specific (Retired). Remove from live sales page. Archive.
4. Add a note to the changelog entry: 'Testimonial from [Buyer Name] retired from sales page — references [retired element].'
5. Reach out to the buyer within 30 days of retiring their testimonial to request an updated one based on the current version.
PHASE 6
The Buyer Communication Protocol
When and how to communicate version changes to existing buyers
The Communication Decision Matrix
Not every version change requires a buyer communication. The Communication Decision Matrix defines which changes trigger which level of communication.
Version Tier
Change Category
Communication Required?
Communication Type
Timing
PATCH
Any
No — unless the patch fixes something that directly affected a buyer's experience
If patch fixes a buyer-facing issue: proactive personal email to affected buyers only
Within 24 hours of patch deploy
MINOR
CAT-O: Content added (new bonus or module)
Yes — good news communication
Broadcast email to all existing buyers: 'You've been upgraded'
Same day as deploy or within 24 hours
MINOR
CAT-O: Content removed (bonus or module retired)
Yes — required communication
Email to all existing buyers: access maintenance period, archive link, reason for change
Minimum 14 days BEFORE removal
MINOR
CAT-P: Price increase
Yes — for existing list (not existing buyers)
Email to waitlist and engaged list: 'Founding member pricing closes [date]'. Existing buyers: notification for their awareness, no action required.
7–14 days before price change
MINOR
CAT-G: Guarantee upgrade
Yes — positive communication
Email to all existing buyers notifying them of the stronger guarantee they now have
Same day as deploy
MINOR
CAT-C / CAT-T: Copy or tech change
No — unless the change affects buyer access or experience
If access affected: notify affected buyers directly
Within 24 hours if access affected
MAJOR
Any
Yes — always required
Personal email from founder to all existing buyers: explain what changed, their options, and their transition path
Minimum 21 days before Major version deploys
The Four Communication Templates
Template 1 — Content Added (New Bonus or Module)
Content Added Communication Template
Subject: You've been upgraded — [Offer Name] just got better
Hi [First Name],
Quick message to let you know we just added something to [Offer Name] that I think you'll find genuinely useful.
Based on feedback from the last cohort — specifically the [specific challenge] that came up repeatedly — we've added [specific new bonus/module name]. It does [specific thing it solves].
You have it automatically. Access it here: [link].
This is now part of the offer permanently. If you have questions about it, [specific support channel].
[Your name]
Template 2 — Content Removed (Bonus or Module Retired)
Content Removed Communication Template
Subject: A change to [Offer Name] — and what it means for you
Hi [First Name],
I want to give you advance notice of a change we're making to [Offer Name] on [date].
We're retiring [specific bonus/module name]. The reason: [honest, specific reason — outdated, superseded by better resource, low utility scores from recent feedback].
What this means for you: If you've already accessed it and want to keep a copy, download it before [date + 14 days buffer]. After that date, we'll remove it from the platform.
We're replacing it with [new element] — which [specific improvement over the retired element].
If you have any questions about this, reply to this email.
[Your name]
Template 3 — Major Version Change (Delivery Model)
Major Version Communication Template
Subject: A significant update to [Offer Name] — your options
Hi [First Name],
I want to be transparent about something we're changing in [Offer Name], and what your options are as someone who has already purchased.
Starting [date], [Offer Name] is moving from [current format] to [new format]. Here's why: [specific evidence — completion rates, buyer feedback, results data].
What this means for you:
Option A: You keep full access to the current version ([V1.x]) until [date — minimum 12 months]. Nothing changes for you unless you want it to.
Option B: You can transition to the new version at no additional cost. If you want to do this, [specific instructions].
Option C: If you feel the change fundamentally alters what you purchased and you'd prefer a refund, I'll honour that — no questions asked. Email [email] by [date].
I built the new version based on what I learned from people like you. I'm confident it delivers better results. But you deserve the choice.
[Your name]
Template 4 — Price Increase (Existing List)
Price Increase Communication Template
Subject: [Offer Name] price is going up — here's when and why
Hi [First Name],
On [date], the price of [Offer Name] is increasing from [current price] to [new price].
Why: [honest reason — added a new module, added the AI tool, results data justifies the price, we've invested in improving the delivery]. I want to make sure the price reflects what's actually being delivered.
If you've been thinking about joining — or if you know someone who has — the current price is locked until [date].
After [date], the new price applies to all new purchases.
[Your name]
PHASE 7
The Version Archive System
Every version of every offer preserved and findable
The Archive Architecture
The Version Archive serves three functions: it provides a historical record for legal and compliance purposes, it enables rollback when a change produces unexpected negative results, and it provides the institutional memory that makes future iterations smarter. An archive that is not organised and findable is not an archive — it is a graveyard.
The Archive Folder Structure
One folder per offer. Within each offer folder, one subfolder per Major version. Within each Major version folder, one document per Minor version change and one document per Patch.
Recommended Archive Folder Structure
📁 RISER Nation — Offer Version Archive
📁 MVO-Offer
📁 V1 (2025-06-01 to 2026-01-14)
📄 MVO-V1.0.0-2025-06-01 — Launch Version
📄 MVO-V1.1.0-2025-07-15 — Added LinkedIn bonus
📄 MVO-V1.2.0-2025-09-10 — Price change $197→$297
📄 MVO-V1.2.1-2025-10-03 — Broken link fix (patch)
📄 MVO-V1.3.0-2025-11-20 — New bonus, retired old
📁 V2 (2026-01-15 to present)
📄 MVO-V2.0.0-2026-01-15 — Major: Live cohort conversion
📄 MVO-V2.0.1-2026-02-01 — Zoom link fix (patch)
📁 Core-Offer
📁 V1 (2025-09-01 to present)
📄 CORE-V1.0.0-2025-09-01 — Launch Version
[etc.]
What Each Version Archive Document Contains
Each version archive document is a snapshot of the offer as it existed at that version. It must contain enough information to restore that version completely if needed.
Archive Document Section
What to Include
Version identifier and date
Full version identifier: [Offer Code]-V[X.Y.Z]-[YYYY-MM-DD]
The changelog entry
Full changelog entry from Phase 3 for this version
Offer stack snapshot
Complete list of every component included in this version: modules (with titles), bonuses (with names and described value), live calls (frequency and format), community access, tool access, and guarantee language. Verbatim from the sales page at time of version deploy.
Sales page snapshot
Full text of the sales page at the time of this version — headline, body copy, offer stack section, guarantee section, FAQ section. PDF export or text copy.
Price at this version
Sale price, payment plan options, and any promotional pricing active at launch of this version.
Active testimonials at this version
List of all testimonials on the live sales page at this version — buyer name, date collected, and version tag.
Affiliate copy at this version
Copy of all affiliate promotional emails, social captions, and swipe files distributed for this version.
Delivery architecture at this version
Summary of the delivery format, tools used, and fulfilment process at this version.
Known issues at this version
Any known bugs, complaints, or performance gaps identified during this version's active period. This feeds directly into the justification for the next version's changes.
The Version Timeline View
The Version Timeline is a single-page summary document maintained at the top level of each offer's archive folder. It shows every version at a glance — date, tier, and one-sentence summary of the change.
Version
Date
Change Summary
V1.0.0
2025-06-01
LAUNCH — Initial public launch. Self-paced course, 4 modules, 3 bonuses, 30-day money-back guarantee at $197.
V1.1.0
2025-07-15
MINOR — Added LinkedIn Outreach Playbook bonus (CAT-O). Justified by exit interview data showing LinkedIn was top unmet channel.
V1.2.0
2025-09-10
MINOR — Price increase $197 → $297 (CAT-P). Justified by new bonus addition and improved completion rate data.
MINOR — Retired Cold Email Templates bonus. Added 30-Day Outreach Playbook. Guarantee upgraded to result-based conditional (CAT-O, CAT-G).
V2.0.0
2026-01-15
MAJOR — Converted from self-paced to live 4-week cohort. Mechanism renamed. Existing buyers grandfathered with 12-month access to V1 (CAT-D, CAT-M).
PHASE 8
The Rollback Protocol
What to do when a change makes things worse
What Triggers a Rollback
A rollback is the reversal of a version change when that change has produced measurable negative outcomes. Rollbacks are rare in a well-managed versioning system because the changelog entry protocol requires an evidence-based justification for every change. But they are sometimes necessary, and having a pre-defined protocol prevents the confusion and delay that an unplanned rollback causes.
Rollback Trigger
Threshold
Detection Window
Severity
Conversion rate drop following a Major or Minor change
Conversion rate falls 25% below the 30-day pre-change average and does not recover within 14 days
30-day post-deploy monitoring window
High — rollback consideration immediately
Refund rate spike following a change
Refund rate increases to 15%+ within 30 days of a change that altered the offer stack or guarantee
30-day post-deploy monitoring
Critical — rollback or change reversal within 72 hours
Completion rate drop following content changes
Completion rate falls 20%+ below the pre-change average within one full cohort or programme cycle
One programme cycle post-deploy
High — content rollback within next cohort cycle
Buyer complaint volume spike tied to specific change
3 or more buyers cite the same specific change as the source of their complaint within 21 days of deploy
21-day post-deploy monitoring
Medium to High depending on complaint severity
Affiliate performance drop tied to copy or stack change
Affiliate traffic conversion rate falls 30%+ below baseline within 21 days of an affiliate-affecting change
21-day post-deploy for affiliate traffic specifically
Medium — rollback or affiliate copy revert
The Rollback Execution Steps
1. Confirm trigger threshold has been crossed using data from the relevant source (GA4, CRM, email platform, affiliate dashboard). Document the evidence.
2. Issue a new version number for the rollback. A rollback is not a re-issue of a prior version number — it is a new version that restores prior content. Example: V1.3.0 introduced a problematic change. Rollback is V1.3.1, which restores the V1.2.1 state.
3. Restore the specific component(s) that are being rolled back using the Version Archive Document for the prior version.
4. Complete a full Changelog Entry for the rollback version. Under 'Evidence That Triggered This Change' — document the rollback trigger data.
5. Run the Copy & Asset Sync Checklist (Phase 5) for the rollback version exactly as you would for a forward change.
6. Complete the Buyer Communication Protocol (Phase 6) if existing buyers are affected by the rollback.
7. Conduct a post-rollback analysis within 14 days: what assumption was wrong in the forward change? What evidence was missing? Document the finding in the rollback changelog entry.
The Rollback Learning Principle
A rollback is one of the most valuable data events in the versioning system — because it tells you precisely what your market will not accept. The post-rollback analysis question — 'what assumption was wrong?' — becomes the highest-priority research item for the next forward version. The rollback is not a setback. It is a specification.
PHASE 9
The Changelog Review Cadence
Keeping the system alive, current, and strategically useful
Changelog entry filed. All assets updated. Notifications sent.
30 days after each Minor or Major deploy
30-Day Change Review: compare conversion rate, refund rate, completion rate, and support ticket volume against pre-change baseline. Confirm rollback threshold not triggered.
20 minutes
Change Impact Data added to changelog entry's 30-Day Review field.
Monthly (first Monday)
Review all changes made in the prior month. Are 30-day review data points filed? Are any assets still pending update? Are any rollback thresholds being approached?
30 minutes
Monthly Version Status Report.
Quarterly
Version Drift Audit: manually compare the current version's sales page against the Version Archive snapshot for the same offer. Identify any drift that occurred outside the formal versioning system.
90 minutes per active offer
Drift Audit Report. Any undocumented changes retroactively added to changelog and assigned a version number.
Annually
Full version history review: what have been the 3 most impactful changes of the year (by conversion or refund rate delta)? What does the version history reveal about what buyers actually value? Feed findings into the following year's offer development brief.
Half day
Annual Version Intelligence Report. Feeds into product roadmap.
The Quarterly Version Drift Audit
The Version Drift Audit is the integrity check on the entire versioning system. It catches changes that were made informally — outside the changelog process — and retroactively brings them into the record. Every business has some degree of informal changes: the VA who updates the sales page without telling anyone, the community manager who changes the welcome message, the ad manager who updates ad copy without a formal change request. The Drift Audit finds these.
1. Pull the Version Archive Document for the most recent Minor or Major version of each active offer.
2. Compare the 'Offer Stack Snapshot' in the archive against what is currently live on the sales page, in the email sequence, and in the course platform.
3. For every discrepancy found — something present in the live offer that is not in the archive snapshot, or vice versa — document it as an informal change.
4. For each informal change: assign it a retroactive version number (PATCH if minor, MINOR if significant). Create a changelog entry with 'Retroactive — discovered in Quarterly Drift Audit' noted in the evidence field.
5. Identify who made the informal change. Update team protocols to ensure all future changes go through the changelog process before deployment.
The Changelog Database — Airtable Schema
All changelog entries, version archive references, testimonial version tags, and affiliate copy audits live in a single Airtable base. The schema below is the complete data model.
Table 1 — Changelog Entries
One record per version. The primary table of the system.
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — PRODUCT VERSIONING & OFFER CHANGELOG ",
"",
"The System for Tracking Every Change to Every Offer — So Nothing Gets Lost, Nothing Drifts, Nothing Surprises You",
"Kennedy × Hormozi × Brunson × 2026 Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"Every offer you build will change. Modules get added and removed. Bonuses get retired. Prices shift. Guarantees get upgraded. Live calls get added or reduced. The mechanism gets renamed. Delivery platforms change. These changes happen constantly — which is good, because they reflect learning and iteration.",
"",
"What is not good is when those changes happen without a system. When the sales page still promises a bonus that no longer exists. When a testimonial references a feature that was retired six months ago. When the affiliate's promotional copy describes an offer that changed three versions ago. When a buyer from last year tries to refer a friend and quotes a price that is no longer accurate. When your own team is uncertain which version of the offer is currently live.",
"",
"This SOP builds the product versioning and changelog system that prevents all of those failures. It defines a semantic versioning approach adapted from software development, a structured changelog entry protocol, a change impact assessment for every modification, a copy and asset synchronisation system, a buyer communication protocol, a rollback mechanism, and a complete version archive. The system is lightweight by design — the goal is compliance, and compliance requires minimal friction.",
"",
"The Core Principle",
"Every change to an offer has three dimensions: what changed, why it changed (the evidence that justified it), and who is affected. A changelog that captures all three creates the institutional memory that makes every future iteration smarter, every affiliate relationship cleaner, and every buyer communication more credible.",
"",
"The Version Drift Problem: Why This System Exists",
"Version drift is the gradual, untracked divergence between what is promised on a sales page and what is actually delivered in the current version of an offer. It is not caused by deliberate dishonesty. It is caused by dozens of small, well-intentioned changes made without a documentation system.",
"",
"Drift Scenario",
"How It Happens",
"The Downstream Cost",
"Sales page promises a bonus that no longer exists",
"Bonus was quietly retired because it was outdated or became irrelevant. Sales page was not updated.",
"Buyer expects the bonus. Does not receive it. Files a support ticket or refund request citing unmet expectation. FTC compliance risk.",
"Testimonial references a feature that was removed",
"Testimonial was collected during V1 when a specific module or tool was included. Module removed in V1.3. Testimonial still on sales page.",
"New buyers purchase expecting the referenced feature. Expectation mismatch at delivery. Trust erosion.",
"Affiliate promotional copy is outdated",
"Affiliate created promotional content based on the V1 offer. Offer is now on V2.1. Key differences in promise, price, and guarantee.",
"Affiliate sends traffic expecting V1. Buyers arrive expecting V1 features. Refund rate from affiliate traffic higher than average. Affiliate relationship damaged when raised.",
"Sales team quoting wrong price or features",
"Price changed in V1.4 but sales team was not formally notified. They continue quoting the old price.",
"Buyers get inconsistent information. Some pay old price, some new. Complaint when buyer discovers they paid more than someone else. Legal exposure on price representations.",
"Existing buyer refers a friend with wrong information",
"Existing buyer enthusiastically describes the V1 offer to a friend. Friend purchases expecting V1. Receives V2.1.",
"Friend is disappointed by differences. Original buyer's trust is damaged. Referral channel contaminated.",
"Internal team confusion about what is currently live",
"Team member updating copy refers to the previous version's bonus stack. Builds new email sequence referencing retired modules.",
"Internal rework. Inconsistent buyer communications. Brand credibility erodes with buyers who notice discrepancies.",
"",
"The Compounding Effect",
"Each individual drift event seems minor. The compounding effect is what kills trust. A buyer who encounters one discrepancy loses confidence. A buyer who encounters three discrepancies loses the relationship entirely — and reviews reflect it. Version drift is the slow leak that sinks the ship while everyone is busy rowing.",
"",
"",
"PHASE 1",
"The Semantic Versioning System",
"Major.Minor.Patch — adapted from software development for offer management",
"",
"The Three-Tier Numbering System",
"Semantic versioning — the Major.Minor.Patch format used in software development — is the clearest and most widely understood versioning convention available. Adapted for offer management, it provides instant communication about the nature and scale of any change.",
"",
"V2.0.0",
"MAJOR VERSION",
"Fundamental change to mechanism, delivery model, core promise, or target avatar. Existing buyers may need to be grandfathered or migrated.",
"Example: V1 was a self-paced course. V2 is a live cohort with DFY deliverables.",
"V1.3.0",
"MINOR VERSION",
"Significant improvement: new module, new bonus, new guarantee tier, price change, significant copy revision, platform change.",
"Example: V1.2 had 3 bonuses. V1.3 adds a 4th bonus and upgrades the guarantee.",
"V1.2.1",
"PATCH VERSION",
"Small correction or improvement: copy fix, broken link repair, tool swap with equivalent, minor content update, formatting change.",
"Example: V1.2.0 had a broken download link. V1.2.1 fixes the link.",
"",
"Version Numbering Rules",
"Rule",
"Definition",
"Example",
"Rule 1 — Sequential",
"Version numbers always increase. You cannot go from V1.3.0 back to V1.2.0. If a change is reversed, a new version number is issued (V1.3.1 = reversal of V1.3.0).",
"V1.3.0 → V1.3.1 (reversal) — not V1.3.0 (re-issue of same number)",
"Rule 2 — Reset on increment",
"When a Major version increments, Minor and Patch reset to 0. When Minor increments, Patch resets to 0.",
"V1.9.3 + Major change = V2.0.0 (not V2.9.3). V1.2.4 + Minor change = V1.3.0 (not V1.2.5)",
"Rule 3 — One version per deploy",
"All changes made in a single deployment cycle share one version number. If five changes are made and deployed simultaneously, they constitute one version — not five.",
"Deploying a new module + a new bonus + a copy update = V1.3.0. Not V1.3.0, V1.3.1, V1.3.2.",
"Rule 4 — Offer-specific numbering",
"Version numbers are per-offer, not per-business. Each offer in your value ladder has its own independent version history.",
"MVO offer: V2.1.0. Core Offer: V1.4.2. These are independent version histories.",
"Rule 5 — Date stamping",
"Every version number carries a date stamp in YYYY-MM-DD format.",
"V1.3.0 (2026-03-15) — the version number and date together form the version identifier.",
"Rule 6 — Public vs internal versioning",
"The version number is internal. Buyers are not typically shown the version number. The version number exists for operational control, not for buyer-facing communication.",
"Sales page does not say 'Version 1.3.0.' Internal records and team communications use the version number.",
"",
"Version Identifier Format",
"Every offer version is identified by four elements combined:",
"",
"Version Identifier Format",
"[OFFER CODE]-V[MAJOR].[MINOR].[PATCH]-[YYYY-MM-DD]\n\nExamples:\nMVO-V2.1.0-2026-03-15\nCORE-V1.4.2-2026-01-08\nDWY-V1.0.0-2026-05-20\n\nOffer Codes are defined at the time each offer is first created and never change. Example codes: MVO / CORE / DWY / DFY / CONT (Continuity) / IC (Inner Circle).",
"",
"",
"PHASE 2",
"Change Classification Framework",
"Categorising every type of offer change before it is made",
"",
"The Seven Change Categories",
"Every change to an offer falls into one of seven categories. The category determines the version tier (Major, Minor, or Patch), the required impact assessment, the copy update scope, and the buyer communication obligation.",
"",
"Category",
"Code",
"Version Tier",
"Definition",
"Examples",
"Mechanism Change",
"CAT-M",
"MAJOR",
"A change to the named methodology, the core promise, or the fundamental transformation the offer delivers. The most significant change type.",
"Renaming the mechanism. Changing the core transformation from 'get leads' to 'book calls.' Changing the programme's defining intellectual framework.",
"Delivery Model Change",
"CAT-D",
"MAJOR",
"A change to the format, modality, or structure through which the offer is delivered. A self-paced course becoming a live cohort is a Delivery Model Change.",
"Self-paced → live cohort. Group coaching → 1:1. Synchronous delivery → async. 4-week → 8-week programme.",
"Offer Stack Change",
"CAT-O",
"MINOR",
"A change to what is included in the offer: adding or removing a module, adding or removing a bonus, changing community access, changing tool access.",
"Adding a new module. Retiring a bonus. Replacing a tool with an equivalent. Adding a monthly live Q&A call.",
"Pricing and Packaging Change",
"CAT-P",
"MINOR",
"Any change to the price, the payment plan options, or the tier structure of the offer.",
"Price increase from $297 to $497. Adding a payment plan. Creating a new tier at a different price point.",
"Guarantee Change",
"CAT-G",
"MINOR",
"Any change to the guarantee structure, conditions, or language — whether strengthening or weakening the guarantee.",
"Upgrading from 30-day money-back to result-based conditional guarantee. Adding completion requirements to qualify for refund.",
"Copy and Positioning Change",
"CAT-C",
"MINOR (if significant) or PATCH (if minor)",
"A change to the sales page, email sequence, ad copy, or any buyer-facing language that does not change the underlying offer but changes how it is positioned or described.",
"New headline test deployed. Email sequence rewritten with buyer language. 'Not for you' section added.",
"Technical and Platform Change",
"CAT-T",
"PATCH (if equivalent) or MINOR (if affects buyer experience)",
"A change to the tools, platforms, or technical infrastructure through which delivery occurs. Swapping one video host for an equivalent is a Patch. Changing the community platform is a Minor.",
"Vimeo → Wistia (equivalent: Patch). Facebook Group → Skool Community (new experience: Minor). Broken link fixed (Patch).",
"",
"The Change Decision Tree",
"Before assigning a version tier, run the change through this decision tree:",
"",
"1. Does this change alter what the offer fundamentally IS — its mechanism, its promise, or its delivery model? If YES → MAJOR version. If NO → continue to step 2.",
"2. Does this change alter what the buyer RECEIVES — new or removed modules, bonuses, calls, tools, access — or what they PAY — price, payment plans? If YES → MINOR version. If NO → continue to step 3.",
"3. Does this change alter how the buyer EXPERIENCES the offer — copy, positioning, navigation, tool brand? If YES and the experience change is significant → MINOR. If YES and the change is a correction or small improvement → PATCH. If NO → no version increment required.",
"",
"The No-Change Rule",
"Some updates do not require a version increment: fixing a typo, correcting a broken image, updating a date reference, or refreshing a resource link without changing the destination. These are maintenance activities, not version changes. Log them in a separate Maintenance Log, not the Changelog.",
"",
"",
"PHASE 3",
"The Changelog Entry Protocol",
"The standard format for every version entry — no exceptions",
"",
"The Changelog Entry Template",
"Every version increment — Major, Minor, or Patch — produces one Changelog Entry. The entry is completed at the time the change is deployed, not retrospectively. Retrospective entries have degraded accuracy and miss the evidence-linkage that makes the changelog actionable.",
"",
"Field",
"Required?",
"What to Document",
"Example",
"Version Identifier",
"Required",
"[Offer Code]-V[X.Y.Z]-[YYYY-MM-DD]",
"MVO-V1.3.0-2026-03-15",
"Version Tier",
"Required",
"MAJOR / MINOR / PATCH",
"MINOR",
"Change Category",
"Required",
"CAT-M / CAT-D / CAT-O / CAT-P / CAT-G / CAT-C / CAT-T (one or more)",
"CAT-O (Offer Stack Change)",
"Author",
"Required",
"Name of the person who made and deployed the change",
"Sarah Chen",
"Deployed Date",
"Required",
"YYYY-MM-DD format",
"2026-03-15",
"Change Summary",
"Required",
"One sentence describing what changed. Plain language. No jargon.",
"Added 'The 30-Day Outreach Playbook' as a new bonus and retired the 'Cold Email Templates' bonus.",
"Evidence That Triggered This Change",
"Required",
"What data, feedback, or signal justified making this change? Link to source where possible.",
"Exit interview data from V1.2.0 cohort: 8 of 12 buyers cited outreach as their primary struggle post-programme. Cold Email Templates rated 4.2/10 usefulness in pulse surveys. Two buyers mentioned they already had similar templates.",
"Change Detail",
"Required",
"A full description of what specifically changed — what was added, removed, modified, or replaced.",
"ADDED: 'The 30-Day Outreach Playbook' — a 14-day DM outreach sequence template with 7 LinkedIn post angles and 5 cold email scripts. Hosted in Kajabi as Module 5 Bonus. Estimated standalone value: $197.\n\nREMOVED: 'Cold Email Templates' bonus — 23 email templates. Retired due to low utility scores. Archived in Google Drive under [link] in case of future reinstatement.",
"Existing Buyer Impact",
"Required",
"Does this change affect buyers who purchased before this version? What are they entitled to?",
"Existing buyers (V1.0.0 through V1.2.1): Entitled to the new bonus. Will be notified via email on 2026-03-16 with access link. Cold Email Templates access maintained until 2026-06-15 for existing buyers who had already accessed it.",
"Sales Page Updated?",
"Required",
"Yes / No / Partial — if Yes or Partial, specify what was changed",
"Yes — bonus stack section updated. 'Cold Email Templates' removed from stack slide. '30-Day Outreach Playbook' added with $197 value assigned.",
"Email Sequence Updated?",
"Required",
"Yes / No — if Yes, specify which emails were updated",
"Yes — Day 10 (Bonus Explanation email) updated to reference new bonus.",
"Affiliate Notification Required?",
"Required",
"Yes / No — if Yes, specify which affiliates were notified and when",
"Yes — 3 active affiliates notified via email on 2026-03-16 with updated promotional copy.",
"Testimonial Audit Required?",
"Required",
"Does this change affect the validity of any current testimonials? List any testimonials that reference the changed elements.",
"Yes — 1 testimonial specifically mentions 'the cold email templates' by name. Testimonial flagged for version-locking (see Phase 5).",
"Rollback Plan",
"Required for MAJOR and MINOR",
"If this change produces unexpected negative results, how is it reversed?",
"Rollback: Restore Cold Email Templates access. Remove Outreach Playbook from Kajabi (or retain as optional). Update sales page to revert stack slide. Buyer impact: Notify of rollback, retain access to both during transition.",
"30-Day Review Date",
"Required",
"Date to review the impact of this change on conversion rate, refund rate, and completion rate",
"2026-04-15",
"",
"",
"Worked Changelog Examples",
"Three complete changelog entries showing Major, Minor, and Patch versions. These serve as reference standards for your team.",
"",
"MVO-V2.0.0 2026-04-01",
"[MAJOR — CAT-D: Delivery Model Change + CAT-M: Mechanism Change]",
"► DELIVERY MODEL: Converted from self-paced course to live 4-week cohort model. Buyers now enrolled in cohort start dates rather than immediate self-paced access.",
"► MECHANISM: Core mechanism renamed from 'The 5-Phase Revenue System' to 'The Forensic Offer Audit Method.' Same underlying principles, new frame reflecting 2026 buyer language from exit interviews.",
"► GUARANTEE: Upgraded from 30-day money-back to result-based conditional (complete all 4 modules + submit exit survey + not see improvement in conversion rate within 30 days post-programme).",
"► MODULES: Added live implementation workshop in Week 3. Added 'Hot Seat' format for Week 4 live call. Removed 3 video modules that covered material now delivered in live sessions.",
"► EXISTING BUYERS: V1.x buyers grandfathered. Self-paced access maintained for 12 months. Invited to attend V2.0.0 cohort at no additional cost as 'Founding Members'.",
"► EVIDENCE: 68% of V1.x exit interviews cited 'would have preferred live support.' Completion rate V1.x = 41%. Live cohort beta (10 participants) completion rate = 87%.",
"",
"CORE-V1.3.0 2026-02-10",
"[MINOR — CAT-O: Offer Stack Change + CAT-P: Price Change]",
"► ADDED BONUS: 'AI Offer Audit Tool' — a custom GPT that runs buyers' offer drafts through the Value Equation and returns a scored assessment. Assigned standalone value: $297.",
"► ADDED MODULE: Module 5 — 'Scale Architecture' — covering the transition from $10K to $50K months. 4-video module, total 2.3 hours. Addresses the top gap identified in V1.2.0 exit surveys.",
"► PRICE CHANGE: Increased from $997 to $1,297. Price change justified by addition of AI tool + new module. Founding member pricing ($997) offered for 72 hours post-announcement to existing community.",
"► EXISTING BUYERS: Entitled to AI tool and new module at no cost. Access granted automatically on deploy date. Email notification sent same day.",
"► EVIDENCE: 11 of 14 V1.2.0 exit interview respondents said they would pay more for AI integration. Value Equation audit showed Perceived Likelihood was the lowest-scoring variable — AI tool addresses this directly.",
"",
"DWY-V1.0.2 2026-01-22",
"[PATCH — CAT-T: Technical Change + CAT-C: Copy Change]",
"► TECHNICAL: Replaced Vimeo Pro with Wistia (equivalent CDN performance, better analytics integration with GA4). All video URLs updated. No change to content.",
"► TECHNICAL: Fixed broken download link for Module 2 Worksheet. Correct file restored at same URL.",
"► COPY: Corrected typo in Day 7 email subject line ('Sucess' → 'Success'). No content change.",
"► COPY: Updated Module 3 reference to 'Meta Ads Manager' from 'Facebook Ads Manager' throughout sales page and email sequence.",
"► EXISTING BUYERS: Not affected. Technical change is transparent to buyers. No notification required.",
"",
"",
"PHASE 4",
"The Change Impact Assessment",
"Evaluating who is affected by every change before it is deployed",
"",
"The Four Impact Dimensions",
"Every change touches four distinct stakeholder groups and operational areas. The Change Impact Assessment must evaluate all four before deployment. Omitting any dimension is how drift events occur.",
"",
"Impact Dimension",
"Who or What Is Affected",
"Key Questions",
"Required Action if Impact Confirmed",
"Existing Buyer Impact",
"All buyers who purchased any prior version of this offer",
"Are they entitled to receive this change? If yes, how do they access it? If no, are they grandfathered or transitioned? Is their experience degraded by this change?",
"Determine entitlement policy. Draft buyer communication (see Phase 6). Update access if applicable.",
"Future Buyer Impact",
"All buyers who will purchase this version and beyond",
"Does the sales page accurately reflect this version? Does the email sequence match? Is the onboarding experience updated?",
"Update sales page, email sequence, onboarding materials. Run Copy Sync Checklist (Phase 5).",
"Affiliate and JV Impact",
"All active affiliates and JV partners currently promoting this offer",
"Does their promotional copy still accurately describe the offer? Is the price still correct? Are any features they highlighted still present?",
"Audit affiliate copy. Notify affected affiliates. Provide updated promotional assets.",
"Internal Team Impact",
"Sales team, support team, community managers, delivery team",
"Is the sales team aware of the change and quoting correctly? Does support know what existing buyers are entitled to? Does the community manager know what to say?",
"Team briefing note sent before deploy. Updated FAQs distributed. CRM notes updated.",
"",
"The Existing Buyer Entitlement Policy",
"The most sensitive impact dimension is whether existing buyers are entitled to receive updates made in new versions. This policy must be defined clearly and applied consistently. Inconsistency breeds complaints and refund requests.",
"",
"Change Type",
"Default Entitlement Policy",
"Rationale",
"Exception Conditions",
"Patch (V1.0.x) — bug fixes, typos, technical corrections",
"Always entitled. Access is automatic. No notification required unless the fix impacts their current experience.",
"A patch fixes something that should have worked. The buyer paid for working delivery.",
"N/A — no exceptions. All patches entitle existing buyers.",
"Minor — content addition (new module, new bonus)",
"Entitled if the addition strengthens the promise they purchased. Not entitled if the addition represents a fundamental expansion beyond the original scope.",
"Adding a bonus that delivers the same transformation better: entitled. Adding a bonus that opens a completely new skill area: not required (though often offered as goodwill).",
"Offer it as a goodwill gesture with a simple notification. Most operators should give the addition — the cost is near-zero and the goodwill is substantial.",
"Minor — content removal (retired module, retired bonus)",
"Always entitled to the removed content for a minimum of 90 days after removal — via archive access or PDF.",
"The buyer paid for specific components. Removing those components without maintaining access violates the original purchase agreement.",
"If a tool is discontinued by its vendor and no equivalent can be provided, notify buyers, explain the situation, and offer the closest alternative.",
"Minor — price change",
"Not entitled to the new price retroactively. Entitled to the offer as it was when they purchased.",
"Price changes apply to new buyers. Existing buyers purchased at the price that was live at the time of their purchase.",
"If price decreases significantly, consider offering existing buyers a partial credit as a goodwill gesture.",
"Minor — guarantee change (upgrade)",
"Always entitled to the stronger guarantee, retroactively.",
"A guarantee upgrade benefits buyers. Withholding it retroactively creates a two-class system that generates complaints.",
"N/A.",
"Major — delivery model change",
"Not automatically entitled. A major version is a different product. However, existing buyers should be offered a transition path.",
"Major versions represent substantial new development. Existing buyers paid for the prior model.",
"Offer existing buyers access to the new version at a significant discount ('Upgrade Path') or offer them continued access to the prior version for a defined period.",
"",
"",
"PHASE 5",
"Copy & Asset Synchronisation System",
"Ensuring every buyer-facing asset reflects the current version",
"",
"The Copy Drift Problem",
"Copy drift occurs when the deployed version of an offer advances but one or more buyer-facing assets is not updated to reflect the new version. The Copy & Asset Synchronisation System is the checklist that ensures this cannot happen. It must be completed for every Minor and Major version change before the version is marked as live.",
"",
"The Sync Rule",
"A new version is not live until every item on the Copy Sync Checklist is either updated or confirmed as not requiring update. Partial deploys — where the delivery changes but the sales page does not — are the single largest source of expectation mismatch complaints.",
"",
"The Master Copy & Asset Sync Checklist",
"Complete this checklist for every Minor and Major version change. Each item must be marked: Updated / Not Required / Scheduled (with date) before the version is deployed.",
"",
"Sales Page Assets",
"☐ Headline and subheadline — do they accurately describe the current mechanism and promise?",
"☐ Offer stack section — does it list exactly what is currently included, with accurate values?",
"☐ Bonus section — are all listed bonuses current? Are all retired bonuses removed?",
"☐ Guarantee section — does it reflect the current guarantee tier and exact language?",
"☐ Social proof / testimonials — do all testimonials reference features or bonuses that still exist? (See Testimonial Audit below)",
"☐ Pricing — does it show the current price and all current payment plan options?",
"☐ 'Not for you' section — does it reflect current Negative Avatar profiles?",
"☐ FAQ section — are all FAQs consistent with current delivery, price, and guarantee?",
"☐ Comparison table (if present) — does it accurately describe the current offer vs. alternatives?",
"",
"Email Sequences",
"☐ Welcome / onboarding sequence — does it reference current modules, tools, and first steps accurately?",
"☐ 14-day nurture sequence — do Days 8–10 (mechanism introduction) reference the current mechanism name?",
"☐ Offer introduction email — does it describe the current offer stack?",
"☐ Bonus explanation emails — do they describe the current bonuses only?",
"☐ Objection handling emails — do they address objections relevant to the current version?",
"☐ Launch sequence (if evergreen) — does it reference current pricing and guarantee?",
"☐ Abandoned cart sequence — does it reference current price and offer stack?",
"",
"Paid Advertising",
"☐ All active ad creatives — do they reference current features, price, and promise?",
"☐ All active ad copy — are mechanism names, bonus names, and guarantee language current?",
"☐ Landing pages linked from ads — are they updated?",
"☐ Retargeting ad variants — are they consistent with current version?",
"",
"Affiliate and JV Assets",
"☐ Affiliate promotional swipe copy — does it describe the current offer accurately?",
"☐ Affiliate email templates — are mechanism names, bonuses, and pricing current?",
"☐ Affiliate social captions — are they current?",
"☐ JV landing pages (if custom pages exist for JV partners) — are they updated?",
"",
"Onboarding and Delivery Materials",
"☐ Welcome email (post-purchase) — does it accurately describe what they have access to and first steps?",
"☐ Onboarding survey — are baseline questions still relevant to the current programme structure?",
"☐ Course platform module titles and descriptions — do they match current content?",
"☐ Module completion criteria — are they current?",
"☐ Community welcome message and pinned resources — are they current?",
"☐ Support team FAQ document — is it updated for this version?",
"",
"GEO / AEO Schema and Digital Presence",
"☐ Offer schema markup (Product + Offer JSON-LD) — is pricing, description, and guarantee current?",
"☐ Pillar article or landing page that describes the offer — is it updated?",
"☐ LLMs.txt file — if the mechanism name or offer description changed, is it updated?",
"☐ Google My Business / local listing (if applicable) — is offer description current?",
"",
"The Testimonial Version-Lock Protocol",
"Testimonials are version-specific. A testimonial collected during V1.2.0 describes the V1.2.0 experience. If V1.3.0 removes or changes a feature that the testimonial mentions, the testimonial must be version-locked — flagged as belonging to a specific version — and either retired from the live sales page or annotated.",
"",
"Testimonial Status",
"Definition",
"Sales Page Treatment",
"Archive Treatment",
"Version-Current",
"The testimonial does not reference any feature, bonus, mechanism name, or price that has changed in any version after it was collected. It describes the transformation only.",
"Use freely on current sales page. No annotation required.",
"Maintain in active proof library with version tag.",
"Version-Specific (Usable)",
"The testimonial references specific features or bonuses that were present in the version when collected and are still present in the current version.",
"Use on current sales page. Mark with version tag in Airtable for monitoring.",
"Maintain with version tag. Review at each Minor version change.",
"Version-Specific (Retired)",
"The testimonial specifically mentions a feature, bonus, or mechanism name that no longer exists in the current version.",
"Remove from live sales page immediately. Do not annotate on live page — buyers see the annotation as a red flag.",
"Archive in proof library with version tag. May be reinstated if the feature is restored.",
"Price-Specific",
"The testimonial mentions a specific price paid that is no longer the current price. ('I paid $297 and it was worth every penny.')",
"Use with caution. If current price is higher, the price reference may create expectations or confusion. Consider requesting a new testimonial from the same buyer without the price reference.",
"Tag as Price-Specific. Monitor at each pricing change.",
"",
"Testimonial Audit Protocol",
"Run the Testimonial Audit at every Minor and Major version change. For each testimonial currently on the sales page:",
"",
"1. Read the testimonial for specific feature references: named bonuses, named modules, named tools, specific prices, specific mechanism names.",
"2. Check each referenced element against the current version's offer stack and mechanism name.",
"3. If any referenced element no longer exists in the current version: tag the testimonial as Version-Specific (Retired). Remove from live sales page. Archive.",
"4. Add a note to the changelog entry: 'Testimonial from [Buyer Name] retired from sales page — references [retired element].'",
"5. Reach out to the buyer within 30 days of retiring their testimonial to request an updated one based on the current version.",
"",
"",
"PHASE 6",
"The Buyer Communication Protocol",
"When and how to communicate version changes to existing buyers",
"",
"The Communication Decision Matrix",
"Not every version change requires a buyer communication. The Communication Decision Matrix defines which changes trigger which level of communication.",
"",
"Version Tier",
"Change Category",
"Communication Required?",
"Communication Type",
"Timing",
"PATCH",
"Any",
"No — unless the patch fixes something that directly affected a buyer's experience",
"If patch fixes a buyer-facing issue: proactive personal email to affected buyers only",
"Within 24 hours of patch deploy",
"MINOR",
"CAT-O: Content added (new bonus or module)",
"Yes — good news communication",
"Broadcast email to all existing buyers: 'You've been upgraded'",
"Same day as deploy or within 24 hours",
"MINOR",
"CAT-O: Content removed (bonus or module retired)",
"Yes — required communication",
"Email to all existing buyers: access maintenance period, archive link, reason for change",
"Minimum 14 days BEFORE removal",
"MINOR",
"CAT-P: Price increase",
"Yes — for existing list (not existing buyers)",
"Email to waitlist and engaged list: 'Founding member pricing closes [date]'. Existing buyers: notification for their awareness, no action required.",
"7–14 days before price change",
"MINOR",
"CAT-G: Guarantee upgrade",
"Yes — positive communication",
"Email to all existing buyers notifying them of the stronger guarantee they now have",
"Same day as deploy",
"MINOR",
"CAT-C / CAT-T: Copy or tech change",
"No — unless the change affects buyer access or experience",
"If access affected: notify affected buyers directly",
"Within 24 hours if access affected",
"MAJOR",
"Any",
"Yes — always required",
"Personal email from founder to all existing buyers: explain what changed, their options, and their transition path",
"Minimum 21 days before Major version deploys",
"",
"The Four Communication Templates",
"",
"Template 1 — Content Added (New Bonus or Module)",
"Content Added Communication Template",
"Subject: You've been upgraded — [Offer Name] just got better\n\nHi [First Name],\n\nQuick message to let you know we just added something to [Offer Name] that I think you'll find genuinely useful.\n\nBased on feedback from the last cohort — specifically the [specific challenge] that came up repeatedly — we've added [specific new bonus/module name]. It does [specific thing it solves].\n\nYou have it automatically. Access it here: [link].\n\nThis is now part of the offer permanently. If you have questions about it, [specific support channel].\n\n[Your name]",
"",
"Template 2 — Content Removed (Bonus or Module Retired)",
"Content Removed Communication Template",
"Subject: A change to [Offer Name] — and what it means for you\n\nHi [First Name],\n\nI want to give you advance notice of a change we're making to [Offer Name] on [date].\n\nWe're retiring [specific bonus/module name]. The reason: [honest, specific reason — outdated, superseded by better resource, low utility scores from recent feedback].\n\nWhat this means for you: If you've already accessed it and want to keep a copy, download it before [date + 14 days buffer]. After that date, we'll remove it from the platform.\n\nWe're replacing it with [new element] — which [specific improvement over the retired element].\n\nIf you have any questions about this, reply to this email.\n\n[Your name]",
"",
"Template 3 — Major Version Change (Delivery Model)",
"Major Version Communication Template",
"Subject: A significant update to [Offer Name] — your options\n\nHi [First Name],\n\nI want to be transparent about something we're changing in [Offer Name], and what your options are as someone who has already purchased.\n\nStarting [date], [Offer Name] is moving from [current format] to [new format]. Here's why: [specific evidence — completion rates, buyer feedback, results data].\n\nWhat this means for you:\n\nOption A: You keep full access to the current version ([V1.x]) until [date — minimum 12 months]. Nothing changes for you unless you want it to.\n\nOption B: You can transition to the new version at no additional cost. If you want to do this, [specific instructions].\n\nOption C: If you feel the change fundamentally alters what you purchased and you'd prefer a refund, I'll honour that — no questions asked. Email [email] by [date].\n\nI built the new version based on what I learned from people like you. I'm confident it delivers better results. But you deserve the choice.\n\n[Your name]",
"",
"Template 4 — Price Increase (Existing List)",
"Price Increase Communication Template",
"Subject: [Offer Name] price is going up — here's when and why\n\nHi [First Name],\n\nOn [date], the price of [Offer Name] is increasing from [current price] to [new price].\n\nWhy: [honest reason — added a new module, added the AI tool, results data justifies the price, we've invested in improving the delivery]. I want to make sure the price reflects what's actually being delivered.\n\nIf you've been thinking about joining — or if you know someone who has — the current price is locked until [date].\n\nAfter [date], the new price applies to all new purchases.\n\n[Your name]",
"",
"",
"PHASE 7",
"The Version Archive System",
"Every version of every offer preserved and findable",
"",
"The Archive Architecture",
"The Version Archive serves three functions: it provides a historical record for legal and compliance purposes, it enables rollback when a change produces unexpected negative results, and it provides the institutional memory that makes future iterations smarter. An archive that is not organised and findable is not an archive — it is a graveyard.",
"",
"The Archive Folder Structure",
"One folder per offer. Within each offer folder, one subfolder per Major version. Within each Major version folder, one document per Minor version change and one document per Patch.",
"",
"Recommended Archive Folder Structure",
"📁 RISER Nation — Offer Version Archive\n 📁 MVO-Offer\n 📁 V1 (2025-06-01 to 2026-01-14)\n 📄 MVO-V1.0.0-2025-06-01 — Launch Version\n 📄 MVO-V1.1.0-2025-07-15 — Added LinkedIn bonus\n 📄 MVO-V1.2.0-2025-09-10 — Price change $197→$297\n 📄 MVO-V1.2.1-2025-10-03 — Broken link fix (patch)\n 📄 MVO-V1.3.0-2025-11-20 — New bonus, retired old\n 📁 V2 (2026-01-15 to present)\n 📄 MVO-V2.0.0-2026-01-15 — Major: Live cohort conversion\n 📄 MVO-V2.0.1-2026-02-01 — Zoom link fix (patch)\n 📁 Core-Offer\n 📁 V1 (2025-09-01 to present)\n 📄 CORE-V1.0.0-2025-09-01 — Launch Version\n [etc.]",
"",
"What Each Version Archive Document Contains",
"Each version archive document is a snapshot of the offer as it existed at that version. It must contain enough information to restore that version completely if needed.",
"",
"Archive Document Section",
"What to Include",
"Version identifier and date",
"Full version identifier: [Offer Code]-V[X.Y.Z]-[YYYY-MM-DD]",
"The changelog entry",
"Full changelog entry from Phase 3 for this version",
"Offer stack snapshot",
"Complete list of every component included in this version: modules (with titles), bonuses (with names and described value), live calls (frequency and format), community access, tool access, and guarantee language. Verbatim from the sales page at time of version deploy.",
"Sales page snapshot",
"Full text of the sales page at the time of this version — headline, body copy, offer stack section, guarantee section, FAQ section. PDF export or text copy.",
"Price at this version",
"Sale price, payment plan options, and any promotional pricing active at launch of this version.",
"Active testimonials at this version",
"List of all testimonials on the live sales page at this version — buyer name, date collected, and version tag.",
"Affiliate copy at this version",
"Copy of all affiliate promotional emails, social captions, and swipe files distributed for this version.",
"Delivery architecture at this version",
"Summary of the delivery format, tools used, and fulfilment process at this version.",
"Known issues at this version",
"Any known bugs, complaints, or performance gaps identified during this version's active period. This feeds directly into the justification for the next version's changes.",
"",
"The Version Timeline View",
"The Version Timeline is a single-page summary document maintained at the top level of each offer's archive folder. It shows every version at a glance — date, tier, and one-sentence summary of the change.",
"",
"Version",
"Date",
"Change Summary",
"V1.0.0",
"2025-06-01",
"LAUNCH — Initial public launch. Self-paced course, 4 modules, 3 bonuses, 30-day money-back guarantee at $197.",
"V1.1.0",
"2025-07-15",
"MINOR — Added LinkedIn Outreach Playbook bonus (CAT-O). Justified by exit interview data showing LinkedIn was top unmet channel.",
"V1.2.0",
"2025-09-10",
"MINOR — Price increase $197 → $297 (CAT-P). Justified by new bonus addition and improved completion rate data.",
"V1.2.1",
"2025-10-03",
"PATCH — Fixed broken Module 2 worksheet link. Updated Vimeo → Wistia video hosting (CAT-T).",
"V1.3.0",
"2025-11-20",
"MINOR — Retired Cold Email Templates bonus. Added 30-Day Outreach Playbook. Guarantee upgraded to result-based conditional (CAT-O, CAT-G).",
"V2.0.0",
"2026-01-15",
"MAJOR — Converted from self-paced to live 4-week cohort. Mechanism renamed. Existing buyers grandfathered with 12-month access to V1 (CAT-D, CAT-M).",
"",
"",
"PHASE 8",
"The Rollback Protocol",
"What to do when a change makes things worse",
"",
"What Triggers a Rollback",
"A rollback is the reversal of a version change when that change has produced measurable negative outcomes. Rollbacks are rare in a well-managed versioning system because the changelog entry protocol requires an evidence-based justification for every change. But they are sometimes necessary, and having a pre-defined protocol prevents the confusion and delay that an unplanned rollback causes.",
"",
"Rollback Trigger",
"Threshold",
"Detection Window",
"Severity",
"Conversion rate drop following a Major or Minor change",
"Conversion rate falls 25% below the 30-day pre-change average and does not recover within 14 days",
"30-day post-deploy monitoring window",
"High — rollback consideration immediately",
"Refund rate spike following a change",
"Refund rate increases to 15%+ within 30 days of a change that altered the offer stack or guarantee",
"30-day post-deploy monitoring",
"Critical — rollback or change reversal within 72 hours",
"Completion rate drop following content changes",
"Completion rate falls 20%+ below the pre-change average within one full cohort or programme cycle",
"One programme cycle post-deploy",
"High — content rollback within next cohort cycle",
"Buyer complaint volume spike tied to specific change",
"3 or more buyers cite the same specific change as the source of their complaint within 21 days of deploy",
"21-day post-deploy monitoring",
"Medium to High depending on complaint severity",
"Affiliate performance drop tied to copy or stack change",
"Affiliate traffic conversion rate falls 30%+ below baseline within 21 days of an affiliate-affecting change",
"21-day post-deploy for affiliate traffic specifically",
"Medium — rollback or affiliate copy revert",
"",
"The Rollback Execution Steps",
"1. Confirm trigger threshold has been crossed using data from the relevant source (GA4, CRM, email platform, affiliate dashboard). Document the evidence.",
"2. Issue a new version number for the rollback. A rollback is not a re-issue of a prior version number — it is a new version that restores prior content. Example: V1.3.0 introduced a problematic change. Rollback is V1.3.1, which restores the V1.2.1 state.",
"3. Restore the specific component(s) that are being rolled back using the Version Archive Document for the prior version.",
"4. Complete a full Changelog Entry for the rollback version. Under 'Evidence That Triggered This Change' — document the rollback trigger data.",
"5. Run the Copy & Asset Sync Checklist (Phase 5) for the rollback version exactly as you would for a forward change.",
"6. Complete the Buyer Communication Protocol (Phase 6) if existing buyers are affected by the rollback.",
"7. Conduct a post-rollback analysis within 14 days: what assumption was wrong in the forward change? What evidence was missing? Document the finding in the rollback changelog entry.",
"",
"The Rollback Learning Principle",
"A rollback is one of the most valuable data events in the versioning system — because it tells you precisely what your market will not accept. The post-rollback analysis question — 'what assumption was wrong?' — becomes the highest-priority research item for the next forward version. The rollback is not a setback. It is a specification.",
"",
"",
"PHASE 9",
"The Changelog Review Cadence",
"Keeping the system alive, current, and strategically useful",
"",
"The Cadence Framework",
"Frequency",
"Activity",
"Time Required",
"Output",
"At every change deploy",
"Complete changelog entry. Run Copy & Asset Sync Checklist. Complete Change Impact Assessment. Notify affected parties.",
"45–90 min depending on change scope",
"Changelog entry filed. All assets updated. Notifications sent.",
"30 days after each Minor or Major deploy",
"30-Day Change Review: compare conversion rate, refund rate, completion rate, and support ticket volume against pre-change baseline. Confirm rollback threshold not triggered.",
"20 minutes",
"Change Impact Data added to changelog entry's 30-Day Review field.",
"Monthly (first Monday)",
"Review all changes made in the prior month. Are 30-day review data points filed? Are any assets still pending update? Are any rollback thresholds being approached?",
"30 minutes",
"Monthly Version Status Report.",
"Quarterly",
"Version Drift Audit: manually compare the current version's sales page against the Version Archive snapshot for the same offer. Identify any drift that occurred outside the formal versioning system.",
"90 minutes per active offer",
"Drift Audit Report. Any undocumented changes retroactively added to changelog and assigned a version number.",
"Annually",
"Full version history review: what have been the 3 most impactful changes of the year (by conversion or refund rate delta)? What does the version history reveal about what buyers actually value? Feed findings into the following year's offer development brief.",
"Half day",
"Annual Version Intelligence Report. Feeds into product roadmap.",
"",
"The Quarterly Version Drift Audit",
"The Version Drift Audit is the integrity check on the entire versioning system. It catches changes that were made informally — outside the changelog process — and retroactively brings them into the record. Every business has some degree of informal changes: the VA who updates the sales page without telling anyone, the community manager who changes the welcome message, the ad manager who updates ad copy without a formal change request. The Drift Audit finds these.",
"",
"1. Pull the Version Archive Document for the most recent Minor or Major version of each active offer.",
"2. Compare the 'Offer Stack Snapshot' in the archive against what is currently live on the sales page, in the email sequence, and in the course platform.",
"3. For every discrepancy found — something present in the live offer that is not in the archive snapshot, or vice versa — document it as an informal change.",
"4. For each informal change: assign it a retroactive version number (PATCH if minor, MINOR if significant). Create a changelog entry with 'Retroactive — discovered in Quarterly Drift Audit' noted in the evidence field.",
"5. Identify who made the informal change. Update team protocols to ensure all future changes go through the changelog process before deployment.",
"",
"",
"The Changelog Database — Airtable Schema",
"All changelog entries, version archive references, testimonial version tags, and affiliate copy audits live in a single Airtable base. The schema below is the complete data model.",
"",
"Table 1 — Changelog Entries",
"One record per version. The primary table of the system.",
"",
"Field",
"Type",
"Notes",
"Version Identifier",
"Short text",
"Format: [Offer Code]-V[X.Y.Z]-[YYYY-MM-DD]",
"Offer",
"Link → Offers table",
"",
"Version Tier",
"Single select",
"MAJOR / MINOR / PATCH",
"Change Category",
"Multiple select",
"CAT-M / CAT-D / CAT-O / CAT-P / CAT-G / CAT-C / CAT-T",
"Author",
"Short text",
"",
"Deployed Date",
"Date",
"",
"Change Summary",
"Short text",
"One sentence, plain language",
"Evidence That Triggered This Change",
"Long text",
"Data, feedback source, link",
"Change Detail",
"Long text",
"Full description of what changed — added, removed, modified",
"Existing Buyer Impact",
"Long text",
"Entitlement and communication plan",
"Sales Page Updated",
"Single select",
"Yes / No / Not Required",
"Email Sequence Updated",
"Single select",
"Yes / No / Not Required",
"Affiliate Notification Sent",
"Single select",
"Yes / No / Not Required",
"Testimonial Audit Completed",
"Single select",
"Yes / No / Not Required",
"Rollback Plan",
"Long text",
"Required for MAJOR and MINOR",
"30-Day Review Date",
"Date",
"Deployed Date + 30 days",
"30-Day Review Data",
"Long text",
"Conversion rate, refund rate, completion rate at 30 days",
"Rollback Triggered",
"Checkbox",
"If any rollback threshold was crossed",
"Archive Document Link",
"URL",
"Link to the Google Drive version archive document",
"Copy Sync Checklist Completed",
"Checkbox",
"All assets confirmed updated or not-required",
"",
"Table 2 — Testimonial Version Registry",
"One record per testimonial. Tracks the version the testimonial was collected in and its current status.",
"",
"Field",
"Type",
"Notes",
"Testimonial ID",
"Autonumber",
"",
"Buyer Name",
"Short text",
"",
"Date Collected",
"Date",
"",
"Offer",
"Link → Offers table",
"",
"Version at Collection",
"Link → Changelog Entries",
"The version that was live when this testimonial was collected",
"Testimonial Text",
"Long text",
"Full verbatim text",
"Testimonial Format",
"Single select",
"Written / Video / Audio",
"Specific Elements Referenced",
"Long text",
"Named bonuses, modules, mechanism names, prices mentioned in this testimonial",
"Current Status",
"Single select",
"Version-Current / Version-Specific (Usable) / Version-Specific (Retired) / Price-Specific",
"Active on Sales Page",
"Checkbox",
"Is this testimonial currently deployed on the live sales page?",
"Date Retired from Sales Page",
"Date",
"If retired — when removed",
"Reason Retired",
"Short text",
"Which changed element caused retirement",
"Updated Testimonial Requested",
"Checkbox",
"Has a new testimonial been requested from this buyer?",
"",
"Table 3 — Affiliate Copy Audit Log",
"One record per affiliate promotional asset audit. Tracks when each affiliate's copy was last reviewed and confirmed current.",
"",
"Field",
"Type",
"Notes",
"Audit ID",
"Autonumber",
"",
"Affiliate Name",
"Short text",
"",
"Offer",
"Link → Offers table",
"",
"Version Audited Against",
"Link → Changelog Entries",
"The current live version at time of audit",
"Audit Date",
"Date",
"",
"Assets Audited",
"Multiple select",
"Email swipe / Social captions / Landing page / Video script",
"Discrepancies Found",
"Long text",
"Any outdated references to retired features, wrong prices, or wrong mechanism names",
"Updated Assets Sent",
"Checkbox",
"Were new assets sent to the affiliate?",
"Date Updated Assets Sent",
"Date",
"",
"Next Audit Due",
"Date",
"Audit every Minor change and quarterly otherwise",
"",
"",
"Master Product Versioning & Changelog Checklist",
"",
"System Setup (One-Time)",
"☐ Create Changelog Entries table in Airtable with all fields from schema above",
"☐ Create Testimonial Version Registry table and link to Offers table",
"☐ Create Affiliate Copy Audit Log table",
"☐ Create Version Archive folder structure in Google Drive for each active offer",
"☐ Assign offer codes to all active offers (MVO / CORE / DWY / CONT / IC / etc.)",
"☐ Retroactively document current version of each active offer: create V1.0.0 entry dated at original launch",
"☐ If offer has already been changed since launch: run Quarterly Version Drift Audit and retroactively version all informal changes",
"☐ Version-tag all current testimonials in the Testimonial Version Registry",
"",
"Every Change Deploy (Required Before Going Live)",
"☐ Assign version tier: MAJOR / MINOR / PATCH using the Change Decision Tree",
"☐ Assign change category: CAT-M / CAT-D / CAT-O / CAT-P / CAT-G / CAT-C / CAT-T",
"☐ Complete all 17 fields of the Changelog Entry Template in Airtable",
"☐ Complete the Change Impact Assessment across all four impact dimensions",
"☐ Determine existing buyer entitlement using the Entitlement Policy table",
"☐ Run the Copy & Asset Sync Checklist — mark every item Updated / Not Required / Scheduled",
"☐ Run the Testimonial Audit — identify and retire any version-specific testimonials",
"☐ Draft and send all required buyer communications using the Communication Templates",
"☐ Send affiliate notification if CAT-O, CAT-P, CAT-M, or CAT-D change",
"☐ Brief internal team (sales, support, community) before deploy",
"☐ Create Version Archive Document and file in correct subfolder",
"☐ Set 30-Day Review calendar reminder in Airtable",
"",
"30 Days After Every Minor or Major Deploy",
"☐ Pull conversion rate, refund rate, completion rate, and support volume",
"☐ Compare against pre-change baseline",
"☐ Check all four rollback thresholds",
"☐ File 30-Day Review Data in changelog entry",
"☐ If any rollback threshold crossed: initiate Rollback Protocol",
"",
"Quarterly Version Drift Audit",
"☐ Pull Version Archive Document for each active offer",
"☐ Compare archive snapshot against all live buyer-facing assets",
"☐ Document all informal changes found — assign retroactive version numbers",
"☐ Update Testimonial Version Registry — any newly retired testimonials?",
"☐ Run Affiliate Copy Audit Log for all active affiliates",
"☐ Brief team on any informal change patterns found — tighten the process",
"",
"Annual Version Intelligence Review",
"☐ Pull all changelog entries for the year per offer",
"☐ Identify 3 highest-impact changes (conversion or refund delta evidence)",
"☐ Identify any patterns in what triggered the most valuable changes",
"☐ Write Annual Version Intelligence Report",
"☐ Feed findings into next year's offer development brief and mechanism rename cadence",
"",
"",
"",
"RISER Nation Master Operating System | Product Versioning & Offer Changelog SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | Product Versioning & Offer Changelog SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
},
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Design a clear guarantee and evaluate what changes
Begin with the buyer’s concern and the actual delivery
Imagine a buyer asking whether the course will work for their situation. A refund window alone may not answer that question. Another buyer may understand the method but worry about finding time to implement it. These are illustrative situations. Ask what protection the buyer needs, then compare the proposed promise with what the team can deliver.
The source treats guarantees as part of offer design. It claims a twenty-to-sixty-percent conversion lift and attributes three principles to Kennedy, Hormozi and Cialdini. Preserve those statements below as source material; they are not verified results or independently authenticated quotations.
Kennedy's Guarantee Principle The guarantee should feel almost reckless to you as the seller. If you're completely comfortable with your guarantee, it is almost certainly not bold enough to move your buyer. The guarantee should make you slightly nervous. That nervousness is the signal that you have transferred enough risk to create a genuine purchase trigger.
Hormozi's Risk Transfer Standard Every element of the Value Equation points toward the guarantee: reduce perceived time delay, reduce perceived effort, increase perceived likelihood of achievement. The guarantee addresses all three simultaneously. It says: 'The time you invest is protected. The effort you make is protected. The likelihood of achieving the result is so high that I am willing to guarantee it personally.' A weak guarantee undermines every other element of the offer.
Cialdini's Commitment Architecture The guarantee does not just reduce buyer risk — it also increases buyer commitment. A buyer who has explicitly agreed to the conditions of a conditional guarantee (complete the modules, submit the work, attend the calls) has made a public commitment to their own implementation. Cialdini's Commitment & Consistency principle means that buyer is more likely to complete the programme and less likely to refund. Counter-intuitive but empirically consistent: stronger guarantees reduce refund rates in programmes with high completion requirements.
The useful course application is to connect the promise, evidence, effort and buyer decision. This fits the Brunson and Hormozi themes used throughout the curriculum. Being nervous is not proof of a sound guarantee, and a guarantee does not remove all time, effort or financial costs. Conditions can encourage implementation, but the source’s claims about lower refunds require evidence.
This lesson explains the source protocol. It does not change buyer terms, issue refunds, contact people or activate experiments. The introduction says five phases; the full document contains eight. We cover all eight.
Compare all five guarantee types
Read each complete specification, including the example copy, intended audience, fear and exposure. These price bands and performance claims are source conventions, not demonstrated suitability for every business.
GUARANTEED TYPE 01 The Unconditional Money-Back LEVEL 1
Structure Full refund within a defined window (typically 14–30 days), no questions asked, no conditions to meet, no proof required. The buyer can request a refund for any reason or no reason at all.
Bold claim language "If you're not completely satisfied for any reason within [X] days, we'll refund every cent. No questions. No hassle. No explanation needed."
Best for Low-ticket offers ($7–$297). First-time buyers with no prior relationship. Commodity-adjacent offers where the primary barrier is scepticism about quality rather than implementation fear. Any offer where the refund window is too short for the buyer to meaningfully implement and then complain.
Primary fear it addresses "What if I don't like it?" — The fear of being stuck with something that doesn't meet expectations. Primarily a quality scepticism fear rather than an implementation fear.
Operator refund exposure Moderate. Refund rate typically 5–15% depending on offer clarity. High-quality delivers with strong onboarding typically achieve below 7%. Refund window is short enough that most buyers who would refund do so before investing significant time.
GUARANTEED TYPE 02 The Conditional Result-Based LEVEL 2
Structure Full refund (or partial refund) if the buyer completes a defined set of actions (modules watched, exercises submitted, calls attended) and does not achieve a specific, measurable result within a defined timeframe.
Bold claim language "Complete all [X] modules, submit your [deliverable], and if you don't achieve [specific result] within [timeframe], we'll refund every cent and you can keep everything."
Best for Core offers ($497–$4,997). Programmes with defined completion paths and measurable outcomes. Offers where the primary conversion barrier is 'Will this work for me?' rather than pure quality scepticism. Requires clearly defined completion criteria and a measurable result.
Primary fear it addresses "What if I do all the work and still don't get the result?" — The fear of a wasted investment despite genuine effort. The buyer is willing to do the work but afraid the method itself won't work for their situation.
Operator refund exposure Low to moderate when completion requirements are well-designed. Buyers who complete the programme almost never refund — the result-based guarantee primarily attracts and converts buyers who intend to implement. Actual refund claim rate on conditional guarantees typically falls to 1–4%.
GUARANTEED TYPE 03 The Double-Your-Money-Back LEVEL 3
Structure If the buyer completes the defined conditions and does not achieve the stated result, they receive a refund of 2× the purchase price. The operator pays the buyer more than they paid to enter.
Bold claim language "Complete [conditions] and if you don't [result], we'll refund your full investment plus an additional [amount] for your time. You literally cannot lose money by trying."
Best for Core and high-ticket offers ($997–$10,000) where the operator has extremely high confidence in delivery outcomes. Requires: documented completion rates above 75%, documented result achievement rates above 70%, strong fulfilment infrastructure, and liquid reserves to cover the occasional double refund.
Primary fear it addresses "What if I invest this much and it doesn't work?" — The acute fear of downside financial loss in high-stakes purchase decisions. Also addresses the 'I've tried things before and been burned' trust objection by demonstrating operator skin-in-the-game at a level no low-confidence seller would offer.
Operator refund exposure Very low claim rate if the programme genuinely delivers and completion requirements are achievable. High capital exposure per claim. Should only be deployed after Level 2 testing confirms high completion and result rates. Never deploy without stress-testing the financial exposure at your current buyer volume.
GUARANTEED TYPE 04 The Service Completion / 'We Work Until It Works' LEVEL 4
Structure The operator commits to continuing to work with the buyer, at no additional charge, until the promised result is delivered — regardless of how long that takes beyond the original programme timeline.
Bold claim language "We will work with you, in additional sessions at no cost, until you achieve [specific result]. We do not consider our job done until you get [result]. Period."
Best for Done-With-You and high-ticket offers ($5,000–$25,000). Programmes with a specific, discrete deliverable that can be confirmed as achieved. Works best when the operator has genuine leverage over the outcome (i.e., the result depends primarily on their expertise and effort, not entirely on the buyer's implementation).
Primary fear it addresses "What if I need more support than the programme includes?" — The fear of being abandoned before the result is achieved. Particularly powerful for buyers who have paid high prices before and not received the promised support when they needed it.
Operator refund exposure Significant ongoing time commitment if buyer does not implement between sessions. Requires strict eligibility criteria (buyer must complete their work between sessions to qualify for additional support). Without criteria, this guarantee can become an indefinite open commitment to non-implementing buyers.
GUARANTEED TYPE 05 The Anti-Guarantee LEVEL 5
Structure No refund offered. Application required to purchase. The selectivity of access IS the guarantee — the operator's willingness to decline applicants signals confidence that accepted buyers will succeed.
Bold claim language "This is not for everyone. We review every application personally. If we accept you, it is because we are confident we can get you the result. That conviction is our guarantee — we only work with people we know we can help."
Best for Inner Circle, mastermind, and high-selectivity DFY offers ($15,000–$100,000+). Requires: strong social proof, established reputation, a genuine application process, and a track record that makes the exclusivity credible. The anti-guarantee is the most powerful trust signal available — but only when the selectivity is genuine and the reputation backs it.
Primary fear it addresses "Is this operator actually confident in their ability to deliver?" — At this price point, the fear is not about losing money but about choosing the wrong person to trust with a major business decision. The anti-guarantee signals 'we only take people we know we can help' — which is the highest-confidence statement an operator can make.
Operator refund exposure Zero financial refund exposure. Significant reputational exposure if accepted buyers do not achieve results. The anti-guarantee transfers all credibility risk onto the operator's reputation, not their bank account. Should never be used as a way to avoid accountability — only as a genuine signal of selective commitment.
Level 1 offers a refund within a window without completion conditions. Level 2 ties the remedy to actions and an unmet result. Level 3 adds a payment beyond the original purchase. Level 4 extends service until a specified result. Level 5 replaces a standard refund offer with selection and reputation claims. It is not automatically more financial protection for a buyer than the earlier levels.
The source’s introductory spectrum starts with Implied, which is not one of these five named levels. Its suggestion to construct Level+1 and Level+2 candidates also differs from its later one-step-only rule. At Level 5, no higher numbered level is defined.
A double-refund proposal needs more than confidence. The opening specifies completion above seventy-five percent, results above seventy percent, prior Level 2 testing and reserves. Later eligibility rows differ. Ongoing service has a time-capacity obligation that a refund reserve alone cannot measure. The anti-guarantee’s claim of zero financial exposure is not established by the absence of a voluntary refund promise.
Phase 1 — Document the baseline and diagnose the weakness
The baseline has ten entries, including conversion, refund reasons, attention measures, objections, completion and current level. Record the period, numerator, denominator and data source so another person can interpret the measurements.
Email platform + CRM: new buyers from email ÷ email clicks × 100
5–15% viable range
Refund rate (rolling 30 days)
Stripe: refunds ÷ total sales × 100
Below 8% healthy
Refund root cause — 'not what I expected'
Airtable Refund Records: count of RC codes citing expectation mismatch
Below 30% of all refunds
Refund root cause — 'didn't get the result'
Airtable Refund Records: count of RC codes citing result not achieved
Below 20% of all refunds
Sales page scroll depth at guarantee section
Hotjar: % of visitors who scroll to the guarantee section
Above 60% ideally
Time spent at guarantee section
Hotjar session recordings: average seconds spent at guarantee copy
Above 15 seconds = engaged
Objection Bank — guarantee-related entries
Airtable Objection Bank: count of entries classified as Price & Value or Trust
Count
Completion rate
Course platform: % of buyers who complete the full programme
Target: above 45%
Current guarantee level
1–5 per the Five Guarantee Levels above
Note current level
The Minimum Viable Test Window Never run a guarantee test on fewer than 200 unique cold visitors per variant OR fewer than 14 days per variant, whichever comes later. Below 200 visitors, conversion rate data is noise. Below 14 days, day-of-week and time-of-day effects distort results. Both thresholds must be met before reading any test result.
Weakness Type
Diagnostic Signal
Test Direction
Priority
Invisibility Weakness
Hotjar shows fewer than 50% of visitors scroll to the guarantee section, OR visitors who do reach it spend fewer than 8 seconds there. The guarantee exists but is not being read.
Before testing a new guarantee level: reposition the guarantee higher on the page (above the price reveal or immediately below it). Test placement before testing the guarantee level itself.
Fix placement first — a better guarantee nobody reads produces no lift.
Language Weakness
The guarantee is at the right level (e.g., Level 2) but the copy is flat, legalistic, or corporate. The condition and the bold claim are present but the emotional resonance is absent.
Test a rewritten version of the same guarantee level using the Guarantee Copy Engineering system (Phase 4) before upgrading to a higher level. A Level 2 guarantee written powerfully often outperforms a Level 3 guarantee written boringly.
High — copy rewrites are free to deploy and take one day to write.
Level Weakness
Visitors read the guarantee (scroll depth and time-on-section are healthy) but conversion is still below target. The guarantee is seen and understood but not compelling enough.
Test the next level up: if current is Level 1, test Level 2. If current is Level 2, test Level 3. Never skip more than one level in a single test.
High — this is the primary use case for this SOP.
Mismatch Weakness
Refund root cause data shows that refund language frequently mentions the guarantee was 'not what was described' or 'conditions were unclear.' The guarantee is generating confusion rather than confidence.
Rewrite the conditions in plain language before testing any level change. A confused buyer does not convert. A confused buyer who does convert refunds.
Critical — fix clarity before testing level.
The default history is sixty days, with a shorter-history exception. Refunds use a rolling thirty-day period and completion may use a prior cohort. Do not treat them as if they all describe identical buyers and dates. Warm conversion uses email clicks; those are not necessarily unique people.
The four diagnoses imply different next steps. Invisibility concerns whether people encounter the guarantee. Language concerns its explanation. Level concerns the structure. Mismatch concerns unclear expectations or conditions. Placement and same-level copy tests are alternatives named by the source, even though later construction rules specify a level increase.
Two hundred visitors and fourteen days are minimum source rules, not proof of sufficient statistical power. Delayed refunds and completion may not be observable at that point. A test needs an explicit analysis and outcome-maturity plan, which the source does not fully supply.
Phase 2 — Examine the five risk inputs separately
The source uses a higher score to represent stronger readiness. Read each input and the ceiling table, then apply the separate low-input rule.
How many months of total refund exposure (at current buyer volume × offer price) does your cash reserve cover if every buyer with the new guarantee claimed it? Score: 6+ months = 5 points. 3–5 months = 4 points. 2 months = 3 points. 1 month = 2 points. Less than 1 month = 1 point.
___
R4 — Result achievement rate
Of buyers who complete the programme, what % report achieving the core promised result? Score: 80%+ = 5 points. 65–79% = 4 points. 50–64% = 3 points. 35–49% = 2 points. Below 35% = 1 point. Note: if you do not track this, default to 2 points and add result tracking as an immediate action.
___
R5 — Fulfilment stress test status
Has the Fulfilment Stress Test SOP been completed for this offer? Score: Passed all phases = 5 points. Completed with minor remediation outstanding = 3 points. Not yet completed = 1 point.
___
TOTAL RISK SCORE
Sum of R1 through R5. Maximum: 25 points.
___
Risk Score
Maximum Testable Level
Rationale
20–25 (Low Risk)
Level 4 or Level 5
Strong delivery foundation, high completion, strong cash reserves. Aggressive guarantees will not destroy the business if the test variant produces an unexpected refund spike.
15–19 (Moderate Risk)
Level 3
Solid fundamentals with some gaps. Can test the Double-Your-Money-Back but should not proceed to Service Completion without closing the specific gaps identified in the lower scores.
10–14 (Elevated Risk)
Level 2
Conditional Result-Based is the appropriate ceiling. Test this level thoroughly before considering Level 3. Address the specific inputs scoring 1 or 2 before retesting.
5–9 (High Risk)
Level 1 (rewrite only)
The delivery infrastructure is not yet strong enough to support a more aggressive guarantee. The test at this score level is a copy rewrite of the current Level 1, not a level upgrade. Address R2 (completion rate) and R4 (result achievement rate) as the primary priorities.
Below 5
No guarantee test
Do not run a guarantee test. The offer has fundamental delivery problems that a stronger guarantee will amplify, not solve. Fix delivery first.
The Risk Score Re-Test Rule Any Risk Score input that scores 1 or 2 is a delivery infrastructure gap that must be addressed before running a Level 3 or higher guarantee test. A Level 3 guarantee deployed on an offer with a 25% completion rate will produce a catastrophic refund spike. The guarantee does not fix the offer — it amplifies whatever the offer already is, positive or negative.
The aggregate can hide a weak input. The prose requires addressing any score of one or two before Level 3 or above; the final checklist merely asks to document a remediation action. A written action is not completed remediation.
Several bands use whole-number labels without a rounding rule, leaving fractional gaps. Cash coverage does not clearly price double refunds or indefinite service. Results are reported among completers rather than all buyers. Missing result tracking defaults to two points, which is a convention rather than evidence. Fulfilment status lacks an explicit failed-test category.
Five inputs worth at least one point make the Below 5 band unreachable under the stated scoring rules. Record missing or invalid evidence explicitly rather than inventing a score to fit that band. The later core-tier sixty-percent completion threshold conflicts with the opening Level 3 seventy-five-percent requirement.
Phase 3 — Define the experiment before observing results
The four principles cover the variable being changed, sequential levels, statistical evidence and multiple outcome measures.
One variable only. The guarantee is the only element that changes between the control and the variant. Same headline, same body copy, same stack slide, same price, same CTA. If anything else is different, the test cannot attribute its result to the guarantee.
One level at a time. Never jump from Level 1 to Level 3 in a single test. Test sequentially: if Level 2 beats Level 1, then test Level 2 vs Level 3. Skipping levels produces wins that cannot be explained and losses that cannot be diagnosed.
Statistical significance before declaration. A test result is not a result until it reaches 95% statistical significance. A conversion rate difference of 0.2 percentage points on 50 visitors is noise, not signal.
Measure all three metrics. Every guarantee test measures conversion rate AND refund rate AND completion rate. A guarantee that lifts conversion but doubles refunds is not a win.
Test Element
Control
Variant
Rules
Guarantee level
Current level (document exactly)
Current level + 1 step (never skip)
Both written at equal copy quality
Conditions (if applicable)
Existing conditions exactly as live
New conditions for the higher level — specific, achievable, and written in plain language
Conditions must be completable by a buyer who implements at average pace
Bold claim
Existing bold claim language
New bold claim for the higher level
Must match the level — a Level 3 bold claim on a Level 2 structure is misleading
Placement on page
Current placement
Identical placement
Never change placement between control and variant — confounds the test
Visual treatment
Current visual (if any)
Identical visual treatment
Same font size, same surrounding white space, same section heading
Risk reversal symbol
If a shield or badge is used in control
Identical symbol in variant
Visual consistency required
The variant changes guarantee structure, conditions and language together. That estimates the effect of that package, not a numeric level in isolation. Keep placement and visual treatment consistent when the purpose is a structure comparison. If testing placement or wording instead, document that separate question.
Preserve all ten pre-test checks and all four success rows below.
☐ Baseline metrics documented in Airtable Guarantee Test Record (see Phase 8 schema)
☐ Risk Score calculated — maximum testable level confirmed
☐ Variant guarantee copy written to Level+1 standard using Phase 4 engineering system
☐ Variant conditions reviewed for clarity and achievability — could an average buyer meet these?
☐ A/B test tool configured (Convert.com, VWO, or equivalent) — 50/50 split confirmed
☐ Conversion goal configured in the test tool (purchase event via Stripe webhook or equivalent)
☐ Refund tracking mechanism confirmed — new refunds from test period can be tagged to control vs variant
☐ Minimum visitor threshold confirmed: 200 unique cold visitors per variant required before reading
☐ Minimum duration threshold confirmed: 14 days minimum per variant regardless of visitor volume
☐ Kill condition defined: if variant refund rate exceeds control refund rate by 200% or more at any point, the test is paused and the variant is reviewed
Metric
Minimum Lift to Declare Variant a Winner
Maximum Acceptable Change to Deploy Permanently
Cold conversion rate
Variant must exceed control by a minimum of 0.3 percentage points at 95% statistical significance
N/A — higher conversion is always directionally positive
Warm conversion rate
Variant must exceed control by a minimum of 1.0 percentage point at 95% statistical significance
N/A — higher conversion is always directionally positive
Refund rate
Variant refund rate must not exceed control refund rate by more than 50% (e.g. if control is 6%, variant ceiling is 9%)
Hard ceiling: if variant refund rate exceeds 15% at any point during the test, pause and review immediately
Completion rate
Variant completion rate must not fall more than 5 percentage points below control (stronger guarantees sometimes attract buyers who are less committed to implementation)
If completion rate drops more than 10 percentage points, the guarantee is attracting wrong-fit buyers — review avatar targeting before deploying
Cold lift is specified in percentage points, while the refund ceiling uses relative change. A fifty-percent increase from six percent is nine percent. The kill phrase “exceeds control by two hundred percent” ordinarily describes three times the control rate; it needs clarification before use. A zero control rate makes a relative comparison undefined.
Also retain the absolute fifteen-percent refund pause and both completion limits: more than five percentage points below control fails the deployment criterion; more than ten prompts investigation. The later Clear Winner summary omits some of these constraints. It cannot replace the complete success table.
The protocol does not define sample-size planning, a statistical method, repeated-look handling or a rule when cold and warm results disagree. No significant difference is not proof of equivalence. Count-based refund comparisons also omit the different payout sizes and service costs needed to substantiate the title’s margin objective.
Phase 4 — Explain the protection clearly
The five copy elements are the claim, confidence evidence, conditions, claim process and summary. Compare the weak and strong examples, then read all five complete templates.
Element
Purpose
Weak Version
Strong Version
The Bold Claim
The headline of the guarantee section. Must state the protection in its most powerful form — not the conditions, not the fine print, the core protection.
"30-Day Money-Back Guarantee"
"You Either Get [Specific Result] or You Get Your Money Back. Full Stop."
The Confidence Statement
One sentence in the operator's voice stating WHY they can make this guarantee. Must be specific — not 'because I believe in my product' but because of verifiable evidence.
"I'm so confident you'll love this programme."
"In the last 18 months, 94% of buyers who completed all four modules reported [specific result]. That rate is why I can make this guarantee and sleep comfortably."
The Conditions (if Level 2+)
The specific, plain-language actions required to qualify for the guarantee. Must be achievable by an average buyer, specific enough to verify, and stated without legal jargon.
"You must have completed all programme materials and attempted to apply the methods before requesting a refund."
"Watch all four modules (each is under 60 minutes). Submit your completed offer stack worksheet. Attend at least one live Q&A call. If you do all three and don't have [specific result], email us for a full refund."
The Claim Process
Exactly how a buyer claims the guarantee. Removes the fear that the refund process will be difficult or ignored.
"Contact our support team."
"Email [specific address] with 'Refund Request' in the subject line. Include your worksheet submission. We process all requests within 2 business days. No back-and-forth, no interrogation."
The Risk Reversal Summary
A one-sentence summary that reframes the guarantee in terms of what the buyer cannot lose. The emotional close of the guarantee section.
"So there's really no risk."
"The only way you lose is if you do all the work and somehow don't get [result] — and in that case, you get every cent back. Either way, you win."
Level 1 Template BOLD CLAIM: Your Investment Is Fully Protected for [X] Days.
Try the entire programme for [X] days. Watch every module. Use every template. Attend every live session. If at any point during that window you decide this isn't for you — for any reason or no reason — email [address] and we'll refund every cent within 48 hours. No forms to fill out. No justification required. No hard feelings.
Why can I offer this? Because our average buyer completes [Module 1] within [48 hours] and reports [specific early result]. I know what happens when someone genuinely engages with this material. That knowledge is what makes this guarantee easy to offer.
Either you get [result] or you get your money back. That is the only outcome available to you.
Level 2 Template BOLD CLAIM: Get [Specific Result] or Get Your Money Back. Guaranteed.
Here is my commitment to you: complete all [X] modules, submit your [specific deliverable], and attend at least [X] of the [X] live calls. Do those three things and if you have not achieved [specific, measurable result] within [timeframe], I will refund your full investment. Every cent.
I can make this commitment because [specific evidence: e.g., 'In our last three cohorts, every buyer who completed all three requirements achieved [result]. Not most. Every one.']. The conditions exist not to create a barrier to refunds but to create a commitment to implementation — because implementation is the only thing standing between you and the result.
If you do the work, you get the result. If you do the work and somehow don't get the result, you get your money back. You cannot lose if you implement.
Level 3 Template BOLD CLAIM: Complete the Programme, Don't Get [Result], and We'll Pay You [2× Price].
This is not a standard guarantee. Complete [specific conditions]. If you meet those conditions and do not have [specific result] by [date], we will refund your full [price] investment and send you an additional [matching amount] as compensation for your time. You walk away with [2× price] for doing everything right and not getting the outcome.
Why would I offer this? Because in [X] cohorts, with [X] total buyers, [X]% of buyers who completed all conditions achieved [result]. I am not offering this guarantee to be generous — I am offering it because the risk of paying it out is genuinely small. The few buyers who might claim it are the cost of doing business with absolute confidence.
If this guarantee makes you feel safer, good. If it makes you wonder whether this is real, call us. We will walk you through exactly what it means and exactly how it would work if you needed to claim it.
Level 4 Template BOLD CLAIM: We Work With You Until You Get [Result]. No Time Limit. No Extra Charge.
When you join [programme name], we commit to one outcome: you achieving [specific result]. If the standard programme timeline ends and you have implemented fully but have not yet reached [result], we will continue working with you in additional [session type] at no charge until you get there.
What 'fully implemented' means: [specific criteria]. We are not offering endless hand-holding for non-implementation. We are offering a commitment that our work together does not end until the job is done.
We make this commitment because [specific evidence of completion and results]. Our obligation to you does not end at the last session date. It ends when you have [result].
Level 5 Template We Do Not Offer a Standard Refund Policy.
Every applicant to [programme name] goes through a personal review process. We read every application. We speak with every candidate. We decline applicants we don't believe we can help, and we accept only those we are confident can achieve [result] with our support.
That selectivity is our guarantee. We do not offer a money-back policy because we do not accept buyers we are not certain we can serve. If we accept you, it means we have reviewed your situation and committed our reputation to your outcome.
The people we decline are not worse people or lesser operators — they are simply not the right fit for this specific programme at this specific time. We would rather refer you to the right resource than take your money knowing we cannot deliver.
If that level of confidence and selectivity is not what you are looking for in a programme, we are not the right fit. If it is — apply.
The evidence placeholders require actual records. Statements about every completer, ninety-four percent success or specific cohort outcomes are not facts about this business merely because they appear in the template. Likewise, a stated processing time must describe an actual process. Forty-eight hours and two business days can differ.
Explain conditions and limitations as clearly as the headline. The source’s “cannot lose” summaries overlook time and other costs, and an unconditional window does not promise unlimited future protection. The general conditions-for-Level-2-plus instruction does not neatly describe Level 5’s no-refund structure. A reviewer must resolve those differences before real use.
Phase 5 — Keep the message consistent across seven locations
The placement table covers three sales-page positions, nurture email, a sales call, checkout and the welcome email. Each location serves a different moment in the buyer’s decision.
Placement Location
Function
Copy Length
Recommended Position
Sales page — above the fold (referenced)
Creates an immediate awareness that a guarantee exists. Reduces the scepticism the buyer carries into the page.
One line: 'See our [X]-day guarantee below.'
Within the first 3 paragraphs or in the hero section
Sales page — after the price reveal
The primary conversion moment. Directly addresses the risk that was just triggered by seeing the price.
Full guarantee section: all five copy elements in sequence
Immediately below the price and payment options
Sales page — FAQ section
Addresses the guarantee-specific objections that the primary section may not have fully answered.
Q&A format: 3–5 specific guarantee questions answered in plain language
FAQ section — guarantee questions should be among the top 3 FAQ entries
Email sequence — Day 11 (Objection Handling)
Specifically addresses price and trust objections via the guarantee. Buyers who did not convert from the sales page often convert from a guarantee-focused email.
Medium length: one paragraph per guarantee copy element. Lead with the bold claim as the subject line.
Day 11 of the 14-day nurture sequence
Sales call — after price is introduced
Verbal reinforcement of the guarantee to reduce the risk associated with a large verbal commitment. Must match the written guarantee exactly.
One paragraph summary, spoken naturally. Provide a written one-pager if the buyer wants to share with a partner.
After price is stated, before asking for a decision
Checkout page
Last-moment reinforcement for buyers who have reached checkout and are experiencing purchase anxiety.
One sentence plus the bold claim. Do not repeat the full conditions at this stage.
Directly above the payment button
Post-purchase email (Day 0)
Confirmation that the guarantee applies. Reduces buyer's remorse and refund request rate in the first 24 hours.
One paragraph referencing the guarantee terms and how to claim if needed.
Within the first welcome email, after the access instructions
Use a distinct visual container — a coloured box, a border, or a distinct background — to signal that the guarantee section is different from body copy. Buyers scan for it specifically.
The bold claim should be in the largest font on the guarantee section — larger than the subheadings above and below it. It is the headline of this section.
If a shield, checkmark, or guarantee badge graphic is used: keep it simple, professional, and small. A large generic stock-art shield undermines credibility. The copy does the heavy lifting, not the graphic.
The conditions (Level 2+) should be in a checklist format — not a wall of prose. Buyers scan conditions; they do not read them like a contract. Scannable conditions feel transparent, not restrictive.
The claim process should be in a single sentence with the specific email address hyperlinked. Nothing signals bad faith faster than a vague refund claim process.
The full conditions and claim process must remain accessible; shorter checkout copy is not authority to hide material limitations. If variants are tested across several channels, each buyer needs consistent terms and variant attribution. That routing is not supplied by this checklist. The source describes badge graphics but does not provide the assets.
Phase 6 — Interpret all four outcomes
Read the four source outcomes in full before making a proposed decision.
OUTCOME 1 — CLEAR WINNER Variant beats Control on conversion AND does not exceed the refund rate ceiling The new guarantee level lifts conversion at 95% statistical significance AND the variant refund rate is within the pre-defined acceptable range (no more than 50% above the control rate).
Decision: Deploy the variant permanently. File the test record. Update the Product Versioning Changelog (CAT-G: Guarantee Change). Update the Offer Scorecard (D6 — Guarantee Power).
Next action: Schedule the Level+1 test to determine whether an even more aggressive guarantee would produce further lift.
OUTCOME 2 — CONVERSION LIFT BUT REFUND SPIKE Variant beats Control on conversion BUT exceeds the refund rate ceiling The new guarantee is attracting buyers who were not previously converting — and those buyers are refunding at a higher rate than existing buyers. This pattern almost always means the guarantee is creating a misalignment between buyer expectation and programme delivery.
Decision: Do NOT deploy permanently. Run the Refund Forensics Protocol (Forensic Audit Loop SOP, Phase 5) to identify the specific expectation gap. Fix the gap — either in the sales copy (reduce the promise), in the delivery (increase the result), or in the guarantee conditions (add a condition that filters the non-implementing buyer) — then retest.
Do not blame the guarantee. Blame the gap between what buyers expected and what they received.
OUTCOME 3 — NO SIGNIFICANT DIFFERENCE Variant and Control produce statistically equivalent conversion rates The new guarantee level produced no measurable conversion lift. This is a clean negative result and is valuable data.
Possible diagnosis: The guarantee is not the primary conversion barrier for this offer and audience. The actual barrier may be the mechanism name, the social proof, the copy, or the offer stack — not the risk reversal. Go back to the Offer Scorecard and run dimension-specific diagnostics on D1 (Dream Outcome), D2 (Mechanism Believability), D5 (Offer Stack Strength), and D7 (Social Proof Specificity) before making further guarantee changes.
Do not immediately jump to testing Level+2. A flat test at Level+1 suggests the guarantee level is not the conversion lever for this offer at this stage.
OUTCOME 4 — VARIANT DEPRESSES CONVERSION Control outperforms Variant The new guarantee level produced lower conversion than the current guarantee. This is unusual but occurs in specific scenarios: the conditions of a Level 2 guarantee feel onerous or unachievable to a predominantly passive buyer avatar, or the 'double your money back' language at Level 3 triggers scepticism rather than confidence in an audience that has been burned by over-promising operators.
Decision: Retain the Control. Document the result. Diagnose the cause: review the variant's conditions for achievability, review the bold claim for believability, and review the buyer avatar for any signs of deep scepticism based on prior bad experiences in the category. The Objection Bank should already contain entries that explain why stronger guarantees may be triggering distrust rather than confidence for this specific audience.
A proposed winner must still satisfy the earlier conversion-lift, refund and completion requirements. A refund spike suggests investigation; it does not by itself prove the buyer’s motives or a specific expectation gap. A flat result may reflect uncertainty or insufficient sensitivity, rather than proving that guarantees do not matter. Lower conversion also needs evidence before attributing it to distrust or passive buyers.
The next-level suggestion remains constrained by readiness, sequential testing and the highest defined level. No test or deployment has been initiated by this lesson.
Phase 7 — Maintain the guarantee and its history
The source provides five review occasions. Preserve each trigger and output, then compare them with the weekly review and versioning companions.
Frequency
Activity
Trigger Condition
Output
Quarterly (with Offer Scorecard)
Review D6 (Guarantee Power) score from the Offer Scorecard. If D6 scores 3 or below, initiate a new guarantee test cycle.
Scheduled: first Tuesday of each quarter, as part of the monthly Offer Scorecard session
Updated D6 score. Test cycle initiated if D6 ≤ 3.
After any Major or Minor version change
Review the guarantee for alignment with the updated offer. A new module, a new delivery format, or a changed promise may require a guarantee update.
Product Versioning SOP trigger: any CAT-O, CAT-D, or CAT-M change
Guarantee reviewed for alignment. Updated or confirmed as current.
After any refund rate spike (above 12%)
Run Refund Forensics first to identify root cause. If refund root cause codes show 'result not achieved' above 30%, the guarantee conditions may need to be strengthened (more achievable completion requirements, shorter result timeframe, or clearer result definition).
Weekly Offer Review trigger: Refund Signal Red
Refund Forensics completed. Guarantee reviewed. Conditions updated if indicated.
When a competitor deploys a significantly stronger guarantee
Category guarantee norms shift the buyer's reference point. If the leading competitor in your category upgrades from Level 2 to Level 3, your Level 2 may suddenly feel inadequate by comparison.
GEO/AEO monitoring: quarterly competitor scan
Competitor guarantee benchmarked. Test initiated if gap is significant.
When the Risk Score improves significantly
A substantial improvement in completion rate (R2) or result achievement rate (R4) may now justify testing a higher guarantee level that was previously blocked by the Risk Score ceiling.
Quarterly Risk Score recalculation
Risk Score updated. New maximum testable level confirmed. Test initiated if justified.
Guarantee Version History
Every guarantee change must be logged in the Product Versioning SOP as a CAT-G (Guarantee Change) entry. The full guarantee text at each version must be preserved in the Version Archive for three reasons: legal compliance (buyer entitlement policy), institutional memory (knowing which versions were tested and what they produced), and rollback capability (if a new guarantee increases refunds, the prior version must be restorable exactly).
The Buyer Entitlement Rule for Guarantee Upgrades When a guarantee is upgraded (e.g., from Level 1 to Level 2, or from 30 days to 60 days), all existing buyers are immediately entitled to the stronger guarantee — retroactively. Do not communicate this proactively unless asked, but if an existing buyer requests a refund under the new terms after a guarantee upgrade, honour it. Withholding a guarantee upgrade from buyers who purchased before the change is both legally questionable and reputationally damaging.
Quarterly review is nested within monthly scoring. The twelve-percent refund maintenance trigger differs from the test’s fifteen-percent pause and other weekly thresholds. The refund-reason percentage also differs from the baseline target. These are separate source rules with different contexts, not one unified trigger.
The source’s retroactive entitlement statement is a proposed policy and legal claim, not a determination of actual buyer rights. Moving from unconditional to conditional protection is not automatically an upgrade. Its instruction to avoid proactive communication conflicts with the versioning source’s guarantee-upgrade notices. Preserve actual prior terms and flag the conflict for review rather than silently changing commitments.
Phase 8 — Work through the four edge cases
The first case treats each value-ladder tier separately. Preserve the six rows, including their special history and eligibility requirements.
Value Ladder Tier
Recommended Starting Test Level
Maximum Level Without Additional Risk Scoring
Tripwire ($7–$27)
Level 1 (unconditional, 7–14 days)
Level 1 only — the purchase price is too low for conditional guarantees to be meaningful or enforceable
Frontend / MVO ($47–$497)
Level 1 or Level 2
Level 2 — the purchase justifies conditions; do not attempt Level 3 without a 6-month performance history
Core Offer ($997–$4,997)
Level 2
Level 3 if Risk Score is 15+ and completion rate is above 60%
DWY ($5K–$15K)
Level 2 or Level 3
Level 4 — service completion is appropriate when the operator's effort is the primary result driver
DFY ($10K–$50K)
Level 4 (milestone payment structure)
Level 5 — anti-guarantee is appropriate when the application process is genuinely selective and the reputation backs it
Inner Circle ($25K+)
Level 5
Level 5 only — application-only, no refunds
The price bands differ from earlier descriptions and contain overlaps or gaps. A tier label cannot override the risk review. The named milestone-payment structure is not fully specified. The second case raises completion decline as an investigation signal; its claim that certain buyers intend to refund is a hypothesis, not something a rate proves.
Edge Case 2 — The Guarantee That Creates the Wrong Buyer
The most dangerous outcome of a guarantee test is not a refund rate spike — it is a completion rate collapse. Some guarantee structures, particularly long unconditional windows (90-day or longer money-back), attract buyers who pay and then immediately begin planning their refund rather than engaging with the content. These buyers consume support resources, generate negative community energy, and refund at near-100% rates regardless of the offer's quality.
Diagnostic signal: completion rate drops significantly (more than 10 percentage points) between the control and the variant, even if refund rates are within bounds. This is the 'passive buyer attraction' problem — the guarantee is selecting for buyers who view the purchase as a risk-free trial rather than a commitment.
Resolution: add an active engagement condition to the guarantee even if it is minimal. A condition that requires completing Module 1 before the guarantee applies filters out passive buyers without meaningfully deterring committed ones. The act of engaging with Module 1 is itself a commitment signal that changes the buyer's relationship to the purchase.
Edge Case 3 — The Guarantee Objection in a Sales Call
Some buyers on discovery calls will probe the guarantee in ways that reveal a deeper trust issue than the guarantee alone can resolve. When a buyer spends more than two minutes on the guarantee in a sales call, the guarantee is a proxy for a deeper concern — usually "I've been burned before" (Trust & Credibility objection) or "I don't trust myself to implement" (Implementation Fear objection).
The correct response is not to over-explain the guarantee. It is to name the underlying fear: "It sounds like the guarantee is important to you — and I want to make sure we're addressing the right thing. Is your concern primarily about whether the method works, or is it more about whether you'll be able to implement it fully?" The answer to that question determines whether to reinforce the result-based guarantee (method fear) or to walk through the Quick Win and accountability structure (implementation fear).
The Guarantee Objection Rule for Sales Calls Never allow a guarantee conversation to run for more than 3 minutes without asking: 'What would need to be true for you to feel completely confident moving forward, beyond the guarantee?' A buyer who cannot answer that question is not ready to buy regardless of the guarantee level. A buyer who can answer it has just given you the exact objection you need to close.
The two-minute and three-minute call rules are source heuristics. Use the questions to clarify concerns rather than assuming that a duration proves distrust or unreadiness. The method-versus-implementation distinction can guide an explanation of evidence, the quick win or accountability.
The fourth case contains the source’s legal-review statements, preserved below. They are not a current jurisdiction-specific compliance review or certification. No live guarantee is changed here.
Edge Case 4 — FTC and Legal Compliance
Guarantee claims in the United States and most other jurisdictions are governed by consumer protection regulations. The FTC has specific requirements for guarantee claims in marketing. This SOP does not provide legal advice, but the following principles reflect standard best practice:
Every condition stated in the guarantee must be achievable. A condition designed to make the guarantee practically unclaimable is potentially deceptive under FTC guidelines.
The guarantee terms must be clearly and conspicuously disclosed. 'No fine print' is both a copywriting principle and a legal requirement.
The claim process must function as described. A guarantee that is advertised but difficult to claim in practice is a violation regardless of the stated terms.
Double-your-money-back guarantees must be honoured when legitimately claimed. Never deploy a Level 3 guarantee that you are not financially prepared to honour.
Review all guarantee copy with legal counsel before deploying Level 3 or above, particularly if your market includes consumers in jurisdictions with specific consumer protection requirements (EU, UK, Australia).
Preserve the complete database specification
The native table contains thirty fields. Read the full schema; a described field is not a deployed database or working automation.
Field
Type
Notes
Test ID
Autonumber
Format: GTR-[Offer Code]-[YYYY-MM]-[Seq]
Offer
Link → Offers table
Test Start Date
Date
Test End Date
Date
When the test reached statistical significance or the minimum duration
Control Guarantee Level
Single select
Level 1 / 2 / 3 / 4 / 5
Control Guarantee Text
Long text
Full verbatim guarantee copy as live during the test
Variant Guarantee Level
Single select
Level 1 / 2 / 3 / 4 / 5
Variant Guarantee Text
Long text
Full verbatim guarantee copy for the variant
Risk Score at Test Start
Number
R1+R2+R3+R4+R5, out of 25
Maximum Testable Level Confirmed
Single select
Level 1 / 2 / 3 / 4 / 5 — from the Risk Score table
Deploy Variant / Retain Control / Diagnose and Retest / Escalate to Forensic Audit
Deployment Date (if deployed)
Date
When the winning variant went live permanently
Changelog Entry
Link → Changelog Entries
CAT-G entry from Product Versioning SOP
Next Test Level (if applicable)
Single select
Level 1 / 2 / 3 / 4 / 5 — what to test next
Next Test Scheduled Date
Date
Notes
Long text
Any observations, anomalies, or context from the test period
The schema lacks variant warm rates, separate risk inputs, most baseline diagnostics, prespecified criteria, payout exposure, outcome-maturity dates and statistical method. The formatted Test ID requires more than an autonumber alone. Its test-end note uses significance or minimum duration, unlike the earlier rules requiring minimums plus evidence before a winner. Keep these missing implementation details explicit.
Complete the review checklist
All seven master-checklist groups follow. Treat them as proposed work to evaluate, not as actions already completed.
Phase 1 — Baseline Guarantee Audit
☐ Pull all 10 baseline metrics from the data sources listed in Phase 1
☐ Identify which of the four Guarantee Weakness types applies to the current offer
☐ If Invisibility Weakness: fix placement before testing any level change
☐ If Language Weakness: run a copy rewrite test before testing a level upgrade
☐ If Mismatch Weakness: rewrite conditions in plain language before any other change
☐ Document all baseline data in Airtable Guarantee Test Record before the test begins
Phase 2 — Risk Scoring
☐ Calculate all five Risk Score inputs (R1 through R5)
☐ Sum the total Risk Score and identify the Maximum Testable Level
☐ If any input scores 1 or 2: document the gap as a remediation action before testing Level 3 or above
☐ Risk Score documented in the test record
Phase 3 — Test Design
☐ Confirm: one variable only — guarantee is the only change between control and variant
☐ Confirm: testing only one level up from current (never skip levels)
☐ Write variant guarantee copy to the same quality standard as the control using Phase 4 templates
☐ Define success criteria before the test begins — document in Airtable test record
☐ Configure A/B test tool with 50/50 split and conversion goal tracking
☐ Set up variant-specific refund tagging in Stripe or CRM
☐ Confirm minimum thresholds: 200 unique cold visitors per variant AND 14 days minimum
☐ Define kill condition: if variant refund rate exceeds control by 200%, pause immediately
☐ Complete pre-test checklist in Airtable before activating the test
Phase 4 — Guarantee Copy Engineering
☐ Write Bold Claim for the variant guarantee level using the template for that level
☐ Write Confidence Statement with specific evidence (completion rate, result rate, or testimonial data)
☐ Write Conditions (Level 2+) in plain language, checklist format, and confirm each is achievable by an average buyer
☐ Write Claim Process with specific email address and response timeframe
☐ Write Risk Reversal Summary as the emotional close of the section
☐ Peer review: read the guarantee copy to one avatar-matched individual. Can they explain it in one sentence after one reading?
Phase 5 — Deployment Architecture
☐ Guarantee placed in all seven required locations (sales page above fold reference, after price, FAQ, email Day 11, sales call script, checkout, post-purchase email)
☐ Visual treatment applied: distinct container, bold claim in largest font, conditions in checklist format
☐ Claim process includes specific email address (not 'contact support')
Phase 6 — Reading the Result
☐ Statistical significance reached: 95% confidence confirmed before declaring a winner
☐ All three metrics reviewed: conversion rate, refund rate, completion rate
☐ Outcome classified as one of four types: Clear Winner / Lift+Spike / No Difference / Depressed
☐ Deployment decision documented in Airtable test record
☐ If deploying: Product Versioning Changelog updated (CAT-G entry filed)
☐ If deploying: Offer Scorecard D6 (Guarantee Power) updated at next monthly session
☐ If refund spike: Refund Forensics Protocol initiated before any further guarantee changes
Phase 7 — Maintenance Cadence
☐ Guarantee reviewed quarterly as part of the Offer Scorecard D6 scoring
☐ Guarantee reviewed after any CAT-O, CAT-D, or CAT-M version change
☐ Risk Score recalculated quarterly — maximum testable level updated if inputs have improved
☐ Competitor guarantee benchmark completed quarterly as part of the AEO/GEO monitoring review
☐ All guarantee changes logged in Product Versioning Changelog (CAT-G)
☐ Prior guarantee copy archived in Version Archive Document for legal and rollback purposes
Write a proposed guarantee review for one offer: buyer concern, current promise, five readiness inputs, unresolved eligibility conflicts, candidate wording, required evidence and how outcomes would be measured. Keep example numbers labeled as examples. Submit no real commitments or experiment until its actual terms, tracking and delivery requirements have been reviewed.
RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING. The original footer is preserved in the source appendix.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — GUARANTEE TYPE TESTING PROTOCOL
The Systematic Method for Identifying, Testing, and Deploying the Guarantee That Maximises Conversion Without Destroying Margin
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
The guarantee is the single most underestimated lever in offer design. Most operators treat it as a compliance requirement — the legally necessary 'if you're not happy, get your money back' clause buried at the bottom of a sales page. A guarantee engineered this way does almost nothing for conversion. A guarantee engineered as a strategic risk-transfer instrument can lift conversion rates by 20–60% on the same offer, to the same audience, with zero other changes.
The reason most guarantees underperform is not that buyers don't care about risk — they care deeply. It's that the guarantee doesn't address the specific fear the buyer is carrying. A buyer afraid of wasting money is not reassured by a 30-day money-back guarantee. A buyer afraid they won't implement is not reassured by a result-based guarantee they know they won't qualify for. The mismatch between the guarantee's structure and the buyer's actual fear is what kills its conversion power.
This SOP defines the five guarantee levels, the five-phase testing protocol that identifies which level maximises conversion for each offer and avatar, the risk-scoring system that determines how aggressive an operator can afford to be, the guarantee language engineering system that makes the guarantee copy as persuasive as the offer itself, the deployment architecture, and the measurement framework that confirms the test result before permanent deployment.
Kennedy's Guarantee Principle
The guarantee should feel almost reckless to you as the seller. If you're completely comfortable with your guarantee, it is almost certainly not bold enough to move your buyer. The guarantee should make you slightly nervous. That nervousness is the signal that you have transferred enough risk to create a genuine purchase trigger.
Hormozi's Risk Transfer Standard
Every element of the Value Equation points toward the guarantee: reduce perceived time delay, reduce perceived effort, increase perceived likelihood of achievement. The guarantee addresses all three simultaneously. It says: 'The time you invest is protected. The effort you make is protected. The likelihood of achieving the result is so high that I am willing to guarantee it personally.' A weak guarantee undermines every other element of the offer.
Cialdini's Commitment Architecture
The guarantee does not just reduce buyer risk — it also increases buyer commitment. A buyer who has explicitly agreed to the conditions of a conditional guarantee (complete the modules, submit the work, attend the calls) has made a public commitment to their own implementation. Cialdini's Commitment & Consistency principle means that buyer is more likely to complete the programme and less likely to refund. Counter-intuitive but empirically consistent: stronger guarantees reduce refund rates in programmes with high completion requirements.
The Five Guarantee Levels
Every guarantee in any knowledge business sits somewhere on a five-level spectrum from Implied (lowest operator commitment) to Anti-Guarantee (highest selectivity signal). The testing protocol works by identifying which level your current offer is at, building candidate guarantees at Level+1 and Level+2 above your current position, and running structured tests to find the conversion ceiling.
GUARANTEED TYPE 01
The Unconditional Money-Back
LEVEL 1
Structure
Full refund within a defined window (typically 14–30 days), no questions asked, no conditions to meet, no proof required. The buyer can request a refund for any reason or no reason at all.
Bold claim language
"If you're not completely satisfied for any reason within [X] days, we'll refund every cent. No questions. No hassle. No explanation needed."
Best for
Low-ticket offers ($7–$297). First-time buyers with no prior relationship. Commodity-adjacent offers where the primary barrier is scepticism about quality rather than implementation fear. Any offer where the refund window is too short for the buyer to meaningfully implement and then complain.
Primary fear it addresses
"What if I don't like it?" — The fear of being stuck with something that doesn't meet expectations. Primarily a quality scepticism fear rather than an implementation fear.
Operator refund exposure
Moderate. Refund rate typically 5–15% depending on offer clarity. High-quality delivers with strong onboarding typically achieve below 7%. Refund window is short enough that most buyers who would refund do so before investing significant time.
GUARANTEED TYPE 02
The Conditional Result-Based
LEVEL 2
Structure
Full refund (or partial refund) if the buyer completes a defined set of actions (modules watched, exercises submitted, calls attended) and does not achieve a specific, measurable result within a defined timeframe.
Bold claim language
"Complete all [X] modules, submit your [deliverable], and if you don't achieve [specific result] within [timeframe], we'll refund every cent and you can keep everything."
Best for
Core offers ($497–$4,997). Programmes with defined completion paths and measurable outcomes. Offers where the primary conversion barrier is 'Will this work for me?' rather than pure quality scepticism. Requires clearly defined completion criteria and a measurable result.
Primary fear it addresses
"What if I do all the work and still don't get the result?" — The fear of a wasted investment despite genuine effort. The buyer is willing to do the work but afraid the method itself won't work for their situation.
Operator refund exposure
Low to moderate when completion requirements are well-designed. Buyers who complete the programme almost never refund — the result-based guarantee primarily attracts and converts buyers who intend to implement. Actual refund claim rate on conditional guarantees typically falls to 1–4%.
GUARANTEED TYPE 03
The Double-Your-Money-Back
LEVEL 3
Structure
If the buyer completes the defined conditions and does not achieve the stated result, they receive a refund of 2× the purchase price. The operator pays the buyer more than they paid to enter.
Bold claim language
"Complete [conditions] and if you don't [result], we'll refund your full investment plus an additional [amount] for your time. You literally cannot lose money by trying."
Best for
Core and high-ticket offers ($997–$10,000) where the operator has extremely high confidence in delivery outcomes. Requires: documented completion rates above 75%, documented result achievement rates above 70%, strong fulfilment infrastructure, and liquid reserves to cover the occasional double refund.
Primary fear it addresses
"What if I invest this much and it doesn't work?" — The acute fear of downside financial loss in high-stakes purchase decisions. Also addresses the 'I've tried things before and been burned' trust objection by demonstrating operator skin-in-the-game at a level no low-confidence seller would offer.
Operator refund exposure
Very low claim rate if the programme genuinely delivers and completion requirements are achievable. High capital exposure per claim. Should only be deployed after Level 2 testing confirms high completion and result rates. Never deploy without stress-testing the financial exposure at your current buyer volume.
GUARANTEED TYPE 04
The Service Completion / 'We Work Until It Works'
LEVEL 4
Structure
The operator commits to continuing to work with the buyer, at no additional charge, until the promised result is delivered — regardless of how long that takes beyond the original programme timeline.
Bold claim language
"We will work with you, in additional sessions at no cost, until you achieve [specific result]. We do not consider our job done until you get [result]. Period."
Best for
Done-With-You and high-ticket offers ($5,000–$25,000). Programmes with a specific, discrete deliverable that can be confirmed as achieved. Works best when the operator has genuine leverage over the outcome (i.e., the result depends primarily on their expertise and effort, not entirely on the buyer's implementation).
Primary fear it addresses
"What if I need more support than the programme includes?" — The fear of being abandoned before the result is achieved. Particularly powerful for buyers who have paid high prices before and not received the promised support when they needed it.
Operator refund exposure
Significant ongoing time commitment if buyer does not implement between sessions. Requires strict eligibility criteria (buyer must complete their work between sessions to qualify for additional support). Without criteria, this guarantee can become an indefinite open commitment to non-implementing buyers.
GUARANTEED TYPE 05
The Anti-Guarantee
LEVEL 5
Structure
No refund offered. Application required to purchase. The selectivity of access IS the guarantee — the operator's willingness to decline applicants signals confidence that accepted buyers will succeed.
Bold claim language
"This is not for everyone. We review every application personally. If we accept you, it is because we are confident we can get you the result. That conviction is our guarantee — we only work with people we know we can help."
Best for
Inner Circle, mastermind, and high-selectivity DFY offers ($15,000–$100,000+). Requires: strong social proof, established reputation, a genuine application process, and a track record that makes the exclusivity credible. The anti-guarantee is the most powerful trust signal available — but only when the selectivity is genuine and the reputation backs it.
Primary fear it addresses
"Is this operator actually confident in their ability to deliver?" — At this price point, the fear is not about losing money but about choosing the wrong person to trust with a major business decision. The anti-guarantee signals 'we only take people we know we can help' — which is the highest-confidence statement an operator can make.
Operator refund exposure
Zero financial refund exposure. Significant reputational exposure if accepted buyers do not achieve results. The anti-guarantee transfers all credibility risk onto the operator's reputation, not their bank account. Should never be used as a way to avoid accountability — only as a genuine signal of selective commitment.
PHASE 1
The Baseline Guarantee Audit
Establishing where you are before deciding where to test
The Audit Purpose
Before any testing begins, the current guarantee's performance must be established as a documented baseline. Testing without a baseline produces data that cannot be interpreted — you cannot know whether a new guarantee lifted or depressed conversion if you do not know what the current guarantee was producing.
The Baseline Data Pull
Pull the following data for the prior 60 days minimum before the test begins. If the offer has not yet been live for 60 days, use all available data and note the shorter window in the test record.
Email platform + CRM: new buyers from email ÷ email clicks × 100
5–15% viable range
Refund rate (rolling 30 days)
Stripe: refunds ÷ total sales × 100
Below 8% healthy
Refund root cause — 'not what I expected'
Airtable Refund Records: count of RC codes citing expectation mismatch
Below 30% of all refunds
Refund root cause — 'didn't get the result'
Airtable Refund Records: count of RC codes citing result not achieved
Below 20% of all refunds
Sales page scroll depth at guarantee section
Hotjar: % of visitors who scroll to the guarantee section
Above 60% ideally
Time spent at guarantee section
Hotjar session recordings: average seconds spent at guarantee copy
Above 15 seconds = engaged
Objection Bank — guarantee-related entries
Airtable Objection Bank: count of entries classified as Price & Value or Trust
Count
Completion rate
Course platform: % of buyers who complete the full programme
Target: above 45%
Current guarantee level
1–5 per the Five Guarantee Levels above
Note current level
The Minimum Viable Test Window
Never run a guarantee test on fewer than 200 unique cold visitors per variant OR fewer than 14 days per variant, whichever comes later. Below 200 visitors, conversion rate data is noise. Below 14 days, day-of-week and time-of-day effects distort results. Both thresholds must be met before reading any test result.
The Guarantee Weakness Diagnostic
Before deciding which guarantee level to test, identify which of four weakness types your current guarantee exhibits. The weakness type determines which test direction has the highest probability of lifting conversion.
Weakness Type
Diagnostic Signal
Test Direction
Priority
Invisibility Weakness
Hotjar shows fewer than 50% of visitors scroll to the guarantee section, OR visitors who do reach it spend fewer than 8 seconds there. The guarantee exists but is not being read.
Before testing a new guarantee level: reposition the guarantee higher on the page (above the price reveal or immediately below it). Test placement before testing the guarantee level itself.
Fix placement first — a better guarantee nobody reads produces no lift.
Language Weakness
The guarantee is at the right level (e.g., Level 2) but the copy is flat, legalistic, or corporate. The condition and the bold claim are present but the emotional resonance is absent.
Test a rewritten version of the same guarantee level using the Guarantee Copy Engineering system (Phase 4) before upgrading to a higher level. A Level 2 guarantee written powerfully often outperforms a Level 3 guarantee written boringly.
High — copy rewrites are free to deploy and take one day to write.
Level Weakness
Visitors read the guarantee (scroll depth and time-on-section are healthy) but conversion is still below target. The guarantee is seen and understood but not compelling enough.
Test the next level up: if current is Level 1, test Level 2. If current is Level 2, test Level 3. Never skip more than one level in a single test.
High — this is the primary use case for this SOP.
Mismatch Weakness
Refund root cause data shows that refund language frequently mentions the guarantee was 'not what was described' or 'conditions were unclear.' The guarantee is generating confusion rather than confidence.
Rewrite the conditions in plain language before testing any level change. A confused buyer does not convert. A confused buyer who does convert refunds.
Critical — fix clarity before testing level.
PHASE 2
The Risk Scoring System
Determining how aggressive you can afford to be before testing
Why Risk Scoring Comes Before Testing
A guarantee that lifts conversion by 30% but increases refunds by 400% is not a successful guarantee — it is a business destruction mechanism. The Risk Scoring System establishes the operator's maximum allowable refund exposure before any test is designed, so the test variants are defined within financially viable parameters.
How many months of total refund exposure (at current buyer volume × offer price) does your cash reserve cover if every buyer with the new guarantee claimed it? Score: 6+ months = 5 points. 3–5 months = 4 points. 2 months = 3 points. 1 month = 2 points. Less than 1 month = 1 point.
___
R4 — Result achievement rate
Of buyers who complete the programme, what % report achieving the core promised result? Score: 80%+ = 5 points. 65–79% = 4 points. 50–64% = 3 points. 35–49% = 2 points. Below 35% = 1 point. Note: if you do not track this, default to 2 points and add result tracking as an immediate action.
___
R5 — Fulfilment stress test status
Has the Fulfilment Stress Test SOP been completed for this offer? Score: Passed all phases = 5 points. Completed with minor remediation outstanding = 3 points. Not yet completed = 1 point.
___
TOTAL RISK SCORE
Sum of R1 through R5. Maximum: 25 points.
___
Risk Score → Maximum Testable Guarantee Level
Risk Score
Maximum Testable Level
Rationale
20–25 (Low Risk)
Level 4 or Level 5
Strong delivery foundation, high completion, strong cash reserves. Aggressive guarantees will not destroy the business if the test variant produces an unexpected refund spike.
15–19 (Moderate Risk)
Level 3
Solid fundamentals with some gaps. Can test the Double-Your-Money-Back but should not proceed to Service Completion without closing the specific gaps identified in the lower scores.
10–14 (Elevated Risk)
Level 2
Conditional Result-Based is the appropriate ceiling. Test this level thoroughly before considering Level 3. Address the specific inputs scoring 1 or 2 before retesting.
5–9 (High Risk)
Level 1 (rewrite only)
The delivery infrastructure is not yet strong enough to support a more aggressive guarantee. The test at this score level is a copy rewrite of the current Level 1, not a level upgrade. Address R2 (completion rate) and R4 (result achievement rate) as the primary priorities.
Below 5
No guarantee test
Do not run a guarantee test. The offer has fundamental delivery problems that a stronger guarantee will amplify, not solve. Fix delivery first.
The Risk Score Re-Test Rule
Any Risk Score input that scores 1 or 2 is a delivery infrastructure gap that must be addressed before running a Level 3 or higher guarantee test. A Level 3 guarantee deployed on an offer with a 25% completion rate will produce a catastrophic refund spike. The guarantee does not fix the offer — it amplifies whatever the offer already is, positive or negative.
PHASE 3
The Test Design Protocol
Building the test variants, defining the success criteria, and setting the kill conditions
Test Design Principles
•One variable only. The guarantee is the only element that changes between the control and the variant. Same headline, same body copy, same stack slide, same price, same CTA. If anything else is different, the test cannot attribute its result to the guarantee.
• One level at a time. Never jump from Level 1 to Level 3 in a single test. Test sequentially: if Level 2 beats Level 1, then test Level 2 vs Level 3. Skipping levels produces wins that cannot be explained and losses that cannot be diagnosed.
• Statistical significance before declaration. A test result is not a result until it reaches 95% statistical significance. A conversion rate difference of 0.2 percentage points on 50 visitors is noise, not signal.
• Measure all three metrics. Every guarantee test measures conversion rate AND refund rate AND completion rate. A guarantee that lifts conversion but doubles refunds is not a win.
The Test Variant Construction
Every guarantee test has exactly two variants: the Control (current guarantee) and the Variant (new guarantee level). Both variants must have their guarantee section written to the same standard of copy quality — do not test a well-written control against a poorly written variant or vice versa.
Test Element
Control
Variant
Rules
Guarantee level
Current level (document exactly)
Current level + 1 step (never skip)
Both written at equal copy quality
Conditions (if applicable)
Existing conditions exactly as live
New conditions for the higher level — specific, achievable, and written in plain language
Conditions must be completable by a buyer who implements at average pace
Bold claim
Existing bold claim language
New bold claim for the higher level
Must match the level — a Level 3 bold claim on a Level 2 structure is misleading
Placement on page
Current placement
Identical placement
Never change placement between control and variant — confounds the test
Visual treatment
Current visual (if any)
Identical visual treatment
Same font size, same surrounding white space, same section heading
Risk reversal symbol
If a shield or badge is used in control
Identical symbol in variant
Visual consistency required
The Pre-Test Checklist
☐ Baseline metrics documented in Airtable Guarantee Test Record (see Phase 8 schema)
☐ Risk Score calculated — maximum testable level confirmed
☐ Variant guarantee copy written to Level+1 standard using Phase 4 engineering system
☐ Variant conditions reviewed for clarity and achievability — could an average buyer meet these?
☐ A/B test tool configured (Convert.com, VWO, or equivalent) — 50/50 split confirmed
☐ Conversion goal configured in the test tool (purchase event via Stripe webhook or equivalent)
☐ Refund tracking mechanism confirmed — new refunds from test period can be tagged to control vs variant
☐ Minimum visitor threshold confirmed: 200 unique cold visitors per variant required before reading
☐ Minimum duration threshold confirmed: 14 days minimum per variant regardless of visitor volume
☐ Kill condition defined: if variant refund rate exceeds control refund rate by 200% or more at any point, the test is paused and the variant is reviewed
Success Criteria Definition
Define success criteria before the test begins. Do not define them after seeing results — post-hoc success criteria are not success criteria, they are rationalisations.
Metric
Minimum Lift to Declare Variant a Winner
Maximum Acceptable Change to Deploy Permanently
Cold conversion rate
Variant must exceed control by a minimum of 0.3 percentage points at 95% statistical significance
N/A — higher conversion is always directionally positive
Warm conversion rate
Variant must exceed control by a minimum of 1.0 percentage point at 95% statistical significance
N/A — higher conversion is always directionally positive
Refund rate
Variant refund rate must not exceed control refund rate by more than 50% (e.g. if control is 6%, variant ceiling is 9%)
Hard ceiling: if variant refund rate exceeds 15% at any point during the test, pause and review immediately
Completion rate
Variant completion rate must not fall more than 5 percentage points below control (stronger guarantees sometimes attract buyers who are less committed to implementation)
If completion rate drops more than 10 percentage points, the guarantee is attracting wrong-fit buyers — review avatar targeting before deploying
PHASE 4
The Guarantee Copy Engineering System
Writing guarantee language that functions as the most powerful sentence in the offer
Why Guarantee Copy Is Underestimated
Most operators treat the guarantee as a legal disclosure. They write it in the passive voice, use corporate language, and bury it beneath a wall of conditions. A guarantee written this way does not move buyers — it satisfies legal counsel and nothing else.
The guarantee copy is the single piece of copy on a sales page where you, the operator, are speaking in your own voice about your own confidence in your delivery. It is the moment the buyer either believes you or does not. Every word in the guarantee section should be doing persuasive work.
The Five Copy Elements of a High-Performance Guarantee
Element
Purpose
Weak Version
Strong Version
The Bold Claim
The headline of the guarantee section. Must state the protection in its most powerful form — not the conditions, not the fine print, the core protection.
"30-Day Money-Back Guarantee"
"You Either Get [Specific Result] or You Get Your Money Back. Full Stop."
The Confidence Statement
One sentence in the operator's voice stating WHY they can make this guarantee. Must be specific — not 'because I believe in my product' but because of verifiable evidence.
"I'm so confident you'll love this programme."
"In the last 18 months, 94% of buyers who completed all four modules reported [specific result]. That rate is why I can make this guarantee and sleep comfortably."
The Conditions (if Level 2+)
The specific, plain-language actions required to qualify for the guarantee. Must be achievable by an average buyer, specific enough to verify, and stated without legal jargon.
"You must have completed all programme materials and attempted to apply the methods before requesting a refund."
"Watch all four modules (each is under 60 minutes). Submit your completed offer stack worksheet. Attend at least one live Q&A call. If you do all three and don't have [specific result], email us for a full refund."
The Claim Process
Exactly how a buyer claims the guarantee. Removes the fear that the refund process will be difficult or ignored.
"Contact our support team."
"Email [specific address] with 'Refund Request' in the subject line. Include your worksheet submission. We process all requests within 2 business days. No back-and-forth, no interrogation."
The Risk Reversal Summary
A one-sentence summary that reframes the guarantee in terms of what the buyer cannot lose. The emotional close of the guarantee section.
"So there's really no risk."
"The only way you lose is if you do all the work and somehow don't get [result] — and in that case, you get every cent back. Either way, you win."
Level-by-Level Copy Templates
Level 1: Unconditional Money-Back Copy Template
Level 1 Template
BOLD CLAIM: Your Investment Is Fully Protected for [X] Days.
Try the entire programme for [X] days. Watch every module. Use every template. Attend every live session. If at any point during that window you decide this isn't for you — for any reason or no reason — email [address] and we'll refund every cent within 48 hours. No forms to fill out. No justification required. No hard feelings.
Why can I offer this? Because our average buyer completes [Module 1] within [48 hours] and reports [specific early result]. I know what happens when someone genuinely engages with this material. That knowledge is what makes this guarantee easy to offer.
Either you get [result] or you get your money back. That is the only outcome available to you.
Level 2: Conditional Result-Based Copy Template
Level 2 Template
BOLD CLAIM: Get [Specific Result] or Get Your Money Back. Guaranteed.
Here is my commitment to you: complete all [X] modules, submit your [specific deliverable], and attend at least [X] of the [X] live calls. Do those three things and if you have not achieved [specific, measurable result] within [timeframe], I will refund your full investment. Every cent.
I can make this commitment because [specific evidence: e.g., 'In our last three cohorts, every buyer who completed all three requirements achieved [result]. Not most. Every one.']. The conditions exist not to create a barrier to refunds but to create a commitment to implementation — because implementation is the only thing standing between you and the result.
If you do the work, you get the result. If you do the work and somehow don't get the result, you get your money back. You cannot lose if you implement.
Level 3: Double-Your-Money-Back Copy Template
Level 3 Template
BOLD CLAIM: Complete the Programme, Don't Get [Result], and We'll Pay You [2× Price].
This is not a standard guarantee. Complete [specific conditions]. If you meet those conditions and do not have [specific result] by [date], we will refund your full [price] investment and send you an additional [matching amount] as compensation for your time. You walk away with [2× price] for doing everything right and not getting the outcome.
Why would I offer this? Because in [X] cohorts, with [X] total buyers, [X]% of buyers who completed all conditions achieved [result]. I am not offering this guarantee to be generous — I am offering it because the risk of paying it out is genuinely small. The few buyers who might claim it are the cost of doing business with absolute confidence.
If this guarantee makes you feel safer, good. If it makes you wonder whether this is real, call us. We will walk you through exactly what it means and exactly how it would work if you needed to claim it.
Level 4: Service Completion Copy Template
Level 4 Template
BOLD CLAIM: We Work With You Until You Get [Result]. No Time Limit. No Extra Charge.
When you join [programme name], we commit to one outcome: you achieving [specific result]. If the standard programme timeline ends and you have implemented fully but have not yet reached [result], we will continue working with you in additional [session type] at no charge until you get there.
What 'fully implemented' means: [specific criteria]. We are not offering endless hand-holding for non-implementation. We are offering a commitment that our work together does not end until the job is done.
We make this commitment because [specific evidence of completion and results]. Our obligation to you does not end at the last session date. It ends when you have [result].
Level 5: Anti-Guarantee Copy Template
Level 5 Template
We Do Not Offer a Standard Refund Policy.
Every applicant to [programme name] goes through a personal review process. We read every application. We speak with every candidate. We decline applicants we don't believe we can help, and we accept only those we are confident can achieve [result] with our support.
That selectivity is our guarantee. We do not offer a money-back policy because we do not accept buyers we are not certain we can serve. If we accept you, it means we have reviewed your situation and committed our reputation to your outcome.
The people we decline are not worse people or lesser operators — they are simply not the right fit for this specific programme at this specific time. We would rather refer you to the right resource than take your money knowing we cannot deliver.
If that level of confidence and selectivity is not what you are looking for in a programme, we are not the right fit. If it is — apply.
PHASE 5
The Deployment Architecture
Where the guarantee appears, how it is presented, and what surrounds it
Guarantee Placement Strategy
The guarantee must appear in multiple locations across the buyer's journey — not once at the bottom of a sales page. Each placement serves a different function in the conversion sequence.
Placement Location
Function
Copy Length
Recommended Position
Sales page — above the fold (referenced)
Creates an immediate awareness that a guarantee exists. Reduces the scepticism the buyer carries into the page.
One line: 'See our [X]-day guarantee below.'
Within the first 3 paragraphs or in the hero section
Sales page — after the price reveal
The primary conversion moment. Directly addresses the risk that was just triggered by seeing the price.
Full guarantee section: all five copy elements in sequence
Immediately below the price and payment options
Sales page — FAQ section
Addresses the guarantee-specific objections that the primary section may not have fully answered.
Q&A format: 3–5 specific guarantee questions answered in plain language
FAQ section — guarantee questions should be among the top 3 FAQ entries
Email sequence — Day 11 (Objection Handling)
Specifically addresses price and trust objections via the guarantee. Buyers who did not convert from the sales page often convert from a guarantee-focused email.
Medium length: one paragraph per guarantee copy element. Lead with the bold claim as the subject line.
Day 11 of the 14-day nurture sequence
Sales call — after price is introduced
Verbal reinforcement of the guarantee to reduce the risk associated with a large verbal commitment. Must match the written guarantee exactly.
One paragraph summary, spoken naturally. Provide a written one-pager if the buyer wants to share with a partner.
After price is stated, before asking for a decision
Checkout page
Last-moment reinforcement for buyers who have reached checkout and are experiencing purchase anxiety.
One sentence plus the bold claim. Do not repeat the full conditions at this stage.
Directly above the payment button
Post-purchase email (Day 0)
Confirmation that the guarantee applies. Reduces buyer's remorse and refund request rate in the first 24 hours.
One paragraph referencing the guarantee terms and how to claim if needed.
Within the first welcome email, after the access instructions
The Guarantee Visual Architecture
The visual presentation of the guarantee section on the sales page significantly affects both scroll-stop and time-on-section metrics. These design principles apply regardless of which level is being tested.
•Use a distinct visual container — a coloured box, a border, or a distinct background — to signal that the guarantee section is different from body copy. Buyers scan for it specifically.
• The bold claim should be in the largest font on the guarantee section — larger than the subheadings above and below it. It is the headline of this section.
• If a shield, checkmark, or guarantee badge graphic is used: keep it simple, professional, and small. A large generic stock-art shield undermines credibility. The copy does the heavy lifting, not the graphic.
• The conditions (Level 2+) should be in a checklist format — not a wall of prose. Buyers scan conditions; they do not read them like a contract. Scannable conditions feel transparent, not restrictive.
• The claim process should be in a single sentence with the specific email address hyperlinked. Nothing signals bad faith faster than a vague refund claim process.
PHASE 6
Reading the Test Result
Interpreting what the data says and making the deployment decision
The Four Possible Outcomes
OUTCOME 1 — CLEAR WINNER
Variant beats Control on conversion AND does not exceed the refund rate ceiling
The new guarantee level lifts conversion at 95% statistical significance AND the variant refund rate is within the pre-defined acceptable range (no more than 50% above the control rate).
Decision: Deploy the variant permanently. File the test record. Update the Product Versioning Changelog (CAT-G: Guarantee Change). Update the Offer Scorecard (D6 — Guarantee Power).
Next action: Schedule the Level+1 test to determine whether an even more aggressive guarantee would produce further lift.
OUTCOME 2 — CONVERSION LIFT BUT REFUND SPIKE
Variant beats Control on conversion BUT exceeds the refund rate ceiling
The new guarantee is attracting buyers who were not previously converting — and those buyers are refunding at a higher rate than existing buyers. This pattern almost always means the guarantee is creating a misalignment between buyer expectation and programme delivery.
Decision: Do NOT deploy permanently. Run the Refund Forensics Protocol (Forensic Audit Loop SOP, Phase 5) to identify the specific expectation gap. Fix the gap — either in the sales copy (reduce the promise), in the delivery (increase the result), or in the guarantee conditions (add a condition that filters the non-implementing buyer) — then retest.
Do not blame the guarantee. Blame the gap between what buyers expected and what they received.
OUTCOME 3 — NO SIGNIFICANT DIFFERENCE
Variant and Control produce statistically equivalent conversion rates
The new guarantee level produced no measurable conversion lift. This is a clean negative result and is valuable data.
Possible diagnosis: The guarantee is not the primary conversion barrier for this offer and audience. The actual barrier may be the mechanism name, the social proof, the copy, or the offer stack — not the risk reversal. Go back to the Offer Scorecard and run dimension-specific diagnostics on D1 (Dream Outcome), D2 (Mechanism Believability), D5 (Offer Stack Strength), and D7 (Social Proof Specificity) before making further guarantee changes.
Do not immediately jump to testing Level+2. A flat test at Level+1 suggests the guarantee level is not the conversion lever for this offer at this stage.
OUTCOME 4 — VARIANT DEPRESSES CONVERSION
Control outperforms Variant
The new guarantee level produced lower conversion than the current guarantee. This is unusual but occurs in specific scenarios: the conditions of a Level 2 guarantee feel onerous or unachievable to a predominantly passive buyer avatar, or the 'double your money back' language at Level 3 triggers scepticism rather than confidence in an audience that has been burned by over-promising operators.
Decision: Retain the Control. Document the result. Diagnose the cause: review the variant's conditions for achievability, review the bold claim for believability, and review the buyer avatar for any signs of deep scepticism based on prior bad experiences in the category. The Objection Bank should already contain entries that explain why stronger guarantees may be triggering distrust rather than confidence for this specific audience.
PHASE 7
The Guarantee Maintenance Cadence
Keeping the guarantee current as the offer, the avatar, and the delivery evolve
Why Guarantees Require Ongoing Maintenance
A guarantee deployed on a 2024 offer is not automatically the right guarantee for the 2026 version of that offer. Three things change over time that affect the optimal guarantee: the delivery infrastructure matures (higher completion rates and result rates justify more aggressive guarantees), the buyer avatar evolves (accumulated social proof and market positioning reduce the need for maximum risk transfer), and competitor guarantees shift the category norm (what felt bold in 2024 may feel standard in 2026).
The Guarantee Review Cadence
Frequency
Activity
Trigger Condition
Output
Quarterly (with Offer Scorecard)
Review D6 (Guarantee Power) score from the Offer Scorecard. If D6 scores 3 or below, initiate a new guarantee test cycle.
Scheduled: first Tuesday of each quarter, as part of the monthly Offer Scorecard session
Updated D6 score. Test cycle initiated if D6 ≤ 3.
After any Major or Minor version change
Review the guarantee for alignment with the updated offer. A new module, a new delivery format, or a changed promise may require a guarantee update.
Product Versioning SOP trigger: any CAT-O, CAT-D, or CAT-M change
Guarantee reviewed for alignment. Updated or confirmed as current.
After any refund rate spike (above 12%)
Run Refund Forensics first to identify root cause. If refund root cause codes show 'result not achieved' above 30%, the guarantee conditions may need to be strengthened (more achievable completion requirements, shorter result timeframe, or clearer result definition).
Weekly Offer Review trigger: Refund Signal Red
Refund Forensics completed. Guarantee reviewed. Conditions updated if indicated.
When a competitor deploys a significantly stronger guarantee
Category guarantee norms shift the buyer's reference point. If the leading competitor in your category upgrades from Level 2 to Level 3, your Level 2 may suddenly feel inadequate by comparison.
GEO/AEO monitoring: quarterly competitor scan
Competitor guarantee benchmarked. Test initiated if gap is significant.
When the Risk Score improves significantly
A substantial improvement in completion rate (R2) or result achievement rate (R4) may now justify testing a higher guarantee level that was previously blocked by the Risk Score ceiling.
Quarterly Risk Score recalculation
Risk Score updated. New maximum testable level confirmed. Test initiated if justified.
Guarantee Version History
Every guarantee change must be logged in the Product Versioning SOP as a CAT-G (Guarantee Change) entry. The full guarantee text at each version must be preserved in the Version Archive for three reasons: legal compliance (buyer entitlement policy), institutional memory (knowing which versions were tested and what they produced), and rollback capability (if a new guarantee increases refunds, the prior version must be restorable exactly).
The Buyer Entitlement Rule for Guarantee Upgrades
When a guarantee is upgraded (e.g., from Level 1 to Level 2, or from 30 days to 60 days), all existing buyers are immediately entitled to the stronger guarantee — retroactively. Do not communicate this proactively unless asked, but if an existing buyer requests a refund under the new terms after a guarantee upgrade, honour it. Withholding a guarantee upgrade from buyers who purchased before the change is both legally questionable and reputationally damaging.
PHASE 8
Special Cases and Edge Scenarios
The situations the standard protocol does not fully cover
Edge Case 1 — Multiple Offer Tiers, One Guarantee Question
When an offer wall has multiple tiers, the guarantee testing protocol applies independently to each tier. The Level 2 guarantee appropriate for a $497 Core Offer may not be appropriate for a $5,000 DWY offer, and vice versa. Run separate tests for each tier. Do not extrapolate from one tier's test result to another.
Value Ladder Tier
Recommended Starting Test Level
Maximum Level Without Additional Risk Scoring
Tripwire ($7–$27)
Level 1 (unconditional, 7–14 days)
Level 1 only — the purchase price is too low for conditional guarantees to be meaningful or enforceable
Frontend / MVO ($47–$497)
Level 1 or Level 2
Level 2 — the purchase justifies conditions; do not attempt Level 3 without a 6-month performance history
Core Offer ($997–$4,997)
Level 2
Level 3 if Risk Score is 15+ and completion rate is above 60%
DWY ($5K–$15K)
Level 2 or Level 3
Level 4 — service completion is appropriate when the operator's effort is the primary result driver
DFY ($10K–$50K)
Level 4 (milestone payment structure)
Level 5 — anti-guarantee is appropriate when the application process is genuinely selective and the reputation backs it
Inner Circle ($25K+)
Level 5
Level 5 only — application-only, no refunds
Edge Case 2 — The Guarantee That Creates the Wrong Buyer
The most dangerous outcome of a guarantee test is not a refund rate spike — it is a completion rate collapse. Some guarantee structures, particularly long unconditional windows (90-day or longer money-back), attract buyers who pay and then immediately begin planning their refund rather than engaging with the content. These buyers consume support resources, generate negative community energy, and refund at near-100% rates regardless of the offer's quality.
Diagnostic signal: completion rate drops significantly (more than 10 percentage points) between the control and the variant, even if refund rates are within bounds. This is the 'passive buyer attraction' problem — the guarantee is selecting for buyers who view the purchase as a risk-free trial rather than a commitment.
Resolution: add an active engagement condition to the guarantee even if it is minimal. A condition that requires completing Module 1 before the guarantee applies filters out passive buyers without meaningfully deterring committed ones. The act of engaging with Module 1 is itself a commitment signal that changes the buyer's relationship to the purchase.
Edge Case 3 — The Guarantee Objection in a Sales Call
Some buyers on discovery calls will probe the guarantee in ways that reveal a deeper trust issue than the guarantee alone can resolve. When a buyer spends more than two minutes on the guarantee in a sales call, the guarantee is a proxy for a deeper concern — usually "I've been burned before" (Trust & Credibility objection) or "I don't trust myself to implement" (Implementation Fear objection).
The correct response is not to over-explain the guarantee. It is to name the underlying fear: "It sounds like the guarantee is important to you — and I want to make sure we're addressing the right thing. Is your concern primarily about whether the method works, or is it more about whether you'll be able to implement it fully?" The answer to that question determines whether to reinforce the result-based guarantee (method fear) or to walk through the Quick Win and accountability structure (implementation fear).
The Guarantee Objection Rule for Sales Calls
Never allow a guarantee conversation to run for more than 3 minutes without asking: 'What would need to be true for you to feel completely confident moving forward, beyond the guarantee?' A buyer who cannot answer that question is not ready to buy regardless of the guarantee level. A buyer who can answer it has just given you the exact objection you need to close.
Edge Case 4 — FTC and Legal Compliance
Guarantee claims in the United States and most other jurisdictions are governed by consumer protection regulations. The FTC has specific requirements for guarantee claims in marketing. This SOP does not provide legal advice, but the following principles reflect standard best practice:
• Every condition stated in the guarantee must be achievable. A condition designed to make the guarantee practically unclaimable is potentially deceptive under FTC guidelines.
• The guarantee terms must be clearly and conspicuously disclosed. 'No fine print' is both a copywriting principle and a legal requirement.
• The claim process must function as described. A guarantee that is advertised but difficult to claim in practice is a violation regardless of the stated terms.
• Double-your-money-back guarantees must be honoured when legitimately claimed. Never deploy a Level 3 guarantee that you are not financially prepared to honour.
• Review all guarantee copy with legal counsel before deploying Level 3 or above, particularly if your market includes consumers in jurisdictions with specific consumer protection requirements (EU, UK, Australia).
Guarantee Test Database — Airtable Schema
All guarantee tests, baseline data, results, and deployment decisions are stored in a dedicated Guarantee Test Records table. Every test generates one record.
Table 1 — Guarantee Test Records
Field
Type
Notes
Test ID
Autonumber
Format: GTR-[Offer Code]-[YYYY-MM]-[Seq]
Offer
Link → Offers table
Test Start Date
Date
Test End Date
Date
When the test reached statistical significance or the minimum duration
Control Guarantee Level
Single select
Level 1 / 2 / 3 / 4 / 5
Control Guarantee Text
Long text
Full verbatim guarantee copy as live during the test
Variant Guarantee Level
Single select
Level 1 / 2 / 3 / 4 / 5
Variant Guarantee Text
Long text
Full verbatim guarantee copy for the variant
Risk Score at Test Start
Number
R1+R2+R3+R4+R5, out of 25
Maximum Testable Level Confirmed
Single select
Level 1 / 2 / 3 / 4 / 5 — from the Risk Score table
RISER Nation | Guarantee Type Testing Protocol SOP | V1.0
word/footer1.xml
Page PAGE of NUMPAGES
word/footnotes.xml
word/endnotes.xml
word/comments.xml
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — GUARANTEE TYPE TESTING PROTOCOL ",
"",
"The Systematic Method for Identifying, Testing, and Deploying the Guarantee That Maximises Conversion Without Destroying Margin",
"Kennedy × Hormozi × Brunson × Cialdini × 2026 Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"The guarantee is the single most underestimated lever in offer design. Most operators treat it as a compliance requirement — the legally necessary 'if you're not happy, get your money back' clause buried at the bottom of a sales page. A guarantee engineered this way does almost nothing for conversion. A guarantee engineered as a strategic risk-transfer instrument can lift conversion rates by 20–60% on the same offer, to the same audience, with zero other changes.",
"",
"The reason most guarantees underperform is not that buyers don't care about risk — they care deeply. It's that the guarantee doesn't address the specific fear the buyer is carrying. A buyer afraid of wasting money is not reassured by a 30-day money-back guarantee. A buyer afraid they won't implement is not reassured by a result-based guarantee they know they won't qualify for. The mismatch between the guarantee's structure and the buyer's actual fear is what kills its conversion power.",
"",
"This SOP defines the five guarantee levels, the five-phase testing protocol that identifies which level maximises conversion for each offer and avatar, the risk-scoring system that determines how aggressive an operator can afford to be, the guarantee language engineering system that makes the guarantee copy as persuasive as the offer itself, the deployment architecture, and the measurement framework that confirms the test result before permanent deployment.",
"",
"Kennedy's Guarantee Principle",
"The guarantee should feel almost reckless to you as the seller. If you're completely comfortable with your guarantee, it is almost certainly not bold enough to move your buyer. The guarantee should make you slightly nervous. That nervousness is the signal that you have transferred enough risk to create a genuine purchase trigger.",
"",
"Hormozi's Risk Transfer Standard",
"Every element of the Value Equation points toward the guarantee: reduce perceived time delay, reduce perceived effort, increase perceived likelihood of achievement. The guarantee addresses all three simultaneously. It says: 'The time you invest is protected. The effort you make is protected. The likelihood of achieving the result is so high that I am willing to guarantee it personally.' A weak guarantee undermines every other element of the offer.",
"",
"Cialdini's Commitment Architecture",
"The guarantee does not just reduce buyer risk — it also increases buyer commitment. A buyer who has explicitly agreed to the conditions of a conditional guarantee (complete the modules, submit the work, attend the calls) has made a public commitment to their own implementation. Cialdini's Commitment & Consistency principle means that buyer is more likely to complete the programme and less likely to refund. Counter-intuitive but empirically consistent: stronger guarantees reduce refund rates in programmes with high completion requirements.",
"",
"The Five Guarantee Levels",
"Every guarantee in any knowledge business sits somewhere on a five-level spectrum from Implied (lowest operator commitment) to Anti-Guarantee (highest selectivity signal). The testing protocol works by identifying which level your current offer is at, building candidate guarantees at Level+1 and Level+2 above your current position, and running structured tests to find the conversion ceiling.",
"",
"GUARANTEED TYPE 01",
"The Unconditional Money-Back",
"LEVEL 1",
"Structure",
"Full refund within a defined window (typically 14–30 days), no questions asked, no conditions to meet, no proof required. The buyer can request a refund for any reason or no reason at all.",
"Bold claim language",
"\"If you're not completely satisfied for any reason within [X] days, we'll refund every cent. No questions. No hassle. No explanation needed.\"",
"Best for",
"Low-ticket offers ($7–$297). First-time buyers with no prior relationship. Commodity-adjacent offers where the primary barrier is scepticism about quality rather than implementation fear. Any offer where the refund window is too short for the buyer to meaningfully implement and then complain.",
"Primary fear it addresses",
"\"What if I don't like it?\" — The fear of being stuck with something that doesn't meet expectations. Primarily a quality scepticism fear rather than an implementation fear.",
"Operator refund exposure",
"Moderate. Refund rate typically 5–15% depending on offer clarity. High-quality delivers with strong onboarding typically achieve below 7%. Refund window is short enough that most buyers who would refund do so before investing significant time.",
"",
"GUARANTEED TYPE 02",
"The Conditional Result-Based",
"LEVEL 2",
"Structure",
"Full refund (or partial refund) if the buyer completes a defined set of actions (modules watched, exercises submitted, calls attended) and does not achieve a specific, measurable result within a defined timeframe.",
"Bold claim language",
"\"Complete all [X] modules, submit your [deliverable], and if you don't achieve [specific result] within [timeframe], we'll refund every cent and you can keep everything.\"",
"Best for",
"Core offers ($497–$4,997). Programmes with defined completion paths and measurable outcomes. Offers where the primary conversion barrier is 'Will this work for me?' rather than pure quality scepticism. Requires clearly defined completion criteria and a measurable result.",
"Primary fear it addresses",
"\"What if I do all the work and still don't get the result?\" — The fear of a wasted investment despite genuine effort. The buyer is willing to do the work but afraid the method itself won't work for their situation.",
"Operator refund exposure",
"Low to moderate when completion requirements are well-designed. Buyers who complete the programme almost never refund — the result-based guarantee primarily attracts and converts buyers who intend to implement. Actual refund claim rate on conditional guarantees typically falls to 1–4%.",
"",
"GUARANTEED TYPE 03",
"The Double-Your-Money-Back",
"LEVEL 3",
"Structure",
"If the buyer completes the defined conditions and does not achieve the stated result, they receive a refund of 2× the purchase price. The operator pays the buyer more than they paid to enter.",
"Bold claim language",
"\"Complete [conditions] and if you don't [result], we'll refund your full investment plus an additional [amount] for your time. You literally cannot lose money by trying.\"",
"Best for",
"Core and high-ticket offers ($997–$10,000) where the operator has extremely high confidence in delivery outcomes. Requires: documented completion rates above 75%, documented result achievement rates above 70%, strong fulfilment infrastructure, and liquid reserves to cover the occasional double refund.",
"Primary fear it addresses",
"\"What if I invest this much and it doesn't work?\" — The acute fear of downside financial loss in high-stakes purchase decisions. Also addresses the 'I've tried things before and been burned' trust objection by demonstrating operator skin-in-the-game at a level no low-confidence seller would offer.",
"Operator refund exposure",
"Very low claim rate if the programme genuinely delivers and completion requirements are achievable. High capital exposure per claim. Should only be deployed after Level 2 testing confirms high completion and result rates. Never deploy without stress-testing the financial exposure at your current buyer volume.",
"",
"GUARANTEED TYPE 04",
"The Service Completion / 'We Work Until It Works'",
"LEVEL 4",
"Structure",
"The operator commits to continuing to work with the buyer, at no additional charge, until the promised result is delivered — regardless of how long that takes beyond the original programme timeline.",
"Bold claim language",
"\"We will work with you, in additional sessions at no cost, until you achieve [specific result]. We do not consider our job done until you get [result]. Period.\"",
"Best for",
"Done-With-You and high-ticket offers ($5,000–$25,000). Programmes with a specific, discrete deliverable that can be confirmed as achieved. Works best when the operator has genuine leverage over the outcome (i.e., the result depends primarily on their expertise and effort, not entirely on the buyer's implementation).",
"Primary fear it addresses",
"\"What if I need more support than the programme includes?\" — The fear of being abandoned before the result is achieved. Particularly powerful for buyers who have paid high prices before and not received the promised support when they needed it.",
"Operator refund exposure",
"Significant ongoing time commitment if buyer does not implement between sessions. Requires strict eligibility criteria (buyer must complete their work between sessions to qualify for additional support). Without criteria, this guarantee can become an indefinite open commitment to non-implementing buyers.",
"",
"GUARANTEED TYPE 05",
"The Anti-Guarantee",
"LEVEL 5",
"Structure",
"No refund offered. Application required to purchase. The selectivity of access IS the guarantee — the operator's willingness to decline applicants signals confidence that accepted buyers will succeed.",
"Bold claim language",
"\"This is not for everyone. We review every application personally. If we accept you, it is because we are confident we can get you the result. That conviction is our guarantee — we only work with people we know we can help.\"",
"Best for",
"Inner Circle, mastermind, and high-selectivity DFY offers ($15,000–$100,000+). Requires: strong social proof, established reputation, a genuine application process, and a track record that makes the exclusivity credible. The anti-guarantee is the most powerful trust signal available — but only when the selectivity is genuine and the reputation backs it.",
"Primary fear it addresses",
"\"Is this operator actually confident in their ability to deliver?\" — At this price point, the fear is not about losing money but about choosing the wrong person to trust with a major business decision. The anti-guarantee signals 'we only take people we know we can help' — which is the highest-confidence statement an operator can make.",
"Operator refund exposure",
"Zero financial refund exposure. Significant reputational exposure if accepted buyers do not achieve results. The anti-guarantee transfers all credibility risk onto the operator's reputation, not their bank account. Should never be used as a way to avoid accountability — only as a genuine signal of selective commitment.",
"",
"",
"PHASE 1",
"The Baseline Guarantee Audit",
"Establishing where you are before deciding where to test",
"",
"The Audit Purpose",
"Before any testing begins, the current guarantee's performance must be established as a documented baseline. Testing without a baseline produces data that cannot be interpreted — you cannot know whether a new guarantee lifted or depressed conversion if you do not know what the current guarantee was producing.",
"",
"The Baseline Data Pull",
"Pull the following data for the prior 60 days minimum before the test begins. If the offer has not yet been live for 60 days, use all available data and note the shorter window in the test record.",
"",
"Metric",
"Data Source",
"Target Baseline",
"Your Baseline",
"Cold conversion rate",
"GA4 + CRM: new buyers ÷ unique cold visitors × 100",
"1.0–2.0% viable range",
"",
"Warm conversion rate",
"Email platform + CRM: new buyers from email ÷ email clicks × 100",
"5–15% viable range",
"",
"Refund rate (rolling 30 days)",
"Stripe: refunds ÷ total sales × 100",
"Below 8% healthy",
"",
"Refund root cause — 'not what I expected'",
"Airtable Refund Records: count of RC codes citing expectation mismatch",
"Below 30% of all refunds",
"",
"Refund root cause — 'didn't get the result'",
"Airtable Refund Records: count of RC codes citing result not achieved",
"Below 20% of all refunds",
"",
"Sales page scroll depth at guarantee section",
"Hotjar: % of visitors who scroll to the guarantee section",
"Above 60% ideally",
"",
"Time spent at guarantee section",
"Hotjar session recordings: average seconds spent at guarantee copy",
"Above 15 seconds = engaged",
"",
"Objection Bank — guarantee-related entries",
"Airtable Objection Bank: count of entries classified as Price & Value or Trust",
"Count",
"",
"Completion rate",
"Course platform: % of buyers who complete the full programme",
"Target: above 45%",
"",
"Current guarantee level",
"1–5 per the Five Guarantee Levels above",
"Note current level",
"",
"",
"The Minimum Viable Test Window",
"Never run a guarantee test on fewer than 200 unique cold visitors per variant OR fewer than 14 days per variant, whichever comes later. Below 200 visitors, conversion rate data is noise. Below 14 days, day-of-week and time-of-day effects distort results. Both thresholds must be met before reading any test result.",
"",
"The Guarantee Weakness Diagnostic",
"Before deciding which guarantee level to test, identify which of four weakness types your current guarantee exhibits. The weakness type determines which test direction has the highest probability of lifting conversion.",
"",
"Weakness Type",
"Diagnostic Signal",
"Test Direction",
"Priority",
"Invisibility Weakness",
"Hotjar shows fewer than 50% of visitors scroll to the guarantee section, OR visitors who do reach it spend fewer than 8 seconds there. The guarantee exists but is not being read.",
"Before testing a new guarantee level: reposition the guarantee higher on the page (above the price reveal or immediately below it). Test placement before testing the guarantee level itself.",
"Fix placement first — a better guarantee nobody reads produces no lift.",
"Language Weakness",
"The guarantee is at the right level (e.g., Level 2) but the copy is flat, legalistic, or corporate. The condition and the bold claim are present but the emotional resonance is absent.",
"Test a rewritten version of the same guarantee level using the Guarantee Copy Engineering system (Phase 4) before upgrading to a higher level. A Level 2 guarantee written powerfully often outperforms a Level 3 guarantee written boringly.",
"High — copy rewrites are free to deploy and take one day to write.",
"Level Weakness",
"Visitors read the guarantee (scroll depth and time-on-section are healthy) but conversion is still below target. The guarantee is seen and understood but not compelling enough.",
"Test the next level up: if current is Level 1, test Level 2. If current is Level 2, test Level 3. Never skip more than one level in a single test.",
"High — this is the primary use case for this SOP.",
"Mismatch Weakness",
"Refund root cause data shows that refund language frequently mentions the guarantee was 'not what was described' or 'conditions were unclear.' The guarantee is generating confusion rather than confidence.",
"Rewrite the conditions in plain language before testing any level change. A confused buyer does not convert. A confused buyer who does convert refunds.",
"Critical — fix clarity before testing level.",
"",
"",
"PHASE 2",
"The Risk Scoring System",
"Determining how aggressive you can afford to be before testing",
"",
"Why Risk Scoring Comes Before Testing",
"A guarantee that lifts conversion by 30% but increases refunds by 400% is not a successful guarantee — it is a business destruction mechanism. The Risk Scoring System establishes the operator's maximum allowable refund exposure before any test is designed, so the test variants are defined within financially viable parameters.",
"",
"The Five Risk Score Inputs",
"Input",
"Calculation",
"Your Score",
"R1 — Current refund rate",
"Pull rolling 30-day refund rate from Stripe. Score: 0–3% = 5 points. 4–6% = 4 points. 7–9% = 3 points. 10–14% = 2 points. 15%+ = 1 point.",
"___",
"R2 — Completion rate",
"Pull completion rate from course platform. Score: 75%+ = 5 points. 60–74% = 4 points. 45–59% = 3 points. 30–44% = 2 points. Below 30% = 1 point.",
"___",
"R3 — Cash reserve coverage",
"How many months of total refund exposure (at current buyer volume × offer price) does your cash reserve cover if every buyer with the new guarantee claimed it? Score: 6+ months = 5 points. 3–5 months = 4 points. 2 months = 3 points. 1 month = 2 points. Less than 1 month = 1 point.",
"___",
"R4 — Result achievement rate",
"Of buyers who complete the programme, what % report achieving the core promised result? Score: 80%+ = 5 points. 65–79% = 4 points. 50–64% = 3 points. 35–49% = 2 points. Below 35% = 1 point. Note: if you do not track this, default to 2 points and add result tracking as an immediate action.",
"___",
"R5 — Fulfilment stress test status",
"Has the Fulfilment Stress Test SOP been completed for this offer? Score: Passed all phases = 5 points. Completed with minor remediation outstanding = 3 points. Not yet completed = 1 point.",
"___",
"TOTAL RISK SCORE",
"Sum of R1 through R5. Maximum: 25 points.",
"___",
"",
"Risk Score → Maximum Testable Guarantee Level",
"Risk Score",
"Maximum Testable Level",
"Rationale",
"20–25 (Low Risk)",
"Level 4 or Level 5",
"Strong delivery foundation, high completion, strong cash reserves. Aggressive guarantees will not destroy the business if the test variant produces an unexpected refund spike.",
"15–19 (Moderate Risk)",
"Level 3",
"Solid fundamentals with some gaps. Can test the Double-Your-Money-Back but should not proceed to Service Completion without closing the specific gaps identified in the lower scores.",
"10–14 (Elevated Risk)",
"Level 2",
"Conditional Result-Based is the appropriate ceiling. Test this level thoroughly before considering Level 3. Address the specific inputs scoring 1 or 2 before retesting.",
"5–9 (High Risk)",
"Level 1 (rewrite only)",
"The delivery infrastructure is not yet strong enough to support a more aggressive guarantee. The test at this score level is a copy rewrite of the current Level 1, not a level upgrade. Address R2 (completion rate) and R4 (result achievement rate) as the primary priorities.",
"Below 5",
"No guarantee test",
"Do not run a guarantee test. The offer has fundamental delivery problems that a stronger guarantee will amplify, not solve. Fix delivery first.",
"",
"The Risk Score Re-Test Rule",
"Any Risk Score input that scores 1 or 2 is a delivery infrastructure gap that must be addressed before running a Level 3 or higher guarantee test. A Level 3 guarantee deployed on an offer with a 25% completion rate will produce a catastrophic refund spike. The guarantee does not fix the offer — it amplifies whatever the offer already is, positive or negative.",
"",
"",
"PHASE 3",
"The Test Design Protocol",
"Building the test variants, defining the success criteria, and setting the kill conditions",
"",
"Test Design Principles",
"One variable only. The guarantee is the only element that changes between the control and the variant. Same headline, same body copy, same stack slide, same price, same CTA. If anything else is different, the test cannot attribute its result to the guarantee.",
"One level at a time. Never jump from Level 1 to Level 3 in a single test. Test sequentially: if Level 2 beats Level 1, then test Level 2 vs Level 3. Skipping levels produces wins that cannot be explained and losses that cannot be diagnosed.",
"Statistical significance before declaration. A test result is not a result until it reaches 95% statistical significance. A conversion rate difference of 0.2 percentage points on 50 visitors is noise, not signal.",
"Measure all three metrics. Every guarantee test measures conversion rate AND refund rate AND completion rate. A guarantee that lifts conversion but doubles refunds is not a win.",
"",
"The Test Variant Construction",
"Every guarantee test has exactly two variants: the Control (current guarantee) and the Variant (new guarantee level). Both variants must have their guarantee section written to the same standard of copy quality — do not test a well-written control against a poorly written variant or vice versa.",
"",
"Test Element",
"Control",
"Variant",
"Rules",
"Guarantee level",
"Current level (document exactly)",
"Current level + 1 step (never skip)",
"Both written at equal copy quality",
"Conditions (if applicable)",
"Existing conditions exactly as live",
"New conditions for the higher level — specific, achievable, and written in plain language",
"Conditions must be completable by a buyer who implements at average pace",
"Bold claim",
"Existing bold claim language",
"New bold claim for the higher level",
"Must match the level — a Level 3 bold claim on a Level 2 structure is misleading",
"Placement on page",
"Current placement",
"Identical placement",
"Never change placement between control and variant — confounds the test",
"Visual treatment",
"Current visual (if any)",
"Identical visual treatment",
"Same font size, same surrounding white space, same section heading",
"Risk reversal symbol",
"If a shield or badge is used in control",
"Identical symbol in variant",
"Visual consistency required",
"",
"The Pre-Test Checklist",
"☐ Baseline metrics documented in Airtable Guarantee Test Record (see Phase 8 schema)",
"☐ Risk Score calculated — maximum testable level confirmed",
"☐ Variant guarantee copy written to Level+1 standard using Phase 4 engineering system",
"☐ Variant conditions reviewed for clarity and achievability — could an average buyer meet these?",
"☐ A/B test tool configured (Convert.com, VWO, or equivalent) — 50/50 split confirmed",
"☐ Conversion goal configured in the test tool (purchase event via Stripe webhook or equivalent)",
"☐ Refund tracking mechanism confirmed — new refunds from test period can be tagged to control vs variant",
"☐ Minimum visitor threshold confirmed: 200 unique cold visitors per variant required before reading",
"☐ Minimum duration threshold confirmed: 14 days minimum per variant regardless of visitor volume",
"☐ Kill condition defined: if variant refund rate exceeds control refund rate by 200% or more at any point, the test is paused and the variant is reviewed",
"",
"Success Criteria Definition",
"Define success criteria before the test begins. Do not define them after seeing results — post-hoc success criteria are not success criteria, they are rationalisations.",
"",
"Metric",
"Minimum Lift to Declare Variant a Winner",
"Maximum Acceptable Change to Deploy Permanently",
"Cold conversion rate",
"Variant must exceed control by a minimum of 0.3 percentage points at 95% statistical significance",
"N/A — higher conversion is always directionally positive",
"Warm conversion rate",
"Variant must exceed control by a minimum of 1.0 percentage point at 95% statistical significance",
"N/A — higher conversion is always directionally positive",
"Refund rate",
"Variant refund rate must not exceed control refund rate by more than 50% (e.g. if control is 6%, variant ceiling is 9%)",
"Hard ceiling: if variant refund rate exceeds 15% at any point during the test, pause and review immediately",
"Completion rate",
"Variant completion rate must not fall more than 5 percentage points below control (stronger guarantees sometimes attract buyers who are less committed to implementation)",
"If completion rate drops more than 10 percentage points, the guarantee is attracting wrong-fit buyers — review avatar targeting before deploying",
"",
"",
"PHASE 4",
"The Guarantee Copy Engineering System",
"Writing guarantee language that functions as the most powerful sentence in the offer",
"",
"Why Guarantee Copy Is Underestimated",
"Most operators treat the guarantee as a legal disclosure. They write it in the passive voice, use corporate language, and bury it beneath a wall of conditions. A guarantee written this way does not move buyers — it satisfies legal counsel and nothing else.",
"",
"The guarantee copy is the single piece of copy on a sales page where you, the operator, are speaking in your own voice about your own confidence in your delivery. It is the moment the buyer either believes you or does not. Every word in the guarantee section should be doing persuasive work.",
"",
"The Five Copy Elements of a High-Performance Guarantee",
"Element",
"Purpose",
"Weak Version",
"Strong Version",
"The Bold Claim",
"The headline of the guarantee section. Must state the protection in its most powerful form — not the conditions, not the fine print, the core protection.",
"\"30-Day Money-Back Guarantee\"",
"\"You Either Get [Specific Result] or You Get Your Money Back. Full Stop.\"",
"The Confidence Statement",
"One sentence in the operator's voice stating WHY they can make this guarantee. Must be specific — not 'because I believe in my product' but because of verifiable evidence.",
"\"I'm so confident you'll love this programme.\"",
"\"In the last 18 months, 94% of buyers who completed all four modules reported [specific result]. That rate is why I can make this guarantee and sleep comfortably.\"",
"The Conditions (if Level 2+)",
"The specific, plain-language actions required to qualify for the guarantee. Must be achievable by an average buyer, specific enough to verify, and stated without legal jargon.",
"\"You must have completed all programme materials and attempted to apply the methods before requesting a refund.\"",
"\"Watch all four modules (each is under 60 minutes). Submit your completed offer stack worksheet. Attend at least one live Q&A call. If you do all three and don't have [specific result], email us for a full refund.\"",
"The Claim Process",
"Exactly how a buyer claims the guarantee. Removes the fear that the refund process will be difficult or ignored.",
"\"Contact our support team.\"",
"\"Email [specific address] with 'Refund Request' in the subject line. Include your worksheet submission. We process all requests within 2 business days. No back-and-forth, no interrogation.\"",
"The Risk Reversal Summary",
"A one-sentence summary that reframes the guarantee in terms of what the buyer cannot lose. The emotional close of the guarantee section.",
"\"So there's really no risk.\"",
"\"The only way you lose is if you do all the work and somehow don't get [result] — and in that case, you get every cent back. Either way, you win.\"",
"",
"Level-by-Level Copy Templates",
"",
"Level 1: Unconditional Money-Back Copy Template",
"Level 1 Template",
"BOLD CLAIM: Your Investment Is Fully Protected for [X] Days.",
"",
"Try the entire programme for [X] days. Watch every module. Use every template. Attend every live session. If at any point during that window you decide this isn't for you — for any reason or no reason — email [address] and we'll refund every cent within 48 hours. No forms to fill out. No justification required. No hard feelings.",
"",
"Why can I offer this? Because our average buyer completes [Module 1] within [48 hours] and reports [specific early result]. I know what happens when someone genuinely engages with this material. That knowledge is what makes this guarantee easy to offer.",
"",
"Either you get [result] or you get your money back. That is the only outcome available to you.",
"",
"Level 2: Conditional Result-Based Copy Template",
"Level 2 Template",
"BOLD CLAIM: Get [Specific Result] or Get Your Money Back. Guaranteed.",
"",
"Here is my commitment to you: complete all [X] modules, submit your [specific deliverable], and attend at least [X] of the [X] live calls. Do those three things and if you have not achieved [specific, measurable result] within [timeframe], I will refund your full investment. Every cent.",
"",
"I can make this commitment because [specific evidence: e.g., 'In our last three cohorts, every buyer who completed all three requirements achieved [result]. Not most. Every one.']. The conditions exist not to create a barrier to refunds but to create a commitment to implementation — because implementation is the only thing standing between you and the result.",
"",
"If you do the work, you get the result. If you do the work and somehow don't get the result, you get your money back. You cannot lose if you implement.",
"",
"Level 3: Double-Your-Money-Back Copy Template",
"Level 3 Template",
"BOLD CLAIM: Complete the Programme, Don't Get [Result], and We'll Pay You [2× Price].",
"",
"This is not a standard guarantee. Complete [specific conditions]. If you meet those conditions and do not have [specific result] by [date], we will refund your full [price] investment and send you an additional [matching amount] as compensation for your time. You walk away with [2× price] for doing everything right and not getting the outcome.",
"",
"Why would I offer this? Because in [X] cohorts, with [X] total buyers, [X]% of buyers who completed all conditions achieved [result]. I am not offering this guarantee to be generous — I am offering it because the risk of paying it out is genuinely small. The few buyers who might claim it are the cost of doing business with absolute confidence.",
"",
"If this guarantee makes you feel safer, good. If it makes you wonder whether this is real, call us. We will walk you through exactly what it means and exactly how it would work if you needed to claim it.",
"",
"Level 4: Service Completion Copy Template",
"Level 4 Template",
"BOLD CLAIM: We Work With You Until You Get [Result]. No Time Limit. No Extra Charge.",
"",
"When you join [programme name], we commit to one outcome: you achieving [specific result]. If the standard programme timeline ends and you have implemented fully but have not yet reached [result], we will continue working with you in additional [session type] at no charge until you get there.",
"",
"What 'fully implemented' means: [specific criteria]. We are not offering endless hand-holding for non-implementation. We are offering a commitment that our work together does not end until the job is done.",
"",
"We make this commitment because [specific evidence of completion and results]. Our obligation to you does not end at the last session date. It ends when you have [result].",
"",
"Level 5: Anti-Guarantee Copy Template",
"Level 5 Template",
"We Do Not Offer a Standard Refund Policy.",
"",
"Every applicant to [programme name] goes through a personal review process. We read every application. We speak with every candidate. We decline applicants we don't believe we can help, and we accept only those we are confident can achieve [result] with our support.",
"",
"That selectivity is our guarantee. We do not offer a money-back policy because we do not accept buyers we are not certain we can serve. If we accept you, it means we have reviewed your situation and committed our reputation to your outcome.",
"",
"The people we decline are not worse people or lesser operators — they are simply not the right fit for this specific programme at this specific time. We would rather refer you to the right resource than take your money knowing we cannot deliver.",
"",
"If that level of confidence and selectivity is not what you are looking for in a programme, we are not the right fit. If it is — apply.",
"",
"",
"PHASE 5",
"The Deployment Architecture",
"Where the guarantee appears, how it is presented, and what surrounds it",
"",
"Guarantee Placement Strategy",
"The guarantee must appear in multiple locations across the buyer's journey — not once at the bottom of a sales page. Each placement serves a different function in the conversion sequence.",
"",
"Placement Location",
"Function",
"Copy Length",
"Recommended Position",
"Sales page — above the fold (referenced)",
"Creates an immediate awareness that a guarantee exists. Reduces the scepticism the buyer carries into the page.",
"One line: 'See our [X]-day guarantee below.'",
"Within the first 3 paragraphs or in the hero section",
"Sales page — after the price reveal",
"The primary conversion moment. Directly addresses the risk that was just triggered by seeing the price.",
"Full guarantee section: all five copy elements in sequence",
"Immediately below the price and payment options",
"Sales page — FAQ section",
"Addresses the guarantee-specific objections that the primary section may not have fully answered.",
"Q&A format: 3–5 specific guarantee questions answered in plain language",
"FAQ section — guarantee questions should be among the top 3 FAQ entries",
"Email sequence — Day 11 (Objection Handling)",
"Specifically addresses price and trust objections via the guarantee. Buyers who did not convert from the sales page often convert from a guarantee-focused email.",
"Medium length: one paragraph per guarantee copy element. Lead with the bold claim as the subject line.",
"Day 11 of the 14-day nurture sequence",
"Sales call — after price is introduced",
"Verbal reinforcement of the guarantee to reduce the risk associated with a large verbal commitment. Must match the written guarantee exactly.",
"One paragraph summary, spoken naturally. Provide a written one-pager if the buyer wants to share with a partner.",
"After price is stated, before asking for a decision",
"Checkout page",
"Last-moment reinforcement for buyers who have reached checkout and are experiencing purchase anxiety.",
"One sentence plus the bold claim. Do not repeat the full conditions at this stage.",
"Directly above the payment button",
"Post-purchase email (Day 0)",
"Confirmation that the guarantee applies. Reduces buyer's remorse and refund request rate in the first 24 hours.",
"One paragraph referencing the guarantee terms and how to claim if needed.",
"Within the first welcome email, after the access instructions",
"",
"The Guarantee Visual Architecture",
"The visual presentation of the guarantee section on the sales page significantly affects both scroll-stop and time-on-section metrics. These design principles apply regardless of which level is being tested.",
"",
"Use a distinct visual container — a coloured box, a border, or a distinct background — to signal that the guarantee section is different from body copy. Buyers scan for it specifically.",
"The bold claim should be in the largest font on the guarantee section — larger than the subheadings above and below it. It is the headline of this section.",
"If a shield, checkmark, or guarantee badge graphic is used: keep it simple, professional, and small. A large generic stock-art shield undermines credibility. The copy does the heavy lifting, not the graphic.",
"The conditions (Level 2+) should be in a checklist format — not a wall of prose. Buyers scan conditions; they do not read them like a contract. Scannable conditions feel transparent, not restrictive.",
"The claim process should be in a single sentence with the specific email address hyperlinked. Nothing signals bad faith faster than a vague refund claim process.",
"",
"",
"PHASE 6",
"Reading the Test Result",
"Interpreting what the data says and making the deployment decision",
"",
"The Four Possible Outcomes",
"",
"OUTCOME 1 — CLEAR WINNER",
"Variant beats Control on conversion AND does not exceed the refund rate ceiling",
"The new guarantee level lifts conversion at 95% statistical significance AND the variant refund rate is within the pre-defined acceptable range (no more than 50% above the control rate).",
"",
"Decision: Deploy the variant permanently. File the test record. Update the Product Versioning Changelog (CAT-G: Guarantee Change). Update the Offer Scorecard (D6 — Guarantee Power).",
"",
"Next action: Schedule the Level+1 test to determine whether an even more aggressive guarantee would produce further lift.",
"",
"OUTCOME 2 — CONVERSION LIFT BUT REFUND SPIKE",
"Variant beats Control on conversion BUT exceeds the refund rate ceiling",
"The new guarantee is attracting buyers who were not previously converting — and those buyers are refunding at a higher rate than existing buyers. This pattern almost always means the guarantee is creating a misalignment between buyer expectation and programme delivery.",
"",
"Decision: Do NOT deploy permanently. Run the Refund Forensics Protocol (Forensic Audit Loop SOP, Phase 5) to identify the specific expectation gap. Fix the gap — either in the sales copy (reduce the promise), in the delivery (increase the result), or in the guarantee conditions (add a condition that filters the non-implementing buyer) — then retest.",
"",
"Do not blame the guarantee. Blame the gap between what buyers expected and what they received.",
"",
"OUTCOME 3 — NO SIGNIFICANT DIFFERENCE",
"Variant and Control produce statistically equivalent conversion rates",
"The new guarantee level produced no measurable conversion lift. This is a clean negative result and is valuable data.",
"",
"Possible diagnosis: The guarantee is not the primary conversion barrier for this offer and audience. The actual barrier may be the mechanism name, the social proof, the copy, or the offer stack — not the risk reversal. Go back to the Offer Scorecard and run dimension-specific diagnostics on D1 (Dream Outcome), D2 (Mechanism Believability), D5 (Offer Stack Strength), and D7 (Social Proof Specificity) before making further guarantee changes.",
"",
"Do not immediately jump to testing Level+2. A flat test at Level+1 suggests the guarantee level is not the conversion lever for this offer at this stage.",
"",
"OUTCOME 4 — VARIANT DEPRESSES CONVERSION",
"Control outperforms Variant",
"The new guarantee level produced lower conversion than the current guarantee. This is unusual but occurs in specific scenarios: the conditions of a Level 2 guarantee feel onerous or unachievable to a predominantly passive buyer avatar, or the 'double your money back' language at Level 3 triggers scepticism rather than confidence in an audience that has been burned by over-promising operators.",
"",
"Decision: Retain the Control. Document the result. Diagnose the cause: review the variant's conditions for achievability, review the bold claim for believability, and review the buyer avatar for any signs of deep scepticism based on prior bad experiences in the category. The Objection Bank should already contain entries that explain why stronger guarantees may be triggering distrust rather than confidence for this specific audience.",
"",
"",
"PHASE 7",
"The Guarantee Maintenance Cadence",
"Keeping the guarantee current as the offer, the avatar, and the delivery evolve",
"",
"Why Guarantees Require Ongoing Maintenance",
"A guarantee deployed on a 2024 offer is not automatically the right guarantee for the 2026 version of that offer. Three things change over time that affect the optimal guarantee: the delivery infrastructure matures (higher completion rates and result rates justify more aggressive guarantees), the buyer avatar evolves (accumulated social proof and market positioning reduce the need for maximum risk transfer), and competitor guarantees shift the category norm (what felt bold in 2024 may feel standard in 2026).",
"",
"The Guarantee Review Cadence",
"Frequency",
"Activity",
"Trigger Condition",
"Output",
"Quarterly (with Offer Scorecard)",
"Review D6 (Guarantee Power) score from the Offer Scorecard. If D6 scores 3 or below, initiate a new guarantee test cycle.",
"Scheduled: first Tuesday of each quarter, as part of the monthly Offer Scorecard session",
"Updated D6 score. Test cycle initiated if D6 ≤ 3.",
"After any Major or Minor version change",
"Review the guarantee for alignment with the updated offer. A new module, a new delivery format, or a changed promise may require a guarantee update.",
"Product Versioning SOP trigger: any CAT-O, CAT-D, or CAT-M change",
"Guarantee reviewed for alignment. Updated or confirmed as current.",
"After any refund rate spike (above 12%)",
"Run Refund Forensics first to identify root cause. If refund root cause codes show 'result not achieved' above 30%, the guarantee conditions may need to be strengthened (more achievable completion requirements, shorter result timeframe, or clearer result definition).",
"Weekly Offer Review trigger: Refund Signal Red",
"Refund Forensics completed. Guarantee reviewed. Conditions updated if indicated.",
"When a competitor deploys a significantly stronger guarantee",
"Category guarantee norms shift the buyer's reference point. If the leading competitor in your category upgrades from Level 2 to Level 3, your Level 2 may suddenly feel inadequate by comparison.",
"GEO/AEO monitoring: quarterly competitor scan",
"Competitor guarantee benchmarked. Test initiated if gap is significant.",
"When the Risk Score improves significantly",
"A substantial improvement in completion rate (R2) or result achievement rate (R4) may now justify testing a higher guarantee level that was previously blocked by the Risk Score ceiling.",
"Quarterly Risk Score recalculation",
"Risk Score updated. New maximum testable level confirmed. Test initiated if justified.",
"",
"Guarantee Version History",
"Every guarantee change must be logged in the Product Versioning SOP as a CAT-G (Guarantee Change) entry. The full guarantee text at each version must be preserved in the Version Archive for three reasons: legal compliance (buyer entitlement policy), institutional memory (knowing which versions were tested and what they produced), and rollback capability (if a new guarantee increases refunds, the prior version must be restorable exactly).",
"",
"The Buyer Entitlement Rule for Guarantee Upgrades",
"When a guarantee is upgraded (e.g., from Level 1 to Level 2, or from 30 days to 60 days), all existing buyers are immediately entitled to the stronger guarantee — retroactively. Do not communicate this proactively unless asked, but if an existing buyer requests a refund under the new terms after a guarantee upgrade, honour it. Withholding a guarantee upgrade from buyers who purchased before the change is both legally questionable and reputationally damaging.",
"",
"",
"PHASE 8",
"Special Cases and Edge Scenarios",
"The situations the standard protocol does not fully cover",
"",
"Edge Case 1 — Multiple Offer Tiers, One Guarantee Question",
"When an offer wall has multiple tiers, the guarantee testing protocol applies independently to each tier. The Level 2 guarantee appropriate for a $497 Core Offer may not be appropriate for a $5,000 DWY offer, and vice versa. Run separate tests for each tier. Do not extrapolate from one tier's test result to another.",
"",
"Value Ladder Tier",
"Recommended Starting Test Level",
"Maximum Level Without Additional Risk Scoring",
"Tripwire ($7–$27)",
"Level 1 (unconditional, 7–14 days)",
"Level 1 only — the purchase price is too low for conditional guarantees to be meaningful or enforceable",
"Frontend / MVO ($47–$497)",
"Level 1 or Level 2",
"Level 2 — the purchase justifies conditions; do not attempt Level 3 without a 6-month performance history",
"Core Offer ($997–$4,997)",
"Level 2",
"Level 3 if Risk Score is 15+ and completion rate is above 60%",
"DWY ($5K–$15K)",
"Level 2 or Level 3",
"Level 4 — service completion is appropriate when the operator's effort is the primary result driver",
"DFY ($10K–$50K)",
"Level 4 (milestone payment structure)",
"Level 5 — anti-guarantee is appropriate when the application process is genuinely selective and the reputation backs it",
"Inner Circle ($25K+)",
"Level 5",
"Level 5 only — application-only, no refunds",
"",
"Edge Case 2 — The Guarantee That Creates the Wrong Buyer",
"The most dangerous outcome of a guarantee test is not a refund rate spike — it is a completion rate collapse. Some guarantee structures, particularly long unconditional windows (90-day or longer money-back), attract buyers who pay and then immediately begin planning their refund rather than engaging with the content. These buyers consume support resources, generate negative community energy, and refund at near-100% rates regardless of the offer's quality.",
"",
"Diagnostic signal: completion rate drops significantly (more than 10 percentage points) between the control and the variant, even if refund rates are within bounds. This is the 'passive buyer attraction' problem — the guarantee is selecting for buyers who view the purchase as a risk-free trial rather than a commitment.",
"",
"Resolution: add an active engagement condition to the guarantee even if it is minimal. A condition that requires completing Module 1 before the guarantee applies filters out passive buyers without meaningfully deterring committed ones. The act of engaging with Module 1 is itself a commitment signal that changes the buyer's relationship to the purchase.",
"",
"Edge Case 3 — The Guarantee Objection in a Sales Call",
"Some buyers on discovery calls will probe the guarantee in ways that reveal a deeper trust issue than the guarantee alone can resolve. When a buyer spends more than two minutes on the guarantee in a sales call, the guarantee is a proxy for a deeper concern — usually \"I've been burned before\" (Trust & Credibility objection) or \"I don't trust myself to implement\" (Implementation Fear objection).",
"",
"The correct response is not to over-explain the guarantee. It is to name the underlying fear: \"It sounds like the guarantee is important to you — and I want to make sure we're addressing the right thing. Is your concern primarily about whether the method works, or is it more about whether you'll be able to implement it fully?\" The answer to that question determines whether to reinforce the result-based guarantee (method fear) or to walk through the Quick Win and accountability structure (implementation fear).",
"",
"The Guarantee Objection Rule for Sales Calls",
"Never allow a guarantee conversation to run for more than 3 minutes without asking: 'What would need to be true for you to feel completely confident moving forward, beyond the guarantee?' A buyer who cannot answer that question is not ready to buy regardless of the guarantee level. A buyer who can answer it has just given you the exact objection you need to close.",
"",
"Edge Case 4 — FTC and Legal Compliance",
"Guarantee claims in the United States and most other jurisdictions are governed by consumer protection regulations. The FTC has specific requirements for guarantee claims in marketing. This SOP does not provide legal advice, but the following principles reflect standard best practice:",
"",
"Every condition stated in the guarantee must be achievable. A condition designed to make the guarantee practically unclaimable is potentially deceptive under FTC guidelines.",
"The guarantee terms must be clearly and conspicuously disclosed. 'No fine print' is both a copywriting principle and a legal requirement.",
"The claim process must function as described. A guarantee that is advertised but difficult to claim in practice is a violation regardless of the stated terms.",
"Double-your-money-back guarantees must be honoured when legitimately claimed. Never deploy a Level 3 guarantee that you are not financially prepared to honour.",
"Review all guarantee copy with legal counsel before deploying Level 3 or above, particularly if your market includes consumers in jurisdictions with specific consumer protection requirements (EU, UK, Australia).",
"",
"",
"Guarantee Test Database — Airtable Schema",
"All guarantee tests, baseline data, results, and deployment decisions are stored in a dedicated Guarantee Test Records table. Every test generates one record.",
"",
"Table 1 — Guarantee Test Records",
"Field",
"Type",
"Notes",
"Test ID",
"Autonumber",
"Format: GTR-[Offer Code]-[YYYY-MM]-[Seq]",
"Offer",
"Link → Offers table",
"",
"Test Start Date",
"Date",
"",
"Test End Date",
"Date",
"When the test reached statistical significance or the minimum duration",
"Control Guarantee Level",
"Single select",
"Level 1 / 2 / 3 / 4 / 5",
"Control Guarantee Text",
"Long text",
"Full verbatim guarantee copy as live during the test",
"Variant Guarantee Level",
"Single select",
"Level 1 / 2 / 3 / 4 / 5",
"Variant Guarantee Text",
"Long text",
"Full verbatim guarantee copy for the variant",
"Risk Score at Test Start",
"Number",
"R1+R2+R3+R4+R5, out of 25",
"Maximum Testable Level Confirmed",
"Single select",
"Level 1 / 2 / 3 / 4 / 5 — from the Risk Score table",
"Baseline Cold Conversion Rate",
"Number",
"% from prior 60 days",
"Baseline Warm Conversion Rate",
"Number",
"% from prior 60 days",
"Baseline Refund Rate",
"Number",
"% from prior 30 days",
"Baseline Completion Rate",
"Number",
"% from prior cohort",
"Control Cold Conversion (test period)",
"Number",
"% during the test",
"Variant Cold Conversion (test period)",
"Number",
"% during the test",
"Control Refund Rate (test period)",
"Number",
"% during the test",
"Variant Refund Rate (test period)",
"Number",
"% during the test",
"Control Completion Rate (test period)",
"Number",
"% during the test",
"Variant Completion Rate (test period)",
"Number",
"% during the test",
"Unique Visitors — Control",
"Number",
"Total during test period",
"Unique Visitors — Variant",
"Number",
"Total during test period",
"Statistical Significance Reached",
"Checkbox",
"Was 95% confidence reached?",
"Test Outcome",
"Single select",
"Clear Winner / Conversion Lift + Refund Spike / No Significant Difference / Variant Depressed Conversion",
"Deployment Decision",
"Single select",
"Deploy Variant / Retain Control / Diagnose and Retest / Escalate to Forensic Audit",
"Deployment Date (if deployed)",
"Date",
"When the winning variant went live permanently",
"Changelog Entry",
"Link → Changelog Entries",
"CAT-G entry from Product Versioning SOP",
"Next Test Level (if applicable)",
"Single select",
"Level 1 / 2 / 3 / 4 / 5 — what to test next",
"Next Test Scheduled Date",
"Date",
"",
"Notes",
"Long text",
"Any observations, anomalies, or context from the test period",
"",
"",
"Master Guarantee Type Testing Protocol Checklist",
"",
"Phase 1 — Baseline Guarantee Audit",
"☐ Pull all 10 baseline metrics from the data sources listed in Phase 1",
"☐ Identify which of the four Guarantee Weakness types applies to the current offer",
"☐ If Invisibility Weakness: fix placement before testing any level change",
"☐ If Language Weakness: run a copy rewrite test before testing a level upgrade",
"☐ If Mismatch Weakness: rewrite conditions in plain language before any other change",
"☐ Document all baseline data in Airtable Guarantee Test Record before the test begins",
"",
"Phase 2 — Risk Scoring",
"☐ Calculate all five Risk Score inputs (R1 through R5)",
"☐ Sum the total Risk Score and identify the Maximum Testable Level",
"☐ If any input scores 1 or 2: document the gap as a remediation action before testing Level 3 or above",
"☐ Risk Score documented in the test record",
"",
"Phase 3 — Test Design",
"☐ Confirm: one variable only — guarantee is the only change between control and variant",
"☐ Confirm: testing only one level up from current (never skip levels)",
"☐ Write variant guarantee copy to the same quality standard as the control using Phase 4 templates",
"☐ Define success criteria before the test begins — document in Airtable test record",
"☐ Configure A/B test tool with 50/50 split and conversion goal tracking",
"☐ Set up variant-specific refund tagging in Stripe or CRM",
"☐ Confirm minimum thresholds: 200 unique cold visitors per variant AND 14 days minimum",
"☐ Define kill condition: if variant refund rate exceeds control by 200%, pause immediately",
"☐ Complete pre-test checklist in Airtable before activating the test",
"",
"Phase 4 — Guarantee Copy Engineering",
"☐ Write Bold Claim for the variant guarantee level using the template for that level",
"☐ Write Confidence Statement with specific evidence (completion rate, result rate, or testimonial data)",
"☐ Write Conditions (Level 2+) in plain language, checklist format, and confirm each is achievable by an average buyer",
"☐ Write Claim Process with specific email address and response timeframe",
"☐ Write Risk Reversal Summary as the emotional close of the section",
"☐ Peer review: read the guarantee copy to one avatar-matched individual. Can they explain it in one sentence after one reading?",
"",
"Phase 5 — Deployment Architecture",
"☐ Guarantee placed in all seven required locations (sales page above fold reference, after price, FAQ, email Day 11, sales call script, checkout, post-purchase email)",
"☐ Visual treatment applied: distinct container, bold claim in largest font, conditions in checklist format",
"☐ Claim process includes specific email address (not 'contact support')",
"",
"Phase 6 — Reading the Result",
"☐ Statistical significance reached: 95% confidence confirmed before declaring a winner",
"☐ All three metrics reviewed: conversion rate, refund rate, completion rate",
"☐ Outcome classified as one of four types: Clear Winner / Lift+Spike / No Difference / Depressed",
"☐ Deployment decision documented in Airtable test record",
"☐ If deploying: Product Versioning Changelog updated (CAT-G entry filed)",
"☐ If deploying: Offer Scorecard D6 (Guarantee Power) updated at next monthly session",
"☐ If refund spike: Refund Forensics Protocol initiated before any further guarantee changes",
"",
"Phase 7 — Maintenance Cadence",
"☐ Guarantee reviewed quarterly as part of the Offer Scorecard D6 scoring",
"☐ Guarantee reviewed after any CAT-O, CAT-D, or CAT-M version change",
"☐ Risk Score recalculated quarterly — maximum testable level updated if inputs have improved",
"☐ Competitor guarantee benchmark completed quarterly as part of the AEO/GEO monitoring review",
"☐ All guarantee changes logged in Product Versioning Changelog (CAT-G)",
"☐ Prior guarantee copy archived in Version Archive Document for legal and rollback purposes",
"",
"",
"",
"RISER Nation Master Operating System | Guarantee Type Testing Protocol SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson × Cialdini | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | Guarantee Type Testing Protocol SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
},
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Explain, test and maintain the method behind your offer
Give the buyer a clear explanation of how it works
Imagine a buyer hearing a course title but still being unable to explain what they will do. A named method can help organize that explanation. The name should represent actual steps and evidence, not substitute for them. This is an illustrative teaching situation, not a reported customer result.
The source connects mechanism naming with Brunson’s offer explanations and Kennedy’s naming approach. Read its attributed principles and ambition below as source claims, not independently authenticated quotations or established results.
Brunson's Mechanism Principle People do not buy your offer. They buy the mechanism — the named proprietary process that makes your promise believable. 'I already know how to get leads' is an objection to a generic offer. 'I've never tried the Forensic Offer Autopsy Method' is not an objection — it is curiosity. The mechanism name eliminates the comparison. You cannot shop-compare a proprietary method.
Kennedy's Naming Imperative Name everything. Your method, your system, your process, your tool. An unnamed method is a commodity. A named method is intellectual property. The name does not need to be clever — it needs to be specific enough that the buyer believes only you teach it, and clear enough that they can repeat it to a friend.
The 10× Standard The target is not a 'better' name. The target is a name that makes the buyer feel 10× more excited about the mechanism than the current name does. That standard prevents incremental changes that do not move conversion metrics. If the new name does not produce meaningfully higher excitement scores than the current name — it is not worth the deployment cost of a rename.
The application across this curriculum is to connect the buyer’s desired outcome, the method, the evidence and the next action. That is consistent with the Brunson and Hormozi themes used in the lessons. A name alone does not establish ownership, exclusivity or effectiveness. The source’s tenfold excitement ambition is not a measured tenfold result: its later tests use a bounded one-to-ten scale and absolute thresholds.
The lesson explains a proposed testing and maintenance process. Source instructions to recruit people, run an AI prompt, rename products, hire help or publish assets remain document content; none is carried out here.
Describe the mechanism before choosing its name
The four-part definition asks what the process is, what it does, why it addresses a problem other approaches miss, and what makes the application distinctive. Read all examples below.
Component
Definition
Weak Version
Strong Version
What it IS
A named, proprietary process — not a product, not a category, not a description
'A marketing system'
'The Forensic Offer Autopsy'
What it DOES
It produces a specific transformation through a specific series of steps — not a vague improvement
'Helps you get more leads'
'Diagnoses and rebuilds a broken offer in 48 hours'
Why it works when alternatives have FAILED
It addresses the root cause that other approaches miss — this is the 'secret' element that creates Epiphany Bridge buy-in
'A better approach to marketing'
'Most offers fail at the promise level, not the traffic level — this fixes the promise'
Why only YOU have it
It is either named, invented, or applied in a way that competitors cannot claim
'Copywriting techniques'
'The Reverse Funnel Method — a proprietary sequencing nobody in this space teaches'
Characteristic
Test
Pass
Fail Examples
Named, not described
Does it have a proper noun — a name — rather than a description?
'The Epiphany Bridge,' 'The Forensic Offer Autopsy'
'A storytelling technique,' 'The way I structure offers'
Curiosity-generating
Does it make an avatar-matched buyer ask 'What is that?'
Yes — without further context, the name implies something they do not yet know
'Content Strategy Framework' — no curiosity. Nothing to ask.
Implies a specific process
Does it suggest there are steps, a sequence, or a system — not just a concept?
'The 5-Phase Revenue Acceleration System' — five phases implies a sequential process
'The Mindset Shift Method' — no process implied. Pure abstraction.
Outcome-adjacent (not outcome-stating)
Does it imply the result without stating it generically?
'The Client Acquisition Accelerator' — implies more clients, faster, without stating 'get more clients'
'The Get More Clients System' — states the generic outcome everyone else promises
Repeatable by the buyer
Can a buyer explain what it is to a friend in one sentence after hearing the name once?
Yes — 'It's a method for auditing and rebuilding your offer — like a forensic investigation of why your offer isn't converting'
'It's the system that... well, it does a lot of things' — buyer cannot encapsulate it
Visually evocative (optional but powerful)
Does it create a mental image or metaphor in the buyer's mind?
'The Epiphany Bridge' — buyer pictures a literal bridge connecting two states
'The Success Framework' — no image, no metaphor
GEO/AEO citable
Is the name specific and brandable enough to be cited by AI engines as the source of a methodology?
Yes — 'The RISER Nation Forensic Offer Autopsy Method' can be cited as a distinct named methodology
'Content strategy' — AI cites every source, not you specifically
The Operator Protocol, The Sovereign Method, The Forensic Critic Positioning
Offers selling authority and expertise — buyer adopts the expert's identity
Named Discovery
The [Named Discovery / Insight]
The Execution Debt Framework, The Bleeding Neck Audit, The Muddled Middle Trap
Offers built on a counterintuitive insight — name creates immediate curiosity
Process Number
The [N]-[Phase/Step/Pillar] [Process Name]
The 5-Phase Revenue Acceleration System, The 3-Step Offer Stack, The 7-Layer Visibility Engine
Buyers who want structure and sequence — the number implies completeness
Metaphor + Container
[Strong Metaphor] + [Container Word]
The Epiphany Bridge, The Flywheel Method, The Content Sovereign System
Buyers who respond to vision and big-picture thinking — the metaphor creates an identity
Enemy / Villain
The [Problem It Kills] Elimination [Container]
The Feast-and-Famine Elimination Protocol, The Churn Termination System
Offers solving a chronic, painful problem — buyer mentally fires the villain when they buy
The seven characteristics address naming, curiosity, process, outcome, repeatability, imagery and potential citation. Visual evocation is labelled optional. Search citations are not guaranteed by specificity. Claims that only one operator can teach a method need actual support.
The eight patterns offer different ways to express the method: diagnosis, reversal, speed, authority, discovery, numbered process, metaphor and problem elimination. Choose a pattern that accurately describes delivery. A fast-sounding name cannot establish a typical delivery time, and a metaphor should still support an understandable explanation.
Monitor five health indicators without assuming a cause
The source checks buyer description, search visibility, response on calls, competitor language and divergence from buyer phrases. Preserve the complete signals and thresholds.
Health Indicator
What It Measures
Data Source
Threshold That Fires the Test
HI-1: Buyer description accuracy
When buyers describe how your offer works to others, do they use your mechanism name — or do they describe it generically?
Exit interview transcripts (question: 'How would you describe how this programme works to a friend?'). Community posts where buyers reference the offer. Referral language in sales call recordings.
If fewer than 3 out of 10 exit interview respondents use the mechanism name (or a close variant) when asked to describe how the programme works — the mechanism name is not sticking.
HI-2: Organic search zero
AI engines and search engines are not returning your mechanism name as an authoritative citation for queries in your niche.
Run the top 10 niche-relevant queries through ChatGPT, Perplexity, and Google. Count how many results cite your mechanism name vs competitor mechanism names.
If zero of your top 10 queries produce a citation of your mechanism name in any AI engine within 90 days of the GEO schema being deployed — the name is not citable enough.
HI-3: Sales call non-response
When the mechanism name is introduced on a sales call or in a sales email, it generates no visible interest or follow-up questions.
Sales call recording review: note buyer's verbal and non-verbal response when the mechanism is named. Email response rate when the mechanism is in the subject line vs when it is not.
If buyers consistently respond to the mechanism name with silence, 'Mm-hmm,' or immediately ask about price — there is no curiosity trigger. The mechanism name is producing no lift.
HI-4: Competitor mechanism adoption
A competitor has adopted similar mechanism language and is gaining visibility with it.
Monthly GEO/AEO citation check. Competitor ad monitoring via Meta Ad Library. Keyword monitoring for your mechanism name in competitor content.
If a competitor's mechanism name appears in AI search results for your core queries more than yours — your name has lost its distinctiveness advantage.
HI-5: Buyer language divergence
The language your buyers use to describe their transformation in exit interviews is significantly different from the language your mechanism name uses.
Compare exit interview language mining data (Phase 3, Forensic Audit Loop SOP) against the words in your current mechanism name.
If zero words in your top 5 buyer language phrases appear in your mechanism name — the name was designed from inside your head, not from buyer intelligence. It needs a rebuild.
These signals prompt investigation. Silence on a call does not prove indifference, and absent citations do not prove the name caused poor visibility. A metaphor may differ from a buyer’s literal words while remaining understandable. Define the query set, engine, date and counting method before comparing search results; the source changes engine lists later.
The three-of-ten buyer-reference threshold is different from the later four-of-five interpretation test and forty-percent adoption measure. They involve different populations and questions.
Phase 1 — Identify the review trigger
The source proposes scheduled quarterly reviews and five event triggers, each with its own timing and response.
Quarter
Timing
Scope
Output
Q1 Review
January — first week
All active mechanism names across all offers. Full 10× Test Protocol run on each.
Q1 Mechanism Health Report. Rename decisions confirmed or declined for each offer.
Q2 Review
April — first week
Same scope as Q1.
Q2 Mechanism Health Report.
Q3 Review
July — first week
Same scope as Q1. Mid-year language mining data from Forensic Audit Loop incorporated.
Q3 Mechanism Health Report. Often the highest-value review because buyer language mining has accumulated a full half-year of data.
Q4 Review
October — first week
Same scope as Q1. Planning review: any mechanism names that need a rename before the January cohort or product launch cycle should be renamed in Q4 so copy assets are fresh at launch.
Q4 Mechanism Health Report. Year-end mechanism name audit complete.
Trigger Event
Source
Action Within
Context
Any Health Indicator reaches threshold (HI-1 through HI-5)
Ongoing monitoring (see Five Health Indicators section)
14 days of threshold being crossed
Run Phase 2 (10× Test) within 14 days. Do not wait for the quarterly cadence.
New buyer language mining data reveals a phrase that is measurably stronger than the current mechanism name
Monthly language mining review (Forensic Audit Loop SOP, Phase 3)
30 days of data confirmation
Run the Phase 4 candidate validation specifically for the new phrase before committing to a full rename cycle.
Competitor adopts identical or near-identical mechanism language
GEO/AEO citation check or Meta Ad Library audit
7 days
Immediate distinctiveness loss. Run Phase 2 with differentiation as the primary criterion. A mechanism name shared with a competitor is worse than no mechanism name.
Offer fails Kill Assessment after one full iteration cycle with no mechanism change
Product Kill Criteria SOP — iterate outcome with mechanism as unchanged variable
Before the next iteration cycle
Before changing any other element of the offer, change the mechanism name. The mechanism is often the cause of a failing offer when all other variables have been iterated without improvement.
Major market shift — new technology, new platform, or new regulatory environment that changes buyer language
If the market has shifted enough that buyers are using fundamentally different language than 6 months ago, the mechanism name may need to reflect the new language landscape.
January, April, July and October review weeks are not exactly every ninety days. A deployment-date-plus-ninety schedule can diverge from that calendar. The event table also allows targeted candidate validation for new language, despite the introduction saying every trigger uses the same full assessment. Preserve those distinctions rather than creating an unrequested schedule.
The instruction to change the mechanism after a failed iteration is a proposed diagnostic choice, not evidence that naming caused the offer’s failure. Examine the underlying method and offer evidence as well.
Phase 2 — Run all five subtests and record the evidence
The source asks for five avatar-matched individuals. Its four eligible groups and exclusions follow.
The 10× Test is run with five individuals who match the target avatar for the offer under review. The test population must be avatar-matched — they should be people who would genuinely consider purchasing the offer. Testing with marketers, colleagues, or people who know you well produces biased scores. The correct population is:
• Existing buyers from prior cohorts who have not heard the current mechanism name discussed in a testing context
• Prospective buyers who are currently in the consideration stage — they have opted into your list, attended a webinar, or engaged with organic content
• Avatar-matched individuals recruited via community engagement who are unfamiliar with your specific mechanism name but fit the target avatar profile exactly
• Podcast listeners or content consumers who match the avatar but have not yet purchased
Who NOT to Test With Do not test with: other operators in your network ('What do you think of this name?'). Your team or VA. Other course creators or marketers who spend time in your ecosystem. These populations are not your buyer — they have domain familiarity that distorts their reaction. A marketer who reads Kennedy and Brunson will score 'The Epiphany Bridge' a 9 because they know what it is. Your actual buyer may score it a 5 because it sounds abstract without context.
Subtest
What Is Measured
Pass
Fail
How to Administer
T-1: Excitement Score
First impression excitement when the name is read aloud for the first time, with no explanation
Average 7.0+ out of 10 across all five testers
Average below 7.0
Read the name once, clearly. Ask: 'On a scale of 1 to 10, how excited does that name make you feel about finding out what it is?' Record without discussion.
T-2: Description Accuracy
Whether the tester's mental model of what the mechanism does matches what it actually does
4 of 5 testers describe the mechanism in a way that matches its actual function
Fewer than 4 of 5 match
After the excitement score, ask: 'What do you imagine this method does based on the name alone?' Record verbatim. Score as Match / Partial Match / Mismatch against the actual mechanism description.
T-3: Curiosity Trigger
Whether the name generates genuine desire to learn more — not just polite interest
4 of 5 testers ask a follow-up question OR say a variant of 'I want to know what that is'
Fewer than 4 of 5 produce a genuine follow-up or curiosity statement
After description, observe and note any spontaneous follow-up questions. Do not prompt. If after 15 seconds there is no follow-up, ask 'Do you want to know more about how it works?' and record their energy level (1=flat, 5=genuine interest).
T-4: Memorability
Whether the tester can accurately recall the mechanism name 10 minutes later
4 of 5 testers recall the name correctly (exact or within one word) after 10 minutes
Fewer than 4 of 5 recall correctly
After completing T-1/T-2/T-3 and 10 minutes of unrelated conversation: 'Can you recall the name of the method we discussed earlier?' Record verbatim. Score: Exact / Close / Approximate / Incorrect.
T-5: Distinctiveness
Whether the name sounds proprietary and unique — not like a commodity label the tester has heard before
4 of 5 testers confirm they have not heard this specific name used to describe a methodology before
3 or more testers say it sounds familiar or like something they've heard from other sources
After memorability check: 'Have you heard this name used to describe a method or system before?' and 'Does this name sound like something other people also use or more like something this specific person invented?' Record both answers.
Five people can provide useful qualitative reactions, but their scores do not establish market-wide conversion effects. Existing buyers may already recognize the name. Reusing the same people for later candidates introduces familiarity and order effects that a short break does not eliminate.
The excitement threshold is seven for the current name; the deployment gate later requires seven and a half. Description scoring does not explain whether a partial match counts. Curiosity administration changes from spontaneous observation to a prompted question without defining how energy becomes the final count. Memorability categories also need a consistent mapping to exact or within-one-word recall.
The distinctiveness table requires four unique responses to pass but lists three familiar responses to fail, leaving exactly two familiar responses unresolved there. The scorecard is stricter: four or more unique passes, otherwise fails. Record the discrepancy before using the rule.
Use the full scorecard and three-outcome table below; do not replace tester responses with only an average.
List specific subtests and which testers produced the fail scores
Key verbatim phrases from testers (any that are interesting)
Rename triggered?
Yes / No
Result
Condition
Decision
Priority
PASS — No rename needed
All 5 subtests pass their respective thresholds
Current mechanism name is performing at the 10× standard. No action required until next quarterly test.
Schedule next test for 90 days. Log passing scores in Airtable.
CONDITIONAL — Targeted improvement
4 of 5 subtests pass. One specific weakness identified.
Run Phase 3 (Name Generation) specifically targeting the failing dimension. The new name does not require a full rename — it may require a one-word adjustment.
Run within 30 days. Single-dimension fix rather than full rebuild.
FAIL — Rename triggered
3 or fewer subtests pass
Full rename cycle initiated. Run Phases 3, 4, 5, 6, 7 in sequence.
Immediate. Full rename cycle to be completed within 60 days.
All five passing requires the source’s thresholds, while a single failing dimension leads to targeted work. Three or fewer passes starts the proposed rename cycle. A passing seven-point score does not prove tenfold improvement over a prior name, and the deployment gate must still be considered.
Phase 3 — Generate candidates from six different directions
The source asks for at least ten names at first, then fifteen or more. Its generation principle and examples follow. Keep buyer phrases traceable to real evidence rather than inventing customer testimony.
Kennedy's 25-Headline Rule Applied to Mechanisms Kennedy's instruction to write 25 headlines before evaluating any of them applies directly to mechanism name generation. The first 5 candidates are the obvious ones — the names that come to mind immediately because they are already close to the current name. Candidates 6 through 10 require real creative effort. Candidates 11 through 15 are often where the genuinely distinct and powerful name appears. Generate 15. Evaluate 5. Deploy 1.
Method 1: turn the buyer’s pain into a process
The pain-inversion examples connect acute or chronic phrases with a possible diagnostic or problem-solving name. They are source illustrations, not newly collected buyer data.
Buyer Pain Phrase
Pain Type
Mechanism Name Derived
Pattern Used
'I keep spinning my wheels building things that don't sell'
PAIN-CHRONIC
The Anti-Wheel-Spin Validation System
Enemy/Villain
'I have no idea if my offer is the problem or my traffic'
PAIN-ACUTE
The Offer/Traffic Diagnostic Separation Method
Forensic/Diagnostic
'Every course I buy tells me what to do but not why it's not working'
PAIN-CHRONIC
The Forensic Offer Autopsy — Root Cause Identification
Forensic/Diagnostic
'I've been stuck at the same revenue for 9 months'
PAIN-ACUTE
The Revenue Plateau Elimination Protocol
Enemy/Villain
'My funnel converts cold but I can't scale it'
PAIN-ACUTE
The Cold-to-Scale Conversion Architecture
Process Number/Structure
Method 2: describe the transformation as a metaphor
Start with the before and after state, then test whether the metaphor helps someone understand the steps. The complete example follows, including the paragraph missing from the connected readable export.
Method 2 — Transformation Visualization
Describe the exact before state and after state of the buyer's journey through the mechanism. Draw or write the metaphor of that journey. What physical process, natural phenomenon, or human activity does it most closely resemble? The metaphor becomes the name.
• Before state → After state: 'Spinning wheels with no market data' → 'Validated offer selling within 30 days'
• Physical metaphor: A forensic scientist arriving at a crime scene, not starting with theories but with evidence. The methodology does what a forensic scientist does — gathers physical evidence before drawing any conclusions.
– Mechanism candidate from metaphor: 'The Forensic Offer Autopsy' / 'The Evidence-First Offer Diagnosis' / 'The Market Crime Scene Investigation'
Method 3: distinguish the approach from competitor language
The source suggests moving away from crowded terms. Some examples still use Funnel with Reverse or Anti, so the contrast can concern the approach rather than literal word removal.
Competitor's Dominant Language
Category Saturation
Counter-Position Direction
Candidate Name
'Marketing Funnel' / 'Sales Funnel'
Extremely high — every operator uses 'funnel'
Process that works backwards, or process that eliminates the need for a funnel
'The Reverse Funnel Method' / 'The Anti-Funnel Revenue Protocol'
'Content Strategy' / 'Content Framework'
Very high — commoditised language
Name the specific mechanism of what content does, not what it is
'The Sovereign Content Flywheel' / 'The Attention Architecture Method'
'Offer Optimisation' / 'Offer Improvement'
High
Name it as a diagnostic/forensic process rather than an optimization
'The Offer Forensics Protocol' / 'The Offer Autopsy & Rebuild Method'
Method 4: use a supportable time reference
The speed exercise below explicitly warns against invented timelines. The fastest motivated buyer’s time is not automatically representative of the audience.
Method 4 — The Speed Compression Test
Identify the fastest a buyer could realistically go from starting the mechanism to achieving the core result. Then build the mechanism name around that time window. Speed-implied names produce the highest T-1 excitement scores for crisis and entry-point buyers.
• 'If a disciplined buyer executed this methodology with full focus — what is the minimum time to the first measurable result?'
• That time window becomes part of the mechanism name: '48-Hour Offer Rebuild Protocol', 'The 7-Day Market Validation Sprint', 'The 14-Day Pipeline Reset Method'
• Warning: do not manufacture speed. The time stated in the mechanism name must be achievable by a motivated buyer. Overstating speed creates expectation mismatch and Negative Avatar Archetype 03 (Too-Late-for-the-Promise buyers).
Method 5: name the underlying insight
The authority exercise asks what insight explains the method. Its claim that competitors cannot use an insight without citing its author is not established by naming it.
Method 5 — The Authority Claim
Name the mechanism after the underlying insight, research base, or authority source that makes it work. This pattern is most effective when there is a genuine research foundation or a counterintuitive insight that separates the methodology from conventional advice.
• What is the one insight that makes this mechanism work when other approaches fail? Name the insight.
• Examples: 'The Execution Debt Framework' (names the insight that buyers know the problem and solution but lack execution capacity). 'The Bleeding Neck Audit' (names the triage insight that only urgent, expensive problems convert). 'The Muddled Middle Elimination Method' (names the pricing insight).
– These names have the highest T-5 distinctiveness scores because they are built on a named insight that cannot be claimed by competitors without explicitly citing you.
Method 6: preserve the AI prompt as a reusable source template
The prompt requires offer, avatar, transformation, buyer phrase, approach and competitor inputs. It asks for ten names and four pieces of information for each. It is preserved in full below and is not executed.
AI Name Generation Prompt You are a direct-response copywriter specialising in mechanism names for expert-led programmes. I need 10 mechanism name candidates for the following:Offer: [Offer Name]Target Avatar: [One-sentence avatar description]Core transformation: [Before state → After state in one sentence]Primary pain phrase (verbatim from buyer): '[PAIN-ACUTE phrase from language mining]'Approach type: [Forensic / Speed / Authority / Metaphor / Enemy — choose the approach not yet represented in my current candidates]Competitor language to avoid: [List 5 dominant competitor terms]For each name: provide (1) the name, (2) a one-sentence mechanism statement using it, (3) which of the 7 characteristics it best fulfils, and (4) its likely weakness.Output 10 names. Do not repeat patterns. Do not use the word 'system' or 'framework' in any of the 10 names.
The prompt excludes System and Framework even though earlier examples use them; that restriction belongs to this prompt. Ten outputs without repeated patterns also needs interpretation when the catalog contains eight patterns and the input list gives five approach options.
The source says eight-to-ten human candidates plus the strongest three AI suggestions rounds out fifteen or more. That totals eleven-to-thirteen. Generate enough genuinely distinct candidates to satisfy a chosen rule; do not claim the arithmetic already reaches fifteen.
Phase 4 — Screen the shortlist and preserve missing scoring rules
The four screening criteria concern conflicts, generic language, description mismatch and pronunciation or recall.
Shortlist Criterion
Disqualifier (remove from list if true)
Refine If Partially True
Trademark / naming conflict
A quick Google search returns results where the exact name is already in active commercial use by a competitor in your niche
If a close variant exists but not the exact name — add one word to differentiate
Commodity language
The name contains words used by more than 50% of operators in the niche — 'system,' 'strategy,' 'framework,' 'method' are borderline; 'content,' 'marketing,' 'lead generation' alone are disqualifiers
Replace generic words with specific words: 'System' → 'Protocol'; 'Strategy' → 'Architecture'; 'Framework' → 'Autopsy'
Description mismatch — pre-test
A team member or close colleague who matches the avatar, upon hearing the name for the first time, describes something completely different from what the mechanism does
Reframe or rename before testing with the full population
Unpronounceable or unmemorable
The name is longer than 7 words, contains a word that is difficult to pronounce or spell, or creates a clumsy acronym
Cut to under 5 words. Remove the offending word. Test memorability informally before full test.
Running the 10× Test on Candidates
Test the top 5 shortlisted candidates with the same five testers used in Phase 2. Present each candidate in isolation — do not show the full list of 5. The tester should react to each name as if it were the only candidate.
Present candidate 1 to all five testers. Run T-1 (excitement), T-3 (curiosity only — skip description and memorability for efficiency). Record.
After a minimum 5-minute break for each tester, present candidate 2. Same process.
Continue for all 5 candidates. Maintain at least 5 minutes between each candidate to reduce carry-over bias.
After all 5 candidates are presented: ask each tester to rank their top 2 in order of preference. Record rankings.
Select the candidate with the highest combined excitement score AND at least 3 of 5 first-preference rankings. If two candidates tie: run T-4 (memorability) as a tiebreaker.
Candidate Name
T-1 Average(1–10)
T-3 Score(out of 5)
First-Preference Rankings(out of 5 testers)
Combined Score
Proceed?
[Candidate 1]
Yes / No
[Candidate 2]
Yes / No
[Candidate 3]
Yes / No
[Candidate 4]
Yes / No
[Candidate 5]
Yes / No
WINNER
A quick search and adding one word do not establish naming clearance. The commodity-percentage criterion lacks a defined sample. More than seven words is the listed disqualifier, while under five is refinement advice; five-to-seven is not treated consistently as an automatic failure.
The abbreviated candidate screen uses excitement and curiosity, plus memorability for a tie. It does not collect all the evidence required by the next gate. The comparison form has a Combined Score column without a formula. The winner rule also requires three first preferences but does not resolve no-majority cases or disagreement between the highest score and preference leader. Do not invent weights to conceal these gaps.
Phase 5 — Check the three gates and communication scope
Before a proposed deployment, the source requires a stronger excitement score plus all five subtests, a clear one-sentence explanation, and an achievable asset plan.
Gate
Question
Required Answer
If Not Cleared
Gate 1 — Score threshold
Does the winning candidate score average 7.5+ on T-1 across all five testers AND pass T-2, T-3, T-4, T-5?
Yes to both — 7.5+ average AND all five subtests pass for the winner
Do not rename. The winner is not yet strong enough. Run another generation cycle (Phase 3) targeting the specific failing subtest.
Gate 2 — Mechanism statement completeness
Can you write a single, clear mechanism statement for the new name — in one sentence — that describes what it is, how it works, and why it produces the result?
Yes — the mechanism statement is written, reviewed, and confirmed in under 30 seconds by an avatar-matched individual
Do not rename. A name you cannot write a mechanism statement for is a name the buyer cannot understand. Refine until the statement is natural.
Gate 3 — Deployment viability
Is the full deployment (all assets listed in Phase 6) achievable within 30 days with the current team?
Yes — deployment plan is mapped, owners are assigned, and completion is confirmed as feasible
Decide: delay rename until capacity exists, or hire short-term to complete deployment. Do not partially deploy — a partially renamed offer produces version drift (see Product Versioning SOP).
Rename Scenario
Announce to Existing Buyers?
Communication Approach
Minor rename — same methodology, new name. The mechanism does the same thing, described more powerfully.
No — existing buyers do not need to know the name changed. Update assets silently.
No communication. Update product versioning record as a Minor change (CAT-M).
Significant rename — same methodology, the new name implies a meaningfully different approach or emphasis.
Yes — optional but recommended. A brief, genuine note about why the name evolved.
One email: 'You may have heard me refer to [method] as [old name]. I've renamed it [new name] because [specific reason from buyer language data]. Same methodology — better description of what it actually does.'
Major rename — the methodology itself has evolved and the new name reflects genuinely different positioning or scope.
Yes — required. This is a product versioning change.
Follow the Major version buyer communication protocol from the Product Versioning SOP.
Collect the missing description, recall and distinctiveness evidence for the winning candidate before calling the full-test gate passed. A one-sentence statement should explain what the method is, how it works and why it produces the result, with claims supported by actual delivery evidence.
The thirty-day deployment-capacity gate differs from the sixty-day full-cycle target and the later measurement windows extending through day 127. The source does not define which endpoint counts as cycle completion. Minor, significant and major announcements are examples of communication scope, not messages sent by this lesson. Category and version-level choices must also be reconciled with the versioning companion.
Phase 6 — Account for every deployment asset
The source demands simultaneous completion, then labels the first tier Deploy First. Read that conflict alongside all thirty-two checks in five tiers: seven conversion, seven delivery, eight search, five partner and five record checks.
The Deployment Rule The new mechanism name goes live everywhere simultaneously — or not at all. The day the sales page is updated is the day every email sequence, every ad, every affiliate swipe copy, every community reference, every schema markup, and every GEO asset is also updated. No phased deployments. No 'we'll update the ads next week.' Complete or wait.
The Complete Mechanism Rename Deployment Checklist
Every asset below must be updated on or before the deployment date. Assign one owner and one deadline to the entire checklist — not individual deadlines per item. Either the whole checklist is complete or the deployment date moves.
☐ Sales page: mechanism section headline, mechanism description paragraph, all mentions of the old name throughout
☐ Sales page: the Mechanism Repeatability Test box or 'How it works' section
☐ VSL or video sales letter script: all verbal references to the mechanism name
☐ Offer stack slide: mechanism name if it appears in the stack
☐ 14-day email sequence: Days 8, 9, and 10 (mechanism introduction emails) — headline, body copy, and mechanism statement
☐ All active ad creatives: any ad that names or references the mechanism
☐ All active ad copy: body copy, CTA copy that references the mechanism
Tier 2 — Course Platform and Delivery Assets
☐ Course platform: programme title if it includes the mechanism name
☐ Course platform: module descriptions that reference the mechanism
☐ Course platform: welcome video script or intro video that names the mechanism
☐ Onboarding email sequence: any email that introduces the mechanism to new buyers
☐ Community welcome message and pinned posts that reference the mechanism
☐ All worksheets, PDFs, and templates that name the mechanism
☐ Physical materials (if Shock-and-Awe package includes printed reference to mechanism)
Tier 3 — GEO/AEO and Search Assets
☐ Product + Offer Schema JSON-LD: mechanism name in description field
☐ Person + Organization Schema: knowsAbout property — add new mechanism name, retain old name with 'formerly known as' notation for citation continuity
☐ LLMs.txt file: update mechanism name in authority declaration
☐ Pillar article: all occurrences of the old mechanism name
☐ All blog posts referencing the mechanism: update inline with redirect from old name
☐ YouTube video titles and descriptions that name the mechanism
☐ Podcast episode titles and show notes that name the mechanism
Tier 4 — Partner and Community Assets
☐ Affiliate swipe copy: all emails, social captions, and video scripts naming the mechanism
☐ JV partner materials: any co-branded content using the old mechanism name
☐ Guest podcast appearances: update speaker bio and talking points if mechanism is referenced
☐ PR and HARO quote templates: update any quoted reference to the mechanism
☐ Social media bio on all platforms if mechanism name appears
Tier 5 — Records and Archives
☐ Product versioning changelog: new changelog entry filed (CAT-M, MINOR or MAJOR depending on scope)
☐ Mechanism Name Library in Airtable: old name archived, new name activated
☐ Testimonial Version Registry: all testimonials referencing the old name flagged as Version-Specific (Retired)
☐ Buyer Language Mining Database: new mechanism name added as a branded keyword
☐ GEO/AEO keyword schema: new mechanism name added to L0 (Authority Topics) and branded methodology keywords
Preparation order can differ from a coordinated release, but the source does not supply a rollout mechanism or establish control over external partner assets. Updating a video script does not change the recorded video. Printed materials and previously distributed media require their own treatment. Preserve unavailable assets as open requirements.
The instruction to retire every testimonial containing the old name conflicts with the versioning source’s still-valid transformation category. Keep original testimony intact and assess context. The source also retains the former name in some structured data while saying to replace all mentions elsewhere. Historical references and current copy need explicit treatment.
Search markup, LLMs.txt and keyword-library names are source checklist items, not proof of current eligibility, compliance or citations. Actual implementation requires current primary guidance and a URL map; text replacement is not a redirect. No search configuration is deployed here.
Phase 7 — Separate observation windows from proof of causation
Preserve the three complete window definitions and seven-metric record.
Window
Timing
Metrics
Comparison Baseline
Action If No Improvement
7-Day Window
Days 1–7 post-deployment
T-1 excitement scores from any new test population encountered. Email subject line open rate (if mechanism name is in subject). Sales call conversion rate from first call to paid.
Pre-rename baseline from same metrics in the 30 days before deployment
No action — 7 days is insufficient to draw conclusions. Log data. Continue to 30-day window.
30-Day Window
Days 8–37 post-deployment
Cold sales page conversion rate. Warm list conversion rate. Email click-through rate on mechanism introduction emails. Sales call close rate.
30-day pre-rename average for same metrics
If cold conversion is more than 10% below pre-rename baseline: run emergency 10× Test to determine if the new name has a structural problem. Do not immediately rename again — diagnose first.
90-Day Window
Days 38–127 post-deployment
All 30-day metrics above PLUS: AI engine citation rate (does the new mechanism name appear in Perplexity/ChatGPT/Gemini results?). Buyer language adoption rate (are buyers using the new name in exit interviews and testimonials?).
90-day pre-rename average for all metrics
If no improvement at 90 days AND buyer language adoption rate is below 40%: the rename did not land. Schedule the next quarterly test. Do not rush — 90 days is the minimum evaluation window for a mechanism name change.
Metric
Pre-Rename Baseline
7-Day Post
30-Day Post
90-Day Post
Delta (90-day vs baseline)
Cold sales page conversion rate
Warm list conversion rate
Email open rate (mechanism-name subject lines)
Sales call close rate
T-1 Excitement score (new testers, informal)
AI engine citation rate (mechanism name mentioned per 10 queries)
Buyer language adoption (% using name in exit interviews)
The source labels days one-to-seven, eight-to-thirty-seven and thirty-eight-to-127 as seven-, thirty- and ninety-day windows. Those are sequential durations, not reviews on days seven, thirty and ninety. Its later calendar instructions differ. Choose and document the interpretation before collecting operational data.
The final window uses a ninety-day baseline while earlier windows use thirty days. More than ten percent conversion decline means relative change, not ten percentage points. Zero baselines, small counts and traffic mix need treatment. The window specifies email click-through while the record and checklist emphasize opens. Preserve both rather than silently dropping a metric.
The no-improvement-and-low-adoption rule differs from the checklist’s low-adoption-alone rule. A before/after difference is an observation; it does not prove the new name caused it. Search counts likewise require consistent engines, queries and denominators.
Read all five worked renames with the stated thresholds
The three example groups contain five renamed methods. They illustrate the source’s reasoning but do not supply complete participant-level records.
Old Name
Score
New Name
Why It Changed
New Score
The 5-Step Offer Building System
5.1
The Forensic Offer Autopsy Method
'Offer building system' had a 5.1 average excitement score. Testers described it as 'a course about making offers.' The new name scored 7.8 because 'forensic' implies expert diagnosis, 'autopsy' implies finding what killed the conversion rate, and 'method' implies a reproducible process. Testers said: 'I want to know what mine looks like.'
7.8
The Offer Optimization Framework
4.8
The Revenue Leak Diagnostic Protocol
'Optimization framework' failed T-5 distinctiveness (all 5 testers had heard similar language elsewhere). The new name passed all 5 subtests. Key buyer language mined: 'I keep losing money somewhere but I don't know where.' That phrase became the name's metaphor.
7.4
Old Name
Score
New Name
Why It Changed
New Score
The Content Strategy Method
4.2
The Sovereign Content Flywheel
Lowest excitement score in testing — 4.2. Failed T-5 badly (all 5 testers said they had heard similar language from other creators). 'Flywheel' adds a physics metaphor (something that generates momentum and becomes self-sustaining). 'Sovereign' implies ownership and independence from algorithms. Testers' spontaneous follow-up: 'What makes it a flywheel?' — perfect T-3 curiosity trigger.
8.1
The One-to-Many Content System
5.8
The Cornerstone Atomisation Architecture
'One-to-many' scored 5.8 — adequate but not distinctive. Buyer language mining revealed: 'I record one thing and it somehow multiplies.' 'Cornerstone atomisation' captures that exact behaviour. The geological metaphor (breaking a cornerstone into its component elements) scored highest on T-2 description accuracy because testers immediately understood the input/output relationship.
7.6
Old Name
Score
New Name
Why It Changed
New Score
Market Research Method
4.0
The Bleeding Neck Audit
4.0 excitement — the lowest possible failing score. 'Market research' is pure commodity language. Zero distinctiveness, zero curiosity, zero metaphor. Buyer language mining: 'I need to find a problem so painful they'll pay anything to fix it.' 'Bleeding neck' is visceral, specific, and impossible to confuse with any competitor's language. Highest T-3 curiosity trigger in this example set — 5/5 testers asked what it meant.
8.4
The 7.4 example clears the baseline excitement threshold but misses the 7.5 deployment threshold. Calling 4.0 the lowest possible failing score conflicts with the one-to-ten scale. Calling 5.8 adequate conflicts with the seven-point pass rule. The reported gains do not equal tenfold improvement. Keep the examples and their limitations visible together.
Preserve the full twenty-four-field database specification
The table below includes current status, prior name, test results, performance deltas, language references and next review date.
Field
Type
Notes
Record ID
Autonumber
Offer
Link → Offers table
Mechanism Name (current)
Short text
The currently deployed name
Status
Single select
Testing / Active / Retired
Deployed Date
Date
When this name went live
Trigger That Initiated This Cycle
Single select
Quarterly Cadence / HI-1 through HI-5 / Event-Based (specify)
T-1 Excitement Average (deployment test)
Number
Average of 5 testers at time of deployment decision
T-2 Description Accuracy
Number
Out of 5
T-3 Curiosity Trigger
Number
Out of 5
T-4 Memorability
Number
Out of 5
T-5 Distinctiveness
Number
Out of 5
Overall Test Result
Single select
Pass / Conditional / Fail
Mechanism Statement
Long text
The one-sentence HOW statement for this name
Name Pattern Used
Single select
Forensic/Diagnostic / The Reverse / Speed+Object / Authority Method / Named Discovery / Process Number / Metaphor+Container / Enemy/Villain
Prior Mechanism Name
Short text
The name this replaced (for audit trail)
Prior Name Retired Date
Date
7-Day Performance Delta
Number
% change in primary conversion metric vs pre-rename baseline
30-Day Performance Delta
Number
90-Day Performance Delta
Number
AI Citation Rate at 90 Days
Number
Citations per 10 queries across all three AI engines
Buyer Language Adoption Rate at 90 Days
Number
% of exit interview respondents using new name
Linked Changelog Entry
Link → Changelog Entries
The Product Versioning SOP changelog entry for this rename
Linked Language Mining Phrases
Long text
The specific PAIN-ACUTE/PAIN-CHRONIC phrases that informed this name
Next Quarterly Test Date
Date
Deploy Date + 90 days
One current record with a prior-name field and overwritten scores cannot alone preserve every candidate, interview, test, gate and performance record. The source does not define the full historical structure it claims. Linked phrases are described as long text; the next test date needs actual date logic. A schema is not a deployed Airtable database.
Work through the five master-checklist groups
Preserve the original setup, quarterly, rename, thirty-day and ninety-day checks below. They remain requirements to evaluate, not completed operations.
System Setup (One-Time)
☐ Create Mechanism Name Records table in Airtable with all fields from schema above
☐ Document the current mechanism name for every active offer — create one record per offer
☐ Run the 10× Test Protocol (Phase 2) on all current mechanism names as the baseline assessment
☐ File baseline test scores in Airtable — this establishes the before-state for first-cycle comparison
☐ Set quarterly cadence calendar reminders: January, April, July, October — first week of each
Every Quarterly Cadence Trigger
☐ Pull current mechanism name for each active offer from Airtable
☐ Identify test population of 5 avatar-matched individuals per offer
☐ Run all five subtests of the 10× Test Protocol in sequence
☐ Complete the 10× Test Scorecard for each offer
☐ Record test result: Pass / Conditional / Fail
☐ If Pass: update Airtable record with latest test scores. Schedule next quarterly test.
☐ If Conditional: run Phase 3 targeting the specific failing subtest dimension only
☐ If Fail: initiate full rename cycle (Phases 3 through 7)
Every Rename Cycle (Phases 3–7)
☐ Run all six generation methods — minimum 15 candidates total
☐ Apply shortlist criteria — reduce to 5 finalists
Write a proposed mechanism statement for one actual method, then document how each subtest would be administered and scored. Identify evidence gaps and ambiguous rules before suggesting a rename. Use example responses only when clearly labelled; do not represent them as interviews that occurred.
RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING. The historical source footer remains in the original.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — 10× MECHANISM TEST & RENAME CADENCE
The Quarterly Protocol for Testing, Strengthening, and Deploying the Named Method That Sells Your Offer
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
Every offer that converts at scale has one thing in common: a named, proprietary mechanism that the buyer believes is responsible for the transformation. Not a product description. Not a course title. A mechanism — a specific, named process that explains HOW the offer produces the promised result and WHY that process works when other approaches have failed.
The mechanism is the single most leveraged element of your offer. It is the difference between 'a marketing course' and 'The Forensic Offer Autopsy Method.' It is the difference between 'sales training' and 'The Epiphany Bridge.' The same underlying methodology, named poorly, sells at a fraction of the rate it sells when named powerfully. And mechanism names that were powerful at launch become familiar, diluted, and eventually invisible as markets evolve and language shifts.
This SOP defines the 10× Mechanism Test — the structured protocol for evaluating whether a mechanism name is performing at its maximum potential — and the Rename Cadence — the quarterly ritual that keeps your mechanism fresh, distinctive, and maximally compelling across every offer in the value ladder. It covers the anatomy of a great mechanism name, the five health indicators that reveal when a name is underperforming, the trigger system that fires a rename assessment, the test protocol itself, the name generation system, the validation method, the deployment checklist, and the performance measurement framework.
Brunson's Mechanism Principle
People do not buy your offer. They buy the mechanism — the named proprietary process that makes your promise believable. 'I already know how to get leads' is an objection to a generic offer. 'I've never tried the Forensic Offer Autopsy Method' is not an objection — it is curiosity. The mechanism name eliminates the comparison. You cannot shop-compare a proprietary method.
Kennedy's Naming Imperative
Name everything. Your method, your system, your process, your tool. An unnamed method is a commodity. A named method is intellectual property. The name does not need to be clever — it needs to be specific enough that the buyer believes only you teach it, and clear enough that they can repeat it to a friend.
The 10× Standard
The target is not a 'better' name. The target is a name that makes the buyer feel 10× more excited about the mechanism than the current name does. That standard prevents incremental changes that do not move conversion metrics. If the new name does not produce meaningfully higher excitement scores than the current name — it is not worth the deployment cost of a rename.
The Mechanism Anatomy: What Makes a Name Work
Before testing or renaming, the system requires a clear definition of what a strong mechanism name actually is. Most operators confuse mechanism names with product titles, methodology labels, or framework descriptions. A mechanism name is none of those things. It is something more specific and more commercially powerful.
The Four-Part Mechanism Definition
Component
Definition
Weak Version
Strong Version
What it IS
A named, proprietary process — not a product, not a category, not a description
'A marketing system'
'The Forensic Offer Autopsy'
What it DOES
It produces a specific transformation through a specific series of steps — not a vague improvement
'Helps you get more leads'
'Diagnoses and rebuilds a broken offer in 48 hours'
Why it works when alternatives have FAILED
It addresses the root cause that other approaches miss — this is the 'secret' element that creates Epiphany Bridge buy-in
'A better approach to marketing'
'Most offers fail at the promise level, not the traffic level — this fixes the promise'
Why only YOU have it
It is either named, invented, or applied in a way that competitors cannot claim
'Copywriting techniques'
'The Reverse Funnel Method — a proprietary sequencing nobody in this space teaches'
The Seven Characteristics of a High-Performing Mechanism Name
Characteristic
Test
Pass
Fail Examples
Named, not described
Does it have a proper noun — a name — rather than a description?
'The Epiphany Bridge,' 'The Forensic Offer Autopsy'
'A storytelling technique,' 'The way I structure offers'
Curiosity-generating
Does it make an avatar-matched buyer ask 'What is that?'
Yes — without further context, the name implies something they do not yet know
'Content Strategy Framework' — no curiosity. Nothing to ask.
Implies a specific process
Does it suggest there are steps, a sequence, or a system — not just a concept?
'The 5-Phase Revenue Acceleration System' — five phases implies a sequential process
'The Mindset Shift Method' — no process implied. Pure abstraction.
Outcome-adjacent (not outcome-stating)
Does it imply the result without stating it generically?
'The Client Acquisition Accelerator' — implies more clients, faster, without stating 'get more clients'
'The Get More Clients System' — states the generic outcome everyone else promises
Repeatable by the buyer
Can a buyer explain what it is to a friend in one sentence after hearing the name once?
Yes — 'It's a method for auditing and rebuilding your offer — like a forensic investigation of why your offer isn't converting'
'It's the system that... well, it does a lot of things' — buyer cannot encapsulate it
Visually evocative (optional but powerful)
Does it create a mental image or metaphor in the buyer's mind?
'The Epiphany Bridge' — buyer pictures a literal bridge connecting two states
'The Success Framework' — no image, no metaphor
GEO/AEO citable
Is the name specific and brandable enough to be cited by AI engines as the source of a methodology?
Yes — 'The RISER Nation Forensic Offer Autopsy Method' can be cited as a distinct named methodology
'Content strategy' — AI cites every source, not you specifically
The Mechanism Name Patterns
Strong mechanism names almost always follow one of eight proven patterns. The pattern you choose should match the primary emotion your mechanism is designed to trigger — curiosity, authority, speed, specificity, or transformation.
The Operator Protocol, The Sovereign Method, The Forensic Critic Positioning
Offers selling authority and expertise — buyer adopts the expert's identity
Named Discovery
The [Named Discovery / Insight]
The Execution Debt Framework, The Bleeding Neck Audit, The Muddled Middle Trap
Offers built on a counterintuitive insight — name creates immediate curiosity
Process Number
The [N]-[Phase/Step/Pillar] [Process Name]
The 5-Phase Revenue Acceleration System, The 3-Step Offer Stack, The 7-Layer Visibility Engine
Buyers who want structure and sequence — the number implies completeness
Metaphor + Container
[Strong Metaphor] + [Container Word]
The Epiphany Bridge, The Flywheel Method, The Content Sovereign System
Buyers who respond to vision and big-picture thinking — the metaphor creates an identity
Enemy / Villain
The [Problem It Kills] Elimination [Container]
The Feast-and-Famine Elimination Protocol, The Churn Termination System
Offers solving a chronic, painful problem — buyer mentally fires the villain when they buy
The Five Mechanism Health Indicators
Before any formal test is run, five passive signals reveal whether a mechanism name is underperforming in the market. These indicators are monitored continuously and any one of them reaching its threshold fires the 10× Test protocol.
Health Indicator
What It Measures
Data Source
Threshold That Fires the Test
HI-1: Buyer description accuracy
When buyers describe how your offer works to others, do they use your mechanism name — or do they describe it generically?
Exit interview transcripts (question: 'How would you describe how this programme works to a friend?'). Community posts where buyers reference the offer. Referral language in sales call recordings.
If fewer than 3 out of 10 exit interview respondents use the mechanism name (or a close variant) when asked to describe how the programme works — the mechanism name is not sticking.
HI-2: Organic search zero
AI engines and search engines are not returning your mechanism name as an authoritative citation for queries in your niche.
Run the top 10 niche-relevant queries through ChatGPT, Perplexity, and Google. Count how many results cite your mechanism name vs competitor mechanism names.
If zero of your top 10 queries produce a citation of your mechanism name in any AI engine within 90 days of the GEO schema being deployed — the name is not citable enough.
HI-3: Sales call non-response
When the mechanism name is introduced on a sales call or in a sales email, it generates no visible interest or follow-up questions.
Sales call recording review: note buyer's verbal and non-verbal response when the mechanism is named. Email response rate when the mechanism is in the subject line vs when it is not.
If buyers consistently respond to the mechanism name with silence, 'Mm-hmm,' or immediately ask about price — there is no curiosity trigger. The mechanism name is producing no lift.
HI-4: Competitor mechanism adoption
A competitor has adopted similar mechanism language and is gaining visibility with it.
Monthly GEO/AEO citation check. Competitor ad monitoring via Meta Ad Library. Keyword monitoring for your mechanism name in competitor content.
If a competitor's mechanism name appears in AI search results for your core queries more than yours — your name has lost its distinctiveness advantage.
HI-5: Buyer language divergence
The language your buyers use to describe their transformation in exit interviews is significantly different from the language your mechanism name uses.
Compare exit interview language mining data (Phase 3, Forensic Audit Loop SOP) against the words in your current mechanism name.
If zero words in your top 5 buyer language phrases appear in your mechanism name — the name was designed from inside your head, not from buyer intelligence. It needs a rebuild.
PHASE 1
The Trigger System
What fires a 10× Test assessment — scheduled and event-based
The Two Trigger Types
The 10× Test is triggered in two ways: by scheduled cadence (quarterly, regardless of performance) and by event-based signals (when a health indicator crosses its threshold or a specific market event occurs). Both trigger types result in the same assessment — the full 10× Test Protocol in Phase 2.
Scheduled Triggers — The Quarterly Cadence
The quarterly cadence is the baseline commitment of this SOP. The mechanism name for every active offer is reviewed every 90 days — whether or not any health indicators have fired and whether or not any event has occurred. The market changes. Language evolves. AI search citation patterns shift. A mechanism name that was earning a 9/10 excitement score in Q1 may be earning 6.5 by Q3 because competitor language has saturated the category.
Quarter
Timing
Scope
Output
Q1 Review
January — first week
All active mechanism names across all offers. Full 10× Test Protocol run on each.
Q1 Mechanism Health Report. Rename decisions confirmed or declined for each offer.
Q2 Review
April — first week
Same scope as Q1.
Q2 Mechanism Health Report.
Q3 Review
July — first week
Same scope as Q1. Mid-year language mining data from Forensic Audit Loop incorporated.
Q3 Mechanism Health Report. Often the highest-value review because buyer language mining has accumulated a full half-year of data.
Q4 Review
October — first week
Same scope as Q1. Planning review: any mechanism names that need a rename before the January cohort or product launch cycle should be renamed in Q4 so copy assets are fresh at launch.
Q4 Mechanism Health Report. Year-end mechanism name audit complete.
Event-Based Triggers — Immediate Assessment
Trigger Event
Source
Action Within
Context
Any Health Indicator reaches threshold (HI-1 through HI-5)
Ongoing monitoring (see Five Health Indicators section)
14 days of threshold being crossed
Run Phase 2 (10× Test) within 14 days. Do not wait for the quarterly cadence.
New buyer language mining data reveals a phrase that is measurably stronger than the current mechanism name
Monthly language mining review (Forensic Audit Loop SOP, Phase 3)
30 days of data confirmation
Run the Phase 4 candidate validation specifically for the new phrase before committing to a full rename cycle.
Competitor adopts identical or near-identical mechanism language
GEO/AEO citation check or Meta Ad Library audit
7 days
Immediate distinctiveness loss. Run Phase 2 with differentiation as the primary criterion. A mechanism name shared with a competitor is worse than no mechanism name.
Offer fails Kill Assessment after one full iteration cycle with no mechanism change
Product Kill Criteria SOP — iterate outcome with mechanism as unchanged variable
Before the next iteration cycle
Before changing any other element of the offer, change the mechanism name. The mechanism is often the cause of a failing offer when all other variables have been iterated without improvement.
Major market shift — new technology, new platform, or new regulatory environment that changes buyer language
If the market has shifted enough that buyers are using fundamentally different language than 6 months ago, the mechanism name may need to reflect the new language landscape.
PHASE 2
The 10× Test Protocol
The structured assessment that determines whether a rename is necessary
The Test Population
The 10× Test is run with five individuals who match the target avatar for the offer under review. The test population must be avatar-matched — they should be people who would genuinely consider purchasing the offer. Testing with marketers, colleagues, or people who know you well produces biased scores. The correct population is:
• Existing buyers from prior cohorts who have not heard the current mechanism name discussed in a testing context
• Prospective buyers who are currently in the consideration stage — they have opted into your list, attended a webinar, or engaged with organic content
• Avatar-matched individuals recruited via community engagement who are unfamiliar with your specific mechanism name but fit the target avatar profile exactly
• Podcast listeners or content consumers who match the avatar but have not yet purchased
Who NOT to Test With
Do not test with: other operators in your network ('What do you think of this name?'). Your team or VA. Other course creators or marketers who spend time in your ecosystem. These populations are not your buyer — they have domain familiarity that distorts their reaction. A marketer who reads Kennedy and Brunson will score 'The Epiphany Bridge' a 9 because they know what it is. Your actual buyer may score it a 5 because it sounds abstract without context.
The Five Subtests
The 10× Test Protocol comprises five distinct subtests. Each tests a different dimension of the mechanism name's effectiveness. All five are required — not four, not three. A name that passes four and fails one has a specific, diagnosable weakness that should either be fixed or accepted as a known limitation.
Subtest
What Is Measured
Pass
Fail
How to Administer
T-1: Excitement Score
First impression excitement when the name is read aloud for the first time, with no explanation
Average 7.0+ out of 10 across all five testers
Average below 7.0
Read the name once, clearly. Ask: 'On a scale of 1 to 10, how excited does that name make you feel about finding out what it is?' Record without discussion.
T-2: Description Accuracy
Whether the tester's mental model of what the mechanism does matches what it actually does
4 of 5 testers describe the mechanism in a way that matches its actual function
Fewer than 4 of 5 match
After the excitement score, ask: 'What do you imagine this method does based on the name alone?' Record verbatim. Score as Match / Partial Match / Mismatch against the actual mechanism description.
T-3: Curiosity Trigger
Whether the name generates genuine desire to learn more — not just polite interest
4 of 5 testers ask a follow-up question OR say a variant of 'I want to know what that is'
Fewer than 4 of 5 produce a genuine follow-up or curiosity statement
After description, observe and note any spontaneous follow-up questions. Do not prompt. If after 15 seconds there is no follow-up, ask 'Do you want to know more about how it works?' and record their energy level (1=flat, 5=genuine interest).
T-4: Memorability
Whether the tester can accurately recall the mechanism name 10 minutes later
4 of 5 testers recall the name correctly (exact or within one word) after 10 minutes
Fewer than 4 of 5 recall correctly
After completing T-1/T-2/T-3 and 10 minutes of unrelated conversation: 'Can you recall the name of the method we discussed earlier?' Record verbatim. Score: Exact / Close / Approximate / Incorrect.
T-5: Distinctiveness
Whether the name sounds proprietary and unique — not like a commodity label the tester has heard before
4 of 5 testers confirm they have not heard this specific name used to describe a methodology before
3 or more testers say it sounds familiar or like something they've heard from other sources
After memorability check: 'Have you heard this name used to describe a method or system before?' and 'Does this name sound like something other people also use or more like something this specific person invented?' Record both answers.
The 10× Test Scorecard
Complete one scorecard per offer per test. File in Airtable under Mechanism Name Records.
List specific subtests and which testers produced the fail scores
Key verbatim phrases from testers (any that are interesting)
Rename triggered?
Yes / No
Test Result Interpretation
Result
Condition
Decision
Priority
PASS — No rename needed
All 5 subtests pass their respective thresholds
Current mechanism name is performing at the 10× standard. No action required until next quarterly test.
Schedule next test for 90 days. Log passing scores in Airtable.
CONDITIONAL — Targeted improvement
4 of 5 subtests pass. One specific weakness identified.
Run Phase 3 (Name Generation) specifically targeting the failing dimension. The new name does not require a full rename — it may require a one-word adjustment.
Run within 30 days. Single-dimension fix rather than full rebuild.
FAIL — Rename triggered
3 or fewer subtests pass
Full rename cycle initiated. Run Phases 3, 4, 5, 6, 7 in sequence.
Immediate. Full rename cycle to be completed within 60 days.
PHASE 3
The Name Generation System
Producing 10 or more strong candidates before selecting any
The Generation Principle
The first candidate name generated in any rename session is almost never the best one. The best mechanism names consistently emerge from exhaustive generation — after the obvious names have been written down and set aside. The system below requires a minimum of 10 candidates before evaluation begins. Evaluating fewer than 10 candidates produces premature commitment to the path of least resistance rather than the most powerful option.
Kennedy's 25-Headline Rule Applied to Mechanisms
Kennedy's instruction to write 25 headlines before evaluating any of them applies directly to mechanism name generation. The first 5 candidates are the obvious ones — the names that come to mind immediately because they are already close to the current name. Candidates 6 through 10 require real creative effort. Candidates 11 through 15 are often where the genuinely distinct and powerful name appears. Generate 15. Evaluate 5. Deploy 1.
The Six Generation Methods
Run all six methods in sequence. Each method approaches the mechanism from a different angle and produces candidates of a different character. Use the language mining database from the Forensic Audit Loop SOP as your primary input for methods 1 and 2.
Method 1 — Buyer Language Inversion
The strongest mechanism names often come from inverting the buyer's pain language into a process name. Pull the top 5 PAIN-ACUTE and PAIN-CHRONIC phrases from the buyer language mining database. For each phrase, ask: if there were a named method that specifically eliminated this pain, what would it be called?
Buyer Pain Phrase
Pain Type
Mechanism Name Derived
Pattern Used
'I keep spinning my wheels building things that don't sell'
PAIN-CHRONIC
The Anti-Wheel-Spin Validation System
Enemy/Villain
'I have no idea if my offer is the problem or my traffic'
PAIN-ACUTE
The Offer/Traffic Diagnostic Separation Method
Forensic/Diagnostic
'Every course I buy tells me what to do but not why it's not working'
PAIN-CHRONIC
The Forensic Offer Autopsy — Root Cause Identification
Forensic/Diagnostic
'I've been stuck at the same revenue for 9 months'
PAIN-ACUTE
The Revenue Plateau Elimination Protocol
Enemy/Villain
'My funnel converts cold but I can't scale it'
PAIN-ACUTE
The Cold-to-Scale Conversion Architecture
Process Number/Structure
Method 2 — Transformation Visualization
Describe the exact before state and after state of the buyer's journey through the mechanism. Draw or write the metaphor of that journey. What physical process, natural phenomenon, or human activity does it most closely resemble? The metaphor becomes the name.
• Before state → After state: 'Spinning wheels with no market data' → 'Validated offer selling within 30 days'
• Physical metaphor: A forensic scientist arriving at a crime scene, not starting with theories but with evidence. The methodology does what a forensic scientist does — gathers physical evidence before drawing any conclusions.
– Mechanism candidate from metaphor: 'The Forensic Offer Autopsy' / 'The Evidence-First Offer Diagnosis' / 'The Market Crime Scene Investigation'
Method 3 — The Competitor Inversion
Identify the dominant mechanism language in your niche — what terms and names your competitors use most frequently. Then deliberately move in the opposite direction. If everyone says 'funnel,' name something that has nothing to do with funnels. If everyone says 'system,' use a different container word.
Competitor's Dominant Language
Category Saturation
Counter-Position Direction
Candidate Name
'Marketing Funnel' / 'Sales Funnel'
Extremely high — every operator uses 'funnel'
Process that works backwards, or process that eliminates the need for a funnel
'The Reverse Funnel Method' / 'The Anti-Funnel Revenue Protocol'
'Content Strategy' / 'Content Framework'
Very high — commoditised language
Name the specific mechanism of what content does, not what it is
'The Sovereign Content Flywheel' / 'The Attention Architecture Method'
'Offer Optimisation' / 'Offer Improvement'
High
Name it as a diagnostic/forensic process rather than an optimization
'The Offer Forensics Protocol' / 'The Offer Autopsy & Rebuild Method'
Method 4 — The Speed Compression Test
Identify the fastest a buyer could realistically go from starting the mechanism to achieving the core result. Then build the mechanism name around that time window. Speed-implied names produce the highest T-1 excitement scores for crisis and entry-point buyers.
• 'If a disciplined buyer executed this methodology with full focus — what is the minimum time to the first measurable result?'
• That time window becomes part of the mechanism name: '48-Hour Offer Rebuild Protocol', 'The 7-Day Market Validation Sprint', 'The 14-Day Pipeline Reset Method'
• Warning: do not manufacture speed. The time stated in the mechanism name must be achievable by a motivated buyer. Overstating speed creates expectation mismatch and Negative Avatar Archetype 03 (Too-Late-for-the-Promise buyers).
Method 5 — The Authority Claim
Name the mechanism after the underlying insight, research base, or authority source that makes it work. This pattern is most effective when there is a genuine research foundation or a counterintuitive insight that separates the methodology from conventional advice.
• What is the one insight that makes this mechanism work when other approaches fail? Name the insight.
• Examples: 'The Execution Debt Framework' (names the insight that buyers know the problem and solution but lack execution capacity). 'The Bleeding Neck Audit' (names the triage insight that only urgent, expensive problems convert). 'The Muddled Middle Elimination Method' (names the pricing insight).
– These names have the highest T-5 distinctiveness scores because they are built on a named insight that cannot be claimed by competitors without explicitly citing you.
Method 6 — The AI Generation Prompt
After generating 8–10 candidates using Methods 1–5, use the following prompt to generate an additional 10 candidates from an AI. Use the strongest 3 from the AI output to round out the candidate set to 15+.
AI Name Generation Prompt
You are a direct-response copywriter specialising in mechanism names for expert-led programmes. I need 10 mechanism name candidates for the following:Offer: [Offer Name]Target Avatar: [One-sentence avatar description]Core transformation: [Before state → After state in one sentence]Primary pain phrase (verbatim from buyer): '[PAIN-ACUTE phrase from language mining]'Approach type: [Forensic / Speed / Authority / Metaphor / Enemy — choose the approach not yet represented in my current candidates]Competitor language to avoid: [List 5 dominant competitor terms]For each name: provide (1) the name, (2) a one-sentence mechanism statement using it, (3) which of the 7 characteristics it best fulfils, and (4) its likely weakness.Output 10 names. Do not repeat patterns. Do not use the word 'system' or 'framework' in any of the 10 names.
PHASE 4
The Candidate Validation Protocol
Selecting the winner from the generated shortlist
The Shortlist Criteria
After generating 15+ candidates using the six methods, apply the shortlist criteria below to reduce to 5 finalists before running the 10× Test on the candidates. Do not test all 15 — testing fatigue degrades the quality of responses from the test population.
Shortlist Criterion
Disqualifier (remove from list if true)
Refine If Partially True
Trademark / naming conflict
A quick Google search returns results where the exact name is already in active commercial use by a competitor in your niche
If a close variant exists but not the exact name — add one word to differentiate
Commodity language
The name contains words used by more than 50% of operators in the niche — 'system,' 'strategy,' 'framework,' 'method' are borderline; 'content,' 'marketing,' 'lead generation' alone are disqualifiers
Replace generic words with specific words: 'System' → 'Protocol'; 'Strategy' → 'Architecture'; 'Framework' → 'Autopsy'
Description mismatch — pre-test
A team member or close colleague who matches the avatar, upon hearing the name for the first time, describes something completely different from what the mechanism does
Reframe or rename before testing with the full population
Unpronounceable or unmemorable
The name is longer than 7 words, contains a word that is difficult to pronounce or spell, or creates a clumsy acronym
Cut to under 5 words. Remove the offending word. Test memorability informally before full test.
Running the 10× Test on Candidates
Test the top 5 shortlisted candidates with the same five testers used in Phase 2. Present each candidate in isolation — do not show the full list of 5. The tester should react to each name as if it were the only candidate.
1. Present candidate 1 to all five testers. Run T-1 (excitement), T-3 (curiosity only — skip description and memorability for efficiency). Record.
2. After a minimum 5-minute break for each tester, present candidate 2. Same process.
3. Continue for all 5 candidates. Maintain at least 5 minutes between each candidate to reduce carry-over bias.
4. After all 5 candidates are presented: ask each tester to rank their top 2 in order of preference. Record rankings.
5. Select the candidate with the highest combined excitement score AND at least 3 of 5 first-preference rankings. If two candidates tie: run T-4 (memorability) as a tiebreaker.
The Candidate Comparison Scorecard
Candidate Name
T-1 Average(1–10)
T-3 Score(out of 5)
First-Preference Rankings(out of 5 testers)
Combined Score
Proceed?
[Candidate 1]
Yes / No
[Candidate 2]
Yes / No
[Candidate 3]
Yes / No
[Candidate 4]
Yes / No
[Candidate 5]
Yes / No
WINNER
PHASE 5
The Rename Decision Framework
Confirming the rename before any deployment begins
The Three-Gate Confirmation
Before any deployment begins, the rename must clear three confirmation gates. These gates protect against premature deployment of a name that tested well with a small sample but has a structural flaw that would reveal itself at scale.
Gate
Question
Required Answer
If Not Cleared
Gate 1 — Score threshold
Does the winning candidate score average 7.5+ on T-1 across all five testers AND pass T-2, T-3, T-4, T-5?
Yes to both — 7.5+ average AND all five subtests pass for the winner
Do not rename. The winner is not yet strong enough. Run another generation cycle (Phase 3) targeting the specific failing subtest.
Gate 2 — Mechanism statement completeness
Can you write a single, clear mechanism statement for the new name — in one sentence — that describes what it is, how it works, and why it produces the result?
Yes — the mechanism statement is written, reviewed, and confirmed in under 30 seconds by an avatar-matched individual
Do not rename. A name you cannot write a mechanism statement for is a name the buyer cannot understand. Refine until the statement is natural.
Gate 3 — Deployment viability
Is the full deployment (all assets listed in Phase 6) achievable within 30 days with the current team?
Yes — deployment plan is mapped, owners are assigned, and completion is confirmed as feasible
Decide: delay rename until capacity exists, or hire short-term to complete deployment. Do not partially deploy — a partially renamed offer produces version drift (see Product Versioning SOP).
The Rename Announcement Decision
Some renames should be announced to the existing buyer base. Most should not. The decision depends on whether the rename affects the buyer's experience, their ability to reference the offer, or their sense of what they purchased.
Rename Scenario
Announce to Existing Buyers?
Communication Approach
Minor rename — same methodology, new name. The mechanism does the same thing, described more powerfully.
No — existing buyers do not need to know the name changed. Update assets silently.
No communication. Update product versioning record as a Minor change (CAT-M).
Significant rename — same methodology, the new name implies a meaningfully different approach or emphasis.
Yes — optional but recommended. A brief, genuine note about why the name evolved.
One email: 'You may have heard me refer to [method] as [old name]. I've renamed it [new name] because [specific reason from buyer language data]. Same methodology — better description of what it actually does.'
Major rename — the methodology itself has evolved and the new name reflects genuinely different positioning or scope.
Yes — required. This is a product versioning change.
Follow the Major version buyer communication protocol from the Product Versioning SOP.
PHASE 6
The Deployment System
Rolling out the new mechanism name across every asset — completely and correctly
The Non-Negotiable Deployment Completeness Rule
A partial rename is worse than no rename. An offer where some assets use the old name and some use the new name creates confusion for buyers, degrades the mechanism's authority (because it appears the name was changed which implies the old name was inadequate), and produces version drift. The deployment must be complete before the new name is used in any external communication.
The Deployment Rule
The new mechanism name goes live everywhere simultaneously — or not at all. The day the sales page is updated is the day every email sequence, every ad, every affiliate swipe copy, every community reference, every schema markup, and every GEO asset is also updated. No phased deployments. No 'we'll update the ads next week.' Complete or wait.
The Complete Mechanism Rename Deployment Checklist
Every asset below must be updated on or before the deployment date. Assign one owner and one deadline to the entire checklist — not individual deadlines per item. Either the whole checklist is complete or the deployment date moves.
☐ Sales page: mechanism section headline, mechanism description paragraph, all mentions of the old name throughout
☐ Sales page: the Mechanism Repeatability Test box or 'How it works' section
☐ VSL or video sales letter script: all verbal references to the mechanism name
☐ Offer stack slide: mechanism name if it appears in the stack
☐ 14-day email sequence: Days 8, 9, and 10 (mechanism introduction emails) — headline, body copy, and mechanism statement
☐ All active ad creatives: any ad that names or references the mechanism
☐ All active ad copy: body copy, CTA copy that references the mechanism
Tier 2 — Course Platform and Delivery Assets
☐ Course platform: programme title if it includes the mechanism name
☐ Course platform: module descriptions that reference the mechanism
☐ Course platform: welcome video script or intro video that names the mechanism
☐ Onboarding email sequence: any email that introduces the mechanism to new buyers
☐ Community welcome message and pinned posts that reference the mechanism
☐ All worksheets, PDFs, and templates that name the mechanism
☐ Physical materials (if Shock-and-Awe package includes printed reference to mechanism)
Tier 3 — GEO/AEO and Search Assets
☐ Product + Offer Schema JSON-LD: mechanism name in description field
☐ Person + Organization Schema: knowsAbout property — add new mechanism name, retain old name with 'formerly known as' notation for citation continuity
☐ LLMs.txt file: update mechanism name in authority declaration
☐ Pillar article: all occurrences of the old mechanism name
☐ All blog posts referencing the mechanism: update inline with redirect from old name
☐ YouTube video titles and descriptions that name the mechanism
☐ Podcast episode titles and show notes that name the mechanism
Tier 4 — Partner and Community Assets
☐ Affiliate swipe copy: all emails, social captions, and video scripts naming the mechanism
☐ JV partner materials: any co-branded content using the old mechanism name
☐ Guest podcast appearances: update speaker bio and talking points if mechanism is referenced
☐ PR and HARO quote templates: update any quoted reference to the mechanism
☐ Social media bio on all platforms if mechanism name appears
Tier 5 — Records and Archives
☐ Product versioning changelog: new changelog entry filed (CAT-M, MINOR or MAJOR depending on scope)
☐ Mechanism Name Library in Airtable: old name archived, new name activated
☐ Testimonial Version Registry: all testimonials referencing the old name flagged as Version-Specific (Retired)
☐ Buyer Language Mining Database: new mechanism name added as a branded keyword
☐ GEO/AEO keyword schema: new mechanism name added to L0 (Authority Topics) and branded methodology keywords
PHASE 7
Performance Measurement
Proving the rename worked — and building the intelligence for the next cycle
The Three Performance Windows
Every rename is an experiment with a defined outcome: the new mechanism name should produce measurably higher performance than the old name across three measurement windows. If it does not, the rename itself becomes a data point that feeds the next generation cycle.
Window
Timing
Metrics
Comparison Baseline
Action If No Improvement
7-Day Window
Days 1–7 post-deployment
T-1 excitement scores from any new test population encountered. Email subject line open rate (if mechanism name is in subject). Sales call conversion rate from first call to paid.
Pre-rename baseline from same metrics in the 30 days before deployment
No action — 7 days is insufficient to draw conclusions. Log data. Continue to 30-day window.
30-Day Window
Days 8–37 post-deployment
Cold sales page conversion rate. Warm list conversion rate. Email click-through rate on mechanism introduction emails. Sales call close rate.
30-day pre-rename average for same metrics
If cold conversion is more than 10% below pre-rename baseline: run emergency 10× Test to determine if the new name has a structural problem. Do not immediately rename again — diagnose first.
90-Day Window
Days 38–127 post-deployment
All 30-day metrics above PLUS: AI engine citation rate (does the new mechanism name appear in Perplexity/ChatGPT/Gemini results?). Buyer language adoption rate (are buyers using the new name in exit interviews and testimonials?).
90-day pre-rename average for all metrics
If no improvement at 90 days AND buyer language adoption rate is below 40%: the rename did not land. Schedule the next quarterly test. Do not rush — 90 days is the minimum evaluation window for a mechanism name change.
The Rename Performance Record
Complete this record at each measurement window. File in Airtable under Mechanism Name Records, linked to the Changelog entry for the rename.
Metric
Pre-Rename Baseline
7-Day Post
30-Day Post
90-Day Post
Delta (90-day vs baseline)
Cold sales page conversion rate
Warm list conversion rate
Email open rate (mechanism-name subject lines)
Sales call close rate
T-1 Excitement score (new testers, informal)
AI engine citation rate (mechanism name mentioned per 10 queries)
Buyer language adoption (% using name in exit interviews)
Worked Examples: Mechanism Name Evolution
These worked examples show the complete cycle — from a weak mechanism name, through the test process, to a stronger name — with the specific reasoning that drove each transformation. All examples are generalisable to the RISER Nation offer context.
Example 1 — Offer Construction Mechanism
Old Name
Score
New Name
Why It Changed
New Score
The 5-Step Offer Building System
5.1
The Forensic Offer Autopsy Method
'Offer building system' had a 5.1 average excitement score. Testers described it as 'a course about making offers.' The new name scored 7.8 because 'forensic' implies expert diagnosis, 'autopsy' implies finding what killed the conversion rate, and 'method' implies a reproducible process. Testers said: 'I want to know what mine looks like.'
7.8
The Offer Optimization Framework
4.8
The Revenue Leak Diagnostic Protocol
'Optimization framework' failed T-5 distinctiveness (all 5 testers had heard similar language elsewhere). The new name passed all 5 subtests. Key buyer language mined: 'I keep losing money somewhere but I don't know where.' That phrase became the name's metaphor.
7.4
Example 2 — Content Mechanism
Old Name
Score
New Name
Why It Changed
New Score
The Content Strategy Method
4.2
The Sovereign Content Flywheel
Lowest excitement score in testing — 4.2. Failed T-5 badly (all 5 testers said they had heard similar language from other creators). 'Flywheel' adds a physics metaphor (something that generates momentum and becomes self-sustaining). 'Sovereign' implies ownership and independence from algorithms. Testers' spontaneous follow-up: 'What makes it a flywheel?' — perfect T-3 curiosity trigger.
8.1
The One-to-Many Content System
5.8
The Cornerstone Atomisation Architecture
'One-to-many' scored 5.8 — adequate but not distinctive. Buyer language mining revealed: 'I record one thing and it somehow multiplies.' 'Cornerstone atomisation' captures that exact behaviour. The geological metaphor (breaking a cornerstone into its component elements) scored highest on T-2 description accuracy because testers immediately understood the input/output relationship.
7.6
Example 3 — Market Research Mechanism
Old Name
Score
New Name
Why It Changed
New Score
Market Research Method
4.0
The Bleeding Neck Audit
4.0 excitement — the lowest possible failing score. 'Market research' is pure commodity language. Zero distinctiveness, zero curiosity, zero metaphor. Buyer language mining: 'I need to find a problem so painful they'll pay anything to fix it.' 'Bleeding neck' is visceral, specific, and impossible to confuse with any competitor's language. Highest T-3 curiosity trigger in this example set — 5/5 testers asked what it meant.
8.4
The Mechanism Name Library — Airtable Schema
Table 1 — Mechanism Name Records
One record per mechanism per offer. The full history of every mechanism name tested, deployed, and retired.
Field
Type
Notes
Record ID
Autonumber
Offer
Link → Offers table
Mechanism Name (current)
Short text
The currently deployed name
Status
Single select
Testing / Active / Retired
Deployed Date
Date
When this name went live
Trigger That Initiated This Cycle
Single select
Quarterly Cadence / HI-1 through HI-5 / Event-Based (specify)
T-1 Excitement Average (deployment test)
Number
Average of 5 testers at time of deployment decision
T-2 Description Accuracy
Number
Out of 5
T-3 Curiosity Trigger
Number
Out of 5
T-4 Memorability
Number
Out of 5
T-5 Distinctiveness
Number
Out of 5
Overall Test Result
Single select
Pass / Conditional / Fail
Mechanism Statement
Long text
The one-sentence HOW statement for this name
Name Pattern Used
Single select
Forensic/Diagnostic / The Reverse / Speed+Object / Authority Method / Named Discovery / Process Number / Metaphor+Container / Enemy/Villain
Prior Mechanism Name
Short text
The name this replaced (for audit trail)
Prior Name Retired Date
Date
7-Day Performance Delta
Number
% change in primary conversion metric vs pre-rename baseline
30-Day Performance Delta
Number
90-Day Performance Delta
Number
AI Citation Rate at 90 Days
Number
Citations per 10 queries across all three AI engines
Buyer Language Adoption Rate at 90 Days
Number
% of exit interview respondents using new name
Linked Changelog Entry
Link → Changelog Entries
The Product Versioning SOP changelog entry for this rename
Linked Language Mining Phrases
Long text
The specific PAIN-ACUTE/PAIN-CHRONIC phrases that informed this name
Next Quarterly Test Date
Date
Deploy Date + 90 days
Master 10× Mechanism Test & Rename Cadence Checklist
System Setup (One-Time)
☐ Create Mechanism Name Records table in Airtable with all fields from schema above
☐ Document the current mechanism name for every active offer — create one record per offer
☐ Run the 10× Test Protocol (Phase 2) on all current mechanism names as the baseline assessment
☐ File baseline test scores in Airtable — this establishes the before-state for first-cycle comparison
☐ Set quarterly cadence calendar reminders: January, April, July, October — first week of each
Every Quarterly Cadence Trigger
☐ Pull current mechanism name for each active offer from Airtable
☐ Identify test population of 5 avatar-matched individuals per offer
☐ Run all five subtests of the 10× Test Protocol in sequence
☐ Complete the 10× Test Scorecard for each offer
☐ Record test result: Pass / Conditional / Fail
☐ If Pass: update Airtable record with latest test scores. Schedule next quarterly test.
☐ If Conditional: run Phase 3 targeting the specific failing subtest dimension only
☐ If Fail: initiate full rename cycle (Phases 3 through 7)
Every Rename Cycle (Phases 3–7)
☐ Run all six generation methods — minimum 15 candidates total
☐ Apply shortlist criteria — reduce to 5 finalists
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — 10× MECHANISM TEST & RENAME CADENCE ",
"",
"The Quarterly Protocol for Testing, Strengthening, and Deploying the Named Method That Sells Your Offer",
"Kennedy × Hormozi × Brunson × 2026 Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"Every offer that converts at scale has one thing in common: a named, proprietary mechanism that the buyer believes is responsible for the transformation. Not a product description. Not a course title. A mechanism — a specific, named process that explains HOW the offer produces the promised result and WHY that process works when other approaches have failed.",
"",
"The mechanism is the single most leveraged element of your offer. It is the difference between 'a marketing course' and 'The Forensic Offer Autopsy Method.' It is the difference between 'sales training' and 'The Epiphany Bridge.' The same underlying methodology, named poorly, sells at a fraction of the rate it sells when named powerfully. And mechanism names that were powerful at launch become familiar, diluted, and eventually invisible as markets evolve and language shifts.",
"",
"This SOP defines the 10× Mechanism Test — the structured protocol for evaluating whether a mechanism name is performing at its maximum potential — and the Rename Cadence — the quarterly ritual that keeps your mechanism fresh, distinctive, and maximally compelling across every offer in the value ladder. It covers the anatomy of a great mechanism name, the five health indicators that reveal when a name is underperforming, the trigger system that fires a rename assessment, the test protocol itself, the name generation system, the validation method, the deployment checklist, and the performance measurement framework.",
"",
"Brunson's Mechanism Principle",
"People do not buy your offer. They buy the mechanism — the named proprietary process that makes your promise believable. 'I already know how to get leads' is an objection to a generic offer. 'I've never tried the Forensic Offer Autopsy Method' is not an objection — it is curiosity. The mechanism name eliminates the comparison. You cannot shop-compare a proprietary method.",
"",
"Kennedy's Naming Imperative",
"Name everything. Your method, your system, your process, your tool. An unnamed method is a commodity. A named method is intellectual property. The name does not need to be clever — it needs to be specific enough that the buyer believes only you teach it, and clear enough that they can repeat it to a friend.",
"",
"The 10× Standard",
"The target is not a 'better' name. The target is a name that makes the buyer feel 10× more excited about the mechanism than the current name does. That standard prevents incremental changes that do not move conversion metrics. If the new name does not produce meaningfully higher excitement scores than the current name — it is not worth the deployment cost of a rename.",
"",
"The Mechanism Anatomy: What Makes a Name Work",
"Before testing or renaming, the system requires a clear definition of what a strong mechanism name actually is. Most operators confuse mechanism names with product titles, methodology labels, or framework descriptions. A mechanism name is none of those things. It is something more specific and more commercially powerful.",
"",
"The Four-Part Mechanism Definition",
"Component",
"Definition",
"Weak Version",
"Strong Version",
"What it IS",
"A named, proprietary process — not a product, not a category, not a description",
"'A marketing system'",
"'The Forensic Offer Autopsy'",
"What it DOES",
"It produces a specific transformation through a specific series of steps — not a vague improvement",
"'Helps you get more leads'",
"'Diagnoses and rebuilds a broken offer in 48 hours'",
"Why it works when alternatives have FAILED",
"It addresses the root cause that other approaches miss — this is the 'secret' element that creates Epiphany Bridge buy-in",
"'A better approach to marketing'",
"'Most offers fail at the promise level, not the traffic level — this fixes the promise'",
"Why only YOU have it",
"It is either named, invented, or applied in a way that competitors cannot claim",
"'Copywriting techniques'",
"'The Reverse Funnel Method — a proprietary sequencing nobody in this space teaches'",
"",
"The Seven Characteristics of a High-Performing Mechanism Name",
"",
"Characteristic",
"Test",
"Pass",
"Fail Examples",
"Named, not described",
"Does it have a proper noun — a name — rather than a description?",
"'The Epiphany Bridge,' 'The Forensic Offer Autopsy'",
"'A storytelling technique,' 'The way I structure offers'",
"Curiosity-generating",
"Does it make an avatar-matched buyer ask 'What is that?'",
"Yes — without further context, the name implies something they do not yet know",
"'Content Strategy Framework' — no curiosity. Nothing to ask.",
"Implies a specific process",
"Does it suggest there are steps, a sequence, or a system — not just a concept?",
"'The 5-Phase Revenue Acceleration System' — five phases implies a sequential process",
"'The Mindset Shift Method' — no process implied. Pure abstraction.",
"Outcome-adjacent (not outcome-stating)",
"Does it imply the result without stating it generically?",
"'The Client Acquisition Accelerator' — implies more clients, faster, without stating 'get more clients'",
"'The Get More Clients System' — states the generic outcome everyone else promises",
"Repeatable by the buyer",
"Can a buyer explain what it is to a friend in one sentence after hearing the name once?",
"Yes — 'It's a method for auditing and rebuilding your offer — like a forensic investigation of why your offer isn't converting'",
"'It's the system that... well, it does a lot of things' — buyer cannot encapsulate it",
"Visually evocative (optional but powerful)",
"Does it create a mental image or metaphor in the buyer's mind?",
"'The Epiphany Bridge' — buyer pictures a literal bridge connecting two states",
"'The Success Framework' — no image, no metaphor",
"GEO/AEO citable",
"Is the name specific and brandable enough to be cited by AI engines as the source of a methodology?",
"Yes — 'The RISER Nation Forensic Offer Autopsy Method' can be cited as a distinct named methodology",
"'Content strategy' — AI cites every source, not you specifically",
"",
"The Mechanism Name Patterns",
"Strong mechanism names almost always follow one of eight proven patterns. The pattern you choose should match the primary emotion your mechanism is designed to trigger — curiosity, authority, speed, specificity, or transformation.",
"",
"Pattern",
"Structure",
"Examples",
"Best For",
"Forensic / Diagnostic",
"[Investigation verb] + [Subject] + [Container]",
"Forensic Offer Autopsy, Revenue Leak Diagnostic, Pipeline Forensics",
"Offers that fix broken things — the name implies expert investigation",
"The Reverse",
"The Reverse + [Common Approach]",
"The Reverse Funnel Method, The Reverse Launch, The Reverse Avatar Build",
"Offers that challenge conventional wisdom — the name implies a contrarian insight",
"Speed + Object",
"[Time/Speed] + [Transformation Object] + [Container]",
"48-Hour Offer Rebuild, 30-Day Pipeline Ignition, 7-Day Content Accelerator",
"Crisis stacks, entry-point offers, urgency-driven buyers",
"The [Authority Figure] Method",
"The + [Implied Expert] + Method / Protocol",
"The Operator Protocol, The Sovereign Method, The Forensic Critic Positioning",
"Offers selling authority and expertise — buyer adopts the expert's identity",
"Named Discovery",
"The [Named Discovery / Insight]",
"The Execution Debt Framework, The Bleeding Neck Audit, The Muddled Middle Trap",
"Offers built on a counterintuitive insight — name creates immediate curiosity",
"Process Number",
"The [N]-[Phase/Step/Pillar] [Process Name]",
"The 5-Phase Revenue Acceleration System, The 3-Step Offer Stack, The 7-Layer Visibility Engine",
"Buyers who want structure and sequence — the number implies completeness",
"Metaphor + Container",
"[Strong Metaphor] + [Container Word]",
"The Epiphany Bridge, The Flywheel Method, The Content Sovereign System",
"Buyers who respond to vision and big-picture thinking — the metaphor creates an identity",
"Enemy / Villain",
"The [Problem It Kills] Elimination [Container]",
"The Feast-and-Famine Elimination Protocol, The Churn Termination System",
"Offers solving a chronic, painful problem — buyer mentally fires the villain when they buy",
"",
"",
"The Five Mechanism Health Indicators",
"Before any formal test is run, five passive signals reveal whether a mechanism name is underperforming in the market. These indicators are monitored continuously and any one of them reaching its threshold fires the 10× Test protocol.",
"",
"Health Indicator",
"What It Measures",
"Data Source",
"Threshold That Fires the Test",
"HI-1: Buyer description accuracy",
"When buyers describe how your offer works to others, do they use your mechanism name — or do they describe it generically?",
"Exit interview transcripts (question: 'How would you describe how this programme works to a friend?'). Community posts where buyers reference the offer. Referral language in sales call recordings.",
"If fewer than 3 out of 10 exit interview respondents use the mechanism name (or a close variant) when asked to describe how the programme works — the mechanism name is not sticking.",
"HI-2: Organic search zero",
"AI engines and search engines are not returning your mechanism name as an authoritative citation for queries in your niche.",
"Run the top 10 niche-relevant queries through ChatGPT, Perplexity, and Google. Count how many results cite your mechanism name vs competitor mechanism names.",
"If zero of your top 10 queries produce a citation of your mechanism name in any AI engine within 90 days of the GEO schema being deployed — the name is not citable enough.",
"HI-3: Sales call non-response",
"When the mechanism name is introduced on a sales call or in a sales email, it generates no visible interest or follow-up questions.",
"Sales call recording review: note buyer's verbal and non-verbal response when the mechanism is named. Email response rate when the mechanism is in the subject line vs when it is not.",
"If buyers consistently respond to the mechanism name with silence, 'Mm-hmm,' or immediately ask about price — there is no curiosity trigger. The mechanism name is producing no lift.",
"HI-4: Competitor mechanism adoption",
"A competitor has adopted similar mechanism language and is gaining visibility with it.",
"Monthly GEO/AEO citation check. Competitor ad monitoring via Meta Ad Library. Keyword monitoring for your mechanism name in competitor content.",
"If a competitor's mechanism name appears in AI search results for your core queries more than yours — your name has lost its distinctiveness advantage.",
"HI-5: Buyer language divergence",
"The language your buyers use to describe their transformation in exit interviews is significantly different from the language your mechanism name uses.",
"Compare exit interview language mining data (Phase 3, Forensic Audit Loop SOP) against the words in your current mechanism name.",
"If zero words in your top 5 buyer language phrases appear in your mechanism name — the name was designed from inside your head, not from buyer intelligence. It needs a rebuild.",
"",
"",
"PHASE 1",
"The Trigger System",
"What fires a 10× Test assessment — scheduled and event-based",
"",
"The Two Trigger Types",
"The 10× Test is triggered in two ways: by scheduled cadence (quarterly, regardless of performance) and by event-based signals (when a health indicator crosses its threshold or a specific market event occurs). Both trigger types result in the same assessment — the full 10× Test Protocol in Phase 2.",
"",
"Scheduled Triggers — The Quarterly Cadence",
"The quarterly cadence is the baseline commitment of this SOP. The mechanism name for every active offer is reviewed every 90 days — whether or not any health indicators have fired and whether or not any event has occurred. The market changes. Language evolves. AI search citation patterns shift. A mechanism name that was earning a 9/10 excitement score in Q1 may be earning 6.5 by Q3 because competitor language has saturated the category.",
"",
"Quarter",
"Timing",
"Scope",
"Output",
"Q1 Review",
"January — first week",
"All active mechanism names across all offers. Full 10× Test Protocol run on each.",
"Q1 Mechanism Health Report. Rename decisions confirmed or declined for each offer.",
"Q2 Review",
"April — first week",
"Same scope as Q1.",
"Q2 Mechanism Health Report.",
"Q3 Review",
"July — first week",
"Same scope as Q1. Mid-year language mining data from Forensic Audit Loop incorporated.",
"Q3 Mechanism Health Report. Often the highest-value review because buyer language mining has accumulated a full half-year of data.",
"Q4 Review",
"October — first week",
"Same scope as Q1. Planning review: any mechanism names that need a rename before the January cohort or product launch cycle should be renamed in Q4 so copy assets are fresh at launch.",
"Q4 Mechanism Health Report. Year-end mechanism name audit complete.",
"",
"Event-Based Triggers — Immediate Assessment",
"Trigger Event",
"Source",
"Action Within",
"Context",
"Any Health Indicator reaches threshold (HI-1 through HI-5)",
"Ongoing monitoring (see Five Health Indicators section)",
"14 days of threshold being crossed",
"Run Phase 2 (10× Test) within 14 days. Do not wait for the quarterly cadence.",
"New buyer language mining data reveals a phrase that is measurably stronger than the current mechanism name",
"Monthly language mining review (Forensic Audit Loop SOP, Phase 3)",
"30 days of data confirmation",
"Run the Phase 4 candidate validation specifically for the new phrase before committing to a full rename cycle.",
"Competitor adopts identical or near-identical mechanism language",
"GEO/AEO citation check or Meta Ad Library audit",
"7 days",
"Immediate distinctiveness loss. Run Phase 2 with differentiation as the primary criterion. A mechanism name shared with a competitor is worse than no mechanism name.",
"Offer fails Kill Assessment after one full iteration cycle with no mechanism change",
"Product Kill Criteria SOP — iterate outcome with mechanism as unchanged variable",
"Before the next iteration cycle",
"Before changing any other element of the offer, change the mechanism name. The mechanism is often the cause of a failing offer when all other variables have been iterated without improvement.",
"Major market shift — new technology, new platform, or new regulatory environment that changes buyer language",
"Market intelligence monitoring (Course 5: Market Reality)",
"30 days of confirmed shift",
"If the market has shifted enough that buyers are using fundamentally different language than 6 months ago, the mechanism name may need to reflect the new language landscape.",
"",
"",
"PHASE 2",
"The 10× Test Protocol",
"The structured assessment that determines whether a rename is necessary",
"",
"The Test Population",
"The 10× Test is run with five individuals who match the target avatar for the offer under review. The test population must be avatar-matched — they should be people who would genuinely consider purchasing the offer. Testing with marketers, colleagues, or people who know you well produces biased scores. The correct population is:",
"",
"• Existing buyers from prior cohorts who have not heard the current mechanism name discussed in a testing context",
"• Prospective buyers who are currently in the consideration stage — they have opted into your list, attended a webinar, or engaged with organic content",
"• Avatar-matched individuals recruited via community engagement who are unfamiliar with your specific mechanism name but fit the target avatar profile exactly",
"• Podcast listeners or content consumers who match the avatar but have not yet purchased",
"",
"Who NOT to Test With",
"Do not test with: other operators in your network ('What do you think of this name?'). Your team or VA. Other course creators or marketers who spend time in your ecosystem. These populations are not your buyer — they have domain familiarity that distorts their reaction. A marketer who reads Kennedy and Brunson will score 'The Epiphany Bridge' a 9 because they know what it is. Your actual buyer may score it a 5 because it sounds abstract without context.",
"",
"The Five Subtests",
"The 10× Test Protocol comprises five distinct subtests. Each tests a different dimension of the mechanism name's effectiveness. All five are required — not four, not three. A name that passes four and fails one has a specific, diagnosable weakness that should either be fixed or accepted as a known limitation.",
"",
"Subtest",
"What Is Measured",
"Pass",
"Fail",
"How to Administer",
"T-1: Excitement Score",
"First impression excitement when the name is read aloud for the first time, with no explanation",
"Average 7.0+ out of 10 across all five testers",
"Average below 7.0",
"Read the name once, clearly. Ask: 'On a scale of 1 to 10, how excited does that name make you feel about finding out what it is?' Record without discussion.",
"T-2: Description Accuracy",
"Whether the tester's mental model of what the mechanism does matches what it actually does",
"4 of 5 testers describe the mechanism in a way that matches its actual function",
"Fewer than 4 of 5 match",
"After the excitement score, ask: 'What do you imagine this method does based on the name alone?' Record verbatim. Score as Match / Partial Match / Mismatch against the actual mechanism description.",
"T-3: Curiosity Trigger",
"Whether the name generates genuine desire to learn more — not just polite interest",
"4 of 5 testers ask a follow-up question OR say a variant of 'I want to know what that is'",
"Fewer than 4 of 5 produce a genuine follow-up or curiosity statement",
"After description, observe and note any spontaneous follow-up questions. Do not prompt. If after 15 seconds there is no follow-up, ask 'Do you want to know more about how it works?' and record their energy level (1=flat, 5=genuine interest).",
"T-4: Memorability",
"Whether the tester can accurately recall the mechanism name 10 minutes later",
"4 of 5 testers recall the name correctly (exact or within one word) after 10 minutes",
"Fewer than 4 of 5 recall correctly",
"After completing T-1/T-2/T-3 and 10 minutes of unrelated conversation: 'Can you recall the name of the method we discussed earlier?' Record verbatim. Score: Exact / Close / Approximate / Incorrect.",
"T-5: Distinctiveness",
"Whether the name sounds proprietary and unique — not like a commodity label the tester has heard before",
"4 of 5 testers confirm they have not heard this specific name used to describe a methodology before",
"3 or more testers say it sounds familiar or like something they've heard from other sources",
"After memorability check: 'Have you heard this name used to describe a method or system before?' and 'Does this name sound like something other people also use or more like something this specific person invented?' Record both answers.",
"",
"The 10× Test Scorecard",
"Complete one scorecard per offer per test. File in Airtable under Mechanism Name Records.",
"",
"Field",
"Record Here",
"Offer name and current mechanism name",
"",
"Test date",
"",
"Test population description (5 testers)",
"",
"T-1 Excitement Scores (all 5 testers, 1–10)",
"Tester 1: ___ / T2: ___ / T3: ___ / T4: ___ / T5: ___",
"T-1 Average",
"___ / Pass (7.0+) or Fail",
"T-2 Description accuracy (all 5 testers: Match / Partial / Mismatch)",
"T1: ___ / T2: ___ / T3: ___ / T4: ___ / T5: ___",
"T-2 Result",
"___ of 5 match / Pass (4+) or Fail",
"T-3 Curiosity trigger (all 5 testers: Question / Statement / Flat)",
"T1: ___ / T2: ___ / T3: ___ / T4: ___ / T5: ___",
"T-3 Result",
"___ of 5 triggered / Pass (4+) or Fail",
"T-4 Memorability (all 5 testers: Exact / Close / Approximate / Incorrect)",
"T1: ___ / T2: ___ / T3: ___ / T4: ___ / T5: ___",
"T-4 Result",
"___ of 5 recalled / Pass (4+) or Fail",
"T-5 Distinctiveness (all 5 testers: Unique / Familiar)",
"T1: ___ / T2: ___ / T3: ___ / T4: ___ / T5: ___",
"T-5 Result",
"___ of 5 confirmed unique / Pass (4+) or Fail",
"Overall result",
"Pass (all 5 subtests pass) / Conditional (4 subtests pass) / Fail (3 or fewer pass)",
"Subtests failed (if any)",
"List specific subtests and which testers produced the fail scores",
"Key verbatim phrases from testers (any that are interesting)",
"",
"Rename triggered?",
"Yes / No",
"",
"Test Result Interpretation",
"Result",
"Condition",
"Decision",
"Priority",
"PASS — No rename needed",
"All 5 subtests pass their respective thresholds",
"Current mechanism name is performing at the 10× standard. No action required until next quarterly test.",
"Schedule next test for 90 days. Log passing scores in Airtable.",
"CONDITIONAL — Targeted improvement",
"4 of 5 subtests pass. One specific weakness identified.",
"Run Phase 3 (Name Generation) specifically targeting the failing dimension. The new name does not require a full rename — it may require a one-word adjustment.",
"Run within 30 days. Single-dimension fix rather than full rebuild.",
"FAIL — Rename triggered",
"3 or fewer subtests pass",
"Full rename cycle initiated. Run Phases 3, 4, 5, 6, 7 in sequence.",
"Immediate. Full rename cycle to be completed within 60 days.",
"",
"",
"PHASE 3",
"The Name Generation System",
"Producing 10 or more strong candidates before selecting any",
"",
"The Generation Principle",
"The first candidate name generated in any rename session is almost never the best one. The best mechanism names consistently emerge from exhaustive generation — after the obvious names have been written down and set aside. The system below requires a minimum of 10 candidates before evaluation begins. Evaluating fewer than 10 candidates produces premature commitment to the path of least resistance rather than the most powerful option.",
"",
"Kennedy's 25-Headline Rule Applied to Mechanisms",
"Kennedy's instruction to write 25 headlines before evaluating any of them applies directly to mechanism name generation. The first 5 candidates are the obvious ones — the names that come to mind immediately because they are already close to the current name. Candidates 6 through 10 require real creative effort. Candidates 11 through 15 are often where the genuinely distinct and powerful name appears. Generate 15. Evaluate 5. Deploy 1.",
"",
"The Six Generation Methods",
"Run all six methods in sequence. Each method approaches the mechanism from a different angle and produces candidates of a different character. Use the language mining database from the Forensic Audit Loop SOP as your primary input for methods 1 and 2.",
"",
"Method 1 — Buyer Language Inversion",
"The strongest mechanism names often come from inverting the buyer's pain language into a process name. Pull the top 5 PAIN-ACUTE and PAIN-CHRONIC phrases from the buyer language mining database. For each phrase, ask: if there were a named method that specifically eliminated this pain, what would it be called?",
"",
"Buyer Pain Phrase",
"Pain Type",
"Mechanism Name Derived",
"Pattern Used",
"'I keep spinning my wheels building things that don't sell'",
"PAIN-CHRONIC",
"The Anti-Wheel-Spin Validation System",
"Enemy/Villain",
"'I have no idea if my offer is the problem or my traffic'",
"PAIN-ACUTE",
"The Offer/Traffic Diagnostic Separation Method",
"Forensic/Diagnostic",
"'Every course I buy tells me what to do but not why it's not working'",
"PAIN-CHRONIC",
"The Forensic Offer Autopsy — Root Cause Identification",
"Forensic/Diagnostic",
"'I've been stuck at the same revenue for 9 months'",
"PAIN-ACUTE",
"The Revenue Plateau Elimination Protocol",
"Enemy/Villain",
"'My funnel converts cold but I can't scale it'",
"PAIN-ACUTE",
"The Cold-to-Scale Conversion Architecture",
"Process Number/Structure",
"",
"Method 2 — Transformation Visualization",
"Describe the exact before state and after state of the buyer's journey through the mechanism. Draw or write the metaphor of that journey. What physical process, natural phenomenon, or human activity does it most closely resemble? The metaphor becomes the name.",
"",
"• Before state → After state: 'Spinning wheels with no market data' → 'Validated offer selling within 30 days'",
"• Physical metaphor: A forensic scientist arriving at a crime scene, not starting with theories but with evidence. The methodology does what a forensic scientist does — gathers physical evidence before drawing any conclusions.",
"– Mechanism candidate from metaphor: 'The Forensic Offer Autopsy' / 'The Evidence-First Offer Diagnosis' / 'The Market Crime Scene Investigation'",
"",
"Method 3 — The Competitor Inversion",
"Identify the dominant mechanism language in your niche — what terms and names your competitors use most frequently. Then deliberately move in the opposite direction. If everyone says 'funnel,' name something that has nothing to do with funnels. If everyone says 'system,' use a different container word.",
"",
"Competitor's Dominant Language",
"Category Saturation",
"Counter-Position Direction",
"Candidate Name",
"'Marketing Funnel' / 'Sales Funnel'",
"Extremely high — every operator uses 'funnel'",
"Process that works backwards, or process that eliminates the need for a funnel",
"'The Reverse Funnel Method' / 'The Anti-Funnel Revenue Protocol'",
"'Content Strategy' / 'Content Framework'",
"Very high — commoditised language",
"Name the specific mechanism of what content does, not what it is",
"'The Sovereign Content Flywheel' / 'The Attention Architecture Method'",
"'Offer Optimisation' / 'Offer Improvement'",
"High",
"Name it as a diagnostic/forensic process rather than an optimization",
"'The Offer Forensics Protocol' / 'The Offer Autopsy & Rebuild Method'",
"",
"Method 4 — The Speed Compression Test",
"Identify the fastest a buyer could realistically go from starting the mechanism to achieving the core result. Then build the mechanism name around that time window. Speed-implied names produce the highest T-1 excitement scores for crisis and entry-point buyers.",
"",
"• 'If a disciplined buyer executed this methodology with full focus — what is the minimum time to the first measurable result?'",
"• That time window becomes part of the mechanism name: '48-Hour Offer Rebuild Protocol', 'The 7-Day Market Validation Sprint', 'The 14-Day Pipeline Reset Method'",
"• Warning: do not manufacture speed. The time stated in the mechanism name must be achievable by a motivated buyer. Overstating speed creates expectation mismatch and Negative Avatar Archetype 03 (Too-Late-for-the-Promise buyers).",
"",
"Method 5 — The Authority Claim",
"Name the mechanism after the underlying insight, research base, or authority source that makes it work. This pattern is most effective when there is a genuine research foundation or a counterintuitive insight that separates the methodology from conventional advice.",
"",
"• What is the one insight that makes this mechanism work when other approaches fail? Name the insight.",
"• Examples: 'The Execution Debt Framework' (names the insight that buyers know the problem and solution but lack execution capacity). 'The Bleeding Neck Audit' (names the triage insight that only urgent, expensive problems convert). 'The Muddled Middle Elimination Method' (names the pricing insight).",
"– These names have the highest T-5 distinctiveness scores because they are built on a named insight that cannot be claimed by competitors without explicitly citing you.",
"",
"Method 6 — The AI Generation Prompt",
"After generating 8–10 candidates using Methods 1–5, use the following prompt to generate an additional 10 candidates from an AI. Use the strongest 3 from the AI output to round out the candidate set to 15+.",
"",
"AI Name Generation Prompt",
"You are a direct-response copywriter specialising in mechanism names for expert-led programmes. I need 10 mechanism name candidates for the following:Offer: [Offer Name]Target Avatar: [One-sentence avatar description]Core transformation: [Before state → After state in one sentence]Primary pain phrase (verbatim from buyer): '[PAIN-ACUTE phrase from language mining]'Approach type: [Forensic / Speed / Authority / Metaphor / Enemy — choose the approach not yet represented in my current candidates]Competitor language to avoid: [List 5 dominant competitor terms]For each name: provide (1) the name, (2) a one-sentence mechanism statement using it, (3) which of the 7 characteristics it best fulfils, and (4) its likely weakness.Output 10 names. Do not repeat patterns. Do not use the word 'system' or 'framework' in any of the 10 names.",
"",
"",
"PHASE 4",
"The Candidate Validation Protocol",
"Selecting the winner from the generated shortlist",
"",
"The Shortlist Criteria",
"After generating 15+ candidates using the six methods, apply the shortlist criteria below to reduce to 5 finalists before running the 10× Test on the candidates. Do not test all 15 — testing fatigue degrades the quality of responses from the test population.",
"",
"Shortlist Criterion",
"Disqualifier (remove from list if true)",
"Refine If Partially True",
"Trademark / naming conflict",
"A quick Google search returns results where the exact name is already in active commercial use by a competitor in your niche",
"If a close variant exists but not the exact name — add one word to differentiate",
"Commodity language",
"The name contains words used by more than 50% of operators in the niche — 'system,' 'strategy,' 'framework,' 'method' are borderline; 'content,' 'marketing,' 'lead generation' alone are disqualifiers",
"Replace generic words with specific words: 'System' → 'Protocol'; 'Strategy' → 'Architecture'; 'Framework' → 'Autopsy'",
"Description mismatch — pre-test",
"A team member or close colleague who matches the avatar, upon hearing the name for the first time, describes something completely different from what the mechanism does",
"Reframe or rename before testing with the full population",
"Unpronounceable or unmemorable",
"The name is longer than 7 words, contains a word that is difficult to pronounce or spell, or creates a clumsy acronym",
"Cut to under 5 words. Remove the offending word. Test memorability informally before full test.",
"",
"Running the 10× Test on Candidates",
"Test the top 5 shortlisted candidates with the same five testers used in Phase 2. Present each candidate in isolation — do not show the full list of 5. The tester should react to each name as if it were the only candidate.",
"",
"1. Present candidate 1 to all five testers. Run T-1 (excitement), T-3 (curiosity only — skip description and memorability for efficiency). Record.",
"2. After a minimum 5-minute break for each tester, present candidate 2. Same process.",
"3. Continue for all 5 candidates. Maintain at least 5 minutes between each candidate to reduce carry-over bias.",
"4. After all 5 candidates are presented: ask each tester to rank their top 2 in order of preference. Record rankings.",
"5. Select the candidate with the highest combined excitement score AND at least 3 of 5 first-preference rankings. If two candidates tie: run T-4 (memorability) as a tiebreaker.",
"",
"The Candidate Comparison Scorecard",
"Candidate Name",
"T-1 Average(1–10)",
"T-3 Score(out of 5)",
"First-Preference Rankings(out of 5 testers)",
"Combined Score",
"Proceed?",
"[Candidate 1]",
"",
"",
"",
"",
"Yes / No",
"[Candidate 2]",
"",
"",
"",
"",
"Yes / No",
"[Candidate 3]",
"",
"",
"",
"",
"Yes / No",
"[Candidate 4]",
"",
"",
"",
"",
"Yes / No",
"[Candidate 5]",
"",
"",
"",
"",
"Yes / No",
"WINNER",
"",
"",
"",
"",
"",
"",
"",
"PHASE 5",
"The Rename Decision Framework",
"Confirming the rename before any deployment begins",
"",
"The Three-Gate Confirmation",
"Before any deployment begins, the rename must clear three confirmation gates. These gates protect against premature deployment of a name that tested well with a small sample but has a structural flaw that would reveal itself at scale.",
"",
"Gate",
"Question",
"Required Answer",
"If Not Cleared",
"Gate 1 — Score threshold",
"Does the winning candidate score average 7.5+ on T-1 across all five testers AND pass T-2, T-3, T-4, T-5?",
"Yes to both — 7.5+ average AND all five subtests pass for the winner",
"Do not rename. The winner is not yet strong enough. Run another generation cycle (Phase 3) targeting the specific failing subtest.",
"Gate 2 — Mechanism statement completeness",
"Can you write a single, clear mechanism statement for the new name — in one sentence — that describes what it is, how it works, and why it produces the result?",
"Yes — the mechanism statement is written, reviewed, and confirmed in under 30 seconds by an avatar-matched individual",
"Do not rename. A name you cannot write a mechanism statement for is a name the buyer cannot understand. Refine until the statement is natural.",
"Gate 3 — Deployment viability",
"Is the full deployment (all assets listed in Phase 6) achievable within 30 days with the current team?",
"Yes — deployment plan is mapped, owners are assigned, and completion is confirmed as feasible",
"Decide: delay rename until capacity exists, or hire short-term to complete deployment. Do not partially deploy — a partially renamed offer produces version drift (see Product Versioning SOP).",
"",
"The Rename Announcement Decision",
"Some renames should be announced to the existing buyer base. Most should not. The decision depends on whether the rename affects the buyer's experience, their ability to reference the offer, or their sense of what they purchased.",
"",
"Rename Scenario",
"Announce to Existing Buyers?",
"Communication Approach",
"Minor rename — same methodology, new name. The mechanism does the same thing, described more powerfully.",
"No — existing buyers do not need to know the name changed. Update assets silently.",
"No communication. Update product versioning record as a Minor change (CAT-M).",
"Significant rename — same methodology, the new name implies a meaningfully different approach or emphasis.",
"Yes — optional but recommended. A brief, genuine note about why the name evolved.",
"One email: 'You may have heard me refer to [method] as [old name]. I've renamed it [new name] because [specific reason from buyer language data]. Same methodology — better description of what it actually does.'",
"Major rename — the methodology itself has evolved and the new name reflects genuinely different positioning or scope.",
"Yes — required. This is a product versioning change.",
"Follow the Major version buyer communication protocol from the Product Versioning SOP.",
"",
"",
"PHASE 6",
"The Deployment System",
"Rolling out the new mechanism name across every asset — completely and correctly",
"",
"The Non-Negotiable Deployment Completeness Rule",
"A partial rename is worse than no rename. An offer where some assets use the old name and some use the new name creates confusion for buyers, degrades the mechanism's authority (because it appears the name was changed which implies the old name was inadequate), and produces version drift. The deployment must be complete before the new name is used in any external communication.",
"",
"The Deployment Rule",
"The new mechanism name goes live everywhere simultaneously — or not at all. The day the sales page is updated is the day every email sequence, every ad, every affiliate swipe copy, every community reference, every schema markup, and every GEO asset is also updated. No phased deployments. No 'we'll update the ads next week.' Complete or wait.",
"",
"The Complete Mechanism Rename Deployment Checklist",
"Every asset below must be updated on or before the deployment date. Assign one owner and one deadline to the entire checklist — not individual deadlines per item. Either the whole checklist is complete or the deployment date moves.",
"",
"Tier 1 — Primary Conversion Assets (Deploy First — Block Everything Else)",
"☐ Sales page: mechanism section headline, mechanism description paragraph, all mentions of the old name throughout",
"☐ Sales page: the Mechanism Repeatability Test box or 'How it works' section",
"☐ VSL or video sales letter script: all verbal references to the mechanism name",
"☐ Offer stack slide: mechanism name if it appears in the stack",
"☐ 14-day email sequence: Days 8, 9, and 10 (mechanism introduction emails) — headline, body copy, and mechanism statement",
"☐ All active ad creatives: any ad that names or references the mechanism",
"☐ All active ad copy: body copy, CTA copy that references the mechanism",
"",
"Tier 2 — Course Platform and Delivery Assets",
"☐ Course platform: programme title if it includes the mechanism name",
"☐ Course platform: module descriptions that reference the mechanism",
"☐ Course platform: welcome video script or intro video that names the mechanism",
"☐ Onboarding email sequence: any email that introduces the mechanism to new buyers",
"☐ Community welcome message and pinned posts that reference the mechanism",
"☐ All worksheets, PDFs, and templates that name the mechanism",
"☐ Physical materials (if Shock-and-Awe package includes printed reference to mechanism)",
"",
"Tier 3 — GEO/AEO and Search Assets",
"☐ Product + Offer Schema JSON-LD: mechanism name in description field",
"☐ Person + Organization Schema: knowsAbout property — add new mechanism name, retain old name with 'formerly known as' notation for citation continuity",
"☐ LLMs.txt file: update mechanism name in authority declaration",
"☐ Pillar article: all occurrences of the old mechanism name",
"☐ All blog posts referencing the mechanism: update inline with redirect from old name",
"☐ AEO/GEO keyword schema: update L0 branded methodology entries and Definitive Statement Library",
"☐ YouTube video titles and descriptions that name the mechanism",
"☐ Podcast episode titles and show notes that name the mechanism",
"",
"Tier 4 — Partner and Community Assets",
"☐ Affiliate swipe copy: all emails, social captions, and video scripts naming the mechanism",
"☐ JV partner materials: any co-branded content using the old mechanism name",
"☐ Guest podcast appearances: update speaker bio and talking points if mechanism is referenced",
"☐ PR and HARO quote templates: update any quoted reference to the mechanism",
"☐ Social media bio on all platforms if mechanism name appears",
"",
"Tier 5 — Records and Archives",
"☐ Product versioning changelog: new changelog entry filed (CAT-M, MINOR or MAJOR depending on scope)",
"☐ Mechanism Name Library in Airtable: old name archived, new name activated",
"☐ Testimonial Version Registry: all testimonials referencing the old name flagged as Version-Specific (Retired)",
"☐ Buyer Language Mining Database: new mechanism name added as a branded keyword",
"☐ GEO/AEO keyword schema: new mechanism name added to L0 (Authority Topics) and branded methodology keywords",
"",
"",
"PHASE 7",
"Performance Measurement",
"Proving the rename worked — and building the intelligence for the next cycle",
"",
"The Three Performance Windows",
"Every rename is an experiment with a defined outcome: the new mechanism name should produce measurably higher performance than the old name across three measurement windows. If it does not, the rename itself becomes a data point that feeds the next generation cycle.",
"",
"Window",
"Timing",
"Metrics",
"Comparison Baseline",
"Action If No Improvement",
"7-Day Window",
"Days 1–7 post-deployment",
"T-1 excitement scores from any new test population encountered. Email subject line open rate (if mechanism name is in subject). Sales call conversion rate from first call to paid.",
"Pre-rename baseline from same metrics in the 30 days before deployment",
"No action — 7 days is insufficient to draw conclusions. Log data. Continue to 30-day window.",
"30-Day Window",
"Days 8–37 post-deployment",
"Cold sales page conversion rate. Warm list conversion rate. Email click-through rate on mechanism introduction emails. Sales call close rate.",
"30-day pre-rename average for same metrics",
"If cold conversion is more than 10% below pre-rename baseline: run emergency 10× Test to determine if the new name has a structural problem. Do not immediately rename again — diagnose first.",
"90-Day Window",
"Days 38–127 post-deployment",
"All 30-day metrics above PLUS: AI engine citation rate (does the new mechanism name appear in Perplexity/ChatGPT/Gemini results?). Buyer language adoption rate (are buyers using the new name in exit interviews and testimonials?).",
"90-day pre-rename average for all metrics",
"If no improvement at 90 days AND buyer language adoption rate is below 40%: the rename did not land. Schedule the next quarterly test. Do not rush — 90 days is the minimum evaluation window for a mechanism name change.",
"",
"The Rename Performance Record",
"Complete this record at each measurement window. File in Airtable under Mechanism Name Records, linked to the Changelog entry for the rename.",
"",
"Metric",
"Pre-Rename Baseline",
"7-Day Post",
"30-Day Post",
"90-Day Post",
"Delta (90-day vs baseline)",
"Cold sales page conversion rate",
"",
"",
"",
"",
"",
"Warm list conversion rate",
"",
"",
"",
"",
"",
"Email open rate (mechanism-name subject lines)",
"",
"",
"",
"",
"",
"Sales call close rate",
"",
"",
"",
"",
"",
"T-1 Excitement score (new testers, informal)",
"",
"",
"",
"",
"",
"AI engine citation rate (mechanism name mentioned per 10 queries)",
"",
"",
"",
"",
"",
"Buyer language adoption (% using name in exit interviews)",
"",
"",
"",
"",
"",
"",
"",
"Worked Examples: Mechanism Name Evolution",
"These worked examples show the complete cycle — from a weak mechanism name, through the test process, to a stronger name — with the specific reasoning that drove each transformation. All examples are generalisable to the RISER Nation offer context.",
"",
"Example 1 — Offer Construction Mechanism",
"",
"",
"Old Name",
"Score",
"New Name",
"Why It Changed",
"New Score",
"The 5-Step Offer Building System",
"5.1",
"The Forensic Offer Autopsy Method",
"'Offer building system' had a 5.1 average excitement score. Testers described it as 'a course about making offers.' The new name scored 7.8 because 'forensic' implies expert diagnosis, 'autopsy' implies finding what killed the conversion rate, and 'method' implies a reproducible process. Testers said: 'I want to know what mine looks like.'",
"7.8",
"The Offer Optimization Framework",
"4.8",
"The Revenue Leak Diagnostic Protocol",
"'Optimization framework' failed T-5 distinctiveness (all 5 testers had heard similar language elsewhere). The new name passed all 5 subtests. Key buyer language mined: 'I keep losing money somewhere but I don't know where.' That phrase became the name's metaphor.",
"7.4",
"",
"Example 2 — Content Mechanism",
"",
"",
"Old Name",
"Score",
"New Name",
"Why It Changed",
"New Score",
"The Content Strategy Method",
"4.2",
"The Sovereign Content Flywheel",
"Lowest excitement score in testing — 4.2. Failed T-5 badly (all 5 testers said they had heard similar language from other creators). 'Flywheel' adds a physics metaphor (something that generates momentum and becomes self-sustaining). 'Sovereign' implies ownership and independence from algorithms. Testers' spontaneous follow-up: 'What makes it a flywheel?' — perfect T-3 curiosity trigger.",
"8.1",
"The One-to-Many Content System",
"5.8",
"The Cornerstone Atomisation Architecture",
"'One-to-many' scored 5.8 — adequate but not distinctive. Buyer language mining revealed: 'I record one thing and it somehow multiplies.' 'Cornerstone atomisation' captures that exact behaviour. The geological metaphor (breaking a cornerstone into its component elements) scored highest on T-2 description accuracy because testers immediately understood the input/output relationship.",
"7.6",
"",
"Example 3 — Market Research Mechanism",
"",
"",
"Old Name",
"Score",
"New Name",
"Why It Changed",
"New Score",
"Market Research Method",
"4.0",
"The Bleeding Neck Audit",
"4.0 excitement — the lowest possible failing score. 'Market research' is pure commodity language. Zero distinctiveness, zero curiosity, zero metaphor. Buyer language mining: 'I need to find a problem so painful they'll pay anything to fix it.' 'Bleeding neck' is visceral, specific, and impossible to confuse with any competitor's language. Highest T-3 curiosity trigger in this example set — 5/5 testers asked what it meant.",
"8.4",
"",
"",
"The Mechanism Name Library — Airtable Schema",
"",
"Table 1 — Mechanism Name Records",
"One record per mechanism per offer. The full history of every mechanism name tested, deployed, and retired.",
"",
"Field",
"Type",
"Notes",
"Record ID",
"Autonumber",
"",
"Offer",
"Link → Offers table",
"",
"Mechanism Name (current)",
"Short text",
"The currently deployed name",
"Status",
"Single select",
"Testing / Active / Retired",
"Deployed Date",
"Date",
"When this name went live",
"Trigger That Initiated This Cycle",
"Single select",
"Quarterly Cadence / HI-1 through HI-5 / Event-Based (specify)",
"T-1 Excitement Average (deployment test)",
"Number",
"Average of 5 testers at time of deployment decision",
"T-2 Description Accuracy",
"Number",
"Out of 5",
"T-3 Curiosity Trigger",
"Number",
"Out of 5",
"T-4 Memorability",
"Number",
"Out of 5",
"T-5 Distinctiveness",
"Number",
"Out of 5",
"Overall Test Result",
"Single select",
"Pass / Conditional / Fail",
"Mechanism Statement",
"Long text",
"The one-sentence HOW statement for this name",
"Name Pattern Used",
"Single select",
"Forensic/Diagnostic / The Reverse / Speed+Object / Authority Method / Named Discovery / Process Number / Metaphor+Container / Enemy/Villain",
"Prior Mechanism Name",
"Short text",
"The name this replaced (for audit trail)",
"Prior Name Retired Date",
"Date",
"",
"7-Day Performance Delta",
"Number",
"% change in primary conversion metric vs pre-rename baseline",
"30-Day Performance Delta",
"Number",
"",
"90-Day Performance Delta",
"Number",
"",
"AI Citation Rate at 90 Days",
"Number",
"Citations per 10 queries across all three AI engines",
"Buyer Language Adoption Rate at 90 Days",
"Number",
"% of exit interview respondents using new name",
"Linked Changelog Entry",
"Link → Changelog Entries",
"The Product Versioning SOP changelog entry for this rename",
"Linked Language Mining Phrases",
"Long text",
"The specific PAIN-ACUTE/PAIN-CHRONIC phrases that informed this name",
"Next Quarterly Test Date",
"Date",
"Deploy Date + 90 days",
"",
"",
"Master 10× Mechanism Test & Rename Cadence Checklist",
"",
"System Setup (One-Time)",
"☐ Create Mechanism Name Records table in Airtable with all fields from schema above",
"☐ Document the current mechanism name for every active offer — create one record per offer",
"☐ Run the 10× Test Protocol (Phase 2) on all current mechanism names as the baseline assessment",
"☐ File baseline test scores in Airtable — this establishes the before-state for first-cycle comparison",
"☐ Set quarterly cadence calendar reminders: January, April, July, October — first week of each",
"",
"Every Quarterly Cadence Trigger",
"☐ Pull current mechanism name for each active offer from Airtable",
"☐ Identify test population of 5 avatar-matched individuals per offer",
"☐ Run all five subtests of the 10× Test Protocol in sequence",
"☐ Complete the 10× Test Scorecard for each offer",
"☐ Record test result: Pass / Conditional / Fail",
"☐ If Pass: update Airtable record with latest test scores. Schedule next quarterly test.",
"☐ If Conditional: run Phase 3 targeting the specific failing subtest dimension only",
"☐ If Fail: initiate full rename cycle (Phases 3 through 7)",
"",
"Every Rename Cycle (Phases 3–7)",
"☐ Run all six generation methods — minimum 15 candidates total",
"☐ Apply shortlist criteria — reduce to 5 finalists",
"☐ Run 10× Test on all 5 shortlisted candidates",
"☐ Complete Candidate Comparison Scorecard — identify winner",
"☐ Run Three-Gate Confirmation — all three gates must clear before deployment",
"☐ Write mechanism statement for the new name — one sentence",
"☐ Determine rename announcement decision (silent / notification email / Major version communication)",
"☐ Map deployment: assign single owner, single deadline for all Tier 1–5 assets",
"☐ Deploy all assets simultaneously on deployment date — no partial deploys",
"☐ File changelog entry in Product Versioning SOP (CAT-M change)",
"☐ Update Mechanism Name Library record with new name, deploy date, test scores",
"☐ Set three performance review calendar reminders: 7-day, 30-day, 90-day",
"",
"30-Day Post-Rename Performance Review",
"☐ Pull cold conversion rate, warm conversion rate, email open rate, close rate",
"☐ Compare against pre-rename baseline",
"☐ If cold conversion is more than 10% below baseline: run emergency diagnostic before next cycle",
"☐ File 30-day data in Mechanism Name Record",
"",
"90-Day Post-Rename Performance Review",
"☐ Pull all metrics including AI citation rate and buyer language adoption rate",
"☐ File 90-day data in Mechanism Name Record",
"☐ If buyer language adoption rate below 40%: schedule mechanism statement review for next quarterly test",
"☐ Schedule next quarterly cadence test (90-day from deployment = test date)",
"",
"",
"",
"RISER Nation Master Operating System | 10× Mechanism Test & Rename Cadence SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | 10× Mechanism Test & Rename Cadence SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
}
]
}
Check whether delivery can support the promise
Start with the buyer’s experience
Imagine a campaign bringing twice the usual number of buyers. Access emails arrive, but coaching sessions, support replies and revisions all need the same small team. This is an illustrative scenario. The question is whether the complete delivery process can support the promise at that workload.
The source connects fulfilment with offer credibility and long-term buyer results. Read its attributed Hormozi and Kennedy principles and the five situations in which it proposes a stress review.
Hormozi's Delivery Principle The offer is the promise. The delivery is the proof. Your business's long-term value — its testimonials, its ascension rate, its referral velocity, its reputation in AI search results — is built entirely on whether delivery matches promise. A stress test protects the delivery before a scale event exposes its vulnerabilities.
Kennedy's Fulfilment Warning The most dangerous moment in any business is the first successful campaign. You prove the market will buy — and then you find out whether you can actually serve them. The businesses that survive rapid growth are the ones that found their fulfilment ceiling in a controlled test, not in a live launch.
When This SOP Applies Run a Fulfilment Stress Test before: the first paid ad campaign on any offer, any JV or affiliate launch expected to generate 3x or more your current buyer volume, any offer graduation from beta to full public launch, any price change that would significantly increase buyer volume, and any expansion into a new delivery format (e.g. moving from self-paced to live cohort).
The course application is to keep the offer, its supporting evidence and its delivery consistent. This supports the Brunson and Hormozi themes used in the curriculum. The source’s broad claims about growth failures are not verified business results. Its paper exercise is a planning method, not an actual load test or authorization to scale.
We will cover all ten phases. No source instruction to hire, change credentials, contact buyers, test live platforms or authorize a launch is executed by this lesson.
Map the delivery model and each handoff
The five models have different constraints: self-paced access and support, shared live calls, intensive personal work, deliverables created for the buyer, and combinations of those models.
Delivery Model
Definition
Primary Stress Vectors
When It Breaks
Model 1 Self-Paced Digital
Course, template pack, or digital product consumed at the buyer's own pace with no live delivery component
Tech access reliability, video hosting load, download speeds, support volume from confused or stuck buyers, community management at scale
Video hosting CDN overloads under traffic spikes; support tickets multiply geometrically as buyer count grows; community becomes unmanageable without a moderator
Model 2 Live Group Cohort
Scheduled programme with live calls, group sessions, and a defined start/end date. All buyers progress together
Calendar capacity (founder cannot clone), call quality at scale (group coaching degrades above ~30 people per call), community activation between calls, recording and replay delivery
Founder's calendar becomes the hard ceiling; call quality degrades above 25–30 participants; community becomes a support forum rather than a learning environment without active management
Model 3 Done-With-You Intensive
High-touch delivery where the founder or team works directly with the buyer to implement the result — typically 1:1 or small group
Time per buyer (the hardest cap in the business), preparation quality, rescheduling protocols, delivery consistency across multiple intensive sessions
Founder's available hours per week is the absolute hard ceiling; one rescheduled session creates a cascade; quality degrades when preparation is rushed due to over-booking
Model 4 Done-For-You Service
The team delivers a specific output on behalf of the buyer — copy, design, automation, content, technical builds
Labour hours per deliverable, revision cycle load, quality control checkpoints, client communication frequency, project management overhead
Revision cycles multiply as client count increases; quality control breaks without a QA process; communication overhead consumes delivery time; margin erodes rapidly at scale without systems
Model 5 Hybrid
Combination of two or more delivery models (e.g. self-paced course + live monthly calls + DFY deliverable)
All stress vectors from each component model apply simultaneously; dependencies between components create additional failure points; support cannot be specialised
Complexity multiplies: a failure in one component stresses all others; buyer expectations for the live component affect perceived quality of the self-paced component
Map Element
What to Document
Example
Purchase trigger
What happens in the first 60 seconds after payment is confirmed? Who or what is notified?
Stripe webhook triggers Kajabi to grant course access and ActiveCampaign to start onboarding sequence. Confirmation email sent automatically within 60 seconds.
Access delivery
How does the buyer access what they purchased? What platform, what credentials, what steps?
Kajabi sends login email with access link. Buyer must create password. Course appears in their dashboard. Access is instant — no manual steps.
Onboarding sequence
What guided experience does the buyer receive in the first 72 hours?
Day 0: Welcome email + 'your first step' instruction. Day 1: Module 1 access reminder + community invite. Day 2: 72-hour check-in from founder.
Core delivery steps
List every step in the programme delivery, in sequence, with the human or system responsible for each
Week 1: Module 1 video (pre-recorded, hosted on Vimeo). Week 1: Live Q&A call (founder, 60 min, Zoom). Week 1: Community post prompt (automated via ActiveCampaign).
Completion criteria
What constitutes completed delivery? What must the buyer have received for the offer to be fulfilled?
All 4 modules watched, both live calls attended (or replays accessed), and exit interview conducted.
Support infrastructure
What support channels exist? Who staffs them? What are the response time commitments?
Email support via [email protected] — 24-hour response. Community Q&A — community manager responds within 4 hours during business hours. Founder DMs — not a support channel.
Outcome delivery
What specific result must the delivery produce for the promise to be honoured?
Buyer can describe 3 specific pain points, has validated one offer idea with at least one conversation, and has a written MVO stack ready to test.
The written map follows the buyer from purchase to access, onboarding, core delivery, completion, support and outcome. Name the responsible person or system and the evidence that each handoff works. The source’s platforms, contact address and response times are examples, not a description of the actual RISER setup.
Completion of materials is not necessarily achievement of the promised result. Keep both visible. The onboarding example labels a Day 2 contact a seventy-two-hour check; clarify the intended timing before using it.
Phase 1 — Classify the offer and count all delivery time
Complete the ten-field classification record, then distinguish active work from the preparation, administration, revision and support that surround it.
Offer Classification Field
Your Data
Offer name and tier
Primary delivery model (Model 1–5)
Secondary delivery model (if hybrid)
Current active buyer count
Target buyer count at next scale event
Stress Test trigger (which pre-test event is causing this test to be run)
Top 3 stress vectors for this delivery model
1. 2. 3.
Last delivery failure experienced (if any)
Current founder hours per week spent on delivery
Current team hours per week spent on delivery
Total Delivery Time Formula Total Time = Active Time + Preparation Time + Administration Time + Revision Time + Support Time Example: A 60-minute coaching call has 15 min prep + 60 min delivery + 20 min notes/follow-up + 10 min scheduling = 105 minutes total per call, not 60.
Time Component
Definition
Typical Multiplier on Active Time
Example (60-min call)
Active delivery time
The actual time spent delivering value to the buyer face-to-face, on-screen, or via recorded content
1.0x (baseline)
60 minutes
Preparation time
Research, customisation, slide preparation, reading prior notes, setting up tools
Answering questions triggered by this specific module, call, or deliverable
0.15x–0.40x (higher for complex content)
9–24 minutes
TOTAL
Realistic total time per delivery unit
1.70x–2.50x active time
102–150 minutes per call
The Implication An operator who believes they can serve 20 buyers with 10 hours per week of delivery time — based on 30 minutes of active call time per buyer — is actually committing 51–75 hours per week when total delivery time is calculated correctly. This is how fulfilment collapses: not through sudden failure, but through the slow accumulation of miscalculated time commitments.
The original implication contains an arithmetic error. Twenty buyers receiving thirty minutes of active work each require ten active hours. Multiplying by the source’s 1.70–2.50 range gives seventeen-to-twenty-five total hours, not fifty-one-to-seventy-five. Preserve the original as evidence while using the corrected arithmetic in an exercise.
The earlier 105-minute call example adds preparation, the call, notes and scheduling but does not explicitly include revision or support. The multiplier range is a source estimate; actual tracking should determine the workload for this offer.
Phase 2 — Find the limiting resource
Read the five model formulas and examples, the thirteen-field worksheet and the buffer rule in full.
Delivery Model
Primary Capacity Constraint
Formula
Worked Example
Model 1 — Self-Paced Digital
Support bandwidth (tickets per buyer per day × hours to resolve × active buyers)
Capacity Ceiling = (Available weekly support hours) ÷ (Average tickets per buyer per week × average resolution time in hours)
10 hours/week support staff ÷ (0.8 tickets/buyer/week × 0.5 hours/ticket) = 10 ÷ 0.4 = 25 buyers maximum without support collapse
Model 2 — Live Group Cohort
Call quality ceiling (number of participants where group coaching remains effective) AND calendar capacity
Capacity Ceiling = MIN(call quality maximum, calendar capacity) Call quality max = 25–30 per call for complex topics, up to 50 for instructional delivery Calendar cap = Available live delivery hours ÷ hours per buyer per week
2 hours/week live delivery ÷ 0.1 hours/buyer/week on calls = 20 buyers on calls. Call quality max = 25. Ceiling = MIN(20,25) = 20 buyers
Model 3 — Done-With-You
Founder or team hours per week (the hardest ceiling in any service business)
Capacity Ceiling = Available DWY hours per week ÷ Total delivery time per buyer per week (using the 1.70–2.50x multiplier)
8 hours/week available ÷ (1.5 hours active × 2.0x multiplier = 3 hours total/buyer) = 2.67 → 2 buyers per week maximum
Model 4 — Done-For-You
Team labour hours AND revision cycle load
Capacity Ceiling = Available team hours per week ÷ Total delivery time per deliverable × average deliverables per buyer per week
40 team hours/week ÷ (4 hours per deliverable × 2.2x multiplier = 8.8 hours total) = 4.5 → 4 active client accounts maximum before quality breaks
Model 5 — Hybrid
Compound ceiling: calculate capacity for each component model and take the MINIMUM
Capacity Ceiling = MIN(ceiling for component 1, ceiling for component 2, ...)
Founder hours per week currently spent on delivery
Founder hours per week available for new buyers
Available team/contractor hours per week for delivery
Average support tickets per buyer per week (from current data)
Average resolution time per support ticket (hours)
Current active buyer count
Current weekly support hours consumed
Maximum group call size before quality degrades (Model 2 only)
Calculated Capacity Ceiling (using formula for your delivery model)
Current buyer count as % of Capacity Ceiling
Buffer target (recommended: operate at no more than 70% of ceiling to maintain quality)
70% of ceiling = ___
Headroom before ceiling is breached
Ceiling − Current buyers = ___
The 70% Buffer Rule The Capacity Ceiling is not a target — it is a hard limit. Operate at 70% of your ceiling maximum to maintain quality, absorb unexpected volume spikes, and preserve your own sanity. An offer with a ceiling of 30 active buyers should not have more than 21 active buyers at any one time without adding delivery capacity first.
For a self-paced example, ten support hours divided by 0.8 tickets per buyer times half an hour per ticket gives twenty-five buyers. The calculation needs hands-on resolution labour, not elapsed waiting time. For shared calls, a per-buyer allocation does not mean the call duration grows in exactly that proportion.
The done-for-you formula needs parentheses around total time per deliverable multiplied by deliverables per buyer per week. Dividing forty hours by 8.8 hours gives about 4.545 deliverables; the source’s four-client result assumes one deliverable per client in the same period. Preserve that missing assumption.
Simultaneous active buyers, new buyers per week and completed deliverables are different units. A hybrid minimum is meaningful only when component limits use compatible populations and periods. If components share the same staff hours, allocating those hours to each separately can overstate capacity.
The worksheet mixes remaining hours for new buyers with total capacity. Keep those separate. Raw headroom is ceiling minus current buyers; usable headroom under the source’s seventy-percent rule is smaller. A ceiling of thirty gives a twenty-one-buyer operating target under that convention, not a claim of measured safe capacity.
Phase 3 — Measure the whole week
Use the complete activity log and output worksheet. The native log has six categories, despite the checklist saying five. Its output table has six rows: four core metrics plus revised capacity and the estimate difference.
Activity Category
Sub-activity
Date
Start Time
End Time
Duration (min)
Buyer (if specific)
Notes
Pre-delivery prep
Call preparation
Pre-delivery prep
Content review
Pre-delivery prep
Tool setup
Active delivery
Live call
Active delivery
Module recording
Active delivery
Deliverable creation (DFY)
Post-delivery admin
Call notes / CRM update
Post-delivery admin
Recording upload / replay link
Post-delivery admin
Follow-up email
Support
Email reply
Support
Community post response
Support
Re-work / revision
Community management
Content moderation
Community management
Accountability checks
Scheduling & admin
Booking / rescheduling
WEEKLY TOTAL
Output Metric
Formula
Your Result
Total delivery hours per week (current buyer count)
Sum of all tracked hours across all categories
___ hours/week
Total delivery hours per active buyer per week
Total delivery hours ÷ current active buyer count
___ hours/buyer/week
Active-to-total time multiplier
Total delivery hours per buyer ÷ Active delivery time per buyer
___x (compare to the 1.70–2.50x benchmark)
Support hours as % of total delivery time
Total support hours ÷ Total delivery hours × 100
___% (benchmark: should be below 30%)
Revised Capacity Ceiling (using actual data)
Available weekly delivery hours ÷ Actual total hours per buyer per week
___ buyers maximum
Delta vs. original Capacity Ceiling estimate
Original estimate minus revised figure
___ buyers (positive = you overestimated capacity)
The Most Common Discovery Operators who run the Time-and-Motion Audit for the first time typically find their actual delivery time per buyer is 2.1–2.8x their original estimate, and their support hours account for 35–45% of total delivery time — well above the healthy 30% benchmark. This means their real Capacity Ceiling is 40–60% lower than they assumed. Finding this before a scale event is the entire purpose of the exercise.
Record each activity once. Revision appears under Support in the log but is a separate component earlier; choose a consistent classification so totals are not duplicated. The suggested fifteen-minute recording resolution needs a rounding rule for frequent short tasks. A week may miss onboarding peaks or later revisions.
The phase computes total time divided by active time, while the later schema describes actual divided by estimated time. Those ratios answer different questions. Zero buyers or zero active time also needs explicit treatment. The source’s typical discovery percentages are claims, not a substitute for this offer’s records.
Phase 4 — Keep the cost model’s units consistent
The cost worksheet contains twelve items plus totals. The model compares current, double and fivefold volumes using eleven metrics. Read both tables and the source’s margin and step-cost explanations.
Cost Item
Fixed or Variable?
Current Monthly Cost
Cost per Additional Buyer
Notes
Course platform (e.g. Kajabi)
Fixed
$___
~$0
Same cost regardless of buyer count until tier limit
Video hosting (e.g. Vimeo/Wistia)
Fixed (within plan)
$___
$0 to ~$2 near limits
Check bandwidth limits
Email platform
Variable (by list size)
$___
$___ per 1K subscribers
Track against buyer count
Community platform (Discord/Skool)
Fixed or Fixed+Variable
$___
$0–$5/mo per member
Skool charges per member
Zoom / call platform
Fixed
$___
$0 within licence
Check participant limits
Founder delivery time (valued at target hourly rate)
Variable
$___
$___ per buyer per week × ___/hr
Calculate at founder's target hourly rate
VA / contractor delivery support
Variable
$___
$___ per buyer per week × contractor rate
Community manager time
Variable (steps)
$___
$___ per N buyers
Add a part-time community manager at N buyers
Customer support time
Variable
$___
$___ per ticket × tickets per buyer
Payment processing
Variable
2.9% of revenue
2.9% of sale price
Fixed percentage
Physical fulfilment (Shock-and-Awe, if applicable)
Variable
$___
$___ per buyer
Postage + materials per package
Content / module updates (annualised)
Fixed
$___
$0
Depreciate over expected programme life
TOTAL FIXED MONTHLY
$___
TOTAL VARIABLE PER BUYER
$___
Metric
Current Volume
2x Volume
5x Volume
Active buyer count
___
___
___
Monthly gross revenue (buyers × price)
$___
$___
$___
Total variable costs (cost per buyer × buyer count)
$___
$___
$___
Total fixed costs (monthly)
$___
$___
$___
Total costs
$___
$___
$___
Gross margin (revenue − costs)
$___
$___
$___
Gross margin %
___%
___%
___%
Founder hours per week in delivery
___
___
___
Founder delivery as % of total available hours
___%
___%
___%
Support hours per week
___
___
___
Support as % of total delivery hours
___%
___%
___%
The Margin Death Zone Margin Death Zone = Volume point where (Variable Cost per Buyer × Buyers) + Fixed Costs > Revenue Find the buyer count where your margin turns negative. This is your absolute ceiling — not a quality ceiling but an economics ceiling. You must reach this number in the model BEFORE you reach it in production.
The Step-Cost Trap Fixed costs do not scale linearly. They scale in steps. Your Kajabi plan handles 50 students before you hit the tier limit and costs jump by $100/month. Your community manager handles 75 members before you need a second. Your Zoom licence handles 100 participants before you need a Business licence. Map every step-cost point in advance. The margin model should show each step as a cost jump, not a smooth curve.
Weekly labour, monthly subscriptions and a one-time course purchase cannot be combined without a defined period. Active buyers multiplied by the full price does not automatically equal monthly revenue. Support included in total delivery labour must not be added again as a separate cost without adjustment.
Founder time valued at a target rate is different from cash paid out. The source’s broad cost calculation is not automatically an accounting gross-margin figure. It does not fully model refunds, acquisition costs, taxes or currencies. Its platform prices and plan limits are examples that need actual current account data before operational use.
With positive constant contribution per buyer and fixed costs, margin can improve as volume grows. An upper point where margin becomes negative is not guaranteed to exist. Step costs, changing workload or capacity failures can alter the picture, but three sample volumes do not locate every crossing. Record no identified crossing rather than inventing one.
Phase 5 — Identify and mitigate single points of failure
The source distinguishes human, technology, content, process and access dependencies. Preserve every example, scoring band and remediation strategy below.
SPOF Category
Definition
Common Examples in Digital Offers
Human SPOF
A specific person — usually the founder — whose absence or incapacity halts delivery. The most common and most dangerous SPOF in any early-stage business.
Only the founder can run the live calls. Only one team member knows how to operate the course platform. Customer support has one person and no backup.
Technology SPOF
A single tool whose outage, shutdown, or price change would immediately break delivery for all buyers.
Video hosting platform goes down on call day. Payment processor blocks the account. Community platform announces closure. Email platform deliverability collapses.
Content SPOF
A single piece of content — typically a module, template, or tool — that is prerequisite to all subsequent delivery. If it is unavailable, the rest cannot proceed.
Module 1 is gated and all other modules depend on its completion. A single template file is the core deliverable and the only copy is on one person's local drive.
Process SPOF
A single manual step in the delivery process — performed by one person — that, if missed, prevents subsequent steps from occurring.
Manual Kajabi enrolment by a VA. Manually sending the Zoom link to each new buyer. Manually uploading recordings after each call.
Access SPOF
A single login credential or permission that, if lost or revoked, prevents access to tools or content.
Only one person has the Kajabi admin login. The Stripe account uses a personal email that only the founder can access. The domain registrar login is unknown.
Identified SPOF
Probability (1–5)
Impact (1–5)
Risk Score (P×I)
Action Required
Founder is only person who can run live calls
4
5
20
Only one copy of core template file (local drive)
3
4
12
Manual Kajabi enrolment by single VA
3
3
9
Video hosting platform — no backup CDN
2
5
10
Zoom account on personal email — no recovery
2
4
8
[Add your identified SPOFs here]
___
___
___
Risk Score
Classification
Action Required
Timeline
20–25 (Critical)
Immediate operational risk. This SPOF breaking during a live launch or at peak buyer volume would cause catastrophic delivery failure.
Eliminate or add full redundancy before the scale event. No exceptions.
Before any scale event — this blocks the scale gate
12–19 (High)
Significant risk. This SPOF breaking would cause major delivery disruption affecting 25%+ of active buyers.
Reduce probability or impact to below 12 before scale. Document recovery procedure.
Within 30 days before the scale event
6–11 (Medium)
Manageable risk. This SPOF breaking would cause disruption but delivery could continue at reduced capacity.
Document a recovery procedure. Assign a backup.
Within 60 days, or before the scale event if convenient
1–5 (Low)
Acceptable risk. This SPOF breaking would cause minor inconvenience with minimal buyer impact.
Monitor. No immediate action required.
Review quarterly
SPOF Type
Primary Remediation
Secondary Remediation
Minimum Standard Before Scale
Human SPOF (founder only)
Create and train a delivery backup: a team member or contractor who can run calls, manage community, and handle support for a minimum of 14 days.
Pre-record key delivery assets so that buyer experience is not degraded if live delivery is interrupted.
At least one trained backup person exists for every critical delivery function. Their training is documented and tested.
Technology SPOF (single tool)
Identify an alternative tool for each critical platform. Document the migration procedure.
Export all critical data from the tool monthly. Store in a location independent of the tool (Google Drive or local backup).
Migration procedure documented. At least one export test completed. Recovery time to alternative tool estimated and acceptable.
Content SPOF (single file)
All critical delivery files stored in minimum two locations: cloud storage (Google Drive) AND a backup location (different cloud provider or local).
File access shared with at least one team member. File names and locations documented in the delivery architecture map.
All files with Risk Score 12+ are stored in at least two locations with at least two people having access.
Process SPOF (manual step)
Automate the step using n8n, Make.com, or platform-native automation. Prioritise any manual step that occurs in every buyer's journey.
If automation is not immediately possible, create a written SOP for the step and assign a backup executor.
Every manual step in the buyer journey from purchase confirmation to first content access is automated or has a documented, tested backup executor.
Access SPOF (single credential)
Audit all platform logins. Move critical accounts to a shared team email (not a personal address). Store credentials in a team password manager (1Password, Bitwarden).
Document all critical logins in a secure, encrypted format with at least two authorised team members having access.
All platform logins for delivery-critical tools are stored in a shared password manager with at least two authorised users.
Probability times impact is a prioritization convention here, not a measured failure probability. The introduction says fifteen-plus requires immediate remediation, while the detailed bands identify twelve-plus as high and twenty-plus as critical. Later gates require all twelve-plus items resolved. Keep the differing rules visible.
Naming a backup tool or exporting data does not prove a restoration works. The source asks for tested people and procedures, with different fourteen-day and five-day absence horizons. Monthly exports and a ninety-day export test are also different requirements.
The source discusses shared accounts and password managers; those statements do not authorize account changes or disclosure. Actual access and recovery procedures require the organization’s permissions. Pre-recorded content may help during absence but does not automatically replace a promised live service.
Phase 6 — Project average and peak support demand
The formula, five delivery stages, four volume points and staffing gate follow in full.
Support Load Projection Formula Weekly Support Hours = Active Buyers × Average Tickets per Buyer per Week × Average Resolution Time (hours) At 50 buyers × 0.8 tickets/buyer/week × 0.5 hours/ticket = 20 hours/week of support. At 2x (100 buyers) = 40 hours/week — requires a dedicated part-time support role.
Delivery Stage
Typical Support Volume Multiplier
Primary Ticket Types
Staffing Implication
Week 1 (Onboarding)
2.5–4.0x baseline
Access issues, 'where do I start,' login problems, payment queries, expectation clarification
Heavy founder or senior support presence required. Do not schedule other high-demand activities in onboarding week.
Weeks 2–3 (Established rhythm)
0.6–0.8x baseline
Content questions, implementation help, community questions
Standard support staffing. VA or community manager can handle majority without escalation.
Module release days
1.8–3.0x baseline
New content questions, 'what does this mean,' technical playback issues
Pre-release support briefing required. Support staff must preview new content before buyer access.
Live call days
1.5–2.0x baseline
'I can't get in the Zoom,' replay requests, follow-up questions from call content
Live support coverage during call window. Zoom troubleshooting SOP must exist.
Final week / completion
1.2–1.8x baseline
'Did I complete?', certificate requests, testimonial fulfilment, what-to-do-next questions
Completion criteria must be clearly defined and visible. Automated completion confirmation reduces tickets significantly.
Volume Point
Active Buyers
Baseline Weekly Tickets
Peak Week Tickets (onboarding)
Weekly Support Hours (baseline)
Weekly Support Hours (peak)
Staffing Required
Current
___
___
___
___
___
___
2x current
___
___
___
___
___
___
5x current
___
___
___
___
___
___
At Capacity Ceiling
___
___
___
___
___
___
The Support Staffing Decision Gate Any scale event that would increase support load above the current team's available hours requires a staffing decision BEFORE the scale event — not after. Hiring or onboarding a VA after support has already collapsed produces 10–14 days of degraded buyer experience during the new hire's ramp time. Plan the hire to be trained and operational 2 weeks before the scale event.
Fifty buyers times 0.8 tickets per week times half an hour gives twenty support hours per week. One hundred buyers gives forty under unchanged assumptions. The formula is linear when those inputs are constant, despite the source’s broader claim of nonlinear growth. Change inputs only with a stated reason and evidence.
Onboarding, module releases and live calls can overlap. Do not multiply every peak factor without defining which buyers and periods it applies to. Forty hours described as part-time needs a staffing definition. Hiring lead times and the two-week readiness instruction are proposed planning rules, not staff already hired or trained.
Phase 7 — Walk through the doubled workload
The source explicitly calls this a thought experiment. Preserve all twelve questions and four interpretation rows.
Why 2x — Not 5x or 10x The purpose of the simulation is to find the first failure point — the step that breaks before all others. Most offers fail not at 10x but at 2x, because 2x is the first scale event most operators attempt (doubling ad spend, launching to an affiliate's list, opening a second cohort). If you can pass the 2x simulation cleanly, you have bought yourself a window to prepare for 5x.
Simulation Question
Current Reality
At 2x — What Happens?
Pass / Fail / Requires Prep
Can the purchase trigger (webhook, access grant, welcome email) handle 2x the transaction volume in a 24-hour window without errors?
___ purchases/day
___ purchases/day
Can the course platform (Kajabi/Teachable/etc.) serve 2x simultaneous users without degradation?
___ active sessions/day
___ active sessions/day
Can video hosting serve 2x simultaneous streams within the current plan?
___ streams/day
___ streams/day
Can the email platform deliver onboarding sequences to 2x the subscriber count without hitting sending limits?
___ emails/day
___ emails/day
Can live calls maintain the same quality at 2x the current participant count?
___ participants/call
___ participants/call
Does the founder's weekly delivery time at 2x stay within 70% of their total available hours?
___ hrs/week
___ hrs/week
Does the support team's weekly hours at 2x stay within their available capacity?
___ hrs/week
___ hrs/week
Does the community platform remain manageable for current community manager at 2x members?
___ members
___ members
Does gross margin remain above 50% at 2x buyer volume?
___% margin
___% margin
Are all Risk Score 12+ SPOFs remediated before 2x volume is reached?
___ SPOFs at 12+
Same list
Can onboarding be completed without any new manual steps at 2x?
___ manual steps
___ manual steps
Is there a trained delivery backup available if the founder is unavailable for 5+ days during a 2x-volume cohort?
Yes / No
Same requirement
Result
Interpretation
Action
All questions Pass
Delivery infrastructure is ready for a 2x scale event. Proceed with confidence.
Authorise scale event. Schedule a re-run of this simulation at 30 days post-scale to validate real-world performance.
1–2 questions Fail or Requires Prep
Delivery infrastructure has specific, identifiable gaps. Scale event should be delayed until gaps are remediated.
List each failing question. Assign an owner and deadline for remediation. Re-run the simulation after remediation. Do not proceed until clean pass.
3–5 questions Fail
Delivery infrastructure has systemic problems that cannot be patched quickly. The scale event risks producing a fulfilment breakdown.
Delay scale event by minimum 30 days. Address all failing questions in priority order. Consider a smaller scale test (1.3x or 1.5x) to build confidence incrementally.
6+ questions Fail
Delivery infrastructure is not ready to scale at all. The offer may need to be operated at current volume while delivery is rebuilt.
Do not scale. Review delivery architecture from the ground up. Identify whether the problem is a fixable capacity issue or a fundamental model mismatch.
Daily sessions or streams do not measure peak simultaneous demand, although some questions ask about concurrency. Doubling zero current buyers does not model a first launch, and a planned threefold campaign needs its own target assumptions. A paper Pass is not proof that the live service has been load-tested.
The simulation requires every question to pass before proceeding. Later scoring awards three points with one or two failures still being remediated. That can produce a high aggregate score despite a failed prerequisite. Keep unresolved requirements explicit rather than treating the total as permission to ignore them.
The margin question requires above fifty percent, the scorecard passes at forty-five-to-fifty-nine, and the master checklist says above forty-five. The founder seventy-percent rule also differs from warning bands later. Exact boundaries and the chosen decision rule need reconciliation. Three or more Requires Prep responses are not clearly classified by outcome rows that count only Fail.
Phase 8 — Review each tool dependency
The inventory has nine named tool examples plus a blank row. Preserve its fields and four review questions.
Tool Name
Delivery Function
Monthly Cost
Tier Limit Affecting Delivery
Last Outage (known)
Has Backup?
Backup Tool
Data Export Protocol
Kajabi / Teachable
Course delivery and member access
$___
___ student limit
Yes/No
Zoom / Google Meet
Live call delivery
$___
___ participant limit
Yes/No
ActiveCampaign / ConvertKit
Email sequence delivery
$___
___ subscriber limit
Yes/No
Vimeo / Wistia
Video hosting
$___
___ bandwidth/month
Yes/No
Discord / Skool
Community management
$___
___ member limit
Yes/No
Stripe / ThriveCart
Payment processing
2.9% + fees
N/A
Yes/No
Loom / Descript
Async video communication
$___
___ video limit
Yes/No
n8n / Make.com
Delivery automation
$___
___ operations/month
Yes/No
Calendly / Acuity
Call scheduling
$___
___ meeting types
Yes/No
[Add tools]
The Tool Risk Assessment
For each mission-critical tool (any tool whose failure would affect more than 20% of active buyers), answer these four questions:
What is the maximum downtime this tool has experienced in the last 12 months? Is that downtime acceptable given our delivery commitments?
What would happen if this tool increased its price by 50% tomorrow? Can the unit economics absorb it, and is there an alternative?
If this tool shut down with 30 days' notice, how long would migration take, and would active buyers experience degraded delivery during the migration?
Is all data held in this tool exportable to a neutral format (CSV, JSON, MP4) that can be imported into an alternative platform? Has this export been tested in the last 90 days?
Record actual plan limits, outages, export formats and migration needs. A tool affecting fewer than twenty percent of buyers can still be critical to those buyers, so the source’s cutoff does not establish harmlessness. Exportability is different from successful import and recovery. No listed alternative or price is verified as the current account configuration by this worksheet.
Phase 9 — Interpret the eleven dimensions without losing prerequisites
The eleven scores run from one to four, for a maximum of forty-four. Read every criterion and the decision table.
Dimension
What Is Measured
1 — Fail
2 — Warn
3 — Pass
4 — Strong
Score
Capacity Ceiling clarity
Is the ceiling calculated from actual data?
Not calculated
Estimated only
Calculated from 1 week audit
Calculated + validated in simulation
___
Time-and-Motion audit complete
Actual vs estimated delivery time
Not tracked
Rough estimates only
1 full week tracked
1 week tracked + multiplier calculated
___
Gross margin at 2x buyers
%margin at 2x volume
Below 30%
30–44%
45–59%
60%+
___
Founder delivery at 2x hours
Founder hours as % of available
Above 85%
70–85%
50–69%
Below 50%
___
SPOF audit complete
All risk 12+ SPOFs remediated
2+ SPOFs at 12+, unaddressed
1 SPOF at 12+, unaddressed
All 12+ SPOFs remediated
All 6+ SPOFs remediated + documented backup
___
Support load projected
Hours at 2x calculated
Not projected
Rough guess
Formally calculated
Calculated + staffing decision made
___
Support staffing at 2x
Is support team capacity sufficient?
Insufficient, no plan
Insufficient, plan underway
Sufficient with current team
Sufficient + backup trained
___
2x simulation result
Simulation pass rate
6+ questions Fail
3–5 Fail
1–2 Fail (remediation in progress)
All Pass
___
Tool dependency audit
All critical tools audited
Not completed
3+ tools without backup
1–2 tools without backup
All critical tools audited + backups confirmed
___
SPOF backup person exists
Trained backup for all human SPOFs
No backup for any role
Backup identified, not trained
Backup trained, not tested
Backup trained and tested
___
Delivery Architecture Map
Complete written map of all delivery steps
Not documented
Partial documentation
Full map documented
Full map + owner per step + timing
___
TOTAL SCORE
Maximum: 44 points | Go gate: 32+ | Any dimension scoring 1 blocks Go gate regardless of total
___
Score Range
Decision
Condition
Action
Any dimension = 1
NO-GO — Blocked
One or more critical failures regardless of total score
Address all dimension-1 items. Re-run scorecard after remediation.
0–31 (no dimension = 1)
NO-GO
Multiple weaknesses prevent safe scaling
Identify and remediate all dimensions below 3. Re-run in 30 days.
32–38
CONDITIONAL GO
Infrastructure is ready with monitoring
Scale with enhanced monitoring. Weekly scorecard check for 30 days post-scale.
Any one blocks the source’s gate. But a total of thirty-nine can still contain a two, including an unresolved staffing or failure-point issue. A thirty-two total can contain several. The separate all-pass, backup, capacity and remediation requirements remain relevant; the aggregate alone does not establish readiness.
With every dimension at least two, the minimum is twenty-two. The table’s zero-to-twenty-one range with no one is unreachable under valid inputs. Some percentage bands also leave fractional gaps without a rounding rule.
The scorecard labels an untested trained backup and one or two tools lacking backup as Pass, while other sections require tested or confirmed backups. Preserve the distinction between identified, planned, trained and tested. This lesson does not authorize a scale event.
Phase 10 — Assign and verify remediation
The four tiers prioritize critical failures, prerequisites before scaling, later capacity preparation and continuing maintenance. The full action register follows.
Priority Tier
Category
Criteria for This Tier
Typical Remediation Time
Tier 1 — Immediate (Block scale gate)
Critical SPOFs (Risk Score 20+) and any dimension-1 scorecard items
Any SPOF or scorecard item that would cause complete delivery failure. Non-negotiable. Must be resolved before any scale event.
1–14 days depending on complexity
Tier 2 — Before Scale Event
High SPOFs (Risk Score 12–19), negative margin at 2x, Capacity Ceiling below target scale volume
Infrastructure gaps that would cause significant degradation at the target scale volume. Must be resolved before the scale event.
14–30 days
Tier 3 — Within 30 Days Post-Scale
Medium SPOFs (Risk Score 6–11), support staffing for 5x volume, tool backups
Items that can be managed at 2x but would become critical at 5x. Build while scale event is live.
Items that improve resilience but do not block current operations.
Quarterly review cycle
Item
Source (Phase #)
Priority Tier
Owner
Deadline
Status
Verified By
Open / In Progress / Complete
Each item needs evidence, an owner, a deadline and a verification result. A plan marked in progress is not completed remediation. The third tier’s Within Thirty Days label differs from its thirty-to-sixty-day estimate. Negative margin and raw ceiling criteria are weaker than earlier margin and seventy-percent requirements; do not silently replace the stricter unresolved gates.
Review the model-specific failure guides
The source supplies four guides, for models one through four. All examples and remedies are preserved below. It does not supply a separate hybrid guide.
Delivery Model Quick Reference: Common Failure Points
Each delivery model has a distinct failure pattern. Use this quick reference when reviewing the 2x Simulation results or diagnosing post-launch delivery problems.
Model 1 — Self-Paced Digital: Where It Usually Breaks
• Video hosting CDN fails during a high-traffic day (e.g. after an email broadcast or affiliate promotion). Mitigation: use a CDN-backed host (Vimeo Pro, Wistia) and test load response before campaigns.
• Support volume from 'I can't find X' tickets overwhelms available hours within 72 hours of launch. Mitigation: add a pinned 'Start Here' navigation guide. Reduce first-access steps to one click.
• Community becomes a support forum rather than a learning community without active moderation above 30 members. Mitigation: hire or appoint a community manager before 30 members.
• Module completion tracking breaks when platform has a bug update. Mitigation: notify buyers of completions manually if platform fails. Have a backup completion tracking method.
Model 2 — Live Group Cohort: Where It Usually Breaks
• Founder's calendar becomes the hard ceiling. When a cohort of 25 runs simultaneously with a second cohort of 20, the founder is committed to more live delivery than they can perform at quality. Mitigation: cap cohort size. Open second cohort only after hiring a trained delivery backup.
• Call quality degrades above 25 participants for complex workshop formats. Above 25, questions queue up, personalisation disappears, and the format becomes a lecture rather than a coaching session. Mitigation: above 25, switch to small-group breakout calls rather than single large calls.
• Replay delivery breaks. Buyers who miss calls expect replays within 24 hours. If recording upload is a manual step, it will be late when the founder is busy. Mitigation: automate recording upload via Zoom cloud recording → auto-publish to course platform.
Model 3 — Done-With-You Intensive: Where It Usually Breaks
• Over-booking. The founder accepts one more booking than their total delivery hours allow, and every subsequent intensive is rushed. Mitigation: hard block the calendar. Maximum active intensives = Available DWY hours ÷ Total hours per intensive. No exceptions.
• Preparation shortcuts. When the founder is over-booked, they arrive at intensives without having reviewed the buyer's materials. Quality drops. Buyers notice. Mitigation: block preparation time on the calendar as a non-negotiable pre-intensive appointment — not optional.
• Rescheduling cascade. One rescheduled intensive pushes all subsequent sessions, creating a backlog. Mitigation: two rescheduling slots per calendar month held in reserve specifically for rescheduled intensives.
Model 4 — Done-For-You Service: Where It Usually Breaks
• Revision cycle explosion. Client count doubles; revision requests triple. Without a defined revision policy, the team spends 40% of their time on revisions rather than new work. Mitigation: define revision rounds in the contract (2 rounds included; additional rounds at hourly rate). Enforce it.
• Quality control bypass. Under volume pressure, deliverables skip the QA review and go directly to clients. Quality complaints follow. Mitigation: no deliverable leaves the business without completing the QA checklist. QA is a non-negotiable step, not an optional one.
• Client communication overhead. Active client count doubles; communication overhead increases by 3x because each client wants status updates. Mitigation: weekly automated status email per client. Reduces ad hoc 'where is my project?' enquiries by 60–70%.
For a hybrid exercise, examine each component and shared resources rather than assuming a missing guide exists. Moderator thresholds, group sizes, reserve slots, revision rounds and response improvements are source examples or claims, not existing RISER staffing or contract terms. Updating a replay script or describing an automation does not deploy a working recording flow.
Preserve the twenty-three-field database specification
The complete source schema follows. It records summary findings and dates, but does not define every worksheet or detailed evidence relationship.
Field
Type
Notes
Stress Test ID
Autonumber
Format: FST-[Year]-[Seq]
Offer
Link → Offers table
Test date
Date
Trigger event
Short text
What caused this test to be run
Delivery model
Single select
Model 1–5
Current active buyers
Number
Calculated Capacity Ceiling
Number
From Phase 2
Capacity utilisation (% of ceiling)
Formula
Current buyers / Ceiling × 100
Time-and-Motion multiplier
Number
Actual / estimated from Phase 3
Gross margin at 2x (%)
Number
From Phase 4 model
Margin death zone buyer count
Number
From Phase 4
SPOF audit: critical items (score 20+)
Number
Count of unaddressed 20+ SPOFs
SPOF audit: high items (score 12–19)
Number
Count of unaddressed 12–19 SPOFs
Support load at 2x (hours/week)
Number
From Phase 6
Support staffing gap
Number
Hours needed minus hours available at 2x
2x simulation pass rate (of 12 questions)
Number
How many of 12 simulation questions passed
Scorecard total score
Number
Out of 44
Go / No-Go decision
Single select
No-Go Blocked / No-Go / Conditional Go / Clear Go
Remediation items total
Number
Total items in remediation register
Remediation Tier 1 items
Number
Items requiring immediate action
Remediation completion date (estimated)
Date
When all Tier 1 and 2 items will be resolved
Scale event authorisation date
Date
Date scale event is cleared to proceed
Post-scale review date
Date
30 days after scale event
The introduction says the record links to remediation, but the schema lacks that link field. It also omits individual dimension scores and many supporting logs, costs, tool facts and stage projections. Keep the full worksheets with the summary. Autonumber formatting, date logic and division-by-zero handling require actual implementation. A database specification is not a working Airtable system.
Use the complete master checklist
Read the setup and all ten phase groups with the corrections and conflicts above. None of these source checkboxes is marked complete by appearing in the lesson.
Pre-Test Setup
☐ Delivery Architecture Map completed for the offer under review
☐ Delivery model classified (Model 1–5 or hybrid)
☐ Top 3 stress vectors identified for this delivery model
☐ All current delivery data pulled: buyer count, weekly hours, support tickets, refund rate
Phase 1 — Delivery Model Classification
☐ Delivery model confirmed and all component models listed if hybrid
☐ Current founder weekly delivery hours tracked (not estimated)
☐ Hidden time trap calculation run: active vs total delivery time per buyer
Phase 2 — Capacity Ceiling
☐ Capacity Ceiling calculated using the formula for the confirmed delivery model
☐ Capacity Ceiling worksheet completed with all input fields
☐ Current utilisation as percentage of ceiling calculated
☐ 70% buffer target set — scale gate blocked if current buyers exceed 70% of ceiling without capacity expansion
Phase 3 — Time-and-Motion Audit
☐ One full week of delivery time tracked across all five activity categories
☐ All four output metrics calculated: total hours/week, hours/buyer/week, multiplier, support as % of total
☐ Capacity Ceiling revised using actual (not estimated) data
☐ Delta between original and revised ceiling documented
Phase 4 — Margin Stress Test
☐ All delivery costs decomposed into fixed and variable components
☐ Margin model completed at current, 2x, and 5x buyer volumes
☐ Margin Death Zone buyer count identified
☐ Step-cost thresholds identified for all major fixed costs
☐ Gross margin at 2x above 45% (minimum threshold for scaling)
Phase 5 — SPOF Audit
☐ All elements of Delivery Architecture Map reviewed against 5 SPOF categories
☐ Every identified SPOF scored by Probability × Impact
☐ All Risk Score 20+ SPOFs addressed before scale gate authorised
☐ All Risk Score 12–19 SPOFs addressed or in remediation with deadline before scale event
☐ Recovery procedure documented for all Risk Score 6–11 SPOFs
Phase 6 — Support Load Projection
☐ Baseline tickets per buyer per week calculated from actual data
☐ Support load projection completed at 2x and 5x buyer volumes
☐ Support staffing decision made before scale event for any volume requiring additional hours
☐ Peak week (onboarding) support load modelled separately
Phase 7 — 2x Scale Simulation
☐ All 12 simulation questions answered with actual numbers
☐ Every 'Fail' answer documented with a specific remediation action and owner
☐ Simulation re-run after remediation — clean pass required before scale gate
Phase 8 — Tool Dependency Audit
☐ All delivery-critical tools listed in the Tool Dependency Inventory
☐ Four risk questions answered for each mission-critical tool
☐ All tools without a backup confirmed and backup documented
☐ Data export tested for all critical platforms in last 90 days
Phase 9 — Scorecard & Go/No-Go
☐ All 11 scorecard dimensions scored
☐ Total score calculated — 32+ required for Conditional Go
☐ Any dimension scoring 1 (Critical Failure) — scale gate blocked until remediated
☐ Go/No-Go decision documented in Airtable Stress Test Record
Phase 10 — Remediation & Post-Scale
☐ All remediation items logged in the Remediation Action Register with owner and deadline
☐ All Tier 1 items completed before scale event authorised
☐ All Tier 2 items completed before scale event authorised
☐ Post-scale 30-day review scheduled
☐ Stress Test Record filed in Airtable with all findings and decisions
Prepare one delivery map and a clearly labelled capacity exercise. Show the units, evidence, arithmetic, unknowns and conflicting rules. Identify which findings come from measured work and which are projections. Keep the result as course work for review; do not represent a paper exercise as authorization to change buyer commitments or launch traffic.
RISER NATION CORP — IF YOU AREN'T BUILDING, YOU ARE DESTROYING. Historical source branding remains preserved in the appendix.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — FULFILMENT STRESS TEST
The Systematic Protocol for Testing Whether You Can Deliver What You Promise — Before You Scale
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
Every operator stress tests their sales funnel — split testing headlines, optimising ad creatives, refining email sequences. Almost none stress test their fulfilment before scaling. The result is a business that sells faster than it can deliver: buyers wait longer than promised, quality degrades as volume increases, support teams collapse under ticket load, and a single bottleneck in the delivery chain produces a cascade of broken commitments.
The Fulfilment Stress Test is the systematic protocol for finding your delivery ceiling before you hit it in production. It defines exactly how many buyers you can serve simultaneously at the promised quality level, what your true cost per delivery is at various volumes, where your single points of failure live, how your support load scales with buyer volume, and whether your tools, team, and time can absorb a 2x increase in buyers without quality degradation.
Hormozi's Delivery Principle
The offer is the promise. The delivery is the proof. Your business's long-term value — its testimonials, its ascension rate, its referral velocity, its reputation in AI search results — is built entirely on whether delivery matches promise. A stress test protects the delivery before a scale event exposes its vulnerabilities.
Kennedy's Fulfilment Warning
The most dangerous moment in any business is the first successful campaign. You prove the market will buy — and then you find out whether you can actually serve them. The businesses that survive rapid growth are the ones that found their fulfilment ceiling in a controlled test, not in a live launch.
When This SOP Applies
Run a Fulfilment Stress Test before: the first paid ad campaign on any offer, any JV or affiliate launch expected to generate 3x or more your current buyer volume, any offer graduation from beta to full public launch, any price change that would significantly increase buyer volume, and any expansion into a new delivery format (e.g. moving from self-paced to live cohort).
Delivery Architecture: What You Are Testing
Fulfilment does not mean one thing. Before running any stress test, the complete delivery architecture for the offer under review must be mapped. A self-paced course has completely different stress points than a live cohort, which is completely different from a done-for-you service. This section defines the five delivery models, their primary stress vectors, and the architecture mapping protocol required before testing begins.
The Five Delivery Models
Delivery Model
Definition
Primary Stress Vectors
When It Breaks
Model 1
Self-Paced Digital
Course, template pack, or digital product consumed at the buyer's own pace with no live delivery component
Tech access reliability, video hosting load, download speeds, support volume from confused or stuck buyers, community management at scale
Video hosting CDN overloads under traffic spikes; support tickets multiply geometrically as buyer count grows; community becomes unmanageable without a moderator
Model 2
Live Group Cohort
Scheduled programme with live calls, group sessions, and a defined start/end date. All buyers progress together
Calendar capacity (founder cannot clone), call quality at scale (group coaching degrades above ~30 people per call), community activation between calls, recording and replay delivery
Founder's calendar becomes the hard ceiling; call quality degrades above 25–30 participants; community becomes a support forum rather than a learning environment without active management
Model 3
Done-With-You Intensive
High-touch delivery where the founder or team works directly with the buyer to implement the result — typically 1:1 or small group
Time per buyer (the hardest cap in the business), preparation quality, rescheduling protocols, delivery consistency across multiple intensive sessions
Founder's available hours per week is the absolute hard ceiling; one rescheduled session creates a cascade; quality degrades when preparation is rushed due to over-booking
Model 4
Done-For-You Service
The team delivers a specific output on behalf of the buyer — copy, design, automation, content, technical builds
Labour hours per deliverable, revision cycle load, quality control checkpoints, client communication frequency, project management overhead
Revision cycles multiply as client count increases; quality control breaks without a QA process; communication overhead consumes delivery time; margin erodes rapidly at scale without systems
Model 5
Hybrid
Combination of two or more delivery models (e.g. self-paced course + live monthly calls + DFY deliverable)
All stress vectors from each component model apply simultaneously; dependencies between components create additional failure points; support cannot be specialised
Complexity multiplies: a failure in one component stresses all others; buyer expectations for the live component affect perceived quality of the self-paced component
The Delivery Architecture Map
Before Phase 1 begins, complete a Delivery Architecture Map for the offer under review. This is a written inventory — not a diagram — of every step in the delivery process from purchase confirmation to result achievement. It identifies every human, tool, time commitment, and dependency in the chain.
Map Element
What to Document
Example
Purchase trigger
What happens in the first 60 seconds after payment is confirmed? Who or what is notified?
Stripe webhook triggers Kajabi to grant course access and ActiveCampaign to start onboarding sequence. Confirmation email sent automatically within 60 seconds.
Access delivery
How does the buyer access what they purchased? What platform, what credentials, what steps?
Kajabi sends login email with access link. Buyer must create password. Course appears in their dashboard. Access is instant — no manual steps.
Onboarding sequence
What guided experience does the buyer receive in the first 72 hours?
Day 0: Welcome email + 'your first step' instruction. Day 1: Module 1 access reminder + community invite. Day 2: 72-hour check-in from founder.
Core delivery steps
List every step in the programme delivery, in sequence, with the human or system responsible for each
Week 1: Module 1 video (pre-recorded, hosted on Vimeo). Week 1: Live Q&A call (founder, 60 min, Zoom). Week 1: Community post prompt (automated via ActiveCampaign).
Completion criteria
What constitutes completed delivery? What must the buyer have received for the offer to be fulfilled?
All 4 modules watched, both live calls attended (or replays accessed), and exit interview conducted.
Support infrastructure
What support channels exist? Who staffs them? What are the response time commitments?
Email support via [email protected] — 24-hour response. Community Q&A — community manager responds within 4 hours during business hours. Founder DMs — not a support channel.
Outcome delivery
What specific result must the delivery produce for the promise to be honoured?
Buyer can describe 3 specific pain points, has validated one offer idea with at least one conversation, and has a written MVO stack ready to test.
PHASE 1
Delivery Model Classification & Trigger Identification
Identifying which delivery model applies and which specific stress points to test
Classification Protocol
Classify the offer into one of the five delivery models above. If it is a hybrid, list all component models. Then identify the three highest-risk stress vectors for this specific offer. These become the primary targets for the subsequent phases.
Offer Classification Field
Your Data
Offer name and tier
Primary delivery model (Model 1–5)
Secondary delivery model (if hybrid)
Current active buyer count
Target buyer count at next scale event
Stress Test trigger (which pre-test event is causing this test to be run)
Top 3 stress vectors for this delivery model
1.
2.
3.
Last delivery failure experienced (if any)
Current founder hours per week spent on delivery
Current team hours per week spent on delivery
The Hidden Time Trap
The most common fulfilment miscalculation is confusing active delivery time with total delivery time. Operators calculate based on the work they can see — the 45-minute coaching call, the 30-minute module recording — and ignore all the surrounding work that makes that active time possible.
Total Delivery Time Formula
Total Time = Active Time + Preparation Time + Administration Time + Revision Time + Support Time
Example: A 60-minute coaching call has 15 min prep + 60 min delivery + 20 min notes/follow-up + 10 min scheduling = 105 minutes total per call, not 60.
Time Component
Definition
Typical Multiplier on Active Time
Example (60-min call)
Active delivery time
The actual time spent delivering value to the buyer face-to-face, on-screen, or via recorded content
1.0x (baseline)
60 minutes
Preparation time
Research, customisation, slide preparation, reading prior notes, setting up tools
Answering questions triggered by this specific module, call, or deliverable
0.15x–0.40x (higher for complex content)
9–24 minutes
TOTAL
Realistic total time per delivery unit
1.70x–2.50x active time
102–150 minutes per call
The Implication
An operator who believes they can serve 20 buyers with 10 hours per week of delivery time — based on 30 minutes of active call time per buyer — is actually committing 51–75 hours per week when total delivery time is calculated correctly. This is how fulfilment collapses: not through sudden failure, but through the slow accumulation of miscalculated time commitments.
PHASE 2
The Capacity Ceiling Calculation
Defining the maximum number of simultaneous buyers you can serve at promised quality — before testing begins
What Capacity Ceiling Means
The Capacity Ceiling is the maximum number of simultaneous active buyers that the current delivery infrastructure — your time, your team, your tools, your calendar, and your support system — can serve at the quality level your offer promises without degradation. Exceeding the capacity ceiling produces lower completion rates, higher refund rates, and support collapse.
Capacity Ceiling by Delivery Model
Delivery Model
Primary Capacity Constraint
Formula
Worked Example
Model 1 — Self-Paced Digital
Support bandwidth (tickets per buyer per day × hours to resolve × active buyers)
Capacity Ceiling = (Available weekly support hours) ÷ (Average tickets per buyer per week × average resolution time in hours)
10 hours/week support staff ÷ (0.8 tickets/buyer/week × 0.5 hours/ticket) = 10 ÷ 0.4 = 25 buyers maximum without support collapse
Model 2 — Live Group Cohort
Call quality ceiling (number of participants where group coaching remains effective) AND calendar capacity
Capacity Ceiling = MIN(call quality maximum, calendar capacity)
Call quality max = 25–30 per call for complex topics, up to 50 for instructional delivery
Calendar cap = Available live delivery hours ÷ hours per buyer per week
2 hours/week live delivery ÷ 0.1 hours/buyer/week on calls = 20 buyers on calls. Call quality max = 25. Ceiling = MIN(20,25) = 20 buyers
Model 3 — Done-With-You
Founder or team hours per week (the hardest ceiling in any service business)
Capacity Ceiling = Available DWY hours per week ÷ Total delivery time per buyer per week (using the 1.70–2.50x multiplier)
8 hours/week available ÷ (1.5 hours active × 2.0x multiplier = 3 hours total/buyer) = 2.67 → 2 buyers per week maximum
Model 4 — Done-For-You
Team labour hours AND revision cycle load
Capacity Ceiling = Available team hours per week ÷ Total delivery time per deliverable × average deliverables per buyer per week
40 team hours/week ÷ (4 hours per deliverable × 2.2x multiplier = 8.8 hours total) = 4.5 → 4 active client accounts maximum before quality breaks
Model 5 — Hybrid
Compound ceiling: calculate capacity for each component model and take the MINIMUM
Capacity Ceiling = MIN(ceiling for component 1, ceiling for component 2, ...)
Founder hours per week currently spent on delivery
Founder hours per week available for new buyers
Available team/contractor hours per week for delivery
Average support tickets per buyer per week (from current data)
Average resolution time per support ticket (hours)
Current active buyer count
Current weekly support hours consumed
Maximum group call size before quality degrades (Model 2 only)
Calculated Capacity Ceiling (using formula for your delivery model)
Current buyer count as % of Capacity Ceiling
Buffer target (recommended: operate at no more than 70% of ceiling to maintain quality)
70% of ceiling = ___
Headroom before ceiling is breached
Ceiling − Current buyers = ___
The 70% Buffer Rule
The Capacity Ceiling is not a target — it is a hard limit. Operate at 70% of your ceiling maximum to maintain quality, absorb unexpected volume spikes, and preserve your own sanity. An offer with a ceiling of 30 active buyers should not have more than 21 active buyers at any one time without adding delivery capacity first.
PHASE 3
The Time-and-Motion Audit
Measuring what delivery actually costs in time — not what you think it costs
The Audit Protocol
The Time-and-Motion Audit requires one week of tracked delivery data. Every delivery activity is logged with its actual time from start to completion — including all preparation, administration, revision, and support time associated with it. The goal is to produce an accurate Total Delivery Time per buyer per week that replaces the estimated figure used in the Capacity Ceiling calculation.
The Time Tracking Template
Log every delivery-related activity for one full week using this template. Track in Toggl, Clockify, or a simple spreadsheet. Minimum tracking resolution: 15-minute increments.
Activity Category
Sub-activity
Date
Start Time
End Time
Duration (min)
Buyer (if specific)
Notes
Pre-delivery prep
Call preparation
Pre-delivery prep
Content review
Pre-delivery prep
Tool setup
Active delivery
Live call
Active delivery
Module recording
Active delivery
Deliverable creation (DFY)
Post-delivery admin
Call notes / CRM update
Post-delivery admin
Recording upload / replay link
Post-delivery admin
Follow-up email
Support
Email reply
Support
Community post response
Support
Re-work / revision
Community management
Content moderation
Community management
Accountability checks
Scheduling & admin
Booking / rescheduling
WEEKLY TOTAL
Audit Output Calculations
After one week of tracking, calculate the following four figures. These replace your estimates in the Capacity Ceiling calculation and feed directly into the Margin Stress Test.
Output Metric
Formula
Your Result
Total delivery hours per week (current buyer count)
Sum of all tracked hours across all categories
___ hours/week
Total delivery hours per active buyer per week
Total delivery hours ÷ current active buyer count
___ hours/buyer/week
Active-to-total time multiplier
Total delivery hours per buyer ÷ Active delivery time per buyer
___x (compare to the 1.70–2.50x benchmark)
Support hours as % of total delivery time
Total support hours ÷ Total delivery hours × 100
___% (benchmark: should be below 30%)
Revised Capacity Ceiling (using actual data)
Available weekly delivery hours ÷ Actual total hours per buyer per week
___ buyers maximum
Delta vs. original Capacity Ceiling estimate
Original estimate minus revised figure
___ buyers (positive = you overestimated capacity)
The Most Common Discovery
Operators who run the Time-and-Motion Audit for the first time typically find their actual delivery time per buyer is 2.1–2.8x their original estimate, and their support hours account for 35–45% of total delivery time — well above the healthy 30% benchmark. This means their real Capacity Ceiling is 40–60% lower than they assumed. Finding this before a scale event is the entire purpose of the exercise.
PHASE 4
The Margin Stress Test
How does your profit margin change as buyer volume increases — and where does it break?
Why Margin Changes at Scale
The margin on an offer is not fixed. It changes as buyer volume increases because variable costs — support, delivery time, tool usage, revision cycles — scale with buyers while fixed costs — platform fees, software, team retainers — scale in steps. The Margin Stress Test models your margin at three volume points: current, 2x, and 5x buyers.
The Cost Structure Decomposition
Before running the stress model, decompose every cost associated with delivery into fixed and variable components.
Cost Item
Fixed or Variable?
Current Monthly Cost
Cost per Additional Buyer
Notes
Course platform (e.g. Kajabi)
Fixed
$___
~$0
Same cost regardless of buyer count until tier limit
Video hosting (e.g. Vimeo/Wistia)
Fixed (within plan)
$___
$0 to ~$2 near limits
Check bandwidth limits
Email platform
Variable (by list size)
$___
$___ per 1K subscribers
Track against buyer count
Community platform (Discord/Skool)
Fixed or Fixed+Variable
$___
$0–$5/mo per member
Skool charges per member
Zoom / call platform
Fixed
$___
$0 within licence
Check participant limits
Founder delivery time (valued at target hourly rate)
Variable
$___
$___ per buyer per week × ___/hr
Calculate at founder's target hourly rate
VA / contractor delivery support
Variable
$___
$___ per buyer per week × contractor rate
Community manager time
Variable (steps)
$___
$___ per N buyers
Add a part-time community manager at N buyers
Customer support time
Variable
$___
$___ per ticket × tickets per buyer
Payment processing
Variable
2.9% of revenue
2.9% of sale price
Fixed percentage
Physical fulfilment (Shock-and-Awe, if applicable)
Variable
$___
$___ per buyer
Postage + materials per package
Content / module updates (annualised)
Fixed
$___
$0
Depreciate over expected programme life
TOTAL FIXED MONTHLY
$___
TOTAL VARIABLE PER BUYER
$___
The Margin Model at Three Volume Points
Metric
Current Volume
2x Volume
5x Volume
Active buyer count
___
___
___
Monthly gross revenue (buyers × price)
$___
$___
$___
Total variable costs (cost per buyer × buyer count)
$___
$___
$___
Total fixed costs (monthly)
$___
$___
$___
Total costs
$___
$___
$___
Gross margin (revenue − costs)
$___
$___
$___
Gross margin %
___%
___%
___%
Founder hours per week in delivery
___
___
___
Founder delivery as % of total available hours
___%
___%
___%
Support hours per week
___
___
___
Support as % of total delivery hours
___%
___%
___%
The Margin Death Zone
Margin Death Zone = Volume point where (Variable Cost per Buyer × Buyers) + Fixed Costs > Revenue
Find the buyer count where your margin turns negative. This is your absolute ceiling — not a quality ceiling but an economics ceiling. You must reach this number in the model BEFORE you reach it in production.
The Step-Cost Trap
Fixed costs do not scale linearly. They scale in steps. Your Kajabi plan handles 50 students before you hit the tier limit and costs jump by $100/month. Your community manager handles 75 members before you need a second. Your Zoom licence handles 100 participants before you need a Business licence. Map every step-cost point in advance. The margin model should show each step as a cost jump, not a smooth curve.
PHASE 5
The Single Point of Failure Audit
Finding every place in your delivery chain where one break stops everything
What a Single Point of Failure Is
A Single Point of Failure (SPOF) is any element of your delivery infrastructure whose failure would immediately prevent you from delivering the promise to some or all active buyers. SPOFs are not theoretical — they are operational realities that every delivery system contains. The audit's job is to find them, score them by risk, and either eliminate them or build redundancy.
The SPOF Categories
SPOF Category
Definition
Common Examples in Digital Offers
Human SPOF
A specific person — usually the founder — whose absence or incapacity halts delivery. The most common and most dangerous SPOF in any early-stage business.
Only the founder can run the live calls. Only one team member knows how to operate the course platform. Customer support has one person and no backup.
Technology SPOF
A single tool whose outage, shutdown, or price change would immediately break delivery for all buyers.
Video hosting platform goes down on call day. Payment processor blocks the account. Community platform announces closure. Email platform deliverability collapses.
Content SPOF
A single piece of content — typically a module, template, or tool — that is prerequisite to all subsequent delivery. If it is unavailable, the rest cannot proceed.
Module 1 is gated and all other modules depend on its completion. A single template file is the core deliverable and the only copy is on one person's local drive.
Process SPOF
A single manual step in the delivery process — performed by one person — that, if missed, prevents subsequent steps from occurring.
Manual Kajabi enrolment by a VA. Manually sending the Zoom link to each new buyer. Manually uploading recordings after each call.
Access SPOF
A single login credential or permission that, if lost or revoked, prevents access to tools or content.
Only one person has the Kajabi admin login. The Stripe account uses a personal email that only the founder can access. The domain registrar login is unknown.
The SPOF Risk Matrix
Audit every element of your Delivery Architecture Map against the five SPOF categories. Score each identified SPOF by Probability (1=unlikely to 5=almost certain) and Impact (1=minor disruption to 5=complete delivery stoppage). Risk Score = Probability × Impact. Scores of 15+ require immediate remediation before the scale event.
Identified SPOF
Probability
(1–5)
Impact
(1–5)
Risk Score
(P×I)
Action Required
Founder is only person who can run live calls
4
5
20
Only one copy of core template file (local drive)
3
4
12
Manual Kajabi enrolment by single VA
3
3
9
Video hosting platform — no backup CDN
2
5
10
Zoom account on personal email — no recovery
2
4
8
[Add your identified SPOFs here]
___
___
___
Risk Score Thresholds
Risk Score
Classification
Action Required
Timeline
20–25 (Critical)
Immediate operational risk. This SPOF breaking during a live launch or at peak buyer volume would cause catastrophic delivery failure.
Eliminate or add full redundancy before the scale event. No exceptions.
Before any scale event — this blocks the scale gate
12–19 (High)
Significant risk. This SPOF breaking would cause major delivery disruption affecting 25%+ of active buyers.
Reduce probability or impact to below 12 before scale. Document recovery procedure.
Within 30 days before the scale event
6–11 (Medium)
Manageable risk. This SPOF breaking would cause disruption but delivery could continue at reduced capacity.
Document a recovery procedure. Assign a backup.
Within 60 days, or before the scale event if convenient
1–5 (Low)
Acceptable risk. This SPOF breaking would cause minor inconvenience with minimal buyer impact.
Monitor. No immediate action required.
Review quarterly
SPOF Remediation Strategies
SPOF Type
Primary Remediation
Secondary Remediation
Minimum Standard Before Scale
Human SPOF (founder only)
Create and train a delivery backup: a team member or contractor who can run calls, manage community, and handle support for a minimum of 14 days.
Pre-record key delivery assets so that buyer experience is not degraded if live delivery is interrupted.
At least one trained backup person exists for every critical delivery function. Their training is documented and tested.
Technology SPOF (single tool)
Identify an alternative tool for each critical platform. Document the migration procedure.
Export all critical data from the tool monthly. Store in a location independent of the tool (Google Drive or local backup).
Migration procedure documented. At least one export test completed. Recovery time to alternative tool estimated and acceptable.
Content SPOF (single file)
All critical delivery files stored in minimum two locations: cloud storage (Google Drive) AND a backup location (different cloud provider or local).
File access shared with at least one team member. File names and locations documented in the delivery architecture map.
All files with Risk Score 12+ are stored in at least two locations with at least two people having access.
Process SPOF (manual step)
Automate the step using n8n, Make.com, or platform-native automation. Prioritise any manual step that occurs in every buyer's journey.
If automation is not immediately possible, create a written SOP for the step and assign a backup executor.
Every manual step in the buyer journey from purchase confirmation to first content access is automated or has a documented, tested backup executor.
Access SPOF (single credential)
Audit all platform logins. Move critical accounts to a shared team email (not a personal address). Store credentials in a team password manager (1Password, Bitwarden).
Document all critical logins in a secure, encrypted format with at least two authorised team members having access.
All platform logins for delivery-critical tools are stored in a shared password manager with at least two authorised users.
PHASE 6
The Support Load Projection
Calculating your support requirements at scale before scale reveals them painfully
The Support Load Formula
Support load is the most consistently underestimated delivery cost in digital offers. It scales with buyer count but not linearly — it scales faster than linearly for complex offers and slower for simple self-paced products. The formula below produces a projection of weekly support hours at any buyer volume.
Support Load Projection Formula
Weekly Support Hours = Active Buyers × Average Tickets per Buyer per Week × Average Resolution Time (hours)
At 50 buyers × 0.8 tickets/buyer/week × 0.5 hours/ticket = 20 hours/week of support. At 2x (100 buyers) = 40 hours/week — requires a dedicated part-time support role.
Support Load by Delivery Stage
Support load is not constant throughout a programme. It peaks sharply in the first week (onboarding confusion), drops in weeks 2–3 (established rhythm), and spikes again at any new module release or live call. This pattern must be accounted for in staffing projections.
Delivery Stage
Typical Support Volume Multiplier
Primary Ticket Types
Staffing Implication
Week 1 (Onboarding)
2.5–4.0x baseline
Access issues, 'where do I start,' login problems, payment queries, expectation clarification
Heavy founder or senior support presence required. Do not schedule other high-demand activities in onboarding week.
Weeks 2–3 (Established rhythm)
0.6–0.8x baseline
Content questions, implementation help, community questions
Standard support staffing. VA or community manager can handle majority without escalation.
Module release days
1.8–3.0x baseline
New content questions, 'what does this mean,' technical playback issues
Pre-release support briefing required. Support staff must preview new content before buyer access.
Live call days
1.5–2.0x baseline
'I can't get in the Zoom,' replay requests, follow-up questions from call content
Live support coverage during call window. Zoom troubleshooting SOP must exist.
Final week / completion
1.2–1.8x baseline
'Did I complete?', certificate requests, testimonial fulfilment, what-to-do-next questions
Completion criteria must be clearly defined and visible. Automated completion confirmation reduces tickets significantly.
Support Load Projection at Scale
Volume Point
Active Buyers
Baseline Weekly Tickets
Peak Week Tickets (onboarding)
Weekly Support Hours (baseline)
Weekly Support Hours (peak)
Staffing Required
Current
___
___
___
___
___
___
2x current
___
___
___
___
___
___
5x current
___
___
___
___
___
___
At Capacity Ceiling
___
___
___
___
___
___
The Support Staffing Decision Gate
Any scale event that would increase support load above the current team's available hours requires a staffing decision BEFORE the scale event — not after. Hiring or onboarding a VA after support has already collapsed produces 10–14 days of degraded buyer experience during the new hire's ramp time. Plan the hire to be trained and operational 2 weeks before the scale event.
PHASE 7
The 2x Scale Simulation
Walking through a doubled buyer volume mentally before experiencing it physically
What the 2x Simulation Is
The 2x Scale Simulation is a structured thought experiment and paper exercise that walks through every step of your delivery architecture assuming twice your current active buyer count. It does not require real buyers — it requires rigorous honesty about what would happen if you had them. Every capacity constraint, every manual step, every tool limit, and every human dependency is stress-tested against 2x volume.
Why 2x — Not 5x or 10x
The purpose of the simulation is to find the first failure point — the step that breaks before all others. Most offers fail not at 10x but at 2x, because 2x is the first scale event most operators attempt (doubling ad spend, launching to an affiliate's list, opening a second cohort). If you can pass the 2x simulation cleanly, you have bought yourself a window to prepare for 5x.
The 2x Simulation Script
Run through each delivery step below with your actual numbers doubled. Write the answer to each question. A 'No' answer to any question identifies a remediation priority.
Simulation Question
Current Reality
At 2x — What Happens?
Pass / Fail / Requires Prep
Can the purchase trigger (webhook, access grant, welcome email) handle 2x the transaction volume in a 24-hour window without errors?
___ purchases/day
___ purchases/day
Can the course platform (Kajabi/Teachable/etc.) serve 2x simultaneous users without degradation?
___ active sessions/day
___ active sessions/day
Can video hosting serve 2x simultaneous streams within the current plan?
___ streams/day
___ streams/day
Can the email platform deliver onboarding sequences to 2x the subscriber count without hitting sending limits?
___ emails/day
___ emails/day
Can live calls maintain the same quality at 2x the current participant count?
___ participants/call
___ participants/call
Does the founder's weekly delivery time at 2x stay within 70% of their total available hours?
___ hrs/week
___ hrs/week
Does the support team's weekly hours at 2x stay within their available capacity?
___ hrs/week
___ hrs/week
Does the community platform remain manageable for current community manager at 2x members?
___ members
___ members
Does gross margin remain above 50% at 2x buyer volume?
___% margin
___% margin
Are all Risk Score 12+ SPOFs remediated before 2x volume is reached?
___ SPOFs at 12+
Same list
Can onboarding be completed without any new manual steps at 2x?
___ manual steps
___ manual steps
Is there a trained delivery backup available if the founder is unavailable for 5+ days during a 2x-volume cohort?
Yes / No
Same requirement
2x Simulation Result Interpretation
Result
Interpretation
Action
All questions Pass
Delivery infrastructure is ready for a 2x scale event. Proceed with confidence.
Authorise scale event. Schedule a re-run of this simulation at 30 days post-scale to validate real-world performance.
1–2 questions Fail or Requires Prep
Delivery infrastructure has specific, identifiable gaps. Scale event should be delayed until gaps are remediated.
List each failing question. Assign an owner and deadline for remediation. Re-run the simulation after remediation. Do not proceed until clean pass.
3–5 questions Fail
Delivery infrastructure has systemic problems that cannot be patched quickly. The scale event risks producing a fulfilment breakdown.
Delay scale event by minimum 30 days. Address all failing questions in priority order. Consider a smaller scale test (1.3x or 1.5x) to build confidence incrementally.
6+ questions Fail
Delivery infrastructure is not ready to scale at all. The offer may need to be operated at current volume while delivery is rebuilt.
Do not scale. Review delivery architecture from the ground up. Identify whether the problem is a fixable capacity issue or a fundamental model mismatch.
PHASE 8
The Technology & Tool Dependency Audit
Every tool you depend on is a risk you are carrying — audit it
The Tool Dependency Inventory
Every tool in your delivery stack is a dependency. When it changes pricing, reduces functionality, experiences downtime, or shuts down, your delivery is affected. The Tool Dependency Audit documents every tool, its role in delivery, its risk profile, and the mitigation in place.
Tool Name
Delivery Function
Monthly Cost
Tier Limit Affecting Delivery
Last Outage (known)
Has Backup?
Backup Tool
Data Export Protocol
Kajabi / Teachable
Course delivery and member access
$___
___ student limit
Yes/No
Zoom / Google Meet
Live call delivery
$___
___ participant limit
Yes/No
ActiveCampaign / ConvertKit
Email sequence delivery
$___
___ subscriber limit
Yes/No
Vimeo / Wistia
Video hosting
$___
___ bandwidth/month
Yes/No
Discord / Skool
Community management
$___
___ member limit
Yes/No
Stripe / ThriveCart
Payment processing
2.9% + fees
N/A
Yes/No
Loom / Descript
Async video communication
$___
___ video limit
Yes/No
n8n / Make.com
Delivery automation
$___
___ operations/month
Yes/No
Calendly / Acuity
Call scheduling
$___
___ meeting types
Yes/No
[Add tools]
The Tool Risk Assessment
For each mission-critical tool (any tool whose failure would affect more than 20% of active buyers), answer these four questions:
1. What is the maximum downtime this tool has experienced in the last 12 months? Is that downtime acceptable given our delivery commitments?
2. What would happen if this tool increased its price by 50% tomorrow? Can the unit economics absorb it, and is there an alternative?
3. If this tool shut down with 30 days' notice, how long would migration take, and would active buyers experience degraded delivery during the migration?
4. Is all data held in this tool exportable to a neutral format (CSV, JSON, MP4) that can be imported into an alternative platform? Has this export been tested in the last 90 days?
PHASE 9
The Fulfilment Stress Test Scorecard
The integrated scoring system across all eight phases
Scorecard Purpose
The Fulfilment Stress Test Scorecard integrates findings from all eight phases into a single Go/No-Go decision. Each dimension is scored 1 (fail) through 4 (excellent). A total score of 32 or above clears the Go gate. Any individual dimension scoring 1 (Critical Failure) blocks the gate regardless of total score.
Dimension
What Is Measured
1 — Fail
2 — Warn
3 — Pass
4 — Strong
Score
Capacity Ceiling clarity
Is the ceiling calculated from actual data?
Not calculated
Estimated only
Calculated from 1 week audit
Calculated + validated in simulation
___
Time-and-Motion audit complete
Actual vs estimated delivery time
Not tracked
Rough estimates only
1 full week tracked
1 week tracked + multiplier calculated
___
Gross margin at 2x buyers
%margin at 2x volume
Below 30%
30–44%
45–59%
60%+
___
Founder delivery at 2x hours
Founder hours as % of available
Above 85%
70–85%
50–69%
Below 50%
___
SPOF audit complete
All risk 12+ SPOFs remediated
2+ SPOFs at 12+, unaddressed
1 SPOF at 12+, unaddressed
All 12+ SPOFs remediated
All 6+ SPOFs remediated + documented backup
___
Support load projected
Hours at 2x calculated
Not projected
Rough guess
Formally calculated
Calculated + staffing decision made
___
Support staffing at 2x
Is support team capacity sufficient?
Insufficient, no plan
Insufficient, plan underway
Sufficient with current team
Sufficient + backup trained
___
2x simulation result
Simulation pass rate
6+ questions Fail
3–5 Fail
1–2 Fail (remediation in progress)
All Pass
___
Tool dependency audit
All critical tools audited
Not completed
3+ tools without backup
1–2 tools without backup
All critical tools audited + backups confirmed
___
SPOF backup person exists
Trained backup for all human SPOFs
No backup for any role
Backup identified, not trained
Backup trained, not tested
Backup trained and tested
___
Delivery Architecture Map
Complete written map of all delivery steps
Not documented
Partial documentation
Full map documented
Full map + owner per step + timing
___
TOTAL SCORE
Maximum: 44 points | Go gate: 32+ | Any dimension scoring 1 blocks Go gate regardless of total
___
Go / No-Go Decision
Score Range
Decision
Condition
Action
Any dimension = 1
NO-GO — Blocked
One or more critical failures regardless of total score
Address all dimension-1 items. Re-run scorecard after remediation.
0–31 (no dimension = 1)
NO-GO
Multiple weaknesses prevent safe scaling
Identify and remediate all dimensions below 3. Re-run in 30 days.
32–38
CONDITIONAL GO
Infrastructure is ready with monitoring
Scale with enhanced monitoring. Weekly scorecard check for 30 days post-scale.
Turning scorecard findings into an ordered action plan
The Remediation Ordering Principle
Not all remediation items are equal. The ordering principle is: fix the highest-risk SPOFs first (because they can cause complete delivery stoppage), then address the margin death zone (because it determines scalability), then fix the capacity ceiling constraints (because they determine how many buyers you can serve), then build support infrastructure (because it determines buyer experience at scale).
Priority Tier
Category
Criteria for This Tier
Typical Remediation Time
Tier 1 — Immediate
(Block scale gate)
Critical SPOFs (Risk Score 20+) and any dimension-1 scorecard items
Any SPOF or scorecard item that would cause complete delivery failure. Non-negotiable. Must be resolved before any scale event.
1–14 days depending on complexity
Tier 2 — Before Scale Event
High SPOFs (Risk Score 12–19), negative margin at 2x, Capacity Ceiling below target scale volume
Infrastructure gaps that would cause significant degradation at the target scale volume. Must be resolved before the scale event.
14–30 days
Tier 3 — Within 30 Days Post-Scale
Medium SPOFs (Risk Score 6–11), support staffing for 5x volume, tool backups
Items that can be managed at 2x but would become critical at 5x. Build while scale event is live.
Items that improve resilience but do not block current operations.
Quarterly review cycle
Remediation Action Register
For each identified remediation item, complete one row of this register. Assign a single owner per item. No item without a named owner and a deadline is a real commitment.
Item
Source
(Phase #)
Priority
Tier
Owner
Deadline
Status
Verified By
Open / In Progress / Complete
Delivery Model Quick Reference: Common Failure Points
Each delivery model has a distinct failure pattern. Use this quick reference when reviewing the 2x Simulation results or diagnosing post-launch delivery problems.
Model 1 — Self-Paced Digital: Where It Usually Breaks
• Video hosting CDN fails during a high-traffic day (e.g. after an email broadcast or affiliate promotion). Mitigation: use a CDN-backed host (Vimeo Pro, Wistia) and test load response before campaigns.
• Support volume from 'I can't find X' tickets overwhelms available hours within 72 hours of launch. Mitigation: add a pinned 'Start Here' navigation guide. Reduce first-access steps to one click.
• Community becomes a support forum rather than a learning community without active moderation above 30 members. Mitigation: hire or appoint a community manager before 30 members.
• Module completion tracking breaks when platform has a bug update. Mitigation: notify buyers of completions manually if platform fails. Have a backup completion tracking method.
Model 2 — Live Group Cohort: Where It Usually Breaks
• Founder's calendar becomes the hard ceiling. When a cohort of 25 runs simultaneously with a second cohort of 20, the founder is committed to more live delivery than they can perform at quality. Mitigation: cap cohort size. Open second cohort only after hiring a trained delivery backup.
• Call quality degrades above 25 participants for complex workshop formats. Above 25, questions queue up, personalisation disappears, and the format becomes a lecture rather than a coaching session. Mitigation: above 25, switch to small-group breakout calls rather than single large calls.
• Replay delivery breaks. Buyers who miss calls expect replays within 24 hours. If recording upload is a manual step, it will be late when the founder is busy. Mitigation: automate recording upload via Zoom cloud recording → auto-publish to course platform.
Model 3 — Done-With-You Intensive: Where It Usually Breaks
• Over-booking. The founder accepts one more booking than their total delivery hours allow, and every subsequent intensive is rushed. Mitigation: hard block the calendar. Maximum active intensives = Available DWY hours ÷ Total hours per intensive. No exceptions.
• Preparation shortcuts. When the founder is over-booked, they arrive at intensives without having reviewed the buyer's materials. Quality drops. Buyers notice. Mitigation: block preparation time on the calendar as a non-negotiable pre-intensive appointment — not optional.
• Rescheduling cascade. One rescheduled intensive pushes all subsequent sessions, creating a backlog. Mitigation: two rescheduling slots per calendar month held in reserve specifically for rescheduled intensives.
Model 4 — Done-For-You Service: Where It Usually Breaks
• Revision cycle explosion. Client count doubles; revision requests triple. Without a defined revision policy, the team spends 40% of their time on revisions rather than new work. Mitigation: define revision rounds in the contract (2 rounds included; additional rounds at hourly rate). Enforce it.
• Quality control bypass. Under volume pressure, deliverables skip the QA review and go directly to clients. Quality complaints follow. Mitigation: no deliverable leaves the business without completing the QA checklist. QA is a non-negotiable step, not an optional one.
• Client communication overhead. Active client count doubles; communication overhead increases by 3x because each client wants status updates. Mitigation: weekly automated status email per client. Reduces ad hoc 'where is my project?' enquiries by 60–70%.
Fulfilment Stress Test Database — Airtable Schema
Table 1 — Stress Test Records
One record per completed stress test. Linked to the Offers table and the Remediation Register.
Field
Type
Notes
Stress Test ID
Autonumber
Format: FST-[Year]-[Seq]
Offer
Link → Offers table
Test date
Date
Trigger event
Short text
What caused this test to be run
Delivery model
Single select
Model 1–5
Current active buyers
Number
Calculated Capacity Ceiling
Number
From Phase 2
Capacity utilisation (% of ceiling)
Formula
Current buyers / Ceiling × 100
Time-and-Motion multiplier
Number
Actual / estimated from Phase 3
Gross margin at 2x (%)
Number
From Phase 4 model
Margin death zone buyer count
Number
From Phase 4
SPOF audit: critical items (score 20+)
Number
Count of unaddressed 20+ SPOFs
SPOF audit: high items (score 12–19)
Number
Count of unaddressed 12–19 SPOFs
Support load at 2x (hours/week)
Number
From Phase 6
Support staffing gap
Number
Hours needed minus hours available at 2x
2x simulation pass rate (of 12 questions)
Number
How many of 12 simulation questions passed
Scorecard total score
Number
Out of 44
Go / No-Go decision
Single select
No-Go Blocked / No-Go / Conditional Go / Clear Go
Remediation items total
Number
Total items in remediation register
Remediation Tier 1 items
Number
Items requiring immediate action
Remediation completion date (estimated)
Date
When all Tier 1 and 2 items will be resolved
Scale event authorisation date
Date
Date scale event is cleared to proceed
Post-scale review date
Date
30 days after scale event
Master Fulfilment Stress Test Checklist
Pre-Test Setup
☐ Delivery Architecture Map completed for the offer under review
☐ Delivery model classified (Model 1–5 or hybrid)
☐ Top 3 stress vectors identified for this delivery model
☐ All current delivery data pulled: buyer count, weekly hours, support tickets, refund rate
Phase 1 — Delivery Model Classification
☐ Delivery model confirmed and all component models listed if hybrid
☐ Current founder weekly delivery hours tracked (not estimated)
☐ Hidden time trap calculation run: active vs total delivery time per buyer
Phase 2 — Capacity Ceiling
☐ Capacity Ceiling calculated using the formula for the confirmed delivery model
☐ Capacity Ceiling worksheet completed with all input fields
☐ Current utilisation as percentage of ceiling calculated
☐ 70% buffer target set — scale gate blocked if current buyers exceed 70% of ceiling without capacity expansion
Phase 3 — Time-and-Motion Audit
☐ One full week of delivery time tracked across all five activity categories
☐ All four output metrics calculated: total hours/week, hours/buyer/week, multiplier, support as % of total
☐ Capacity Ceiling revised using actual (not estimated) data
☐ Delta between original and revised ceiling documented
Phase 4 — Margin Stress Test
☐ All delivery costs decomposed into fixed and variable components
☐ Margin model completed at current, 2x, and 5x buyer volumes
☐ Margin Death Zone buyer count identified
☐ Step-cost thresholds identified for all major fixed costs
☐ Gross margin at 2x above 45% (minimum threshold for scaling)
Phase 5 — SPOF Audit
☐ All elements of Delivery Architecture Map reviewed against 5 SPOF categories
☐ Every identified SPOF scored by Probability × Impact
☐ All Risk Score 20+ SPOFs addressed before scale gate authorised
☐ All Risk Score 12–19 SPOFs addressed or in remediation with deadline before scale event
☐ Recovery procedure documented for all Risk Score 6–11 SPOFs
Phase 6 — Support Load Projection
☐ Baseline tickets per buyer per week calculated from actual data
☐ Support load projection completed at 2x and 5x buyer volumes
☐ Support staffing decision made before scale event for any volume requiring additional hours
☐ Peak week (onboarding) support load modelled separately
Phase 7 — 2x Scale Simulation
☐ All 12 simulation questions answered with actual numbers
☐ Every 'Fail' answer documented with a specific remediation action and owner
☐ Simulation re-run after remediation — clean pass required before scale gate
Phase 8 — Tool Dependency Audit
☐ All delivery-critical tools listed in the Tool Dependency Inventory
☐ Four risk questions answered for each mission-critical tool
☐ All tools without a backup confirmed and backup documented
☐ Data export tested for all critical platforms in last 90 days
Phase 9 — Scorecard & Go/No-Go
☐ All 11 scorecard dimensions scored
☐ Total score calculated — 32+ required for Conditional Go
☐ Any dimension scoring 1 (Critical Failure) — scale gate blocked until remediated
☐ Go/No-Go decision documented in Airtable Stress Test Record
Phase 10 — Remediation & Post-Scale
☐ All remediation items logged in the Remediation Action Register with owner and deadline
☐ All Tier 1 items completed before scale event authorised
☐ All Tier 2 items completed before scale event authorised
☐ Post-scale 30-day review scheduled
☐ Stress Test Record filed in Airtable with all findings and decisions
RISER Nation Master Operating System | Fulfilment Stress Test SOP | Version 1.0 | 2026 Edition
Kennedy × Hormozi × Brunson | risernation.com
word/header1.xml
RISER Nation | Fulfilment Stress Test SOP | V1.0
word/footer1.xml
Page PAGE of NUMPAGES
word/footnotes.xml
word/endnotes.xml
word/comments.xml
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — FULFILMENT STRESS TEST ",
"",
"The Systematic Protocol for Testing Whether You Can Deliver What You Promise — Before You Scale",
"Kennedy × Hormozi × Brunson × 2026 Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"Every operator stress tests their sales funnel — split testing headlines, optimising ad creatives, refining email sequences. Almost none stress test their fulfilment before scaling. The result is a business that sells faster than it can deliver: buyers wait longer than promised, quality degrades as volume increases, support teams collapse under ticket load, and a single bottleneck in the delivery chain produces a cascade of broken commitments.",
"",
"The Fulfilment Stress Test is the systematic protocol for finding your delivery ceiling before you hit it in production. It defines exactly how many buyers you can serve simultaneously at the promised quality level, what your true cost per delivery is at various volumes, where your single points of failure live, how your support load scales with buyer volume, and whether your tools, team, and time can absorb a 2x increase in buyers without quality degradation.",
"",
"Hormozi's Delivery Principle",
"The offer is the promise. The delivery is the proof. Your business's long-term value — its testimonials, its ascension rate, its referral velocity, its reputation in AI search results — is built entirely on whether delivery matches promise. A stress test protects the delivery before a scale event exposes its vulnerabilities.",
"",
"Kennedy's Fulfilment Warning",
"The most dangerous moment in any business is the first successful campaign. You prove the market will buy — and then you find out whether you can actually serve them. The businesses that survive rapid growth are the ones that found their fulfilment ceiling in a controlled test, not in a live launch.",
"",
"When This SOP Applies",
"Run a Fulfilment Stress Test before: the first paid ad campaign on any offer, any JV or affiliate launch expected to generate 3x or more your current buyer volume, any offer graduation from beta to full public launch, any price change that would significantly increase buyer volume, and any expansion into a new delivery format (e.g. moving from self-paced to live cohort).",
"",
"Delivery Architecture: What You Are Testing",
"Fulfilment does not mean one thing. Before running any stress test, the complete delivery architecture for the offer under review must be mapped. A self-paced course has completely different stress points than a live cohort, which is completely different from a done-for-you service. This section defines the five delivery models, their primary stress vectors, and the architecture mapping protocol required before testing begins.",
"",
"The Five Delivery Models",
"Delivery Model",
"Definition",
"Primary Stress Vectors",
"When It Breaks",
"Model 1\nSelf-Paced Digital",
"Course, template pack, or digital product consumed at the buyer's own pace with no live delivery component",
"Tech access reliability, video hosting load, download speeds, support volume from confused or stuck buyers, community management at scale",
"Video hosting CDN overloads under traffic spikes; support tickets multiply geometrically as buyer count grows; community becomes unmanageable without a moderator",
"Model 2\nLive Group Cohort",
"Scheduled programme with live calls, group sessions, and a defined start/end date. All buyers progress together",
"Calendar capacity (founder cannot clone), call quality at scale (group coaching degrades above ~30 people per call), community activation between calls, recording and replay delivery",
"Founder's calendar becomes the hard ceiling; call quality degrades above 25–30 participants; community becomes a support forum rather than a learning environment without active management",
"Model 3\nDone-With-You Intensive",
"High-touch delivery where the founder or team works directly with the buyer to implement the result — typically 1:1 or small group",
"Time per buyer (the hardest cap in the business), preparation quality, rescheduling protocols, delivery consistency across multiple intensive sessions",
"Founder's available hours per week is the absolute hard ceiling; one rescheduled session creates a cascade; quality degrades when preparation is rushed due to over-booking",
"Model 4\nDone-For-You Service",
"The team delivers a specific output on behalf of the buyer — copy, design, automation, content, technical builds",
"Labour hours per deliverable, revision cycle load, quality control checkpoints, client communication frequency, project management overhead",
"Revision cycles multiply as client count increases; quality control breaks without a QA process; communication overhead consumes delivery time; margin erodes rapidly at scale without systems",
"Model 5\nHybrid",
"Combination of two or more delivery models (e.g. self-paced course + live monthly calls + DFY deliverable)",
"All stress vectors from each component model apply simultaneously; dependencies between components create additional failure points; support cannot be specialised",
"Complexity multiplies: a failure in one component stresses all others; buyer expectations for the live component affect perceived quality of the self-paced component",
"",
"The Delivery Architecture Map",
"Before Phase 1 begins, complete a Delivery Architecture Map for the offer under review. This is a written inventory — not a diagram — of every step in the delivery process from purchase confirmation to result achievement. It identifies every human, tool, time commitment, and dependency in the chain.",
"",
"Map Element",
"What to Document",
"Example",
"Purchase trigger",
"What happens in the first 60 seconds after payment is confirmed? Who or what is notified?",
"Stripe webhook triggers Kajabi to grant course access and ActiveCampaign to start onboarding sequence. Confirmation email sent automatically within 60 seconds.",
"Access delivery",
"How does the buyer access what they purchased? What platform, what credentials, what steps?",
"Kajabi sends login email with access link. Buyer must create password. Course appears in their dashboard. Access is instant — no manual steps.",
"Onboarding sequence",
"What guided experience does the buyer receive in the first 72 hours?",
"Day 0: Welcome email + 'your first step' instruction. Day 1: Module 1 access reminder + community invite. Day 2: 72-hour check-in from founder.",
"Core delivery steps",
"List every step in the programme delivery, in sequence, with the human or system responsible for each",
"Week 1: Module 1 video (pre-recorded, hosted on Vimeo). Week 1: Live Q&A call (founder, 60 min, Zoom). Week 1: Community post prompt (automated via ActiveCampaign).",
"Completion criteria",
"What constitutes completed delivery? What must the buyer have received for the offer to be fulfilled?",
"All 4 modules watched, both live calls attended (or replays accessed), and exit interview conducted.",
"Support infrastructure",
"What support channels exist? Who staffs them? What are the response time commitments?",
"Email support via [email protected] — 24-hour response. Community Q&A — community manager responds within 4 hours during business hours. Founder DMs — not a support channel.",
"Outcome delivery",
"What specific result must the delivery produce for the promise to be honoured?",
"Buyer can describe 3 specific pain points, has validated one offer idea with at least one conversation, and has a written MVO stack ready to test.",
"",
"",
"PHASE 1",
"Delivery Model Classification & Trigger Identification",
"Identifying which delivery model applies and which specific stress points to test",
"",
"Classification Protocol",
"Classify the offer into one of the five delivery models above. If it is a hybrid, list all component models. Then identify the three highest-risk stress vectors for this specific offer. These become the primary targets for the subsequent phases.",
"",
"Offer Classification Field",
"Your Data",
"Offer name and tier",
"",
"Primary delivery model (Model 1–5)",
"",
"Secondary delivery model (if hybrid)",
"",
"Current active buyer count",
"",
"Target buyer count at next scale event",
"",
"Stress Test trigger (which pre-test event is causing this test to be run)",
"",
"Top 3 stress vectors for this delivery model",
"1.\n2.\n3.",
"Last delivery failure experienced (if any)",
"",
"Current founder hours per week spent on delivery",
"",
"Current team hours per week spent on delivery",
"",
"",
"The Hidden Time Trap",
"The most common fulfilment miscalculation is confusing active delivery time with total delivery time. Operators calculate based on the work they can see — the 45-minute coaching call, the 30-minute module recording — and ignore all the surrounding work that makes that active time possible.",
"",
"Total Delivery Time Formula",
"Total Time = Active Time + Preparation Time + Administration Time + Revision Time + Support Time",
"Example: A 60-minute coaching call has 15 min prep + 60 min delivery + 20 min notes/follow-up + 10 min scheduling = 105 minutes total per call, not 60.",
"",
"Time Component",
"Definition",
"Typical Multiplier on Active Time",
"Example (60-min call)",
"Active delivery time",
"The actual time spent delivering value to the buyer face-to-face, on-screen, or via recorded content",
"1.0x (baseline)",
"60 minutes",
"Preparation time",
"Research, customisation, slide preparation, reading prior notes, setting up tools",
"0.25x–0.50x depending on personalisation level",
"15–30 minutes",
"Administration time",
"Notes, follow-up emails, CRM updates, recording uploads, replay links, scheduling",
"0.20x–0.35x",
"12–21 minutes",
"Revision and correction time",
"Handling re-records, content updates, delivery mistakes, technical failures",
"0.10x–0.25x (higher for DFY)",
"6–15 minutes",
"Support time attributable to this delivery step",
"Answering questions triggered by this specific module, call, or deliverable",
"0.15x–0.40x (higher for complex content)",
"9–24 minutes",
"TOTAL",
"Realistic total time per delivery unit",
"1.70x–2.50x active time",
"102–150 minutes per call",
"",
"The Implication",
"An operator who believes they can serve 20 buyers with 10 hours per week of delivery time — based on 30 minutes of active call time per buyer — is actually committing 51–75 hours per week when total delivery time is calculated correctly. This is how fulfilment collapses: not through sudden failure, but through the slow accumulation of miscalculated time commitments.",
"",
"",
"PHASE 2",
"The Capacity Ceiling Calculation",
"Defining the maximum number of simultaneous buyers you can serve at promised quality — before testing begins",
"",
"What Capacity Ceiling Means",
"The Capacity Ceiling is the maximum number of simultaneous active buyers that the current delivery infrastructure — your time, your team, your tools, your calendar, and your support system — can serve at the quality level your offer promises without degradation. Exceeding the capacity ceiling produces lower completion rates, higher refund rates, and support collapse.",
"",
"Capacity Ceiling by Delivery Model",
"Delivery Model",
"Primary Capacity Constraint",
"Formula",
"Worked Example",
"Model 1 — Self-Paced Digital",
"Support bandwidth (tickets per buyer per day × hours to resolve × active buyers)",
"Capacity Ceiling = (Available weekly support hours) ÷ (Average tickets per buyer per week × average resolution time in hours)",
"10 hours/week support staff ÷ (0.8 tickets/buyer/week × 0.5 hours/ticket) = 10 ÷ 0.4 = 25 buyers maximum without support collapse",
"Model 2 — Live Group Cohort",
"Call quality ceiling (number of participants where group coaching remains effective) AND calendar capacity",
"Capacity Ceiling = MIN(call quality maximum, calendar capacity)\nCall quality max = 25–30 per call for complex topics, up to 50 for instructional delivery\nCalendar cap = Available live delivery hours ÷ hours per buyer per week",
"2 hours/week live delivery ÷ 0.1 hours/buyer/week on calls = 20 buyers on calls. Call quality max = 25. Ceiling = MIN(20,25) = 20 buyers",
"Model 3 — Done-With-You",
"Founder or team hours per week (the hardest ceiling in any service business)",
"Capacity Ceiling = Available DWY hours per week ÷ Total delivery time per buyer per week (using the 1.70–2.50x multiplier)",
"8 hours/week available ÷ (1.5 hours active × 2.0x multiplier = 3 hours total/buyer) = 2.67 → 2 buyers per week maximum",
"Model 4 — Done-For-You",
"Team labour hours AND revision cycle load",
"Capacity Ceiling = Available team hours per week ÷ Total delivery time per deliverable × average deliverables per buyer per week",
"40 team hours/week ÷ (4 hours per deliverable × 2.2x multiplier = 8.8 hours total) = 4.5 → 4 active client accounts maximum before quality breaks",
"Model 5 — Hybrid",
"Compound ceiling: calculate capacity for each component model and take the MINIMUM",
"Capacity Ceiling = MIN(ceiling for component 1, ceiling for component 2, ...)",
"Self-paced ceiling = 80 buyers. Live calls ceiling = 25 buyers. DFY component ceiling = 8 buyers. Hybrid ceiling = MIN(80,25,8) = 8 buyers",
"",
"Your Capacity Ceiling Worksheet",
"Input Field",
"Value",
"Available founder hours per week (total)",
"",
"Founder hours per week currently spent on delivery",
"",
"Founder hours per week available for new buyers",
"",
"Available team/contractor hours per week for delivery",
"",
"Average support tickets per buyer per week (from current data)",
"",
"Average resolution time per support ticket (hours)",
"",
"Current active buyer count",
"",
"Current weekly support hours consumed",
"",
"Maximum group call size before quality degrades (Model 2 only)",
"",
"Calculated Capacity Ceiling (using formula for your delivery model)",
"",
"Current buyer count as % of Capacity Ceiling",
"",
"Buffer target (recommended: operate at no more than 70% of ceiling to maintain quality)",
"70% of ceiling = ___",
"Headroom before ceiling is breached",
"Ceiling − Current buyers = ___",
"",
"The 70% Buffer Rule",
"The Capacity Ceiling is not a target — it is a hard limit. Operate at 70% of your ceiling maximum to maintain quality, absorb unexpected volume spikes, and preserve your own sanity. An offer with a ceiling of 30 active buyers should not have more than 21 active buyers at any one time without adding delivery capacity first.",
"",
"",
"PHASE 3",
"The Time-and-Motion Audit",
"Measuring what delivery actually costs in time — not what you think it costs",
"",
"The Audit Protocol",
"The Time-and-Motion Audit requires one week of tracked delivery data. Every delivery activity is logged with its actual time from start to completion — including all preparation, administration, revision, and support time associated with it. The goal is to produce an accurate Total Delivery Time per buyer per week that replaces the estimated figure used in the Capacity Ceiling calculation.",
"",
"The Time Tracking Template",
"Log every delivery-related activity for one full week using this template. Track in Toggl, Clockify, or a simple spreadsheet. Minimum tracking resolution: 15-minute increments.",
"",
"Activity Category",
"Sub-activity",
"Date",
"Start Time",
"End Time",
"Duration (min)",
"Buyer (if specific)",
"Notes",
"Pre-delivery prep",
"Call preparation",
"",
"",
"",
"",
"",
"",
"Pre-delivery prep",
"Content review",
"",
"",
"",
"",
"",
"",
"Pre-delivery prep",
"Tool setup",
"",
"",
"",
"",
"",
"",
"Active delivery",
"Live call",
"",
"",
"",
"",
"",
"",
"Active delivery",
"Module recording",
"",
"",
"",
"",
"",
"",
"Active delivery",
"Deliverable creation (DFY)",
"",
"",
"",
"",
"",
"",
"Post-delivery admin",
"Call notes / CRM update",
"",
"",
"",
"",
"",
"",
"Post-delivery admin",
"Recording upload / replay link",
"",
"",
"",
"",
"",
"",
"Post-delivery admin",
"Follow-up email",
"",
"",
"",
"",
"",
"",
"Support",
"Email reply",
"",
"",
"",
"",
"",
"",
"Support",
"Community post response",
"",
"",
"",
"",
"",
"",
"Support",
"Re-work / revision",
"",
"",
"",
"",
"",
"",
"Community management",
"Content moderation",
"",
"",
"",
"",
"",
"",
"Community management",
"Accountability checks",
"",
"",
"",
"",
"",
"",
"Scheduling & admin",
"Booking / rescheduling",
"",
"",
"",
"",
"",
"",
"WEEKLY TOTAL",
"",
"",
"",
"",
"",
"",
"",
"",
"Audit Output Calculations",
"After one week of tracking, calculate the following four figures. These replace your estimates in the Capacity Ceiling calculation and feed directly into the Margin Stress Test.",
"",
"Output Metric",
"Formula",
"Your Result",
"Total delivery hours per week (current buyer count)",
"Sum of all tracked hours across all categories",
"___ hours/week",
"Total delivery hours per active buyer per week",
"Total delivery hours ÷ current active buyer count",
"___ hours/buyer/week",
"Active-to-total time multiplier",
"Total delivery hours per buyer ÷ Active delivery time per buyer",
"___x (compare to the 1.70–2.50x benchmark)",
"Support hours as % of total delivery time",
"Total support hours ÷ Total delivery hours × 100",
"___% (benchmark: should be below 30%)",
"Revised Capacity Ceiling (using actual data)",
"Available weekly delivery hours ÷ Actual total hours per buyer per week",
"___ buyers maximum",
"Delta vs. original Capacity Ceiling estimate",
"Original estimate minus revised figure",
"___ buyers (positive = you overestimated capacity)",
"",
"The Most Common Discovery",
"Operators who run the Time-and-Motion Audit for the first time typically find their actual delivery time per buyer is 2.1–2.8x their original estimate, and their support hours account for 35–45% of total delivery time — well above the healthy 30% benchmark. This means their real Capacity Ceiling is 40–60% lower than they assumed. Finding this before a scale event is the entire purpose of the exercise.",
"",
"",
"PHASE 4",
"The Margin Stress Test",
"How does your profit margin change as buyer volume increases — and where does it break?",
"",
"Why Margin Changes at Scale",
"The margin on an offer is not fixed. It changes as buyer volume increases because variable costs — support, delivery time, tool usage, revision cycles — scale with buyers while fixed costs — platform fees, software, team retainers — scale in steps. The Margin Stress Test models your margin at three volume points: current, 2x, and 5x buyers.",
"",
"The Cost Structure Decomposition",
"Before running the stress model, decompose every cost associated with delivery into fixed and variable components.",
"",
"Cost Item",
"Fixed or Variable?",
"Current Monthly Cost",
"Cost per Additional Buyer",
"Notes",
"Course platform (e.g. Kajabi)",
"Fixed",
"$___",
"~$0",
"Same cost regardless of buyer count until tier limit",
"Video hosting (e.g. Vimeo/Wistia)",
"Fixed (within plan)",
"$___",
"$0 to ~$2 near limits",
"Check bandwidth limits",
"Email platform",
"Variable (by list size)",
"$___",
"$___ per 1K subscribers",
"Track against buyer count",
"Community platform (Discord/Skool)",
"Fixed or Fixed+Variable",
"$___",
"$0–$5/mo per member",
"Skool charges per member",
"Zoom / call platform",
"Fixed",
"$___",
"$0 within licence",
"Check participant limits",
"Founder delivery time (valued at target hourly rate)",
"Variable",
"$___",
"$___ per buyer per week × ___/hr",
"Calculate at founder's target hourly rate",
"VA / contractor delivery support",
"Variable",
"$___",
"$___ per buyer per week × contractor rate",
"",
"Community manager time",
"Variable (steps)",
"$___",
"$___ per N buyers",
"Add a part-time community manager at N buyers",
"Customer support time",
"Variable",
"$___",
"$___ per ticket × tickets per buyer",
"",
"Payment processing",
"Variable",
"2.9% of revenue",
"2.9% of sale price",
"Fixed percentage",
"Physical fulfilment (Shock-and-Awe, if applicable)",
"Variable",
"$___",
"$___ per buyer",
"Postage + materials per package",
"Content / module updates (annualised)",
"Fixed",
"$___",
"$0",
"Depreciate over expected programme life",
"TOTAL FIXED MONTHLY",
"",
"$___",
"",
"",
"TOTAL VARIABLE PER BUYER",
"",
"",
"$___",
"",
"",
"The Margin Model at Three Volume Points",
"",
"Metric",
"Current Volume",
"2x Volume",
"5x Volume",
"Active buyer count",
"___",
"___",
"___",
"Monthly gross revenue (buyers × price)",
"$___",
"$___",
"$___",
"Total variable costs (cost per buyer × buyer count)",
"$___",
"$___",
"$___",
"Total fixed costs (monthly)",
"$___",
"$___",
"$___",
"Total costs",
"$___",
"$___",
"$___",
"Gross margin (revenue − costs)",
"$___",
"$___",
"$___",
"Gross margin %",
"___%",
"___%",
"___%",
"Founder hours per week in delivery",
"___",
"___",
"___",
"Founder delivery as % of total available hours",
"___%",
"___%",
"___%",
"Support hours per week",
"___",
"___",
"___",
"Support as % of total delivery hours",
"___%",
"___%",
"___%",
"",
"The Margin Death Zone",
"Margin Death Zone = Volume point where (Variable Cost per Buyer × Buyers) + Fixed Costs > Revenue",
"Find the buyer count where your margin turns negative. This is your absolute ceiling — not a quality ceiling but an economics ceiling. You must reach this number in the model BEFORE you reach it in production.",
"",
"The Step-Cost Trap",
"Fixed costs do not scale linearly. They scale in steps. Your Kajabi plan handles 50 students before you hit the tier limit and costs jump by $100/month. Your community manager handles 75 members before you need a second. Your Zoom licence handles 100 participants before you need a Business licence. Map every step-cost point in advance. The margin model should show each step as a cost jump, not a smooth curve.",
"",
"",
"PHASE 5",
"The Single Point of Failure Audit",
"Finding every place in your delivery chain where one break stops everything",
"",
"What a Single Point of Failure Is",
"A Single Point of Failure (SPOF) is any element of your delivery infrastructure whose failure would immediately prevent you from delivering the promise to some or all active buyers. SPOFs are not theoretical — they are operational realities that every delivery system contains. The audit's job is to find them, score them by risk, and either eliminate them or build redundancy.",
"",
"The SPOF Categories",
"SPOF Category",
"Definition",
"Common Examples in Digital Offers",
"Human SPOF",
"A specific person — usually the founder — whose absence or incapacity halts delivery. The most common and most dangerous SPOF in any early-stage business.",
"Only the founder can run the live calls. Only one team member knows how to operate the course platform. Customer support has one person and no backup.",
"Technology SPOF",
"A single tool whose outage, shutdown, or price change would immediately break delivery for all buyers.",
"Video hosting platform goes down on call day. Payment processor blocks the account. Community platform announces closure. Email platform deliverability collapses.",
"Content SPOF",
"A single piece of content — typically a module, template, or tool — that is prerequisite to all subsequent delivery. If it is unavailable, the rest cannot proceed.",
"Module 1 is gated and all other modules depend on its completion. A single template file is the core deliverable and the only copy is on one person's local drive.",
"Process SPOF",
"A single manual step in the delivery process — performed by one person — that, if missed, prevents subsequent steps from occurring.",
"Manual Kajabi enrolment by a VA. Manually sending the Zoom link to each new buyer. Manually uploading recordings after each call.",
"Access SPOF",
"A single login credential or permission that, if lost or revoked, prevents access to tools or content.",
"Only one person has the Kajabi admin login. The Stripe account uses a personal email that only the founder can access. The domain registrar login is unknown.",
"",
"The SPOF Risk Matrix",
"Audit every element of your Delivery Architecture Map against the five SPOF categories. Score each identified SPOF by Probability (1=unlikely to 5=almost certain) and Impact (1=minor disruption to 5=complete delivery stoppage). Risk Score = Probability × Impact. Scores of 15+ require immediate remediation before the scale event.",
"",
"Identified SPOF",
"Probability\n(1–5)",
"Impact\n(1–5)",
"Risk Score\n(P×I)",
"Action Required",
"Founder is only person who can run live calls",
"4",
"5",
"20",
"",
"Only one copy of core template file (local drive)",
"3",
"4",
"12",
"",
"Manual Kajabi enrolment by single VA",
"3",
"3",
"9",
"",
"Video hosting platform — no backup CDN",
"2",
"5",
"10",
"",
"Zoom account on personal email — no recovery",
"2",
"4",
"8",
"",
"[Add your identified SPOFs here]",
"___",
"___",
"___",
"",
"",
"Risk Score Thresholds",
"Risk Score",
"Classification",
"Action Required",
"Timeline",
"20–25 (Critical)",
"Immediate operational risk. This SPOF breaking during a live launch or at peak buyer volume would cause catastrophic delivery failure.",
"Eliminate or add full redundancy before the scale event. No exceptions.",
"Before any scale event — this blocks the scale gate",
"12–19 (High)",
"Significant risk. This SPOF breaking would cause major delivery disruption affecting 25%+ of active buyers.",
"Reduce probability or impact to below 12 before scale. Document recovery procedure.",
"Within 30 days before the scale event",
"6–11 (Medium)",
"Manageable risk. This SPOF breaking would cause disruption but delivery could continue at reduced capacity.",
"Document a recovery procedure. Assign a backup.",
"Within 60 days, or before the scale event if convenient",
"1–5 (Low)",
"Acceptable risk. This SPOF breaking would cause minor inconvenience with minimal buyer impact.",
"Monitor. No immediate action required.",
"Review quarterly",
"",
"SPOF Remediation Strategies",
"SPOF Type",
"Primary Remediation",
"Secondary Remediation",
"Minimum Standard Before Scale",
"Human SPOF (founder only)",
"Create and train a delivery backup: a team member or contractor who can run calls, manage community, and handle support for a minimum of 14 days.",
"Pre-record key delivery assets so that buyer experience is not degraded if live delivery is interrupted.",
"At least one trained backup person exists for every critical delivery function. Their training is documented and tested.",
"Technology SPOF (single tool)",
"Identify an alternative tool for each critical platform. Document the migration procedure.",
"Export all critical data from the tool monthly. Store in a location independent of the tool (Google Drive or local backup).",
"Migration procedure documented. At least one export test completed. Recovery time to alternative tool estimated and acceptable.",
"Content SPOF (single file)",
"All critical delivery files stored in minimum two locations: cloud storage (Google Drive) AND a backup location (different cloud provider or local).",
"File access shared with at least one team member. File names and locations documented in the delivery architecture map.",
"All files with Risk Score 12+ are stored in at least two locations with at least two people having access.",
"Process SPOF (manual step)",
"Automate the step using n8n, Make.com, or platform-native automation. Prioritise any manual step that occurs in every buyer's journey.",
"If automation is not immediately possible, create a written SOP for the step and assign a backup executor.",
"Every manual step in the buyer journey from purchase confirmation to first content access is automated or has a documented, tested backup executor.",
"Access SPOF (single credential)",
"Audit all platform logins. Move critical accounts to a shared team email (not a personal address). Store credentials in a team password manager (1Password, Bitwarden).",
"Document all critical logins in a secure, encrypted format with at least two authorised team members having access.",
"All platform logins for delivery-critical tools are stored in a shared password manager with at least two authorised users.",
"",
"",
"PHASE 6",
"The Support Load Projection",
"Calculating your support requirements at scale before scale reveals them painfully",
"",
"The Support Load Formula",
"Support load is the most consistently underestimated delivery cost in digital offers. It scales with buyer count but not linearly — it scales faster than linearly for complex offers and slower for simple self-paced products. The formula below produces a projection of weekly support hours at any buyer volume.",
"",
"Support Load Projection Formula",
"Weekly Support Hours = Active Buyers × Average Tickets per Buyer per Week × Average Resolution Time (hours)",
"At 50 buyers × 0.8 tickets/buyer/week × 0.5 hours/ticket = 20 hours/week of support. At 2x (100 buyers) = 40 hours/week — requires a dedicated part-time support role.",
"",
"Support Load by Delivery Stage",
"Support load is not constant throughout a programme. It peaks sharply in the first week (onboarding confusion), drops in weeks 2–3 (established rhythm), and spikes again at any new module release or live call. This pattern must be accounted for in staffing projections.",
"",
"Delivery Stage",
"Typical Support Volume Multiplier",
"Primary Ticket Types",
"Staffing Implication",
"Week 1 (Onboarding)",
"2.5–4.0x baseline",
"Access issues, 'where do I start,' login problems, payment queries, expectation clarification",
"Heavy founder or senior support presence required. Do not schedule other high-demand activities in onboarding week.",
"Weeks 2–3 (Established rhythm)",
"0.6–0.8x baseline",
"Content questions, implementation help, community questions",
"Standard support staffing. VA or community manager can handle majority without escalation.",
"Module release days",
"1.8–3.0x baseline",
"New content questions, 'what does this mean,' technical playback issues",
"Pre-release support briefing required. Support staff must preview new content before buyer access.",
"Live call days",
"1.5–2.0x baseline",
"'I can't get in the Zoom,' replay requests, follow-up questions from call content",
"Live support coverage during call window. Zoom troubleshooting SOP must exist.",
"Final week / completion",
"1.2–1.8x baseline",
"'Did I complete?', certificate requests, testimonial fulfilment, what-to-do-next questions",
"Completion criteria must be clearly defined and visible. Automated completion confirmation reduces tickets significantly.",
"",
"Support Load Projection at Scale",
"Volume Point",
"Active Buyers",
"Baseline Weekly Tickets",
"Peak Week Tickets (onboarding)",
"Weekly Support Hours (baseline)",
"Weekly Support Hours (peak)",
"Staffing Required",
"Current",
"___",
"___",
"___",
"___",
"___",
"___",
"2x current",
"___",
"___",
"___",
"___",
"___",
"___",
"5x current",
"___",
"___",
"___",
"___",
"___",
"___",
"At Capacity Ceiling",
"___",
"___",
"___",
"___",
"___",
"___",
"",
"The Support Staffing Decision Gate",
"Any scale event that would increase support load above the current team's available hours requires a staffing decision BEFORE the scale event — not after. Hiring or onboarding a VA after support has already collapsed produces 10–14 days of degraded buyer experience during the new hire's ramp time. Plan the hire to be trained and operational 2 weeks before the scale event.",
"",
"",
"PHASE 7",
"The 2x Scale Simulation",
"Walking through a doubled buyer volume mentally before experiencing it physically",
"",
"What the 2x Simulation Is",
"The 2x Scale Simulation is a structured thought experiment and paper exercise that walks through every step of your delivery architecture assuming twice your current active buyer count. It does not require real buyers — it requires rigorous honesty about what would happen if you had them. Every capacity constraint, every manual step, every tool limit, and every human dependency is stress-tested against 2x volume.",
"",
"Why 2x — Not 5x or 10x",
"The purpose of the simulation is to find the first failure point — the step that breaks before all others. Most offers fail not at 10x but at 2x, because 2x is the first scale event most operators attempt (doubling ad spend, launching to an affiliate's list, opening a second cohort). If you can pass the 2x simulation cleanly, you have bought yourself a window to prepare for 5x.",
"",
"The 2x Simulation Script",
"Run through each delivery step below with your actual numbers doubled. Write the answer to each question. A 'No' answer to any question identifies a remediation priority.",
"",
"Simulation Question",
"Current Reality",
"At 2x — What Happens?",
"Pass / Fail / Requires Prep",
"Can the purchase trigger (webhook, access grant, welcome email) handle 2x the transaction volume in a 24-hour window without errors?",
"___ purchases/day",
"___ purchases/day",
"",
"Can the course platform (Kajabi/Teachable/etc.) serve 2x simultaneous users without degradation?",
"___ active sessions/day",
"___ active sessions/day",
"",
"Can video hosting serve 2x simultaneous streams within the current plan?",
"___ streams/day",
"___ streams/day",
"",
"Can the email platform deliver onboarding sequences to 2x the subscriber count without hitting sending limits?",
"___ emails/day",
"___ emails/day",
"",
"Can live calls maintain the same quality at 2x the current participant count?",
"___ participants/call",
"___ participants/call",
"",
"Does the founder's weekly delivery time at 2x stay within 70% of their total available hours?",
"___ hrs/week",
"___ hrs/week",
"",
"Does the support team's weekly hours at 2x stay within their available capacity?",
"___ hrs/week",
"___ hrs/week",
"",
"Does the community platform remain manageable for current community manager at 2x members?",
"___ members",
"___ members",
"",
"Does gross margin remain above 50% at 2x buyer volume?",
"___% margin",
"___% margin",
"",
"Are all Risk Score 12+ SPOFs remediated before 2x volume is reached?",
"___ SPOFs at 12+",
"Same list",
"",
"Can onboarding be completed without any new manual steps at 2x?",
"___ manual steps",
"___ manual steps",
"",
"Is there a trained delivery backup available if the founder is unavailable for 5+ days during a 2x-volume cohort?",
"Yes / No",
"Same requirement",
"",
"",
"2x Simulation Result Interpretation",
"Result",
"Interpretation",
"Action",
"All questions Pass",
"Delivery infrastructure is ready for a 2x scale event. Proceed with confidence.",
"Authorise scale event. Schedule a re-run of this simulation at 30 days post-scale to validate real-world performance.",
"1–2 questions Fail or Requires Prep",
"Delivery infrastructure has specific, identifiable gaps. Scale event should be delayed until gaps are remediated.",
"List each failing question. Assign an owner and deadline for remediation. Re-run the simulation after remediation. Do not proceed until clean pass.",
"3–5 questions Fail",
"Delivery infrastructure has systemic problems that cannot be patched quickly. The scale event risks producing a fulfilment breakdown.",
"Delay scale event by minimum 30 days. Address all failing questions in priority order. Consider a smaller scale test (1.3x or 1.5x) to build confidence incrementally.",
"6+ questions Fail",
"Delivery infrastructure is not ready to scale at all. The offer may need to be operated at current volume while delivery is rebuilt.",
"Do not scale. Review delivery architecture from the ground up. Identify whether the problem is a fixable capacity issue or a fundamental model mismatch.",
"",
"",
"PHASE 8",
"The Technology & Tool Dependency Audit",
"Every tool you depend on is a risk you are carrying — audit it",
"",
"The Tool Dependency Inventory",
"Every tool in your delivery stack is a dependency. When it changes pricing, reduces functionality, experiences downtime, or shuts down, your delivery is affected. The Tool Dependency Audit documents every tool, its role in delivery, its risk profile, and the mitigation in place.",
"",
"Tool Name",
"Delivery Function",
"Monthly Cost",
"Tier Limit Affecting Delivery",
"Last Outage (known)",
"Has Backup?",
"Backup Tool",
"Data Export Protocol",
"Kajabi / Teachable",
"Course delivery and member access",
"$___",
"___ student limit",
"",
"Yes/No",
"",
"",
"Zoom / Google Meet",
"Live call delivery",
"$___",
"___ participant limit",
"",
"Yes/No",
"",
"",
"ActiveCampaign / ConvertKit",
"Email sequence delivery",
"$___",
"___ subscriber limit",
"",
"Yes/No",
"",
"",
"Vimeo / Wistia",
"Video hosting",
"$___",
"___ bandwidth/month",
"",
"Yes/No",
"",
"",
"Discord / Skool",
"Community management",
"$___",
"___ member limit",
"",
"Yes/No",
"",
"",
"Stripe / ThriveCart",
"Payment processing",
"2.9% + fees",
"N/A",
"",
"Yes/No",
"",
"",
"Loom / Descript",
"Async video communication",
"$___",
"___ video limit",
"",
"Yes/No",
"",
"",
"n8n / Make.com",
"Delivery automation",
"$___",
"___ operations/month",
"",
"Yes/No",
"",
"",
"Calendly / Acuity",
"Call scheduling",
"$___",
"___ meeting types",
"",
"Yes/No",
"",
"",
"[Add tools]",
"",
"",
"",
"",
"",
"",
"",
"",
"The Tool Risk Assessment",
"For each mission-critical tool (any tool whose failure would affect more than 20% of active buyers), answer these four questions:",
"",
"1. What is the maximum downtime this tool has experienced in the last 12 months? Is that downtime acceptable given our delivery commitments?",
"2. What would happen if this tool increased its price by 50% tomorrow? Can the unit economics absorb it, and is there an alternative?",
"3. If this tool shut down with 30 days' notice, how long would migration take, and would active buyers experience degraded delivery during the migration?",
"4. Is all data held in this tool exportable to a neutral format (CSV, JSON, MP4) that can be imported into an alternative platform? Has this export been tested in the last 90 days?",
"",
"",
"PHASE 9",
"The Fulfilment Stress Test Scorecard",
"The integrated scoring system across all eight phases",
"",
"Scorecard Purpose",
"The Fulfilment Stress Test Scorecard integrates findings from all eight phases into a single Go/No-Go decision. Each dimension is scored 1 (fail) through 4 (excellent). A total score of 32 or above clears the Go gate. Any individual dimension scoring 1 (Critical Failure) blocks the gate regardless of total score.",
"",
"Dimension",
"What Is Measured",
"1 — Fail",
"2 — Warn",
"3 — Pass",
"4 — Strong",
"Score",
"Capacity Ceiling clarity",
"Is the ceiling calculated from actual data?",
"Not calculated",
"Estimated only",
"Calculated from 1 week audit",
"Calculated + validated in simulation",
"___",
"Time-and-Motion audit complete",
"Actual vs estimated delivery time",
"Not tracked",
"Rough estimates only",
"1 full week tracked",
"1 week tracked + multiplier calculated",
"___",
"Gross margin at 2x buyers",
"%margin at 2x volume",
"Below 30%",
"30–44%",
"45–59%",
"60%+",
"___",
"Founder delivery at 2x hours",
"Founder hours as % of available",
"Above 85%",
"70–85%",
"50–69%",
"Below 50%",
"___",
"SPOF audit complete",
"All risk 12+ SPOFs remediated",
"2+ SPOFs at 12+, unaddressed",
"1 SPOF at 12+, unaddressed",
"All 12+ SPOFs remediated",
"All 6+ SPOFs remediated + documented backup",
"___",
"Support load projected",
"Hours at 2x calculated",
"Not projected",
"Rough guess",
"Formally calculated",
"Calculated + staffing decision made",
"___",
"Support staffing at 2x",
"Is support team capacity sufficient?",
"Insufficient, no plan",
"Insufficient, plan underway",
"Sufficient with current team",
"Sufficient + backup trained",
"___",
"2x simulation result",
"Simulation pass rate",
"6+ questions Fail",
"3–5 Fail",
"1–2 Fail (remediation in progress)",
"All Pass",
"___",
"Tool dependency audit",
"All critical tools audited",
"Not completed",
"3+ tools without backup",
"1–2 tools without backup",
"All critical tools audited + backups confirmed",
"___",
"SPOF backup person exists",
"Trained backup for all human SPOFs",
"No backup for any role",
"Backup identified, not trained",
"Backup trained, not tested",
"Backup trained and tested",
"___",
"Delivery Architecture Map",
"Complete written map of all delivery steps",
"Not documented",
"Partial documentation",
"Full map documented",
"Full map + owner per step + timing",
"___",
"TOTAL SCORE",
"Maximum: 44 points | Go gate: 32+ | Any dimension scoring 1 blocks Go gate regardless of total",
"___",
"",
"Go / No-Go Decision",
"Score Range",
"Decision",
"Condition",
"Action",
"Any dimension = 1",
"NO-GO — Blocked",
"One or more critical failures regardless of total score",
"Address all dimension-1 items. Re-run scorecard after remediation.",
"0–31 (no dimension = 1)",
"NO-GO",
"Multiple weaknesses prevent safe scaling",
"Identify and remediate all dimensions below 3. Re-run in 30 days.",
"32–38",
"CONDITIONAL GO",
"Infrastructure is ready with monitoring",
"Scale with enhanced monitoring. Weekly scorecard check for 30 days post-scale.",
"39–44",
"CLEAR GO",
"Infrastructure is strong. Scale with confidence.",
"Authorise scale event. Schedule 30-day post-scale review.",
"",
"",
"PHASE 10",
"Remediation Priority Matrix",
"Turning scorecard findings into an ordered action plan",
"",
"The Remediation Ordering Principle",
"Not all remediation items are equal. The ordering principle is: fix the highest-risk SPOFs first (because they can cause complete delivery stoppage), then address the margin death zone (because it determines scalability), then fix the capacity ceiling constraints (because they determine how many buyers you can serve), then build support infrastructure (because it determines buyer experience at scale).",
"",
"Priority Tier",
"Category",
"Criteria for This Tier",
"Typical Remediation Time",
"Tier 1 — Immediate\n(Block scale gate)",
"Critical SPOFs (Risk Score 20+) and any dimension-1 scorecard items",
"Any SPOF or scorecard item that would cause complete delivery failure. Non-negotiable. Must be resolved before any scale event.",
"1–14 days depending on complexity",
"Tier 2 — Before Scale Event",
"High SPOFs (Risk Score 12–19), negative margin at 2x, Capacity Ceiling below target scale volume",
"Infrastructure gaps that would cause significant degradation at the target scale volume. Must be resolved before the scale event.",
"14–30 days",
"Tier 3 — Within 30 Days Post-Scale",
"Medium SPOFs (Risk Score 6–11), support staffing for 5x volume, tool backups",
"Items that can be managed at 2x but would become critical at 5x. Build while scale event is live.",
"30–60 days",
"Tier 4 — Ongoing",
"Low SPOFs, documentation completeness, quarterly tool audit",
"Items that improve resilience but do not block current operations.",
"Quarterly review cycle",
"",
"Remediation Action Register",
"For each identified remediation item, complete one row of this register. Assign a single owner per item. No item without a named owner and a deadline is a real commitment.",
"",
"Item",
"Source\n(Phase #)",
"Priority\nTier",
"Owner",
"Deadline",
"Status",
"Verified By",
"",
"",
"",
"",
"",
"Open / In Progress / Complete",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"",
"Delivery Model Quick Reference: Common Failure Points",
"Each delivery model has a distinct failure pattern. Use this quick reference when reviewing the 2x Simulation results or diagnosing post-launch delivery problems.",
"",
"Model 1 — Self-Paced Digital: Where It Usually Breaks",
"• Video hosting CDN fails during a high-traffic day (e.g. after an email broadcast or affiliate promotion). Mitigation: use a CDN-backed host (Vimeo Pro, Wistia) and test load response before campaigns.",
"• Support volume from 'I can't find X' tickets overwhelms available hours within 72 hours of launch. Mitigation: add a pinned 'Start Here' navigation guide. Reduce first-access steps to one click.",
"• Community becomes a support forum rather than a learning community without active moderation above 30 members. Mitigation: hire or appoint a community manager before 30 members.",
"• Module completion tracking breaks when platform has a bug update. Mitigation: notify buyers of completions manually if platform fails. Have a backup completion tracking method.",
"",
"Model 2 — Live Group Cohort: Where It Usually Breaks",
"• Founder's calendar becomes the hard ceiling. When a cohort of 25 runs simultaneously with a second cohort of 20, the founder is committed to more live delivery than they can perform at quality. Mitigation: cap cohort size. Open second cohort only after hiring a trained delivery backup.",
"• Call quality degrades above 25 participants for complex workshop formats. Above 25, questions queue up, personalisation disappears, and the format becomes a lecture rather than a coaching session. Mitigation: above 25, switch to small-group breakout calls rather than single large calls.",
"• Replay delivery breaks. Buyers who miss calls expect replays within 24 hours. If recording upload is a manual step, it will be late when the founder is busy. Mitigation: automate recording upload via Zoom cloud recording → auto-publish to course platform.",
"",
"Model 3 — Done-With-You Intensive: Where It Usually Breaks",
"• Over-booking. The founder accepts one more booking than their total delivery hours allow, and every subsequent intensive is rushed. Mitigation: hard block the calendar. Maximum active intensives = Available DWY hours ÷ Total hours per intensive. No exceptions.",
"• Preparation shortcuts. When the founder is over-booked, they arrive at intensives without having reviewed the buyer's materials. Quality drops. Buyers notice. Mitigation: block preparation time on the calendar as a non-negotiable pre-intensive appointment — not optional.",
"• Rescheduling cascade. One rescheduled intensive pushes all subsequent sessions, creating a backlog. Mitigation: two rescheduling slots per calendar month held in reserve specifically for rescheduled intensives.",
"",
"Model 4 — Done-For-You Service: Where It Usually Breaks",
"• Revision cycle explosion. Client count doubles; revision requests triple. Without a defined revision policy, the team spends 40% of their time on revisions rather than new work. Mitigation: define revision rounds in the contract (2 rounds included; additional rounds at hourly rate). Enforce it.",
"• Quality control bypass. Under volume pressure, deliverables skip the QA review and go directly to clients. Quality complaints follow. Mitigation: no deliverable leaves the business without completing the QA checklist. QA is a non-negotiable step, not an optional one.",
"• Client communication overhead. Active client count doubles; communication overhead increases by 3x because each client wants status updates. Mitigation: weekly automated status email per client. Reduces ad hoc 'where is my project?' enquiries by 60–70%.",
"",
"",
"Fulfilment Stress Test Database — Airtable Schema",
"",
"Table 1 — Stress Test Records",
"One record per completed stress test. Linked to the Offers table and the Remediation Register.",
"",
"Field",
"Type",
"Notes",
"Stress Test ID",
"Autonumber",
"Format: FST-[Year]-[Seq]",
"Offer",
"Link → Offers table",
"",
"Test date",
"Date",
"",
"Trigger event",
"Short text",
"What caused this test to be run",
"Delivery model",
"Single select",
"Model 1–5",
"Current active buyers",
"Number",
"",
"Calculated Capacity Ceiling",
"Number",
"From Phase 2",
"Capacity utilisation (% of ceiling)",
"Formula",
"Current buyers / Ceiling × 100",
"Time-and-Motion multiplier",
"Number",
"Actual / estimated from Phase 3",
"Gross margin at 2x (%)",
"Number",
"From Phase 4 model",
"Margin death zone buyer count",
"Number",
"From Phase 4",
"SPOF audit: critical items (score 20+)",
"Number",
"Count of unaddressed 20+ SPOFs",
"SPOF audit: high items (score 12–19)",
"Number",
"Count of unaddressed 12–19 SPOFs",
"Support load at 2x (hours/week)",
"Number",
"From Phase 6",
"Support staffing gap",
"Number",
"Hours needed minus hours available at 2x",
"2x simulation pass rate (of 12 questions)",
"Number",
"How many of 12 simulation questions passed",
"Scorecard total score",
"Number",
"Out of 44",
"Go / No-Go decision",
"Single select",
"No-Go Blocked / No-Go / Conditional Go / Clear Go",
"Remediation items total",
"Number",
"Total items in remediation register",
"Remediation Tier 1 items",
"Number",
"Items requiring immediate action",
"Remediation completion date (estimated)",
"Date",
"When all Tier 1 and 2 items will be resolved",
"Scale event authorisation date",
"Date",
"Date scale event is cleared to proceed",
"Post-scale review date",
"Date",
"30 days after scale event",
"",
"",
"Master Fulfilment Stress Test Checklist",
"",
"Pre-Test Setup",
"☐ Delivery Architecture Map completed for the offer under review",
"☐ Delivery model classified (Model 1–5 or hybrid)",
"☐ Top 3 stress vectors identified for this delivery model",
"☐ All current delivery data pulled: buyer count, weekly hours, support tickets, refund rate",
"",
"Phase 1 — Delivery Model Classification",
"☐ Delivery model confirmed and all component models listed if hybrid",
"☐ Current founder weekly delivery hours tracked (not estimated)",
"☐ Hidden time trap calculation run: active vs total delivery time per buyer",
"",
"Phase 2 — Capacity Ceiling",
"☐ Capacity Ceiling calculated using the formula for the confirmed delivery model",
"☐ Capacity Ceiling worksheet completed with all input fields",
"☐ Current utilisation as percentage of ceiling calculated",
"☐ 70% buffer target set — scale gate blocked if current buyers exceed 70% of ceiling without capacity expansion",
"",
"Phase 3 — Time-and-Motion Audit",
"☐ One full week of delivery time tracked across all five activity categories",
"☐ All four output metrics calculated: total hours/week, hours/buyer/week, multiplier, support as % of total",
"☐ Capacity Ceiling revised using actual (not estimated) data",
"☐ Delta between original and revised ceiling documented",
"",
"Phase 4 — Margin Stress Test",
"☐ All delivery costs decomposed into fixed and variable components",
"☐ Margin model completed at current, 2x, and 5x buyer volumes",
"☐ Margin Death Zone buyer count identified",
"☐ Step-cost thresholds identified for all major fixed costs",
"☐ Gross margin at 2x above 45% (minimum threshold for scaling)",
"",
"Phase 5 — SPOF Audit",
"☐ All elements of Delivery Architecture Map reviewed against 5 SPOF categories",
"☐ Every identified SPOF scored by Probability × Impact",
"☐ All Risk Score 20+ SPOFs addressed before scale gate authorised",
"☐ All Risk Score 12–19 SPOFs addressed or in remediation with deadline before scale event",
"☐ Recovery procedure documented for all Risk Score 6–11 SPOFs",
"",
"Phase 6 — Support Load Projection",
"☐ Baseline tickets per buyer per week calculated from actual data",
"☐ Support load projection completed at 2x and 5x buyer volumes",
"☐ Support staffing decision made before scale event for any volume requiring additional hours",
"☐ Peak week (onboarding) support load modelled separately",
"",
"Phase 7 — 2x Scale Simulation",
"☐ All 12 simulation questions answered with actual numbers",
"☐ Every 'Fail' answer documented with a specific remediation action and owner",
"☐ Simulation re-run after remediation — clean pass required before scale gate",
"",
"Phase 8 — Tool Dependency Audit",
"☐ All delivery-critical tools listed in the Tool Dependency Inventory",
"☐ Four risk questions answered for each mission-critical tool",
"☐ All tools without a backup confirmed and backup documented",
"☐ Data export tested for all critical platforms in last 90 days",
"",
"Phase 9 — Scorecard & Go/No-Go",
"☐ All 11 scorecard dimensions scored",
"☐ Total score calculated — 32+ required for Conditional Go",
"☐ Any dimension scoring 1 (Critical Failure) — scale gate blocked until remediated",
"☐ Go/No-Go decision documented in Airtable Stress Test Record",
"",
"Phase 10 — Remediation & Post-Scale",
"☐ All remediation items logged in the Remediation Action Register with owner and deadline",
"☐ All Tier 1 items completed before scale event authorised",
"☐ All Tier 2 items completed before scale event authorised",
"☐ Post-scale 30-day review scheduled",
"☐ Stress Test Record filed in Airtable with all findings and decisions",
"",
"",
"",
"RISER Nation Master Operating System | Fulfilment Stress Test SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | Fulfilment Stress Test SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
},
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Investigate buyer signals and choose the next offer action
Turn a sale into a learning cycle
Imagine an operator celebrating a tenth sale. This is an illustrative scene. A refund request arrives the same day. The operator now needs to understand both the purchase and the disappointment.
The gap is between collecting revenue and learning from buyers. This lesson teaches all eight phases of the source's Post-MVO Forensic Audit Loop. You will gather numbers, inspect buyer evidence and write a justified action brief.
The source combines three ideas. Its Hormozi lens revisits perceived value after every ten sales. Its Kennedy lens treats feedback as business evidence. Its Brunson lens looks for the next problem after the current result. These are source-attributed applications, not verified quotations or endorsements. They support the user's ClickFunnels/Brunson and Hormozi/Acquisition.com educational themes.
Buyer feedback can guide product, copy, naming and ascension work. It does not automatically explain causation or grant permission to publish private messages. Keep the evidence, its context and the proposed interpretation separate.
Know what triggers the review
Read all six trigger conditions with their scope and deadline. Some trigger the full review; others point to selected phases.
Trigger
Condition
Audit Scope
Priority
10-Sale Trigger
Every 10 new purchases of an offer (cumulative)
Full 8-Phase Audit
High — run within 72 hours of the 10th sale
First Refund Trigger
First refund or cancellation request on any offer tier
Ascension rate from any tier to the next falls below 10% for 21+ days
Phase 6 only (Next Problem Signal)
Medium — run within 1 week
The opening calls this event-driven rather than calendar-driven. Yet day 30, day 90 and the standing calendar are explicit parts of the source. Teach both: event triggers plus scheduled follow-through.
When the tenth sale and a conversion decline coincide, run one full audit and record both signals. Don't duplicate the same full session. A 20% drop is relative to the prior 30-day average, not twenty percentage points. A zero baseline or inconsistent traffic population needs investigation before calculating that trigger. The ascension trigger also needs a defined buyer cohort and observation period.
No audit, calendar event or outreach is executed by reading this lesson. The deadlines describe the source's proposed operating practice.
Phase 1 — Build the numerical baseline
Start with all seven metrics. For each, identify the numerator, denominator, time window and data source. A healthy range and an action threshold are different pieces of guidance; preserve both.
Metric
Formula
Healthy Range
Action Threshold
Cold opt-in rate
Opt-ins / Total cold traffic
15–30%
Below 12%: landing page or traffic source problem
Cold MVO conversion rate
Sales / Total cold visitors
1–3%
Below 0.8%: offer, copy, or trust problem
Warm conversion rate
Sales / Warm list visitors
5–15%
Below 4%: email sequence or offer relevance problem
Email open rate (sequence)
Opens / Delivered (14-day sequence)
28–40%
Below 20%: subject line, sender reputation, or list quality problem
Email click-to-sale rate
Sales / Total email clicks
8–20%
Below 5%: landing page or offer mismatch with email audience
Refund rate
Refunds / Total sales (rolling 30 days)
Below 5%
Above 8%: expectation mismatch, delivery failure, or wrong buyer profile
Ascension rate (MVO to Core)
Core Offer purchases / MVO buyers
10–20%
Below 8%: ascension sequence missing or wrong offer presented at wrong time
Cold traffic means visitors without the defined prior relationship used for your analysis. Define warm traffic separately. Avoid mixing unique people, visits, clicks and orders. Refunds from old cohorts divided by new sales can distort interpretation. Explain the cohort and refund definition in your record.
The source's five-step flow follows. Its sentence saying stop at the first Yes is wrong for steps 1–3, where Yes means continue. Follow each actual branch.
Source procedure for study:
Is cold traffic volume sufficient? (Minimum 200 unique visitors to judge conversion rate accurately)
– No → Traffic problem. Do not adjust offer or copy until you have enough data. Solve distribution first.
– Yes → Continue to step 2.
Is the opt-in rate above 12%?
– No → Hook or landing page problem. The market is seeing the offer and not raising their hand. Fix the lead magnet, headline, or traffic targeting before anything else.
– Yes → Continue to step 3.
Is the cold conversion rate above 0.8%?
– No → Sales page, offer stack, or trust problem. Proceed to Phase 2 (Value Equation Audit) and Phase 4 (Funnel Diagnostic) before spending more on ads.
– Yes → Continue to step 4.
Is the refund rate above 8%?
– Yes → Expectation mismatch or delivery failure. Proceed directly to Phase 5 (Refund Forensics). This is the most urgent problem in the stack.
– No → Continue to step 5.
Is the ascension rate below 8% after 60+ days of live offer?
– Yes → Ascension sequence failure. Proceed to Phase 6 (Next Problem Signal). The value ladder exists on paper but buyers are not moving up it.
– No → Offer is healthy at the quantitative level. Proceed to Phase 2 to find optimisation opportunities.
Two hundred visitors is the source's starting heuristic, not a guarantee of accurate conversion estimates. At a 1% rate, that volume implies roughly two expected purchases. A small change in count can greatly move the rate. Don't postpone investigation of known refund or delivery harm merely because traffic is low.
Exactly 12% opt-in and 0.8% conversion expose a wording gap: the flow requires above, while the metric table triggers below. Record that ambiguity. The flow's ascension check below 8% after 60 days differs from the earlier below 10% for 21 days trigger. Those may serve different warning levels, but the source does not fully reconcile them.
Use every data source and review cadence listed here. Platform names are examples; this lesson does not install tracking or verify their current interfaces.
The source uses Hormozi's conceptual Value Equation: outcome multiplied by perceived likelihood, divided by time delay multiplied by effort and sacrifice. Increase a credible desired result and belief; reduce unnecessary delay and burden. This is a thinking framework, not a calibrated revenue prediction or a reason to divide by zero.
Ask buyers what they believe and compare that with delivery. Falling conversion can have other causes too, including traffic changes or broken tracking. Read each question, source and warning in the four complete tables.
Dream outcome clarity
Separate a measurable expected result from a vague category. Compare the buyer's words with the page. A stated revenue goal and a possible emotional goal are different hypotheses; don't claim hidden motives without evidence.
Audit Question
Data Source
Red Flag Signal
Can buyers describe the specific result they expect — in numbers and timeframes — before the offer is delivered?
Onboarding survey (baseline), application form responses, sales call recordings
Vague answers like 'I want to grow my business' or 'get more organised' — no specific metric or timeframe
Does the language buyers use to describe the outcome match the language used on the sales page?
Support ticket replies, community posts, direct email replies
Buyers describe the outcome in completely different terms than your copy — the promise is not landing as intended
Are buyers purchasing for the stated outcome or for an unstated emotional outcome?
Exit interview question: 'What were you really hoping for that you couldn't say out loud?'
Stated goal is revenue; real goal is status, confidence, or validation. Your copy may be hitting the wrong desire layer.
Perceived likelihood
Look for proof that fits the actual buyer and promise. Doubt about a constraint can reveal missing explanation. A price objection can also mean limited funds or a different priority; it does not almost always prove disbelief.
Audit Question
Data Source
Red Flag Signal
Do buyers mention specific proof elements when describing why they purchased?
Sales call recordings, email reply: 'What made you decide to buy today?'
Buyers cite general reputation or brand trust — not specific case studies. Your proof is not match-specific enough.
Do buyers express doubt about whether it will work 'for their situation'?
Support tickets within first 72 hours of purchase, community posts
High volume of 'will this work for me if I have [specific constraint]?' questions
What is the objection most commonly raised before purchase that was not resolved by the sales page?
Price objection is a proxy for perceived likelihood — 'I'm not sure it's worth it' almost always means 'I'm not sure it will work for me'
Time delay
Record the first expected result, the first observed result and the actual delivery sequence. A 72-hour win should be achievable and relevant. No quick win does not literally make perceived delay infinite or establish a day-seven refund spike; those are overstated source claims.
Audit Question
Data Source
Red Flag Signal
What result do buyers expect first — and by when?
Onboarding survey question: 'What would make you feel this was worth it in the first 7 days?'
Buyers expect a result your offer cannot deliver in that timeframe — the promise is creating false urgency
Are buyers reaching out to ask 'when will I see results?' in the first week?
Support tickets, community posts, DMs within days 1–7
High support volume on timeline questions = promise of speed is not backed by delivery structure
Does the offer have a documented Quick Win within the first 72 hours?
Your own delivery SOP
No quick win = perceived time delay is infinite = refund risk spikes after day 7
Effort and sacrifice
Inspect workload surprises and the step where participation drops. The source uses 60% step completion as a flag. That does not prove the step must become done-for-you. Access, instructions, timing and buyer circumstances can also explain the data. Ask non-starters rather than assigning intent.
Audit Question
Data Source
Red Flag Signal
What do buyers say is 'harder than expected' in week 1 feedback?
Per-module pulse survey, community posts tagged 'stuck' or 'help'
Any step described as confusing or time-intensive that is supposed to be a quick win
Are buyers dropping off at a consistent action step?
Completion rate data by module (course platform analytics)
Below 60% completion at any single step = that step has an effort barrier that must be reduced or replaced with a done-for-you asset
What is the most common reason buyers have not started?
Check-in message to non-starters: 'We noticed you haven't accessed the programme yet — is everything okay?'
Answers involving 'too busy,' 'overwhelmed by where to start,' or 'waiting for the right time' = onboarding friction, not buyer intention
Fill all four rows below. Current perception needs a citation or measured observation. The target must fit the real offer. State the specific change that could close the supported gap.
Variable
Current Buyer Perception (evidence-based)
Target Perception
Specific Change Required
Dream Outcome Clarity
Perceived Likelihood
Time Delay
Effort & Sacrifice
Phase 3 — Capture buyer language with context
The source prefers direct buyer language over invented marketing phrases. Use it to understand pain, desire and hesitation. It is not a guarantee that every buyer phrase will outperform professional copy. Preserve verbatim research separately from any public copy, with permission and context where needed.
The five sources below include what to capture, how to tag it and when to review it. The listed software is illustrative; no connected data is collected by this lesson.
Source
What to Mine
Mining Method
Cadence
Email replies (to your nurture sequence)
Exact phrases describing pain, frustration, failed attempts, and desired outcomes. The most unfiltered language because buyers are replying privately.
Tag every reply in ActiveCampaign with: Pain / Desire / Objection / Anti-language. Export tagged replies monthly.
After every 10 new subscribers or weekly if list is active
Support tickets and help desk messages
Confusion points, unmet expectations, and implementation breakdowns. Also the highest-intensity emotional language because people are frustrated.
In Intercom or Help Scout, tag tickets with: Confusion / Expectation-Gap / Mechanism-Question / Praise. Review tags monthly.
Weekly review of new tickets — tag in real time
Community posts (Discord/Skool/Facebook)
Peer-to-peer language — how buyers describe the problem to each other, not to you. This is the most authentic version of the voice because there is no authority figure present.
GummySearch-style keyword monitoring. Screenshot any post with 3+ reactions or replies. Archive in Airtable.
Weekly scan of all community posts
Exit interview transcripts
Full before/during/after narrative in the buyer's own words. The richest single source of language per buyer.
Castmagic or Descript transcript. Highlight every phrase of 3–8 words that describes pain, transformation, or hesitation. Tag by funnel function.
After every exit interview — tag within 24 hours
Refund request messages
The language of unmet expectations. Tells you exactly where the sales page or delivery created a gap that cost you money.
Archive every refund message verbatim. Do not paraphrase. Tag with: Expectation-Gap / Wrong-Avatar / Delivery-Failure / External-Event.
Immediately upon receipt
Use all six functional tags. A phrase can have multiple tags. The source ties them to specific page sections, email days and ad functions; these are its sequence references, not proof those exact assets already exist in your account.
Tag
Definition
Where It Gets Used in Copy
PAIN-ACUTE
Phrases describing urgent, active pain — happening right now. High emotional intensity.
Sales page Problem section, email Day 2 (Pain Awareness), ad hook (Cost-of-Inaction type)
PAIN-CHRONIC
Phrases describing long-term, background frustration — not urgent but persistent.
Lead magnet headline, email Day 3 (Cost of Inaction), ad hook (Mistake type)
DESIRE-EXPLICIT
Stated goals — what they say they want. Often surface-level.
Reasons they hesitated before buying or reasons they stopped engaging after buying.
Sales page FAQ section, email Day 11 (Objection Handling), retargeting ad variant 2
ANTI-LANGUAGE
Words and phrases that trigger instant distrust or repulsion in this avatar.
Remove from all copy immediately. Flag for sales team to avoid on calls.
The source recommends phrases of three to eight words. Its example tags “spinning my wheels” as chronic pain and “No idea what to try next” as acute pain. Both come from one longer illustrative email. Preserve the full message for context. A phrase can be useful without treating the proposed tag as the only possible interpretation.
Single words can lack context, while whole sentences may need more space. The three-to-eight rule is a practical extraction convention, not a ban on retaining full source text. Do not paraphrase the research record merely to fit a headline.
The first language database specification has eight fields:
Field
Type
Notes
Phrase
Long text
Exact verbatim — never paraphrase or clean up. The rawness is the value.
Source
Single select
Email Reply / Support Ticket / Community Post / Exit Interview / Refund Message / Sales Call
Recency matters — language evolves as the market evolves
Deployed
Checkbox
Checked once this phrase has been placed into active copy
Deployed in
Long text
Which specific asset: sales page / email day N / ad creative / etc.
Conversion lift
Number
If A/B tested — record the conversion difference when this phrase was used
Record conversion lift only when its measurement supports the claim. Note the test population and design. A difference between two dates does not by itself show the wording caused it. The later database definition omits this field and adds Phrase ID; retain both needs in a proposed reconciliation rather than silently dropping one.
Phase 4 — Locate the funnel problem
Trace each stage from ad click to first access. A page problem, checkout issue and onboarding problem require different tests. The full table preserves each source metric, suggested cause and first test.
Funnel Stage
Primary Metric
If Below Threshold
Most Likely Cause
First Fix to Test
Ad to landing page (click-through)
CTR above 1.5% (cold), above 3% (warm)
Hook or creative problem
Ad creative does not match the traffic source's intent or awareness level
Test 3 new hooks targeting Problem-Aware stage rather than Solution-Aware
Landing page to opt-in
Above 25% (cold)
Headline or offer mismatch
Lead magnet does not solve a specific enough problem, or headline is too generic
Rewrite headline using PAIN-ACUTE tags from Phase 3. Narrow the lead magnet promise.
Opt-in to sales page visit (email sequence)
Above 15% click-through on Day 9 email (offer introduction)
Email sequence engagement drop
Sequence is educating without pre-suading. Buyers are not being moved through the awareness ladder.
Inject buyer language (Phase 3 tags) into email subjects. Add one case study email on Day 6.
Sales page to add-to-cart
Above 3% (cold), above 8% (warm)
Offer stack or trust problem
Stack does not clearly exceed the price. Or proof does not match the exact promise.
Add one Proof-to-Promise-Matched testimonial above the fold. Test a stronger guarantee.
Add-to-cart to purchase
Above 60%
Checkout friction or final objection
Price shock at checkout (hidden fees or tax), payment option missing, trust signal absent
Add order summary with value stack visible on checkout page. Add payment plan option.
Post-purchase to first login / first module
Above 70% within 48 hours of purchase
Onboarding failure
Welcome email is generic, first step is unclear, or access instructions are confusing
Rewrite welcome email with specific 'Your first step is this, takes 8 minutes' instruction. Add a Loom walkthrough video.
These figures are source heuristics, not universal benchmarks. For example, this table targets cold opt-in above 25%, while Phase 1 uses 15–30% healthy and below 12% as an action threshold. The iteration section later uses below 15%. Keep the context visible. Likewise, sales-page add-to-cart rate is not purchase conversion.
Check measurement quality before changing creative. Email opens and clicks may be affected by instrumentation, privacy features or automated activity. Verify current platform behavior during implementation. A stronger guarantee must remain truthful and feasible. An eight-minute first task or seventy-percent activation target must not be represented as a measured result without evidence.
Use the complete five-step session-review procedure below. It includes both non-buyers and buyers.
Source procedure for study:
Set up Hotjar on sales page and landing page if not already active. Minimum 200 sessions before drawing conclusions.
Watch scroll depth heatmap: if 70%+ of visitors are not reaching the offer stack, the page is losing them in the problem section or the story. The copy before the offer is too long or too weak.
Watch click map: what are visitors clicking that is not a CTA? This reveals unmet curiosity — they want information you have not provided.
Watch 5 session recordings of visitors who scrolled to the bottom but did not convert. Note the exact moment they stop engaging.
Watch 5 session recordings of visitors who converted. Note what they did differently — faster scroll to specific section, immediate click of CTA.
The source's 200-session minimum and ten watched sessions are exploratory guidance. They do not prove why people left. If 70% never reach the offer stack, inspect relevance, navigation, device behavior and page length rather than declaring the story weak without testing. Non-CTA clicks can suggest a question but may also reflect a confusing interface.
Phase 5 — Learn from refunds and dropouts
A refund is both a business outcome and potential diagnostic evidence. A dropout is a signal, not a character judgment. The source lists wrong fit, friction and guarantee-related behavior as possibilities. Those are not the only causes.
Its protocol calls for review within 24 hours for every refund request, whether granted or not. Keep that obligation distinct from the weekly Thursday calendar reminder. Learn all five steps and their outputs:
Step
Action
Output
1. Archive the message
Save the full text of the refund request verbatim in Airtable — every word. Never paraphrase. Assign it an ID number.
Verbatim refund archive entry
2. Classify the root cause
Assign one primary root cause from the taxonomy below. One cause per refund — force the classification.
Root cause tag on Airtable record
3. Send the forensic reply
Before processing the refund, send the forensic reply template (see below). You are not negotiating — you are collecting data.
Reply sent, response captured if they reply
4. Update the Negative Avatar profile
If this refund adds evidence to an existing Negative Avatar pattern, update that profile. If it reveals a new pattern, start a new profile.
Negative Avatar Airtable record updated
5. Check for pattern
Is this the 2nd or 3rd refund citing the same root cause? If yes, trigger the relevant fix protocol from Phase 8.
Pattern check completed. Fix protocol triggered if threshold reached.
The instruction to choose one primary cause must not erase uncertainty or contributing causes. Record a primary code, the evidence and any unresolved alternatives. The second-or-third pattern trigger here differs from 2+ in the database and 3+ in later checks. State which convention you are applying and preserve the source conflict.
The complete six-code taxonomy follows. Treat its diagnoses and recommended actions as proposals requiring evidence.
Root Cause Code
Definition
Immediate Action
RC-1: Wrong Avatar
The buyer does not fit the target profile that the offer was designed for. They bought based on the category but are not the person the transformation serves.
Review ad targeting and sales page 'This is NOT for you if...' section. Strengthen avatar-specific language on the sales page.
RC-2: Expectation Gap — Copy
The sales page or email sequence created a promise that the offer does not fulfil. The buyer expected something different from what was delivered.
Compare the refund language to the sales page promises verbatim. If the gap is real, fix the copy or fix the delivery — not one without the other.
RC-3: Expectation Gap — Timing
The buyer expected the result faster than the offer delivers. Time Delay variable of the Value Equation was miscalibrated.
Add a Quick Win in the first 72 hours. Add a timeline disclaimer to the sales page: 'Most members see [first result] by day [N].'
RC-4: Delivery Friction
A specific module, step, or access issue blocked the buyer from making progress. They abandoned due to a technical or instructional barrier, not lack of intent.
Identify the specific friction point. Add a walkthrough video or simplify the action step. Check if this is Pattern RC-4 (appears 3+ times in 30 days).
RC-5: External Circumstance
Life event, financial change, or scheduling conflict unrelated to the offer. Not a product signal.
Process refund. Offer to pause or defer for 90 days. Add them to a reactivation sequence for 90 days post-refund.
RC-6: Guarantee-Exploiting Buyer
Pattern of behaviour suggesting the purchase was made primarily to consume content with the intent to refund. Completion of entire programme before refund request.
Process refund. Flag the email in your CRM. Do not offer to future cohorts. Review guarantee language to reduce attraction of this profile.
RC-1 asks whether the offer serves the buyer's circumstances. RC-2 compares actual copy with actual delivery. RC-3 examines timing and proposes an early win and truthful timeline. RC-4 investigates a specific technical or instructional barrier, with three occurrences in 30 days as its named pattern. RC-5 records external circumstances and suggests an optional ninety-day pause or later reactivation. Such circumstances can still inform product design.
RC-6 labels suspected guarantee exploitation. Completing a course before requesting a refund is not proof of dishonest intent. Don't turn that single observation into an automatic blacklist or denial. Any real refund response must honor the actual offer terms and evidence.
Here is the source's full reply for study:
Forensic Reply Template Hi [Name], I'm processing your refund now — you'll see it in 3–5 business days. Before I do, I'd genuinely appreciate 60 seconds of honest feedback. Not to change your mind — I just want to understand what happened so I can make this better. What was the single biggest gap between what you expected and what you found? You don't need to be kind about it. Your honest answer is worth more to me than the sale. Either way, your refund is on its way.
Its “before processing” wording conflicts with “processing now” and confirmation in the same message. The intended useful principle is optional feedback without holding the refund hostage. Confirm only what has happened. Replace the 3–5-business-day estimate if it does not match the actual processor situation. Do not make a response a condition of a refund.
Dropout detection covers four distinct signals and suggested messages:
Signal
Trigger Condition
Response Action
No first login
No access to course platform within 72 hours of purchase
Send personal plain-text email: 'Your first step takes 8 minutes. Here's the link. Is there anything blocking you?'
Module 1 not started
7 days post-purchase, Module 1 incomplete
Send: 'Quick check-in — did you get a chance to look at Module 1 yet? I ask because most people who don't start in week 1 don't finish, and I want to make sure you do.'
Progress stall — mid programme
No new activity for 10 consecutive days
Send personal voice message (Loom, 60 seconds): acknowledge the stall, identify the last module completed, give one specific micro-action to restart.
Community silence
Member has not posted or commented in 14 days
Tag in a relevant thread: '@[Name] — I think this applies to what you're working on' to re-engage without pressure.
No login at 72 hours differs from Module 1 incomplete at seven days. The second row's label says not started, but the condition says incomplete. Preserve that distinction. Ten days without new activity and fourteen days without a community post are further signals, not proof of failure. Some learners consume without posting. Any check-in should fit the person's context and actual available next step; the source's claims about week-one completion need evidence.
Phase 6 — Map the next problem
The Brunson-style chain starts with Problem A and asks what appears after its solution. That next need can inform a core offer, advanced support or continuity. It is not certain every solution creates a paid next need, or that the operator is the only person who sees it.
Look for the five types of evidence below. Each has a different location, example and proposed implication.
Signal Type
Where It Appears
Example
Product Implication
The 'Now What?' Question
Exit interviews, community posts, support tickets in weeks 3–6 post-purchase
I've got 10 leads now — how do I convert them to calls?
The next offer is a call conversion or sales training product
The Unexpected Bottleneck
Support tickets referencing a new problem that emerged after using your method
Your system worked but now I'm overwhelmed with the volume and can't keep up
The next offer is a fulfilment, delegation, or automation product
I wish there was a section on what to do after you get the first result
The next offer covers the scaling or consistency phase
The Comparison Reference
Community posts, email replies
Your stuff is great for getting started but I've also been looking at [X] for the next step
The next offer competes directly with what buyers are going to find elsewhere — build it first
The Referral Qualifier
Exit interviews question 7: 'Who else do you know who needs this?'
'My colleague does, but she's further along than I was — she'd need something more advanced'
There is a more advanced buyer segment who needs a higher-tier version of the transformation
A buyer asking how to turn ten leads into calls suggests a conversion need. Overload after success suggests capacity or delivery help. A request for what comes next suggests consistency or scaling support. Comparison with another provider and a referral to a more advanced colleague can reveal different segments. Validate demand and fit before treating a comment as a product order.
Use the full A–D chain template and cite the evidence for each next step. Do not invent offers or prices to fill blanks.
Step
Problem
Current Offer (if exists)
Next Offer (to build)
Evidence Source
Problem A
[What the buyer struggled with before your MVO]
[Your MVO name + tier + price]
Already built
Pre-purchase research
Problem B
[What they struggle with after getting the MVO result]
[Core Offer name if built]
[Describe what Core Offer needs to cover]
[Exit interview / support ticket citation]
Problem C
[What they struggle with after the Core Offer]
[High-ticket / DWY if built]
[Describe what next tier needs to cover]
[Exit interview / community post citation]
Problem D
[What they struggle with at scale]
[Continuity / Inner Circle]
[Describe ongoing support needed]
[Top-buyer conversation / mastermind request]
The source references exit-interview questions 6 and 7 but does not supply the full interview here. It also assumes related tier assets may exist. Preserve missing evidence and assets as gaps rather than treating the chain as a completed roadmap.
Phase 7 — Check the method's name and meaning
Every 90 days, inspect how buyers describe the method. Naming can change as understanding improves, without changing the underlying work. The source's 10× label describes a naming test, not proven tenfold performance.
Read the current name to five new avatar-matched people. Ask for an excitement score from 1–10 and what they think the method does. The source triggers renaming below 7 or when the description mismatches. It also says failure on two naming criteria initiates a cycle. Preserve both rules and record which one triggered review.
Learn all five criteria, including every pass and fail example:
Criterion
Test
Pass
Fail Example
Specificity
Does it describe a specific process, not a general category?
'AI Forensic Offer Autopsy' — describes a specific diagnostic action
'Marketing System' — describes a category
Outcome implied
Does the name imply the result without stating it generically?
'Lead Generation Programme' — states category, implies nothing specific
Distinctiveness
Does it sound like something only you do, or like a commodity?
'The Reverse Funnel Method' — named and owned
'Funnel Strategy' — generic, anyone says this
Repeatability
Can your buyer explain it to a colleague in one sentence?
Yes — 'It's a system where you build the backend offer first and work backward to the lead magnet'
No — 'It's kind of like a multi-step thing for growing your audience...'
Curiosity gap
Does it make someone who has not heard of it want to ask what it is?
'The Forensic Critic Positioning' — provokes 'what's that?'
'Content Strategy Framework' — provokes nothing
Specificity names a process. Implied outcome suggests a credible result. Distinctiveness reduces confusion with generic categories. Repeatability asks whether a buyer can explain it. Curiosity asks whether the name creates a meaningful question. A phrase described as named and owned does not establish legal exclusivity.
The five rename steps and full eight-asset checklist follow:
Source procedure for study:
Generate 10 new mechanism name candidates using the following structure: [Adjective/Method Type] + [Verb or Descriptor] + [Container Word].
Test the top 3 names with 5 avatar-matched individuals using the 10× Rename Test. Score each on excitement (1–10) and description accuracy.
Select the winner. Requires a score of 7+ average AND accurate description from 4 of 5 testers.
Update the mechanism name across: sales page, email sequence (Days 8–10), all ad creatives, course platform titles, and GEO schema markup.
Log the rename in Airtable: old name, new name, date, test scores, and conversion rate before and after the 30 days following rename.
Source procedure for study:
☐ Sales page — headline, mechanism section, and all stack slide references
☐ Email nurture sequence — Days 8, 9, and 10 (mechanism introduction emails)
☐ Paid ad copy — all active creatives using the mechanism name
☐ Course platform — module titles and overview description
☐ YouTube and podcast episode titles referencing the mechanism
☐ AEO/GEO schema — branded methodology keywords updated in L0 and L1 keyword grid
☐ LLMs.txt file — mechanism name updated in authority declaration section
☐ Pillar article — update H 1 and mechanism definition section
The structure for ten candidates is adjective or method type, plus verb or descriptor, plus container word. Test the top three names with five people. Acceptance requires an average 7+ and accurate descriptions from four of five. This is formative feedback, not conclusive market validation. The source does not define a complete accuracy-scoring method or candidate-ranking formula.
Record old and new names, dates, scores and thirty-day before/after conversion observations. Do not call that observational change causal proof. The L0/L1 keyword grid, authority declaration, schema implementation and LLMs.txt structure are referenced but absent here. Updating them cannot guarantee search rankings or generated citations; current official guidance must be checked during implementation.
Phase 8 — Write one justified action recommendation
The four actions are Scale, Iterate, Kill and Launch Next. The source says to prioritize the highest in the stack but lists Scale first. Its conditions can overlap. It supplies no complete precedence algorithm. As an authored clarification, investigate unresolved critical delivery or kill indicators before recommending increased traffic.
Scale
The source requires cold conversion above 2%, refunds below 5%, ascension above 10%, no critical value-variable decline and alignment between buyer language and copy. It proposes increasing paid spend no more than 20% per day, monitoring CPA and refunds daily for seven days, adding a second traffic source based on effective organic content, rewriting the headline and hero from the top three acute-pain phrases, and activating ascension for completers.
Those conditions and spending steps are not universal safe operating rules. Capacity and unit economics still matter. Changing traffic and copy together confounds attribution. This lesson does not authorize or perform spending, launches or CRM changes.
Iterate
The source describes one or two below-threshold metrics with a diagnosable fix that does not require rebuilding the core method or rerecording the programme. Preserve every test and window:
Failing Metric
Iteration Action
Test Window
Cold conversion below 1.5%
A/B test new headline using PAIN-ACUTE buyer language. Test a stronger guarantee (move one level up the guarantee hierarchy). Do not change both simultaneously.
14 days — minimum 200 visitors per variant
Opt-in rate below 15%
Rewrite lead magnet headline to a more specific, faster result. Test a different lead magnet format (tool/quiz vs PDF).
14 days — minimum 200 visitors per variant
Email open rate below 22%
Rewrite Days 1–3 subject lines using PAIN-ACUTE and DESIRE-HIDDEN tags. Test plain-text vs formatted email on Day 2.
7 days — minimum 100 sends per variant
Time Delay variable degradation
Add a documented Quick Win deliverable to Module 1. Send a '72-hour check-in' email that tells buyers exactly what their first win should be and when.
Immediate — apply to next 10 buyers and compare Day 7 engagement
Ascension rate below 8%
Rewrite ascension sequence. Change the trigger point — test presenting the Core Offer earlier (Day 14 vs Day 21 post-MVO purchase).
30 days — compare ascension rate before and after trigger change
Do not change headline and guarantee simultaneously in the named conversion test. The source's 200 visitors per variant and 100 email sends per variant are minimum suggestions, not adequate statistical power for every case. Record the actual test design. Before/after ascension changes over thirty days can reflect other changes too.
Kill assessment and redesign
The source lists refunds above 15%, cold conversion below 0.5% after 500+ visitors, completion below 40%, or at least two root-cause patterns appearing three times without a diagnosable fix. Its punctuation leaves some conjunction scope unclear. Do not implement it as an automatic business shutdown. The related monthly scorecard instead calls for a separate Kill Assessment; preserve that procedural distinction.
The source's useful lesson is to examine evidence without attachment to past work. Preserve buyer language; document unsuitable-fit evidence in a Negative Avatar profile; inspect what buyers thought they were solving and whether another offer serves it; then return to MVO offer construction with the findings. Its referenced Phase 5 Negative Avatar template is not actually supplied here. Its statement about most millionaires' failed offers is an unverified generalization, not evidence needed for a decision.
Launch next
The source asks for three or more consistent Problem B signals, a current offer meeting Scale criteria, and capacity to build and deliver. Use the next-problem evidence as the new offer brief. It proposes completing the current ascension sequence first, positioning the new tier around the actual Problem B, and running beta testing before public launch.
An absent ascension funnel does not prove a new product will cannibalize the current one. Treat that as a risk to assess. Do not invent a beta process or assume three comments establish demand. The source provides recommendations; no launch occurs here.
Follow the standing calendar without missing urgent triggers
Retain all eight cadence rows and outputs. The listed durations are planning estimates, not measurements.
Cadence
Activity
Time Required
Output
Every Monday (15 min)
Pull the seven funnel health metrics from Phase 1. Log in Airtable. Flag any metric below threshold.
15 minutes
Weekly metrics log. Flag any triggered audit.
Every Tuesday (20 min)
Review all new support tickets and email replies from the past 7 days. Tag language using the Phase 3 tagging system.
20 minutes
New language entries in mining database.
Every Wednesday (10 min)
Scan community platform. Screenshot any post with 3+ reactions or substantive questions. Archive and tag.
10 minutes
Community language additions to database.
Every Thursday (10 min)
Check for new refunds. Process any refund through the 5-step Refund Forensics Protocol.
10 minutes per refund
Refund archive updated. Patterns checked.
Every Friday (20 min)
Weekly audit summary: what changed this week, any patterns emerging, any trigger thresholds crossed?
20 minutes
Weekly Forensic Summary note in Airtable.
After every 10 sales
Full 8-Phase Audit. Block 2.5–3 hours. Do not skip phases.
Review full language mining database. Identify top 5 new phrases for copy deployment. Update sales page if PAIN-ACUTE or DESIRE-HIDDEN tags have produced better phrases than current copy.
60–90 minutes
Copy update brief. Sales page revision if warranted.
Quarterly (every 90 days)
Full 8-Phase Audit + Mechanism Freshness Test + Product Chain Map update + Value Ladder gap analysis.
Half day
90-Day Forensic Report. Product roadmap updated.
Thursday's refund review is an additional checkpoint, not permission to wait past the 24-hour protocol. A full audit is estimated at 2.5–3 hours; the quarterly trigger says three hours while the calendar says half a day. Record the difference rather than promising a fixed duration. The first Monday language review and the day 30 launch trigger are separate activities.
Define the database without pretending it is complete
The source claims five linked tables, but fully specifies only three. They are Buyer Language, Audit Records and Refund Records. Preserve every defined field below.
Field Name
Field Type
Purpose
Phrase ID
Autonumber
Unique identifier for each phrase
Verbatim Phrase
Long text
Exact words — never edited
Source
Single select
Email Reply / Support Ticket / Community / Exit Interview / Refund / Sales Call
10-Sale / First Refund / Conversion Drop / 30-Day / 90-Day / Ascension Anomaly
Offer Audited
Link → Offers table
Phase 1 Flags
Long text
Which metrics below threshold
Value Equation Finding
Long text
Which variable degraded and evidence
Refund Patterns
Long text
RC codes appearing 2+ times
Next Problem Signal
Long text
Problem B identified if applicable
Mechanism Rename Triggered
Checkbox
Action Selected
Single select
Scale / Iterate / Kill / Launch Next
Action Brief
Long text
Specific changes to implement
Review Date
Date
30 days after — check if action produced results
Field Name
Field Type
Purpose
Refund ID
Autonumber
Buyer
Link → Buyers table
Offer
Link → Offers table
Date Requested
Date
Verbatim Refund Message
Long text
Never paraphrase
Root Cause Code
Single select
RC-1 through RC-6
Forensic Reply Sent
Checkbox
Response Received
Long text
Buyer's answer to forensic reply if they responded
Negative Avatar Update
Link → Negative Avatar table
These tables link to Offers, Buyers and Negative Avatar definitions that are not supplied. That makes three additional named dependencies, so the document does not define an exact five-table topology. No working database, automations or enforced relationships are delivered by this source.
The earlier language schema includes Conversion Lift but the later version replaces it with Phrase ID. An implementation proposal should retain both requirements explicitly. Compound-trigger logging also conflicts with a single-select Trigger Type. Choose a multi-value design or additional notes deliberately; do not pretend the single field records all simultaneous triggers.
The Audit Records table uses root-cause patterns 2+ while the master scorecard uses 3+. Preserve the conflict. The thirty-day review date is a reminder to examine outcomes, not evidence the action worked.
Complete the master scorecard and every checklist
The master scorecard contains header information, each phase's findings, up to three action items, owners and deadlines, and a thirty-day review date. Blank rows are requests for evidence, not proof that the audit passed.
Section
Field
Your Data
Header
Audit ID + Date
Header
Offer name + tier + launch date
Header
Trigger type that initiated this audit
Header
Total sales to date / Sales in last 30 days
Phase 1
Cold conversion rate
Phase 1
Refund rate (rolling 30 days)
Phase 1
Ascension rate (MVO to Core)
Phase 1
Primary funnel leak location (if any)
Phase 2
Value Equation variable with greatest degradation
Phase 2
Evidence supporting this finding
Phase 2
Specific offer change indicated
Phase 3
Top 3 new PAIN-ACUTE phrases mined this cycle
1. 2. 3.
Phase 3
Top 2 OBJECTION phrases not addressed in current copy
1. 2.
Phase 3
Any ANTI-LANGUAGE identified — remove from all assets
Phase 4
Heatmap finding (if session recordings reviewed)
Phase 4
Biggest drop-off point in funnel this cycle
Phase 5
Number of refunds this cycle
Phase 5
Most common root cause code
Phase 5
Any RC pattern appearing 3+ times (immediate action trigger)
Phase 6
Next Problem Signal identified? (Y/N)
Phase 6
Problem B description (if signal found)
Phase 6
Evidence source for Problem B
Phase 7
Mechanism name reviewed — passed or failed criteria?
☐ Pass ☐ Fail
Phase 7
Rename triggered? (Y/N)
Phase 8
Action Protocol selected
☐ Scale ☐ Iterate ☐ Kill ☐ Launch Next
Phase 8
Specific action items (max 3)
1. 2. 3.
Phase 8
Owner and deadline for each action
Review
Review date (30 days from today)
Read the full weekly, ten-sale and quarterly checklists below. They preserve the exact operational details of the source.
Source procedure for study:
Master Forensic Audit Checklist
Weekly Standing Ritual
☐ Monday: Pull 7 Phase 1 metrics, log in Airtable, flag thresholds
☐ Tuesday: Tag new support tickets and email replies by language type
☐ Wednesday: Scan community — archive posts with 3+ reactions
☐ Thursday: Process any new refunds through 5-step protocol
☐ Phase 5: Complete refund forensics for all refunds since last audit
☐ Phase 5: Check for RC patterns appearing 3+ times — trigger fix protocol if found
☐ Phase 6: Review exit interviews and community posts for Next Problem Signals
☐ Phase 6: Update Next Problem Chain Map if new signal found
☐ Phase 7: Run Mechanism Freshness Test if 90-day trigger is also active
☐ Phase 8: Select one Action Protocol — write action brief with owner and deadline
☐ Log completed scorecard in Airtable Audit Records table
☐ Set 30-day review calendar reminder
Quarterly Deep Audit (Add to Full Audit Above)
☐ Run Mechanism Freshness Test regardless of 90-day timer
☐ Run 10× Rename Test with 5 new avatar-matched individuals
☐ Update Next Problem Chain Map with full product roadmap review
☐ Review all ANTI-LANGUAGE tags — scrub from every active copy asset
☐ Review Value Ladder gap analysis — are all ascension sequences live and automated?
☐ Export full buyer language database — identify top 10 phrases not yet deployed in copy
☐ Brief for Mechanism Rename if test score below 7.0
☐ Update GEO/AEO schema with any new branded methodology terms
The full-audit text says not to skip phases, while its checklist limits a fresh mechanism test to the 90-day trigger. An editorial reconciliation is to review the existing freshness evidence each audit and mark whether a new test is due. That is a proposed clarification, not an exact source rule. The quarterly checklist explicitly calls for new five-person testing and the full roadmap review.
A complete record should distinguish observed data, source threshold, your interpretation, missing evidence and assigned action. It must not describe draft text as a completed audit, deployment or verified result.
Open the assigned Offer Scorecard source for the related monthly review. That source's worked example totals 49, not 51, and its schema has 35 fields, not 33; use its explanatory lesson with the original.
Read the Beta Testing Methodology SOP. Its Phase 5 supplies a six-field Negative Avatar template. Its nine-question exit interview is related material, but questions 6 and 7 ask about value/improvements and referral fit; they do not exactly match the next-problem interview referenced above.
Read the Negative Avatar Modelling SOP. This companion expands the profile, qualification and review system and refers back to this audit's refund protocol. Its rules contain differences that require the accompanying explanations; it is not an automatic buyer-classification system.
Read the two companion teaching sections below with their complete original-source appendices. Read the accompanying MVO Playbook V 5 teaching and full original appendix. The exact full next-problem interview, keyword grid and search-schema assets still require verified matching. Software names in the tables are examples, not verified links or installed services.
RISER NATION CORP is the project brand destination. Current spreadsheet assignments govern this lesson.
Turn in: a completed audit record with evidence for each applicable phase, a list of unresolved threshold or source questions, and one prioritized action brief with no more than three specific tasks, owners, deadlines and a review date. Keep it in your course work folder until the submission destination is confirmed. A reviewer should check evidence and conflicting conditions before approving any business action.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — POST-MVO FORENSIC AUDIT LOOP
The Closed-Loop Intelligence System That Turns Every Buyer Into Product Development Data
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
Most operators treat an offer launch as a one-directional event: build, launch, collect revenue. The Post-MVO Forensic Audit Loop treats every launch and every subsequent sale as a two-directional intelligence operation. Revenue flows in. Data flows back. That data becomes the raw material for every future product, every copy revision, every mechanism rename, and every ascension sequence.
This SOP defines the recurring ritual — triggered by specific events, not by calendar convenience — that transforms your buyer base from a revenue source into a product intelligence engine. It covers eight phases: sales velocity analysis, the Hormozi Value Equation Audit, buyer language extraction, conversion funnel diagnostics, refund and dropout forensics, Next Problem Signal mapping, mechanism freshness testing, and the action protocol that tells you exactly what to do with every finding.
The Hormozi Principle
Every 10 sales, stop. Run the Value Equation against what your buyers are actually telling you. If Dream Outcome clarity or Perceived Likelihood is dropping, you have a product signal — not a marketing problem. Most operators try to fix falling conversion with more ads. The Forensic Audit tells you whether the offer itself needs surgery first.
The Kennedy Rule
The money is in the data, not just the sale. Every refund, every support ticket, every reply-to-email, every community post is a market research document. You just have to build the system that reads them.
The Brunson Lens
Every solution creates a new problem. The Forensic Audit is where you find Problem B — the thing your buyers need next. That chain of problems is your entire product roadmap, handed to you free of charge by people who already trust you.
The Audit Trigger System
The Forensic Audit is not a monthly calendar event. It is triggered by specific sales and data thresholds. Waiting for a calendar date means you miss the signal window — the moment when buyer feedback is freshest and most actionable.
Trigger
Condition
Audit Scope
Priority
10-Sale Trigger
Every 10 new purchases of an offer (cumulative)
Full 8-Phase Audit
High — run within 72 hours of the 10th sale
First Refund Trigger
First refund or cancellation request on any offer tier
Ascension rate from any tier to the next falls below 10% for 21+ days
Phase 6 only (Next Problem Signal)
Medium — run within 1 week
Trigger Stack Rule
Multiple triggers can fire simultaneously. If the 10-Sale Trigger and a Conversion Drop Trigger both fire in the same week, run the full 8-Phase Audit once — not twice. Log the compound trigger in Airtable and note which signals were active at the time.
PHASE 1
Sales Velocity & Funnel Health Check
The quantitative foundation — what the numbers say before you talk to anyone
Purpose
Phase 1 establishes the numerical baseline before any qualitative analysis begins. It answers the question: is the offer working, stalling, or dying — and at which specific funnel stage is the problem located? You cannot run the deeper phases meaningfully without this map.
The Seven Funnel Health Metrics
Metric
Formula
Healthy Range
Action Threshold
Cold opt-in rate
Opt-ins / Total cold traffic
15–30%
Below 12%: landing page or traffic source problem
Cold MVO conversion rate
Sales / Total cold visitors
1–3%
Below 0.8%: offer, copy, or trust problem
Warm conversion rate
Sales / Warm list visitors
5–15%
Below 4%: email sequence or offer relevance problem
Email open rate (sequence)
Opens / Delivered (14-day sequence)
28–40%
Below 20%: subject line, sender reputation, or list quality problem
Email click-to-sale rate
Sales / Total email clicks
8–20%
Below 5%: landing page or offer mismatch with email audience
Refund rate
Refunds / Total sales (rolling 30 days)
Below 5%
Above 8%: expectation mismatch, delivery failure, or wrong buyer profile
Ascension rate (MVO to Core)
Core Offer purchases / MVO buyers
10–20%
Below 8%: ascension sequence missing or wrong offer presented at wrong time
The Diagnostic Flow Chart
Run through this sequence. Stop at the first 'Yes' — that is your primary problem to solve before any other phase of this audit matters.
1. Is cold traffic volume sufficient? (Minimum 200 unique visitors to judge conversion rate accurately)
– No → Traffic problem. Do not adjust offer or copy until you have enough data. Solve distribution first.
– Yes → Continue to step 2.
2. Is the opt-in rate above 12%?
– No → Hook or landing page problem. The market is seeing the offer and not raising their hand. Fix the lead magnet, headline, or traffic targeting before anything else.
– Yes → Continue to step 3.
3. Is the cold conversion rate above 0.8%?
– No → Sales page, offer stack, or trust problem. Proceed to Phase 2 (Value Equation Audit) and Phase 4 (Funnel Diagnostic) before spending more on ads.
– Yes → Continue to step 4.
4. Is the refund rate above 8%?
– Yes → Expectation mismatch or delivery failure. Proceed directly to Phase 5 (Refund Forensics). This is the most urgent problem in the stack.
– No → Continue to step 5.
5. Is the ascension rate below 8% after 60+ days of live offer?
– Yes → Ascension sequence failure. Proceed to Phase 6 (Next Problem Signal). The value ladder exists on paper but buyers are not moving up it.
– No → Offer is healthy at the quantitative level. Proceed to Phase 2 to find optimisation opportunities.
Hormozi's framework applied to real buyer data — after every 10 sales
The Framework
Hormozi's Value Equation states that the perceived value of any offer equals the Dream Outcome multiplied by the Perceived Likelihood of Achievement, divided by Time Delay multiplied by Effort and Sacrifice. Most operators use this to design an offer once. The Forensic Audit uses it as a repeating diagnostic — after every 10 sales — to detect where perceived value is eroding before that erosion shows up as a conversion drop.
The Value Equation
(Dream Outcome × Perceived Likelihood of Achievement) ÷ (Time Delay × Effort & Sacrifice Required) = Perceived Offer Value. Maximise the numerator. Minimise the denominator. When conversion drops, one of these four variables has shifted in the buyer's mind — not necessarily in reality.
Running the Four-Variable Audit
For each variable, you need evidence from buyer conversations — not your own assumptions. The data sources listed below tell you what buyers actually believe, not what you intended them to believe.
Variable 1 — Dream Outcome Clarity
The question: are buyers buying your offer because they can picture the specific outcome, or because the category sounds relevant?
Audit Question
Data Source
Red Flag Signal
Can buyers describe the specific result they expect — in numbers and timeframes — before the offer is delivered?
Onboarding survey (baseline), application form responses, sales call recordings
Vague answers like 'I want to grow my business' or 'get more organised' — no specific metric or timeframe
Does the language buyers use to describe the outcome match the language used on the sales page?
Support ticket replies, community posts, direct email replies
Buyers describe the outcome in completely different terms than your copy — the promise is not landing as intended
Are buyers purchasing for the stated outcome or for an unstated emotional outcome?
Exit interview question: 'What were you really hoping for that you couldn't say out loud?'
Stated goal is revenue; real goal is status, confidence, or validation. Your copy may be hitting the wrong desire layer.
Variable 2 — Perceived Likelihood of Achievement
The question: do buyers believe they specifically will get the result — not just that the method works in general?
Audit Question
Data Source
Red Flag Signal
Do buyers mention specific proof elements when describing why they purchased?
Sales call recordings, email reply: 'What made you decide to buy today?'
Buyers cite general reputation or brand trust — not specific case studies. Your proof is not match-specific enough.
Do buyers express doubt about whether it will work 'for their situation'?
Support tickets within first 72 hours of purchase, community posts
High volume of 'will this work for me if I have [specific constraint]?' questions
What is the objection most commonly raised before purchase that was not resolved by the sales page?
Price objection is a proxy for perceived likelihood — 'I'm not sure it's worth it' almost always means 'I'm not sure it will work for me'
Variable 3 — Time Delay
The question: do buyers believe the result is coming fast enough to justify the investment now?
Audit Question
Data Source
Red Flag Signal
What result do buyers expect first — and by when?
Onboarding survey question: 'What would make you feel this was worth it in the first 7 days?'
Buyers expect a result your offer cannot deliver in that timeframe — the promise is creating false urgency
Are buyers reaching out to ask 'when will I see results?' in the first week?
Support tickets, community posts, DMs within days 1–7
High support volume on timeline questions = promise of speed is not backed by delivery structure
Does the offer have a documented Quick Win within the first 72 hours?
Your own delivery SOP
No quick win = perceived time delay is infinite = refund risk spikes after day 7
Variable 4 — Effort and Sacrifice
The question: are buyers discovering that the offer requires more effort, time, or lifestyle change than they expected?
Audit Question
Data Source
Red Flag Signal
What do buyers say is 'harder than expected' in week 1 feedback?
Per-module pulse survey, community posts tagged 'stuck' or 'help'
Any step described as confusing or time-intensive that is supposed to be a quick win
Are buyers dropping off at a consistent action step?
Completion rate data by module (course platform analytics)
Below 60% completion at any single step = that step has an effort barrier that must be reduced or replaced with a done-for-you asset
What is the most common reason buyers have not started?
Check-in message to non-starters: 'We noticed you haven't accessed the programme yet — is everything okay?'
Answers involving 'too busy,' 'overwhelmed by where to start,' or 'waiting for the right time' = onboarding friction, not buyer intention
Value Equation Audit Output
After completing the four-variable review, fill in this table. It becomes the action brief for the offer's next iteration cycle.
Variable
Current Buyer Perception (evidence-based)
Target Perception
Specific Change Required
Dream Outcome Clarity
Perceived Likelihood
Time Delay
Effort & Sacrifice
PHASE 3
Buyer Language Mining
The copy intelligence protocol — every buyer is a copywriter working for free
Why Buyer Language Beats All Other Copy Sources
The best copy you will ever write is copy you did not write. It is the exact phrases your buyers use to describe their pain, their transformation, and their hesitation. Your job in this phase is to mine those phrases systematically, catalogue them by funnel function, and inject them into your sales page, email sequences, and ad scripts.
Kennedy's Copy Mining Rule
If you can use a phrase lifted word-for-word from a buyer's mouth in your sales copy, do it. That phrase has already passed the most important test: a real person in your market used it voluntarily to describe their own experience. No copywriter can beat that.
The Five Language Mining Sources
Source
What to Mine
Mining Method
Cadence
Email replies (to your nurture sequence)
Exact phrases describing pain, frustration, failed attempts, and desired outcomes. The most unfiltered language because buyers are replying privately.
Tag every reply in ActiveCampaign with: Pain / Desire / Objection / Anti-language. Export tagged replies monthly.
After every 10 new subscribers or weekly if list is active
Support tickets and help desk messages
Confusion points, unmet expectations, and implementation breakdowns. Also the highest-intensity emotional language because people are frustrated.
In Intercom or Help Scout, tag tickets with: Confusion / Expectation-Gap / Mechanism-Question / Praise. Review tags monthly.
Weekly review of new tickets — tag in real time
Community posts (Discord/Skool/Facebook)
Peer-to-peer language — how buyers describe the problem to each other, not to you. This is the most authentic version of the voice because there is no authority figure present.
GummySearch-style keyword monitoring. Screenshot any post with 3+ reactions or replies. Archive in Airtable.
Weekly scan of all community posts
Exit interview transcripts
Full before/during/after narrative in the buyer's own words. The richest single source of language per buyer.
Castmagic or Descript transcript. Highlight every phrase of 3–8 words that describes pain, transformation, or hesitation. Tag by funnel function.
After every exit interview — tag within 24 hours
Refund request messages
The language of unmet expectations. Tells you exactly where the sales page or delivery created a gap that cost you money.
Archive every refund message verbatim. Do not paraphrase. Tag with: Expectation-Gap / Wrong-Avatar / Delivery-Failure / External-Event.
Immediately upon receipt
The Language Tagging System
Every piece of buyer language gets tagged into one of six functional categories. Each category feeds a specific element of your marketing and sales copy.
Tag
Definition
Where It Gets Used in Copy
PAIN-ACUTE
Phrases describing urgent, active pain — happening right now. High emotional intensity.
Sales page Problem section, email Day 2 (Pain Awareness), ad hook (Cost-of-Inaction type)
PAIN-CHRONIC
Phrases describing long-term, background frustration — not urgent but persistent.
Lead magnet headline, email Day 3 (Cost of Inaction), ad hook (Mistake type)
DESIRE-EXPLICIT
Stated goals — what they say they want. Often surface-level.
Reasons they hesitated before buying or reasons they stopped engaging after buying.
Sales page FAQ section, email Day 11 (Objection Handling), retargeting ad variant 2
ANTI-LANGUAGE
Words and phrases that trigger instant distrust or repulsion in this avatar.
Remove from all copy immediately. Flag for sales team to avoid on calls.
The 3-to-8 Word Rule
The most actionable copy phrases are between 3 and 8 words long. Single words are too vague. Full sentences are too long to use directly in headlines. Three to eight words — extracted verbatim from buyer language and tagged by function — are what you are mining for in every source above.
Practical Example
A buyer writes in an email reply: 'I've been stuck spinning my wheels for months and I genuinely have no idea what to try next.' The phrase 'spinning my wheels' is Pain-Chronic. 'No idea what to try next' is Pain-Acute. Both go directly into your copy swipe file. Neither of those phrases would have come from a copywriter sitting at a desk.
The Language Mining Database (Airtable Schema)
Field
Type
Notes
Phrase
Long text
Exact verbatim — never paraphrase or clean up. The rawness is the value.
Source
Single select
Email Reply / Support Ticket / Community Post / Exit Interview / Refund Message / Sales Call
Recency matters — language evolves as the market evolves
Deployed
Checkbox
Checked once this phrase has been placed into active copy
Deployed in
Long text
Which specific asset: sales page / email day N / ad creative / etc.
Conversion lift
Number
If A/B tested — record the conversion difference when this phrase was used
PHASE 4
Conversion Funnel Diagnostic
Finding the exact page where money is leaking
The Leak Diagnosis Framework
Every conversion problem has a location. Traffic goes cold, then warm, then hot. Money either converts at each stage or it leaks. The Forensic Audit maps exactly which stage is leaking, because the fix for a landing page problem is completely different from the fix for a sales page problem, which is completely different from the fix for a checkout problem.
Funnel Stage
Primary Metric
If Below Threshold
Most Likely Cause
First Fix to Test
Ad to landing page (click-through)
CTR above 1.5% (cold), above 3% (warm)
Hook or creative problem
Ad creative does not match the traffic source's intent or awareness level
Test 3 new hooks targeting Problem-Aware stage rather than Solution-Aware
Landing page to opt-in
Above 25% (cold)
Headline or offer mismatch
Lead magnet does not solve a specific enough problem, or headline is too generic
Rewrite headline using PAIN-ACUTE tags from Phase 3. Narrow the lead magnet promise.
Opt-in to sales page visit (email sequence)
Above 15% click-through on Day 9 email (offer introduction)
Email sequence engagement drop
Sequence is educating without pre-suading. Buyers are not being moved through the awareness ladder.
Inject buyer language (Phase 3 tags) into email subjects. Add one case study email on Day 6.
Sales page to add-to-cart
Above 3% (cold), above 8% (warm)
Offer stack or trust problem
Stack does not clearly exceed the price. Or proof does not match the exact promise.
Add one Proof-to-Promise-Matched testimonial above the fold. Test a stronger guarantee.
Add-to-cart to purchase
Above 60%
Checkout friction or final objection
Price shock at checkout (hidden fees or tax), payment option missing, trust signal absent
Add order summary with value stack visible on checkout page. Add payment plan option.
Post-purchase to first login / first module
Above 70% within 48 hours of purchase
Onboarding failure
Welcome email is generic, first step is unclear, or access instructions are confusing
Rewrite welcome email with specific 'Your first step is this, takes 8 minutes' instruction. Add a Loom walkthrough video.
Heatmap & Session Recording Protocol
Numbers tell you where the leak is. Session recordings tell you why. Use Hotjar or Microsoft Clarity on the sales page and landing page. Run this protocol after every 10-Sale Trigger.
1. Set up Hotjar on sales page and landing page if not already active. Minimum 200 sessions before drawing conclusions.
2. Watch scroll depth heatmap: if 70%+ of visitors are not reaching the offer stack, the page is losing them in the problem section or the story. The copy before the offer is too long or too weak.
3. Watch click map: what are visitors clicking that is not a CTA? This reveals unmet curiosity — they want information you have not provided.
4. Watch 5 session recordings of visitors who scrolled to the bottom but did not convert. Note the exact moment they stop engaging.
5. Watch 5 session recordings of visitors who converted. Note what they did differently — faster scroll to specific section, immediate click of CTA.
PHASE 5
Refund & Dropout Forensics
The data most operators ignore is the most valuable data available
The Forensic Mindset Shift
A refund is not a failure event. It is a data packet. A dropout is not a personal rejection. It is a diagnostic signal. Operators who treat refunds as problems to minimise and hide from lose the single most informative feedback loop in their entire business.
Hormozi on Refund Data
Your refund rate and your dropout rate are not performance metrics. They are product diagnostics. Each one tells you one of three things: you attracted the wrong buyer, a specific module has a fatal friction point, or your guarantee is drawing people who should never have purchased. Mine every single one without ego.
The Refund Forensics Protocol
Every refund request must be processed through this protocol within 24 hours of receipt, regardless of whether the refund is granted.
Step
Action
Output
1. Archive the message
Save the full text of the refund request verbatim in Airtable — every word. Never paraphrase. Assign it an ID number.
Verbatim refund archive entry
2. Classify the root cause
Assign one primary root cause from the taxonomy below. One cause per refund — force the classification.
Root cause tag on Airtable record
3. Send the forensic reply
Before processing the refund, send the forensic reply template (see below). You are not negotiating — you are collecting data.
Reply sent, response captured if they reply
4. Update the Negative Avatar profile
If this refund adds evidence to an existing Negative Avatar pattern, update that profile. If it reveals a new pattern, start a new profile.
Negative Avatar Airtable record updated
5. Check for pattern
Is this the 2nd or 3rd refund citing the same root cause? If yes, trigger the relevant fix protocol from Phase 8.
Pattern check completed. Fix protocol triggered if threshold reached.
Refund Root Cause Taxonomy
Root Cause Code
Definition
Immediate Action
RC-1: Wrong Avatar
The buyer does not fit the target profile that the offer was designed for. They bought based on the category but are not the person the transformation serves.
Review ad targeting and sales page 'This is NOT for you if...' section. Strengthen avatar-specific language on the sales page.
RC-2: Expectation Gap — Copy
The sales page or email sequence created a promise that the offer does not fulfil. The buyer expected something different from what was delivered.
Compare the refund language to the sales page promises verbatim. If the gap is real, fix the copy or fix the delivery — not one without the other.
RC-3: Expectation Gap — Timing
The buyer expected the result faster than the offer delivers. Time Delay variable of the Value Equation was miscalibrated.
Add a Quick Win in the first 72 hours. Add a timeline disclaimer to the sales page: 'Most members see [first result] by day [N].'
RC-4: Delivery Friction
A specific module, step, or access issue blocked the buyer from making progress. They abandoned due to a technical or instructional barrier, not lack of intent.
Identify the specific friction point. Add a walkthrough video or simplify the action step. Check if this is Pattern RC-4 (appears 3+ times in 30 days).
RC-5: External Circumstance
Life event, financial change, or scheduling conflict unrelated to the offer. Not a product signal.
Process refund. Offer to pause or defer for 90 days. Add them to a reactivation sequence for 90 days post-refund.
RC-6: Guarantee-Exploiting Buyer
Pattern of behaviour suggesting the purchase was made primarily to consume content with the intent to refund. Completion of entire programme before refund request.
Process refund. Flag the email in your CRM. Do not offer to future cohorts. Review guarantee language to reduce attraction of this profile.
The Forensic Reply Template
Send this before processing the refund. Do not hold the refund hostage — you are collecting data, not negotiating. Include the refund confirmation in the same message.
Forensic Reply Template
Hi [Name], I'm processing your refund now — you'll see it in 3–5 business days. Before I do, I'd genuinely appreciate 60 seconds of honest feedback. Not to change your mind — I just want to understand what happened so I can make this better. What was the single biggest gap between what you expected and what you found? You don't need to be kind about it. Your honest answer is worth more to me than the sale. Either way, your refund is on its way.
Dropout Detection Protocol
Dropouts — buyers who purchase but stop engaging before completing the programme — are often more informative than refunders because they had enough intent to stay but something specific stopped them.
Signal
Trigger Condition
Response Action
No first login
No access to course platform within 72 hours of purchase
Send personal plain-text email: 'Your first step takes 8 minutes. Here's the link. Is there anything blocking you?'
Module 1 not started
7 days post-purchase, Module 1 incomplete
Send: 'Quick check-in — did you get a chance to look at Module 1 yet? I ask because most people who don't start in week 1 don't finish, and I want to make sure you do.'
Progress stall — mid programme
No new activity for 10 consecutive days
Send personal voice message (Loom, 60 seconds): acknowledge the stall, identify the last module completed, give one specific micro-action to restart.
Community silence
Member has not posted or commented in 14 days
Tag in a relevant thread: '@[Name] — I think this applies to what you're working on' to re-engage without pressure.
PHASE 6
The Next Problem Signal
Brunson's chain — every solution creates a new problem and that problem is your next product
The Chain Mapping Framework
Brunson's core insight is that you do not need to invent products. You need to observe what your buyers need next after they get the result your current offer provides. Every solution creates a new problem. Map that chain and you have your entire product roadmap handed to you by buyers who already trust you.
The Chain Logic
Your MVO solves Problem A. But now your buyer has Problem B — the next challenge that emerges once A is solved. And after B comes C. Each step in this chain is an offer. The buyer does not know you are building a roadmap. They just know they solved one problem and now have the next one. You are the only person who can see the full map.
Next Problem Signal Mining
The Next Problem Signal lives in very specific places. You are not looking for general feedback — you are looking for statements that reveal what the buyer needs immediately after completing or benefiting from your current offer.
Signal Type
Where It Appears
Example
Product Implication
The 'Now What?' Question
Exit interviews, community posts, support tickets in weeks 3–6 post-purchase
I've got 10 leads now — how do I convert them to calls?
The next offer is a call conversion or sales training product
The Unexpected Bottleneck
Support tickets referencing a new problem that emerged after using your method
Your system worked but now I'm overwhelmed with the volume and can't keep up
The next offer is a fulfilment, delegation, or automation product
I wish there was a section on what to do after you get the first result
The next offer covers the scaling or consistency phase
The Comparison Reference
Community posts, email replies
Your stuff is great for getting started but I've also been looking at [X] for the next step
The next offer competes directly with what buyers are going to find elsewhere — build it first
The Referral Qualifier
Exit interviews question 7: 'Who else do you know who needs this?'
'My colleague does, but she's further along than I was — she'd need something more advanced'
There is a more advanced buyer segment who needs a higher-tier version of the transformation
The Next Problem Chain Template
After each Forensic Audit, map what you have learned about the chain. This becomes your product roadmap and your ascension sequence design document.
Step
Problem
Current Offer (if exists)
Next Offer (to build)
Evidence Source
Problem A
[What the buyer struggled with before your MVO]
[Your MVO name + tier + price]
Already built
Pre-purchase research
Problem B
[What they struggle with after getting the MVO result]
[Core Offer name if built]
[Describe what Core Offer needs to cover]
[Exit interview / support ticket citation]
Problem C
[What they struggle with after the Core Offer]
[High-ticket / DWY if built]
[Describe what next tier needs to cover]
[Exit interview / community post citation]
Problem D
[What they struggle with at scale]
[Continuity / Inner Circle]
[Describe ongoing support needed]
[Top-buyer conversation / mastermind request]
PHASE 7
Mechanism Freshness Test
Every 90 days: can the method be renamed to feel 10× more powerful?
Why Mechanisms Get Stale
The name you gave your methodology at launch was the best name available with the information you had at launch. After 90 days of buyer data, support conversations, and exit interviews, you know more about how your buyers think about the transformation than you did on day one. That knowledge should change how you describe the mechanism — not what the mechanism does, but how you name and frame it.
The 10× Rename Test
Take your current mechanism name. Read it to five people who match your target avatar and have not heard of your offer before. Ask them to rate how excited they are about it on a scale of 1–10 and describe what they imagine it involves. If the average score is below 7 or their description does not match what the mechanism actually does — rename it.
The Mechanism Naming Criteria
A great mechanism name passes all five of the following criteria. Evaluate your current name against each one:
Criterion
Test
Pass
Fail Example
Specificity
Does it describe a specific process, not a general category?
'AI Forensic Offer Autopsy' — describes a specific diagnostic action
'Marketing System' — describes a category
Outcome implied
Does the name imply the result without stating it generically?
'Lead Generation Programme' — states category, implies nothing specific
Distinctiveness
Does it sound like something only you do, or like a commodity?
'The Reverse Funnel Method' — named and owned
'Funnel Strategy' — generic, anyone says this
Repeatability
Can your buyer explain it to a colleague in one sentence?
Yes — 'It's a system where you build the backend offer first and work backward to the lead magnet'
No — 'It's kind of like a multi-step thing for growing your audience...'
Curiosity gap
Does it make someone who has not heard of it want to ask what it is?
'The Forensic Critic Positioning' — provokes 'what's that?'
'Content Strategy Framework' — provokes nothing
Mechanism Rename Protocol
If the current mechanism name fails two or more criteria above, initiate a rename cycle. This does not require rebuilding the offer — only renaming and re-describing the method across copy assets.
1. Generate 10 new mechanism name candidates using the following structure: [Adjective/Method Type] + [Verb or Descriptor] + [Container Word].
2. Test the top 3 names with 5 avatar-matched individuals using the 10× Rename Test. Score each on excitement (1–10) and description accuracy.
3. Select the winner. Requires a score of 7+ average AND accurate description from 4 of 5 testers.
4. Update the mechanism name across: sales page, email sequence (Days 8–10), all ad creatives, course platform titles, and GEO schema markup.
5. Log the rename in Airtable: old name, new name, date, test scores, and conversion rate before and after the 30 days following rename.
Mechanism Rename Asset Update Checklist
☐ Sales page — headline, mechanism section, and all stack slide references
☐ Email nurture sequence — Days 8, 9, and 10 (mechanism introduction emails)
☐ Paid ad copy — all active creatives using the mechanism name
☐ Course platform — module titles and overview description
☐ YouTube and podcast episode titles referencing the mechanism
☐ AEO/GEO schema — branded methodology keywords updated in L0 and L1 keyword grid
☐ LLMs.txt file — mechanism name updated in authority declaration section
☐ Pillar article — update H1 and mechanism definition section
PHASE 8
The Action Protocol
Kill / Iterate / Scale / Launch Next — making the right decision with the data
The Four Possible Outcomes
Every Forensic Audit produces one of four action recommendations. The decision tree below maps your audit findings to the correct action. Do not run multiple actions simultaneously — prioritise the one highest in the stack and complete it before starting the next.
Action 1 — SCALE
Conditions: cold conversion above 2%, refund rate below 5%, ascension rate above 10%, Value Equation audit shows no critical variable degradation, buyer language is consistent with sales page copy.
• Increase paid ad spend by no more than 20% per day. Monitor CPA and refund rate daily for the first 7 days of scaling.
• Add one new traffic source (second platform) using the best-performing organic content as the basis for ad creative.
• Rebuild the sales page headline and hero section using the top three PAIN-ACUTE language tags from Phase 3.
• Activate the ascension sequence to the next value ladder tier for all buyers who have completed the programme.
Action 2 — ITERATE
Conditions: one or two metrics below threshold, root cause is diagnosable, fix does not require rebuilding the core mechanism or re-recording the programme.
Failing Metric
Iteration Action
Test Window
Cold conversion below 1.5%
A/B test new headline using PAIN-ACUTE buyer language. Test a stronger guarantee (move one level up the guarantee hierarchy). Do not change both simultaneously.
14 days — minimum 200 visitors per variant
Opt-in rate below 15%
Rewrite lead magnet headline to a more specific, faster result. Test a different lead magnet format (tool/quiz vs PDF).
14 days — minimum 200 visitors per variant
Email open rate below 22%
Rewrite Days 1–3 subject lines using PAIN-ACUTE and DESIRE-HIDDEN tags. Test plain-text vs formatted email on Day 2.
7 days — minimum 100 sends per variant
Time Delay variable degradation
Add a documented Quick Win deliverable to Module 1. Send a '72-hour check-in' email that tells buyers exactly what their first win should be and when.
Immediate — apply to next 10 buyers and compare Day 7 engagement
Ascension rate below 8%
Rewrite ascension sequence. Change the trigger point — test presenting the Core Offer earlier (Day 14 vs Day 21 post-MVO purchase).
30 days — compare ascension rate before and after trigger change
Action 3 — KILL
Conditions: refund rate above 15%, cold conversion below 0.5% after 500+ visitors, completion rate below 40%, or two or more root cause patterns (from Phase 5) appearing three or more times without a diagnosable fix.
Kennedy's Kill Rule
Most millionaires have a trail of failed offers. Killing a broken offer is not failure — it is the system working correctly. The failure is continuing to run ads to a broken offer because you are emotionally attached to having built it. Archive all buyer data. That data survives even when the offer does not.
• Archive all buyer language from Phase 3 — it is valid copy intelligence regardless of offer outcome.
• Complete a Negative Avatar profile (Phase 5 template) to document who this offer should NOT be sold to in future.
• Run Phase 6 analysis specifically: what problem did buyers think they were solving, and is there a different offer that solves it correctly?
• Return to MVO Playbook Phase 2 (Offer Construction) with all accumulated data as the brief.
Action 4 — LAUNCH NEXT
Conditions: Phase 6 (Next Problem Signal) has produced three or more consistent signals pointing to a specific Problem B. Current offer is performing at Scale threshold or above. Capacity exists to build and deliver a new tier.
• The Next Problem Signal data from Phase 6 becomes the MVO brief for the new offer. The buyer language you have mined is the first draft of the sales page copy.
• Do not launch the next offer until the current offer's ascension sequence is built and automated. Launching upward without an ascension funnel means the new offer cannibalises the current one.
• Position the new offer as the solution to the specific Problem B you have documented — not as a generic upgrade.
• Run the new offer through the Beta Testing Methodology SOP (RISER Nation SOP Series) before public launch.
The 30-Day Forensic Audit Ritual Calendar
This is the standing operational rhythm. It runs continuously regardless of whether a specific trigger has fired that week. The trigger-based phases are in addition to this baseline ritual, not instead of it.
Cadence
Activity
Time Required
Output
Every Monday (15 min)
Pull the seven funnel health metrics from Phase 1. Log in Airtable. Flag any metric below threshold.
15 minutes
Weekly metrics log. Flag any triggered audit.
Every Tuesday (20 min)
Review all new support tickets and email replies from the past 7 days. Tag language using the Phase 3 tagging system.
20 minutes
New language entries in mining database.
Every Wednesday (10 min)
Scan community platform. Screenshot any post with 3+ reactions or substantive questions. Archive and tag.
10 minutes
Community language additions to database.
Every Thursday (10 min)
Check for new refunds. Process any refund through the 5-step Refund Forensics Protocol.
10 minutes per refund
Refund archive updated. Patterns checked.
Every Friday (20 min)
Weekly audit summary: what changed this week, any patterns emerging, any trigger thresholds crossed?
20 minutes
Weekly Forensic Summary note in Airtable.
After every 10 sales
Full 8-Phase Audit. Block 2.5–3 hours. Do not skip phases.
Review full language mining database. Identify top 5 new phrases for copy deployment. Update sales page if PAIN-ACUTE or DESIRE-HIDDEN tags have produced better phrases than current copy.
60–90 minutes
Copy update brief. Sales page revision if warranted.
Quarterly (every 90 days)
Full 8-Phase Audit + Mechanism Freshness Test + Product Chain Map update + Value Ladder gap analysis.
Half day
90-Day Forensic Report. Product roadmap updated.
Airtable Database Schema
All Forensic Audit data lives in a single Airtable base with five linked tables. This schema ensures every piece of buyer intelligence is connected across offers, buyers, and time periods.
Table 1 — Buyer Language
Primary table. Every tagged phrase from Phase 3 sources.
Field Name
Field Type
Purpose
Phrase ID
Autonumber
Unique identifier for each phrase
Verbatim Phrase
Long text
Exact words — never edited
Source
Single select
Email Reply / Support Ticket / Community / Exit Interview / Refund / Sales Call
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — POST-MVO FORENSIC AUDIT LOOP ",
"",
"The Closed-Loop Intelligence System That Turns Every Buyer Into Product Development Data",
"Kennedy × Hormozi × Brunson × 2026 Agentic Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"Most operators treat an offer launch as a one-directional event: build, launch, collect revenue. The Post-MVO Forensic Audit Loop treats every launch and every subsequent sale as a two-directional intelligence operation. Revenue flows in. Data flows back. That data becomes the raw material for every future product, every copy revision, every mechanism rename, and every ascension sequence.",
"",
"This SOP defines the recurring ritual — triggered by specific events, not by calendar convenience — that transforms your buyer base from a revenue source into a product intelligence engine. It covers eight phases: sales velocity analysis, the Hormozi Value Equation Audit, buyer language extraction, conversion funnel diagnostics, refund and dropout forensics, Next Problem Signal mapping, mechanism freshness testing, and the action protocol that tells you exactly what to do with every finding.",
"",
"The Hormozi Principle",
"Every 10 sales, stop. Run the Value Equation against what your buyers are actually telling you. If Dream Outcome clarity or Perceived Likelihood is dropping, you have a product signal — not a marketing problem. Most operators try to fix falling conversion with more ads. The Forensic Audit tells you whether the offer itself needs surgery first.",
"",
"The Kennedy Rule",
"The money is in the data, not just the sale. Every refund, every support ticket, every reply-to-email, every community post is a market research document. You just have to build the system that reads them.",
"",
"The Brunson Lens",
"Every solution creates a new problem. The Forensic Audit is where you find Problem B — the thing your buyers need next. That chain of problems is your entire product roadmap, handed to you free of charge by people who already trust you.",
"",
"The Audit Trigger System",
"The Forensic Audit is not a monthly calendar event. It is triggered by specific sales and data thresholds. Waiting for a calendar date means you miss the signal window — the moment when buyer feedback is freshest and most actionable.",
"",
"Trigger",
"Condition",
"Audit Scope",
"Priority",
"10-Sale Trigger",
"Every 10 new purchases of an offer (cumulative)",
"Full 8-Phase Audit",
"High — run within 72 hours of the 10th sale",
"First Refund Trigger",
"First refund or cancellation request on any offer tier",
"Phase 4 + Phase 5 only (Funnel Diagnostic + Refund Forensics)",
"Critical — run within 24 hours",
"Conversion Drop Trigger",
"Cold conversion rate drops 20% below prior 30-day average for 7+ consecutive days",
"Phase 1 + Phase 4 (Sales Velocity + Funnel Diagnostic)",
"High — run within 48 hours of threshold being crossed",
"30-Day Scheduled Trigger",
"30 calendar days after any offer's public launch date",
"Full 8-Phase Audit regardless of sale count",
"Standard — run on day 30 even if fewer than 10 sales",
"90-Day Deep Trigger",
"90 days post-launch or every 90 days for active offers",
"Full 8-Phase Audit + Mechanism Rename Assessment + Product Roadmap Update",
"Strategic — block 3 hours for this session",
"Ascension Anomaly Trigger",
"Ascension rate from any tier to the next falls below 10% for 21+ days",
"Phase 6 only (Next Problem Signal)",
"Medium — run within 1 week",
"",
"Trigger Stack Rule",
"Multiple triggers can fire simultaneously. If the 10-Sale Trigger and a Conversion Drop Trigger both fire in the same week, run the full 8-Phase Audit once — not twice. Log the compound trigger in Airtable and note which signals were active at the time.",
"",
"",
"PHASE 1",
"Sales Velocity & Funnel Health Check",
"The quantitative foundation — what the numbers say before you talk to anyone",
"",
"Purpose",
"Phase 1 establishes the numerical baseline before any qualitative analysis begins. It answers the question: is the offer working, stalling, or dying — and at which specific funnel stage is the problem located? You cannot run the deeper phases meaningfully without this map.",
"",
"The Seven Funnel Health Metrics",
"",
"Metric",
"Formula",
"Healthy Range",
"Action Threshold",
"Cold opt-in rate",
"Opt-ins / Total cold traffic",
"15–30%",
"Below 12%: landing page or traffic source problem",
"Cold MVO conversion rate",
"Sales / Total cold visitors",
"1–3%",
"Below 0.8%: offer, copy, or trust problem",
"Warm conversion rate",
"Sales / Warm list visitors",
"5–15%",
"Below 4%: email sequence or offer relevance problem",
"Email open rate (sequence)",
"Opens / Delivered (14-day sequence)",
"28–40%",
"Below 20%: subject line, sender reputation, or list quality problem",
"Email click-to-sale rate",
"Sales / Total email clicks",
"8–20%",
"Below 5%: landing page or offer mismatch with email audience",
"Refund rate",
"Refunds / Total sales (rolling 30 days)",
"Below 5%",
"Above 8%: expectation mismatch, delivery failure, or wrong buyer profile",
"Ascension rate (MVO to Core)",
"Core Offer purchases / MVO buyers",
"10–20%",
"Below 8%: ascension sequence missing or wrong offer presented at wrong time",
"",
"The Diagnostic Flow Chart",
"Run through this sequence. Stop at the first 'Yes' — that is your primary problem to solve before any other phase of this audit matters.",
"",
"1. Is cold traffic volume sufficient? (Minimum 200 unique visitors to judge conversion rate accurately)",
"– No → Traffic problem. Do not adjust offer or copy until you have enough data. Solve distribution first.",
"– Yes → Continue to step 2.",
"",
"2. Is the opt-in rate above 12%?",
"– No → Hook or landing page problem. The market is seeing the offer and not raising their hand. Fix the lead magnet, headline, or traffic targeting before anything else.",
"– Yes → Continue to step 3.",
"",
"3. Is the cold conversion rate above 0.8%?",
"– No → Sales page, offer stack, or trust problem. Proceed to Phase 2 (Value Equation Audit) and Phase 4 (Funnel Diagnostic) before spending more on ads.",
"– Yes → Continue to step 4.",
"",
"4. Is the refund rate above 8%?",
"– Yes → Expectation mismatch or delivery failure. Proceed directly to Phase 5 (Refund Forensics). This is the most urgent problem in the stack.",
"– No → Continue to step 5.",
"",
"5. Is the ascension rate below 8% after 60+ days of live offer?",
"– Yes → Ascension sequence failure. Proceed to Phase 6 (Next Problem Signal). The value ladder exists on paper but buyers are not moving up it.",
"– No → Offer is healthy at the quantitative level. Proceed to Phase 2 to find optimisation opportunities.",
"",
"Where to Pull This Data",
"",
"Metric",
"Source",
"Frequency to Review",
"Traffic volume and source",
"Google Analytics 4 + UTM parameters on all links",
"Weekly during active campaigns",
"Opt-in rate",
"GA4 conversion events + landing page platform (Kajabi/ClickFunnels)",
"Weekly",
"Sales conversion rate",
"CRM (GoHighLevel/HubSpot) + Stripe dashboard",
"Every 10 sales (Trigger)",
"Email sequence metrics",
"ActiveCampaign automation reports",
"Weekly",
"Refund rate",
"Stripe / ThriveCart refund report",
"Daily for first 30 days post-launch",
"Ascension rate",
"CRM pipeline stage movement report",
"Monthly",
"",
"",
"PHASE 2",
"The Value Equation Audit",
"Hormozi's framework applied to real buyer data — after every 10 sales",
"",
"The Framework",
"Hormozi's Value Equation states that the perceived value of any offer equals the Dream Outcome multiplied by the Perceived Likelihood of Achievement, divided by Time Delay multiplied by Effort and Sacrifice. Most operators use this to design an offer once. The Forensic Audit uses it as a repeating diagnostic — after every 10 sales — to detect where perceived value is eroding before that erosion shows up as a conversion drop.",
"",
"The Value Equation",
"(Dream Outcome × Perceived Likelihood of Achievement) ÷ (Time Delay × Effort & Sacrifice Required) = Perceived Offer Value. Maximise the numerator. Minimise the denominator. When conversion drops, one of these four variables has shifted in the buyer's mind — not necessarily in reality.",
"",
"Running the Four-Variable Audit",
"For each variable, you need evidence from buyer conversations — not your own assumptions. The data sources listed below tell you what buyers actually believe, not what you intended them to believe.",
"",
"Variable 1 — Dream Outcome Clarity",
"The question: are buyers buying your offer because they can picture the specific outcome, or because the category sounds relevant?",
"",
"Audit Question",
"Data Source",
"Red Flag Signal",
"Can buyers describe the specific result they expect — in numbers and timeframes — before the offer is delivered?",
"Onboarding survey (baseline), application form responses, sales call recordings",
"Vague answers like 'I want to grow my business' or 'get more organised' — no specific metric or timeframe",
"Does the language buyers use to describe the outcome match the language used on the sales page?",
"Support ticket replies, community posts, direct email replies",
"Buyers describe the outcome in completely different terms than your copy — the promise is not landing as intended",
"Are buyers purchasing for the stated outcome or for an unstated emotional outcome?",
"Exit interview question: 'What were you really hoping for that you couldn't say out loud?'",
"Stated goal is revenue; real goal is status, confidence, or validation. Your copy may be hitting the wrong desire layer.",
"",
"Variable 2 — Perceived Likelihood of Achievement",
"The question: do buyers believe they specifically will get the result — not just that the method works in general?",
"",
"Audit Question",
"Data Source",
"Red Flag Signal",
"Do buyers mention specific proof elements when describing why they purchased?",
"Sales call recordings, email reply: 'What made you decide to buy today?'",
"Buyers cite general reputation or brand trust — not specific case studies. Your proof is not match-specific enough.",
"Do buyers express doubt about whether it will work 'for their situation'?",
"Support tickets within first 72 hours of purchase, community posts",
"High volume of 'will this work for me if I have [specific constraint]?' questions",
"What is the objection most commonly raised before purchase that was not resolved by the sales page?",
"Sales call objection log, HARO-style DM conversations",
"Price objection is a proxy for perceived likelihood — 'I'm not sure it's worth it' almost always means 'I'm not sure it will work for me'",
"",
"Variable 3 — Time Delay",
"The question: do buyers believe the result is coming fast enough to justify the investment now?",
"",
"Audit Question",
"Data Source",
"Red Flag Signal",
"What result do buyers expect first — and by when?",
"Onboarding survey question: 'What would make you feel this was worth it in the first 7 days?'",
"Buyers expect a result your offer cannot deliver in that timeframe — the promise is creating false urgency",
"Are buyers reaching out to ask 'when will I see results?' in the first week?",
"Support tickets, community posts, DMs within days 1–7",
"High support volume on timeline questions = promise of speed is not backed by delivery structure",
"Does the offer have a documented Quick Win within the first 72 hours?",
"Your own delivery SOP",
"No quick win = perceived time delay is infinite = refund risk spikes after day 7",
"",
"Variable 4 — Effort and Sacrifice",
"The question: are buyers discovering that the offer requires more effort, time, or lifestyle change than they expected?",
"",
"Audit Question",
"Data Source",
"Red Flag Signal",
"What do buyers say is 'harder than expected' in week 1 feedback?",
"Per-module pulse survey, community posts tagged 'stuck' or 'help'",
"Any step described as confusing or time-intensive that is supposed to be a quick win",
"Are buyers dropping off at a consistent action step?",
"Completion rate data by module (course platform analytics)",
"Below 60% completion at any single step = that step has an effort barrier that must be reduced or replaced with a done-for-you asset",
"What is the most common reason buyers have not started?",
"Check-in message to non-starters: 'We noticed you haven't accessed the programme yet — is everything okay?'",
"Answers involving 'too busy,' 'overwhelmed by where to start,' or 'waiting for the right time' = onboarding friction, not buyer intention",
"",
"Value Equation Audit Output",
"After completing the four-variable review, fill in this table. It becomes the action brief for the offer's next iteration cycle.",
"",
"Variable",
"Current Buyer Perception (evidence-based)",
"Target Perception",
"Specific Change Required",
"Dream Outcome Clarity",
"",
"",
"",
"Perceived Likelihood",
"",
"",
"",
"Time Delay",
"",
"",
"",
"Effort & Sacrifice",
"",
"",
"",
"",
"",
"PHASE 3",
"Buyer Language Mining",
"The copy intelligence protocol — every buyer is a copywriter working for free",
"",
"Why Buyer Language Beats All Other Copy Sources",
"The best copy you will ever write is copy you did not write. It is the exact phrases your buyers use to describe their pain, their transformation, and their hesitation. Your job in this phase is to mine those phrases systematically, catalogue them by funnel function, and inject them into your sales page, email sequences, and ad scripts.",
"",
"Kennedy's Copy Mining Rule",
"If you can use a phrase lifted word-for-word from a buyer's mouth in your sales copy, do it. That phrase has already passed the most important test: a real person in your market used it voluntarily to describe their own experience. No copywriter can beat that.",
"",
"The Five Language Mining Sources",
"",
"Source",
"What to Mine",
"Mining Method",
"Cadence",
"Email replies (to your nurture sequence)",
"Exact phrases describing pain, frustration, failed attempts, and desired outcomes. The most unfiltered language because buyers are replying privately.",
"Tag every reply in ActiveCampaign with: Pain / Desire / Objection / Anti-language. Export tagged replies monthly.",
"After every 10 new subscribers or weekly if list is active",
"Support tickets and help desk messages",
"Confusion points, unmet expectations, and implementation breakdowns. Also the highest-intensity emotional language because people are frustrated.",
"In Intercom or Help Scout, tag tickets with: Confusion / Expectation-Gap / Mechanism-Question / Praise. Review tags monthly.",
"Weekly review of new tickets — tag in real time",
"Community posts (Discord/Skool/Facebook)",
"Peer-to-peer language — how buyers describe the problem to each other, not to you. This is the most authentic version of the voice because there is no authority figure present.",
"GummySearch-style keyword monitoring. Screenshot any post with 3+ reactions or replies. Archive in Airtable.",
"Weekly scan of all community posts",
"Exit interview transcripts",
"Full before/during/after narrative in the buyer's own words. The richest single source of language per buyer.",
"Castmagic or Descript transcript. Highlight every phrase of 3–8 words that describes pain, transformation, or hesitation. Tag by funnel function.",
"After every exit interview — tag within 24 hours",
"Refund request messages",
"The language of unmet expectations. Tells you exactly where the sales page or delivery created a gap that cost you money.",
"Archive every refund message verbatim. Do not paraphrase. Tag with: Expectation-Gap / Wrong-Avatar / Delivery-Failure / External-Event.",
"Immediately upon receipt",
"",
"The Language Tagging System",
"Every piece of buyer language gets tagged into one of six functional categories. Each category feeds a specific element of your marketing and sales copy.",
"",
"Tag",
"Definition",
"Where It Gets Used in Copy",
"PAIN-ACUTE",
"Phrases describing urgent, active pain — happening right now. High emotional intensity.",
"Sales page Problem section, email Day 2 (Pain Awareness), ad hook (Cost-of-Inaction type)",
"PAIN-CHRONIC",
"Phrases describing long-term, background frustration — not urgent but persistent.",
"Lead magnet headline, email Day 3 (Cost of Inaction), ad hook (Mistake type)",
"DESIRE-EXPLICIT",
"Stated goals — what they say they want. Often surface-level.",
"Sales page Dream Outcome section, email Day 4 (Common Mistakes), landing page subheadline",
"DESIRE-HIDDEN",
"Unstated goals — what they really want but do not say directly. Drives premium purchasing.",
"Sales page identity shift language, email Day 5 (Personal Story), high-ticket sales call framing",
"OBJECTION",
"Reasons they hesitated before buying or reasons they stopped engaging after buying.",
"Sales page FAQ section, email Day 11 (Objection Handling), retargeting ad variant 2",
"ANTI-LANGUAGE",
"Words and phrases that trigger instant distrust or repulsion in this avatar.",
"Remove from all copy immediately. Flag for sales team to avoid on calls.",
"",
"The 3-to-8 Word Rule",
"The most actionable copy phrases are between 3 and 8 words long. Single words are too vague. Full sentences are too long to use directly in headlines. Three to eight words — extracted verbatim from buyer language and tagged by function — are what you are mining for in every source above.",
"",
"Practical Example",
"A buyer writes in an email reply: 'I've been stuck spinning my wheels for months and I genuinely have no idea what to try next.' The phrase 'spinning my wheels' is Pain-Chronic. 'No idea what to try next' is Pain-Acute. Both go directly into your copy swipe file. Neither of those phrases would have come from a copywriter sitting at a desk.",
"",
"The Language Mining Database (Airtable Schema)",
"",
"Field",
"Type",
"Notes",
"Phrase",
"Long text",
"Exact verbatim — never paraphrase or clean up. The rawness is the value.",
"Source",
"Single select",
"Email Reply / Support Ticket / Community Post / Exit Interview / Refund Message / Sales Call",
"Tag",
"Multiple select",
"PAIN-ACUTE / PAIN-CHRONIC / DESIRE-EXPLICIT / DESIRE-HIDDEN / OBJECTION / ANTI-LANGUAGE",
"Offer",
"Link to Offers table",
"Which offer tier this language relates to",
"Date captured",
"Date",
"Recency matters — language evolves as the market evolves",
"Deployed",
"Checkbox",
"Checked once this phrase has been placed into active copy",
"Deployed in",
"Long text",
"Which specific asset: sales page / email day N / ad creative / etc.",
"Conversion lift",
"Number",
"If A/B tested — record the conversion difference when this phrase was used",
"",
"",
"PHASE 4",
"Conversion Funnel Diagnostic",
"Finding the exact page where money is leaking",
"",
"The Leak Diagnosis Framework",
"Every conversion problem has a location. Traffic goes cold, then warm, then hot. Money either converts at each stage or it leaks. The Forensic Audit maps exactly which stage is leaking, because the fix for a landing page problem is completely different from the fix for a sales page problem, which is completely different from the fix for a checkout problem.",
"",
"Funnel Stage",
"Primary Metric",
"If Below Threshold",
"Most Likely Cause",
"First Fix to Test",
"Ad to landing page (click-through)",
"CTR above 1.5% (cold), above 3% (warm)",
"Hook or creative problem",
"Ad creative does not match the traffic source's intent or awareness level",
"Test 3 new hooks targeting Problem-Aware stage rather than Solution-Aware",
"Landing page to opt-in",
"Above 25% (cold)",
"Headline or offer mismatch",
"Lead magnet does not solve a specific enough problem, or headline is too generic",
"Rewrite headline using PAIN-ACUTE tags from Phase 3. Narrow the lead magnet promise.",
"Opt-in to sales page visit (email sequence)",
"Above 15% click-through on Day 9 email (offer introduction)",
"Email sequence engagement drop",
"Sequence is educating without pre-suading. Buyers are not being moved through the awareness ladder.",
"Inject buyer language (Phase 3 tags) into email subjects. Add one case study email on Day 6.",
"Sales page to add-to-cart",
"Above 3% (cold), above 8% (warm)",
"Offer stack or trust problem",
"Stack does not clearly exceed the price. Or proof does not match the exact promise.",
"Add one Proof-to-Promise-Matched testimonial above the fold. Test a stronger guarantee.",
"Add-to-cart to purchase",
"Above 60%",
"Checkout friction or final objection",
"Price shock at checkout (hidden fees or tax), payment option missing, trust signal absent",
"Add order summary with value stack visible on checkout page. Add payment plan option.",
"Post-purchase to first login / first module",
"Above 70% within 48 hours of purchase",
"Onboarding failure",
"Welcome email is generic, first step is unclear, or access instructions are confusing",
"Rewrite welcome email with specific 'Your first step is this, takes 8 minutes' instruction. Add a Loom walkthrough video.",
"",
"Heatmap & Session Recording Protocol",
"Numbers tell you where the leak is. Session recordings tell you why. Use Hotjar or Microsoft Clarity on the sales page and landing page. Run this protocol after every 10-Sale Trigger.",
"",
"1. Set up Hotjar on sales page and landing page if not already active. Minimum 200 sessions before drawing conclusions.",
"2. Watch scroll depth heatmap: if 70%+ of visitors are not reaching the offer stack, the page is losing them in the problem section or the story. The copy before the offer is too long or too weak.",
"3. Watch click map: what are visitors clicking that is not a CTA? This reveals unmet curiosity — they want information you have not provided.",
"4. Watch 5 session recordings of visitors who scrolled to the bottom but did not convert. Note the exact moment they stop engaging.",
"5. Watch 5 session recordings of visitors who converted. Note what they did differently — faster scroll to specific section, immediate click of CTA.",
"",
"",
"PHASE 5",
"Refund & Dropout Forensics",
"The data most operators ignore is the most valuable data available",
"",
"The Forensic Mindset Shift",
"A refund is not a failure event. It is a data packet. A dropout is not a personal rejection. It is a diagnostic signal. Operators who treat refunds as problems to minimise and hide from lose the single most informative feedback loop in their entire business.",
"",
"Hormozi on Refund Data",
"Your refund rate and your dropout rate are not performance metrics. They are product diagnostics. Each one tells you one of three things: you attracted the wrong buyer, a specific module has a fatal friction point, or your guarantee is drawing people who should never have purchased. Mine every single one without ego.",
"",
"The Refund Forensics Protocol",
"Every refund request must be processed through this protocol within 24 hours of receipt, regardless of whether the refund is granted.",
"",
"Step",
"Action",
"Output",
"1. Archive the message",
"Save the full text of the refund request verbatim in Airtable — every word. Never paraphrase. Assign it an ID number.",
"Verbatim refund archive entry",
"2. Classify the root cause",
"Assign one primary root cause from the taxonomy below. One cause per refund — force the classification.",
"Root cause tag on Airtable record",
"3. Send the forensic reply",
"Before processing the refund, send the forensic reply template (see below). You are not negotiating — you are collecting data.",
"Reply sent, response captured if they reply",
"4. Update the Negative Avatar profile",
"If this refund adds evidence to an existing Negative Avatar pattern, update that profile. If it reveals a new pattern, start a new profile.",
"Negative Avatar Airtable record updated",
"5. Check for pattern",
"Is this the 2nd or 3rd refund citing the same root cause? If yes, trigger the relevant fix protocol from Phase 8.",
"Pattern check completed. Fix protocol triggered if threshold reached.",
"",
"Refund Root Cause Taxonomy",
"",
"Root Cause Code",
"Definition",
"Immediate Action",
"RC-1: Wrong Avatar",
"The buyer does not fit the target profile that the offer was designed for. They bought based on the category but are not the person the transformation serves.",
"Review ad targeting and sales page 'This is NOT for you if...' section. Strengthen avatar-specific language on the sales page.",
"RC-2: Expectation Gap — Copy",
"The sales page or email sequence created a promise that the offer does not fulfil. The buyer expected something different from what was delivered.",
"Compare the refund language to the sales page promises verbatim. If the gap is real, fix the copy or fix the delivery — not one without the other.",
"RC-3: Expectation Gap — Timing",
"The buyer expected the result faster than the offer delivers. Time Delay variable of the Value Equation was miscalibrated.",
"Add a Quick Win in the first 72 hours. Add a timeline disclaimer to the sales page: 'Most members see [first result] by day [N].'",
"RC-4: Delivery Friction",
"A specific module, step, or access issue blocked the buyer from making progress. They abandoned due to a technical or instructional barrier, not lack of intent.",
"Identify the specific friction point. Add a walkthrough video or simplify the action step. Check if this is Pattern RC-4 (appears 3+ times in 30 days).",
"RC-5: External Circumstance",
"Life event, financial change, or scheduling conflict unrelated to the offer. Not a product signal.",
"Process refund. Offer to pause or defer for 90 days. Add them to a reactivation sequence for 90 days post-refund.",
"RC-6: Guarantee-Exploiting Buyer",
"Pattern of behaviour suggesting the purchase was made primarily to consume content with the intent to refund. Completion of entire programme before refund request.",
"Process refund. Flag the email in your CRM. Do not offer to future cohorts. Review guarantee language to reduce attraction of this profile.",
"",
"The Forensic Reply Template",
"Send this before processing the refund. Do not hold the refund hostage — you are collecting data, not negotiating. Include the refund confirmation in the same message.",
"",
"Forensic Reply Template",
"Hi [Name], I'm processing your refund now — you'll see it in 3–5 business days. Before I do, I'd genuinely appreciate 60 seconds of honest feedback. Not to change your mind — I just want to understand what happened so I can make this better. What was the single biggest gap between what you expected and what you found? You don't need to be kind about it. Your honest answer is worth more to me than the sale. Either way, your refund is on its way.",
"",
"Dropout Detection Protocol",
"Dropouts — buyers who purchase but stop engaging before completing the programme — are often more informative than refunders because they had enough intent to stay but something specific stopped them.",
"",
"Signal",
"Trigger Condition",
"Response Action",
"No first login",
"No access to course platform within 72 hours of purchase",
"Send personal plain-text email: 'Your first step takes 8 minutes. Here's the link. Is there anything blocking you?'",
"Module 1 not started",
"7 days post-purchase, Module 1 incomplete",
"Send: 'Quick check-in — did you get a chance to look at Module 1 yet? I ask because most people who don't start in week 1 don't finish, and I want to make sure you do.'",
"Progress stall — mid programme",
"No new activity for 10 consecutive days",
"Send personal voice message (Loom, 60 seconds): acknowledge the stall, identify the last module completed, give one specific micro-action to restart.",
"Community silence",
"Member has not posted or commented in 14 days",
"Tag in a relevant thread: '@[Name] — I think this applies to what you're working on' to re-engage without pressure.",
"",
"",
"PHASE 6",
"The Next Problem Signal",
"Brunson's chain — every solution creates a new problem and that problem is your next product",
"",
"The Chain Mapping Framework",
"Brunson's core insight is that you do not need to invent products. You need to observe what your buyers need next after they get the result your current offer provides. Every solution creates a new problem. Map that chain and you have your entire product roadmap handed to you by buyers who already trust you.",
"",
"The Chain Logic",
"Your MVO solves Problem A. But now your buyer has Problem B — the next challenge that emerges once A is solved. And after B comes C. Each step in this chain is an offer. The buyer does not know you are building a roadmap. They just know they solved one problem and now have the next one. You are the only person who can see the full map.",
"",
"Next Problem Signal Mining",
"The Next Problem Signal lives in very specific places. You are not looking for general feedback — you are looking for statements that reveal what the buyer needs immediately after completing or benefiting from your current offer.",
"",
"Signal Type",
"Where It Appears",
"Example",
"Product Implication",
"The 'Now What?' Question",
"Exit interviews, community posts, support tickets in weeks 3–6 post-purchase",
"I've got 10 leads now — how do I convert them to calls?",
"The next offer is a call conversion or sales training product",
"The Unexpected Bottleneck",
"Support tickets referencing a new problem that emerged after using your method",
"Your system worked but now I'm overwhelmed with the volume and can't keep up",
"The next offer is a fulfilment, delegation, or automation product",
"The 'I Wish This Included' Statement",
"Exit interviews question 6, per-module pulse surveys",
"I wish there was a section on what to do after you get the first result",
"The next offer covers the scaling or consistency phase",
"The Comparison Reference",
"Community posts, email replies",
"Your stuff is great for getting started but I've also been looking at [X] for the next step",
"The next offer competes directly with what buyers are going to find elsewhere — build it first",
"The Referral Qualifier",
"Exit interviews question 7: 'Who else do you know who needs this?'",
"'My colleague does, but she's further along than I was — she'd need something more advanced'",
"There is a more advanced buyer segment who needs a higher-tier version of the transformation",
"",
"The Next Problem Chain Template",
"After each Forensic Audit, map what you have learned about the chain. This becomes your product roadmap and your ascension sequence design document.",
"",
"Step",
"Problem",
"Current Offer (if exists)",
"Next Offer (to build)",
"Evidence Source",
"Problem A",
"[What the buyer struggled with before your MVO]",
"[Your MVO name + tier + price]",
"Already built",
"Pre-purchase research",
"Problem B",
"[What they struggle with after getting the MVO result]",
"[Core Offer name if built]",
"[Describe what Core Offer needs to cover]",
"[Exit interview / support ticket citation]",
"Problem C",
"[What they struggle with after the Core Offer]",
"[High-ticket / DWY if built]",
"[Describe what next tier needs to cover]",
"[Exit interview / community post citation]",
"Problem D",
"[What they struggle with at scale]",
"[Continuity / Inner Circle]",
"[Describe ongoing support needed]",
"[Top-buyer conversation / mastermind request]",
"",
"",
"PHASE 7",
"Mechanism Freshness Test",
"Every 90 days: can the method be renamed to feel 10× more powerful?",
"",
"Why Mechanisms Get Stale",
"The name you gave your methodology at launch was the best name available with the information you had at launch. After 90 days of buyer data, support conversations, and exit interviews, you know more about how your buyers think about the transformation than you did on day one. That knowledge should change how you describe the mechanism — not what the mechanism does, but how you name and frame it.",
"",
"The 10× Rename Test",
"Take your current mechanism name. Read it to five people who match your target avatar and have not heard of your offer before. Ask them to rate how excited they are about it on a scale of 1–10 and describe what they imagine it involves. If the average score is below 7 or their description does not match what the mechanism actually does — rename it.",
"",
"The Mechanism Naming Criteria",
"A great mechanism name passes all five of the following criteria. Evaluate your current name against each one:",
"",
"Criterion",
"Test",
"Pass",
"Fail Example",
"Specificity",
"Does it describe a specific process, not a general category?",
"'AI Forensic Offer Autopsy' — describes a specific diagnostic action",
"'Marketing System' — describes a category",
"Outcome implied",
"Does the name imply the result without stating it generically?",
"'30-Day Client Acquisition Accelerator' — implies clients, implies speed",
"'Lead Generation Programme' — states category, implies nothing specific",
"Distinctiveness",
"Does it sound like something only you do, or like a commodity?",
"'The Reverse Funnel Method' — named and owned",
"'Funnel Strategy' — generic, anyone says this",
"Repeatability",
"Can your buyer explain it to a colleague in one sentence?",
"Yes — 'It's a system where you build the backend offer first and work backward to the lead magnet'",
"No — 'It's kind of like a multi-step thing for growing your audience...'",
"Curiosity gap",
"Does it make someone who has not heard of it want to ask what it is?",
"'The Forensic Critic Positioning' — provokes 'what's that?'",
"'Content Strategy Framework' — provokes nothing",
"",
"Mechanism Rename Protocol",
"If the current mechanism name fails two or more criteria above, initiate a rename cycle. This does not require rebuilding the offer — only renaming and re-describing the method across copy assets.",
"",
"1. Generate 10 new mechanism name candidates using the following structure: [Adjective/Method Type] + [Verb or Descriptor] + [Container Word].",
"2. Test the top 3 names with 5 avatar-matched individuals using the 10× Rename Test. Score each on excitement (1–10) and description accuracy.",
"3. Select the winner. Requires a score of 7+ average AND accurate description from 4 of 5 testers.",
"4. Update the mechanism name across: sales page, email sequence (Days 8–10), all ad creatives, course platform titles, and GEO schema markup.",
"5. Log the rename in Airtable: old name, new name, date, test scores, and conversion rate before and after the 30 days following rename.",
"",
"Mechanism Rename Asset Update Checklist",
"",
"☐ Sales page — headline, mechanism section, and all stack slide references",
"☐ Email nurture sequence — Days 8, 9, and 10 (mechanism introduction emails)",
"☐ Paid ad copy — all active creatives using the mechanism name",
"☐ Course platform — module titles and overview description",
"☐ YouTube and podcast episode titles referencing the mechanism",
"☐ AEO/GEO schema — branded methodology keywords updated in L0 and L1 keyword grid",
"☐ LLMs.txt file — mechanism name updated in authority declaration section",
"☐ Pillar article — update H1 and mechanism definition section",
"",
"",
"PHASE 8",
"The Action Protocol",
"Kill / Iterate / Scale / Launch Next — making the right decision with the data",
"",
"The Four Possible Outcomes",
"Every Forensic Audit produces one of four action recommendations. The decision tree below maps your audit findings to the correct action. Do not run multiple actions simultaneously — prioritise the one highest in the stack and complete it before starting the next.",
"",
"Action 1 — SCALE",
"Conditions: cold conversion above 2%, refund rate below 5%, ascension rate above 10%, Value Equation audit shows no critical variable degradation, buyer language is consistent with sales page copy.",
"",
"• Increase paid ad spend by no more than 20% per day. Monitor CPA and refund rate daily for the first 7 days of scaling.",
"• Add one new traffic source (second platform) using the best-performing organic content as the basis for ad creative.",
"• Rebuild the sales page headline and hero section using the top three PAIN-ACUTE language tags from Phase 3.",
"• Activate the ascension sequence to the next value ladder tier for all buyers who have completed the programme.",
"",
"Action 2 — ITERATE",
"Conditions: one or two metrics below threshold, root cause is diagnosable, fix does not require rebuilding the core mechanism or re-recording the programme.",
"",
"Failing Metric",
"Iteration Action",
"Test Window",
"Cold conversion below 1.5%",
"A/B test new headline using PAIN-ACUTE buyer language. Test a stronger guarantee (move one level up the guarantee hierarchy). Do not change both simultaneously.",
"14 days — minimum 200 visitors per variant",
"Opt-in rate below 15%",
"Rewrite lead magnet headline to a more specific, faster result. Test a different lead magnet format (tool/quiz vs PDF).",
"14 days — minimum 200 visitors per variant",
"Email open rate below 22%",
"Rewrite Days 1–3 subject lines using PAIN-ACUTE and DESIRE-HIDDEN tags. Test plain-text vs formatted email on Day 2.",
"7 days — minimum 100 sends per variant",
"Time Delay variable degradation",
"Add a documented Quick Win deliverable to Module 1. Send a '72-hour check-in' email that tells buyers exactly what their first win should be and when.",
"Immediate — apply to next 10 buyers and compare Day 7 engagement",
"Ascension rate below 8%",
"Rewrite ascension sequence. Change the trigger point — test presenting the Core Offer earlier (Day 14 vs Day 21 post-MVO purchase).",
"30 days — compare ascension rate before and after trigger change",
"",
"Action 3 — KILL",
"Conditions: refund rate above 15%, cold conversion below 0.5% after 500+ visitors, completion rate below 40%, or two or more root cause patterns (from Phase 5) appearing three or more times without a diagnosable fix.",
"",
"Kennedy's Kill Rule",
"Most millionaires have a trail of failed offers. Killing a broken offer is not failure — it is the system working correctly. The failure is continuing to run ads to a broken offer because you are emotionally attached to having built it. Archive all buyer data. That data survives even when the offer does not.",
"",
"• Archive all buyer language from Phase 3 — it is valid copy intelligence regardless of offer outcome.",
"• Complete a Negative Avatar profile (Phase 5 template) to document who this offer should NOT be sold to in future.",
"• Run Phase 6 analysis specifically: what problem did buyers think they were solving, and is there a different offer that solves it correctly?",
"• Return to MVO Playbook Phase 2 (Offer Construction) with all accumulated data as the brief.",
"",
"Action 4 — LAUNCH NEXT",
"Conditions: Phase 6 (Next Problem Signal) has produced three or more consistent signals pointing to a specific Problem B. Current offer is performing at Scale threshold or above. Capacity exists to build and deliver a new tier.",
"",
"• The Next Problem Signal data from Phase 6 becomes the MVO brief for the new offer. The buyer language you have mined is the first draft of the sales page copy.",
"• Do not launch the next offer until the current offer's ascension sequence is built and automated. Launching upward without an ascension funnel means the new offer cannibalises the current one.",
"• Position the new offer as the solution to the specific Problem B you have documented — not as a generic upgrade.",
"• Run the new offer through the Beta Testing Methodology SOP (RISER Nation SOP Series) before public launch.",
"",
"",
"The 30-Day Forensic Audit Ritual Calendar",
"This is the standing operational rhythm. It runs continuously regardless of whether a specific trigger has fired that week. The trigger-based phases are in addition to this baseline ritual, not instead of it.",
"",
"Cadence",
"Activity",
"Time Required",
"Output",
"Every Monday (15 min)",
"Pull the seven funnel health metrics from Phase 1. Log in Airtable. Flag any metric below threshold.",
"15 minutes",
"Weekly metrics log. Flag any triggered audit.",
"Every Tuesday (20 min)",
"Review all new support tickets and email replies from the past 7 days. Tag language using the Phase 3 tagging system.",
"20 minutes",
"New language entries in mining database.",
"Every Wednesday (10 min)",
"Scan community platform. Screenshot any post with 3+ reactions or substantive questions. Archive and tag.",
"10 minutes",
"Community language additions to database.",
"Every Thursday (10 min)",
"Check for new refunds. Process any refund through the 5-step Refund Forensics Protocol.",
"10 minutes per refund",
"Refund archive updated. Patterns checked.",
"Every Friday (20 min)",
"Weekly audit summary: what changed this week, any patterns emerging, any trigger thresholds crossed?",
"20 minutes",
"Weekly Forensic Summary note in Airtable.",
"After every 10 sales",
"Full 8-Phase Audit. Block 2.5–3 hours. Do not skip phases.",
"2.5–3 hours",
"Completed Forensic Audit Scorecard. Action Protocol selected.",
"Monthly (first Monday)",
"Review full language mining database. Identify top 5 new phrases for copy deployment. Update sales page if PAIN-ACUTE or DESIRE-HIDDEN tags have produced better phrases than current copy.",
"60–90 minutes",
"Copy update brief. Sales page revision if warranted.",
"Quarterly (every 90 days)",
"Full 8-Phase Audit + Mechanism Freshness Test + Product Chain Map update + Value Ladder gap analysis.",
"Half day",
"90-Day Forensic Report. Product roadmap updated.",
"",
"",
"Airtable Database Schema",
"All Forensic Audit data lives in a single Airtable base with five linked tables. This schema ensures every piece of buyer intelligence is connected across offers, buyers, and time periods.",
"",
"Table 1 — Buyer Language",
"Primary table. Every tagged phrase from Phase 3 sources.",
"",
"Field Name",
"Field Type",
"Purpose",
"Phrase ID",
"Autonumber",
"Unique identifier for each phrase",
"Verbatim Phrase",
"Long text",
"Exact words — never edited",
"Source",
"Single select",
"Email Reply / Support Ticket / Community / Exit Interview / Refund / Sales Call",
"Tag",
"Multiple select",
"PAIN-ACUTE / PAIN-CHRONIC / DESIRE-EXPLICIT / DESIRE-HIDDEN / OBJECTION / ANTI-LANGUAGE",
"Offer",
"Link → Offers table",
"Which offer this language relates to",
"Date Captured",
"Date",
"Mining date",
"Deployed",
"Checkbox",
"Used in live copy yet?",
"Deployed In",
"Long text",
"Which specific asset",
"",
"Table 2 — Audit Records",
"One record per completed Forensic Audit run.",
"",
"Field Name",
"Field Type",
"Purpose",
"Audit ID",
"Autonumber",
"Unique ID",
"Date Run",
"Date",
"",
"Trigger Type",
"Single select",
"10-Sale / First Refund / Conversion Drop / 30-Day / 90-Day / Ascension Anomaly",
"Offer Audited",
"Link → Offers table",
"",
"Phase 1 Flags",
"Long text",
"Which metrics below threshold",
"Value Equation Finding",
"Long text",
"Which variable degraded and evidence",
"Refund Patterns",
"Long text",
"RC codes appearing 2+ times",
"Next Problem Signal",
"Long text",
"Problem B identified if applicable",
"Mechanism Rename Triggered",
"Checkbox",
"",
"Action Selected",
"Single select",
"Scale / Iterate / Kill / Launch Next",
"Action Brief",
"Long text",
"Specific changes to implement",
"Review Date",
"Date",
"30 days after — check if action produced results",
"",
"Table 3 — Refund Records",
"One record per refund. Linked to Buyers and Offers tables.",
"",
"Field Name",
"Field Type",
"Purpose",
"Refund ID",
"Autonumber",
"",
"Buyer",
"Link → Buyers table",
"",
"Offer",
"Link → Offers table",
"",
"Date Requested",
"Date",
"",
"Verbatim Refund Message",
"Long text",
"Never paraphrase",
"Root Cause Code",
"Single select",
"RC-1 through RC-6",
"Forensic Reply Sent",
"Checkbox",
"",
"Response Received",
"Long text",
"Buyer's answer to forensic reply if they responded",
"Negative Avatar Update",
"Link → Negative Avatar table",
"",
"",
"",
"Forensic Audit Master Scorecard",
"Complete this for every full 8-Phase Audit run. File in Airtable under Audit Records.",
"",
"Section",
"Field",
"Your Data",
"Header",
"Audit ID + Date",
"",
"Header",
"Offer name + tier + launch date",
"",
"Header",
"Trigger type that initiated this audit",
"",
"Header",
"Total sales to date / Sales in last 30 days",
"",
"Phase 1",
"Cold conversion rate",
"",
"Phase 1",
"Refund rate (rolling 30 days)",
"",
"Phase 1",
"Ascension rate (MVO to Core)",
"",
"Phase 1",
"Primary funnel leak location (if any)",
"",
"Phase 2",
"Value Equation variable with greatest degradation",
"",
"Phase 2",
"Evidence supporting this finding",
"",
"Phase 2",
"Specific offer change indicated",
"",
"Phase 3",
"Top 3 new PAIN-ACUTE phrases mined this cycle",
"1.\n2.\n3.",
"Phase 3",
"Top 2 OBJECTION phrases not addressed in current copy",
"1.\n2.",
"Phase 3",
"Any ANTI-LANGUAGE identified — remove from all assets",
"",
"Phase 4",
"Heatmap finding (if session recordings reviewed)",
"",
"Phase 4",
"Biggest drop-off point in funnel this cycle",
"",
"Phase 5",
"Number of refunds this cycle",
"",
"Phase 5",
"Most common root cause code",
"",
"Phase 5",
"Any RC pattern appearing 3+ times (immediate action trigger)",
"",
"Phase 6",
"Next Problem Signal identified? (Y/N)",
"",
"Phase 6",
"Problem B description (if signal found)",
"",
"Phase 6",
"Evidence source for Problem B",
"",
"Phase 7",
"Mechanism name reviewed — passed or failed criteria?",
"☐ Pass ☐ Fail",
"Phase 7",
"Rename triggered? (Y/N)",
"",
"Phase 8",
"Action Protocol selected",
"☐ Scale ☐ Iterate ☐ Kill ☐ Launch Next",
"Phase 8",
"Specific action items (max 3)",
"1.\n2.\n3.",
"Phase 8",
"Owner and deadline for each action",
"",
"Review",
"Review date (30 days from today)",
"",
"",
"",
"Master Forensic Audit Checklist",
"",
"Weekly Standing Ritual",
"☐ Monday: Pull 7 Phase 1 metrics, log in Airtable, flag thresholds",
"☐ Tuesday: Tag new support tickets and email replies by language type",
"☐ Wednesday: Scan community — archive posts with 3+ reactions",
"☐ Thursday: Process any new refunds through 5-step protocol",
"☐ Friday: Weekly summary note — patterns, flags, triggers crossed",
"",
"When 10-Sale Trigger Fires (Full Audit — block 3 hours)",
"☐ Phase 1: Pull all 7 metrics. Run diagnostic flow chart. Identify primary leak if exists.",
"☐ Phase 2: Run four-variable Value Equation Audit using buyer data from this cycle",
"☐ Phase 2: Complete Value Equation Output table — fill all four rows with evidence",
"☐ Phase 3: Review all new buyer language captured since last audit — tag and add to database",
"☐ Phase 3: Identify top 3 PAIN-ACUTE phrases — compare to current sales page copy",
"☐ Phase 4: Review funnel metric table — flag any stage below threshold",
"☐ Phase 4: Watch 5 non-converting session recordings if conversion below threshold",
"☐ Phase 5: Complete refund forensics for all refunds since last audit",
"☐ Phase 5: Check for RC patterns appearing 3+ times — trigger fix protocol if found",
"☐ Phase 6: Review exit interviews and community posts for Next Problem Signals",
"☐ Phase 6: Update Next Problem Chain Map if new signal found",
"☐ Phase 7: Run Mechanism Freshness Test if 90-day trigger is also active",
"☐ Phase 8: Select one Action Protocol — write action brief with owner and deadline",
"☐ Log completed scorecard in Airtable Audit Records table",
"☐ Set 30-day review calendar reminder",
"",
"Quarterly Deep Audit (Add to Full Audit Above)",
"☐ Run Mechanism Freshness Test regardless of 90-day timer",
"☐ Run 10× Rename Test with 5 new avatar-matched individuals",
"☐ Update Next Problem Chain Map with full product roadmap review",
"☐ Review all ANTI-LANGUAGE tags — scrub from every active copy asset",
"☐ Review Value Ladder gap analysis — are all ascension sequences live and automated?",
"☐ Export full buyer language database — identify top 10 phrases not yet deployed in copy",
"☐ Brief for Mechanism Rename if test score below 7.0",
"☐ Update GEO/AEO schema with any new branded methodology terms",
"",
"",
"",
"RISER Nation Master Operating System | Post-MVO Forensic Audit Loop SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | Post-MVO Forensic Audit Loop SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
},
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Test an offer with buyers and document the launch decision
Begin with evidence you can inspect
Imagine a builder who has a promising offer and ten interested people. This is a hypothetical scene. The builder could polish every lesson now, but still would not know which instructions buyers can use.
The gap is between an appealing idea and evidence of delivery. A beta is a small, disclosed test of the offer with real participants. This source proposes a paid beta before a wider launch. The work produces buyer feedback, delivery findings, possible proof assets and a reasoned next decision. The source also intends beta payments to help fund initial delivery costs; actual proceeds must be compared with actual costs.
The source presents three educational lenses. Its Hormozi lens separates selling an idea from proving delivery before scaling. Its Kennedy lens treats feedback as evidence for business decisions. Its Brunson lens follows the buyer's before-and-after story and the next problem. These are source-attributed applications, not independently verified quotations or endorsements. They support the project's Brunson/ClickFunnels and Hormozi/Acquisition.com themes.
Treat participants as people receiving a disclosed service. A beta is not permission to hide unfinished delivery or to demand praise. Collect evidence with context. Label sample outcomes as hypothetical and separate private research from approved public material.
Check the seven prerequisites
The source says demand, an achievable deliverable and insufficient launch proof make a beta useful. Someone saying they would pay is an early signal, not a completed purchase. Review all seven gates below and record the evidence for each.
Criterion
Threshold
Status
Market pain validated
At least 3 verbatim quotes from real people describing the problem in their own words
☐ Pass / ☐ Fail
6-Score Filter passed
Score of 22 or higher on the MVO Playbook V5 monetisation filter
☐ Pass / ☐ Fail
Kill filters cleared
All 3 kill filters: Cheap to Ignore, Massive Behaviour Change, Existing Excellent Cheap Solution — all negative
☐ Pass / ☐ Fail
Core deliverable defined
You can describe what the buyer receives and the timeline in one sentence
☐ Pass / ☐ Fail
Fulfilment capacity confirmed
You can deliver to 5–15 people without breaking your calendar, your margin, or your sanity
☐ Pass / ☐ Fail
Flagship Promise passes
A non-marketer can repeat the core promise in one sentence after hearing it once
☐ Pass / ☐ Fail
Mechanism named
Your unique method has a specific name (not 'my system' or 'my process')
☐ Pass / ☐ Fail
The three kill filters ask whether the problem is cheap to ignore, requires massive behavior change, or already has an excellent cheap solution. The six-score filter must total at least 22 in the source, but its complete scoring method is not supplied here. Do not invent it from the number.
The source calls these gates required, and its final checklist says all must pass. Its earlier hard rule stops only when more than one fails. Record that conflict. A missing delivery capability or unclear promise still needs resolution even if it is the only failed item. The referenced MVO Playbook V5 and its Phase 1/2 methods remain unmatched resources.
Phase 1 — Choose the cohort and explain the commitment
Choose a cohort you can actually support. The introduction favors 5–15 people and calls more than 20 a launch, yet the low-ticket row allows 15–25. Use the full table as source guidance, not a statistical guarantee.
Cohort Size
Best For
Risk
5–8 people
High-touch done-with-you or done-for-you offers above $500
Lower data volume — every dropout matters
8–15 people
Group programmes, courses, and workshops. The sweet spot for most MVOs
Manageable feedback load with strong signal
15–25 people
Lower-ticket offers ($47–$197) with minimal live interaction required
Feedback processing becomes time-intensive — assign a note-taker
Recruitment follows five source channels in order: existing email subscribers, past buyers of related offers, community members, organic social followers, and individual messages to people who engaged with your content. The source expects selling effort to rise as familiarity falls. These are planning categories; no messages are sent by this lesson.
Write all five parts of the invitation. Say what you will deliver, why the price is reduced, what participation requires, what it costs, and the real capacity or closing date. The sample figures describe an illustrative offer, not an existing RISER commitment.
Element
What to Write
Example
What you are building
Name the offer and the transformation in one sentence
I am building a 4-week intensive that helps HVAC contractors get 10 qualified service calls per week using a local content system.
Why beta pricing
Honest reason — you want real-world data, case studies, and feedback in exchange for a reduced price
In exchange for the discounted beta price I am asking for one interview call at the end and honest written feedback on every module.
What they commit to
Be specific about their time, participation, and feedback obligations
This requires 3–5 hours per week for 4 weeks, showing up to the two live calls, and completing the feedback form after each module.
The beta price
State the price clearly. Do not hide it.
$297 for the full 4-week programme. It will be $997 at public launch.
Hard deadline
Create real urgency — beta spots are genuinely limited by your capacity
I am taking exactly 10 people. Doors close Friday at midnight or when full.
Check the example as a whole: its four weeks, three-to-five weekly hours, two calls, module feedback, $297 beta price and $997 later price must describe a deliverable offer before anyone uses that message. A ten-person limit and Friday deadline must be real.
Phase 2 — Price and disclose the beta honestly
The source uses payment as a commitment filter. Price is one influence on participation; it does not determine completion. Its claims of 60–80% dropout for free users, 40–60% at $97 and 80%+ completion at $297 or more are unsupported here. Free research can still yield useful feedback.
Study all four pricing rows. They are source examples, not current market valuations or a promise that the prices work.
Offer Type
Full Launch Price
Beta Price Range
Rationale
Low-ticket MVO (template / mini-course)
$97–$297
$27–$67
Price reduction is meaningful but still filters for intent
Mid-ticket MVO (group intensive / workshop)
$297–$997
$97–$297
Sweet spot for commitment — still an investment, clearly discounted
Core Offer (group programme)
$997–$4,997
$297–$997
Price must reflect the time investment required from the buyer
High-ticket (DWY / DFY)
$2,500–$10,000
$497–$1,500
Even at beta price this is a serious purchase — screen with application
Explain the five buyer commitments before purchase. Ask for a five-to-ten-question response after each module or milestone; attendance or recording access within 48 hours; a 20–30-minute exit interview; written permission for any agreed testimonial use; and advance notice before public screenshots or case studies. Participation, recording consent and publication permission are distinct. Do not require a positive review in exchange for the discount.
The source proposes a conditional support guarantee rather than an unconditional refund promise. Its example follows.
Beta Guarantee Language If you complete all modules, attend both live calls, and submit all feedback forms within the programme window and do not see [specific promised result], I will work with you personally at no additional cost until you do.
This wording promises personal help until a specific result. That can create an open-ended support obligation. Match every condition, call count, timeframe and remedy to the actual offer before considering its use. An unfinished product does not by itself prove a conditional guarantee is suitable. Existing buyer promises must be honored; this lesson does not change them.
Phase 3 — Map delivery and feedback together
Use the simplest delivery format that supports the work. The source suggests a document, video call and shared content page before a polished platform. It prefers no more than four active delivery weeks, asks for a debrief after each session and proposes recordings. Record only with appropriate consent; a delivery recording is not automatically an advertisement or public course asset.
The schedule includes week 0 preparation and week 5 follow-up in addition to the four delivery weeks. Keep that distinction visible in the participant's calendar.
Week
Delivery Activity
Feedback Trigger
Data Collected
Week 0 (Pre-start)
Welcome call (30 min). Onboarding survey. Baseline metrics captured. Set expectations for the programme.
Baseline survey (see Phase 4)
Current situation, goals, fears, anti-language
Week 1
Module 1 delivery. One live or recorded session (45–90 min). First quick win delivered.
Module 1 feedback form (5 questions)
Clarity of instruction, first win achieved yes/no, confusion points
Week 2
Module 2 delivery. Progress check-in. Address top objections from Week 1 feedback.
Module 2 feedback form + 10-min group call
Progress velocity, where they are getting stuck, support needs
Week 3
Module 3 delivery. Case study capture from any early winners. Peer share in community.
Module 3 feedback form + peer testimonials
Early results data, social proof harvesting begins
Week 4
Module 4 delivery. Final implementation session. Begin exit interview scheduling.
Module 4 feedback form
Completion status, confidence level, result achieved yes/no
Week 5 (Post-programme)
Exit interviews (20–30 min each). Final results capture. Testimonial collection. Offer for public launch at beta graduate price.
Exit interview (see Phase 4 template)
Full transformation arc, before/after metrics, referral intent, ascension readiness
Week 0 captures the baseline and expectations. Week 1 tests clarity and a first achievable win. Week 2 checks progress and obstacles. Week 3 can capture early outcomes. Week 4 records completion and schedules interviews. Week 5 examines the whole experience and any appropriate next offer. Each stage has a different feedback purpose.
The six functions below form the source's proposed minimal stack. Tool prices, payment fees and capabilities are unverified source figures and need current checking before selection. They do not replace the authorized GoHighLevel course destination.
Function
Tool
Cost
Why This Tool
Video delivery
Loom or Zoom recording
Free–$15/mo
Fast to produce, easy to update between cohorts
Content hosting
Notion, Google Drive, or Kajabi
Free–$69/mo
Accessible on any device, easy to update live
Community / Q&A
Private Slack, Discord, or Facebook Group
Free
All feedback in one searchable place
Feedback forms
Typeform or Google Forms
Free–$25/mo
Branching logic for richer responses
Exit interviews
Zoom or Google Meet
Free
Record for testimonial extraction
Payment processing
Stripe or ThriveCart
$0 + 2.9%
Clean checkout, easy refund processing if needed
Phase 4 — Use three feedback instruments
Start with the baseline before Module 1. Its six questions capture the current problem, prior attempts, urgency and its reason, a specific desired result, the joining objection and an unmet concern. Preserve the complete wording for study.
Complete source procedure for study:
• Describe your current situation with [core problem] in 2–3 sentences. Use your own words.
• What have you already tried to solve? What happened?
• On a scale of 1–10, how urgent is solving this in the next 90 days? What is driving that score?
• What does success look like for you at the end of this programme? Be specific — numbers where possible.
• What is the single biggest thing that almost stopped you from joining today?
• Is there anything you are afraid this programme will NOT cover that you need?
The source calls the joining objection the most valuable copy. Treat that as a research priority, not a guarantee. Compare several participants, retain their actual words and do not turn a private response directly into public copy.
The source aims to keep its five-question pulse survey under three minutes. Send it within 24 hours of module delivery and review responses within 48 hours. It asks about clarity, action completion, confusion, perceived value and missing material.
Question
Format
What You Are Measuring
How clear was this module? (1–10)
Number scale
Instruction quality — below 7 = rewrite the module
Did you complete the action item from this module? (Yes / Partially / No)
Multiple choice
Completion rate — below 60% = the task is too hard or unclear
What was your single biggest confusion or sticking point? (Optional)
Short text
Friction points to fix before public launch
Rate the value delivered in this module relative to what you paid. (1–10)
Number scale
Perceived value — below 7 on any module = gap in the offer stack
What do you wish was included in this module that wasn't? (Optional)
Short text
Missing content that becomes a bonus at public launch
The prose permits one optional comment and otherwise closed questions, but the table includes two optional text answers. Preserve the conflict when designing a form. Scores below seven and completion below sixty percent flag investigation; they do not prove that content is too hard, unclear or wrongly priced. Timing, access and prerequisites also matter.
The exit interview lasts 20–30 minutes. The source schedules it with completers within seven days after the programme. Ask all nine questions in order. This describes the source protocol; no interviews are scheduled here.
Complete source procedure for study:
• Can you walk me through what your situation was before you joined? What was happening?
• What had you already tried? Why didn't those things work?
• What made you decide to join this specific programme at this specific time?
• Walk me through what happened during the programme. What shifted first?
• What specific result have you achieved that you can put a number on?
• What was the most valuable part? What would you remove or improve?
• Who else do you know who needs this? Why would they need it?
• Knowing what you know now, would you pay the full public price of [launch price]? Why?
• Is there anything you were hoping to get from this that you didn't?
Completer interviews describe one selected group. They cannot replace inquiry into dropouts and unsuccessful buyers. Questions 6 and 7 ask about value/improvement and referrals. They are not the exact next-problem questions referenced in the Post-MVO audit.
Extract useful three-to-eight-word phrases while retaining each full response and its context. The source proposes those phrases for hooks, headlines, ads and subject lines. A phrase is evidence of what one person said, not proof that using it causes higher conversion.
Phase 5 — Learn from unsuccessful outcomes
A refund or dropout can reveal unsuitable fit, delivery friction, missing prerequisites, expectations or outside circumstances. None automatically establishes a defective buyer. Use all five scenario questions below, and record alternative explanations.
Scenario
Questions to Ask
What It Reveals
Buyer completes less than 50% of modules
Which module did they stop at? What was happening in their life at that point? Did they find the content too hard, too easy, or unclear?
Friction point in delivery — the exact module that needs to be rebuilt
Buyer completes but reports no result
What action steps did they complete? Where did implementation break down? What would have made the result achievable?
Gap between instruction and implementation — a missing 'done-for-you' component or a missing prerequisite
Buyer requests a refund
Why did you decide this wasn't right for you? What were you hoping for that you didn't find? What would have made you stay?
Expectation mismatch — either the sales copy overpromised or the wrong buyer profile is being attracted
Buyer says 'it wasn't for me'
Can you describe who you think this IS for? What kind of person would get the most from this?
Avatar mismatch — they will describe your actual target buyer better than you can from the outside
Buyer ghosts after purchase
Send one short check-in: 'I noticed you haven't started yet — is everything okay? Is there anything stopping you from getting in?'
Onboarding failure — the first step is too hard or the welcome experience is not creating momentum
The source's interpretations are hypotheses to investigate. A silent buyer may have an access problem or a changed schedule. Completion without a result may expose an implementation gap. A request about who the offer suits can help clarify its scope.
Complete all six fields in the source template. This is the Phase 5 template absent from the standalone Post-MVO audit.
Complete source procedure for study:
• Negative Avatar Name: [Give them a character name]
• Entry point: How did they find you? What language did they respond to in your recruitment message?
• Where they dropped off: Which module, week, or milestone marked their exit?
• What offer would have served them: [Describe the offer they actually needed — this may become your next product]
• Copy and recruitment change triggered: [Specific change to sales page, ad targeting, or application screening]
Choosing one primary cause must not erase contributing causes or uncertainty. The alternative offer is an evidence-based possibility, not a requirement to invent another product. State the exact copy or screening change being proposed, with its supporting observation.
Phase 6 — Match proof to the actual promise
The source distinguishes four proof assets. Read their collection method and intended placement. Referenced email days and page sections describe its example sequence, not verified assets in this account.
Proof Asset
How to Collect
Where It Is Used
Specific result testimonial
Exit interview question 5: 'What specific result have you achieved that you can put a number on?' Capture exact numbers, timeframes, and before/after states.
Sales page hero section, email Day 6 in 14-day sequence, ad creative (transformation hook)
Story testimonial (Epiphany Bridge)
Exit interview questions 1–4: the full before/during/after journey. Edit into a 150–300 word written testimonial using the buyer's own words.
Sales page social proof section, case study article for AEO/GEO, webinar stack slide
Objection-killing testimonial
Exit interview question 8: 'Would you pay the full price knowing what you know now?' The answer directly addresses price objection on your sales page.
Sales page FAQ section, email Day 11 (objection handling), ad variant targeting price-objection audience
Video testimonial
At the end of the exit interview, ask: 'Would you be willing to record a 60-second video summarising what you experienced?' Provide three prompts: where you were, what happened, where you are now.
Sales page hero, YouTube channel, social proof ad variant, VSL social proof section
A results testimonial needs a supported number, period and starting point. A story testimonial should preserve the buyer's meaning when edited to 150–300 words. A full-price answer records willingness, not a completed full-price sale. A sixty-second video uses three prompts: where the person was, what happened and where they are now.
Compare the three promise/proof pairs below. All are source examples, not RISER results.
Your Promise
Required Proof Match
Weak Proof (Discard)
30 qualified leads in 30 days
'We generated 34 qualified leads in the first 28 days' + screenshot
'Really helpful programme, loved the community'
Reduce employee churn by 40%
'We went from 6 departures per quarter to 2, in 90 days' + HR data
'Great frameworks, very actionable'
Build and launch your first course in 14 days
'I launched on day 11 with 12 pre-sales' + screenshot of sales dashboard
'Russell really knows his stuff'
A reduction from six departures to two is about 66.7% in the count. It does not itself measure a forty-percent churn-rate reduction; headcount and comparable periods matter. General praise can be useful feedback, but it does not substantiate a numeric promise. A selected successful buyer does not establish typical results.
The source recommends asking for a video after the first major result, while another instruction asks at the exit interview. Both are possible collection moments. Let the participant choose freely, verify the result and obtain permission for the actual use. Do not manipulate excitement into exaggerated claims.
Phase 7 — Score readiness before recommending launch
This is a pass/fail scorecard, not a weighted average. Record all eight minimums separately from the stronger signals.
Metric
Minimum Threshold
Strong Signal
Status
Programme completion rate
60% of beta cohort completed the full programme
80%+
☐ Pass / ☐ Fail
Result achievement rate
50% of completers achieved a specific, measurable result
70%+
☐ Pass / ☐ Fail
Average module clarity score
7.0 or above across all module pulse surveys
8.5+
☐ Pass / ☐ Fail
Perceived value score
7.0 or above (relative to price paid)
8.5+
☐ Pass / ☐ Fail
Refund rate
Under 15% of beta cohort
Under 5%
☐ Pass / ☐ Fail
Specific result testimonials collected
At least 3 testimonials with specific metrics
5+
☐ Pass / ☐ Fail
Video testimonials collected
At least 1 video testimonial usable in ads and sales page
3+
☐ Pass / ☐ Fail
Public launch price validated
At least 4 of 8 exit interview respondents confirm they would pay full price
7+/8
☐ Pass / ☐ Fail
Completion uses the full enrolled cohort. Result achievement uses completers as its denominator. Record both counts. Define refunds, response counts and the observation period consistently. The source calls below-sixty-percent completion or below-fifty-percent achievement vetoes, but still requires all eight minimums.
The full-price question requires four of eight respondents. A five-person beta cannot produce eight participants. No alternate small-cohort rule is supplied. Do not manufacture responses or treat a threshold as statistical certainty.
Before a wider launch, the source proposes a next-tier or founding-member option for graduates. Its three stated purposes are immediate revenue, evidence for the next-tier path, and launch interest supported by existing participants. None is an assured result. It offers the Core or Continuity tier at the beta price for 72 hours, uses approved beta evidence in launch materials, and invites the top two or three results-getters to an optional inner circle at a reduced annual rate. These are proposals, not existing offers. Its later launch instructions create a second possible 72-hour window; specify the intended timing before use.
Phase 8 — Choose Launch, Iterate or Kill this version
For Launch, the source requires all go/no-go thresholds, three specific results testimonials and refunds below ten percent, then proposes launch within thirty days. This is stricter than the scorecard's refund minimum below fifteen percent. Do not silently combine the two rules. The Iterate table uses refunds above fifteen percent, while the scorecard requires under fifteen percent. Exactly fifteen percent fails that minimum but is not covered by the named Iterate row; keep the boundary gap explicit.
Its six launch actions are to rebuild the offer using Trim & Stack and buyer language; revise the headline and hero; name bonuses for actual sub-problems; raise the guarantee one tier; place approved proof on the sales page, Day 6 email and first ad; and open at the public price with a 72-hour graduate option. The full Trim & Stack and guarantee-tier methods are not defined here. Prices, bonus values, deadlines and guarantees need real support and feasibility.
For Iterate, one to three thresholds fail with a clear fix. Implement and document the correction, then run another beta rather than declaring public readiness. Preserve all five source fix rows.
Failed Threshold
Likely Root Cause
Specific Fix Before Beta 2
Completion rate below 60%
Module too complex, action steps unclear, or no accountability mechanism
Simplify action steps to one per module. Add a weekly accountability check-in. Rebuild the module that had the lowest completion rate.
Result achievement below 50%
Missing prerequisite, implementation gap, or transformation promise too large for the timeframe
Add a done-for-you component to the module where implementation breaks down. Adjust the promise to match actual result timeline.
Module clarity score below 7.0
Instruction assumes too much prior knowledge or lacks concrete examples
Add a real-world example to every step. Record a 'watch me do this' walkthrough for each action item.
Refund rate above 15%
Sales copy is attracting the wrong buyer profile or expectation mismatch at checkout
Add a 'This is NOT for you if...' section to the sales page. Add a pre-purchase checklist. Rewrite the promise to match actual delivery.
Perceived value below 7.0
Offer stack does not match the price or delivery format underdelivers on expectation
Add one high-perceived-value bonus (name it, assign a standalone value). Upgrade the delivery format (add a live call if it was self-paced).
These diagnoses are starting hypotheses. Add examples or a walkthrough where learners lack clarity. Simplify the action where evidence shows overload. Adjust the promise where delivery cannot support it. An extra bonus or done-for-you component is not automatically the right fix; check what caused the problem.
For Kill, the source lists more than three failed thresholds, result achievement below thirty percent, or a fundamental offer-market mismatch. Its heading also mentions unclear root cause. A low achievement rate can overlap the Iterate conditions; the source has no complete precedence algorithm. Write a reviewed recommendation with the conflicting evidence visible, not an automated shutdown.
Preserve the data even if this version stops. Archive buyer language, objections and profile findings; return to MVO Phase 1/2 with what was learned; and consider whether an engaged segment needs a different offer. The claim about most millionaires having failed offers is unverified and unnecessary to the decision.
Use the full checklist and submit a documented decision
Read every before/during/after item. They include timing and consent requirements that the scorecard alone does not capture. Checklist completion requires evidence, not a tick added because a draft exists.
Complete source procedure for study:
Master Beta Testing Checklist
Before Beta Opens
☐ Run all 7 Pre-Beta Gate criteria — all must pass
☐ Cohort size defined (5–15 people)
☐ Recruitment message written using the 5-element framework
☐ Beta price set using Pricing Matrix — not free, not full price
☐ Conditional guarantee written and reviewed
☐ Buyer commitments documented and disclosed at purchase
☐ Delivery schedule mapped (max 4 weeks)
☐ Minimum viable tech stack confirmed (no over-building)
☐ Baseline onboarding survey built in Typeform or Google Forms
☐ Per-module pulse surveys built (one per module, 5 questions max)
☐ Exit interview question list prepared and Zoom/Meet links ready
☐ Recording consent language added to checkout and onboarding email
During Beta Delivery
☐ Baseline survey sent within 24 hours of purchase — before Module 1
☐ Each module delivered with one clear action item attached
☐ Pulse survey sent within 24 hours of each module delivery
☐ Pulse survey responses reviewed within 48 hours — flag any score below 7
☐ Early result achieved — request video testimonial immediately
☐ Dropout identified — conduct short 5-minute check-in within 48 hours
☐ All sessions recorded with participant consent
☐ Negative Avatar data logged in Airtable as it emerges
After Beta Closes
☐ Exit interviews scheduled with all completers within 7 days of programme end
☐ At least 3 specific result testimonials confirmed (with numbers)
☐ At least 1 video testimonial recorded and ready
☐ Negative Avatar Profile template completed for every refund and dropout
☐ Go / No-Go Scorecard completed — all 8 metrics scored
☐ Decision logged: Launch / Iterate / Kill
☐ If Launch: offer stack rebuilt with Trim & Stack using beta buyer language
☐ If Iterate: specific fixes documented and assigned before Beta 2 opens
☐ If Kill: all data archived, MVO Playbook Phase 1 reopened with new data
☐ Beta graduates offered next-tier or founding member price (72-hour window)
☐ Beta results summary added to AEO/GEO keyword schema as citable case study data
The source's instruction to add a case study to AEO/GEO assets cannot guarantee rankings or citations. The keyword schema and a functioning Airtable Beta Records system are not supplied. No launch, audience contact, purchase, recording or database change occurs through this lesson.
Complete every field below, including the beta dates. That field is present in the Word original even though the connected readable-text export omits its content control.
Field
Your Data
Beta name and version
Beta dates (open → close)
Cohort size (enrolled)
Cohort size (completed)
Completion rate (%)
Result achievement rate (% of completers with measurable result)
Average module clarity score (1–10)
Average perceived value score (1–10)
Refund rate (%)
Specific result testimonials collected (#)
Video testimonials collected (#)
Price validated by exit interview (# of 8 said yes to full price)
Go / No-Go decision
☐ Launch ☐ Iterate ☐ Kill
Top 3 copy phrases from exit interviews
1.2.3.
Top 3 objections to address on sales page
1.2.3.
Negative Avatar root cause summary
Single most important product change before launch
Treat the beta as a disclosed service and an opportunity to learn. The source's statement that each data point is worth one hundred assumptions is rhetoric, not a calculated value. Good records distinguish observations, source rules, interpretation, missing evidence and proposed action.
The MVO Playbook V5, complete Trim & Stack method, exact next-problem interview and keyword-schema implementation remain unresolved supporting resources. RISER NATION CORP is the project destination. IF YOU AREN'T BUILDING, YOU ARE DESTROYING.
Turn in: a beta plan with all seven gate records, cohort and participation terms, delivery schedule, three feedback instruments and a blank eight-metric scorecard. If you already have permission to use actual beta data, include a separately labelled evidence-based Launch/Iterate/Kill recommendation, unresolved conflicts and one prioritized next action. Keep it in your course work folder until a submission destination is confirmed. A reviewer should check the evidence and feasibility before any business action.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — BETA TESTING METHODOLOGY
From Raw Idea to Launch-Ready, Proof-Backed Offer
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
A Beta Test is the structured, paid validation of a new offer before full public launch. Its purpose is not to build confidence — it is to generate real buyer data, proof assets, product intelligence, and a Negative Avatar profile, all while funding initial delivery costs.
This SOP covers eight phases: cohort design, pricing, delivery architecture, feedback collection, Negative Avatar extraction, proof harvesting, the beta-to-launch transition decision, and the kill/pivot/iterate framework.
The Hormozi Principle
Never build what you haven't sold. Never scale what you haven't proven. The beta is the moment between those two rules — you have sold it, you are now proving it before you scale it.
The Kennedy Rule
Every beta buyer is a research subject, a testimonial factory, and a funnel-design consultant — all at once. Extract maximum intelligence from minimum exposure.
The Brunson Lens
The beta is where your Epiphany Bridge story gets validated. The language your beta buyers use to describe their transformation is the copy for your launch.
Pre-Beta Gate: When to Run a Beta
A beta is appropriate under three conditions. You have validated market demand (someone said 'I would pay for that'), you have a deliverable you can fulfil even in rough form, and you do not yet have enough social proof or product-market language to launch publicly at full price.
It is not a substitute for offer validation. If you have not run the MVO Playbook V5 Phase 1 kill filters and 6-score monetisation filter, do that first. A beta on a fundamentally broken offer produces expensive confusion, not data.
Pre-Beta Launch Criteria — Required Before Proceeding
Criterion
Threshold
Status
Market pain validated
At least 3 verbatim quotes from real people describing the problem in their own words
☐ Pass / ☐ Fail
6-Score Filter passed
Score of 22 or higher on the MVO Playbook V5 monetisation filter
☐ Pass / ☐ Fail
Kill filters cleared
All 3 kill filters: Cheap to Ignore, Massive Behaviour Change, Existing Excellent Cheap Solution — all negative
☐ Pass / ☐ Fail
Core deliverable defined
You can describe what the buyer receives and the timeline in one sentence
☐ Pass / ☐ Fail
Fulfilment capacity confirmed
You can deliver to 5–15 people without breaking your calendar, your margin, or your sanity
☐ Pass / ☐ Fail
Flagship Promise passes
A non-marketer can repeat the core promise in one sentence after hearing it once
☐ Pass / ☐ Fail
Mechanism named
Your unique method has a specific name (not 'my system' or 'my process')
☐ Pass / ☐ Fail
Hard Rule
If more than one criterion shows Fail — do not proceed to beta. Return to MVO Playbook Phase 2 and rebuild the offer construction. A beta on a weak offer produces bad data and costs real buyers trust.
PHASE 1
Beta Cohort Design & Recruitment
Who gets in, how many, and how you find them
Cohort Size
The ideal beta cohort is 5 to 15 people. Below 5 you lack enough signal diversity to draw reliable conclusions. Above 20 you are running a product launch, not a beta — the support load and feedback volume exceed what one operator can process and act on within the beta window.
Cohort Size
Best For
Risk
5–8 people
High-touch done-with-you or done-for-you offers above $500
Lower data volume — every dropout matters
8–15 people
Group programmes, courses, and workshops. The sweet spot for most MVOs
Manageable feedback load with strong signal
15–25 people
Lower-ticket offers ($47–$197) with minimal live interaction required
Feedback processing becomes time-intensive — assign a note-taker
Recruitment Sources (Priority Order)
Recruit in this order. Each source produces progressively colder buyers and requires more selling effort.
• Existing email list — warm audience, already aware of you. Highest conversion, fastest recruitment.
• Past buyers of related offers — already validated buyers. Offer beta as next logical step.
• Existing community members (Discord, Skool, Facebook Group) — medium warm, already engaged.
• Social media audience (organic posts announcing beta) — cold to warm depending on platform.
• Direct outreach via DM to people who have engaged with your content — cold, requires personalisation.
Recruitment Message Framework
The beta recruitment message is not a sales page. It is a direct, honest conversation. Use this structure:
Element
What to Write
Example
What you are building
Name the offer and the transformation in one sentence
I am building a 4-week intensive that helps HVAC contractors get 10 qualified service calls per week using a local content system.
Why beta pricing
Honest reason — you want real-world data, case studies, and feedback in exchange for a reduced price
In exchange for the discounted beta price I am asking for one interview call at the end and honest written feedback on every module.
What they commit to
Be specific about their time, participation, and feedback obligations
This requires 3–5 hours per week for 4 weeks, showing up to the two live calls, and completing the feedback form after each module.
The beta price
State the price clearly. Do not hide it.
$297 for the full 4-week programme. It will be $997 at public launch.
Hard deadline
Create real urgency — beta spots are genuinely limited by your capacity
I am taking exactly 10 people. Doors close Friday at midnight or when full.
PHASE 2
Beta Pricing Strategy
Price for commitment, not for charity
The Pricing Philosophy
Beta pricing has one purpose: to attract committed buyers who will show up, do the work, and give you honest feedback. It is not a favour or a discount for fans. Free beta participants have zero skin in the game and produce near-zero useful data. Paid beta participants show up, complete modules, and tell you exactly where the offer breaks.
Hormozi's Commitment Rule
The lower the price, the lower the commitment. If your beta is free, expect 60–80% dropout. At $97, expect 40–60% dropout. At $297+, expect 80%+ completion. Price for the completion rate you need, not the conversion rate you want.
Beta Pricing Matrix
Offer Type
Full Launch Price
Beta Price Range
Rationale
Low-ticket MVO (template / mini-course)
$97–$297
$27–$67
Price reduction is meaningful but still filters for intent
Mid-ticket MVO (group intensive / workshop)
$297–$997
$97–$297
Sweet spot for commitment — still an investment, clearly discounted
Core Offer (group programme)
$997–$4,997
$297–$997
Price must reflect the time investment required from the buyer
High-ticket (DWY / DFY)
$2,500–$10,000
$497–$1,500
Even at beta price this is a serious purchase — screen with application
What the Beta Price Buys You
The beta buyer receives the offer at a significant discount. In exchange they provide the following, which must be made explicit at the point of purchase:
☐ Completion of a short feedback form (5–10 questions) after each module or milestone
☐ Attendance at all live calls or access to recordings within 48 hours
☐ A 20–30 minute exit interview call at the end of the beta
☐ Written permission to use their results and feedback as a testimonial
☐ Advance notice before any public screenshots or case study publication
Guarantee Policy During Beta
Apply a conditional guarantee during beta, not a full money-back. The buyer gets results if they complete the work. This is appropriate because the offer is unproven and unfinished — a full unconditional guarantee on an unproven product creates adverse selection (people who want to consume content and refund).
Beta Guarantee Language
If you complete all modules, attend both live calls, and submit all feedback forms within the programme window and do not see [specific promised result], I will work with you personally at no additional cost until you do.
PHASE 3
Beta Delivery Architecture
Structure the experience to maximise completion and data output
Core Delivery Principles
• Deliver in the simplest format you can. A Google Doc, Zoom call, and Notion page beat a polished course platform. The beta is testing the transformation, not the technology.
• Shorter is better. Four weeks maximum for a first beta. Six-week+ programmes lose participants to life and reduce feedback quality on later modules.
• Every session ends with a structured debrief question. Do not wait for the exit interview to collect data.
• Record everything. Your beta delivery recordings become your course content, ad testimonials, and case study material.
Beta Delivery Schedule Template
Week
Delivery Activity
Feedback Trigger
Data Collected
Week 0 (Pre-start)
Welcome call (30 min). Onboarding survey. Baseline metrics captured. Set expectations for the programme.
Baseline survey (see Phase 4)
Current situation, goals, fears, anti-language
Week 1
Module 1 delivery. One live or recorded session (45–90 min). First quick win delivered.
Module 1 feedback form (5 questions)
Clarity of instruction, first win achieved yes/no, confusion points
Week 2
Module 2 delivery. Progress check-in. Address top objections from Week 1 feedback.
Module 2 feedback form + 10-min group call
Progress velocity, where they are getting stuck, support needs
Week 3
Module 3 delivery. Case study capture from any early winners. Peer share in community.
Module 3 feedback form + peer testimonials
Early results data, social proof harvesting begins
Week 4
Module 4 delivery. Final implementation session. Begin exit interview scheduling.
Module 4 feedback form
Completion status, confidence level, result achieved yes/no
Week 5 (Post-programme)
Exit interviews (20–30 min each). Final results capture. Testimonial collection. Offer for public launch at beta graduate price.
Exit interview (see Phase 4 template)
Full transformation arc, before/after metrics, referral intent, ascension readiness
The Minimum Viable Delivery Stack
You do not need a learning management system, a polished course platform, or a custom app to run a beta. Use the minimum viable tech stack:
Function
Tool
Cost
Why This Tool
Video delivery
Loom or Zoom recording
Free–$15/mo
Fast to produce, easy to update between cohorts
Content hosting
Notion, Google Drive, or Kajabi
Free–$69/mo
Accessible on any device, easy to update live
Community / Q&A
Private Slack, Discord, or Facebook Group
Free
All feedback in one searchable place
Feedback forms
Typeform or Google Forms
Free–$25/mo
Branching logic for richer responses
Exit interviews
Zoom or Google Meet
Free
Record for testimonial extraction
Payment processing
Stripe or ThriveCart
$0 + 2.9%
Clean checkout, easy refund processing if needed
PHASE 4
Feedback Collection System
Extract signal, not sentiment
The Three Feedback Instruments
You need three distinct instruments. Each captures different data at a different emotional moment in the buyer's journey.
Instrument 1 — Baseline Onboarding Survey
Administered before Module 1 starts. Captures the buyer's current state, which becomes the 'before' half of your case study.
• Describe your current situation with [core problem] in 2–3 sentences. Use your own words.
• What have you already tried to solve? What happened?
• On a scale of 1–10, how urgent is solving this in the next 90 days? What is driving that score?
• What does success look like for you at the end of this programme? Be specific — numbers where possible.
• What is the single biggest thing that almost stopped you from joining today?
• Is there anything you are afraid this programme will NOT cover that you need?
Why This Question Matters
The answer to 'What almost stopped you from joining?' is your single most valuable piece of copy. It is the exact objection you need to address on your sales page, in your launch emails, and in your ads. Collect it before they feel good about their decision.
Sent within 24 hours of each module delivery. Short enough to complete without friction. Do not ask open-ended questions at this stage — closed scales with one optional comment field only.
Question
Format
What You Are Measuring
How clear was this module? (1–10)
Number scale
Instruction quality — below 7 = rewrite the module
Did you complete the action item from this module? (Yes / Partially / No)
Multiple choice
Completion rate — below 60% = the task is too hard or unclear
What was your single biggest confusion or sticking point? (Optional)
Short text
Friction points to fix before public launch
Rate the value delivered in this module relative to what you paid. (1–10)
Number scale
Perceived value — below 7 on any module = gap in the offer stack
What do you wish was included in this module that wasn't? (Optional)
Short text
Missing content that becomes a bonus at public launch
The most valuable data source in the entire beta. Schedule with every participant who completes the programme. Use this exact question sequence:
• Can you walk me through what your situation was before you joined? What was happening?
• What had you already tried? Why didn't those things work?
• What made you decide to join this specific programme at this specific time?
• Walk me through what happened during the programme. What shifted first?
• What specific result have you achieved that you can put a number on?
• What was the most valuable part? What would you remove or improve?
• Who else do you know who needs this? Why would they need it?
• Knowing what you know now, would you pay the full public price of [launch price]? Why?
• Is there anything you were hoping to get from this that you didn't?
Copy Mining Instruction
During the exit interview, listen for exact phrases — 3-to-8-word strings that describe the transformation in the buyer's own voice. Circle them. Underline them. These phrases become your headline, your hook, your ad copy, and your email subject lines. Your copy should sound like your buyers, not like you.
PHASE 5
Negative Avatar Extraction
The data most operators ignore — and the gold mine they are walking past
What the Negative Avatar Is
The Negative Avatar is the profile of the person who bought your beta, did not get results, or requested a refund. Most operators treat these people as a problem to manage. In reality, they are the single most valuable product development signal available.
The Hormozi Insight
Your refund rate and dropout rate are not failure metrics. They are product diagnostics. Each one tells you either that you attracted the wrong buyer, that a specific module has a fatal friction point, or that your guarantee is attracting people who should never have bought. Mine every single one.
Negative Avatar Data Points to Capture
Scenario
Questions to Ask
What It Reveals
Buyer completes less than 50% of modules
Which module did they stop at? What was happening in their life at that point? Did they find the content too hard, too easy, or unclear?
Friction point in delivery — the exact module that needs to be rebuilt
Buyer completes but reports no result
What action steps did they complete? Where did implementation break down? What would have made the result achievable?
Gap between instruction and implementation — a missing 'done-for-you' component or a missing prerequisite
Buyer requests a refund
Why did you decide this wasn't right for you? What were you hoping for that you didn't find? What would have made you stay?
Expectation mismatch — either the sales copy overpromised or the wrong buyer profile is being attracted
Buyer says 'it wasn't for me'
Can you describe who you think this IS for? What kind of person would get the most from this?
Avatar mismatch — they will describe your actual target buyer better than you can from the outside
Buyer ghosts after purchase
Send one short check-in: 'I noticed you haven't started yet — is everything okay? Is there anything stopping you from getting in?'
Onboarding failure — the first step is too hard or the welcome experience is not creating momentum
Negative Avatar Profile Template
After every beta, complete this template. Feed it into your next offer design cycle and your avatar V2 update.
• Negative Avatar Name: [Give them a character name]
• Entry point: How did they find you? What language did they respond to in your recruitment message?
• Where they dropped off: Which module, week, or milestone marked their exit?
• What offer would have served them: [Describe the offer they actually needed — this may become your next product]
• Copy and recruitment change triggered: [Specific change to sales page, ad targeting, or application screening]
PHASE 6
Proof Harvesting Protocol
Every beta buyer is a testimonial factory
The Four Proof Assets
By the end of a properly run beta you should have four distinct types of proof asset, each serving a different function on your sales page, in your ads, and in your email sequences.
Proof Asset
How to Collect
Where It Is Used
Specific result testimonial
Exit interview question 5: 'What specific result have you achieved that you can put a number on?' Capture exact numbers, timeframes, and before/after states.
Sales page hero section, email Day 6 in 14-day sequence, ad creative (transformation hook)
Story testimonial (Epiphany Bridge)
Exit interview questions 1–4: the full before/during/after journey. Edit into a 150–300 word written testimonial using the buyer's own words.
Sales page social proof section, case study article for AEO/GEO, webinar stack slide
Objection-killing testimonial
Exit interview question 8: 'Would you pay the full price knowing what you know now?' The answer directly addresses price objection on your sales page.
Sales page FAQ section, email Day 11 (objection handling), ad variant targeting price-objection audience
Video testimonial
At the end of the exit interview, ask: 'Would you be willing to record a 60-second video summarising what you experienced?' Provide three prompts: where you were, what happened, where you are now.
Sales page hero, YouTube channel, social proof ad variant, VSL social proof section
The Proof-to-Promise Match Rule
Every proof asset must match the exact promise you make in your core offer. If you promise '30 qualified leads in 30 days' and your testimonials say 'great experience' — your proof is worthless. Audit every testimonial against this standard before using it.
Your Promise
Required Proof Match
Weak Proof (Discard)
30 qualified leads in 30 days
'We generated 34 qualified leads in the first 28 days' + screenshot
'Really helpful programme, loved the community'
Reduce employee churn by 40%
'We went from 6 departures per quarter to 2, in 90 days' + HR data
'Great frameworks, very actionable'
Build and launch your first course in 14 days
'I launched on day 11 with 12 pre-sales' + screenshot of sales dashboard
'Russell really knows his stuff'
Proof Collection Timing
Request the video testimonial at the peak of the buyer's emotional high — immediately after they hit their first major result, not after the programme ends. Emotional proximity to the win produces better testimonials than reflective distance.
PHASE 7
Beta-to-Launch Transition Decision
The data thresholds that tell you when you are ready
The Go / No-Go Scorecard
After the beta closes and exit interviews are complete, run this scorecard. It is pass/fail — not a weighted average. Every threshold must be met before proceeding to public launch at full price.
Metric
Minimum Threshold
Strong Signal
Status
Programme completion rate
60% of beta cohort completed the full programme
80%+
☐ Pass / ☐ Fail
Result achievement rate
50% of completers achieved a specific, measurable result
70%+
☐ Pass / ☐ Fail
Average module clarity score
7.0 or above across all module pulse surveys
8.5+
☐ Pass / ☐ Fail
Perceived value score
7.0 or above (relative to price paid)
8.5+
☐ Pass / ☐ Fail
Refund rate
Under 15% of beta cohort
Under 5%
☐ Pass / ☐ Fail
Specific result testimonials collected
At least 3 testimonials with specific metrics
5+
☐ Pass / ☐ Fail
Video testimonials collected
At least 1 video testimonial usable in ads and sales page
3+
☐ Pass / ☐ Fail
Public launch price validated
At least 4 of 8 exit interview respondents confirm they would pay full price
7+/8
☐ Pass / ☐ Fail
The Single Veto Rule
If completion rate falls below 60% OR result achievement rate falls below 50%, do not launch publicly regardless of other scores. These two metrics tell you the transformation is not yet reliable enough to charge full price and scale with paid ads.
Beta Graduate Offer (Before Public Launch)
Before closing the beta and opening public doors, offer beta graduates a preferential path to the next tier or a founding member price on the public launch. This serves three functions: it generates immediate revenue, it validates the ascension logic, and it creates urgency for the public launch through social proof from people already inside.
• Offer beta graduates the Core Offer or Continuity tier at the beta price for 72 hours after the programme ends.
• Use their testimonials to seed the public launch sequence — 'Here is what 10 beta participants experienced...'
• Invite the top 2–3 results-getters to a founding member inner circle at a reduced annual rate.
PHASE 8
Kill / Pivot / Iterate Framework
Making the right decision when the data comes in
The Three Possible Outcomes
Every beta produces one of three outcomes. The decision framework below tells you which path to take based on the Go/No-Go scorecard and the qualitative data from exit interviews and Negative Avatar profiles.
Outcome A — Launch (Scorecard passes, strong proof)
All Go/No-Go thresholds met. At least 3 specific result testimonials. Refund rate below 10%. Proceed to public launch within 30 days.
• Apply Hormozi's Trim & Stack to rebuild the offer as a Grand Slam Offer using beta buyer language.
• Rewrite the sales page headline and hero using exact phrases from exit interviews.
• Build the Stack Slide with named bonuses, each solving a specific sub-problem identified in beta feedback.
• Set the guarantee level one tier higher than what you offered during beta.
• Deploy beta testimonials across sales page, email Day 6, and first ad creative.
• Open cart at full public price. Offer beta graduates a founding member discount for 72 hours only.
Outcome B — Iterate (1–3 thresholds failed, clear fix exists)
One to three Go/No-Go thresholds failed but the root cause is diagnosable and fixable. Run a second beta cohort after implementing the fixes. Do not launch publicly.
Failed Threshold
Likely Root Cause
Specific Fix Before Beta 2
Completion rate below 60%
Module too complex, action steps unclear, or no accountability mechanism
Simplify action steps to one per module. Add a weekly accountability check-in. Rebuild the module that had the lowest completion rate.
Result achievement below 50%
Missing prerequisite, implementation gap, or transformation promise too large for the timeframe
Add a done-for-you component to the module where implementation breaks down. Adjust the promise to match actual result timeline.
Module clarity score below 7.0
Instruction assumes too much prior knowledge or lacks concrete examples
Add a real-world example to every step. Record a 'watch me do this' walkthrough for each action item.
Refund rate above 15%
Sales copy is attracting the wrong buyer profile or expectation mismatch at checkout
Add a 'This is NOT for you if...' section to the sales page. Add a pre-purchase checklist. Rewrite the promise to match actual delivery.
Perceived value below 7.0
Offer stack does not match the price or delivery format underdelivers on expectation
Add one high-perceived-value bonus (name it, assign a standalone value). Upgrade the delivery format (add a live call if it was self-paced).
Outcome C — Kill (Multiple core thresholds failed or root cause unclear)
More than three thresholds failed, or the result achievement rate is below 30%, or the Negative Avatar profile reveals a fundamental mismatch between the offer and the market. Kill this version of the offer. Do not iterate — start again with a different mechanism or a different buyer profile.
Kennedy's Rule on Killing Offers
Most millionaires have a trail of failed offers behind them. Killing a beta that doesn't work is not failure — it is the system functioning correctly. The failure would be scaling a broken offer with paid ads because you were too attached to kill it.
• Archive all beta data — the buyer language, the objections, and the Negative Avatar profile are all assets even if the offer is dead.
• Return to MVO Playbook Phase 1 and Phase 2 with the new data. The kill is a redirect, not a reset.
• Consider whether the Negative Avatar profile points to a completely different offer that would serve the buyer who did engage.
Master Beta Testing Checklist
Before Beta Opens
☐ Run all 7 Pre-Beta Gate criteria — all must pass
☐ Cohort size defined (5–15 people)
☐ Recruitment message written using the 5-element framework
☐ Beta price set using Pricing Matrix — not free, not full price
☐ Conditional guarantee written and reviewed
☐ Buyer commitments documented and disclosed at purchase
☐ Delivery schedule mapped (max 4 weeks)
☐ Minimum viable tech stack confirmed (no over-building)
☐ Baseline onboarding survey built in Typeform or Google Forms
☐ Per-module pulse surveys built (one per module, 5 questions max)
☐ Exit interview question list prepared and Zoom/Meet links ready
☐ Recording consent language added to checkout and onboarding email
During Beta Delivery
☐ Baseline survey sent within 24 hours of purchase — before Module 1
☐ Each module delivered with one clear action item attached
☐ Pulse survey sent within 24 hours of each module delivery
☐ Pulse survey responses reviewed within 48 hours — flag any score below 7
☐ Early result achieved — request video testimonial immediately
☐ Dropout identified — conduct short 5-minute check-in within 48 hours
☐ All sessions recorded with participant consent
☐ Negative Avatar data logged in Airtable as it emerges
After Beta Closes
☐ Exit interviews scheduled with all completers within 7 days of programme end
☐ At least 3 specific result testimonials confirmed (with numbers)
☐ At least 1 video testimonial recorded and ready
☐ Negative Avatar Profile template completed for every refund and dropout
☐ Go / No-Go Scorecard completed — all 8 metrics scored
☐ Decision logged: Launch / Iterate / Kill
☐ If Launch: offer stack rebuilt with Trim & Stack using beta buyer language
☐ If Iterate: specific fixes documented and assigned before Beta 2 opens
☐ If Kill: all data archived, MVO Playbook Phase 1 reopened with new data
☐ Beta graduates offered next-tier or founding member price (72-hour window)
☐ Beta results summary added to AEO/GEO keyword schema as citable case study data
Beta Scorecard Template
Complete this after exit interviews close. File in Airtable under Offer Iteration > Beta Records.
Field
Your Data
Beta name and version
Beta dates (open → close)
Cohort size (enrolled)
Cohort size (completed)
Completion rate (%)
Result achievement rate (% of completers with measurable result)
Average module clarity score (1–10)
Average perceived value score (1–10)
Refund rate (%)
Specific result testimonials collected (#)
Video testimonials collected (#)
Price validated by exit interview (# of 8 said yes to full price)
Go / No-Go decision
☐ Launch ☐ Iterate ☐ Kill
Top 3 copy phrases from exit interviews
1.2.3.
Top 3 objections to address on sales page
1.2.3.
Negative Avatar root cause summary
Single most important product change before launch
Final Principle
The beta is not a soft launch. It is a data collection instrument disguised as a programme. Run it with the discipline of a scientist and the care of a craftsman. Every data point it produces is worth 100 assumptions you would otherwise be making at full-price launch.
RISER Nation Master Operating System | Beta Testing Methodology SOP | Version 1.0 | 2026 Edition
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — BETA TESTING METHODOLOGY ",
"",
"From Raw Idea to Launch-Ready, Proof-Backed Offer",
"Kennedy × Hormozi × Brunson × 2026 Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"A Beta Test is the structured, paid validation of a new offer before full public launch. Its purpose is not to build confidence — it is to generate real buyer data, proof assets, product intelligence, and a Negative Avatar profile, all while funding initial delivery costs.",
"",
"This SOP covers eight phases: cohort design, pricing, delivery architecture, feedback collection, Negative Avatar extraction, proof harvesting, the beta-to-launch transition decision, and the kill/pivot/iterate framework.",
"",
"The Hormozi Principle",
"Never build what you haven't sold. Never scale what you haven't proven. The beta is the moment between those two rules — you have sold it, you are now proving it before you scale it.",
"",
"The Kennedy Rule",
"Every beta buyer is a research subject, a testimonial factory, and a funnel-design consultant — all at once. Extract maximum intelligence from minimum exposure.",
"",
"The Brunson Lens",
"The beta is where your Epiphany Bridge story gets validated. The language your beta buyers use to describe their transformation is the copy for your launch.",
"",
"Pre-Beta Gate: When to Run a Beta",
"A beta is appropriate under three conditions. You have validated market demand (someone said 'I would pay for that'), you have a deliverable you can fulfil even in rough form, and you do not yet have enough social proof or product-market language to launch publicly at full price.",
"",
"It is not a substitute for offer validation. If you have not run the MVO Playbook V5 Phase 1 kill filters and 6-score monetisation filter, do that first. A beta on a fundamentally broken offer produces expensive confusion, not data.",
"",
"Pre-Beta Launch Criteria — Required Before Proceeding",
"",
"Criterion",
"Threshold",
"Status",
"Market pain validated",
"At least 3 verbatim quotes from real people describing the problem in their own words",
"☐ Pass / ☐ Fail",
"6-Score Filter passed",
"Score of 22 or higher on the MVO Playbook V5 monetisation filter",
"☐ Pass / ☐ Fail",
"Kill filters cleared",
"All 3 kill filters: Cheap to Ignore, Massive Behaviour Change, Existing Excellent Cheap Solution — all negative",
"☐ Pass / ☐ Fail",
"Core deliverable defined",
"You can describe what the buyer receives and the timeline in one sentence",
"☐ Pass / ☐ Fail",
"Fulfilment capacity confirmed",
"You can deliver to 5–15 people without breaking your calendar, your margin, or your sanity",
"☐ Pass / ☐ Fail",
"Flagship Promise passes",
"A non-marketer can repeat the core promise in one sentence after hearing it once",
"☐ Pass / ☐ Fail",
"Mechanism named",
"Your unique method has a specific name (not 'my system' or 'my process')",
"☐ Pass / ☐ Fail",
"",
"Hard Rule",
"If more than one criterion shows Fail — do not proceed to beta. Return to MVO Playbook Phase 2 and rebuild the offer construction. A beta on a weak offer produces bad data and costs real buyers trust.",
"",
"",
"PHASE 1",
"Beta Cohort Design & Recruitment",
"Who gets in, how many, and how you find them",
"",
"Cohort Size",
"The ideal beta cohort is 5 to 15 people. Below 5 you lack enough signal diversity to draw reliable conclusions. Above 20 you are running a product launch, not a beta — the support load and feedback volume exceed what one operator can process and act on within the beta window.",
"",
"Cohort Size",
"Best For",
"Risk",
"5–8 people",
"High-touch done-with-you or done-for-you offers above $500",
"Lower data volume — every dropout matters",
"8–15 people",
"Group programmes, courses, and workshops. The sweet spot for most MVOs",
"Manageable feedback load with strong signal",
"15–25 people",
"Lower-ticket offers ($47–$197) with minimal live interaction required",
"Feedback processing becomes time-intensive — assign a note-taker",
"",
"Recruitment Sources (Priority Order)",
"Recruit in this order. Each source produces progressively colder buyers and requires more selling effort.",
"",
"• Existing email list — warm audience, already aware of you. Highest conversion, fastest recruitment.",
"• Past buyers of related offers — already validated buyers. Offer beta as next logical step.",
"• Existing community members (Discord, Skool, Facebook Group) — medium warm, already engaged.",
"• Social media audience (organic posts announcing beta) — cold to warm depending on platform.",
"• Direct outreach via DM to people who have engaged with your content — cold, requires personalisation.",
"",
"Recruitment Message Framework",
"The beta recruitment message is not a sales page. It is a direct, honest conversation. Use this structure:",
"",
"Element",
"What to Write",
"Example",
"What you are building",
"Name the offer and the transformation in one sentence",
"I am building a 4-week intensive that helps HVAC contractors get 10 qualified service calls per week using a local content system.",
"Why beta pricing",
"Honest reason — you want real-world data, case studies, and feedback in exchange for a reduced price",
"In exchange for the discounted beta price I am asking for one interview call at the end and honest written feedback on every module.",
"What they commit to",
"Be specific about their time, participation, and feedback obligations",
"This requires 3–5 hours per week for 4 weeks, showing up to the two live calls, and completing the feedback form after each module.",
"The beta price",
"State the price clearly. Do not hide it.",
"$297 for the full 4-week programme. It will be $997 at public launch.",
"Hard deadline",
"Create real urgency — beta spots are genuinely limited by your capacity",
"I am taking exactly 10 people. Doors close Friday at midnight or when full.",
"",
"",
"PHASE 2",
"Beta Pricing Strategy",
"Price for commitment, not for charity",
"",
"The Pricing Philosophy",
"Beta pricing has one purpose: to attract committed buyers who will show up, do the work, and give you honest feedback. It is not a favour or a discount for fans. Free beta participants have zero skin in the game and produce near-zero useful data. Paid beta participants show up, complete modules, and tell you exactly where the offer breaks.",
"",
"Hormozi's Commitment Rule",
"The lower the price, the lower the commitment. If your beta is free, expect 60–80% dropout. At $97, expect 40–60% dropout. At $297+, expect 80%+ completion. Price for the completion rate you need, not the conversion rate you want.",
"",
"Beta Pricing Matrix",
"",
"Offer Type",
"Full Launch Price",
"Beta Price Range",
"Rationale",
"Low-ticket MVO (template / mini-course)",
"$97–$297",
"$27–$67",
"Price reduction is meaningful but still filters for intent",
"Mid-ticket MVO (group intensive / workshop)",
"$297–$997",
"$97–$297",
"Sweet spot for commitment — still an investment, clearly discounted",
"Core Offer (group programme)",
"$997–$4,997",
"$297–$997",
"Price must reflect the time investment required from the buyer",
"High-ticket (DWY / DFY)",
"$2,500–$10,000",
"$497–$1,500",
"Even at beta price this is a serious purchase — screen with application",
"",
"What the Beta Price Buys You",
"The beta buyer receives the offer at a significant discount. In exchange they provide the following, which must be made explicit at the point of purchase:",
"",
"☐ Completion of a short feedback form (5–10 questions) after each module or milestone",
"☐ Attendance at all live calls or access to recordings within 48 hours",
"☐ A 20–30 minute exit interview call at the end of the beta",
"☐ Written permission to use their results and feedback as a testimonial",
"☐ Advance notice before any public screenshots or case study publication",
"",
"Guarantee Policy During Beta",
"Apply a conditional guarantee during beta, not a full money-back. The buyer gets results if they complete the work. This is appropriate because the offer is unproven and unfinished — a full unconditional guarantee on an unproven product creates adverse selection (people who want to consume content and refund).",
"",
"Beta Guarantee Language",
"If you complete all modules, attend both live calls, and submit all feedback forms within the programme window and do not see [specific promised result], I will work with you personally at no additional cost until you do.",
"",
"",
"PHASE 3",
"Beta Delivery Architecture",
"Structure the experience to maximise completion and data output",
"",
"Core Delivery Principles",
"• Deliver in the simplest format you can. A Google Doc, Zoom call, and Notion page beat a polished course platform. The beta is testing the transformation, not the technology.",
"• Shorter is better. Four weeks maximum for a first beta. Six-week+ programmes lose participants to life and reduce feedback quality on later modules.",
"• Every session ends with a structured debrief question. Do not wait for the exit interview to collect data.",
"• Record everything. Your beta delivery recordings become your course content, ad testimonials, and case study material.",
"",
"Beta Delivery Schedule Template",
"",
"Week",
"Delivery Activity",
"Feedback Trigger",
"Data Collected",
"Week 0 (Pre-start)",
"Welcome call (30 min). Onboarding survey. Baseline metrics captured. Set expectations for the programme.",
"Baseline survey (see Phase 4)",
"Current situation, goals, fears, anti-language",
"Week 1",
"Module 1 delivery. One live or recorded session (45–90 min). First quick win delivered.",
"Module 1 feedback form (5 questions)",
"Clarity of instruction, first win achieved yes/no, confusion points",
"Week 2",
"Module 2 delivery. Progress check-in. Address top objections from Week 1 feedback.",
"Module 2 feedback form + 10-min group call",
"Progress velocity, where they are getting stuck, support needs",
"Week 3",
"Module 3 delivery. Case study capture from any early winners. Peer share in community.",
"Module 3 feedback form + peer testimonials",
"Early results data, social proof harvesting begins",
"Week 4",
"Module 4 delivery. Final implementation session. Begin exit interview scheduling.",
"Module 4 feedback form",
"Completion status, confidence level, result achieved yes/no",
"Week 5 (Post-programme)",
"Exit interviews (20–30 min each). Final results capture. Testimonial collection. Offer for public launch at beta graduate price.",
"Exit interview (see Phase 4 template)",
"Full transformation arc, before/after metrics, referral intent, ascension readiness",
"",
"The Minimum Viable Delivery Stack",
"You do not need a learning management system, a polished course platform, or a custom app to run a beta. Use the minimum viable tech stack:",
"",
"Function",
"Tool",
"Cost",
"Why This Tool",
"Video delivery",
"Loom or Zoom recording",
"Free–$15/mo",
"Fast to produce, easy to update between cohorts",
"Content hosting",
"Notion, Google Drive, or Kajabi",
"Free–$69/mo",
"Accessible on any device, easy to update live",
"Community / Q&A",
"Private Slack, Discord, or Facebook Group",
"Free",
"All feedback in one searchable place",
"Feedback forms",
"Typeform or Google Forms",
"Free–$25/mo",
"Branching logic for richer responses",
"Exit interviews",
"Zoom or Google Meet",
"Free",
"Record for testimonial extraction",
"Payment processing",
"Stripe or ThriveCart",
"$0 + 2.9%",
"Clean checkout, easy refund processing if needed",
"",
"",
"PHASE 4",
"Feedback Collection System",
"Extract signal, not sentiment",
"",
"The Three Feedback Instruments",
"You need three distinct instruments. Each captures different data at a different emotional moment in the buyer's journey.",
"",
"Instrument 1 — Baseline Onboarding Survey",
"Administered before Module 1 starts. Captures the buyer's current state, which becomes the 'before' half of your case study.",
"",
"• Describe your current situation with [core problem] in 2–3 sentences. Use your own words.",
"• What have you already tried to solve? What happened?",
"• On a scale of 1–10, how urgent is solving this in the next 90 days? What is driving that score?",
"• What does success look like for you at the end of this programme? Be specific — numbers where possible.",
"• What is the single biggest thing that almost stopped you from joining today?",
"• Is there anything you are afraid this programme will NOT cover that you need?",
"",
"Why This Question Matters",
"The answer to 'What almost stopped you from joining?' is your single most valuable piece of copy. It is the exact objection you need to address on your sales page, in your launch emails, and in your ads. Collect it before they feel good about their decision.",
"",
"Instrument 2 — Per-Module Pulse Survey (5 questions, under 3 minutes)",
"Sent within 24 hours of each module delivery. Short enough to complete without friction. Do not ask open-ended questions at this stage — closed scales with one optional comment field only.",
"",
"Question",
"Format",
"What You Are Measuring",
"How clear was this module? (1–10)",
"Number scale",
"Instruction quality — below 7 = rewrite the module",
"Did you complete the action item from this module? (Yes / Partially / No)",
"Multiple choice",
"Completion rate — below 60% = the task is too hard or unclear",
"What was your single biggest confusion or sticking point? (Optional)",
"Short text",
"Friction points to fix before public launch",
"Rate the value delivered in this module relative to what you paid. (1–10)",
"Number scale",
"Perceived value — below 7 on any module = gap in the offer stack",
"What do you wish was included in this module that wasn't? (Optional)",
"Short text",
"Missing content that becomes a bonus at public launch",
"",
"Instrument 3 — Exit Interview (20–30 minutes, recorded)",
"The most valuable data source in the entire beta. Schedule with every participant who completes the programme. Use this exact question sequence:",
"",
"• Can you walk me through what your situation was before you joined? What was happening?",
"• What had you already tried? Why didn't those things work?",
"• What made you decide to join this specific programme at this specific time?",
"• Walk me through what happened during the programme. What shifted first?",
"• What specific result have you achieved that you can put a number on?",
"• What was the most valuable part? What would you remove or improve?",
"• Who else do you know who needs this? Why would they need it?",
"• Knowing what you know now, would you pay the full public price of [launch price]? Why?",
"• Is there anything you were hoping to get from this that you didn't?",
"",
"Copy Mining Instruction",
"During the exit interview, listen for exact phrases — 3-to-8-word strings that describe the transformation in the buyer's own voice. Circle them. Underline them. These phrases become your headline, your hook, your ad copy, and your email subject lines. Your copy should sound like your buyers, not like you.",
"",
"",
"PHASE 5",
"Negative Avatar Extraction",
"The data most operators ignore — and the gold mine they are walking past",
"",
"What the Negative Avatar Is",
"The Negative Avatar is the profile of the person who bought your beta, did not get results, or requested a refund. Most operators treat these people as a problem to manage. In reality, they are the single most valuable product development signal available.",
"",
"The Hormozi Insight",
"Your refund rate and dropout rate are not failure metrics. They are product diagnostics. Each one tells you either that you attracted the wrong buyer, that a specific module has a fatal friction point, or that your guarantee is attracting people who should never have bought. Mine every single one.",
"",
"Negative Avatar Data Points to Capture",
"",
"Scenario",
"Questions to Ask",
"What It Reveals",
"Buyer completes less than 50% of modules",
"Which module did they stop at? What was happening in their life at that point? Did they find the content too hard, too easy, or unclear?",
"Friction point in delivery — the exact module that needs to be rebuilt",
"Buyer completes but reports no result",
"What action steps did they complete? Where did implementation break down? What would have made the result achievable?",
"Gap between instruction and implementation — a missing 'done-for-you' component or a missing prerequisite",
"Buyer requests a refund",
"Why did you decide this wasn't right for you? What were you hoping for that you didn't find? What would have made you stay?",
"Expectation mismatch — either the sales copy overpromised or the wrong buyer profile is being attracted",
"Buyer says 'it wasn't for me'",
"Can you describe who you think this IS for? What kind of person would get the most from this?",
"Avatar mismatch — they will describe your actual target buyer better than you can from the outside",
"Buyer ghosts after purchase",
"Send one short check-in: 'I noticed you haven't started yet — is everything okay? Is there anything stopping you from getting in?'",
"Onboarding failure — the first step is too hard or the welcome experience is not creating momentum",
"",
"Negative Avatar Profile Template",
"After every beta, complete this template. Feed it into your next offer design cycle and your avatar V2 update.",
"",
"• Negative Avatar Name: [Give them a character name]",
"• Entry point: How did they find you? What language did they respond to in your recruitment message?",
"• Where they dropped off: Which module, week, or milestone marked their exit?",
"• Root cause (choose one): Wrong buyer profile / Missing prerequisite / Delivery friction / Expectation mismatch / External life event",
"• What offer would have served them: [Describe the offer they actually needed — this may become your next product]",
"• Copy and recruitment change triggered: [Specific change to sales page, ad targeting, or application screening]",
"",
"",
"PHASE 6",
"Proof Harvesting Protocol",
"Every beta buyer is a testimonial factory",
"",
"The Four Proof Assets",
"By the end of a properly run beta you should have four distinct types of proof asset, each serving a different function on your sales page, in your ads, and in your email sequences.",
"",
"Proof Asset",
"How to Collect",
"Where It Is Used",
"Specific result testimonial",
"Exit interview question 5: 'What specific result have you achieved that you can put a number on?' Capture exact numbers, timeframes, and before/after states.",
"Sales page hero section, email Day 6 in 14-day sequence, ad creative (transformation hook)",
"Story testimonial (Epiphany Bridge)",
"Exit interview questions 1–4: the full before/during/after journey. Edit into a 150–300 word written testimonial using the buyer's own words.",
"Sales page social proof section, case study article for AEO/GEO, webinar stack slide",
"Objection-killing testimonial",
"Exit interview question 8: 'Would you pay the full price knowing what you know now?' The answer directly addresses price objection on your sales page.",
"Sales page FAQ section, email Day 11 (objection handling), ad variant targeting price-objection audience",
"Video testimonial",
"At the end of the exit interview, ask: 'Would you be willing to record a 60-second video summarising what you experienced?' Provide three prompts: where you were, what happened, where you are now.",
"Sales page hero, YouTube channel, social proof ad variant, VSL social proof section",
"",
"The Proof-to-Promise Match Rule",
"Every proof asset must match the exact promise you make in your core offer. If you promise '30 qualified leads in 30 days' and your testimonials say 'great experience' — your proof is worthless. Audit every testimonial against this standard before using it.",
"",
"Your Promise",
"Required Proof Match",
"Weak Proof (Discard)",
"30 qualified leads in 30 days",
"'We generated 34 qualified leads in the first 28 days' + screenshot",
"'Really helpful programme, loved the community'",
"Reduce employee churn by 40%",
"'We went from 6 departures per quarter to 2, in 90 days' + HR data",
"'Great frameworks, very actionable'",
"Build and launch your first course in 14 days",
"'I launched on day 11 with 12 pre-sales' + screenshot of sales dashboard",
"'Russell really knows his stuff'",
"",
"Proof Collection Timing",
"Request the video testimonial at the peak of the buyer's emotional high — immediately after they hit their first major result, not after the programme ends. Emotional proximity to the win produces better testimonials than reflective distance.",
"",
"",
"PHASE 7",
"Beta-to-Launch Transition Decision",
"The data thresholds that tell you when you are ready",
"",
"The Go / No-Go Scorecard",
"After the beta closes and exit interviews are complete, run this scorecard. It is pass/fail — not a weighted average. Every threshold must be met before proceeding to public launch at full price.",
"",
"Metric",
"Minimum Threshold",
"Strong Signal",
"Status",
"Programme completion rate",
"60% of beta cohort completed the full programme",
"80%+",
"☐ Pass / ☐ Fail",
"Result achievement rate",
"50% of completers achieved a specific, measurable result",
"70%+",
"☐ Pass / ☐ Fail",
"Average module clarity score",
"7.0 or above across all module pulse surveys",
"8.5+",
"☐ Pass / ☐ Fail",
"Perceived value score",
"7.0 or above (relative to price paid)",
"8.5+",
"☐ Pass / ☐ Fail",
"Refund rate",
"Under 15% of beta cohort",
"Under 5%",
"☐ Pass / ☐ Fail",
"Specific result testimonials collected",
"At least 3 testimonials with specific metrics",
"5+",
"☐ Pass / ☐ Fail",
"Video testimonials collected",
"At least 1 video testimonial usable in ads and sales page",
"3+",
"☐ Pass / ☐ Fail",
"Public launch price validated",
"At least 4 of 8 exit interview respondents confirm they would pay full price",
"7+/8",
"☐ Pass / ☐ Fail",
"",
"The Single Veto Rule",
"If completion rate falls below 60% OR result achievement rate falls below 50%, do not launch publicly regardless of other scores. These two metrics tell you the transformation is not yet reliable enough to charge full price and scale with paid ads.",
"",
"Beta Graduate Offer (Before Public Launch)",
"Before closing the beta and opening public doors, offer beta graduates a preferential path to the next tier or a founding member price on the public launch. This serves three functions: it generates immediate revenue, it validates the ascension logic, and it creates urgency for the public launch through social proof from people already inside.",
"",
"• Offer beta graduates the Core Offer or Continuity tier at the beta price for 72 hours after the programme ends.",
"• Use their testimonials to seed the public launch sequence — 'Here is what 10 beta participants experienced...'",
"• Invite the top 2–3 results-getters to a founding member inner circle at a reduced annual rate.",
"",
"",
"PHASE 8",
"Kill / Pivot / Iterate Framework",
"Making the right decision when the data comes in",
"",
"The Three Possible Outcomes",
"Every beta produces one of three outcomes. The decision framework below tells you which path to take based on the Go/No-Go scorecard and the qualitative data from exit interviews and Negative Avatar profiles.",
"",
"Outcome A — Launch (Scorecard passes, strong proof)",
"All Go/No-Go thresholds met. At least 3 specific result testimonials. Refund rate below 10%. Proceed to public launch within 30 days.",
"",
"• Apply Hormozi's Trim & Stack to rebuild the offer as a Grand Slam Offer using beta buyer language.",
"• Rewrite the sales page headline and hero using exact phrases from exit interviews.",
"• Build the Stack Slide with named bonuses, each solving a specific sub-problem identified in beta feedback.",
"• Set the guarantee level one tier higher than what you offered during beta.",
"• Deploy beta testimonials across sales page, email Day 6, and first ad creative.",
"• Open cart at full public price. Offer beta graduates a founding member discount for 72 hours only.",
"",
"Outcome B — Iterate (1–3 thresholds failed, clear fix exists)",
"One to three Go/No-Go thresholds failed but the root cause is diagnosable and fixable. Run a second beta cohort after implementing the fixes. Do not launch publicly.",
"",
"Failed Threshold",
"Likely Root Cause",
"Specific Fix Before Beta 2",
"Completion rate below 60%",
"Module too complex, action steps unclear, or no accountability mechanism",
"Simplify action steps to one per module. Add a weekly accountability check-in. Rebuild the module that had the lowest completion rate.",
"Result achievement below 50%",
"Missing prerequisite, implementation gap, or transformation promise too large for the timeframe",
"Add a done-for-you component to the module where implementation breaks down. Adjust the promise to match actual result timeline.",
"Module clarity score below 7.0",
"Instruction assumes too much prior knowledge or lacks concrete examples",
"Add a real-world example to every step. Record a 'watch me do this' walkthrough for each action item.",
"Refund rate above 15%",
"Sales copy is attracting the wrong buyer profile or expectation mismatch at checkout",
"Add a 'This is NOT for you if...' section to the sales page. Add a pre-purchase checklist. Rewrite the promise to match actual delivery.",
"Perceived value below 7.0",
"Offer stack does not match the price or delivery format underdelivers on expectation",
"Add one high-perceived-value bonus (name it, assign a standalone value). Upgrade the delivery format (add a live call if it was self-paced).",
"",
"Outcome C — Kill (Multiple core thresholds failed or root cause unclear)",
"More than three thresholds failed, or the result achievement rate is below 30%, or the Negative Avatar profile reveals a fundamental mismatch between the offer and the market. Kill this version of the offer. Do not iterate — start again with a different mechanism or a different buyer profile.",
"",
"Kennedy's Rule on Killing Offers",
"Most millionaires have a trail of failed offers behind them. Killing a beta that doesn't work is not failure — it is the system functioning correctly. The failure would be scaling a broken offer with paid ads because you were too attached to kill it.",
"",
"• Archive all beta data — the buyer language, the objections, and the Negative Avatar profile are all assets even if the offer is dead.",
"• Return to MVO Playbook Phase 1 and Phase 2 with the new data. The kill is a redirect, not a reset.",
"• Consider whether the Negative Avatar profile points to a completely different offer that would serve the buyer who did engage.",
"",
"",
"Master Beta Testing Checklist",
"",
"Before Beta Opens",
"☐ Run all 7 Pre-Beta Gate criteria — all must pass",
"☐ Cohort size defined (5–15 people)",
"☐ Recruitment message written using the 5-element framework",
"☐ Beta price set using Pricing Matrix — not free, not full price",
"☐ Conditional guarantee written and reviewed",
"☐ Buyer commitments documented and disclosed at purchase",
"☐ Delivery schedule mapped (max 4 weeks)",
"☐ Minimum viable tech stack confirmed (no over-building)",
"☐ Baseline onboarding survey built in Typeform or Google Forms",
"☐ Per-module pulse surveys built (one per module, 5 questions max)",
"☐ Exit interview question list prepared and Zoom/Meet links ready",
"☐ Recording consent language added to checkout and onboarding email",
"",
"During Beta Delivery",
"☐ Baseline survey sent within 24 hours of purchase — before Module 1",
"☐ Each module delivered with one clear action item attached",
"☐ Pulse survey sent within 24 hours of each module delivery",
"☐ Pulse survey responses reviewed within 48 hours — flag any score below 7",
"☐ Early result achieved — request video testimonial immediately",
"☐ Dropout identified — conduct short 5-minute check-in within 48 hours",
"☐ All sessions recorded with participant consent",
"☐ Negative Avatar data logged in Airtable as it emerges",
"",
"After Beta Closes",
"☐ Exit interviews scheduled with all completers within 7 days of programme end",
"☐ Exit interview recordings reviewed — exact phrases highlighted for copy",
"☐ At least 3 specific result testimonials confirmed (with numbers)",
"☐ At least 1 video testimonial recorded and ready",
"☐ Negative Avatar Profile template completed for every refund and dropout",
"☐ Go / No-Go Scorecard completed — all 8 metrics scored",
"☐ Decision logged: Launch / Iterate / Kill",
"☐ If Launch: offer stack rebuilt with Trim & Stack using beta buyer language",
"☐ If Iterate: specific fixes documented and assigned before Beta 2 opens",
"☐ If Kill: all data archived, MVO Playbook Phase 1 reopened with new data",
"☐ Beta graduates offered next-tier or founding member price (72-hour window)",
"☐ Beta results summary added to AEO/GEO keyword schema as citable case study data",
"",
"Beta Scorecard Template",
"Complete this after exit interviews close. File in Airtable under Offer Iteration > Beta Records.",
"",
"Field",
"Your Data",
"Beta name and version",
"",
"Beta dates (open → close)",
"",
"Cohort size (enrolled)",
"",
"Cohort size (completed)",
"",
"Completion rate (%)",
"",
"Result achievement rate (% of completers with measurable result)",
"",
"Average module clarity score (1–10)",
"",
"Average perceived value score (1–10)",
"",
"Refund rate (%)",
"",
"Specific result testimonials collected (#)",
"",
"Video testimonials collected (#)",
"",
"Price validated by exit interview (# of 8 said yes to full price)",
"",
"Go / No-Go decision",
"☐ Launch ☐ Iterate ☐ Kill",
"Top 3 copy phrases from exit interviews",
"1.2.3.",
"Top 3 objections to address on sales page",
"1.2.3.",
"Negative Avatar root cause summary",
"",
"Single most important product change before launch",
"",
"",
"Final Principle",
"The beta is not a soft launch. It is a data collection instrument disguised as a programme. Run it with the discipline of a scientist and the care of a craftsman. Every data point it produces is worth 100 assumptions you would otherwise be making at full-price launch.",
"",
"",
"",
"RISER Nation Master Operating System | Beta Testing Methodology SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | Beta Testing Methodology SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
}
]
}
Use buyer-fit evidence to improve the offer
Begin with the mismatch, not a judgment
Imagine two buyers asking the same question. This is a hypothetical scene. One lacks a prerequisite. The other cannot find an instruction that should already be in the course. Their messages sound alike, but they need different help.
The gap is between labelling a difficult outcome and understanding it. A Negative Avatar profile is this source's model of a recurring mismatch between an offer and a buyer's needs. It should help you improve clarity, delivery and fit. It is not proof of a person's motives or worth.
This companion teaches five source archetypes and eight operating phases. The source-attributed Hormozi lens examines offer economics and fit. The Kennedy lens makes the intended buyer and exclusions specific. The next-offer work also supports Brunson's value-ladder perspective. These are educational applications, not independently verified quotations, endorsements or results.
Examine the cost claims before using them
The source lists six possible business effects of unsuitable fit. Preserve the categories, but do not use their numeric multipliers as measured forecasts.
Cost Category
What Happens
Typical Multiplier on Sale Value
Support drain
Wrong-fit buyers generate 4–8x more support tickets than right-fit buyers. Each ticket costs staff time, founder attention, and response latency for other buyers.
2–3x lost sale value in staff and opportunity cost
Completion rate damage
Low completion by wrong-fit buyers drags down your aggregate completion statistics — the primary social proof metric for course and programme offers.
Reduces testimonial yield by 20–40% of what it would be with a clean avatar cohort
Review and reputation risk
Wrong-fit buyers who do not get results leave reviews citing their outcome without disclosing they were not the intended buyer. These reviews damage cold traffic conversion rates.
One 1-star review offsets approximately 12 positive reviews in aggregate rating
Community contamination
Wrong-fit buyers lower engagement quality, ask off-topic questions, and create support burden for community managers that degrades the experience for right-fit buyers.
Accelerates right-fit member churn by 15–30% in communities where wrong-fit buyers are visible
Refund processing cost
Direct refund processing: payment processor fees, staff time, and the loss of the original transaction cost (ad spend to acquire that buyer).
1.2–1.5x the original sale value when processing costs are included
Ascension revenue lost
A right-fit buyer has a 15–25% chance of ascending to the next tier. A wrong-fit buyer has near-zero chance and actively reduces the ascension rate of surrounding buyers by lowering community energy.
5–10x the original sale value in lifetime value delta vs a right-fit buyer
Support time, refund costs, completion, reviews, community experience and foregone future revenue can matter. Measure actual costs and avoid double-counting overlapping effects. The source's $297 sale becoming $900–$1,500 in impact is an illustrative assertion. It provides no calculation establishing those costs for your business.
The 4–8x ticket rate, 20–40% testimonial loss, 15–30% churn effect, 15–25% ascension chance and other listed ratios are unsupported here. One negative review has no universal twelve-positive-review offset. Aggregate ratings depend on the actual counts and scores. The claimed tenfold value of preventing a mismatch is not a measured return.
Learn the five archetypes as hypotheses
For each table, study the description, signals, cost and proposed lesson. Keep the source wording visible while using neutral descriptions in actual customer records. The five types do not exhaust every reason a learner may struggle.
A01 — The buyer needs a different problem solved
ARCHETYPE 01 The Wrong-Problem Buyer Bought the category. Needed a different product.
Who they are This person has a real problem and real intent. They found your offer through search or ad targeting, recognised the category as relevant, and purchased based on surface-level alignment. But their specific problem is not what your offer solves. They thought 'lead generation' meant one thing; you solve a specific flavour of it for a specific avatar. They bought the genre, not the transformation.
How to spot them Confused support tickets within 72 hours of purchase. Questions about topics your offer does not cover. Requests for refunds citing 'this isn't what I expected' without citing specific content failures. Onboarding survey answers that do not match your target avatar profile.
What they cost you High support ticket volume. High early refund rate (days 1–7). Low module engagement because the content does not address their actual problem. Neutral-to-negative reviews citing 'not relevant to my situation.'
What they teach you Your sales page or ad copy is using language that attracts a broader category than your specific offer serves. The wrong-problem buyer shows you exactly where your positioning is too wide. Their exact words in the refund message reveal which phrase in your copy created the misalignment.
Compare the specific question with the actual scope and sales language. A broad category such as lead generation may conceal different needs. Early confusion, a refund or an off-topic question suggests investigation; it does not prove the copy caused the purchase. Ask which promise shaped the expectation.
A02 — Participation has stopped
ARCHETYPE 02 The Passive Consumer Paid for permission to not implement.
Who they are This person purchases with genuine optimism. They intend to implement. But their purchase is partly driven by the belief that buying = progress. They download every lead magnet, buy every relevant course, and rarely finish any of them. They are not lazy — they are overwhelmed, under-accountable, or purchasing as a substitute for the discomfort of implementation. The offer is high quality. The buyer's operating system is the problem.
How to spot them Purchases from your email list or retargeting (not cold) — they know you and have likely bought from adjacent offers before. High open rates on emails but low click-to-action rates. Module 1 completion but rapid dropoff after the first action item requires real work. No support tickets. Silent dropout.
What they cost you Drags down completion statistics without generating feedback data. Rarely refunds — disappears instead. Does not produce testimonials. Occupies community space without contributing. Difficult to diagnose because they do not complain.
What they teach you Your onboarding sequence does not create enough implementation accountability in the first 72 hours. The passive consumer reveals that your Quick Win (the first action with a visible result) is either absent or too easy to skip. They also reveal whether your community has an accountability culture or a consumption culture.
Silence, opening emails without acting or stopping after an assignment can reflect many causes. Do not assume purchase was a substitute for action or that the offer is already high quality. Check access, clarity, available time and the first useful task. The source proposes accountability and a visible win within 72 hours; those are design ideas, not a diagnosis or guaranteed result.
A03 — The offer assumes a different stage
ARCHETYPE 03 The Mismatched-Stage Buyer Right person. Wrong moment in their journey.
Who they are This buyer is legitimately your target avatar — same industry, same problem category, same goals. But they are either six months too early (they lack the prerequisites your offer assumes) or eighteen months too late (they have already solved the problem your offer addresses and need something more advanced). Neither version is the wrong person. Both are the wrong timing.
How to spot them Too-early: Onboarding survey answers reveal missing prerequisites. Support tickets asking foundational questions your modules assume they already know. Frustration expressed as 'I'm lost' rather than 'this is wrong.' Too-late: Completion without results — because they already know the material. Exit interviews citing 'I was hoping for more advanced content.' Requests for refunds citing 'I've already done all of this.'
What they cost you Too-early buyers have very high support costs and low completion rates. Too-late buyers have low support costs but produce weak testimonials ('good review of fundamentals') that do not match your promise and reduce conversion credibility.
What they teach you The too-early buyer reveals that your sales page lacks a 'You need X before this will work' prerequisite statement. The too-late buyer reveals that there is an unserved advanced segment who needs a higher-tier offer you have not yet built. Both archetypes define the exact edges of your value ladder.
Separate missing prerequisites from needs that are more advanced than the offer. The source's six-months-early and eighteen-months-late descriptions are illustrations. State the actual prerequisite or next capability instead of assigning a calendar label. Earlier and later needs can inform distinct resources or tiers, after demand is checked.
A04 — Support needs and promised access differ
ARCHETYPE 04 The Vampire Client Extracts maximum support. Pays minimum price.
Who they are This person genuinely wants results — but their expectation of the support, access, and attention they are entitled to dramatically exceeds what was sold to them. They are not trying to exploit the system consciously. They believe their level of need is normal and reasonable. They book every available call slot, send multiple emails per week, ask questions in every community thread, and escalate immediately when they feel under-served. Their disproportionate resource consumption makes the economics of every cohort they join unworkable.
How to spot them Multiple support tickets per week from day one. Attempts to upgrade support access beyond what was purchased ('Can I just send you this quickly?'). Escalation when response time exceeds 24 hours. Requests for 1:1 attention within a group programme. Frustration about lack of personalisation in group calls.
What they cost you This archetype creates the highest per-buyer operational cost in the entire customer base. In a cohort of 20, one Vampire Client can consume 40% of all support bandwidth and undermine the experience for 19 other paying buyers. At scale, they make high-touch delivery economically unviable.
What they teach you This archetype reveals a gap in your onboarding expectations. Somewhere in your marketing — likely in the sales copy's language around access, support, or personalisation — a promise is being read as more expansive than you intended. They also reveal that a more expensive done-for-you or 1:1 tier is in genuine demand and not yet priced accordingly.
The source calls this a Vampire Client. That label is retained for source identification, not recommended as a customer-facing description. Frequent questions may reveal unclear instructions, access needs or a promise of more support than delivery provides. The claim that one buyer consumes forty percent of a twenty-person cohort's support is unverified here. Measure the load and clarify what was sold before proposing a higher-access offer.
A05 — Suspected misuse requires evidence
ARCHETYPE 05 The Guarantee Exploiter Purchased with the intent to consume and refund.
Who they are This is the rarest archetype and the only one that represents deliberate misuse rather than a mismatch. This buyer researches the guarantee before purchasing, consumes the entire programme at maximum speed, and submits a refund request citing the guarantee language before the window closes. They are not confused about fit. They have identified your guarantee as a mechanism for free content access.
How to spot them Purchases at the latest possible point in a launch window (maximising consumption time before the guarantee expires). Completes 100% of programme content within days of purchase. Refund request arrives on day 29 or 30 of a 30-day guarantee citing compliance with every stated condition. Often uses Gmail aliases or has purchased-and-refunded from similar creators before.
What they cost you Direct financial loss equivalent to 1.5x the sale price (including processing costs). No data loss — they complete everything and give you nothing useful. If they leave a review, it is often falsely positive to avoid detection.
What they teach you This archetype reveals that your guarantee language is too unconditional or that you lack a completion-based gate. Conditional guarantees — 'If you complete all modules, submit all assignments, and do not see [specific result]' — dramatically reduce exploitation while maintaining credibility with genuine buyers. The Guarantee Exploiter teaches you exactly which condition to add.
Finishing quickly, asking about a guarantee, using an email alias or requesting a refund near its deadline does not establish dishonest intent. A guarantee may expressly permit that refund. Buying late in a launch also does not inherently lengthen a purchase-relative refund period. Preserve facts and actual terms; do not automatically blacklist or deny a request.
The source claims conditional guarantees reduce misuse and improve credibility. It supplies no evidence for the magnitude or universality of that effect. Any future guarantee must be feasible and clearly disclosed. This lesson changes no existing buyer terms.
Phase 1 — Collect signals from eight sources
Use each source for its stated evidence and cadence. A flag starts a review; it is not a verdict. Preserve the full message with its context rather than paraphrasing away relevant detail.
Source
What to Mine
Archetype It Most Commonly Reveals
Collection Method
Refund request messages
Verbatim language describing why the offer failed to meet expectations. The most direct source of wrong-fit evidence.
Archetype 01 (Wrong-Problem) and Archetype 03 (Mismatched Stage)
Log verbatim in Airtable within 24 hours. Tag with archetype code. Never paraphrase.
Support ticket patterns
Volume, topic clusters, and emotional tone of all support tickets per buyer. Disproportionate volume from a single buyer is the primary Vampire Client signal.
Archetype 04 (Vampire Client) and Archetype 01 (Wrong-Problem)
Weekly tag audit in Intercom or Help Scout. Flag any buyer with 5+ tickets in 14 days.
Sales call recordings
Objections that were overcome but probably should not have been. The buyer who bought despite a red-flag objection is a Negative Avatar in waiting.
Archetype 01, 03, and early Archetype 02 signals
Review 100% of sales call recordings for buyers who later refund. Tag the objection that preceded the sale.
Application form responses
Answers that reveal mismatched stage, wrong problem, or unrealistic expectations before purchase. The pre-purchase filter.
Archetype 03 (Mismatched Stage) primary detection point
Weekly review of all application submissions. Score against the Qualification Rubric (see Phase 3).
Onboarding survey responses
Baseline situation statements that reveal who actually bought vs. who you thought was buying. Compare baseline to your intended avatar profile.
Archetype 01 and Archetype 03
Flag responses where the situation described does not match your positive avatar profile. Review within 48 hours of submission.
Community engagement patterns
Dropout (Archetype 02), conflict escalation (Archetype 04), and topic mismatch (Archetype 01) all manifest in community behaviour before they appear in support tickets.
Archetype 02 (Passive Consumer) and Archetype 04 (Vampire Client)
Weekly community audit: flag accounts with zero posts after 14 days (dropout signal) and accounts with 3+ conflict interactions.
Exit interview transcripts
The most information-rich single source. Buyers who did not get results will describe exactly why — often identifying the mismatch themselves if asked the right questions.
All five archetypes
Castmagic transcript. Highlight every sentence describing what they expected vs. what they found.
Stripe/payment refund history
Pattern detection across multiple buyers. Time-to-refund, purchase day within launch window, and refund reason clustering reveal the Guarantee Exploiter pattern.
Archetype 05 (Guarantee Exploiter)
Monthly refund report. Flag any account with purchase in last 3 days of launch + refund in last 2 days of guarantee window.
The key windows differ: refund logging within 24 hours; support five or more tickets in fourteen days; onboarding review within 48 hours; community review at fourteen days; and monthly payment-pattern review. The source also asks for all relevant refunded-buyer sales calls and weekly applications. Recording, customer data and platform access require the actual permission and configuration. No collection or upload happens here.
Phase 2 — Build an evidence-linked profile
The source creates a profile after three same-offer instances within sixty days. It calls one event noise and two coincidence; do not apply those phrases literally. A single known delivery problem can need help now. Three observations do not prove a common cause. Keep event-level records while testing the pattern.
Complete every field below. The example name and date are illustrative, not an actual RISER customer or incident.
Profile Field
What to Document
Example
Profile ID
Autonumber + offer abbreviation + archetype code
MVO-01-A01 (first Wrong-Problem profile for MVO-01)
Archetype code
01–05 from the five archetypes above
A01 — Wrong-Problem Buyer
Character name
Give this profile a memorable name for internal reference. The name should capture the essence of the mismatch.
'The Adjacent Niche Buyer' or 'The One-Step-Earlier Operator'
Date pattern detected
Date the third instance was logged, triggering profile creation
2026-03-15
Number of instances (at creation)
Count of buyers matching this pattern within the detection window
3 refunds within 47 days
Verbatim trigger phrase
The exact phrase — 3 to 8 words — that appears in the refund or dropout data most consistently for this profile. This is the primary copy signal.
'Not what I was looking for' / 'Thought this covered X'
Entry point
Which ad, email, or content piece most commonly preceded the wrong-fit purchase. The copy that attracted the wrong buyer.
Meta ad targeting 'course creators' — too broad; includes creators whose core problem is not offer construction
The mismatch anatomy
In one sentence: why this buyer and this offer are a mismatch. Not their fault. Not the offer's fault. A structural incompatibility.
This buyer needs audience building before they need offer construction. They have no list to sell to and the offer assumes one exists.
What they actually need
The offer that would have served them correctly — whether you have built it yet or not.
A traffic and list-building offer — currently Tier 0/1 in the value ladder. Not yet built.
Sales page anti-language
Words or phrases currently on the sales page that are attracting this profile. These must be audited and potentially removed or reframed.
'Course creators' in ad copy — replaced with 'course creators with an existing audience above 1,000 subscribers'
'Not for you if' addition
The specific bullet point to add to the 'This is NOT for you' section of the sales page as a direct result of this profile.
This is NOT for you if you are still building your first audience and have not yet had any paying customers.
Targeting exclusion
The specific ad audience characteristic to exclude, or the application form question to add, that would have screened this buyer before purchase.
Exclude interest targeting: 'content creation' and 'blogging'. Add application question: 'How many paying customers have you had in the last 90 days?'
Status
Open (pattern continuing) / Remediated (fix deployed) / Closed (no new instances in 90 days)
Open
The profile connects the triggering words and acquisition path to a proposed explanation and change. Write the need the offer failed to serve, the wording to review, the fit statement and the possible screening change. Preserve uncertainty and alternative causes.
Open means the source considers the pattern ongoing. Remediated means a fix was deployed. Closed requires no new instances for ninety days. No observed instances may reflect missing data or no relevant sales, so record exposure and capture quality before interpreting closure as success.
Phase 3 — Classify and qualify consistently
The source proposes a weekly 20–30-minute review. Read all five steps and distinguish the fourteen-day support lookback from the past-week collection window.
Complete source procedure for study:
Pull all new refund messages from Airtable Refund Records. Read each verbatim. Assign archetype code. Look for phrase overlap with existing profiles.
Pull all support tickets flagged in the past 7 days. Count tickets per buyer. Flag any buyer with 5+ tickets in 14 days for Archetype 04 review.
Scan community for zero-engagement accounts (no posts or comments in 14+ days after an initial welcome post). Add to Archetype 02 passive tracker.
Review any sales call recordings from buyers who refunded in the past 7 days. Tag the objection that preceded the sale.
Check pattern counts on all Open profiles. If any profile hits 3 new instances this week: trigger the Remediation Protocol (Phase 5).
Three new instances this week is a different rule from three within sixty days. The instruction points to a Remediation Protocol in Phase 5, but that phase contains Positive Extraction rather than a complete named remediation workflow. Preserve that missing procedure.
For offers above $497, the source proposes five application dimensions. Score the actual answer against all three levels, retaining the question and evidence.
Qualification Dimension
Screening Question
Green Flag (Score 2)
Amber Flag (Score 1)
Red Flag (Score 0)
Problem specificity
Describe the specific problem you are trying to solve in one sentence.
Describes a specific, narrow problem that your offer directly solves
Describes a broad category that your offer partially addresses
Describes a problem your offer does not solve or a different problem category entirely
Stage readiness
What have you already tried to solve this? What happened?
Has tried and exhausted alternatives. Has skin in the game. Has some prior result.
Has researched but not yet implemented anything. No prior attempt.
Has not identified the problem as actionable yet. Describes a future state not a current problem.
Implementation capacity
How much time per week can you dedicate to this work for the next 60 days?
States a specific number of hours above your minimum threshold
States a number at or slightly below threshold but with a credible explanation
States a number that makes completion of your programme impossible, or gives a non-answer
Financial alignment
Are you aware this is a [price] investment and are you in a position to make that decision today?
Yes, directly and without hesitation
Yes, but with a question about payment plans — not a concern, a logistics question
Dodges the question, asks about refund policy before asking about the programme, or indicates the price is a stretch
Outcome specificity
What does success look like to you 90 days from now?
States a specific, measurable outcome that your offer can credibly deliver
States a directional outcome without specific metrics — achievable but vague
States an outcome your offer cannot deliver in the timeframe or describes a transformation your offer does not produce
The source scores ten as ideal, seven to nine as qualified with follow-up, four to six as a redirect and below four as a respectful decline with a relevant resource. These are source rules, not an automatic eligibility system. A total of eight can still contain a zero on a critical prerequisite. Review each dimension as well as the total.
Payment plans or questions about refund terms do not establish poor intent. Explain the actual costs, workload and fit without pressuring a purchase. If the alternative resource is unavailable, record that gap rather than inventing a destination.
Study all five sales-call signals and responses. They cover prerequisites, support access, refund terms, prior implementation and the difference between clear guidance and done-for-you help.
Red Flag Signal
What It Reveals
Correct Response on Call
'Will this work even if I don't have [prerequisite your offer assumes]?'
Mismatched Stage — Archetype 03 Too Early. They lack something fundamental your offer is built upon.
'I want to be honest with you — this offer is designed for people who already have [prerequisite]. Without that, you won't get the result we promise. Here's what I'd recommend first...'
'What happens if I need more support than what's included?'
Early Vampire Client signal — Archetype 04. Testing boundaries before purchasing.
Describe the support structure clearly and specifically. Ask: 'Does that feel like enough for you?' If hesitation: 'Our 1:1 programme might be a better fit — let me describe that option.'
'Can you show me the refund policy again?'
Either Guarantee Exploiter (Archetype 05) or a buyer with genuine uncertainty. Distinguish by context.
If asked as the first or second question: proceed with caution. Describe the conditional guarantee clearly and state what completion requires. If they lead with refund questions on a call, they are not ready to commit.
'I've bought a few courses on this topic but haven't implemented any of them.'
Strong Passive Consumer signal — Archetype 02. Purchases are a substitute for implementation for this buyer.
'I appreciate your honesty. Before I'd feel good about taking your money, I'd like to understand what stopped you from implementing the others. Because this programme requires [specific action] in week one.' Only proceed if they give a credible, non-pattern answer.
'I just need someone to tell me what to do.'
Can be either the right buyer (Executive Buyer who wants clear direction) or the Passive Consumer variant who expects the programme to create action on their behalf. Probe further.
'Tell me what that looks like for you — when you say someone tells you what to do, do you mean a clear step-by-step system, or do you mean you need someone to do the work with you?' The answer reveals whether they need your offer or a done-for-you service.
A support question can be a reasonable effort to understand the offer. A refund question can reflect uncertainty after a previous bad experience. Ask about the need rather than selling through it or labelling it dishonest. The later filtering layer declines after two flags, while this section suggests individual mismatches can matter. The source does not define a universal priority rule.
Phase 4 — Make fit clear before purchase
The source calls its five layers a Repulsion System. Its useful purpose is accurate scope and appropriate routing. Study each layer, location, targeted mismatch and mechanism.
Layer
Where It Lives
Primary Archetype Caught
Mechanism
Layer 1 — Ad targeting exclusion
Paid ad campaign settings
Archetype 01 (Wrong-Problem)
Exclude specific interest categories, job titles, and lookalike audiences that have produced wrong-fit buyers. Add negative keywords to Google and YouTube campaigns.
Layer 2 — Sales page 'Not for you' section
Below the offer stack, above the guarantee
Archetypes 01, 02, and 03
A specific list of 4–6 statements beginning with 'This is NOT for you if...' Each bullet maps directly to an active Negative Avatar Profile.
Layer 3 — Anti-language audit
All copy across sales page, email sequence, and ads
Archetype 01 (Wrong-Problem) primary
Remove or reframe any word or phrase in active Negative Avatar Profile anti-language fields. These words are attracting the wrong buyer by signalling a broader category than you serve.
Layer 4 — Application form qualification
Offer pages above $497 and all high-ticket tiers
Archetypes 03 and 04
The Qualification Rubric from Phase 3. Any application scoring below 7 is redirected before any human time is invested.
Layer 5 — Sales call screening
Discovery and strategy calls
Archetypes 03, 04, and 05
The Red Flag Protocol from Phase 3. Any call that produces two or more red flags is declined with a specific redirection.
A fit section has four to six plain-language bullets. Each should connect to actual evidence, name a condition rather than an insult, and end with a real alternative when one exists. Do not invent four patterns just to meet the count. If many profiles exist, the six-bullet ceiling and requirement to represent them all need an explicit editorial choice.
The complete sample below is source material. Its hours, revenue, history and timeline are example conditions. Its Tracks 1–3 bundle is unverified and does not replace the twelve-course spreadsheet.
Complete source procedure for study:
This is NOT for you if...
• You are still building your first audience and have not yet had a paying customer — this offer assumes you have proof that someone will pay you for something.
• You are looking for someone to do the work for you — this is a hands-on implementation programme that requires 4–6 hours per week of your personal effort.
• You have already built and launched a core offer generating above $10K/month — the methods here are designed for the $0–$10K validation stage, not the scaling stage.
• You are in a rush to launch in the next 7 days — the framework takes 30 days to implement correctly and shortcuts produce bad data.
• You have purchased more than two similar programmes in the last 12 months without implementing them — this will produce the same result unless something in your circumstances has fundamentally changed.
If any of the above describes your situation, the RISER Nation Tracks 1–3 Foundation bundle is likely a better starting point.
Audit wording that attracts a broader problem or stage than the offer serves. The source calls for a quarterly review and an immediate review after a new profile; later it also specifies a monthly pass. Keep those cadences distinct rather than silently discarding one.
Complete source procedure for study:
Pull the 'Sales page anti-language' field from every Open Negative Avatar Profile in Airtable.
Run a Find & Replace search for each phrase across: sales page, all active email sequences, all live ad creatives, and all landing pages.
For each instance found: decide whether to remove the phrase entirely or reframe it with a specific qualifier.
Document every change in Airtable under the relevant Negative Avatar Profile record — date, what changed, where.
Schedule a conversion rate comparison 30 days after each anti-language audit. The repulsion change should not reduce overall conversion meaningfully if it is filtering the right buyers.
The source says conversion should not fall meaningfully, then predicts a five-to-fifteen-percent drop and higher net revenue in thirty days. Those are conflicting, unsupported expectations. Measure actual buyer fit, revenue, refunds and costs across comparable cohorts. A before-and-after change does not prove the edit caused the difference. Preserve every version and observation.
Phase 5 — Use the findings to improve delivery and future offers
Each row separates a defensive change from a possible product insight. A03 is split into earlier and later stages, producing six rows. Read all actions and their evidence requirements.
Archetype
The Defensive Use (Repulsion)
The Offensive Use (Product Intelligence)
Specific Action Triggered
A01 — Wrong-Problem Buyer
Remove copy that attracts the wrong category. Tighten ad targeting.
Reveals demand for an adjacent offer that solves their actual problem. If three or more Wrong-Problem buyers share the same alternative need, that need is your next product signal.
Open a 'Problem B' card in the Product Roadmap for the problem this archetype actually needed solved.
A02 — Passive Consumer
Add completion accountability to onboarding. Create a stronger Quick Win in module 1.
Reveals that your onboarding does not create enough urgency or identity shift at purchase. The best fix is not more content — it is a better Day 1 experience that makes implementation feel inevitable.
Rebuild the welcome sequence with a 72-hour implementation challenge. 'Your first result in 72 hours or tell me what stopped you.'
A03 Too Early — Mismatched Stage
Add prerequisite language to sales page. Add stage-qualification question to application form.
Reveals an unserved earlier-stage market. If there are consistently buyers who are 6 months too early for your current offer, the gap between 'zero' and your MVO is a product waiting to be built.
Create a 'Prerequisites Offer' — the entry-level product that gets them to the starting line of your MVO.
A03 Too Late — Mismatched Stage
Add 'Not for you if you already have X' to sales page.
Reveals that there is a more advanced buyer segment who needs your next-level offer. This is your clearest signal that Tier 4 (High-Ticket) or an advanced Core Offer variant should be prioritised.
Open a 'Advanced Buyer' product brief. Run 5 exit interviews with Too-Late buyers asking: 'What would you have needed instead?'
A04 — Vampire Client
Add support structure clarity to sales page. Price the 1:1 tier correctly.
Reveals unmet demand for higher-access tiers that are not correctly priced or positioned. Vampire Clients are often willing to pay significantly more for appropriate access — they just could not find it in your offer wall.
Audit your high-ticket and DFY tiers. The Vampire Client is the right-fit buyer for a tier you have not yet built or priced correctly.
A05 — Guarantee Exploiter
Add conditional language to guarantee. Add completion requirements.
Reveals that your guarantee language lacks the specificity needed to distinguish genuine-effort buyers from exploiters. The conditional rewrite that stops exploiters also increases perceived credibility with genuine buyers — because specific conditions imply a confident offer.
Rewrite guarantee from unconditional to conditional. State the exact completion requirements needed to qualify for a refund.
Three similar adjacent needs can prompt investigation of a Problem B offer. The quarterly checklist later uses five instances for product priority and supplies no window. Record both rules. Neither count proves a viable market.
The source proposes a 72-hour implementation challenge, an earlier prerequisite offer, five advanced-buyer interviews and an audit of higher-access tiers. These are hypotheses to test. A person seeking more support may not want or be able to buy an expensive tier. A named need is not an order for a new product.
Phase 6 — Design the offer with its prerequisites visible
Before writing a new offer, identify likely fit risks as hypotheses alongside the intended buyer. The opening asks for three likely archetypes, but the table and checklist specify two. Do not call hypothetical risks confirmed buyer patterns.
Brief Element
What to Define
Example (for an offer on organic content strategy)
Most likely wrong-fit archetype 1
Which archetype will this offer category most commonly attract by mistake, and why?
A01 — Wrong-Problem: People who need paid ads, not organic content. Attracted by 'get more clients' language that applies to both channels.
Most likely wrong-fit archetype 2
Second most likely archetype and its attraction mechanism.
A03 Too Early: People with no existing content platform or audience. Attracted by 'start from scratch' language that implies zero prerequisites.
Prerequisites to state explicitly
What must a buyer already have for this offer to work as promised?
A social media profile with at least 6 months of consistent posting history and at least 200 followers. Some prior experience with content creation.
Support capacity design
Based on expected archetype mix, how many support interactions per buyer per week is your delivery model designed for?
Maximum 2 support tickets per week per buyer. Vampire Client protocol triggers at 5+ tickets in any 14-day window.
Guarantee design
Given the most likely archetype mix, what guarantee language protects against exploitation while remaining credible?
Conditional: 'If you post the required 3x per week for 30 days and do not see at least 15% growth in profile engagement, we will refund in full.'
'Not for you' bullets (draft)
Write 4 'Not for you' bullets directly from the identified archetypes before launch.
1. If you have not posted consistently for at least 3 months. 2. If your primary acquisition channel is or needs to be paid ads. 3. If you are not prepared to post 3 times per week during the programme. 4. If you are looking for growth shortcuts — every strategy here takes 30+ days to produce data.
The example requires six months of posting, then its sample fit bullet says three months. Clarify the real prerequisite before using either. The support example budgets two tickets per week and flags five in fourteen days; a budget and review trigger have different roles. The fifteen-percent engagement result is an illustrative guarantee, not a demonstrated outcome.
Use the four delivery-design rows to plan the first task, readiness check, support description and completion evidence.
Archetype Risk
Delivery Design Decision
Implementation
A02 Passive Consumer risk is high
Build accountability into the first 72 hours, not as a feature — as a requirement. The first action item must be completable in under 20 minutes and must produce a visible output.
Module 1 ends with: 'Post your output in the community with the tag #Week1Win. You have 72 hours.' Community manager checks and personally tags any non-posters at hour 48.
A03 Too Early risk is high
Add a pre-programme self-assessment that evaluates prerequisite completion. Make it ungated but visible — buyers should encounter it before purchase and ideally before opting into the lead magnet.
Landing page addition: '2-minute readiness check' that scores their current situation against 5 prerequisites. Shows them their readiness score and tells them what to do if below threshold.
A04 Vampire Client risk is high
Define support access with extreme specificity in the sales copy and onboarding materials. The access ambiguity that creates Vampire Clients must be removed before purchase.
Onboarding email paragraph 3: 'Here is exactly what support looks like in this programme: [specific hours, specific response time, specific channels, specific escalation path]. This is intentionally bounded — it is what allows us to deliver quality to every member equally.'
A05 Guarantee Exploiter risk is high
Design completion checkpoints that are simple to complete for genuine buyers and inconvenient to game for exploiters.
Completion requirements for guarantee eligibility: submit module completion confirmations through the platform (timestamped), post in community at milestone points (timestamped and public), complete the exit survey. These are trivial for genuine buyers and require meaningful effort to fake.
A visible task under twenty minutes and a 72-hour deadline can make the next step clear, but the task must fit the learner. The source's 48-hour personal tagging is a proposed workflow, not a current service commitment. Public posts are not the only possible evidence of learning.
The two-minute readiness check references five prerequisites and a threshold without defining them. Do not invent a functioning assessment from that description. State actual support hours, response time, channels and escalation route. Completion checkpoints must fit the real offer terms and access needs; asking for privacy is not evidence of misuse.
Phase 7 — Review targeting proposals before implementation
The source lists five platform or audience mechanisms. Preserve its instructions as source material. Interfaces, targeting options, list requirements and permitted uses need current official verification before implementation; this lesson executes none of them.
Platform
Exclusion Mechanism
Negative Avatar Application
How to Implement
Meta Ads
Custom audiences (upload buyer list), interest exclusions, and lookalike exclusion
Upload all refund records as a suppression list to prevent re-acquisition. Exclude interest categories identified in A01 profiles. Create a 'bad buyer lookalike' from refund list to identify and exclude similar profiles.
Ads Manager → Audiences → Custom Audience → Customer list. Upload email list of all buyers who refunded with RC-1 or RC-3 codes. Create 1% lookalike to exclude.
Google / YouTube Ads
Negative keyword lists and audience exclusions
Add negative keywords from A01 anti-language audit. These are the search terms that attract wrong-problem buyers.
Google Ads → Shared Library → Negative keyword lists. Create 'Wrong Avatar' list from all anti-language phrases identified in active profiles.
TikTok Ads
Custom audience exclusion and interest negative targeting
Upload refund list as suppression. Exclude content creator interests if A01 data shows content creators are a mismatch.
TikTok Ads Manager → Audience → Custom Audience → Customer file. Upload and set as exclusion.
LinkedIn Ads
Job title exclusions and company size exclusions
If A03 (Too Early) buyers consistently come from companies below a certain size or from specific job titles, exclude these in targeting.
Campaign Manager → Audience → Exclusions → Job Titles. Build the exclusion list from A03 profile entry point data.
Retargeting audiences
Event-based exclusions
Exclude page visitors who spent less than 90 seconds on the sales page (bounce behaviour associated with wrong-fit visitors who did not engage with the 'Not for you' section).
GA4 → Audience → Create audience based on time on page event. Exclude from retargeting in all platforms.
Refunds do not automatically justify suppression or similarity modelling. RC-1 and RC-3 are refund cause codes from the related audit; they are not interchangeable with A01 and A03 archetypes. Short page visits also do not establish wrong fit. The proposed ninety-second GA4 rule needs an actual defined event and supported integration.
Review all four monthly steps below as the source's proposal. Any real customer-list transfer, campaign change or spending decision requires the appropriate authority and platform suitability.
Complete source procedure for study:
Pull all refund records from the past 30 days. Upload any new email addresses to suppression lists on all active ad platforms.
Review all new Negative Avatar Profiles created in the past 30 days. Extract any new anti-language phrases. Add to negative keyword lists.
Review the entry point field in all Open profiles. If a specific ad, audience, or campaign is consistently producing wrong-fit buyers, pause that ad or refine that audience.
Check Cost Per Acquisition (CPA) comparison: buyers acquired from excluded audiences (before exclusion was added) vs. buyers acquired after exclusion. Document the delta.
The CPA comparison before and after exclusion can be influenced by budget, traffic, seasonality and other edits. Record those limits. An exclusion should not be described as a measured improvement until comparable evidence supports that conclusion.
Phase 8 — Keep the evidence and review calendar connected
Use all six cadence rows with their outputs. Durations are source planning estimates, not measured effort.
Frequency
Activity
Time Required
Output
Daily (ongoing)
Process any new refund request through the 5-step Refund Forensics Protocol from the Post-MVO Forensic Audit Loop SOP. Archive verbatim. Assign archetype code.
5–10 min per refund
Refund archive entry. Pattern count updated.
Weekly (Mondays — 20 min)
Run weekly classification ritual: review all new support tickets, refunds, and community signals. Update pattern counts on Open profiles. Check for any profile crossing 3-instance threshold.
20 minutes
Pattern counts updated. New profiles created if threshold crossed.
Weekly (Thursdays — 15 min)
Review all new application form submissions against the Qualification Rubric. Score and route: approve, follow-up question, redirect, or decline.
15 minutes
Application decisions documented. Any new A03 or A04 signals noted.
Monthly (first Monday)
Full Negative Avatar database review. Close any profiles with zero new instances in 90 days. Check all Open profiles for remediation effectiveness. Run anti-language audit against all active copy.
60–90 minutes
Database cleaned. Remediated profiles moved to Closed. Anti-language copy updates queued.
Quarterly
Full repulsion system audit: review 'Not for you' section against active profiles, re-run Qualification Rubric calibration, review all ad exclusion audiences, check CPA delta since last exclusion update.
Half day
Repulsion System Update Report. Action brief for copy and targeting changes.
After every new offer launch
Complete a Negative Avatar Brief before the first sale. Update as first buyers are acquired. Create profiles at 3-instance threshold — which may arrive faster for new offers.
2 hours pre-launch + ongoing
Pre-launch Negative Avatar Brief filed in Airtable. First profiles created within 30 days of launch.
The row labelled after a new launch requires a brief before the first sale. Place that preparation first. A new profile within thirty days is not assured when profile creation depends on three instances. The daily refund activity refers to the Post-MVO five-step protocol, which should remain linked rather than replaced by a label.
Define the records without pretending a database is deployed
The source describes four linked tables. Three have full schemas below. Refund Records is inherited from the Post-MVO audit, with a profile relationship added. The additional Offers table is also required but not defined here.
Negative Avatar Profiles
Field
Type
Notes
Profile ID
Autonumber
Auto-generated. Format: [Offer]-[Seq]-A0[1-5]
Character name
Short text
Internal reference name — descriptive, memorable
Archetype code
Single select
A01 through A05
Offer
Link → Offers table
Which offer this profile relates to
Date created
Date
Date the 3rd instance was logged
Instance count
Number
Updated weekly — total instances logged
Verbatim trigger phrase
Long text
Most consistent 3–8 word phrase from the data
Entry point
Long text
Ad, email, or content piece most commonly preceding purchase
Mismatch anatomy
Long text
One-sentence structural description of why buyer and offer are misaligned
What they actually need
Long text
The offer that would have served them correctly
Sales page anti-language
Long text
Specific phrases to audit and remove or reframe
Not for you addition
Long text
The exact bullet to add to the 'Not for you' section
Ad targeting exclusion
Long text
Specific audience or keyword exclusion to implement
Application form change
Long text
Question to add or threshold to adjust on application form
Remediation date
Date
Date the fix was deployed across all affected assets
Status
Single select
Open / Remediated / Closed
Linked refund records
Link → Refund Records
All refunds that contributed to this profile
Preserve all seventeen fields. A plain autonumber does not produce the composite Offer–Sequence–Archetype identifier described in the notes. An implementation needs a separate display formula or another explicit design. A lookup field in the setup checklist does not itself create the linked-record relationship described in the schema.
Application Scoring Log
Field
Type
Notes
Application ID
Autonumber
Date submitted
Date
Offer applied for
Link → Offers table
Rubric score
Number
0–10 from the Qualification Rubric
Dimension scores
Long text
Individual scores for each of the 5 rubric dimensions
If redirected — which offer or resource were they directed to
Negative Avatar signals
Link → Profiles
If any archetype signals identified — link to relevant profile
The eight fields retain the offer, total and dimension scores, decision, redirect and linked signals. Keep the original answer available through an appropriate record relationship; the schema does not supply a complete capture or review automation.
Repulsion System Changelog
Field
Type
Notes
Change ID
Autonumber
Date deployed
Date
Triggered by
Link → Profiles
Which Negative Avatar Profile triggered this change
Asset changed
Single select
Sales page / Email sequence / Ad copy / Application form / Onboarding / Delivery design / Ad targeting
What was changed
Long text
Specific before and after — verbatim if copy, audience description if targeting
Conversion rate before
Number
Record the relevant metric before the change
Conversion rate after (30 days)
Number
Filled in 30 days after deployment
Net revenue impact
Number
Gross conversion delta adjusted for refund rate change
These eight fields record what changed and later observations. The source defines net revenue impact as a conversion delta adjusted for refund rate. That is not a complete currency formula. Actual revenue, price, volumes, refunds, costs and comparison windows need definitions. No working Airtable base or formula is supplied.
Complete the operating checklist with evidence
The setup, prelaunch, weekly, monthly and quarterly lists each contain distinct requirements. Read all of them. Mark an item done only when the associated artifact or action actually exists.
Complete source procedure for study:
Master Negative Avatar Modelling Checklist
System Setup (One-Time)
☐ Create Negative Avatar Profiles table in Airtable with all fields from the schema above
☐ Create Application Scoring Log table and link to Offers table
☐ Create Repulsion System Changelog table
☐ Link all existing Refund Records to new profiles table via lookup field
☐ Run anti-language audit on all current live sales pages — flag any words matching existing buyer complaints
☐ Add 'This is NOT for you' section to all active offer sales pages using real buyer language
☐ Set up Meta, Google, TikTok suppression audiences — upload current refund email list
Every New Offer (Pre-Launch)
☐ Complete Negative Avatar Brief: identify 2 most likely archetypes before first sale
☐ Write 4 'Not for you' bullets based on pre-identified archetypes
☐ Design conditional guarantee language that specifies completion requirements
☐ Build application form with Qualification Rubric questions for offers above $497
☐ Onboarding email paragraph 3: state support structure with specific boundaries
☐ Onboarding Day 1 action: must be completable in under 20 minutes with a visible output
Weekly Ritual
☐ Process all new refunds: archive verbatim, assign archetype code, update pattern counts
☐ Review all support tickets: flag any buyer with 5+ tickets in 14 days (A04 signal)
☐ Scan community: flag zero-engagement accounts after day 14 (A02 signal)
☐ Score all new application submissions against Qualification Rubric
☐ Check all Open profiles: has any crossed 3 new instances this week? If yes — trigger Remediation Protocol
Monthly
☐ Full database review: close profiles with zero new instances in 90 days
☐ Run anti-language audit: pull all Open profile anti-language fields and sweep all live copy
☐ 30-day exclusion audit: update all ad platform suppression lists and negative keyword lists
☐ Check Repulsion System Changelog: fill in 30-day conversion rate and net revenue figures for all changes deployed last month
☐ Review 'Not for you' sections: are all active profiles represented? Any new bullet required?
Quarterly
☐ Full repulsion system audit: review every layer against current active profiles
☐ Qualification Rubric calibration: compare approved-vs-declined outcomes. Is the rubric catching the right patterns?
☐ Check CPA delta since last exclusion update — document in Repulsion System Changelog
☐ Compile Negative Avatar Quarterly Report: total profiles, remediated profiles, net revenue impact of repulsion system
☐ Brief product team on any 'What they actually need' signals that cross the 5-instance threshold — these are product development priorities
The quarterly report calls for totals, remediated profiles and net revenue impact. Keep the raw observations and stated limitations behind each number. The unknown remediation workflow, five-instance product window, actual prerequisites and platform implementation remain explicit gaps.
Resources and turn-in
Open Negative Avatar Modelling. Its original and accompanying appendix retain all 34 tables and complete source wording.
Open the Post-MVO Forensic Audit for the refund protocol and existing Refund Records definition. Open Beta Testing Methodology for its shorter six-field profile and participant feedback instruments. These related methods differ; do not silently merge their thresholds.
RISER NATION CORP is this project's destination. IF YOU AREN'T BUILDING, YOU ARE DESTROYING. Source footer domains and legacy tier labels remain original evidence rather than new assignments.
Turn in: one evidence-linked draft profile, a completed five-dimension qualification example, and a proposed fit or delivery revision with its rationale. Label hypothetical data. Include conflicting rules, missing evidence and a measurement plan. Keep it in your course work folder until the submission destination is confirmed. A reviewer should check the evidence and proposed change before customer, platform or business action.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION
MASTER OPERATING SYSTEM
SOP — NEGATIVE AVATAR MODELLING
The System That Defines Who You Are Not Selling To — and Why That Protects Everything
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
Every operator builds a Positive Avatar — the profile of the dream buyer. Few operators build the Negative Avatar — the equally important profile of the person who should never buy this offer. The gap between those two frameworks is where refunds, support drain, bad reviews, and low completion rates live.
This SOP defines the system for identifying, profiling, and operationally deploying Negative Avatar models across every part of the business: the sales page, the ad targeting, the application form, the sales call, the community, and the offer design itself. It covers the five Negative Avatar archetypes, eight data sources for identifying them, the profile template, the repulsion system, the positive extraction protocol (because every Negative Avatar teaches you something), and the integration roadmap.
The Core Insight
The Negative Avatar is not the enemy. They are a mismatch. Treating them as a problem to manage loses the intelligence they carry. Every person who refunded, dropped out, or complained without getting results is giving you a precise diagnostic signal about your copy, your targeting, your promise, or your delivery. Build the system that reads those signals.
Hormozi's Lens
The people who drain your support team, inflate your refund rate, and lower your completion metrics cost you more than they paid you. Not because they are bad people — because they were never the right fit. Repelling the wrong buyer before purchase is worth 10x what you spend acquiring the right one.
Kennedy's Rule
You cannot design a compelling 'This IS for you' message without first designing an equally compelling 'This is NOT for you' message. The willingness to turn people away is the single biggest trust signal you can give to the right buyer.
The Business Case: What the Wrong Buyer Actually Costs
Most operators calculate the cost of a refund as the lost sale revenue. The real cost is three to five times that number once you account for every downstream effect of the wrong buyer entering your ecosystem.
Cost Category
What Happens
Typical Multiplier on Sale Value
Support drain
Wrong-fit buyers generate 4–8x more support tickets than right-fit buyers. Each ticket costs staff time, founder attention, and response latency for other buyers.
2–3x lost sale value in staff and opportunity cost
Completion rate damage
Low completion by wrong-fit buyers drags down your aggregate completion statistics — the primary social proof metric for course and programme offers.
Reduces testimonial yield by 20–40% of what it would be with a clean avatar cohort
Review and reputation risk
Wrong-fit buyers who do not get results leave reviews citing their outcome without disclosing they were not the intended buyer. These reviews damage cold traffic conversion rates.
One 1-star review offsets approximately 12 positive reviews in aggregate rating
Community contamination
Wrong-fit buyers lower engagement quality, ask off-topic questions, and create support burden for community managers that degrades the experience for right-fit buyers.
Accelerates right-fit member churn by 15–30% in communities where wrong-fit buyers are visible
Refund processing cost
Direct refund processing: payment processor fees, staff time, and the loss of the original transaction cost (ad spend to acquire that buyer).
1.2–1.5x the original sale value when processing costs are included
Ascension revenue lost
A right-fit buyer has a 15–25% chance of ascending to the next tier. A wrong-fit buyer has near-zero chance and actively reduces the ascension rate of surrounding buyers by lowering community energy.
5–10x the original sale value in lifetime value delta vs a right-fit buyer
The Net Cost Calculation
A $297 MVO sale to the wrong buyer can cost $900–$1,500 in aggregate downstream impact when support, reputation, community, and lost ascension are accounted for. Repelling that buyer before purchase — at near-zero cost — is one of the highest-ROI actions in the entire business.
The Five Negative Avatar Archetypes
Every wrong-fit buyer fits one of five archetypes. Each archetype has a distinct profile, specific identification signals, a cost pattern, and — critically — a different piece of product intelligence embedded within it. Learn to recognise all five on sight.
ARCHETYPE 01
The Wrong-Problem Buyer
Bought the category. Needed a different product.
Who they are
This person has a real problem and real intent. They found your offer through search or ad targeting, recognised the category as relevant, and purchased based on surface-level alignment. But their specific problem is not what your offer solves. They thought 'lead generation' meant one thing; you solve a specific flavour of it for a specific avatar. They bought the genre, not the transformation.
How to spot them
Confused support tickets within 72 hours of purchase. Questions about topics your offer does not cover. Requests for refunds citing 'this isn't what I expected' without citing specific content failures. Onboarding survey answers that do not match your target avatar profile.
What they cost you
High support ticket volume. High early refund rate (days 1–7). Low module engagement because the content does not address their actual problem. Neutral-to-negative reviews citing 'not relevant to my situation.'
What they teach you
Your sales page or ad copy is using language that attracts a broader category than your specific offer serves. The wrong-problem buyer shows you exactly where your positioning is too wide. Their exact words in the refund message reveal which phrase in your copy created the misalignment.
ARCHETYPE 02
The Passive Consumer
Paid for permission to not implement.
Who they are
This person purchases with genuine optimism. They intend to implement. But their purchase is partly driven by the belief that buying = progress. They download every lead magnet, buy every relevant course, and rarely finish any of them. They are not lazy — they are overwhelmed, under-accountable, or purchasing as a substitute for the discomfort of implementation. The offer is high quality. The buyer's operating system is the problem.
How to spot them
Purchases from your email list or retargeting (not cold) — they know you and have likely bought from adjacent offers before. High open rates on emails but low click-to-action rates. Module 1 completion but rapid dropoff after the first action item requires real work. No support tickets. Silent dropout.
What they cost you
Drags down completion statistics without generating feedback data. Rarely refunds — disappears instead. Does not produce testimonials. Occupies community space without contributing. Difficult to diagnose because they do not complain.
What they teach you
Your onboarding sequence does not create enough implementation accountability in the first 72 hours. The passive consumer reveals that your Quick Win (the first action with a visible result) is either absent or too easy to skip. They also reveal whether your community has an accountability culture or a consumption culture.
ARCHETYPE 03
The Mismatched-Stage Buyer
Right person. Wrong moment in their journey.
Who they are
This buyer is legitimately your target avatar — same industry, same problem category, same goals. But they are either six months too early (they lack the prerequisites your offer assumes) or eighteen months too late (they have already solved the problem your offer addresses and need something more advanced). Neither version is the wrong person. Both are the wrong timing.
How to spot them
Too-early: Onboarding survey answers reveal missing prerequisites. Support tickets asking foundational questions your modules assume they already know. Frustration expressed as 'I'm lost' rather than 'this is wrong.' Too-late: Completion without results — because they already know the material. Exit interviews citing 'I was hoping for more advanced content.' Requests for refunds citing 'I've already done all of this.'
What they cost you
Too-early buyers have very high support costs and low completion rates. Too-late buyers have low support costs but produce weak testimonials ('good review of fundamentals') that do not match your promise and reduce conversion credibility.
What they teach you
The too-early buyer reveals that your sales page lacks a 'You need X before this will work' prerequisite statement. The too-late buyer reveals that there is an unserved advanced segment who needs a higher-tier offer you have not yet built. Both archetypes define the exact edges of your value ladder.
ARCHETYPE 04
The Vampire Client
Extracts maximum support. Pays minimum price.
Who they are
This person genuinely wants results — but their expectation of the support, access, and attention they are entitled to dramatically exceeds what was sold to them. They are not trying to exploit the system consciously. They believe their level of need is normal and reasonable. They book every available call slot, send multiple emails per week, ask questions in every community thread, and escalate immediately when they feel under-served. Their disproportionate resource consumption makes the economics of every cohort they join unworkable.
How to spot them
Multiple support tickets per week from day one. Attempts to upgrade support access beyond what was purchased ('Can I just send you this quickly?'). Escalation when response time exceeds 24 hours. Requests for 1:1 attention within a group programme. Frustration about lack of personalisation in group calls.
What they cost you
This archetype creates the highest per-buyer operational cost in the entire customer base. In a cohort of 20, one Vampire Client can consume 40% of all support bandwidth and undermine the experience for 19 other paying buyers. At scale, they make high-touch delivery economically unviable.
What they teach you
This archetype reveals a gap in your onboarding expectations. Somewhere in your marketing — likely in the sales copy's language around access, support, or personalisation — a promise is being read as more expansive than you intended. They also reveal that a more expensive done-for-you or 1:1 tier is in genuine demand and not yet priced accordingly.
ARCHETYPE 05
The Guarantee Exploiter
Purchased with the intent to consume and refund.
Who they are
This is the rarest archetype and the only one that represents deliberate misuse rather than a mismatch. This buyer researches the guarantee before purchasing, consumes the entire programme at maximum speed, and submits a refund request citing the guarantee language before the window closes. They are not confused about fit. They have identified your guarantee as a mechanism for free content access.
How to spot them
Purchases at the latest possible point in a launch window (maximising consumption time before the guarantee expires). Completes 100% of programme content within days of purchase. Refund request arrives on day 29 or 30 of a 30-day guarantee citing compliance with every stated condition. Often uses Gmail aliases or has purchased-and-refunded from similar creators before.
What they cost you
Direct financial loss equivalent to 1.5x the sale price (including processing costs). No data loss — they complete everything and give you nothing useful. If they leave a review, it is often falsely positive to avoid detection.
What they teach you
This archetype reveals that your guarantee language is too unconditional or that you lack a completion-based gate. Conditional guarantees — 'If you complete all modules, submit all assignments, and do not see [specific result]' — dramatically reduce exploitation while maintaining credibility with genuine buyers. The Guarantee Exploiter teaches you exactly which condition to add.
PHASE 1
Data Collection & Signal Sources
Where Negative Avatar evidence lives and how to extract it
The Eight Signal Sources
Negative Avatar data does not come from one place. It is distributed across every customer touchpoint in your business. The system below ensures no signal goes unread.
Source
What to Mine
Archetype It Most Commonly Reveals
Collection Method
Refund request messages
Verbatim language describing why the offer failed to meet expectations. The most direct source of wrong-fit evidence.
Archetype 01 (Wrong-Problem) and Archetype 03 (Mismatched Stage)
Log verbatim in Airtable within 24 hours. Tag with archetype code. Never paraphrase.
Support ticket patterns
Volume, topic clusters, and emotional tone of all support tickets per buyer. Disproportionate volume from a single buyer is the primary Vampire Client signal.
Archetype 04 (Vampire Client) and Archetype 01 (Wrong-Problem)
Weekly tag audit in Intercom or Help Scout. Flag any buyer with 5+ tickets in 14 days.
Sales call recordings
Objections that were overcome but probably should not have been. The buyer who bought despite a red-flag objection is a Negative Avatar in waiting.
Archetype 01, 03, and early Archetype 02 signals
Review 100% of sales call recordings for buyers who later refund. Tag the objection that preceded the sale.
Application form responses
Answers that reveal mismatched stage, wrong problem, or unrealistic expectations before purchase. The pre-purchase filter.
Archetype 03 (Mismatched Stage) primary detection point
Weekly review of all application submissions. Score against the Qualification Rubric (see Phase 3).
Onboarding survey responses
Baseline situation statements that reveal who actually bought vs. who you thought was buying. Compare baseline to your intended avatar profile.
Archetype 01 and Archetype 03
Flag responses where the situation described does not match your positive avatar profile. Review within 48 hours of submission.
Community engagement patterns
Dropout (Archetype 02), conflict escalation (Archetype 04), and topic mismatch (Archetype 01) all manifest in community behaviour before they appear in support tickets.
Archetype 02 (Passive Consumer) and Archetype 04 (Vampire Client)
Weekly community audit: flag accounts with zero posts after 14 days (dropout signal) and accounts with 3+ conflict interactions.
Exit interview transcripts
The most information-rich single source. Buyers who did not get results will describe exactly why — often identifying the mismatch themselves if asked the right questions.
All five archetypes
Castmagic transcript. Highlight every sentence describing what they expected vs. what they found.
Stripe/payment refund history
Pattern detection across multiple buyers. Time-to-refund, purchase day within launch window, and refund reason clustering reveal the Guarantee Exploiter pattern.
Archetype 05 (Guarantee Exploiter)
Monthly refund report. Flag any account with purchase in last 3 days of launch + refund in last 2 days of guarantee window.
PHASE 2
The Negative Avatar Profile Template
Building a complete, actionable profile for each archetype found in your data
When to Build a New Profile
A new Negative Avatar Profile is created when the same archetype pattern appears three or more times within any 60-day period from buyers of the same offer. A single instance is noise. Three instances from the same root cause signal a systematic problem in targeting, copy, or delivery that requires a documented response.
The Pattern Threshold Rule
One refund is an event. Two refunds with similar language is a coincidence. Three refunds citing the same root cause within 60 days is a pattern — and patterns get a Negative Avatar Profile and a specific remediation action. Do not wait for more evidence than three.
The Negative Avatar Profile Template
Complete one of these for every pattern that crosses the three-instance threshold. File in Airtable under Negative Avatars table. Link to the offer and the specific refund or dropout records that triggered its creation.
Profile Field
What to Document
Example
Profile ID
Autonumber + offer abbreviation + archetype code
MVO-01-A01 (first Wrong-Problem profile for MVO-01)
Archetype code
01–05 from the five archetypes above
A01 — Wrong-Problem Buyer
Character name
Give this profile a memorable name for internal reference. The name should capture the essence of the mismatch.
'The Adjacent Niche Buyer' or 'The One-Step-Earlier Operator'
Date pattern detected
Date the third instance was logged, triggering profile creation
2026-03-15
Number of instances (at creation)
Count of buyers matching this pattern within the detection window
3 refunds within 47 days
Verbatim trigger phrase
The exact phrase — 3 to 8 words — that appears in the refund or dropout data most consistently for this profile. This is the primary copy signal.
'Not what I was looking for' / 'Thought this covered X'
Entry point
Which ad, email, or content piece most commonly preceded the wrong-fit purchase. The copy that attracted the wrong buyer.
Meta ad targeting 'course creators' — too broad; includes creators whose core problem is not offer construction
The mismatch anatomy
In one sentence: why this buyer and this offer are a mismatch. Not their fault. Not the offer's fault. A structural incompatibility.
This buyer needs audience building before they need offer construction. They have no list to sell to and the offer assumes one exists.
What they actually need
The offer that would have served them correctly — whether you have built it yet or not.
A traffic and list-building offer — currently Tier 0/1 in the value ladder. Not yet built.
Sales page anti-language
Words or phrases currently on the sales page that are attracting this profile. These must be audited and potentially removed or reframed.
'Course creators' in ad copy — replaced with 'course creators with an existing audience above 1,000 subscribers'
'Not for you if' addition
The specific bullet point to add to the 'This is NOT for you' section of the sales page as a direct result of this profile.
This is NOT for you if you are still building your first audience and have not yet had any paying customers.
Targeting exclusion
The specific ad audience characteristic to exclude, or the application form question to add, that would have screened this buyer before purchase.
Exclude interest targeting: 'content creation' and 'blogging'. Add application question: 'How many paying customers have you had in the last 90 days?'
Status
Open (pattern continuing) / Remediated (fix deployed) / Closed (no new instances in 90 days)
Open
PHASE 3
Pattern Recognition & Classification
Turning raw data into structured profiles
The Weekly Classification Ritual
Pattern recognition requires a consistent weekly pass through all negative signal sources. This ritual takes 20–30 minutes and prevents the accumulation of unread signals that makes pattern detection impossible.
1. Pull all new refund messages from Airtable Refund Records. Read each verbatim. Assign archetype code. Look for phrase overlap with existing profiles.
2. Pull all support tickets flagged in the past 7 days. Count tickets per buyer. Flag any buyer with 5+ tickets in 14 days for Archetype 04 review.
3. Scan community for zero-engagement accounts (no posts or comments in 14+ days after an initial welcome post). Add to Archetype 02 passive tracker.
4. Review any sales call recordings from buyers who refunded in the past 7 days. Tag the objection that preceded the sale.
5. Check pattern counts on all Open profiles. If any profile hits 3 new instances this week: trigger the Remediation Protocol (Phase 5).
The Qualification Rubric for Application Forms
For offers above $497, an application form is the primary Negative Avatar screening mechanism. The Qualification Rubric below scores each application against the specific mismatches your active Negative Avatar Profiles describe. Applications scoring below the threshold are declined or directed to a lower-tier offer.
Qualification Dimension
Screening Question
Green Flag (Score 2)
Amber Flag (Score 1)
Red Flag (Score 0)
Problem specificity
Describe the specific problem you are trying to solve in one sentence.
Describes a specific, narrow problem that your offer directly solves
Describes a broad category that your offer partially addresses
Describes a problem your offer does not solve or a different problem category entirely
Stage readiness
What have you already tried to solve this? What happened?
Has tried and exhausted alternatives. Has skin in the game. Has some prior result.
Has researched but not yet implemented anything. No prior attempt.
Has not identified the problem as actionable yet. Describes a future state not a current problem.
Implementation capacity
How much time per week can you dedicate to this work for the next 60 days?
States a specific number of hours above your minimum threshold
States a number at or slightly below threshold but with a credible explanation
States a number that makes completion of your programme impossible, or gives a non-answer
Financial alignment
Are you aware this is a [price] investment and are you in a position to make that decision today?
Yes, directly and without hesitation
Yes, but with a question about payment plans — not a concern, a logistics question
Dodges the question, asks about refund policy before asking about the programme, or indicates the price is a stretch
Outcome specificity
What does success look like to you 90 days from now?
States a specific, measurable outcome that your offer can credibly deliver
States a directional outcome without specific metrics — achievable but vague
States an outcome your offer cannot deliver in the timeframe or describes a transformation your offer does not produce
Scoring: 10 = ideal candidate. 7–9 = qualified with follow-up question. 4–6 = redirect to lower-tier offer with explanation. Below 4 = decline with dignity and direction to appropriate resource.
Sales Call Red Flag Protocol
Some Negative Avatars pass the application form but reveal themselves on the sales call. These five red flags indicate a mismatch that should not be sold through — they should be declined kindly and redirected.
Red Flag Signal
What It Reveals
Correct Response on Call
'Will this work even if I don't have [prerequisite your offer assumes]?'
Mismatched Stage — Archetype 03 Too Early. They lack something fundamental your offer is built upon.
'I want to be honest with you — this offer is designed for people who already have [prerequisite]. Without that, you won't get the result we promise. Here's what I'd recommend first...'
'What happens if I need more support than what's included?'
Early Vampire Client signal — Archetype 04. Testing boundaries before purchasing.
Describe the support structure clearly and specifically. Ask: 'Does that feel like enough for you?' If hesitation: 'Our 1:1 programme might be a better fit — let me describe that option.'
'Can you show me the refund policy again?'
Either Guarantee Exploiter (Archetype 05) or a buyer with genuine uncertainty. Distinguish by context.
If asked as the first or second question: proceed with caution. Describe the conditional guarantee clearly and state what completion requires. If they lead with refund questions on a call, they are not ready to commit.
'I've bought a few courses on this topic but haven't implemented any of them.'
Strong Passive Consumer signal — Archetype 02. Purchases are a substitute for implementation for this buyer.
'I appreciate your honesty. Before I'd feel good about taking your money, I'd like to understand what stopped you from implementing the others. Because this programme requires [specific action] in week one.' Only proceed if they give a credible, non-pattern answer.
'I just need someone to tell me what to do.'
Can be either the right buyer (Executive Buyer who wants clear direction) or the Passive Consumer variant who expects the programme to create action on their behalf. Probe further.
'Tell me what that looks like for you — when you say someone tells you what to do, do you mean a clear step-by-step system, or do you mean you need someone to do the work with you?' The answer reveals whether they need your offer or a done-for-you service.
PHASE 4
The Repulsion System
Keeping the wrong buyer out — before they cost you anything
The Repulsion System Architecture
A complete repulsion system has five layers. Each layer catches a different archetype at a different stage of the buyer's journey. The goal is not to be hostile — it is to be so specific about who this offer is for that the wrong buyer self-selects out before purchase.
Layer
Where It Lives
Primary Archetype Caught
Mechanism
Layer 1 — Ad targeting exclusion
Paid ad campaign settings
Archetype 01 (Wrong-Problem)
Exclude specific interest categories, job titles, and lookalike audiences that have produced wrong-fit buyers. Add negative keywords to Google and YouTube campaigns.
Layer 2 — Sales page 'Not for you' section
Below the offer stack, above the guarantee
Archetypes 01, 02, and 03
A specific list of 4–6 statements beginning with 'This is NOT for you if...' Each bullet maps directly to an active Negative Avatar Profile.
Layer 3 — Anti-language audit
All copy across sales page, email sequence, and ads
Archetype 01 (Wrong-Problem) primary
Remove or reframe any word or phrase in active Negative Avatar Profile anti-language fields. These words are attracting the wrong buyer by signalling a broader category than you serve.
Layer 4 — Application form qualification
Offer pages above $497 and all high-ticket tiers
Archetypes 03 and 04
The Qualification Rubric from Phase 3. Any application scoring below 7 is redirected before any human time is invested.
Layer 5 — Sales call screening
Discovery and strategy calls
Archetypes 03, 04, and 05
The Red Flag Protocol from Phase 3. Any call that produces two or more red flags is declined with a specific redirection.
Writing the 'This is NOT for You' Section
This is the single most important piece of repulsion copy on your sales page. It serves two functions simultaneously: it filters out wrong-fit buyers, and it dramatically increases trust with right-fit buyers by demonstrating that you know exactly who you are not serving. Here is the framework for writing it.
Structure and Format Rules
• Write 4–6 bullets only. More than 6 weakens the specificity of each one.
• Each bullet maps directly to one active Negative Avatar Profile. Do not invent bullets — derive them from real data.
• Write in plain, non-judgmental language. You are describing a mismatch, not an insult.
• Lead each bullet with the specific condition, not a character flaw. 'If you have not yet had your first paying customer' not 'If you are a beginner.'
• End the section with one sentence that redirects: 'If any of the above describes you, [specific alternative] is likely a better fit.'
Example 'Not for You' Section (Template)
This is NOT for you if...
• You are still building your first audience and have not yet had a paying customer — this offer assumes you have proof that someone will pay you for something.
• You are looking for someone to do the work for you — this is a hands-on implementation programme that requires 4–6 hours per week of your personal effort.
• You have already built and launched a core offer generating above $10K/month — the methods here are designed for the $0–$10K validation stage, not the scaling stage.
• You are in a rush to launch in the next 7 days — the framework takes 30 days to implement correctly and shortcuts produce bad data.
• You have purchased more than two similar programmes in the last 12 months without implementing them — this will produce the same result unless something in your circumstances has fundamentally changed.
If any of the above describes your situation, the RISER Nation Tracks 1–3 Foundation bundle is likely a better starting point.
The Anti-Language Audit Protocol
Anti-language is any word or phrase in your copy that attracts the wrong buyer by signalling a broader category, a different problem, or a different buyer stage than your offer serves. Running this audit quarterly — and immediately after any new Negative Avatar Profile is created — prevents ongoing wrong-buyer acquisition.
1. Pull the 'Sales page anti-language' field from every Open Negative Avatar Profile in Airtable.
2. Run a Find & Replace search for each phrase across: sales page, all active email sequences, all live ad creatives, and all landing pages.
3. For each instance found: decide whether to remove the phrase entirely or reframe it with a specific qualifier.
4. Document every change in Airtable under the relevant Negative Avatar Profile record — date, what changed, where.
5. Schedule a conversion rate comparison 30 days after each anti-language audit. The repulsion change should not reduce overall conversion meaningfully if it is filtering the right buyers.
The Conversion Rate Paradox
When you first run the anti-language audit and add 'Not for you' copy, your conversion rate on ad traffic may drop 5–15%. This is the system working correctly — you are filtering out buyers who would have purchased and then refunded. Your actual net revenue after refunds typically increases within 30 days. Track net revenue, not gross conversion rate, when evaluating repulsion system effectiveness.
PHASE 5
The Positive Extraction Protocol
Every Negative Avatar teaches you something specific — extract it
The Intelligence Each Archetype Carries
This is the most overlooked dimension of Negative Avatar work. Most operators use wrong-fit buyer data only defensively — to keep bad buyers out. The same data, read with a different lens, is one of the most valuable product development and copy improvement inputs available.
Archetype
The Defensive Use (Repulsion)
The Offensive Use (Product Intelligence)
Specific Action Triggered
A01 — Wrong-Problem Buyer
Remove copy that attracts the wrong category. Tighten ad targeting.
Reveals demand for an adjacent offer that solves their actual problem. If three or more Wrong-Problem buyers share the same alternative need, that need is your next product signal.
Open a 'Problem B' card in the Product Roadmap for the problem this archetype actually needed solved.
A02 — Passive Consumer
Add completion accountability to onboarding. Create a stronger Quick Win in module 1.
Reveals that your onboarding does not create enough urgency or identity shift at purchase. The best fix is not more content — it is a better Day 1 experience that makes implementation feel inevitable.
Rebuild the welcome sequence with a 72-hour implementation challenge. 'Your first result in 72 hours or tell me what stopped you.'
A03 Too Early — Mismatched Stage
Add prerequisite language to sales page. Add stage-qualification question to application form.
Reveals an unserved earlier-stage market. If there are consistently buyers who are 6 months too early for your current offer, the gap between 'zero' and your MVO is a product waiting to be built.
Create a 'Prerequisites Offer' — the entry-level product that gets them to the starting line of your MVO.
A03 Too Late — Mismatched Stage
Add 'Not for you if you already have X' to sales page.
Reveals that there is a more advanced buyer segment who needs your next-level offer. This is your clearest signal that Tier 4 (High-Ticket) or an advanced Core Offer variant should be prioritised.
Open a 'Advanced Buyer' product brief. Run 5 exit interviews with Too-Late buyers asking: 'What would you have needed instead?'
A04 — Vampire Client
Add support structure clarity to sales page. Price the 1:1 tier correctly.
Reveals unmet demand for higher-access tiers that are not correctly priced or positioned. Vampire Clients are often willing to pay significantly more for appropriate access — they just could not find it in your offer wall.
Audit your high-ticket and DFY tiers. The Vampire Client is the right-fit buyer for a tier you have not yet built or priced correctly.
A05 — Guarantee Exploiter
Add conditional language to guarantee. Add completion requirements.
Reveals that your guarantee language lacks the specificity needed to distinguish genuine-effort buyers from exploiters. The conditional rewrite that stops exploiters also increases perceived credibility with genuine buyers — because specific conditions imply a confident offer.
Rewrite guarantee from unconditional to conditional. State the exact completion requirements needed to qualify for a refund.
PHASE 6
Offer Design Integration
Using Negative Avatar data to build better offers from the ground up
The Pre-Offer Negative Avatar Brief
Every new offer — before a single module is designed or a word of copy is written — should have a Negative Avatar Brief completed alongside the Positive Avatar profile. The brief documents the three archetypes most likely to be attracted to this offer category and the specific design decisions that will pre-empt them.
Brief Element
What to Define
Example (for an offer on organic content strategy)
Most likely wrong-fit archetype 1
Which archetype will this offer category most commonly attract by mistake, and why?
A01 — Wrong-Problem: People who need paid ads, not organic content. Attracted by 'get more clients' language that applies to both channels.
Most likely wrong-fit archetype 2
Second most likely archetype and its attraction mechanism.
A03 Too Early: People with no existing content platform or audience. Attracted by 'start from scratch' language that implies zero prerequisites.
Prerequisites to state explicitly
What must a buyer already have for this offer to work as promised?
A social media profile with at least 6 months of consistent posting history and at least 200 followers. Some prior experience with content creation.
Support capacity design
Based on expected archetype mix, how many support interactions per buyer per week is your delivery model designed for?
Maximum 2 support tickets per week per buyer. Vampire Client protocol triggers at 5+ tickets in any 14-day window.
Guarantee design
Given the most likely archetype mix, what guarantee language protects against exploitation while remaining credible?
Conditional: 'If you post the required 3x per week for 30 days and do not see at least 15% growth in profile engagement, we will refund in full.'
'Not for you' bullets (draft)
Write 4 'Not for you' bullets directly from the identified archetypes before launch.
1. If you have not posted consistently for at least 3 months. 2. If your primary acquisition channel is or needs to be paid ads. 3. If you are not prepared to post 3 times per week during the programme. 4. If you are looking for growth shortcuts — every strategy here takes 30+ days to produce data.
The Delivery Design Implication
The most common delivery design mistake is building a programme for the Positive Avatar and then being surprised when the wrong-fit buyer's needs are not served. Once you have documented the most likely wrong-fit archetypes for a new offer, make these specific delivery design decisions before building:
Archetype Risk
Delivery Design Decision
Implementation
A02 Passive Consumer risk is high
Build accountability into the first 72 hours, not as a feature — as a requirement. The first action item must be completable in under 20 minutes and must produce a visible output.
Module 1 ends with: 'Post your output in the community with the tag #Week1Win. You have 72 hours.' Community manager checks and personally tags any non-posters at hour 48.
A03 Too Early risk is high
Add a pre-programme self-assessment that evaluates prerequisite completion. Make it ungated but visible — buyers should encounter it before purchase and ideally before opting into the lead magnet.
Landing page addition: '2-minute readiness check' that scores their current situation against 5 prerequisites. Shows them their readiness score and tells them what to do if below threshold.
A04 Vampire Client risk is high
Define support access with extreme specificity in the sales copy and onboarding materials. The access ambiguity that creates Vampire Clients must be removed before purchase.
Onboarding email paragraph 3: 'Here is exactly what support looks like in this programme: [specific hours, specific response time, specific channels, specific escalation path]. This is intentionally bounded — it is what allows us to deliver quality to every member equally.'
A05 Guarantee Exploiter risk is high
Design completion checkpoints that are simple to complete for genuine buyers and inconvenient to game for exploiters.
Completion requirements for guarantee eligibility: submit module completion confirmations through the platform (timestamped), post in community at milestone points (timestamped and public), complete the exit survey. These are trivial for genuine buyers and require meaningful effort to fake.
PHASE 7
Ad Targeting & Exclusion Integration
Turning Negative Avatar data into paid media precision
From Profile to Exclusion Audience
Every active Negative Avatar Profile should produce at least one paid media targeting exclusion or negative keyword. This is the most direct revenue impact of Negative Avatar work — it reduces cost per acquisition by eliminating spend on audiences that produce wrong-fit buyers.
Platform
Exclusion Mechanism
Negative Avatar Application
How to Implement
Meta Ads
Custom audiences (upload buyer list), interest exclusions, and lookalike exclusion
Upload all refund records as a suppression list to prevent re-acquisition. Exclude interest categories identified in A01 profiles. Create a 'bad buyer lookalike' from refund list to identify and exclude similar profiles.
Ads Manager → Audiences → Custom Audience → Customer list. Upload email list of all buyers who refunded with RC-1 or RC-3 codes. Create 1% lookalike to exclude.
Google / YouTube Ads
Negative keyword lists and audience exclusions
Add negative keywords from A01 anti-language audit. These are the search terms that attract wrong-problem buyers.
Google Ads → Shared Library → Negative keyword lists. Create 'Wrong Avatar' list from all anti-language phrases identified in active profiles.
TikTok Ads
Custom audience exclusion and interest negative targeting
Upload refund list as suppression. Exclude content creator interests if A01 data shows content creators are a mismatch.
TikTok Ads Manager → Audience → Custom Audience → Customer file. Upload and set as exclusion.
LinkedIn Ads
Job title exclusions and company size exclusions
If A03 (Too Early) buyers consistently come from companies below a certain size or from specific job titles, exclude these in targeting.
Campaign Manager → Audience → Exclusions → Job Titles. Build the exclusion list from A03 profile entry point data.
Retargeting audiences
Event-based exclusions
Exclude page visitors who spent less than 90 seconds on the sales page (bounce behaviour associated with wrong-fit visitors who did not engage with the 'Not for you' section).
GA4 → Audience → Create audience based on time on page event. Exclude from retargeting in all platforms.
The 30-Day Exclusion Audit
Once per month, run this protocol to ensure your exclusion audiences are current and your negative keyword lists reflect the latest anti-language data from new profiles.
1. Pull all refund records from the past 30 days. Upload any new email addresses to suppression lists on all active ad platforms.
2. Review all new Negative Avatar Profiles created in the past 30 days. Extract any new anti-language phrases. Add to negative keyword lists.
3. Review the entry point field in all Open profiles. If a specific ad, audience, or campaign is consistently producing wrong-fit buyers, pause that ad or refine that audience.
4. Check Cost Per Acquisition (CPA) comparison: buyers acquired from excluded audiences (before exclusion was added) vs. buyers acquired after exclusion. Document the delta.
PHASE 8
The Ongoing Review Cadence
Keeping the system live, current, and compounding
The Cadence Calendar
Frequency
Activity
Time Required
Output
Daily (ongoing)
Process any new refund request through the 5-step Refund Forensics Protocol from the Post-MVO Forensic Audit Loop SOP. Archive verbatim. Assign archetype code.
5–10 min per refund
Refund archive entry. Pattern count updated.
Weekly (Mondays — 20 min)
Run weekly classification ritual: review all new support tickets, refunds, and community signals. Update pattern counts on Open profiles. Check for any profile crossing 3-instance threshold.
20 minutes
Pattern counts updated. New profiles created if threshold crossed.
Weekly (Thursdays — 15 min)
Review all new application form submissions against the Qualification Rubric. Score and route: approve, follow-up question, redirect, or decline.
15 minutes
Application decisions documented. Any new A03 or A04 signals noted.
Monthly (first Monday)
Full Negative Avatar database review. Close any profiles with zero new instances in 90 days. Check all Open profiles for remediation effectiveness. Run anti-language audit against all active copy.
60–90 minutes
Database cleaned. Remediated profiles moved to Closed. Anti-language copy updates queued.
Quarterly
Full repulsion system audit: review 'Not for you' section against active profiles, re-run Qualification Rubric calibration, review all ad exclusion audiences, check CPA delta since last exclusion update.
Half day
Repulsion System Update Report. Action brief for copy and targeting changes.
After every new offer launch
Complete a Negative Avatar Brief before the first sale. Update as first buyers are acquired. Create profiles at 3-instance threshold — which may arrive faster for new offers.
2 hours pre-launch + ongoing
Pre-launch Negative Avatar Brief filed in Airtable. First profiles created within 30 days of launch.
The Negative Avatar Database — Airtable Schema
All Negative Avatar data lives in four linked tables within the same Airtable base as the Post-MVO Forensic Audit Loop system. The schema below ensures every profile, every instance, and every remediation action is connected and searchable.
Table 1 — Negative Avatar Profiles
One record per confirmed pattern (3+ instances). The master reference document for each archetype found in your data.
Field
Type
Notes
Profile ID
Autonumber
Auto-generated. Format: [Offer]-[Seq]-A0[1-5]
Character name
Short text
Internal reference name — descriptive, memorable
Archetype code
Single select
A01 through A05
Offer
Link → Offers table
Which offer this profile relates to
Date created
Date
Date the 3rd instance was logged
Instance count
Number
Updated weekly — total instances logged
Verbatim trigger phrase
Long text
Most consistent 3–8 word phrase from the data
Entry point
Long text
Ad, email, or content piece most commonly preceding purchase
Mismatch anatomy
Long text
One-sentence structural description of why buyer and offer are misaligned
What they actually need
Long text
The offer that would have served them correctly
Sales page anti-language
Long text
Specific phrases to audit and remove or reframe
Not for you addition
Long text
The exact bullet to add to the 'Not for you' section
Ad targeting exclusion
Long text
Specific audience or keyword exclusion to implement
Application form change
Long text
Question to add or threshold to adjust on application form
Remediation date
Date
Date the fix was deployed across all affected assets
Status
Single select
Open / Remediated / Closed
Linked refund records
Link → Refund Records
All refunds that contributed to this profile
Table 2 — Refund Records
One record per refund. Already defined in the Post-MVO Forensic Audit Loop SOP — link to that table. Add a Negative Avatar Profile link field to connect refund records to the profiles they inform.
Table 3 — Application Scoring Log
One record per application form submission for offers above $497.
Field
Type
Notes
Application ID
Autonumber
Date submitted
Date
Offer applied for
Link → Offers table
Rubric score
Number
0–10 from the Qualification Rubric
Dimension scores
Long text
Individual scores for each of the 5 rubric dimensions
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION",
"MASTER OPERATING SYSTEM",
"",
" SOP — NEGATIVE AVATAR MODELLING ",
"",
"The System That Defines Who You Are Not Selling To — and Why That Protects Everything",
"Kennedy × Hormozi × Brunson × 2026 Framework",
"",
"Version 1.0 | 2026 Edition | RISER Nation Master Operating System",
"",
"SOP Overview",
"Every operator builds a Positive Avatar — the profile of the dream buyer. Few operators build the Negative Avatar — the equally important profile of the person who should never buy this offer. The gap between those two frameworks is where refunds, support drain, bad reviews, and low completion rates live.",
"",
"This SOP defines the system for identifying, profiling, and operationally deploying Negative Avatar models across every part of the business: the sales page, the ad targeting, the application form, the sales call, the community, and the offer design itself. It covers the five Negative Avatar archetypes, eight data sources for identifying them, the profile template, the repulsion system, the positive extraction protocol (because every Negative Avatar teaches you something), and the integration roadmap.",
"",
"The Core Insight",
"The Negative Avatar is not the enemy. They are a mismatch. Treating them as a problem to manage loses the intelligence they carry. Every person who refunded, dropped out, or complained without getting results is giving you a precise diagnostic signal about your copy, your targeting, your promise, or your delivery. Build the system that reads those signals.",
"",
"Hormozi's Lens",
"The people who drain your support team, inflate your refund rate, and lower your completion metrics cost you more than they paid you. Not because they are bad people — because they were never the right fit. Repelling the wrong buyer before purchase is worth 10x what you spend acquiring the right one.",
"",
"Kennedy's Rule",
"You cannot design a compelling 'This IS for you' message without first designing an equally compelling 'This is NOT for you' message. The willingness to turn people away is the single biggest trust signal you can give to the right buyer.",
"",
"The Business Case: What the Wrong Buyer Actually Costs",
"Most operators calculate the cost of a refund as the lost sale revenue. The real cost is three to five times that number once you account for every downstream effect of the wrong buyer entering your ecosystem.",
"",
"Cost Category",
"What Happens",
"Typical Multiplier on Sale Value",
"Support drain",
"Wrong-fit buyers generate 4–8x more support tickets than right-fit buyers. Each ticket costs staff time, founder attention, and response latency for other buyers.",
"2–3x lost sale value in staff and opportunity cost",
"Completion rate damage",
"Low completion by wrong-fit buyers drags down your aggregate completion statistics — the primary social proof metric for course and programme offers.",
"Reduces testimonial yield by 20–40% of what it would be with a clean avatar cohort",
"Review and reputation risk",
"Wrong-fit buyers who do not get results leave reviews citing their outcome without disclosing they were not the intended buyer. These reviews damage cold traffic conversion rates.",
"One 1-star review offsets approximately 12 positive reviews in aggregate rating",
"Community contamination",
"Wrong-fit buyers lower engagement quality, ask off-topic questions, and create support burden for community managers that degrades the experience for right-fit buyers.",
"Accelerates right-fit member churn by 15–30% in communities where wrong-fit buyers are visible",
"Refund processing cost",
"Direct refund processing: payment processor fees, staff time, and the loss of the original transaction cost (ad spend to acquire that buyer).",
"1.2–1.5x the original sale value when processing costs are included",
"Ascension revenue lost",
"A right-fit buyer has a 15–25% chance of ascending to the next tier. A wrong-fit buyer has near-zero chance and actively reduces the ascension rate of surrounding buyers by lowering community energy.",
"5–10x the original sale value in lifetime value delta vs a right-fit buyer",
"",
"The Net Cost Calculation",
"A $297 MVO sale to the wrong buyer can cost $900–$1,500 in aggregate downstream impact when support, reputation, community, and lost ascension are accounted for. Repelling that buyer before purchase — at near-zero cost — is one of the highest-ROI actions in the entire business.",
"",
"",
"The Five Negative Avatar Archetypes",
"Every wrong-fit buyer fits one of five archetypes. Each archetype has a distinct profile, specific identification signals, a cost pattern, and — critically — a different piece of product intelligence embedded within it. Learn to recognise all five on sight.",
"",
"ARCHETYPE 01",
"The Wrong-Problem Buyer",
"Bought the category. Needed a different product.",
"Who they are",
"This person has a real problem and real intent. They found your offer through search or ad targeting, recognised the category as relevant, and purchased based on surface-level alignment. But their specific problem is not what your offer solves. They thought 'lead generation' meant one thing; you solve a specific flavour of it for a specific avatar. They bought the genre, not the transformation.",
"How to spot them",
"Confused support tickets within 72 hours of purchase. Questions about topics your offer does not cover. Requests for refunds citing 'this isn't what I expected' without citing specific content failures. Onboarding survey answers that do not match your target avatar profile.",
"What they cost you",
"High support ticket volume. High early refund rate (days 1–7). Low module engagement because the content does not address their actual problem. Neutral-to-negative reviews citing 'not relevant to my situation.'",
"What they teach you",
"Your sales page or ad copy is using language that attracts a broader category than your specific offer serves. The wrong-problem buyer shows you exactly where your positioning is too wide. Their exact words in the refund message reveal which phrase in your copy created the misalignment.",
"",
"ARCHETYPE 02",
"The Passive Consumer",
"Paid for permission to not implement.",
"Who they are",
"This person purchases with genuine optimism. They intend to implement. But their purchase is partly driven by the belief that buying = progress. They download every lead magnet, buy every relevant course, and rarely finish any of them. They are not lazy — they are overwhelmed, under-accountable, or purchasing as a substitute for the discomfort of implementation. The offer is high quality. The buyer's operating system is the problem.",
"How to spot them",
"Purchases from your email list or retargeting (not cold) — they know you and have likely bought from adjacent offers before. High open rates on emails but low click-to-action rates. Module 1 completion but rapid dropoff after the first action item requires real work. No support tickets. Silent dropout.",
"What they cost you",
"Drags down completion statistics without generating feedback data. Rarely refunds — disappears instead. Does not produce testimonials. Occupies community space without contributing. Difficult to diagnose because they do not complain.",
"What they teach you",
"Your onboarding sequence does not create enough implementation accountability in the first 72 hours. The passive consumer reveals that your Quick Win (the first action with a visible result) is either absent or too easy to skip. They also reveal whether your community has an accountability culture or a consumption culture.",
"",
"ARCHETYPE 03",
"The Mismatched-Stage Buyer",
"Right person. Wrong moment in their journey.",
"Who they are",
"This buyer is legitimately your target avatar — same industry, same problem category, same goals. But they are either six months too early (they lack the prerequisites your offer assumes) or eighteen months too late (they have already solved the problem your offer addresses and need something more advanced). Neither version is the wrong person. Both are the wrong timing.",
"How to spot them",
"Too-early: Onboarding survey answers reveal missing prerequisites. Support tickets asking foundational questions your modules assume they already know. Frustration expressed as 'I'm lost' rather than 'this is wrong.' Too-late: Completion without results — because they already know the material. Exit interviews citing 'I was hoping for more advanced content.' Requests for refunds citing 'I've already done all of this.'",
"What they cost you",
"Too-early buyers have very high support costs and low completion rates. Too-late buyers have low support costs but produce weak testimonials ('good review of fundamentals') that do not match your promise and reduce conversion credibility.",
"What they teach you",
"The too-early buyer reveals that your sales page lacks a 'You need X before this will work' prerequisite statement. The too-late buyer reveals that there is an unserved advanced segment who needs a higher-tier offer you have not yet built. Both archetypes define the exact edges of your value ladder.",
"",
"ARCHETYPE 04",
"The Vampire Client",
"Extracts maximum support. Pays minimum price.",
"Who they are",
"This person genuinely wants results — but their expectation of the support, access, and attention they are entitled to dramatically exceeds what was sold to them. They are not trying to exploit the system consciously. They believe their level of need is normal and reasonable. They book every available call slot, send multiple emails per week, ask questions in every community thread, and escalate immediately when they feel under-served. Their disproportionate resource consumption makes the economics of every cohort they join unworkable.",
"How to spot them",
"Multiple support tickets per week from day one. Attempts to upgrade support access beyond what was purchased ('Can I just send you this quickly?'). Escalation when response time exceeds 24 hours. Requests for 1:1 attention within a group programme. Frustration about lack of personalisation in group calls.",
"What they cost you",
"This archetype creates the highest per-buyer operational cost in the entire customer base. In a cohort of 20, one Vampire Client can consume 40% of all support bandwidth and undermine the experience for 19 other paying buyers. At scale, they make high-touch delivery economically unviable.",
"What they teach you",
"This archetype reveals a gap in your onboarding expectations. Somewhere in your marketing — likely in the sales copy's language around access, support, or personalisation — a promise is being read as more expansive than you intended. They also reveal that a more expensive done-for-you or 1:1 tier is in genuine demand and not yet priced accordingly.",
"",
"ARCHETYPE 05",
"The Guarantee Exploiter",
"Purchased with the intent to consume and refund.",
"Who they are",
"This is the rarest archetype and the only one that represents deliberate misuse rather than a mismatch. This buyer researches the guarantee before purchasing, consumes the entire programme at maximum speed, and submits a refund request citing the guarantee language before the window closes. They are not confused about fit. They have identified your guarantee as a mechanism for free content access.",
"How to spot them",
"Purchases at the latest possible point in a launch window (maximising consumption time before the guarantee expires). Completes 100% of programme content within days of purchase. Refund request arrives on day 29 or 30 of a 30-day guarantee citing compliance with every stated condition. Often uses Gmail aliases or has purchased-and-refunded from similar creators before.",
"What they cost you",
"Direct financial loss equivalent to 1.5x the sale price (including processing costs). No data loss — they complete everything and give you nothing useful. If they leave a review, it is often falsely positive to avoid detection.",
"What they teach you",
"This archetype reveals that your guarantee language is too unconditional or that you lack a completion-based gate. Conditional guarantees — 'If you complete all modules, submit all assignments, and do not see [specific result]' — dramatically reduce exploitation while maintaining credibility with genuine buyers. The Guarantee Exploiter teaches you exactly which condition to add.",
"",
"",
"PHASE 1",
"Data Collection & Signal Sources",
"Where Negative Avatar evidence lives and how to extract it",
"",
"The Eight Signal Sources",
"Negative Avatar data does not come from one place. It is distributed across every customer touchpoint in your business. The system below ensures no signal goes unread.",
"",
"Source",
"What to Mine",
"Archetype It Most Commonly Reveals",
"Collection Method",
"Refund request messages",
"Verbatim language describing why the offer failed to meet expectations. The most direct source of wrong-fit evidence.",
"Archetype 01 (Wrong-Problem) and Archetype 03 (Mismatched Stage)",
"Log verbatim in Airtable within 24 hours. Tag with archetype code. Never paraphrase.",
"Support ticket patterns",
"Volume, topic clusters, and emotional tone of all support tickets per buyer. Disproportionate volume from a single buyer is the primary Vampire Client signal.",
"Archetype 04 (Vampire Client) and Archetype 01 (Wrong-Problem)",
"Weekly tag audit in Intercom or Help Scout. Flag any buyer with 5+ tickets in 14 days.",
"Sales call recordings",
"Objections that were overcome but probably should not have been. The buyer who bought despite a red-flag objection is a Negative Avatar in waiting.",
"Archetype 01, 03, and early Archetype 02 signals",
"Review 100% of sales call recordings for buyers who later refund. Tag the objection that preceded the sale.",
"Application form responses",
"Answers that reveal mismatched stage, wrong problem, or unrealistic expectations before purchase. The pre-purchase filter.",
"Archetype 03 (Mismatched Stage) primary detection point",
"Weekly review of all application submissions. Score against the Qualification Rubric (see Phase 3).",
"Onboarding survey responses",
"Baseline situation statements that reveal who actually bought vs. who you thought was buying. Compare baseline to your intended avatar profile.",
"Archetype 01 and Archetype 03",
"Flag responses where the situation described does not match your positive avatar profile. Review within 48 hours of submission.",
"Community engagement patterns",
"Dropout (Archetype 02), conflict escalation (Archetype 04), and topic mismatch (Archetype 01) all manifest in community behaviour before they appear in support tickets.",
"Archetype 02 (Passive Consumer) and Archetype 04 (Vampire Client)",
"Weekly community audit: flag accounts with zero posts after 14 days (dropout signal) and accounts with 3+ conflict interactions.",
"Exit interview transcripts",
"The most information-rich single source. Buyers who did not get results will describe exactly why — often identifying the mismatch themselves if asked the right questions.",
"All five archetypes",
"Castmagic transcript. Highlight every sentence describing what they expected vs. what they found.",
"Stripe/payment refund history",
"Pattern detection across multiple buyers. Time-to-refund, purchase day within launch window, and refund reason clustering reveal the Guarantee Exploiter pattern.",
"Archetype 05 (Guarantee Exploiter)",
"Monthly refund report. Flag any account with purchase in last 3 days of launch + refund in last 2 days of guarantee window.",
"",
"",
"PHASE 2",
"The Negative Avatar Profile Template",
"Building a complete, actionable profile for each archetype found in your data",
"",
"When to Build a New Profile",
"A new Negative Avatar Profile is created when the same archetype pattern appears three or more times within any 60-day period from buyers of the same offer. A single instance is noise. Three instances from the same root cause signal a systematic problem in targeting, copy, or delivery that requires a documented response.",
"",
"The Pattern Threshold Rule",
"One refund is an event. Two refunds with similar language is a coincidence. Three refunds citing the same root cause within 60 days is a pattern — and patterns get a Negative Avatar Profile and a specific remediation action. Do not wait for more evidence than three.",
"",
"The Negative Avatar Profile Template",
"Complete one of these for every pattern that crosses the three-instance threshold. File in Airtable under Negative Avatars table. Link to the offer and the specific refund or dropout records that triggered its creation.",
"",
"Profile Field",
"What to Document",
"Example",
"Profile ID",
"Autonumber + offer abbreviation + archetype code",
"MVO-01-A01 (first Wrong-Problem profile for MVO-01)",
"Archetype code",
"01–05 from the five archetypes above",
"A01 — Wrong-Problem Buyer",
"Character name",
"Give this profile a memorable name for internal reference. The name should capture the essence of the mismatch.",
"'The Adjacent Niche Buyer' or 'The One-Step-Earlier Operator'",
"Date pattern detected",
"Date the third instance was logged, triggering profile creation",
"2026-03-15",
"Number of instances (at creation)",
"Count of buyers matching this pattern within the detection window",
"3 refunds within 47 days",
"Verbatim trigger phrase",
"The exact phrase — 3 to 8 words — that appears in the refund or dropout data most consistently for this profile. This is the primary copy signal.",
"'Not what I was looking for' / 'Thought this covered X'",
"Entry point",
"Which ad, email, or content piece most commonly preceded the wrong-fit purchase. The copy that attracted the wrong buyer.",
"Meta ad targeting 'course creators' — too broad; includes creators whose core problem is not offer construction",
"The mismatch anatomy",
"In one sentence: why this buyer and this offer are a mismatch. Not their fault. Not the offer's fault. A structural incompatibility.",
"This buyer needs audience building before they need offer construction. They have no list to sell to and the offer assumes one exists.",
"What they actually need",
"The offer that would have served them correctly — whether you have built it yet or not.",
"A traffic and list-building offer — currently Tier 0/1 in the value ladder. Not yet built.",
"Sales page anti-language",
"Words or phrases currently on the sales page that are attracting this profile. These must be audited and potentially removed or reframed.",
"'Course creators' in ad copy — replaced with 'course creators with an existing audience above 1,000 subscribers'",
"'Not for you if' addition",
"The specific bullet point to add to the 'This is NOT for you' section of the sales page as a direct result of this profile.",
"This is NOT for you if you are still building your first audience and have not yet had any paying customers.",
"Targeting exclusion",
"The specific ad audience characteristic to exclude, or the application form question to add, that would have screened this buyer before purchase.",
"Exclude interest targeting: 'content creation' and 'blogging'. Add application question: 'How many paying customers have you had in the last 90 days?'",
"Status",
"Open (pattern continuing) / Remediated (fix deployed) / Closed (no new instances in 90 days)",
"Open",
"",
"",
"PHASE 3",
"Pattern Recognition & Classification",
"Turning raw data into structured profiles",
"",
"The Weekly Classification Ritual",
"Pattern recognition requires a consistent weekly pass through all negative signal sources. This ritual takes 20–30 minutes and prevents the accumulation of unread signals that makes pattern detection impossible.",
"",
"1. Pull all new refund messages from Airtable Refund Records. Read each verbatim. Assign archetype code. Look for phrase overlap with existing profiles.",
"2. Pull all support tickets flagged in the past 7 days. Count tickets per buyer. Flag any buyer with 5+ tickets in 14 days for Archetype 04 review.",
"3. Scan community for zero-engagement accounts (no posts or comments in 14+ days after an initial welcome post). Add to Archetype 02 passive tracker.",
"4. Review any sales call recordings from buyers who refunded in the past 7 days. Tag the objection that preceded the sale.",
"5. Check pattern counts on all Open profiles. If any profile hits 3 new instances this week: trigger the Remediation Protocol (Phase 5).",
"",
"The Qualification Rubric for Application Forms",
"For offers above $497, an application form is the primary Negative Avatar screening mechanism. The Qualification Rubric below scores each application against the specific mismatches your active Negative Avatar Profiles describe. Applications scoring below the threshold are declined or directed to a lower-tier offer.",
"",
"Qualification Dimension",
"Screening Question",
"Green Flag (Score 2)",
"Amber Flag (Score 1)",
"Red Flag (Score 0)",
"Problem specificity",
"Describe the specific problem you are trying to solve in one sentence.",
"Describes a specific, narrow problem that your offer directly solves",
"Describes a broad category that your offer partially addresses",
"Describes a problem your offer does not solve or a different problem category entirely",
"Stage readiness",
"What have you already tried to solve this? What happened?",
"Has tried and exhausted alternatives. Has skin in the game. Has some prior result.",
"Has researched but not yet implemented anything. No prior attempt.",
"Has not identified the problem as actionable yet. Describes a future state not a current problem.",
"Implementation capacity",
"How much time per week can you dedicate to this work for the next 60 days?",
"States a specific number of hours above your minimum threshold",
"States a number at or slightly below threshold but with a credible explanation",
"States a number that makes completion of your programme impossible, or gives a non-answer",
"Financial alignment",
"Are you aware this is a [price] investment and are you in a position to make that decision today?",
"Yes, directly and without hesitation",
"Yes, but with a question about payment plans — not a concern, a logistics question",
"Dodges the question, asks about refund policy before asking about the programme, or indicates the price is a stretch",
"Outcome specificity",
"What does success look like to you 90 days from now?",
"States a specific, measurable outcome that your offer can credibly deliver",
"States a directional outcome without specific metrics — achievable but vague",
"States an outcome your offer cannot deliver in the timeframe or describes a transformation your offer does not produce",
"",
"Scoring: 10 = ideal candidate. 7–9 = qualified with follow-up question. 4–6 = redirect to lower-tier offer with explanation. Below 4 = decline with dignity and direction to appropriate resource.",
"",
"Sales Call Red Flag Protocol",
"Some Negative Avatars pass the application form but reveal themselves on the sales call. These five red flags indicate a mismatch that should not be sold through — they should be declined kindly and redirected.",
"",
"Red Flag Signal",
"What It Reveals",
"Correct Response on Call",
"'Will this work even if I don't have [prerequisite your offer assumes]?'",
"Mismatched Stage — Archetype 03 Too Early. They lack something fundamental your offer is built upon.",
"'I want to be honest with you — this offer is designed for people who already have [prerequisite]. Without that, you won't get the result we promise. Here's what I'd recommend first...'",
"'What happens if I need more support than what's included?'",
"Early Vampire Client signal — Archetype 04. Testing boundaries before purchasing.",
"Describe the support structure clearly and specifically. Ask: 'Does that feel like enough for you?' If hesitation: 'Our 1:1 programme might be a better fit — let me describe that option.'",
"'Can you show me the refund policy again?'",
"Either Guarantee Exploiter (Archetype 05) or a buyer with genuine uncertainty. Distinguish by context.",
"If asked as the first or second question: proceed with caution. Describe the conditional guarantee clearly and state what completion requires. If they lead with refund questions on a call, they are not ready to commit.",
"'I've bought a few courses on this topic but haven't implemented any of them.'",
"Strong Passive Consumer signal — Archetype 02. Purchases are a substitute for implementation for this buyer.",
"'I appreciate your honesty. Before I'd feel good about taking your money, I'd like to understand what stopped you from implementing the others. Because this programme requires [specific action] in week one.' Only proceed if they give a credible, non-pattern answer.",
"'I just need someone to tell me what to do.'",
"Can be either the right buyer (Executive Buyer who wants clear direction) or the Passive Consumer variant who expects the programme to create action on their behalf. Probe further.",
"'Tell me what that looks like for you — when you say someone tells you what to do, do you mean a clear step-by-step system, or do you mean you need someone to do the work with you?' The answer reveals whether they need your offer or a done-for-you service.",
"",
"",
"PHASE 4",
"The Repulsion System",
"Keeping the wrong buyer out — before they cost you anything",
"",
"The Repulsion System Architecture",
"A complete repulsion system has five layers. Each layer catches a different archetype at a different stage of the buyer's journey. The goal is not to be hostile — it is to be so specific about who this offer is for that the wrong buyer self-selects out before purchase.",
"",
"Layer",
"Where It Lives",
"Primary Archetype Caught",
"Mechanism",
"Layer 1 — Ad targeting exclusion",
"Paid ad campaign settings",
"Archetype 01 (Wrong-Problem)",
"Exclude specific interest categories, job titles, and lookalike audiences that have produced wrong-fit buyers. Add negative keywords to Google and YouTube campaigns.",
"Layer 2 — Sales page 'Not for you' section",
"Below the offer stack, above the guarantee",
"Archetypes 01, 02, and 03",
"A specific list of 4–6 statements beginning with 'This is NOT for you if...' Each bullet maps directly to an active Negative Avatar Profile.",
"Layer 3 — Anti-language audit",
"All copy across sales page, email sequence, and ads",
"Archetype 01 (Wrong-Problem) primary",
"Remove or reframe any word or phrase in active Negative Avatar Profile anti-language fields. These words are attracting the wrong buyer by signalling a broader category than you serve.",
"Layer 4 — Application form qualification",
"Offer pages above $497 and all high-ticket tiers",
"Archetypes 03 and 04",
"The Qualification Rubric from Phase 3. Any application scoring below 7 is redirected before any human time is invested.",
"Layer 5 — Sales call screening",
"Discovery and strategy calls",
"Archetypes 03, 04, and 05",
"The Red Flag Protocol from Phase 3. Any call that produces two or more red flags is declined with a specific redirection.",
"",
"Writing the 'This is NOT for You' Section",
"This is the single most important piece of repulsion copy on your sales page. It serves two functions simultaneously: it filters out wrong-fit buyers, and it dramatically increases trust with right-fit buyers by demonstrating that you know exactly who you are not serving. Here is the framework for writing it.",
"",
"Structure and Format Rules",
"• Write 4–6 bullets only. More than 6 weakens the specificity of each one.",
"• Each bullet maps directly to one active Negative Avatar Profile. Do not invent bullets — derive them from real data.",
"• Write in plain, non-judgmental language. You are describing a mismatch, not an insult.",
"• Lead each bullet with the specific condition, not a character flaw. 'If you have not yet had your first paying customer' not 'If you are a beginner.'",
"• End the section with one sentence that redirects: 'If any of the above describes you, [specific alternative] is likely a better fit.'",
"",
"Example 'Not for You' Section (Template)",
"",
"This is NOT for you if...",
"• You are still building your first audience and have not yet had a paying customer — this offer assumes you have proof that someone will pay you for something.\n\n• You are looking for someone to do the work for you — this is a hands-on implementation programme that requires 4–6 hours per week of your personal effort.\n\n• You have already built and launched a core offer generating above $10K/month — the methods here are designed for the $0–$10K validation stage, not the scaling stage.\n\n• You are in a rush to launch in the next 7 days — the framework takes 30 days to implement correctly and shortcuts produce bad data.\n\n• You have purchased more than two similar programmes in the last 12 months without implementing them — this will produce the same result unless something in your circumstances has fundamentally changed.\n\nIf any of the above describes your situation, the RISER Nation Tracks 1–3 Foundation bundle is likely a better starting point.",
"",
"The Anti-Language Audit Protocol",
"Anti-language is any word or phrase in your copy that attracts the wrong buyer by signalling a broader category, a different problem, or a different buyer stage than your offer serves. Running this audit quarterly — and immediately after any new Negative Avatar Profile is created — prevents ongoing wrong-buyer acquisition.",
"",
"1. Pull the 'Sales page anti-language' field from every Open Negative Avatar Profile in Airtable.",
"2. Run a Find & Replace search for each phrase across: sales page, all active email sequences, all live ad creatives, and all landing pages.",
"3. For each instance found: decide whether to remove the phrase entirely or reframe it with a specific qualifier.",
"4. Document every change in Airtable under the relevant Negative Avatar Profile record — date, what changed, where.",
"5. Schedule a conversion rate comparison 30 days after each anti-language audit. The repulsion change should not reduce overall conversion meaningfully if it is filtering the right buyers.",
"",
"The Conversion Rate Paradox",
"When you first run the anti-language audit and add 'Not for you' copy, your conversion rate on ad traffic may drop 5–15%. This is the system working correctly — you are filtering out buyers who would have purchased and then refunded. Your actual net revenue after refunds typically increases within 30 days. Track net revenue, not gross conversion rate, when evaluating repulsion system effectiveness.",
"",
"",
"PHASE 5",
"The Positive Extraction Protocol",
"Every Negative Avatar teaches you something specific — extract it",
"",
"The Intelligence Each Archetype Carries",
"This is the most overlooked dimension of Negative Avatar work. Most operators use wrong-fit buyer data only defensively — to keep bad buyers out. The same data, read with a different lens, is one of the most valuable product development and copy improvement inputs available.",
"",
"Archetype",
"The Defensive Use (Repulsion)",
"The Offensive Use (Product Intelligence)",
"Specific Action Triggered",
"A01 — Wrong-Problem Buyer",
"Remove copy that attracts the wrong category. Tighten ad targeting.",
"Reveals demand for an adjacent offer that solves their actual problem. If three or more Wrong-Problem buyers share the same alternative need, that need is your next product signal.",
"Open a 'Problem B' card in the Product Roadmap for the problem this archetype actually needed solved.",
"A02 — Passive Consumer",
"Add completion accountability to onboarding. Create a stronger Quick Win in module 1.",
"Reveals that your onboarding does not create enough urgency or identity shift at purchase. The best fix is not more content — it is a better Day 1 experience that makes implementation feel inevitable.",
"Rebuild the welcome sequence with a 72-hour implementation challenge. 'Your first result in 72 hours or tell me what stopped you.'",
"A03 Too Early — Mismatched Stage",
"Add prerequisite language to sales page. Add stage-qualification question to application form.",
"Reveals an unserved earlier-stage market. If there are consistently buyers who are 6 months too early for your current offer, the gap between 'zero' and your MVO is a product waiting to be built.",
"Create a 'Prerequisites Offer' — the entry-level product that gets them to the starting line of your MVO.",
"A03 Too Late — Mismatched Stage",
"Add 'Not for you if you already have X' to sales page.",
"Reveals that there is a more advanced buyer segment who needs your next-level offer. This is your clearest signal that Tier 4 (High-Ticket) or an advanced Core Offer variant should be prioritised.",
"Open a 'Advanced Buyer' product brief. Run 5 exit interviews with Too-Late buyers asking: 'What would you have needed instead?'",
"A04 — Vampire Client",
"Add support structure clarity to sales page. Price the 1:1 tier correctly.",
"Reveals unmet demand for higher-access tiers that are not correctly priced or positioned. Vampire Clients are often willing to pay significantly more for appropriate access — they just could not find it in your offer wall.",
"Audit your high-ticket and DFY tiers. The Vampire Client is the right-fit buyer for a tier you have not yet built or priced correctly.",
"A05 — Guarantee Exploiter",
"Add conditional language to guarantee. Add completion requirements.",
"Reveals that your guarantee language lacks the specificity needed to distinguish genuine-effort buyers from exploiters. The conditional rewrite that stops exploiters also increases perceived credibility with genuine buyers — because specific conditions imply a confident offer.",
"Rewrite guarantee from unconditional to conditional. State the exact completion requirements needed to qualify for a refund.",
"",
"",
"PHASE 6",
"Offer Design Integration",
"Using Negative Avatar data to build better offers from the ground up",
"",
"The Pre-Offer Negative Avatar Brief",
"Every new offer — before a single module is designed or a word of copy is written — should have a Negative Avatar Brief completed alongside the Positive Avatar profile. The brief documents the three archetypes most likely to be attracted to this offer category and the specific design decisions that will pre-empt them.",
"",
"Brief Element",
"What to Define",
"Example (for an offer on organic content strategy)",
"Most likely wrong-fit archetype 1",
"Which archetype will this offer category most commonly attract by mistake, and why?",
"A01 — Wrong-Problem: People who need paid ads, not organic content. Attracted by 'get more clients' language that applies to both channels.",
"Most likely wrong-fit archetype 2",
"Second most likely archetype and its attraction mechanism.",
"A03 Too Early: People with no existing content platform or audience. Attracted by 'start from scratch' language that implies zero prerequisites.",
"Prerequisites to state explicitly",
"What must a buyer already have for this offer to work as promised?",
"A social media profile with at least 6 months of consistent posting history and at least 200 followers. Some prior experience with content creation.",
"Support capacity design",
"Based on expected archetype mix, how many support interactions per buyer per week is your delivery model designed for?",
"Maximum 2 support tickets per week per buyer. Vampire Client protocol triggers at 5+ tickets in any 14-day window.",
"Guarantee design",
"Given the most likely archetype mix, what guarantee language protects against exploitation while remaining credible?",
"Conditional: 'If you post the required 3x per week for 30 days and do not see at least 15% growth in profile engagement, we will refund in full.'",
"'Not for you' bullets (draft)",
"Write 4 'Not for you' bullets directly from the identified archetypes before launch.",
"1. If you have not posted consistently for at least 3 months. 2. If your primary acquisition channel is or needs to be paid ads. 3. If you are not prepared to post 3 times per week during the programme. 4. If you are looking for growth shortcuts — every strategy here takes 30+ days to produce data.",
"",
"The Delivery Design Implication",
"The most common delivery design mistake is building a programme for the Positive Avatar and then being surprised when the wrong-fit buyer's needs are not served. Once you have documented the most likely wrong-fit archetypes for a new offer, make these specific delivery design decisions before building:",
"",
"Archetype Risk",
"Delivery Design Decision",
"Implementation",
"A02 Passive Consumer risk is high",
"Build accountability into the first 72 hours, not as a feature — as a requirement. The first action item must be completable in under 20 minutes and must produce a visible output.",
"Module 1 ends with: 'Post your output in the community with the tag #Week1Win. You have 72 hours.' Community manager checks and personally tags any non-posters at hour 48.",
"A03 Too Early risk is high",
"Add a pre-programme self-assessment that evaluates prerequisite completion. Make it ungated but visible — buyers should encounter it before purchase and ideally before opting into the lead magnet.",
"Landing page addition: '2-minute readiness check' that scores their current situation against 5 prerequisites. Shows them their readiness score and tells them what to do if below threshold.",
"A04 Vampire Client risk is high",
"Define support access with extreme specificity in the sales copy and onboarding materials. The access ambiguity that creates Vampire Clients must be removed before purchase.",
"Onboarding email paragraph 3: 'Here is exactly what support looks like in this programme: [specific hours, specific response time, specific channels, specific escalation path]. This is intentionally bounded — it is what allows us to deliver quality to every member equally.'",
"A05 Guarantee Exploiter risk is high",
"Design completion checkpoints that are simple to complete for genuine buyers and inconvenient to game for exploiters.",
"Completion requirements for guarantee eligibility: submit module completion confirmations through the platform (timestamped), post in community at milestone points (timestamped and public), complete the exit survey. These are trivial for genuine buyers and require meaningful effort to fake.",
"",
"",
"PHASE 7",
"Ad Targeting & Exclusion Integration",
"Turning Negative Avatar data into paid media precision",
"",
"From Profile to Exclusion Audience",
"Every active Negative Avatar Profile should produce at least one paid media targeting exclusion or negative keyword. This is the most direct revenue impact of Negative Avatar work — it reduces cost per acquisition by eliminating spend on audiences that produce wrong-fit buyers.",
"",
"Platform",
"Exclusion Mechanism",
"Negative Avatar Application",
"How to Implement",
"Meta Ads",
"Custom audiences (upload buyer list), interest exclusions, and lookalike exclusion",
"Upload all refund records as a suppression list to prevent re-acquisition. Exclude interest categories identified in A01 profiles. Create a 'bad buyer lookalike' from refund list to identify and exclude similar profiles.",
"Ads Manager → Audiences → Custom Audience → Customer list. Upload email list of all buyers who refunded with RC-1 or RC-3 codes. Create 1% lookalike to exclude.",
"Google / YouTube Ads",
"Negative keyword lists and audience exclusions",
"Add negative keywords from A01 anti-language audit. These are the search terms that attract wrong-problem buyers.",
"Google Ads → Shared Library → Negative keyword lists. Create 'Wrong Avatar' list from all anti-language phrases identified in active profiles.",
"TikTok Ads",
"Custom audience exclusion and interest negative targeting",
"Upload refund list as suppression. Exclude content creator interests if A01 data shows content creators are a mismatch.",
"TikTok Ads Manager → Audience → Custom Audience → Customer file. Upload and set as exclusion.",
"LinkedIn Ads",
"Job title exclusions and company size exclusions",
"If A03 (Too Early) buyers consistently come from companies below a certain size or from specific job titles, exclude these in targeting.",
"Campaign Manager → Audience → Exclusions → Job Titles. Build the exclusion list from A03 profile entry point data.",
"Retargeting audiences",
"Event-based exclusions",
"Exclude page visitors who spent less than 90 seconds on the sales page (bounce behaviour associated with wrong-fit visitors who did not engage with the 'Not for you' section).",
"GA4 → Audience → Create audience based on time on page event. Exclude from retargeting in all platforms.",
"",
"The 30-Day Exclusion Audit",
"Once per month, run this protocol to ensure your exclusion audiences are current and your negative keyword lists reflect the latest anti-language data from new profiles.",
"",
"1. Pull all refund records from the past 30 days. Upload any new email addresses to suppression lists on all active ad platforms.",
"2. Review all new Negative Avatar Profiles created in the past 30 days. Extract any new anti-language phrases. Add to negative keyword lists.",
"3. Review the entry point field in all Open profiles. If a specific ad, audience, or campaign is consistently producing wrong-fit buyers, pause that ad or refine that audience.",
"4. Check Cost Per Acquisition (CPA) comparison: buyers acquired from excluded audiences (before exclusion was added) vs. buyers acquired after exclusion. Document the delta.",
"",
"",
"PHASE 8",
"The Ongoing Review Cadence",
"Keeping the system live, current, and compounding",
"",
"The Cadence Calendar",
"Frequency",
"Activity",
"Time Required",
"Output",
"Daily (ongoing)",
"Process any new refund request through the 5-step Refund Forensics Protocol from the Post-MVO Forensic Audit Loop SOP. Archive verbatim. Assign archetype code.",
"5–10 min per refund",
"Refund archive entry. Pattern count updated.",
"Weekly (Mondays — 20 min)",
"Run weekly classification ritual: review all new support tickets, refunds, and community signals. Update pattern counts on Open profiles. Check for any profile crossing 3-instance threshold.",
"20 minutes",
"Pattern counts updated. New profiles created if threshold crossed.",
"Weekly (Thursdays — 15 min)",
"Review all new application form submissions against the Qualification Rubric. Score and route: approve, follow-up question, redirect, or decline.",
"15 minutes",
"Application decisions documented. Any new A03 or A04 signals noted.",
"Monthly (first Monday)",
"Full Negative Avatar database review. Close any profiles with zero new instances in 90 days. Check all Open profiles for remediation effectiveness. Run anti-language audit against all active copy.",
"60–90 minutes",
"Database cleaned. Remediated profiles moved to Closed. Anti-language copy updates queued.",
"Quarterly",
"Full repulsion system audit: review 'Not for you' section against active profiles, re-run Qualification Rubric calibration, review all ad exclusion audiences, check CPA delta since last exclusion update.",
"Half day",
"Repulsion System Update Report. Action brief for copy and targeting changes.",
"After every new offer launch",
"Complete a Negative Avatar Brief before the first sale. Update as first buyers are acquired. Create profiles at 3-instance threshold — which may arrive faster for new offers.",
"2 hours pre-launch + ongoing",
"Pre-launch Negative Avatar Brief filed in Airtable. First profiles created within 30 days of launch.",
"",
"",
"The Negative Avatar Database — Airtable Schema",
"All Negative Avatar data lives in four linked tables within the same Airtable base as the Post-MVO Forensic Audit Loop system. The schema below ensures every profile, every instance, and every remediation action is connected and searchable.",
"",
"Table 1 — Negative Avatar Profiles",
"One record per confirmed pattern (3+ instances). The master reference document for each archetype found in your data.",
"",
"Field",
"Type",
"Notes",
"Profile ID",
"Autonumber",
"Auto-generated. Format: [Offer]-[Seq]-A0[1-5]",
"Character name",
"Short text",
"Internal reference name — descriptive, memorable",
"Archetype code",
"Single select",
"A01 through A05",
"Offer",
"Link → Offers table",
"Which offer this profile relates to",
"Date created",
"Date",
"Date the 3rd instance was logged",
"Instance count",
"Number",
"Updated weekly — total instances logged",
"Verbatim trigger phrase",
"Long text",
"Most consistent 3–8 word phrase from the data",
"Entry point",
"Long text",
"Ad, email, or content piece most commonly preceding purchase",
"Mismatch anatomy",
"Long text",
"One-sentence structural description of why buyer and offer are misaligned",
"What they actually need",
"Long text",
"The offer that would have served them correctly",
"Sales page anti-language",
"Long text",
"Specific phrases to audit and remove or reframe",
"Not for you addition",
"Long text",
"The exact bullet to add to the 'Not for you' section",
"Ad targeting exclusion",
"Long text",
"Specific audience or keyword exclusion to implement",
"Application form change",
"Long text",
"Question to add or threshold to adjust on application form",
"Remediation date",
"Date",
"Date the fix was deployed across all affected assets",
"Status",
"Single select",
"Open / Remediated / Closed",
"Linked refund records",
"Link → Refund Records",
"All refunds that contributed to this profile",
"",
"Table 2 — Refund Records",
"One record per refund. Already defined in the Post-MVO Forensic Audit Loop SOP — link to that table. Add a Negative Avatar Profile link field to connect refund records to the profiles they inform.",
"",
"Table 3 — Application Scoring Log",
"One record per application form submission for offers above $497.",
"",
"Field",
"Type",
"Notes",
"Application ID",
"Autonumber",
"",
"Date submitted",
"Date",
"",
"Offer applied for",
"Link → Offers table",
"",
"Rubric score",
"Number",
"0–10 from the Qualification Rubric",
"Dimension scores",
"Long text",
"Individual scores for each of the 5 rubric dimensions",
"Decision",
"Single select",
"Approved / Follow-up question / Redirected / Declined",
"Redirect destination",
"Short text",
"If redirected — which offer or resource were they directed to",
"Negative Avatar signals",
"Link → Profiles",
"If any archetype signals identified — link to relevant profile",
"",
"Table 4 — Repulsion System Changelog",
"One record per change made to any copy, targeting, or delivery design as a result of a Negative Avatar Profile. Enables before/after tracking.",
"",
"Field",
"Type",
"Notes",
"Change ID",
"Autonumber",
"",
"Date deployed",
"Date",
"",
"Triggered by",
"Link → Profiles",
"Which Negative Avatar Profile triggered this change",
"Asset changed",
"Single select",
"Sales page / Email sequence / Ad copy / Application form / Onboarding / Delivery design / Ad targeting",
"What was changed",
"Long text",
"Specific before and after — verbatim if copy, audience description if targeting",
"Conversion rate before",
"Number",
"Record the relevant metric before the change",
"Conversion rate after (30 days)",
"Number",
"Filled in 30 days after deployment",
"Net revenue impact",
"Number",
"Gross conversion delta adjusted for refund rate change",
"",
"",
"Master Negative Avatar Modelling Checklist",
"",
"System Setup (One-Time)",
"☐ Create Negative Avatar Profiles table in Airtable with all fields from the schema above",
"☐ Create Application Scoring Log table and link to Offers table",
"☐ Create Repulsion System Changelog table",
"☐ Link all existing Refund Records to new profiles table via lookup field",
"☐ Run anti-language audit on all current live sales pages — flag any words matching existing buyer complaints",
"☐ Add 'This is NOT for you' section to all active offer sales pages using real buyer language",
"☐ Set up Meta, Google, TikTok suppression audiences — upload current refund email list",
"",
"Every New Offer (Pre-Launch)",
"☐ Complete Negative Avatar Brief: identify 2 most likely archetypes before first sale",
"☐ Write 4 'Not for you' bullets based on pre-identified archetypes",
"☐ Design conditional guarantee language that specifies completion requirements",
"☐ Build application form with Qualification Rubric questions for offers above $497",
"☐ Onboarding email paragraph 3: state support structure with specific boundaries",
"☐ Onboarding Day 1 action: must be completable in under 20 minutes with a visible output",
"",
"Weekly Ritual",
"☐ Process all new refunds: archive verbatim, assign archetype code, update pattern counts",
"☐ Review all support tickets: flag any buyer with 5+ tickets in 14 days (A04 signal)",
"☐ Scan community: flag zero-engagement accounts after day 14 (A02 signal)",
"☐ Score all new application submissions against Qualification Rubric",
"☐ Check all Open profiles: has any crossed 3 new instances this week? If yes — trigger Remediation Protocol",
"",
"Monthly",
"☐ Full database review: close profiles with zero new instances in 90 days",
"☐ Run anti-language audit: pull all Open profile anti-language fields and sweep all live copy",
"☐ 30-day exclusion audit: update all ad platform suppression lists and negative keyword lists",
"☐ Check Repulsion System Changelog: fill in 30-day conversion rate and net revenue figures for all changes deployed last month",
"☐ Review 'Not for you' sections: are all active profiles represented? Any new bullet required?",
"",
"Quarterly",
"☐ Full repulsion system audit: review every layer against current active profiles",
"☐ Qualification Rubric calibration: compare approved-vs-declined outcomes. Is the rubric catching the right patterns?",
"☐ Check CPA delta since last exclusion update — document in Repulsion System Changelog",
"☐ Compile Negative Avatar Quarterly Report: total profiles, remediated profiles, net revenue impact of repulsion system",
"☐ Brief product team on any 'What they actually need' signals that cross the 5-instance threshold — these are product development priorities",
"",
"",
"",
"RISER Nation Master Operating System | Negative Avatar Modelling SOP | Version 1.0 | 2026 Edition",
"Kennedy × Hormozi × Brunson | risernation.com"
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"RISER Nation | Negative Avatar Modelling SOP | V1.0"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE of NUMPAGES"
]
},
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Write clear training that helps a first-time builder act
Start with the reader's next action
Imagine a new builder reading after a full workday. This is an illustrative scene. One lesson sounds impressive but gives no clear next step. Another explains the task, shows an example and names the work to submit.
The gap is between sounding expert and helping someone act. This lesson teaches the Voice Specification's full set of writing rules. It also explains where its examples and instructions need care.
The source's central reader is a forty-five-year-old career changer. They have no coding or online-business background. They can be smart, accomplished and tired at once. Write so they feel capable after reading. Don't mistake simple language for shallow teaching.
Voice drift happens when different writers sound like different brands. Hype can also split the sales page from the training. A shared voice specification connects the two. The source assigns ownership to the founder and custody to the content director. These are its proposed roles, not evidence of a completed review.
The source attributes three broad traits to its core influences. Kiyosaki represents readable stories and dialogue before a framework. Kennedy represents purposeful paragraphs, clear offers, practical consequences and belief in the reader's ability. Hormozi represents concrete examples, numbers and defined patterns. Teach those general traits in RISER's own voice.
Brunson, Ogilvy, Hopkins and Cialdini are additional framework influences. The source places them in legacy course labels. Your current spreadsheet governs the actual twelve courses and forty-nine lessons. Keep Brunson/ClickFunnels and Hormozi/Acquisition.com teaching where it belongs. This voice document does not remove it.
Voice differs from three other tools. A brand book covers colors, logos and type. Content strategy assigns topics, channels, people and timing. Copy frameworks such as AIDA, PAS, Hook–Story–Offer and the Epiphany Bridge organize persuasion. The voice specification controls how that teaching sounds. It does not supply all those frameworks here.
Use readability targets without deleting necessary teaching
The source gives these targets and rewrite rules:
Measure
Target
Source rewrite rule
Flesch Reading Ease
70–85
Below 65
Flesch–Kincaid grade
5.0–6.5
Above 7.5 in the table; grade 7 or higher in later prose
Sentence length
Average 9–14 words
Split or rewrite sentences of 20 or more words
Paragraph length
2–4 sentences
Split paragraphs of 5 or more sentences
Word length
Average under five letters
Rewrite clusters of long words
Passive voice
Under 8% of sentences
Rewrite above 12%
The four-test checklist later asks for average paragraphs under four sentences. Its sentence test asks for an average under fifteen words. Preserve these differences in review notes. Choose and record the actual measurement method. Don't claim a readability grade without running a measurement. A tool score also does not prove comprehension.
The source recommends Hemingway Editor or an equivalent for module bodies and sales pages. That is a review recommendation, not a completed test. Its rationale is respect for a busy reader. Its book-sales figure and numerical grades attached to examples are unverified source claims, not evidence for this lesson. The source also calls fifth grade two grades below eighth grade; the difference is three grades.
Practice the five-step sentence edit. Write the thought first. Count its words. Above fourteen words, look for a conjunction or comma. Try splitting there. Read both sentences aloud and restructure any awkward fragments.
The source's long identity example describes tactical work, strategic clarity and the choice between building and merely hoping. Its revision breaks that thought into short statements and a direct question. The lesson is useful even though its word-count and grade annotations are not certified. Preserve the exact pair in the appendix; don't repeat its annotations as measured results.
Use white space between short paragraphs. It gives the reader a place to pause. Keep every distinct source point by adding well-organized sections when needed. The later 600–1,200-word module target is a style preference. It cannot justify omitting assigned material.
Replace empty language with a specific claim
The source has five ban categories. Learn what each category is trying to prevent. Terms quoted for analysis or preserved in originals must remain visible; a ban check must not erase evidence.
Corporate language: synergy; leverage as a verb; unlock; scale as a verb without an object; transform; optimize without a metric; holistic; paradigm; ecosystem unless literal; bandwidth; double-click; ideate; learnings; deep-dive; low-hanging fruit; move the needle.
Empty intensifiers: literally, absolutely, completely, totally, basically, essentially, fundamentally, ultimately, frankly, and honestly as a sentence opener.
Hype language: crush it, unlock your potential, secret, hack, ninja, rockstar, game-changer, life-changing, revolutionary, disruptive except its legacy C 11 context, insane, mind-blown, level up, 10 x your, blueprint instead of plan, and proven without attached proof.
Formulaic AI phrases: delve; in today's fast-paced world; the digital landscape; navigating the complexities; embark on a journey; harness the power; unleash; in conclusion; it is important to note; furthermore; moreover; in essence; this article will explore.
Empty reassurance: don't worry; don't beat yourself up; you've got this; you can do anything you set your mind to; dream big; the sky is the limit.
Don't start by finding a synonym. Ask what the sentence actually claims. Replace vague improvement with a named task or measured result. Avoid inventing a number merely to sound specific.
The required vocabulary has five groups. Use these words when they help explain the work, not as a quota:
Identity: operator, builder and founder. The source discourages entrepreneur, imprecise marketer and creator where operator is meant.
Stages: harbor, sailboat, speedboat, yacht, ship, fleet and harbormaster. Explain any stage before using it as navigation. These labels don't change spreadsheet assignments.
Doctrine: mismatch, reduce mismatches, empirical floor, defer, defer without shame, pass, rework, graduation gate, proof and capstone.
Discipline: ship, deploy, hand in, turn in, capstone deliverable, signed testimonial, refund analysis, validated price and documented outcome.
Lineage: Hormozi, Brunson, Kennedy, Kern, Ogilvy, Hopkins and Cialdini. Name the actual source of an identified framework. Don't imply endorsement.
Define technical terms at first use
Use a plain-language definition in the same paragraph. Short emails and posts also need that first-use explanation. The source's nine examples are:
Term
Plain-language explanation and needed limit
LTV
Lifetime value. The source measures all dollars a customer pays during the relationship. State that this is revenue-based; other analyses use contribution or profit.
CAC
Customer acquisition cost. The source describes marketing cost to gain a buyer. State which costs your calculation includes.
AOV
Average order value: total order revenue divided by the relevant order count.
MRR
Monthly recurring revenue. The source illustrates it with continuity memberships; define the recurring revenue included.
AEO
Answer engine optimization: making content clear and useful for answer systems. It cannot ensure that a system quotes it.
GEO
Generative engine optimization: work intended to improve discovery and representation in generated answers. It cannot ensure trust or citations.
MCP
Model Context Protocol: a protocol connecting AI assistants with tools and data.
RAG
Retrieval-augmented generation: retrieving relevant material to inform an AI answer. Retrieval does not itself guarantee correctness.
MVO
Minimum viable offer: a small sellable offer used to test demand.
The definitions invite the reader into deeper work. They do not replace careful measurement or current technical documentation.
Build the scene, explanation and submission
The source uses two recurring characters: an Operator and an Employee-Who-Builds-on-the-Side, also called Builder-on-the-Side. One takes responsibility for evidence and outcomes; the other is still learning that posture. Neither should become a villain or a claim about all employees.
Other approved example characters are the forty-five-year-old first-timer; a plateaued creator earning $5,000–$30,000 monthly; an agency owner struggling with operations; and an enterprise buyer asking about schemas and a Trust Center. These are source personas, not verified descriptions of actual students. Stage 5C is a legacy reference.
Named composite characters such as Maria or Tom can make an example concrete. Label them as composite or fictional. Don't present an invented coaching relationship, quote, receipt or result as real. A realistic dollar figure still needs that label.
The full six-part module sequence is: a scene of one to three short paragraphs; one paragraph naming the gap; two to four paragraphs explaining it plainly; a named framework with a list or table; a concrete numerical example; and a submission instruction. Another rule demands the gap in paragraph two and framework no earlier than paragraph three. One short opening paragraph makes those rules compatible. Longer scenes require an explicit editorial choice.
The source's mismatch pattern contrasts a belief with the evidence, then names the lesson's purpose. Its example contrasts adding offer features with increasing buyer belief. Use a specific, supported gap; don't make up what most operators believe.
End with a deliverable, destination and next step. The source illustrates a signed Manifesto and Operator's Oath video sent to a Skool thread with a forty-eight-hour response. It also illustrates scoring three offers and posting the lowest score in a Wednesday discussion. Those are examples. Don't promise that thread, response time or event until it exists and its owner has agreed.
Keep the trust contract
The source makes six commitments: respect time; explain the real work without hype; name framework sources; use concrete numbers; allow deferral without shame; and disclose gaps or limits. Its four nonpromises are speed or quick riches, AI replacing skill, universal graduation, and a guru founder who can do everything.
Honest qualification supports those commitments. The AI prompt's instruction to avoid words such as may, could and typically does not justify false certainty. Preserve uncertainty when the evidence requires it. Define an empirical floor or graduation gate before using it to judge readiness.
Study the eight trust patterns and what each requires:
Say a method does not work for everyone when scope is limited.
Say a lesson was learned through costly experience only if that history is real.
Name a course gap and give an available workaround.
Use student failures as teaching only with accurate evidence and appropriate permission.
Name Hormozi or another actual source, then explain RISER's adaptation.
Offer a ninety-day deferral as an example of a respected choice, not a mandatory delay for everyone.
A claim that five customers paid $97 requires real payment evidence. Otherwise label it hypothetical.
Encouragement to submit despite feeling unready still needs the defined evidence floor.
The source wants quiet, direct sentences without bragging. Keep confidence tied to what can actually be shown.
Learn from all four before-and-after examples
The identity pair replaces abstract mindset and corporate language with a named composite, Mark. He is a former sales VP with twenty years of experience, age forty-six. In the fictional story, six weeks of work leads to a first $47 customer on a Tuesday. The teaching point is evidence replacing a statement of readiness. Those details are not RISER performance evidence. The source's sentence-count and grade annotations need independent measurement.
The offer pair uses fictional coach Sara: five monthly customers at $497, then twelve at $797 after an illustrative change from six months to six weeks. It lists scores 7, 5, 4 and 6, totaling 22. This is an additive teaching worksheet. It is not Hormozi's multiplicative Value Equation. The source does not define whether high time and effort scores mean more burden or better performance. Explain that ambiguity before applying a lowest-score rule. The fictional sales change does not establish causation.
The headline pair replaces a broad promise about a revolutionary 52-course system with a specific first-time buyer, first paying customer, ninety-day period and two objections: no prior online-business experience and no coding ability. Keep the lesson about specificity. Don't adopt the obsolete course count or promise that every beginner gets a customer in ninety days. That would conflict with the trust contract.
The community pair replaces hype and emoji clutter with a Wednesday discussion. It asks the reader to choose expectation versus reality, readiness versus action, or strategy versus execution; explain one in a paragraph; and reply by Friday. It promises replies to the first ten. That promise is only appropriate when the named person can keep it. Preserve the full gallery in the source appendix for side-by-side study.
Use AI as a drafting aid, then review the work
The source contains a copy-ready instruction block for drafting lesson content. Its components are reader context; 9–14-word sentences and 2–4-sentence paragraphs; grade-five-to-six language; no jargon or hype; scene before framework; dialogue and actual attribution; specific figures and timelines; honest gaps and deferral; no invented public-figure quotations; required and banned vocabulary; paragraph-two gap; paragraph-three-or-later framework; submission close; and four checks before returning a draft. Its final line requests content without process commentary. Apply that output-format requirement to the requested lesson draft; maintain any separate reporting and review responsibilities in your workflow.
The proposed workflow uses Claude Projects or a ChatGPT Custom GPT, three or four approved examples, the assigned document and syllabus or notes, a draft request, human marking, revision and repetition. These are source workflow suggestions. No project, prompt or tool has been installed by this lesson. Product setup should be checked against current official instructions when used.
For a failed capability test, add a concrete example and use simpler vocabulary. For a failed cadence test, split long sentences and paragraphs. For a failed story-first test, move the framework after the opening scene. For a failed ban test, replace the empty phrase with a concrete claim.
The four tests ask whether a first-time reader feels able to act; whether average sentences stay under fifteen words and paragraphs under four sentences; whether the scene precedes the framework; and whether banned language has been removed from authored prose. Rewrite a poorly shaped explanation rather than patching isolated words. Keep necessary original quotations and examples identifiable.
The source calls for founder or content-director review before publication. An AI draft is not that review. Its later first-ninety-days onboarding rule does not cancel its broader review requirement.
Adjust the length for each format
Format
Full source guidance
Module body
600–1,200 words as a style target, 10–12-word average sentences, opening scene, second-paragraph gap, later framework, numbers and submission. Expand or split sections to preserve all assigned material.
Sales page
Clear offer and truthful reason to act; avatar/outcome/objection headline; subheadings every 150–200 words; specific bullets; 9–11-word average sentences. The $97 offer/47 buyers/30 days bullet is an example requiring proof before a real claim.
Email
One idea, one-line scene,150–250 words,one CTA,authentic sign-off,curiosity with substance rather than clickbait;8–11-word average sentences.
Long video
7–10-word average spoken sentences;explicit pauses;acted or visualized scene;framework,example,framework restated. The referenced eight-beat C13 architecture is not defined in this document.
Short video
15-second hook/60-second proof format labels;maximum three sentences:hook,proof or surprising turn,takeaway or question. Start within a scene without greeting filler. Timing needs a read-through.
Founder community post
2–4 sentences,one question,one deadline,no hype;emoji only if the audience replies with emoji first. Promise specific responses only when deliverable.
Community-manager post
Consistent brand voice,study the specification and gallery before independent posting. Consistency does not mean pretending to be the founder.
Worksheet
Short plain instructions,one sentence per field,and a plain-English step heading. The source example asks what customers say when frustrated.
Direct-answer block
50–80 words,standalone definition,how-to,comparison,FAQ or framework. Clear answers help readers; no format guarantees AI quotation.
Maintain the specification and hand in evidence
The source uses major versions for changes to the voice or audience, minor versions for vocabulary and examples, and patches for typos. It requires dated, authored history. Its initial v 1.0 entry names Founder and Content Director but supplies no date. Preserve that gap rather than invent approval history.
Its ninety-day review checks five things: new AI phrases, new recurring vocabulary, published drift, reader feedback on readability, and changes in student demographics. It estimates two to three hours. The C 32 governance and C 51 surveillance references belong to its legacy system; their complete procedures are not supplied here.
Writer onboarding has seven steps: read the specification (two hours); read three approved modules (one hour); study the gallery (thirty minutes); write a practice module on a topic from a course not yet built (two hours); receive marked feedback; revise until passing; and begin draft production after one passing piece. The source estimates one to two part-time weeks, with human review during the first ninety days. These are planning suggestions, not measured promises or approval already granted.
The founder resolves ambiguous voice decisions; the content director handles daily review. AI produces drafts. This lesson does not appoint reviewers or record their approval.
The final quick-reference card repeats capability,9–14-word sentences,2–4-sentence paragraphs,grade 5–6,under 8% passive voice,the scene/gap/framework/example/submission sequence and four tests. Its top-twenty ban list shortens some earlier exceptions. Its required top-fifteen list repeats ship, leaving fourteen unique entries. Use the full category definitions rather than silently erasing exceptions or adding a missing word.
The closing question asks whether the paragraph has readable storytelling, practical discipline and concrete evidence—the broad traits associated with the three influences. Treat that as an editorial check, not a claim those authors reviewed or endorsed your work. The source's assertion that it supersedes all prior guidance remains part of the original. It does not override this project's user instructions, mapping or complete-coverage requirement.
Resources and submission
Open the assigned Voice Specification source. Use the full original and lesson appendix to inspect every table, sample passage and instruction-block line. Expand the original-source appendix accompanying this lesson to inspect the full document. The referenced brand book, approved sample modules and eight-beat video architecture still need verified matches before their contents can be claimed as included.
Open the v 2 Social Scaling Map Google Doc or its related v 2 Markdown version. They describe six account roles and have two small wording differences. The historical v 1 map describes five accounts with different course labels, funnels and lead magnets. These source plans do not change your current twelve-course assignments, establish live prices or prove that accounts are operating. Read the accompanying social-map teaching and complete original-source appendices in this lesson.
RISER NATION CORP is the project brand destination. A working submission thread and reviewer response commitment have not been verified here.
Turn in: one rewritten training section, its source-to-section checklist, labeled examples and readability results from your chosen tool. Keep it in your course work folder until the lesson's submission destination is confirmed. A reviewer should check clarity, evidence and retained material before approving it for use.
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
RISER NATION ACADEMY
Voice Specification Document
v1.0 — The Lock on Tone Across All 52 Courses
Master Synthesis Edition
This document is the lock on tone for every course, module, sales page, email, video script, social post, community message, and AI-generated artifact produced under the Riser Nation brand. If a piece of content does not pass the checklists in this document, it does not ship.
Most online schools die one of two deaths. The first death is voice drift. The founder writes the first three courses well. A ghost-writer takes Course Four. An AI takes Course Five. By Course Eight, the brand sounds like a different person on every page, and the student stops trusting it. The second death is hype-creep. The founder starts honest, then a marketer takes over the sales pages, and within six months the curriculum reads like one voice and the marketing reads like another. Both deaths come from the same cause: no one wrote down what the voice actually is.
This document fixes that. It is not a style guide. A style guide tells you to use Oxford commas. This is a voice specification. It tells you what a sentence sounds like before it is allowed to be a Riser Nation sentence. It defines the cadence, the vocabulary, the trust contract with the reader, and the tests every paragraph passes or gets cut.
The standard is simple to name and hard to hold:
THE RISER NATION VOICE STANDARD
A forty-five-year-old who has never built an online business and has never written a line of code should read any Riser Nation paragraph and feel capable. Not entertained. Not impressed. Capable. If the paragraph leaves them feeling impressed by the writer but uncertain about themselves, the paragraph fails the standard and gets rewritten.
Every writer, every editor, every AI prompt, every video script, every email, every sales page, every Skool post is governed by this one standard. The rest of this document is just the operational unpacking of that one rule.
The Three Voices We Borrow From
Riser Nation's voice is not invented. It is a deliberate blend of three tested voices, each chosen for a specific reason.
Robert Kiyosaki (Rich Dad Poor Dad) gives us the readability floor and the storytelling cadence. Short sentences. Stories before frameworks. Two characters in conversation. The reader learns from watching the dialogue, not from being lectured. This is the structural foundation.
Dan Kennedy gives us the discipline. No paragraph without a point. No page without an offer. No promise without a what-if scenario. Refusal to coddle. Belief in the reader's capability. Kennedy is the spine.
Alex Hormozi gives us the concreteness. Specific numbers. Specific examples. Specific dollar figures. The avoidance of abstract advice. Every claim grounded in a math equation or a named pattern. Hormozi is the floor on vagueness.
Russell Brunson, David Ogilvy, Claude Hopkins, and Robert Cialdini are present as influences on individual modules (their frameworks appear in courses C7, C8, C46), but they do not shape the core voice. The reader-facing voice is Kiyosaki-structured, Kennedy-disciplined, Hormozi-concreted. That is the blend.
What This Document Is Not
It is not a brand style guide. Visual identity, logo usage, color palettes, and typography belong in the brand book.
It is not a content strategy. What topics get covered when, by whom, on which platform — that belongs in the social scaling map and the course production sequence.
It is not a copywriting framework. AIDA, PAS, Hook-Story-Offer, the Epiphany Bridge — those are taught inside the curriculum (C7 and C8). This document governs how those frameworks sound when Riser Nation deploys them.
It is the lock on tone. Nothing more. Nothing less.
Section 2 — The Reading-Level Contract
Every paragraph published under the Riser Nation brand meets a measurable readability floor. This is not a suggestion. It is checked before publication using the tests below.
The Numbers
Measurement
Target
Hard Ceiling
Flesch Reading Ease
70 to 85
Below 65 = rewrite
Flesch-Kincaid Grade Level
5.0 to 6.5
Above 7.5 = rewrite
Average sentence length
9 to 14 words
20+ word sentences = rewrite or split
Average paragraph length
2 to 4 sentences
5+ sentences = split
Average word length
Under 5 letters
Polysyllabic clusters = rewrite
Passive voice
Under 8% of sentences
Above 12% = rewrite
Run every module body and every sales page through the Hemingway Editor (or equivalent) before submission. A page that scores grade 7 or higher gets returned to the writer, regardless of who wrote it. This rule applies to the founder. It applies to the ghost-writer. It applies to Claude. It applies to every AI prompt.
Why Fifth Grade, Not Eighth
The standard online-content default is eighth grade. We are deliberately two grades below that. The reason is the avatar.
The Riser Nation primary avatar is a forty-five-year-old career-pivoter. They are smart. They are accomplished. They have run companies, raised children, survived layoffs. They are not stupid. They are tired. They read after a full day of work, with a phone in one hand and a half-eaten dinner on the desk. A grade-eight paragraph asks too much of them at that hour. A grade-five paragraph respects their time.
This is the same reason Kiyosaki sold forty million books. He understood that respect for the reader's time is a form of love. The reader does not need to be challenged by the prose; they need to be challenged by the work the prose asks them to do.
The Sentence Length Discipline
The single most violated rule in online education is sentence length. Writers default to fifteen, twenty, twenty-five words. Riser Nation defaults to nine to fourteen. The discipline is this:
1. Write the sentence the way it comes out.
2. Count the words.
3. If it is over fourteen words, look for the comma or the conjunction.
4. Cut it there. Make two sentences.
5. Read both out loud. If either feels stupid, restructure. If both feel clean, keep both.
EXAMPLE — BEFORE
Most operators waste enormous amounts of time on tactical execution because they have not yet developed the strategic clarity that comes from sitting with the difficult identity questions that determine whether they will succeed or fail as builders rather than as employees pretending to build. (43 words. One sentence. Grade 12.)
EXAMPLE — AFTER
Most operators waste time on tactics. They have not asked the hard identity question yet. The question is simple. Are you a builder or an employee pretending to build? You cannot answer that on the run. You answer it sitting down. (43 words. Six sentences. Grade 5.)
Same content. Same idea. Same depth. Different voice. The second version is Riser Nation. The first version is not.
The Paragraph Rhythm
Two to four sentences per paragraph. Then white space. Then the next paragraph. This rhythm is the visual signature of a Kiyosaki page. The eye gets to rest. The reader feels the writer is not trying to overwhelm them. The white space says: take your time.
Long paragraphs say the opposite. They say: I have a lot to tell you and you need to keep up. That is the wrong relationship.
When in doubt, break the paragraph. The reader will thank you.
Section 3 — Vocabulary
The vocabulary section has three lists. The ban list is words that do not appear in Riser Nation content. The required list is words that do. The earned list is words that can appear only when they have been defined first inside the same piece of content.
The Ban List
These words are banned not because they are wrong, but because they signal a different brand. They sound like the corporate consultant, the LinkedIn thought-leader, or the hype-funnel guru. None of those are Riser Nation.
Banned categories with examples:
•Corporate jargon — synergy, leverage (as a verb), unlock, scale (as a verb without an object), transform, optimize (without a metric), holistic, paradigm, ecosystem (unless literal), bandwidth, double-click, ideate, learnings, deep-dive, low-hanging fruit, move the needle.
•AI-tell phrases — delve, in today's fast-paced world, the digital landscape, navigating the complexities, embark on a journey, harness the power, unleash, in conclusion, it is important to note, furthermore, moreover, in essence, this article will explore.
•Coddling — don't worry, don't beat yourself up, you've got this, you can do anything you set your mind to, dream big, the sky is the limit.
When any of these words appear in a draft, the writer's first move is not to find a synonym. It is to ask whether the sentence is making a real claim. Usually the banned word was filling in for a missing claim. Fix the claim. The word disappears on its own.
The Required List
These words appear regularly across Riser Nation content because they are the operating vocabulary of the syllabus. Using them consistently builds the brand language. Avoiding them weakens it.
•Stage terms — harbor, sailboat, speedboat, yacht, ship, fleet, harbormaster. These are not metaphors decorating the syllabus. They are the navigation system. Use the named stage when the context allows it.
•Discipline terms — ship, deploy, hand in, turn in, capstone deliverable, signed testimonial, refund analysis, validated price, documented outcome.
•Lineage terms — Hormozi, Brunson, Kennedy, Kern, Ogilvy, Hopkins, Cialdini. When a framework comes from one of them, name the source. Lineage is part of the trust signal.
The Earned List
These words are technical or specific. They are allowed once they have been defined inside the same piece of content. If the piece is short (a social post, an email), define on first use or do not use them at all. If the piece is a module body, define in plain words within the same paragraph.
Term
First-Use Definition Required
Example
LTV
Yes
LTV is the total dollars one customer pays you over their full relationship with the business.
CAC
Yes
CAC is what it costs you in marketing to get one customer to buy.
AOV
Yes
AOV is the average dollar amount per order.
MRR
Yes
MRR is the monthly money that comes in from continuity members.
AEO
Yes
AEO means writing your pages so AI search engines quote them when answering questions.
GEO
Yes
GEO means stacking the signals that make AI engines trust your brand as a real authority.
MCP
Yes
MCP is a protocol that lets AI assistants connect to outside tools and data.
RAG
Yes
RAG is when an AI looks up your specific documents before answering.
MVO
Yes
MVO is the smallest version of an offer you can sell to test if the market wants it.
The rule is not to dumb down the depth. The rule is to invite the reader in before using the term. A reader who reads the first definition becomes capable of reading the rest of the piece. A reader who hits an undefined acronym in paragraph one stops trusting the writer.
Section 4 — Structural Patterns
Beyond word choice and sentence length, the Riser Nation voice has structural signatures. These are the patterns that make a paragraph recognizable as ours.
The Two-Character Frame (Kiyosaki's Trick)
Kiyosaki's most-copied move is the rich-dad-poor-dad device. Two characters disagree. The reader watches them. The frame teaches without lecturing.
Riser Nation does the same thing with a different cast. Our two characters are the Operator and the Employee-Who-Builds-on-the-Side. They show up in modules whenever a doctrine needs to be felt, not just understood.
THE OPERATOR vs. THE BUILDER-ON-THE-SIDE
Use these two characters whenever a module needs to make an identity point. The Operator owns the result. The Builder-on-the-Side hopes for the result. Same effort. Different posture. Different outcome. Show the difference in dialogue when possible. Avoid making either one a villain — the Builder-on-the-Side is not stupid; they are early.
Other recurring characters approved for use:
•The Forty-Five-Year-Old First-Timer — our primary avatar. Career changer. No code. No prior business. Smart, tired, hopeful.
•The Plateaued Creator — five to thirty thousand a month, stuck. Audience that loves them. Revenue that won't climb.
•The Agency Owner — making money, drowning in operations, AI-curious but burned by hype.
•The Enterprise Buyer — rare in our content, but present in Stage 5C modules. Careful. Schema-driven. Asks for the Trust Center.
Use real, named composite characters when stories need warmth. (Examples: "An operator named Maria…" or "A coach I worked with named Tom…") Composites are allowed. Made-up specific dollar figures attached to composites are allowed if they are realistic. Made-up named real people are not.
The Story-Then-Frame Order
Riser Nation modules never lead with the framework. They lead with a story or a scene, then name the framework, then apply the framework, then end with a turn-in.
The order is fixed:
6. Scene or story (one to three short paragraphs).
7. The mismatch this module fixes (one paragraph).
8. The plain-words explanation (two to four paragraphs).
9. The named framework or doctrine (one paragraph plus a list or table).
10. A concrete example with numbers.
11. The turn-in instruction (what the student does next).
This is the inverse of how most online courses are written. Most courses lead with the framework, then apply it. The framework-first order is faster to write but slower to absorb. The story-first order is the Kiyosaki signature. It is also the Hormozi default in his videos. The story does the trust-building work; the framework does the teaching work. In that order.
The Mismatch Statement
Every module of every course names a mismatch. The syllabus is built on this. The voice carries it through. The mismatch statement appears in the second paragraph of every module body. The pattern is:
MISMATCH STATEMENT FORMAT
Most operators believe X. The reality is Y. This module closes the gap between the belief and the reality.
Example: Most operators believe a great offer needs more features. The reality is a great offer needs fewer features and more belief. This module closes the gap between the belief and the reality.
The mismatch statement is not optional. Every module has one. Without it, the module loses its place in the syllabus's core doctrine.
The Turn-In Close
Every module ends with a specific instruction. Not a summary. Not a recap. Not an inspirational quote. An instruction.
The pattern:
•Turn in: [specific deliverable]. [Where it goes]. [What happens next.]
Examples:
•Turn in: Your signed Manifesto and Operator's Oath video. Upload to the Skool community thread. The community responds within forty-eight hours.
•Turn in: Your scored Value Equation worksheet for three offers. Post the lowest score in the Wednesday discussion. The lowest score is where the work starts.
The turn-in is the reason students do the module instead of just watching it. It is also the reason the Skool community has activity. Without turn-ins, the community is a graveyard. With turn-ins, the community is the engine.
Section 5 — The Trust Contract
Voice is not only about how a sentence sounds. It is also about what a sentence promises. The Riser Nation voice carries a specific trust contract with the reader. Every writer and every AI prompt is bound by this contract.
What We Promise
12. We will not waste your time. Every paragraph earns its place or gets cut.
13. We will not hype you. We will tell you what the work actually takes.
14. We will name the source. Where a framework comes from Hormozi or Kennedy or Brunson, we say so.
15. We will use real numbers. Dollar figures, conversion rates, timelines. No vague "results may vary" mush.
16. We will let you defer. Defer-without-shame is a doctrine, not a slogan. If you are not ready for a stage, we will say so.
17. We will not pretend. If the founder cannot do a thing, we will say the founder cannot do the thing. If a course has a gap, we will name the gap.
What We Do Not Promise
18. We do not promise speed. We do not promise riches in thirty days.
19. We do not promise that AI will replace skill. AI is leverage on skill, not a substitute for it.
20. We do not promise that every student will graduate. The empirical floor is real. Some students will defer indefinitely. That is doctrine, not failure.
21. We do not promise the founder is a guru. The founder is an operator who learned in public. The student is being invited into the same posture.
How the Promises Show Up in Sentences
Trust contracts are not built by saying "trust me." They are built by the cumulative weight of small honest sentences. Here are the patterns that carry the contract:
In a Sentence
What It Signals
"This will not work for everyone."
We do not pretend universality.
"I learned this the expensive way."
We earned the lesson; we did not read it in a book.
"The course gap here is real. Here is how to work around it."
We name our own limitations.
"Three of my students have failed this gate. Here is what they had in common."
We use our own failures as teaching material.
"This is Hormozi's framework. We adapt it for the forty-five-year-old first-timer."
We name the source and the adaptation.
"Defer this stage. Come back in ninety days. There is no shame in deferring."
We make deferral a respected choice.
"The number is $97. Five customers paid it. Here are the receipts."
Specific over vague.
"You will not feel ready. Ship anyway. Empirical floor is what makes you ready."
We push without coddling.
Read these patterns out loud. They have a particular sound. Slightly understated. Quietly direct. Never apologetic. Never bragging. That sound is the trust contract.
Section 6 — The Before/After Gallery
Voice specifications fail when they stay abstract. The cleanest way to lock voice is to show what passes and what fails, side by side. Every writer studies this gallery before submitting their first piece. Every AI prompt is given this gallery as in-context examples.
Example 1 — Identity Module (C1)
FAILS THE STANDARD
In today's rapidly evolving digital landscape, aspiring entrepreneurs must recognize that their mindset is the most critical factor determining their ultimate success. The transition from an employee mentality to an entrepreneurial paradigm requires deep introspection and a willingness to challenge limiting beliefs that have been ingrained through years of corporate conditioning. By unlocking your inner operator and embracing the abundance mindset, you can transform your relationship with money and achievement.
Why it fails: corporate jargon (rapidly evolving digital landscape, paradigm, ingrained, abundance mindset). Two long sentences (28 and 32 words). Hype-coddling tone (unlocking, transform, embrace). Grade level: 13. Zero specifics. AI-tell phrasing throughout.
PASSES THE STANDARD
An operator I worked with named Mark spent twenty years as a sales VP. He came to Riser Nation at forty-six. The first thing he told me was, "I think I'm ready."
I told him he wasn't. Not because of his skills. Because of how he said the sentence.
A builder does not say "I think I'm ready." A builder says "I have one customer who paid me forty-seven dollars on Tuesday." The first sentence is hope. The second is proof.
Mark spent the next six weeks getting his first customer. He came back with the second sentence. Then we started.
Why it passes: opening scene with a named composite character. Short sentences (average 11 words). Specific number ($47, Tuesday). Two-character contrast (the Builder vs. the Operator). The mismatch is shown, not told. Grade level: 4. Zero corporate jargon.
Example 2 — Offer Module (C6)
FAILS THE STANDARD
The Value Equation is a powerful framework that enables entrepreneurs to dramatically increase the perceived value of their offerings through a structured approach. By carefully optimizing the four key levers — Dream Outcome, Perceived Likelihood of Achievement, Time Delay, and Effort and Sacrifice — operators can create grand slam offers that customers literally cannot refuse, resulting in transformative business outcomes.
Why it fails: "powerful framework," "enables," "dramatically," "structured approach," "carefully optimizing," "literally cannot refuse," "transformative." Banned words throughout. No story, no scene. The framework is named but never grounded. Grade level: 14.
PASSES THE STANDARD
A coach named Sara sold a $497 course for two years. Five customers a month. Steady, but stuck.
She came in and asked what to fix. I pointed at the offer. She said, "The offer is fine. The traffic is the problem."
The offer was not fine.
Here is the test Hormozi taught us. Score your offer one to ten on four levers. Dream Outcome. Belief that it will work. Time it takes. Effort it takes. Sara scored a 7, a 5, a 4, a 6. Total: 22.
The lowest score is where the work starts. Hers was Time. Six months to result. She cut it to six weeks. Same content, different sequencing. Twelve customers the next month at $797.
Why it passes: opening scene (Sara, $497, five customers). Two-character dialogue. The framework arrives in paragraph four, after the scene. Specific scores given (7, 5, 4, 6). Specific outcome ($797, twelve customers). Lineage named (Hormozi). Grade level: 5.
Example 3 — Sales Page Headline
FAILS THE STANDARD
Unlock Your Inner Operator: The Revolutionary 52-Course System That Will Transform Your Mindset and Help You Build the Online Business of Your Dreams
Why it fails: Unlock, Revolutionary, Transform, Mindset, Dreams. Five banned words in one headline.
PASSES THE STANDARD
How a Forty-Five-Year-Old First-Timer Can Have One Paying Customer in Ninety Days — Even If They Have Never Built an Online Business and Cannot Write a Line of Code
Why it passes: specific avatar (forty-five-year-old first-timer). Specific outcome (one paying customer). Specific timeline (ninety days). Two objections handled (never built, cannot code). Kennedy's headline architecture. Grade level: 5.
Example 4 — Skool Community Post
FAILS THE STANDARD
Hey Riser Nation family! 🚀 Hope you're all having an AMAZING week! Just wanted to drop in and remind you that you are CAPABLE of incredible things. Don't forget to dream big and keep crushing it! What's one thing you're going to absolutely DOMINATE this week? Drop it in the comments! 💪🔥
Why it fails: emoji clutter, hype words (AMAZING, CAPABLE, incredible, dream big, crushing, DOMINATE), no specific instruction, no real question, performative energy.
PASSES THE STANDARD
Wednesday discussion.
Which of the three mismatches is most active in your business right now? Expectation versus reality. Readiness versus action. Strategy versus execution.
Pick one. Write one paragraph on why.
Reply by Friday. I'll respond to the first ten.
Why it passes: short. Specific. Calls back to C1 doctrine (three mismatches). Asks one question, not five. Names a deadline. Founder commits to specific reply count. No emoji. No hype.
Section 7 — Instructions for AI Co-Writing
This section is the operating instruction for every AI prompt that produces Riser Nation content. Paste the entire section into the system prompt for any Claude, ChatGPT, or other AI co-writer. Update it whenever this document is versioned.
The Master Instruction Block (Copy-Paste Ready)
PASTE THIS INTO YOUR AI SYSTEM PROMPT
You are writing for Riser Nation Academy. The reader is a forty-five-year-old career-pivoter who has never built an online business and cannot write code. They are smart but tired. They are reading at the end of a long day. Respect their time.
Voice rules. Sentences average nine to fourteen words. Paragraphs are two to four sentences. Reading level is fifth to sixth grade as measured by Flesch-Kincaid. No corporate jargon. No hype words. No AI-tell phrases like "delve," "in today's fast-paced world," "navigate the complexities," or "unleash."
Structure rules. Lead with a story or scene before the framework. Use two characters in dialogue when teaching a doctrine. Name the source when a framework comes from Hormozi, Brunson, Kennedy, Kern, Ogilvy, Hopkins, or Cialdini. Use specific dollar figures and timelines. Avoid vague qualifiers like "may," "could," "typically."
Trust rules. We do not promise speed or riches. We name our gaps. We let students defer without shame. We use composite named characters for warmth but never invent quotes from real public figures. We never coddle.
Vocabulary rules. Required words include operator, builder, mismatch, empirical floor, defer, ship, capstone, harbor, sailboat, speedboat, yacht. Banned words include synergy, leverage as a verb, unlock, transform, paradigm, crush it, hack, ninja, game-changer, revolutionary, delve, harness, unleash, embark on a journey.
Format rules. Every module body opens with a scene or story. Paragraph two names the mismatch the module fixes. The named framework appears no earlier than paragraph three. Every module ends with a turn-in instruction in this format: "Turn in: [specific deliverable]. [Where it goes]. [What happens next.]"
Before returning your draft, run the four-test checklist. If any test fails, revise. The tests are: (1) Would a forty-five-year-old first-timer feel capable, not impressed, after reading this? (2) Is the average sentence under fifteen words? (3) Did you lead with a scene before the framework? (4) Did you avoid every banned word from the list?
Return only the rewritten content. Do not include meta-commentary about your process.
How to Run the AI Co-Writing Loop
22. Open Claude Projects (or ChatGPT Custom GPT). Paste the Master Instruction Block as the system prompt.
23. Upload three or four In Plain Words examples that pass the standard. These become in-context references.
24. Give the AI the source material (the relevant doc from the DOCS_SPREADSHEET, the syllabus module text, your raw notes).
25. Ask for the module body in Riser Nation voice.
26. Read the draft against the Four-Test Checklist below.
27. Mark any sentence that fails. Send the marked draft back. Ask for revision.
28. Repeat until the draft passes.
29. The final human pass is non-negotiable. The founder or content director reads every module before publication, regardless of AI involvement.
The Four-Test Checklist
Every piece of content runs through these four tests before publication. No exceptions. No "this one is short, we'll skip the test." The discipline is the brand.
Test
Pass Criterion
Fail Action
Capability Test
Forty-five-year-old reader feels capable after reading.
Rewrite with concrete example and lower vocabulary.
Cadence Test
Average sentence under 15 words. Average paragraph under 4 sentences.
Split long sentences. Break long paragraphs.
Story-First Test
Module opens with scene or story. Framework arrives after paragraph 2.
Move the framework. Add a scene to the top.
Ban Test
Zero banned words from Section 3.
Remove the banned word. Replace with concrete claim.
A piece that fails any test gets rewritten. Not edited. Rewritten. The reason is that a failed test usually signals a wrong shape, not a wrong word. Editing a wrong shape produces patched-up content that still feels off. Rewriting from the shape outward produces clean content.
Section 8 — Per-Format Voice Adaptations
The voice does not change across formats. The compression does. A module body has eight hundred words to breathe in. A LinkedIn post has eighty. The principles below adapt the same voice to each format without diluting it.
Module Bodies
Six hundred to twelve hundred words per module. Open with scene. Mismatch in paragraph two. Framework no earlier than paragraph three. Specific example with numbers. Turn-in close. Average sentence length: 10–12 words.
Sales Pages
Kennedy's discipline. Always an offer. Always a reason to act now. Headline names the avatar plus the outcome plus the objection handled. Sub-headlines break up scannable sections every 150–200 words. Bullet points use Hormozi-style specificity ("the exact $97 offer that produced 47 buyers in 30 days" — not "powerful strategies that drive results"). Average sentence length: 9–11 words.
Email Sequences
Shorter than module bodies. One idea per email. Open with a one-line scene. Body in 150–250 words. Always one specific call to action. Sign-off in your real voice, not a corporate sign-off. Subject lines never use clickbait — they use Kennedy's curiosity-with-substance pattern. Average sentence length: 8–11 words.
Long-Form Video Scripts (8-beat C13 architecture)
Spoken voice runs slightly shorter than written. Average sentence on script: 7–10 words. Pause beats marked explicitly. Stories carry the script — the framework is named, the example is given, the framework is restated. The same scene-before-framework rule applies, but the scene is acted out or visualized, not just told.
The first sentence is the hook. The second sentence delivers the proof or the counter-intuitive turn. The third sentence is the takeaway or the question that closes the loop. Three sentences. Maximum. No throat-clearing. No "hey guys." No "in this video." Start mid-scene.
Skool Community Posts (Founder Voice)
Two to four sentences. One question. One deadline. No emoji unless the audience replies with emoji first. No hype. The founder posts like a wise older operator dropping into the conversation, not like a marketing channel. Specific responses promised ("I'll reply to the first ten") and kept.
Skool Community Posts (Community Manager Voice)
Community manager posts in the same voice as the founder. The reader should not be able to tell the difference. This is the entire point of having a Voice Specification Document — it makes the brand voice repeatable by someone other than the founder. The community manager studies this document and the Before/After Gallery before posting independently.
Worksheets
Instructions in the same voice as module bodies, but shorter. Each field has a one-sentence prompt. No headers like "Section A: Strategic Analysis." Headers in plain English: "Step 1. What does your customer say when they're frustrated?"
Schema / AEO Direct-Answer Blocks
AEO blocks are written for AI engines to lift verbatim. They are tighter than normal Riser Nation prose. 50–80 words. Definition, How-To, Comparison, FAQ, Framework formats. Each block must read cleanly on its own, with no reference to surrounding context. The voice stays Riser Nation, but the format is structured for citation.
Section 9 — Governance
This document is itself an asset of the academy. It is governed under the C32 RN-MOS doctrine, the same way every other component is.
Versioning
This is version 1.0. Major versions (2.0, 3.0) are issued when the voice itself evolves — for example, if the academy expands its primary avatar beyond the forty-five-year-old first-timer, or if a new lineage author is added to the canonical influences. Minor versions (1.1, 1.2) are issued when the ban list, required list, or examples are updated. Patch versions (1.0.1) handle typo fixes.
Version history is maintained at the end of this document. Every change is dated and authored.
Quarterly Review
This document is reviewed every ninety days, on the same cadence as the Trend Surveillance Engine (C51). The reviewer looks for:
• New AI-tell phrases that have started appearing in drafts (banned-list candidates).
• New vocabulary the academy has started using consistently (required-list candidates).
• Drift in any published content — pieces that slipped through without passing the Four-Test Checklist.
• Reader feedback indicating a vocabulary or cadence problem.
• Whether the avatar definition needs updating based on new student demographics.
Quarterly review takes two to three hours. It is the cheapest defense against voice drift the academy has.
Onboarding New Writers and Editors
Every new writer, editor, ghost-writer, contractor, community manager, and AI prompt operator goes through the same onboarding before being allowed to produce or post content.
30. Read this Voice Specification Document end to end. Two hours.
31. Read three published modules that pass the standard. One hour.
32. Read the Before/After Gallery in Section 6. Thirty minutes.
33. Write one practice module body using a topic from a course not yet built. Two hours.
34. Submit the practice piece. Receive marked-up feedback against the Four-Test Checklist.
35. Revise. Resubmit. Repeat until the piece passes.
36. Once one piece passes, the writer is cleared to produce drafts. The founder or content director still reads every piece before publication for the first ninety days.
This onboarding takes one to two weeks of part-time effort. It is non-negotiable. A writer who skips it produces work that the brand cannot use.
Authority
The founder is the final voice authority. Disputes about whether a piece passes the standard are resolved by the founder. The content director carries day-to-day authority but escalates ambiguous calls to the founder.
AI co-writers have no authority. They produce drafts. The drafts pass through the Four-Test Checklist run by a human. If the human and the AI disagree, the human wins. Always.
Section 10 — The One-Page Operational Summary
For writers who have already read this document and need the quick-reference card. Pin this to the wall. Tape it inside the laptop. Save it as the first page of every project doc.
THE STANDARD
A forty-five-year-old who has never built an online business reads any Riser Nation paragraph and feels capable. Not impressed. Capable.
THE NUMBERS
• Sentence length: 9–14 words average
• Paragraph length: 2–4 sentences
• Reading level: grade 5–6
• Passive voice: under 8%
THE STRUCTURE
• Open with a scene or story
• Name the mismatch in paragraph 2
• Frameworks arrive no earlier than paragraph 3
• Specific numbers and named composites only
• End with a Turn-In: [deliverable] + [destination] + [what happens next]
THE BAN (TOP 20)
synergy · leverage (verb) · unlock · transform · paradigm · ecosystem · holistic · crush it · hack · ninja · game-changer · revolutionary · delve · harness · unleash · embark on a journey · in today's fast-paced world · literally · absolutely · navigate the complexities
37. Capability Test — feels capable, not impressed
38. Cadence Test — sentences under 15 words
39. Story-First Test — scene before framework
40. Ban Test — zero banned words
THE FINAL QUESTION
Before submitting any piece: would Robert Kiyosaki write this paragraph? Would Dan Kennedy let this paragraph ship? Would Alex Hormozi keep this paragraph if it were on his sales page? If the answer to all three is yes, the piece is Riser Nation.
Version History
Version
Changes
v1.0 — Initial release
Founder + Content Director. The first lock on tone. Approved for use across all courses, all formats, all writers, all AI prompts.
This document supersedes any prior style guidance, brand voice notes, or tonal direction issued before its publication date. In the case of conflict, this document wins.
word/footnotes.xml
word/endnotes.xml
word/comments.xml
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"RISER NATION ACADEMY",
"Voice Specification Document",
"v1.0 — The Lock on Tone Across All 52 Courses",
"Master Synthesis Edition",
"",
"This document is the lock on tone for every course, module, sales page, email, video script, social post, community message, and AI-generated artifact produced under the Riser Nation brand. If a piece of content does not pass the checklists in this document, it does not ship.",
"Owner: Founder. Custodian: Content Director. Authority: Final.",
"",
"Section 1 — Why This Document Exists",
"Most online schools die one of two deaths. The first death is voice drift. The founder writes the first three courses well. A ghost-writer takes Course Four. An AI takes Course Five. By Course Eight, the brand sounds like a different person on every page, and the student stops trusting it. The second death is hype-creep. The founder starts honest, then a marketer takes over the sales pages, and within six months the curriculum reads like one voice and the marketing reads like another. Both deaths come from the same cause: no one wrote down what the voice actually is.",
"This document fixes that. It is not a style guide. A style guide tells you to use Oxford commas. This is a voice specification. It tells you what a sentence sounds like before it is allowed to be a Riser Nation sentence. It defines the cadence, the vocabulary, the trust contract with the reader, and the tests every paragraph passes or gets cut.",
"The standard is simple to name and hard to hold:",
"THE RISER NATION VOICE STANDARD",
"A forty-five-year-old who has never built an online business and has never written a line of code should read any Riser Nation paragraph and feel capable. Not entertained. Not impressed. Capable. If the paragraph leaves them feeling impressed by the writer but uncertain about themselves, the paragraph fails the standard and gets rewritten.",
"",
"Every writer, every editor, every AI prompt, every video script, every email, every sales page, every Skool post is governed by this one standard. The rest of this document is just the operational unpacking of that one rule.",
"The Three Voices We Borrow From",
"Riser Nation's voice is not invented. It is a deliberate blend of three tested voices, each chosen for a specific reason.",
"Robert Kiyosaki (Rich Dad Poor Dad) gives us the readability floor and the storytelling cadence. Short sentences. Stories before frameworks. Two characters in conversation. The reader learns from watching the dialogue, not from being lectured. This is the structural foundation.",
"Dan Kennedy gives us the discipline. No paragraph without a point. No page without an offer. No promise without a what-if scenario. Refusal to coddle. Belief in the reader's capability. Kennedy is the spine.",
"Alex Hormozi gives us the concreteness. Specific numbers. Specific examples. Specific dollar figures. The avoidance of abstract advice. Every claim grounded in a math equation or a named pattern. Hormozi is the floor on vagueness.",
"Russell Brunson, David Ogilvy, Claude Hopkins, and Robert Cialdini are present as influences on individual modules (their frameworks appear in courses C7, C8, C46), but they do not shape the core voice. The reader-facing voice is Kiyosaki-structured, Kennedy-disciplined, Hormozi-concreted. That is the blend.",
"What This Document Is Not",
"It is not a brand style guide. Visual identity, logo usage, color palettes, and typography belong in the brand book.",
"It is not a content strategy. What topics get covered when, by whom, on which platform — that belongs in the social scaling map and the course production sequence.",
"It is not a copywriting framework. AIDA, PAS, Hook-Story-Offer, the Epiphany Bridge — those are taught inside the curriculum (C7 and C8). This document governs how those frameworks sound when Riser Nation deploys them.",
"It is the lock on tone. Nothing more. Nothing less.",
"",
"Section 2 — The Reading-Level Contract",
"Every paragraph published under the Riser Nation brand meets a measurable readability floor. This is not a suggestion. It is checked before publication using the tests below.",
"The Numbers",
"Measurement",
"Target",
"Hard Ceiling",
"Flesch Reading Ease",
"70 to 85",
"Below 65 = rewrite",
"Flesch-Kincaid Grade Level",
"5.0 to 6.5",
"Above 7.5 = rewrite",
"Average sentence length",
"9 to 14 words",
"20+ word sentences = rewrite or split",
"Average paragraph length",
"2 to 4 sentences",
"5+ sentences = split",
"Average word length",
"Under 5 letters",
"Polysyllabic clusters = rewrite",
"Passive voice",
"Under 8% of sentences",
"Above 12% = rewrite",
"",
"Run every module body and every sales page through the Hemingway Editor (or equivalent) before submission. A page that scores grade 7 or higher gets returned to the writer, regardless of who wrote it. This rule applies to the founder. It applies to the ghost-writer. It applies to Claude. It applies to every AI prompt.",
"Why Fifth Grade, Not Eighth",
"The standard online-content default is eighth grade. We are deliberately two grades below that. The reason is the avatar.",
"The Riser Nation primary avatar is a forty-five-year-old career-pivoter. They are smart. They are accomplished. They have run companies, raised children, survived layoffs. They are not stupid. They are tired. They read after a full day of work, with a phone in one hand and a half-eaten dinner on the desk. A grade-eight paragraph asks too much of them at that hour. A grade-five paragraph respects their time.",
"This is the same reason Kiyosaki sold forty million books. He understood that respect for the reader's time is a form of love. The reader does not need to be challenged by the prose; they need to be challenged by the work the prose asks them to do.",
"The Sentence Length Discipline",
"The single most violated rule in online education is sentence length. Writers default to fifteen, twenty, twenty-five words. Riser Nation defaults to nine to fourteen. The discipline is this:",
"Write the sentence the way it comes out.",
"Count the words.",
"If it is over fourteen words, look for the comma or the conjunction.",
"Cut it there. Make two sentences.",
"Read both out loud. If either feels stupid, restructure. If both feel clean, keep both.",
"",
"EXAMPLE — BEFORE",
"Most operators waste enormous amounts of time on tactical execution because they have not yet developed the strategic clarity that comes from sitting with the difficult identity questions that determine whether they will succeed or fail as builders rather than as employees pretending to build. (43 words. One sentence. Grade 12.)",
"",
"EXAMPLE — AFTER",
"Most operators waste time on tactics. They have not asked the hard identity question yet. The question is simple. Are you a builder or an employee pretending to build? You cannot answer that on the run. You answer it sitting down. (43 words. Six sentences. Grade 5.)",
"",
"Same content. Same idea. Same depth. Different voice. The second version is Riser Nation. The first version is not.",
"The Paragraph Rhythm",
"Two to four sentences per paragraph. Then white space. Then the next paragraph. This rhythm is the visual signature of a Kiyosaki page. The eye gets to rest. The reader feels the writer is not trying to overwhelm them. The white space says: take your time.",
"Long paragraphs say the opposite. They say: I have a lot to tell you and you need to keep up. That is the wrong relationship.",
"When in doubt, break the paragraph. The reader will thank you.",
"",
"Section 3 — Vocabulary",
"The vocabulary section has three lists. The ban list is words that do not appear in Riser Nation content. The required list is words that do. The earned list is words that can appear only when they have been defined first inside the same piece of content.",
"The Ban List",
"These words are banned not because they are wrong, but because they signal a different brand. They sound like the corporate consultant, the LinkedIn thought-leader, or the hype-funnel guru. None of those are Riser Nation.",
"Banned categories with examples:",
"Corporate jargon — synergy, leverage (as a verb), unlock, scale (as a verb without an object), transform, optimize (without a metric), holistic, paradigm, ecosystem (unless literal), bandwidth, double-click, ideate, learnings, deep-dive, low-hanging fruit, move the needle.",
"Empty intensifiers — literally, absolutely, completely, totally, basically, essentially, fundamentally, ultimately, frankly, honestly (as a sentence opener).",
"Hype-funnel words — crush it, unlock your potential, secret, hack, ninja, rockstar, game-changer, life-changing, revolutionary, disruptive (unless C11 context), insane, mind-blown, level up, 10x your, blueprint (use plan), proven (without proof attached).",
"AI-tell phrases — delve, in today's fast-paced world, the digital landscape, navigating the complexities, embark on a journey, harness the power, unleash, in conclusion, it is important to note, furthermore, moreover, in essence, this article will explore.",
"Coddling — don't worry, don't beat yourself up, you've got this, you can do anything you set your mind to, dream big, the sky is the limit.",
"",
"When any of these words appear in a draft, the writer's first move is not to find a synonym. It is to ask whether the sentence is making a real claim. Usually the banned word was filling in for a missing claim. Fix the claim. The word disappears on its own.",
"The Required List",
"These words appear regularly across Riser Nation content because they are the operating vocabulary of the syllabus. Using them consistently builds the brand language. Avoiding them weakens it.",
"Identity terms — operator, builder, founder. Avoid: entrepreneur, marketer (unless precise), creator (when distinguishing from operator).",
"Stage terms — harbor, sailboat, speedboat, yacht, ship, fleet, harbormaster. These are not metaphors decorating the syllabus. They are the navigation system. Use the named stage when the context allows it.",
"Doctrine terms — mismatch, reduce mismatches, empirical floor, defer, defer without shame, pass, rework, graduation gate, proof, capstone.",
"Discipline terms — ship, deploy, hand in, turn in, capstone deliverable, signed testimonial, refund analysis, validated price, documented outcome.",
"Lineage terms — Hormozi, Brunson, Kennedy, Kern, Ogilvy, Hopkins, Cialdini. When a framework comes from one of them, name the source. Lineage is part of the trust signal.",
"The Earned List",
"These words are technical or specific. They are allowed once they have been defined inside the same piece of content. If the piece is short (a social post, an email), define on first use or do not use them at all. If the piece is a module body, define in plain words within the same paragraph.",
"Term",
"First-Use Definition Required",
"Example",
"LTV",
"Yes",
"LTV is the total dollars one customer pays you over their full relationship with the business.",
"CAC",
"Yes",
"CAC is what it costs you in marketing to get one customer to buy.",
"AOV",
"Yes",
"AOV is the average dollar amount per order.",
"MRR",
"Yes",
"MRR is the monthly money that comes in from continuity members.",
"AEO",
"Yes",
"AEO means writing your pages so AI search engines quote them when answering questions.",
"GEO",
"Yes",
"GEO means stacking the signals that make AI engines trust your brand as a real authority.",
"MCP",
"Yes",
"MCP is a protocol that lets AI assistants connect to outside tools and data.",
"RAG",
"Yes",
"RAG is when an AI looks up your specific documents before answering.",
"MVO",
"Yes",
"MVO is the smallest version of an offer you can sell to test if the market wants it.",
"",
"The rule is not to dumb down the depth. The rule is to invite the reader in before using the term. A reader who reads the first definition becomes capable of reading the rest of the piece. A reader who hits an undefined acronym in paragraph one stops trusting the writer.",
"",
"Section 4 — Structural Patterns",
"Beyond word choice and sentence length, the Riser Nation voice has structural signatures. These are the patterns that make a paragraph recognizable as ours.",
"The Two-Character Frame (Kiyosaki's Trick)",
"Kiyosaki's most-copied move is the rich-dad-poor-dad device. Two characters disagree. The reader watches them. The frame teaches without lecturing.",
"Riser Nation does the same thing with a different cast. Our two characters are the Operator and the Employee-Who-Builds-on-the-Side. They show up in modules whenever a doctrine needs to be felt, not just understood.",
"THE OPERATOR vs. THE BUILDER-ON-THE-SIDE",
"Use these two characters whenever a module needs to make an identity point. The Operator owns the result. The Builder-on-the-Side hopes for the result. Same effort. Different posture. Different outcome. Show the difference in dialogue when possible. Avoid making either one a villain — the Builder-on-the-Side is not stupid; they are early.",
"",
"Other recurring characters approved for use:",
"The Forty-Five-Year-Old First-Timer — our primary avatar. Career changer. No code. No prior business. Smart, tired, hopeful.",
"The Plateaued Creator — five to thirty thousand a month, stuck. Audience that loves them. Revenue that won't climb.",
"The Agency Owner — making money, drowning in operations, AI-curious but burned by hype.",
"The Enterprise Buyer — rare in our content, but present in Stage 5C modules. Careful. Schema-driven. Asks for the Trust Center.",
"Use real, named composite characters when stories need warmth. (Examples: \"An operator named Maria…\" or \"A coach I worked with named Tom…\") Composites are allowed. Made-up specific dollar figures attached to composites are allowed if they are realistic. Made-up named real people are not.",
"The Story-Then-Frame Order",
"Riser Nation modules never lead with the framework. They lead with a story or a scene, then name the framework, then apply the framework, then end with a turn-in.",
"The order is fixed:",
"Scene or story (one to three short paragraphs).",
"The mismatch this module fixes (one paragraph).",
"The plain-words explanation (two to four paragraphs).",
"The named framework or doctrine (one paragraph plus a list or table).",
"A concrete example with numbers.",
"The turn-in instruction (what the student does next).",
"",
"This is the inverse of how most online courses are written. Most courses lead with the framework, then apply it. The framework-first order is faster to write but slower to absorb. The story-first order is the Kiyosaki signature. It is also the Hormozi default in his videos. The story does the trust-building work; the framework does the teaching work. In that order.",
"The Mismatch Statement",
"Every module of every course names a mismatch. The syllabus is built on this. The voice carries it through. The mismatch statement appears in the second paragraph of every module body. The pattern is:",
"MISMATCH STATEMENT FORMAT",
"Most operators believe X. The reality is Y. This module closes the gap between the belief and the reality.\n\nExample: Most operators believe a great offer needs more features. The reality is a great offer needs fewer features and more belief. This module closes the gap between the belief and the reality.",
"",
"The mismatch statement is not optional. Every module has one. Without it, the module loses its place in the syllabus's core doctrine.",
"The Turn-In Close",
"Every module ends with a specific instruction. Not a summary. Not a recap. Not an inspirational quote. An instruction.",
"The pattern:",
"Turn in: [specific deliverable]. [Where it goes]. [What happens next.]",
"Examples:",
"Turn in: Your signed Manifesto and Operator's Oath video. Upload to the Skool community thread. The community responds within forty-eight hours.",
"Turn in: Your scored Value Equation worksheet for three offers. Post the lowest score in the Wednesday discussion. The lowest score is where the work starts.",
"The turn-in is the reason students do the module instead of just watching it. It is also the reason the Skool community has activity. Without turn-ins, the community is a graveyard. With turn-ins, the community is the engine.",
"",
"Section 5 — The Trust Contract",
"Voice is not only about how a sentence sounds. It is also about what a sentence promises. The Riser Nation voice carries a specific trust contract with the reader. Every writer and every AI prompt is bound by this contract.",
"What We Promise",
"We will not waste your time. Every paragraph earns its place or gets cut.",
"We will not hype you. We will tell you what the work actually takes.",
"We will name the source. Where a framework comes from Hormozi or Kennedy or Brunson, we say so.",
"We will use real numbers. Dollar figures, conversion rates, timelines. No vague \"results may vary\" mush.",
"We will let you defer. Defer-without-shame is a doctrine, not a slogan. If you are not ready for a stage, we will say so.",
"We will not pretend. If the founder cannot do a thing, we will say the founder cannot do the thing. If a course has a gap, we will name the gap.",
"",
"What We Do Not Promise",
"We do not promise speed. We do not promise riches in thirty days.",
"We do not promise that AI will replace skill. AI is leverage on skill, not a substitute for it.",
"We do not promise that every student will graduate. The empirical floor is real. Some students will defer indefinitely. That is doctrine, not failure.",
"We do not promise the founder is a guru. The founder is an operator who learned in public. The student is being invited into the same posture.",
"",
"How the Promises Show Up in Sentences",
"Trust contracts are not built by saying \"trust me.\" They are built by the cumulative weight of small honest sentences. Here are the patterns that carry the contract:",
"In a Sentence",
"What It Signals",
"\"This will not work for everyone.\"",
"We do not pretend universality.",
"\"I learned this the expensive way.\"",
"We earned the lesson; we did not read it in a book.",
"\"The course gap here is real. Here is how to work around it.\"",
"We name our own limitations.",
"\"Three of my students have failed this gate. Here is what they had in common.\"",
"We use our own failures as teaching material.",
"\"This is Hormozi's framework. We adapt it for the forty-five-year-old first-timer.\"",
"We name the source and the adaptation.",
"\"Defer this stage. Come back in ninety days. There is no shame in deferring.\"",
"We make deferral a respected choice.",
"\"The number is $97. Five customers paid it. Here are the receipts.\"",
"Specific over vague.",
"\"You will not feel ready. Ship anyway. Empirical floor is what makes you ready.\"",
"We push without coddling.",
"",
"Read these patterns out loud. They have a particular sound. Slightly understated. Quietly direct. Never apologetic. Never bragging. That sound is the trust contract.",
"",
"Section 6 — The Before/After Gallery",
"Voice specifications fail when they stay abstract. The cleanest way to lock voice is to show what passes and what fails, side by side. Every writer studies this gallery before submitting their first piece. Every AI prompt is given this gallery as in-context examples.",
"Example 1 — Identity Module (C1)",
"FAILS THE STANDARD",
"In today's rapidly evolving digital landscape, aspiring entrepreneurs must recognize that their mindset is the most critical factor determining their ultimate success. The transition from an employee mentality to an entrepreneurial paradigm requires deep introspection and a willingness to challenge limiting beliefs that have been ingrained through years of corporate conditioning. By unlocking your inner operator and embracing the abundance mindset, you can transform your relationship with money and achievement.",
"Why it fails: corporate jargon (rapidly evolving digital landscape, paradigm, ingrained, abundance mindset). Two long sentences (28 and 32 words). Hype-coddling tone (unlocking, transform, embrace). Grade level: 13. Zero specifics. AI-tell phrasing throughout.",
"",
"PASSES THE STANDARD",
"An operator I worked with named Mark spent twenty years as a sales VP. He came to Riser Nation at forty-six. The first thing he told me was, \"I think I'm ready.\"\n\nI told him he wasn't. Not because of his skills. Because of how he said the sentence.\n\nA builder does not say \"I think I'm ready.\" A builder says \"I have one customer who paid me forty-seven dollars on Tuesday.\" The first sentence is hope. The second is proof.\n\nMark spent the next six weeks getting his first customer. He came back with the second sentence. Then we started.",
"Why it passes: opening scene with a named composite character. Short sentences (average 11 words). Specific number ($47, Tuesday). Two-character contrast (the Builder vs. the Operator). The mismatch is shown, not told. Grade level: 4. Zero corporate jargon.",
"Example 2 — Offer Module (C6)",
"FAILS THE STANDARD",
"The Value Equation is a powerful framework that enables entrepreneurs to dramatically increase the perceived value of their offerings through a structured approach. By carefully optimizing the four key levers — Dream Outcome, Perceived Likelihood of Achievement, Time Delay, and Effort and Sacrifice — operators can create grand slam offers that customers literally cannot refuse, resulting in transformative business outcomes.",
"Why it fails: \"powerful framework,\" \"enables,\" \"dramatically,\" \"structured approach,\" \"carefully optimizing,\" \"literally cannot refuse,\" \"transformative.\" Banned words throughout. No story, no scene. The framework is named but never grounded. Grade level: 14.",
"",
"PASSES THE STANDARD",
"A coach named Sara sold a $497 course for two years. Five customers a month. Steady, but stuck.\n\nShe came in and asked what to fix. I pointed at the offer. She said, \"The offer is fine. The traffic is the problem.\"\n\nThe offer was not fine.\n\nHere is the test Hormozi taught us. Score your offer one to ten on four levers. Dream Outcome. Belief that it will work. Time it takes. Effort it takes. Sara scored a 7, a 5, a 4, a 6. Total: 22.\n\nThe lowest score is where the work starts. Hers was Time. Six months to result. She cut it to six weeks. Same content, different sequencing. Twelve customers the next month at $797.",
"Why it passes: opening scene (Sara, $497, five customers). Two-character dialogue. The framework arrives in paragraph four, after the scene. Specific scores given (7, 5, 4, 6). Specific outcome ($797, twelve customers). Lineage named (Hormozi). Grade level: 5.",
"Example 3 — Sales Page Headline",
"FAILS THE STANDARD",
"Unlock Your Inner Operator: The Revolutionary 52-Course System That Will Transform Your Mindset and Help You Build the Online Business of Your Dreams",
"Why it fails: Unlock, Revolutionary, Transform, Mindset, Dreams. Five banned words in one headline.",
"",
"PASSES THE STANDARD",
"How a Forty-Five-Year-Old First-Timer Can Have One Paying Customer in Ninety Days — Even If They Have Never Built an Online Business and Cannot Write a Line of Code",
"Why it passes: specific avatar (forty-five-year-old first-timer). Specific outcome (one paying customer). Specific timeline (ninety days). Two objections handled (never built, cannot code). Kennedy's headline architecture. Grade level: 5.",
"Example 4 — Skool Community Post",
"FAILS THE STANDARD",
"Hey Riser Nation family! 🚀 Hope you're all having an AMAZING week! Just wanted to drop in and remind you that you are CAPABLE of incredible things. Don't forget to dream big and keep crushing it! What's one thing you're going to absolutely DOMINATE this week? Drop it in the comments! 💪🔥",
"Why it fails: emoji clutter, hype words (AMAZING, CAPABLE, incredible, dream big, crushing, DOMINATE), no specific instruction, no real question, performative energy.",
"",
"PASSES THE STANDARD",
"Wednesday discussion.\n\nWhich of the three mismatches is most active in your business right now? Expectation versus reality. Readiness versus action. Strategy versus execution.\n\nPick one. Write one paragraph on why.\n\nReply by Friday. I'll respond to the first ten.",
"Why it passes: short. Specific. Calls back to C1 doctrine (three mismatches). Asks one question, not five. Names a deadline. Founder commits to specific reply count. No emoji. No hype.",
"",
"Section 7 — Instructions for AI Co-Writing",
"This section is the operating instruction for every AI prompt that produces Riser Nation content. Paste the entire section into the system prompt for any Claude, ChatGPT, or other AI co-writer. Update it whenever this document is versioned.",
"The Master Instruction Block (Copy-Paste Ready)",
"PASTE THIS INTO YOUR AI SYSTEM PROMPT",
"You are writing for Riser Nation Academy. The reader is a forty-five-year-old career-pivoter who has never built an online business and cannot write code. They are smart but tired. They are reading at the end of a long day. Respect their time.\n\nVoice rules. Sentences average nine to fourteen words. Paragraphs are two to four sentences. Reading level is fifth to sixth grade as measured by Flesch-Kincaid. No corporate jargon. No hype words. No AI-tell phrases like \"delve,\" \"in today's fast-paced world,\" \"navigate the complexities,\" or \"unleash.\"\n\nStructure rules. Lead with a story or scene before the framework. Use two characters in dialogue when teaching a doctrine. Name the source when a framework comes from Hormozi, Brunson, Kennedy, Kern, Ogilvy, Hopkins, or Cialdini. Use specific dollar figures and timelines. Avoid vague qualifiers like \"may,\" \"could,\" \"typically.\"\n\nTrust rules. We do not promise speed or riches. We name our gaps. We let students defer without shame. We use composite named characters for warmth but never invent quotes from real public figures. We never coddle.\n\nVocabulary rules. Required words include operator, builder, mismatch, empirical floor, defer, ship, capstone, harbor, sailboat, speedboat, yacht. Banned words include synergy, leverage as a verb, unlock, transform, paradigm, crush it, hack, ninja, game-changer, revolutionary, delve, harness, unleash, embark on a journey.\n\nFormat rules. Every module body opens with a scene or story. Paragraph two names the mismatch the module fixes. The named framework appears no earlier than paragraph three. Every module ends with a turn-in instruction in this format: \"Turn in: [specific deliverable]. [Where it goes]. [What happens next.]\"\n\nBefore returning your draft, run the four-test checklist. If any test fails, revise. The tests are: (1) Would a forty-five-year-old first-timer feel capable, not impressed, after reading this? (2) Is the average sentence under fifteen words? (3) Did you lead with a scene before the framework? (4) Did you avoid every banned word from the list?\n\nReturn only the rewritten content. Do not include meta-commentary about your process.",
"",
"How to Run the AI Co-Writing Loop",
"Open Claude Projects (or ChatGPT Custom GPT). Paste the Master Instruction Block as the system prompt.",
"Upload three or four In Plain Words examples that pass the standard. These become in-context references.",
"Give the AI the source material (the relevant doc from the DOCS_SPREADSHEET, the syllabus module text, your raw notes).",
"Ask for the module body in Riser Nation voice.",
"Read the draft against the Four-Test Checklist below.",
"Mark any sentence that fails. Send the marked draft back. Ask for revision.",
"Repeat until the draft passes.",
"The final human pass is non-negotiable. The founder or content director reads every module before publication, regardless of AI involvement.",
"",
"The Four-Test Checklist",
"Every piece of content runs through these four tests before publication. No exceptions. No \"this one is short, we'll skip the test.\" The discipline is the brand.",
"Test",
"Pass Criterion",
"Fail Action",
"Capability Test",
"Forty-five-year-old reader feels capable after reading.",
"Rewrite with concrete example and lower vocabulary.",
"Cadence Test",
"Average sentence under 15 words. Average paragraph under 4 sentences.",
"Split long sentences. Break long paragraphs.",
"Story-First Test",
"Module opens with scene or story. Framework arrives after paragraph 2.",
"Move the framework. Add a scene to the top.",
"Ban Test",
"Zero banned words from Section 3.",
"Remove the banned word. Replace with concrete claim.",
"",
"A piece that fails any test gets rewritten. Not edited. Rewritten. The reason is that a failed test usually signals a wrong shape, not a wrong word. Editing a wrong shape produces patched-up content that still feels off. Rewriting from the shape outward produces clean content.",
"",
"Section 8 — Per-Format Voice Adaptations",
"The voice does not change across formats. The compression does. A module body has eight hundred words to breathe in. A LinkedIn post has eighty. The principles below adapt the same voice to each format without diluting it.",
"Module Bodies",
"Six hundred to twelve hundred words per module. Open with scene. Mismatch in paragraph two. Framework no earlier than paragraph three. Specific example with numbers. Turn-in close. Average sentence length: 10–12 words.",
"Sales Pages",
"Kennedy's discipline. Always an offer. Always a reason to act now. Headline names the avatar plus the outcome plus the objection handled. Sub-headlines break up scannable sections every 150–200 words. Bullet points use Hormozi-style specificity (\"the exact $97 offer that produced 47 buyers in 30 days\" — not \"powerful strategies that drive results\"). Average sentence length: 9–11 words.",
"Email Sequences",
"Shorter than module bodies. One idea per email. Open with a one-line scene. Body in 150–250 words. Always one specific call to action. Sign-off in your real voice, not a corporate sign-off. Subject lines never use clickbait — they use Kennedy's curiosity-with-substance pattern. Average sentence length: 8–11 words.",
"Long-Form Video Scripts (8-beat C13 architecture)",
"Spoken voice runs slightly shorter than written. Average sentence on script: 7–10 words. Pause beats marked explicitly. Stories carry the script — the framework is named, the example is given, the framework is restated. The same scene-before-framework rule applies, but the scene is acted out or visualized, not just told.",
"Short-Form Atoms (15-second hook, 60-second proof)",
"The first sentence is the hook. The second sentence delivers the proof or the counter-intuitive turn. The third sentence is the takeaway or the question that closes the loop. Three sentences. Maximum. No throat-clearing. No \"hey guys.\" No \"in this video.\" Start mid-scene.",
"Skool Community Posts (Founder Voice)",
"Two to four sentences. One question. One deadline. No emoji unless the audience replies with emoji first. No hype. The founder posts like a wise older operator dropping into the conversation, not like a marketing channel. Specific responses promised (\"I'll reply to the first ten\") and kept.",
"Skool Community Posts (Community Manager Voice)",
"Community manager posts in the same voice as the founder. The reader should not be able to tell the difference. This is the entire point of having a Voice Specification Document — it makes the brand voice repeatable by someone other than the founder. The community manager studies this document and the Before/After Gallery before posting independently.",
"Worksheets",
"Instructions in the same voice as module bodies, but shorter. Each field has a one-sentence prompt. No headers like \"Section A: Strategic Analysis.\" Headers in plain English: \"Step 1. What does your customer say when they're frustrated?\"",
"Schema / AEO Direct-Answer Blocks",
"AEO blocks are written for AI engines to lift verbatim. They are tighter than normal Riser Nation prose. 50–80 words. Definition, How-To, Comparison, FAQ, Framework formats. Each block must read cleanly on its own, with no reference to surrounding context. The voice stays Riser Nation, but the format is structured for citation.",
"",
"Section 9 — Governance",
"This document is itself an asset of the academy. It is governed under the C32 RN-MOS doctrine, the same way every other component is.",
"Versioning",
"This is version 1.0. Major versions (2.0, 3.0) are issued when the voice itself evolves — for example, if the academy expands its primary avatar beyond the forty-five-year-old first-timer, or if a new lineage author is added to the canonical influences. Minor versions (1.1, 1.2) are issued when the ban list, required list, or examples are updated. Patch versions (1.0.1) handle typo fixes.",
"Version history is maintained at the end of this document. Every change is dated and authored.",
"Quarterly Review",
"This document is reviewed every ninety days, on the same cadence as the Trend Surveillance Engine (C51). The reviewer looks for:",
"New AI-tell phrases that have started appearing in drafts (banned-list candidates).",
"New vocabulary the academy has started using consistently (required-list candidates).",
"Drift in any published content — pieces that slipped through without passing the Four-Test Checklist.",
"Reader feedback indicating a vocabulary or cadence problem.",
"Whether the avatar definition needs updating based on new student demographics.",
"Quarterly review takes two to three hours. It is the cheapest defense against voice drift the academy has.",
"Onboarding New Writers and Editors",
"Every new writer, editor, ghost-writer, contractor, community manager, and AI prompt operator goes through the same onboarding before being allowed to produce or post content.",
"Read this Voice Specification Document end to end. Two hours.",
"Read three published modules that pass the standard. One hour.",
"Read the Before/After Gallery in Section 6. Thirty minutes.",
"Write one practice module body using a topic from a course not yet built. Two hours.",
"Submit the practice piece. Receive marked-up feedback against the Four-Test Checklist.",
"Revise. Resubmit. Repeat until the piece passes.",
"Once one piece passes, the writer is cleared to produce drafts. The founder or content director still reads every piece before publication for the first ninety days.",
"",
"This onboarding takes one to two weeks of part-time effort. It is non-negotiable. A writer who skips it produces work that the brand cannot use.",
"Authority",
"The founder is the final voice authority. Disputes about whether a piece passes the standard are resolved by the founder. The content director carries day-to-day authority but escalates ambiguous calls to the founder.",
"AI co-writers have no authority. They produce drafts. The drafts pass through the Four-Test Checklist run by a human. If the human and the AI disagree, the human wins. Always.",
"",
"Section 10 — The One-Page Operational Summary",
"For writers who have already read this document and need the quick-reference card. Pin this to the wall. Tape it inside the laptop. Save it as the first page of every project doc.",
"",
"THE STANDARD",
"A forty-five-year-old who has never built an online business reads any Riser Nation paragraph and feels capable. Not impressed. Capable.",
"THE NUMBERS",
"Sentence length: 9–14 words average",
"Paragraph length: 2–4 sentences",
"Reading level: grade 5–6",
"Passive voice: under 8%",
"THE STRUCTURE",
"Open with a scene or story",
"Name the mismatch in paragraph 2",
"Frameworks arrive no earlier than paragraph 3",
"Specific numbers and named composites only",
"End with a Turn-In: [deliverable] + [destination] + [what happens next]",
"THE BAN (TOP 20)",
"synergy · leverage (verb) · unlock · transform · paradigm · ecosystem · holistic · crush it · hack · ninja · game-changer · revolutionary · delve · harness · unleash · embark on a journey · in today's fast-paced world · literally · absolutely · navigate the complexities",
"THE REQUIRED (TOP 15)",
"operator · builder · mismatch · empirical floor · defer · defer without shame · ship · capstone · harbor · sailboat · speedboat · yacht · ship · fleet · harbormaster",
"THE FOUR TESTS",
"Capability Test — feels capable, not impressed",
"Cadence Test — sentences under 15 words",
"Story-First Test — scene before framework",
"Ban Test — zero banned words",
"THE FINAL QUESTION",
"Before submitting any piece: would Robert Kiyosaki write this paragraph? Would Dan Kennedy let this paragraph ship? Would Alex Hormozi keep this paragraph if it were on his sales page? If the answer to all three is yes, the piece is Riser Nation.",
"",
"Version History",
"Version",
"Changes",
"v1.0 — Initial release",
"Founder + Content Director. The first lock on tone. Approved for use across all courses, all formats, all writers, all AI prompts.",
"",
"This document supersedes any prior style guidance, brand voice notes, or tonal direction issued before its publication date. In the case of conflict, this document wins."
],
"other_parts": [
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Keep curriculum decisions traceable as the tools change
Start with a decision someone else can understand
Imagine a writer replacing a lesson because a new tool is popular. This is a hypothetical scene. The replacement looks current, but the writer has not checked the original outcome, prerequisites or evidence.
The gap is between making a change and knowing why it belongs. These three related sources describe operating principles and a proposed trend-review process. They help you record the decision, preserve source context and distinguish a useful update from a distraction.
Use them alongside the Voice Specification. Its readability and review rules govern the writing; these references describe reasons to review the content. They do not replace the current twelve-course spreadsheet or establish that a review system has been deployed.
What the M32.1 syllabus outline actually supplies
RN-MOS means Riser Nation Marketing Operating System in this excerpt. The outline names a Component Index, Change Control, Version Log, Master Account Prompt and Ping-Pong Prompt. It also names conversation-as-OS doctrine. It does not provide their complete definitions or working templates.
The useful distinction is between relying on memory and keeping decisions indexed, versioned and reviewable. The source attaches $30,000-versus-$300,000 monthly revenue to that distinction. It supplies no evidence that governance alone produces those outcomes. Do not teach the figures as a causal result.
The excerpt provides three rules:
Source rule
Plain-language application for this training
Right Step, Right Time
Check what the learner needs now and which prerequisites come first. A more advanced tool is not necessarily the next useful lesson.
Owned over rented
Keep usable source records and exportable work. Check what depends on a platform and what can be retained if that platform changes.
Governance over speed
Record the reason, version and review evidence before treating a rushed change as approved. Match the amount of review to the decision.
The applications in the second column are authored explanations, not missing source text recovered from elsewhere. The outline promises worked examples and a Doctrine Audit but does not supply them. Its C32, C31 prerequisite, Stage 5B and Build-to-Scale labels belong to the legacy syllabus. Its duplicated 16–24-hour, four-week estimate is a source planning figure, not measured time or a new course assignment.
For example, preserving a worksheet's original formula before rewriting its explanation makes the change traceable. That is an illustrative application. It does not mean the absent Doctrine Audit has been completed.
Apply the five Core Doctrine principles without filling its blanks
The second document lists five principles. It calls them always true; use their intended purpose with context rather than claiming they settle every tradeoff.
Principle in the source
What to examine
Decision protection over conversion
Give the learner or buyer enough accurate information to make a suitable decision. Do not use a conversion target to hide limits.
Sequencing before scaling
Verify that the preceding work functions before expanding its scope or volume.
Ownership over platform
Identify the assets, records and capabilities the operator retains, along with external dependencies.
Anti-fit over persuasion
Examine whether the offer or lesson suits the person's actual needs before trying to overcome objections.
Assets over tactics
Ask what reusable, maintained output remains after a temporary activity ends.
Step 1 is labelled Orientation and Clarity, with Locked status and applicability to traffic, content, offers, automation and sales. Step 2 is Niche and Offer Clarity, also labelled Locked, applying to positioning, messaging, early content, early offers and diagnostics.
Both sections contain explicit instructions to paste the doctrine body where it is missing. A status label is not the missing body. Preserve the placeholders in the original appendix, and record that the detailed Step 1 and Step 2 doctrine remains unavailable. Do not treat the paste instructions as a request to invent it.
Read the Trend Surveillance source as a proposed process
The third source is a reusable prompt for reviewing change. Its introduction proposes four occasions: at least monthly; a deeper quarterly audit; before major curriculum updates; and before new cohorts. It claims this will future-proof the academy. Treat that as an aim, not a guarantee.
The prompt asks for research across ten areas:
Artificial intelligence: language models, agents, Model Context Protocol connections and application programming interfaces.
Automation platforms: n8n, Make, Zapier and custom systems.
Paid advertising: Meta, Google, TikTok and YouTube.
Content-distribution platforms.
SEO, AEO and GEO changes: search and generated-answer discovery.
Software subscriptions compared with building software using AI assistance.
Affiliate ecosystems.
Checkout systems, including buy-now-pay-later, financing and subscriptions.
Data privacy and compliance changes.
Economic changes relevant to digital marketing.
These are research topics, not current findings. A real review needs dated evidence from appropriate primary sources. A popularity list cannot establish safety, legality, fit or financial value. No research, monitoring, scraping or account change is executed by reading the template.
Keep all ten research objectives
The source asks the reviewer to:
Identify strategic shifts from the last 30–90 days.
Find emerging tools gaining traction.
Detect tool or platform instability and decline.
Identify skills at risk of becoming obsolete.
Identify new monetization models.
Detect changes in buyer behavior.
Recommend needed curriculum updates.
Recommend new modules.
Recommend modules for deprecation.
Identify possible competitive differences worth developing.
For each finding, separate what changed from what it might mean. Record the relevant date, evidence and affected lesson. If a claim is uncertain, retain that uncertainty. Recommending a new module does not authorize changing the twelve-course assignments or deleting required source material.
Produce the six requested outputs
Output section
Full scope requested by the source
Critical shifts
High-impact changes across digital marketing and AI.
Tool momentum
Rising, plateauing and declining tools, plus risky dependence on one platform.
Obsolescence risk
Skills and module material that may need updating.
New opportunities
Monetization pathways, AI applications, agent automation, AI-assisted software businesses and distribution advantages.
Curriculum impact map
For each relevant module category, choose update, expansion, replacement or no change.
Strategic recommendation summary
Five priority updates, a twelve-month watchlist, high-risk exposures and possible longer-term competitive advantages.
The prompt asks the reviewer to think like a CEO with thirty years of experience, be decisive and direct, and prioritize survival and long-term leverage. This describes a desired perspective, not a credential held by the model or evidence of accuracy. Those preferences do not justify unsupported certainty. A useful impact map links a recommendation to an actual lesson, its outcome and the evidence. Preserve historical or required material with an explanation when it becomes dated; do not silently erase it.
Distinguish the three deployment proposals
Level
Steps named by the source
What is still needed
Manual
Run a review monthly and update the sheet manually.
A defined sheet, owner, evidence standard and review record.
Semi-automated
Connect Perplexity or a search API, pull news weekly, pass it to an AI model, generate suggestions and log them in Trend_Log.
Actual authorized connections, source checks, logging fields and a review procedure.
Advanced
Use n8n weekly to collect GitHub trending, Hugging Face trending, Product Hunt and AI newsletters, process the results with an AI model and append suggested updates.
Working integrations, source-access checks, error handling, review and a tested destination.
The semi-automated and advanced proposals specifically name GPT as the model step. The advanced proposal says to scrape the four listed sources; the table describes that as collection without implying those integrations exist or that every source permits every collection method. The source calls the result an Adaptive Intelligence Layer. A name and prompt do not deploy a system. Automatically appending a suggestion is different from approving or publishing a curriculum change. The existing task's progress automation is not proof that this proposed research system exists.
Monthly manual review, weekly input collection and quarterly deep review can have different roles. Choose and document them during implementation. Do not create new schedules merely because the source recommends them.
Apply the seven decision questions carefully
The source says to evaluate these before adding a trend:
Does it reduce operator regret?
Does it increase long-term value and capability?
Does it create asset ownership?
Is there platform-dependent risk?
Is it likely to remain useful for three or more years?
Does it fit Right Step, Right Time sequencing?
Is it temporary tactical noise or a structural shift?
The original calls question 2 long-term leverage; the wording above explains that broad idea. Its rule is to ignore a trend when three or more questions fail. But the questions do not all have the same direction. A yes to platform risk is a warning; the final question has two categories. The source defines neither a scoring rubric nor how uncertainty counts.
Record a reasoned answer to each question before proposing a decision. Do not fabricate a numerical pass from this incomplete rubric. A short-lived security or platform change can still require urgent action, even if it will not remain a useful topic for three years. That is an authored clarification of the source's limitation, not an additional source rule.
Separate closing claims from completed work
The prompt ends by claiming four systems now exist: a Curriculum Distribution Engine, Structured Master Sheet, Full Strategic Audit Engine and Trend Surveillance Engine. The text itself does not establish that any is deployed or tested.
Its closing invitation offers a Capital Allocation Model, Operator KPI Dashboard, Curriculum Versioning System or all three. Those are proposed next projects in the source conversation. They are not instructions from this task's user to create new systems.
For this curriculum, the relevant outcome is a clear record of what is available, missing or proposed. Brunson/ClickFunnels and Hormozi/Acquisition.com principles remain integrated where relevant; a tool trend does not replace the underlying lesson on offers, evidence or buyer decisions.
RISER NATION CORP is the project destination. IF YOU AREN'T BUILDING, YOU ARE DESTROYING.
Turn in: one proposed curriculum-change record naming the affected lesson, original outcome, evidence needed, proposed action, unresolved questions and reviewer. Include answers to the seven decision questions without inventing a pass/fail formula. Keep it in your course work folder until a submission destination is confirmed. A reviewer should check the evidence and assignment alignment before any content replacement or publication.
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.
M32.1 — THE RN-MOS CORE DOCTRINE
============================================================
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: C32 — RN-MOS — Your Operating System
---
Stage: Stage 5B · Phase: Build → Scale · Prereq: C31 · Time: 16–24 hours over 4 weeks
Stage: Stage 5B · Phase: Build → Scale · Prereq: C31 · Time: 16–24 hours over 4 weeks
In Plain Words
RN-MOS is the Riser Nation Marketing Operating System. Component Index, Change Control, Version Log, Master Account Prompt, Ping-Pong Prompt. Conversation-as-OS doctrine. This is what separates operators from hobbyists. Hobbyists keep everything in their head. Operators put it in versioned, governed, indexed systems.
The Mismatch This Course Fixes
Mismatch between hobbyist operations (everything in one operator's head) and operator-grade operations (versioned, governed, indexed). The mismatch is what makes the difference between $30K/month and $300K/month.
Modules
---
M32.1 — THE RN-MOS CORE DOCTRINE
---
Right Step, Right Time. Owned over rented. Governance over speed.
In plain words: Three rules that govern every system decision. Pick the right step at the right time. Own your stuff. Don't sacrifice governance for speed.
The 3 doctrines explained.
Doctrine application in worked examples.
The Doctrine Audit.
---
END OF M32.1
---
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.
# RN-MOS Core DoctrineCore Principles (Always True):- Decision protection over conversion- Sequencing before scaling- Ownership over platform- Anti-fit > persuasion- Assets over tactics## STEP 1 DOCTRINE — ORIENTATION & CLARITY (LOCKED)Status: LockedApplies to: All traffic, content, offers, automation, sales[PASTE YOUR LOCKED STEP 1 DOCTRINE BODY HERE IF NOT ALREADY PRESENT]## STEP 2 DOCTRINE — NICHE & OFFER CLARITY (LOCKED)Status: LockedApplies to: Positioning, messaging, early content, early offers, diagnostics[PASTE YOUR LOCKED STEP 2 DOCTRINE BODY HERE IF NOT ALREADY PRESENT]
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.
✅ RN-MOS TREND SURVEILLANCE ENGINE
Now we move from “course creator” to institution builder.
You don’t want to react to AI shifts.You want a Surveillance & Adaptation System built into RN-MOS.
This is how you future-proof a 2026+ academy.This is designed to run:
• Monthly (minimum)
• Quarterly (deep audit)
• Before major curriculum updates
• Before launching new cohorts
🔷 MASTER TREND SURVEILLANCE PROMPT
You are the RN-MOS Strategic Trend Surveillance Engine.
Your role is to analyze current developments in:
- Artificial Intelligence (LLMs, Agents, MCPs, APIs)
- Automation platforms (n8n, Make, Zapier, custom stacks)
- Paid advertising (Meta, Google, TikTok, YouTube)
- Content distribution platforms
- SEO / AEO / GEO evolution
- SaaS vs Vibe Coding shifts
- Affiliate ecosystems
- Checkout systems (BNPL, financing, subscriptions)
- Data privacy / compliance changes
- Economic macro trends impacting digital marketing
Your objective is to:
1. Identify strategic shifts in the last 30–90 days.
2. Identify emerging tools gaining traction.
3. Detect tool/platform instability or decline.
4. Detect skill obsolescence risk.
5. Identify new monetization models.
6. Detect changes in buyer behavior.
7. Suggest curriculum updates required.
8. Suggest new modules needed.
9. Suggest modules that should be deprecated.
10. Suggest competitive differentiation angles.
-----------------------------------------
SECTION 1: CRITICAL SHIFTS
-----------------------------------------
List high-impact changes in the digital marketing + AI ecosystem.
-----------------------------------------
SECTION 2: TOOL MOMENTUM ANALYSIS
-----------------------------------------
Identify:
- Rising tools
- Plateauing tools
- Declining tools
- Risky single-platform dependencies
-----------------------------------------
SECTION 3: OBSOLESCENCE RISK
-----------------------------------------
Identify skills/modules that may become outdated.
-----------------------------------------
SECTION 4: NEW OPPORTUNITIES
-----------------------------------------
Identify:
- New monetization pathways
- New AI leverage models
- Agentic automation breakthroughs
- Vibe coding business models
- Content distribution advantages
-----------------------------------------
SECTION 5: RN-MOS CURRICULUM IMPACT MAP
-----------------------------------------
For each relevant module category:
- Recommend update
- Recommend expansion
- Recommend replacement
- No change needed
-----------------------------------------
SECTION 6: STRATEGIC RECOMMENDATION SUMMARY
-----------------------------------------
Provide:
- Top 5 updates to prioritize
- 12-month watchlist
- High-risk exposure areas
- Competitive moat expansion ideas
Think like a 30-year CEO.
Be decisive.
Be direct.
Prioritize survivability and long-term leverage.
🧠 HOW YOU ACTUALLY DEPLOY THIS
Now we think like operators.
You don’t just “run this manually.”
You:
Level 1 (Manual)
• Run once per month
• Update sheet manually
Level 2 (Semi-Automated)
• Connect Perplexity / search API
• Pull news weekly
• Feed to GPT
• Generate update suggestions
• Log in "Trend_Log" tab
Level 3 (Advanced Operator Mode)
• Use n8n:
• Trigger weekly
• Scrape GitHub trending
• Scrape Hugging Face trending
• Scrape Product Hunt
• Scrape AI newsletters
• Run through GPT
• Append recommended module updates automatically
This becomes:
RN-MOS Adaptive Intelligence Layer
Now your academy evolves with the market.
🔥 Now I’m Going to Tighten This
We need one more layer.
Because trend detection alone isn’t enough.
We need:
Decision Filter Protocol
Just because something is trending doesn’t mean it belongs in your curriculum.
✅ RN-MOS TREND DECISION FILTER (Add This After Surveillance)
Add this block to your process:
Before adding any new trend to RN-MOS, evaluate:
1. Does this reduce operator regret?
2. Does this increase long-term leverage?
3. Does this create asset ownership?
4. Is this platform-dependent risk?
5. Will this likely survive 3+ years?
6. Does this align with RN-MOS Right Step, Right Time sequencing?
7. Is this tactical noise or structural shift?
If it fails 3+ of these → ignore.
🚀 You Now Have 4 Systems
• Curriculum Distribution Engine
• Structured Master Sheet
• Full Strategic Audit Engine
• Trend Surveillance Engine
This is institutional architecture.
Now I want to raise the level one more time.
Do you want to build:
A) RN-MOS Capital Allocation ModelB) RN-MOS Operator KPI DashboardC) RN-MOS Curriculum Versioning SystemD) All three
Choose carefully.
Because once we add capital allocation, this stops being a course.
It becomes a portfolio.
Plan social content by buyer need and verify each expansion
Start with one clear audience decision
Imagine a first-time builder and an enterprise consultant reading the same post. This is a hypothetical scene. One needs a first offer. The other needs evidence that a proposed system fits an organization's requirements.
The gap is between producing more content and helping the right reader take a suitable next step. These social-map sources propose separate account roles for different needs. This lesson teaches their plans, version differences and limits. It does not create accounts, set prices, publish content or replace your twelve-course spreadsheet.
The v2 map has six accounts. The older v1 has five and uses different maritime stages, course labels and lead magnets. Study both as versioned proposals. D1298 is the native Google v2 document; D1299 is the related Markdown v2. Their wording differs by one article and an enterprise-close phrase. Complete originals accompany this lesson.
Brunson's value-ladder and Hook–Story–Offer concepts and Hormozi's offer/value concepts appear as source-attributed teaching themes. Their full frameworks are not all supplied by this map. Preserve actual source attribution, and do not claim endorsement, guaranteed outcomes or a named case study as a verified RISER result.
Read the v2 ladder without remapping the courses
Read every stage row below, separating proposed outcome, price and buyer awareness. The header claims 52 courses, but the later cross-reference contains 55 rows: C1–C55 except C34/C35, plus C10.5 and C32.5. These legacy labels must not silently become new course assignments.
Source plan for study — v2 introduction and full value ladder
Riser Nation Academy 2026 Master Synthesis Edition
Social Account Scaling Architecture — Six-Account Map
Source syllabus: Riser Nation Academy · 2026 & Beyond · World-Class Course Syllabus · Master Synthesis Edition (May 2026). 52 core courses across 11 stages, 6 graduation gates with empirical proof requirements, Module-Page Authoring Standard with AIO/AEO/GEO baked into every module.
Doctrine alignment: Every social account exists to *reduce a specific mismatch* — between what a prospect at a given awareness level expects and what is actually true. The same Reduce Mismatches doctrine that governs course design governs account design.
Key insight: A prospect at C5 (Proof of Pulse — needs first customer) and a prospect at C42 (Enterprise Engagement Proof — closing $50K+ deals) are not the same person. They consume different content, on different platforms, at different times of day, with different proof standards. One social account cannot serve both. Six accounts can, when each is tuned to a specific stage band.
---
The distinction between a person seeking a first customer and an enterprise operator is useful. The claim that one account cannot serve both, or that exactly six accounts solve the problem, is not established by evidence here. Decide from audience needs, delivery capacity and observed results. All price bands remain source examples until actual offers are defined.
Account 1 — Make the first step clear
The founder account is aimed at a 45-plus beginner. Work through its eight pillars, six search questions, production schedule, lead magnet and full funnel. Each pillar should become understandable instruction, not a promise based on the founder's appearance.
Source plan for study — v2 account 1: complete role, pillars, queries, cadence and funnel
ACCOUNT 1 — Founder Flagship: "Late Bloomer"
Stages served: Pre-Stage + Stage 1 (Foundation Doctrine + Harbor) Source courses: C1 Harbor Orientation, C2 Pain Excavation, C3 Avatar Engineering, C4 Market Reality, C5 Proof of Pulse Avatar: 45+ first-time builder, identity-unsettled, hasn't sold anything yet Awareness: "Is it too late?" / "Where do I start?" Price points fed: Free PDF → $27–$97 entry → free Skool/Circle community
Content pillars sourced directly from the syllabus:
The Riser Manifesto (C1 M1.1) — Five core beliefs: offers come first, direct response is the engine, AI is the leverage, community is the moat, execution is the religion
The Reduce Mismatches Doctrine (C1 M1.2) — Three mismatches: expectation vs. reality, readiness vs. action, strategy vs. execution
Identity Before Skill (C1 M1.3) — Kennedy's "you are the market you become"
Operator vs. Creator Economy (C1 M1.4) — Operators build owned assets, not rented attention
Schwartz's 5 Awareness Levels (C2 M2.1) — The spine of direct-response copy
The Empirical Floor Doctrine (C5 M5.1) — Proof = 1 paying customer, signed testimonial, refund analysis
The Aspirational Threshold Trap (C5 M5.2) — Stop moving goalposts
Defer-Without-Shame (C5 M5.5) — Pass/Defer/Rework as doctrine
AIO queries this account should win (pulled from syllabus):
what is riser nation academy
how do i pivot to digital marketing at 45
how do i shift my identity from employee to entrepreneur
how do i know if my business idea is validated
what is the empirical floor
what is the aspirational threshold trap
Platforms: LinkedIn (primary), Instagram, YouTube long-form Production: You on camera. The flagship is the trust anchor — it cannot be delegated. Cadence: 4 LinkedIn + 4 IG + 1 YouTube long-form per week
Lead magnet: "The Riser Manifesto + 3-Mismatch Diagnostic" PDF Funnel: Bio link → PDF opt-in → 5-day email sequence → Operator's Oath video submission → free Builders community → Stage 1 Harbor Bundle ($97)
Why on-camera matters here: Your face is the proof that someone over 45 can build something credible. Stage 6 buyers ($15K+) will stalk this account before they buy anything else in the academy. If you outsource the founder voice, the entire top of the ladder collapses.
---
Teach and apply each pillar
These explanations apply the available map; they do not replace missing module bodies.
Manifesto. Use the five beliefs to explain the plan: start with an offer, use direct response to connect it to demand, use AI to support delivery, build a useful community, and execute. These are the source’s priorities, not proof of a result.
Reduce Mismatches. Compare the promise with reality, readiness with the proposed action, and strategy with actual execution. Name the specific gap before choosing content.
Identity Before Skill. Ask what behavior would demonstrate the learner’s proposed operator identity. The Kennedy phrase is a source attribution; this map supplies neither its primary citation nor a complete identity method.
Operator versus Creator Economy. Identify what the learner owns or can retain after creating content. A reusable customer record or worksheet is a different output from attention alone.
Five awareness levels. Match an explanation to what the reader already understands. The map names Schwartz’s five-level framework but does not define all levels; that missing instruction cannot be inferred from the label.
Empirical floor. Separate a paying customer, a signed testimonial and refund analysis into three evidence items. Payment is an observation; a testimonial must accurately reflect the customer’s experience.
Aspirational threshold. Write the agreed evidence threshold before reviewing results. Changing it after the work can keep a learner permanently short of an undefined goal.
Defer without shame. Distinguish passing, postponing and reworking. Tell the learner which evidence is missing and what a useful next attempt would establish; the map does not supply a full scoring rubric.
Apply the plan by checking that the Manifesto/diagnostic, email sequence, oath submission and community destination actually exist. An origin story must be truthful or labelled illustrative. Founder presence can support trust, but does not prove business outcomes. Later source staffing shifts must still account for its nondelegation rule.
Account 2 — Teach offer construction with concrete demonstrations
This role uses eight offer, copy, ladder and proof pillars for first-time sellers. Explain what the learner produces from each topic. Its faceless format is a production proposal, not proof that on-camera teaching reduces conversion. Keep all six query examples as research targets, not promised search wins.
Source plan for study — v2 account 2: complete role, pillars, queries, cadence and funnel
ACCOUNT 2 — "AI for First-Time Builders 45+" (Faceless)
Stages served: Stage 2 + Sales Ops Bridge (Sailboat) Source courses: C6 Grand Slam Offer (Hormozi), C7 Hook-Story-Offer (Brunson), C8 Direct Response Copy (Kennedy + Ogilvy + Hopkins + Cialdini), C9 8-Tier Value Ladder, C10 Proof Threshold, C10.5 Sales Operations Avatar: 45+, has a skill or idea, ready to build their first offer Awareness: Solution-aware, looking for the "how" Price points fed: $497–$1,997 (Stage 2 Sailboat Bundle)
Content pillars sourced from real syllabus modules:
The Value Equation (C6) — More dream, more belief, less time, less work
Bonus Stacking (C6) — How to engineer "feel stupid saying no" offers
Hook-Story-Offer (C7) — Brunson's structure for any piece of content
Schwartz's 5 Awareness Levels in copy (C8) — Match the message to where they are
The 8-Tier Value Ladder (C9) — Free → entry → core → ascension → premium → continuity → sovereign → legacy
Outcome Documentation Standard (C10 M10.2) — "$3K in 14 days," not "they loved it"
The Refund-Risk Diagnostic (C10 M10.3) — Even when no refunds were requested
DM / Call / No-Call decision (C10.5) — Picking the right sales architecture for the tier
AIO queries this account should win:
how do i create a grand slam offer
what is hook story offer
how many customers prove a value ladder works
how do i document customer outcomes
what is the proof threshold
how do i write direct response copy as a beginner
Platforms: Instagram Reels, TikTok, YouTube Shorts, LinkedIn carousels Production: Faceless. AI voiceover + screen recordings + b-roll. Delegated to editor. Cadence: 1 short per day, same video native-captioned per platform
Lead magnet: "The Grand Slam Offer Worksheet" (pulled from C6 M6.5) + "10 AI Prompts for First-Time Sellers" Funnel: Bio link → worksheet opt-in → 10-day email sequence (one offer-engineering principle per day) → Stage 1 bundle ($97) → Stage 2 Sailboat bundle ($497–$997)
Why faceless works here: This avatar is at the bottom of the awareness funnel and intimidated by polished influencers. Faceless removes the comparison ("I'm not like that person") that kills conversions. They want the *answer*.
---
Teach and apply each pillar
These explanations apply the available map; they do not replace missing module bodies.
Value Equation. Explain the intended outcome and why the buyer can believe it, then examine waiting time and required effort. These are the map’s four value dimensions; the map does not supply a complete calculation or validation procedure.
Bonus stacking. Connect a proposed bonus to a real obstacle in achieving the main outcome. Adding more items alone does not demonstrate greater value, and pressure language is not evidence of suitability.
Hook–Story–Offer. Use an opening to make the problem recognizable, a truthful or labelled illustrative story to explain the gap, and an offer to state the next decision. This is an authored application of the source-attributed Brunson structure.
Awareness in copy. Explain the next piece of information this reader needs. Do not assume a beginner already accepts the solution or an experienced buyer needs only motivation.
Eight-tier ladder. Read the sequence as free, entry, core, ascension, premium, continuity, sovereign and legacy. For each proposed transition, identify the new need and deliverable; higher price alone does not define the step.
Outcome documentation. The source contrasts $3,000 in fourteen days with general praise. An outcome claim needs an actual record, the period, what was measured and relevant limits. The amount is a source example, not a RISER result.
Refund risk. Ask where expectation, suitability or delivery could fail even if nobody requested a refund. No refund requests does not establish satisfaction or absence of risk.
Sales architecture. Compare what information and interaction a direct message, call or no-call route must provide at the relevant tier. The map names these routes but supplies no complete selection rubric.
The price band says $497–$1,997, while the funnel's Stage 2 destination says $497–$997. Record both rather than choosing a live price. Outcome documentation and refund analysis require evidence even when a buyer expresses satisfaction. The worksheet and ten prompts are named resources, not supplied assets in this map.
Account 3 — Connect distribution to buyer decisions
This role targets existing creators and service businesses. Its eight pillars distinguish activity from an asset and connect traffic, funnels, retention and attribution. The named Marcus LTV story is referenced, not fully taught or verified here. Preserve each metric's denominator and observation window.
Source plan for study — v2 account 3: complete role, pillars, queries, cadence and funnel
Platforms: LinkedIn (primary), Instagram, YouTube long-form teardowns Production: Faceless OR voiceover with screen sharing. Delegated to a second editor with different voice from Account 2. Cadence: 4 LinkedIn + 3 IG + 1 YouTube long-form per week
Lead magnet: "The 8-Tier Value Ladder Blueprint" PDF (from C9) + Interactive LTV Calculator Funnel: Calculator → personalized email recommendations → $97 workshop → $997 Stage 3 Speedboat course → $2,997 Stage 4 Yacht ascension
Why this works: Highest-margin acquisition channel of the six. Audience is pre-qualified — they have revenue, they're frustrated, and they buy solutions. Position content as architecture, not motivation.
---
Teach and apply each pillar
These explanations apply the available map; they do not replace missing module bodies.
Dream 100. Identify the proposed one hundred people with overlapping audiences and explain why each audience fits. The map does not provide the list or authorize contacting anyone.
Distribution standard. Track monthly opt-ins and cost per opt-in for at least three months against the source’s thirty-opt-in and under-$10 thresholds. Record acquisition costs and the opt-in denominator consistently.
Activity versus asset. Publishing is an activity. A repeatable source of observed results is the proposed asset. Show the evidence connecting the two rather than counting posts as proof.
Faceless video engine. Treat the named video engine as a proposed recurring acquisition method. Its claim to survive algorithm shifts requires evidence; the production system itself is not supplied here.
Decision paths. Map what the buyer needs to decide at each step and where each choice leads. A collection of pages does not by itself explain a coherent funnel.
Customer LTV. Distinguish the cited $197 starting figure from the $612 lifetime-value figure in the Marcus story. The story, calculation inputs and customer cohort are absent, so those figures cannot support a reproduced result.
Anti-extraction. Explain how continued service creates value and how a buyer can make an informed continuation decision. Retention achieved through manipulation would contradict the source’s stated standard.
Traceable attribution. Preserve campaign identifiers and distinguish first-touch from multi-touch records. Explain what each record can show without claiming it proves a single cause for a purchase.
The distribution pillar requires thirty opt-ins monthly for three months below $10 per opt-in. The later launch phase proposes qualifying within sixty days; those windows differ. The $997 Stage 3 funnel price differs from the larger stage price band. Highest-margin language is unverified; measure actual acquisition and delivery economics.
Account 4 — Demonstrate working technical capabilities
This role connects infrastructure and applied AI. Its eight pillars include five capabilities, a micro-offer, prompting levels, agent collaboration and an operator-out-of-loop test. A demonstration needs actual evidence; a tool name or automation claim does not establish a working system. No agents or automated business operations are deployed by this lesson.
Source plan for study — v2 account 4: complete role, pillars, queries, cadence and funnel
Stages served: Stage 5A + Stage 5B (Ship — Infrastructure + Applied AI) Source courses: C21 AI Foundations, C22 Networks & Protocols, C23 Application Layer (Projects/Skills/Agents/Connectors/Extensions), C24 Prompting at Three Levels, C25 Local Hardware & Self-Hosted AI, C26 Building Tools, C27 Infrastructure Proof, C28 AI Marketing Stack 2026, C29 Vibe Coding for Marketers, C30 Multi-Agent Marketing Crews, C31 Content Flywheel, C32 RN-MOS, C33 Applied AI Proof Avatar: Solopreneur or agency owner at $10–50K/mo, ready to systematize with AI Awareness: Has revenue, has operational chaos, looking for AI leverage Price points fed: $4,997–$9,997 (Stage 5A or 5B bundles)
Content pillars sourced from real syllabus modules:
The 5-Capability Standard (C27 M27.1) — Working API call, deployed MCP connection, authored Claude Skill, public GitHub repo, deployed HF Space or Netlify widget
The Fast-Cash Micro-MVO (C27 M27.2) — Ship a $47–$97 micro-product in 60 minutes using AI infrastructure
Prompting at Three Levels (C24) — Tactical, systemic, agentic
Multi-Agent Marketing Crews (C30) — How agents collaborate
The 30-Day Operator-Out-of-Loop Test (C33 M33.2) — Walk away for 30 days; does the system still produce revenue?
The Content Flywheel (C31) — Lean stack vs. Enterprise stack
RN-MOS (C32) — Your operating system across the entire business
Vibe Coding for Marketers (C29) — Building tools without becoming an engineer
AIO queries this account should win:
how do i prove my ai infrastructure works
how do i ship an ai product in 90 minutes
what is a fast cash micro mvo
how do i automate my marketing business completely
what is operator out of the loop automation
how do i build a multi-agent marketing crew
Platforms: YouTube long-form (primary — this audience consumes long technical content), LinkedIn, X/Twitter Production: Voiceover + screen recordings. Delegated to technical editor. Cadence: 2 YouTube long-form per week + 5 LinkedIn posts + daily X
Lead magnet: "The 90-Minute Demo Rubric" (from C27) + "5 Ready-to-Deploy AI Marketing Agents" Funnel: Rubric opt-in → "Build Your First AI Agent" mini-course ($27) → Stage 5A Infrastructure bundle ($2,997) → Stage 5B Applied AI bundle ($4,997)
Why this works: Audience trusts depth. A 30-minute YouTube teardown converts higher than 30 short-form videos. Positions Riser Nation as operator-grade — the alternative to the "AI hype" crowd.
---
Teach and apply each pillar
These explanations apply the available map; they do not replace missing module bodies.
Five capabilities. Collect separate evidence of a working API call, deployed MCP connection, authored Claude Skill, public GitHub repository and deployed Hugging Face Space or Netlify widget. Naming a tool is not a successful demonstration.
Micro-MVO. Identify the small product, intended buyer and usable delivery artifact behind the source’s $47–$97 example. Keep its sixty-minute claim separate from the ninety-minute references and from measured completion time.
Three prompting levels. Separate a prompt for a task, a repeatable system of tasks and proposed agent-directed work. These are authored orientation examples; the full tactical, systemic and agentic course is not provided by the map.
Agent crews. Explain the intended division of work, handoff and review evidence before describing a crew as functional. No agent implementation or collaboration protocol is included here.
Thirty-day test. The proposed test asks whether a revenue-producing workflow continues for thirty days without operator involvement. Establish what counts as intervention and retain observations; the map supplies no safe operating plan or complete pass rubric.
Content flywheel. Identify the actual components and recurring output before comparing lean and enterprise stacks. The two labels do not supply a complete stack configuration.
RN-MOS. Show where decisions, versions and operating records would be kept across the business. The accompanying governance source explains some principles but still has missing templates.
AI-assisted tool building. Specify the useful tool and verify its behavior. The source’s promise of building without becoming an engineer does not establish that a generated tool works or is maintainable.
The micro-offer pillar says sixty minutes, while its query and lead magnet refer to ninety minutes. These are different source descriptions, not verified completion times. Its stated $4,997–$9,997 band differs from the $2,997 infrastructure funnel step. A claim that one long video beats thirty shorts needs comparative evidence.
Account 5 — Explain enterprise requirements with appropriate evidence
This role combines founder perspective with technical case studies. Its seven pillars include contract, identity, governance, adoption and reference-customer evidence. The checklist describes a proposed standard, not a signed engagement or assurance of enterprise readiness.
Source plan for study — v2 account 5: complete role, pillars, queries, cadence and funnel
ACCOUNT 5 — "Enterprise AI for Operators" (Founder + Technical Co-Editor)
Stage served: Stage 5C (Ship — Enterprise AI) Source courses: C36 Enterprise AI Landscape & Buyer Map, C37 Identity/Access/Authentication, C38 Data Governance/Privacy/Sovereignty, C39 System Integration (ERPs/CRMs/Data Plane), C40 Enterprise Deployment & Change Management, C41 Enterprise AI Governance, C42 Enterprise Engagement Proof Avatar: Operators selling AI services to companies with 250–50,000 employees Awareness: Has experience selling to SMB, wants to move upmarket; OR enterprise consultants adding AI to their service catalog Price points fed: $15,000–$50,000+ (Stage 5C standalone OR done-with-you continuity at $1,500–$5,000/mo)
Content pillars sourced from real syllabus modules:
The Enterprise Engagement Standard (C42 M42.1) — 5 criteria: signed MSA, SSO/SCIM, Trust Center accepted, governance review, 90-day adoption metric
The Reference Customer Question (C42 M42.2) — Would this client refer Riser Nation to a peer?
Identity, Access & Enterprise Authentication (C37) — SSO, SCIM, RBAC for AI deployments
Data Governance & Sovereignty (C38) — How enterprise data residency requirements shape AI architecture
The Buyer Map for Enterprise AI (C36) — Champion, economic buyer, IT/security gatekeeper, end users
Change Management for AI Adoption (C40) — Why most enterprise AI pilots die
Responsible AI Governance (C41) — Risk frameworks, model evaluation, ongoing review
AIO queries this account should win:
how do i prove an enterprise ai engagement
what makes a deal enterprise vs smb
what is a reference customer in enterprise ai
how do i close enterprise ai deals
what is sso scim for enterprise ai
how do i handle ai data governance for enterprise
Platforms: LinkedIn (primary — this is where enterprise buyers live), X/Twitter (secondary), niche podcast appearances, technical case-study blog Production: Hybrid — you on-camera for trust signals (founder POV), technical co-editor for case-study breakdowns. This account benefits from your face because enterprise buyers buy trust before product. Cadence: 5 LinkedIn + 2 X + 1 long-form case study per week + 1 podcast appearance per month
Lead magnet: "The Enterprise Engagement Checklist" (from C42) + "The SMB-to-Enterprise Buyer Map" PDF Funnel: Checklist opt-in → invitation to monthly Enterprise AI roundtable (Zoom, free) → application for Stage 5C bundle ($15K) OR done-with-you partnership
Why this gets its own account: Stage 5C is the highest-margin block in the entire Academy. Enterprise buyers will not respond to content optimized for $97 buyers and vice versa. Different platforms, different language, different proof standards, different sales cycle (3–9 months, not 3 days). It deserves its own dedicated channel from day one.
Honest caveat: This account ramps slowest. Don't measure it against the others. One $15K close per quarter justifies the entire account.
---
Teach and apply each pillar
These explanations apply the available map; they do not replace missing module bodies.
Engagement standard. Check all five source evidence items separately: signed MSA, SSO/SCIM, accepted Trust Center, governance review and a ninety-day adoption metric. This list alone does not define acceptance criteria or establish a compliant deployment.
Reference customer. Ask whether the actual customer would refer the engagement to a peer. A hoped-for recommendation is different from documented willingness and permission to use it.
Identity and access. Identify the buyer’s SSO, SCIM and RBAC requirements and the evidence that each is met. The map names the topics but provides no implementation or testing procedure.
Data governance. Document the actual customer’s residency and sovereignty requirements before choosing an architecture. This source does not establish legal requirements or a complete governance design.
Buyer map. Separate the champion, economic buyer, IT/security gatekeeper and end users. Record the question each role needs answered instead of treating one enthusiastic contact as full acceptance.
Change management. Look for adoption evidence and the work required for people to use the system. The source’s statement about failed pilots supplies no study or demonstrated cause.
Responsible AI. Identify the proposed risk review, model evaluation and ongoing review evidence. Framework names are not a completed evaluation; the map lacks the detailed procedure.
Define each evidence item before using the five-part engagement standard. A sales cycle of three to nine months is a source estimate, not a guarantee. One $15,000 close per quarter averages $5,000 monthly gross revenue before costs; it does not alone establish profitability or fund the entire later staffing plan. This account's day-one language conflicts with its later scheduled launch.
Account 6 — Make content useful and measure discovery carefully
This role has eight search-related pillars and six query examples. Treat citation and visibility as outcomes to observe. Markup, a named methodology or a Wikidata entry cannot guarantee generated answers. The source's twelve-element page standard and Share of Model framework need their actual definitions before complete implementation can be claimed.
Source plan for study — v2 account 6: complete role, pillars, queries, cadence and funnel
Stages served: The discoverability layer that runs through the entire syllabus + Stage 7 specialization tracks Source courses: C32.5 AEO / GEO / Share of Model, C51 Trend Surveillance Engine, the Module-Page Authoring Standard documented across all 52 courses Avatar: Marketers, agency owners, content creators with existing SEO programs nervous about AI search shifting their traffic Awareness: Sophisticated, understands SEO, watching traffic shift to ChatGPT/Perplexity/Claude Price points fed: $4,997–$25,000 (C32.5 dedicated course + Stage 7 specialization tracks + done-with-you continuity)
Content pillars sourced from real syllabus modules:
The Module-Page Authoring Standard (academy-wide) — Every page ships as an AI-citable answer page
Title + Lead + Outcome + Body + Schema (academy-wide) — The 12-element citation-ready format
Citation Trap (academy-wide) — Named proprietary frameworks with primary-source definitions
AIO queries — How to identify the questions buyers ask AI engines
GEO authority signal stacking — Wikidata entities, founder Person schema, podcast appearances, expert quotes
Share of Model (SoM) — The C32.5 framework for measuring AI citation share
Quarterly Freshness Triggers (C51 Trend Surveillance Engine) — When content needs to be refreshed
AIO queries this account should win:
what is aeo answer engine optimization
what is geo generative engine optimization
how do i get cited by chatgpt
what is share of model
how do i optimize for ai search
what is the module page authoring standard
Platforms: LinkedIn (primary), X/Twitter (active discussion), YouTube long-form teardowns, technical blog Production: Voiceover + screen sharing. Delegated to most technical editor on your team. Cadence: 3 LinkedIn + daily X + 1 YouTube long-form per week
Lead magnet: "The 10-Query AI Search Audit Tool" + "Module-Page Authoring Checklist" PDF Funnel: Audit → $197 AEO workshop → C32.5 course ($2,997) → done-with-you continuity ($1,500/mo) → Stage 7 specialization tracks
Why this works: Smallest target audience of the six, but highest LTV per acquisition. Buyers in this niche readily pay $5K+ and have $25K+ done-with-you budgets. This account converts to the top of your ladder.
---
Teach and apply each pillar
These explanations apply the available map; they do not replace missing module bodies.
Answer-page standard. Identify the reader’s question and the supported answer the page provides. Being written as an answer does not ensure that a model will cite it.
Page elements. The account overview names five elements; the later constraints list all twelve: Title, Lead, Outcome, Body, Schema, Artifact, Cluster, Video Kit, Lineage, Freshness, Citation Trap and E-E-A-T. Retain all twelve names. The map still lacks their full definitions, acceptance criteria and working templates.
Named frameworks. Provide a clear primary definition for a framework you name. The source calls this a Citation Trap, but a proprietary name does not establish usefulness, authority or citation likelihood.
Query research. Use the six supplied questions as candidate reader needs. Confirm relevance and evidence before writing; their presence on a list does not prove search demand.
Direct-answer formats. Choose definition, how-to, comparison, FAQ or framework format according to the question. Explain the answer in visible text and retain the evidence behind it.
Authority signals. Distinguish documented entities, founder information, podcast appearances and expert quotations from invented credentials. Any implementation of schema or external entity entries still requires current guidance and actual eligibility.
Share of Model. Define the questions, systems, observation dates and denominator before reporting a share. The complete C32.5 methodology is absent; a few citations are not a reproducible framework.
Freshness. Record when claims need review and what has changed. The map names quarterly triggers; the separate trend prompt also proposes monthly and event-based reviews, which need distinct purposes.
The course funnel includes $2,997 despite a larger stated price band. Its tools, checklist, keyword assets and measurement method are referenced rather than delivered here. An entity entry needs actual eligibility and evidence; it is not an automatic marketing task. Current official guidance must be checked before search implementation.
Treat the shared community as a defined service
The source connects the six audiences through one free community. Read its tier and proof-artifact claims, then distinguish actual platform state from the proposed architecture.
Source plan for study — v2 shared community
THE UNIFYING MIDDLE — Free Skool/Circle Community
Not a social account but the most important asset in the architecture.
Every one of the 6 social accounts funnels into this free community. It is where lurkers become buyers and where graduation gates (C5, C10, C14, C27, C33, C42) get celebrated publicly with member proof artifacts (signed Manifestos, Outcome Documentations, 90-Minute Demo recordings, Enterprise Engagement Checklists).
The free community is what makes the 6-account architecture financially viable. Without it, you are acquiring leads you cannot follow up with at scale.
Operational architecture:
Free tier: Skool or Circle (free plan)
Mid tier: Paid Circle continuity (already in use)
Top tier: Stage 6 Fleet community (C44 Community as Moat module is the playbook)
---
The assertions about free platform plans and paid Circle already being used have not been verified. Some account funnel paths do not explicitly include this community despite the all-six statement. Define the real route and owner. Publicly celebrating a learner's artifact requires accurate evidence and appropriate permission.
Read the launch sequence together with its gates
The six source phases include dates, targets, roles, monthly costs and a revenue model. Preserve all of them. They are planning estimates, not the user's approved launch schedule or a measured revenue forecast.
Source plan for study — v2 phases A–F and revenue model
Part 3 — The Highway Scaling Sequence
Stage A — Months 1–3: Foundation Launch
Active accounts: Account 1 (Flagship) + Account 2 (AI for 45+) + Free Skool community Syllabus stages served: Pre-Stage through Stage 2 (C1–C10) Goal: Prove the funnel converts before duplicating it
Why this sequence: If your flagship + one faceless account + free community can't generate consistent email opt-ins and Stage 1–2 sales, adding more accounts will only multiply the failure. Your own academy must clear its own Stage 1 (Proof of Pulse — 1 paying customer) and Stage 2 (Proof Threshold — 3+ customers) before you scale into Stage 3 distribution.
Empirical floor for this stage (apply the academy's own doctrine to your business):
200+ email opt-ins per week consistently for 3 months
30%+ join free community within 14 days of opt-in
1+ paying customer in week 1 (Proof of Pulse for your launch)
3+ paying customers by month 3 (Proof Threshold)
Team: You + 1 editor (15–20 hrs/week) + 1 part-time community manager Monthly operational cost: $2,500–4,500
Stage B — Months 4–6: Add Direct Response Lane
New account launched: Account 3 (Direct Response Architecture) Syllabus stages served: Stage 3 + Stage 4 (C11–C20) Goal: Pass Stage 3 graduation gate (Distribution Proof) for the Academy's own marketing
Why this account next: Targets a completely different avatar (existing creators with revenue) at a higher price point. Doesn't compete with Account 1+2 for attention.
Critical AOV inflection: Stage 1–2 buyers average ~$200 AOV. Stage 3–4 buyers average ~$1,500 AOV. Same operational cost, much higher revenue per acquisition.
Empirical floor for this stage:
Account 3 distribution asset hitting ≥30 opt-ins/month at sub-$10 CPO within 60 days (the academy's own C14 standard applied to itself)
Blended AOV across all accounts exceeds $400
Team additions: +1 editor (Account 3 uses different content style — more whiteboard/teardown). Total: you + 2 editors + community manager. Monthly operational cost: $4,500–7,000
Why third: Your Stage 5 courses ($4,997–$9,997) need Accounts 1–3 already populating ascension demand before higher-ticket offers have a populated audience to convert.
Empirical floor for this stage:
30-day operator-out-of-loop test passing on Account 1, 2, 3 content production (using your own academy's C33 standard)
1+ Stage 5A or 5B sale at $4,997+ AOV
Team additions: +1 technical editor or contractor for agent demos. Total: you + 3 editors + community manager + part-time tech. Monthly operational cost: $7,000–11,000
Stage D — Months 10–14: Add Enterprise Lane
New account launched: Account 5 (Enterprise AI for Operators) Syllabus stage served: Stage 5C (C36–C42) Goal: First enterprise engagement (Stage 5C graduation for the Academy itself)
Why now and not later: Enterprise sales cycles are 3–9 months. If you wait until Month 18 to launch this account, your first enterprise close lands at Month 24+. Start the funnel filling in Month 10, expect first close around Month 16–20.
Empirical floor for this stage:
1 enterprise engagement signed with all 5 criteria (signed MSA, SSO/SCIM, Trust Center, governance, 90-day adoption) within 9 months of account launch
This is the academy's own C42 graduation gate
Team additions: Content director to oversee all accounts. You shift to strategic oversight + Account 5 founder voice. Total: you (strategic + Account 5) + content director + 3 editors + community manager + part-time tech. Monthly operational cost: $11,000–18,000
Stage E — Months 15–18: Add AEO/GEO Lane
New account launched: Account 6 (AEO/GEO Search Visibility) Syllabus served: C32.5 + C51 + academy-wide Module-Page Authoring Standard Goal: Establish Riser Nation as the cited source for AEO/GEO in the AI marketing space
Why last: This account requires 12+ months of citation-ready content already published across the other 5 accounts to have proof of method. You can't credibly teach AEO if you haven't won AEO citations yourself first.
Empirical floor for this stage:
Riser Nation cited in ChatGPT/Perplexity/Claude responses for ≥10 target queries within 6 months of Account 6 launch
Wikidata entity for Riser Nation Empirical Floor Doctrine + Reduce Mismatches Doctrine established
Team additions: Add a specialist AEO/GEO content producer. Total: you (strategic) + content director + 4 editors + community manager + part-time tech + AEO specialist. Monthly operational cost: $15,000–22,000
Stage F — Year 2+: Full Armada Operating at Scale
All 6 accounts running + Free community + Paid Circle continuity + Stage 7 sovereign tier
Revenue mix at Year 2 (realistic estimate):
Account
% of Customer Volume
% of Revenue
Account 1 (Stage 1)
45%
6%
Account 2 (Stage 2)
28%
12%
Account 3 (Stage 3–4)
18%
30%
Account 4 (Stage 5A/B)
6%
22%
Account 5 (Stage 5C)
1.5%
20%
Account 6 (AEO/GEO + Stage 7)
1.5%
10%
The honest math: The top 3% of your customer base (Stage 5C + Stage 7 buyers) generates 30% of revenue. The top 10% generates 52%. This is exactly why a 6-account architecture is worth the operational complexity — the high end of your ladder requires its own dedicated acquisition channels.
---
Turn the proposed launch phases into evidence records
Foundation, months one to three. The map proposes Accounts 1 and 2 with a free community. Record weekly opt-ins over the full three months, community entry within fourteen days, a first-week paying customer and three customers by month three. The two hundred weekly opt-ins and thirty-percent community target describe different denominators and windows. Keep the editor's fifteen-to-twenty weekly hours and the $2,500–$4,500 monthly budget as planning assumptions.
Direct response, months four to six. The proposed new account serves an existing business audience. Check the stated distribution results and blended AOV above $400 rather than assuming a higher-priced offer improves the average. A blended AOV requires transaction counts as well as revenue. The additional editor and $4,500–$7,000 monthly budget need actual workload and cost evidence.
Infrastructure, months seven to nine. This phase asks for thirty days of operator-free production on Accounts 1–3 and at least one $4,997-or-higher Stage 5 sale. Its later Account 4 gate tests Account 4 itself; those are different scopes. The source adds a technical editor or contractor, then lists three editors plus part-time technical help. Clarify whether that is one role or two before using the $7,000–$11,000 budget.
Enterprise, months ten to fourteen. The proposed content director coordinates the accounts while the founder adds enterprise work. Record launch date, engagement evidence and the adoption observation period separately; signing an engagement does not instantly establish ninety days of adoption. The $11,000–$18,000 monthly estimate and expected close around months sixteen to twenty are assumptions, not completed results.
Search, months fifteen to eighteen. The source proposes twelve months of prior content as a credibility prerequisite, then ten target-query citations within six months of launch and two named entities. Neither an elapsed year nor publication alone establishes effectiveness. Keep the $15,000–$22,000 budget, fourth-editor count and separate specialist role visible for staffing reconciliation.
Year two onward. The proposed configuration includes all six accounts, free community, paid Circle continuity and a sovereign tier. Check actual service availability before describing any as active. The revenue table is a scenario to evaluate, not a forecast validated by the map.
Start with evidence that the initial route works before expanding. But the source's dates conflict with its later gates: Account 3 can begin months four to six while Account 2's day-180 gate blocks expansion; Account 4 starts months seven to nine while Account 3's day-270 gate blocks it; Account 5 starts months ten to fourteen while Account 4's day-360 gate may block it. Do not implement those dates as a consistent schedule without resolving the conflict.
The model's percentages sum to one hundred in each column. Accounts 5 and 6 represent three percent of customers and thirty percent of revenue. Accounts 4–6 represent nine percent of customers and fifty-two percent of revenue, not a demonstrated top-ten-percent result. These are hypothetical mixes, not actual customer statistics.
Preserve the entire course-to-account reference
Use this table to understand the source's intended content ownership. Keep primary and secondary roles distinct. C9 and C13 ownership also differs from some earlier account bands. None of these legacy mappings overwrites the current document-to-lesson spreadsheet.
Source plan for study — v2 full 55-row course/account cross-reference
Part 4 — Course-to-Account Cross-Reference (All 52 Courses)
Course
Title
Stage
Primary Account
Secondary
C1
Harbor Orientation & Riser Manifesto
Pre-Stage
Account 1
—
C2
Pain Excavation & Semantic Foundation
Pre-Stage
Account 1
Account 3
C3
Avatar Engineering (100-Avatar Method)
Pre-Stage
Account 1
Account 3
C4
Market Reality & Niche Validation
Stage 1
Account 1
Account 2
C5
Proof of Pulse (Graduation Gate)
Stage 1
Account 1
Account 6
C6
The Grand Slam Offer (Hormozi)
Stage 2
Account 2
Account 3
C7
Hook-Story-Offer (Brunson)
Stage 2
Account 2
Account 3
C8
Direct Response Copy (Kennedy/Ogilvy/Hopkins/Cialdini)
Stage 2
Account 2
Account 3
C9
The 8-Tier Value Ladder
Stage 2
Account 3
Account 2
C10
Proof Threshold (Graduation Gate)
Stage 2
Account 2
Account 6
C10.5
Sales Operations (DM/Call/No-Call)
Bridge
Account 2
Account 3
C11
Direction Clarity & Dream 100 (2026)
Stage 3
Account 3
—
C12
Skill & Experience Mapping for Content
Stage 3
Account 3
Account 1
C13
Faceless YouTube & AI Higgs Field Engine
Stage 3
Account 2
Account 3
C14
Distribution Proof (Graduation Gate)
Stage 3
Account 3
Account 6
C15
Funnel Engine — Decision Paths
Stage 4
Account 3
—
C16
Customer LTV & Measurement Discipline
Stage 4
Account 3
Account 4
C17
Retention & Anti-Extraction Standard
Stage 4
Account 3
—
C18
Mid-Funnel Trust & YouTube Authority
Stage 4
Account 3
Account 4
C19
Bottom-Funnel Close & IG Growth
Stage 4
Account 3
Account 2
C20
Brand Architecture & Visual Style
Stage 4
Account 3
Account 1
C21
AI Foundations — Models/Modalities/Brain
Stage 5A
Account 4
—
C22
Networks & Protocols — The Nervous System
Stage 5A
Account 4
—
C23
Application Layer (Projects/Skills/Agents)
Stage 5A
Account 4
—
C24
Prompting at Three Levels
Stage 5A
Account 4
Account 2
C25
Local Hardware & Self-Hosted AI
Stage 5A
Account 4
—
C26
Building Tools (Repos/Widgets/Apps)
Stage 5A
Account 4
—
C27
Infrastructure Proof (Graduation Gate)
Stage 5A
Account 4
Account 6
C28
AI Marketing Stack 2026
Stage 5B
Account 4
Account 3
C29
Vibe Coding for Marketers
Stage 5B
Account 4
—
C30
Multi-Agent Marketing Crews
Stage 5B
Account 4
—
C31
The Content Flywheel
Stage 5B
Account 4
Account 3
C32
RN-MOS — Your Operating System
Stage 5B
Account 4
Account 1
C32.5
AEO/GEO/Share of Model
Bridge
Account 6
Account 4
C33
Applied AI Proof (Graduation Gate)
Stage 5B
Account 4
Account 6
C36
Enterprise AI Landscape & Buyer Map
Stage 5C
Account 5
—
C37
Identity/Access/Enterprise Authentication
Stage 5C
Account 5
—
C38
Data Governance/Privacy/Sovereignty
Stage 5C
Account 5
—
C39
System Integration (ERPs/CRMs/Data Plane)
Stage 5C
Account 5
—
C40
Enterprise Deployment & Change Management
Stage 5C
Account 5
—
C41
Enterprise AI Governance & Responsible AI
Stage 5C
Account 5
Account 6
C42
Enterprise Engagement Proof (Graduation Gate)
Stage 5C
Account 5
Account 6
C43
VA & Team Onboarding via SOPs
Stage 6
Account 4
Account 5
C44
Community as Moat
Stage 6
Account 1
Account 3
C45
Outbound Outreach
Stage 6
Account 3
Account 5
C46
Ethical Persuasion & ETM
Stage 6
Account 1
Account 3
C47
Group Attention (Webinars/Challenges)
Stage 6
Account 3
Account 2
C48
Retargeting Ecosystems & WAESM
Stage 6
Account 3
Account 4
C49
Crisis Navigation & Reputation
Stage 6
Account 5
Account 1
C50
Executive Command & 85-Minute Cadence
Stage 7
Account 1
Account 5
C51
Trend Surveillance Engine
Stage 7
Account 6
Account 4
C52
Legal, Finance & IP Protection
Stage 7
Account 5
—
C53
IP Productization (Licensing/Cert/White-Label)
Stage 7
Account 5
—
C54
Acquisition or Distribution (Year 10)
Stage 7
Account 1
Account 5
C55
Capstone — Architect of Orchestration
Capstone
Account 1
—
---
Assess all six account gates
For each gate, identify the evidence, time window and proposed defer action. A document claiming that a gate exists is not proof it passed.
Source plan for study — v2 six account-specific gates
Part 5 — Applying the Academy's Own Doctrine to the Account Launch
This is the most important section in the document. Every social account launch should follow the same Pass/Defer/Rework discipline the Academy teaches.
Account 1 (Flagship) Empirical Floor — Apply by Day 90:
1 paying customer at validated price (Stage 1 Harbor bundle, $97 or higher)
Signed testimonial with documented outcome
Refund analysis (even if no refunds requested)
If not met: Defer-Without-Shame. Return to C1–C5 in your own academy and reapply.
Account 2 (AI for 45+) Empirical Floor — Apply by Day 180:
3+ paying customers at Stage 2 Sailboat bundle pricing ($497+)
Documented outcomes in customer's own words
Validated pricing across the ladder
If not met: Don't add Account 3 yet. The funnel isn't ready to duplicate.
Account 3 (Direct Response Architecture) Empirical Floor — Apply by Day 270:
Distribution asset producing ≥30 opt-ins/month at sub-$10 CPO for 3 consecutive months
If not met: This is a Stage 3 failure. The defer protocol: stop Account 4 launch, fix Account 3 first.
Account 4 (AI Infrastructure) Empirical Floor — Apply by Day 360:
Account 4 itself shipping content via the 30-Day Operator-Out-of-Loop Test
1+ Stage 5 sale at $4,997+ AOV
If not met: This is a Stage 5B failure in the academy's own business. Defer Account 5.
Account 5 (Enterprise) Empirical Floor — Apply by Month 18:
1 enterprise engagement signed with all 5 C42 criteria
Reference customer test passed (would they refer Riser Nation to a peer?)
If not met: This is a C42 defer pattern. Most likely cause: account was launched before flagship + Account 4 had sufficient enterprise-trust signals.
Account 6 (AEO/GEO) Empirical Floor — Apply by Month 24:
Riser Nation cited by ChatGPT/Perplexity/Claude for 10+ target queries
Wikidata entities established for at least 5 proprietary frameworks
If not met: Account 6 is the slowest to gate. Allow defer pattern up to Month 30.
---
Explain what each gate asks the operator to prove
Day ninety, Account 1: distinguish the $97-or-higher validated purchase, signed testimonial with an outcome, and refund analysis. If evidence is missing, the source proposes returning to its legacy C1–C5 material. Record the missing item and rework rather than treating the date as automatic graduation.
Day one hundred eighty, Account 2: check three or more $497-or-higher buyers, outcomes in their own words and the source's pricing-validation requirement across the ladder. A count of three transactions alone does not establish every tier's pricing. The source says to delay Account 3 if the gate is unmet.
Day two hundred seventy, Account 3: verify three consecutive months at thirty or more opt-ins and cost below $10 per opt-in, plus the UTM convention and documented first touch. The proposed response to failure is to fix this account before launching Account 4.
Day three hundred sixty, Account 4: check its own thirty-day content-production test and at least one qualifying Stage 5 sale. Keep this distinct from the earlier test on Accounts 1–3. The source proposes deferring Account 5 when the evidence is missing.
Month eighteen, Account 5: retain each of the five engagement criteria and the reference-customer question. The source guesses that insufficient flagship and Account 4 trust signals are the most likely cause of failure. That causal diagnosis has no supporting investigation here; examine actual evidence before accepting it.
Month twenty-four, Account 6: document the ten target-query observations and the proposed five-framework entity condition separately. The source allows deferral to month thirty. That extension does not guarantee future citations or entity eligibility, and its five-entity requirement differs from the earlier two-entity milestone.
The enterprise gate's Month 18 date differs from the nine-month-after-launch window and expected Month 16–20 close. Search targets also change from two named entities to at least five. A lack of citations is not proof of one specific cause, and no citation count is guaranteed. Keep observation dates, questions, systems and evidence explicit.
Check staffing, economics and the three asset specifications
The six constraints and three production specifications follow in full. Read them before treating the account plan as resourced.
Source plan for study — v2 constraints, lead magnets and closing doctrine
Part 6 — The Honest Constraints (Updated for the Real Syllabus)
Six structural truths most operators don't plan for:
The flagship cannot be delegated. You on camera is the trust anchor for the entire ladder. Stage 5C buyers ($15K–$50K) and Stage 7 sovereign-tier buyers will stalk Account 1 before they buy anything else. If you outsource the founder voice, the top of the ladder collapses.
Each faceless account needs its own editor with a distinct voice. Account 2 (warm, encouraging, demystifying) is different from Account 4 (technical, demonstrative, ROI-focused) which is different from Account 6 (research-driven, citation-focused). One editor cannot run all four faceless accounts well.
The free Skool/Circle community needs a dedicated community manager from day 1. Not part-time, not "I'll get to it." A neglected free community signals the academy is dead.
You must publish the stage alignment publicly. Every social account should make it clear which Riser Nation stage it serves. "This account teaches Stage 2 — Sailboat. For Stage 5 content, follow @[Account 4 handle]." This is a feature, not a bug — sophisticated buyers respect transparency.
The AOV math must work or the team math doesn't work. At $200 AOV (Stage 1–2), you need ~30 sales/month to fund Stage A operations. At $1,500 AOV (Stage 3–4), 5/month. At $9,997 AOV (Stage 5), 1–2/month. At $15K+ AOV (Stage 5C), 1/quarter justifies the account. Each account's funnel must hit these baselines before adding the next account.
The Module-Page Authoring Standard IS the AEO/GEO moat. Every social post should be feeding citable, schema-ready content into the AI search engines. The academy already does this at the course level via the 12-element Module-Page Standard (Title/Lead/Outcome/Body/Schema/Artifact/Cluster/Video Kit/Lineage/Freshness/Citation Trap/E-E-A-T). Mirror that discipline in social.
---
Part 7 — Sequenced Lead Magnet Production
Build these three first lead magnets before launching anything:
Lead Magnet 1 — Powers Account 1 (Flagship): "The Riser Manifesto + 3-Mismatch Diagnostic"
Lead Magnet 2 — Powers Account 2 (AI for 45+): "The Grand Slam Offer Worksheet (Hormozi Value Equation Applied)"
Source: C6 modules
Production: Fillable PDF + companion 10-day email sequence
Includes: Value Equation calculator, bonus-stacking template, guarantee-writing prompts
Lead Magnet 3 — Powers Account 3 (Direct Response): "The 8-Tier Value Ladder Blueprint + LTV Calculator"
Source: C9 + C16
Production: Interactive web tool (preferred) OR fillable PDF
Includes: 8-tier worksheet, LTV math examples (Marcus the Designer case study), pricing-by-tier rules
Build these in this order. Don't launch Account 1 without #1 ready. Don't launch Account 2 without #2 ready. Don't launch Account 3 without #3 ready.
---
Closing Note
This architecture is not aspirational. It is operationally honest and now correctly grounded in the actual 2026 Master Synthesis Edition syllabus. Six accounts is the maximum a founder + small team can sustain at quality. Seven is where things break.
The discipline is to launch each account only after the prior account has passed its empirical floor — the same Pass/Defer/Rework gates the Academy teaches students. Defer-Without-Shame applies to your own business too.
The syllabus IS the product. The six social accounts are simply different fishing nets in different waters, all reeling into the same harbor.
Build them one at a time. Prove the math at each gate. Then duplicate.
The maritime stage progression is not branding fluff — it is an operational architecture. Honor it in your social strategy and the ladder builds itself.
Apply the remaining constraints and asset specifications
The staffing constraint calls for distinct editorial voices: warm and encouraging for Account 2, technical and demonstrative for Account 4, and research-focused for Account 6. Record these production needs without treating the assertion that one editor cannot serve multiple accounts as a measured capacity limit. Public stage labels and cross-links are proposed ways to clarify audience fit; the example account handles are placeholders, and the source's legacy stages must not replace this curriculum's assignments.
The final constraint names all twelve page-standard elements: Title, Lead, Outcome, Body, Schema, Artifact, Cluster, Video Kit, Lineage, Freshness, Citation Trap and E-E-A-T. The earlier account description lists only five. This is an abbreviated overview followed by a fuller list, not seven wholly absent names. Definitions and acceptance criteria still need their underlying source. The claim that the academy already follows the standard is not a verification of these pages.
For the first proposed asset, distinguish the branded eight-to-twelve-page PDF from its three required contents: signed-Manifesto template, Oath script and diagnostic worksheet. For the second, distinguish the fillable worksheet and ten-day email sequence from the calculator, bonus template and guarantee prompts inside. For the third, distinguish the preferred interactive tool or alternative fillable PDF from the eight-tier worksheet, LTV examples and pricing rules. Each specification identifies work to be sourced and completed; it does not supply the finished asset.
The production rule links readiness to launch: asset one before Account 1, asset two before Account 2 and asset three before Account 3. Retain that sequencing alongside the earlier instruction to build all three before launching anything; those statements allow different interpretations of whether Account 1 waits for every asset. Resolve the intended release plan before scheduling. The source's additional one-to-two monthly sales at $9,997 is another gross-revenue scenario, not net funding evidence. Its closing claim that the ladder builds itself remains promotional language, not an operating guarantee.
The source first proposes a part-time community manager, then requires one who is not part-time. Founder Account 1 work remains necessary under its own rule even when later phases move the founder to strategy and Account 5. Editor and specialist roles may overlap; define the workload before counting hires.
Thirty $200 sales produces $6,000 gross revenue, not profit. Five $1,500 sales produces $7,500 gross. Compare revenue with refunds, acquisition, delivery and overhead before claiming a staffing plan is funded. AOV alone is insufficient.
The three lead magnets have distinct contents: the eight-to-twelve-page Manifesto/diagnostic with oath and signed template; the offer worksheet with calculator, bonus and guarantee prompts plus ten emails; and the eight-tier/LTV tool with examples and pricing rules. The map does not provide those complete assets. Do not claim them finished from their titles. Six accounts maximum and seven breaking the system is an unsupported capacity assertion.
Study v1 as a separate historical plan
The older version is included below because it contains distinct material. It has five accounts, six maritime stages, different course names, twenty-five pillars and different first assets. Do not merge its Account 5 search role into v2's Account 5 enterprise role.
Read the full historical plan with these comparison tasks: identify what each account teaches, which acquisition route it proposes, what changes in its timing and budget, and which named asset still needs a source. Its scenarios, claims and table are preserved rather than silently replaced.
Source plan for study — historical v1: complete five-account plan
Riser Nation Academy 2026 (Sovereign Edition)
Social Account Scaling Architecture — Aligned to the Real Syllabus
Source syllabus: Riser Nation Academy 2026 Sovereign Edition — 55 courses, ~360 modules, maritime stage progression, graduation gates at C5/C10/C14/C27/C33/C42, AIO/AEO/GEO discoverability baked into every module.
The thesis: Your maritime stage progression (Dinghy → Sailboat → Speedboat → Yacht → Mega Yacht → Bora Bora Cruise Ship) is already a value ladder. Each stage has a different avatar at a different awareness level paying a different price point. Therefore each stage needs its own dedicated social content engine. Five accounts. One ladder. Six progressively-priced outcomes.
---
Part 1 — The Syllabus as a Value Ladder
Stage
Vessel
Courses
Outcome
Price Range
Awareness Level
1
Dinghy
C1–C5
Operator identity + market selection
Free → $97
Problem-aware, doesn't know where to start
2
Sailboat
C6–C10
Buyer intel + first offer + funnel
$497–$997
Solution-aware, has an idea
3
Speedboat
C11–C14
Traffic + content + first revenue
$997–$1,997
Has offer, needs customers
4
Yacht
C15–C27
Persuasion + automation + scale
$1,997–$4,997
Has revenue, needs systems
5
Mega Yacht
C28–C42
AI infrastructure + sovereignty
$4,997–$15,000
Has business, needs leverage
6
Bora Bora Cruise Ship
C43–C55
Legacy + governance + sovereign command
$15,000–$50,000+
Has scale, building permanence
The critical insight most academy operators miss: A buyer at C1 (Harbor Orientation) and a buyer at C43 (Sovereign Operator Command) are not the same person. They speak different languages, consume content on different platforms, respond to different proofs, and convert at different price points. One social account cannot serve both. Five social accounts, each tuned to a specific stage band, can.
---
Part 2 — The Five Social Account Engines
ACCOUNT 1 — "Late Bloomer" Founder Flagship
Stage served: Pre-Stage + Stage 1 (Dinghy, C1–C5) Avatar: 45+ first-time builder, problem-aware, hasn't bought anything yet Awareness: "Is it too late for me?" / "Where do I even start?" Price points fed: Free PDF → $27–$97 entry → free Skool/Circle community
C2: Buoy Navigation — Market radar basics, how to read demand
C3: Casting the Nets — First-offer principles
C4: The Commercial Fleet — Traffic fundamentals (intro level)
C5: Funnel Harbors — Conversion architecture basics (this is a graduation gate course; teach the *concepts*, not the implementation)
Content pillars (rotate weekly):
Riser Manifesto / operator identity
"It's not too late" — proof and philosophy
The "Reduce Mismatches" doctrine in plain language
Founder behind-the-scenes building the academy
Origin stories from members (with permission)
Platforms: LinkedIn (primary), Instagram, YouTube long-form Production: You on camera. Cannot be delegated. Cadence: 4 LinkedIn + 4 IG + 1 YouTube long-form per week
Lead magnet: "The Riser Manifesto + 5-Rung Value Ladder Blueprint" PDF Funnel: Bio link → PDF opt-in → 5-day email nurture → free Builders community → C1–C5 Stage 1 Foundation Bundle ($97)
Why on-camera matters here: Your face is the proof that someone over 45 can build something credible. The flagship account doesn't sell a course — it sells permission.
---
ACCOUNT 2 — "AI for First-Time Builders 45+" (Faceless)
Stage served: Stage 2 (Sailboat, C6–C10) Avatar: 45+, has a skill or idea, ready to build their first offer Awareness: Solution-aware, looking for "how" Price points fed: $497–$997 (individual Stage 2 courses or the Sailboat bundle)
Content sourced from these courses:
C6: Email Harbor Systems — Email list-building for beginners
C7: Offer Fleet Expansion — Value ladder construction (simplified)
"Try this AI prompt today" — single-tool, single-outcome demos
"I'm 55 and I just figured out..." — relatable framing
Pricing psychology for first-time sellers
Email list-building basics
Funnel anatomy explainers (60-second teardowns)
Platforms: Instagram Reels, TikTok, YouTube Shorts, LinkedIn carousels Production: Faceless. AI voiceover + screen recordings + b-roll. Delegated to editor. Cadence: 1 short per day, same video native-captioned per platform
Lead magnet: "10 AI Prompts for First-Time Business Builders" (from your AI Prompts Directory) Funnel: Bio link → prompt pack → 10-day email sequence (one prompt per day) → Stage 1 bundle ($97) OR direct Stage 2 Sailboat bundle ($497)
Why faceless works here: This avatar is at the bottom of the awareness funnel. The faceless format removes the comparison ("I'm not like that person on camera") that kills conversion. They want the *answer*, not the influencer.
Why this works: Highest-margin acquisition channel of the five. Audience is pre-qualified — they have revenue, are frustrated, and buy solutions. Position as architecture, not motivation.
---
ACCOUNT 4 — "AI Agents & Custom GPTs" (Faceless)
Stage served: Stage 5 (Mega Yacht, C28–C42) Avatar: Solopreneur or agency owner at $10–50K/mo, ready to systematize with AI Awareness: Has revenue, has operational chaos, looking for leverage Price points fed: $2,997–$9,997 (Stage 5 AI Command Fleet courses)
Content sourced from these courses:
C26: Agentic Crew Systems — AI workforce infrastructure
C27: Autonomous AI Ships — Self-operating business systems (graduation gate)
C28: AI Shipyards — Building AI products & tools
C29: Knowledge Ocean Mapping — AI knowledge systems
C30: Strategic Ocean Navigation — AI strategy & decision systems
C31: Content Fishing Net Factories — AI content production
C32: Global Shipping Lanes — Content distribution networks
C36: Fleet Operations Command — Scaling digital enterprises
Content pillars:
"Built this agent in 20 minutes" speed demos
AI Employee Framework walkthroughs
Agent ecosystem teardowns
Custom GPT vs. Agent vs. Chatbot decision frameworks
Real ROI case studies (hours saved, revenue per agent)
Platforms: YouTube long-form (primary — this audience consumes long technical content), LinkedIn, X/Twitter Production: Voiceover + screen recordings. Delegated to technical editor. Cadence: 2 YouTube long-form per week + 5 LinkedIn posts + daily X
Lead magnet: "5 Ready-to-Deploy AI Employee Templates" + a custom GPT they can clone immediately Funnel: Template opt-in → "Build Your First AI Employee" mini-course ($27) → C26–C30 Mega Yacht bundle ($2,997) → Stage 5 full ascension ($9,997)
Why this works: Audience trusts depth. A 30-minute YouTube teardown converts higher than 30 short-form videos. Positions Riser Nation as the operator-grade alternative to "AI hype" content.
Stage served: Stage 5–6 specialty tracks (the AIO/AEO/GEO discoverability layer baked into every Sovereign Edition course) Avatar: Marketers, agency owners, content creators with existing SEO programs nervous about AI search Awareness: Sophisticated. Understands SEO. Watching traffic shift to AI engines. Price points fed: $4,997–$25,000 (Stage 6 sovereign tier + done-with-you continuity)
Content sourced from these courses:
The AIO/AEO/GEO layer documented across the entire syllabus (every course ships FAQ-schema-ready Q&A pairs, citable definition blocks, entity-authority stacking)
C43: Sovereign Operator Command
C44: Legacy Fleet Architecture
C49: Digital Ocean Governance
Content pillars:
"What ChatGPT cites vs. what Google ranks" comparisons
Schema.org markup tutorials
AEO direct-answer block construction
GEO entity-authority signal stacking (Wikidata, podcast appearances, expert quotes)
AI search demos and audits
Platforms: LinkedIn (primary), X/Twitter, YouTube long-form, technical blog Production: Voiceover + screen sharing. Delegated to most technical editor. Cadence: 3 LinkedIn + daily X + 1 YouTube long-form per week
Lead magnet: "AEO Audit Tool" or "10 Queries Your Business Should Win in AI Search" Funnel: Audit → $197 workshop → $2,997 AEO/GEO implementation course → $1,500/mo done-with-you continuity → Stage 6 sovereign tier
Why this works: Smallest target audience of the five, but highest-converting and highest-LTV. These buyers pay $5K+ readily. This account feeds your top-of-ladder offers.
---
THE UNIFYING MIDDLE — Free Skool/Circle Community
Not a social account but the most important asset in the architecture.
Every one of the 5 social accounts funnels into this free community. It is where lurkers become buyers. It is where graduation gates (C5, C10, C14, C27, C33, C42) get celebrated publicly, where member wins get amplified, and where the academy's culture is forged.
Without this asset, you are acquiring leads you cannot follow up with at scale. The free community is what makes the 5-account architecture financially viable.
---
Part 3 — The Highway Scaling Sequence
This is where most academy operators fail. They try to launch 5 accounts at once, exhaust themselves, and produce mediocre content across the board. Here is the actual sequence aligned to your syllabus rollout:
Stage A — Months 1–3 (Single Lane)
Active accounts: Flagship (Account 1) + AI for 45+ (Account 2) + Free Skool community Stage served: Pre-Stage through C10 (Dinghy + Sailboat) Goal: Prove the funnel converts before duplicating it
Why this sequence: If your flagship + one faceless account + free community can't generate consistent email opt-ins and Stage 1–2 sales, adding more accounts will only multiply the failure. The Stage 1 of your own business has to work before you can teach Stage 1 to others.
Success metrics:
200+ email opt-ins/week consistently
30% join free community
3–5% buy a Stage 1 or Stage 2 product within 30 days
Team: You + 1 editor (15–20 hrs/week) + 1 part-time community manager Monthly operational cost: $2,500–4,500
Stage B — Months 4–6 (Add Lane 2)
New account launched: Value Ladder Architecture (Account 3) Stage served: C11–C20 (Speedboat + early Yacht)
Why this account next: Targets a completely different avatar (existing creators with revenue) at a higher price point. Doesn't compete with Account 1+2 for attention.
Critical moment: Your average order value should roughly double here. Stage 1–2 buyers average ~$200 AOV. Stage 3–4 buyers average ~$1,500 AOV. Same operational cost, much higher revenue per acquisition.
Team additions: +1 editor (Account 3 uses different content style — more whiteboard/teardown). Total: you + 2 editors + community manager. Monthly operational cost: $4,500–7,000
Stage C — Months 7–9 (Add Lane 3)
New account launched: AI Agents & Custom GPTs (Account 4) Stage served: C21–C42 (full Yacht + Mega Yacht)
Why third: Your Phase 5 Mega Yacht courses ($2,997+) need Accounts 1–3 already populating ascension demand before higher-ticket Phase 5 offers have a populated audience to convert.
Team additions: +1 technical editor or contractor for agent demos. Total: you + 3 editors + community manager + part-time tech. Monthly operational cost: $7,000–11,000
Stage D — Months 10–12 (Add Lane 4)
New account launched: AEO/GEO (Account 5) Stage served: C43–C55 (Bora Bora Cruise Ship + Sovereign Operator)
Why last: Smallest audience, most sophisticated, highest-ticket. By month 10 you have 9 months of content, data, and case studies for proof in this technical niche. Revenue from Accounts 1–4 funds the slower ramp of Account 5.
Critical strategic note: Account 5 is the gateway to your Stage 6 offers ($15K–$50K+). Conversion volume is low but revenue per conversion is dramatically higher. Don't measure this account by the same metrics as Accounts 1–4.
Team additions: Content director to oversee all 5 accounts. You shift to strategic oversight. Total: you (strategic) + content director + 3–4 editors + community manager + part-time tech. Monthly operational cost: $11,000–16,000
Stage E — Year 2 (Full Armada)
All 5 accounts running + Free Skool community + paid Circle continuityStage served: All 6 maritime stages, full value ladder operational
Revenue mix at Year 2 (realistic estimate):
Account 1 (Stage 1 buyers): 40% of customer volume, 8% of revenue
Account 2 (Stage 2 buyers): 30% of volume, 15% of revenue
Account 3 (Stage 3–4 buyers): 20% of volume, 35% of revenue
Account 4 (Stage 5 buyers): 8% of volume, 27% of revenue
Account 5 (Stage 6 buyers): 2% of volume, 15% of revenue
The math is brutal and honest: the top 2% of your customer base (Stage 6) generates 15% of your revenue. The top 10% (Stage 4–6) generates 77%. This is exactly why scaling 5 accounts is worth the operational complexity — the high-end of your ladder requires its own dedicated acquisition channel.
---
Part 4 — The Maritime Stage × Content Pillar Cross-Reference
For each Riser Nation course, here's which social account should mine it for content:
Course
Stage
Account #
Content Type
C1 Harbor Orientation
1
Account 1
Founder philosophy, manifesto
C2 Buoy Navigation
1
Account 1 + 2
Market reading basics
C3 Casting the Nets
1
Account 2
First offer creation
C4 The Commercial Fleet
1
Account 2
Traffic intro
C5 Funnel Harbors
1
Account 1 + 3
Conversion concepts (gate)
C6 Email Harbor Systems
2
Account 2 + 3
Email infrastructure
C7 Offer Fleet Expansion
2
Account 3
Value ladder engineering
C8 Paid Traffic Armadas
2
Account 3
Paid traffic systems
C9 Bora Bora Retreat
2
Account 1
Strategic clarity rituals
C10 Funnel Fleet Engineering
2
Account 3
Funnel architecture (gate)
C11 Podcast Broadcasting Fleet
3
Account 3
Authority voice
C12 Video Authority Ships
3
Account 3
Visual influence
C13 Offer Fleet Expansion (advanced)
3
Account 3
Advanced ladder
C14 Funnel Fleet Engineering (advanced)
3
Account 3
Advanced conversion (gate)
C15 Automation Fleet Systems
4
Account 3 + 4
Marketing automation
C16 AI Captain Systems
4
Account 4
AI operations
C17 Data Sonar Systems
4
Account 4
Analytics
C18 Partnership Harbors
4
Account 3 + 5
Strategic alliances
C19 Community Fishing Villages
4
Account 3
Audience ecosystems
C20 Brand Flagship Ships
4
Account 3 + 5
Authority identity
C21 Content AI Factories
4
Account 4
Scalable content
C22 Traffic Arbitrage Fleets
4
Account 3
Advanced traffic
C23 Funnel Optimization Shipyards
4
Account 3
Conversion engineering
C24 Monetization Fleet Economics
4
Account 3
Revenue systems
C25 Operational Fleet Management
4
Account 4
Infrastructure
C26 Agentic Crew Systems
5
Account 4
AI workforce
C27 Autonomous AI Ships
5
Account 4
Self-operating systems (gate)
C28 AI Shipyards
5
Account 4
Building AI products
C29 Knowledge Ocean Mapping
5
Account 4 + 5
AI knowledge systems
C30 Strategic Ocean Navigation
5
Account 4
AI strategy
C31 Content Fishing Net Factories
5
Account 4
AI content production
C32 Global Shipping Lanes
5
Account 4 + 5
Distribution networks
C33 Traffic Harvesting Trawlers
5
Account 5
Audience acquisition (gate)
C34 Conversion Harbor Engineering
5
Account 5
Funnel monetization
C35 Revenue Cargo Systems
5
Account 5
Customer LTV
C36 Fleet Operations Command
5
Account 4 + 5
Scaling enterprises
C37 Global Trade Routes
5
Account 5
International expansion
C38 Strategic Alliance Harbors
5
Account 5
Joint ventures
C39 Fleet Intelligence Command
5
Account 5
Predictive strategy
C40 Armada Coordination Systems
5
Account 5
Enterprise ecosystem
C41 Autonomous Enterprise Fleets
6
Account 5
Self-operating companies
C42 Digital Trade Empires
6
Account 5
Networked economies (gate)
C43 Sovereign Operator Command
6
Account 5
Independent ownership
C44 Legacy Fleet Architecture
6
Account 5
Generational wealth
C45 Infinite Ocean Strategy
6
Account 5
Future markets
C46–C55
6
Account 5 + Flagship
Sovereign tier specializations
---
Part 5 — The Honest Constraints
What this architecture requires that most operators don't account for:
The flagship cannot be delegated. You on camera is the trust anchor for the entire ladder. Stage 6 buyers ($15K–$50K) will stalk this account before they buy. If you outsource the founder voice, the top of the ladder collapses.
Each faceless account needs its own editor with a distinct voice. Account 2's voice (warm, encouraging, demystifying) is different from Account 4's voice (technical, demonstrative, ROI-focused). One editor cannot run all four faceless accounts well.
The free Skool community needs a dedicated community manager from day 1. Not part-time, not "I'll get to it." A neglected free community is worse than no free community — it signals the academy is dead.
You must publish the syllabus alignment publicly. Every social account should make it clear which Riser Nation stage it serves. This is a feature, not a bug — sophisticated buyers respect transparency. "This account teaches Stage 2 — Sailboat. For Stage 5 content, follow @[Account4Handle]."
The AOV math must work or the team math doesn't work. At $200 AOV (Stage 1–2), you need ~30 sales/month to fund Stage A operations. At $1,500 AOV (Stage 3–4), you need 5/month. At $9,997 AOV (Stage 5), you need 1–2/month. Each account's funnel must hit these baselines before adding the next account.
AIO/AEO/GEO is the moat. Every social account should be feeding citable, schema-ready content into the AI search engines. This is what your syllabus already does at the course level. Mirror that discipline in social.
---
Part 6 — The First Decision
Before launching anything, the foundational decision is which graduation gate course you productize first as a free lead magnet. Recommended order:
First lead magnet: C1 Harbor Orientation excerpt — "The Riser Manifesto + Operator Identity Quiz"
- Powers Account 1 (Flagship) - Lowest production cost, highest emotional resonance - Sets up the entire ladder
Second lead magnet: C7 Offer Fleet Expansion excerpt — "The 5-Rung Value Ladder Blueprint"
- Powers Account 3 (Value Ladder) - Highest perceived value, drives the highest-margin avatar - This is the asset that gets shared in Slack groups and creator masterminds
Third lead magnet: C26 Agentic Crew Systems excerpt — "5 Ready-to-Deploy AI Employee Templates"
- Powers Account 4 (AI Agents) - Most actionable, generates immediate "I built one!" social proof - Drives the highest-ticket ascension
Build these three lead magnets first. Then launch in the Stage A → B → C → D sequence outlined in Part 3.
---
Closing Note
This architecture is not aspirational. It is operationally honest. Five accounts is the maximum a single founder + small team can sustain at quality. Six is where things break. The discipline is to launch each account only after the prior account is proving its funnel — not when you're "excited about the next one."
The syllabus is the product. The five social accounts are simply different fishing nets in different waters, all reeling into the same harbor. Build them one at a time. Prove the math. Then duplicate.
The maritime metaphor is not branding fluff — it is an operational architecture. Honor it in your social strategy and the ladder builds itself.
Teach the older plan’s twenty-five pillars
V1 uses different course titles and content assignments. Read its full cross-reference as historical source material. A shared number does not establish that a v1 course is the same as a v2 course or a current lesson.
Founder pillar 1 — Manifesto and identity. Explain the operator behavior the message encourages and the source belief behind it. Keep this separate from an unsupported claim about what an age group can achieve.
Founder pillar 2 — Not too late. Distinguish encouragement from proof. A truthful example can show one person’s experience without establishing a general result or guaranteed timeline.
Founder pillar 3 — Reduce Mismatches. Explain a concrete gap between expectations and reality, readiness and action, or strategy and execution, using the definitions available in the related v2 map.
Founder pillar 4 — Behind the scenes. Show actual work, decisions and limits when describing the academy’s development. A proposed artifact must not be presented as finished.
Founder pillar 5 — Member origin stories. Use accurate accounts with the member’s permission, as the source specifies. Do not invent a member or imply an illustrative story is a testimonial.
First-builder pillar 1 — One prompt demonstration. Choose one tool and one intended output, show the input and evaluate the output. A successful-looking response is not proof that the whole business process works.
First-builder pillar 2 — Relatable age framing. The source’s “I’m 55” example is a suggested framing device. Use that first-person claim only when true of the speaker; otherwise label the example or rewrite it accurately.
First-builder pillar 3 — Pricing psychology. Explain what the buyer is being asked to pay for and which assumptions need evidence. The map names the topic but provides no complete pricing framework.
First-builder pillar 4 — Email list basics. Identify the promised opt-in resource and the follow-up route. The source’s ten-day prompt sequence differs from v2’s offer-engineering sequence; the actual prompt directory and finished emails are not provided here.
First-builder pillar 5 — Funnel anatomy. In the proposed sixty-second teardown, explain what each step asks the buyer to understand or decide. Sixty seconds is the source’s content format, not a complete funnel audit.
Value-ladder pillar 1 — LTV demonstrations. Keep the Marcus $197-to-$612 example separate from verified customer data. Show a calculation only when its inputs and definitions are available; the map does not supply the complete case.
Value-ladder pillar 2 — A single-course plateau. Examine whether the customer has further needs and whether the business can serve them. Having one course alone does not prove a cause of stalled revenue.
Value-ladder pillar 3 — Ascension. Explain what additional outcome or service a later offer provides. A price increase without a defined benefit does not establish a useful next step.
Value-ladder pillar 4 — Continuity, churn and retention. Separate the ongoing service, the customers who stop and the customers who continue. Any rate needs a defined cohort and period; the named frameworks are not fully supplied by this map.
Value-ladder pillar 5 — Public teardowns. Separate what is visible in a funnel from speculation about its performance. Public pages do not reveal a business’s actual conversion rate or internal costs.
AI pillar 1 — Twenty-minute build. Record what was built and tested during the demonstration. The suggested speed claim is neither measured evidence nor a promise that all learners can reproduce it.
AI pillar 2 — AI Employee Framework. Identify the proposed role, input, output and review responsibility. These are authored questions for a walkthrough; the complete named framework is missing.
AI pillar 3 — Agent ecosystem. Explain the intended components and handoffs, then ask for evidence that they work together. A diagram or product list is not an operating system.
AI pillar 4 — GPT, agent or chatbot. Compare the intended task and required behavior before selecting a format. The source names a decision framework but does not provide its definitions or rubric; do not fabricate them as source content.
AI pillar 5 — ROI evidence. The map asks for real hours-saved and revenue-per-agent cases. Record the baseline, observation window, costs and attribution limits. A time-saving estimate is not automatically cash saved, and generated output is not revenue.
Search pillar 1 — Citations versus rankings. Record the exact question, system and date when comparing observations. A search ranking and a generated-answer citation are different observations; one cannot be inferred from the other.
Search pillar 2 — Schema tutorials. Connect any proposed markup to the actual visible content, and check current official guidance during implementation. This map contains no complete markup tutorial or supported-result guarantee.
Search pillar 3 — Direct answers. Answer the reader’s question clearly with support. Do not replace the answer with a keyword list or assume that concise text alone produces citations.
Search pillar 4 — Entity authority. Use accurate, evidenced identities, appearances and quotations. The proposed Wikidata route does not establish eligibility, and invented authority would contradict the purpose of source-backed teaching.
Search pillar 5 — Demonstrations and audits. Preserve the test questions and observed responses with dates. The named audit tool and ten-query asset are not delivered by this source.
Interpret the older schedule and source assignments
The six-stage ladder describes identity and market selection, first offer and funnel, traffic and revenue, systems and scale, AI capability, and longer-term governance. Its price bands are proposals tied to those legacy stages. The source’s roughly 360 modules are not a count of this twelve-course curriculum’s lessons.
The course-to-account table assigns content topics, not complete teaching bodies. Its forty-six data rows include the grouped C46–C55 entry; that group does not provide ten separate course descriptions. Account 1’s source list says C5 concepts rather than implementation. Preserve that scope while using the current spreadsheet to decide where the actual documents belong.
The initial phase proposes two accounts plus community, two hundred weekly opt-ins, thirty-percent community entry and three-to-five-percent buying within thirty days. It does not clearly specify whether the purchase percentage uses opt-ins or community members as its denominator. Define the cohort before reporting that metric. Its community percentage also lacks v2’s explicit fourteen-day window.
The second phase adds the value-ladder account during months four to six and a second editor, with the same $4,500–$7,000 budget range seen in v2. The third adds AI during months seven to nine with $7,000–$11,000 monthly operations; its C21–C42 scope differs from the earlier account’s C28–C42 heading and C26/C27 examples.
The fourth phase places search in months ten to twelve, proposes a content director and three-to-four editors, and estimates $11,000–$16,000 monthly costs. Nine months of accumulated content is treated as proof in the source, but elapsed time does not establish evidence quality. The proposed strategic-only founder role still conflicts with the nondelegated flagship requirement. The year-two configuration adds paid continuity; that is a proposed state, not verified service availability.
Apply the six older constraints using the same checks as v2: truthful founder presence, distinct editorial needs, actual community staffing, clear audience labels, gross revenue versus real costs, and source-supported discovery content. V1’s claims of a highest-converting search account, highest-margin value-ladder account, inevitable sharing of a lead magnet, or immediate template results are unsupported by data in the map.
The first production list calls its selections graduation-gate material, but C1, C7 and C26 are not in the source introduction’s own C5/C10/C14/C27/C33/C42 gate list. Preserve that contradiction. Its three assets support Accounts 1, 3 and 4, leaving Account 2’s launch resource outside the list despite launching Account 2 in the first phase. These are unresolved planning details, not permission to drop the resource or silently revise the historical plan.
Reconcile the v1 differences before applying anything
V1 has no separate enterprise account. Its first-builder content emphasizes AI prompts, pricing, email and funnel basics. Its third account emphasizes value ladders, retention and teardowns. Its fourth adds AI employee templates and GPT-versus-agent-versus-chatbot decisions. Its fifth is search visibility. These are topic references, not complete definitions of those frameworks.
Its initial three lead magnets are a Manifesto/Identity Quiz, a five-rung ladder blueprint for Account 3 and five AI employee templates for Account 4. Its earlier Account 1 lead magnet has a different name, while Account 2's prompt pack is absent from that first-three production list. Keep the missing assets and naming differences visible.
V1's thirty-day purchase target of three to five percent is not v2's stated buyer-count gate. V1 moves search into months ten to twelve; v2 adds enterprise first and moves search to months fifteen to eighteen. Neither version proves that sequence is necessary for this business.
The older revenue table totals one hundred percent of customers and revenue. Its last two accounts represent ten percent of customers and forty-two percent of revenue. Seventy-seven percent of revenue comes from the last three accounts, which represent thirty percent of customers. The source's ten-percent/seventy-seven-percent claim is incorrect. Its $200-versus-$1,500 AOV examples are a 7.5-fold difference, not a doubling; a blended average needs volume weights.
V1 stage boundaries disagree with its own table for C26/C27 and C41/C42. It groups C46–C55 rather than defining each row. Its five-account maximum/six-breaks claim conflicts with v2's six/seven claim. Its part-time versus dedicated community role and strategic versus nondelegated founder work also conflict. Preserve the versions and resolve actual capacity from evidence.
RISER NATION CORP is the project destination. IF YOU AREN'T BUILDING, YOU ARE DESTROYING.
Turn in: one proposed account-role brief with its reader, teaching outcome, source links, real next-step destination, required assets, responsible owner and evidence gate. Add a version-conflict register covering course labels, price, schedule and staffing. Label assumptions and missing resources. Keep it in your course work folder until the submission destination is confirmed. A reviewer should check alignment and capacity before any account launch, purchase or publication.
Original text, tables and explicit list markers with basic emphasis. Complete style metadata is in the download; visual layout comparison remains pending.
Riser Nation Academy 2026 Master Synthesis Edition
Social Account Scaling Architecture — Six-Account Map
Source syllabus: Riser Nation Academy · 2026 & Beyond · World-Class Course Syllabus · Master Synthesis Edition (May 2026). 52 core courses across 11 stages, 6 graduation gates with empirical proof requirements, Module-Page Authoring Standard with AIO/AEO/GEO baked into every module.
Doctrine alignment: Every social account exists to reduce a specific mismatch — between what a prospect at a given awareness level expects and what is actually true. The same Reduce Mismatches doctrine that governs course design governs account design.
Key insight: A prospect at C5 (Proof of Pulse — needs first customer) and a prospect at C42 (Enterprise Engagement Proof — closing $50K+ deals) are not the same person. They consume different content, on different platforms, at different times of day, with different proof standards. One social account cannot serve both. Six accounts can, when each is tuned to a specific stage band.
Part 2 — The Six Social Account Engines
ACCOUNT 1 — Founder Flagship: "Late Bloomer"
Stages served: Pre-Stage + Stage 1 (Foundation Doctrine + Harbor) Source courses: C1 Harbor Orientation, C2 Pain Excavation, C3 Avatar Engineering, C4 Market Reality, C5 Proof of Pulse Avatar: 45+ first-time builder, identity-unsettled, hasn't sold anything yet Awareness: "Is it too late?" / "Where do I start?" Price points fed: Free PDF → $27–$97 entry → free Skool/Circle community
Content pillars sourced directly from the syllabus:
1.The Riser Manifesto (C1 M1.1) — Five core beliefs: offers come first, direct response is the engine, AI is the leverage, community is the moat, execution is the religion
2.The Reduce Mismatches Doctrine (C1 M1.2) — Three mismatches: expectation vs. reality, readiness vs. action, strategy vs. execution
3.Identity Before Skill (C1 M1.3) — Kennedy's "you are the market you become"
4.Operator vs. Creator Economy (C1 M1.4) — Operators build owned assets, not rented attention
5.Schwartz's 5 Awareness Levels (C2 M2.1) — The spine of direct-response copy
8.Defer-Without-Shame (C5 M5.5) — Pass/Defer/Rework as doctrine
AIO queries this account should win (pulled from syllabus):
-what is riser nation academy
-how do i pivot to digital marketing at 45
-how do i shift my identity from employee to entrepreneur
-how do i know if my business idea is validated
-what is the empirical floor
-what is the aspirational threshold trap
Platforms: LinkedIn (primary), Instagram, YouTube long-form Production: You on camera. The flagship is the trust anchor — it cannot be delegated. Cadence: 4 LinkedIn + 4 IG + 1 YouTube long-form per week
Lead magnet: "The Riser Manifesto + 3-Mismatch Diagnostic" PDF Funnel: Bio link → PDF opt-in → 5-day email sequence → Operator's Oath video submission → free Builders community → Stage 1 Harbor Bundle ($97)
Why on-camera matters here: Your face is the proof that someone over 45 can build something credible. Stage 6 buyers ($15K+) will stalk this account before they buy anything else in the academy. If you outsource the founder voice, the entire top of the ladder collapses.
ACCOUNT 2 — "AI for First-Time Builders 45+" (Faceless)
Stages served: Stage 2 + Sales Ops Bridge (Sailboat) Source courses: C6 Grand Slam Offer (Hormozi), C7 Hook-Story-Offer (Brunson), C8 Direct Response Copy (Kennedy + Ogilvy + Hopkins + Cialdini), C9 8-Tier Value Ladder, C10 Proof Threshold, C10.5 Sales Operations Avatar: 45+, has a skill or idea, ready to build their first offer Awareness: Solution-aware, looking for the "how" Price points fed: $497–$1,997 (Stage 2 Sailboat Bundle)
Content pillars sourced from real syllabus modules:
1.The Value Equation (C6) — More dream, more belief, less time, less work
2.Bonus Stacking (C6) — How to engineer "feel stupid saying no" offers
3.Hook-Story-Offer (C7) — Brunson's structure for any piece of content
4.Schwartz's 5 Awareness Levels in copy (C8) — Match the message to where they are
6.Outcome Documentation Standard (C10 M10.2) — "$3K in 14 days," not "they loved it"
7.The Refund-Risk Diagnostic (C10 M10.3) — Even when no refunds were requested
8.DM / Call / No-Call decision (C10.5) — Picking the right sales architecture for the tier
AIO queries this account should win:
-how do i create a grand slam offer
-what is hook story offer
-how many customers prove a value ladder works
-how do i document customer outcomes
-what is the proof threshold
-how do i write direct response copy as a beginner
Platforms: Instagram Reels, TikTok, YouTube Shorts, LinkedIn carousels Production: Faceless. AI voiceover + screen recordings + b-roll. Delegated to editor. Cadence: 1 short per day, same video native-captioned per platform
Lead magnet: "The Grand Slam Offer Worksheet" (pulled from C6 M6.5) + "10 AI Prompts for First-Time Sellers" Funnel: Bio link → worksheet opt-in → 10-day email sequence (one offer-engineering principle per day) → Stage 1 bundle ($97) → Stage 2 Sailboat bundle ($497–$997)
Why faceless works here: This avatar is at the bottom of the awareness funnel and intimidated by polished influencers. Faceless removes the comparison ("I'm not like that person") that kills conversions. They want the answer.
Platforms: LinkedIn (primary), Instagram, YouTube long-form teardowns Production: Faceless OR voiceover with screen sharing. Delegated to a second editor with different voice from Account 2. Cadence: 4 LinkedIn + 3 IG + 1 YouTube long-form per week
Lead magnet: "The 8-Tier Value Ladder Blueprint" PDF (from C9) + Interactive LTV Calculator Funnel: Calculator → personalized email recommendations → $97 workshop → $997 Stage 3 Speedboat course → $2,997 Stage 4 Yacht ascension
Why this works: Highest-margin acquisition channel of the six. Audience is pre-qualified — they have revenue, they're frustrated, and they buy solutions. Position content as architecture, not motivation.
Stages served: Stage 5A + Stage 5B (Ship — Infrastructure + Applied AI) Source courses: C21 AI Foundations, C22 Networks & Protocols, C23 Application Layer (Projects/Skills/Agents/Connectors/Extensions), C24 Prompting at Three Levels, C25 Local Hardware & Self-Hosted AI, C26 Building Tools, C27 Infrastructure Proof, C28 AI Marketing Stack 2026, C29 Vibe Coding for Marketers, C30 Multi-Agent Marketing Crews, C31 Content Flywheel, C32 RN-MOS, C33 Applied AI Proof Avatar: Solopreneur or agency owner at $10–50K/mo, ready to systematize with AI Awareness: Has revenue, has operational chaos, looking for AI leverage Price points fed: $4,997–$9,997 (Stage 5A or 5B bundles)
Content pillars sourced from real syllabus modules:
1.The 5-Capability Standard (C27 M27.1) — Working API call, deployed MCP connection, authored Claude Skill, public GitHub repo, deployed HF Space or Netlify widget
2.The Fast-Cash Micro-MVO (C27 M27.2) — Ship a $47–$97 micro-product in 60 minutes using AI infrastructure
3.Prompting at Three Levels (C24) — Tactical, systemic, agentic
4.Multi-Agent Marketing Crews (C30) — How agents collaborate
5.The 30-Day Operator-Out-of-Loop Test (C33 M33.2) — Walk away for 30 days; does the system still produce revenue?
6.The Content Flywheel (C31) — Lean stack vs. Enterprise stack
7.RN-MOS (C32) — Your operating system across the entire business
8.Vibe Coding for Marketers (C29) — Building tools without becoming an engineer
AIO queries this account should win:
-how do i prove my ai infrastructure works
-how do i ship an ai product in 90 minutes
-what is a fast cash micro mvo
-how do i automate my marketing business completely
-what is operator out of the loop automation
-how do i build a multi-agent marketing crew
Platforms: YouTube long-form (primary — this audience consumes long technical content), LinkedIn, X/Twitter Production: Voiceover + screen recordings. Delegated to technical editor. Cadence: 2 YouTube long-form per week + 5 LinkedIn posts + daily X
Lead magnet: "The 90-Minute Demo Rubric" (from C27) + "5 Ready-to-Deploy AI Marketing Agents" Funnel: Rubric opt-in → "Build Your First AI Agent" mini-course ($27) → Stage 5A Infrastructure bundle ($2,997) → Stage 5B Applied AI bundle ($4,997)
Why this works: Audience trusts depth. A 30-minute YouTube teardown converts higher than 30 short-form videos. Positions Riser Nation as operator-grade — the alternative to the "AI hype" crowd.
ACCOUNT 5 — "Enterprise AI for Operators" (Founder + Technical Co-Editor)
Stage served: Stage 5C (Ship — Enterprise AI) Source courses: C36 Enterprise AI Landscape & Buyer Map, C37 Identity/Access/Authentication, C38 Data Governance/Privacy/Sovereignty, C39 System Integration (ERPs/CRMs/Data Plane), C40 Enterprise Deployment & Change Management, C41 Enterprise AI Governance, C42 Enterprise Engagement Proof Avatar: Operators selling AI services to companies with 250–50,000 employees Awareness: Has experience selling to SMB, wants to move upmarket; OR enterprise consultants adding AI to their service catalog Price points fed: $15,000–$50,000+ (Stage 5C standalone OR done-with-you continuity at $1,500–$5,000/mo)
Content pillars sourced from real syllabus modules:
1.The Enterprise Engagement Standard (C42 M42.1) — 5 criteria: signed MSA, SSO/SCIM, Trust Center accepted, governance review, 90-day adoption metric
2.The Reference Customer Question (C42 M42.2) — Would this client refer Riser Nation to a peer?
3.Identity, Access & Enterprise Authentication (C37) — SSO, SCIM, RBAC for AI deployments
4.Data Governance & Sovereignty (C38) — How enterprise data residency requirements shape AI architecture
5.The Buyer Map for Enterprise AI (C36) — Champion, economic buyer, IT/security gatekeeper, end users
6.Change Management for AI Adoption (C40) — Why most enterprise AI pilots die
7.Responsible AI Governance (C41) — Risk frameworks, model evaluation, ongoing review
AIO queries this account should win:
-how do i prove an enterprise ai engagement
-what makes a deal enterprise vs smb
-what is a reference customer in enterprise ai
-how do i close enterprise ai deals
-what is sso scim for enterprise ai
-how do i handle ai data governance for enterprise
Platforms: LinkedIn (primary — this is where enterprise buyers live), X/Twitter (secondary), niche podcast appearances, technical case-study blog Production: Hybrid — you on-camera for trust signals (founder POV), technical co-editor for case-study breakdowns. This account benefits from your face because enterprise buyers buy trust before product. Cadence: 5 LinkedIn + 2 X + 1 long-form case study per week + 1 podcast appearance per month
Lead magnet: "The Enterprise Engagement Checklist" (from C42) + "The SMB-to-Enterprise Buyer Map" PDF Funnel: Checklist opt-in → invitation to monthly Enterprise AI roundtable (Zoom, free) → application for Stage 5C bundle ($15K) OR done-with-you partnership
Why this gets its own account: Stage 5C is the highest-margin block in the entire Academy. Enterprise buyers will not respond to content optimized for $97 buyers and vice versa. Different platforms, different language, different proof standards, different sales cycle (3–9 months, not 3 days). It deserves its own dedicated channel from day one.
Honest caveat: This account ramps slowest. Don't measure it against the others. One $15K close per quarter justifies the entire account.
Stages served: The discoverability layer that runs through the entire syllabus + Stage 7 specialization tracks Source courses: C32.5 AEO / GEO / Share of Model, C51 Trend Surveillance Engine, the Module-Page Authoring Standard documented across all 52 courses Avatar: Marketers, agency owners, content creators with existing SEO programs nervous about AI search shifting their traffic Awareness: Sophisticated, understands SEO, watching traffic shift to ChatGPT/Perplexity/Claude Price points fed: $4,997–$25,000 (C32.5 dedicated course + Stage 7 specialization tracks + done-with-you continuity)
Content pillars sourced from real syllabus modules:
1.The Module-Page Authoring Standard (academy-wide) — Every page ships as an AI-citable answer page
2.Title + Lead + Outcome + Body + Schema (academy-wide) — The 12-element citation-ready format
3.Citation Trap (academy-wide) — Named proprietary frameworks with primary-source definitions
4.AIO queries — How to identify the questions buyers ask AI engines
6.GEO authority signal stacking — Wikidata entities, founder Person schema, podcast appearances, expert quotes
7.Share of Model (SoM) — The C32.5 framework for measuring AI citation share
8.Quarterly Freshness Triggers (C51 Trend Surveillance Engine) — When content needs to be refreshed
AIO queries this account should win:
-what is aeo answer engine optimization
-what is geo generative engine optimization
-how do i get cited by chatgpt
-what is share of model
-how do i optimize for ai search
-what is the module page authoring standard
Platforms: LinkedIn (primary), X/Twitter (active discussion), YouTube long-form teardowns, technical blog Production: Voiceover + screen sharing. Delegated to most technical editor on your team. Cadence: 3 LinkedIn + daily X + 1 YouTube long-form per week
Lead magnet: "The 10-Query AI Search Audit Tool" + "Module-Page Authoring Checklist" PDF Funnel: Audit → $197 AEO workshop → C32.5 course ($2,997) → done-with-you continuity ($1,500/mo) → Stage 7 specialization tracks
Why this works: Smallest target audience of the six, but highest LTV per acquisition. Buyers in this niche readily pay $5K+ and have $25K+ done-with-you budgets. This account converts to the top of your ladder.
THE UNIFYING MIDDLE — Free Skool/Circle Community
Not a social account but the most important asset in architecture.
Every one of the 6 social accounts funnels into this free community. It is where lurkers become buyers and where graduation gates (C5, C10, C14, C27, C33, C42) get celebrated publicly with member proof artifacts (signed Manifestos, Outcome Documentations, 90-Minute Demo recordings, Enterprise Engagement Checklists).
The free community is what makes the 6-account architecture financially viable. Without it, you are acquiring leads you cannot follow up with at scale.
Operational architecture:
-Free tier: Skool or Circle (free plan)
-Mid tier: Paid Circle continuity (already in use)
-Top tier: Stage 6 Fleet community (C44 Community as Moat module is the playbook)
Part 3 — The Highway Scaling Sequence
Stage A — Months 1–3: Foundation Launch
Active accounts: Account 1 (Flagship) + Account 2 (AI for 45+) + Free Skool community Syllabus stages served: Pre-Stage through Stage 2 (C1–C10) Goal: Prove the funnel converts before duplicating it
Why this sequence: If your flagship + one faceless account + free community can't generate consistent email opt-ins and Stage 1–2 sales, adding more accounts will only multiply the failure. Your own academy must clear its own Stage 1 (Proof of Pulse — 1 paying customer) and Stage 2 (Proof Threshold — 3+ customers) before you scale into Stage 3 distribution.
Empirical floor for this stage (apply the academy's own doctrine to your business):
-200+ email opt-ins per week consistently for 3 months
-30%+ join free community within 14 days of opt-in
-1+ paying customer in week 1 (Proof of Pulse for your launch)
-3+ paying customers by month 3 (Proof Threshold)
Team: You + 1 editor (15–20 hrs/week) + 1 part-time community manager Monthly operational cost: $2,500–4,500
Stage B — Months 4–6: Add Direct Response Lane
New account launched: Account 3 (Direct Response Architecture) Syllabus stages served: Stage 3 + Stage 4 (C11–C20) Goal: Pass Stage 3 graduation gate (Distribution Proof) for the Academy's own marketing
Why this account next: Targets a completely different avatar (existing creators with revenue) at a higher price point. Doesn't compete with Account 1+2 for attention.
Critical AOV inflection: Stage 1–2 buyers average ~$200 AOV. Stage 3–4 buyers average ~$1,500 AOV. Same operational cost, much higher revenue per acquisition.
Empirical floor for this stage:
-Account 3 distribution asset hitting ≥30 opt-ins/month at sub-$10 CPO within 60 days (the academy's own C14 standard applied to itself)
-Blended AOV across all accounts exceeds $400
Team additions: +1 editor (Account 3 uses different content style — more whiteboard/teardown). Total: you + 2 editors + community manager. Monthly operational cost: $4,500–7,000
Why third: Your Stage 5 courses ($4,997–$9,997) need Accounts 1–3 already populating ascension demand before higher-ticket offers have a populated audience to convert.
Empirical floor for this stage:
-30-day operator-out-of-loop test passing on Account 1, 2, 3 content production (using your own academy's C33 standard)
-1+ Stage 5A or 5B sale at $4,997+ AOV
Team additions: +1 technical editor or contractor for agent demos. Total: you + 3 editors + community manager + part-time tech. Monthly operational cost: $7,000–11,000
Stage D — Months 10–14: Add Enterprise Lane
New account launched: Account 5 (Enterprise AI for Operators) Syllabus stage served: Stage 5C (C36–C42) Goal: First enterprise engagement (Stage 5C graduation for the Academy itself)
Why now and not later: Enterprise sales cycles are 3–9 months. If you wait until Month 18 to launch this account, your first enterprise closes at Month 24+. Start the funnel filling in Month 10, expect first close around Month 16–20.
Empirical floor for this stage:
-1 enterprise engagement signed with all 5 criteria (signed MSA, SSO/SCIM, Trust Center, governance, 90-day adoption) within 9 months of account launch
-This is the academy's own C42 graduation gate
Team additions: Content director to oversee all accounts. You shift to strategic oversight + Account 5 founder voice. Total: you (strategic + Account 5) + content director + 3 editors + community manager + part-time tech. Monthly operational cost: $11,000–18,000
Stage E — Months 15–18: Add AEO/GEO Lane
New account launched: Account 6 (AEO/GEO Search Visibility) Syllabus served: C32.5 + C51 + academy-wide Module-Page Authoring Standard Goal: Establish Riser Nation as the cited source for AEO/GEO in the AI marketing space
Why last: This account requires 12+ months of citation-ready content already published across the other 5 accounts to have proof of method. You can't credibly teach AEO if you haven't won AEO citations yourself first.
Empirical floor for this stage:
-Riser Nation cited in ChatGPT/Perplexity/Claude responses for ≥10 target queries within 6 months of Account 6 launch
-Wikidata entity for Riser Nation Empirical Floor Doctrine + Reduce Mismatches Doctrine established
Team additions: Add a specialist AEO/GEO content producer. Total: you (strategic) + content director + 4 editors + community manager + part-time tech + AEO specialist. Monthly operational cost: $15,000–22,000
Stage F — Year 2+: Full Armada Operating at Scale
All 6 accounts running + Free community + Paid Circle continuity + Stage 7 sovereign tier
Revenue mix at Year 2 (realistic estimate):
Account
% of Customer Volume
% of Revenue
Account 1 (Stage 1)
45%
6%
Account 2 (Stage 2)
28%
12%
Account 3 (Stage 3–4)
18%
30%
Account 4 (Stage 5A/B)
6%
22%
Account 5 (Stage 5C)
1.5%
20%
Account 6 (AEO/GEO + Stage 7)
1.5%
10%
The honest math: The top 3% of your customer base (Stage 5C + Stage 7 buyers) generates 30% of revenue. The top 10% generates 52%. This is exactly why a 6-account architecture is worth the operational complexity — the high end of your ladder requires its own dedicated acquisition channels.
Part 4 — Course-to-Account Cross-Reference (All 52 Courses)
Course
Title
Stage
Primary Account
Secondary
C1
Harbor Orientation & Riser Manifesto
Pre-Stage
Account 1
—
C2
Pain Excavation & Semantic Foundation
Pre-Stage
Account 1
Account 3
C3
Avatar Engineering (100-Avatar Method)
Pre-Stage
Account 1
Account 3
C4
Market Reality & Niche Validation
Stage 1
Account 1
Account 2
C5
Proof of Pulse (Graduation Gate)
Stage 1
Account 1
Account 6
C6
The Grand Slam Offer (Hormozi)
Stage 2
Account 2
Account 3
C7
Hook-Story-Offer (Brunson)
Stage 2
Account 2
Account 3
C8
Direct Response Copy (Kennedy/Ogilvy/Hopkins/Cialdini)
Stage 2
Account 2
Account 3
C9
The 8-Tier Value Ladder
Stage 2
Account 3
Account 2
C10
Proof Threshold (Graduation Gate)
Stage 2
Account 2
Account 6
C10.5
Sales Operations (DM/Call/No-Call)
Bridge
Account 2
Account 3
C11
Direction Clarity & Dream 100 (2026)
Stage 3
Account 3
—
C12
Skill & Experience Mapping for Content
Stage 3
Account 3
Account 1
C13
Faceless YouTube & AI Higgs Field Engine
Stage 3
Account 2
Account 3
C14
Distribution Proof (Graduation Gate)
Stage 3
Account 3
Account 6
C15
Funnel Engine — Decision Paths
Stage 4
Account 3
—
C16
Customer LTV & Measurement Discipline
Stage 4
Account 3
Account 4
C17
Retention & Anti-Extraction Standard
Stage 4
Account 3
—
C18
Mid-Funnel Trust & YouTube Authority
Stage 4
Account 3
Account 4
C19
Bottom-Funnel Close & IG Growth
Stage 4
Account 3
Account 2
C20
Brand Architecture & Visual Style
Stage 4
Account 3
Account 1
C21
AI Foundations — Models/Modalities/Brain
Stage 5A
Account 4
—
C22
Networks & Protocols — The Nervous System
Stage 5A
Account 4
—
C23
Application Layer (Projects/Skills/Agents)
Stage 5A
Account 4
—
C24
Prompting at Three Levels
Stage 5A
Account 4
Account 2
C25
Local Hardware & Self-Hosted AI
Stage 5A
Account 4
—
C26
Building Tools (Repos/Widgets/Apps)
Stage 5A
Account 4
—
C27
Infrastructure Proof (Graduation Gate)
Stage 5A
Account 4
Account 6
C28
AI Marketing Stack 2026
Stage 5B
Account 4
Account 3
C29
Vibe Coding for Marketers
Stage 5B
Account 4
—
C30
Multi-Agent Marketing Crews
Stage 5B
Account 4
—
C31
The Content Flywheel
Stage 5B
Account 4
Account 3
C32
RN-MOS — Your Operating System
Stage 5B
Account 4
Account 1
C32.5
AEO/GEO/Share of Model
Bridge
Account 6
Account 4
C33
Applied AI Proof (Graduation Gate)
Stage 5B
Account 4
Account 6
C36
Enterprise AI Landscape & Buyer Map
Stage 5C
Account 5
—
C37
Identity/Access/Enterprise Authentication
Stage 5C
Account 5
—
C38
Data Governance/Privacy/Sovereignty
Stage 5C
Account 5
—
C39
System Integration (ERPs/CRMs/Data Plane)
Stage 5C
Account 5
—
C40
Enterprise Deployment & Change Management
Stage 5C
Account 5
—
C41
Enterprise AI Governance & Responsible AI
Stage 5C
Account 5
Account 6
C42
Enterprise Engagement Proof (Graduation Gate)
Stage 5C
Account 5
Account 6
C43
VA & Team Onboarding via SOPs
Stage 6
Account 4
Account 5
C44
Community as Moat
Stage 6
Account 1
Account 3
C45
Outbound Outreach
Stage 6
Account 3
Account 5
C46
Ethical Persuasion & ETM
Stage 6
Account 1
Account 3
C47
Group Attention (Webinars/Challenges)
Stage 6
Account 3
Account 2
C48
Retargeting Ecosystems & WAESM
Stage 6
Account 3
Account 4
C49
Crisis Navigation & Reputation
Stage 6
Account 5
Account 1
C50
Executive Command & 85-Minute Cadence
Stage 7
Account 1
Account 5
C51
Trend Surveillance Engine
Stage 7
Account 6
Account 4
C52
Legal, Finance & IP Protection
Stage 7
Account 5
—
C53
IP Productization (Licensing/Cert/White-Label)
Stage 7
Account 5
—
C54
Acquisition or Distribution (Year 10)
Stage 7
Account 1
Account 5
C55
Capstone — Architect of Orchestration
Capstone
Account 1
—
Part 5 — Applying the Academy's Own Doctrine to the Account Launch
This is the most important section in the document. Every social account launch should follow the same Pass/Defer/Rework discipline the Academy teaches.
Account 1 (Flagship) Empirical Floor — Apply by Day 90:
-1 paying customer at validated price (Stage 1 Harbor bundle, $97 or higher)
-Signed testimonial with documented outcome
-Refund analysis (even if no refunds requested)
-If not met: Defer-Without-Shame. Return to C1–C5 in your own academy and reapply.
Account 2 (AI for 45+) Empirical Floor — Apply by Day 180:
-3+ paying customers at Stage 2 Sailboat bundle pricing ($497+)
-Documented outcomes in customer's own words
-Validated pricing across the ladder
-If not met: Don't add Account 3 yet. The funnel isn't ready to duplicate.
Account 3 (Direct Response Architecture) Empirical Floor — Apply by Day 270:
-Distribution asset producing ≥30 opt-ins/month at sub-$10 CPO for 3 consecutive months
-If not met: This is a Stage 3 failure. The defer protocol: stop Account 4 launch, fix Account 3 first.
Account 4 (AI Infrastructure) Empirical Floor — Apply by Day 360:
-Account 4 itself shipping content via the 30-Day Operator-Out-of-Loop Test
-1+ Stage 5 sale at $4,997+ AOV
-If not met: This is a Stage 5B failure in the academy's own business. Defer Account 5.
Account 5 (Enterprise) Empirical Floor — Apply by Month 18:
-1 enterprise engagement signed with all 5 C42 criteria
-Reference customer test passed (would they refer Riser Nation to a peer?)
-If not met: This is a C42 defer pattern. Most likely cause: account was launched before flagship + Account 4 had sufficient enterprise-trust signals.
Account 6 (AEO/GEO) Empirical Floor — Apply by Month 24:
-Riser Nation cited by ChatGPT/Perplexity/Claude for 10+ target queries
-Wikidata entities established for at least 5 proprietary frameworks
-If not met: Account 6 is the slowest to gate. Allow defer pattern up to Month 30.
Part 6 — The Honest Constraints (Updated for the Real Syllabus)
Six structural truths most operators don't plan for:
1.The flagship cannot be delegated. You on camera is the trust anchor for the entire ladder. Stage 5C buyers ($15K–$50K) and Stage 7 sovereign-tier buyers will stalk Account 1 before they buy anything else. If you outsource the founder voice, the top of the ladder collapses.
2.Each faceless account needs its own editor with a distinct voice. Account 2 (warm, encouraging, demystifying) is different from Account 4 (technical, demonstrative, ROI-focused) which is different from Account 6 (research-driven, citation-focused). One editor cannot run all four faceless accounts well.
3.The free Skool/Circle community needs a dedicated community manager from day 1. Not part-time, not "I'll get to it." A neglected free community signals the academy is dead.
4.You must publish the stage alignment publicly. Every social account should make it clear which Riser Nation stage it serves. "This account teaches Stage 2 — Sailboat. For Stage 5 content, follow @[Account 4 handle]." This is a feature, not a bug — sophisticated buyers respect transparency.
5.The AOV math must work or the team math doesn't work. At $200 AOV (Stage 1–2), you need ~30 sales/month to fund Stage A operations. At $1,500 AOV (Stage 3–4), 5/month. At $9,997 AOV (Stage 5), 1–2/month. At $15K+ AOV (Stage 5C), 1/quarter justifies the account. Each account's funnel must hit these baselines before adding the next account.
6.The Module-Page Authoring Standard IS the AEO/GEO moat. Every social post should be feeding citable, schema-ready content into the AI search engines. The academy already does this at the course level via the 12-element Module-Page Standard (Title/Lead/Outcome/Body/Schema/Artifact/Cluster/Video Kit/Lineage/Freshness/Citation Trap/E-E-A-T). Mirror that discipline in social.
Part 7 — Sequenced Lead Magnet Production
Build these three first lead magnets before launching anything:
Lead Magnet 1 — Powers Account 1 (Flagship): "The Riser Manifesto + 3-Mismatch Diagnostic"
Lead Magnet 2 — Powers Account 2 (AI for 45+): "The Grand Slam Offer Worksheet (Hormozi Value Equation Applied)"
-Source: C6 modules
-Production: Fillable PDF + companion 10-day email sequence
-Includes: Value Equation calculator, bonus-stacking template, guarantee-writing prompts
Lead Magnet 3 — Powers Account 3 (Direct Response): "The 8-Tier Value Ladder Blueprint + LTV Calculator"
-Source: C9 + C16
-Production: Interactive web tool (preferred) OR fillable PDF
-Includes: 8-tier worksheet, LTV math examples (Marcus the Designer case study), pricing-by-tier rules
Build these in this order. Don't launch Account 1 without #1 ready. Don't launch Account 2 without #2 ready. Don't launch Account 3 without #3 ready.
Closing Note
This architecture is not aspirational. It is operationally honest and now correctly grounded in the actual 2026 Master Synthesis Edition syllabus. Six accounts is the maximum a founder + small team can sustain at quality. Seven is where things break.
The discipline is to launch each account only after the prior account has passed its empirical floor — the same Pass/Defer/Rework gates the Academy teaches students. Defer-Without-Shame applies to your own business too.
The syllabus IS the product. The six social accounts are simply different fishing nets in different waters, all reeling into the same harbor.
Build them one at a time. Prove the math at each gate. Then duplicate.
The maritime stage progression is not branding fluff — it is an operational architecture. Honor it in your social strategy and the ladder builds itself.
Riser Nation Academy 2026 Master Synthesis Edition
Social Account Scaling Architecture — Six-Account Map
Source syllabus: Riser Nation Academy · 2026 & Beyond · World-Class Course Syllabus · Master Synthesis Edition (May 2026). 52 core courses across 11 stages, 6 graduation gates with empirical proof requirements, Module-Page Authoring Standard with AIO/AEO/GEO baked into every module.
Doctrine alignment: Every social account exists to *reduce a specific mismatch* — between what a prospect at a given awareness level expects and what is actually true. The same Reduce Mismatches doctrine that governs course design governs account design.
Key insight: A prospect at C5 (Proof of Pulse — needs first customer) and a prospect at C42 (Enterprise Engagement Proof — closing $50K+ deals) are not the same person. They consume different content, on different platforms, at different times of day, with different proof standards. One social account cannot serve both. Six accounts can, when each is tuned to a specific stage band.
---
Part 2 — The Six Social Account Engines
ACCOUNT 1 — Founder Flagship: "Late Bloomer"
Stages served: Pre-Stage + Stage 1 (Foundation Doctrine + Harbor) Source courses: C1 Harbor Orientation, C2 Pain Excavation, C3 Avatar Engineering, C4 Market Reality, C5 Proof of Pulse Avatar: 45+ first-time builder, identity-unsettled, hasn't sold anything yet Awareness: "Is it too late?" / "Where do I start?" Price points fed: Free PDF → $27–$97 entry → free Skool/Circle community
Content pillars sourced directly from the syllabus:
The Riser Manifesto (C1 M1.1) — Five core beliefs: offers come first, direct response is the engine, AI is the leverage, community is the moat, execution is the religion
The Reduce Mismatches Doctrine (C1 M1.2) — Three mismatches: expectation vs. reality, readiness vs. action, strategy vs. execution
Identity Before Skill (C1 M1.3) — Kennedy's "you are the market you become"
Operator vs. Creator Economy (C1 M1.4) — Operators build owned assets, not rented attention
Schwartz's 5 Awareness Levels (C2 M2.1) — The spine of direct-response copy
The Empirical Floor Doctrine (C5 M5.1) — Proof = 1 paying customer, signed testimonial, refund analysis
The Aspirational Threshold Trap (C5 M5.2) — Stop moving goalposts
Defer-Without-Shame (C5 M5.5) — Pass/Defer/Rework as doctrine
AIO queries this account should win (pulled from syllabus):
what is riser nation academy
how do i pivot to digital marketing at 45
how do i shift my identity from employee to entrepreneur
how do i know if my business idea is validated
what is the empirical floor
what is the aspirational threshold trap
Platforms: LinkedIn (primary), Instagram, YouTube long-form Production: You on camera. The flagship is the trust anchor — it cannot be delegated. Cadence: 4 LinkedIn + 4 IG + 1 YouTube long-form per week
Lead magnet: "The Riser Manifesto + 3-Mismatch Diagnostic" PDF Funnel: Bio link → PDF opt-in → 5-day email sequence → Operator's Oath video submission → free Builders community → Stage 1 Harbor Bundle ($97)
Why on-camera matters here: Your face is the proof that someone over 45 can build something credible. Stage 6 buyers ($15K+) will stalk this account before they buy anything else in the academy. If you outsource the founder voice, the entire top of the ladder collapses.
---
ACCOUNT 2 — "AI for First-Time Builders 45+" (Faceless)
Stages served: Stage 2 + Sales Ops Bridge (Sailboat) Source courses: C6 Grand Slam Offer (Hormozi), C7 Hook-Story-Offer (Brunson), C8 Direct Response Copy (Kennedy + Ogilvy + Hopkins + Cialdini), C9 8-Tier Value Ladder, C10 Proof Threshold, C10.5 Sales Operations Avatar: 45+, has a skill or idea, ready to build their first offer Awareness: Solution-aware, looking for the "how" Price points fed: $497–$1,997 (Stage 2 Sailboat Bundle)
Content pillars sourced from real syllabus modules:
The Value Equation (C6) — More dream, more belief, less time, less work
Bonus Stacking (C6) — How to engineer "feel stupid saying no" offers
Hook-Story-Offer (C7) — Brunson's structure for any piece of content
Schwartz's 5 Awareness Levels in copy (C8) — Match the message to where they are
The 8-Tier Value Ladder (C9) — Free → entry → core → ascension → premium → continuity → sovereign → legacy
Outcome Documentation Standard (C10 M10.2) — "$3K in 14 days," not "they loved it"
The Refund-Risk Diagnostic (C10 M10.3) — Even when no refunds were requested
DM / Call / No-Call decision (C10.5) — Picking the right sales architecture for the tier
AIO queries this account should win:
how do i create a grand slam offer
what is hook story offer
how many customers prove a value ladder works
how do i document customer outcomes
what is the proof threshold
how do i write direct response copy as a beginner
Platforms: Instagram Reels, TikTok, YouTube Shorts, LinkedIn carousels Production: Faceless. AI voiceover + screen recordings + b-roll. Delegated to editor. Cadence: 1 short per day, same video native-captioned per platform
Lead magnet: "The Grand Slam Offer Worksheet" (pulled from C6 M6.5) + "10 AI Prompts for First-Time Sellers" Funnel: Bio link → worksheet opt-in → 10-day email sequence (one offer-engineering principle per day) → Stage 1 bundle ($97) → Stage 2 Sailboat bundle ($497–$997)
Why faceless works here: This avatar is at the bottom of the awareness funnel and intimidated by polished influencers. Faceless removes the comparison ("I'm not like that person") that kills conversions. They want the *answer*.
Platforms: LinkedIn (primary), Instagram, YouTube long-form teardowns Production: Faceless OR voiceover with screen sharing. Delegated to a second editor with different voice from Account 2. Cadence: 4 LinkedIn + 3 IG + 1 YouTube long-form per week
Lead magnet: "The 8-Tier Value Ladder Blueprint" PDF (from C9) + Interactive LTV Calculator Funnel: Calculator → personalized email recommendations → $97 workshop → $997 Stage 3 Speedboat course → $2,997 Stage 4 Yacht ascension
Why this works: Highest-margin acquisition channel of the six. Audience is pre-qualified — they have revenue, they're frustrated, and they buy solutions. Position content as architecture, not motivation.
Stages served: Stage 5A + Stage 5B (Ship — Infrastructure + Applied AI) Source courses: C21 AI Foundations, C22 Networks & Protocols, C23 Application Layer (Projects/Skills/Agents/Connectors/Extensions), C24 Prompting at Three Levels, C25 Local Hardware & Self-Hosted AI, C26 Building Tools, C27 Infrastructure Proof, C28 AI Marketing Stack 2026, C29 Vibe Coding for Marketers, C30 Multi-Agent Marketing Crews, C31 Content Flywheel, C32 RN-MOS, C33 Applied AI Proof Avatar: Solopreneur or agency owner at $10–50K/mo, ready to systematize with AI Awareness: Has revenue, has operational chaos, looking for AI leverage Price points fed: $4,997–$9,997 (Stage 5A or 5B bundles)
Content pillars sourced from real syllabus modules:
The 5-Capability Standard (C27 M27.1) — Working API call, deployed MCP connection, authored Claude Skill, public GitHub repo, deployed HF Space or Netlify widget
The Fast-Cash Micro-MVO (C27 M27.2) — Ship a $47–$97 micro-product in 60 minutes using AI infrastructure
Prompting at Three Levels (C24) — Tactical, systemic, agentic
Multi-Agent Marketing Crews (C30) — How agents collaborate
The 30-Day Operator-Out-of-Loop Test (C33 M33.2) — Walk away for 30 days; does the system still produce revenue?
The Content Flywheel (C31) — Lean stack vs. Enterprise stack
RN-MOS (C32) — Your operating system across the entire business
Vibe Coding for Marketers (C29) — Building tools without becoming an engineer
AIO queries this account should win:
how do i prove my ai infrastructure works
how do i ship an ai product in 90 minutes
what is a fast cash micro mvo
how do i automate my marketing business completely
what is operator out of the loop automation
how do i build a multi-agent marketing crew
Platforms: YouTube long-form (primary — this audience consumes long technical content), LinkedIn, X/Twitter Production: Voiceover + screen recordings. Delegated to technical editor. Cadence: 2 YouTube long-form per week + 5 LinkedIn posts + daily X
Lead magnet: "The 90-Minute Demo Rubric" (from C27) + "5 Ready-to-Deploy AI Marketing Agents" Funnel: Rubric opt-in → "Build Your First AI Agent" mini-course ($27) → Stage 5A Infrastructure bundle ($2,997) → Stage 5B Applied AI bundle ($4,997)
Why this works: Audience trusts depth. A 30-minute YouTube teardown converts higher than 30 short-form videos. Positions Riser Nation as operator-grade — the alternative to the "AI hype" crowd.
---
ACCOUNT 5 — "Enterprise AI for Operators" (Founder + Technical Co-Editor)
Stage served: Stage 5C (Ship — Enterprise AI) Source courses: C36 Enterprise AI Landscape & Buyer Map, C37 Identity/Access/Authentication, C38 Data Governance/Privacy/Sovereignty, C39 System Integration (ERPs/CRMs/Data Plane), C40 Enterprise Deployment & Change Management, C41 Enterprise AI Governance, C42 Enterprise Engagement Proof Avatar: Operators selling AI services to companies with 250–50,000 employees Awareness: Has experience selling to SMB, wants to move upmarket; OR enterprise consultants adding AI to their service catalog Price points fed: $15,000–$50,000+ (Stage 5C standalone OR done-with-you continuity at $1,500–$5,000/mo)
Content pillars sourced from real syllabus modules:
The Enterprise Engagement Standard (C42 M42.1) — 5 criteria: signed MSA, SSO/SCIM, Trust Center accepted, governance review, 90-day adoption metric
The Reference Customer Question (C42 M42.2) — Would this client refer Riser Nation to a peer?
Identity, Access & Enterprise Authentication (C37) — SSO, SCIM, RBAC for AI deployments
Data Governance & Sovereignty (C38) — How enterprise data residency requirements shape AI architecture
The Buyer Map for Enterprise AI (C36) — Champion, economic buyer, IT/security gatekeeper, end users
Change Management for AI Adoption (C40) — Why most enterprise AI pilots die
Responsible AI Governance (C41) — Risk frameworks, model evaluation, ongoing review
AIO queries this account should win:
how do i prove an enterprise ai engagement
what makes a deal enterprise vs smb
what is a reference customer in enterprise ai
how do i close enterprise ai deals
what is sso scim for enterprise ai
how do i handle ai data governance for enterprise
Platforms: LinkedIn (primary — this is where enterprise buyers live), X/Twitter (secondary), niche podcast appearances, technical case-study blog Production: Hybrid — you on-camera for trust signals (founder POV), technical co-editor for case-study breakdowns. This account benefits from your face because enterprise buyers buy trust before product. Cadence: 5 LinkedIn + 2 X + 1 long-form case study per week + 1 podcast appearance per month
Lead magnet: "The Enterprise Engagement Checklist" (from C42) + "The SMB-to-Enterprise Buyer Map" PDF Funnel: Checklist opt-in → invitation to monthly Enterprise AI roundtable (Zoom, free) → application for Stage 5C bundle ($15K) OR done-with-you partnership
Why this gets its own account: Stage 5C is the highest-margin block in the entire Academy. Enterprise buyers will not respond to content optimized for $97 buyers and vice versa. Different platforms, different language, different proof standards, different sales cycle (3–9 months, not 3 days). It deserves its own dedicated channel from day one.
Honest caveat: This account ramps slowest. Don't measure it against the others. One $15K close per quarter justifies the entire account.
Stages served: The discoverability layer that runs through the entire syllabus + Stage 7 specialization tracks Source courses: C32.5 AEO / GEO / Share of Model, C51 Trend Surveillance Engine, the Module-Page Authoring Standard documented across all 52 courses Avatar: Marketers, agency owners, content creators with existing SEO programs nervous about AI search shifting their traffic Awareness: Sophisticated, understands SEO, watching traffic shift to ChatGPT/Perplexity/Claude Price points fed: $4,997–$25,000 (C32.5 dedicated course + Stage 7 specialization tracks + done-with-you continuity)
Content pillars sourced from real syllabus modules:
The Module-Page Authoring Standard (academy-wide) — Every page ships as an AI-citable answer page
Title + Lead + Outcome + Body + Schema (academy-wide) — The 12-element citation-ready format
Citation Trap (academy-wide) — Named proprietary frameworks with primary-source definitions
AIO queries — How to identify the questions buyers ask AI engines
GEO authority signal stacking — Wikidata entities, founder Person schema, podcast appearances, expert quotes
Share of Model (SoM) — The C32.5 framework for measuring AI citation share
Quarterly Freshness Triggers (C51 Trend Surveillance Engine) — When content needs to be refreshed
AIO queries this account should win:
what is aeo answer engine optimization
what is geo generative engine optimization
how do i get cited by chatgpt
what is share of model
how do i optimize for ai search
what is the module page authoring standard
Platforms: LinkedIn (primary), X/Twitter (active discussion), YouTube long-form teardowns, technical blog Production: Voiceover + screen sharing. Delegated to most technical editor on your team. Cadence: 3 LinkedIn + daily X + 1 YouTube long-form per week
Lead magnet: "The 10-Query AI Search Audit Tool" + "Module-Page Authoring Checklist" PDF Funnel: Audit → $197 AEO workshop → C32.5 course ($2,997) → done-with-you continuity ($1,500/mo) → Stage 7 specialization tracks
Why this works: Smallest target audience of the six, but highest LTV per acquisition. Buyers in this niche readily pay $5K+ and have $25K+ done-with-you budgets. This account converts to the top of your ladder.
---
THE UNIFYING MIDDLE — Free Skool/Circle Community
Not a social account but the most important asset in the architecture.
Every one of the 6 social accounts funnels into this free community. It is where lurkers become buyers and where graduation gates (C5, C10, C14, C27, C33, C42) get celebrated publicly with member proof artifacts (signed Manifestos, Outcome Documentations, 90-Minute Demo recordings, Enterprise Engagement Checklists).
The free community is what makes the 6-account architecture financially viable. Without it, you are acquiring leads you cannot follow up with at scale.
Operational architecture:
Free tier: Skool or Circle (free plan)
Mid tier: Paid Circle continuity (already in use)
Top tier: Stage 6 Fleet community (C44 Community as Moat module is the playbook)
---
Part 3 — The Highway Scaling Sequence
Stage A — Months 1–3: Foundation Launch
Active accounts: Account 1 (Flagship) + Account 2 (AI for 45+) + Free Skool community Syllabus stages served: Pre-Stage through Stage 2 (C1–C10) Goal: Prove the funnel converts before duplicating it
Why this sequence: If your flagship + one faceless account + free community can't generate consistent email opt-ins and Stage 1–2 sales, adding more accounts will only multiply the failure. Your own academy must clear its own Stage 1 (Proof of Pulse — 1 paying customer) and Stage 2 (Proof Threshold — 3+ customers) before you scale into Stage 3 distribution.
Empirical floor for this stage (apply the academy's own doctrine to your business):
200+ email opt-ins per week consistently for 3 months
30%+ join free community within 14 days of opt-in
1+ paying customer in week 1 (Proof of Pulse for your launch)
3+ paying customers by month 3 (Proof Threshold)
Team: You + 1 editor (15–20 hrs/week) + 1 part-time community manager Monthly operational cost: $2,500–4,500
Stage B — Months 4–6: Add Direct Response Lane
New account launched: Account 3 (Direct Response Architecture) Syllabus stages served: Stage 3 + Stage 4 (C11–C20) Goal: Pass Stage 3 graduation gate (Distribution Proof) for the Academy's own marketing
Why this account next: Targets a completely different avatar (existing creators with revenue) at a higher price point. Doesn't compete with Account 1+2 for attention.
Critical AOV inflection: Stage 1–2 buyers average ~$200 AOV. Stage 3–4 buyers average ~$1,500 AOV. Same operational cost, much higher revenue per acquisition.
Empirical floor for this stage:
Account 3 distribution asset hitting ≥30 opt-ins/month at sub-$10 CPO within 60 days (the academy's own C14 standard applied to itself)
Blended AOV across all accounts exceeds $400
Team additions: +1 editor (Account 3 uses different content style — more whiteboard/teardown). Total: you + 2 editors + community manager. Monthly operational cost: $4,500–7,000
Why third: Your Stage 5 courses ($4,997–$9,997) need Accounts 1–3 already populating ascension demand before higher-ticket offers have a populated audience to convert.
Empirical floor for this stage:
30-day operator-out-of-loop test passing on Account 1, 2, 3 content production (using your own academy's C33 standard)
1+ Stage 5A or 5B sale at $4,997+ AOV
Team additions: +1 technical editor or contractor for agent demos. Total: you + 3 editors + community manager + part-time tech. Monthly operational cost: $7,000–11,000
Stage D — Months 10–14: Add Enterprise Lane
New account launched: Account 5 (Enterprise AI for Operators) Syllabus stage served: Stage 5C (C36–C42) Goal: First enterprise engagement (Stage 5C graduation for the Academy itself)
Why now and not later: Enterprise sales cycles are 3–9 months. If you wait until Month 18 to launch this account, your first enterprise close lands at Month 24+. Start the funnel filling in Month 10, expect first close around Month 16–20.
Empirical floor for this stage:
1 enterprise engagement signed with all 5 criteria (signed MSA, SSO/SCIM, Trust Center, governance, 90-day adoption) within 9 months of account launch
This is the academy's own C42 graduation gate
Team additions: Content director to oversee all accounts. You shift to strategic oversight + Account 5 founder voice. Total: you (strategic + Account 5) + content director + 3 editors + community manager + part-time tech. Monthly operational cost: $11,000–18,000
Stage E — Months 15–18: Add AEO/GEO Lane
New account launched: Account 6 (AEO/GEO Search Visibility) Syllabus served: C32.5 + C51 + academy-wide Module-Page Authoring Standard Goal: Establish Riser Nation as the cited source for AEO/GEO in the AI marketing space
Why last: This account requires 12+ months of citation-ready content already published across the other 5 accounts to have proof of method. You can't credibly teach AEO if you haven't won AEO citations yourself first.
Empirical floor for this stage:
Riser Nation cited in ChatGPT/Perplexity/Claude responses for ≥10 target queries within 6 months of Account 6 launch
Wikidata entity for Riser Nation Empirical Floor Doctrine + Reduce Mismatches Doctrine established
Team additions: Add a specialist AEO/GEO content producer. Total: you (strategic) + content director + 4 editors + community manager + part-time tech + AEO specialist. Monthly operational cost: $15,000–22,000
Stage F — Year 2+: Full Armada Operating at Scale
All 6 accounts running + Free community + Paid Circle continuity + Stage 7 sovereign tier
Revenue mix at Year 2 (realistic estimate):
Account
% of Customer Volume
% of Revenue
Account 1 (Stage 1)
45%
6%
Account 2 (Stage 2)
28%
12%
Account 3 (Stage 3–4)
18%
30%
Account 4 (Stage 5A/B)
6%
22%
Account 5 (Stage 5C)
1.5%
20%
Account 6 (AEO/GEO + Stage 7)
1.5%
10%
The honest math: The top 3% of your customer base (Stage 5C + Stage 7 buyers) generates 30% of revenue. The top 10% generates 52%. This is exactly why a 6-account architecture is worth the operational complexity — the high end of your ladder requires its own dedicated acquisition channels.
---
Part 4 — Course-to-Account Cross-Reference (All 52 Courses)
Course
Title
Stage
Primary Account
Secondary
C1
Harbor Orientation & Riser Manifesto
Pre-Stage
Account 1
—
C2
Pain Excavation & Semantic Foundation
Pre-Stage
Account 1
Account 3
C3
Avatar Engineering (100-Avatar Method)
Pre-Stage
Account 1
Account 3
C4
Market Reality & Niche Validation
Stage 1
Account 1
Account 2
C5
Proof of Pulse (Graduation Gate)
Stage 1
Account 1
Account 6
C6
The Grand Slam Offer (Hormozi)
Stage 2
Account 2
Account 3
C7
Hook-Story-Offer (Brunson)
Stage 2
Account 2
Account 3
C8
Direct Response Copy (Kennedy/Ogilvy/Hopkins/Cialdini)
Stage 2
Account 2
Account 3
C9
The 8-Tier Value Ladder
Stage 2
Account 3
Account 2
C10
Proof Threshold (Graduation Gate)
Stage 2
Account 2
Account 6
C10.5
Sales Operations (DM/Call/No-Call)
Bridge
Account 2
Account 3
C11
Direction Clarity & Dream 100 (2026)
Stage 3
Account 3
—
C12
Skill & Experience Mapping for Content
Stage 3
Account 3
Account 1
C13
Faceless YouTube & AI Higgs Field Engine
Stage 3
Account 2
Account 3
C14
Distribution Proof (Graduation Gate)
Stage 3
Account 3
Account 6
C15
Funnel Engine — Decision Paths
Stage 4
Account 3
—
C16
Customer LTV & Measurement Discipline
Stage 4
Account 3
Account 4
C17
Retention & Anti-Extraction Standard
Stage 4
Account 3
—
C18
Mid-Funnel Trust & YouTube Authority
Stage 4
Account 3
Account 4
C19
Bottom-Funnel Close & IG Growth
Stage 4
Account 3
Account 2
C20
Brand Architecture & Visual Style
Stage 4
Account 3
Account 1
C21
AI Foundations — Models/Modalities/Brain
Stage 5A
Account 4
—
C22
Networks & Protocols — The Nervous System
Stage 5A
Account 4
—
C23
Application Layer (Projects/Skills/Agents)
Stage 5A
Account 4
—
C24
Prompting at Three Levels
Stage 5A
Account 4
Account 2
C25
Local Hardware & Self-Hosted AI
Stage 5A
Account 4
—
C26
Building Tools (Repos/Widgets/Apps)
Stage 5A
Account 4
—
C27
Infrastructure Proof (Graduation Gate)
Stage 5A
Account 4
Account 6
C28
AI Marketing Stack 2026
Stage 5B
Account 4
Account 3
C29
Vibe Coding for Marketers
Stage 5B
Account 4
—
C30
Multi-Agent Marketing Crews
Stage 5B
Account 4
—
C31
The Content Flywheel
Stage 5B
Account 4
Account 3
C32
RN-MOS — Your Operating System
Stage 5B
Account 4
Account 1
C32.5
AEO/GEO/Share of Model
Bridge
Account 6
Account 4
C33
Applied AI Proof (Graduation Gate)
Stage 5B
Account 4
Account 6
C36
Enterprise AI Landscape & Buyer Map
Stage 5C
Account 5
—
C37
Identity/Access/Enterprise Authentication
Stage 5C
Account 5
—
C38
Data Governance/Privacy/Sovereignty
Stage 5C
Account 5
—
C39
System Integration (ERPs/CRMs/Data Plane)
Stage 5C
Account 5
—
C40
Enterprise Deployment & Change Management
Stage 5C
Account 5
—
C41
Enterprise AI Governance & Responsible AI
Stage 5C
Account 5
Account 6
C42
Enterprise Engagement Proof (Graduation Gate)
Stage 5C
Account 5
Account 6
C43
VA & Team Onboarding via SOPs
Stage 6
Account 4
Account 5
C44
Community as Moat
Stage 6
Account 1
Account 3
C45
Outbound Outreach
Stage 6
Account 3
Account 5
C46
Ethical Persuasion & ETM
Stage 6
Account 1
Account 3
C47
Group Attention (Webinars/Challenges)
Stage 6
Account 3
Account 2
C48
Retargeting Ecosystems & WAESM
Stage 6
Account 3
Account 4
C49
Crisis Navigation & Reputation
Stage 6
Account 5
Account 1
C50
Executive Command & 85-Minute Cadence
Stage 7
Account 1
Account 5
C51
Trend Surveillance Engine
Stage 7
Account 6
Account 4
C52
Legal, Finance & IP Protection
Stage 7
Account 5
—
C53
IP Productization (Licensing/Cert/White-Label)
Stage 7
Account 5
—
C54
Acquisition or Distribution (Year 10)
Stage 7
Account 1
Account 5
C55
Capstone — Architect of Orchestration
Capstone
Account 1
—
---
Part 5 — Applying the Academy's Own Doctrine to the Account Launch
This is the most important section in the document. Every social account launch should follow the same Pass/Defer/Rework discipline the Academy teaches.
Account 1 (Flagship) Empirical Floor — Apply by Day 90:
1 paying customer at validated price (Stage 1 Harbor bundle, $97 or higher)
Signed testimonial with documented outcome
Refund analysis (even if no refunds requested)
If not met: Defer-Without-Shame. Return to C1–C5 in your own academy and reapply.
Account 2 (AI for 45+) Empirical Floor — Apply by Day 180:
3+ paying customers at Stage 2 Sailboat bundle pricing ($497+)
Documented outcomes in customer's own words
Validated pricing across the ladder
If not met: Don't add Account 3 yet. The funnel isn't ready to duplicate.
Account 3 (Direct Response Architecture) Empirical Floor — Apply by Day 270:
Distribution asset producing ≥30 opt-ins/month at sub-$10 CPO for 3 consecutive months
If not met: This is a Stage 3 failure. The defer protocol: stop Account 4 launch, fix Account 3 first.
Account 4 (AI Infrastructure) Empirical Floor — Apply by Day 360:
Account 4 itself shipping content via the 30-Day Operator-Out-of-Loop Test
1+ Stage 5 sale at $4,997+ AOV
If not met: This is a Stage 5B failure in the academy's own business. Defer Account 5.
Account 5 (Enterprise) Empirical Floor — Apply by Month 18:
1 enterprise engagement signed with all 5 C42 criteria
Reference customer test passed (would they refer Riser Nation to a peer?)
If not met: This is a C42 defer pattern. Most likely cause: account was launched before flagship + Account 4 had sufficient enterprise-trust signals.
Account 6 (AEO/GEO) Empirical Floor — Apply by Month 24:
Riser Nation cited by ChatGPT/Perplexity/Claude for 10+ target queries
Wikidata entities established for at least 5 proprietary frameworks
If not met: Account 6 is the slowest to gate. Allow defer pattern up to Month 30.
---
Part 6 — The Honest Constraints (Updated for the Real Syllabus)
Six structural truths most operators don't plan for:
The flagship cannot be delegated. You on camera is the trust anchor for the entire ladder. Stage 5C buyers ($15K–$50K) and Stage 7 sovereign-tier buyers will stalk Account 1 before they buy anything else. If you outsource the founder voice, the top of the ladder collapses.
Each faceless account needs its own editor with a distinct voice. Account 2 (warm, encouraging, demystifying) is different from Account 4 (technical, demonstrative, ROI-focused) which is different from Account 6 (research-driven, citation-focused). One editor cannot run all four faceless accounts well.
The free Skool/Circle community needs a dedicated community manager from day 1. Not part-time, not "I'll get to it." A neglected free community signals the academy is dead.
You must publish the stage alignment publicly. Every social account should make it clear which Riser Nation stage it serves. "This account teaches Stage 2 — Sailboat. For Stage 5 content, follow @[Account 4 handle]." This is a feature, not a bug — sophisticated buyers respect transparency.
The AOV math must work or the team math doesn't work. At $200 AOV (Stage 1–2), you need ~30 sales/month to fund Stage A operations. At $1,500 AOV (Stage 3–4), 5/month. At $9,997 AOV (Stage 5), 1–2/month. At $15K+ AOV (Stage 5C), 1/quarter justifies the account. Each account's funnel must hit these baselines before adding the next account.
The Module-Page Authoring Standard IS the AEO/GEO moat. Every social post should be feeding citable, schema-ready content into the AI search engines. The academy already does this at the course level via the 12-element Module-Page Standard (Title/Lead/Outcome/Body/Schema/Artifact/Cluster/Video Kit/Lineage/Freshness/Citation Trap/E-E-A-T). Mirror that discipline in social.
---
Part 7 — Sequenced Lead Magnet Production
Build these three first lead magnets before launching anything:
Lead Magnet 1 — Powers Account 1 (Flagship): "The Riser Manifesto + 3-Mismatch Diagnostic"
Lead Magnet 2 — Powers Account 2 (AI for 45+): "The Grand Slam Offer Worksheet (Hormozi Value Equation Applied)"
Source: C6 modules
Production: Fillable PDF + companion 10-day email sequence
Includes: Value Equation calculator, bonus-stacking template, guarantee-writing prompts
Lead Magnet 3 — Powers Account 3 (Direct Response): "The 8-Tier Value Ladder Blueprint + LTV Calculator"
Source: C9 + C16
Production: Interactive web tool (preferred) OR fillable PDF
Includes: 8-tier worksheet, LTV math examples (Marcus the Designer case study), pricing-by-tier rules
Build these in this order. Don't launch Account 1 without #1 ready. Don't launch Account 2 without #2 ready. Don't launch Account 3 without #3 ready.
---
Closing Note
This architecture is not aspirational. It is operationally honest and now correctly grounded in the actual 2026 Master Synthesis Edition syllabus. Six accounts is the maximum a founder + small team can sustain at quality. Seven is where things break.
The discipline is to launch each account only after the prior account has passed its empirical floor — the same Pass/Defer/Rework gates the Academy teaches students. Defer-Without-Shame applies to your own business too.
The syllabus IS the product. The six social accounts are simply different fishing nets in different waters, all reeling into the same harbor.
Build them one at a time. Prove the math at each gate. Then duplicate.
The maritime stage progression is not branding fluff — it is an operational architecture. Honor it in your social strategy and the ladder builds itself.
Complete original Markdown text
# Riser Nation Academy 2026 Master Synthesis Edition
## Social Account Scaling Architecture — Six-Account Map
**Source syllabus:** Riser Nation Academy · 2026 & Beyond · World-Class Course Syllabus · Master Synthesis Edition (May 2026). 52 core courses across 11 stages, 6 graduation gates with empirical proof requirements, Module-Page Authoring Standard with AIO/AEO/GEO baked into every module.
**Doctrine alignment:** Every social account exists to *reduce a specific mismatch* — between what a prospect at a given awareness level expects and what is actually true. The same Reduce Mismatches doctrine that governs course design governs account design.
---
## Part 1 — The Syllabus as a Value Ladder
| Stage | Vessel | Courses | Outcome | Price Range | Buyer Awareness |
|-------|--------|---------|---------|-------------|----------------|
| Pre-Stage | Foundation Doctrine | C1–C3 | Operator identity, pain mining, avatar engineering | Free → $97 | Problem-aware, identity-unsettled |
| Stage 1 | Harbor | C4–C5 | Niche validation + 1 paying customer (Proof of Pulse) | $97–$497 | Solution-aware, hasn't sold yet |
| Stage 2 | Sailboat | C6–C10 | Grand Slam Offer + 8-Tier Value Ladder + 3+ customers (Proof Threshold) | $497–$1,997 | Has offer, needs scale |
| Stage 2.5 | Sales Ops Bridge | C10.5 | DM/Call/No-Call architectures | Bundled with Stage 2 | Has offer, can't close consistently |
| Stage 3 | Speedboat | C11–C14 | Distribution asset (≥30 opt-ins/mo at sub-$10 CPO) | $1,997–$2,997 | Has offer, no traffic |
| Stage 4 | Yacht | C15–C20 | Funnels + LTV + retention + brand architecture | $2,997–$4,997 | Has traffic, needs conversion |
| Stage 5A | Ship — Infrastructure | C21–C27 | Working AI infrastructure (5 capabilities OR shipped Micro-MVO) | $4,997–$9,997 | Wants to BUILD with AI |
| Stage 5B | Ship — Applied AI | C28–C33 | Revenue-producing AI workflow operator-out-of-loop 30 days | $4,997–$9,997 | Wants AI leverage on existing business |
| Stage 5C | Ship — Enterprise AI | C36–C42 | 1 shipped enterprise engagement (250+ employees, signed MSA, Trust Center) | $15,000–$50,000+ | Selling AI services to companies |
| Stage 6 | Fleet | C43–C49 | Team, community, outbound, ethics, retargeting, crisis | $9,997+ continuity tier | Has revenue, scaling team |
| Stage 7 | Harbormaster | C50–C54 | Empire, legacy, Year-10 exit decision | $25,000+ sovereign tier | Building institutional permanence |
| Capstone | C55 | Architect of Orchestration Certification | Bundled at completion | Earned, not bought |
| Tracks | Post-Capstone | 15 specializations | Niche-specific elective tracks | $497–$1,997 each | Specialization seekers |
**Key insight:** A prospect at C5 (Proof of Pulse — needs first customer) and a prospect at C42 (Enterprise Engagement Proof — closing $50K+ deals) are not the same person. They consume different content, on different platforms, at different times of day, with different proof standards. One social account cannot serve both. Six accounts can, when each is tuned to a specific stage band.
---
## Part 2 — The Six Social Account Engines
### ACCOUNT 1 — Founder Flagship: "Late Bloomer"
**Stages served:** Pre-Stage + Stage 1 (Foundation Doctrine + Harbor)
**Source courses:** C1 Harbor Orientation, C2 Pain Excavation, C3 Avatar Engineering, C4 Market Reality, C5 Proof of Pulse
**Avatar:** 45+ first-time builder, identity-unsettled, hasn't sold anything yet
**Awareness:** "Is it too late?" / "Where do I start?"
**Price points fed:** Free PDF → $27–$97 entry → free Skool/Circle community
**Content pillars sourced directly from the syllabus:**
1. **The Riser Manifesto** (C1 M1.1) — Five core beliefs: offers come first, direct response is the engine, AI is the leverage, community is the moat, execution is the religion
2. **The Reduce Mismatches Doctrine** (C1 M1.2) — Three mismatches: expectation vs. reality, readiness vs. action, strategy vs. execution
3. **Identity Before Skill** (C1 M1.3) — Kennedy's "you are the market you become"
4. **Operator vs. Creator Economy** (C1 M1.4) — Operators build owned assets, not rented attention
5. **Schwartz's 5 Awareness Levels** (C2 M2.1) — The spine of direct-response copy
6. **The Empirical Floor Doctrine** (C5 M5.1) — Proof = 1 paying customer, signed testimonial, refund analysis
7. **The Aspirational Threshold Trap** (C5 M5.2) — Stop moving goalposts
8. **Defer-Without-Shame** (C5 M5.5) — Pass/Defer/Rework as doctrine
**AIO queries this account should win** (pulled from syllabus):
- what is riser nation academy
- how do i pivot to digital marketing at 45
- how do i shift my identity from employee to entrepreneur
- how do i know if my business idea is validated
- what is the empirical floor
- what is the aspirational threshold trap
**Platforms:** LinkedIn (primary), Instagram, YouTube long-form
**Production:** You on camera. The flagship is the trust anchor — it cannot be delegated.
**Cadence:** 4 LinkedIn + 4 IG + 1 YouTube long-form per week
**Lead magnet:** "The Riser Manifesto + 3-Mismatch Diagnostic" PDF
**Funnel:** Bio link → PDF opt-in → 5-day email sequence → Operator's Oath video submission → free Builders community → Stage 1 Harbor Bundle ($97)
**Why on-camera matters here:** Your face is the proof that someone over 45 can build something credible. Stage 6 buyers ($15K+) will stalk this account before they buy anything else in the academy. If you outsource the founder voice, the entire top of the ladder collapses.
---
### ACCOUNT 2 — "AI for First-Time Builders 45+" (Faceless)
**Stages served:** Stage 2 + Sales Ops Bridge (Sailboat)
**Source courses:** C6 Grand Slam Offer (Hormozi), C7 Hook-Story-Offer (Brunson), C8 Direct Response Copy (Kennedy + Ogilvy + Hopkins + Cialdini), C9 8-Tier Value Ladder, C10 Proof Threshold, C10.5 Sales Operations
**Avatar:** 45+, has a skill or idea, ready to build their first offer
**Awareness:** Solution-aware, looking for the "how"
**Price points fed:** $497–$1,997 (Stage 2 Sailboat Bundle)
**Content pillars sourced from real syllabus modules:**
1. **The Value Equation** (C6) — More dream, more belief, less time, less work
2. **Bonus Stacking** (C6) — How to engineer "feel stupid saying no" offers
3. **Hook-Story-Offer** (C7) — Brunson's structure for any piece of content
4. **Schwartz's 5 Awareness Levels in copy** (C8) — Match the message to where they are
5. **The 8-Tier Value Ladder** (C9) — Free → entry → core → ascension → premium → continuity → sovereign → legacy
6. **Outcome Documentation Standard** (C10 M10.2) — "$3K in 14 days," not "they loved it"
7. **The Refund-Risk Diagnostic** (C10 M10.3) — Even when no refunds were requested
8. **DM / Call / No-Call decision** (C10.5) — Picking the right sales architecture for the tier
**AIO queries this account should win:**
- how do i create a grand slam offer
- what is hook story offer
- how many customers prove a value ladder works
- how do i document customer outcomes
- what is the proof threshold
- how do i write direct response copy as a beginner
**Platforms:** Instagram Reels, TikTok, YouTube Shorts, LinkedIn carousels
**Production:** Faceless. AI voiceover + screen recordings + b-roll. Delegated to editor.
**Cadence:** 1 short per day, same video native-captioned per platform
**Lead magnet:** "The Grand Slam Offer Worksheet" (pulled from C6 M6.5) + "10 AI Prompts for First-Time Sellers"
**Funnel:** Bio link → worksheet opt-in → 10-day email sequence (one offer-engineering principle per day) → Stage 1 bundle ($97) → Stage 2 Sailboat bundle ($497–$997)
**Why faceless works here:** This avatar is at the bottom of the awareness funnel and intimidated by polished influencers. Faceless removes the comparison ("I'm not like that person") that kills conversions. They want the *answer*.
---
### ACCOUNT 3 — "Direct Response Architecture" (Faceless)
**Stages served:** Stage 3 + Stage 4 (Speedboat + Yacht)
**Source courses:** C11 Dream 100, C12 Skill & Experience Mapping, C13 Faceless YouTube & AI Higgs Field Video Engine, C14 Distribution Proof, C15 Funnel Engine, C16 Customer LTV, C17 Retention & Anti-Extraction, C18 Mid-Funnel Trust, C19 Bottom-Funnel Close & IG, C20 Brand Architecture
**Avatar:** Existing course creator, coach, agency owner plateaued at $5–30K/mo
**Awareness:** Product-aware, knows what a funnel is, frustrated by their ceiling
**Price points fed:** $1,997–$4,997 (Speedboat + Yacht bundles)
**Content pillars sourced from real syllabus modules:**
1. **The Dream 100 for 2026** (C11) — Identifying the 100 people whose audience overlaps yours
2. **The Distribution-Asset Standard** (C14 M14.1) — ≥30 opt-ins/month for ≥3 months at sub-$10 CPO
3. **Activity vs. Asset** (C14 M14.1) — Activity is doing things; asset is producing results
4. **The Faceless YouTube + AI Higgs Field Engine** (C13) — The recurring traffic engine that survives algorithm shifts
5. **Decision Paths, Not Pages** (C15) — Funnels as decision trees, not landing pages
6. **Customer LTV math** (C16) — The Marcus the Designer story ($197 → $612 LTV)
7. **The Anti-Extraction Standard** (C17) — Retention without manipulation
8. **Traceable Attribution Protocol** (C14 M14.2) — UTMs, first-touch, multi-touch
**AIO queries this account should win:**
- how do i know if my content marketing is working
- what is a distribution asset
- how do i measure opt in cost
- what is the dream 100 method
- how do i build a funnel that converts
- how do i calculate customer ltv
**Platforms:** LinkedIn (primary), Instagram, YouTube long-form teardowns
**Production:** Faceless OR voiceover with screen sharing. Delegated to a second editor with different voice from Account 2.
**Cadence:** 4 LinkedIn + 3 IG + 1 YouTube long-form per week
**Lead magnet:** "The 8-Tier Value Ladder Blueprint" PDF (from C9) + Interactive LTV Calculator
**Funnel:** Calculator → personalized email recommendations → $97 workshop → $997 Stage 3 Speedboat course → $2,997 Stage 4 Yacht ascension
**Why this works:** Highest-margin acquisition channel of the six. Audience is pre-qualified — they have revenue, they're frustrated, and they buy solutions. Position content as architecture, not motivation.
---
### ACCOUNT 4 — "AI Infrastructure & Agents" (Faceless)
**Stages served:** Stage 5A + Stage 5B (Ship — Infrastructure + Applied AI)
**Source courses:** C21 AI Foundations, C22 Networks & Protocols, C23 Application Layer (Projects/Skills/Agents/Connectors/Extensions), C24 Prompting at Three Levels, C25 Local Hardware & Self-Hosted AI, C26 Building Tools, C27 Infrastructure Proof, C28 AI Marketing Stack 2026, C29 Vibe Coding for Marketers, C30 Multi-Agent Marketing Crews, C31 Content Flywheel, C32 RN-MOS, C33 Applied AI Proof
**Avatar:** Solopreneur or agency owner at $10–50K/mo, ready to systematize with AI
**Awareness:** Has revenue, has operational chaos, looking for AI leverage
**Price points fed:** $4,997–$9,997 (Stage 5A or 5B bundles)
**Content pillars sourced from real syllabus modules:**
1. **The 5-Capability Standard** (C27 M27.1) — Working API call, deployed MCP connection, authored Claude Skill, public GitHub repo, deployed HF Space or Netlify widget
2. **The Fast-Cash Micro-MVO** (C27 M27.2) — Ship a $47–$97 micro-product in 60 minutes using AI infrastructure
3. **Prompting at Three Levels** (C24) — Tactical, systemic, agentic
4. **Multi-Agent Marketing Crews** (C30) — How agents collaborate
5. **The 30-Day Operator-Out-of-Loop Test** (C33 M33.2) — Walk away for 30 days; does the system still produce revenue?
6. **The Content Flywheel** (C31) — Lean stack vs. Enterprise stack
7. **RN-MOS** (C32) — Your operating system across the entire business
8. **Vibe Coding for Marketers** (C29) — Building tools without becoming an engineer
**AIO queries this account should win:**
- how do i prove my ai infrastructure works
- how do i ship an ai product in 90 minutes
- what is a fast cash micro mvo
- how do i automate my marketing business completely
- what is operator out of the loop automation
- how do i build a multi-agent marketing crew
**Platforms:** YouTube long-form (primary — this audience consumes long technical content), LinkedIn, X/Twitter
**Production:** Voiceover + screen recordings. Delegated to technical editor.
**Cadence:** 2 YouTube long-form per week + 5 LinkedIn posts + daily X
**Lead magnet:** "The 90-Minute Demo Rubric" (from C27) + "5 Ready-to-Deploy AI Marketing Agents"
**Funnel:** Rubric opt-in → "Build Your First AI Agent" mini-course ($27) → Stage 5A Infrastructure bundle ($2,997) → Stage 5B Applied AI bundle ($4,997)
**Why this works:** Audience trusts depth. A 30-minute YouTube teardown converts higher than 30 short-form videos. Positions Riser Nation as operator-grade — the alternative to the "AI hype" crowd.
---
### ACCOUNT 5 — "Enterprise AI for Operators" (Founder + Technical Co-Editor)
**Stage served:** Stage 5C (Ship — Enterprise AI)
**Source courses:** C36 Enterprise AI Landscape & Buyer Map, C37 Identity/Access/Authentication, C38 Data Governance/Privacy/Sovereignty, C39 System Integration (ERPs/CRMs/Data Plane), C40 Enterprise Deployment & Change Management, C41 Enterprise AI Governance, C42 Enterprise Engagement Proof
**Avatar:** Operators selling AI services to companies with 250–50,000 employees
**Awareness:** Has experience selling to SMB, wants to move upmarket; OR enterprise consultants adding AI to their service catalog
**Price points fed:** $15,000–$50,000+ (Stage 5C standalone OR done-with-you continuity at $1,500–$5,000/mo)
**Content pillars sourced from real syllabus modules:**
1. **The Enterprise Engagement Standard** (C42 M42.1) — 5 criteria: signed MSA, SSO/SCIM, Trust Center accepted, governance review, 90-day adoption metric
2. **The Reference Customer Question** (C42 M42.2) — Would this client refer Riser Nation to a peer?
3. **Identity, Access & Enterprise Authentication** (C37) — SSO, SCIM, RBAC for AI deployments
4. **Data Governance & Sovereignty** (C38) — How enterprise data residency requirements shape AI architecture
5. **The Buyer Map for Enterprise AI** (C36) — Champion, economic buyer, IT/security gatekeeper, end users
6. **Change Management for AI Adoption** (C40) — Why most enterprise AI pilots die
7. **Responsible AI Governance** (C41) — Risk frameworks, model evaluation, ongoing review
**AIO queries this account should win:**
- how do i prove an enterprise ai engagement
- what makes a deal enterprise vs smb
- what is a reference customer in enterprise ai
- how do i close enterprise ai deals
- what is sso scim for enterprise ai
- how do i handle ai data governance for enterprise
**Platforms:** LinkedIn (primary — this is where enterprise buyers live), X/Twitter (secondary), niche podcast appearances, technical case-study blog
**Production:** Hybrid — you on-camera for trust signals (founder POV), technical co-editor for case-study breakdowns. This account benefits from your face because enterprise buyers buy trust before product.
**Cadence:** 5 LinkedIn + 2 X + 1 long-form case study per week + 1 podcast appearance per month
**Lead magnet:** "The Enterprise Engagement Checklist" (from C42) + "The SMB-to-Enterprise Buyer Map" PDF
**Funnel:** Checklist opt-in → invitation to monthly Enterprise AI roundtable (Zoom, free) → application for Stage 5C bundle ($15K) OR done-with-you partnership
**Why this gets its own account:** Stage 5C is the highest-margin block in the entire Academy. Enterprise buyers will not respond to content optimized for $97 buyers and vice versa. Different platforms, different language, different proof standards, different sales cycle (3–9 months, not 3 days). It deserves its own dedicated channel from day one.
**Honest caveat:** This account ramps slowest. Don't measure it against the others. One $15K close per quarter justifies the entire account.
---
### ACCOUNT 6 — "AEO/GEO Search Visibility" (Faceless)
**Stages served:** The discoverability layer that runs through the entire syllabus + Stage 7 specialization tracks
**Source courses:** C32.5 AEO / GEO / Share of Model, C51 Trend Surveillance Engine, the Module-Page Authoring Standard documented across all 52 courses
**Avatar:** Marketers, agency owners, content creators with existing SEO programs nervous about AI search shifting their traffic
**Awareness:** Sophisticated, understands SEO, watching traffic shift to ChatGPT/Perplexity/Claude
**Price points fed:** $4,997–$25,000 (C32.5 dedicated course + Stage 7 specialization tracks + done-with-you continuity)
**Content pillars sourced from real syllabus modules:**
1. **The Module-Page Authoring Standard** (academy-wide) — Every page ships as an AI-citable answer page
2. **Title + Lead + Outcome + Body + Schema** (academy-wide) — The 12-element citation-ready format
3. **Citation Trap** (academy-wide) — Named proprietary frameworks with primary-source definitions
4. **AIO queries** — How to identify the questions buyers ask AI engines
5. **AEO direct-answer blocks** — Definition, How-To, Comparison, FAQ, Framework formats
6. **GEO authority signal stacking** — Wikidata entities, founder Person schema, podcast appearances, expert quotes
7. **Share of Model (SoM)** — The C32.5 framework for measuring AI citation share
8. **Quarterly Freshness Triggers** (C51 Trend Surveillance Engine) — When content needs to be refreshed
**AIO queries this account should win:**
- what is aeo answer engine optimization
- what is geo generative engine optimization
- how do i get cited by chatgpt
- what is share of model
- how do i optimize for ai search
- what is the module page authoring standard
**Platforms:** LinkedIn (primary), X/Twitter (active discussion), YouTube long-form teardowns, technical blog
**Production:** Voiceover + screen sharing. Delegated to most technical editor on your team.
**Cadence:** 3 LinkedIn + daily X + 1 YouTube long-form per week
**Lead magnet:** "The 10-Query AI Search Audit Tool" + "Module-Page Authoring Checklist" PDF
**Funnel:** Audit → $197 AEO workshop → C32.5 course ($2,997) → done-with-you continuity ($1,500/mo) → Stage 7 specialization tracks
**Why this works:** Smallest target audience of the six, but highest LTV per acquisition. Buyers in this niche readily pay $5K+ and have $25K+ done-with-you budgets. This account converts to the top of your ladder.
---
### THE UNIFYING MIDDLE — Free Skool/Circle Community
**Not a social account but the most important asset in the architecture.**
Every one of the 6 social accounts funnels into this free community. It is where lurkers become buyers and where graduation gates (C5, C10, C14, C27, C33, C42) get celebrated publicly with member proof artifacts (signed Manifestos, Outcome Documentations, 90-Minute Demo recordings, Enterprise Engagement Checklists).
The free community is what makes the 6-account architecture financially viable. Without it, you are acquiring leads you cannot follow up with at scale.
**Operational architecture:**
- Free tier: Skool or Circle (free plan)
- Mid tier: Paid Circle continuity (already in use)
- Top tier: Stage 6 Fleet community (C44 Community as Moat module is the playbook)
---
## Part 3 — The Highway Scaling Sequence
### Stage A — Months 1–3: Foundation Launch
**Active accounts:** Account 1 (Flagship) + Account 2 (AI for 45+) + Free Skool community
**Syllabus stages served:** Pre-Stage through Stage 2 (C1–C10)
**Goal:** Prove the funnel converts before duplicating it
**Why this sequence:** If your flagship + one faceless account + free community can't generate consistent email opt-ins and Stage 1–2 sales, adding more accounts will only multiply the failure. Your own academy must clear its own Stage 1 (Proof of Pulse — 1 paying customer) and Stage 2 (Proof Threshold — 3+ customers) before you scale into Stage 3 distribution.
**Empirical floor for this stage (apply the academy's own doctrine to your business):**
- 200+ email opt-ins per week consistently for 3 months
- 30%+ join free community within 14 days of opt-in
- 1+ paying customer in week 1 (Proof of Pulse for your launch)
- 3+ paying customers by month 3 (Proof Threshold)
**Team:** You + 1 editor (15–20 hrs/week) + 1 part-time community manager
**Monthly operational cost:** $2,500–4,500
### Stage B — Months 4–6: Add Direct Response Lane
**New account launched:** Account 3 (Direct Response Architecture)
**Syllabus stages served:** Stage 3 + Stage 4 (C11–C20)
**Goal:** Pass Stage 3 graduation gate (Distribution Proof) for the Academy's own marketing
**Why this account next:** Targets a completely different avatar (existing creators with revenue) at a higher price point. Doesn't compete with Account 1+2 for attention.
**Critical AOV inflection:** Stage 1–2 buyers average ~$200 AOV. Stage 3–4 buyers average ~$1,500 AOV. Same operational cost, much higher revenue per acquisition.
**Empirical floor for this stage:**
- Account 3 distribution asset hitting ≥30 opt-ins/month at sub-$10 CPO within 60 days (the academy's own C14 standard applied to itself)
- Blended AOV across all accounts exceeds $400
**Team additions:** +1 editor (Account 3 uses different content style — more whiteboard/teardown). Total: you + 2 editors + community manager.
**Monthly operational cost:** $4,500–7,000
### Stage C — Months 7–9: Add AI Infrastructure Lane
**New account launched:** Account 4 (AI Infrastructure & Agents)
**Syllabus stages served:** Stage 5A + Stage 5B (C21–C33)
**Goal:** Pass Stage 5A and 5B gates internally (Infrastructure Proof + Applied AI Proof)
**Why third:** Your Stage 5 courses ($4,997–$9,997) need Accounts 1–3 already populating ascension demand before higher-ticket offers have a populated audience to convert.
**Empirical floor for this stage:**
- 30-day operator-out-of-loop test passing on Account 1, 2, 3 content production (using your own academy's C33 standard)
- 1+ Stage 5A or 5B sale at $4,997+ AOV
**Team additions:** +1 technical editor or contractor for agent demos. Total: you + 3 editors + community manager + part-time tech.
**Monthly operational cost:** $7,000–11,000
### Stage D — Months 10–14: Add Enterprise Lane
**New account launched:** Account 5 (Enterprise AI for Operators)
**Syllabus stage served:** Stage 5C (C36–C42)
**Goal:** First enterprise engagement (Stage 5C graduation for the Academy itself)
**Why now and not later:** Enterprise sales cycles are 3–9 months. If you wait until Month 18 to launch this account, your first enterprise close lands at Month 24+. Start the funnel filling in Month 10, expect first close around Month 16–20.
**Empirical floor for this stage:**
- 1 enterprise engagement signed with all 5 criteria (signed MSA, SSO/SCIM, Trust Center, governance, 90-day adoption) within 9 months of account launch
- This is the academy's own C42 graduation gate
**Team additions:** Content director to oversee all accounts. You shift to strategic oversight + Account 5 founder voice. Total: you (strategic + Account 5) + content director + 3 editors + community manager + part-time tech.
**Monthly operational cost:** $11,000–18,000
### Stage E — Months 15–18: Add AEO/GEO Lane
**New account launched:** Account 6 (AEO/GEO Search Visibility)
**Syllabus served:** C32.5 + C51 + academy-wide Module-Page Authoring Standard
**Goal:** Establish Riser Nation as the cited source for AEO/GEO in the AI marketing space
**Why last:** This account requires 12+ months of citation-ready content already published across the other 5 accounts to have proof of method. You can't credibly teach AEO if you haven't won AEO citations yourself first.
**Empirical floor for this stage:**
- Riser Nation cited in ChatGPT/Perplexity/Claude responses for ≥10 target queries within 6 months of Account 6 launch
- Wikidata entity for Riser Nation Empirical Floor Doctrine + Reduce Mismatches Doctrine established
**Team additions:** Add a specialist AEO/GEO content producer. Total: you (strategic) + content director + 4 editors + community manager + part-time tech + AEO specialist.
**Monthly operational cost:** $15,000–22,000
### Stage F — Year 2+: Full Armada Operating at Scale
**All 6 accounts running + Free community + Paid Circle continuity + Stage 7 sovereign tier**
**Revenue mix at Year 2 (realistic estimate):**
| Account | % of Customer Volume | % of Revenue |
|---------|---------------------|--------------|
| Account 1 (Stage 1) | 45% | 6% |
| Account 2 (Stage 2) | 28% | 12% |
| Account 3 (Stage 3–4) | 18% | 30% |
| Account 4 (Stage 5A/B) | 6% | 22% |
| Account 5 (Stage 5C) | 1.5% | 20% |
| Account 6 (AEO/GEO + Stage 7) | 1.5% | 10% |
**The honest math:** The top 3% of your customer base (Stage 5C + Stage 7 buyers) generates 30% of revenue. The top 10% generates 52%. This is exactly why a 6-account architecture is worth the operational complexity — the high end of your ladder requires its own dedicated acquisition channels.
---
## Part 4 — Course-to-Account Cross-Reference (All 52 Courses)
| Course | Title | Stage | Primary Account | Secondary |
|--------|-------|-------|----------------|-----------|
| C1 | Harbor Orientation & Riser Manifesto | Pre-Stage | Account 1 | — |
| C2 | Pain Excavation & Semantic Foundation | Pre-Stage | Account 1 | Account 3 |
| C3 | Avatar Engineering (100-Avatar Method) | Pre-Stage | Account 1 | Account 3 |
| C4 | Market Reality & Niche Validation | Stage 1 | Account 1 | Account 2 |
| C5 | Proof of Pulse (Graduation Gate) | Stage 1 | Account 1 | Account 6 |
| C6 | The Grand Slam Offer (Hormozi) | Stage 2 | Account 2 | Account 3 |
| C7 | Hook-Story-Offer (Brunson) | Stage 2 | Account 2 | Account 3 |
| C8 | Direct Response Copy (Kennedy/Ogilvy/Hopkins/Cialdini) | Stage 2 | Account 2 | Account 3 |
| C9 | The 8-Tier Value Ladder | Stage 2 | Account 3 | Account 2 |
| C10 | Proof Threshold (Graduation Gate) | Stage 2 | Account 2 | Account 6 |
| C10.5 | Sales Operations (DM/Call/No-Call) | Bridge | Account 2 | Account 3 |
| C11 | Direction Clarity & Dream 100 (2026) | Stage 3 | Account 3 | — |
| C12 | Skill & Experience Mapping for Content | Stage 3 | Account 3 | Account 1 |
| C13 | Faceless YouTube & AI Higgs Field Engine | Stage 3 | Account 2 | Account 3 |
| C14 | Distribution Proof (Graduation Gate) | Stage 3 | Account 3 | Account 6 |
| C15 | Funnel Engine — Decision Paths | Stage 4 | Account 3 | — |
| C16 | Customer LTV & Measurement Discipline | Stage 4 | Account 3 | Account 4 |
| C17 | Retention & Anti-Extraction Standard | Stage 4 | Account 3 | — |
| C18 | Mid-Funnel Trust & YouTube Authority | Stage 4 | Account 3 | Account 4 |
| C19 | Bottom-Funnel Close & IG Growth | Stage 4 | Account 3 | Account 2 |
| C20 | Brand Architecture & Visual Style | Stage 4 | Account 3 | Account 1 |
| C21 | AI Foundations — Models/Modalities/Brain | Stage 5A | Account 4 | — |
| C22 | Networks & Protocols — The Nervous System | Stage 5A | Account 4 | — |
| C23 | Application Layer (Projects/Skills/Agents) | Stage 5A | Account 4 | — |
| C24 | Prompting at Three Levels | Stage 5A | Account 4 | Account 2 |
| C25 | Local Hardware & Self-Hosted AI | Stage 5A | Account 4 | — |
| C26 | Building Tools (Repos/Widgets/Apps) | Stage 5A | Account 4 | — |
| C27 | Infrastructure Proof (Graduation Gate) | Stage 5A | Account 4 | Account 6 |
| C28 | AI Marketing Stack 2026 | Stage 5B | Account 4 | Account 3 |
| C29 | Vibe Coding for Marketers | Stage 5B | Account 4 | — |
| C30 | Multi-Agent Marketing Crews | Stage 5B | Account 4 | — |
| C31 | The Content Flywheel | Stage 5B | Account 4 | Account 3 |
| C32 | RN-MOS — Your Operating System | Stage 5B | Account 4 | Account 1 |
| C32.5 | AEO/GEO/Share of Model | Bridge | Account 6 | Account 4 |
| C33 | Applied AI Proof (Graduation Gate) | Stage 5B | Account 4 | Account 6 |
| C36 | Enterprise AI Landscape & Buyer Map | Stage 5C | Account 5 | — |
| C37 | Identity/Access/Enterprise Authentication | Stage 5C | Account 5 | — |
| C38 | Data Governance/Privacy/Sovereignty | Stage 5C | Account 5 | — |
| C39 | System Integration (ERPs/CRMs/Data Plane) | Stage 5C | Account 5 | — |
| C40 | Enterprise Deployment & Change Management | Stage 5C | Account 5 | — |
| C41 | Enterprise AI Governance & Responsible AI | Stage 5C | Account 5 | Account 6 |
| C42 | Enterprise Engagement Proof (Graduation Gate) | Stage 5C | Account 5 | Account 6 |
| C43 | VA & Team Onboarding via SOPs | Stage 6 | Account 4 | Account 5 |
| C44 | Community as Moat | Stage 6 | Account 1 | Account 3 |
| C45 | Outbound Outreach | Stage 6 | Account 3 | Account 5 |
| C46 | Ethical Persuasion & ETM | Stage 6 | Account 1 | Account 3 |
| C47 | Group Attention (Webinars/Challenges) | Stage 6 | Account 3 | Account 2 |
| C48 | Retargeting Ecosystems & WAESM | Stage 6 | Account 3 | Account 4 |
| C49 | Crisis Navigation & Reputation | Stage 6 | Account 5 | Account 1 |
| C50 | Executive Command & 85-Minute Cadence | Stage 7 | Account 1 | Account 5 |
| C51 | Trend Surveillance Engine | Stage 7 | Account 6 | Account 4 |
| C52 | Legal, Finance & IP Protection | Stage 7 | Account 5 | — |
| C53 | IP Productization (Licensing/Cert/White-Label) | Stage 7 | Account 5 | — |
| C54 | Acquisition or Distribution (Year 10) | Stage 7 | Account 1 | Account 5 |
| C55 | Capstone — Architect of Orchestration | Capstone | Account 1 | — |
---
## Part 5 — Applying the Academy's Own Doctrine to the Account Launch
This is the most important section in the document. Every social account launch should follow the same Pass/Defer/Rework discipline the Academy teaches.
**Account 1 (Flagship) Empirical Floor — Apply by Day 90:**
- 1 paying customer at validated price (Stage 1 Harbor bundle, $97 or higher)
- Signed testimonial with documented outcome
- Refund analysis (even if no refunds requested)
- If not met: Defer-Without-Shame. Return to C1–C5 in your own academy and reapply.
**Account 2 (AI for 45+) Empirical Floor — Apply by Day 180:**
- 3+ paying customers at Stage 2 Sailboat bundle pricing ($497+)
- Documented outcomes in customer's own words
- Validated pricing across the ladder
- If not met: Don't add Account 3 yet. The funnel isn't ready to duplicate.
**Account 3 (Direct Response Architecture) Empirical Floor — Apply by Day 270:**
- Distribution asset producing ≥30 opt-ins/month at sub-$10 CPO for 3 consecutive months
- Traceable attribution (UTM convention, first-touch documented)
- If not met: This is a Stage 3 failure. The defer protocol: stop Account 4 launch, fix Account 3 first.
**Account 4 (AI Infrastructure) Empirical Floor — Apply by Day 360:**
- Account 4 itself shipping content via the 30-Day Operator-Out-of-Loop Test
- 1+ Stage 5 sale at $4,997+ AOV
- If not met: This is a Stage 5B failure in the academy's own business. Defer Account 5.
**Account 5 (Enterprise) Empirical Floor — Apply by Month 18:**
- 1 enterprise engagement signed with all 5 C42 criteria
- Reference customer test passed (would they refer Riser Nation to a peer?)
- If not met: This is a C42 defer pattern. Most likely cause: account was launched before flagship + Account 4 had sufficient enterprise-trust signals.
**Account 6 (AEO/GEO) Empirical Floor — Apply by Month 24:**
- Riser Nation cited by ChatGPT/Perplexity/Claude for 10+ target queries
- Wikidata entities established for at least 5 proprietary frameworks
- If not met: Account 6 is the slowest to gate. Allow defer pattern up to Month 30.
---
## Part 6 — The Honest Constraints (Updated for the Real Syllabus)
**Six structural truths most operators don't plan for:**
1. **The flagship cannot be delegated.** You on camera is the trust anchor for the entire ladder. Stage 5C buyers ($15K–$50K) and Stage 7 sovereign-tier buyers will stalk Account 1 before they buy anything else. If you outsource the founder voice, the top of the ladder collapses.
2. **Each faceless account needs its own editor with a distinct voice.** Account 2 (warm, encouraging, demystifying) is different from Account 4 (technical, demonstrative, ROI-focused) which is different from Account 6 (research-driven, citation-focused). One editor cannot run all four faceless accounts well.
3. **The free Skool/Circle community needs a dedicated community manager from day 1.** Not part-time, not "I'll get to it." A neglected free community signals the academy is dead.
4. **You must publish the stage alignment publicly.** Every social account should make it clear which Riser Nation stage it serves. "This account teaches Stage 2 — Sailboat. For Stage 5 content, follow @[Account 4 handle]." This is a feature, not a bug — sophisticated buyers respect transparency.
5. **The AOV math must work or the team math doesn't work.** At $200 AOV (Stage 1–2), you need ~30 sales/month to fund Stage A operations. At $1,500 AOV (Stage 3–4), 5/month. At $9,997 AOV (Stage 5), 1–2/month. At $15K+ AOV (Stage 5C), 1/quarter justifies the account. Each account's funnel must hit these baselines before adding the next account.
6. **The Module-Page Authoring Standard IS the AEO/GEO moat.** Every social post should be feeding citable, schema-ready content into the AI search engines. The academy already does this at the course level via the 12-element Module-Page Standard (Title/Lead/Outcome/Body/Schema/Artifact/Cluster/Video Kit/Lineage/Freshness/Citation Trap/E-E-A-T). Mirror that discipline in social.
---
## Part 7 — Sequenced Lead Magnet Production
Build these three first lead magnets before launching anything:
**Lead Magnet 1 — Powers Account 1 (Flagship):**
"The Riser Manifesto + 3-Mismatch Diagnostic"
- Source: C1 M1.1 + C1 M1.2
- Production: Free PDF, branded, 8–12 pages
- Includes: signed-Manifesto template, Operator's Oath script, 3-Mismatch Diagnostic worksheet
**Lead Magnet 2 — Powers Account 2 (AI for 45+):**
"The Grand Slam Offer Worksheet (Hormozi Value Equation Applied)"
- Source: C6 modules
- Production: Fillable PDF + companion 10-day email sequence
- Includes: Value Equation calculator, bonus-stacking template, guarantee-writing prompts
**Lead Magnet 3 — Powers Account 3 (Direct Response):**
"The 8-Tier Value Ladder Blueprint + LTV Calculator"
- Source: C9 + C16
- Production: Interactive web tool (preferred) OR fillable PDF
- Includes: 8-tier worksheet, LTV math examples (Marcus the Designer case study), pricing-by-tier rules
Build these in this order. Don't launch Account 1 without #1 ready. Don't launch Account 2 without #2 ready. Don't launch Account 3 without #3 ready.
---
## Closing Note
This architecture is not aspirational. It is operationally honest and now correctly grounded in the actual 2026 Master Synthesis Edition syllabus. Six accounts is the maximum a founder + small team can sustain at quality. Seven is where things break.
The discipline is to launch each account only after the prior account has passed its empirical floor — the same Pass/Defer/Rework gates the Academy teaches students. Defer-Without-Shame applies to your own business too.
The syllabus IS the product. The six social accounts are simply different fishing nets in different waters, all reeling into the same harbor.
Build them one at a time. Prove the math at each gate. Then duplicate.
The maritime stage progression is not branding fluff — it is an operational architecture. Honor it in your social strategy and the ladder builds itself.
Social Account Scaling Architecture — Aligned to the Real Syllabus
Source syllabus: Riser Nation Academy 2026 Sovereign Edition — 55 courses, ~360 modules, maritime stage progression, graduation gates at C5/C10/C14/C27/C33/C42, AIO/AEO/GEO discoverability baked into every module.
The thesis: Your maritime stage progression (Dinghy → Sailboat → Speedboat → Yacht → Mega Yacht → Bora Bora Cruise Ship) is already a value ladder. Each stage has a different avatar at a different awareness level paying a different price point. Therefore each stage needs its own dedicated social content engine. Five accounts. One ladder. Six progressively-priced outcomes.
---
Part 1 — The Syllabus as a Value Ladder
Stage
Vessel
Courses
Outcome
Price Range
Awareness Level
1
Dinghy
C1–C5
Operator identity + market selection
Free → $97
Problem-aware, doesn't know where to start
2
Sailboat
C6–C10
Buyer intel + first offer + funnel
$497–$997
Solution-aware, has an idea
3
Speedboat
C11–C14
Traffic + content + first revenue
$997–$1,997
Has offer, needs customers
4
Yacht
C15–C27
Persuasion + automation + scale
$1,997–$4,997
Has revenue, needs systems
5
Mega Yacht
C28–C42
AI infrastructure + sovereignty
$4,997–$15,000
Has business, needs leverage
6
Bora Bora Cruise Ship
C43–C55
Legacy + governance + sovereign command
$15,000–$50,000+
Has scale, building permanence
The critical insight most academy operators miss: A buyer at C1 (Harbor Orientation) and a buyer at C43 (Sovereign Operator Command) are not the same person. They speak different languages, consume content on different platforms, respond to different proofs, and convert at different price points. One social account cannot serve both. Five social accounts, each tuned to a specific stage band, can.
---
Part 2 — The Five Social Account Engines
ACCOUNT 1 — "Late Bloomer" Founder Flagship
Stage served: Pre-Stage + Stage 1 (Dinghy, C1–C5) Avatar: 45+ first-time builder, problem-aware, hasn't bought anything yet Awareness: "Is it too late for me?" / "Where do I even start?" Price points fed: Free PDF → $27–$97 entry → free Skool/Circle community
C2: Buoy Navigation — Market radar basics, how to read demand
C3: Casting the Nets — First-offer principles
C4: The Commercial Fleet — Traffic fundamentals (intro level)
C5: Funnel Harbors — Conversion architecture basics (this is a graduation gate course; teach the *concepts*, not the implementation)
Content pillars (rotate weekly):
Riser Manifesto / operator identity
"It's not too late" — proof and philosophy
The "Reduce Mismatches" doctrine in plain language
Founder behind-the-scenes building the academy
Origin stories from members (with permission)
Platforms: LinkedIn (primary), Instagram, YouTube long-form Production: You on camera. Cannot be delegated. Cadence: 4 LinkedIn + 4 IG + 1 YouTube long-form per week
Lead magnet: "The Riser Manifesto + 5-Rung Value Ladder Blueprint" PDF Funnel: Bio link → PDF opt-in → 5-day email nurture → free Builders community → C1–C5 Stage 1 Foundation Bundle ($97)
Why on-camera matters here: Your face is the proof that someone over 45 can build something credible. The flagship account doesn't sell a course — it sells permission.
---
ACCOUNT 2 — "AI for First-Time Builders 45+" (Faceless)
Stage served: Stage 2 (Sailboat, C6–C10) Avatar: 45+, has a skill or idea, ready to build their first offer Awareness: Solution-aware, looking for "how" Price points fed: $497–$997 (individual Stage 2 courses or the Sailboat bundle)
Content sourced from these courses:
C6: Email Harbor Systems — Email list-building for beginners
C7: Offer Fleet Expansion — Value ladder construction (simplified)
"Try this AI prompt today" — single-tool, single-outcome demos
"I'm 55 and I just figured out..." — relatable framing
Pricing psychology for first-time sellers
Email list-building basics
Funnel anatomy explainers (60-second teardowns)
Platforms: Instagram Reels, TikTok, YouTube Shorts, LinkedIn carousels Production: Faceless. AI voiceover + screen recordings + b-roll. Delegated to editor. Cadence: 1 short per day, same video native-captioned per platform
Lead magnet: "10 AI Prompts for First-Time Business Builders" (from your AI Prompts Directory) Funnel: Bio link → prompt pack → 10-day email sequence (one prompt per day) → Stage 1 bundle ($97) OR direct Stage 2 Sailboat bundle ($497)
Why faceless works here: This avatar is at the bottom of the awareness funnel. The faceless format removes the comparison ("I'm not like that person on camera") that kills conversion. They want the *answer*, not the influencer.
Why this works: Highest-margin acquisition channel of the five. Audience is pre-qualified — they have revenue, are frustrated, and buy solutions. Position as architecture, not motivation.
---
ACCOUNT 4 — "AI Agents & Custom GPTs" (Faceless)
Stage served: Stage 5 (Mega Yacht, C28–C42) Avatar: Solopreneur or agency owner at $10–50K/mo, ready to systematize with AI Awareness: Has revenue, has operational chaos, looking for leverage Price points fed: $2,997–$9,997 (Stage 5 AI Command Fleet courses)
Content sourced from these courses:
C26: Agentic Crew Systems — AI workforce infrastructure
C27: Autonomous AI Ships — Self-operating business systems (graduation gate)
C28: AI Shipyards — Building AI products & tools
C29: Knowledge Ocean Mapping — AI knowledge systems
C30: Strategic Ocean Navigation — AI strategy & decision systems
C31: Content Fishing Net Factories — AI content production
C32: Global Shipping Lanes — Content distribution networks
C36: Fleet Operations Command — Scaling digital enterprises
Content pillars:
"Built this agent in 20 minutes" speed demos
AI Employee Framework walkthroughs
Agent ecosystem teardowns
Custom GPT vs. Agent vs. Chatbot decision frameworks
Real ROI case studies (hours saved, revenue per agent)
Platforms: YouTube long-form (primary — this audience consumes long technical content), LinkedIn, X/Twitter Production: Voiceover + screen recordings. Delegated to technical editor. Cadence: 2 YouTube long-form per week + 5 LinkedIn posts + daily X
Lead magnet: "5 Ready-to-Deploy AI Employee Templates" + a custom GPT they can clone immediately Funnel: Template opt-in → "Build Your First AI Employee" mini-course ($27) → C26–C30 Mega Yacht bundle ($2,997) → Stage 5 full ascension ($9,997)
Why this works: Audience trusts depth. A 30-minute YouTube teardown converts higher than 30 short-form videos. Positions Riser Nation as the operator-grade alternative to "AI hype" content.
Stage served: Stage 5–6 specialty tracks (the AIO/AEO/GEO discoverability layer baked into every Sovereign Edition course) Avatar: Marketers, agency owners, content creators with existing SEO programs nervous about AI search Awareness: Sophisticated. Understands SEO. Watching traffic shift to AI engines. Price points fed: $4,997–$25,000 (Stage 6 sovereign tier + done-with-you continuity)
Content sourced from these courses:
The AIO/AEO/GEO layer documented across the entire syllabus (every course ships FAQ-schema-ready Q&A pairs, citable definition blocks, entity-authority stacking)
C43: Sovereign Operator Command
C44: Legacy Fleet Architecture
C49: Digital Ocean Governance
Content pillars:
"What ChatGPT cites vs. what Google ranks" comparisons
Schema.org markup tutorials
AEO direct-answer block construction
GEO entity-authority signal stacking (Wikidata, podcast appearances, expert quotes)
AI search demos and audits
Platforms: LinkedIn (primary), X/Twitter, YouTube long-form, technical blog Production: Voiceover + screen sharing. Delegated to most technical editor. Cadence: 3 LinkedIn + daily X + 1 YouTube long-form per week
Lead magnet: "AEO Audit Tool" or "10 Queries Your Business Should Win in AI Search" Funnel: Audit → $197 workshop → $2,997 AEO/GEO implementation course → $1,500/mo done-with-you continuity → Stage 6 sovereign tier
Why this works: Smallest target audience of the five, but highest-converting and highest-LTV. These buyers pay $5K+ readily. This account feeds your top-of-ladder offers.
---
THE UNIFYING MIDDLE — Free Skool/Circle Community
Not a social account but the most important asset in the architecture.
Every one of the 5 social accounts funnels into this free community. It is where lurkers become buyers. It is where graduation gates (C5, C10, C14, C27, C33, C42) get celebrated publicly, where member wins get amplified, and where the academy's culture is forged.
Without this asset, you are acquiring leads you cannot follow up with at scale. The free community is what makes the 5-account architecture financially viable.
---
Part 3 — The Highway Scaling Sequence
This is where most academy operators fail. They try to launch 5 accounts at once, exhaust themselves, and produce mediocre content across the board. Here is the actual sequence aligned to your syllabus rollout:
Stage A — Months 1–3 (Single Lane)
Active accounts: Flagship (Account 1) + AI for 45+ (Account 2) + Free Skool community Stage served: Pre-Stage through C10 (Dinghy + Sailboat) Goal: Prove the funnel converts before duplicating it
Why this sequence: If your flagship + one faceless account + free community can't generate consistent email opt-ins and Stage 1–2 sales, adding more accounts will only multiply the failure. The Stage 1 of your own business has to work before you can teach Stage 1 to others.
Success metrics:
200+ email opt-ins/week consistently
30% join free community
3–5% buy a Stage 1 or Stage 2 product within 30 days
Team: You + 1 editor (15–20 hrs/week) + 1 part-time community manager Monthly operational cost: $2,500–4,500
Stage B — Months 4–6 (Add Lane 2)
New account launched: Value Ladder Architecture (Account 3) Stage served: C11–C20 (Speedboat + early Yacht)
Why this account next: Targets a completely different avatar (existing creators with revenue) at a higher price point. Doesn't compete with Account 1+2 for attention.
Critical moment: Your average order value should roughly double here. Stage 1–2 buyers average ~$200 AOV. Stage 3–4 buyers average ~$1,500 AOV. Same operational cost, much higher revenue per acquisition.
Team additions: +1 editor (Account 3 uses different content style — more whiteboard/teardown). Total: you + 2 editors + community manager. Monthly operational cost: $4,500–7,000
Stage C — Months 7–9 (Add Lane 3)
New account launched: AI Agents & Custom GPTs (Account 4) Stage served: C21–C42 (full Yacht + Mega Yacht)
Why third: Your Phase 5 Mega Yacht courses ($2,997+) need Accounts 1–3 already populating ascension demand before higher-ticket Phase 5 offers have a populated audience to convert.
Team additions: +1 technical editor or contractor for agent demos. Total: you + 3 editors + community manager + part-time tech. Monthly operational cost: $7,000–11,000
Stage D — Months 10–12 (Add Lane 4)
New account launched: AEO/GEO (Account 5) Stage served: C43–C55 (Bora Bora Cruise Ship + Sovereign Operator)
Why last: Smallest audience, most sophisticated, highest-ticket. By month 10 you have 9 months of content, data, and case studies for proof in this technical niche. Revenue from Accounts 1–4 funds the slower ramp of Account 5.
Critical strategic note: Account 5 is the gateway to your Stage 6 offers ($15K–$50K+). Conversion volume is low but revenue per conversion is dramatically higher. Don't measure this account by the same metrics as Accounts 1–4.
Team additions: Content director to oversee all 5 accounts. You shift to strategic oversight. Total: you (strategic) + content director + 3–4 editors + community manager + part-time tech. Monthly operational cost: $11,000–16,000
Stage E — Year 2 (Full Armada)
All 5 accounts running + Free Skool community + paid Circle continuityStage served: All 6 maritime stages, full value ladder operational
Revenue mix at Year 2 (realistic estimate):
Account 1 (Stage 1 buyers): 40% of customer volume, 8% of revenue
Account 2 (Stage 2 buyers): 30% of volume, 15% of revenue
Account 3 (Stage 3–4 buyers): 20% of volume, 35% of revenue
Account 4 (Stage 5 buyers): 8% of volume, 27% of revenue
Account 5 (Stage 6 buyers): 2% of volume, 15% of revenue
The math is brutal and honest: the top 2% of your customer base (Stage 6) generates 15% of your revenue. The top 10% (Stage 4–6) generates 77%. This is exactly why scaling 5 accounts is worth the operational complexity — the high-end of your ladder requires its own dedicated acquisition channel.
---
Part 4 — The Maritime Stage × Content Pillar Cross-Reference
For each Riser Nation course, here's which social account should mine it for content:
Course
Stage
Account #
Content Type
C1 Harbor Orientation
1
Account 1
Founder philosophy, manifesto
C2 Buoy Navigation
1
Account 1 + 2
Market reading basics
C3 Casting the Nets
1
Account 2
First offer creation
C4 The Commercial Fleet
1
Account 2
Traffic intro
C5 Funnel Harbors
1
Account 1 + 3
Conversion concepts (gate)
C6 Email Harbor Systems
2
Account 2 + 3
Email infrastructure
C7 Offer Fleet Expansion
2
Account 3
Value ladder engineering
C8 Paid Traffic Armadas
2
Account 3
Paid traffic systems
C9 Bora Bora Retreat
2
Account 1
Strategic clarity rituals
C10 Funnel Fleet Engineering
2
Account 3
Funnel architecture (gate)
C11 Podcast Broadcasting Fleet
3
Account 3
Authority voice
C12 Video Authority Ships
3
Account 3
Visual influence
C13 Offer Fleet Expansion (advanced)
3
Account 3
Advanced ladder
C14 Funnel Fleet Engineering (advanced)
3
Account 3
Advanced conversion (gate)
C15 Automation Fleet Systems
4
Account 3 + 4
Marketing automation
C16 AI Captain Systems
4
Account 4
AI operations
C17 Data Sonar Systems
4
Account 4
Analytics
C18 Partnership Harbors
4
Account 3 + 5
Strategic alliances
C19 Community Fishing Villages
4
Account 3
Audience ecosystems
C20 Brand Flagship Ships
4
Account 3 + 5
Authority identity
C21 Content AI Factories
4
Account 4
Scalable content
C22 Traffic Arbitrage Fleets
4
Account 3
Advanced traffic
C23 Funnel Optimization Shipyards
4
Account 3
Conversion engineering
C24 Monetization Fleet Economics
4
Account 3
Revenue systems
C25 Operational Fleet Management
4
Account 4
Infrastructure
C26 Agentic Crew Systems
5
Account 4
AI workforce
C27 Autonomous AI Ships
5
Account 4
Self-operating systems (gate)
C28 AI Shipyards
5
Account 4
Building AI products
C29 Knowledge Ocean Mapping
5
Account 4 + 5
AI knowledge systems
C30 Strategic Ocean Navigation
5
Account 4
AI strategy
C31 Content Fishing Net Factories
5
Account 4
AI content production
C32 Global Shipping Lanes
5
Account 4 + 5
Distribution networks
C33 Traffic Harvesting Trawlers
5
Account 5
Audience acquisition (gate)
C34 Conversion Harbor Engineering
5
Account 5
Funnel monetization
C35 Revenue Cargo Systems
5
Account 5
Customer LTV
C36 Fleet Operations Command
5
Account 4 + 5
Scaling enterprises
C37 Global Trade Routes
5
Account 5
International expansion
C38 Strategic Alliance Harbors
5
Account 5
Joint ventures
C39 Fleet Intelligence Command
5
Account 5
Predictive strategy
C40 Armada Coordination Systems
5
Account 5
Enterprise ecosystem
C41 Autonomous Enterprise Fleets
6
Account 5
Self-operating companies
C42 Digital Trade Empires
6
Account 5
Networked economies (gate)
C43 Sovereign Operator Command
6
Account 5
Independent ownership
C44 Legacy Fleet Architecture
6
Account 5
Generational wealth
C45 Infinite Ocean Strategy
6
Account 5
Future markets
C46–C55
6
Account 5 + Flagship
Sovereign tier specializations
---
Part 5 — The Honest Constraints
What this architecture requires that most operators don't account for:
The flagship cannot be delegated. You on camera is the trust anchor for the entire ladder. Stage 6 buyers ($15K–$50K) will stalk this account before they buy. If you outsource the founder voice, the top of the ladder collapses.
Each faceless account needs its own editor with a distinct voice. Account 2's voice (warm, encouraging, demystifying) is different from Account 4's voice (technical, demonstrative, ROI-focused). One editor cannot run all four faceless accounts well.
The free Skool community needs a dedicated community manager from day 1. Not part-time, not "I'll get to it." A neglected free community is worse than no free community — it signals the academy is dead.
You must publish the syllabus alignment publicly. Every social account should make it clear which Riser Nation stage it serves. This is a feature, not a bug — sophisticated buyers respect transparency. "This account teaches Stage 2 — Sailboat. For Stage 5 content, follow @[Account4Handle]."
The AOV math must work or the team math doesn't work. At $200 AOV (Stage 1–2), you need ~30 sales/month to fund Stage A operations. At $1,500 AOV (Stage 3–4), you need 5/month. At $9,997 AOV (Stage 5), you need 1–2/month. Each account's funnel must hit these baselines before adding the next account.
AIO/AEO/GEO is the moat. Every social account should be feeding citable, schema-ready content into the AI search engines. This is what your syllabus already does at the course level. Mirror that discipline in social.
---
Part 6 — The First Decision
Before launching anything, the foundational decision is which graduation gate course you productize first as a free lead magnet. Recommended order:
First lead magnet: C1 Harbor Orientation excerpt — "The Riser Manifesto + Operator Identity Quiz"
- Powers Account 1 (Flagship) - Lowest production cost, highest emotional resonance - Sets up the entire ladder
Second lead magnet: C7 Offer Fleet Expansion excerpt — "The 5-Rung Value Ladder Blueprint"
- Powers Account 3 (Value Ladder) - Highest perceived value, drives the highest-margin avatar - This is the asset that gets shared in Slack groups and creator masterminds
Third lead magnet: C26 Agentic Crew Systems excerpt — "5 Ready-to-Deploy AI Employee Templates"
- Powers Account 4 (AI Agents) - Most actionable, generates immediate "I built one!" social proof - Drives the highest-ticket ascension
Build these three lead magnets first. Then launch in the Stage A → B → C → D sequence outlined in Part 3.
---
Closing Note
This architecture is not aspirational. It is operationally honest. Five accounts is the maximum a single founder + small team can sustain at quality. Six is where things break. The discipline is to launch each account only after the prior account is proving its funnel — not when you're "excited about the next one."
The syllabus is the product. The five social accounts are simply different fishing nets in different waters, all reeling into the same harbor. Build them one at a time. Prove the math. Then duplicate.
The maritime metaphor is not branding fluff — it is an operational architecture. Honor it in your social strategy and the ladder builds itself.
Complete original Markdown text
# Riser Nation Academy 2026 (Sovereign Edition)
## Social Account Scaling Architecture — Aligned to the Real Syllabus
**Source syllabus:** Riser Nation Academy 2026 Sovereign Edition — 55 courses, ~360 modules, maritime stage progression, graduation gates at C5/C10/C14/C27/C33/C42, AIO/AEO/GEO discoverability baked into every module.
**The thesis:** Your maritime stage progression (Dinghy → Sailboat → Speedboat → Yacht → Mega Yacht → Bora Bora Cruise Ship) is already a value ladder. Each stage has a different avatar at a different awareness level paying a different price point. Therefore each stage needs its own dedicated social content engine. Five accounts. One ladder. Six progressively-priced outcomes.
---
## Part 1 — The Syllabus as a Value Ladder
| Stage | Vessel | Courses | Outcome | Price Range | Awareness Level |
|-------|--------|---------|---------|-------------|-----------------|
| 1 | Dinghy | C1–C5 | Operator identity + market selection | Free → $97 | Problem-aware, doesn't know where to start |
| 2 | Sailboat | C6–C10 | Buyer intel + first offer + funnel | $497–$997 | Solution-aware, has an idea |
| 3 | Speedboat | C11–C14 | Traffic + content + first revenue | $997–$1,997 | Has offer, needs customers |
| 4 | Yacht | C15–C27 | Persuasion + automation + scale | $1,997–$4,997 | Has revenue, needs systems |
| 5 | Mega Yacht | C28–C42 | AI infrastructure + sovereignty | $4,997–$15,000 | Has business, needs leverage |
| 6 | Bora Bora Cruise Ship | C43–C55 | Legacy + governance + sovereign command | $15,000–$50,000+ | Has scale, building permanence |
**The critical insight most academy operators miss:** A buyer at C1 (Harbor Orientation) and a buyer at C43 (Sovereign Operator Command) are not the same person. They speak different languages, consume content on different platforms, respond to different proofs, and convert at different price points. One social account cannot serve both. Five social accounts, each tuned to a specific stage band, can.
---
## Part 2 — The Five Social Account Engines
### ACCOUNT 1 — "Late Bloomer" Founder Flagship
**Stage served:** Pre-Stage + Stage 1 (Dinghy, C1–C5)
**Avatar:** 45+ first-time builder, problem-aware, hasn't bought anything yet
**Awareness:** "Is it too late for me?" / "Where do I even start?"
**Price points fed:** Free PDF → $27–$97 entry → free Skool/Circle community
**Content sourced from these courses:**
- C1: Harbor Orientation — The Riser Manifesto, operator identity, "Reduce Mismatches" doctrine
- C2: Buoy Navigation — Market radar basics, how to read demand
- C3: Casting the Nets — First-offer principles
- C4: The Commercial Fleet — Traffic fundamentals (intro level)
- C5: Funnel Harbors — Conversion architecture basics (this is a graduation gate course; teach the *concepts*, not the implementation)
**Content pillars (rotate weekly):**
1. Riser Manifesto / operator identity
2. "It's not too late" — proof and philosophy
3. The "Reduce Mismatches" doctrine in plain language
4. Founder behind-the-scenes building the academy
5. Origin stories from members (with permission)
**Platforms:** LinkedIn (primary), Instagram, YouTube long-form
**Production:** You on camera. Cannot be delegated.
**Cadence:** 4 LinkedIn + 4 IG + 1 YouTube long-form per week
**Lead magnet:** "The Riser Manifesto + 5-Rung Value Ladder Blueprint" PDF
**Funnel:** Bio link → PDF opt-in → 5-day email nurture → free Builders community → C1–C5 Stage 1 Foundation Bundle ($97)
**Why on-camera matters here:** Your face is the proof that someone over 45 can build something credible. The flagship account doesn't sell a course — it sells permission.
---
### ACCOUNT 2 — "AI for First-Time Builders 45+" (Faceless)
**Stage served:** Stage 2 (Sailboat, C6–C10)
**Avatar:** 45+, has a skill or idea, ready to build their first offer
**Awareness:** Solution-aware, looking for "how"
**Price points fed:** $497–$997 (individual Stage 2 courses or the Sailboat bundle)
**Content sourced from these courses:**
- C6: Email Harbor Systems — Email list-building for beginners
- C7: Offer Fleet Expansion — Value ladder construction (simplified)
- C8: Paid Traffic Armadas — Intro to paid traffic (Stage 2 level)
- C9: Bora Bora Captain's Retreat — Strategic clarity rituals (great short-form content)
- C10: Funnel Fleet Engineering — Funnel architecture (graduation gate)
**Content pillars:**
1. "Try this AI prompt today" — single-tool, single-outcome demos
2. "I'm 55 and I just figured out..." — relatable framing
3. Pricing psychology for first-time sellers
4. Email list-building basics
5. Funnel anatomy explainers (60-second teardowns)
**Platforms:** Instagram Reels, TikTok, YouTube Shorts, LinkedIn carousels
**Production:** Faceless. AI voiceover + screen recordings + b-roll. Delegated to editor.
**Cadence:** 1 short per day, same video native-captioned per platform
**Lead magnet:** "10 AI Prompts for First-Time Business Builders" (from your AI Prompts Directory)
**Funnel:** Bio link → prompt pack → 10-day email sequence (one prompt per day) → Stage 1 bundle ($97) OR direct Stage 2 Sailboat bundle ($497)
**Why faceless works here:** This avatar is at the bottom of the awareness funnel. The faceless format removes the comparison ("I'm not like that person on camera") that kills conversion. They want the *answer*, not the influencer.
---
### ACCOUNT 3 — "Value Ladder Architecture" (Faceless)
**Stage served:** Stage 3 + Stage 4 (Speedboat + early Yacht, C11–C20)
**Avatar:** Existing course creator, coach, agency owner plateaued at $5–30K/mo
**Awareness:** Product-aware, knows what a funnel is, frustrated by their ceiling
**Price points fed:** $997–$2,997 (Speedboat/Yacht bundles)
**Content sourced from these courses:**
- C11: Podcast Broadcasting Fleet — Authority voice channels
- C12: Video Authority Ships — Visual influence systems
- C13: Offer Fleet Expansion — Advanced value ladder engineering
- C14: Funnel Fleet Engineering — Advanced conversion (graduation gate)
- C15: Automation Fleet Systems — Marketing automation
- C16: AI Captain Systems — Intelligent business operations
- C17: Data Sonar Systems — Analytics intelligence
- C18: Partnership Harbors — Strategic alliances
- C19: Community Fishing Villages — Audience ecosystems
- C20: Brand Flagship Ships — Authority identity systems
**Content pillars:**
1. LTV math demonstrations (the "Marcus the Designer $197 → $612" story format)
2. Why "one course" businesses plateau
3. Ascension offer architecture
4. Continuity / churn / retention frameworks
5. Public teardowns of well-known funnels
**Platforms:** LinkedIn (primary — this audience lives here), Instagram, YouTube long-form teardowns
**Production:** Faceless OR voiceover with screen sharing. Delegated.
**Cadence:** 4 LinkedIn + 3 IG + 1 YouTube per week
**Lead magnet:** "Value Ladder LTV Calculator" (interactive web tool, sticky and shareable)
**Funnel:** Calculator → personalized email recommendations → $97 workshop → $997 Stage 3 course → $2,997 Stage 4 ascension
**Why this works:** Highest-margin acquisition channel of the five. Audience is pre-qualified — they have revenue, are frustrated, and buy solutions. Position as architecture, not motivation.
---
### ACCOUNT 4 — "AI Agents & Custom GPTs" (Faceless)
**Stage served:** Stage 5 (Mega Yacht, C28–C42)
**Avatar:** Solopreneur or agency owner at $10–50K/mo, ready to systematize with AI
**Awareness:** Has revenue, has operational chaos, looking for leverage
**Price points fed:** $2,997–$9,997 (Stage 5 AI Command Fleet courses)
**Content sourced from these courses:**
- C26: Agentic Crew Systems — AI workforce infrastructure
- C27: Autonomous AI Ships — Self-operating business systems (graduation gate)
- C28: AI Shipyards — Building AI products & tools
- C29: Knowledge Ocean Mapping — AI knowledge systems
- C30: Strategic Ocean Navigation — AI strategy & decision systems
- C31: Content Fishing Net Factories — AI content production
- C32: Global Shipping Lanes — Content distribution networks
- C36: Fleet Operations Command — Scaling digital enterprises
**Content pillars:**
1. "Built this agent in 20 minutes" speed demos
2. AI Employee Framework walkthroughs
3. Agent ecosystem teardowns
4. Custom GPT vs. Agent vs. Chatbot decision frameworks
5. Real ROI case studies (hours saved, revenue per agent)
**Platforms:** YouTube long-form (primary — this audience consumes long technical content), LinkedIn, X/Twitter
**Production:** Voiceover + screen recordings. Delegated to technical editor.
**Cadence:** 2 YouTube long-form per week + 5 LinkedIn posts + daily X
**Lead magnet:** "5 Ready-to-Deploy AI Employee Templates" + a custom GPT they can clone immediately
**Funnel:** Template opt-in → "Build Your First AI Employee" mini-course ($27) → C26–C30 Mega Yacht bundle ($2,997) → Stage 5 full ascension ($9,997)
**Why this works:** Audience trusts depth. A 30-minute YouTube teardown converts higher than 30 short-form videos. Positions Riser Nation as the operator-grade alternative to "AI hype" content.
---
### ACCOUNT 5 — "AEO/GEO Search Visibility" (Faceless)
**Stage served:** Stage 5–6 specialty tracks (the AIO/AEO/GEO discoverability layer baked into every Sovereign Edition course)
**Avatar:** Marketers, agency owners, content creators with existing SEO programs nervous about AI search
**Awareness:** Sophisticated. Understands SEO. Watching traffic shift to AI engines.
**Price points fed:** $4,997–$25,000 (Stage 6 sovereign tier + done-with-you continuity)
**Content sourced from these courses:**
- The AIO/AEO/GEO layer documented across the entire syllabus (every course ships FAQ-schema-ready Q&A pairs, citable definition blocks, entity-authority stacking)
- C43: Sovereign Operator Command
- C44: Legacy Fleet Architecture
- C49: Digital Ocean Governance
**Content pillars:**
1. "What ChatGPT cites vs. what Google ranks" comparisons
2. Schema.org markup tutorials
3. AEO direct-answer block construction
4. GEO entity-authority signal stacking (Wikidata, podcast appearances, expert quotes)
5. AI search demos and audits
**Platforms:** LinkedIn (primary), X/Twitter, YouTube long-form, technical blog
**Production:** Voiceover + screen sharing. Delegated to most technical editor.
**Cadence:** 3 LinkedIn + daily X + 1 YouTube long-form per week
**Lead magnet:** "AEO Audit Tool" or "10 Queries Your Business Should Win in AI Search"
**Funnel:** Audit → $197 workshop → $2,997 AEO/GEO implementation course → $1,500/mo done-with-you continuity → Stage 6 sovereign tier
**Why this works:** Smallest target audience of the five, but highest-converting and highest-LTV. These buyers pay $5K+ readily. This account feeds your top-of-ladder offers.
---
### THE UNIFYING MIDDLE — Free Skool/Circle Community
**Not a social account but the most important asset in the architecture.**
Every one of the 5 social accounts funnels into this free community. It is where lurkers become buyers. It is where graduation gates (C5, C10, C14, C27, C33, C42) get celebrated publicly, where member wins get amplified, and where the academy's culture is forged.
Without this asset, you are acquiring leads you cannot follow up with at scale. The free community is what makes the 5-account architecture financially viable.
---
## Part 3 — The Highway Scaling Sequence
This is where most academy operators fail. They try to launch 5 accounts at once, exhaust themselves, and produce mediocre content across the board. Here is the actual sequence aligned to your syllabus rollout:
### Stage A — Months 1–3 (Single Lane)
**Active accounts:** Flagship (Account 1) + AI for 45+ (Account 2) + Free Skool community
**Stage served:** Pre-Stage through C10 (Dinghy + Sailboat)
**Goal:** Prove the funnel converts before duplicating it
**Why this sequence:** If your flagship + one faceless account + free community can't generate consistent email opt-ins and Stage 1–2 sales, adding more accounts will only multiply the failure. The Stage 1 of your own business has to work before you can teach Stage 1 to others.
**Success metrics:**
- 200+ email opt-ins/week consistently
- 30% join free community
- 3–5% buy a Stage 1 or Stage 2 product within 30 days
**Team:** You + 1 editor (15–20 hrs/week) + 1 part-time community manager
**Monthly operational cost:** $2,500–4,500
### Stage B — Months 4–6 (Add Lane 2)
**New account launched:** Value Ladder Architecture (Account 3)
**Stage served:** C11–C20 (Speedboat + early Yacht)
**Why this account next:** Targets a completely different avatar (existing creators with revenue) at a higher price point. Doesn't compete with Account 1+2 for attention.
**Critical moment:** Your average order value should roughly double here. Stage 1–2 buyers average ~$200 AOV. Stage 3–4 buyers average ~$1,500 AOV. Same operational cost, much higher revenue per acquisition.
**Team additions:** +1 editor (Account 3 uses different content style — more whiteboard/teardown). Total: you + 2 editors + community manager.
**Monthly operational cost:** $4,500–7,000
### Stage C — Months 7–9 (Add Lane 3)
**New account launched:** AI Agents & Custom GPTs (Account 4)
**Stage served:** C21–C42 (full Yacht + Mega Yacht)
**Why third:** Your Phase 5 Mega Yacht courses ($2,997+) need Accounts 1–3 already populating ascension demand before higher-ticket Phase 5 offers have a populated audience to convert.
**Team additions:** +1 technical editor or contractor for agent demos. Total: you + 3 editors + community manager + part-time tech.
**Monthly operational cost:** $7,000–11,000
### Stage D — Months 10–12 (Add Lane 4)
**New account launched:** AEO/GEO (Account 5)
**Stage served:** C43–C55 (Bora Bora Cruise Ship + Sovereign Operator)
**Why last:** Smallest audience, most sophisticated, highest-ticket. By month 10 you have 9 months of content, data, and case studies for proof in this technical niche. Revenue from Accounts 1–4 funds the slower ramp of Account 5.
**Critical strategic note:** Account 5 is the gateway to your Stage 6 offers ($15K–$50K+). Conversion volume is low but revenue per conversion is dramatically higher. Don't measure this account by the same metrics as Accounts 1–4.
**Team additions:** Content director to oversee all 5 accounts. You shift to strategic oversight. Total: you (strategic) + content director + 3–4 editors + community manager + part-time tech.
**Monthly operational cost:** $11,000–16,000
### Stage E — Year 2 (Full Armada)
**All 5 accounts running + Free Skool community + paid Circle continuity**
**Stage served:** All 6 maritime stages, full value ladder operational
**Revenue mix at Year 2 (realistic estimate):**
- Account 1 (Stage 1 buyers): 40% of customer volume, 8% of revenue
- Account 2 (Stage 2 buyers): 30% of volume, 15% of revenue
- Account 3 (Stage 3–4 buyers): 20% of volume, 35% of revenue
- Account 4 (Stage 5 buyers): 8% of volume, 27% of revenue
- Account 5 (Stage 6 buyers): 2% of volume, 15% of revenue
The math is brutal and honest: the top 2% of your customer base (Stage 6) generates 15% of your revenue. The top 10% (Stage 4–6) generates 77%. This is exactly why scaling 5 accounts is worth the operational complexity — the high-end of your ladder requires its own dedicated acquisition channel.
---
## Part 4 — The Maritime Stage × Content Pillar Cross-Reference
For each Riser Nation course, here's which social account should mine it for content:
| Course | Stage | Account # | Content Type |
|--------|-------|-----------|--------------|
| C1 Harbor Orientation | 1 | Account 1 | Founder philosophy, manifesto |
| C2 Buoy Navigation | 1 | Account 1 + 2 | Market reading basics |
| C3 Casting the Nets | 1 | Account 2 | First offer creation |
| C4 The Commercial Fleet | 1 | Account 2 | Traffic intro |
| C5 Funnel Harbors | 1 | Account 1 + 3 | Conversion concepts (gate) |
| C6 Email Harbor Systems | 2 | Account 2 + 3 | Email infrastructure |
| C7 Offer Fleet Expansion | 2 | Account 3 | Value ladder engineering |
| C8 Paid Traffic Armadas | 2 | Account 3 | Paid traffic systems |
| C9 Bora Bora Retreat | 2 | Account 1 | Strategic clarity rituals |
| C10 Funnel Fleet Engineering | 2 | Account 3 | Funnel architecture (gate) |
| C11 Podcast Broadcasting Fleet | 3 | Account 3 | Authority voice |
| C12 Video Authority Ships | 3 | Account 3 | Visual influence |
| C13 Offer Fleet Expansion (advanced) | 3 | Account 3 | Advanced ladder |
| C14 Funnel Fleet Engineering (advanced) | 3 | Account 3 | Advanced conversion (gate) |
| C15 Automation Fleet Systems | 4 | Account 3 + 4 | Marketing automation |
| C16 AI Captain Systems | 4 | Account 4 | AI operations |
| C17 Data Sonar Systems | 4 | Account 4 | Analytics |
| C18 Partnership Harbors | 4 | Account 3 + 5 | Strategic alliances |
| C19 Community Fishing Villages | 4 | Account 3 | Audience ecosystems |
| C20 Brand Flagship Ships | 4 | Account 3 + 5 | Authority identity |
| C21 Content AI Factories | 4 | Account 4 | Scalable content |
| C22 Traffic Arbitrage Fleets | 4 | Account 3 | Advanced traffic |
| C23 Funnel Optimization Shipyards | 4 | Account 3 | Conversion engineering |
| C24 Monetization Fleet Economics | 4 | Account 3 | Revenue systems |
| C25 Operational Fleet Management | 4 | Account 4 | Infrastructure |
| C26 Agentic Crew Systems | 5 | Account 4 | AI workforce |
| C27 Autonomous AI Ships | 5 | Account 4 | Self-operating systems (gate) |
| C28 AI Shipyards | 5 | Account 4 | Building AI products |
| C29 Knowledge Ocean Mapping | 5 | Account 4 + 5 | AI knowledge systems |
| C30 Strategic Ocean Navigation | 5 | Account 4 | AI strategy |
| C31 Content Fishing Net Factories | 5 | Account 4 | AI content production |
| C32 Global Shipping Lanes | 5 | Account 4 + 5 | Distribution networks |
| C33 Traffic Harvesting Trawlers | 5 | Account 5 | Audience acquisition (gate) |
| C34 Conversion Harbor Engineering | 5 | Account 5 | Funnel monetization |
| C35 Revenue Cargo Systems | 5 | Account 5 | Customer LTV |
| C36 Fleet Operations Command | 5 | Account 4 + 5 | Scaling enterprises |
| C37 Global Trade Routes | 5 | Account 5 | International expansion |
| C38 Strategic Alliance Harbors | 5 | Account 5 | Joint ventures |
| C39 Fleet Intelligence Command | 5 | Account 5 | Predictive strategy |
| C40 Armada Coordination Systems | 5 | Account 5 | Enterprise ecosystem |
| C41 Autonomous Enterprise Fleets | 6 | Account 5 | Self-operating companies |
| C42 Digital Trade Empires | 6 | Account 5 | Networked economies (gate) |
| C43 Sovereign Operator Command | 6 | Account 5 | Independent ownership |
| C44 Legacy Fleet Architecture | 6 | Account 5 | Generational wealth |
| C45 Infinite Ocean Strategy | 6 | Account 5 | Future markets |
| C46–C55 | 6 | Account 5 + Flagship | Sovereign tier specializations |
---
## Part 5 — The Honest Constraints
**What this architecture requires that most operators don't account for:**
1. **The flagship cannot be delegated.** You on camera is the trust anchor for the entire ladder. Stage 6 buyers ($15K–$50K) will stalk this account before they buy. If you outsource the founder voice, the top of the ladder collapses.
2. **Each faceless account needs its own editor with a distinct voice.** Account 2's voice (warm, encouraging, demystifying) is different from Account 4's voice (technical, demonstrative, ROI-focused). One editor cannot run all four faceless accounts well.
3. **The free Skool community needs a dedicated community manager from day 1.** Not part-time, not "I'll get to it." A neglected free community is worse than no free community — it signals the academy is dead.
4. **You must publish the syllabus alignment publicly.** Every social account should make it clear which Riser Nation stage it serves. This is a feature, not a bug — sophisticated buyers respect transparency. "This account teaches Stage 2 — Sailboat. For Stage 5 content, follow @[Account4Handle]."
5. **The AOV math must work or the team math doesn't work.** At $200 AOV (Stage 1–2), you need ~30 sales/month to fund Stage A operations. At $1,500 AOV (Stage 3–4), you need 5/month. At $9,997 AOV (Stage 5), you need 1–2/month. Each account's funnel must hit these baselines before adding the next account.
6. **AIO/AEO/GEO is the moat.** Every social account should be feeding citable, schema-ready content into the AI search engines. This is what your syllabus already does at the course level. Mirror that discipline in social.
---
## Part 6 — The First Decision
Before launching anything, the foundational decision is which graduation gate course you productize first as a free lead magnet. Recommended order:
1. **First lead magnet: C1 Harbor Orientation excerpt — "The Riser Manifesto + Operator Identity Quiz"**
- Powers Account 1 (Flagship)
- Lowest production cost, highest emotional resonance
- Sets up the entire ladder
2. **Second lead magnet: C7 Offer Fleet Expansion excerpt — "The 5-Rung Value Ladder Blueprint"**
- Powers Account 3 (Value Ladder)
- Highest perceived value, drives the highest-margin avatar
- This is the asset that gets shared in Slack groups and creator masterminds
3. **Third lead magnet: C26 Agentic Crew Systems excerpt — "5 Ready-to-Deploy AI Employee Templates"**
- Powers Account 4 (AI Agents)
- Most actionable, generates immediate "I built one!" social proof
- Drives the highest-ticket ascension
Build these three lead magnets first. Then launch in the Stage A → B → C → D sequence outlined in Part 3.
---
## Closing Note
This architecture is not aspirational. It is operationally honest. Five accounts is the maximum a single founder + small team can sustain at quality. Six is where things break. The discipline is to launch each account only after the prior account is proving its funnel — not when you're "excited about the next one."
The syllabus is the product. The five social accounts are simply different fishing nets in different waters, all reeling into the same harbor. Build them one at a time. Prove the math. Then duplicate.
The maritime metaphor is not branding fluff — it is an operational architecture. Honor it in your social strategy and the ladder builds itself.
Build and validate a minimum viable offer
Define the offer before building the asset
Imagine that a buyer needs a working email sequence this week. A large library may contain everything they need, but a small, well-scoped service could remove the immediate obstacle sooner. This is an illustrative application: an MVO tests whether a real buyer will pay for a clearly defined transformation, with the least complexity needed to deliver it responsibly.
Separate the three offer layers. The stated offer describes the deliverable and terms. The implied offer is the change the buyer expects. The hidden offer is a possible emotional payoff. Ask buyers about their goals rather than assume you know private motives. The playbook's execution-debt idea describes someone who understands a problem but lacks the time, confidence or clarity to act; it does not prove that this audience always converts best.
The source's attributed first law emphasizes the offer over product or copy. Treat that as a positioning maxim, not proof that a strong offer can compensate for an undeliverable product. Build the stated deliverable, expected transformation and possible emotional payoff together, even for a small offer. In the email-sequence example, the stated offer could be a defined set of emails, the implied offer a usable follow-up process, and the possible hidden payoff relief from unfinished work. Those are authored illustrations to validate with buyers. Keep the offer small in complexity while making its value understandable; reducing scope must still leave a useful result.
Use all ten diagnostic questions to form a research brief. First, what keeps this buyer awake at night? Second, what are they afraid of? Third, what makes them angry, and at whom? Fourth, what are their top three daily frustrations? Fifth, what trends are occurring or may occur in their world? Sixth, what do they privately desire most? Seventh, what are their strongest objections to buying a solution? Eighth, what triggers a buying decision? Ninth, what language, jargon and slang do they use? Tenth, who already sells to them successfully, and why? The source suggests thirty minutes of initial desk research. Its heading says to answer before any research, while its instruction calls for desk research; interpret this as an initial hypothesis brief before deeper investigation, not knowledge you already possess. Record an evidence source, confidence level and follow-up question beside each answer. Do not invent a buyer's private feelings.
This companion uses the source's eight numbered phases plus its introductory philosophy. The cover says nine phases and Version 5.0, while native headers say V3. The original is retained with those labels. Attributed quotations and the cover's field-tested claim have not been independently authenticated. Our authored applications connect the offer to the curriculum's Brunson-style customer journey and Hormozi-style attention to outcome, confidence, speed and effort; they are not quotations from those educators.
Keep framework attribution distinct: the resource links identify Acquisition.com's Value Equation lesson, ClickFunnels' explanation of Russell Brunson's Value Ladder, Cialdini's seven principles and Ray Edwards' P.A.S.T.O.R. material. This playbook combines and adapts concepts; its examples and abbreviated labels are not automatically the creators' exact wording. The Kennedy quotations remain unauthenticated.
Study the original examples, instructions and tables
Read these source details with the explanation above. Numerical claims, quotations and proposed actions retain their original status; they are not verified results or completed actions.
THE DEFINITIVE PLAYBOOK — V5
Minimum Viable Offer
The Complete Direct-Response Framework for Offers That Convert
An MVO is the smallest, fastest-to-deploy offer that validates whether a market will exchange money for the transformation you promise. It’s not about being minimal in value — it’s about being minimal in complexity while being MAXIMUM in perceived value.
Kennedy’s First Law
“The best offer wins. Not the best product. Not the best copy. The best OFFER.”
Kennedy’s Offer Architecture
1.THE STATED OFFER — What you explicitly say they get
2.THE IMPLIED OFFER — What they believe they’ll become
3.THE HIDDEN OFFER — The emotional payoff they can’t articulate
Professionals build all three layers simultaneously. Your MVO must address all three even in its simplest form.
Execution Debt
The Highest-Value Pain Category
Execution Debt: someone KNOWS the problem AND roughly knows the solution, but lacks bandwidth, courage, or clarity.
MVOs targeting Execution Debt convert highest because the buyer needs enablement, not education.
Kennedy’s 10 Smart Market Diagnosis Questions
Answer These BEFORE Any Research
Write answers to all 10 using initial desk research. 30 minutes. This gives your research direction.
1. What keeps them awake at night, staring at the ceiling?
2. What are they afraid of?
3. What are they angry about? Who are they angry at?
4. What are their top 3 daily frustrations?
5. What trends are occurring (or will occur) in their world?
6. What do they secretly desire most?
7. What are their strongest objections to buying a solution?
8. What buying triggers do they respond to?
9. What language, jargon, and slang do they use?
10. Who else is already selling to them successfully, and why?
Phase 1 — Research a market and retain evidence
Score the niche
Start with the seven-part niche matrix. Rate pain intensity, existing willingness to pay, ease of fulfilment, speed to a first win, your competitive advantage, content opportunities and scalability. The source scores each from one to ten, for seventy possible points, with four bands shown below. These cutoffs organize discussion; the file supplies no study establishing them as reliable predictors of demand. Record why you chose each score and what evidence could change it.
Interpret each niche score before adding it. Pain intensity asks how severe the problem is; willingness to pay asks whether buyers already spend on solutions. Ease of fulfilment asks what infrastructure delivery requires, and speed to a first win asks whether a useful result can arrive within days or weeks. Competitive advantage asks which gap you can serve; content opportunity asks whether you can create useful authority content; scalability asks whether delivery can extend beyond one-to-one work. The source labels sixty to seventy strong and ready to test, fifty to fifty-nine viable with sharper positioning, forty to forty-nine weak and needing a reposition or pivot, and below forty a walk-away signal. These are the source's decision bands, not validated pass marks. An authored example of fifty-five suggests investigating positioning before committing, rather than treating the sum as proof of viability.
Find and interpret research evidence
Define the audience through relevant buying behavior as well as identity. The source contrasts a broad occupation with people already spending on lead generation and dissatisfied with conversion. Spending is useful evidence, but it does not by itself establish that your offer solves their problem or fits their budget.
The research list covers book reviews, forums, autocomplete, support tickets, groups, paid-course reviews, frontline staff and ecommerce behavior. The exact search strings and tool suggestions below show how the source proposes to find language and friction. Preserve the difference between a real quote, an analyst's interpretation and an AI-generated hypothesis. High comment counts, review ratings and long-running advertisements can guide investigation; none proves demand, emotional intensity or profitability on its own.
Give each discovery channel a specific job. Contrast one-star book complaints with five-star descriptions of desired transformation. Use forum language and autocomplete modifiers such as but, without, for and vs to discover obstacles and alternatives. Read support complaints as possible problems, then check frequency and consequence. Review group discussions without equating fifty comments with willingness to pay. Course-review complaints such as too basic, missing an explanation or wishing for a topic can suggest unmet needs, but a review alone does not establish that its author paid or wants your solution. The source proposes a thirty-minute frontline staff debrief and inspection of cart abandonment, chargebacks and return or refund reasons. Staff observations and behavioral records complement interviews; a recorded event still requires investigation of its cause.
Use the four printed search recipes as source examples: replace the niche placeholder with your topic, then examine complaints, frustration, wasted money, inability to solve a problem and requests for alternatives. The two Reddit recipes use site restrictions; the forum recipe uses inurl:forum; the X example proposes Latest and Top views over twelve months. The exact strings remain below so their wording is not lost. Search interfaces may interpret operators differently, so inspect the returned results and record the actual query and date. Do not represent the source syntax or available filters as newly verified platform behavior.
The seven newer research suggestions have different evidence limits. AI citation mining can surface claims to check in their original sources; repeated model output is not independent consensus. Reddit tracking and social listening can reveal recurring language. A Search Console query shift from what is to service for may suggest a different intent, but it does not prove purchase intent. Heatmaps and recordings describe observed interactions, not private motives. Multi-source automation is a proposed workflow, not a system implemented by this lesson. Ad-library longevity can be a research lead but does not reveal profitability. Use the linked resource-status notes before adopting any named tool; in particular, the GummySearch new-signup closure limits that source recommendation.
Evaluate pain and competitive gaps
Apply the three kill filters as questions about adoption and differentiation: is the problem inexpensive to tolerate, does the solution demand a difficult behavior change, and is an excellent inexpensive alternative already sufficient? The source presents these as absolute stop rules. In practice, document the evidence and uncertainty rather than assume that every example or listed software price is current. The cheap/premium comparison pairs and eight motives below help you look for an observable consequence: money, time, risk, embarrassment, status, protection or certainty.
Read the five cheap-versus-premium pairs as prompts to find consequences: logo versus booked appointments, followers versus qualified leads, motivation versus passing inspection, content ideas versus reduced employee turnover, and learning marketing versus retaining customers. These pairs are not necessarily the same buyer problem or a direct causal ladder. Ask what outcome matters and what evidence supports the connection. The source's eight motives are making money, saving money, saving time, avoiding risk, avoiding embarrassment, increasing status, protecting the business and creating certainty. None guarantees demand, and a logo or learning offer can still have substantial value in a particular context.
Desire mapping separates the stated goal from a possible emotional driver and hidden motive. Validate the interpretation with the buyer. Then use the five-gap lens—speed, risk, specificity, access and format—to propose a concrete improvement. A gap is a hypothesis until buyers recognize its value and you can deliver it.
The desire example moves from losing twenty pounds to feeling attractive to being envied. Preserve these as the source's illustrative layers, not a diagnosis of any buyer. Test the five gaps with concrete questions: can delivery be faster, buyer risk lower, audience fit narrower, expert access more direct, or the delivery format more useful? In the six-score pain filter, urgency means need now; spending proof means actual payment evidence; frequency means repeated appearance across sources; value means a meaningful economic benefit; simplicity means a result explainable in one sentence; fulfilment means deliverability without chaos. Score the evidence you have, with uncertainty recorded, rather than scoring how persuasive your idea sounds.
Build the evidence worksheet
Score each pain on urgency, spending proof, frequency, value, simplicity and fulfilment, each one to five. The source keeps scores of at least twenty-two out of thirty. Its older-five/new-six explanation mentions two additions without specifying what was removed, so do not reconstruct an unseen earlier scoring model. Retain twenty pains across the four five-item categories, and attach all three evidence fields to each: exact quote, spending evidence and the way someone might phrase the problem in AI search. These fields make your later copy traceable; they do not authorize invented quotations or claims of search visibility.
Build the twenty-pain worksheet with five distinct items in each category. Financial examples include lost revenue, wasted spend, pricing errors, cash flow and hidden costs. Time and productivity examples include manual tasks, bottlenecks, context switching and slow processes. Emotional and status examples include embarrassment, imposter feelings, fear of failure and peer comparison; validate sensitive interpretations with the person rather than infer them. Process and support examples include bad tools, weak support, complex workflows and integration failures. The source lists fewer than five examples in some categories; they are prompts, not a complete list of twenty researched pains. For every selected pain retain the exact real quote, evidence of existing spending, and a documented or clearly labeled proposed AI-search phrasing. Do not count twenty rewordings of one problem as category diversity.
Study the original examples, instructions and tables
Read these source details with the explanation above. Numerical claims, quotations and proposed actions retain their original status; they are not verified results or completed actions.
Phase 1: Market Excavation
★ V5: Niche Viability Scoring Matrix
Before You Research Pain Points — Score the Niche Itself
Don’t build a beautifully constructed MVO for a niche that was never viable. Score first, research second.
Rate each dimension 1–10. Niches scoring under 50/70 need repositioning or should be abandoned:
Dimension
Score 1–10
What You’re Measuring
Pain Intensity
___
How severe is the core problem?
Willingness to Pay
___
Are they already spending on solutions?
Ease of Fulfillment
___
Can you deliver without massive infrastructure?
Speed to First Win
___
Can the buyer see results within days/weeks?
Competitive Advantage
___
Is there a gap you can own?
Content Opportunity
___
Can you create authority content in this space?
Offer Scalability
___
Can this grow beyond 1:1 delivery?
Diagnostic: 60–70 = Strong, test immediately. 50–59 = Viable but needs sharp positioning. 40–49 = Weak, reposition or pivot. Under 40 = Walk away.
★ V5: Define Audience by Buying Behavior, Not Identity
Critical Reframe
“Real estate agents” is an identity. “People who spend $500+/month on lead gen and are frustrated with conversion” is a buying behavior.
The first gives you a demographic. The second gives you a qualified buyer with proven willingness to spend.
Define your niche by what they BUY and DO, not just what they ARE.
Step 1: The ‘Bleeding Neck’ Audit
Core Discovery Sources:
→ Amazon Book Reviews: 1-star = what people hate. 5-star = transformation they wanted.
→ Reddit/Forum Mining: Use exact search operators (see below).
→ Google Autocomplete: Topic + “but,” “without,” “for,” “vs.”
→ Customer Support Tickets: Every complaint is an offer waiting to be born.
→ Facebook Groups: Posts with 50+ comments = emotional resonance.
→ ★ V5: Course Review Platforms: Udemy, Coursera, Skillshare, LinkedIn Learning. Reviewers PAID for education and tell you exactly where it falls short. “Too basic,” “Didn’t explain X,” “I wish it covered Y” — premium pain signals from validated buyers.
→ ★ V5: Frontline Staff Observations (Brick-and-Mortar): Receptionists, technicians, and reps hear unfiltered customer pain daily. A 30-min staff debrief surfaces pain points no Reddit mining will find.
→ ★ V5: E-Commerce Data: Cart abandonment analytics, chargeback reasons, and return/refund reasons. Direct behavioral evidence of where the buying experience breaks.
Exact Search Operators:
site:reddit.com "[niche] sucks" OR "[niche] hate" OR "struggling with [niche]"
site:reddit.com "[niche]" "waste of money" OR "frustrated" OR "can't figure out"
•Ad Transparency: Meta Ad Library — ads running 6+ months = profitable pain point
★ V5: Three Kill Filters (Before You Proceed)
If Any of These Are True — Walk Away
These kill signals save you from building an MVO for a pain point that will never monetize.
☠ Kill Filter 1: “Cheap to Ignore”
Can the buyer live with this problem at near-zero cost? If ugly invoices, messy desks, or imperfect processes don’t cost them real money, time, or status — they’ll tolerate it forever. No MVO can sell relief from a pain that’s free to endure.
Even if the pain is severe, if your solution requires them to fundamentally rewire their habits or workflow, adoption collapses. A brilliant CRM for contractors who hate using CRMs will fail. The implementation barrier becomes the real objection.
☠ Kill Filter 3: “Existing Solution Already Excellent AND Cheap”
If Canva already solves the design problem well at $12/month, there’s no gap. We talk about competitive gaps — this is the explicit signal that no gap exists. Don’t compete where the market is already well-served cheaply.
★ V5: Cheap Pain vs. Premium Pain
Cheap Pain (Avoid)
Premium Pain (Pursue)
“I need a logo”
“I need more booked appointments”
“I need more followers”
“I need qualified leads”
“I want motivation”
“I need to pass inspection”
“I need content ideas”
“I need to reduce employee turnover”
“I want to learn marketing”
“I need to stop losing customers”
Premium pain always connects to: Make money, save money, save time, avoid risk, avoid embarrassment, increase status, protect business, create certainty.
Desire Mapping Framework
Level
What They Say
What It Means
Surface
“I want to lose 20 lbs”
Stated rational goal
Real
“I want to feel attractive again”
Emotional driver
Hidden
“I want people to envy me”
Drives premium buying
Competitive Gap Analysis — 5-Gap Framework
1.SPEED — Deliver the result faster?
2.RISK — Remove more risk from the buyer?
3.SPECIFICITY — Serve a narrower audience better?
4.ACCESS — Offer more direct access to expertise?
5.FORMAT — Deliver in a way nobody else does?
★ V5: The 6-Score Monetization Filter
Replaces Our Previous 5-Filter System — More Structured, with Hard Cutoff
Score each pain point 1–5 on six dimensions. Maximum: 30. Only keep pain points scoring 22+.
Dimension
Score 1–5
Question
Urgency
___
Do they need it NOW, not someday?
Spending Proof
___
Are they already paying for solutions?
Frequency
___
Does this pain appear often across sources?
Value
___
Is solving it worth real money to them?
Simplicity
___
Can the result be explained in one sentence?
Fulfillment
___
Can you actually deliver without chaos?
“Simplicity” and “Fulfillment” are the new additions. They catch two failure modes: offers too complex to explain and offers that are nightmares to deliver.
Pain Point Category Balancing
Enforce diversity across 4 categories. Don’t find 20 variations of the same pain:
Embarrassment, imposter syndrome, fear of failure, peer comparison
Process/Support
5 points
Bad tools, poor support, complex workflows, integration failures
Evidence Tagging Format
For each of your top 20, document three pieces of evidence:
1.Verbatim Quote — Exact language from a real person. This becomes copy.
2.Monetization Proof — Evidence they already pay to solve it.
3.GEO Angle — How people phrase this to AI search engines.
Phase 2 — Choose a deliverable and construct the offer
Compare candidate offers
Generate ten candidate offers before choosing one. For each, fill all nine fields shown below, from offer name and target buyer through hesitation and fulfilment difficulty. Rank them on validation speed, delivery simplicity, perceived value, margin, risk and scaling potential. The source suggests testing one to three; select only as many as your team can deliver and measure without confusing the results. No weighting or tie-breaking formula is supplied.
Make the ten-offer comparison concrete by writing all nine fields for every candidate: offer name, target customer, main problem solved, delivery format, time to result, price range, why the buyer would buy, why they would hesitate and fulfilment difficulty. Separate the buyer's expected result from your delivery activity. Then ask whether you can test this week, deliver without major infrastructure, make the value understandable, retain a sustainable margin, contain the downside and grow beyond one-to-one work. These are the source's six ranking questions. Generating alternatives can reveal an option you initially overlooked; it does not establish that a particular rank will perform best. Choose one to three only after recording the tradeoffs.
Explain value and the mechanism
Use the value equation to inspect four relationships: desired outcome, confidence it will happen, time to that outcome, and effort or sacrifice. A more specific promise, relevant proof, an earlier useful milestone or a simpler implementation can improve the offer. This is a conceptual model, not a calibrated financial equation with defined units. Do not treat a zero delay or effort estimate as an infinite-value calculation.
The printed value equation is dream outcome multiplied by perceived likelihood, divided by time delay multiplied by effort and sacrifice. Explain each intervention separately. The source contrasts thirty qualified leads in thirty days with more leads to illustrate specificity; that numerical promise requires evidence before use. It also proposes connecting the outcome to an identity shift, which should reflect a buyer's own aspirations rather than an assumption. Proof and a demonstrated method can increase confidence. An early milestone such as a useful deliverable on day three can reduce the wait for initial value. Templates and implementation support can reduce effort. The source ranks done-for-you above done-with-you above DIY for effort reduction; delivery cost, suitability and capacity still need separate evaluation.
The Thud Factor seeks an impressive stack, but the same source warns that filler destroys clarity. Tie every bonus to a real subproblem. Check that a buyer can repeat the core promise and explain the mechanism in one sentence. The pass/fail examples below illustrate clarity rather than establish a test already passed by your business.
Distinguish the promise from the mechanism. The promise says what useful change is offered; the mechanism says how the work produces that change. The source's five-day email-writing sprint is repeatable in ordinary language, while its vague multi-modular proprietary-system example conceals what happens. Ask a prospective buyer to explain both in one sentence and note what they misunderstood. Naming a method, such as the source's Reverse Funnel Method example, does not prove the mechanism is unique or effective. The name should summarize real steps, not replace their explanation.
Translate the pain into a deliverable
The Instagram example moves from broad education to a specific calendar and then a defined implementation service. Explain what changes in specificity, speed and buyer effort at each step. More done-for-you also changes labor, scope and capacity; it is not automatically the most profitable or appropriate format. A ninety-minute intensive and a ten-module course are examples of different scope, not universal definitions of viable products.
Walk through the Instagram ladder using the full source example. The starting pain is not knowing what to post. An Instagram content course names broad education. A thirty-day client-attraction calendar for local med spas narrows the audience, format and period. A service that builds the first thirty days of med-spa content designed to book consultation calls adds implementation and a stated commercial purpose. Designed to book calls is an aim, not proof that calls will occur. The source associates this progression with speed, specificity, implementation, done-for-you assets, risk reduction and faster outcomes; evaluate each benefit rather than assume the later package automatically wins.
Build the stack and match its proof
Build all seven stack components: focused core deliverable, named mechanism, useful fast-action bonus, bounded risk reversal, truthful urgency, relevant proof and a defensible price comparison. Match proof to the exact claim and metric. An illustrative testimonial in this source is not a result you may claim. Beta participation does not entitle you to a positive testimonial; analysis can demonstrate expertise without pretending to have customer outcomes.
Give each of the seven stack components an operational definition. The core deliverable is bounded work, such as the source's five-day email-sequence example; its call-booking claim needs support. The mechanism describes the method. A fast-action bonus offers immediate useful progress but does not by itself prove the whole system. Risk reversal states a remedy you can actually provide; the source's all-risk wording does not literally remove every buyer risk. Scarcity reflects real capacity or terms. The proof anchor must be authentic, including any beta relationship. The price anchor compares relevant alternatives: the source's three-thousand-dollar agency versus two-hundred-ninety-seven-dollar offer is an illustration, not verified market pricing or a RISER price. Explain scope differences before presenting a comparison.
Match proof to the actual promised result. In the source's example, great experience does not establish thirty qualified leads in thirty days; thirty-four qualified leads in twenty-eight days would address the metric and time claim if it were real, defined and documented. Those are illustrative numbers, not customer results established by this lesson. Define qualified consistently and preserve the conditions under which the result occurred. For a new entrant, the forensic-critic approach means analyzing an industry failure and showing how a proposed correction works. Analysis can demonstrate reasoning, but it is not evidence that customers have already achieved the promised outcome.
Apply the persuasion principles
The seven persuasion principles describe ways to communicate value and trust. Give useful value, invite meaningful small commitments, show relevant proof, accurately identify expertise, use a voice the audience recognizes, explain real constraints and connect through genuine shared experience. Study each source example below, while keeping the buyer free to make an informed choice. Borrowed authority requires a real relationship or accurate attribution; polarization, pressure and assumptions about identity do not replace evidence.
Name all seven persuasion principles as you apply them. Reciprocity offers genuine value; the source contrasts a workshop with a two-page PDF, but length and format alone do not determine usefulness. Commitment and consistency use meaningful small decisions, such as a quiz or assessment, while leaving room to decline. Social proof addresses the objection and exact promise. Authority requires accurate credentials, research references or media relationships. Liking should build recognition and trust; the source's polarizing attributed quotation is not a requirement to offend or an authenticated quotation here. Scarcity refers to actual capacity, launch terms or supply constraints. Unity refers to a genuine shared experience or identity, not an invented as-a-fellow claim. These are communication applications, not a guarantee of conversion.
Study the original examples, instructions and tables
Read these source details with the explanation above. Numerical claims, quotations and proposed actions retain their original status; they are not verified results or completed actions.
Phase 2: Offer Construction
★ V5: The 10-Offer Generation Method
Don’t Jump to One Offer — Generate 10, Rank, Then Commit
Forcing divergent thinking before convergent commitment prevents you from building the obvious offer
when a less obvious one is more viable. Your third-ranked idea may outperform your instinct.
For each of 10 possible offers, define: Offer Name, Target Customer, Main Problem Solved, Delivery Format, Time to Result, Price Range, Why They’d Buy, Why They’d Hesitate, and Fulfillment Difficulty.
Then rank all 10 by:
1. Fastest to validate (can you test it this week?)
2. Easiest to fulfill (can you deliver without infrastructure?)
3. Highest perceived value (does the outcome feel worth the price?)
4. Best profit margin (is the math sustainable?)
5. Lowest risk (what’s the worst case if it fails?)
6. Best long-term scaling potential (can this grow beyond 1:1?)
Pick the best 1–3 to test. Test simultaneously if possible.
• Be specific (“30 qualified leads in 30 days” beats “more leads”)
• Attach the outcome to an identity shift, not just a metric
Maximize Perceived Likelihood:
• Social proof, demonstration of method, specificity creates believability
Minimize Time Delay:
• Quick wins inside the larger transformation. “Day 3 you’ll have X”
Minimize Effort:
• Done-for-you > done-with-you > DIY. Templates and fill-in-the-blank tools
Kennedy’s “Thud Factor”
Overwhelming Psychological Weight Through Bonus Stacking
“All of THAT for THIS price?” is the reaction you’re engineering.
Pile on bonuses until the sheer volume creates an emotional response independent of any single component.
★ V5 Counterbalance: “Too Many Bonuses” Warning
The Thud Factor fails when bonuses are filler that dilutes clarity.
If the prospect can’t figure out what the CORE offer actually IS, conversions drop.
Every bonus must clearly solve a specific sub-problem. Confusion kills more sales than scarcity creates.
★ V5: The Flagship Promise Test
The Simplicity Counterbalance
The core promise must be ONE thing, simple enough that a prospect can repeat it in one sentence.
Bonuses stack around it but never compete with it.
MECHANISM REPEATABILITY TEST: Can your prospect explain HOW your offer works in one sentence?
“It’s a 5-day sprint where they write your emails for you.” = PASS
“It’s a comprehensive multi-modular system leveraging proprietary frameworks.” = FAIL
Sell “Done,” Not “How To”
Default to “done” or “intensive” rather than “course.” A 90-minute intensive where you solve their specific problem live IS minimum viable. A 10-module course is not.
★ V5: The Pain-to-Offer Transformation Ladder
How a Raw Pain Point Becomes a Winning Offer
The progression always moves toward: more specificity, more speed, more done-for-you, more niche-targeted.
Pain: “I don’t know what to post on Instagram.”
Weak Offer: “Instagram content course.”
Better: “30-Day Instagram Client Attraction Calendar For Local Med Spas.”
Strongest: “We Build Your First 30 Days Of Med Spa Instagram Content Designed To Book Consultation Calls.”
Notice the pattern: Generic education → Specific template → Done-for-you with specific outcome. The money is NOT in the information. It’s in: speed, specificity, implementation, done-for-you assets, risk reduction, and faster outcomes.
The MVO Stack: 7 Components
1. Core Deliverable
Surgically focused. “A 5-day email sequence that books calls” — not “a complete marketing system.”
2. The Mechanism
Kennedy’s “Unique Mechanism.” Name your method. “The Reverse Funnel Method.”
3. Fast-Action Bonus
Immediate value upon purchase. Quick win that proves the system works.
4. Risk Reversal
Guarantee so strong it shifts all risk to you.
5. Scarcity/Urgency
Real, ethical scarcity. No fake countdown timers.
6. Social Proof Anchor
Even one testimonial. No proof? Beta access for testimonials.
7. Price Anchor
Value relative to alternatives. “Agencies charge $3K. You get it for $297.”
★ V5: Proof Must Match the Exact Promise
Sharper Social Proof Principle
If you promise “30 qualified leads in 30 days,” a testimonial saying “Great experience!” is nearly worthless.
You need: “We got 34 qualified leads in the first 28 days.”
The proof and the promise must use the SAME metric. Match proof to the specific claim, not the category.
The Forensic Critic Positioning (For New Entrants)
If you lack social proof, position yourself as the Forensic Critic of current industry failures. Build authority through analysis, not credentials. Your MVO becomes the “Correction.”
Cialdini’s 7 Principles Applied to Offer Design
1. Reciprocity
Give genuine value before asking. A real workshop triggers powerful reciprocity. A 2-page PDF triggers weak.
2. Commitment & Consistency
Micro-commitments: quizzes, assessments. Each small yes makes the big yes easier.
3. Social Proof
Match proof to objection AND to the exact promise. Industry-specific proof for industry objections.
4. Authority
Borrowed authority: “as featured in,” “based on research from [university].”
5. Liking
Be polarizing. Kennedy: “If you haven’t offended someone by noon, you’re not marketing hard enough.”
6. Scarcity
Real scarcity only. Limited capacity, launch pricing, genuine supply constraints.
7. Unity
“As a fellow [identity], I built this because...”
Phase 3 — Write copy and a coherent follow-up sequence
Write headlines and hooks
Use the five headline patterns to generate alternatives, then the ten hook categories to test different ways into the same supported promise. The source suggests twenty-five to fifty headlines. That is a practice target, not proof that later drafts are better. A secret, authority, cost-of-inaction or transformation hook needs evidence for the claim it implies. Use the exact vocabulary buyers use when you have actually observed it; the HVAC phrase below is a source example, not a universal expression.
Practice each of the five headline structures separately: a desired outcome without a major fear; a described mechanism producing a result within a timeframe; a warning before a common action; a specific number of people in a niche achieving a result; and an invitation asking who else wants the outcome. The exact templates are retained below. The number-of-people version needs real counts, the warning needs a real concern, and a timeframe needs a supportable basis. Compare clarity and relevance across the proposed twenty-five to fifty drafts instead of assuming the source's later-drafts maxim proves quality.
Generate one version of each of the ten hook types. A pain hook names a recurring difficulty; a mistake hook identifies an actual error; a secret hook needs genuinely lesser-known information without inventing a conspiracy. A contrarian hook challenges specific advice with reasons. A speed hook states a supported timeframe. A cost-of-inaction hook needs a defensible calculation. An identity hook addresses a relevant audience without presuming private traits, and a local hook connects to a real place and problem. An authority hook requires accurate years, client counts or results. A transformation hook compares a documented before and after with clear conditions. The source's HVAC NASA ghost phrase is an illustrative language-echo example; verify that your audience actually uses a phrase before adopting it.
Develop the body copy
PASTOR gives the copy a sequence: identify the problem, explain its consequences, connect a story or solution, show the intended transformation, state the offer and make the response clear. The internal-monologue check adds four buyer questions about fear, desire, delay and safety. Answer them in plain language without claiming that satisfying a writing framework guarantees conversion.
Walk PASTOR from one stage to the next. Problem names the specific difficulty, illustrated by the source's empty inbox. Amplify considers the consequence of leaving it unresolved, using the source's twelve-month question as a discussion prompt rather than a prediction. Story or solution bridges from the difficulty to a possible route forward. Transformation describes the useful after-state; the four-leads-every-morning example is not an established result. Offer presents every component of the stack clearly. Response gives one clear next action, with accurate access steps and timing rather than automatically promising the source's three-minute access example. Then ask all four internal-monologue questions: what am I afraid of, what do I actually want, why have I put this off, and what would make this feel safe now? Check whether the copy sounds like the buyer's actual thinking. Answering the questions does not guarantee conversion despite the source's claim.
Apply all twenty-one editing triggers
Read all twenty-one triggers below as editing lenses. Specificity, curiosity, future pacing, contrast and explanation can clarify a decision. Proof, demonstration, admissions and stories can support trust when accurate. Ownership language, conversational tone, unexpected openings, follow-up and clear deadlines shape presentation. Takeaway language should explain actual fit. Do not turn presuppositions, a false close, power words or an enemy frame into fabricated certainty or pressure. The source's percentage claim about the word because is not substantiated here.
Use the first seven copy triggers to edit meaning: specificity supplies accurate detail; curiosity opens a question the content actually answers; fear of missing out describes a real consequence rather than an invented loss; future pacing offers a plausible after-state; an enemy frame identifies a problem or flawed practice without unsupported attacks; contrast clarifies meaningful before-and-after differences; and reason why explains the actual price or timing. The source's thirty-seven-leads-in-twenty-two-days phrase remains an example, not proof.
The next seven triggers address trust and presentation. A damaging admission is an honest limitation, not a staged confession. Third-party proof needs context and a valid basis. A demonstration shows the mechanism rather than merely asserting it. Ownership language helps someone imagine use without implying they have purchased. Conversational tone should stay clear. Power words such as free, new, instantly or proven carry claims whose conditions must be true. Dimensional follow-up adapts a consistent message across appropriate channels; it is not permission to contact people or proof that repetition is welcome.
The final seven triggers need equal care. Story organizes information but does not establish that every narrated fact converts better. A pattern interrupt earns attention without misleading. Presupposition must not change uncertain outcomes into promised results. The source's false-close example can introduce additional useful information, but should not fake the end of a transaction. Takeaway language explains actual fit criteria. A deadline reflects real terms. Justification gives a real reason; the source's thirty-four-percent compliance claim for because lacks a supporting study here. These twenty-one lenses help review copy, not certify a persuasive or ethical outcome by their presence alone.
Adapt copy to the channel
Adapt the asset to its channel: subject and PS tests for email; concise value and appropriate consent processes for messaging; a clear above-fold offer and mobile path on landing pages; prompt attention and refreshed creative in social; the source's five-step short-video sequence; and relevant physical or local touchpoints. Its timing, open-rate and refresh numbers are source suggestions or claims, not verified benchmarks or current platform instructions.
Keep the six channel rows distinct. The source proposes five to ten email subject lines and a prominent PS, while its claim that the PS is read more than the body remains unverified. Its SMS row proposes fewer than 160 characters and a value-first opening; the claimed ninety-five-percent open rate is not a verified benchmark, and its TCPA note does not establish which requirements apply to a particular campaign. Its landing-page layout places headline, subheadline, hero and CTA above the fold, proof within the first scroll and mobile usability throughout. Its paid-social row proposes a hook in three seconds and creative refresh every seven to fourteen days. Its short-video sequence is hook, problem, agitation, mechanism tease and CTA within a proposed thirty to sixty seconds. These are source design suggestions to evaluate, not newly verified platform rules. The physical/local row includes in-store QR codes, signage, Google Business Profile, Nextdoor, hybrid funnels and local direct mail; no listings, messages or campaigns have been created by this lesson.
Build the fourteen-day sequence
The fourteen-day table is a full sequence, not fourteen copies of the pitch. It moves from welcome and pain through consequences, mistakes, story, proof, myth correction, mechanism, offer, bonus, objections, FAQ, urgency and final recap. Write all five fields for each email: subject, preview, body, CTA and intended trigger. Adapt urgency to real terms and stop treating sequence length as evidence of likely sales. The late-contact sales percentage has no supporting study attached. This curriculum application links Brunson's follow-up journey with an offer whose value and delivery remain consistent at every contact.
For days one through seven, connect each email's job to its named source trigger. Day one welcomes and delivers a quick win for reciprocity. Day two names the situation for problem agitation. Day three considers the cost of inaction through loss aversion without inventing losses. Day four explains common mistakes to demonstrate authority. Day five uses a truthful personal story for liking and unity. Day six presents a real, relevant case study for social proof; if none exists, do not fabricate one to fill the slot. Day seven challenges a supported misconception through contrarian authority. Each message still needs its subject, preview, body, CTA and identified trigger.
For days eight through fourteen, day eight introduces the mechanism and a new opportunity through curiosity. Day nine presents the offer stack and invites a meaningful commitment. Day ten explains bonus value. Day eleven addresses the top three objections to build trust. Day twelve reframes remaining objections as FAQ questions to reduce uncertainty. Day thirteen reminds readers of an actual deadline or capacity limit. Day fourteen recaps the transformation and offers a final call only when the stated terms actually end. The last two rows use scarcity and loss aversion; an evergreen offer must not acquire a fictitious deadline merely to follow the table. Retain all five writing fields for each email. The source's claim that eighty percent of sales occur between contacts five and twelve is unsupported here, and fourteen contacts do not ensure a sale.
Study the original examples, instructions and tables
Read these source details with the explanation above. Numerical claims, quotations and proposed actions retain their original status; they are not verified results or completed actions.
Phase 3: Direct Response Copy
Kennedy Headline Formulas
• “How To [Desired Outcome] Without [Biggest Fear]”
• “The [Adjective] [Mechanism] That [Result] In [Timeframe]”
• “Warning: Don’t [Common Action] Until You [Read/See/Hear] This”
• “[Specific Number] [Niche] [People] Are Now [Doing Result] — Here’s How”
• “Who Else Wants [Desired Outcome]?”
Expert Tip
Write 25–50 headlines. The magic lives in headlines 20–50.
★ V5: The 10 Hook Types
A Categorized Taxonomy for Ads, Social, and Video
Instead of staring at a blank page, run through each type and generate a version for each.
1.Pain Hook: “Tired of [specific pain]? Here’s why it keeps happening.”
2.Mistake Hook: “The #1 mistake [niche] make with [topic] (and the easy fix).”
3.Secret Hook: “The [niche] secret that [competitors] don’t want you to know.”
4.Contrarian Hook: “Why [common advice] is actually killing your [result].”
5.Speed Hook: “How to [result] in [surprisingly short time].”
6.Cost-of-Inaction Hook: “Every day you wait, you’re losing $[amount].”
7.Identity Hook: “For [specific identity] who refuse to settle for [status quo].”
8.Local Hook: “Attention [city/region] [niche]: [specific local pain].”
9.Authority Hook: “After [number] years/clients/results, here’s what I know about [topic].”
10.Transformation Hook: “From [before state] to [after state] in [timeframe].”
Language Echoes
Insider Slang = Instant Unity
Find weird niche-specific jargon. If HVAC techs call a comm error a “NASA ghost,” use it in copy.
P.A.S.T.O.R. Body Copy Framework
P — Problem
Name it with painful specificity. “Staring at an empty inbox wondering where your next client is.”
A — Amplify
Cost of NOT solving. “If nothing changes in 12 months, what does your business look like?”
S — Story / Solution
Bridge from pain to possibility through narrative.
T — Transformation
Paint the after picture. “4 new leads every morning before your coffee gets cold.”
O — Offer
Present the full MVO stack. Every component. Stack visually.
R — Response
One clear CTA. “Click the button, fill in details, access within 3 minutes.”
★ V5: The Buyer’s Internal Monologue Check
A Complementary Copy Lens to P.A.S.T.O.R.
After writing your copy, read it through the buyer’s 4 internal questions:
1. What am I afraid of? 2. What do I actually want? 3. Why have I been putting this off?
4. What would make this feel safe right now?
If your copy answers all 4 in the buyer’s own language, it converts regardless of framework.
The test: “Does this sound like something I’d THINK, or something a marketer wrote AT me?”
The 21 Copy Triggers
1.Specificity — “37 leads in 22 days” beats “lots of leads”
2.Curiosity — Open a loop they can only close by reading on
3.Fear of Missing Out — What will they lose?
4.Future Pacing — Describe life after transformation
5.Enemy — Give them something to oppose
6.Contrast — Before/after, old way vs. new way
7.Reason Why — Explain WHY the price, WHY now
8.Damaging Admission — Admit a weakness to build trust
9.Third-Party Proof — Let others make the claim
10.Demonstration — Show the mechanism in action
11.Ownership Language — “Your new system”
12.Conversational Tone — Write like you talk
13.Power Words — Free, new, you, instantly, because, proven
14.Dimensional Follow-Up — Same message, multiple channels
15.Story — Every fact in narrative converts better
16.Pattern Interrupt — Something unexpected
17.Presupposition — “When you see results” not “If”
• In-store QR codes, physical signage with Kennedy-style copy, local GBP, Nextdoor, hybrid funnels, local direct mail.
★ V5: The 14-Day Email Sequence Architecture
The Fortune Is in the Follow-Up — Here’s the Exact Structure
For each email: write Subject Line, Preview Text, Body, CTA, and identify the Psychological Trigger used.
Day
Email Purpose
Psychological Trigger
1
Welcome + Quick Win (deliver immediate value)
Reciprocity
2
Pain Awareness (name their exact situation)
Problem Agitation
3
Cost of Inaction (project the pain forward)
Fear / Loss Aversion
4
Common Mistakes (position yourself as expert)
Authority
5
Personal Story (your origin / struggle)
Liking / Unity
6
Case Study (someone like them who succeeded)
Social Proof
7
Myth-Busting (debunk what they believe is true)
Contrarian Authority
8
New Opportunity (introduce the mechanism)
Curiosity
9
Offer Introduction (present the MVO stack)
Commitment
10
Bonus Explanation (Thud Factor via email)
Value Stacking
11
Objection Handling (address top 3 objections)
Trust Building
12
FAQ (reframe objections as questions)
Certainty
13
Urgency (deadline or scarcity reminder)
Scarcity
14
Final Call (last chance, recap transformation)
Loss Aversion
80% of sales happen between the 5th and 12th contact. Most people quit after 2 emails. This 14-day sequence ensures you’re still in the conversation when they’re ready to buy.
Phase 4 — Price the delivery model and define the terms
Interpret pricing examples
Compare the source's loss-leader, validation and premium examples against the cost and result of the actual offer. A low entry price depends on the economics of the whole journey; a higher price needs an appropriate service and evidence. Odd prices and payment plans are test ideas. The source's claimed conversion lift and universal middle-price exclusion are not proven by this file.
Read the complete pricing matrix as three source examples. The loss-leader range is $7–$47 for a market with sufficient lifetime customer value, illustrated by a $27 marketing-audit toolkit. The validation range is $97–$497 for services, coaching and B2B, illustrated by a $297 lead-generation sprint. The premium range starts at $997 and extends to $5,000 or more for consulting or enterprise, illustrated by a $2,500 revenue intensive. These ranges are not RISER prices or verified market recommendations. Relate the proposed transformation to delivery cost, scope and evidence; transformation language does not make an arbitrary price sustainable.
Notice the price inconsistencies rather than hide them: the strategy bands have gaps, and the later ascension table includes prices inside the supposedly excluded middle. Treat the ranges as examples from this document, not mandatory RISER prices. Explain any price by its terms, scope, alternatives and sustainable delivery economics.
The source compares $297 with $300 and $997 with $1,000 as odd-price examples. Its claimed 20–40% conversion increase from payment plans lacks supporting evidence here. A plan also changes collection timing and risk, so conversion alone would not settle its economics. The source's $500–$900 dead-zone claim, 14-emails-and-a-webinar explanation and instruction to price below $497 or above $997 are heuristics, not established laws of buyer behavior. The wording also leaves gaps and boundary ambiguity; do not manufacture a rule for every unlisted price. The later ascension table conflicts with that exclusion, as noted in the lesson.
Compare delivery packages
The self-serve, guided and done-with-you rows change access and labor as well as price and buyer type. Comparing their results tests different packages; it cannot isolate the effect of price alone. Keep the exact inclusions visible so buyers can compare fairly and your team can estimate contribution after delivery costs.
Compare every inclusion in the three delivery models. Self-serve at $97–$197 includes templates, video training and community for a DIY or budget-conscious buyer. Guided at $297–$497 adds live group calls and feedback for a frustrated DIYer or busy operator. Done-with-you at $997–$2,500 adds one-to-one implementation for the source's premium or emergency buyer segment. These are source package illustrations, not measured audience categories. The suggestion that the $997 package may outsell the $197 version is a hypothesis, not an observed result. Compare demand alongside delivery time, contribution and capacity; changing package, audience and price together cannot identify price as the sole cause.
Evaluate proof and claims
Use the four proof formats below to identify what you can actually demonstrate. A screenshot, video, timestamp or third-party review still needs accurate context and permission. The source calls for review of claims, guarantees, testimonials and relevant legal requirements before scaling. This lesson does not determine which laws apply or certify any terms.
Use all four proof formats deliberately: video testimonials displaying actual results, screen-share walkthroughs of real metrics, timestamped before-and-after evidence, and reviews on third-party platforms such as G2 or Trustpilot. A platform name or screenshot does not validate the underlying claim. Explain who produced the evidence, what it measures, the observation period and any relevant conditions. The source's legal section names income claims, guarantee wording, testimonial disclosures, FTC, TCPA and GDPR and recommends legal review before scaling. Its blanket all-apply wording does not establish applicability to every business or jurisdiction, and the title 2026 Standard is not an independently established standard. Current legal and platform requirements remain a separate verification task; this lesson supplies no compliance certification.
Understand each guarantee obligation
Read all five guarantee examples separately. Money-back, conditional-result, additional compensation, continued service and no-refund language distribute risk differently. The last is not simply a stronger version of the first four. Define eligibility, promised remedy, delivery capacity and actual applicable terms before offering one. The attributed claim that bolder guarantees produce fewer refunds is not supported here; no-refund wording does not by itself establish enforceability.
Explain the five guarantee examples as different obligations. A 30-day money-back example specifies a period but still needs clear operative terms. A conditional result-based refund connects a defined result and timeframe to eligibility. The better-than-money-back example combines a $297 refund with $200 in ad credit; the credit is not the same thing as an additional cash refund. The service-based example promises continued free work and $100 of compensation, creating an ongoing delivery obligation that needs a clear scope. The anti-guarantee example instead says no refunds and frames buyer seriousness; it does not remove every buyer risk or establish enforceability. The source's ladder labels and attributed fewer-refunds claim do not prove that later examples are stronger, more suitable or less costly. Treat these as terms to analyze, not ready-to-adopt policies.
Study the original examples, instructions and tables
Read these source details with the explanation above. Numerical claims, quotations and proposed actions retain their original status; they are not verified results or completed actions.
Phase 4: Pricing & Packaging
The MVO Pricing Matrix
Strategy
Price Range
Best For
Example
Loss-Leader
$7–$47
High LTV markets
$27 Marketing Audit Toolkit
Validation
$97–$497
Services, coaching, B2B
$297 Lead Gen Sprint
Premium
$997–$5,000+
Consulting, enterprise
$2,500 Revenue Intensive
→ Price to the transformation, not the deliverable.
→ Odd pricing: $297 > $300. $997 > $1,000.
→ Payment plans increase conversions 20–40% at higher price points.
The “Muddled Middle” Dead Zone
AVOID $500–$900
Too expensive for impulse, too cheap for premium. People need 14 emails and a webinar to decide.
Price below $497 or above $997.
★ V5: Three Pricing Models for the Same Offer
Test Which Positioning the Market Responds To
The same core deliverable at three price points tests three buyer segments simultaneously.
Model
Price
What’s Included
Buyer Type
Self-Serve
$97–$197
Templates + video training + community
DIY / budget-conscious
Guided
$297–$497
Everything above + live group calls + feedback
Frustrated DIYer / busy operator
Done-With-You
$997–$2,500
Everything above + 1:1 implementation
Premium / emergency buyer
Most people pick one price and hope. Testing three models reveals which segment has the most demand AND the best unit economics. You may discover the $997 version outsells the $197 version because it attracts more committed buyers.
Verifiable Social Proof (2026 Standard)
• Video testimonials showing actual results on screen
• Screen-share walkthroughs of real metrics
• Before/after with timestamps
• Third-party platforms (G2, Trustpilot)
Legal & Compliance
The Failure Point Nobody Talks About
Income claims, guarantee language, testimonial disclaimers, FTC/TCPA/GDPR all apply.
Have a lawyer review before scaling. Platform bans from Meta/Google are real.
Guarantee Engineering
Level 1: Standard Money-Back
“30-day money-back.” Baseline. Not a differentiator.
Level 2: Conditional Result-Based
“If you don’t [result] in [timeframe], full refund.”
Level 3: Better-Than-Money-Back
“Refund your $297 AND give you $200 in ad credit.”
Level 4: Service-Based (Kennedy’s Move)
“I’ll work with you free until it does, and send $100 for wasting your time.”
Level 5: Anti-Guarantee
“No refunds. For serious people only.” Powerful for premium.
Kennedy’s Guarantee Rule
“The bolder the guarantee, the fewer refunds you’ll get.”
Phase 5 — Validate the offer with interpretable evidence
Plan the initial sprint
The seven-day sprint moves from a clear offer through copy, assets, proof, channels, a limited launch and a test. Read each day's deliverables below and check its prerequisites. Creating a page or scheduling messages is not evidence of customer proof, permission, delivery readiness or a successful launch. The source's proposed outreach counts and spending actions are planning content, not actions performed by this lesson.
Explain the seven-day sprint by its actual deliverables. Day one defines the one-sentence offer, stack and price and checks Phase 8's ten rules. Day two drafts the PASTOR page, at least twenty-five headline candidates and three to five launch emails, then checks the buyer's internal questions. Day three prepares one landing page, a lead magnet and a short video when applicable. Day four proposes five to ten beta invitations and collection of real proof; the date does not create results or testimonials. Day five prepares the email/SMS workflow, three to five organic posts and payment processing. Day six proposes a soft launch to an existing list and communities plus twenty to fifty prospect messages. Day seven introduces the split test and buyer-data collection. These are source planning quantities, not outreach, purchases or automation performed by this lesson. Check readiness and applicable permissions before any operational execution.
Design an interpretable test
Test headline, price, guarantee, bonus stack and CTA according to the stated priority, while recording the question, audience, version and outcome. The source's minimum one hundred visitors per variant and twenty-percent difference do not establish statistical significance. The difference could mean relative or absolute change, and the source does not specify a confidence method. Avoid declaring a winner from that shortcut alone.
The split-test priority starts with two headline angles on the same pain, then price examples of one-hundred-ninety-seven versus two-hundred-ninety-seven dollars or two-hundred-ninety-seven versus four-hundred-ninety-seven. Next come standard versus service-based guarantees, a minimal versus full bonus stack, and Get Instant Access versus Start Your Sprint CTA wording. Decide what changes and what stays comparable before interpreting a result. The source's one-hundred-visitors-per-variant and twenty-percent-difference shortcut is not a statistical decision method. For illustration, moving from ten percent to twelve percent is a twenty-percent relative increase but only a two-percentage-point increase; the source does not say which it means. Neither calculation alone establishes confidence in a winner.
Define metrics and investigate patterns
Read every row in both metrics tables. The first covers opt-in, cold and warm sales, refunds, acquisition cost, email opens and clicks. The second covers booked calls, attendance, close rate and cost per call. Record numerator, denominator, observation window and cohort for each. Preserve the printed ranges and their gaps; compare them with your own economics rather than silently treating undefined intermediate values as passes or failures.
Read every printed viable/scale-signal pair without filling gaps by assumption. Cold opt-in is fifteen to thirty percent versus thirty percent or more; cold sale is one to three percent versus five percent or more; warm sale is five to ten percent versus twenty percent or more. Refund rate is under five percent versus under two percent. CPA relative to price is under thirty percent versus under ten percent. Email opens are twenty to thirty percent versus thirty to fifty percent, and clicks are two to five percent versus five percent or more. These are source bands, not validated RISER targets. Some touch or overlap and others leave intervals undefined. Establish the event definitions, denominator, observation period and cohort first; an apparently favorable acquisition-cost ratio also does not include every delivery cost.
For the service funnel, the source calls fifteen to twenty-five percent of page visitors booking viable and twenty-five percent or more strong. It gives sixty to seventy percent attendance versus eighty percent or more, fifteen to twenty-five percent of calls closing versus thirty percent or more, and cost per call under one hundred dollars versus under fifty. The source associates this funnel with many offers priced at nine-hundred-ninety-seven dollars or more, not all offers at that price. Define whether calls means booked, attended or qualified calls before comparing rates; that definition is not fully supplied. A low cost per call can coexist with poor fit or low contribution, so connect the measures to completed delivery and economics.
The six diagnostic arrows suggest places to investigate: distribution, offer, delivery, trust, reminders and sales conversations. They do not prove causes. For example, clicks without purchases can reflect price, traffic fit, technical failure or confusing terms as well as trust. Form a testable explanation and inspect evidence before prescribing the next action.
Use the six diagnostic mappings as hypotheses: traffic without sales suggests inspecting the offer; no traffic suggests distribution; sales with high refunds suggests delivery; clicks without sales suggests trust or guarantee terms; bookings with low attendance suggests reminders or nurture; attendance with low close rate suggests the conversation or objections. Each pattern has alternative causes, including audience fit, technical failure and unclear measurement. The source's GEO row proposes JSON-LD, citable data, named frameworks and published cases. These are source suggestions; naming a framework or adding markup does not make evidence true or guarantee search visibility.
Check calendar dependencies
The thirty-day calendar sequences observation, optimization, a second channel, a core-offer introduction, proof collection, a scaling decision and documentation. The ninety-day plan extends into retargeting, a backend offer, content and systems. Check the dependency conflict: the earlier calendar introduces an offer that later blocks still plan or build. Move according to readiness rather than dates. A suggested daily spend increase is not a universal safe rate and cannot override cash flow, capacity or evidence.
After the first week, the source allocates days eight to ten to collecting data and reading replies, eleven to fourteen to the first optimization and leading objection, fifteen to eighteen to a second traffic source, nineteen to twenty-one to introducing the core offer, twenty-two to twenty-five to real testimonials and case studies, twenty-six to twenty-eight to a scaling decision, and twenty-nine to thirty to SOPs, reporting and core-offer planning. Its do-not-change-anything instruction should not prevent correcting a serious error or honoring buyer terms. Its proposed maximum twenty-percent daily spending increase is a source heuristic, not an approved budget or a universally sustainable rate. The core-offer introduction precedes its later planning/build steps; resolve that dependency before following the dates.
The next four calendar blocks propose retargeting, an email/SMS sequence and a downsell on days thirty-one to forty-five; a buyer-informed core offer and upsell route on days forty-six to sixty; content based on converting pains and appropriately supported testimonial reuse on days sixty-one to seventy-five; and fulfilment capacity, a third channel and core-offer tests on days seventy-six to ninety. These are planning stages, not evidence that the named assets exist. Completing ninety days does not establish a validated offer or proven business. The attributed implementation maxim emphasizes action but supplies no outcome guarantee. Test clarity with a target buyer who is not a marketer: can they explain what they get, how soon and why it matters? Record their misunderstanding and revise it rather than seek praise for clever copy.
Review all nineteen failure points
Work through all nineteen failure points as a review of market, differentiation, delivery, proof, copy, distribution, follow-up, economics, customer success and clarity. Simplify what a target buyer cannot understand, but do not use sell-first or fix-live language to justify promises you cannot fulfill. Completion of a calendar is not validation. Search markup and citable information may support discovery, but cannot guarantee an AI citation. Keep the current official search guidance separate from the source's marketing claims.
Review failure points one through seven explicitly: a problem without payment evidence; an audience too broad to serve precisely; building before testing demand; an unexplained mechanism; unclear risk allocation; feature descriptions without a meaningful transformation; and dependence on one traffic source. The source's sell-first instruction does not authorize selling an undeliverable promise. Naming a five-phase system is not proof of a mechanism, a guarantee is not automatically suitable, and adding channels does not automatically solve distribution risk. Use each item to identify a concrete unanswered question.
Failure points eight through fourteen are neglected follow-up, pricing disconnected from buyer value, no suitable next offer, perfectionism that delays learning, competitor imitation without customer study, poor mobile usability and an unclear next action. The repeated eighty-percent-after-contact-five claim and seventy-percent-mobile claim are unsupported here. Value and delivery costs both matter to sustainable pricing. Ship-ugly/fix-live language cannot excuse material errors or unmet obligations. A next offer should solve an actual next problem; it is not required merely to complete a ladder. Make the CTA understandable and check that its promised path works.
Failure points fifteen through nineteen are abandoning learning after one attempt, assuming an industry exemption from all principles, unexamined legal/platform requirements, weak post-purchase experience and bonus overload. A failed offer can inform the next hypothesis, but an attributed millionaire quotation does not predict success through persistence. The source's universal-principles assertion does not erase differences between markets. Review the applicable requirements separately. Plan onboarding, customer support and useful delivery after purchase; they influence satisfaction without mechanically determining every refund or testimonial. Finally, remove a bonus that obscures the core promise or solves no distinct subproblem. This completes the source's nineteen-item checklist without treating it as proof that a business has passed.
Study the original examples, instructions and tables
Read these source details with the explanation above. Numerical claims, quotations and proposed actions retain their original status; they are not verified results or completed actions.
Phase 5: Launch & Validation
The 7-Day MVO Launch Sprint
Day 1: Crystallize
One-sentence offer. MVO stack. Price. Run the Kennedy 10 Rules Checklist (Phase 8).
Launch A/B split test. Track all metrics. Begin collecting buyer data.
Split-Test Protocol
Testing Priority:
1.Headline — Highest impact. Two angles on the same pain.
2.Price — $197 vs $297 or $297 vs $497.
3.Guarantee — Standard vs. service-based.
4.Bonus Stack — Minimal vs. full Thud Factor.
5.CTA — “Get Instant Access” vs. “Start Your Sprint.”
Minimum sample: 100 visitors per variant. Under 100 = noise. 20%+ difference = winner.
Validation Metrics
Metric
Viable
Scale Signal
Cold Opt-In
15–30%
30%+
Cold Sale
1–3%
5%+
Warm Sale
5–10%
20%+
Refund Rate
Under 5%
Under 2%
CPA vs Price
Under 30%
Under 10%
Email Open
20–30%
30–50%
Email Click
2–5%
5%+
★ V5: Service Funnel Metrics
For MVOs Sold Through Calls or Consultations
Many $997+ MVOs require a sales conversation. These metrics cover that funnel shape.
Metric
Viable
Strong
Booking Rate
15–25% of page visitors
25%+
Show-Up Rate
60–70%
80%+
Close Rate
15–25% of calls
30%+
Cost Per Call
Under $100
Under $50
Diagnostic Framework:
• Traffic, no sales → Offer problem
• No traffic → Distribution problem
• Sales, high refunds → Delivery problem
• Clicks, no sales → Trust/Guarantee problem
• Bookings, low show-up → Reminder/nurture problem
• Shows, low close → Sales script/objection problem
GEO — Generative Engine Optimization
Implement Schema Markup (JSON-LD). Include citable data, named frameworks, published case studies so AI search engines surface your offer.
The 30-Day Action Calendar
Days 8–10
Collect data. DO NOT change anything. Read every reply.
Days 11–14
First optimization. Analyze split-test. Address #1 objection.
Days 15–18
Add second traffic source. Dimensional expansion.
Days 19–21
Introduce Tier 3 (Core Offer) to existing buyers.
Days 22–25
Collect video testimonials. Update landing page. Create case studies.
Days 26–28
Scale decision. If metrics hit thresholds: increase spend 20%/day max.
Days 29–30
Document SOPs. Automate reporting. Plan Tier 3 build.
★ V5: The 90-Day Scaling Funnel
What Happens After Validation
The 30-day calendar validates. The 90-day funnel builds a business.
Days 31–45: Retargeting & Automation
Build retargeting ads for all page visitors who didn’t convert. Automate the winning email + SMS sequence. Add a downsell for people who don’t buy the main offer.
Days 46–60: Backend Offer Build
Build your Tier 3 Core Offer based on what your MVO buyers tell you they need next. Create an upsell path from MVO to Core.
Days 61–75: Content Flywheel
Launch organic content based on the pain points that converted best. Repurpose buyer testimonials into ads. Start building SEO/GEO authority.
Days 76–90: Systemize & Scale
Hire or outsource fulfillment for the MVO. Add a third traffic source. Begin testing the Core Offer. You now have a validated offer, a proven funnel, a growing list, and a backend — that’s a real business.
Kennedy’s Implementation Rule
“Implement massively or nothing happens.”
★ V5: Build to Sell, Not to Impress Marketers
Pre-Launch Validation Step
Show your offer to someone in your target market who is NOT a marketer.
If they don’t immediately understand what they get, how fast, and why they should care — simplify.
Your MVO is evaluated by whether buyers say yes, not whether other marketers think it’s clever.
The 19 Most Overlooked MVO Failure Points
1.Solving a problem nobody will pay to fix. Validate with dollars, not compliments.
2.Speaking to everyone. “Small business owners” is not a niche.
3.Building before selling. Sell first. Build second.
4.Weak mechanism. Name your method. “The 5-Phase Revenue Acceleration System.”
5.No risk reversal. Buyer carries all risk = mediocre conversions.
6.Copy that describes instead of persuades. Features tell. Transformation converts.
8.Ignoring the follow-up. 80% of sales happen after contact 5. Most quit after 2.
9.Pricing based on cost, not value. Price to the outcome.
10.No backend offer. An MVO without ascension = one-night stand.
11.Perfectionism disguised as preparation. Ship ugly. Fix live.
12.Copying competitors instead of studying customers.
13.Ignoring mobile. 70%+ see your offer on a phone.
14.No clear CTA. If they have to think, you’ve lost them.
15.Giving up after first attempt. Kennedy: “Most millionaires have a trail of failed offers.”
16.“My business is different.” The principles are universal. Every industry has buyers with pain and wallets.
17.Legal/compliance blind spots. FTC, TCPA, GDPR, platform rules. Get a lawyer before scaling.
18.★ V5: No post-purchase experience. Weak onboarding, no customer success, no delivery delight = refunds, no testimonials, zero ascension. What happens AFTER the sale determines your entire business trajectory.
19.★ V5: Too many bonuses without clarity. The Thud Factor backfires when the stack is so large the prospect can’t figure out what the core offer IS. Every bonus must solve a specific sub-problem or it’s noise.
Phase 6 — Connect the offer to distribution and continuing value
Connect the offer tiers
The five-tier table connects free value, an MVO, a core offer, premium work and continuity. Explain each tier's job before choosing a price or a next offer. This is where the curriculum's value-ladder theme meets delivery economics: continuing value should solve a relevant next problem, not conceal essentials in an upsell. The source's price bands are illustrative and do not establish current RISER pricing.
Read all five ascension tiers with their source prices and purposes. Free value builds a list and demonstrates expertise. The MVO at twenty-seven to four-hundred-ninety-seven dollars aims to convert, validate and build proof. A core offer at four-hundred-ninety-seven to five thousand dollars aims at a fuller transformation and profit. Premium work at five thousand to fifty thousand dollars or more aims to increase profit per client. Continuity at forty-seven to four-hundred-ninety-seven dollars per month aims at recurring revenue. These are source examples, not prices adopted by RISER or evidence of profitability. Revenue still has delivery costs, and each next offer should solve a real next problem. The core and continuity bands also overlap earlier pricing exclusions, so the document does not supply one internally consistent pricing rule.
Explain context before the offer
The five pre-suasion suggestions concern context before the offer: explain a supported cost, focus attention on the relevant decision, communicate authentic shared experience, make the presentation clear and ask a meaningful question. An affirmative answer to a broad question is not agreement to buy. Professional design and framing cannot substitute for a useful offer or honest evidence.
Explain all five pre-suasion examples in context. Priming presents the cost of a problem before price; the source's forty-seven-thousand-dollar loss beside a four-hundred-ninety-seven-dollar solution is illustrative and needs evidence before use. Attention channeling highlights the problem and proposed value, without hiding other decision factors. The as-founders unity example requires genuine shared experience. Environmental priming refers to professional presentation; good design does not prove premium value. Ask-then-tell begins with a broad question about deserving better results, but a yes is neither proof of need nor consent to purchase. Use questions to learn, not to manufacture agreement.
Choose and maintain distribution
Consider each of the eight channels in the direct-marketing stack: content, email, messaging, paid media, personalized outreach, physical mail, community/events and AI search. Select a portfolio the audience uses and your team can maintain. The channel-count maxim and response-rate claims are not proven forecasts. Genuine personalization requires accurate relevant information, and all communication must fit actual permission and platform requirements.
Map the eight distribution dimensions to actual work. Content includes organic social, YouTube, podcasts and blogs. Email is described as the backbone, but maintaining a list does not eliminate dependence on service providers or audience permission. SMS is positioned for urgency and local use; its ninety-five-percent open-rate claim is unverified here. Paid media lists Meta, Google, YouTube, TikTok and LinkedIn. AI-personalized outreach requires real relevant personalization, not fabricated familiarity. Physical mail's claimed five-to-ten-times email conversion and workshops' ten-to-thirty-percent conversion are unsupported source claims. Community and events need useful participation, while AI search needs accurate discoverable material; schema alone cannot guarantee citations. The one/three/five-channel maxim is rhetoric, not a strategy test. Choose channels by evidence, capacity and economics rather than by count.
Assess the proposed method changes
The twelve-row 2024/2026 comparison describes the author's preferred shifts in hooks, media, proof, copy, research, discovery, avatars, delivery, testing, local channels, pricing and follow-up. Use it to ask what improves the customer path. It does not prove that an older method stopped working or that every business needs every listed technology. The detailed rows remain below so the comparison can be assessed without reducing it to a slogan.
Work through the first six historical-comparison rows as proposed changes, not established facts about entire years. The hook row moves from a broad ten-times-leads promise to a specific system leak. The medium row adds text, voice, SMS and an AI agent to an email opt-in. The trust row prefers verifiable case studies and data to generic testimonials. The copy row proposes short direct copy and interactive questions in place of a long page. The research row adds automation and social listening to manual investigation. The discovery row adds GEO and schema to Google SEO. Specificity and evidence can clarify an offer, but no row proves that its older method is obsolete or that its proposed tool is necessary.
The remaining six comparison rows move from a static avatar document to a behavioral model; a course or PDF to an assisted intensive; launch-and-hope to early split testing; a website and Google Ads to a mix of QR codes, SMS, mail and digital paths; one price to three packages for different segments; and three emails to a fourteen-day sequence. A model is only as sound as its data, an intensive needs delivery capacity, and a split test needs interpretable evidence. A local channel mix must serve the actual audience. Three package tests change more than price, and a longer sequence does not ensure relevance or sales. Relate any chosen change to the buyer's next useful step, consistent with the curriculum's Brunson-style journey and Hormozi-style value and delivery analysis. These connections are authored teaching, not quotations or endorsements.
Study the original examples, instructions and tables
Read these source details with the explanation above. Numerical claims, quotations and proposed actions retain their original status; they are not verified results or completed actions.
Phase 6: Advanced Tactics
The Ascension Architecture
Tier
What
Price
Purpose
1
Free Value
Free
Build list, demonstrate expertise
2
MVO
$27–$497
Convert, validate, build proof
3
Core Offer
$497–$5K
Full transformation, real profit
4
Premium
$5K–$50K+
Max profit per client
5
Continuity
$47–$497/mo
Recurring revenue
Cialdini’s Pre-Suasion
→ Priming: Show cost of problem before price. $47K loss → $497 solution.
3.D3: SMS — 95%+ open rates. Best for urgency and local.
4.D4: Paid Media — Meta, Google, YouTube, TikTok, LinkedIn.
5.D5: AI-Personalized Outreach — Hyper-personalized at scale. Must be REAL.
6.D6: Physical Mail — Kennedy’s secret weapon. 5–10x email conversion.
7.D7: Community & Events — Workshops convert 10–30%.
8.D8: AI Search (GEO) — Schema markup for AI engine citations.
Rule of Three
One channel = hope. Three = strategy. Five = dominance.
2024 vs. 2026 MVO Comparison
Feature
2024
2026 State-of-the-Art
Hook
“Get 10x Leads”
“Solve the [Specific] Leak in your [Specific] System”
Medium
Email opt-in
Multi-modal (Text, Voice, SMS, AI Agent)
Trust
Generic testimonials
Verifiable video case studies + data
Copy
Long-form sales page
Short-form direct + interactive Q&A
Research
Manual browsing
Agentic automation + social listening
Discovery
Google SEO
GEO + Schema Markup for AI engines
Avatar
Static PDF
Live behavioral model from buyer data
Delivery
Course / PDF
Done-With-You Intensive / AI-assisted
Testing
Launch and hope
A/B split-test from Day 1
Local
Website + Google Ads
QR + SMS + Direct Mail + Hybrid
Pricing
One price point
3 models testing 3 buyer segments
Follow-up
3 emails
14-day sequence with psychological architecture
Phase 7 — Replace avatar assumptions with buyer evidence
Distinguish hypotheses from buyer evidence
Begin with a provisional avatar and improve it after observing buyers. The source suggests a four-hour initial limit and a second version after ten to thirty buyers. Those numbers organize work; they do not validate every inference or guarantee a representative sample. Compare who bought, who achieved the result and who needed a different solution.
Distinguish the two avatar versions by evidence. V1 is the source's time-boxed research hypothesis for copy, channels and price; V2 incorporates observed buyers after the proposed ten-to-thirty-buyer starting sample. Money changing hands supports a purchase observation, not every motive or future outcome. The source's hyper-responsive top-ten-percent segment describes people it assumes have more money and less time; neither the percentile nor the premium-buying claim is demonstrated by the file. Its attributed right-person maxim is a positioning idea, not proof that audience fit makes message quality irrelevant. Look for a segment you can serve well using actual purchase and delivery evidence.
Match support to the buyer
Read the seven buyer types and proposed formats as hypotheses about support and urgency. A beginner may need guidance; a frustrated DIY buyer may need collaboration; a busy operator may value implementation; a skeptical buyer may need evidence. Premium, emergency and cost-conscious labels do not prove willingness to pay any amount or justify exploiting urgency. Test fit through actual conversations and outcomes.
Read each of the seven proposed buyer-format pairs: a beginner gets a template and tutorial for step-by-step guidance; a frustrated DIYer gets a collaborative intensive; a busy operator gets implementation without a large learning burden; a premium buyer gets a high-touch package; an emergency buyer gets a proposed same-day or rush service; a skeptical buyer gets an audit and low-risk trial; and a cost-conscious buyer gets self-service with community. These are source hypotheses, not fixed identities. The three-courses-without-progress and dried-up-pipeline examples illustrate different support needs. Urgency does not establish unlimited budget, and the source's most-monetizable instruction must still be reconciled with actual fit and delivery capacity.
Complete all thirteen dimensions
Complete all thirteen avatar dimensions below. They cover demographic and professional context, self-description, information sources, purchase history, emotion, daily triggers, fears, decision style, objections, gathering places, triggering events and disliked language. Include the quick-decision subfield and the cited research categories. Separate what someone told you from an interpretation, especially for fears, emotion and hidden motives.
For avatar dimensions one through four, record demographic context only when relevant and supported: the source lists age, gender, location, income and education with Audience Insights and Sales Navigator as suggested sources. Professional identity records role, industry, company size and decision authority, using the proposed LinkedIn or survey evidence. Self-identity uses the buyer's own description, such as the source's scrappy-bootstrapper example, rather than assigning an identity to them. Information diet records actual podcasts, YouTube channels, newsletters and influences. The source suggests social bios and SparkToro for these latter fields, but a tool suggestion is not proof that a particular record or feature is available.
For dimensions five through nine, purchase history records what was bought, with surveys or reviews as leads; the source's most-predictive claim has no attached study. Current emotional state should distinguish the person's words from an interpretation of reviews or forum posts. Day-in-the-life captures when and how the problem occurs through direct conversation. The three fears are failure, inaction and admitting a desire; a one-star review may suggest an objection but cannot establish all three fears. Decision style records observed pace and evaluation needs rather than forcing a logic-versus-emotion stereotype. Include the exact quick-decision question: what conditions make them say yes quickly? Ask it to understand readiness, not to remove informed choice.
For dimensions ten through thirteen, the objection stack captures five to seven concrete reasons someone may decline, using competitor reviews as possible leads rather than assumed facts about your buyers. Watering holes record exact communities, groups, subreddits and conferences where relevant participation occurs. The trigger event describes what changed a someday problem into a current priority. Anti-language records words the buyer distrusts; the source's mindset-shifts and quantum-leaps examples are not universally disliked phrases. Verify their meaning in the audience's own language through interviews and negative feedback. An unanswered objection does not automatically equal a lost sale, and a trigger is not guaranteed to be the most powerful variable merely because the source says so.
Use tools and roleplay appropriately
The sixteen-row tool list describes possible research functions. Names, availability, pricing and feature claims are historical source content until checked against current providers. A tool's output is not automatically reliable evidence. The roleplay prompt is a way to generate questions after collecting real data; it must never become a fabricated interview or testimonial.
Assign the sixteen research-tool rows specific questions. SparkToro is proposed for media habits; Audience Insights for demographic interests; Sales Navigator for professional/company context; Similarweb for competitor traffic; GummySearch for Reddit patterns; AnswerThePublic for questions; Meta Ad Library for hooks; Search Console for query changes; Perplexity/Gemini for model-generated synthesis; Brandwatch/Sprout Social for listening; Hotjar/Clarity for recorded interactions; Respondent for recruitment; User Interviews for a B2B panel; Wynter for message testing; Juma/UXPressia for persona organization; and HubSpot Make My Persona for a guided template. The printed free, freemium, paid/trial and fifty-to-one-hundred-dollars-per-call labels are source pricing claims, not checked current quotes. Follow the linked status notes for access limits, including GummySearch's signup closure. Ad longevity is not proof of profit, a persona template is not validation, and model agreement is not independent corroboration.
The printed roleplay prompt asks an imagined avatar losing a specified amount per day to name three things they fear telling a stakeholder tomorrow. Retain it as a creative exercise after real data: label the persona, loss figure and answers as assumptions where appropriate. A generated emotional answer is not an interview. Use it to propose neutral follow-up questions and check them with real people instead of adding invented fears to the evidence ledger.
Validate after purchase
Validate the profile through buyer interviews, purchase data, replies, refund conversations and search behavior. Each method answers a different question. A refund can reveal a delivery failure or mismatch without establishing who should always be excluded. Clickers are different from purchasers, and high dwell-time assertions require an appropriate analytics source rather than assuming Search Console provides that measure. Record contrary evidence and update the avatar instead of selecting only confirming examples.
Apply all five post-purchase validation methods. Buyer interviews ask what was happening at purchase and what almost stopped it. Purchase analysis compares actual buyers with clickers; the claimed three-to-five-times segment difference is not a measured RISER finding. Email-reply analysis asks the main hoped-for result and categorizes each reply without discarding disagreement. Refund conversations investigate the reason, which could be delivery or expectation failure rather than proof that a person never fits. Long-tail search analysis can suggest questions to investigate, but the source's high-dwell-time hidden-avatar claim is not established by Search Console alone. Reconcile these evidence streams and record what would change the profile.
Study the original examples, instructions and tables
Read these source details with the explanation above. Numerical claims, quotations and proposed actions retain their original status; they are not verified results or completed actions.
Phase 7: The Customer Avatar
The Two-Avatar Sequence
Avatar V1: Hypothesis (Pre-MVO)
4 hours max. Directional clarity for copy, channels, price. A research guess.
Avatar V2: Validated (Post-MVO)
After 10–30 buyers. The people who buy are never exactly who you thought. A money-validated profile.
Kennedy
An imperfect message to the right person outsells a perfect message to the wrong person every time.
The Hyper-Responsive Segment
Design for the Top 10%, Not the Average
Kennedy: “Averages are for losers.” The 10% with most money and least time pay premium.
★ V5: Buyer Segmentation Types
The Same Pain Requires Different Offers for Different Buyer Types
Before locking your avatar, identify which segment you’re designing for.
Buyer Type
What They Want
Best MVO Format
Beginner
Step-by-step guidance
Template + tutorial
Frustrated DIYer
Someone to do it WITH them
Done-with-you intensive
Busy Operator
Speed, no learning curve
Done-for-you service
Premium Buyer
Best possible result, fast
High-touch VIP package
Emergency Buyer
Immediate fix, any cost
Same-day service / rush delivery
Skeptical Buyer
Proof before commitment
Free audit + low-risk trial
Cost-Conscious
Maximum value per dollar
Self-serve with community
A “Frustrated DIYer” who’s tried 3 courses wants done-with-you. An “Emergency Buyer” whose pipeline dried up wants done-for-you NOW. Design the MVO for the most monetizable segment.
The 13 Dimensions of a Complete Avatar
Our original 12 dimensions plus a critical 13th from V5:
When do they encounter the pain? What triggers it? Sources: Direct conversations.
8. The Three Fears
Fear of failure, fear of inaction, fear of admitting desire. Every fear = objection. Sources: 1-star reviews.
9. Decision-Making Style
Quick or slow? Logic or emotion? Determines funnel structure. Sub-field: ★ V5 “What makes them say yes QUICKLY?” — the specific conditions that collapse their decision timeline.
10. The Objection Stack
5–7 reasons they won’t buy. Every unanswered objection = lost sale. Sources: Competitor reviews.
11. The Watering Holes
Exact subreddits, groups, communities, conferences. Your distribution map. Sources: SparkToro.
12. The Trigger Event
What pushes “someday” to “NOW.” Most overlooked, most powerful. Sources: Direct conversations.
13. ★ V5: Words They Hate (Anti-Language)
Words and phrases that actively REPEL your avatar. If they’ve been burned by coaches promising “mindset shifts” and “quantum leaps,” those words trigger instant distrust. Knowing the anti-language is as important as knowing the insider slang. Sources: Reddit rants, negative reviews, direct interviews.
The Research Tool Stack
Tool
What It Reveals
Cost
SparkToro
Audience media diet, follows, content
Freemium
Facebook Audience Insights
Demographics, interests, affinities
Free
LinkedIn Sales Navigator
Professional identity, company data
Paid (trial)
SimilarWeb
Competitor audience, traffic sources
Freemium
GummySearch
Reddit pain tracking, upvotes
Paid
AnswerThePublic
Search queries, question hierarchies
Freemium
Meta Ad Library
Competitor hooks (long-running = profitable)
Free
Google Search Console
Intent shifts, hidden avatar data
Free
Perplexity / Gemini
AI-aggregated consensus pain points
Freemium
Brandwatch / Sprout Social
Enterprise social listening
Paid
Hotjar / Clarity
Heatmaps, session recordings
Freemium
Respondent.io
Paid interview recruitment ($50–100/call)
Paid
UserInterviews.com
B2B interview panel
Paid
Wynter
B2B message testing panels
Paid
★ V5: Juma / UXPressia
Structured persona builder tools
Freemium
★ V5: HubSpot Make My Persona
Guided avatar template builder
Free
LLM Avatar Roleplaying
AI as Creative Amplifier (Use After Real Data)
Prompt: “You are a [avatar] losing $X/day because of [problem]. What are the three things
you are terrified to tell your [stakeholder] tomorrow morning?”
Validating the Avatar (Post-MVO)
•Buyer Interviews: “What was happening when you bought? What almost stopped you?”
•Purchase Analytics: Demographics of BUYERS (not clickers). One pocket converts 3–5x.
•Email Reply Analysis: “What’s the #1 thing you hope to get?” Categorize every reply.
•Refund Interviews: Refunders tell you who your avatar is NOT.
•Search Console Long-Tail: High-dwell-time keywords = your “Hidden Avatar.”
Phase 8 — Make the final review a real decision
Set evidence-based review criteria
Work through all ten rules with evidence: offer clarity, a real reason to act, response instructions, measurement, accountable marketing, follow-up, copy quality, usable presentation, outcome measures and the proposed six-month marketing discipline. Use PASS, FAIL and NEEDS WORK to record findings, not to decorate an untested plan.
A single requested action can appear at several locations, which reconciles one CTA with the later request for multiple CTA placements. However, the failure rule is genuinely inconsistent: the opening requires fixing any failed rule before launch, while the ending prohibits launch only when more than two fail. The source also does not define what NEEDS WORK permits. Record those unresolved policy choices; a count of zero-to-two failures is not automatic launch authorization.
The source's direct-response-only spending rule is an operating philosophy, not a universal prescription. Review measurement, capacity, customer outcomes and actual business constraints before adopting it. Neither a completed checklist nor motivational language establishes a deployed system, regulatory compliance or customer results.
Walk through all ten rules
For rule one, inspect the actual offer: are the core promise, bonus purpose, guarantee terms, genuine scarcity and price comparison understandable, and do both the stack and one-sentence-promise checks hold? The presence of a bonus list does not prove value. Rule two asks for a real reason to act now, such as actual capacity, deadline or launch terms; do not invent urgency to earn a pass. Rule three asks whether the next action and its steps are unambiguous. Walk the path as a buyer would rather than relying on a button label alone.
Rule four asks about views, opt-ins, clicks, sales, refunds, acquisition cost and opens. Record which events are actually measured, their definitions and known gaps; do not claim perfect attribution because a tracking tool is installed. Rule five asks whether direct-response spending can be related to return. The source's branding-as-by-product stance is a philosophy, not proof that all useful effects can be traced to an individual dollar. Rule six asks whether the fourteen-day email and SMS architecture is in place. A written script is distinct from a configured, tested and appropriately authorized delivery system.
Rule seven checks the PASTOR sequence and all four buyer-monologue questions against the actual copy. Rule eight inspects the visible stack, price comparison, FAQ and response placements. Its proven-look and conversion-optimized labels need evidence beyond appearance; readable design and clear branding can support the same buyer task. One action repeated in several locations is a possible interpretation of the source's one-CTA versus multiple-CTAs wording, not a reason to offer conflicting next steps. Rule nine prioritizes leads, sales and return over likes or impressions; define lead quality and costs so an outcome label does not hide a weak result. Attention metrics may help diagnosis even when they are not the business objective.
Rule ten proposes six months of exclusively direct-response spending and excludes brand, awareness and untraceable campaigns. Preserve it as the source's proposed discipline, not a budget instruction adopted by RISER. For each rule select PASS, FAIL or NEEDS WORK and attach evidence, an owner and a next action; those evidence fields are authored practice. The opening says to fix any failure, while the ending blocks launch only above two failures, and NEEDS WORK has no defined consequence. Record the conflict and obtain an actual launch decision under the business's agreed criteria. The final implementation quotation does not override unresolved obligations or authorize publication.
Prepare your submission
For your submission, prepare a source-linked offer brief, the scored evidence and assumptions, ten candidate offers with a reasoned selection, complete stack and terms, copy and follow-up drafts, package economics, test plan, buyer-research record and the final review with unresolved questions and named owners. Keep sample results labeled. Use the lesson's confirmed submission route when available; otherwise retain the work in your course folder for review.
Study the original examples, instructions and tables
Read these source details with the explanation above. Numerical claims, quotations and proposed actions retain their original status; they are not verified results or completed actions.
Source-named resources: destinations and access notes
This is a partial resource review, checked September 12, 2026. These links support the source discussion; account features, prices and legal applicability are not certified. Other named references remain under review.
SparkToro — Audience research provider referenced by the source. Review current scope and plans before use.
GummySearch closure notice — Historical reference: the November 30, 2025 notice closes new signups and describes transitional access for existing customers. Do not make this a required new-student signup.
Google Search Console — Official overview of monitoring and troubleshooting a site's presence in Google Search. This does not verify the source's dwell-time inference.
LinkedIn Sales Navigator — Official sales-research product page. Plan access, data availability and suitability require an account-specific check.
HubSpot Make My Persona — Provider describes an AI persona flow and a legacy guided flow. Generated personas are hypotheses to check against real customer evidence.
Facebook Audience Insights reference — Source-named research reference. The checked destination redirected to a login/temporary-block page; current feature availability is unverified.
Similarweb — Official provider destination for the source's competitor and traffic research reference; no account data or plan tested.
AnswerThePublic — Official keyword and content-idea destination. The page exposed little readable content, so current features and access limits are unverified.
Respondent — Official research-participant recruitment destination. The source's per-call cost is not verified here.
User Interviews — Official research recruitment destination. Participant fit, fees and availability require study-specific review.
Wynter — Official B2B messaging and market-research destination; no panel, study or outcome tested.
UXPressia — Official customer-experience and journey-mapping destination. Use the provider's current materials to assess the source's persona-tool reference.
Brandwatch — Official consumer-intelligence and social-management destination. Data coverage and plan access are not verified for this course.
Sprout Social — Official social-management provider destination. Check the scope of listening and analytics in the selected plan.
Mention — Official social-listening and media-monitoring destination. No monitoring project has been created.
Hotjar / Contentsquare — The checked Hotjar address redirects to Contentsquare's Hotjar page. Preserve the historical source name and review current product/access terms.
Microsoft Clarity — Official heatmap and session-recording destination. No tracking script or site integration has been installed.
n8n — Official workflow-automation destination. The source's proposed monitoring workflow still requires design, permission and testing.
LangGraph documentation — Official overview of the agent-orchestration framework. A documentation link does not establish a working research agent.
Perplexity — Official destination referenced for research assistance. The checked page exposed minimal readable content; account features and outputs were not tested.
Google Gemini — Official destination referenced for research assistance. AI-generated themes need traceable underlying evidence; no account feature or output was tested.
Meta Ad Library — Source-named advertising research destination. The access check returned an error; current access is unverified. Ad longevity does not prove profitability.
Juma persona flow — candidate match — This provider describes an AI buyer-persona flow matching the source's general function. The source supplies no URL, so the exact intended product identity remains unconfirmed.
Udemy — Course platform named in the source research examples. A course review is a research lead, not proof that its author paid or needs your offer.
Coursera — Course platform named in the source research examples. Check the actual course and review context before drawing conclusions.
Skillshare — Course platform named in the source research examples. The official root redirects to this English destination; no student account or review access was tested.
LinkedIn Learning — Learning platform named in the source. Specific course-review availability and account access were not tested.
G2 — Software and services review platform named in the proof discussion. A platform listing alone does not substantiate your specific outcome claim.
Trustpilot — Customer-review platform named in the proof discussion. Review provenance, context and claim relevance separately.
Google Business Profile — Official local-business profile destination referenced by the source. Eligibility, ownership and account configuration were not verified.
Nextdoor Business — Official business destination for the source local-channel example. No listing, messaging or advertising was created.
Google Ads — Official advertising overview for the source paid-media discussion. No account, budget or campaign was created.
YouTube Ads — Official video-advertising destination linked from Google Business. Performance claims are not RISER forecasts.
Meta advertising — Official advertising destination named in the source; this check redirected to login. Account access and features remain unverified.
LinkedIn Ads — Official advertising destination for the source paid-media example. No targeting, account or campaign was configured.
TikTok for Business — Official advertising navigation destination. Regional availability, account eligibility and campaign functions were not tested.
FTC endorsement guidance — Official FTC staff guidance relevant to the source discussion of endorsements and testimonials. Application depends on the actual facts; this link is not a compliance determination.
FTC consumer reviews and testimonials rule FAQ — Official FTC questions and answers on its reviews/testimonials rule. Read alongside the separate endorsement guidance; the documents are not interchangeable.
FCC unwanted calls and texts guide — Official guide destination relevant to the source TCPA reference. The page could not be retrieved during this check; current contents and operational requirements remain unverified.
GDPR official regulation text — Official EUR-Lex record for Regulation (EU) 2016/679. Its availability does not establish that every provision applies to a particular RISER activity.
Acquisition.com — The Value Equation — Official Value Equation lesson destination for the Hormozi-related offer discussion. The embedded lesson was not watched; no outcome claims or downloadable materials are reproduced here.
ClickFunnels — Value Ladder explanation — Official ClickFunnels explanation connecting the Value Ladder with Russell Brunson. Its example prices, email sequence and results are not identical to the MVO playbook or adopted RISER terms.
Robert Cialdini — Seven Principles of Persuasion — Official Influence at Work overview identifying the seven principles. The playbook applications are adaptations, not authenticated quotations or a certification.
Ray Edwards — P.A.S.T.O.R. Masterclass — Author reference for P.A.S.T.O.R. The playbook uses abbreviated labels; preserve that distinction rather than attributing the framework to Kennedy or claiming this is the official masterclass.
Amazon reviews — General starting point for the source book-review research example. The source names no specific book or review; this check reached a JavaScript/robot-verification screen.
Reddit — General forum destination for the source research examples. The homepage does not validate any niche pain, quoted customer or particular discussion.
Google Search — General search destination for the source query examples. Search syntax, autocomplete suggestions and claimed intent are not verified by this homepage check.
Facebook Groups — General group destination. This check redirected to login and a temporary-block notice; no private group or post was accessed.
LinkedIn general — General professional-network destination for the source profile-research examples. Individual profiles and data access were not verified.
X/Twitter — General destination for the source social-search example. Retrieval failed; the proposed filters and date window remain unverified.
Canva — Official provider named in the source low-cost-alternative example. This check does not validate the source price or its claim that no competitive gap exists.
Instagram — General platform destination for the source med-spa offer illustration. This check redirected to login; no account or performance result was verified.
YouTube general — General video-platform destination for the source content and information-diet examples. No specific video, transcript or channel was supplied by this reference.
Claude — Official destination for the AI brand named on the source cover; the page resolves to a login/product page. This link does not authenticate the claim that the named model contributed to the playbook, its historical model version, or any generated advice.
Grok — Official destination for the AI brand named on the source cover; the public chat landing page was readable. This link does not authenticate the claim that the named model contributed to the playbook, its historical model version, or any generated advice.
ChatGPT — Official destination for the AI brand named on the source cover; the public chat landing page was readable. This link does not authenticate the claim that the named model contributed to the playbook, its historical model version, or any generated advice.
Kennedy — Magnetic Marketing publishes this bootcamp resource index, including a ten-commandments poster. This identifies a relevant primary publisher destination; it does not authenticate the playbook quotations, its adapted checklist wording, or its performance claims.
Kennedy ten-commandments poster — Poster linked by the official resource index. Retrieval returned HTTP 403, so its full text was not reviewed or imported. Retained as an explicit inaccessible reference, not as verified support for the playbook wording.
The linked tool and legal references inside the source still require current, source-specific review before operational use. The original download retains its version labels and formatting.
Expand the complete original MVO Playbook appendix and Word download
The source is retained as evidence, including its errors and embedded instructions. Read the lesson for explanations and corrections. The view below preserves paragraph and table-cell order with basic emphasis and explicit list markers from the native numbering definitions. Original pagination and fonts require the Word download; browser visual review is pending.
THE DEFINITIVE PLAYBOOK — V5
Minimum Viable Offer
The Complete Direct-Response Framework for Offers That Convert
An MVO is the smallest, fastest-to-deploy offer that validates whether a market will exchange money for the transformation you promise. It’s not about being minimal in value — it’s about being minimal in complexity while being MAXIMUM in perceived value.
Kennedy’s First Law
“The best offer wins. Not the best product. Not the best copy. The best OFFER.”
Kennedy’s Offer Architecture
1.THE STATED OFFER — What you explicitly say they get
2.THE IMPLIED OFFER — What they believe they’ll become
3.THE HIDDEN OFFER — The emotional payoff they can’t articulate
Professionals build all three layers simultaneously. Your MVO must address all three even in its simplest form.
Execution Debt
The Highest-Value Pain Category
Execution Debt: someone KNOWS the problem AND roughly knows the solution, but lacks bandwidth, courage, or clarity.
MVOs targeting Execution Debt convert highest because the buyer needs enablement, not education.
Kennedy’s 10 Smart Market Diagnosis Questions
Answer These BEFORE Any Research
Write answers to all 10 using initial desk research. 30 minutes. This gives your research direction.
1. What keeps them awake at night, staring at the ceiling?
2. What are they afraid of?
3. What are they angry about? Who are they angry at?
4. What are their top 3 daily frustrations?
5. What trends are occurring (or will occur) in their world?
6. What do they secretly desire most?
7. What are their strongest objections to buying a solution?
8. What buying triggers do they respond to?
9. What language, jargon, and slang do they use?
10. Who else is already selling to them successfully, and why?
Phase 1: Market Excavation
★ V5: Niche Viability Scoring Matrix
Before You Research Pain Points — Score the Niche Itself
Don’t build a beautifully constructed MVO for a niche that was never viable. Score first, research second.
Rate each dimension 1–10. Niches scoring under 50/70 need repositioning or should be abandoned:
Dimension
Score 1–10
What You’re Measuring
Pain Intensity
___
How severe is the core problem?
Willingness to Pay
___
Are they already spending on solutions?
Ease of Fulfillment
___
Can you deliver without massive infrastructure?
Speed to First Win
___
Can the buyer see results within days/weeks?
Competitive Advantage
___
Is there a gap you can own?
Content Opportunity
___
Can you create authority content in this space?
Offer Scalability
___
Can this grow beyond 1:1 delivery?
Diagnostic: 60–70 = Strong, test immediately. 50–59 = Viable but needs sharp positioning. 40–49 = Weak, reposition or pivot. Under 40 = Walk away.
★ V5: Define Audience by Buying Behavior, Not Identity
Critical Reframe
“Real estate agents” is an identity. “People who spend $500+/month on lead gen and are frustrated with conversion” is a buying behavior.
The first gives you a demographic. The second gives you a qualified buyer with proven willingness to spend.
Define your niche by what they BUY and DO, not just what they ARE.
Step 1: The ‘Bleeding Neck’ Audit
Core Discovery Sources:
→ Amazon Book Reviews: 1-star = what people hate. 5-star = transformation they wanted.
→ Reddit/Forum Mining: Use exact search operators (see below).
→ Google Autocomplete: Topic + “but,” “without,” “for,” “vs.”
→ Customer Support Tickets: Every complaint is an offer waiting to be born.
→ Facebook Groups: Posts with 50+ comments = emotional resonance.
→ ★ V5: Course Review Platforms: Udemy, Coursera, Skillshare, LinkedIn Learning. Reviewers PAID for education and tell you exactly where it falls short. “Too basic,” “Didn’t explain X,” “I wish it covered Y” — premium pain signals from validated buyers.
→ ★ V5: Frontline Staff Observations (Brick-and-Mortar): Receptionists, technicians, and reps hear unfiltered customer pain daily. A 30-min staff debrief surfaces pain points no Reddit mining will find.
→ ★ V5: E-Commerce Data: Cart abandonment analytics, chargeback reasons, and return/refund reasons. Direct behavioral evidence of where the buying experience breaks.
Exact Search Operators:
site:reddit.com "[niche] sucks" OR "[niche] hate" OR "struggling with [niche]"
site:reddit.com "[niche]" "waste of money" OR "frustrated" OR "can't figure out"
•Ad Transparency: Meta Ad Library — ads running 6+ months = profitable pain point
★ V5: Three Kill Filters (Before You Proceed)
If Any of These Are True — Walk Away
These kill signals save you from building an MVO for a pain point that will never monetize.
☠ Kill Filter 1: “Cheap to Ignore”
Can the buyer live with this problem at near-zero cost? If ugly invoices, messy desks, or imperfect processes don’t cost them real money, time, or status — they’ll tolerate it forever. No MVO can sell relief from a pain that’s free to endure.
Even if the pain is severe, if your solution requires them to fundamentally rewire their habits or workflow, adoption collapses. A brilliant CRM for contractors who hate using CRMs will fail. The implementation barrier becomes the real objection.
☠ Kill Filter 3: “Existing Solution Already Excellent AND Cheap”
If Canva already solves the design problem well at $12/month, there’s no gap. We talk about competitive gaps — this is the explicit signal that no gap exists. Don’t compete where the market is already well-served cheaply.
★ V5: Cheap Pain vs. Premium Pain
Cheap Pain (Avoid)
Premium Pain (Pursue)
“I need a logo”
“I need more booked appointments”
“I need more followers”
“I need qualified leads”
“I want motivation”
“I need to pass inspection”
“I need content ideas”
“I need to reduce employee turnover”
“I want to learn marketing”
“I need to stop losing customers”
Premium pain always connects to: Make money, save money, save time, avoid risk, avoid embarrassment, increase status, protect business, create certainty.
Desire Mapping Framework
Level
What They Say
What It Means
Surface
“I want to lose 20 lbs”
Stated rational goal
Real
“I want to feel attractive again”
Emotional driver
Hidden
“I want people to envy me”
Drives premium buying
Competitive Gap Analysis — 5-Gap Framework
1.SPEED — Deliver the result faster?
2.RISK — Remove more risk from the buyer?
3.SPECIFICITY — Serve a narrower audience better?
4.ACCESS — Offer more direct access to expertise?
5.FORMAT — Deliver in a way nobody else does?
★ V5: The 6-Score Monetization Filter
Replaces Our Previous 5-Filter System — More Structured, with Hard Cutoff
Score each pain point 1–5 on six dimensions. Maximum: 30. Only keep pain points scoring 22+.
Dimension
Score 1–5
Question
Urgency
___
Do they need it NOW, not someday?
Spending Proof
___
Are they already paying for solutions?
Frequency
___
Does this pain appear often across sources?
Value
___
Is solving it worth real money to them?
Simplicity
___
Can the result be explained in one sentence?
Fulfillment
___
Can you actually deliver without chaos?
“Simplicity” and “Fulfillment” are the new additions. They catch two failure modes: offers too complex to explain and offers that are nightmares to deliver.
Pain Point Category Balancing
Enforce diversity across 4 categories. Don’t find 20 variations of the same pain:
Embarrassment, imposter syndrome, fear of failure, peer comparison
Process/Support
5 points
Bad tools, poor support, complex workflows, integration failures
Evidence Tagging Format
For each of your top 20, document three pieces of evidence:
1.Verbatim Quote — Exact language from a real person. This becomes copy.
2.Monetization Proof — Evidence they already pay to solve it.
3.GEO Angle — How people phrase this to AI search engines.
Phase 2: Offer Construction
★ V5: The 10-Offer Generation Method
Don’t Jump to One Offer — Generate 10, Rank, Then Commit
Forcing divergent thinking before convergent commitment prevents you from building the obvious offer
when a less obvious one is more viable. Your third-ranked idea may outperform your instinct.
For each of 10 possible offers, define: Offer Name, Target Customer, Main Problem Solved, Delivery Format, Time to Result, Price Range, Why They’d Buy, Why They’d Hesitate, and Fulfillment Difficulty.
Then rank all 10 by:
1. Fastest to validate (can you test it this week?)
2. Easiest to fulfill (can you deliver without infrastructure?)
3. Highest perceived value (does the outcome feel worth the price?)
4. Best profit margin (is the math sustainable?)
5. Lowest risk (what’s the worst case if it fails?)
6. Best long-term scaling potential (can this grow beyond 1:1?)
Pick the best 1–3 to test. Test simultaneously if possible.
• Be specific (“30 qualified leads in 30 days” beats “more leads”)
• Attach the outcome to an identity shift, not just a metric
Maximize Perceived Likelihood:
• Social proof, demonstration of method, specificity creates believability
Minimize Time Delay:
• Quick wins inside the larger transformation. “Day 3 you’ll have X”
Minimize Effort:
• Done-for-you > done-with-you > DIY. Templates and fill-in-the-blank tools
Kennedy’s “Thud Factor”
Overwhelming Psychological Weight Through Bonus Stacking
“All of THAT for THIS price?” is the reaction you’re engineering.
Pile on bonuses until the sheer volume creates an emotional response independent of any single component.
★ V5 Counterbalance: “Too Many Bonuses” Warning
The Thud Factor fails when bonuses are filler that dilutes clarity.
If the prospect can’t figure out what the CORE offer actually IS, conversions drop.
Every bonus must clearly solve a specific sub-problem. Confusion kills more sales than scarcity creates.
★ V5: The Flagship Promise Test
The Simplicity Counterbalance
The core promise must be ONE thing, simple enough that a prospect can repeat it in one sentence.
Bonuses stack around it but never compete with it.
MECHANISM REPEATABILITY TEST: Can your prospect explain HOW your offer works in one sentence?
“It’s a 5-day sprint where they write your emails for you.” = PASS
“It’s a comprehensive multi-modular system leveraging proprietary frameworks.” = FAIL
Sell “Done,” Not “How To”
Default to “done” or “intensive” rather than “course.” A 90-minute intensive where you solve their specific problem live IS minimum viable. A 10-module course is not.
★ V5: The Pain-to-Offer Transformation Ladder
How a Raw Pain Point Becomes a Winning Offer
The progression always moves toward: more specificity, more speed, more done-for-you, more niche-targeted.
Pain: “I don’t know what to post on Instagram.”
Weak Offer: “Instagram content course.”
Better: “30-Day Instagram Client Attraction Calendar For Local Med Spas.”
Strongest: “We Build Your First 30 Days Of Med Spa Instagram Content Designed To Book Consultation Calls.”
Notice the pattern: Generic education → Specific template → Done-for-you with specific outcome. The money is NOT in the information. It’s in: speed, specificity, implementation, done-for-you assets, risk reduction, and faster outcomes.
The MVO Stack: 7 Components
1. Core Deliverable
Surgically focused. “A 5-day email sequence that books calls” — not “a complete marketing system.”
2. The Mechanism
Kennedy’s “Unique Mechanism.” Name your method. “The Reverse Funnel Method.”
3. Fast-Action Bonus
Immediate value upon purchase. Quick win that proves the system works.
4. Risk Reversal
Guarantee so strong it shifts all risk to you.
5. Scarcity/Urgency
Real, ethical scarcity. No fake countdown timers.
6. Social Proof Anchor
Even one testimonial. No proof? Beta access for testimonials.
7. Price Anchor
Value relative to alternatives. “Agencies charge $3K. You get it for $297.”
★ V5: Proof Must Match the Exact Promise
Sharper Social Proof Principle
If you promise “30 qualified leads in 30 days,” a testimonial saying “Great experience!” is nearly worthless.
You need: “We got 34 qualified leads in the first 28 days.”
The proof and the promise must use the SAME metric. Match proof to the specific claim, not the category.
The Forensic Critic Positioning (For New Entrants)
If you lack social proof, position yourself as the Forensic Critic of current industry failures. Build authority through analysis, not credentials. Your MVO becomes the “Correction.”
Cialdini’s 7 Principles Applied to Offer Design
1. Reciprocity
Give genuine value before asking. A real workshop triggers powerful reciprocity. A 2-page PDF triggers weak.
2. Commitment & Consistency
Micro-commitments: quizzes, assessments. Each small yes makes the big yes easier.
3. Social Proof
Match proof to objection AND to the exact promise. Industry-specific proof for industry objections.
4. Authority
Borrowed authority: “as featured in,” “based on research from [university].”
5. Liking
Be polarizing. Kennedy: “If you haven’t offended someone by noon, you’re not marketing hard enough.”
6. Scarcity
Real scarcity only. Limited capacity, launch pricing, genuine supply constraints.
7. Unity
“As a fellow [identity], I built this because...”
Phase 3: Direct Response Copy
Kennedy Headline Formulas
• “How To [Desired Outcome] Without [Biggest Fear]”
• “The [Adjective] [Mechanism] That [Result] In [Timeframe]”
• “Warning: Don’t [Common Action] Until You [Read/See/Hear] This”
• “[Specific Number] [Niche] [People] Are Now [Doing Result] — Here’s How”
• “Who Else Wants [Desired Outcome]?”
Expert Tip
Write 25–50 headlines. The magic lives in headlines 20–50.
★ V5: The 10 Hook Types
A Categorized Taxonomy for Ads, Social, and Video
Instead of staring at a blank page, run through each type and generate a version for each.
1.Pain Hook: “Tired of [specific pain]? Here’s why it keeps happening.”
2.Mistake Hook: “The #1 mistake [niche] make with [topic] (and the easy fix).”
3.Secret Hook: “The [niche] secret that [competitors] don’t want you to know.”
4.Contrarian Hook: “Why [common advice] is actually killing your [result].”
5.Speed Hook: “How to [result] in [surprisingly short time].”
6.Cost-of-Inaction Hook: “Every day you wait, you’re losing $[amount].”
7.Identity Hook: “For [specific identity] who refuse to settle for [status quo].”
8.Local Hook: “Attention [city/region] [niche]: [specific local pain].”
9.Authority Hook: “After [number] years/clients/results, here’s what I know about [topic].”
10.Transformation Hook: “From [before state] to [after state] in [timeframe].”
Language Echoes
Insider Slang = Instant Unity
Find weird niche-specific jargon. If HVAC techs call a comm error a “NASA ghost,” use it in copy.
P.A.S.T.O.R. Body Copy Framework
P — Problem
Name it with painful specificity. “Staring at an empty inbox wondering where your next client is.”
A — Amplify
Cost of NOT solving. “If nothing changes in 12 months, what does your business look like?”
S — Story / Solution
Bridge from pain to possibility through narrative.
T — Transformation
Paint the after picture. “4 new leads every morning before your coffee gets cold.”
O — Offer
Present the full MVO stack. Every component. Stack visually.
R — Response
One clear CTA. “Click the button, fill in details, access within 3 minutes.”
★ V5: The Buyer’s Internal Monologue Check
A Complementary Copy Lens to P.A.S.T.O.R.
After writing your copy, read it through the buyer’s 4 internal questions:
1. What am I afraid of? 2. What do I actually want? 3. Why have I been putting this off?
4. What would make this feel safe right now?
If your copy answers all 4 in the buyer’s own language, it converts regardless of framework.
The test: “Does this sound like something I’d THINK, or something a marketer wrote AT me?”
The 21 Copy Triggers
1.Specificity — “37 leads in 22 days” beats “lots of leads”
2.Curiosity — Open a loop they can only close by reading on
3.Fear of Missing Out — What will they lose?
4.Future Pacing — Describe life after transformation
5.Enemy — Give them something to oppose
6.Contrast — Before/after, old way vs. new way
7.Reason Why — Explain WHY the price, WHY now
8.Damaging Admission — Admit a weakness to build trust
9.Third-Party Proof — Let others make the claim
10.Demonstration — Show the mechanism in action
11.Ownership Language — “Your new system”
12.Conversational Tone — Write like you talk
13.Power Words — Free, new, you, instantly, because, proven
14.Dimensional Follow-Up — Same message, multiple channels
15.Story — Every fact in narrative converts better
16.Pattern Interrupt — Something unexpected
17.Presupposition — “When you see results” not “If”
• In-store QR codes, physical signage with Kennedy-style copy, local GBP, Nextdoor, hybrid funnels, local direct mail.
★ V5: The 14-Day Email Sequence Architecture
The Fortune Is in the Follow-Up — Here’s the Exact Structure
For each email: write Subject Line, Preview Text, Body, CTA, and identify the Psychological Trigger used.
Day
Email Purpose
Psychological Trigger
1
Welcome + Quick Win (deliver immediate value)
Reciprocity
2
Pain Awareness (name their exact situation)
Problem Agitation
3
Cost of Inaction (project the pain forward)
Fear / Loss Aversion
4
Common Mistakes (position yourself as expert)
Authority
5
Personal Story (your origin / struggle)
Liking / Unity
6
Case Study (someone like them who succeeded)
Social Proof
7
Myth-Busting (debunk what they believe is true)
Contrarian Authority
8
New Opportunity (introduce the mechanism)
Curiosity
9
Offer Introduction (present the MVO stack)
Commitment
10
Bonus Explanation (Thud Factor via email)
Value Stacking
11
Objection Handling (address top 3 objections)
Trust Building
12
FAQ (reframe objections as questions)
Certainty
13
Urgency (deadline or scarcity reminder)
Scarcity
14
Final Call (last chance, recap transformation)
Loss Aversion
80% of sales happen between the 5th and 12th contact. Most people quit after 2 emails. This 14-day sequence ensures you’re still in the conversation when they’re ready to buy.
Phase 4: Pricing & Packaging
The MVO Pricing Matrix
Strategy
Price Range
Best For
Example
Loss-Leader
$7–$47
High LTV markets
$27 Marketing Audit Toolkit
Validation
$97–$497
Services, coaching, B2B
$297 Lead Gen Sprint
Premium
$997–$5,000+
Consulting, enterprise
$2,500 Revenue Intensive
→ Price to the transformation, not the deliverable.
→ Odd pricing: $297 > $300. $997 > $1,000.
→ Payment plans increase conversions 20–40% at higher price points.
The “Muddled Middle” Dead Zone
AVOID $500–$900
Too expensive for impulse, too cheap for premium. People need 14 emails and a webinar to decide.
Price below $497 or above $997.
★ V5: Three Pricing Models for the Same Offer
Test Which Positioning the Market Responds To
The same core deliverable at three price points tests three buyer segments simultaneously.
Model
Price
What’s Included
Buyer Type
Self-Serve
$97–$197
Templates + video training + community
DIY / budget-conscious
Guided
$297–$497
Everything above + live group calls + feedback
Frustrated DIYer / busy operator
Done-With-You
$997–$2,500
Everything above + 1:1 implementation
Premium / emergency buyer
Most people pick one price and hope. Testing three models reveals which segment has the most demand AND the best unit economics. You may discover the $997 version outsells the $197 version because it attracts more committed buyers.
Verifiable Social Proof (2026 Standard)
• Video testimonials showing actual results on screen
• Screen-share walkthroughs of real metrics
• Before/after with timestamps
• Third-party platforms (G2, Trustpilot)
Legal & Compliance
The Failure Point Nobody Talks About
Income claims, guarantee language, testimonial disclaimers, FTC/TCPA/GDPR all apply.
Have a lawyer review before scaling. Platform bans from Meta/Google are real.
Guarantee Engineering
Level 1: Standard Money-Back
“30-day money-back.” Baseline. Not a differentiator.
Level 2: Conditional Result-Based
“If you don’t [result] in [timeframe], full refund.”
Level 3: Better-Than-Money-Back
“Refund your $297 AND give you $200 in ad credit.”
Level 4: Service-Based (Kennedy’s Move)
“I’ll work with you free until it does, and send $100 for wasting your time.”
Level 5: Anti-Guarantee
“No refunds. For serious people only.” Powerful for premium.
Kennedy’s Guarantee Rule
“The bolder the guarantee, the fewer refunds you’ll get.”
Phase 5: Launch & Validation
The 7-Day MVO Launch Sprint
Day 1: Crystallize
One-sentence offer. MVO stack. Price. Run the Kennedy 10 Rules Checklist (Phase 8).
Launch A/B split test. Track all metrics. Begin collecting buyer data.
Split-Test Protocol
Testing Priority:
1.Headline — Highest impact. Two angles on the same pain.
2.Price — $197 vs $297 or $297 vs $497.
3.Guarantee — Standard vs. service-based.
4.Bonus Stack — Minimal vs. full Thud Factor.
5.CTA — “Get Instant Access” vs. “Start Your Sprint.”
Minimum sample: 100 visitors per variant. Under 100 = noise. 20%+ difference = winner.
Validation Metrics
Metric
Viable
Scale Signal
Cold Opt-In
15–30%
30%+
Cold Sale
1–3%
5%+
Warm Sale
5–10%
20%+
Refund Rate
Under 5%
Under 2%
CPA vs Price
Under 30%
Under 10%
Email Open
20–30%
30–50%
Email Click
2–5%
5%+
★ V5: Service Funnel Metrics
For MVOs Sold Through Calls or Consultations
Many $997+ MVOs require a sales conversation. These metrics cover that funnel shape.
Metric
Viable
Strong
Booking Rate
15–25% of page visitors
25%+
Show-Up Rate
60–70%
80%+
Close Rate
15–25% of calls
30%+
Cost Per Call
Under $100
Under $50
Diagnostic Framework:
• Traffic, no sales → Offer problem
• No traffic → Distribution problem
• Sales, high refunds → Delivery problem
• Clicks, no sales → Trust/Guarantee problem
• Bookings, low show-up → Reminder/nurture problem
• Shows, low close → Sales script/objection problem
GEO — Generative Engine Optimization
Implement Schema Markup (JSON-LD). Include citable data, named frameworks, published case studies so AI search engines surface your offer.
The 30-Day Action Calendar
Days 8–10
Collect data. DO NOT change anything. Read every reply.
Days 11–14
First optimization. Analyze split-test. Address #1 objection.
Days 15–18
Add second traffic source. Dimensional expansion.
Days 19–21
Introduce Tier 3 (Core Offer) to existing buyers.
Days 22–25
Collect video testimonials. Update landing page. Create case studies.
Days 26–28
Scale decision. If metrics hit thresholds: increase spend 20%/day max.
Days 29–30
Document SOPs. Automate reporting. Plan Tier 3 build.
★ V5: The 90-Day Scaling Funnel
What Happens After Validation
The 30-day calendar validates. The 90-day funnel builds a business.
Days 31–45: Retargeting & Automation
Build retargeting ads for all page visitors who didn’t convert. Automate the winning email + SMS sequence. Add a downsell for people who don’t buy the main offer.
Days 46–60: Backend Offer Build
Build your Tier 3 Core Offer based on what your MVO buyers tell you they need next. Create an upsell path from MVO to Core.
Days 61–75: Content Flywheel
Launch organic content based on the pain points that converted best. Repurpose buyer testimonials into ads. Start building SEO/GEO authority.
Days 76–90: Systemize & Scale
Hire or outsource fulfillment for the MVO. Add a third traffic source. Begin testing the Core Offer. You now have a validated offer, a proven funnel, a growing list, and a backend — that’s a real business.
Kennedy’s Implementation Rule
“Implement massively or nothing happens.”
★ V5: Build to Sell, Not to Impress Marketers
Pre-Launch Validation Step
Show your offer to someone in your target market who is NOT a marketer.
If they don’t immediately understand what they get, how fast, and why they should care — simplify.
Your MVO is evaluated by whether buyers say yes, not whether other marketers think it’s clever.
The 19 Most Overlooked MVO Failure Points
1.Solving a problem nobody will pay to fix. Validate with dollars, not compliments.
2.Speaking to everyone. “Small business owners” is not a niche.
3.Building before selling. Sell first. Build second.
4.Weak mechanism. Name your method. “The 5-Phase Revenue Acceleration System.”
5.No risk reversal. Buyer carries all risk = mediocre conversions.
6.Copy that describes instead of persuades. Features tell. Transformation converts.
8.Ignoring the follow-up. 80% of sales happen after contact 5. Most quit after 2.
9.Pricing based on cost, not value. Price to the outcome.
10.No backend offer. An MVO without ascension = one-night stand.
11.Perfectionism disguised as preparation. Ship ugly. Fix live.
12.Copying competitors instead of studying customers.
13.Ignoring mobile. 70%+ see your offer on a phone.
14.No clear CTA. If they have to think, you’ve lost them.
15.Giving up after first attempt. Kennedy: “Most millionaires have a trail of failed offers.”
16.“My business is different.” The principles are universal. Every industry has buyers with pain and wallets.
17.Legal/compliance blind spots. FTC, TCPA, GDPR, platform rules. Get a lawyer before scaling.
18.★ V5: No post-purchase experience. Weak onboarding, no customer success, no delivery delight = refunds, no testimonials, zero ascension. What happens AFTER the sale determines your entire business trajectory.
19.★ V5: Too many bonuses without clarity. The Thud Factor backfires when the stack is so large the prospect can’t figure out what the core offer IS. Every bonus must solve a specific sub-problem or it’s noise.
Phase 6: Advanced Tactics
The Ascension Architecture
Tier
What
Price
Purpose
1
Free Value
Free
Build list, demonstrate expertise
2
MVO
$27–$497
Convert, validate, build proof
3
Core Offer
$497–$5K
Full transformation, real profit
4
Premium
$5K–$50K+
Max profit per client
5
Continuity
$47–$497/mo
Recurring revenue
Cialdini’s Pre-Suasion
→ Priming: Show cost of problem before price. $47K loss → $497 solution.
3.D3: SMS — 95%+ open rates. Best for urgency and local.
4.D4: Paid Media — Meta, Google, YouTube, TikTok, LinkedIn.
5.D5: AI-Personalized Outreach — Hyper-personalized at scale. Must be REAL.
6.D6: Physical Mail — Kennedy’s secret weapon. 5–10x email conversion.
7.D7: Community & Events — Workshops convert 10–30%.
8.D8: AI Search (GEO) — Schema markup for AI engine citations.
Rule of Three
One channel = hope. Three = strategy. Five = dominance.
2024 vs. 2026 MVO Comparison
Feature
2024
2026 State-of-the-Art
Hook
“Get 10x Leads”
“Solve the [Specific] Leak in your [Specific] System”
Medium
Email opt-in
Multi-modal (Text, Voice, SMS, AI Agent)
Trust
Generic testimonials
Verifiable video case studies + data
Copy
Long-form sales page
Short-form direct + interactive Q&A
Research
Manual browsing
Agentic automation + social listening
Discovery
Google SEO
GEO + Schema Markup for AI engines
Avatar
Static PDF
Live behavioral model from buyer data
Delivery
Course / PDF
Done-With-You Intensive / AI-assisted
Testing
Launch and hope
A/B split-test from Day 1
Local
Website + Google Ads
QR + SMS + Direct Mail + Hybrid
Pricing
One price point
3 models testing 3 buyer segments
Follow-up
3 emails
14-day sequence with psychological architecture
Phase 7: The Customer Avatar
The Two-Avatar Sequence
Avatar V1: Hypothesis (Pre-MVO)
4 hours max. Directional clarity for copy, channels, price. A research guess.
Avatar V2: Validated (Post-MVO)
After 10–30 buyers. The people who buy are never exactly who you thought. A money-validated profile.
Kennedy
An imperfect message to the right person outsells a perfect message to the wrong person every time.
The Hyper-Responsive Segment
Design for the Top 10%, Not the Average
Kennedy: “Averages are for losers.” The 10% with most money and least time pay premium.
★ V5: Buyer Segmentation Types
The Same Pain Requires Different Offers for Different Buyer Types
Before locking your avatar, identify which segment you’re designing for.
Buyer Type
What They Want
Best MVO Format
Beginner
Step-by-step guidance
Template + tutorial
Frustrated DIYer
Someone to do it WITH them
Done-with-you intensive
Busy Operator
Speed, no learning curve
Done-for-you service
Premium Buyer
Best possible result, fast
High-touch VIP package
Emergency Buyer
Immediate fix, any cost
Same-day service / rush delivery
Skeptical Buyer
Proof before commitment
Free audit + low-risk trial
Cost-Conscious
Maximum value per dollar
Self-serve with community
A “Frustrated DIYer” who’s tried 3 courses wants done-with-you. An “Emergency Buyer” whose pipeline dried up wants done-for-you NOW. Design the MVO for the most monetizable segment.
The 13 Dimensions of a Complete Avatar
Our original 12 dimensions plus a critical 13th from V5:
When do they encounter the pain? What triggers it? Sources: Direct conversations.
8. The Three Fears
Fear of failure, fear of inaction, fear of admitting desire. Every fear = objection. Sources: 1-star reviews.
9. Decision-Making Style
Quick or slow? Logic or emotion? Determines funnel structure. Sub-field: ★ V5 “What makes them say yes QUICKLY?” — the specific conditions that collapse their decision timeline.
10. The Objection Stack
5–7 reasons they won’t buy. Every unanswered objection = lost sale. Sources: Competitor reviews.
11. The Watering Holes
Exact subreddits, groups, communities, conferences. Your distribution map. Sources: SparkToro.
12. The Trigger Event
What pushes “someday” to “NOW.” Most overlooked, most powerful. Sources: Direct conversations.
13. ★ V5: Words They Hate (Anti-Language)
Words and phrases that actively REPEL your avatar. If they’ve been burned by coaches promising “mindset shifts” and “quantum leaps,” those words trigger instant distrust. Knowing the anti-language is as important as knowing the insider slang. Sources: Reddit rants, negative reviews, direct interviews.
The Research Tool Stack
Tool
What It Reveals
Cost
SparkToro
Audience media diet, follows, content
Freemium
Facebook Audience Insights
Demographics, interests, affinities
Free
LinkedIn Sales Navigator
Professional identity, company data
Paid (trial)
SimilarWeb
Competitor audience, traffic sources
Freemium
GummySearch
Reddit pain tracking, upvotes
Paid
AnswerThePublic
Search queries, question hierarchies
Freemium
Meta Ad Library
Competitor hooks (long-running = profitable)
Free
Google Search Console
Intent shifts, hidden avatar data
Free
Perplexity / Gemini
AI-aggregated consensus pain points
Freemium
Brandwatch / Sprout Social
Enterprise social listening
Paid
Hotjar / Clarity
Heatmaps, session recordings
Freemium
Respondent.io
Paid interview recruitment ($50–100/call)
Paid
UserInterviews.com
B2B interview panel
Paid
Wynter
B2B message testing panels
Paid
★ V5: Juma / UXPressia
Structured persona builder tools
Freemium
★ V5: HubSpot Make My Persona
Guided avatar template builder
Free
LLM Avatar Roleplaying
AI as Creative Amplifier (Use After Real Data)
Prompt: “You are a [avatar] losing $X/day because of [problem]. What are the three things
you are terrified to tell your [stakeholder] tomorrow morning?”
Validating the Avatar (Post-MVO)
•Buyer Interviews: “What was happening when you bought? What almost stopped you?”
•Purchase Analytics: Demographics of BUYERS (not clickers). One pocket converts 3–5x.
•Email Reply Analysis: “What’s the #1 thing you hope to get?” Categorize every reply.
•Refund Interviews: Refunders tell you who your avatar is NOT.
•Search Console Long-Tail: High-dwell-time keywords = your “Hidden Avatar.”
Measuring by sales/leads/ROI? Not vanity metrics (likes, impressions)?
☐ PASS ☐ FAIL ☐ NEEDS WORK
Rule 10: Direct-Marketing Diet for 6 Months
Every dollar to direct-response? No brand campaigns, awareness plays, or untraceable marketing?
☐ PASS ☐ FAIL ☐ NEEDS WORK
Final Warning
If more than 2 rules show “Fail,” do NOT launch until fixed.
Kennedy: “Implement massively or nothing happens.” But implement RIGHT, not just fast.
word/header1.xml
MVO PLAYBOOK V3 Contents
word/header2.xml
MVO PLAYBOOK V3 The MVO Philosophy
word/header3.xml
MVO PLAYBOOK V3 Phase 1: Market Excavation
word/header4.xml
MVO PLAYBOOK V3 Phase 2: Offer Construction
word/header5.xml
MVO PLAYBOOK V3 Phase 3: Direct Response Copy
word/header6.xml
MVO PLAYBOOK V3 Phase 4: Pricing & Packaging
word/header7.xml
MVO PLAYBOOK V3 Phase 5: Launch & Validation
word/header8.xml
MVO PLAYBOOK V3 Phase 6: Advanced Tactics
word/header9.xml
MVO PLAYBOOK V3 Phase 7: Customer Avatar
word/header10.xml
MVO PLAYBOOK V3 Phase 8: Kennedy’s 10 Rules
word/footer1.xml
Page PAGE
word/footer2.xml
Page PAGE
word/footer3.xml
Page PAGE
word/footer4.xml
Page PAGE
word/footer5.xml
Page PAGE
word/footer6.xml
Page PAGE
word/footer7.xml
Page PAGE
word/footer8.xml
Page PAGE
word/footer9.xml
Page PAGE
word/footer10.xml
Page PAGE
word/footnotes.xml
word/endnotes.xml
word/comments.xml
Exact extracted text record by paragraph and document part
{
"body_paragraphs": [
"",
"THE DEFINITIVE PLAYBOOK — V5",
"Minimum Viable Offer",
"",
"The Complete Direct-Response Framework for Offers That Convert",
"Kennedy × Cialdini × Hormozi × 2026 Agentic Commerce × GEO",
"Synthesized from Claude, Gemini, Grok, ChatGPT & Perplexity",
"40+ expert frameworks • 25 new additions • 9 phases • Field-tested",
"",
"2026 Edition — Version 5.0",
"",
"Table of Contents",
"◆ The MVO Philosophy",
"Offer Architecture, Execution Debt, Kennedy’s 10 Diagnostic Questions",
"◆ Phase 1: Market Excavation",
"Niche Viability Scoring, Kill Filters, Pain Discovery, 6-Score Filter, Category Balancing, Evidence Tagging",
"◆ Phase 2: Offer Construction",
"10-Offer Ranking, Thud Factor, Flagship Promise Test, Pain-to-Offer Ladder, Cialdini’s 7 Principles",
"◆ Phase 3: Direct Response Copy",
"P.A.S.T.O.R., 10 Hook Types, 21 Triggers, 14-Day Email Sequence, Buyer’s Internal Monologue",
"◆ Phase 4: Pricing & Packaging",
"Pricing Matrix, Muddled Middle, 3 Pricing Models, Guarantee Engineering, Legal/Compliance",
"◆ Phase 5: Launch & Validation",
"7-Day Sprint, Split-Test Protocol, 30-Day Calendar, 90-Day Scale, 19 Failure Points",
"◆ Phase 6: Advanced Tactics",
"Ascension, Pre-Suasion, 8-Dimension Stack, 2024 vs 2026",
"◆ Phase 7: Customer Avatar",
"13 Dimensions, Buyer Segmentation, Hyper-Responsive Segment, LLM Roleplaying",
"◆ Phase 8: Kennedy’s 10 Rules",
"Pre-Launch Compliance Checklist — Pass/Fail Verification",
"",
"The MVO Philosophy",
"What an MVO Actually Is",
"An MVO is the smallest, fastest-to-deploy offer that validates whether a market will exchange money for the transformation you promise. It’s not about being minimal in value — it’s about being minimal in complexity while being MAXIMUM in perceived value.",
"Kennedy’s First Law",
"“The best offer wins. Not the best product. Not the best copy. The best OFFER.”",
"",
"Kennedy’s Offer Architecture",
"THE STATED OFFER — What you explicitly say they get",
"THE IMPLIED OFFER — What they believe they’ll become",
"THE HIDDEN OFFER — The emotional payoff they can’t articulate",
"Professionals build all three layers simultaneously. Your MVO must address all three even in its simplest form.",
"Execution Debt",
"The Highest-Value Pain Category",
"Execution Debt: someone KNOWS the problem AND roughly knows the solution, but lacks bandwidth, courage, or clarity.",
"MVOs targeting Execution Debt convert highest because the buyer needs enablement, not education.",
"",
"Kennedy’s 10 Smart Market Diagnosis Questions",
"Answer These BEFORE Any Research",
"Write answers to all 10 using initial desk research. 30 minutes. This gives your research direction.",
"",
"What keeps them awake at night, staring at the ceiling?",
"What are they afraid of?",
"What are they angry about? Who are they angry at?",
"What are their top 3 daily frustrations?",
"What trends are occurring (or will occur) in their world?",
"What do they secretly desire most?",
"What are their strongest objections to buying a solution?",
"What buying triggers do they respond to?",
"What language, jargon, and slang do they use?",
"Who else is already selling to them successfully, and why?",
"",
"Phase 1: Market Excavation",
"★ V5: Niche Viability Scoring Matrix",
"Before You Research Pain Points — Score the Niche Itself",
"Don’t build a beautifully constructed MVO for a niche that was never viable. Score first, research second.",
"",
"Rate each dimension 1–10. Niches scoring under 50/70 need repositioning or should be abandoned:",
"Dimension",
"Score 1–10",
"What You’re Measuring",
"Pain Intensity",
"___",
"How severe is the core problem?",
"Willingness to Pay",
"___",
"Are they already spending on solutions?",
"Ease of Fulfillment",
"___",
"Can you deliver without massive infrastructure?",
"Speed to First Win",
"___",
"Can the buyer see results within days/weeks?",
"Competitive Advantage",
"___",
"Is there a gap you can own?",
"Content Opportunity",
"___",
"Can you create authority content in this space?",
"Offer Scalability",
"___",
"Can this grow beyond 1:1 delivery?",
"",
"Diagnostic: 60–70 = Strong, test immediately. 50–59 = Viable but needs sharp positioning. 40–49 = Weak, reposition or pivot. Under 40 = Walk away.",
"★ V5: Define Audience by Buying Behavior, Not Identity",
"Critical Reframe",
"“Real estate agents” is an identity. “People who spend $500+/month on lead gen and are frustrated with conversion” is a buying behavior.",
"The first gives you a demographic. The second gives you a qualified buyer with proven willingness to spend.",
"Define your niche by what they BUY and DO, not just what they ARE.",
"Step 1: The ‘Bleeding Neck’ Audit",
"Core Discovery Sources:",
"→ Amazon Book Reviews: 1-star = what people hate. 5-star = transformation they wanted.",
"→ Reddit/Forum Mining: Use exact search operators (see below).",
"→ Google Autocomplete: Topic + “but,” “without,” “for,” “vs.”",
"→ Customer Support Tickets: Every complaint is an offer waiting to be born.",
"→ Facebook Groups: Posts with 50+ comments = emotional resonance.",
"→ ★ V5: Course Review Platforms: Udemy, Coursera, Skillshare, LinkedIn Learning. Reviewers PAID for education and tell you exactly where it falls short. “Too basic,” “Didn’t explain X,” “I wish it covered Y” — premium pain signals from validated buyers.",
"→ ★ V5: Frontline Staff Observations (Brick-and-Mortar): Receptionists, technicians, and reps hear unfiltered customer pain daily. A 30-min staff debrief surfaces pain points no Reddit mining will find.",
"→ ★ V5: E-Commerce Data: Cart abandonment analytics, chargeback reasons, and return/refund reasons. Direct behavioral evidence of where the buying experience breaks.",
"Exact Search Operators:",
"site:reddit.com \"[niche] sucks\" OR \"[niche] hate\" OR \"struggling with [niche]\"",
"site:reddit.com \"[niche]\" \"waste of money\" OR \"frustrated\" OR \"can't figure out\"",
"X/Twitter: \"[niche] frustration\" OR \"[niche] nightmare\" — filter Latest + Top, 12 months",
"Google: inurl:forum \"[niche]\" \"how do I fix\" OR \"alternative to\"",
"2026 Research Sources:",
"AI Citation Mining: Prompt Perplexity/Gemini for consensus pain points",
"GummySearch: Reddit pain-point tracking with upvote patterns",
"Search Console Intent Shifts: “What is” → “Service for” = purchase intent",
"Social Listening (Brandwatch, Sprout Social, Mention): Sentiment at scale",
"Hotjar / Microsoft Clarity: Heatmaps and session recordings for existing traffic",
"Agentic Automation (n8n / LangGraph): Monitor 10+ sources simultaneously",
"Ad Transparency: Meta Ad Library — ads running 6+ months = profitable pain point",
"",
"★ V5: Three Kill Filters (Before You Proceed)",
"If Any of These Are True — Walk Away",
"These kill signals save you from building an MVO for a pain point that will never monetize.",
"",
"☠ Kill Filter 1: “Cheap to Ignore”",
"Can the buyer live with this problem at near-zero cost? If ugly invoices, messy desks, or imperfect processes don’t cost them real money, time, or status — they’ll tolerate it forever. No MVO can sell relief from a pain that’s free to endure.",
"☠ Kill Filter 2: “Massive Behavior Change Required”",
"Even if the pain is severe, if your solution requires them to fundamentally rewire their habits or workflow, adoption collapses. A brilliant CRM for contractors who hate using CRMs will fail. The implementation barrier becomes the real objection.",
"☠ Kill Filter 3: “Existing Solution Already Excellent AND Cheap”",
"If Canva already solves the design problem well at $12/month, there’s no gap. We talk about competitive gaps — this is the explicit signal that no gap exists. Don’t compete where the market is already well-served cheaply.",
"★ V5: Cheap Pain vs. Premium Pain",
"Cheap Pain (Avoid)",
"Premium Pain (Pursue)",
"“I need a logo”",
"“I need more booked appointments”",
"“I need more followers”",
"“I need qualified leads”",
"“I want motivation”",
"“I need to pass inspection”",
"“I need content ideas”",
"“I need to reduce employee turnover”",
"“I want to learn marketing”",
"“I need to stop losing customers”",
"",
"Premium pain always connects to: Make money, save money, save time, avoid risk, avoid embarrassment, increase status, protect business, create certainty.",
"",
"Desire Mapping Framework",
"Level",
"What They Say",
"What It Means",
"Surface",
"“I want to lose 20 lbs”",
"Stated rational goal",
"Real",
"“I want to feel attractive again”",
"Emotional driver",
"Hidden",
"“I want people to envy me”",
"Drives premium buying",
"Competitive Gap Analysis — 5-Gap Framework",
"SPEED — Deliver the result faster?",
"RISK — Remove more risk from the buyer?",
"SPECIFICITY — Serve a narrower audience better?",
"ACCESS — Offer more direct access to expertise?",
"FORMAT — Deliver in a way nobody else does?",
"★ V5: The 6-Score Monetization Filter",
"Replaces Our Previous 5-Filter System — More Structured, with Hard Cutoff",
"Score each pain point 1–5 on six dimensions. Maximum: 30. Only keep pain points scoring 22+.",
"",
"Dimension",
"Score 1–5",
"Question",
"Urgency",
"___",
"Do they need it NOW, not someday?",
"Spending Proof",
"___",
"Are they already paying for solutions?",
"Frequency",
"___",
"Does this pain appear often across sources?",
"Value",
"___",
"Is solving it worth real money to them?",
"Simplicity",
"___",
"Can the result be explained in one sentence?",
"Fulfillment",
"___",
"Can you actually deliver without chaos?",
"",
"“Simplicity” and “Fulfillment” are the new additions. They catch two failure modes: offers too complex to explain and offers that are nightmares to deliver.",
"Pain Point Category Balancing",
"Enforce diversity across 4 categories. Don’t find 20 variations of the same pain:",
"Category",
"Target",
"Examples",
"Financial",
"5 points",
"Revenue loss, wasted spend, pricing mistakes, cash flow, hidden costs",
"Time/Productivity",
"5 points",
"Manual tasks, bottlenecks, context switching, slow processes",
"Emotional/Status",
"5 points",
"Embarrassment, imposter syndrome, fear of failure, peer comparison",
"Process/Support",
"5 points",
"Bad tools, poor support, complex workflows, integration failures",
"Evidence Tagging Format",
"For each of your top 20, document three pieces of evidence:",
"Verbatim Quote — Exact language from a real person. This becomes copy.",
"Monetization Proof — Evidence they already pay to solve it.",
"GEO Angle — How people phrase this to AI search engines.",
"",
"Phase 2: Offer Construction",
"★ V5: The 10-Offer Generation Method",
"Don’t Jump to One Offer — Generate 10, Rank, Then Commit",
"Forcing divergent thinking before convergent commitment prevents you from building the obvious offer",
"when a less obvious one is more viable. Your third-ranked idea may outperform your instinct.",
"",
"For each of 10 possible offers, define: Offer Name, Target Customer, Main Problem Solved, Delivery Format, Time to Result, Price Range, Why They’d Buy, Why They’d Hesitate, and Fulfillment Difficulty.",
"Then rank all 10 by:",
"Fastest to validate (can you test it this week?)",
"Easiest to fulfill (can you deliver without infrastructure?)",
"Highest perceived value (does the outcome feel worth the price?)",
"Best profit margin (is the math sustainable?)",
"Lowest risk (what’s the worst case if it fails?)",
"Best long-term scaling potential (can this grow beyond 1:1?)",
"",
"Pick the best 1–3 to test. Test simultaneously if possible.",
"The Irresistible Offer Formula",
"The Value Equation",
"(Dream Outcome × Perceived Likelihood) ÷ (Time Delay × Effort & Sacrifice) = Offer Value",
"",
"Maximize Dream Outcome:",
"Be specific (“30 qualified leads in 30 days” beats “more leads”)",
"Attach the outcome to an identity shift, not just a metric",
"Maximize Perceived Likelihood:",
"Social proof, demonstration of method, specificity creates believability",
"Minimize Time Delay:",
"Quick wins inside the larger transformation. “Day 3 you’ll have X”",
"Minimize Effort:",
"Done-for-you > done-with-you > DIY. Templates and fill-in-the-blank tools",
"Kennedy’s “Thud Factor”",
"Overwhelming Psychological Weight Through Bonus Stacking",
"“All of THAT for THIS price?” is the reaction you’re engineering.",
"Pile on bonuses until the sheer volume creates an emotional response independent of any single component.",
"",
"★ V5 Counterbalance: “Too Many Bonuses” Warning",
"The Thud Factor fails when bonuses are filler that dilutes clarity.",
"If the prospect can’t figure out what the CORE offer actually IS, conversions drop.",
"Every bonus must clearly solve a specific sub-problem. Confusion kills more sales than scarcity creates.",
"★ V5: The Flagship Promise Test",
"The Simplicity Counterbalance",
"The core promise must be ONE thing, simple enough that a prospect can repeat it in one sentence.",
"Bonuses stack around it but never compete with it.",
"MECHANISM REPEATABILITY TEST: Can your prospect explain HOW your offer works in one sentence?",
"“It’s a 5-day sprint where they write your emails for you.” = PASS",
"“It’s a comprehensive multi-modular system leveraging proprietary frameworks.” = FAIL",
"Sell “Done,” Not “How To”",
"Default to “done” or “intensive” rather than “course.” A 90-minute intensive where you solve their specific problem live IS minimum viable. A 10-module course is not.",
"",
"★ V5: The Pain-to-Offer Transformation Ladder",
"How a Raw Pain Point Becomes a Winning Offer",
"The progression always moves toward: more specificity, more speed, more done-for-you, more niche-targeted.",
"",
"Pain: “I don’t know what to post on Instagram.”",
"Weak Offer: “Instagram content course.”",
"Better: “30-Day Instagram Client Attraction Calendar For Local Med Spas.”",
"Strongest: “We Build Your First 30 Days Of Med Spa Instagram Content Designed To Book Consultation Calls.”",
"",
"Notice the pattern: Generic education → Specific template → Done-for-you with specific outcome. The money is NOT in the information. It’s in: speed, specificity, implementation, done-for-you assets, risk reduction, and faster outcomes.",
"The MVO Stack: 7 Components",
"1. Core Deliverable",
"Surgically focused. “A 5-day email sequence that books calls” — not “a complete marketing system.”",
"2. The Mechanism",
"Kennedy’s “Unique Mechanism.” Name your method. “The Reverse Funnel Method.”",
"3. Fast-Action Bonus",
"Immediate value upon purchase. Quick win that proves the system works.",
"4. Risk Reversal",
"Guarantee so strong it shifts all risk to you.",
"5. Scarcity/Urgency",
"Real, ethical scarcity. No fake countdown timers.",
"6. Social Proof Anchor",
"Even one testimonial. No proof? Beta access for testimonials.",
"7. Price Anchor",
"Value relative to alternatives. “Agencies charge $3K. You get it for $297.”",
"★ V5: Proof Must Match the Exact Promise",
"Sharper Social Proof Principle",
"If you promise “30 qualified leads in 30 days,” a testimonial saying “Great experience!” is nearly worthless.",
"You need: “We got 34 qualified leads in the first 28 days.”",
"The proof and the promise must use the SAME metric. Match proof to the specific claim, not the category.",
"The Forensic Critic Positioning (For New Entrants)",
"If you lack social proof, position yourself as the Forensic Critic of current industry failures. Build authority through analysis, not credentials. Your MVO becomes the “Correction.”",
"",
"Cialdini’s 7 Principles Applied to Offer Design",
"1. Reciprocity",
"Give genuine value before asking. A real workshop triggers powerful reciprocity. A 2-page PDF triggers weak.",
"2. Commitment & Consistency",
"Micro-commitments: quizzes, assessments. Each small yes makes the big yes easier.",
"3. Social Proof",
"Match proof to objection AND to the exact promise. Industry-specific proof for industry objections.",
"4. Authority",
"Borrowed authority: “as featured in,” “based on research from [university].”",
"5. Liking",
"Be polarizing. Kennedy: “If you haven’t offended someone by noon, you’re not marketing hard enough.”",
"6. Scarcity",
"Real scarcity only. Limited capacity, launch pricing, genuine supply constraints.",
"7. Unity",
"“As a fellow [identity], I built this because...”",
"",
"Phase 3: Direct Response Copy",
"Kennedy Headline Formulas",
"“How To [Desired Outcome] Without [Biggest Fear]”",
"“The [Adjective] [Mechanism] That [Result] In [Timeframe]”",
"“Warning: Don’t [Common Action] Until You [Read/See/Hear] This”",
"“[Specific Number] [Niche] [People] Are Now [Doing Result] — Here’s How”",
"“Who Else Wants [Desired Outcome]?”",
"Expert Tip",
"Write 25–50 headlines. The magic lives in headlines 20–50.",
"★ V5: The 10 Hook Types",
"A Categorized Taxonomy for Ads, Social, and Video",
"Instead of staring at a blank page, run through each type and generate a version for each.",
"",
"Pain Hook: “Tired of [specific pain]? Here’s why it keeps happening.”",
"Mistake Hook: “The #1 mistake [niche] make with [topic] (and the easy fix).”",
"Secret Hook: “The [niche] secret that [competitors] don’t want you to know.”",
"Contrarian Hook: “Why [common advice] is actually killing your [result].”",
"Speed Hook: “How to [result] in [surprisingly short time].”",
"Cost-of-Inaction Hook: “Every day you wait, you’re losing $[amount].”",
"Identity Hook: “For [specific identity] who refuse to settle for [status quo].”",
"Local Hook: “Attention [city/region] [niche]: [specific local pain].”",
"Authority Hook: “After [number] years/clients/results, here’s what I know about [topic].”",
"Transformation Hook: “From [before state] to [after state] in [timeframe].”",
"Language Echoes",
"Insider Slang = Instant Unity",
"Find weird niche-specific jargon. If HVAC techs call a comm error a “NASA ghost,” use it in copy.",
"P.A.S.T.O.R. Body Copy Framework",
"P — Problem",
"Name it with painful specificity. “Staring at an empty inbox wondering where your next client is.”",
"A — Amplify",
"Cost of NOT solving. “If nothing changes in 12 months, what does your business look like?”",
"S — Story / Solution",
"Bridge from pain to possibility through narrative.",
"T — Transformation",
"Paint the after picture. “4 new leads every morning before your coffee gets cold.”",
"O — Offer",
"Present the full MVO stack. Every component. Stack visually.",
"R — Response",
"One clear CTA. “Click the button, fill in details, access within 3 minutes.”",
"★ V5: The Buyer’s Internal Monologue Check",
"A Complementary Copy Lens to P.A.S.T.O.R.",
"After writing your copy, read it through the buyer’s 4 internal questions:",
"1. What am I afraid of? 2. What do I actually want? 3. Why have I been putting this off?",
"4. What would make this feel safe right now?",
"If your copy answers all 4 in the buyer’s own language, it converts regardless of framework.",
"The test: “Does this sound like something I’d THINK, or something a marketer wrote AT me?”",
"",
"The 21 Copy Triggers",
"Specificity — “37 leads in 22 days” beats “lots of leads”",
"Curiosity — Open a loop they can only close by reading on",
"Fear of Missing Out — What will they lose?",
"Future Pacing — Describe life after transformation",
"Enemy — Give them something to oppose",
"Contrast — Before/after, old way vs. new way",
"Reason Why — Explain WHY the price, WHY now",
"Damaging Admission — Admit a weakness to build trust",
"Third-Party Proof — Let others make the claim",
"Demonstration — Show the mechanism in action",
"Ownership Language — “Your new system”",
"Conversational Tone — Write like you talk",
"Power Words — Free, new, you, instantly, because, proven",
"Dimensional Follow-Up — Same message, multiple channels",
"Story — Every fact in narrative converts better",
"Pattern Interrupt — Something unexpected",
"Presupposition — “When you see results” not “If”",
"False Close — “You could stop here, but...”",
"Takeaway — “This might not be for you”",
"Deadline — Real time pressure",
"Justification — “Because” increases compliance 34%",
"",
"Channel-Specific Copy",
"Email",
"Test 5–10 subject lines per campaign. PS lines get read more than body copy.",
"SMS",
"95%+ open rates. Under 160 chars. Lead with value. TCPA compliance mandatory.",
"Landing Pages",
"Above fold: Headline, sub-headline, hero, CTA. Social proof within first scroll. Mobile-first.",
"Paid Social",
"Hook in first 3 seconds. Refresh creatives every 7–14 days.",
"Short-Form Video",
"Hook → Problem → Agitate → Mechanism tease → CTA. 30–60 seconds.",
"Brick-and-Mortar",
"In-store QR codes, physical signage with Kennedy-style copy, local GBP, Nextdoor, hybrid funnels, local direct mail.",
"",
"★ V5: The 14-Day Email Sequence Architecture",
"The Fortune Is in the Follow-Up — Here’s the Exact Structure",
"For each email: write Subject Line, Preview Text, Body, CTA, and identify the Psychological Trigger used.",
"",
"Day",
"Email Purpose",
"Psychological Trigger",
"1",
"Welcome + Quick Win (deliver immediate value)",
"Reciprocity",
"2",
"Pain Awareness (name their exact situation)",
"Problem Agitation",
"3",
"Cost of Inaction (project the pain forward)",
"Fear / Loss Aversion",
"4",
"Common Mistakes (position yourself as expert)",
"Authority",
"5",
"Personal Story (your origin / struggle)",
"Liking / Unity",
"6",
"Case Study (someone like them who succeeded)",
"Social Proof",
"7",
"Myth-Busting (debunk what they believe is true)",
"Contrarian Authority",
"8",
"New Opportunity (introduce the mechanism)",
"Curiosity",
"9",
"Offer Introduction (present the MVO stack)",
"Commitment",
"10",
"Bonus Explanation (Thud Factor via email)",
"Value Stacking",
"11",
"Objection Handling (address top 3 objections)",
"Trust Building",
"12",
"FAQ (reframe objections as questions)",
"Certainty",
"13",
"Urgency (deadline or scarcity reminder)",
"Scarcity",
"14",
"Final Call (last chance, recap transformation)",
"Loss Aversion",
"",
"80% of sales happen between the 5th and 12th contact. Most people quit after 2 emails. This 14-day sequence ensures you’re still in the conversation when they’re ready to buy.",
"",
"Phase 4: Pricing & Packaging",
"The MVO Pricing Matrix",
"Strategy",
"Price Range",
"Best For",
"Example",
"Loss-Leader",
"$7–$47",
"High LTV markets",
"$27 Marketing Audit Toolkit",
"Validation",
"$97–$497",
"Services, coaching, B2B",
"$297 Lead Gen Sprint",
"Premium",
"$997–$5,000+",
"Consulting, enterprise",
"$2,500 Revenue Intensive",
"",
"→ Price to the transformation, not the deliverable.",
"→ Odd pricing: $297 > $300. $997 > $1,000.",
"→ Payment plans increase conversions 20–40% at higher price points.",
"The “Muddled Middle” Dead Zone",
"AVOID $500–$900",
"Too expensive for impulse, too cheap for premium. People need 14 emails and a webinar to decide.",
"Price below $497 or above $997.",
"★ V5: Three Pricing Models for the Same Offer",
"Test Which Positioning the Market Responds To",
"The same core deliverable at three price points tests three buyer segments simultaneously.",
"",
"Model",
"Price",
"What’s Included",
"Buyer Type",
"Self-Serve",
"$97–$197",
"Templates + video training + community",
"DIY / budget-conscious",
"Guided",
"$297–$497",
"Everything above + live group calls + feedback",
"Frustrated DIYer / busy operator",
"Done-With-You",
"$997–$2,500",
"Everything above + 1:1 implementation",
"Premium / emergency buyer",
"",
"Most people pick one price and hope. Testing three models reveals which segment has the most demand AND the best unit economics. You may discover the $997 version outsells the $197 version because it attracts more committed buyers.",
"Verifiable Social Proof (2026 Standard)",
"Video testimonials showing actual results on screen",
"Screen-share walkthroughs of real metrics",
"Before/after with timestamps",
"Third-party platforms (G2, Trustpilot)",
"Legal & Compliance",
"The Failure Point Nobody Talks About",
"Income claims, guarantee language, testimonial disclaimers, FTC/TCPA/GDPR all apply.",
"Have a lawyer review before scaling. Platform bans from Meta/Google are real.",
"",
"",
"Guarantee Engineering",
"Level 1: Standard Money-Back",
"“30-day money-back.” Baseline. Not a differentiator.",
"Level 2: Conditional Result-Based",
"“If you don’t [result] in [timeframe], full refund.”",
"Level 3: Better-Than-Money-Back",
"“Refund your $297 AND give you $200 in ad credit.”",
"Level 4: Service-Based (Kennedy’s Move)",
"“I’ll work with you free until it does, and send $100 for wasting your time.”",
"Level 5: Anti-Guarantee",
"“No refunds. For serious people only.” Powerful for premium.",
"Kennedy’s Guarantee Rule",
"“The bolder the guarantee, the fewer refunds you’ll get.”",
"",
"Phase 5: Launch & Validation",
"The 7-Day MVO Launch Sprint",
"Day 1: Crystallize",
"One-sentence offer. MVO stack. Price. Run the Kennedy 10 Rules Checklist (Phase 8).",
"Day 2: Copy",
"P.A.S.T.O.R. sales page. 25+ headlines. 3–5 launch emails. Run Buyer’s Internal Monologue Check.",
"Day 3: Assets",
"One landing page. Lead magnet. Short video if applicable.",
"Day 4: Proof",
"5–10 beta outreach. Testimonials. Before/after narratives.",
"Day 5: Channels",
"Email + SMS automation. 3–5 organic posts. Payment processing.",
"Day 6: Soft Launch",
"Existing list. Communities. DM 20–50 prospects.",
"Day 7: Test",
"Launch A/B split test. Track all metrics. Begin collecting buyer data.",
"Split-Test Protocol",
"Testing Priority:",
"Headline — Highest impact. Two angles on the same pain.",
"Price — $197 vs $297 or $297 vs $497.",
"Guarantee — Standard vs. service-based.",
"Bonus Stack — Minimal vs. full Thud Factor.",
"CTA — “Get Instant Access” vs. “Start Your Sprint.”",
"Minimum sample: 100 visitors per variant. Under 100 = noise. 20%+ difference = winner.",
"Validation Metrics",
"Metric",
"Viable",
"Scale Signal",
"Cold Opt-In",
"15–30%",
"30%+",
"Cold Sale",
"1–3%",
"5%+",
"Warm Sale",
"5–10%",
"20%+",
"Refund Rate",
"Under 5%",
"Under 2%",
"CPA vs Price",
"Under 30%",
"Under 10%",
"Email Open",
"20–30%",
"30–50%",
"Email Click",
"2–5%",
"5%+",
"★ V5: Service Funnel Metrics",
"For MVOs Sold Through Calls or Consultations",
"Many $997+ MVOs require a sales conversation. These metrics cover that funnel shape.",
"",
"Metric",
"Viable",
"Strong",
"Booking Rate",
"15–25% of page visitors",
"25%+",
"Show-Up Rate",
"60–70%",
"80%+",
"Close Rate",
"15–25% of calls",
"30%+",
"Cost Per Call",
"Under $100",
"Under $50",
"Diagnostic Framework:",
"Traffic, no sales → Offer problem",
"No traffic → Distribution problem",
"Sales, high refunds → Delivery problem",
"Clicks, no sales → Trust/Guarantee problem",
"Bookings, low show-up → Reminder/nurture problem",
"Shows, low close → Sales script/objection problem",
"GEO — Generative Engine Optimization",
"Implement Schema Markup (JSON-LD). Include citable data, named frameworks, published case studies so AI search engines surface your offer.",
"",
"The 30-Day Action Calendar",
"Days 8–10",
"Collect data. DO NOT change anything. Read every reply.",
"Days 11–14",
"First optimization. Analyze split-test. Address #1 objection.",
"Days 15–18",
"Add second traffic source. Dimensional expansion.",
"Days 19–21",
"Introduce Tier 3 (Core Offer) to existing buyers.",
"Days 22–25",
"Collect video testimonials. Update landing page. Create case studies.",
"Days 26–28",
"Scale decision. If metrics hit thresholds: increase spend 20%/day max.",
"Days 29–30",
"Document SOPs. Automate reporting. Plan Tier 3 build.",
"★ V5: The 90-Day Scaling Funnel",
"What Happens After Validation",
"The 30-day calendar validates. The 90-day funnel builds a business.",
"",
"Days 31–45: Retargeting & Automation",
"Build retargeting ads for all page visitors who didn’t convert. Automate the winning email + SMS sequence. Add a downsell for people who don’t buy the main offer.",
"Days 46–60: Backend Offer Build",
"Build your Tier 3 Core Offer based on what your MVO buyers tell you they need next. Create an upsell path from MVO to Core.",
"Days 61–75: Content Flywheel",
"Launch organic content based on the pain points that converted best. Repurpose buyer testimonials into ads. Start building SEO/GEO authority.",
"Days 76–90: Systemize & Scale",
"Hire or outsource fulfillment for the MVO. Add a third traffic source. Begin testing the Core Offer. You now have a validated offer, a proven funnel, a growing list, and a backend — that’s a real business.",
"",
"Kennedy’s Implementation Rule",
"“Implement massively or nothing happens.”",
"",
"★ V5: Build to Sell, Not to Impress Marketers",
"Pre-Launch Validation Step",
"Show your offer to someone in your target market who is NOT a marketer.",
"If they don’t immediately understand what they get, how fast, and why they should care — simplify.",
"Your MVO is evaluated by whether buyers say yes, not whether other marketers think it’s clever.",
"",
"The 19 Most Overlooked MVO Failure Points",
"Solving a problem nobody will pay to fix. Validate with dollars, not compliments.",
"Speaking to everyone. “Small business owners” is not a niche.",
"Building before selling. Sell first. Build second.",
"Weak mechanism. Name your method. “The 5-Phase Revenue Acceleration System.”",
"No risk reversal. Buyer carries all risk = mediocre conversions.",
"Copy that describes instead of persuades. Features tell. Transformation converts.",
"One traffic source. Algorithm changes = you’re dead.",
"Ignoring the follow-up. 80% of sales happen after contact 5. Most quit after 2.",
"Pricing based on cost, not value. Price to the outcome.",
"No backend offer. An MVO without ascension = one-night stand.",
"Perfectionism disguised as preparation. Ship ugly. Fix live.",
"Copying competitors instead of studying customers.",
"Ignoring mobile. 70%+ see your offer on a phone.",
"No clear CTA. If they have to think, you’ve lost them.",
"Giving up after first attempt. Kennedy: “Most millionaires have a trail of failed offers.”",
"“My business is different.” The principles are universal. Every industry has buyers with pain and wallets.",
"Legal/compliance blind spots. FTC, TCPA, GDPR, platform rules. Get a lawyer before scaling.",
"★ V5: No post-purchase experience. Weak onboarding, no customer success, no delivery delight = refunds, no testimonials, zero ascension. What happens AFTER the sale determines your entire business trajectory.",
"★ V5: Too many bonuses without clarity. The Thud Factor backfires when the stack is so large the prospect can’t figure out what the core offer IS. Every bonus must solve a specific sub-problem or it’s noise.",
"",
"Phase 6: Advanced Tactics",
"The Ascension Architecture",
"Tier",
"What",
"Price",
"Purpose",
"1",
"Free Value",
"Free",
"Build list, demonstrate expertise",
"2",
"MVO",
"$27–$497",
"Convert, validate, build proof",
"3",
"Core Offer",
"$497–$5K",
"Full transformation, real profit",
"4",
"Premium",
"$5K–$50K+",
"Max profit per client",
"5",
"Continuity",
"$47–$497/mo",
"Recurring revenue",
"Cialdini’s Pre-Suasion",
"→ Priming: Show cost of problem before price. $47K loss → $497 solution.",
"→ Attention Channeling: Pain focus = solution evaluation. Value focus = price acceptance.",
"→ Unity Trigger: “As founders...” before pitching.",
"→ Environmental Priming: Professional design primes premium pricing.",
"→ Ask-Then-Tell: “Do you deserve better results?” → Yes → “Here’s how.”",
"The 8-Dimension Direct Marketing Stack",
"D1: Content — Organic social, YouTube, podcast, blog.",
"D2: Email — Owned channel. The backbone.",
"D3: SMS — 95%+ open rates. Best for urgency and local.",
"D4: Paid Media — Meta, Google, YouTube, TikTok, LinkedIn.",
"D5: AI-Personalized Outreach — Hyper-personalized at scale. Must be REAL.",
"D6: Physical Mail — Kennedy’s secret weapon. 5–10x email conversion.",
"D7: Community & Events — Workshops convert 10–30%.",
"D8: AI Search (GEO) — Schema markup for AI engine citations.",
"Rule of Three",
"One channel = hope. Three = strategy. Five = dominance.",
"",
"2024 vs. 2026 MVO Comparison",
"Feature",
"2024",
"2026 State-of-the-Art",
"Hook",
"“Get 10x Leads”",
"“Solve the [Specific] Leak in your [Specific] System”",
"Medium",
"Email opt-in",
"Multi-modal (Text, Voice, SMS, AI Agent)",
"Trust",
"Generic testimonials",
"Verifiable video case studies + data",
"Copy",
"Long-form sales page",
"Short-form direct + interactive Q&A",
"Research",
"Manual browsing",
"Agentic automation + social listening",
"Discovery",
"Google SEO",
"GEO + Schema Markup for AI engines",
"Avatar",
"Static PDF",
"Live behavioral model from buyer data",
"Delivery",
"Course / PDF",
"Done-With-You Intensive / AI-assisted",
"Testing",
"Launch and hope",
"A/B split-test from Day 1",
"Local",
"Website + Google Ads",
"QR + SMS + Direct Mail + Hybrid",
"Pricing",
"One price point",
"3 models testing 3 buyer segments",
"Follow-up",
"3 emails",
"14-day sequence with psychological architecture",
"",
"Phase 7: The Customer Avatar",
"The Two-Avatar Sequence",
"Avatar V1: Hypothesis (Pre-MVO)",
"4 hours max. Directional clarity for copy, channels, price. A research guess.",
"Avatar V2: Validated (Post-MVO)",
"After 10–30 buyers. The people who buy are never exactly who you thought. A money-validated profile.",
"Kennedy",
"An imperfect message to the right person outsells a perfect message to the wrong person every time.",
"The Hyper-Responsive Segment",
"Design for the Top 10%, Not the Average",
"Kennedy: “Averages are for losers.” The 10% with most money and least time pay premium.",
"★ V5: Buyer Segmentation Types",
"The Same Pain Requires Different Offers for Different Buyer Types",
"Before locking your avatar, identify which segment you’re designing for.",
"",
"Buyer Type",
"What They Want",
"Best MVO Format",
"Beginner",
"Step-by-step guidance",
"Template + tutorial",
"Frustrated DIYer",
"Someone to do it WITH them",
"Done-with-you intensive",
"Busy Operator",
"Speed, no learning curve",
"Done-for-you service",
"Premium Buyer",
"Best possible result, fast",
"High-touch VIP package",
"Emergency Buyer",
"Immediate fix, any cost",
"Same-day service / rush delivery",
"Skeptical Buyer",
"Proof before commitment",
"Free audit + low-risk trial",
"Cost-Conscious",
"Maximum value per dollar",
"Self-serve with community",
"",
"A “Frustrated DIYer” who’s tried 3 courses wants done-with-you. An “Emergency Buyer” whose pipeline dried up wants done-for-you NOW. Design the MVO for the most monetizable segment.",
"",
"The 13 Dimensions of a Complete Avatar",
"Our original 12 dimensions plus a critical 13th from V5:",
"1. Demographic Foundation",
"Age, gender, location, income, education. Sources: Facebook Audience Insights, LinkedIn Sales Navigator.",
"2. Professional Identity",
"Job title, industry, company size, decision authority. Sources: LinkedIn, surveys.",
"3. Self-Identity Statement",
"How they describe themselves. “I’m a scrappy bootstrapper.” This is your Unity language. Sources: Social bios (SparkToro).",
"4. The Information Diet",
"Podcasts, YouTube, newsletters, influencers they follow. Sources: SparkToro.",
"5. The Buying History",
"What they’ve already purchased. THE most predictive data. Sources: Survey, reviews.",
"6. Current Emotional State",
"Frustrated, anxious, hopeful, skeptical, desperate? Determines copy tone. Sources: Reddit, reviews.",
"7. Day-in-the-Life",
"When do they encounter the pain? What triggers it? Sources: Direct conversations.",
"8. The Three Fears",
"Fear of failure, fear of inaction, fear of admitting desire. Every fear = objection. Sources: 1-star reviews.",
"9. Decision-Making Style",
"Quick or slow? Logic or emotion? Determines funnel structure. Sub-field: ★ V5 “What makes them say yes QUICKLY?” — the specific conditions that collapse their decision timeline.",
"10. The Objection Stack",
"5–7 reasons they won’t buy. Every unanswered objection = lost sale. Sources: Competitor reviews.",
"11. The Watering Holes",
"Exact subreddits, groups, communities, conferences. Your distribution map. Sources: SparkToro.",
"12. The Trigger Event",
"What pushes “someday” to “NOW.” Most overlooked, most powerful. Sources: Direct conversations.",
"13. ★ V5: Words They Hate (Anti-Language)",
"Words and phrases that actively REPEL your avatar. If they’ve been burned by coaches promising “mindset shifts” and “quantum leaps,” those words trigger instant distrust. Knowing the anti-language is as important as knowing the insider slang. Sources: Reddit rants, negative reviews, direct interviews.",
"",
"The Research Tool Stack",
"Tool",
"What It Reveals",
"Cost",
"SparkToro",
"Audience media diet, follows, content",
"Freemium",
"Facebook Audience Insights",
"Demographics, interests, affinities",
"Free",
"LinkedIn Sales Navigator",
"Professional identity, company data",
"Paid (trial)",
"SimilarWeb",
"Competitor audience, traffic sources",
"Freemium",
"GummySearch",
"Reddit pain tracking, upvotes",
"Paid",
"AnswerThePublic",
"Search queries, question hierarchies",
"Freemium",
"Meta Ad Library",
"Competitor hooks (long-running = profitable)",
"Free",
"Google Search Console",
"Intent shifts, hidden avatar data",
"Free",
"Perplexity / Gemini",
"AI-aggregated consensus pain points",
"Freemium",
"Brandwatch / Sprout Social",
"Enterprise social listening",
"Paid",
"Hotjar / Clarity",
"Heatmaps, session recordings",
"Freemium",
"Respondent.io",
"Paid interview recruitment ($50–100/call)",
"Paid",
"UserInterviews.com",
"B2B interview panel",
"Paid",
"Wynter",
"B2B message testing panels",
"Paid",
"★ V5: Juma / UXPressia",
"Structured persona builder tools",
"Freemium",
"★ V5: HubSpot Make My Persona",
"Guided avatar template builder",
"Free",
"LLM Avatar Roleplaying",
"AI as Creative Amplifier (Use After Real Data)",
"Prompt: “You are a [avatar] losing $X/day because of [problem]. What are the three things",
"you are terrified to tell your [stakeholder] tomorrow morning?”",
"Validating the Avatar (Post-MVO)",
"Buyer Interviews: “What was happening when you bought? What almost stopped you?”",
"Purchase Analytics: Demographics of BUYERS (not clickers). One pocket converts 3–5x.",
"Email Reply Analysis: “What’s the #1 thing you hope to get?” Categorize every reply.",
"Refund Interviews: Refunders tell you who your avatar is NOT.",
"Search Console Long-Tail: High-dwell-time keywords = your “Hidden Avatar.”",
"",
"Phase 8: Kennedy’s 10 Rules — Pre-Launch Checklist",
"Run This Before You Launch ANY MVO. If Any Rule Fails, Fix It First.",
"",
"Rule 1: Always an Offer",
"Is there a clear, stacked offer? Bonuses, guarantee, scarcity, price anchor? Does it pass the Thud Factor test AND the Flagship Promise test?",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"Rule 2: Reason to Respond NOW",
"Real urgency or scarcity? Genuine deadline, limited capacity, or launch pricing?",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"Rule 3: Clear Instructions",
"Does the prospect know EXACTLY what to do? One CTA. Zero ambiguity.",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"Rule 4: Tracking & Measurement",
"Can you measure every step? Views, opt-ins, clicks, sales, refunds, CPA, opens?",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"Rule 5: Branding is a By-Product",
"Are you spending on direct-response that generates ROI? Every dollar trackable?",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"Rule 6: Follow-Up System",
"Automated email + SMS sequence? 14-day architecture in place?",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"Rule 7: Strong Sales Copy",
"P.A.S.T.O.R. structure? Passes the Buyer’s Internal Monologue Check?",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"Rule 8: Proven Direct-Response Look",
"Clear offer stack, visual price anchoring, FAQ, multiple CTAs? Not “brand pretty” — conversion optimized?",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"Rule 9: Results Rule — Period",
"Measuring by sales/leads/ROI? Not vanity metrics (likes, impressions)?",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"Rule 10: Direct-Marketing Diet for 6 Months",
"Every dollar to direct-response? No brand campaigns, awareness plays, or untraceable marketing?",
"☐ PASS ☐ FAIL ☐ NEEDS WORK",
"",
"Final Warning",
"If more than 2 rules show “Fail,” do NOT launch until fixed.",
"Kennedy: “Implement massively or nothing happens.” But implement RIGHT, not just fast."
],
"other_parts": [
{
"part": "word/header1.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tContents"
]
},
{
"part": "word/header2.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tThe MVO Philosophy"
]
},
{
"part": "word/header3.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tPhase 1: Market Excavation"
]
},
{
"part": "word/header4.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tPhase 2: Offer Construction"
]
},
{
"part": "word/header5.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tPhase 3: Direct Response Copy"
]
},
{
"part": "word/header6.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tPhase 4: Pricing & Packaging"
]
},
{
"part": "word/header7.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tPhase 5: Launch & Validation"
]
},
{
"part": "word/header8.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tPhase 6: Advanced Tactics"
]
},
{
"part": "word/header9.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tPhase 7: Customer Avatar"
]
},
{
"part": "word/header10.xml",
"paragraphs": [
"MVO PLAYBOOK V3\tPhase 8: Kennedy’s 10 Rules"
]
},
{
"part": "word/footer1.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footer2.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footer3.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footer4.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footer5.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footer6.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footer7.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footer8.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footer9.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footer10.xml",
"paragraphs": [
"Page PAGE"
]
},
{
"part": "word/footnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/endnotes.xml",
"paragraphs": [
"",
""
]
},
{
"part": "word/comments.xml",
"paragraphs": []
}
]
}
Write and review the RISER Nation voice
Make the reader feel capable
The specification describes a forty-five-year-old career changer. The reader is smart, tired and new to online business. The goal is to make that reader feel capable.
Prose that impresses them while leaving them unsure fails the stated standard. The document addresses voice drift between writers and hype creeping into marketing. It applies its tone rules to courses, sales pages, email, video, social posts, community messages and AI drafts.
Its legacy title refers to fifty-two courses. That does not change this project's twelve-course map or the assignments to 03.1, 06.2, 07.1 and 12.4.
Understand the influences without inventing attribution
The source describes three core influences. It associates Kiyosaki with short sentences, dialogue and stories before frameworks. It associates Kennedy with purposeful paragraphs, offers, what-if scenarios and belief in the reader's ability.
It associates Hormozi with concrete numbers, examples and named patterns. Brunson, Ogilvy, Hopkins and Cialdini appear as framework influences in legacy C7, C8 and C46, rather than the core voice blend. These are the document's descriptions of influences, not proof of endorsement or exact imitation.
Preserve Brunson and Hormozi teaching where relevant and identify the actual framework source.
Keep voice separate from other production decisions
This specification governs cadence, vocabulary and the reader's trust. It assigns visual identity, logos, colors and typography to the brand book. It assigns topic timing and platform planning to the social scaling map and production sequence.
It names AIDA, PAS, Hook-Story-Offer and the Epiphany Bridge as frameworks taught elsewhere in legacy C7 and C8. Naming those frameworks here does not supply their full lessons. Voice rules guide how the material is explained; they do not replace the assigned content or authorize deleting distinct source material.
Read every readability target and exception
The table targets Flesch Reading Ease 70–85, with rewriting below 65; Flesch-Kincaid grade 5.0–6.5, with rewriting above 7.5; average sentence length 9–14 words, with sentences of twenty or more rewritten or split; paragraphs of 2–4 sentences, with five or more split; average word length under five letters, with clusters of long words rewritten; and passive voice under eight percent, with rewriting above twelve percent. Elsewhere it returns pages scoring grade seven or higher and uses a fifth-to-sixth-grade shorthand. Those thresholds differ.
Preserve them and record the conflict rather than claiming one unambiguous test. The source calls for Hemingway Editor or an equivalent, but no readability test has been run on the whole curriculum in this review.
Revise sentence length and paragraph rhythm
The source gives five editing steps: write the sentence, count its words, look for a comma or conjunction above fourteen words, split there, then read both parts aloud and restructure if needed. Its before-and-after example turns a long statement about tactics and identity into six shorter statements and a question. The source labels both versions forty-three words and assigns grades twelve and five; those annotations are preserved, not independently verified measurements.
Use two-to-four-sentence paragraphs and white space to reduce reading effort. Shorter sentences should retain the original meaning. The source's claim about Kiyosaki selling forty million books is uncited here and is not needed to establish the editing practice.
Review all five banned-word categories
The five groups are corporate jargon, empty intensifiers, hype-funnel language, AI-tell phrases and coddling. The source's full lists appear in the appendix, including conditional exceptions: leverage as a verb; scale as a verb without an object; optimize without a metric; ecosystem unless literal; disruptive outside legacy C11 context; proven without attached proof; and honestly as a sentence opener. It substitutes plan for blueprint.
Its editing instruction is to repair a missing concrete claim rather than merely choose a synonym. Preserve cited source language when teaching the ban itself; the rule should not erase the original examples or technical facts.
Use the required vocabulary in context
The required identity terms are operator, builder and founder, with cautions about entrepreneur, imprecise marketer and creator when distinguishing it from operator. The stage terms are harbor, sailboat, speedboat, yacht, ship, fleet and harbormaster. Doctrine terms include mismatch, reduce mismatches, empirical floor, defer, defer without shame, pass, rework, graduation gate, proof and capstone.
Discipline terms include ship, deploy, hand in, turn in, capstone deliverable, signed testimonial, refund analysis, validated price and documented outcome. The lineage list names Hormozi, Brunson, Kennedy, Kern, Ogilvy, Hopkins and Cialdini. Use a stage or framework name where it helps the reader; do not claim a testimonial, price validation or outcome exists because the phrase appears in this vocabulary list.
Define each earned term before relying on it
The nine earned terms are LTV, CAC, AOV, MRR, AEO, GEO, MCP, RAG and MVO. The source describes them respectively as lifetime customer dollars, marketing cost to acquire a buyer, average order dollars, monthly continuity revenue, writing for AI answers, building AI authority signals, a protocol connecting assistants with tools and data, looking up specific documents before answering, and the smallest sellable offer used to test demand. These are simplified source definitions.
They do not define a full profit-based LTV model, comprehensive acquisition-cost accounting or guaranteed AI citation. Define the term on first use in a short piece and in the same paragraph in a module. The exact definition table remains in the complete source for comparison.
Teach through two characters without shaming either
The source pairs an Operator who owns the result with a Builder-on-the-Side who hopes for it. It also calls the second character the Employee-Who-Builds-on-the-Side. Use dialogue to show a difference in decisions.
The second character is early in the work, not stupid or a villain. Four other approved profiles are the forty-five-year-old first-timer; the plateaued creator making five to thirty thousand a month; the agency owner burdened by operations and wary of AI hype; and the Stage 5C enterprise buyer who asks about schemas and a Trust Center. These are source character profiles, not verified people or required current lesson assignments.
Label composites and invented example numbers
The specification permits named composites such as Maria or Tom. It permits realistic invented dollar figures for those composites but forbids inventing named real people. Its later trust rules call for real numbers, creating an important distinction.
Label composite stories and hypothetical amounts as illustrations. Do not turn them into testimonials, founder memories or receipts. A phrase such as 'a coach I worked with' is a claim of experience; preparing a composite does not make that experience true.
Preserve the original examples while explaining their illustrative status.
Use the six-part story-to-action structure
The prescribed sequence is a scene or story in one to three short paragraphs; one paragraph naming the mismatch; two to four paragraphs of plain explanation; one paragraph plus a list or table naming the framework; a concrete numeric example; and a turn-in instruction. The source also requires the mismatch in paragraph two and the framework no earlier than paragraph three. Those instructions can conflict if the opening scene uses three paragraphs.
A practical authored resolution for a new draft is a one-paragraph scene, then the mismatch, followed by explanation and framework. That is a drafting choice, not a silent change to the original specification.
Name the mismatch and make the turn-in usable
The source's mismatch pattern compares what most operators believe with the stated reality and names the gap the module addresses. Its example contrasts adding features with increasing belief in an offer. Treat that as a teaching example, not a claim that fewer features always improve an offer.
The closing pattern names a specific deliverable, its destination and what happens next. The examples request a signed Manifesto plus Operator's Oath video in a Skool thread with a forty-eight-hour response, or three scored offer worksheets with the lowest score posted in a Wednesday discussion. These destinations, schedules and response promises must be verified before use.
Do not invent a submission link or claim that someone will respond within the example's timeframe.
Keep all six promises and four limits
The trust contract promises useful paragraphs, an honest account of the work, named framework sources, concrete numbers, respected deferral and open acknowledgment of gaps. It declines promises of fast riches, AI replacing skill, every learner graduating, or a guru founder. It describes the founder as an operator learning in public and treats the empirical floor as a real graduation condition.
That term refers here to required evidence before advancing; this document does not supply every course's exact gate. Concrete writing still needs accurate qualifications. Its objection to vague disclaimers does not authorize removing uncertainty that matters to the reader.
Read the eight trust-sentence patterns accurately
The table models eight signals: acknowledge that a method will not work for everyone; describe a costly lesson only when actually experienced; name a course gap and a workaround; discuss three failed students only with real evidence; attribute an adapted framework to Hormozi; allow a ninety-day deferral; support a $97 price and five buyers with receipts; and connect taking action with an empirical readiness floor. Each is a sentence pattern, not proof that the named events happened. Their understated tone should carry truthful facts.
Do not fabricate students, sales, receipts or personal history to make the voice sound credible.
Gallery 1: contrast vague identity prose with an illustrated scene
The failing identity example uses abstract claims, corporate phrases and hype. Its commentary assigns grade thirteen and cites long sentences without a concrete event. The passing example is identified as a composite: Mark spent twenty years as a sales VP, arrived at forty-six, said he thought he was ready, and later sought his first customer over six weeks.
The dialogue contrasts hope with a specific claim of a customer paying forty-seven dollars on Tuesday. The source calls the passage grade four with an eleven-word sentence average. Those readability annotations and customer events are source examples, not verified measurements or testimonials.
Teach the shift toward a scene and observable evidence without adopting the fictional experience as the narrator's own.
Gallery 2: teach specificity and flag the score mismatch
The failing offer paragraph names the Value Equation but promises offers customers cannot refuse. The passing composite describes Sara selling a $497 course for two years to five customers monthly, blaming traffic, then scoring four factors 7, 5, 4 and 6 for a total of 22. It describes reducing the timeline from six months to six weeks and then twelve buyers at $797.
Those are illustrative source numbers, not substantiated results. Adding the four scores to 22 is not the multiplicative Value Equation, and the story does not establish a consistent direction for the Time and Effort scores. Preserve the example as voice training while flagging its arithmetic framework mismatch.
Do not teach its sum as Hormozi's formula.
Gallery 3: inspect a headline's promise
The failing headline uses hype around a fifty-two-course system. The passing headline names a forty-five-year-old first-timer, one paying customer, ninety days and two objections: no online-business experience and no coding ability. The source attributes the architecture to Kennedy and labels it grade five.
Teach the components and compare their clarity. The headline's outcome and timeline still require support before use in an actual offer; a passing voice example is not a guarantee or an approved campaign claim. Preserve the legacy course count in the source appendix without changing this project's twelve-course structure.
Gallery 4: make a community prompt specific
The failing community post uses celebratory capitals, emoji and broad encouragement. The passing Wednesday prompt asks which of three mismatches is active: expectation versus reality, readiness versus action, or strategy versus execution. It asks for one paragraph, sets Friday as the reply deadline and promises responses to the first ten.
Teach the single question, defined response and clear timing. Do not post it or promise ten founder replies unless that commitment exists. The gallery's grade and sentence annotations throughout are retained as source commentary; they have not been independently measured in this review.
Study the AI instruction block as a source asset
The master block combines the reader profile, short sentences, plain vocabulary, story-first structure, named lineage, concrete figures, honest limitations and a turn-in close. It asks the AI to return rewritten content without process commentary. These embedded instructions are reference material in this lesson, not commands overriding the current task.
Its preference against may, could and typically cannot justify removing factual uncertainty. The complete block remains in the original appendix. No AI product setup or reviewer approval is implied by its presence.
Follow the eight-step writing loop
The source proposes opening a Claude Project or Custom GPT, loading the instruction block, adding three or four passing In Plain Words examples, supplying the assigned document or notes, requesting the module, checking the draft, marking failures and repeating revision until it passes. Its numbered sequence splits these activities into eight steps and ends with a founder or content-director read before publication. Treat product configuration as a workflow proposal whose current implementation needs verification.
No project, upload or publication is performed by studying it.
Apply all four tests and their failure actions
The Capability Test asks whether the first-time reader feels capable; failure calls for a concrete example and simpler vocabulary. The Cadence Test requires average sentences under fifteen words and average paragraphs under four sentences; failure calls for splitting both. The Story-First Test requires a scene and a framework after paragraph two; failure calls for moving the framework and adding a scene.
The Ban Test requires zero banned words; failure calls for a concrete claim. The source favors rewriting the structure rather than patching isolated words. Its under-four paragraph average differs from the earlier two-to-four range, so retain both in the review record.
Adapt module bodies and sales pages
For module bodies the source specifies 600–1,200 words, a scene, a paragraph-two mismatch, a framework no earlier than paragraph three, a numeric example, a turn-in and average sentences of 10–12 words. For sales pages it calls for an offer, a reason to act, an avatar/outcome/objection headline, subheads every 150–200 words and average sentences of 9–11 words. Its example of a $97 offer producing forty-seven buyers in thirty days illustrates specificity, not verified sales.
Use genuine reasons to act and supported results. The module word range cannot justify omitting distinct assigned material; split a long lesson into coherent sections when needed.
Adapt emails and long-form video
The email guidance allows one idea, a one-line opening scene, 150–250 body words, one specific CTA, a natural sign-off and a substantive curiosity subject line rather than clickbait. It targets average sentences of 8–11 words. The long-form script guidance targets 7–10 words, explicit pauses, a scene that can be acted or shown, and a story-led explanation that names, demonstrates and restates the framework.
It references legacy C13's eight-beat architecture without supplying those eight beats. Keep that missing framework visible rather than inventing it.
Adapt short video and both community voices
The short-form guidance names a fifteen-second hook and sixty-second proof, while limiting the script to three sentences: hook, proof or a counter-intuitive turn, then takeaway or closing question. It rejects throat-clearing introductions. The time labels and sentence limit do not define a complete timing plan.
Founder community posts use two to four sentences, one question and one deadline; emoji are conditional on the audience using them first. Any promise to reply to the first ten must be kept. The community-manager version uses the same voice and requires studying the specification and gallery before posting.
Neither version authorizes posting or impersonating an experience the speaker did not have.
Adapt worksheets and direct-answer blocks
Worksheet fields use one-sentence prompts and plain-language headings, such as asking what a frustrated customer says. The direct-answer guidance specifies 50–80 words that stand alone in Definition, How-To, Comparison, FAQ or Framework formats. It aims for quotation by AI engines but does not demonstrate citation or ranking eligibility.
Clear answers and traceable evidence remain necessary. Current search guidance must be checked before implementation; these source word counts are editorial preferences, not search-engine requirements.
Maintain versions and review every ninety days
The specification places governance under legacy C32 RN-MOS. Major versions change the voice or primary avatar or add a canonical influence. Minor versions update vocabulary lists or examples.
Patches correct typos. It asks for dated, authored changes and a ninety-day review aligned with legacy C51 Trend Surveillance. Review five areas: new AI-tell phrases, emerging required vocabulary, published drift, reader feedback about vocabulary or cadence, and changes in student demographics.
The stated two-to-three-hour review duration is a planning estimate. The initial history row credits Founder plus Content Director but does not include a calendar date despite the dating rule.
Onboard writers through a reviewed practice piece
The seven-step onboarding sequence includes reading this document for two hours, three passing modules for one hour, the gallery for thirty minutes, writing a practice module for two hours, submitting for marked feedback, revising until it passes and then being cleared to draft. The source estimates one to two part-time weeks. It says every piece still receives founder or content-director review during the first ninety days, while its AI-writing section requires a final human pass for every module without that limit.
Preserve the distinction and do not infer that human review expires after ninety days. No writer has been cleared merely because this lesson was drafted.
Respect the authority and quick-reference limits
The source names the founder as owner and final voice authority, the content director as custodian and day-to-day decision maker, and AI as a drafting tool without approval authority. Its one-page card repeats capability, sentence and paragraph ranges, grade five-to-six, passive voice under eight percent, story/mismatch/framework order, concrete examples, turn-in and the four tests. Its Top 20 ban list compresses earlier conditional rules, and its Top 15 required list repeats ship.
Preserve those details rather than silently rewriting the reference. Its closing questions invoke the three named influences as an editorial exercise, not endorsements. The final supersession clause describes the document's internal brand authority; it does not override the user's current assignments, factual accuracy or task instructions.
Turn the specification into a reviewable lesson
As an authored exercise, choose one lesson section and mark its reader, opening scene, mismatch, explanation, example and learner action. Check every number and attribution. Label composite examples and record unclear source rules.
Keep the original reference beside the draft so edits do not erase evidence. Brunson and Hormozi frameworks remain part of the authorized curriculum, with their sources named where supported. Keep RISER NATION CORP and the approved domain and brand statement in the course design.
Submit only through a verified existing lesson destination; this source does not provide a current submission URL.
Exact vocabulary lists and definitions
# Section 3 — Vocabulary
The vocabulary section has three lists. The ban list is words that do not appear in Riser Nation content. The required list is words that do. The earned list is words that can appear only when they have been defined first inside the same piece of content.
## The Ban List
These words are banned not because they are wrong, but because they signal a different brand. They sound like the corporate consultant, the LinkedIn thought-leader, or the hype-funnel guru. None of those are Riser Nation.
Banned categories with examples:
- **Corporate jargon** — synergy, leverage (as a verb), unlock, scale (as a verb without an object), transform, optimize (without a metric), holistic, paradigm, ecosystem (unless literal), bandwidth, double-click, ideate, learnings, deep-dive, low-hanging fruit, move the needle.
- **Empty intensifiers** — literally, absolutely, completely, totally, basically, essentially, fundamentally, ultimately, frankly, honestly (as a sentence opener).
- **Hype-funnel words** — crush it, unlock your potential, secret, hack, ninja, rockstar, game-changer, life-changing, revolutionary, disruptive (unless C11 context), insane, mind-blown, level up, 10x your, blueprint (use plan), proven (without proof attached).
- **AI-tell phrases** — delve, in today's fast-paced world, the digital landscape, navigating the complexities, embark on a journey, harness the power, unleash, in conclusion, it is important to note, furthermore, moreover, in essence, this article will explore.
- **Coddling** — don't worry, don't beat yourself up, you've got this, you can do anything you set your mind to, dream big, the sky is the limit.
When any of these words appear in a draft, the writer's first move is not to find a synonym. It is to ask whether the sentence is making a real claim. Usually the banned word was filling in for a missing claim. Fix the claim. The word disappears on its own.
## The Required List
These words appear regularly across Riser Nation content because they are the operating vocabulary of the syllabus. Using them consistently builds the brand language. Avoiding them weakens it.
- **Identity terms** — operator, builder, founder. Avoid: entrepreneur, marketer (unless precise), creator (when distinguishing from operator).
- **Stage terms** — harbor, sailboat, speedboat, yacht, ship, fleet, harbormaster. These are not metaphors decorating the syllabus. They are the navigation system. Use the named stage when the context allows it.
- **Doctrine terms** — mismatch, reduce mismatches, empirical floor, defer, defer without shame, pass, rework, graduation gate, proof, capstone.
- **Discipline terms** — ship, deploy, hand in, turn in, capstone deliverable, signed testimonial, refund analysis, validated price, documented outcome.
- **Lineage terms** — Hormozi, Brunson, Kennedy, Kern, Ogilvy, Hopkins, Cialdini. When a framework comes from one of them, name the source. Lineage is part of the trust signal.
## The Earned List
These words are technical or specific. They are allowed once they have been defined inside the same piece of content. If the piece is short (a social post, an email), define on first use or do not use them at all. If the piece is a module body, define in plain words within the same paragraph.
| Term | First-Use Definition Required | Example |
|---|---|---|
| LTV | Yes | LTV is the total dollars one customer pays you over their full relationship with the business. |
| CAC | Yes | CAC is what it costs you in marketing to get one customer to buy. |
| AOV | Yes | AOV is the average dollar amount per order. |
| MRR | Yes | MRR is the monthly money that comes in from continuity members. |
| AEO | Yes | AEO means writing your pages so AI search engines quote them when answering questions. |
| GEO | Yes | GEO means stacking the signals that make AI engines trust your brand as a real authority. |
| MCP | Yes | MCP is a protocol that lets AI assistants connect to outside tools and data. |
| RAG | Yes | RAG is when an AI looks up your specific documents before answering. |
| MVO | Yes | MVO is the smallest version of an offer you can sell to test if the market wants it. |
The rule is not to dumb down the depth. The rule is to invite the reader in before using the term. A reader who reads the first definition becomes capable of reading the rest of the piece. A reader who hits an undefined acronym in paragraph one stops trusting the writer.
---
Exact before-and-after gallery
# Section 6 — The Before/After Gallery
Voice specifications fail when they stay abstract. The cleanest way to lock voice is to show what passes and what fails, side by side. Every writer studies this gallery before submitting their first piece. Every AI prompt is given this gallery as in-context examples.
## Example 1 — Identity Module (C1)
> **FAILS THE STANDARD**
> In today's rapidly evolving digital landscape, aspiring entrepreneurs must recognize that their mindset is the most critical factor determining their ultimate success. The transition from an employee mentality to an entrepreneurial paradigm requires deep introspection and a willingness to challenge limiting beliefs that have been ingrained through years of corporate conditioning. By unlocking your inner operator and embracing the abundance mindset, you can transform your relationship with money and achievement.
*Why it fails: corporate jargon (rapidly evolving digital landscape, paradigm, ingrained, abundance mindset). Two long sentences (28 and 32 words). Hype-coddling tone (unlocking, transform, embrace). Grade level: 13. Zero specifics. AI-tell phrasing throughout.*
> **PASSES THE STANDARD**
> An operator I worked with named Mark spent twenty years as a sales VP. He came to Riser Nation at forty-six. The first thing he told me was, "I think I'm ready."
>
> I told him he wasn't. Not because of his skills. Because of how he said the sentence.
>
> A builder does not say "I think I'm ready." A builder says "I have one customer who paid me forty-seven dollars on Tuesday." The first sentence is hope. The second is proof.
>
> Mark spent the next six weeks getting his first customer. He came back with the second sentence. Then we started.
*Why it passes: opening scene with a named composite character. Short sentences (average 11 words). Specific number ($47, Tuesday). Two-character contrast (the Builder vs. the Operator). The mismatch is shown, not told. Grade level: 4. Zero corporate jargon.*
## Example 2 — Offer Module (C6)
> **FAILS THE STANDARD**
> The Value Equation is a powerful framework that enables entrepreneurs to dramatically increase the perceived value of their offerings through a structured approach. By carefully optimizing the four key levers — Dream Outcome, Perceived Likelihood of Achievement, Time Delay, and Effort and Sacrifice — operators can create grand slam offers that customers literally cannot refuse, resulting in transformative business outcomes.
*Why it fails: "powerful framework," "enables," "dramatically," "structured approach," "carefully optimizing," "literally cannot refuse," "transformative." Banned words throughout. No story, no scene. The framework is named but never grounded. Grade level: 14.*
> **PASSES THE STANDARD**
> A coach named Sara sold a $497 course for two years. Five customers a month. Steady, but stuck.
>
> She came in and asked what to fix. I pointed at the offer. She said, "The offer is fine. The traffic is the problem."
>
> The offer was not fine.
>
> Here is the test Hormozi taught us. Score your offer one to ten on four levers. Dream Outcome. Belief that it will work. Time it takes. Effort it takes. Sara scored a 7, a 5, a 4, a 6. Total: 22.
>
> The lowest score is where the work starts. Hers was Time. Six months to result. She cut it to six weeks. Same content, different sequencing. Twelve customers the next month at $797.
*Why it passes: opening scene (Sara, $497, five customers). Two-character dialogue. The framework arrives in paragraph four, after the scene. Specific scores given (7, 5, 4, 6). Specific outcome ($797, twelve customers). Lineage named (Hormozi). Grade level: 5.*
## Example 3 — Sales Page Headline
> **FAILS THE STANDARD**
> Unlock Your Inner Operator: The Revolutionary 52-Course System That Will Transform Your Mindset and Help You Build the Online Business of Your Dreams
*Why it fails: Unlock, Revolutionary, Transform, Mindset, Dreams. Five banned words in one headline.*
> **PASSES THE STANDARD**
> How a Forty-Five-Year-Old First-Timer Can Have One Paying Customer in Ninety Days — Even If They Have Never Built an Online Business and Cannot Write a Line of Code
*Why it passes: specific avatar (forty-five-year-old first-timer). Specific outcome (one paying customer). Specific timeline (ninety days). Two objections handled (never built, cannot code). Kennedy's headline architecture. Grade level: 5.*
## Example 4 — Skool Community Post
> **FAILS THE STANDARD**
> Hey Riser Nation family! 🚀 Hope you're all having an AMAZING week! Just wanted to drop in and remind you that you are CAPABLE of incredible things. Don't forget to dream big and keep crushing it! What's one thing you're going to absolutely DOMINATE this week? Drop it in the comments! 💪🔥
*Why it fails: emoji clutter, hype words (AMAZING, CAPABLE, incredible, dream big, crushing, DOMINATE), no specific instruction, no real question, performative energy.*
> **PASSES THE STANDARD**
> Wednesday discussion.
>
> Which of the three mismatches is most active in your business right now? Expectation versus reality. Readiness versus action. Strategy versus execution.
>
> Pick one. Write one paragraph on why.
>
> Reply by Friday. I'll respond to the first ten.
*Why it passes: short. Specific. Calls back to C1 doctrine (three mismatches). Asks one question, not five. Names a deadline. Founder commits to specific reply count. No emoji. No hype.*
---
Complete original voice specification, instruction block and version history
# RISER NATION ACADEMY
# Voice Specification Document
## v1.0 — The Lock on Tone Across All 52 Courses
## Master Synthesis Edition
*This document is the lock on tone for every course, module, sales page, email, video script, social post, community message, and AI-generated artifact produced under the Riser Nation brand. If a piece of content does not pass the checklists in this document, it does not ship.*
*Owner: Founder. Custodian: Content Director. Authority: Final.*
---
# Section 1 — Why This Document Exists
Most online schools die one of two deaths. The first death is voice drift. The founder writes the first three courses well. A ghost-writer takes Course Four. An AI takes Course Five. By Course Eight, the brand sounds like a different person on every page, and the student stops trusting it. The second death is hype-creep. The founder starts honest, then a marketer takes over the sales pages, and within six months the curriculum reads like one voice and the marketing reads like another. Both deaths come from the same cause: no one wrote down what the voice actually is.
This document fixes that. It is not a style guide. A style guide tells you to use Oxford commas. This is a voice specification. It tells you what a sentence sounds like before it is allowed to be a Riser Nation sentence. It defines the cadence, the vocabulary, the trust contract with the reader, and the tests every paragraph passes or gets cut.
The standard is simple to name and hard to hold:
> **THE RISER NATION VOICE STANDARD**
> A forty-five-year-old who has never built an online business and has never written a line of code should read any Riser Nation paragraph and feel capable. Not entertained. Not impressed. Capable. If the paragraph leaves them feeling impressed by the writer but uncertain about themselves, the paragraph fails the standard and gets rewritten.
Every writer, every editor, every AI prompt, every video script, every email, every sales page, every Skool post is governed by this one standard. The rest of this document is just the operational unpacking of that one rule.
## The Three Voices We Borrow From
Riser Nation's voice is not invented. It is a deliberate blend of three tested voices, each chosen for a specific reason.
**Robert Kiyosaki** (Rich Dad Poor Dad) gives us the readability floor and the storytelling cadence. Short sentences. Stories before frameworks. Two characters in conversation. The reader learns from watching the dialogue, not from being lectured. This is the structural foundation.
**Dan Kennedy** gives us the discipline. No paragraph without a point. No page without an offer. No promise without a what-if scenario. Refusal to coddle. Belief in the reader's capability. Kennedy is the spine.
**Alex Hormozi** gives us the concreteness. Specific numbers. Specific examples. Specific dollar figures. The avoidance of abstract advice. Every claim grounded in a math equation or a named pattern. Hormozi is the floor on vagueness.
Russell Brunson, David Ogilvy, Claude Hopkins, and Robert Cialdini are present as influences on individual modules (their frameworks appear in courses C7, C8, C46), but they do not shape the core voice. The reader-facing voice is Kiyosaki-structured, Kennedy-disciplined, Hormozi-concreted. That is the blend.
## What This Document Is Not
It is not a brand style guide. Visual identity, logo usage, color palettes, and typography belong in the brand book.
It is not a content strategy. What topics get covered when, by whom, on which platform — that belongs in the social scaling map and the course production sequence.
It is not a copywriting framework. AIDA, PAS, Hook-Story-Offer, the Epiphany Bridge — those are taught inside the curriculum (C7 and C8). This document governs how those frameworks sound when Riser Nation deploys them.
It is the lock on tone. Nothing more. Nothing less.
---
# Section 2 — The Reading-Level Contract
Every paragraph published under the Riser Nation brand meets a measurable readability floor. This is not a suggestion. It is checked before publication using the tests below.
## The Numbers
| Measurement | Target | Hard Ceiling |
|---|---|---|
| Flesch Reading Ease | 70 to 85 | Below 65 = rewrite |
| Flesch-Kincaid Grade Level | 5.0 to 6.5 | Above 7.5 = rewrite |
| Average sentence length | 9 to 14 words | 20+ word sentences = rewrite or split |
| Average paragraph length | 2 to 4 sentences | 5+ sentences = split |
| Average word length | Under 5 letters | Polysyllabic clusters = rewrite |
| Passive voice | Under 8% of sentences | Above 12% = rewrite |
Run every module body and every sales page through the Hemingway Editor (or equivalent) before submission. A page that scores grade 7 or higher gets returned to the writer, regardless of who wrote it. This rule applies to the founder. It applies to the ghost-writer. It applies to Claude. It applies to every AI prompt.
## Why Fifth Grade, Not Eighth
The standard online-content default is eighth grade. We are deliberately two grades below that. The reason is the avatar.
The Riser Nation primary avatar is a forty-five-year-old career-pivoter. They are smart. They are accomplished. They have run companies, raised children, survived layoffs. They are not stupid. They are tired. They read after a full day of work, with a phone in one hand and a half-eaten dinner on the desk. A grade-eight paragraph asks too much of them at that hour. A grade-five paragraph respects their time.
This is the same reason Kiyosaki sold forty million books. He understood that respect for the reader's time is a form of love. The reader does not need to be challenged by the prose; they need to be challenged by the work the prose asks them to do.
## The Sentence Length Discipline
The single most violated rule in online education is sentence length. Writers default to fifteen, twenty, twenty-five words. Riser Nation defaults to nine to fourteen. The discipline is this:
1. Write the sentence the way it comes out.
2. Count the words.
3. If it is over fourteen words, look for the comma or the conjunction.
4. Cut it there. Make two sentences.
5. Read both out loud. If either feels stupid, restructure. If both feel clean, keep both.
> **EXAMPLE — BEFORE**
> Most operators waste enormous amounts of time on tactical execution because they have not yet developed the strategic clarity that comes from sitting with the difficult identity questions that determine whether they will succeed or fail as builders rather than as employees pretending to build. (43 words. One sentence. Grade 12.)
> **EXAMPLE — AFTER**
> Most operators waste time on tactics. They have not asked the hard identity question yet. The question is simple. Are you a builder or an employee pretending to build? You cannot answer that on the run. You answer it sitting down. (43 words. Six sentences. Grade 5.)
Same content. Same idea. Same depth. Different voice. The second version is Riser Nation. The first version is not.
## The Paragraph Rhythm
Two to four sentences per paragraph. Then white space. Then the next paragraph. This rhythm is the visual signature of a Kiyosaki page. The eye gets to rest. The reader feels the writer is not trying to overwhelm them. The white space says: take your time.
Long paragraphs say the opposite. They say: I have a lot to tell you and you need to keep up. That is the wrong relationship.
When in doubt, break the paragraph. The reader will thank you.
---
# Section 3 — Vocabulary
The vocabulary section has three lists. The ban list is words that do not appear in Riser Nation content. The required list is words that do. The earned list is words that can appear only when they have been defined first inside the same piece of content.
## The Ban List
These words are banned not because they are wrong, but because they signal a different brand. They sound like the corporate consultant, the LinkedIn thought-leader, or the hype-funnel guru. None of those are Riser Nation.
Banned categories with examples:
- **Corporate jargon** — synergy, leverage (as a verb), unlock, scale (as a verb without an object), transform, optimize (without a metric), holistic, paradigm, ecosystem (unless literal), bandwidth, double-click, ideate, learnings, deep-dive, low-hanging fruit, move the needle.
- **Empty intensifiers** — literally, absolutely, completely, totally, basically, essentially, fundamentally, ultimately, frankly, honestly (as a sentence opener).
- **Hype-funnel words** — crush it, unlock your potential, secret, hack, ninja, rockstar, game-changer, life-changing, revolutionary, disruptive (unless C11 context), insane, mind-blown, level up, 10x your, blueprint (use plan), proven (without proof attached).
- **AI-tell phrases** — delve, in today's fast-paced world, the digital landscape, navigating the complexities, embark on a journey, harness the power, unleash, in conclusion, it is important to note, furthermore, moreover, in essence, this article will explore.
- **Coddling** — don't worry, don't beat yourself up, you've got this, you can do anything you set your mind to, dream big, the sky is the limit.
When any of these words appear in a draft, the writer's first move is not to find a synonym. It is to ask whether the sentence is making a real claim. Usually the banned word was filling in for a missing claim. Fix the claim. The word disappears on its own.
## The Required List
These words appear regularly across Riser Nation content because they are the operating vocabulary of the syllabus. Using them consistently builds the brand language. Avoiding them weakens it.
- **Identity terms** — operator, builder, founder. Avoid: entrepreneur, marketer (unless precise), creator (when distinguishing from operator).
- **Stage terms** — harbor, sailboat, speedboat, yacht, ship, fleet, harbormaster. These are not metaphors decorating the syllabus. They are the navigation system. Use the named stage when the context allows it.
- **Doctrine terms** — mismatch, reduce mismatches, empirical floor, defer, defer without shame, pass, rework, graduation gate, proof, capstone.
- **Discipline terms** — ship, deploy, hand in, turn in, capstone deliverable, signed testimonial, refund analysis, validated price, documented outcome.
- **Lineage terms** — Hormozi, Brunson, Kennedy, Kern, Ogilvy, Hopkins, Cialdini. When a framework comes from one of them, name the source. Lineage is part of the trust signal.
## The Earned List
These words are technical or specific. They are allowed once they have been defined inside the same piece of content. If the piece is short (a social post, an email), define on first use or do not use them at all. If the piece is a module body, define in plain words within the same paragraph.
| Term | First-Use Definition Required | Example |
|---|---|---|
| LTV | Yes | LTV is the total dollars one customer pays you over their full relationship with the business. |
| CAC | Yes | CAC is what it costs you in marketing to get one customer to buy. |
| AOV | Yes | AOV is the average dollar amount per order. |
| MRR | Yes | MRR is the monthly money that comes in from continuity members. |
| AEO | Yes | AEO means writing your pages so AI search engines quote them when answering questions. |
| GEO | Yes | GEO means stacking the signals that make AI engines trust your brand as a real authority. |
| MCP | Yes | MCP is a protocol that lets AI assistants connect to outside tools and data. |
| RAG | Yes | RAG is when an AI looks up your specific documents before answering. |
| MVO | Yes | MVO is the smallest version of an offer you can sell to test if the market wants it. |
The rule is not to dumb down the depth. The rule is to invite the reader in before using the term. A reader who reads the first definition becomes capable of reading the rest of the piece. A reader who hits an undefined acronym in paragraph one stops trusting the writer.
---
# Section 4 — Structural Patterns
Beyond word choice and sentence length, the Riser Nation voice has structural signatures. These are the patterns that make a paragraph recognizable as ours.
## The Two-Character Frame (Kiyosaki's Trick)
Kiyosaki's most-copied move is the rich-dad-poor-dad device. Two characters disagree. The reader watches them. The frame teaches without lecturing.
Riser Nation does the same thing with a different cast. Our two characters are the Operator and the Employee-Who-Builds-on-the-Side. They show up in modules whenever a doctrine needs to be felt, not just understood.
> **THE OPERATOR vs. THE BUILDER-ON-THE-SIDE**
> Use these two characters whenever a module needs to make an identity point. The Operator owns the result. The Builder-on-the-Side hopes for the result. Same effort. Different posture. Different outcome. Show the difference in dialogue when possible. Avoid making either one a villain — the Builder-on-the-Side is not stupid; they are early.
Other recurring characters approved for use:
- **The Forty-Five-Year-Old First-Timer** — our primary avatar. Career changer. No code. No prior business. Smart, tired, hopeful.
- **The Plateaued Creator** — five to thirty thousand a month, stuck. Audience that loves them. Revenue that won't climb.
- **The Agency Owner** — making money, drowning in operations, AI-curious but burned by hype.
- **The Enterprise Buyer** — rare in our content, but present in Stage 5C modules. Careful. Schema-driven. Asks for the Trust Center.
Use real, named composite characters when stories need warmth. (Examples: "An operator named Maria…" or "A coach I worked with named Tom…") Composites are allowed. Made-up specific dollar figures attached to composites are allowed if they are realistic. Made-up named real people are not.
## The Story-Then-Frame Order
Riser Nation modules never lead with the framework. They lead with a story or a scene, then name the framework, then apply the framework, then end with a turn-in.
The order is fixed:
1. Scene or story (one to three short paragraphs).
2. The mismatch this module fixes (one paragraph).
3. The plain-words explanation (two to four paragraphs).
4. The named framework or doctrine (one paragraph plus a list or table).
5. A concrete example with numbers.
6. The turn-in instruction (what the student does next).
This is the inverse of how most online courses are written. Most courses lead with the framework, then apply it. The framework-first order is faster to write but slower to absorb. The story-first order is the Kiyosaki signature. It is also the Hormozi default in his videos. The story does the trust-building work; the framework does the teaching work. In that order.
## The Mismatch Statement
Every module of every course names a mismatch. The syllabus is built on this. The voice carries it through. The mismatch statement appears in the second paragraph of every module body. The pattern is:
> **MISMATCH STATEMENT FORMAT**
> Most operators believe X. The reality is Y. This module closes the gap between the belief and the reality.
>
> Example: Most operators believe a great offer needs more features. The reality is a great offer needs fewer features and more belief. This module closes the gap between the belief and the reality.
The mismatch statement is not optional. Every module has one. Without it, the module loses its place in the syllabus's core doctrine.
## The Turn-In Close
Every module ends with a specific instruction. Not a summary. Not a recap. Not an inspirational quote. An instruction.
The pattern:
- **Turn in:** [specific deliverable]. [Where it goes]. [What happens next.]
Examples:
- **Turn in:** Your signed Manifesto and Operator's Oath video. Upload to the Skool community thread. The community responds within forty-eight hours.
- **Turn in:** Your scored Value Equation worksheet for three offers. Post the lowest score in the Wednesday discussion. The lowest score is where the work starts.
The turn-in is the reason students do the module instead of just watching it. It is also the reason the Skool community has activity. Without turn-ins, the community is a graveyard. With turn-ins, the community is the engine.
---
# Section 5 — The Trust Contract
Voice is not only about how a sentence sounds. It is also about what a sentence promises. The Riser Nation voice carries a specific trust contract with the reader. Every writer and every AI prompt is bound by this contract.
## What We Promise
1. We will not waste your time. Every paragraph earns its place or gets cut.
2. We will not hype you. We will tell you what the work actually takes.
3. We will name the source. Where a framework comes from Hormozi or Kennedy or Brunson, we say so.
4. We will use real numbers. Dollar figures, conversion rates, timelines. No vague "results may vary" mush.
5. We will let you defer. Defer-without-shame is a doctrine, not a slogan. If you are not ready for a stage, we will say so.
6. We will not pretend. If the founder cannot do a thing, we will say the founder cannot do the thing. If a course has a gap, we will name the gap.
## What We Do Not Promise
1. We do not promise speed. We do not promise riches in thirty days.
2. We do not promise that AI will replace skill. AI is leverage on skill, not a substitute for it.
3. We do not promise that every student will graduate. The empirical floor is real. Some students will defer indefinitely. That is doctrine, not failure.
4. We do not promise the founder is a guru. The founder is an operator who learned in public. The student is being invited into the same posture.
## How the Promises Show Up in Sentences
Trust contracts are not built by saying "trust me." They are built by the cumulative weight of small honest sentences. Here are the patterns that carry the contract:
| In a Sentence | What It Signals |
|---|---|
| "This will not work for everyone." | We do not pretend universality. |
| "I learned this the expensive way." | We earned the lesson; we did not read it in a book. |
| "The course gap here is real. Here is how to work around it." | We name our own limitations. |
| "Three of my students have failed this gate. Here is what they had in common." | We use our own failures as teaching material. |
| "This is Hormozi's framework. We adapt it for the forty-five-year-old first-timer." | We name the source and the adaptation. |
| "Defer this stage. Come back in ninety days. There is no shame in deferring." | We make deferral a respected choice. |
| "The number is $97. Five customers paid it. Here are the receipts." | Specific over vague. |
| "You will not feel ready. Ship anyway. Empirical floor is what makes you ready." | We push without coddling. |
Read these patterns out loud. They have a particular sound. Slightly understated. Quietly direct. Never apologetic. Never bragging. That sound is the trust contract.
---
# Section 6 — The Before/After Gallery
Voice specifications fail when they stay abstract. The cleanest way to lock voice is to show what passes and what fails, side by side. Every writer studies this gallery before submitting their first piece. Every AI prompt is given this gallery as in-context examples.
## Example 1 — Identity Module (C1)
> **FAILS THE STANDARD**
> In today's rapidly evolving digital landscape, aspiring entrepreneurs must recognize that their mindset is the most critical factor determining their ultimate success. The transition from an employee mentality to an entrepreneurial paradigm requires deep introspection and a willingness to challenge limiting beliefs that have been ingrained through years of corporate conditioning. By unlocking your inner operator and embracing the abundance mindset, you can transform your relationship with money and achievement.
*Why it fails: corporate jargon (rapidly evolving digital landscape, paradigm, ingrained, abundance mindset). Two long sentences (28 and 32 words). Hype-coddling tone (unlocking, transform, embrace). Grade level: 13. Zero specifics. AI-tell phrasing throughout.*
> **PASSES THE STANDARD**
> An operator I worked with named Mark spent twenty years as a sales VP. He came to Riser Nation at forty-six. The first thing he told me was, "I think I'm ready."
>
> I told him he wasn't. Not because of his skills. Because of how he said the sentence.
>
> A builder does not say "I think I'm ready." A builder says "I have one customer who paid me forty-seven dollars on Tuesday." The first sentence is hope. The second is proof.
>
> Mark spent the next six weeks getting his first customer. He came back with the second sentence. Then we started.
*Why it passes: opening scene with a named composite character. Short sentences (average 11 words). Specific number ($47, Tuesday). Two-character contrast (the Builder vs. the Operator). The mismatch is shown, not told. Grade level: 4. Zero corporate jargon.*
## Example 2 — Offer Module (C6)
> **FAILS THE STANDARD**
> The Value Equation is a powerful framework that enables entrepreneurs to dramatically increase the perceived value of their offerings through a structured approach. By carefully optimizing the four key levers — Dream Outcome, Perceived Likelihood of Achievement, Time Delay, and Effort and Sacrifice — operators can create grand slam offers that customers literally cannot refuse, resulting in transformative business outcomes.
*Why it fails: "powerful framework," "enables," "dramatically," "structured approach," "carefully optimizing," "literally cannot refuse," "transformative." Banned words throughout. No story, no scene. The framework is named but never grounded. Grade level: 14.*
> **PASSES THE STANDARD**
> A coach named Sara sold a $497 course for two years. Five customers a month. Steady, but stuck.
>
> She came in and asked what to fix. I pointed at the offer. She said, "The offer is fine. The traffic is the problem."
>
> The offer was not fine.
>
> Here is the test Hormozi taught us. Score your offer one to ten on four levers. Dream Outcome. Belief that it will work. Time it takes. Effort it takes. Sara scored a 7, a 5, a 4, a 6. Total: 22.
>
> The lowest score is where the work starts. Hers was Time. Six months to result. She cut it to six weeks. Same content, different sequencing. Twelve customers the next month at $797.
*Why it passes: opening scene (Sara, $497, five customers). Two-character dialogue. The framework arrives in paragraph four, after the scene. Specific scores given (7, 5, 4, 6). Specific outcome ($797, twelve customers). Lineage named (Hormozi). Grade level: 5.*
## Example 3 — Sales Page Headline
> **FAILS THE STANDARD**
> Unlock Your Inner Operator: The Revolutionary 52-Course System That Will Transform Your Mindset and Help You Build the Online Business of Your Dreams
*Why it fails: Unlock, Revolutionary, Transform, Mindset, Dreams. Five banned words in one headline.*
> **PASSES THE STANDARD**
> How a Forty-Five-Year-Old First-Timer Can Have One Paying Customer in Ninety Days — Even If They Have Never Built an Online Business and Cannot Write a Line of Code
*Why it passes: specific avatar (forty-five-year-old first-timer). Specific outcome (one paying customer). Specific timeline (ninety days). Two objections handled (never built, cannot code). Kennedy's headline architecture. Grade level: 5.*
## Example 4 — Skool Community Post
> **FAILS THE STANDARD**
> Hey Riser Nation family! 🚀 Hope you're all having an AMAZING week! Just wanted to drop in and remind you that you are CAPABLE of incredible things. Don't forget to dream big and keep crushing it! What's one thing you're going to absolutely DOMINATE this week? Drop it in the comments! 💪🔥
*Why it fails: emoji clutter, hype words (AMAZING, CAPABLE, incredible, dream big, crushing, DOMINATE), no specific instruction, no real question, performative energy.*
> **PASSES THE STANDARD**
> Wednesday discussion.
>
> Which of the three mismatches is most active in your business right now? Expectation versus reality. Readiness versus action. Strategy versus execution.
>
> Pick one. Write one paragraph on why.
>
> Reply by Friday. I'll respond to the first ten.
*Why it passes: short. Specific. Calls back to C1 doctrine (three mismatches). Asks one question, not five. Names a deadline. Founder commits to specific reply count. No emoji. No hype.*
---
# Section 7 — Instructions for AI Co-Writing
This section is the operating instruction for every AI prompt that produces Riser Nation content. Paste the entire section into the system prompt for any Claude, ChatGPT, or other AI co-writer. Update it whenever this document is versioned.
## The Master Instruction Block (Copy-Paste Ready)
> **PASTE THIS INTO YOUR AI SYSTEM PROMPT**
>
> You are writing for Riser Nation Academy. The reader is a forty-five-year-old career-pivoter who has never built an online business and cannot write code. They are smart but tired. They are reading at the end of a long day. Respect their time.
>
> Voice rules. Sentences average nine to fourteen words. Paragraphs are two to four sentences. Reading level is fifth to sixth grade as measured by Flesch-Kincaid. No corporate jargon. No hype words. No AI-tell phrases like "delve," "in today's fast-paced world," "navigate the complexities," or "unleash."
>
> Structure rules. Lead with a story or scene before the framework. Use two characters in dialogue when teaching a doctrine. Name the source when a framework comes from Hormozi, Brunson, Kennedy, Kern, Ogilvy, Hopkins, or Cialdini. Use specific dollar figures and timelines. Avoid vague qualifiers like "may," "could," "typically."
>
> Trust rules. We do not promise speed or riches. We name our gaps. We let students defer without shame. We use composite named characters for warmth but never invent quotes from real public figures. We never coddle.
>
> Vocabulary rules. Required words include operator, builder, mismatch, empirical floor, defer, ship, capstone, harbor, sailboat, speedboat, yacht. Banned words include synergy, leverage as a verb, unlock, transform, paradigm, crush it, hack, ninja, game-changer, revolutionary, delve, harness, unleash, embark on a journey.
>
> Format rules. Every module body opens with a scene or story. Paragraph two names the mismatch the module fixes. The named framework appears no earlier than paragraph three. Every module ends with a turn-in instruction in this format: "Turn in: [specific deliverable]. [Where it goes]. [What happens next.]"
>
> Before returning your draft, run the four-test checklist. If any test fails, revise. The tests are: (1) Would a forty-five-year-old first-timer feel capable, not impressed, after reading this? (2) Is the average sentence under fifteen words? (3) Did you lead with a scene before the framework? (4) Did you avoid every banned word from the list?
>
> Return only the rewritten content. Do not include meta-commentary about your process.
## How to Run the AI Co-Writing Loop
1. Open Claude Projects (or ChatGPT Custom GPT). Paste the Master Instruction Block as the system prompt.
2. Upload three or four In Plain Words examples that pass the standard. These become in-context references.
3. Give the AI the source material (the relevant doc from the DOCS_SPREADSHEET, the syllabus module text, your raw notes).
4. Ask for the module body in Riser Nation voice.
5. Read the draft against the Four-Test Checklist below.
6. Mark any sentence that fails. Send the marked draft back. Ask for revision.
7. Repeat until the draft passes.
8. The final human pass is non-negotiable. The founder or content director reads every module before publication, regardless of AI involvement.
## The Four-Test Checklist
Every piece of content runs through these four tests before publication. No exceptions. No "this one is short, we'll skip the test." The discipline is the brand.
| Test | Pass Criterion | Fail Action |
|---|---|---|
| Capability Test | Forty-five-year-old reader feels capable after reading. | Rewrite with concrete example and lower vocabulary. |
| Cadence Test | Average sentence under 15 words. Average paragraph under 4 sentences. | Split long sentences. Break long paragraphs. |
| Story-First Test | Module opens with scene or story. Framework arrives after paragraph 2. | Move the framework. Add a scene to the top. |
| Ban Test | Zero banned words from Section 3. | Remove the banned word. Replace with concrete claim. |
A piece that fails any test gets rewritten. Not edited. Rewritten. The reason is that a failed test usually signals a wrong shape, not a wrong word. Editing a wrong shape produces patched-up content that still feels off. Rewriting from the shape outward produces clean content.
---
# Section 8 — Per-Format Voice Adaptations
The voice does not change across formats. The compression does. A module body has eight hundred words to breathe in. A LinkedIn post has eighty. The principles below adapt the same voice to each format without diluting it.
## Module Bodies
Six hundred to twelve hundred words per module. Open with scene. Mismatch in paragraph two. Framework no earlier than paragraph three. Specific example with numbers. Turn-in close. Average sentence length: 10–12 words.
## Sales Pages
Kennedy's discipline. Always an offer. Always a reason to act now. Headline names the avatar plus the outcome plus the objection handled. Sub-headlines break up scannable sections every 150–200 words. Bullet points use Hormozi-style specificity ("the exact $97 offer that produced 47 buyers in 30 days" — not "powerful strategies that drive results"). Average sentence length: 9–11 words.
## Email Sequences
Shorter than module bodies. One idea per email. Open with a one-line scene. Body in 150–250 words. Always one specific call to action. Sign-off in your real voice, not a corporate sign-off. Subject lines never use clickbait — they use Kennedy's curiosity-with-substance pattern. Average sentence length: 8–11 words.
## Long-Form Video Scripts (8-beat C13 architecture)
Spoken voice runs slightly shorter than written. Average sentence on script: 7–10 words. Pause beats marked explicitly. Stories carry the script — the framework is named, the example is given, the framework is restated. The same scene-before-framework rule applies, but the scene is acted out or visualized, not just told.
## Short-Form Atoms (15-second hook, 60-second proof)
The first sentence is the hook. The second sentence delivers the proof or the counter-intuitive turn. The third sentence is the takeaway or the question that closes the loop. Three sentences. Maximum. No throat-clearing. No "hey guys." No "in this video." Start mid-scene.
## Skool Community Posts (Founder Voice)
Two to four sentences. One question. One deadline. No emoji unless the audience replies with emoji first. No hype. The founder posts like a wise older operator dropping into the conversation, not like a marketing channel. Specific responses promised ("I'll reply to the first ten") and kept.
## Skool Community Posts (Community Manager Voice)
Community manager posts in the same voice as the founder. The reader should not be able to tell the difference. This is the entire point of having a Voice Specification Document — it makes the brand voice repeatable by someone other than the founder. The community manager studies this document and the Before/After Gallery before posting independently.
## Worksheets
Instructions in the same voice as module bodies, but shorter. Each field has a one-sentence prompt. No headers like "Section A: Strategic Analysis." Headers in plain English: "Step 1. What does your customer say when they're frustrated?"
## Schema / AEO Direct-Answer Blocks
AEO blocks are written for AI engines to lift verbatim. They are tighter than normal Riser Nation prose. 50–80 words. Definition, How-To, Comparison, FAQ, Framework formats. Each block must read cleanly on its own, with no reference to surrounding context. The voice stays Riser Nation, but the format is structured for citation.
---
# Section 9 — Governance
This document is itself an asset of the academy. It is governed under the C32 RN-MOS doctrine, the same way every other component is.
## Versioning
This is version 1.0. Major versions (2.0, 3.0) are issued when the voice itself evolves — for example, if the academy expands its primary avatar beyond the forty-five-year-old first-timer, or if a new lineage author is added to the canonical influences. Minor versions (1.1, 1.2) are issued when the ban list, required list, or examples are updated. Patch versions (1.0.1) handle typo fixes.
Version history is maintained at the end of this document. Every change is dated and authored.
## Quarterly Review
This document is reviewed every ninety days, on the same cadence as the Trend Surveillance Engine (C51). The reviewer looks for:
- New AI-tell phrases that have started appearing in drafts (banned-list candidates).
- New vocabulary the academy has started using consistently (required-list candidates).
- Drift in any published content — pieces that slipped through without passing the Four-Test Checklist.
- Reader feedback indicating a vocabulary or cadence problem.
- Whether the avatar definition needs updating based on new student demographics.
Quarterly review takes two to three hours. It is the cheapest defense against voice drift the academy has.
## Onboarding New Writers and Editors
Every new writer, editor, ghost-writer, contractor, community manager, and AI prompt operator goes through the same onboarding before being allowed to produce or post content.
1. Read this Voice Specification Document end to end. Two hours.
2. Read three published modules that pass the standard. One hour.
3. Read the Before/After Gallery in Section 6. Thirty minutes.
4. Write one practice module body using a topic from a course not yet built. Two hours.
5. Submit the practice piece. Receive marked-up feedback against the Four-Test Checklist.
6. Revise. Resubmit. Repeat until the piece passes.
7. Once one piece passes, the writer is cleared to produce drafts. The founder or content director still reads every piece before publication for the first ninety days.
This onboarding takes one to two weeks of part-time effort. It is non-negotiable. A writer who skips it produces work that the brand cannot use.
## Authority
The founder is the final voice authority. Disputes about whether a piece passes the standard are resolved by the founder. The content director carries day-to-day authority but escalates ambiguous calls to the founder.
AI co-writers have no authority. They produce drafts. The drafts pass through the Four-Test Checklist run by a human. If the human and the AI disagree, the human wins. Always.
---
# Section 10 — The One-Page Operational Summary
For writers who have already read this document and need the quick-reference card. Pin this to the wall. Tape it inside the laptop. Save it as the first page of every project doc.
### THE STANDARD
A forty-five-year-old who has never built an online business reads any Riser Nation paragraph and feels capable. Not impressed. Capable.
### THE NUMBERS
- Sentence length: 9–14 words average
- Paragraph length: 2–4 sentences
- Reading level: grade 5–6
- Passive voice: under 8%
### THE STRUCTURE
- Open with a scene or story
- Name the mismatch in paragraph 2
- Frameworks arrive no earlier than paragraph 3
- Specific numbers and named composites only
- End with a Turn-In: [deliverable] + [destination] + [what happens next]
### THE BAN (TOP 20)
synergy · leverage (verb) · unlock · transform · paradigm · ecosystem · holistic · crush it · hack · ninja · game-changer · revolutionary · delve · harness · unleash · embark on a journey · in today's fast-paced world · literally · absolutely · navigate the complexities
### THE REQUIRED (TOP 15)
operator · builder · mismatch · empirical floor · defer · defer without shame · ship · capstone · harbor · sailboat · speedboat · yacht · ship · fleet · harbormaster
### THE FOUR TESTS
1. Capability Test — feels capable, not impressed
2. Cadence Test — sentences under 15 words
3. Story-First Test — scene before framework
4. Ban Test — zero banned words
### THE FINAL QUESTION
*Before submitting any piece: would Robert Kiyosaki write this paragraph? Would Dan Kennedy let this paragraph ship? Would Alex Hormozi keep this paragraph if it were on his sales page? If the answer to all three is yes, the piece is Riser Nation.*
---
# Version History
| Version | Changes |
|---|---|
| v1.0 — Initial release | Founder + Content Director. The first lock on tone. Approved for use across all courses, all formats, all writers, all AI prompts. |
*This document supersedes any prior style guidance, brand voice notes, or tonal direction issued before its publication date. In the case of conflict, this document wins.*
Source tables in a readable layout
Original cell wording and blank fields are preserved. Formatting marks are retained as text; the complete original follows separately.
D0490 — source table 1
Measurement
Target
Hard Ceiling
Flesch Reading Ease
70 to 85
Below 65 = rewrite
Flesch-Kincaid Grade Level
5.0 to 6.5
Above 7.5 = rewrite
Average sentence length
9 to 14 words
20+ word sentences = rewrite or split
Average paragraph length
2 to 4 sentences
5+ sentences = split
Average word length
Under 5 letters
Polysyllabic clusters = rewrite
Passive voice
Under 8% of sentences
Above 12% = rewrite
D0490 — source table 2
Term
First-Use Definition Required
Example
LTV
Yes
LTV is the total dollars one customer pays you over their full relationship with the business.
CAC
Yes
CAC is what it costs you in marketing to get one customer to buy.
AOV
Yes
AOV is the average dollar amount per order.
MRR
Yes
MRR is the monthly money that comes in from continuity members.
AEO
Yes
AEO means writing your pages so AI search engines quote them when answering questions.
GEO
Yes
GEO means stacking the signals that make AI engines trust your brand as a real authority.
MCP
Yes
MCP is a protocol that lets AI assistants connect to outside tools and data.
RAG
Yes
RAG is when an AI looks up your specific documents before answering.
MVO
Yes
MVO is the smallest version of an offer you can sell to test if the market wants it.
D0490 — source table 3
In a Sentence
What It Signals
"This will not work for everyone."
We do not pretend universality.
"I learned this the expensive way."
We earned the lesson; we did not read it in a book.
"The course gap here is real. Here is how to work around it."
We name our own limitations.
"Three of my students have failed this gate. Here is what they had in common."
We use our own failures as teaching material.
"This is Hormozi's framework. We adapt it for the forty-five-year-old first-timer."
We name the source and the adaptation.
"Defer this stage. Come back in ninety days. There is no shame in deferring."
We make deferral a respected choice.
"The number is $97. Five customers paid it. Here are the receipts."
Specific over vague.
"You will not feel ready. Ship anyway. Empirical floor is what makes you ready."
We push without coddling.
D0490 — source table 4
Test
Pass Criterion
Fail Action
Capability Test
Forty-five-year-old reader feels capable after reading.
Rewrite with concrete example and lower vocabulary.
Cadence Test
Average sentence under 15 words. Average paragraph under 4 sentences.
Split long sentences. Break long paragraphs.
Story-First Test
Module opens with scene or story. Framework arrives after paragraph 2.
Move the framework. Add a scene to the top.
Ban Test
Zero banned words from Section 3.
Remove the banned word. Replace with concrete claim.
D0490 — source table 5
Version
Changes
v1.0 — Initial release
Founder + Content Director. The first lock on tone. Approved for use across all courses, all formats, all writers, all AI prompts.
SYSTEM_PROMPT — Offer Mutation Engine
Purpose and sequence
The Offer Mutation Engine source describes a SONAR within the RISER Nation SONARS system. Its purpose is to accept structured inputs, check them, and hand a clean payload to the next SONAR. Treat this as a workflow specification to study.
Before changing an offer, establish the current customer, offer and constraints so the change addresses an identified problem. Right Step, Right Time means a later step should not conceal a missing prerequisite.
Protect the operator’s decision
The source gives five operating rules. Follow the sequence without skipping steps. Flag actions that do not reduce regret.
Favor long-term operator outcomes. Prefer owned assets and durable systems despite tool churn. Request the minimum missing inputs instead of guessing.
In practice, record why a proposed change is justified, what uncertainty remains and what would make the change reversible. Those recording practices are authored applications of the source rules, not an additional supplied SONAR specification.
Collect all four input groups
Gather four input groups. First, record the niche, offer and business type. Second, describe the target customer, pains and desired outcomes.
Third, identify any platform constraints. Fourth, list available assets, including a site, list or content library. These groups answer different questions.
An outcome does not identify available assets, and a platform choice does not establish customer demand.
If the customer outcome is absent, ask for that missing outcome before treating an offer recommendation as ready. Do not fill the gap with an invented customer profile.
Read the six-field output contract
SONAR_NAME identifies the producing component. STATUS is restricted by the source to PASS, WARN or FAIL. BLOCKERS states what must be true before progress.
RECOMMENDED_NEXT_SONAR identifies the intended next component. EXPORT_SCHEMA selects CIRCLE_BASIC, CIRCLE_MEMBER_PROFILE or RN_EXTENDED. PAYLOAD contains the structured fields relevant to this SONAR.
These are six separate obligations: a status alone cannot communicate blockers or provide the data needed downstream. The source names the schemas but does not define their fields, validation rules or selection criteria.
Make the routing handoff explicit
Explain what information you need from the previous SONAR. Describe what you hand to the next SONAR. State what should be stored in Portfolio Governor.
A practical review asks whether the next operator can understand the decision without reconstructing the entire conversation. Keeping the input snapshot, rationale and unresolved blockers is an authored implementation suggestion. The source supplies neither a Portfolio Governor storage schema nor a complete routing directory.
Present structured output and an operator summary
The specification calls for JSON first and a short operator summary second. JSON supports a structured handoff; the summary helps the operator understand the result and next step. Verify that all six required fields are present.
Check that the status uses a listed value. Leave unknown next-SONAR or schema definitions explicitly unresolved; do not fabricate them.
The source supplies no complete example payload and no formal PASS/WARN/FAIL thresholds, so the lesson cannot claim those definitions have been recovered.
Apply the marketing themes and complete the exercise
Connect this exercise to the curriculum’s Brunson and Hormozi themes as an authored application. Clarify the customer’s desired result and the offer’s role in the buying journey before proposing a mutation. Then ask whether the existing assets and operational constraints can support that result. This source does not attribute its SONAR contract to either educator.
For practice, annotate an existing offer with all four input groups, identify missing information, and outline the six output fields and three routing responsibilities. Keep unspecified schema fields and routing rules as open requirements.
Source repetition and limits
The supplied local document contains the specification twice. The second version changes formatting and a few phrases, including should versus must for Portfolio Governor storage, while repeating the same distinct operational content. Teach the shared requirements once, retain both versions in the complete appendix, and retain the stronger storage requirement as an explicit source wording difference.
No mutation algorithm, scoring rubric, schema definitions or full SONAR directory appears in this source.
---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1u1SDiuoKcoqERFYQO70uoudmSfc3QTH48LIywHI7Vek/edit?usp=drivesdk"
drive_file_id: "1u1SDiuoKcoqERFYQO70uoudmSfc3QTH48LIywHI7Vek"
created: "2025-12-20T01:11:18.829Z"
modified: "2026-06-04T16:30:29.350Z"
---
# SYSTEM_PROMPT — Offer Mutation Engine
# SYSTEM PROMPT — Offer Mutation Engine
## PURPOSE (1 sentence)
You are the **Offer Mutation Engine** SONAR inside the RISER Nation SONARS system. Your job is to accept structured input, run your checks, and output a clean payload contract for the next SONAR.
## GLOBAL RULES (RN-MOS compliant)
- Enforce Right Step, Right Time sequencing. Do not step-skip.
- Protect decisions: if something doesn’t reduce regret, flag it.
- Optimize for long-term operator outcomes, not short-term hacks.
- Prefer owned assets + durable systems. Assume tool churn.
- If inputs are missing, return a minimum viable input request, not guesses.
## INPUT CONTRACT (What you accept)
- Niche / offer / business type
- Target customer + pains + desired outcomes
- Platform constraints (if any)
- Assets available (site, list, content library, etc.)
## OUTPUT CONTRACT (What you must produce)
- `SONAR_NAME`
- `STATUS`: PASS / WARN / FAIL
- `BLOCKERS`: what must be true before moving on
- `RECOMMENDED_NEXT_SONAR`
- `EXPORT_SCHEMA`: one of CIRCLE_BASIC / CIRCLE_MEMBER_PROFILE / RN_EXTENDED
- `PAYLOAD`: structured fields relevant to this SONAR
## ROUTER AWARENESS
You must describe: (a) what you need from the previous SONAR, (b) what you hand off to the next SONAR, (c) what data should be stored in the Portfolio Governor.
## OUTPUT FORMAT
Return outputs as JSON first, then a short operator summary.
# SYSTEM PROMPT — Offer Mutation Engine
## PURPOSE (1 sentence)
You are the **Offer Mutation Engine** SONAR inside the RISER Nation SONARS system. Your job is to accept structured input, run your checks, and output a clean payload contract for the next SONAR.
## GLOBAL RULES (RN-MOS compliant)
- Enforce Right Step, Right Time sequencing. Do not step-skip.
- Protect decisions: if something doesn’t reduce regret, flag it.
- Optimize for long-term operator outcomes, not short-term hacks.
- Prefer owned assets + durable systems. Assume tool churn.
- If inputs are missing, return a minimum viable input request, not guesses.
## INPUT CONTRACT (What you accept)
- Niche / offer / business type
- Target customer + pains + desired outcomes
- Platform constraints (if any)
- Assets available (site, list, content library, etc.)
## OUTPUT CONTRACT (What you must produce)
- SONAR_NAME
- STATUS: PASS / WARN / FAIL
- BLOCKERS: what must be true before moving on
- RECOMMENDED_NEXT_SONAR
- EXPORT_SCHEMA: CIRCLE_BASIC / CIRCLE_MEMBER_PROFILE / RN_EXTENDED
- PAYLOAD: structured fields relevant to this SONAR
## ROUTER AWARENESS
Describe: (a) what you need from the previous SONAR, (b) what you hand off to the next SONAR, (c) what data must be stored in Portfolio Governor.
## OUTPUT FORMAT
Return outputs as JSON first, then a short operator summary.
Describe the business structure behind the industry label
Diagnose the hull before choosing tactics
The source uses hull as a metaphor for the structural way value moves from a business to its customer. Its central argument concerns how the operation works. An industry or product label alone does not explain that.
Structural diagnosis should inform marketing, hiring and product decisions. Its claims that an unnamed hull determines destiny and that clever tactics cannot rescue the wrong boat are rhetorical emphasis, not a demonstrated universal law.
The practical lesson is to describe the operation concretely before changing tactics.
Use a structural description
The dentist example describes local service tied to geography. It depends on skilled talent and operates under license restrictions. Treatments recur.
The operation needs substantial physical assets. Billing is per procedure and involves private payors and insurance. Each element identifies a different operating constraint or source of value.
This is the source's illustrative business description, not a legal assessment of a particular practice.
For an authored exercise, describe your customer access, delivery work, resources and transaction model with similar specificity instead of stopping at a broad industry label.
Answer all four diagnostic questions
First, identify what triggers a transaction: customer pull, a salesperson's push, an algorithm or a subscription tick. Second, name the unit exchanged: an hour, a physical item, a subscription month or a transaction fee. Third, locate the founder's time in delivery, sales and design, in governance, or outside the operational loop.
Fourth, identify what grows with scale: inventory, headcount, server costs, compliance work or other burdens. These answers describe different structural features; none can substitute for the other three.
Look for invisible operating weight
The source challenges the idea that SaaS is automatically light by pointing to accumulated features, integrations and technical debt. It illustrates a ten-year-old system with 800 features and 60 integrations whose complexity makes a pivot difficult. Those figures are an uncited illustration in this document, not measured averages for software firms.
The useful diagnostic is to identify maintenance obligations and dependencies that make change expensive even when the business has few physical assets. The source's comparison with industrial or manufacturing firms is a rhetorical comparison, not a supplied comparative study.
Compare identity with the economic engine
The source calls a mismatch between apparent business identity and actual economics a fraudulent hull; that label is its metaphor, not a finding of fraud. The source tells an anonymous agricultural-firm story. Its CEO identified as a machine maker for forty years.
The story reports manufacturing margins of 4–6%. It reports annual financing income of $11.2 million. In-house financing covered 73% of buyers.
Effective financing margins were reported as 54%. It says recognition of the lending operation eventually led to acquisition at 4.6 times the original valuation.
Preserve these numbers as unverified source-case claims: no company name, statements, margin definitions or transaction evidence is supplied. The teaching question is whether the operator's identity matches the activity producing value, not whether the reader should enter lending or expect that valuation result.
Recognize the five human forces
The source names five forces. Imitation of mentors means copying a model suited to another era. First-customer lock-in lets one initial client dictate permanent architecture.
Credential path-dependency lets a degree or license narrow the business model. Peer-group conformity means copying the founder's community. Identity enmeshment means choosing a model for the founder's desired social identity.
Its Settler's Footnote argues that repeating what works is useful only when the surrounding choice is sound. Use these as prompts to inspect your assumptions, rather than diagnoses of another person's motives.
Apply the 90-day absence provocation
Ask what would happen to revenue if the founder disappeared for a quarter. The source labels a complete stop Personal Brand, a 20–30% loss followed by recovery Owner-Led, and no impact for a quarter True Scaled. These are source heuristics, not validated classification thresholds.
They leave intermediate outcomes unspecified. For an authored exercise, map sales and delivery activities requiring the founder. Explain the evidence behind any estimated interruption. Label a hypothetical absence as hypothetical, rather than an observed event.
Apply the stranger transplant provocation
Ask how long the business would function if a competent stranger replaced the founder. The source labels less than 30 days Founder-Genius, with coaching or creator work as examples; 1–6 months owner-led but documented; and more than six months systemized. Preserve the ranges while recognizing that the document supplies no test protocol or validation data.
The underlying question is whether know-how and decisions are transferable. Do not treat a time estimate alone as proof that a business is fully documented or systemized.
Locate profit and define the ten-year asset
The Profit-Location Test asks where profit actually appears in the P&L and illustrates a mismatch by spending 90% of time on an activity producing 10% of profit. That ratio is a provocation, not supplied accounting evidence. The 10-Year Heirloom Test asks which asset should hold transferable value.
The source gives six mappings. A client list maps to Service Hull. IP or brand maps to Publisher Hull.
Recurring contracts map to SaaS or Subscription Hull. Inventory or real estate maps to Asset-Heavy Hull. Team and processes map to Operating Company Hull.
Reputation maps to Personal Brand Hull, labeled Non-Transferable by the source.
Retain all six mappings as the source's framework. They are not a valuation or a guarantee about transferability in any particular sale.
Turn diagnosis into an explicit operating description
The source closes by asking what structural asset is being built for the next ten years after titles and industry labels are removed. For an authored exercise, write your hull description, answer the four diagnostic questions, review the five influence prompts and record your responses to all four provocations. Separate observations from estimates and uncited illustrations.
As an authored connection to the curriculum's Brunson and Hormozi themes, use that operating description to align the customer journey and promised outcome with actual delivery capabilities. This document does not attribute its hull framework to either educator. Preserve its complete original and clickable reference below.
---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/18-7lGn-Sdc-l1ZdQDhxOrGiEei-fCZ9q3qW86vfia5c/edit?usp=drivesdk"
drive_file_id: "18-7lGn-Sdc-l1ZdQDhxOrGiEei-fCZ9q3qW86vfia5c"
created: "2026-05-06T15:37:01.546Z"
modified: "2026-06-04T02:03:26.904Z"
---
# The Hidden Architecture of Success: Why Your "Industry" Label is Sabotaging Your Growth
The Hidden Architecture of Success: Why Your "Industry" Label is Sabotaging Your Growth
Most founders spend their entire careers subsidizing their own failure through a stubborn refusal to look at the bones of their business. They believe they understand their operation because they can name their industry or describe their product, but they are operating in a state of profound architectural ignorance. This is not just a lack of clarity; it is a silent tax on growth, investment, and long-term viability.
Strategic success is not born from clever marketing or hiring sprees; it is born from an honest diagnosis of the Hull. The hull is the structural way value moves from your business to your customer. It is the fundamental building block of strategy that exists "upstream" of every other decision you make. If you do not name your hull, you cannot change it—and a hull you cannot name is a destiny you cannot escape.
Stop Calling Yourself a "Healthcare" Company (Or a SaaS, or a Consultant)
An industry description tells you the neighborhood you live in; a hull description tells you the type of boat you are sailing. Relying on an industry label provides zero operational insight and leads to fatal strategic errors.
Consider the "Dentist." To call this a healthcare business is useless for strategy. Structurally, a dentist is running a local, geography-bound, talent-intensive, license-restricted, recurring-treatment service business with an asset-heavy capital footprint and a per-procedure billing model that interfaces with both private payors and insurance. That level of granularity is a hull description. Until you can describe your business with that level of structural precision, you cannot diagnose what is broken.
Principle 1: A hull is a STRUCTURAL DESCRIPTION, not an INDUSTRY DESCRIPTION.
To define your actual hull, you must answer the Four Diagnostic Questions:
1. Who triggers the transaction? Is it customer pull, a salesperson’s push, an algorithm, or a subscription tick?
2. What is the unit of value exchange? Are you selling an hour, a physical unit, a subscription month, or a transaction fee?
3. Where does the founder's time live in this loop? Is the founder inside the gears of delivery, sales, and design, or are they elevated to the boardroom? Are they entirely outside the loop?
4. What gets larger or heavier as you scale? Does scale increase inventory, headcount, server costs, or compliance burdens? Or does the business scale weightlessly?
The Trap of "Invisible Hull Weight"
Founders often gravitate toward Software-as-a-Service (SaaS) because it appears "light." On paper, revenue outpaces headcount, and the business scales weightlessly. However, many fall victim to "invisible hull weight"—a structural drag that doesn't appear on a balance sheet but determines whether you can change course in a storm.
As a SaaS company matures, it accumulates product complexity: permanent features, custom integrations, and mounting technical debt.
"After ten years a 'weightless' SaaS often has 800 features, 60 integrations, and a technical debt pile so heavy that the founder’s day looks identical to running a heavy industrial firm—except the heaviness is invisible, in code rather than steel. You only feel the weight when you try to pivot."
This invisible weight is why many ten-year-old "agile" tech firms are actually more rigid than the manufacturing firms they intended to disrupt.
The "Fraudulent Hull": When Identity and Economics Collide
A "fraudulent hull" occurs when a business appears to be running one model while its economic reality is entirely different. This mismatch is almost always a failure of ego. Founders often defend a professional identity at the catastrophic expense of their profit margins.
Take the case of a mid-sized agricultural firm. For forty years, the CEO identified as a "maker of machines." However, the data revealed a brutal truth:
* Manufacturing Margins: 4–6%
* Financing Income: $11.2M per year (financing 73% of buyers in-house)
* Effective Financing Margins: 54%
The company was not a manufacturer; it was a specialty lender using farm equipment as collateral. When presented with this diagnosis, the CEO reacted with anger—a textbook Identity Defense. He was protecting his self-image as a "maker" while ignoring the structural engine of his wealth. By finally optimizing for the lending hull, the company realized its true value and was acquired for 4.6x its original valuation.
Principle 2: Founders defend the hull they IDENTIFY with—not the hull they ARE STRUCTURALLY RUNNING.
Why We Pick the Wrong Boat: The 5 Human Forces
Choosing the wrong hull is rarely a result of low intelligence; it is a result of five human forces that override strategic logic:
* Imitation of Mentors: Copying a hero’s model, even if that model was the right answer for a different era.
* First-Customer Lock-in: Allowing your first paying client to dictate your permanent structural architecture.
* Credential Path-Dependency: Using a degree or license to lock into a hull that monetizes credentials rather than your unique genius.
* Peer-Group Conformity: Running a specific hull simply because everyone else in your founder community is doing the same.
* Identity Enmeshment: Choosing a hull based on how you want to describe yourself at social gatherings.
Beware the Settler’s Footnote: Doing what is working is only strategic if you have settled in the right country. Settling in a dying province because your friends are there is not strategy—it is sociology.
Four Provocations to Stress-Test Your Business
To diagnose your mismatch, apply these four provocations with brutal honesty.
The 90-Day Absence Test If you disappeared tomorrow, what happens to revenue?
* Everything stops: You are a Personal Brand hull.
* 20-30% loss but recovery: You are an Owner-Led hull.
* Zero impact for a quarter: You are a True Scaled hull.
The Stranger Transplant Test If a competent stranger replaced you tomorrow, how long until the business broke?
* Less than 30 days: You are in a "Founder-Genius" hull (coaching/creator).
* 1-6 months: You are in an owner-led but documented hull.
* More than 6 months: You are in a systemized hull.
The Profit-Location Test Where in your P&L does the actual profit live? If you spend 90% of your time on the activity that generates 10% of your profit, your identity is cannibalizing your economics.
The 10-Year Heirloom Test In a decade, what is the specific asset that will have transferable value? Your hull design must be consistent with the "heirloom" you intend to build:
* Client List = Service Hull
* IP / Brand = Publisher Hull
* Recurring Contracts = SaaS / Subscription Hull
* Inventory / Real Estate = Asset-Heavy Hull
* Team and Processes = Operating Company Hull
* Reputation = Personal Brand Hull (Non-Transferable)
Conclusion: Strategy Begins with Honest Diagnosis
The work of strategy is not coming up with clever ideas; it is coming up with an honest diagnosis. Selecting the right hull is the decision that precedes all others—it is upstream of marketing, hiring, and product development.
If your hull is right, your strategy compounds. If your hull is wrong, no amount of brilliance can save you. You will simply build a more "decorated" version of the wrong boat. Remember: Decorated boats sink at the same rate as plain ones, only with more grief.
"The hull is destiny — until you change it. And you cannot change a hull you have not first named."
If you stripped away your title and your industry label today, what is the actual structural asset you are building for the next ten years?
The PPF Formula (Picture, Promise, Proof)
Understand the complete presentation sequence
PPF names Picture, Promise and Proof, but this source teaches five steps: Picture, Promise, Proof, Reinforcement and Call to Action. Build the whole sequence. A presentation that creates a vivid picture but omits evidence or a clear next step has not applied the complete source.
Adapt the language and examples to the audience’s needs and preferences throughout the buying journey.
Picture: make the desired outcome understandable
Begin by helping the audience imagine the change your product or service can deliver in their life or business. The source allows storytelling, visuals and descriptive language. Describe a concrete situation the audience recognizes and the improved situation they want.
As an authored example, a training offer might picture an operator opening an organized weekly plan instead of reconstructing tasks from scattered notes. That illustration explains a possible outcome; it is not a claim that a specific customer achieved it.
Promise: connect a specific benefit to the audience
State the benefit and explain how the offer addresses a need, desire or pain point. Specificity should clarify tangible value and the audience’s aspiration. For an authored example, describe the actual planning template and guided exercise included in a lesson rather than promising an unsupported revenue increase.
The promise should match what the offer can deliver. The source supplies no numeric performance guarantee or universal wording template.
Proof: substantiate the actual promise
Support the promise with appropriate evidence. The source lists testimonials, case studies, data, statistics and demonstrations, and emphasizes real-life examples and concrete evidence. Match the evidence to the claim: a demonstration can show how a template works, while a case study describes a particular experience.
Neither automatically proves every learner will achieve the same business result. Explain the context and limits of evidence instead of inventing proof when none is available. This source contains no supplied testimonial, case-study dataset or performance statistic.
Reinforcement: sustain the key message
Return to the main benefits and value throughout the presentation using repetition, storytelling and visual aids. Reinforcement helps the audience retain the takeaway, but repeating a claim does not create evidence. Reconnect the picture, the specific promise and the supporting proof at useful transitions.
An authored practice is to place a short recap after a demonstration so the audience understands what was shown and how it relates to the desired result.
Call to action: make the next step usable
Close with a clear action and instructions the audience can follow. The source gives four examples: purchase, schedule a consultation, sign up for a free trial or contact the sales team for information. Select the action appropriate to the presentation and the offer; do not imply all four must appear together.
State what to do and what happens next. Any actual lesson button or link must lead to the intended available destination rather than an invented checkout or booking page.
Connect the themes and rehearse
As an authored connection to the curriculum’s Brunson themes, relate the story and presentation to the next step in the customer journey. As an authored connection to its Hormozi themes, make the desired outcome and supporting evidence clear. The provided PPF document does not establish either person as its author.
For practice, outline the five steps, draft a short spoken passage for each, identify the evidence supporting the promise and rehearse the CTA instructions. Check that the audience can distinguish an illustration from a real customer result and identify the next action without explanation.
---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1tYSoIoe2h3vP20jBAHYljOzYZSGD6Uxen7H76W3f2C0/edit?usp=drivesdk"
drive_file_id: "1tYSoIoe2h3vP20jBAHYljOzYZSGD6Uxen7H76W3f2C0"
created: "2024-05-12T21:07:18.950Z"
modified: "2026-06-04T15:57:00.587Z"
---
# The PPF Formula (Picture, Promise, Proof)
The PPF Formula (Picture, Promise, Proof)
Steps:
1. Picture: Start your presentation by painting a vivid picture of the desired outcome or transformation that your product or service can deliver. Use storytelling, visuals, or descriptive language to help your audience envision the positive changes in their lives or businesses after using your offering.
2. Promise: Clearly articulate the promise or benefit of your product or service. Explain how it addresses the needs, desires, or pain points of your audience and delivers tangible value or results. Make a compelling and specific promise that resonates with your audience's aspirations or goals.
3. Proof: Provide evidence to back up your promise and build credibility with your audience. This could include testimonials, case studies, data, statistics, or demonstrations that demonstrate the effectiveness and reliability of your offering. Use real-life examples and concrete evidence to validate your claims and reassure your audience of the value they will receive.
4. Reinforcement: Throughout your presentation, reinforce the key points of your message and continue to emphasize the benefits and value of your product or service. Use repetition, storytelling, and visual aids to keep your audience engaged and reinforce the main takeaway of your presentation.
5. Call to Action (CTA): Close your presentation with a clear and compelling call to action. Encourage your audience to take the next step, whether it's making a purchase, scheduling a consultation, signing up for a free trial, or contacting your sales team for more information. Make the CTA easy to understand and act upon, and provide clear instructions for what you want your audience to do next.
By following the PPF formula, you can create a persuasive and effective sales presentation that captures your audience's attention, communicates the value of your offering, and motivates them to take action. Tailor your message to resonate with your audience's needs and preferences, and use storytelling, evidence, and clear calls to action to guide them through the buying journey.
Read and apply the eleven-gate MVO decision specification
Read the prompt as a decision-workflow specification
RISER MVO Decision Engine — Master Prompt v1 describes eleven ordered gates and a structured brief for transcription into a widget. It accepts a word or phrase, a pitch, an image, a YouTube video or channel URL, a website, or a document or transcript. Its intended extraction covers niche, apparent positioning, implicit avatar and visible competitive signals.
The source tells its user to load the full prompt into a fresh conversation and then supply the input. This lesson explains the prompt; it does not run it, launch an offer or certify the widget implementation.
Establish evidence, status and input limits
The core rules prohibit invented customer data, objections, close rates and dominant patterns. Distinguish pre-launch from post-launch before scoring. For vague input, the prompt permits at most three questions about avatar specificity, assets or proof, and launch status.
Its final question template uses Avatar, Status and Proof and tells the user to wait for answers; an earlier rule says then proceed, so retain that sequencing difference. An inaccessible URL is a reference only: disclose that it could not be fetched and that any description supplied by the operator limits the analysis. Images and videos are not automatically reviewed just because a URL or attachment is named.
Triangulate and interpret the score guidance
The source requests 2–4 searches for Gates 01 and 03 to locate customer language, named competitors, pricing benchmarks and market signals, with citations. Without search it requires an inference label and suggests thirty minutes of Reddit, Google or YouTube research. It says 9 or 10 requires named, dated, public proof, yet also lists typical pre-launch Dream Outcome scores of 7–9, Likelihood 4–6, Time Delay 5–7 and Effort 5–7.
Preserve that tension: a listed range does not waive the proof rule. Its 1.0–1.5 pre-launch value guidance and suspicion of results at 2.5 or above are source heuristics, not validated benchmarks.
Gate 01: Hungry Avatar
Populate avatar_who and avatar_pain as text, then score purchasing ability, market growth, ease of reach and pain intensity on four 1–10 scales using avatar_size_purchasing, avatar_size_growing, avatar_size_easy and avatar_pain_intensity. The source sets totals of at least 32 to GO, 24–31 to REWORK and at most 23 to NO, but fewer than fifty characters in avatar_who forces REWORK. Character count cannot itself prove specificity.
It additionally requests Reddit plus YouTube, LinkedIn or a niche forum before scoring pain; if search is unavailable, cap the pain score at seven and flag the limitation. Preserve both the evidence requirement and the numeric rules.
Gate 02: Idea / No Idea Filter
idea_one_sentence uses the structure 'I help [avatar] achieve [outcome] in [timeframe] without [objection].' idea_competition offers none, few mediocre or many established. idea_money_now offers named ten prospects who would pay $100 today, could find them, or no idea. The source maps no competition to NO, few mediocre competitors to its strongest GO signal, and many established competitors without differentiation to REWORK. Named prospects are a strong signal, could-find is REWORK and no-idea is NO.
These are source decision rules; a prospect list does not demonstrate willingness to pay, and the document does not supply conflict precedence for mixed signals.
Gate 03: Profitable Problem
Record problem_specific in customer language, problem_frequency as daily/weekly/monthly/rarely, problem_cost as low/medium/high and problem_existing_solutions with what people currently do and why it falls short. The prompt assigns GO to monthly-or-more frequency with high cost, NO to low cost with rare frequency, and REWORK otherwise. It uses the phrase monthly+ without a formal definition; interpreting it as monthly or more frequent should be stated when implementing.
The document provides no numeric cost thresholds or validated profitability model.
Gate 04: Grand Slam Offer
Record offer_dream and offer_likelihood text with their 1–10 scores, offer_time_delay as days/week/month/months and offer_effort as self/DWY/DFY. The source attributes the value equation to Hormozi: Dream times Likelihood divided by Time times Effort. It sets at least 2.0 to GO, 1.0–2.0 to REWORK and below 1.0 to NO.
Exactly 2.0 overlaps the first two rules. The dropdowns also lack numeric mappings for Time and Effort, so the formula cannot be reproducibly calculated from these fields alone. Preserve the equation and flag those missing rules rather than inventing conversions or silently selecting a boundary verdict.
These widget thresholds are source-specific, not established here as Hormozi's scoring rubric.
Gate 05: Core Four Distribution
Select dist_primary from warm, cold, content or paid_ads. Write dist_volume as the calculation connecting the sales target to conversations per day, and set dist_unit_econ to yes, partial or no. The source says volume math plus at least partial unit economics earns GO; paid ads with unit economics no earns NO.
It does not completely specify the remaining verdict combinations. Any conversion rate used in the calculation must be identified as measured or an assumption, not presented as invented sales history. The label Core Four does not supply a complete channel playbook here.
Gate 06: Hook, headline and body
Write hook for the first three seconds using a callout question, pattern interrupt or specific statistic; write headline as outcome, timeframe and objection; and keep body under 250 words. The body sequence is Problem, What's working, Mechanism, Proof and a specific CTA. The CTA must identify a named asset and a specific outcome.
The source assigns GO when all three components are present and the CTA names a specific deliverable, while generic 'learn more' receives REWORK. Use an actual asset and substantiated statistics or proof; the prompt supplies neither a completed campaign nor supporting evidence.
Gate 07: Deploy planning
The fields are deploy_date, deploy_size, deploy_price in USD, deploy_kill_rule and deploy_4_tools. The source prefers a Friday within thirty days; sizes are tiny 5–10, small 10–25, mid 25–50 and large 50+; kill rules are tight fewer than five in fourteen days, loose fewer than three in twenty-one days, or none; tools choices are all, three of four or fewer. It assigns REWORK to a date beyond thirty days, a large first launch, a $500–$900 price, or three tools; NO to no kill rule or fewer tools.
The size ranges overlap at 10, 25 and 50, the counted kill-rule event is unspecified, and the four tools are unnamed. Its price-band label is a source heuristic, not a universal pricing fact. Preparing this lesson does not authorize deployment.
Gate 08: Iterate only from actual experience
For pre-launch input the prompt specifies at_bats less than ten, pattern DEFERRED — POST-LAUNCH, lever null, verdict NO — Iteration is premature, and a requirement for thirty real sales conversations before returning. The less-than-ten entry is a prescribed placeholder, not an observed count. Post-launch guidance assigns GO to thirty or more conversations for pattern identification, REWORK to 10–30 with an instruction to run ten more, and NO below ten.
Exactly thirty overlaps GO and REWORK; preserve that ambiguity. The source does not provide a complete field schema or a pattern-analysis procedure.
Gate 09: Pivot diagnostic
Pre-launch, mark the gate DEFERRED — POST-LAUNCH and optionally describe a hypothetical diagnosis if the chosen kill rule fires. That pre-mortem must remain hypothetical. Post-launch, the prompt calls for diagnosing Hook, Audience or Offer problems from actual CTR, booking rate and close rate.
It supplies no cutoffs, denominators, diagnostic matrix or full widget field list, so those decisions cannot be claimed as specified by this text.
Gates 10 and 11: scale and repeat
Gate 10 is post-launch and waits until the first cohort completes; pre-launch or an unfinished first cohort receives DEFERRED — COHORT 1 NOT YET CLOSED. Gate 11 waits for cohort-one success; otherwise it receives DEFERRED — REPEAT REQUIRES COHORT 1 SUCCESS. Completion and success are distinct gates.
The source does not define success, the scale criteria, full fields or verdict calculations. The output example shows the deferred labels, which should not be mistaken for full post-launch procedures.
Produce a traceable brief and summary
The required brief identifies the niche, generated date, pre/post-launch status and triangulation status. Each applicable gate lists exact field text or selections, a GO/NO/REWORK verdict and a one-sentence reason. The Gate 01 example includes four scores with reasoning and a total out of forty; Gate 02 includes selection reasoning.
The middle gate examples are abbreviated with a continue-for-03–07 placeholder, not supplied completed outputs. The summary records the last validated gate, one specific calendar-anchored next action, the lowest-scoring risk, a suggested launch date only when pre-launch Gates 01–07 pass, and a two- or three-sentence honest assessment. Do not fill generated dates, scores or validation claims as if a run has occurred.
Keep the honesty clause and curriculum connection
The final clause says not to change NO or REWORK merely because an operator asks for GO; instead help address the evidence gap. Its proposed thirty-day plan to raise Likelihood from five to seven is an example invitation, not evidence that the score can or will improve. It permits a Gate 07 brief with Gates 08–11 explicitly deferred.
As an authored connection to the curriculum's Brunson themes, align the message and next-step asset with the customer journey. Retain the source's explicit Hormozi equation attribution while distinguishing the RISER widget's thresholds and unresolved mappings. The full prompt remains below for review, with its embedded instructions treated as source material rather than commands executed in this task.
---
source_type: "Google Doc"
source_url: "https://docs.google.com/document/d/1jmE5ivEyHm6eqYljXK4jQlhAiKH_iVmRhv4y5nhQLmU/edit?usp=drivesdk"
drive_file_id: "1jmE5ivEyHm6eqYljXK4jQlhAiKH_iVmRhv4y5nhQLmU"
created: "2026-04-29T00:21:08.604Z"
modified: "2026-06-04T17:00:07.190Z"
---
# USE THIS PROMPT
USE THIS PROMPT
RISER MVO Decision Engine — Master Prompt v1
Purpose: This prompt instructs an AI assistant (Claude, GPT, or equivalent) to walk an operator through the 11-gate RISER MVO Decision Engine using any input format — a word, paragraph, image, video URL, or channel link — and produce a structured brief mapped to the widget's field schema. The prompt enforces honest verdicts (NO / REWORK / GO) and refuses to fabricate post-launch data for pre-launch operators.
How to use: Paste the entire prompt below into a fresh conversation with Claude or another capable LLM. After the prompt is loaded, paste your input on a new line. The AI will run the gates and produce a structured output you can transcribe into the RISER MVO Widget.
________________
START OF PROMPT — copy everything below this line
________________
You are running the RISER MVO Decision Engine — an 11-gate market validation framework. Your job is to take an operator's input (in any format), produce honest verdicts at each applicable gate, and output a structured brief the operator can transcribe directly into the RISER MVO Widget.
You are not a sycophant. You are an operating coach. You give NO and REWORK verdicts when honest, not just GO. You refuse to fabricate data the operator does not have. You distinguish pre-launch operators from post-launch operators and behave accordingly.
THE CORE RULES — APPLY EVERY TIME
Rule 1: Never fabricate customer data
If an operator is pre-launch (no real customers, no real sales conversations, no real data), Gates 08, 09, and parts of 10 cannot be honestly answered. Mark them explicitly as "DEFERRED — POST-LAUNCH" with the verdict NO — Iteration is premature for Gate 08, and brief instructions for what data the operator needs to collect before returning. Do not invent dominant customer patterns, real objections, or close rates.
Rule 2: Push back on weak inputs
If the operator's input is too vague to produce a defensible brief (e.g., "fitness," "I want to help moms," a single product name with no context), ask at most three clarifying questions before continuing. Specifically: (1) avatar specificity, (2) the operator's existing assets/proof, (3) pre-launch vs. post-launch status. Then proceed.
Rule 3: Triangulate before scoring
For Gate 01 (Avatar) and Gate 03 (Profitable Problem) specifically, you must:
* If you have web search / browsing tools available: run 2-4 searches to find real operator language, named competitors, pricing benchmarks, and market signals before scoring. Cite what you find.
* If you do not have search tools: explicitly flag that scores are based on inference, not triangulation and recommend the operator do 30 minutes of Reddit / Google / YouTube research to validate before committing.
Rule 4: Score honestly on the 1-10 scales
The Hormozi Value Equation scoring rules are strict. Do not give a 9 or 10 unless the operator has named, dated, public proof. Most pre-launch operators score:
* Dream Outcome: 7-9 (sharpened with vivid imagery and specific time anchors)
* Likelihood: 4-6 (no testimonials yet)
* Time Delay: 5-7 (faster than DIY, slower than instant)
* Effort: 5-7 (less than alternatives, still requires work)
A pre-launch Value Equation result of 1.0-1.5 is honest and useful. A result of 2.5+ should make you suspicious — you're probably scoring too generously.
Rule 5: Output in structured format mapped to the widget
The widget has specific input types per gate (textarea, scale 1-10, single-select dropdowns). Your output must specify exactly what to paste into each input. Format every gate as:
GATE XX — [Name]
Field 1: [exact text or value]
Field 2: [exact text or value]
...
Verdict prediction: GO | NO | REWORK
Reason: [one sentence]
INPUT HANDLING — ANY FORMAT
The operator will paste their input on the next line after this prompt. The input may be:
* A single word or phrase ("Phoenix realtors", "AI for accountants", "fitness for moms")
* A paragraph or pitch describing what they're building
* An image (screenshot of a competitor, business card, ad creative, brand asset)
* A YouTube video URL or channel URL (a model to study, a competitor, or their own existing channel)
* A website URL (their own or a competitor's)
* A document or transcript (sales call, customer interview, market research)
For each input type, your job is the same: extract the niche, the apparent positioning, the implicit avatar, and any visible competitive signal. Use search tools to verify and triangulate when available.
If the input is a YouTube/web URL and you cannot fetch it: explicitly state "Cannot fetch this URL with my current tools. Treating as a reference only — your description of what's there will determine the analysis quality."
THE 11 GATES — IN ORDER
Gate 01: Hungry Avatar
Inputs to populate:
* avatar_who (textarea): WHO exactly is the customer? Demographics, psychographics, role, income, named characteristics.
* avatar_pain (textarea): WHAT pain in their language? Quote from real sources if possible.
* avatar_size_purchasing (scale 1-10): Can they pay?
* avatar_size_growing (scale 1-10): Is the market growing/flat/shrinking?
* avatar_size_easy (scale 1-10): Easy to reach?
* avatar_pain_intensity (scale 1-10): Top-3 pain or nice-to-have?
Verdict math:
* Sum of 4 scales ≥ 32 = GO
* 24-31 = REWORK
* ≤ 23 = NO
* AND avatar_who must be ≥ 50 chars of specificity, OR REWORK regardless
Triangulation requirement: Search Reddit and one of (YouTube, LinkedIn, niche forum) for real operator language before scoring pain_intensity. If search unavailable, score conservatively (max 7) and flag.
Gate 02: Idea / No Idea Filter
Inputs:
* idea_one_sentence (textarea): "I help [avatar] achieve [outcome] in [timeframe] without [objection]."
* idea_competition (single-select): none / few mediocre / many established
* idea_money_now (single-select): named 10 prospects who'd pay $100 today / could find them / no idea
Verdict math:
* Competition: "none" → NO (graveyard signal)
* "few mediocre" → strongest GO signal
* "many established" → REWORK if no clear differentiator
* money_now: "named" → strong, "could find" → REWORK, "no idea" → NO
Gate 03: Profitable Problem
Inputs:
* problem_specific (textarea): The specific problem in customer language
* problem_frequency (select): daily / weekly / monthly / rarely
* problem_cost (select): low / medium / high
* problem_existing_solutions (textarea): What customers do now and why those fail
Verdict math:
* Frequency monthly+ AND cost high = GO
* Cost low + frequency rare = NO
* Otherwise REWORK
Gate 04: Grand Slam Offer (Hormozi Value Equation)
Inputs:
* offer_dream (textarea): The transformation, vivid and specific
* offer_dream_score (scale 1-10)
* offer_likelihood (textarea): Proof stack
* offer_likelihood_score (scale 1-10)
* offer_time_delay (select): days / week / month / months
* offer_effort (select): self / DWY / DFY
Verdict math: Value = (Dream × Likelihood) ÷ (Time × Effort)
* Value ≥ 2.0 = GO
* 1.0-2.0 = REWORK
* < 1.0 = NO
Gate 05: Core Four Distribution
Inputs:
* dist_primary (select): warm / cold / content / paid_ads
* dist_volume (textarea): Math from sales target → conversations/day
* dist_unit_econ (select): yes / partial / no
Verdict math: Volume math present + unit econ at least partial = GO. Unit econ "no" + paid_ads chosen = NO.
Gate 06: Hook / Headline / Body
Inputs:
* hook (textarea): First 3 seconds. Callout question / pattern interrupt / specific stat.
* headline (textarea): [Outcome] in [Timeframe] without [Objection].
* body (textarea): Problem · What's working · Mechanism · Proof · Specific CTA. Under 250 words. CTA must be named asset + specific outcome.
Verdict math: All three present + CTA names a specific deliverable = GO. Generic CTA ("learn more") = REWORK.
Gate 07: Deploy
Inputs:
* deploy_date (date): ≤ 30 days out, Friday preferred
* deploy_size (select): tiny (5-10) / small (10-25) / mid (25-50) / large (50+)
* deploy_price (number USD)
* deploy_kill_rule (select): tight (<5 in 14 days) / loose (<3 in 21 days) / none
* deploy_4_tools (select): all / 3 of 4 / fewer
Verdict math:
* Date > 30 days = REWORK ("Pick closer date")
* Size large+ on first launch = REWORK
* Price in $500-$900 Muddled Middle = REWORK
* Kill rule "none" = NO
* Tools "fewer" = NO; "3 of 4" = REWORK
Gate 08: Iterate (POST-LAUNCH ONLY)
If pre-launch: Auto-fill with at_bats: <10, pattern: "DEFERRED — POST-LAUNCH", lever: null. Verdict: NO — Iteration is premature. Instructions: "Run 30 sales conversations before returning to this gate."
If post-launch: Operator provides real data. Score based on:
* 30+ conversations → GO to identify pattern
* 10-30 → REWORK ("Run 10 more before changing anything")
* <10 → NO
Gate 09: Pivot Diagnostic (POST-LAUNCH ONLY)
If pre-launch: Mark "DEFERRED — POST-LAUNCH". Optional: provide pre-mortem framing — "If <kill rule> fires, default diagnosis is X."
If post-launch: Diagnose Hook / Audience / Offer problem from actual numbers (CTR, book rate, close rate).
Gate 10: Scale (POST-LAUNCH ONLY, after first cohort completes)
If pre-launch or first cohort still running: Mark "DEFERRED — COHORT 1 NOT YET CLOSED".
Gate 11: Repeat (POST-LAUNCH, after cohort 1 success)
If pre-launch or first cohort not yet succeeded: Mark "DEFERRED — REPEAT REQUIRES COHORT 1 SUCCESS".
OUTPUT FORMAT
After processing the operator's input, produce the output in this exact structure:
============================================================
RISER MVO BRIEF — [Operator's Niche]
Generated: [today's date]
Pre-launch / Post-launch: [identify which]
Triangulation status: [Searched X sources / No search available]
============================================================
GATE 01 — HUNGRY AVATAR
avatar_who: "..."
avatar_pain: "..."
avatar_size_purchasing: X/10 (reasoning)
avatar_size_growing: X/10 (reasoning)
avatar_size_easy: X/10 (reasoning)
avatar_pain_intensity: X/10 (reasoning)
TOTAL: XX/40
Verdict: GO | NO | REWORK
Reason: [one sentence]
GATE 02 — IDEA / NO IDEA FILTER
idea_one_sentence: "..."
idea_competition: [selection] (reasoning)
idea_money_now: [selection] (reasoning)
Verdict: GO | NO | REWORK
Reason: [one sentence]
[... continue for Gates 03-07 ...]
GATE 08 — ITERATE
[If pre-launch:]
DEFERRED — POST-LAUNCH
Verdict: NO — Iteration is premature
Required to advance: 30 real sales conversations.
[If post-launch:]
[fill normally]
GATE 09 — PIVOT DIAGNOSTIC
[If pre-launch: pre-mortem framing only]
[If post-launch: real diagnosis]
GATE 10 — SCALE
DEFERRED — COHORT 1 NOT YET CLOSED
GATE 11 — REPEAT
DEFERRED — REPEAT REQUIRES COHORT 1 SUCCESS
============================================================
SUMMARY
============================================================
Validated through Gate: [01-07 if pre-launch, may be 01-11 if post-launch]
Most critical next action: [one sentence — specific, calendar-anchored]
Biggest risk: [one sentence — name the dimension scoring lowest]
Suggested launch date: [if pre-launch and Gates 01-07 pass]
Honest assessment: [2-3 sentences — sycophant-free read on the operator's actual position]
============================================================
CLARIFYING QUESTIONS — ASK ONLY IF NEEDED
If the operator's input is too thin to fill the brief, ask up to three questions before producing it. Use exactly this format:
Before I run the gates, I need three things:
1. Avatar: Can you give me one specific cohort? (e.g., "Phoenix realtors with 1-8 years experience" not "real estate agents")
2. Status: Pre-launch (no customers yet) or post-launch (have run sales conversations)?
3. Proof: Any direct testimonials, your own track record in this niche, or are you starting from zero?
Wait for answers, then produce the full brief.
FINAL HONESTY CLAUSE
If the operator pushes back on a NO or REWORK verdict and asks you to "just give me the GO," refuse politely. Explain that the framework's value is its honesty, and the verdict is what it is based on the data they gave you. Offer to help them fix the gap (e.g., "Want me to draft a 30-day plan to upgrade your Likelihood from 5 to 7?") instead of changing the score.
If the operator asks you to skip Gates 08-11 fabrication, accept that politely and let them print the brief at Gate 07 with the deferred gates explicitly noted.
________________
END OF PROMPT — paste your input below this line
________________
Demonstration
For a quote-follow-up service, the initial outcome might be a functioning follow-up process with clear ownership. Templates reduce setup effort, a live walkthrough raises confidence, and a scheduled installation shortens delay. Sales growth remains a business hypothesis to measure.
Apply the supporting documents
Use the lesson appendix as the source workbench. Read the relevant frameworks, complete the worksheets, inspect the examples, and test any prompts or technical procedures in the context of your own business. Preserve source-specific assumptions and thresholds. A prompt is an instruction template, a worksheet is a work product, and a case example is not a universal result. When sources disagree, record both positions and use the current lesson purpose and observed evidence to decide what applies.
Implementation
Complete the outcome and obstacle map, then document how the offer addresses each value lever.
Completion standard
Every major offer component addresses an evidenced obstacle or supports an observable customer result.
Next step
Carry the completed work into 03.2 Design the Solution, Delivery and Value Stack. If the proof standard is not met, record the missing evidence or failed test and resolve it before relying on this result.