RISER NATION CORP

IF YOU AREN'T BUILDING, YOU ARE DESTROYING

03.3 Price, Proof, Risk Reversal and Validation — Part 5 of 5

Offer development and operating practice — source-linked curriculum

Working teaching for review; source and dependency gaps remain identified in each module.

Lesson 03.3

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

Assigned source documents: riser-first-dollar-forge-v3 (2).html — source 1 · riser-first-dollar-forge-v3 (2).html — source 2 ·

First Dollar Forge: version3 workflow

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

Working curriculum for review. Source bodies and distinct teaching have been reviewed in a first pass; remaining dependency, version, accessibility and semantic checks are not certified complete. Commercial examples are educational proposals, not active offers. Assigned lesson 03.3.

Video placeholder

Record the workflow and version distinctions after confirming the demonstrated tool is appropriate to use.

Lesson outline

Choose a small, accountable first offer
Setup and format routing in version3
Viability: distinguish a first sale from a scalable business
Skill audit: turn experience into observable deliverables
Buyer match: investigate fit and readiness
Offer design: define scope before persuasion
Sales conversation and scripts: make one relevant request
Nine offer scores and a corrected value-ratio example
Fulfillment blueprint: plan the customer experience
The fourteen-day sprint and its decision gates
Payment-platform examples and continuity of the record
Use the source formulas without fabricating evidence
Worked offer exercise: make every promise inspectable
Worked writing exercise: messages, discovery and an honest close
Evidence, tools and responsible use

Choose a small, accountable first offer

The Forge is a planning assistant for an initial knowledge-based sale. Its operating sequence favors a service before a large product, direct conversations before a complex funnel, manageable transaction volume and proof before scale. Treat these as a beginner-validation approach, not rules that make every other model invalid. Selling two services at$500 and ten at$100 both produces$1,000 gross; workload, sales effort, cost and buyer fit determine which is better.

Begin with one honest description of relevant skill, experience and the problem you can competently address. The source’s example niches are first-time home-buyer guidance, corporate wellness, freelance web design, dog training, small-business bookkeeping, nutrition for busy parents, real-estate investing basics and Excel/data skills. They are examples, not verified opportunities or evidence of qualifications to offer regulated advice.

The target is an experiment that creates useful customer evidence and delivers its promise. Track collected revenue separately from profit, and include fees, refunds, support and fulfillment time. A generated plan cannot supply real buyer research, authentic testimonials or permission to contact people.

Supporting sources: riser-first-dollar-forge-v3 (2).html — source variant 1 · riser-first-dollar-forge-v3 (2).html — source variant 2 · Version comparison — riser-first-dollar-forge.html — variant 1

Setup and format routing in version3

Answer three setup questions: direct/related/no experience, comfort with live calls and preference for live or asynchronous delivery. In code, relevant experience plus comfortable live delivery and a non-async preference selects consulting; relevant experience with other non-async combinations selects an audit; relevant experience plus async selects mini done-for-you; no experience selects a template. Missing answers fall back to audit internally, even though the interface intends completed answers.

That routing is a rough suggestion, not a competency assessment. A novice is not qualified to sell a toolkit simply because a selector recommends it. The formats and proposed prices are Audit$200–$400(default300), StrategyCall$150–$300(default200), MiniDFY$300–$500(default400), and Template$97–$200(default150). Price and delivery risk still need validation.

The interface’s four static gross-revenue paths are2×$500,4×$250,10×$100 and20×$50. It assigns outreach estimates14/22/50/100 and timing2–5/3–6/5–8/10-plus days. These are hardcoded assumptions; the first path is highlighted regardless of the qualifier result. Do not represent it as a personalized forecast.

Supporting sources: riser-first-dollar-forge-v3 (2).html — source variant 1 · riser-first-dollar-forge-v3 (2).html — source variant 2

Viability: distinguish a first sale from a scalable business

Review five possible changes to a weak idea: retire it, reduce it to a feature, package it inside a stronger offer, use it to reach an audience, or use it as an entry to affiliate/service revenue. Explain the evidence behind the recommendation; an AI verdict alone cannot determine that a market need is absent.

The four business-model tests concern recurring potential, economics at volume, growth without proportional founder time and defensibility. Version3 asks for PASS/FAIL reasons, one path toward the first$1,000 and one structural risk with mitigation. A one-off service can be a useful experiment even if it is not yet recurring or defensible.

Before scaling, examine buyer clarity, purchases beyond personal relationships, contribution after acquisition cost, repeatable fulfillment and acceptable refunds/churn. The source additionally suggests three manual sales before automation and payment before website building. Those are focus heuristics. Legal, accessibility, payment, delivery and other necessary infrastructure cannot be skipped merely because a blocklist discourages polish.

Supporting sources: riser-first-dollar-forge-v3 (2).html — source variant 1 · riser-first-dollar-forge-v3 (2).html — source variant 2

Skill audit: turn experience into observable deliverables

List five to seven specific services or deliverables with an output and timeframe. For example, a bounded review could produce a two-page improvement report within an agreed period; avoid promising a complete transformation from vague advice. Check that you have the skill, access and time to do what you propose.

Describe useful experience another person may value, two or three reachable buyer types, and a hidden problem existing approaches may overlook. The source calls that hidden issue a sewer leak. Treat the proposed cause as a hypothesis requiring evidence rather than assuming the model discovered the market’s most important problem.

The earlier version also requests an honest first-sale challenge and a response. Version3 adds a named mechanism statement contrasting a common assumption with an evidence-supported explanation: the buyer struggles not simply because of the assumed cause but because of a specific process failure. A memorable label must clarify an actual method, not disguise a fabricated cause.

Buyer match: investigate fit and readiness

Describe a specific situation, problem and prior attempted solution. Identify three places the relevant people can appropriately be reached through existing relationships, professional networks or relevant communities. Name three observable signs of need or timing, such as a stated deadline or request for help. A so-called hot-hand signal does not prove someone will pay this week.

Define unsuitable situations using scope, ability to benefit, readiness and boundaries rather than dismissing anyone who asks questions as a bad buyer. For version3, separately examine time lost, money lost, stress, prior attempts and urgency. Watch whether an unexpected segment responds better and investigate what that says about the initial hypothesis.

Keep actual quotations and evidence distinct from generated buyer descriptions. The source asks for specific ages and roles as examples; relevant buying context is more useful than invented demographic detail. No list, conversation or buyer intent is established merely because AI wrote it down.

Offer design: define scope before persuasion

Give the offer a clear three-to-seven-word name and a one-sentence promise connecting person, problem, concrete result, timeframe and obstacle removed. The earlier source emphasizes result leading to a meaningful outcome; version3 uses the person/problem/result/time/frustration structure explicitly.

Name every deliverable, duration and format. Explain the day-by-day delivery process and a supportable guarantee, if appropriate, without creating terms you cannot honor. A forty-five-minute call, written report or recorded walkthrough is clearer than a session. The earlier version asks for a two-sentence buyer-value price rationale; use actual evidence and economics to support it.

Version3 limits the suggested early delivery tools to Zoom, Loom, Google Docs and email and requires four or five explicit exclusions. These are simplification choices, not proof other tools are unsuitable. Include inputs, revision limits, access and responsibilities so scope stays manageable.

Sales conversation and scripts: make one relevant request

Prepare a warm message under sixty words with one specific question, and a short cold/community message referring to a genuine observation about the recipient. The older prompt caps the cold message below fifty words; version3 uses below fifty-five. Personalization requires true context, not invented familiarity.

Use the fifteen-minute discovery outline to understand the situation, listen for needs and fit, explain the relevant offer and agree a next step if appropriate. The close message should specify the actual deliverable, price, payment method and next action. Do not hide the scope or pressure an unsuitable buyer into a commitment.

Prepare honest responses to price concerns, uncertainty about fit and requests for more time. Ask what the concern means before proposing an answer. Version3 adds a cost-of-inaction comparison: use a supported cost and a realistic potential benefit, not an inflated loss designed to force urgency. These are writing exercises; no outreach, payment request or sales call is executed by this lesson.

Nine offer scores and a corrected value-ratio example

Version3 rates nine areas from one to ten: pain, urgency, clarity, willingness to pay, ease of fulfillment, confidence to deliver, ease of closing, ease of obtaining genuine feedback and repeatability. Sum to a maximum of ninety and explain each rating with evidence. The source requests Strong/Caution/Reframe labels but defines no numerical boundaries, so do not invent them or treat them as validated categories.

The code compares annual unsolved-problem cost divided by price and seeks at least ten-to-one. If the supported cost is$2,000 and price$300, the ratio is6.67. Raising price lowers that ratio; it cannot repair the source’s below-ten instruction. Holding that cost fixed, a ten-to-one target requires price no greater than$200. Alternatively, verify whether the offer addresses a different, genuinely larger cost—never inflate the estimate.

This cost ratio is not the same as realized benefit, willingness to pay or Hormozi’s conceptual outcome/likelihood/time/effort framework. A possible avoided loss is not a guaranteed customer gain. The source’s phrase one-tenth at minimum also conflicts with its own inequality, so use explicit assumptions and arithmetic.

Supporting sources: riser-first-dollar-forge-v3 (2).html — source variant 1 · riser-first-dollar-forge-v3 (2).html — source variant 2 · Acquisition.com — offer design framework

Fulfillment blueprint: plan the customer experience

Prepare the document, checklist or template needed before delivery. Map what happens each day, what you send, what the client supplies and the observable signals of a good result. Anticipate two likely delivery failures and specify an honest response for each, including what requires a revised agreement.

After the first delivery, save reusable structure and document the work so the next delivery can improve. The prompt’s forty-percent speed gain is a target without evidence. Measure actual hours and quality instead of assuming a template achieves it.

The source requests a two-sentence feedback/testimonial invitation within forty-eight hours. Ask what changed and what was useful, without scripting a favorable result or making feedback compulsory. Obtain permission before publishing identifiable feedback and preserve its context.

Supporting sources: riser-first-dollar-forge-v3 (2).html — source variant 1 · riser-first-dollar-forge-v3 (2).html — source variant 2

The fourteen-day sprint and its decision gates

Days1–2 allow at most three preparation tasks and propose starting appropriate outreach on day2afternoon. Days3–7 focus on a specific daily activity and prospect priority. Days8–11 turn interested conversations into clear decisions and diagnose lack of response. Days12–14 focus on responsible delivery, feedback and a possible second engagement.

The prompt asks for measurable gates on days3,7,11 and14, with first revenue by11 and a$1,000 checkpoint at14. These are proposed targets, not deadlines the model can guarantee. Before the sprint, record which scale assumptions remain unproven and what evidence this test can realistically supply.

If there are no conversions by day11, change one hypothesis—buyer, promise, price, package or channel—while preserving a record of the previous test. Avoid treating a short period without adequate exposure as conclusive proof. After initial sales, improve fulfillment and evidence before multiplying volume.

The structural-drift list discourages websites, branding, automation/CRM, social accounts, content and funnels too early. Its timing conflicts: the interface says until Phase6, the script still postpones these before outreach, the system waits for payment for websites and three manual sales for automation. Teach focus on necessary delivery and evidence, not a single falsely consistent prohibition.

Supporting sources: riser-first-dollar-forge-v3 (2).html — source variant 1 · riser-first-dollar-forge-v3 (2).html — source variant 2

Payment-platform examples and continuity of the record

The source routes audit and done-for-you services toward Stripe Payment Links, calls toward a Calendly event with Stripe payments, and templates toward Gumroad. Official documentation confirms the general hosted-payment and scheduled-payment capabilities. Verify account eligibility, terms, fees, taxes, refunds and actual product configuration before any operational setup. Writing this lesson creates no account, product or payment link.

A free product option is not the same as fee-free paid selling. Gumroad’s own pricing and free-product guidance should govern its current terms rather than the source’s shorthand. Keep the purchase promise, access instructions and deliverable consistent across the chosen system.

Version3 passes only the last two prior outputs, each cut to eight hundred characters, plus a three-hundred-character viability excerpt in the skill phase. Maintain a complete approved brief containing buyer evidence, exclusions, price assumptions and delivery commitments; compare every later output against it to prevent omitted constraints.

Supporting sources: riser-first-dollar-forge-v3 (2).html — source variant 1 · riser-first-dollar-forge-v3 (2).html — source variant 2 · Stripe — hosted Payment Links · Calendly — Stripe payment integration · Gumroad — fees · Gumroad — free/pay-what-you-want products

Use the source formulas without fabricating evidence

The version3 offer prompt specifies this structure: I help [SPECIFIC PERSON] solve [SPECIFIC PAINFUL PROBLEM] by giving them [SMALL CONCRETE RESULT] in [SHORT TIMEFRAME] without [MAJOR FRUSTRATION THEY HAVE EXPERIENCED BEFORE]. Fill each slot with evidence-backed scope. In the practice case, the small result is a prioritized clarity report; a sales increase would be a different and unsupported promise.

Its mechanism prompt uses: Most [buyers] fail at [goal] not because of [common assumption] but because of [Mechanism Name] — [one sentence explanation]. This is the source’s requested copy structure, not proof that a single cause explains the problem. Use it only when the causal explanation is justified; otherwise state a qualified hypothesis instead of dismissing alternative causes.

The cost-of-inaction prompt asks whether avoiding a specific cost would be a fair trade. Establish that cost with the buyer and explain what portion the offer could realistically address. If the evidence is missing, explain the deliverable and price directly. Do not transform a hypothetical lost sale into a guaranteed saving.

Supporting sources: riser-first-dollar-forge-v3 (2).html — source variant 1 · riser-first-dollar-forge-v3 (2).html — source variant 2

Worked offer exercise: make every promise inspectable

This is an authored practice case, not a current RISER offer or a proven market opportunity. Assume a designer can competently review one existing desktop service page. The buyer is an independent consultant who says prospects cannot understand the service. Before proposing work, verify that this is the buyer’s actual problem and that a page review is within the designer’s skill.

A possible exercise name is Consultant Service Page Clarity Audit. Define delivery as a recorded walkthrough of up to fifteen minutes plus a two-page report with five prioritized clarity changes, delivered within two working days after receiving the page link and agreed context. This promises a review artifact, not more sales. The five recommendations must identify the confusing element, why it matters and a concrete revision.

Inputs are the existing public page, intended customer, service scope and the buyer’s own account of confusion. Day one: inspect the page and draft the findings. Day two: verify the recommendations against the brief and deliver the report and recording. Use an agreed private delivery route if the material is confidential. Do not invent customer quotes or conversion data.

Example exclusions are implementation, a website rebuild, search rankings, paid-ad management and a guaranteed sales increase. A bounded remedy could be correcting an incomplete report against the agreed specification; its exact terms need agreement. A hypothetical $200 price is a scenario, not a recommendation. Evaluate actual time, fees, revisions and willingness to pay before making a real offer.

Score the nine version3 areas only when using that version, explaining evidence and unknowns rather than selecting numbers to force a favorable verdict. If the buyer’s cost of the problem is unknown, say unknown. Do not manufacture an annual loss to justify the price. The earlier version can use the same clear scope without claiming it contains the version3 scoring system.

Worked writing exercise: messages, discovery and an honest close

The following examples are drafts to adapt only to true context. Nothing is sent. Warm example: You mentioned that prospects struggle to understand your consulting page. I am testing a focused review that identifies five clarity improvements. Would you be open to a short conversation about where visitors seem to get stuck? This ends with one specific question and stays under the source’s sixty-word limit.

Cold example: I read your public page about team coaching. I could not tell whether the workshop or ongoing support is the main service. Would you be open to one question about how you want prospects to choose? Use this only if that observation is true. It is below both versions’ cold-message limits and contains one request.

For an authored fifteen-minute discovery outline, use roughly two minutes for context and permission, five for the problem and prior attempts, four for the desired outcome and fit, and four for a clear next step. These minute allocations are an authored aid; the source asks for an ordered structure but does not prescribe them. Ask what people misunderstand, what the buyer has tried, what would make a review useful and what constraints apply. Listen before presenting scope.

Example close after genuine interest: The exercise package is a recorded walkthrough and a two-page report with five prioritized changes for $200, delivered within two working days after I receive the agreed inputs. It excludes implementation and sales guarantees. If that scope fits, the next step is to confirm the written brief and payment method. Replace every example term with the actual agreed one before use.

For a price concern, ask whether the uncertainty is budget, priority or expected usefulness; explain scope without inventing ROI. For fit, identify the outcome the buyer needs and say when the service would not address it. For a timing objection, ask what information or date would make a decision possible and respect a decline. A concern is not proof of a hidden fear; the buyer’s answer determines the response.

Evidence, tools and responsible use

Both source files send user prompts directly from the browser to a hardcoded model, read the first returned text block and do not check whether output was truncated. The older cap is1,000tokens and version3 uses1,500. A returned answer therefore does not demonstrate that all requested fields were completed. Check each deliverable against the phase checklist.

Both keep only the API key in session storage; niche, profile and generated outputs are held in memory and can disappear on reload. Version3 adds a final text download. Maintain a separate complete working record rather than assuming the browser is durable storage.

The source code exposes a direct-browser credential design and inserts generated markup without sanitization. The lesson preserves these files as non-executable source text and does not request credentials or run them as a course embed. Its free-key, model-availability and cost-per-run claims are time-sensitive and are not accepted here as current setup instructions.

Code inspection also identified phase-advance behavior that can hide the new output until returning to the prior screen, and navigation paths that may require regeneration. Version3 has additional niche-input/rerender and numeric-input focus concerns. These are static review findings, not live-tested behavior or fixes. Preserve the intended workflow while verifying the actual tool before demonstrating it.

Practice and completion check

Produce an evidence-linked buyer hypothesis, a bounded offer, a delivery checklist, draft conversation scripts and a dated test plan. Record assumptions behind every price, conversion rate and promised outcome. Check every generated section manually and preserve all decisions outside the tool before proceeding.

Complete original HTML/CSS/JavaScript — source variant 1, non-executable

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>RISER First Dollar Forge v3</title>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link href="https://fonts.googleapis.com/css2?family=Lora:ital,wght@0,500;0,600;1,400&family=DM+Sans:opsz,[email protected],400;9..40,500&family=DM+Mono:wght@400;500&display=swap" rel="stylesheet">
<style>
:root{--bg:#0C0F14;--panel:#141920;--card:#1C2430;--border:#2A3340;
--gold:#C9A84C;--gold-dim:rgba(201,168,76,.12);--gold-bright:#EAB84C;
--green:#3FB950;--green-dim:rgba(63,185,80,.1);--green-b:rgba(63,185,80,.3);
--amber:#E68A1A;--amber-dim:rgba(230,138,26,.1);
--red:#F85149;--red-dim:rgba(248,81,73,.09);--red-b:rgba(248,81,73,.35);
--info:#58A6FF;--info-dim:rgba(88,166,255,.08);
--purple:#A78BFA;--purple-dim:rgba(167,139,250,.1);
--text:#E6EDF3;--muted:#7D8590;--hint:#4A5568;
--mono:'DM Mono',monospace;--serif:'Lora',serif;--sans:'DM Sans',sans-serif}
*{box-sizing:border-box;margin:0;padding:0}
body{background:var(--bg);color:var(--text);font-family:var(--sans);min-height:100vh;font-size:14px;line-height:1.7}
.app{max-width:800px;margin:0 auto;padding:24px 20px}
.hdr{display:flex;align-items:center;justify-content:space-between;margin-bottom:22px;padding-bottom:14px;border-bottom:.5px solid var(--border)}
.brand{font-family:var(--mono);font-size:11px;letter-spacing:.1em;color:var(--gold)}
.brand span{color:var(--muted)}
.brand sup{font-size:8px;color:var(--amber)}
.pills{display:flex;gap:5px;flex-wrap:wrap}
.pill{font-size:10px;padding:3px 9px;border-radius:20px;border:.5px solid var(--border);color:var(--hint);font-family:var(--mono);cursor:pointer;background:none;transition:all .15s}
.pill.done{background:var(--green-dim);color:var(--green);border-color:var(--green-b)}
.pill.active{border:1px solid var(--gold);color:var(--gold);background:var(--gold-dim)}
.pill:hover:not(.active):not(.done){border-color:var(--muted);color:var(--muted)}
.prog-wrap{margin-bottom:18px}
.prog-bar{height:2px;background:var(--border);border-radius:1px;overflow:hidden}
.prog-fill{height:100%;background:var(--gold);border-radius:1px;transition:width .4s}
.prog-label{font-size:11px;color:var(--muted);font-family:var(--mono);margin-top:5px;display:flex;justify-content:space-between}
.phase-num{font-family:var(--mono);font-size:10px;letter-spacing:.12em;color:var(--muted);margin-bottom:4px;text-transform:uppercase}
.section-head{font-family:var(--serif);font-size:22px;font-weight:500;margin-bottom:4px}
.section-sub{font-size:13px;color:var(--muted);margin-bottom:18px;line-height:1.6}
textarea,.text-in{width:100%;padding:10px 14px;background:var(--card);border:.5px solid var(--border);border-radius:8px;color:var(--text);font-family:var(--sans);font-size:14px;resize:vertical;outline:none;transition:border-color .15s;line-height:1.6}
textarea:focus,.text-in:focus{border-color:var(--gold)}
textarea::placeholder,.text-in::placeholder{color:var(--hint)}
.q-card{background:var(--card);border:.5px solid var(--border);border-radius:10px;padding:16px;margin-bottom:12px}
.q-label{font-size:13px;font-weight:500;margin-bottom:10px}
.q-opts{display:flex;flex-direction:column;gap:6px}
.q-opt{display:flex;align-items:flex-start;gap:9px;padding:8px 10px;border:.5px solid var(--border);border-radius:7px;cursor:pointer;transition:all .15s}
.q-opt:hover{border-color:var(--muted)}
.q-opt.sel{border-color:var(--gold);background:var(--gold-dim)}
.q-opt input[type=radio]{accent-color:var(--gold);margin-top:3px;flex-shrink:0}
.q-opt-text{font-size:13px}
.q-opt-sub{font-size:11px;color:var(--muted);margin-top:1px}
.mvo-rec{background:var(--green-dim);border:1px solid var(--green-b);border-radius:9px;padding:14px 16px;margin-bottom:16px}
.mvo-rec-label{font-family:var(--mono);font-size:9px;color:var(--green);letter-spacing:.12em;text-transform:uppercase;margin-bottom:5px}
.mvo-rec-title{font-size:15px;font-weight:500;color:var(--green);margin-bottom:3px}
.mvo-rec-reason{font-size:12px;color:var(--muted);line-height:1.5}
.five-choices{margin-bottom:14px}
.choice-row{display:flex;gap:8px;padding:9px 12px;border-radius:8px;margin-bottom:5px;border:.5px solid var(--border);background:var(--panel)}
.choice-num{font-family:var(--mono);font-size:15px;font-weight:500;min-width:22px;flex-shrink:0;line-height:1.3}
.choice-title{font-size:12px;font-weight:500;margin-bottom:1px}
.choice-detail{font-size:11px;color:var(--muted)}
.four-paths{display:grid;grid-template-columns:1fr 1fr;gap:8px;margin:12px 0}
.path-card{background:var(--card);border:.5px solid var(--border);border-radius:8px;padding:12px 14px}
.path-card.rec{border:1.5px solid var(--green-b);background:var(--green-dim)}
.path-math{font-family:var(--mono);font-size:16px;font-weight:500;margin-bottom:3px}
.path-math.rec{color:var(--green)}
.path-detail{font-size:11px;color:var(--muted);margin-bottom:3px}
.path-badge{display:inline-block;font-size:10px;padding:2px 7px;border-radius:20px}
.badge-rec{background:var(--green-dim);color:var(--green)}
.badge-hard{background:var(--red-dim);color:var(--red)}
.badge-ok{background:var(--amber-dim);color:var(--amber)}
.ratio-row{display:flex;align-items:center;gap:10px;margin:12px 0}
.ratio-in{flex:1;padding:8px 12px;background:var(--card);border:.5px solid var(--border);border-radius:7px;color:var(--text);font-family:var(--mono);font-size:14px;outline:none;transition:border-color .15s}
.ratio-in:focus{border-color:var(--gold)}
.ratio-disp{font-family:var(--mono);font-size:15px;min-width:80px;text-align:right}
.platform-box{background:var(--card);border:.5px solid var(--border);border-radius:9px;padding:14px 16px;margin:12px 0}
.platform-label{font-family:var(--mono);font-size:9px;color:var(--gold);letter-spacing:.12em;text-transform:uppercase;margin-bottom:10px}
.platform-name{font-size:14px;font-weight:500;color:var(--gold);margin-bottom:3px}
.platform-setup{font-size:12px;color:var(--text);margin-top:6px;padding:8px 10px;background:var(--panel);border-radius:6px}
.drift-bar{background:var(--red-dim);border:.5px solid var(--red-b);border-radius:9px;padding:12px 16px;margin-bottom:18px}
.drift-label{font-family:var(--mono);font-size:9px;color:var(--red);letter-spacing:.12em;text-transform:uppercase;margin-bottom:7px}
.drift-grid{display:grid;grid-template-columns:1fr 1fr;gap:4px}
.drift-item{font-size:12px;color:var(--red);display:flex;align-items:center;gap:6px}
.drift-item::before{content:'✕';font-size:10px;flex-shrink:0}
.ex-chips{display:flex;flex-wrap:wrap;gap:6px;margin-bottom:14px}
.chip{padding:5px 12px;background:var(--card);border:.5px solid var(--border);border-radius:20px;font-size:12px;color:var(--muted);cursor:pointer;transition:all .15s}
.chip:hover{border-color:var(--gold);color:var(--gold)}
.out-box{background:var(--card);border:.5px solid var(--border);border-radius:10px;padding:18px;margin-bottom:14px}
.out-box.loading{display:flex;align-items:center;gap:12px;min-height:60px}
.spinner{width:15px;height:15px;border:1.5px solid var(--border);border-top-color:var(--gold);border-radius:50%;animation:spin .7s linear infinite;flex-shrink:0}
.load-txt{font-size:13px;color:var(--muted)}
.out-content h2{font-family:var(--mono);font-size:10px;color:var(--muted);text-transform:uppercase;letter-spacing:.1em;margin:14px 0 7px;padding-bottom:4px;border-bottom:.5px solid var(--border)}
.out-content h2:first-child{margin-top:0}
.out-content h3{font-size:13px;font-weight:500;color:var(--gold-bright);margin:9px 0 3px}
.out-content p{font-size:13px;margin-bottom:6px}
.out-content ul{padding-left:16px;margin-bottom:8px}
.out-content li{font-size:13px;margin-bottom:3px}
.out-content strong{font-weight:500;color:var(--gold-bright)}
.script-box{background:var(--info-dim);border-left:3px solid var(--info);border-radius:0 8px 8px 0;padding:12px 14px;margin:8px 0}
.script-label{font-family:var(--mono);font-size:10px;color:var(--info);text-transform:uppercase;letter-spacing:.08em;margin-bottom:6px}
.action-row{display:flex;align-items:center;gap:8px;flex-wrap:wrap;margin-top:16px}
.btn{padding:9px 18px;font-size:13px;border-radius:7px;cursor:pointer;transition:all .15s;font-family:var(--sans);border:.5px solid var(--border);background:transparent;color:var(--muted)}
.btn:hover{border-color:var(--muted);color:var(--text)}
.btn:disabled{cursor:not-allowed;opacity:.4}
.btn.primary{background:var(--gold);color:var(--bg);border-color:var(--gold);font-weight:500}
.btn.primary:hover{background:var(--gold-bright)}
.btn.primary:disabled{background:var(--hint);border-color:var(--hint)}
.err{background:var(--red-dim);border:.5px solid var(--red-b);border-radius:7px;padding:10px 14px;font-size:13px;color:var(--red);margin-bottom:14px}
.key-row{display:grid;grid-template-columns:1fr auto;gap:8px;margin-bottom:6px}
.key-note{font-size:12px;color:var(--hint)}
.key-note a{color:var(--muted)}
.divider{height:.5px;background:var(--border);margin:20px 0}
.hint-txt{font-size:12px;color:var(--hint)}
.scaling-grid{display:grid;grid-template-columns:1fr 1fr;gap:8px;margin:10px 0}
.sc-item{background:var(--panel);border-radius:7px;padding:9px 11px;border:.5px solid var(--border)}
.sc-check{width:14px;height:14px;border-radius:50%;background:var(--green-dim);border:.5px solid var(--green-b);display:inline-block;margin-right:6px;vertical-align:middle}
.sc-text{font-size:12px}
@keyframes spin{to{transform:rotate(360deg)}}
::-webkit-scrollbar{width:4px}
::-webkit-scrollbar-thumb{background:var(--border);border-radius:2px}
</style>
</head>
<body>
<div class="app">
<div class="hdr">
  <div class="brand">RISER <span>|</span> First Dollar Forge<sup> v3</sup></div>
  <div class="pills" id="pills"></div>
</div>
<div class="prog-wrap">
  <div class="prog-bar"><div class="prog-fill" id="prog" style="width:0%"></div></div>
  <div class="prog-label"><span id="prog-label">Ready</span><span id="prog-count">0/7 phases</span></div>
</div>
<div id="body"></div>
</div>

<script>
const SYS=`You are the RISER Nation First Dollar Architect v3.

OPERATING LAW:
1. Service before product. Expertise sold directly before building any course.
2. Outreach before inbound. Direct personal contact before any audience exists.
3. Conversation before funnel. A 15-minute call beats a sales page with no social proof.
4. Fewer transactions always. 2 clients at $500 beats 10 clients at $100.
5. Proof before scale. First $1K is proof-gathering, not a business launch.
6. Never automate what you haven't sold manually at least three times.

FIVE HONEST CHOICES for a failing/weak idea (use these when relevant):
1. Kill it — market need is not real
2. Reduce to a feature — too small to stand alone
3. Wrap in a stronger offer — knowledge is real, packaging is wrong
4. Turn into a channel/audience wedge — build audience, monetize differently
5. Use as front-end for affiliate or service revenue

FASTEST $1K PATHS (in order): Audit/review ($200-400) → Strategy call ($150-300) → Mini DFY ($300-500) → Template/toolkit ($97-200)

FOUR BUSINESS MODEL TESTS — flag if idea fails any:
1. Recurring revenue potential
2. Unit economics survive at volume
3. Revenue can grow without proportional founder time
4. Defensible moat exists

PRE-SCALING CONDITIONS (before recommending scale):
Buyer is clear, offer converts from non-personal contacts, margin survives acquisition at volume, fulfillment is repeatable without founder, churn/refunds are tolerable.

NEVER RECOMMEND: building a course first, running paid ads, growing social audience first, building automation before 3 manual sales, website before first payment.

OUTPUT: Specific, concrete, immediately actionable. Write actual scripts. Every output usable today.`;

const PHASES=[
  {id:0,l:'Setup'},
  {id:1,l:'Viability check'},
  {id:2,l:'Skill audit'},
  {id:3,l:'Buyer match'},
  {id:4,l:'Offer design'},
  {id:5,l:'Fulfillment'},
  {id:6,l:'Sale scripts'},
  {id:7,l:'14-day sprint'},
];

const MVO_FORMATS={
  audit:{label:'Audit / Review',range:'$200–400',reason:"You have experience spotting problems. Delivers a concrete written report in 1-3 hours."},
  consult:{label:'Strategy Call',range:'$150–300',reason:"You can think clearly about someone's situation and give direction. Zero build required."},
  dfy:{label:'Mini Done-For-You',range:'$300–500',reason:"You can produce something tangible for the client. Low fulfillment risk."},
  template:{label:'Template / Toolkit',range:'$97–200',reason:"Packaged solution that doesn't require live delivery."},
};

const PLATFORMS={
  audit:{name:'Stripe Payment Links',setup:'dashboard.stripe.com → Products → Payment Links. No website needed. Share the URL directly in DMs and bio.'},
  consult:{name:'Calendly with payment enabled',setup:'Create a Calendly event → enable "Collect Payments" → connect Stripe. Client books and pays in one step.'},
  dfy:{name:'Stripe Payment Links',setup:'Create a Payment Link for your service. After payment, send delivery instructions and intake form by email.'},
  template:{name:'Gumroad',setup:'Free Gumroad account → New Product → Upload template → Set price → Share the link. $0 option for email capture.'},
};

const FOUR_PATHS=[
  {math:'2 × $500',clients:2,price:500,outreach:14,days:'2-5',badge:'rec',note:'Fewest conversations. Worth the harder close.'},
  {math:'4 × $250',clients:4,price:250,outreach:22,days:'3-6',badge:'ok',note:'Sweet spot for most niches.'},
  {math:'10 × $100',clients:10,price:100,outreach:50,days:'5-8',badge:'ok',note:'More closings than it looks.'},
  {math:'20 × $50',clients:20,price:50,outreach:100,days:'10+',badge:'hard',note:'Avoid as first target.'},
];

let S={
  key:sessionStorage.getItem('fdf3_k')||'',
  niche:'',q1:null,q2:null,q3:null,
  mvo:'audit',price:300,unsolved:'',
  phase:0,out:{},loading:false,err:''
};

function getMvo(){
  if(!S.q1||!S.q2||!S.q3)return'audit';
  const exp=S.q1==='yes'||S.q1==='some';
  const live=S.q2==='yes';
  const async_p=S.q3==='async';
  if(exp&&live&&!async_p)return'consult';
  if(exp&&!async_p)return'audit';
  if(exp&&async_p)return'dfy';
  return'template';
}
function getMvoPrice(m){return{audit:300,consult:200,dfy:400,template:150}[m]||250;}

function save(){sessionStorage.setItem('fdf3_k',S.key);}
async function callClaude(prompt){
  const r=await fetch('https://api.anthropic.com/v1/messages',{
    method:'POST',
    headers:{'Content-Type':'application/json','x-api-key':S.key,'anthropic-version':'2023-06-01','anthropic-dangerous-direct-browser-access':'true'},
    body:JSON.stringify({model:'claude-sonnet-4-20250514',max_tokens:1500,system:SYS,messages:[{role:'user',content:prompt}]})
  });
  const d=await r.json();
  if(!r.ok||d.error)throw new Error(d.error?.message||'API error '+r.status);
  return d.content[0].text;
}

function buildPrompt(ph){
  const prev=Object.entries(S.out).filter(([k])=>Number(k)<ph).slice(-2).map(([k,v])=>`[Phase ${k}]:\n${v.slice(0,800)}`).join('\n\n');
  const ctx=prev?`\n\nPrior phases:\n${prev}\n\n`:'';
  const ml=MVO_FORMATS[S.mvo]?.label||'audit';
  const ps={
    1:`Niche/idea: "${S.niche}"\n\nIDEA VIABILITY CHECK — run this before anything else.\n\n## The 5 Honest Choices assessment\nFor this specific idea, which of the 5 Honest Choices applies? Be direct:\n1. Kill it (market need is not real)\n2. Reduce to a feature\n3. Wrap in a stronger offer\n4. Turn into a channel or audience wedge\n5. Use as front-end for affiliate or service revenue\n\nState your verdict clearly: "This idea is most likely Choice [X] because..."\n\n## The 4 Business Model Tests\nFor each test, rate PASS/FAIL with one sentence:\n1. Recurring revenue potential\n2. Unit economics survive at volume\n3. Revenue can grow without proportional founder time\n4. Defensible moat exists\n\n## The fastest $1K path for this idea\nGiven the viability assessment, what is the single fastest path to $1,000 for this specific niche? Name it precisely.\n\n## The one structural risk\nThe most likely failure mode for this specific niche — and the exact mitigation.`,

    2:`${ctx}Niche: "${S.niche}"\nViability verdict: ${S.out[1]?.slice(0,300)||'not run'}\nProfile: ${S.q1==='yes'?'has direct experience':S.q1==='some'?'some related experience':'new to this'}. ${S.q2==='yes'?'Comfortable on live video calls':S.q2==='some'?'Somewhat comfortable live':'Prefers async delivery'}. Recommended MVO: ${ml}.\n\nSKILL AUDIT — complete beginner, no audience.\n\n## What you can deliver for someone today\n5-7 specific deliverables matched to the ${ml} format. Each must be a concrete outcome with a timeframe: "Spend 60 minutes reviewing X and produce a written report with 5 priority improvements within 24 hours." Not vague: "teach people about X."\n\n## Your unfair advantage\nWhat does someone with experience in "${S.niche}" know that took years to learn, that someone would pay to skip?\n\n## Who already needs this in your life right now\n2-3 specific types of people in a typical expert's personal network who have this problem today and could pay.\n\n## The Sewer Leak\nThe #1 hidden problem in "${S.niche}" that existing solutions completely miss.\n\n## The Mechanism Statement\nName WHY the usual approach fails in this niche. Give it a memorable label: "The [Name] Problem." Format: "Most [buyers] fail at [goal] not because of [common assumption] but because of [Mechanism Name] — [one sentence explanation]."`,

    3:`${ctx}Niche: "${S.niche}". MVO: ${ml}.\n\nBUYER MATCH + PAIN FILTER — reach them with no audience.\n\nPain filter first:\nWhich problem costs them TIME? Which costs MONEY? Which creates STRESS? Which have they already tried to solve? Which do they want fixed fastest?\n\n## The ideal first buyer\nSpecific: "a [age] [exact role/situation] who has [specific problem], has already tried [specific approach], and is actively frustrated right now." Give their exact current state.\n\n## The Hot-Hand Signal\n3 specific phrases, situations, or behaviours that mean this person will pay THIS WEEK, not someday.\n\n## Where to find them without an audience\n3 specific places the operator can access TODAY: personal LinkedIn connections, local community groups, online communities by name. No paid traffic.\n\n## The Negative Buyer\nWho looks right but will waste time? The person who asks many questions, never commits, drains energy. How to spot them in the first message.\n\n## The "wrong buyer responded better" watch\nFor this niche, what buyer TYPE might convert better than the intended one? What would that signal about the business model?`,

    4:`${ctx}Niche: "${S.niche}". Format: ${ml}. Price: $${S.price}. Buyer's unsolved problem cost: ${S.unsolved?'$'+S.unsolved:'not specified'}.\n\nOFFER DESIGN — one specific sellable thing.\n\n## THE OFFER FORMULA (mandatory — output this first, exactly)\n"I help [SPECIFIC PERSON] solve [SPECIFIC PAINFUL PROBLEM] by giving them [SMALL CONCRETE RESULT] in [SHORT TIMEFRAME] without [MAJOR FRUSTRATION THEY'VE EXPERIENCED BEFORE]."\n\n## The offer name\n3-7 words. Not clever, not vague. Pattern: [Audience] + [Specific Problem] + [Audit/Sprint/Package].\n\n## Exactly what they receive\nEvery deliverable. Be specific: "A 45-minute Zoom call recorded and sent to them" not "a session."\n\n## How you deliver it (step by step)\nDay-by-day using only: Zoom, Loom, Google Doc, or email. A beginner should be confident delivering this tomorrow.\n\n## MVO SCORING (rate each 1-10 with one-line reason)\n1. Pain intensity: X/10\n2. Urgency: X/10\n3. Offer clarity: X/10\n4. Buyer willingness to pay: X/10\n5. Ease of fulfillment: X/10\n6. Confidence to deliver: X/10\n7. Ease of closing: X/10\n8. Ease of getting testimonials: X/10\n9. Repeatability: X/10\nTOTAL: XX/90 [STRONG PROCEED / PROCEED WITH CAUTION / REFRAME FIRST]\n\n## The 1:10 Value Ratio\n${S.unsolved?`Buyer's cost if unsolved: $${S.unsolved}. Value ratio: ${Math.round(Number(S.unsolved)/S.price)}:1. ${Number(S.unsolved)/S.price>=10?'Strong anchor — defend this price.':'Below 10:1 — either raise the price or identify a more expensive problem.'}`:'State the specific dollar cost to the buyer if this problem remains unsolved for 12 months. Your price should be 1/10th of that number at minimum.'}\n\n## The guarantee\nA specific, beginner-appropriate promise that removes buyer risk.\n\n## NOT included (scope protection)\nList 4-5 things explicitly excluded. This prevents scope creep and protects margin.`,

    5:`${ctx}Niche: "${S.niche}". Offer: ${ml}. Price: $${S.price}.\n\nFULFILLMENT BLUEPRINT — what to do after someone pays.\n\n## Before the first session\nExactly what to prepare: the document, checklist, or template to have ready before delivery.\n\n## The delivery step-by-step\nDay-by-day: what you do first, what you send, what the client experiences. Use only: Zoom, Loom, Google Docs, email. No other tools.\n\n## What a great delivery looks like\nThe specific signals that tell you you've done excellent work — from the client's perspective.\n\n## What can go wrong and how to handle it\nThe 2 most likely delivery problems for a ${ml} in "${S.niche}" and the exact response for each.\n\n## How to make the second delivery faster\nWhat to document, template, or save after the first delivery that makes the second 40% faster.\n\n## The testimonial extraction (send within 48 hours of delivery)\n[SCRIPT]\nThe exact 2-sentence message to send after delivery.\n[/SCRIPT]`,

    6:`${ctx}Niche: "${S.niche}". Offer: ${ml} at $${S.price}.\n\nFIRST SALE SYSTEM — with no audience.\n\nNOTE: Before sending any of these scripts — do NOT build a website, design a logo, set up any automation, or create any content. These scripts work without any of that.\n\n## Warm outreach (personal contacts who know you)\n[SCRIPT]\nUnder 60 words. Conversational, not pitch-y. Ends with one specific yes/no question.\n[/SCRIPT]\n\n## LinkedIn/community outreach (people who don't know you well)\n[SCRIPT]\nUnder 55 words. References something specific about their situation. One request only.\n[/SCRIPT]\n\n## The 15-minute discovery conversation\nWalk through it in order: what to ask, what to listen for, how to present the offer, how to transition from conversation to offer. Feel like a helpful conversation, not a sales call.\n\n## The close message (after they express interest)\n[SCRIPT]\nExact words. Includes price, specific next step, and payment platform.\n[/SCRIPT]\n\n## The 3 objections they'll face\nFor each: the real fear underneath it, and the exact honest response.\n1. Price / "too expensive"\n2. "Not sure it will work for me"\n3. "I need to think about it"\n\n## The Cost-of-Inaction close\n[SCRIPT]\n"If [your offer] saves you from [specific cost of the problem remaining unsolved], is that a fair trade?" — complete this for this specific niche.\n[/SCRIPT]`,

    7:`${ctx}Niche: "${S.niche}". Offer: ${ml} at $${S.price}. Target: $1,000.\n\n14-DAY FIRST DOLLAR SPRINT — day-by-day specifics.\n\n## Pre-scaling conditions check\nBefore this sprint begins, confirm: buyer is clear, offer converts from non-personal contacts, margin survives acquisition, fulfillment is repeatable, churn is tolerable. Which of these is NOT yet proven? What does this sprint need to accomplish to prove it?\n\n## Days 1-2 — Minimal preparation\nMaximum 3 tasks. Goal: outreach starts Day 2 afternoon.\n\n## Days 3-7 — Outreach sprint\nSpecific daily task + daily send target number + who to prioritise.\n\n## Days 8-11 — Convert conversations\nHow to move from interested to paid. What to do if there are zero responses (specific single-axis pivot instruction — which one axis to change).\n\n## Days 12-14 — First delivery and proof\nHow to deliver the first client excellently. Testimonial extraction. How to turn the first client into the second.\n\n## Success gates\nDay 3: [specific measurable gate]\nDay 7: [specific measurable gate]\nDay 11: [gate — should include first revenue]\nDay 14: [gate — the $1,000 confirmation]\n\n## The single-axis pivot if nothing works by Day 11\nIf no conversions by Day 11, which ONE axis to change first: buyer / promise / price / packaging / channel. Not all of them — one.\n\n## After the first $1,000\nThe single biggest mistake, and the right next move instead.`,
  };
  return ps[ph]||'';
}

function md(t){
  if(!t)return'';
  return t
    .replace(/^## (.+)$/gm,'<h2>$1</h2>')
    .replace(/^### (.+)$/gm,'<h3>$1</h3>')
    .replace(/\*\*([^*]+)\*\*/g,'<strong>$1</strong>')
    .replace(/^[*-] (.+)$/gm,'<li>$1</li>')
    .replace(/(<li>.*<\/li>\n?)+/gs,m=>`<ul>${m}</ul>`)
    .replace(/\[SCRIPT\]([\s\S]*?)\[\/SCRIPT\]/g,(_,s)=>`<div class="script-box"><div class="script-label">Script — copy this exactly</div>${s.trim()}</div>`)
    .replace(/^(?!<[hulisd]|<\/[ul])(.+)$/gm,'<p>$1</p>')
    .replace(/<p><\/p>/g,'');
}

async function run(ph){
  if(!S.key){S.err='Add your API key below to generate.';render();return;}
  if(!S.niche.trim()){S.err='Enter your niche first.';render();return;}
  S.loading=true;S.err='';render();
  try{
    S.out[ph]=await callClaude(buildPrompt(ph));
    S.phase=Math.min(ph+1,7);save();
  }catch(e){
    S.err=e.message.includes('401')?'API key invalid — check console.anthropic.com':`Error: ${e.message}`;
  }
  S.loading=false;render();window.scrollTo(0,0);
}

function render(){
  const el=document.getElementById('body');
  const pills=document.getElementById('pills');
  const done=Object.keys(S.out).length;
  document.getElementById('prog').style.width=`${done/7*100}%`;
  document.getElementById('prog-label').textContent=done===7?'All phases complete':'Phase '+(S.phase===0?'0 — Setup':''+S.phase);
  document.getElementById('prog-count').textContent=`${done}/7 phases`;
  pills.innerHTML=PHASES.map(p=>{
    const isDone=p.id>0&&!!S.out[p.id];
    const isActive=p.id===S.phase;
    return `<button class="pill ${isDone?'done':isActive?'active':''}" onclick="goP(${p.id})">${p.l}</button>`;
  }).join('');
  if(!S.key)el.innerHTML=renderKey();
  else if(S.phase===0)el.innerHTML=renderSetup();
  else el.innerHTML=renderStage();
}

function renderKey(){
  return`<div class="phase-num">Setup</div>
<div class="section-head">Enter your Anthropic API key</div>
<div class="section-sub">Stored in browser session only. ~$0.03–0.08 per complete 7-phase run.</div>
${S.err?`<div class="err">${S.err}</div>`:''}
<div class="key-row"><input class="text-in" id="ki" type="password" placeholder="sk-ant-api03-..." style="font-family:var(--mono);font-size:13px"><button class="btn primary" onclick="setK()">Save</button></div>
<div class="key-note">Get a free key at <a href="https://console.anthropic.com" target="_blank">console.anthropic.com</a></div>`;
}

function renderSetup(){
  const EX=['First-time home buyers Phoenix','Corporate burnout recovery','Freelance web design for restaurants','Dog training for reactive dogs','Bookkeeping for ecommerce sellers','Nutrition for busy parents','Real estate investing basics','Excel and data skills'];
  const Q1=[{v:'yes',t:'Yes — directly solved this',s:'I have results and direct experience.'},{v:'some',t:'Some related experience',s:'Adjacent background, not a direct expert.'},{v:'no',t:'Not yet',s:'New to this, willing to learn fast.'}];
  const Q2=[{v:'yes',t:'Comfortable on live calls',s:'Video/phone calls are fine.'},{v:'some',t:'Somewhat comfortable',s:'Can do it, not my preference.'},{v:'no',t:'Prefer async',s:'Rather deliver in writing or via Loom.'}];
  const Q3=[{v:'live',t:'Live delivery is fine',s:'Calls, sessions, workshops — open to it.'},{v:'async',t:'Prefer written/async',s:'Documents, templates, Loom videos.'}];
  const allOK=S.q1&&S.q2&&S.q3&&S.niche.trim();
  const recMvo=getMvo();
  const mvoInfo=MVO_FORMATS[recMvo];
  const recHTML=allOK?`<div class="mvo-rec"><div class="mvo-rec-label">Recommended MVO format based on your answers</div><div class="mvo-rec-title">${mvoInfo.label} · ${mvoInfo.range}</div><div class="mvo-rec-reason">${mvoInfo.reason}</div></div>`:'';
  return`<div class="phase-num">Phase 0 — start here</div>
<div class="section-head">Your niche and how you work</div>
<div class="section-sub">3 quick questions auto-select the right offer format. Your niche powers every phase after this.</div>
${S.err?`<div class="err">${S.err}</div>`:''}
<textarea id="ni" rows="2" placeholder="e.g. I help first-time home buyers in Phoenix win bids against cash investors...">${S.niche}</textarea>
<div style="margin-top:8px;margin-bottom:12px"><div style="font-size:12px;color:var(--muted);margin-bottom:6px">Quick examples:</div>
<div class="ex-chips">${EX.map(e=>`<button class="chip" onclick="useS('${e}')">${e}</button>`).join('')}</div></div>
<div class="q-card"><div class="q-label">Have you personally solved this problem or done this type of work?</div>
<div class="q-opts">${Q1.map(o=>`<div class="q-opt ${S.q1===o.v?'sel':''}" onclick="setQ(1,'${o.v}')"><input type="radio" ${S.q1===o.v?'checked':''}><div><div class="q-opt-text">${o.t}</div><div class="q-opt-sub">${o.s}</div></div></div>`).join('')}</div></div>
<div class="q-card"><div class="q-label">How do you feel about delivering on a live video call?</div>
<div class="q-opts">${Q2.map(o=>`<div class="q-opt ${S.q2===o.v?'sel':''}" onclick="setQ(2,'${o.v}')"><input type="radio" ${S.q2===o.v?'checked':''}><div><div class="q-opt-text">${o.t}</div><div class="q-opt-sub">${o.s}</div></div></div>`).join('')}</div></div>
<div class="q-card"><div class="q-label">How do you prefer to deliver your work?</div>
<div class="q-opts">${Q3.map(o=>`<div class="q-opt ${S.q3===o.v?'sel':''}" onclick="setQ(3,'${o.v}')"><input type="radio" ${S.q3===o.v?'checked':''}><div><div class="q-opt-text">${o.t}</div><div class="q-opt-sub">${o.s}</div></div></div>`).join('')}</div></div>
${recHTML}
<div class="action-row"><button class="btn primary" onclick="startBuild()" ${!allOK?'disabled':''}>Start — Phase 1: Viability Check →</button>
<span class="hint-txt">${allOK?'Ready':'Complete all 3 questions + enter your niche'}</span></div>`;
}

function renderStage(){
  const ph=S.phase;
  const done=!!S.out[ph];
  const platform=PLATFORMS[S.mvo];
  const recPI=0;
  const INFO=[{},{num:'Phase 1',t:'Viability check',s:'The Five Honest Choices + four business model tests — before building anything.',btn:'Run viability check ⚡'},{num:'Phase 2',t:'Skill audit',s:'What you can actually sell right now. The Mechanism Statement. The Sewer Leak.',btn:'Run skill audit ⚡'},{num:'Phase 3',t:'Buyer match',s:'The ideal first buyer, where to find them, the Hot-Hand Signal, the Negative Buyer.',btn:'Find my buyers ⚡'},{num:'Phase 4',t:'Offer design',s:'The Offer Formula, MVO Scoring, 1:10 Value Ratio, platform routing.',btn:'Design my offer ⚡'},{num:'Phase 5',t:'Fulfillment blueprint',s:'What to do after someone pays. The missing phase in most tools.',btn:'Build fulfillment plan ⚡'},{num:'Phase 6',t:'Sale scripts',s:'Word-for-word outreach, close scripts, COI close, objection responses.',btn:'Generate scripts ⚡'},{num:'Phase 7',t:'14-day sprint',s:'Day-by-day with pre-scaling conditions, success gates, and single-axis pivot instruction.',btn:'Build sprint plan ⚡'}][ph]||{};

  const driftBar=ph>=2?`<div class="drift-bar"><div class="drift-label">Structural drift blocklist — do NOT do any of these until Phase 6</div>
<div class="drift-grid"><div class="drift-item">Build a website or landing page</div><div class="drift-item">Design a logo or branding</div><div class="drift-item">Set up automation or CRM</div><div class="drift-item">Create social media accounts</div><div class="drift-item">Write blog posts or create content</div><div class="drift-item">Build email sequences or funnels</div></div></div>`:'';

  const mvoTag=ph>=2?`<div style="display:flex;align-items:center;gap:8px;margin-bottom:14px;flex-wrap:wrap">
<span style="font-size:12px;color:var(--muted)">MVO:</span>
<span style="font-size:12px;padding:3px 10px;background:var(--gold-dim);color:var(--gold);border-radius:20px;font-family:var(--mono)">${MVO_FORMATS[S.mvo]?.label||''} · ${MVO_FORMATS[S.mvo]?.range||''}</span>
<span style="font-size:12px;color:var(--muted)">${S.niche.slice(0,40)}${S.niche.length>40?'…':''}</span></div>`:'';

  const calcHTML=ph===4?`<div style="margin-bottom:14px">
<div style="font-size:12px;color:var(--muted);margin-bottom:8px">What does this problem cost the buyer unsolved? (1:10 value ratio test)</div>
<div class="ratio-row"><span style="font-size:13px;color:var(--muted)">$</span>
<input class="ratio-in" id="unsolved-in" type="number" placeholder="5000" value="${S.unsolved}" oninput="updateUnsolved(this.value)">
${S.unsolved&&S.price?`<div class="ratio-disp" style="color:${Number(S.unsolved)/S.price>=10?'var(--green)':'var(--amber)'}">Ratio: ${Math.round(Number(S.unsolved)/S.price)}:1</div>`:'<div class="ratio-disp" style="color:var(--hint)">Ratio: —</div>'}</div>
<div style="font-size:11px;color:var(--hint)">Target: 10:1 minimum. Aim for 20-30:1. Price should be 1/10th of what the problem costs unsolved.</div>
<div class="four-paths">${FOUR_PATHS.map((p,i)=>`<div class="path-card ${i===0?'rec':''}">
<div class="path-math ${i===0?'rec':''}">${p.math}</div>
<div class="path-detail">${p.clients} clients · ~${p.outreach} outreach · ~${p.days} days</div>
<span class="path-badge ${p.badge==='rec'?'badge-rec':p.badge==='hard'?'badge-hard':'badge-ok'}">${i===0?'recommended':p.badge==='hard'?'avoid':'workable'}</span>
<div style="font-size:11px;color:var(--hint);margin-top:4px">${p.note}</div></div>`).join('')}</div></div>`:'';

  const platformHTML=ph===4&&done?`<div class="platform-box">
<div class="platform-label">Payment platform for your ${MVO_FORMATS[S.mvo]?.label}</div>
<div class="platform-name">${platform?.name}</div>
<div class="platform-setup">${platform?.setup}</div></div>`:'';

  const outHTML=S.loading?`<div class="out-box loading"><div class="spinner"></div><div class="load-txt">Generating ${INFO.t?.toLowerCase()}…</div></div>`:
    done?`<div class="out-box"><div class="out-content">${md(S.out[ph])}</div></div>`:'';

  const nav=`<div class="action-row">
${ph>1?`<button class="btn" onclick="goP(${ph-1})">← Back</button>`:''}
${!done&&!S.loading?`<button class="btn primary" onclick="run(${ph})">${INFO.btn||'Generate ⚡'}</button>`:''}
${done&&ph<7?`<button class="btn primary" onclick="goP(${ph+1})">Next: ${PHASES[ph+1]?.l} →</button>`:''}
${done?`<button class="btn" onclick="run(${ph})">↺ Regenerate</button><button class="btn" onclick="cp(${ph})">Copy</button>`:''}
${done&&ph===7?`<button class="btn" onclick="dlAll()" style="border-color:var(--gold);color:var(--gold)">↓ Download full package</button>`:''}
${S.err?'':`<span class="hint-txt">${S.niche.slice(0,35)}${S.niche.length>35?'…':''}</span>`}</div>`;

  const keyInline=!S.key?`<div class="divider"></div><div class="key-row"><input class="text-in" id="ki2" type="password" placeholder="sk-ant-api03-..." style="font-family:var(--mono);font-size:13px"><button class="btn primary" onclick="setK2()">Save key</button></div><div class="key-note">Get at <a href="https://console.anthropic.com" target="_blank">console.anthropic.com</a></div>`:'';

  return`<div class="phase-num">${INFO.num||''}</div>
<div class="section-head">${INFO.t||''}</div>
<div class="section-sub">${INFO.s||''}</div>
${S.err?`<div class="err">${S.err}</div>`:''}
${driftBar}${mvoTag}${calcHTML}${outHTML}${platformHTML}${nav}${keyInline}`;
}

window.goP=function(p){if(p===0||p<=S.phase){S.phase=p;S.err='';render();}};
window.setK=function(){const v=document.getElementById('ki')?.value.trim();if(v?.startsWith('sk-')){S.key=v;save();render();}else{S.err='Enter a valid key starting with sk-';render();}};
window.setK2=function(){const v=document.getElementById('ki2')?.value.trim();if(v?.startsWith('sk-')){S.key=v;save();render();}else{S.err='Enter a valid key';render();}};
window.useS=function(s){S.niche=s;render();setTimeout(()=>{const t=document.getElementById('ni');if(t)t.value=s;},10);};
window.setQ=function(n,v){S['q'+n]=v;if(S.q1&&S.q2&&S.q3){S.mvo=getMvo();S.price=getMvoPrice(S.mvo);}render();};
window.startBuild=function(){const t=document.getElementById('ni');if(t)S.niche=t.value.trim();if(!S.niche){S.err='Enter your niche first.';render();return;}S.mvo=getMvo();S.price=getMvoPrice(S.mvo);S.phase=1;S.err='';render();};
window.updateUnsolved=function(v){S.unsolved=v;render();};
window.cp=function(ph){if(S.out[ph])navigator.clipboard.writeText(S.out[ph]).catch(()=>{});};
window.dlAll=function(){
  const lines=[`RISER FIRST DOLLAR FORGE v3 — COMPLETE PACKAGE\n${'='.repeat(60)}\nNICHE: ${S.niche}\nMVO: ${MVO_FORMATS[S.mvo]?.label}\nGenerated: ${new Date().toLocaleDateString()}\n`];
  PHASES.forEach(p=>{if(S.out[p.id])lines.push(`\n${'='.repeat(60)}\n${p.l.toUpperCase()}\n${'='.repeat(60)}\n${S.out[p.id]}\n`);});
  const a=Object.assign(document.createElement('a'),{href:URL.createObjectURL(new Blob([lines.join('\n')],{type:'text/plain'})),download:`fdf-${S.niche.slice(0,20).replace(/\s+/g,'-').toLowerCase()}.txt`});a.click();
};
render();
</script>
</body>
</html>

Complete original HTML/CSS/JavaScript — source variant 2, non-executable

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>RISER First Dollar Forge v3</title>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link href="https://fonts.googleapis.com/css2?family=Lora:ital,wght@0,500;0,600;1,400&family=DM+Sans:opsz,[email protected],400;9..40,500&family=DM+Mono:wght@400;500&display=swap" rel="stylesheet">
<style>
:root{--bg:#0C0F14;--panel:#141920;--card:#1C2430;--border:#2A3340;
--gold:#C9A84C;--gold-dim:rgba(201,168,76,.12);--gold-bright:#EAB84C;
--green:#3FB950;--green-dim:rgba(63,185,80,.1);--green-b:rgba(63,185,80,.3);
--amber:#E68A1A;--amber-dim:rgba(230,138,26,.1);
--red:#F85149;--red-dim:rgba(248,81,73,.09);--red-b:rgba(248,81,73,.35);
--info:#58A6FF;--info-dim:rgba(88,166,255,.08);
--purple:#A78BFA;--purple-dim:rgba(167,139,250,.1);
--text:#E6EDF3;--muted:#7D8590;--hint:#4A5568;
--mono:'DM Mono',monospace;--serif:'Lora',serif;--sans:'DM Sans',sans-serif}
*{box-sizing:border-box;margin:0;padding:0}
body{background:var(--bg);color:var(--text);font-family:var(--sans);min-height:100vh;font-size:14px;line-height:1.7}
.app{max-width:800px;margin:0 auto;padding:24px 20px}
.hdr{display:flex;align-items:center;justify-content:space-between;margin-bottom:22px;padding-bottom:14px;border-bottom:.5px solid var(--border)}
.brand{font-family:var(--mono);font-size:11px;letter-spacing:.1em;color:var(--gold)}
.brand span{color:var(--muted)}
.brand sup{font-size:8px;color:var(--amber)}
.pills{display:flex;gap:5px;flex-wrap:wrap}
.pill{font-size:10px;padding:3px 9px;border-radius:20px;border:.5px solid var(--border);color:var(--hint);font-family:var(--mono);cursor:pointer;background:none;transition:all .15s}
.pill.done{background:var(--green-dim);color:var(--green);border-color:var(--green-b)}
.pill.active{border:1px solid var(--gold);color:var(--gold);background:var(--gold-dim)}
.pill:hover:not(.active):not(.done){border-color:var(--muted);color:var(--muted)}
.prog-wrap{margin-bottom:18px}
.prog-bar{height:2px;background:var(--border);border-radius:1px;overflow:hidden}
.prog-fill{height:100%;background:var(--gold);border-radius:1px;transition:width .4s}
.prog-label{font-size:11px;color:var(--muted);font-family:var(--mono);margin-top:5px;display:flex;justify-content:space-between}
.phase-num{font-family:var(--mono);font-size:10px;letter-spacing:.12em;color:var(--muted);margin-bottom:4px;text-transform:uppercase}
.section-head{font-family:var(--serif);font-size:22px;font-weight:500;margin-bottom:4px}
.section-sub{font-size:13px;color:var(--muted);margin-bottom:18px;line-height:1.6}
textarea,.text-in{width:100%;padding:10px 14px;background:var(--card);border:.5px solid var(--border);border-radius:8px;color:var(--text);font-family:var(--sans);font-size:14px;resize:vertical;outline:none;transition:border-color .15s;line-height:1.6}
textarea:focus,.text-in:focus{border-color:var(--gold)}
textarea::placeholder,.text-in::placeholder{color:var(--hint)}
.q-card{background:var(--card);border:.5px solid var(--border);border-radius:10px;padding:16px;margin-bottom:12px}
.q-label{font-size:13px;font-weight:500;margin-bottom:10px}
.q-opts{display:flex;flex-direction:column;gap:6px}
.q-opt{display:flex;align-items:flex-start;gap:9px;padding:8px 10px;border:.5px solid var(--border);border-radius:7px;cursor:pointer;transition:all .15s}
.q-opt:hover{border-color:var(--muted)}
.q-opt.sel{border-color:var(--gold);background:var(--gold-dim)}
.q-opt input[type=radio]{accent-color:var(--gold);margin-top:3px;flex-shrink:0}
.q-opt-text{font-size:13px}
.q-opt-sub{font-size:11px;color:var(--muted);margin-top:1px}
.mvo-rec{background:var(--green-dim);border:1px solid var(--green-b);border-radius:9px;padding:14px 16px;margin-bottom:16px}
.mvo-rec-label{font-family:var(--mono);font-size:9px;color:var(--green);letter-spacing:.12em;text-transform:uppercase;margin-bottom:5px}
.mvo-rec-title{font-size:15px;font-weight:500;color:var(--green);margin-bottom:3px}
.mvo-rec-reason{font-size:12px;color:var(--muted);line-height:1.5}
.five-choices{margin-bottom:14px}
.choice-row{display:flex;gap:8px;padding:9px 12px;border-radius:8px;margin-bottom:5px;border:.5px solid var(--border);background:var(--panel)}
.choice-num{font-family:var(--mono);font-size:15px;font-weight:500;min-width:22px;flex-shrink:0;line-height:1.3}
.choice-title{font-size:12px;font-weight:500;margin-bottom:1px}
.choice-detail{font-size:11px;color:var(--muted)}
.four-paths{display:grid;grid-template-columns:1fr 1fr;gap:8px;margin:12px 0}
.path-card{background:var(--card);border:.5px solid var(--border);border-radius:8px;padding:12px 14px}
.path-card.rec{border:1.5px solid var(--green-b);background:var(--green-dim)}
.path-math{font-family:var(--mono);font-size:16px;font-weight:500;margin-bottom:3px}
.path-math.rec{color:var(--green)}
.path-detail{font-size:11px;color:var(--muted);margin-bottom:3px}
.path-badge{display:inline-block;font-size:10px;padding:2px 7px;border-radius:20px}
.badge-rec{background:var(--green-dim);color:var(--green)}
.badge-hard{background:var(--red-dim);color:var(--red)}
.badge-ok{background:var(--amber-dim);color:var(--amber)}
.ratio-row{display:flex;align-items:center;gap:10px;margin:12px 0}
.ratio-in{flex:1;padding:8px 12px;background:var(--card);border:.5px solid var(--border);border-radius:7px;color:var(--text);font-family:var(--mono);font-size:14px;outline:none;transition:border-color .15s}
.ratio-in:focus{border-color:var(--gold)}
.ratio-disp{font-family:var(--mono);font-size:15px;min-width:80px;text-align:right}
.platform-box{background:var(--card);border:.5px solid var(--border);border-radius:9px;padding:14px 16px;margin:12px 0}
.platform-label{font-family:var(--mono);font-size:9px;color:var(--gold);letter-spacing:.12em;text-transform:uppercase;margin-bottom:10px}
.platform-name{font-size:14px;font-weight:500;color:var(--gold);margin-bottom:3px}
.platform-setup{font-size:12px;color:var(--text);margin-top:6px;padding:8px 10px;background:var(--panel);border-radius:6px}
.drift-bar{background:var(--red-dim);border:.5px solid var(--red-b);border-radius:9px;padding:12px 16px;margin-bottom:18px}
.drift-label{font-family:var(--mono);font-size:9px;color:var(--red);letter-spacing:.12em;text-transform:uppercase;margin-bottom:7px}
.drift-grid{display:grid;grid-template-columns:1fr 1fr;gap:4px}
.drift-item{font-size:12px;color:var(--red);display:flex;align-items:center;gap:6px}
.drift-item::before{content:'✕';font-size:10px;flex-shrink:0}
.ex-chips{display:flex;flex-wrap:wrap;gap:6px;margin-bottom:14px}
.chip{padding:5px 12px;background:var(--card);border:.5px solid var(--border);border-radius:20px;font-size:12px;color:var(--muted);cursor:pointer;transition:all .15s}
.chip:hover{border-color:var(--gold);color:var(--gold)}
.out-box{background:var(--card);border:.5px solid var(--border);border-radius:10px;padding:18px;margin-bottom:14px}
.out-box.loading{display:flex;align-items:center;gap:12px;min-height:60px}
.spinner{width:15px;height:15px;border:1.5px solid var(--border);border-top-color:var(--gold);border-radius:50%;animation:spin .7s linear infinite;flex-shrink:0}
.load-txt{font-size:13px;color:var(--muted)}
.out-content h2{font-family:var(--mono);font-size:10px;color:var(--muted);text-transform:uppercase;letter-spacing:.1em;margin:14px 0 7px;padding-bottom:4px;border-bottom:.5px solid var(--border)}
.out-content h2:first-child{margin-top:0}
.out-content h3{font-size:13px;font-weight:500;color:var(--gold-bright);margin:9px 0 3px}
.out-content p{font-size:13px;margin-bottom:6px}
.out-content ul{padding-left:16px;margin-bottom:8px}
.out-content li{font-size:13px;margin-bottom:3px}
.out-content strong{font-weight:500;color:var(--gold-bright)}
.script-box{background:var(--info-dim);border-left:3px solid var(--info);border-radius:0 8px 8px 0;padding:12px 14px;margin:8px 0}
.script-label{font-family:var(--mono);font-size:10px;color:var(--info);text-transform:uppercase;letter-spacing:.08em;margin-bottom:6px}
.action-row{display:flex;align-items:center;gap:8px;flex-wrap:wrap;margin-top:16px}
.btn{padding:9px 18px;font-size:13px;border-radius:7px;cursor:pointer;transition:all .15s;font-family:var(--sans);border:.5px solid var(--border);background:transparent;color:var(--muted)}
.btn:hover{border-color:var(--muted);color:var(--text)}
.btn:disabled{cursor:not-allowed;opacity:.4}
.btn.primary{background:var(--gold);color:var(--bg);border-color:var(--gold);font-weight:500}
.btn.primary:hover{background:var(--gold-bright)}
.btn.primary:disabled{background:var(--hint);border-color:var(--hint)}
.err{background:var(--red-dim);border:.5px solid var(--red-b);border-radius:7px;padding:10px 14px;font-size:13px;color:var(--red);margin-bottom:14px}
.key-row{display:grid;grid-template-columns:1fr auto;gap:8px;margin-bottom:6px}
.key-note{font-size:12px;color:var(--hint)}
.key-note a{color:var(--muted)}
.divider{height:.5px;background:var(--border);margin:20px 0}
.hint-txt{font-size:12px;color:var(--hint)}
.scaling-grid{display:grid;grid-template-columns:1fr 1fr;gap:8px;margin:10px 0}
.sc-item{background:var(--panel);border-radius:7px;padding:9px 11px;border:.5px solid var(--border)}
.sc-check{width:14px;height:14px;border-radius:50%;background:var(--green-dim);border:.5px solid var(--green-b);display:inline-block;margin-right:6px;vertical-align:middle}
.sc-text{font-size:12px}
@keyframes spin{to{transform:rotate(360deg)}}
::-webkit-scrollbar{width:4px}
::-webkit-scrollbar-thumb{background:var(--border);border-radius:2px}
</style>
</head>
<body>
<div class="app">
<div class="hdr">
  <div class="brand">RISER <span>|</span> First Dollar Forge<sup> v3</sup></div>
  <div class="pills" id="pills"></div>
</div>
<div class="prog-wrap">
  <div class="prog-bar"><div class="prog-fill" id="prog" style="width:0%"></div></div>
  <div class="prog-label"><span id="prog-label">Ready</span><span id="prog-count">0/7 phases</span></div>
</div>
<div id="body"></div>
</div>

<script>
const SYS=`You are the RISER Nation First Dollar Architect v3.

OPERATING LAW:
1. Service before product. Expertise sold directly before building any course.
2. Outreach before inbound. Direct personal contact before any audience exists.
3. Conversation before funnel. A 15-minute call beats a sales page with no social proof.
4. Fewer transactions always. 2 clients at $500 beats 10 clients at $100.
5. Proof before scale. First $1K is proof-gathering, not a business launch.
6. Never automate what you haven't sold manually at least three times.

FIVE HONEST CHOICES for a failing/weak idea (use these when relevant):
1. Kill it — market need is not real
2. Reduce to a feature — too small to stand alone
3. Wrap in a stronger offer — knowledge is real, packaging is wrong
4. Turn into a channel/audience wedge — build audience, monetize differently
5. Use as front-end for affiliate or service revenue

FASTEST $1K PATHS (in order): Audit/review ($200-400) → Strategy call ($150-300) → Mini DFY ($300-500) → Template/toolkit ($97-200)

FOUR BUSINESS MODEL TESTS — flag if idea fails any:
1. Recurring revenue potential
2. Unit economics survive at volume
3. Revenue can grow without proportional founder time
4. Defensible moat exists

PRE-SCALING CONDITIONS (before recommending scale):
Buyer is clear, offer converts from non-personal contacts, margin survives acquisition at volume, fulfillment is repeatable without founder, churn/refunds are tolerable.

NEVER RECOMMEND: building a course first, running paid ads, growing social audience first, building automation before 3 manual sales, website before first payment.

OUTPUT: Specific, concrete, immediately actionable. Write actual scripts. Every output usable today.`;

const PHASES=[
  {id:0,l:'Setup'},
  {id:1,l:'Viability check'},
  {id:2,l:'Skill audit'},
  {id:3,l:'Buyer match'},
  {id:4,l:'Offer design'},
  {id:5,l:'Fulfillment'},
  {id:6,l:'Sale scripts'},
  {id:7,l:'14-day sprint'},
];

const MVO_FORMATS={
  audit:{label:'Audit / Review',range:'$200–400',reason:"You have experience spotting problems. Delivers a concrete written report in 1-3 hours."},
  consult:{label:'Strategy Call',range:'$150–300',reason:"You can think clearly about someone's situation and give direction. Zero build required."},
  dfy:{label:'Mini Done-For-You',range:'$300–500',reason:"You can produce something tangible for the client. Low fulfillment risk."},
  template:{label:'Template / Toolkit',range:'$97–200',reason:"Packaged solution that doesn't require live delivery."},
};

const PLATFORMS={
  audit:{name:'Stripe Payment Links',setup:'dashboard.stripe.com → Products → Payment Links. No website needed. Share the URL directly in DMs and bio.'},
  consult:{name:'Calendly with payment enabled',setup:'Create a Calendly event → enable "Collect Payments" → connect Stripe. Client books and pays in one step.'},
  dfy:{name:'Stripe Payment Links',setup:'Create a Payment Link for your service. After payment, send delivery instructions and intake form by email.'},
  template:{name:'Gumroad',setup:'Free Gumroad account → New Product → Upload template → Set price → Share the link. $0 option for email capture.'},
};

const FOUR_PATHS=[
  {math:'2 × $500',clients:2,price:500,outreach:14,days:'2-5',badge:'rec',note:'Fewest conversations. Worth the harder close.'},
  {math:'4 × $250',clients:4,price:250,outreach:22,days:'3-6',badge:'ok',note:'Sweet spot for most niches.'},
  {math:'10 × $100',clients:10,price:100,outreach:50,days:'5-8',badge:'ok',note:'More closings than it looks.'},
  {math:'20 × $50',clients:20,price:50,outreach:100,days:'10+',badge:'hard',note:'Avoid as first target.'},
];

let S={
  key:sessionStorage.getItem('fdf3_k')||'',
  niche:'',q1:null,q2:null,q3:null,
  mvo:'audit',price:300,unsolved:'',
  phase:0,out:{},loading:false,err:''
};

function getMvo(){
  if(!S.q1||!S.q2||!S.q3)return'audit';
  const exp=S.q1==='yes'||S.q1==='some';
  const live=S.q2==='yes';
  const async_p=S.q3==='async';
  if(exp&&live&&!async_p)return'consult';
  if(exp&&!async_p)return'audit';
  if(exp&&async_p)return'dfy';
  return'template';
}
function getMvoPrice(m){return{audit:300,consult:200,dfy:400,template:150}[m]||250;}

function save(){sessionStorage.setItem('fdf3_k',S.key);}
async function callClaude(prompt){
  const r=await fetch('https://api.anthropic.com/v1/messages',{
    method:'POST',
    headers:{'Content-Type':'application/json','x-api-key':S.key,'anthropic-version':'2023-06-01','anthropic-dangerous-direct-browser-access':'true'},
    body:JSON.stringify({model:'claude-sonnet-4-20250514',max_tokens:1500,system:SYS,messages:[{role:'user',content:prompt}]})
  });
  const d=await r.json();
  if(!r.ok||d.error)throw new Error(d.error?.message||'API error '+r.status);
  return d.content[0].text;
}

function buildPrompt(ph){
  const prev=Object.entries(S.out).filter(([k])=>Number(k)<ph).slice(-2).map(([k,v])=>`[Phase ${k}]:\n${v.slice(0,800)}`).join('\n\n');
  const ctx=prev?`\n\nPrior phases:\n${prev}\n\n`:'';
  const ml=MVO_FORMATS[S.mvo]?.label||'audit';
  const ps={
    1:`Niche/idea: "${S.niche}"\n\nIDEA VIABILITY CHECK — run this before anything else.\n\n## The 5 Honest Choices assessment\nFor this specific idea, which of the 5 Honest Choices applies? Be direct:\n1. Kill it (market need is not real)\n2. Reduce to a feature\n3. Wrap in a stronger offer\n4. Turn into a channel or audience wedge\n5. Use as front-end for affiliate or service revenue\n\nState your verdict clearly: "This idea is most likely Choice [X] because..."\n\n## The 4 Business Model Tests\nFor each test, rate PASS/FAIL with one sentence:\n1. Recurring revenue potential\n2. Unit economics survive at volume\n3. Revenue can grow without proportional founder time\n4. Defensible moat exists\n\n## The fastest $1K path for this idea\nGiven the viability assessment, what is the single fastest path to $1,000 for this specific niche? Name it precisely.\n\n## The one structural risk\nThe most likely failure mode for this specific niche — and the exact mitigation.`,

    2:`${ctx}Niche: "${S.niche}"\nViability verdict: ${S.out[1]?.slice(0,300)||'not run'}\nProfile: ${S.q1==='yes'?'has direct experience':S.q1==='some'?'some related experience':'new to this'}. ${S.q2==='yes'?'Comfortable on live video calls':S.q2==='some'?'Somewhat comfortable live':'Prefers async delivery'}. Recommended MVO: ${ml}.\n\nSKILL AUDIT — complete beginner, no audience.\n\n## What you can deliver for someone today\n5-7 specific deliverables matched to the ${ml} format. Each must be a concrete outcome with a timeframe: "Spend 60 minutes reviewing X and produce a written report with 5 priority improvements within 24 hours." Not vague: "teach people about X."\n\n## Your unfair advantage\nWhat does someone with experience in "${S.niche}" know that took years to learn, that someone would pay to skip?\n\n## Who already needs this in your life right now\n2-3 specific types of people in a typical expert's personal network who have this problem today and could pay.\n\n## The Sewer Leak\nThe #1 hidden problem in "${S.niche}" that existing solutions completely miss.\n\n## The Mechanism Statement\nName WHY the usual approach fails in this niche. Give it a memorable label: "The [Name] Problem." Format: "Most [buyers] fail at [goal] not because of [common assumption] but because of [Mechanism Name] — [one sentence explanation]."`,

    3:`${ctx}Niche: "${S.niche}". MVO: ${ml}.\n\nBUYER MATCH + PAIN FILTER — reach them with no audience.\n\nPain filter first:\nWhich problem costs them TIME? Which costs MONEY? Which creates STRESS? Which have they already tried to solve? Which do they want fixed fastest?\n\n## The ideal first buyer\nSpecific: "a [age] [exact role/situation] who has [specific problem], has already tried [specific approach], and is actively frustrated right now." Give their exact current state.\n\n## The Hot-Hand Signal\n3 specific phrases, situations, or behaviours that mean this person will pay THIS WEEK, not someday.\n\n## Where to find them without an audience\n3 specific places the operator can access TODAY: personal LinkedIn connections, local community groups, online communities by name. No paid traffic.\n\n## The Negative Buyer\nWho looks right but will waste time? The person who asks many questions, never commits, drains energy. How to spot them in the first message.\n\n## The "wrong buyer responded better" watch\nFor this niche, what buyer TYPE might convert better than the intended one? What would that signal about the business model?`,

    4:`${ctx}Niche: "${S.niche}". Format: ${ml}. Price: $${S.price}. Buyer's unsolved problem cost: ${S.unsolved?'$'+S.unsolved:'not specified'}.\n\nOFFER DESIGN — one specific sellable thing.\n\n## THE OFFER FORMULA (mandatory — output this first, exactly)\n"I help [SPECIFIC PERSON] solve [SPECIFIC PAINFUL PROBLEM] by giving them [SMALL CONCRETE RESULT] in [SHORT TIMEFRAME] without [MAJOR FRUSTRATION THEY'VE EXPERIENCED BEFORE]."\n\n## The offer name\n3-7 words. Not clever, not vague. Pattern: [Audience] + [Specific Problem] + [Audit/Sprint/Package].\n\n## Exactly what they receive\nEvery deliverable. Be specific: "A 45-minute Zoom call recorded and sent to them" not "a session."\n\n## How you deliver it (step by step)\nDay-by-day using only: Zoom, Loom, Google Doc, or email. A beginner should be confident delivering this tomorrow.\n\n## MVO SCORING (rate each 1-10 with one-line reason)\n1. Pain intensity: X/10\n2. Urgency: X/10\n3. Offer clarity: X/10\n4. Buyer willingness to pay: X/10\n5. Ease of fulfillment: X/10\n6. Confidence to deliver: X/10\n7. Ease of closing: X/10\n8. Ease of getting testimonials: X/10\n9. Repeatability: X/10\nTOTAL: XX/90 [STRONG PROCEED / PROCEED WITH CAUTION / REFRAME FIRST]\n\n## The 1:10 Value Ratio\n${S.unsolved?`Buyer's cost if unsolved: $${S.unsolved}. Value ratio: ${Math.round(Number(S.unsolved)/S.price)}:1. ${Number(S.unsolved)/S.price>=10?'Strong anchor — defend this price.':'Below 10:1 — either raise the price or identify a more expensive problem.'}`:'State the specific dollar cost to the buyer if this problem remains unsolved for 12 months. Your price should be 1/10th of that number at minimum.'}\n\n## The guarantee\nA specific, beginner-appropriate promise that removes buyer risk.\n\n## NOT included (scope protection)\nList 4-5 things explicitly excluded. This prevents scope creep and protects margin.`,

    5:`${ctx}Niche: "${S.niche}". Offer: ${ml}. Price: $${S.price}.\n\nFULFILLMENT BLUEPRINT — what to do after someone pays.\n\n## Before the first session\nExactly what to prepare: the document, checklist, or template to have ready before delivery.\n\n## The delivery step-by-step\nDay-by-day: what you do first, what you send, what the client experiences. Use only: Zoom, Loom, Google Docs, email. No other tools.\n\n## What a great delivery looks like\nThe specific signals that tell you you've done excellent work — from the client's perspective.\n\n## What can go wrong and how to handle it\nThe 2 most likely delivery problems for a ${ml} in "${S.niche}" and the exact response for each.\n\n## How to make the second delivery faster\nWhat to document, template, or save after the first delivery that makes the second 40% faster.\n\n## The testimonial extraction (send within 48 hours of delivery)\n[SCRIPT]\nThe exact 2-sentence message to send after delivery.\n[/SCRIPT]`,

    6:`${ctx}Niche: "${S.niche}". Offer: ${ml} at $${S.price}.\n\nFIRST SALE SYSTEM — with no audience.\n\nNOTE: Before sending any of these scripts — do NOT build a website, design a logo, set up any automation, or create any content. These scripts work without any of that.\n\n## Warm outreach (personal contacts who know you)\n[SCRIPT]\nUnder 60 words. Conversational, not pitch-y. Ends with one specific yes/no question.\n[/SCRIPT]\n\n## LinkedIn/community outreach (people who don't know you well)\n[SCRIPT]\nUnder 55 words. References something specific about their situation. One request only.\n[/SCRIPT]\n\n## The 15-minute discovery conversation\nWalk through it in order: what to ask, what to listen for, how to present the offer, how to transition from conversation to offer. Feel like a helpful conversation, not a sales call.\n\n## The close message (after they express interest)\n[SCRIPT]\nExact words. Includes price, specific next step, and payment platform.\n[/SCRIPT]\n\n## The 3 objections they'll face\nFor each: the real fear underneath it, and the exact honest response.\n1. Price / "too expensive"\n2. "Not sure it will work for me"\n3. "I need to think about it"\n\n## The Cost-of-Inaction close\n[SCRIPT]\n"If [your offer] saves you from [specific cost of the problem remaining unsolved], is that a fair trade?" — complete this for this specific niche.\n[/SCRIPT]`,

    7:`${ctx}Niche: "${S.niche}". Offer: ${ml} at $${S.price}. Target: $1,000.\n\n14-DAY FIRST DOLLAR SPRINT — day-by-day specifics.\n\n## Pre-scaling conditions check\nBefore this sprint begins, confirm: buyer is clear, offer converts from non-personal contacts, margin survives acquisition, fulfillment is repeatable, churn is tolerable. Which of these is NOT yet proven? What does this sprint need to accomplish to prove it?\n\n## Days 1-2 — Minimal preparation\nMaximum 3 tasks. Goal: outreach starts Day 2 afternoon.\n\n## Days 3-7 — Outreach sprint\nSpecific daily task + daily send target number + who to prioritise.\n\n## Days 8-11 — Convert conversations\nHow to move from interested to paid. What to do if there are zero responses (specific single-axis pivot instruction — which one axis to change).\n\n## Days 12-14 — First delivery and proof\nHow to deliver the first client excellently. Testimonial extraction. How to turn the first client into the second.\n\n## Success gates\nDay 3: [specific measurable gate]\nDay 7: [specific measurable gate]\nDay 11: [gate — should include first revenue]\nDay 14: [gate — the $1,000 confirmation]\n\n## The single-axis pivot if nothing works by Day 11\nIf no conversions by Day 11, which ONE axis to change first: buyer / promise / price / packaging / channel. Not all of them — one.\n\n## After the first $1,000\nThe single biggest mistake, and the right next move instead.`,
  };
  return ps[ph]||'';
}

function md(t){
  if(!t)return'';
  return t
    .replace(/^## (.+)$/gm,'<h2>$1</h2>')
    .replace(/^### (.+)$/gm,'<h3>$1</h3>')
    .replace(/\*\*([^*]+)\*\*/g,'<strong>$1</strong>')
    .replace(/^[*-] (.+)$/gm,'<li>$1</li>')
    .replace(/(<li>.*<\/li>\n?)+/gs,m=>`<ul>${m}</ul>`)
    .replace(/\[SCRIPT\]([\s\S]*?)\[\/SCRIPT\]/g,(_,s)=>`<div class="script-box"><div class="script-label">Script — copy this exactly</div>${s.trim()}</div>`)
    .replace(/^(?!<[hulisd]|<\/[ul])(.+)$/gm,'<p>$1</p>')
    .replace(/<p><\/p>/g,'');
}

async function run(ph){
  if(!S.key){S.err='Add your API key below to generate.';render();return;}
  if(!S.niche.trim()){S.err='Enter your niche first.';render();return;}
  S.loading=true;S.err='';render();
  try{
    S.out[ph]=await callClaude(buildPrompt(ph));
    S.phase=Math.min(ph+1,7);save();
  }catch(e){
    S.err=e.message.includes('401')?'API key invalid — check console.anthropic.com':`Error: ${e.message}`;
  }
  S.loading=false;render();window.scrollTo(0,0);
}

function render(){
  const el=document.getElementById('body');
  const pills=document.getElementById('pills');
  const done=Object.keys(S.out).length;
  document.getElementById('prog').style.width=`${done/7*100}%`;
  document.getElementById('prog-label').textContent=done===7?'All phases complete':'Phase '+(S.phase===0?'0 — Setup':''+S.phase);
  document.getElementById('prog-count').textContent=`${done}/7 phases`;
  pills.innerHTML=PHASES.map(p=>{
    const isDone=p.id>0&&!!S.out[p.id];
    const isActive=p.id===S.phase;
    return `<button class="pill ${isDone?'done':isActive?'active':''}" onclick="goP(${p.id})">${p.l}</button>`;
  }).join('');
  if(!S.key)el.innerHTML=renderKey();
  else if(S.phase===0)el.innerHTML=renderSetup();
  else el.innerHTML=renderStage();
}

function renderKey(){
  return`<div class="phase-num">Setup</div>
<div class="section-head">Enter your Anthropic API key</div>
<div class="section-sub">Stored in browser session only. ~$0.03–0.08 per complete 7-phase run.</div>
${S.err?`<div class="err">${S.err}</div>`:''}
<div class="key-row"><input class="text-in" id="ki" type="password" placeholder="sk-ant-api03-..." style="font-family:var(--mono);font-size:13px"><button class="btn primary" onclick="setK()">Save</button></div>
<div class="key-note">Get a free key at <a href="https://console.anthropic.com" target="_blank">console.anthropic.com</a></div>`;
}

function renderSetup(){
  const EX=['First-time home buyers Phoenix','Corporate burnout recovery','Freelance web design for restaurants','Dog training for reactive dogs','Bookkeeping for ecommerce sellers','Nutrition for busy parents','Real estate investing basics','Excel and data skills'];
  const Q1=[{v:'yes',t:'Yes — directly solved this',s:'I have results and direct experience.'},{v:'some',t:'Some related experience',s:'Adjacent background, not a direct expert.'},{v:'no',t:'Not yet',s:'New to this, willing to learn fast.'}];
  const Q2=[{v:'yes',t:'Comfortable on live calls',s:'Video/phone calls are fine.'},{v:'some',t:'Somewhat comfortable',s:'Can do it, not my preference.'},{v:'no',t:'Prefer async',s:'Rather deliver in writing or via Loom.'}];
  const Q3=[{v:'live',t:'Live delivery is fine',s:'Calls, sessions, workshops — open to it.'},{v:'async',t:'Prefer written/async',s:'Documents, templates, Loom videos.'}];
  const allOK=S.q1&&S.q2&&S.q3&&S.niche.trim();
  const recMvo=getMvo();
  const mvoInfo=MVO_FORMATS[recMvo];
  const recHTML=allOK?`<div class="mvo-rec"><div class="mvo-rec-label">Recommended MVO format based on your answers</div><div class="mvo-rec-title">${mvoInfo.label} · ${mvoInfo.range}</div><div class="mvo-rec-reason">${mvoInfo.reason}</div></div>`:'';
  return`<div class="phase-num">Phase 0 — start here</div>
<div class="section-head">Your niche and how you work</div>
<div class="section-sub">3 quick questions auto-select the right offer format. Your niche powers every phase after this.</div>
${S.err?`<div class="err">${S.err}</div>`:''}
<textarea id="ni" rows="2" placeholder="e.g. I help first-time home buyers in Phoenix win bids against cash investors...">${S.niche}</textarea>
<div style="margin-top:8px;margin-bottom:12px"><div style="font-size:12px;color:var(--muted);margin-bottom:6px">Quick examples:</div>
<div class="ex-chips">${EX.map(e=>`<button class="chip" onclick="useS('${e}')">${e}</button>`).join('')}</div></div>
<div class="q-card"><div class="q-label">Have you personally solved this problem or done this type of work?</div>
<div class="q-opts">${Q1.map(o=>`<div class="q-opt ${S.q1===o.v?'sel':''}" onclick="setQ(1,'${o.v}')"><input type="radio" ${S.q1===o.v?'checked':''}><div><div class="q-opt-text">${o.t}</div><div class="q-opt-sub">${o.s}</div></div></div>`).join('')}</div></div>
<div class="q-card"><div class="q-label">How do you feel about delivering on a live video call?</div>
<div class="q-opts">${Q2.map(o=>`<div class="q-opt ${S.q2===o.v?'sel':''}" onclick="setQ(2,'${o.v}')"><input type="radio" ${S.q2===o.v?'checked':''}><div><div class="q-opt-text">${o.t}</div><div class="q-opt-sub">${o.s}</div></div></div>`).join('')}</div></div>
<div class="q-card"><div class="q-label">How do you prefer to deliver your work?</div>
<div class="q-opts">${Q3.map(o=>`<div class="q-opt ${S.q3===o.v?'sel':''}" onclick="setQ(3,'${o.v}')"><input type="radio" ${S.q3===o.v?'checked':''}><div><div class="q-opt-text">${o.t}</div><div class="q-opt-sub">${o.s}</div></div></div>`).join('')}</div></div>
${recHTML}
<div class="action-row"><button class="btn primary" onclick="startBuild()" ${!allOK?'disabled':''}>Start — Phase 1: Viability Check →</button>
<span class="hint-txt">${allOK?'Ready':'Complete all 3 questions + enter your niche'}</span></div>`;
}

function renderStage(){
  const ph=S.phase;
  const done=!!S.out[ph];
  const platform=PLATFORMS[S.mvo];
  const recPI=0;
  const INFO=[{},{num:'Phase 1',t:'Viability check',s:'The Five Honest Choices + four business model tests — before building anything.',btn:'Run viability check ⚡'},{num:'Phase 2',t:'Skill audit',s:'What you can actually sell right now. The Mechanism Statement. The Sewer Leak.',btn:'Run skill audit ⚡'},{num:'Phase 3',t:'Buyer match',s:'The ideal first buyer, where to find them, the Hot-Hand Signal, the Negative Buyer.',btn:'Find my buyers ⚡'},{num:'Phase 4',t:'Offer design',s:'The Offer Formula, MVO Scoring, 1:10 Value Ratio, platform routing.',btn:'Design my offer ⚡'},{num:'Phase 5',t:'Fulfillment blueprint',s:'What to do after someone pays. The missing phase in most tools.',btn:'Build fulfillment plan ⚡'},{num:'Phase 6',t:'Sale scripts',s:'Word-for-word outreach, close scripts, COI close, objection responses.',btn:'Generate scripts ⚡'},{num:'Phase 7',t:'14-day sprint',s:'Day-by-day with pre-scaling conditions, success gates, and single-axis pivot instruction.',btn:'Build sprint plan ⚡'}][ph]||{};

  const driftBar=ph>=2?`<div class="drift-bar"><div class="drift-label">Structural drift blocklist — do NOT do any of these until Phase 6</div>
<div class="drift-grid"><div class="drift-item">Build a website or landing page</div><div class="drift-item">Design a logo or branding</div><div class="drift-item">Set up automation or CRM</div><div class="drift-item">Create social media accounts</div><div class="drift-item">Write blog posts or create content</div><div class="drift-item">Build email sequences or funnels</div></div></div>`:'';

  const mvoTag=ph>=2?`<div style="display:flex;align-items:center;gap:8px;margin-bottom:14px;flex-wrap:wrap">
<span style="font-size:12px;color:var(--muted)">MVO:</span>
<span style="font-size:12px;padding:3px 10px;background:var(--gold-dim);color:var(--gold);border-radius:20px;font-family:var(--mono)">${MVO_FORMATS[S.mvo]?.label||''} · ${MVO_FORMATS[S.mvo]?.range||''}</span>
<span style="font-size:12px;color:var(--muted)">${S.niche.slice(0,40)}${S.niche.length>40?'…':''}</span></div>`:'';

  const calcHTML=ph===4?`<div style="margin-bottom:14px">
<div style="font-size:12px;color:var(--muted);margin-bottom:8px">What does this problem cost the buyer unsolved? (1:10 value ratio test)</div>
<div class="ratio-row"><span style="font-size:13px;color:var(--muted)">$</span>
<input class="ratio-in" id="unsolved-in" type="number" placeholder="5000" value="${S.unsolved}" oninput="updateUnsolved(this.value)">
${S.unsolved&&S.price?`<div class="ratio-disp" style="color:${Number(S.unsolved)/S.price>=10?'var(--green)':'var(--amber)'}">Ratio: ${Math.round(Number(S.unsolved)/S.price)}:1</div>`:'<div class="ratio-disp" style="color:var(--hint)">Ratio: —</div>'}</div>
<div style="font-size:11px;color:var(--hint)">Target: 10:1 minimum. Aim for 20-30:1. Price should be 1/10th of what the problem costs unsolved.</div>
<div class="four-paths">${FOUR_PATHS.map((p,i)=>`<div class="path-card ${i===0?'rec':''}">
<div class="path-math ${i===0?'rec':''}">${p.math}</div>
<div class="path-detail">${p.clients} clients · ~${p.outreach} outreach · ~${p.days} days</div>
<span class="path-badge ${p.badge==='rec'?'badge-rec':p.badge==='hard'?'badge-hard':'badge-ok'}">${i===0?'recommended':p.badge==='hard'?'avoid':'workable'}</span>
<div style="font-size:11px;color:var(--hint);margin-top:4px">${p.note}</div></div>`).join('')}</div></div>`:'';

  const platformHTML=ph===4&&done?`<div class="platform-box">
<div class="platform-label">Payment platform for your ${MVO_FORMATS[S.mvo]?.label}</div>
<div class="platform-name">${platform?.name}</div>
<div class="platform-setup">${platform?.setup}</div></div>`:'';

  const outHTML=S.loading?`<div class="out-box loading"><div class="spinner"></div><div class="load-txt">Generating ${INFO.t?.toLowerCase()}…</div></div>`:
    done?`<div class="out-box"><div class="out-content">${md(S.out[ph])}</div></div>`:'';

  const nav=`<div class="action-row">
${ph>1?`<button class="btn" onclick="goP(${ph-1})">← Back</button>`:''}
${!done&&!S.loading?`<button class="btn primary" onclick="run(${ph})">${INFO.btn||'Generate ⚡'}</button>`:''}
${done&&ph<7?`<button class="btn primary" onclick="goP(${ph+1})">Next: ${PHASES[ph+1]?.l} →</button>`:''}
${done?`<button class="btn" onclick="run(${ph})">↺ Regenerate</button><button class="btn" onclick="cp(${ph})">Copy</button>`:''}
${done&&ph===7?`<button class="btn" onclick="dlAll()" style="border-color:var(--gold);color:var(--gold)">↓ Download full package</button>`:''}
${S.err?'':`<span class="hint-txt">${S.niche.slice(0,35)}${S.niche.length>35?'…':''}</span>`}</div>`;

  const keyInline=!S.key?`<div class="divider"></div><div class="key-row"><input class="text-in" id="ki2" type="password" placeholder="sk-ant-api03-..." style="font-family:var(--mono);font-size:13px"><button class="btn primary" onclick="setK2()">Save key</button></div><div class="key-note">Get at <a href="https://console.anthropic.com" target="_blank">console.anthropic.com</a></div>`:'';

  return`<div class="phase-num">${INFO.num||''}</div>
<div class="section-head">${INFO.t||''}</div>
<div class="section-sub">${INFO.s||''}</div>
${S.err?`<div class="err">${S.err}</div>`:''}
${driftBar}${mvoTag}${calcHTML}${outHTML}${platformHTML}${nav}${keyInline}`;
}

window.goP=function(p){if(p===0||p<=S.phase){S.phase=p;S.err='';render();}};
window.setK=function(){const v=document.getElementById('ki')?.value.trim();if(v?.startsWith('sk-')){S.key=v;save();render();}else{S.err='Enter a valid key starting with sk-';render();}};
window.setK2=function(){const v=document.getElementById('ki2')?.value.trim();if(v?.startsWith('sk-')){S.key=v;save();render();}else{S.err='Enter a valid key';render();}};
window.useS=function(s){S.niche=s;render();setTimeout(()=>{const t=document.getElementById('ni');if(t)t.value=s;},10);};
window.setQ=function(n,v){S['q'+n]=v;if(S.q1&&S.q2&&S.q3){S.mvo=getMvo();S.price=getMvoPrice(S.mvo);}render();};
window.startBuild=function(){const t=document.getElementById('ni');if(t)S.niche=t.value.trim();if(!S.niche){S.err='Enter your niche first.';render();return;}S.mvo=getMvo();S.price=getMvoPrice(S.mvo);S.phase=1;S.err='';render();};
window.updateUnsolved=function(v){S.unsolved=v;render();};
window.cp=function(ph){if(S.out[ph])navigator.clipboard.writeText(S.out[ph]).catch(()=>{});};
window.dlAll=function(){
  const lines=[`RISER FIRST DOLLAR FORGE v3 — COMPLETE PACKAGE\n${'='.repeat(60)}\nNICHE: ${S.niche}\nMVO: ${MVO_FORMATS[S.mvo]?.label}\nGenerated: ${new Date().toLocaleDateString()}\n`];
  PHASES.forEach(p=>{if(S.out[p.id])lines.push(`\n${'='.repeat(60)}\n${p.l.toUpperCase()}\n${'='.repeat(60)}\n${S.out[p.id]}\n`);});
  const a=Object.assign(document.createElement('a'),{href:URL.createObjectURL(new Blob([lines.join('\n')],{type:'text/plain'})),download:`fdf-${S.niche.slice(0,20).replace(/\s+/g,'-').toLowerCase()}.txt`});a.click();
};
render();
</script>
</body>
</html>

Assigned source documents: riser-first-dollar-forge.html — source 1 ·

First Dollar Forge: earlier version workflow

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

Video placeholder

Record the workflow and version distinctions after confirming the demonstrated tool is appropriate to use.

Lesson outline

Choose a small, accountable first offer
Earlier setup, five formats and price defaults
Read the calculator as a scenario, not a forecast
Skill audit: turn experience into observable deliverables
Buyer match: investigate fit and readiness
Offer design: define scope before persuasion
Sales conversation and scripts: make one relevant request
The twenty-one-day sprint and feedback
Worked offer exercise: make every promise inspectable
Worked writing exercise: messages, discovery and an honest close
Evidence, tools and responsible use

Choose a small, accountable first offer

Supporting sources: riser-first-dollar-forge.html — source variant 1 · Version comparison — riser-first-dollar-forge-v3 (2).html — variant 1 · Version comparison — riser-first-dollar-forge-v3 (2).html — variant 2

Earlier setup, five formats and price defaults

The earlier interface offers four selections: StrategyCall$100–$300, Audit$200–$500, MiniDFY$300–$800 and GroupBeta with three to five people at$100–$300each. Its system prompt also mentions a$500–$1,500VIP day, which is not selectable in that interface. Preserve it as source material rather than promising a fifth button.

After a format is selected, the defaults are consulting$200, audit$300, done-for-you$500 and beta$150. The initial unselected/default state uses consulting$250. These are software defaults, not market prices or recommended fees. Advice still needs a defined outcome, scope and record even though the source calls a strategy call a product with no deliverable.

The earlier version has setup plus five generated phases: skill audit, buyer match, offer, sales scripts and a twenty-one-day sprint. Version3 adds separate viability and fulfillment phases and changes the sprint to fourteen days; the Pricing Architecture document’s six-phase description must not silently replace either version.

Read the calculator as a scenario, not a forecast

The earlier calculator uses customers=ceiling(1000/price). It assumes close rates of30%at prices up to$100,22%up to$300,18%up to$600, and12%above$600. Outreach=ceiling(customers/assumed rate), and days=ceiling(outreach/10). The price slider spans$50–$2,000 in$10steps.

At$250, four customers gross$1,000. Under the code’s22%assumption, it rounds outreach to nineteen and days to two. This does not predict nineteen messages will produce four sales in two days; the assumed denominator, reply/call stages, demand and fulfillment time are missing.

The software flags$150–$600 as its preferred zone, while nearby low-price guidance says$150–$500. These are inconsistent heuristics. For a group beta, separate seats, cohorts, capacity and per-seat price rather than assuming the generic client calculation models delivery. Deduct costs before describing the result as profit.

Supporting sources: riser-first-dollar-forge.html — source variant 1

Skill audit: turn experience into observable deliverables

Buyer match: investigate fit and readiness

Offer design: define scope before persuasion

Sales conversation and scripts: make one relevant request

The twenty-one-day sprint and feedback

Days1–3 define no more than three preparation tasks and propose beginning outreach by day3. Days4–10 specify daily work and a chosen activity target. Days11–14 focus on interested-to-paid decisions and a change if nobody responds. Days15–21 deliver the promise and collect voluntary feedback.

The source asks for measurable gates on days7,14 and21, including a final$1,000 target, plus one appropriate next move after the first sale. Build the gates from real activity and customer evidence. A target is not a guaranteed result and cannot justify exaggerated claims.

Prepare a two-sentence feedback request after delivery. Ask about the experience and permission for any public quotation. Check that improving the next offer is based on actual results rather than immediately building a large course or funnel from one sale.

Supporting sources: riser-first-dollar-forge.html — source variant 1

Worked offer exercise: make every promise inspectable

Worked writing exercise: messages, discovery and an honest close

Evidence, tools and responsible use

Practice and completion check

Complete original HTML/CSS/JavaScript — source variant 1, non-executable

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>RISER First Dollar Forge — First $1,000 MVO Builder</title>
<style>
@import url('https://fonts.googleapis.com/css2?family=Lora:ital,wght@0,500;0,600;1,400&family=DM+Sans:opsz,[email protected],400;9..40,500&family=DM+Mono:wght@400;500&display=swap');
*,*::before,*::after{box-sizing:border-box;margin:0;padding:0}
:root{
  --bg:#0C0F14;--panel:#141920;--card:#1C2430;--border:#2A3340;
  --gold:#C9A84C;--gold-dim:rgba(201,168,76,0.12);--gold-bright:#EAB84C;
  --green:#3FB950;--green-dim:rgba(63,185,80,0.1);
  --amber:#E68A1A;--amber-dim:rgba(230,138,26,0.1);
  --red:#F85149;--red-dim:rgba(248,81,73,0.09);
  --info:#58A6FF;--info-dim:rgba(88,166,255,0.1);
  --text:#E6EDF3;--muted:#7D8590;--hint:#4A5568;
  --mono:'DM Mono',monospace;--serif:'Lora',serif;--sans:'DM Sans',sans-serif;
}
body{background:var(--bg);color:var(--text);font-family:var(--sans);min-height:100vh;font-size:14px;line-height:1.7}
.app{max-width:760px;margin:0 auto;padding:24px 20px}
.header{display:flex;align-items:center;justify-content:space-between;margin-bottom:28px;padding-bottom:16px;border-bottom:0.5px solid var(--border)}
.brand{font-family:var(--mono);font-size:12px;letter-spacing:.1em;color:var(--gold)}
.brand span{color:var(--muted);font-weight:400}
.stage-pills{display:flex;gap:6px;flex-wrap:wrap}
.pill{font-size:11px;padding:3px 10px;border-radius:20px;border:0.5px solid var(--border);color:var(--hint);font-family:var(--mono);cursor:pointer;transition:all .15s;background:none}
.pill.done{background:var(--green-dim);color:var(--green);border-color:rgba(63,185,80,0.3)}
.pill.active{border:1px solid var(--gold);color:var(--gold);background:var(--gold-dim)}
.pill:hover:not(.active):not(.done){border-color:var(--muted);color:var(--muted)}

.phase-num{font-family:var(--mono);font-size:10px;letter-spacing:.12em;color:var(--muted);margin-bottom:4px;text-transform:uppercase}
.section-head{font-family:var(--serif);font-size:22px;font-weight:500;color:var(--text);margin-bottom:4px}
.section-sub{font-size:13px;color:var(--muted);margin-bottom:18px;line-height:1.6}
.section-sub strong{color:var(--text)}

.calc-card{background:var(--card);border:0.5px solid var(--border);border-radius:12px;padding:18px;margin-bottom:20px}
.calc-head{font-family:var(--mono);font-size:10px;color:var(--muted);letter-spacing:.1em;text-transform:uppercase;margin-bottom:10px}
.price-row{display:flex;align-items:center;gap:10px;margin-bottom:12px}
.price-row input[type=range]{flex:1;accent-color:var(--gold)}
.price-display{font-family:var(--mono);font-size:18px;color:var(--gold);min-width:68px;font-weight:500}
.calc-grid{display:grid;grid-template-columns:repeat(3,1fr);gap:10px;margin-bottom:12px}
.calc-metric{background:var(--panel);border-radius:8px;padding:10px 12px}
.calc-metric-label{font-family:var(--mono);font-size:10px;color:var(--muted);margin-bottom:3px;text-transform:uppercase;letter-spacing:.08em}
.calc-metric-value{font-size:22px;font-weight:500}
.calc-metric-value.gold{color:var(--gold)}
.sweet-ok{display:inline-block;font-size:11px;padding:3px 10px;background:var(--green-dim);color:var(--green);border-radius:20px}
.sweet-warn{display:inline-block;font-size:11px;padding:3px 10px;background:var(--amber-dim);color:var(--amber);border-radius:20px}

textarea,.text-input{width:100%;padding:10px 14px;background:var(--card);border:0.5px solid var(--border);border-radius:8px;color:var(--text);font-family:var(--sans);font-size:14px;resize:vertical;outline:none;transition:border-color .15s;line-height:1.6}
textarea:focus,.text-input:focus{border-color:var(--gold);box-shadow:0 0 0 2px var(--gold-dim)}
textarea::placeholder,.text-input::placeholder{color:var(--hint)}

.mvo-grid{display:grid;grid-template-columns:1fr 1fr;gap:10px;margin-bottom:18px}
.mvo-card{border:0.5px solid var(--border);border-radius:10px;padding:14px;cursor:pointer;transition:all .15s;background:var(--card)}
.mvo-card:hover{border-color:var(--muted)}
.mvo-card.sel{border:1.5px solid var(--green);background:var(--green-dim)}
.mvo-title{font-weight:500;font-size:14px;margin-bottom:2px}
.mvo-range{font-family:var(--mono);font-size:12px;color:var(--muted)}
.mvo-when{font-size:12px;color:var(--hint);margin-top:5px;line-height:1.5}
.mvo-card.sel .mvo-title{color:var(--green)}
.mvo-card.sel .mvo-range{color:var(--green)}

.example-chips{display:flex;flex-wrap:wrap;gap:6px;margin-bottom:18px}
.chip-btn{padding:5px 12px;background:var(--card);border:0.5px solid var(--border);border-radius:20px;font-size:12px;color:var(--muted);cursor:pointer;transition:all .15s}
.chip-btn:hover{border-color:var(--gold);color:var(--gold)}

.out-box{background:var(--card);border:0.5px solid var(--border);border-radius:10px;padding:18px;margin-bottom:16px}
.out-box.loading{display:flex;align-items:center;gap:12px;padding:20px}
.spinner{width:16px;height:16px;border:1.5px solid var(--border);border-top-color:var(--gold);border-radius:50%;animation:spin .7s linear infinite;flex-shrink:0}
.loading-txt{font-size:13px;color:var(--muted)}
.out-content h2{font-family:var(--mono);font-size:10px;color:var(--muted);text-transform:uppercase;letter-spacing:.1em;margin:16px 0 8px;padding-bottom:5px;border-bottom:0.5px solid var(--border)}
.out-content h2:first-child{margin-top:0}
.out-content h3{font-size:13px;font-weight:500;color:var(--gold-bright);margin:10px 0 4px}
.out-content p{font-size:13px;margin-bottom:6px}
.out-content ul{padding-left:16px;margin-bottom:8px}
.out-content li{font-size:13px;margin-bottom:3px}
.out-content strong{font-weight:500;color:var(--gold-bright)}
.script-box{background:rgba(88,166,255,0.06);border-left:3px solid var(--info);border-radius:0 8px 8px 0;padding:12px 14px;margin:8px 0}
.script-label{font-family:var(--mono);font-size:10px;color:var(--info);text-transform:uppercase;letter-spacing:.08em;margin-bottom:6px}
.script-box p{color:var(--text)}

.action-row{display:flex;align-items:center;gap:8px;flex-wrap:wrap;margin-top:16px}
.btn{padding:9px 18px;font-size:13px;border-radius:7px;cursor:pointer;transition:all .15s;font-family:var(--sans);border:0.5px solid var(--border);background:transparent;color:var(--muted)}
.btn:hover{border-color:var(--muted);color:var(--text)}
.btn.primary{background:var(--gold);color:var(--bg);border-color:var(--gold);font-weight:500}
.btn.primary:hover{background:var(--gold-bright)}
.btn.primary:disabled{background:var(--hint);border-color:var(--hint);cursor:not-allowed}
.hint{font-size:12px;color:var(--hint)}

.key-row{display:grid;grid-template-columns:1fr auto;gap:8px;margin-bottom:6px;align-items:start}
.key-note{font-size:12px;color:var(--hint);line-height:1.5}
.key-note a{color:var(--muted)}
.err{background:var(--red-dim);border:0.5px solid rgba(248,81,73,0.4);border-radius:7px;padding:10px 14px;font-size:13px;color:var(--red);margin-bottom:14px}
.divider{height:0.5px;background:var(--border);margin:20px 0}
@keyframes spin{to{transform:rotate(360deg)}}
::-webkit-scrollbar{width:4px}
::-webkit-scrollbar-track{background:var(--panel)}
::-webkit-scrollbar-thumb{background:var(--border);border-radius:2px}
</style>
</head>
<body>
<div class="app">
  <div class="header">
    <div class="brand">RISER <span>|</span> First Dollar Forge</div>
    <div class="stage-pills" id="pills"></div>
  </div>
  <div id="body"></div>
</div>
<script>
const SYSTEM=`You are the RISER Nation First Dollar Architect — a specialist helping complete beginners earn their first $1,000 from a knowledge-based offer as fast as possible.

LAW: Service before product. Outreach before inbound. Conversation before funnel. Fewer transactions (2x$500 beats 10x$100). Proof before scale.

FASTEST $1,000 PATHS: (1) Strategy/consulting call $100-300 (2) Audit/review service $200-500 (3) Mini DFY service $300-800 (4) Small group beta 3-5 people x $100-300 (5) VIP intensive day $500-1500.

NEVER RECOMMEND: building a full course, running paid ads, growing social first, building funnels before getting paid.

OUTPUT: Specific, immediate, copy-paste ready. Write actual scripts — not descriptions of scripts.`;

const PHASES=[{id:0,l:'Niche'},{id:1,l:'Skill audit'},{id:2,l:'Buyer match'},{id:3,l:'Offer design'},{id:4,l:'Sale scripts'},{id:5,l:'Sprint plan'}];
const MVO=[{id:'consult',t:'Strategy call',r:'$100–300',w:"Advice is the product. No deliverable."},{id:'audit',t:'Audit / review',r:'$200–500',w:"There's something to assess and improve."},{id:'dfy',t:'Mini done-for-you',r:'$300–800',w:"Produce a tangible result for them."},{id:'beta',t:'Group beta',r:'$100–300 × 3-5',w:"Practice reps + income + testimonials."}];

let S={key:sessionStorage.getItem('fdf_k')||'',niche:'',mvo:'consult',price:250,phase:0,out:{},loading:false,err:''};

function save(){sessionStorage.setItem('fdf_k',S.key);}

async function callClaude(p){
  const r=await fetch('https://api.anthropic.com/v1/messages',{
    method:'POST',headers:{'Content-Type':'application/json','x-api-key':S.key,'anthropic-version':'2023-06-01','anthropic-dangerous-direct-browser-access':'true'},
    body:JSON.stringify({model:'claude-sonnet-4-20250514',max_tokens:1000,system:SYSTEM,messages:[{role:'user',content:p}]})
  });
  const d=await r.json();
  if(!r.ok||d.error)throw new Error(d.error?.message||'API error '+r.status);
  return d.content[0].text;
}

function calc(price){
  const c=Math.ceil(1000/price);
  const rt=price<=100?.30:price<=300?.22:price<=600?.18:.12;
  const o=Math.ceil(c/rt);
  const dy=Math.ceil(o/10);
  const zone=price>=150&&price<=600?'ok':price<150?'low':'high';
  return{c,o,dy,zone};
}

function prompt(ph){
  const prev=Object.entries(S.out).filter(([k])=>Number(k)<ph).map(([k,v])=>`[Phase ${k}]:\n${v}`).join('\n\n');
  const ctx=prev?`\n\nPrior phases:\n${prev}\n\n`:'';
  const ml=MVO.find(m=>m.id===S.mvo)?.t||'strategy call';
  const ps={
    1:`${ctx}Niche: "${S.niche}"\n\nSKILL AUDIT — complete beginner, no audience, no email list, no course.\n\n## What you can do for someone today\n5-7 specific services with concrete outcomes — e.g. "audit someone's X and give them a written 2-page improvement report in 24 hours." Not "teach people about X."\n\n## Your unfair advantage\nWhat does someone in "${S.niche}" know that took years to learn, that another person would pay to skip?\n\n## Who already needs this in your life\n2-3 types of people in a typical "${S.niche}" expert's personal network who have this problem right now and could pay.\n\n## The sewer leak\nThe #1 hidden problem in "${S.niche}" that existing solutions completely miss.\n\n## Quick reality check\nThe biggest honest challenge to the first sale in this niche and exactly how to overcome it.`,
    2:`${ctx}Niche: "${S.niche}". Offer: ${ml} at $${S.price}.\n\nIDEAL FIRST BUYER — reachable without any audience.\n\n## The ideal first buyer profile\nSpecific: "a 38-year-old [role] who has [specific problem] and has already tried [specific thing] and failed." Give their exact situation.\n\n## Where to find them without an audience\n3 specific places TODAY using only personal contacts, LinkedIn, online communities, local networks. No paid traffic.\n\n## The hot-hand signal\n3 specific phrases or situations that mean this person is ready to buy RIGHT NOW — not someday.\n\n## The negative buyer (filter these out)\nWho should this beginner avoid? The person who looks right but won't convert.`,
    3:`${ctx}Niche: "${S.niche}". Format: ${ml}. Price: $${S.price}.\n\nEXACT FIRST OFFER — one specific sellable thing.\n\n## The offer name\nClear 3-7 word title. Not clever. Not vague.\n\n## The one-sentence promise\n"In [timeframe], I'll help you [specific result] so that [meaningful outcome]."\n\n## Exactly what they receive\nEvery deliverable. Be specific: "A 45-minute Zoom call" not "a session."\n\n## How you deliver it\nDay-by-day delivery process. A beginner should be able to do this tomorrow.\n\n## The guarantee\nA specific beginner-appropriate promise that removes buyer risk.\n\n## Why $${S.price} is right\nTwo sentences from the buyer's value perspective.`,
    4:`${ctx}Niche: "${S.niche}". Offer: ${ml} at $${S.price}.\n\nFIRST SALE SYSTEM — for someone with no audience reaching out directly.\n\n## Warm outreach message (personal contacts)\n[SCRIPT]Write the exact message. Under 60 words. No hype. Ends with a specific yes/no question.[/SCRIPT]\n\n## Cold LinkedIn/community message\n[SCRIPT]Under 50 words. References something specific about them. One ask only.[/SCRIPT]\n\n## 15-minute discovery call structure\nQuestions to ask in order, what to listen for, and exactly how to present the offer at the end.\n\n## Close message (when they say yes)\n[SCRIPT]Exact words. Includes price, specific next step, and payment method mention.[/SCRIPT]\n\n## Top 3 objections and exact responses\nThe real fear underneath each objection, and the honest response that addresses it.`,
    5:`${ctx}Niche: "${S.niche}". Offer: ${ml} at $${S.price}. Target: $1,000.\n\n21-DAY FIRST DOLLAR SPRINT.\n\n## Days 1-3 — Foundation\nMaximum 3 things to prepare. Goal: outreach starts by Day 3.\n\n## Days 4-10 — Outreach sprint\nSpecific daily tasks with a daily send target number.\n\n## Days 11-14 — Conversion week\nHow to move from interested to paid. What to do if nobody has responded.\n\n## Days 15-21 — First delivery and proof\nHow to deliver excellently and extract a testimonial immediately.\n\n## Success gates\nDay 7: [specific measurable gate] Day 14: [gate] Day 21: [$1,000 confirmation gate]\n\n## After the first $1,000\nThe most common mistake after the first sale, and the right next move.\n\n## Testimonial extraction message\n[SCRIPT]Exact 2-sentence message to send after delivery.[/SCRIPT]`
  };
  return ps[ph]||'';
}

function md(t){
  if(!t)return'';
  return t
    .replace(/^## (.+)$/gm,'<h2>$1</h2>')
    .replace(/^### (.+)$/gm,'<h3>$1</h3>')
    .replace(/\*\*([^*]+)\*\*/g,'<strong>$1</strong>')
    .replace(/^- (.+)$/gm,'<li>$1</li>')
    .replace(/(<li>.*<\/li>\n?)+/gs,m=>`<ul>${m}<\/ul>`)
    .replace(/\[SCRIPT\]([\s\S]*?)\[\/SCRIPT\]/g,(_,s)=>`<div class="script-box"><div class="script-label">Script — copy this exactly<\/div>${s.trim()}<\/div>`)
    .replace(/^(?!<[hulisd]|<\/[ul])(.+)$/gm,'<p>$1<\/p>')
    .replace(/<p><\/p>/g,'');
}

async function run(ph){
  if(!S.key){S.err='Add your API key to generate.';render();return;}
  if(!S.niche.trim()){S.err='Enter your niche first.';render();return;}
  S.loading=true;S.err='';render();
  try{
    S.out[ph]=await callClaude(prompt(ph));
    S.phase=Math.min(ph+1,5);
    save();
  }catch(e){
    S.err=e.message.includes('401')?'API key invalid — check console.anthropic.com':`Error: ${e.message}`;
  }
  S.loading=false;render();
  window.scrollTo(0,0);
}

function render(){
  const el=document.getElementById('body');
  const pills=document.getElementById('pills');
  pills.innerHTML=PHASES.map(p=>{
    const done=p.id>0&&!!S.out[p.id];
    const active=p.id===S.phase;
    return `<button class="pill ${done?'done':active?'active':''}" onclick="goP(${p.id})">${p.l}</button>`;
  }).join('');
  if(!S.key)el.innerHTML=renderKey();
  else if(S.phase===0)el.innerHTML=renderNiche();
  else el.innerHTML=renderStage();
}

function renderKey(){
  return`<div class="phase-num">Setup</div>
<div class="section-head">Enter your Anthropic API key</div>
<div class="section-sub">The tool uses Claude to build your personalised first-dollar blueprint. Your key is stored in your browser session only.</div>
${S.err?`<div class="err">${S.err}</div>`:''}
<div class="key-row"><input class="text-input" id="ki" type="password" placeholder="sk-ant-api03-..." style="font-size:13px;font-family:var(--mono)"><button class="btn primary" onclick="setK()">Save</button></div>
<div class="key-note">Get a free key at <a href="https://console.anthropic.com" target="_blank">console.anthropic.com</a> &nbsp;·&nbsp; ~$0.02–0.05 per full 5-phase run</div>`;
}

function renderNiche(){
  const EX=['First-time home buyer guidance','Corporate wellness coaching','Freelance web design','Dog training','Bookkeeping for small business','Nutrition for busy parents','Real estate investing basics','Excel and data skills'];
  return`<div class="phase-num">Phase 0 — start here</div>
<div class="section-head">What's your niche or expertise?</div>
<div class="section-sub">One sentence is enough. Describe what you know, do, or have experience with. You don't need to have a polished answer — just describe it honestly.</div>
${S.err?`<div class="err">${S.err}</div>`:''}
<textarea id="ni" rows="3" placeholder="e.g. I've been a freelance graphic designer for 3 years and I'm good at brand identity and Canva...">${S.niche}</textarea>
<div class="section-sub" style="margin-top:12px;margin-bottom:8px">Or start with one of these:</div>
<div class="example-chips">${EX.map(e=>`<button class="chip-btn" onclick="useS('${e}')">${e}</button>`).join('')}</div>
<div class="action-row">
  <button class="btn primary" onclick="go()">Start building my MVO →</button>
  <span class="hint">5 phases · ~5 min total</span>
</div>`;
}

function renderStage(){
  const ph=S.phase;
  const done=!!S.out[ph];
  const {c,o,dy,zone}=calc(S.price);
  const INFO=[{},{num:'Phase 1',t:'Skill audit',s:'What you can actually sell right now — before any audience, course, or funnel.',btn:'Run skill audit ⚡'},{num:'Phase 2',t:'Buyer match',s:'Who needs this today, can pay, and is already within your reach.',btn:'Find my buyers ⚡'},{num:'Phase 3',t:'Offer design',s:'Your exact first offer — format, price, promise, deliverables, and delivery.',btn:'Design my offer ⚡'},{num:'Phase 4',t:'First sale scripts',s:'The exact messages and conversation structure to close your first client.',btn:'Generate scripts ⚡'},{num:'Phase 5',t:'21-day sprint',s:'Day-by-day actions from today to your first $1,000 in hand.',btn:'Build sprint plan ⚡'}][ph]||{};
  const calcHTML=ph>=3?`<div class="calc-card">
    <div class="calc-head">$1,000 calculator — drag to adjust your price</div>
    <div class="price-row"><input type="range" min="50" max="2000" step="10" value="${S.price}" id="ps" oninput="upP(this.value)"><span class="price-display" id="pd">$${S.price}</span></div>
    <div class="calc-grid">
      <div class="calc-metric"><div class="calc-metric-label">Clients needed</div><div class="calc-metric-value gold" id="cc">${c}</div></div>
      <div class="calc-metric"><div class="calc-metric-label">Outreach needed</div><div class="calc-metric-value" id="co">${o}</div></div>
      <div class="calc-metric"><div class="calc-metric-label">Days at 10/day</div><div class="calc-metric-value" id="cd">${dy}</div></div>
    </div>
    <span class="${zone==='ok'?'sweet-ok':'sweet-warn'}" id="cz">${zone==='ok'?'Sweet spot for first $1,000':S.price<150?'Many transactions — consider $150-500':'High-ticket — harder for beginners to close'}</span>
  </div>`:'';
  const mvoHTML=ph===3&&!done?`<div class="mvo-grid">${MVO.map(m=>`<div class="mvo-card ${S.mvo===m.id?'sel':''}" onclick="setM('${m.id}')"><div class="mvo-title">${m.t}</div><div class="mvo-range">${m.r}</div><div class="mvo-when">${m.w}</div></div>`).join('')}</div>`:'';
  const outHTML=S.loading?`<div class="out-box loading"><div class="spinner"></div><div class="loading-txt">Generating your personalised ${INFO.t?.toLowerCase()}…</div></div>`:
    done?`<div class="out-box"><div class="out-content">${md(S.out[ph])}</div></div>`:'';
  const nav=`<div class="action-row">
    ${ph>1?`<button class="btn" onclick="goP(${ph-1})">← Back</button>`:''}
    ${!done&&!S.loading?`<button class="btn primary" onclick="run(${ph})">${INFO.btn||'Generate ⚡'}</button>`:''}
    ${done&&ph<5?`<button class="btn primary" onclick="goP(${ph+1})">Next: ${PHASES[ph+1]?.l} →</button>`:''}
    ${done?`<button class="btn" onclick="run(${ph})">↺ Regenerate</button>`:''}
    ${done?`<button class="btn" onclick="cp(${ph})">Copy</button>`:''}
    ${S.err?'':`<span class="hint">${S.niche.slice(0,40)}${S.niche.length>40?'…':''}</span>`}
  </div>`;
  const keyInline=!S.key?`<div class="divider"></div><div class="key-row"><input class="text-input" id="ki2" type="password" placeholder="sk-ant-api03-..." style="font-size:13px;font-family:var(--mono)"><button class="btn primary" onclick="setK2()">Save key</button></div><div class="key-note" style="margin-top:4px">Need a key? <a href="https://console.anthropic.com" target="_blank">console.anthropic.com</a></div>`:'';
  return`<div class="phase-num">${INFO.num||''}</div>
<div class="section-head">${INFO.t||''}</div>
<div class="section-sub">${INFO.s||''}</div>
${S.err?`<div class="err">${S.err}</div>`:''}
${calcHTML}${mvoHTML}${outHTML}${nav}${keyInline}`;
}

window.goP=function(p){if(p===0||p<=S.phase){S.phase=p;S.err='';render();}};
window.setK=function(){const v=document.getElementById('ki')?.value.trim();if(v?.startsWith('sk-')){S.key=v;save();render();}else{S.err='Enter a valid key starting with sk-';render();}};
window.setK2=function(){const v=document.getElementById('ki2')?.value.trim();if(v?.startsWith('sk-')){S.key=v;save();render();}else{S.err='Enter a valid key starting with sk-';render();}};
window.useS=function(s){S.niche=s;render();setTimeout(()=>{const t=document.getElementById('ni');if(t)t.value=s;},10);};
window.go=function(){const t=document.getElementById('ni');if(t)S.niche=t.value.trim();if(!S.niche){S.err='Enter your niche first.';render();return;}S.phase=1;S.err='';render();};
window.setM=function(id){S.mvo=id;const p={consult:200,audit:300,dfy:500,beta:150}[id]||250;S.price=p;render();};
window.upP=function(v){S.price=Number(v);const{c,o,dy,zone}=calc(S.price);document.getElementById('pd').textContent='$'+S.price;document.getElementById('cc').textContent=c;document.getElementById('co').textContent=o;document.getElementById('cd').textContent=dy;const z=document.getElementById('cz');if(z){z.className=zone==='ok'?'sweet-ok':'sweet-warn';z.textContent=zone==='ok'?'Sweet spot for first $1,000':S.price<150?'Many transactions — consider $150-500':'High-ticket — harder for beginners to close';}};
window.cp=function(ph){if(S.out[ph])navigator.clipboard.writeText(S.out[ph]).catch(()=>{});};
render();
</script>
</body>
</html>

Assigned source documents: RISER-Funnel-Hacking-Methodology-SOP.docx — source 1 ·

Funnel research: turn observations into original, testable improvements

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

Video placeholder

Record the lesson using the section scripts below, with a worked report and clearly labeled evidence limits.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

Curriculum outline

Study a decision process and produce an original test
Choose comparable funnels and record uncertainty
Use a tool for a defined observation
Map legitimate access and the observed email window
Stage 1: connect the ad hook to a testable entry hypothesis
Stage 2: explain the first conversion ask
Stage 3: inspect checkout, registration and qualification
Stage 4: evaluate the next problem offered after purchase
Stage 5: reconstruct the sales argument
Stage 6: evaluate proof specificity and placement
Stage 7: explain the observed email progression
Stage 8: extract structures without inventing customer testimony
Stage 9: compare offer scope and delivery burden
Stage 10: distinguish distribution evidence from speculation
Move from surface to structure to a qualified principle
Complete the ten-part report with evidence boundaries
Synthesize comparisons without overstating confidence
Maintain a dated research cadence
Apply originality and provenance checks
Keep both schemas traceable to evidence
Run the complete setup and session checklist
Explain each copy-pattern family as a decision hypothesis
Complete report fields with explicit units and provenance
Maintain schema types, history and meaningful blanks

1. Study a decision process and produce an original test

Funnel research begins with a buyer decision: what must the buyer understand, believe or do to move forward? Record what is actually visible, propose why it might matter, then design an original implementation and a measurable test. Keep those three layers separate. A screenshot is an observation; a conversion explanation is a hypothesis until supported by performance evidence.

Use the source’s extraction-versus-replication standard to check your work. Ask whether it preserves original authorship, whether it improves your own offer and whether you can explain the research process transparently. These are review questions, not legal clearance. The source attributes principles to Kennedy and Brunson without pinpoint citations; treat those passages as source attributions rather than independently verified quotations.

The Brunson connection is studying the sequence from attention through offer and next step. The Hormozi connection is evaluating the promised outcome, confidence, delay and effort at each decision. RISER’s application is to document the evidence behind each proposed improvement and test it against actual buyer response. Research should produce a better decision, not a collection of copied pages.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

Original source table 1 — includes source claims qualified above

The Extraction vs Replication StandardThe test for every insight extracted from a funnel hack:Legal: Would the operator whose funnel you are studying be able to recognise their specific words, images, or assets in your output? If yes: replication.Strategic: Are you deploying the underlying principle that made their approach work, or the surface-level execution of that principle? If surface-level: replication.Ethical: Would you be comfortable if the operator whose funnel you studied read your output? If not: replication.All funnel hacking work in the RISER Nation system operates by extraction only. No template, copy, image, or asset is ever used verbatim from a competitor's funnel.

Original source table 2 — includes source claims qualified above

Kennedy's Competitive Intelligence PrincipleThe best competitive research is not the most secret. It is the most systematic. Every operator in your category is running ads, publishing content, building funnels, and sending emails. The question is not whether to look — it is whether to look with a framework that extracts generalisable intelligence or to look without one and see only surface features.

Original source table 3 — includes source claims qualified above

Brunson's Funnel Hacking InsightMost operators look at a competitor's funnel and say 'I could have done that.' A funnel hacker looks at the same funnel and asks: 'Why does this work? What problem in the buyer's decision-making process does each element solve? What would be different about the conversion rate if any one element were removed?' The answers to those questions are the intelligence. The surface elements are just the evidence.

2. Choose comparable funnels and record uncertainty

Screen targets on five dimensions: visible paid-traffic activity, at least 90 days of apparent operation, revenue signals, overlap with the intended avatar and a comparable price point. For each, record the standard, evidence, date and unresolved uncertainty using the original criteria table below. A team, testimonials, large audience or persistent advertising can justify investigating a business; none establishes profitable unit economics.

Archived captures establish that a page was captured on a date, not its launch date. Public revenue claims remain claims unless supported. A comparable price without comparable delivery scope is a weak match. Record audience awareness and warm-versus-cold traffic because these can explain differences in the required persuasion.

The source screens out organic-only funnels while also encouraging adjacent-category research. Keep those as separate comparison groups. Organic distribution is not inherently uninformative; it answers a different question. Choose a target because it can illuminate a stated research question, and label exclusions instead of silently selecting only examples that support your preferred answer.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Psychographic-DNA-SOP.docx · RISER-Negative-Avatar-Modelling-SOP.docx

Original source table 4 — includes source claims qualified above

Criterion	Standard	How to Confirm	Disqualifier
Evidence of significant paid traffic	The operator is running paid ads (Meta, Google, YouTube, TikTok) to the funnel at scale. Paid traffic at scale almost always indicates positive unit economics — meaning the funnel is working well enough to justify ongoing spend.	Facebook Ads Library: search the operator's page name for active ads. Google: search '[operator name] ads.' AdSpy, SpyFu, or SimilarWeb for estimated traffic volumes. Active ads running for 30+ days = significant paid traffic.	Funnel receives traffic exclusively from organic audience (existing email list, large social following). This type of funnel performs because of the audience, not the architecture — extracting copy patterns from it will produce misleading results.
Funnel has been running for at least 90 days	A funnel that has been live for fewer than 90 days may not have been optimised against real conversion data. A 12–36 month-old funnel represents tested, iterated architecture.	Check the Wayback Machine (web.archive.org) for the first cached version of the funnel URL. Facebook Ads Library shows the earliest date each ad was active.	Newly launched funnel. The copy and architecture may not yet reflect the operator's learnings from live conversion data. Flag for review in 90 days rather than hacking now.
Operator is generating meaningful revenue	A funnel from an operator who is not generating significant revenue from that funnel is not a useful intelligence source. The goal is to study systems that work at scale.	Social proof signals: large testimonial counts, public case studies, community size, team size indicators on LinkedIn, SimilarWeb traffic estimates. Kennedy's signal: operators who are still running the same funnel after 12 months are making money from it.	Operator with a small, newly built audience and a new funnel. Limited data about what is converting vs what was simply built first.
Operator is selling to your target avatar	The intelligence is only transferable if the funnel's target buyer overlaps significantly with your own. A funnel designed for B2C lifestyle buyers uses different copy patterns and different psychology than one designed for B2B operators.	Read the funnel's headline, the problem section, and the 'who this is for' section. Does the avatar description match your own? Is the problem section describing the same pain you are addressing?	Avatar mismatch. If the operator targets a fundamentally different audience (different industry, different sophistication level, different decision-making context), the psychological patterns may not transfer.
Funnel is at a comparable or higher price point	Copy patterns, guarantee architecture, and social proof density differ significantly between a $47 SLO and a $5,000 high-ticket programme. Hacking a $47 funnel to improve a $5,000 programme (or vice versa) produces mismatched insights.	The funnel's price point is usually visible on the checkout page or in the sales copy. If not: check the OTO pages.	Significant price mismatch. Insights from a $97 funnel are not directly applicable to a $3,000 funnel — and vice versa. Note the price tier and only apply insights within the same price psychology category.

3. Use a tool for a defined observation

The seven source tool groups are Meta Ads Library for visible advertising, Wayback for archived pages, AdSpy or Anstrex for ad discovery, Similarweb for traffic estimates, Google Ads Transparency for ad research, Hunter or MailTester and email headers for mail clues, and the operator’s public content for positioning and distribution. The table preserves the source’s proposed capture fields and workflow. Product access, coverage and paid features still require current verification before a tool demonstration.

Keep the URL, capture date, tool and evidence type with each observation. An estimated traffic channel is not actual spend or email-list size. More creative variations do not prove increased spend. An MX record primarily describes mail handling, not necessarily the marketing automation platform. Identifiable email headers or footers can be stronger clues, but still need contextual interpretation.

Use unavailable or unknown when access is missing. Do not fill empty fields with invented estimates. A tool screenshot can establish what the tool displayed, not the truth of every underlying inference. Preserve historical captures separately so a later page change does not erase the record you used.

The source proposes searching an operator’s page and filtering by country in the Meta library, comparing earliest available and current Wayback captures, searching category keywords and the prior ninety days in paid discovery tools, and recording traffic sources, referring sites and geography in traffic estimates. In Google’s transparency resource it proposes an advertiser search and capturing visible headlines, descriptions and destination pages. These are source workflow descriptions; verify current interfaces, export options and archive coverage before demonstrating them.

For public content, the source suggests the latest two or three podcast appearances and thirty days of social observation, recording mechanism language, teaching stories, proof metrics and descriptions of the audience. Public case studies and interviews reveal what the operator says, not privileged access to performance. Subscription or follow actions are optional research choices, not prerequisites for this lesson. Keeping an analysis mailbox separate helps organize messages; receiving competitor email does not by itself establish an effect on your outbound sender reputation.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

Original source table 5 — includes source claims qualified above

Tool	Purpose	What It Surfaces	How to Use It
Facebook Ads Library (free)	Reveals every active and historical ad running from a specific Facebook page. Includes creative, copy, and — in some cases — targeting indicators.	Ad creative format (video vs image vs carousel), headline patterns, offer types (lead magnet, challenge, webinar, SLO, application), how long each ad has been running.	Search the operator's Facebook page name at facebook.com/ads/library. Filter by country. Sort by date to see which ads have been running longest (= most successful). Download screenshots of all active ads.
Wayback Machine (free)	Archives historical versions of web pages at web.archive.org. Shows how funnel pages have evolved over time.	Which elements have been added, removed, or changed. The original headline vs the current one (which is probably better — the current headline survived testing). Price changes. Offer additions.	Enter the funnel's URL into web.archive.org. Review the earliest cached version vs the current version. Changes made over 12+ months of operation represent tested optimisations.
AdSpy / Anstrex (paid)	Cross-platform ad intelligence tools that surface ads from multiple networks with engagement data.	Ad performance signals (likes, shares, saves), how long an ad has been running, which landing page it links to, targeting demographic indicators (where available).	Filter by your category keywords. Sort by run length (longest-running = most successful). Export the top-performing ads from the past 90 days.
SimilarWeb (freemium)	Estimates website traffic volume, traffic source breakdown, and top referring sites for any domain.	Whether paid or organic traffic is the primary source. Which ad platforms are driving traffic. Geographic distribution. Monthly visitor estimates.	Enter the funnel domain. Review: Traffic Sources section (paid vs organic vs direct vs referral), Top Referring Sites (other operators sending them traffic = JV relationships), and Traffic by Country.
Google Transparency Report (free)	Google's equivalent of the Facebook Ads Library for Google Search and Display ads.	Active Google ads including headlines, descriptions, and landing pages.	Search at adstransparency.google.com. Filter by advertiser. Export the currently active Google ads.
Hunter.io / MailTester (freemium)	Identifies the email platform a domain is using and, in some cases, email formats.	Which email platform the operator uses (Klaviyo, ActiveCampaign, ConvertKit, etc.), which signals likely email sophistication and automation capability.	Enter the domain. Review the MX records and email headers (visible in forwarded emails from opt-ins to the funnel).
The Operator's Own Content (free)	The operator's podcast appearances, YouTube channel, published case studies, and social media content reveal their messaging framework, proof points, and positioning — often more candidly than their funnel copy.	Mechanism language, parable subjects, proof metrics they share publicly, interview language about their avatar and their method.	Subscribe to their YouTube channel, listen to their most recent 2–3 podcast appearances, follow their primary social media account for 30 days before conducting the analysis.

4. Map legitimate access and the observed email window

The source proposes a dedicated analysis address, entry-page capture, an opt-in or purchase path, and 30 days of email observation. Its low-price purchase suggestion is $47 or less; its high-ticket flow stops at application confirmation rather than booking a call. These are source research options, not required actions for this lesson. Use only access you legitimately have, and do not create false applications or disrupt another operator’s work.

Record form fields and their order, required versus optional answers, headline, bullets, proof, redirect, every legitimately accessible page URL, order bump, upsell, thank-you page and delivery mechanism. A subscriber path and a buyer path can differ. Mark a payment-gated or otherwise unavailable branch as unobserved instead of calling the map complete.

For each received email, record subject, timestamp relative to entry, content purpose, format and CTA. Distinguish education, proof, mechanism, story, offer, urgency and re-engagement. Thirty days defines an observation window, not the complete lifecycle: segmentation, behavior triggers and later messages may remain unknown.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Email-Fundamentals-SOP.docx

Original source table 6 — includes source claims qualified above

The Analysis Email AddressCreate a dedicated email address for all funnel hacking opt-ins: e.g., [yourbrand]-analysis@[yourdomain].com. All competitor opt-ins go to this address. Never use your primary business email — you want all analysis emails segmented separately from your business communications, and you do not want competitor email sequences to interfere with your deliverability metrics.

Original source table 7 — includes source claims qualified above

Step	Action	What to Capture
1. Opt in to the lead magnet or register for the free product	Use the analysis email address. Complete the opt-in form as a real prospect would. Note: form fields (what data is collected), social proof elements on the opt-in page, and the redirect destination.	Form field count and type. Opt-in page elements (headline, subheadline, bullet points, social proof). Redirect destination (sales page or thank-you page with OTO).
2. Go through the full funnel sequence	For a free funnel: opt in only. For an SLO or low-price funnel: purchase the entry product. For a high-ticket funnel: submit the application (do not book a discovery call — stop at the confirmation page). Complete every page you legitimately reach.	Every page URL. Every page's copy (screenshotted). Every order bump and OTO (screenshotted). Thank-you page and delivery mechanism.
3. Document the complete email sequence	Over the next 30 days: open every email from the operator to the analysis address. Screenshot every email. Note: subject lines, send timing, sequence structure, and CTA evolution across the sequence.	Subject lines (verbatim). Send timing (day-by-day or week-by-week). Content type per email (value, proof, mechanism, offer, urgency). CTA language. Email platform indicators (check the unsubscribe footer for ESP identification).
4. Purchase the SLO if one exists	If the funnel includes an SLO at $47 or below: purchase it. This is the most complete way to access the full funnel including all upsells, the thank-you page, and the buyer email sequence (which is different from the subscriber sequence).	Every upsell page. The order bump. The thank-you page delivery. The buyer onboarding sequence (different from the subscriber sequence — captures the full post-purchase architecture).

5. Stage 1: connect the ad hook to a testable entry hypothesis

Capture visible static, video and carousel creatives, headline, primary text, button label and dates. For video, separate the opening hook, explanation and CTA. Classify the appeal as acute pain, desire, curiosity, counterintuitive claim or proof. Describe likely avatar cues as an inference unless actual targeting data is available.

Ask what makes the promise understandable and relevant before the click. Then propose an original creative that tests the hook category with your own evidence and voice. The longest-running creative may be worth studying; its tenure does not prove it is the most successful, and library visibility does not reveal conversion rate or profit.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Hook-Engineering-Attention-Engineering-SOP.docx · RISER-Creative-Brief-Template-SOP (1).docx

Original source table 8 — includes source claims qualified above

ANALYSIS STAGE 1Ad Creative AnalysisCentral question: What entry message is this funnel using to stop the scroll and generate a click?

What to captureEvery active ad creative: screenshots of static images, notes on video content (hook, body, CTA), carousel structure. Ad copy: headline, primary text, CTA button label. Targeting signals: which audiences does each ad appear in (interest-based, lookalike, broad)? Run length of each creative.

What it revealsThe entry hook — what specific pain, desire, or curiosity the operator is using to generate traffic. Whether the funnel is using a direct-response approach (specific promise, specific outcome) or a content/educational approach. The primary avatar being targeted (inferred from the hook language). Which creatives have been running the longest (= most successful).

How to apply itThe entry hook informs the PAIN-ACUTE selection for your own ad creative — not by copying it but by confirming that the hook category (pain, desire, curiosity, proof, or counterintuitive claim) resonates with the target avatar. Longest-running creatives identify which hook categories the market responds to.

6. Stage 2: explain the first conversion ask

Capture the entire entry page, including the content below the fold. Record headline structure, subheadline, each bullet’s promise type, CTA, proof density, page length and urgency. Distinguish a result promise, identity shift and curiosity or revelation promise. Note what the buyer must supply or commit to in return.

Translate the observation into a headline or layout hypothesis for your audience. For example, test whether a concrete outcome is clearer than an identity claim while keeping the actual offer constant. A competitor’s current page is not proof that its layout won a test. Preserve the original source table as the capture checklist and document the reasoning for each proposed change.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Lead-Funnel-Squeeze-Page-Types-SOP.docx · RISER-Sales-Page-Architecture-SOP.docx

Original source table 9 — includes source claims qualified above

ANALYSIS STAGE 2Entry Page Analysis (Opt-in, Registration, or Sales Page)Central question: What is the first conversion ask, and how does the page architecture support it?

What to captureComplete screenshot of the entry page above and below the fold. Verbatim headline and subheadline. The bullet point structure and what each bullet promises (not the words — the promise type: result, process, or revelation). The CTA label. Social proof format and density. Page length. Any urgency mechanisms.

What it revealsThe specific promise that converts a cold visitor into an opt-in or a buyer. The promise architecture: whether the headline is result-focused, identity-focused, or curiosity-focused. What the operator believes is the highest-value offer they can make to a cold stranger in one page. The social proof format that the operator has converged on after testing (aggregate number vs specific story vs specific testimonial).

How to apply itThe promise architecture informs your own entry page headline testing — specifically confirming whether result-focused or identity-focused headlines are converting better in this category. The social proof format informs your own opt-in page design.

7. Stage 3: inspect checkout, registration and qualification

A checkout, application and event registration request different commitments. Capture all visible fields, required minimums and question sequence. For checkout, record the order bump, its scope and price relative to the main purchase. For an application, record what each question appears designed to qualify without treating that interpretation as confirmed operator intent.

Use the findings to decide what information your own fulfillment or qualification genuinely requires. Every additional field creates effort, but removing necessary information can harm delivery. Test a defined change and measure qualified progression, completed purchases and downstream outcomes rather than celebrating more form submissions alone.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-SLO-Funnel-SOP.docx · RISER-Application-Funnel-SOP.docx

Original source table 10 — includes source claims qualified above

ANALYSIS STAGE 3Application or Checkout ArchitectureCentral question: What does the commitment step look like — and how does the architecture increase it?

What to captureFor SLO funnels: full checkout page including all fields, order bump (verbatim or paraphrase), and the checkout design. For application funnels: the full application form structure (which questions, in what sequence, with what required minimums). For webinar/challenge funnels: the registration form fields and any pre-registration qualifying questions.

What it revealsHow much information the operator requires before they accept a lead or a buyer. The order bump positioning, copy structure, and price relationship to the main offer. For applications: which questions the operator uses to qualify — revealing their ideal client criteria and their most important qualification dimensions.

How to apply itThe order bump structure directly informs the Order Bump Design Standards in the SLO Funnel SOP and the Downsell Paths SOP. Application form question structure directly informs the Application Funnel SOP's Question Card design.

8. Stage 4: evaluate the next problem offered after purchase

For each accessible one-time offer, capture headline, bridge from the original purchase, components, price, urgency and the decline link. Preserve the sequence and note whether prices rise or fall, whether a downsell appears, and what happens when an offer is declined. Do not assume an unobserved branch is absent.

Ask whether the next offer solves a distinct obstacle created or revealed by the first result. The operator’s sequence expresses a theory of the buyer journey; validate it with your own buyers. Price totals alone cannot establish average cart value. You need take rates, purchase paths, refunds and a defined denominator before computing a meaningful expected cart value.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Downsell-Paths-SOP.docx · RISER-SLO-Funnel-SOP.docx

Original source table 11 — includes source claims qualified above

ANALYSIS STAGE 4OTO / Upsell Page AnalysisCentral question: What does the operator believe their buyer most wants immediately after the first purchase?

What to captureEvery OTO page encountered in sequence: verbatim headline, the bridge sentence (how the OTO connects to the primary purchase), the offer components, the price, the urgency mechanism, and the 'no' link language. Note the structure of the OTO stack: how many OTOs, in what price sequence (ascending or descending), and what topics each OTO covers.

What it revealsThe operator's theory of the buyer's next most urgent desire immediately after purchase. This reveals what the operator believes is the highest-value next problem in the avatar's journey. The OTO sequence price architecture reveals whether the operator is using an ascending stack (low-to-high) or a descending stack (high-to-low) — and the price relationships reveal their assumptions about buyer psychology at each point.

How to apply itOTO stack architecture informs the order bump and upsell design in the SLO Funnel SOP and the Downsell Paths SOP. Specifically: what the operator believes the 'next problem' is after the entry product tells you what the most urgent sub-problem is in this market — which informs the core offer's mechanism positioning.

9. Stage 5: reconstruct the sales argument

Map the argument in order: headline, problem, mechanism, proof, components, value presentation, price, guarantee and FAQ. Count mechanism components and describe their roles in your own words. Record which claims receive supporting evidence and where the page asks the reader to make an unsupported leap.

Use this map to write an original explanation of how your offer produces its outcome. A guarantee reveals published terms; it does not establish refund tolerance or confidence. FAQ placement identifies publicly addressed objections, not necessarily their measured priority. Add candidate objections for investigation with actual buyer evidence rather than assigning priority from competitor copy.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-VSL-Script-Template-SOP.docx · RISER-Guarantee-Type-Testing-Protocol-SOP.docx · RISER-Sales-Page-Architecture-SOP.docx

Original source table 12 — includes source claims qualified above

ANALYSIS STAGE 5Sales Page Deep AnalysisCentral question: What is the complete argument the operator makes for why the buyer should invest in this offer?

What to captureComplete sales page architecture: headline, subheadline, problem section (paraphrased — not copied), mechanism section name and structure (how many components, what each is called), proof section structure (how many case studies, what format), offer stack (how many components, how value is presented), guarantee language and level, FAQ structure and which questions are addressed.

What it revealsThe operator's sales argument structure — the specific sequence of psychological moves they make from problem identification through to close. The mechanism naming convention and how many components it has. The guarantee level they are using (which signals their confidence in the offer and their refund rate tolerance). The objections they consider important enough to address in the FAQ.

How to apply itThe sales argument structure informs the VSL Script Template SOP — specifically the sequence of sections and the density of proof at each stage. The guarantee level informs the Guarantee Type Testing Protocol SOP's baseline for this price point in this category. The FAQ questions are added directly to the Objection Bank SOP as new entries to be investigated for Priority Score.

10. Stage 6: evaluate proof specificity and placement

Count visible testimonials and distinguish text, video, screenshots, case studies and metrics-only claims. Record position before or after mechanism, price and FAQ, plus whether each item addresses an avatar, result or objection. Separate third-party logos, press mentions and aggregate statements from individual experiences.

The exercise is to match your own substantiated evidence to the claim it supports. A large proof count is not a validated minimum for the market. Publicly displayed testimonials are not independently verified just because they appear on a page. Record what you can establish and never present another business’s case study as your own.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Proof-Injection-Checklist-SOP.docx

Original source table 13 — includes source claims qualified above

ANALYSIS STAGE 6Proof Architecture AnalysisCentral question: What proof patterns is the operator using — and how are they structuring the social evidence?

What to captureCount of total testimonials visible. Testimonial format types present (text, video, screenshots, case studies, metrics-only). Testimonial positioning on the page (above the fold, after mechanism, after price, in FAQ). Whether testimonials are avatar-specific or result-specific or objection-specific. Aggregate proof statements ('500 operators have used this to achieve X'). Third-party credibility signals (press mentions, awards, partner logos).

What it revealsThe proof density the market appears to require before making a purchase at this price point. Whether the operator is leading with volume proof (many testimonials) or quality proof (a few highly specific case studies). Which avatar variations are represented in the proof — revealing which segments the operator considers most important to address. Which objections are addressed through proof (objection-matching) vs through FAQ text.

How to apply itThe proof architecture informs the Testimonial Version Registry's selection criteria for which testimonials to place on the sales page and in what sequence. Specifically: does the market respond to a few powerful case studies or to a large volume of shorter testimonials? Both approaches have worked in different categories — hacking multiple competitors in the category establishes which pattern dominates.

11. Stage 7: explain the observed email progression

Build a dated sequence with one row per observed message. Record subject, timing, value or sales purpose, CTA, plain-text or HTML format, length and apparent personal or broadcast presentation. Keep buyer onboarding separate from subscriber nurture. Identify the first direct offer and any return to education or re-engagement.

Turn timing into a hypothesis about readiness, not a universal rule. An established sender may use a short subject effectively because of an existing relationship; your new subscribers may respond differently. Evaluate qualified clicks, purchases, complaints and unsubscribes alongside opens, whose measurement has limitations. Preserve the actual observation period and missing branches.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Email-Fundamentals-SOP.docx

Original source table 14 — includes source claims qualified above

ANALYSIS STAGE 7Email Sequence AnalysisCentral question: What does the operator do with new subscribers and new buyers after the first touchpoint?

What to captureComplete subscriber email sequence: every email subject line (verbatim), send timing, content type (value, proof, mechanism, story, offer, urgency, re-engagement). Complete buyer email sequence (if accessible through an SLO purchase). The transition point where the subscriber sequence shifts from value delivery to offer presentation. Email format patterns (plain text vs HTML, long vs short, personal vs broadcast).

What it revealsThe operator's content distribution framework — how they balance education, entertainment, trust-building, and conversion in the email channel. The timing cadence (daily, every-other-day, weekly) and what the cadence tells you about the operator's theory of buyer readiness. The subject line patterns that the operator has converged on (question-format, curiosity, proof, pain, direct). The transition moment from value to offer (which tells you how much trust the operator believes they need to build before converting).

How to apply itThe email sequence structure informs the Buyer Onboarding sequences and Nurture Sequences in every funnel SOP. Subject line patterns inform the email testing strategy in the monthly email review. The transition timing informs when to introduce the core offer in nurture sequences.

12. Stage 8: extract structures without inventing customer testimony

Classify headlines as result-for-avatar, how-to, contrast, question or numbered promise. Capture pain metaphors and vocabulary, mechanism naming, risk reversal, urgency and CTA structure. For every pattern, explain the buyer concern it might address and propose an original wording grounded in your offer.

The source asks for three to five phrases that resemble buyer language. Label these as competitor copy with the source and date. They do not become verbatim customer evidence because they sound authentic. To populate a genuine voice-of-customer record, recover the original customer statement and its context. Do not move marketing prose into acute-pain, chronic-pain or hidden-desire fields as if a customer said it.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Voice-Consistency-Gate-Founder-POV-Layer-SOP.docx

Original source table 15 — includes source claims qualified above

ANALYSIS STAGE 8Copy Pattern AnalysisCentral question: What specific language patterns and structures appear repeatedly across this funnel's copy?

What to captureHeadline structures (what formula type: result-for-avatar, how-to, contrast, question, number-list). Pain language patterns (specific words and phrases used to describe the problem). Mechanism language (how the solution is named and described — the naming convention and the number of components). Guarantee language (how the risk is reversed). Urgency language (how time sensitivity is created). CTA language (what words are used in buttons and offer-closing moments).

What it revealsThe copy conventions that the market has trained the operator to use. If a category leader has converged on specific headline formulas, specific guarantee language, or specific CTA words after years of testing — those patterns are market-validated. They work with this audience. The specific language patterns also reveal buyer language that can be fed into the Buyer Language Mining database.

How to apply itThe most valuable output of the copy analysis: 3–5 specific phrases from the operator's copy that feel like they mirror buyer language exactly. These are not copied into your funnel — they are added to the PAIN-ACUTE and PAIN-CHRONIC fields in the Buyer Language Mining database for use in your own original copy. Buyer language is not owned by anyone — it belongs to the buyers.

13. Stage 9: compare offer scope and delivery burden

Record offer name, core component count, each component’s purpose, bonuses and stated value, price, payment plans and explicit exclusions. Separate list-price claims from independently established value. Compare what the buyer can accomplish and the effort required, not simply the number of files or bonuses.

An exclusion may reflect positioning, capacity, economics or another reason; it does not prove a component was removed after refund analysis. Use the findings to test your own minimum viable offer and stack. Ask whether each addition increases useful outcome or confidence, reduces delay or effort, and can be delivered reliably without overwhelming the buyer.

The linked M6.2 Trim & Stack excerpt supports the remove-unhelpful-components principle. It names a five-question filter, inventory and $97, $997, $5,000 and $25,000 examples without supplying them. It is a related excerpt, not confirmation that the full MVO Playbook referenced by this source has been recovered.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx · RISER-Bonus-Discipline-Audit-SOP.docx · M6.2 - TRIM & STACK METHODOLOGY

Original source table 16 — includes source claims qualified above

ANALYSIS STAGE 9Offer Architecture AnalysisCentral question: How is the offer designed — what does the operator include, exclude, and name?

What to captureOffer name and any sub-brand or programme series naming. Number of components in the core offer stack. Each component named and described (paraphrase only — do not copy verbatim). Bonus structure (how many, what types, how valued). Price point. Payment plan options and their structure. What the offer specifically does NOT include (as stated in the copy or FAQ).

What it revealsThe operator's theory of what the ideal offer structure is for this avatar at this price point. The bonus types they have selected — which reveals which sub-problems they believe are most important to solve alongside the core promise. The stated exclusions — which are often as revealing as the inclusions, because they show what the operator has deliberately removed after finding it either too costly to deliver or not valued enough by buyers.

How to apply itThe offer architecture informs the MVO Playbook's Trim & Stack process and the Offer Stacking & Unbundling Strategy SOP. Specifically: how many components does a competitive offer in this category contain? What bonus types dominate? How is value stated? These parameters set the competitive baseline against which your own offer is designed.

14. Stage 10: distinguish distribution evidence from speculation

Record traffic estimates, visible ad platforms, public podcast appearances, YouTube audience and content, affiliate-program links and affiliate-specific pages. Keep estimates distinct from measured first-party data. A referral source can suggest a relationship worth investigating; it does not establish a JV agreement.

Long-term advertising indicates persistence, not proven profitable acquisition. Direct traffic is not an email-list census, and creative volume is not spend. Use the channel map to prioritize an appropriately sized test for your audience, offer and economics. Do not inherit a competitor’s platform choice without checking your own acquisition and fulfillment results.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Paid-Ads-Foundations-SOP.docx · RISER-Dream-100-Strategy-SOP.docx · RISER-Affiliate-Program-Architecture-SOP.docx

Original source table 17 — includes source claims qualified above

ANALYSIS STAGE 10Traffic and Distribution AnalysisCentral question: Where is the operator getting their traffic — and what does their distribution strategy tell you about what works?

What to captureSimilarWeb traffic source breakdown. Active ad platforms (Facebook Ads Library, Google Transparency Report). Podcast appearances (search the operator's name on Apple Podcasts / Spotify for guest appearances). YouTube channel subscriber count and top-performing videos. Email list size estimates (SimilarWeb direct traffic as a proxy). Affiliate or JV programme indicators (affiliate programme link in footer, affiliate-specific landing pages).

What it revealsThe operator's primary acquisition channels and their relative investment in each. Whether the funnel works primarily with warm traffic (existing audience) or cold traffic (paid ads). Which platforms the operator has chosen to invest in — and which they have abandoned (their ad history on the Facebook Ads Library shows past tests that were stopped). Whether the operator has built a JV network (affiliate programme = they believe their offer converts for other people's audiences).

How to apply itThe traffic analysis informs the traffic architecture section of each funnel SOP. Specifically: which paid platforms are the category leaders using, and for how long? A category leader who has been running Meta ads for 24+ months with consistent creative updates is confirming that Meta works for this audience. That is a traffic platform decision that does not need to be re-researched from scratch.

15. Move from surface to structure to a qualified principle

At the surface level, you see specific words. At the structure level, you identify a reusable relationship such as result plus avatar plus timeframe plus objection. At the principle level, you hypothesize that clarity about attainability and a primary concern helps a buyer evaluate the offer. Structure alone does not guarantee originality or performance; use independently authored content and evidence-backed promises.

Work through all ten pattern families in the table: headline architecture, pain language, mechanism naming, proof framing, guarantee, urgency, CTA, FAQ, pricing/value and email subjects. For each, record the decision governed, observed form, proposed explanation, evidence limit and your test. The source’s psychological interpretations are hypotheses, not universal buyer laws.

Use real constraints for urgency, genuine scope comparisons for value, supported claims for proof and fulfillable terms for guarantees. A sophisticated mechanism name is not intrinsically better than plain language. FAQ order and established subject-line patterns cannot be assumed to reflect successful experiments without the experiment data.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Guarantee-Type-Testing-Protocol-SOP.docx · RISER-Proof-Injection-Checklist-SOP.docx

Original source table 18 — includes source claims qualified above

PHASE 1The Copy Pattern Extraction SystemTurning observed copy into transferable structural insights

Original source table 19 — includes source claims qualified above

Level	What Is Observed	Example	Output
Level 1 — Surface	The specific words and phrases in the copy.	Headline: 'How [Avatar Type] Are Getting [Specific Result] in [X] Days Without [Primary Fear]'	A headline to copy. Legally problematic if used verbatim. Strategically weak because it lacks your voice and mechanism.
Level 2 — Structure	The formula or pattern underlying the specific words.	Formula: Result + Avatar + Timeframe + Without + Primary Objection. A specific promise for a specific person with a specific timeframe and a specific objection handled.	A headline formula to apply with your own content. Legally sound. Strategically better than Level 1 because your voice and mechanism are intact.
Level 3 — Principle	The psychological reason why this structure works — what need or concern in the buyer's decision-making it addresses.	Principle: Buyers need to see that the result is achievable in a concrete timeframe (not 'eventually') and that their primary fear does not prevent it (the objection is pre-empted before it forms). The headline does both in one sentence.	A principle to apply across all copy — headlines, bullet points, email subject lines, guarantee language. Produces consistently better copy because every element is evaluated against the same underlying principle.

Original source table 20 — includes source claims qualified above

Pattern Family	What It Governs	What to Look For	Level 3 Principle
1. Headline Architecture	The structure of the primary headline on each page	Result + Avatar + Timeframe + Without / How-To + Result + Avatar / Number + Promise + Timeframe / Counterintuitive claim	What does the buyer need to believe first to engage with this funnel? The headline's job is to establish that first belief.
2. Problem Agitation Language	How the pain is described and amplified in copy	Specific vocabulary, metaphors used for the problem, whose fault it is (internal attribution vs external), the time dimension of the pain ('every day that passes...')	The intensity and specificity of pain language required to produce action. Markets with higher pain tolerance require higher agitation. Markets with lower tolerance convert on lighter problem description.
3. Mechanism Naming Convention	How the proprietary method is named	Number of components (3-step, 5-phase, 7-part), naming pattern (acronym, metaphor, proprietary name, borrowed concept), how the name differentiates from conventional approach names	What naming convention the category responds to. Some categories respond to sophisticated mechanism names; others respond to plain language ('the method' or 'the system').
4. Proof Framing	How case studies and testimonials are structured and positioned	Result first vs story first, metric specificity, avatar specificity, objection-matching, before/after structure, quote placement relative to the specific claim it supports	The minimum proof specificity required for this category. Categories with sophisticated, sceptical buyers require higher specificity (exact numbers, specific timelines) than less sophisticated categories.
5. Guarantee Architecture	The structure and boldness of the risk reversal	Guarantee level (unconditional, conditional, result-based), guarantee window (30/60/90 days), what the guarantee covers (refund, re-do, result guarantee), the confidence statement	How much risk the market expects to be removed before committing to a purchase at this price point. Higher price = more risk to reverse.
6. Urgency Mechanics	How scarcity and time-sensitivity are created and communicated	Cohort close (real date), founding pricing (real window), spot limits (real cap), bonus expiry (real deadline), countdown timers (static vs live)	Which urgency mechanisms the market trusts. Some markets have been burned by fake countdown timers and respond only to genuine cohort-based urgency.
7. CTA Language	The specific words used on buttons and close moments	Action verbs (Get, Start, Join, Apply, Claim, Access), object of the action (Your Copy, My Spot, Access, The Programme), price presentation at point of action	What identity the buyer is stepping into when they click. 'Apply' creates a different self-concept than 'Buy.' The CTA language signals what kind of purchase this is.
8. FAQ Objection Selection	Which objections the operator chose to include in the FAQ	Which objection types are included (price, fit, time, prior failure, partner), how they are ordered (most common first vs most blocking first), how they are answered (reframe vs evidence vs guarantee)	Which objections the operator considers most important to address publicly — these are almost certainly their highest-Priority-Score Objection Bank entries, confirmed by their real conversion data.
9. Pricing and Value Presentation	How the price and the value are presented relative to each other	Total stack value before price reveal, price contrast technique (what the price is compared to), payment plan presentation (before or after primary price), guarantee position relative to price	The value-to-price gap the category requires. Some categories convert at 3× stated value; others require 10× stated value before the price is revealed.
10. Email Subject Line Patterns	The recurring structures in the operator's email subject lines	Question vs statement vs one-word subject lines, curiosity gaps vs direct benefit statements, personalisation tokens, emoji usage, capitalisation	The subject line structures the market opens. Operators who have been running their email list for 3+ years have tested subject line patterns extensively — their current patterns are the survivors.

16. Complete the ten-part report with evidence boundaries

Create a dated report identifier, operator, analyst, funnel type, entry and primary prices, estimated traffic, visible ad tenure and a qualified assessment. Complete the ten parts: ads, entry page, conversion path, sales authority, emails, copy patterns, offer architecture, distribution, language provenance and five proposed actions. The complete original template below retains every field.

Distinguish observed prices from an estimated average cart value; leave the latter unknown without take-rate evidence. Record proof-format proportions using a stated count and denominator. Keep an exclusion as an observation rather than a story about past refund analysis. In the language section, separate competitor wording from original customer statements.

Write each of the five actions as a test: change a named element, state the supporting observation, define an outcome measure and specify what would disconfirm the hypothesis. Finish with three to five sentences explaining what the research confirms, challenges or leaves unknown. Do not call the report complete if gated pages or lifecycle branches are missing; describe its actual coverage.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

Original source table 21 — includes source claims qualified above

PHASE 2The Funnel Hacking Report TemplateStructuring the intelligence for actionable application

Original source table 22 — includes source claims qualified above

FUNNEL HACKING REPORT TEMPLATE — Complete one report per hacked funnel.HEADERFunnel Hack ID: [FH-[Operator Code]-[YYYY-MM]. e.g. FH-COMP01-2026-09]Target Operator: [Name / Brand]Date of Analysis: [Date]Analyst: [Name]Funnel Type: [SLO / Application / Webinar / Challenge / Book / Summit / Other]Entry Product Price: $[ ]Primary Offer Price: $[ ]Estimated Monthly Traffic (SimilarWeb): [ ]Ads Running Since: [Earliest Facebook Ads Library date]Overall Assessment: [ ] Best-in-category [ ] Strong [ ] Average [ ] Weak (used primarily as a negative example)PART 1 — AD CREATIVE INTELLIGENCEPrimary Hook Type: [ ] Pain-Acute [ ] Desire-Hidden [ ] Counterintuitive Claim [ ] Proof/Result [ ] Curiosity [ ] QuestionPrimary Hook (paraphrase — do not copy verbatim):[Paraphrase the hook's core message in your own words]Hook's Strongest Element:[What makes this hook work? Specificity? Emotional resonance? Pattern interrupt?]Creative Format: [ ] Static image [ ] Short video (under 60s) [ ] Long video (60s+) [ ] CarouselLongest-Running Creative (described, not copied):[Describe the creative elements: what is shown, what emotion is evoked, what claim is made]Key Ad Copy Insight:[The single most transferable insight from this operator's ad approach — described as a principle, not a surface feature]Buyer Language Extracted (add to Buyer Language Mining database):1. [Phrase 1 — verbatim from ad copy if it reads as buyer language]2. [Phrase 2]3. [Phrase 3]PART 2 — ENTRY PAGE INTELLIGENCEHeadline Formula: [Describe the formula type used, not the verbatim headline]Above-the-Fold Architecture:[Describe what is visible without scrolling: layout, elements, visual hierarchy]Primary Promise Type: [ ] Result + Timeframe [ ] Identity shift [ ] Secret/Revelation [ ] How-toLead Magnet / Entry Product Type: [Describe the format and value proposition type]Social Proof Format: [Number of testimonials, format, specificity level]Key Entry Page Insight:[The single most transferable insight from this page — as a principle]Buyer Language Extracted:1. [Pain phrase]2. [Desire phrase]PART 3 — CONVERSION ARCHITECTURE INTELLIGENCEOrder Bump Structure (if present): [Price, what it is, one-sentence description]OTO 1 Structure: [Price, what it is, bridge approach, urgency mechanism]OTO 2 Structure (if present): [Price, what it is]Downsell (if present): [Price, positioning]Total Funnel ACV Estimate: $[ ]Key Conversion Architecture Insight:[The single most transferable insight — as a principle]PART 4 — SALES PAGE / AUTHORITY PAGE INTELLIGENCEMechanism Name: [Their mechanism name — for reference only. Not to be used.]Mechanism Component Count: [Number]Mechanism Component Names: [Paraphrase, not verbatim. What category does each name fall into?]Proof Count: [Total testimonials visible]Proof Format Distribution: [X% text, X% video, X% screenshot, X% case study]Proof Positioning: [Where on the page? Before price? After mechanism? In FAQ?]Guarantee Level: [ ] Unconditional [ ] Conditional [ ] Result-based [ ] Anti-guaranteeGuarantee Window: [X days]FAQ Question Count: [ ]FAQ Objection Types Addressed: [List the objection types, matched to Objection Bank categories]Key Sales Page Insight:[The single most transferable insight — as a principle]Objection Bank Entries to Add:1. [Objection type + verbatim or paraphrased objection language]2. [Continue]PART 5 — EMAIL SEQUENCE INTELLIGENCESequence length observed: [X emails over X days]Sequence structure (summarise in one sentence per email):Day [X]: [Content type + CTA type][Continue for each email observed]Subject line patterns observed:Pattern 1: [Describe the formula — e.g., 'One-word subject lines. Product of the sender's familiarity with the list.']Pattern 2: [Continue]Transition point (when does the sequence shift from value to offer?): Day [X]Key Email Sequence Insight:[The single most transferable insight — as a principle]PART 6 — COPY PATTERN FINDINGSFor each of the ten copy pattern families, note the pattern used and the Level 3 principle extracted:1. Headline Architecture: [Pattern observed] → [Level 3 principle]2. Problem Agitation: [Pattern observed] → [Level 3 principle]3. Mechanism Naming: [Pattern observed] → [Level 3 principle]4. Proof Framing: [Pattern observed] → [Level 3 principle]5. Guarantee Architecture: [Pattern observed] → [Level 3 principle]6. Urgency Mechanics: [Pattern observed] → [Level 3 principle]7. CTA Language: [Pattern observed] → [Level 3 principle]8. FAQ Objection Selection: [Pattern observed] → [Level 3 principle]9. Pricing and Value Presentation: [Pattern observed] → [Level 3 principle]10. Email Subject Line Patterns: [Pattern observed] → [Level 3 principle]PART 7 — OFFER ARCHITECTURE FINDINGSOffer component count: [ ]Bonus types present: [List: template / coaching / community / tool / swipe file / other]Bonus count: [ ]Price point: $[ ]Value stated before price reveal: $[ ] (stated value ÷ price = [X]× ratio)Offer exclusions noted (what the offer explicitly does NOT include):[Note anything the operator says is NOT included — these deliberate exclusions often reveal what was once included but removed after refund analysis]Key Offer Architecture Insight:[The single most transferable insight — as a principle]PART 8 — TRAFFIC AND DISTRIBUTION FINDINGSPrimary Traffic Sources: [ ] Paid Meta [ ] Paid Google [ ] YouTube [ ] TikTok [ ] Organic [ ] JV / AffiliateEstimated Traffic Volume: [Monthly estimate from SimilarWeb]Longest-Running Ad Platform: [Platform + approximate tenure from Ads Library dates]JV / Affiliate Programme: [ ] Yes [ ] NoKey Traffic Insight:[The single most transferable insight — as a principle]PART 9 — BUYER LANGUAGE DATABASE UPDATEList all phrases extracted from this funnel hack that should be added to the Buyer Language Mining database:PAIN-ACUTE additions: [Phrases verbatim if they read as buyer language — not marketing copy]PAIN-CHRONIC additions: [Phrases]DESIRE-HIDDEN additions: [Phrases]Objection Bank additions: [New objection entries with type classification]PART 10 — TOP 5 ACTIONABLE INSIGHTS// These are the five most important findings from this funnel hack, each expressed as a specific action the RISER Nation operator should take.1. [Finding stated as an action: 'Test [specific change] to [specific page/element] based on this operator's pattern of [specific observation].']2. [Continue]3. [Continue]4. [Continue]5. [Continue]Overall Assessment Summary (3–5 sentences):[What is the most important thing this funnel hack confirms, challenges, or reveals about the category? What did you expect to find that you did not? What surprised you?]

17. Synthesize comparisons without overstating confidence

The source groups evidence into one-funnel hypotheses, patterns across at least three comparable funnels, and proposed principles across at least five plus your own performance data. Retain those as organizational milestones. Sample count alone does not establish statistical confidence or causality, and common practice is not enough to deploy a change without evaluating its consequences.

Answer the seven convergence questions about headline, proof, guarantee, timing before offer, FAQ objections, mechanism names and stated value ratios. Then answer the three divergence questions: what varies, what a demonstrably strong performer does differently, and what weaker performers share. If performance is unknown, label it unknown rather than ranking by appearance.

Address all three opportunity questions: missing promises or proof supported by buyer evidence, a potentially stronger but deliverable guarantee, and customer concerns absent from current copy. Write three to five concise principles with scope, evidence and exceptions. A longer guarantee may create a different risk profile; generosity alone does not establish better economics.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

Original source table 23 — includes source claims qualified above

PHASE 3The Synthesis Protocol — From Intelligence to Decisions

Original source table 24 — includes source claims qualified above

Synthesis Level	Input	Output	Decision Trigger
Level 1 — Single Funnel Finding	One completed Funnel Hacking Report	Specific hypotheses about what might work in your funnel, based on what is working in one competitor's funnel. Minimum confidence — one data point.	A/B test hypothesis. One element to test in your funnel based on this funnel's approach. Low confidence — test before deploying.
Level 2 — Category Pattern	Three or more Funnel Hacking Reports from funnels serving the same avatar at a comparable price point	A pattern confirmed across multiple high-performing funnels. Medium confidence — the market has spoken through multiple operators' testing.	An element to deploy (not just test) in your funnel with confidence. Still monitor performance, but the category pattern is strong enough evidence to implement without extensive prior testing.
Level 3 — Category Principle	Five or more Funnel Hacking Reports + your own funnel performance data showing the same pattern converts in your funnel	A principle that governs conversion architecture in this category. High confidence — confirmed across multiple independent data sources.	A foundational design decision for all future funnel work in this category. Update the relevant RISER Nation SOPs to reflect the category-validated principle.

Original source table 25 — includes source claims qualified above

CATEGORY SYNTHESIS QUESTIONSCONVERGING PATTERNS (patterns present in 3+ of the hacked funnels)1. What headline formula type appears most consistently across the category's highest-performing funnels?2. What proof format and density appears most consistently?3. What guarantee level and structure appears most consistently at this price point?4. What is the typical number of email sequence elements before the offer is introduced?5. What are the most common objection types addressed in the FAQ sections? (Add any new ones to the Objection Bank.)6. What mechanism naming convention dominates — and what does that tell you about the buyer's sophistication level?7. What is the typical value-to-price stated ratio in the offer stack presentations?DIVERGING PATTERNS (patterns that vary significantly across hacked funnels)1. Which funnel elements show the most variation? (Divergence may indicate an area where differentiation is possible.)2. What does the highest-performing funnel do differently from the others? (Their differentiation is likely intentional — what problem does it solve?)3. What do the underperforming funnels have in common that the top performers do not?GAPS AND OPPORTUNITIES1. Is there a promise, mechanism, or proof type that is absent from all hacked funnels but that the Buyer Language Mining database suggests buyers want?2. Is there a guarantee level that is more generous than what any category competitor offers? (A category where all operators offer 30-day money-back is a category where a 60-day result guarantee is a differentiator.)3. Is there a buyer language pattern from Q&A sessions, forums, or support tickets that no competitor's copy addresses directly? (Unaddressed language = an opening.)CATEGORY PRINCIPLE STATEMENTS (consolidate findings into principles)// Write 3–5 one-sentence principles that capture the most important category-level findings.// Example: 'In this category, proof density above [X testimonials] does not increase conversion — specificity of individual testimonials matters more than volume.'// Example: 'Mechanism names in this category follow a [naming convention] — departing from this convention requires additional explanation of the mechanism's nature.'Principle 1: [ ]Principle 2: [ ]Principle 3: [ ]Principle 4: [ ]Principle 5: [ ]

18. Maintain a dated research cadence

The proposed annual cycle is Q1: three to five full funnel reviews and synthesis, eight to sixteen hours; Q2: ad refresh, two to three hours; Q3: email refresh, four to six hours; Q4: offer review, three to five hours. These are planning estimates. A thirty-day email observation spans elapsed time beyond the analyst hours and cannot be compressed into a single sitting.

Maintain six to ten operators, a proposed thirty-minute Monday review and a monthly change record. Check new ads, formats, hooks, offers, retirement of long-running creatives and public positioning. Changes can suggest a question; retirement does not prove a failed ad. Keep dates and prior states rather than replacing history.

The five source triggers are a new funnel type, a primary-price change over twenty percent, a new mechanism, apparent scaling and a public rebrand or pivot. Creative volume is only a weak scaling proxy. The source says both immediate review and scheduling within fourteen days; record the chosen priority and due date explicitly. This lesson describes a cadence and does not create accounts, subscriptions or monitoring automations.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx · RISER-Guarantee-Type-Testing-Protocol-SOP.docx · RISER-Creative-Brief-Template-SOP (1).docx

Original source table 26 — includes source claims qualified above

PHASE 4The Quarterly Category Audit CadenceKeeping competitive intelligence current in a changing market

Original source table 27 — includes source claims qualified above

Quarter	Audit Focus	Time Investment	Output
Q1 — Full Category Audit	Complete new funnel hacks on the top 3–5 funnels in the category. For each: complete Funnel Hacking Report. Run the Category Synthesis Protocol.	8–16 hours total for the full audit	Updated Category Principles document. New Buyer Language Mining database entries. New Objection Bank entries. Updated funnel SOP recommendations.
Q2 — Ad Creative Monitor	Review the Facebook Ads Library for all tracked competitors. Screenshot all new creatives and note the retirement of old ones. Which hooks have been replaced? What does the new creative tell you about what stopped working?	2–3 hours	New creative intelligence notes. Updated Hook Analysis for the Ad Creative Brief Template (SLO Funnel SOP Phase 1 and Challenge Funnel SOP Phase 4).
Q3 — Email Sequence Refresh	Re-opt-in to the top 3 competitor funnels with a fresh analysis email address. Map the new email sequence structure. Compare to the Q1 baseline — what has changed?	4–6 hours	Updated email sequence intelligence. New subject line patterns. Updated Email Sequence Architecture section in relevant funnel SOPs.
Q4 — Offer Architecture Review	Review the current offer stacks of top 3–5 competitors. Have new bonuses been added? Have components been removed? Have prices changed? Have guarantee levels changed?	3–5 hours	Updated Offer Architecture Intelligence. New inputs for the Offer Stacking & Unbundling Strategy SOP and the Guarantee Type Testing Protocol SOP.

Original source table 28 — includes source claims qualified above

COMPETITOR WATCH LIST TEMPLATEWATCH LIST OPERATORS (6–10 names)Operator 1: [Name] — Primary Funnel Type: [Type] — Current Entry Offer: $[ ] — Ad Platforms Active: [ ]Operator 2: [ ][Continue for all watch list operators]WEEKLY REVIEW ITEMS (30 minutes every Monday)1. Facebook Ads Library check: any new ads launched by any watch list operator in the past 7 days?2. New creative format? New hook type? New offer type?3. Any ads retired that had been running for 30+ days? (Retirement of a long-running ad = the operator may be pivoting)4. Any social media posts from watch list operators containing new mechanism language, new results, or new positioning?TRIGGER CONDITIONS FOR A FULL FUNNEL HACK// The following events should trigger an immediate full funnel hack of the relevant operator:[ ] A new funnel type launched (different from their established funnel — e.g., they were SLO-based and launched a challenge)[ ] A significant price change (more than 20% up or down on their primary offer)[ ] A new mechanism name or naming convention visible in ads or content[ ] Evidence of significant scaling (ad spend appearing to increase dramatically based on increased creative volume)[ ] A public announcement of a rebrand, pivot, or programme restructureMONTHLY INTELLIGENCE UPDATEDate: [ ]Watch list changes (operators added or removed): [ ]Notable category developments this month: [ ]Actions triggered: [ ]

19. Apply originality and provenance checks

Use the originality, authority and sourcing-transparency questions before turning research into published material. Would the other operator recognize their specific assets? Does your own explanation work with your mechanism and evidence? Can you explain where the idea came from? These questions guide review but do not settle legal rights.

Preserve the six source prohibitions: no verbatim competitor marketing copy, unauthorized images or video, borrowed testimonials presented as yours, appropriation of mechanism names, unauthorized reuse of purchased program content, or false identity and disruption. The source broadly labels purchasing to use course content as theft; distinguish legitimate study and licensed use from unauthorized copying or redistribution. Do not treat a paid purchase as unrestricted rights to publish its contents.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

Original source table 29 — includes source claims qualified above

Question	Pass	Fail — Required Action
1. Originality Test: If the operator whose funnel you studied read this output, would they recognise their specific words, phrases, images, or structural elements in it?	No — the output uses different words, different images, and different structure. Only the underlying principle has been applied.	Yes — stop. Rewrite from the Level 3 principle, not from the specific execution observed. If an image is being reused: commission an original image. If copy is being reused: rewrite in your own voice addressing the same buyer concern.
2. Authority Test: Would this output be more effective WITH the competitor's specific elements, or is it actually better when you apply the principle with your own voice, mechanism, and buyer language?	Your own voice + your mechanism + your buyer language > their copy in your context. This is almost always true.	The output is weaker when you apply your own elements. This is a signal that you are extracting too little value from the funnel hack — you are copying rather than learning. Go back to the Level 3 principle and re-extract.
3. Sourcing Transparency Test: If a client asked 'where did the idea for this element come from?' — could you explain the full process (you observed a category pattern, extracted the underlying principle, and applied it with your own content) without any discomfort?	Yes — the process is transparent and defensible. The principle, not the specific execution, was borrowed.	No — there is something in the output that you would not be comfortable explaining fully. Remove or replace that element.

Original source table 30 — includes source claims qualified above

The Specific ProhibitionsThe following actions are prohibited within the RISER Nation funnel hacking methodology, regardless of the perceived competitive pressure or time constraint:1. Reproducing any headline, subheadline, or copy section verbatim from a competitor's funnel in your own marketing materials.2. Using any competitor's images, graphics, or video content without permission.3. Representing a competitor's testimonials or case studies as your own.4. Using a competitor's mechanism name in your own marketing — even with attribution.5. Purchasing a competitor's programme with the intent to use the programme content rather than to study the funnel architecture. This is theft of intellectual property, not competitive intelligence.6. Opt-ing in to a competitor's funnel under a false identity or with the intent to disrupt their business processes.

20. Keep both schemas traceable to evidence

The Funnel Hack Records schema stores identity, URLs, analyst/date, type, prices, traffic estimates, ad dates and platforms, hook/headline classifications, proof, guarantee, email window, value ratio, mechanism and upsell counts, estimated cart value, five actions, linked report, update counts, watch status and next review. Preserve its exact field types and select values in the table below; annotate unavailable evidence rather than fabricating a number.

The Category Intelligence schema links source reports to category identity and audit date, dominant patterns, proof and guarantee baselines, value ratios, days before an offer, channel, five principles, exceptions and watchlist history. A linked report should let a reviewer trace any summary back to the actual captured evidence.

Keep customer-language entries separate from competitor-copy notes. Do not turn a subjective assessment into a performance fact. A checked update box only records that an update happened, not that the new principle is validated. As an exercise, complete one report from accessible material, mark every unknown, propose five tests, then reconcile each category statement to its supporting records.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

Original source table 31 — includes source claims qualified above

Field	Type	Notes
Funnel Hack ID	Short text	Format: FH-[Operator Code]-[YYYY-MM]. e.g. FH-COMP01-2026-09
Target Operator Name	Short text
Target Operator Website	URL
Date of Analysis	Date
Analyst	Short text
Funnel Type	Single select	SLO / Application / Webinar / Challenge / Book / Summit / VSL / Hybrid
Entry Product Price	Currency
Primary Offer Price	Currency
Estimated Monthly Traffic (SimilarWeb)	Number
Ads Running Since	Date	Earliest date in Facebook Ads Library
Active Ad Platforms	Multi-select	Meta / Google / YouTube / TikTok / LinkedIn
Primary Traffic Source	Single select	Paid / Organic / Mixed — paid dominant / Mixed — organic dominant
JV Programme Active	Checkbox
Overall Funnel Assessment	Single select	Best-in-category / Strong / Average / Weak
Primary Hook Type	Single select	Pain-Acute / Desire-Hidden / Counterintuitive / Proof/Result / Curiosity / Question
Headline Formula Type	Single select	Result+Avatar / How-To / Counterintuitive / Number+Promise / Identity Shift / Other
Proof Format Dominant	Single select	Text testimonials / Video testimonials / Case studies / Screenshots / Mixed
Proof Count	Number
Guarantee Level	Single select	None / Unconditional / Conditional / Result-based / Anti-guarantee
Guarantee Window (days)	Number
Email Sequence Length (days observed)	Number
Offer-to-Value Ratio	Number	Total stated value ÷ offer price
Mechanism Component Count	Number
OTO Count	Number
Estimated ACV	Currency
Top 5 Actionable Insights	Long text	From Part 10 of the Report
Category Principles Updated	Checkbox	Were any Category Principle statements updated or added based on this hack?
Buyer Language Entries Added	Number	Count of new entries added to the Buyer Language Mining database from this hack
Objection Bank Entries Added	Number	Count of new Objection Bank entries triggered by this hack
Full Report Link	URL	Google Drive link to the completed Funnel Hacking Report document
Watch List Status	Single select	On watch list / Removed from watch list / Never on watch list
Next Scheduled Hack Date	Date
Notes	Long text	Observations that did not fit into structured fields

Original source table 32 — includes source claims qualified above

Field	Type	Notes
Category ID	Short text	Format: CAT-[Topic Code]. e.g. CAT-OFFERS
Category Name	Short text
Last Full Audit Date	Date
Funnel Hacks in This Category	Link → Funnel Hack Records	All hacked funnels in this category
Dominant Headline Formula	Short text	The formula type that appears most frequently in this category
Dominant Proof Format	Single select
Category Baseline Proof Count	Number	Average number of testimonials on the sales page of strong funnels
Dominant Guarantee Level	Single select
Category Baseline Guarantee Window	Number	Modal guarantee window in days
Category Baseline Value-to-Price Ratio	Number	Typical stated value ÷ offer price in this category
Typical Email Sequence Length Before Offer	Number	Days
Dominant Traffic Platform	Single select	Meta / Google / YouTube / TikTok / Organic / Mixed
Category Principle 1	Short text
Category Principle 2	Short text
Category Principle 3	Short text
Category Principle 4	Short text
Category Principle 5	Short text
Copy Pattern Exceptions	Long text	Documented cases where a top performer violates a category pattern — and what seems to be the reason
Competitor Watch List (active)	Long text	Names and monitoring status of all watch list operators in this category
Last Watch List Update	Date

21. Run the complete setup and session checklist

Before a research session, prepare a dedicated analysis address if one is legitimately needed, a Funnel Hack Records table, a Category Intelligence table and a watchlist of six to ten relevant operators. The paid ad-intelligence account in the source is optional. Existing public information can support a limited review without a purchase or new account. Record that limit rather than treating an unavailable step as completed.

For target screening, the source uses thirty days of active ads as a paid-traffic signal, ninety days of funnel operation as a maturity threshold, and twelve to thirty-six months as an example of older architecture. These durations are selection heuristics, not measured spend or optimization evidence. The source proposes rechecking a new funnel after ninety days. Its twelve-month persistence claim does not establish revenue or profit.

Confirm avatar fit using the headline, problem and who-this-is-for language. Compare price tiers and decision context: a $47 self-liquidating offer and a $5,000 program usually require different commitments; the source also contrasts $97 and $3,000. It permits comparable or higher-price targets, but a higher price alone does not make a useful comparison. Record scope, audience and buying process alongside price.

In the session record, capture visible ads and dates, traffic estimates, earliest available archived versus current pages, legitimate entry access and screenshots of each observed step. Record the start of the thirty-day email window. The source checklist says entry purchase below $47 while its protocol says $47 or less; retain this boundary discrepancy and do not silently authorize a purchase under either rule.

Complete every report part, identify five testable actions, and create a traceable research record. Review candidate acute-pain, chronic-pain and hidden-desire language with provenance rather than copying competitor wording into customer-evidence fields. Treat new FAQ objections as investigation candidates. Close the session by identifying unavailable pages, emails and evidence, and assigning follow-up dates.

After each quarterly audit, update the category record and flag affected SOPs for review. In Q3 the source proposes observing fresh entry sequences for the top three operators; record whether a new legitimate observation actually occurred. Each weekly review preserves new-creative screenshots, hook and format notes, retirement history and social positioning changes. A triggered full review has both immediate and fourteen-day source timing language; set an explicit due date and preserve the discrepancy.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

22. Explain each copy-pattern family as a decision hypothesis

Headline architecture governs the first reason to pay attention. Compare result-plus-avatar-plus-timeframe-plus-objection, how-to, numbered promise and counterintuitive structures. State what must be believed first, then test whether the headline communicates that claim accurately. A concrete timeframe belongs only where the offer can support it.

Pain language describes the problem through vocabulary, metaphor, attribution and time. Notice whether the copy blames the buyer or an external obstacle and whether it emphasizes the cost of delay. The source links agitation intensity to pain tolerance, but that is not a measured law. Use genuine buyer evidence and avoid exaggerating consequences merely to increase pressure.

Mechanism naming gives the method a handle: component count, acronym, metaphor, proprietary label or plain-language name. Ask what explanation makes the actual process understandable. A three-step or seven-part label is a presentation choice, not evidence that the underlying method works. Do not appropriate a competitor’s mechanism name.

Proof framing can lead with a result or a story, use specific metrics and timing, show before-and-after context, and match an avatar or objection. Place your own evidence next to the specific claim it supports. The source suggests more skeptical categories need more specificity; use that as a testable communication hypothesis rather than a formula for minimum testimonial counts.

Guarantee architecture specifies unconditional, conditional or result-based terms; thirty-, sixty- and ninety-day windows; refund, redo or another remedy; and an explanation of confidence. Compare the actual risk removed, the buyer obligations and delivery economics. A higher price does not by itself dictate a particular guarantee or make an unsupportable result promise acceptable.

Urgency can arise from a real cohort close, genuine introductory-price window, capacity cap or bonus expiry. Check whether the deadline actually changes availability or terms. A timer’s appearance is not proof of a real deadline. Record observable evidence and design only constraints you can honor.

CTA language signals an action and its object: get a copy, start, join, apply, claim or access. Note whether price is shown at that moment. Apply implies a qualification process; buy implies a transaction. Make the destination match the button rather than adopting a phrase solely because another operator uses it.

FAQ selection can cover price, fit, time, prior failure and partner approval. Record whether answers reframe the issue, provide evidence or reference a guarantee, and whether ordering appears based on frequency or blocking importance. Only actual research or performance data can establish that priority; the visible order cannot.

Price and value presentation may reveal stack value before price, use a comparison anchor, introduce installments before or after the primary price, and position a guarantee nearby. The source contrasts three-times and ten-times stated-value ratios. Treat those as unvalidated category examples, not target multipliers or permission to invent component values.

Email subjects can use questions, statements, a single word, curiosity, direct benefits, personalization, emojis or capitalization. Record the sender relationship and observed message purpose. Three years of list operation does not prove every surviving subject pattern was tested. Develop an original subject that truthfully represents the message, then evaluate it with appropriate outcome measures.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx · RISER-Hook-Engineering-Attention-Engineering-SOP.docx · RISER-Guarantee-Type-Testing-Protocol-SOP.docx · RISER-Proof-Injection-Checklist-SOP.docx · RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx

23. Complete report fields with explicit units and provenance

Start the report with an identifier such as FH-COMP01-2026-09, target operator, analysis date, analyst, funnel type, entry price and primary-offer price. Keep estimated monthly traffic labeled as an estimate and record the earliest ad date actually observed. The source assessment options are best-in-category, strong, average and weak; describe the basis and do not let a subjective design rating imply measured sales performance.

In the ad section, classify the hook, paraphrase its message, explain its strongest visible element and identify static, short-video under sixty seconds, long-video sixty seconds or more, or carousel format. Describe the longest-running observed creative and one transferable hypothesis. The source’s three extracted-language slots require provenance labels before they can be used as customer evidence.

For the entry page, record headline formula, above-the-fold hierarchy, promise type, lead-magnet or entry-product format, proof and one proposed insight. For conversion architecture, record the bump, each upsell, bridge, urgency, price and downsell. Leave average cart value unknown unless observed take rates support a calculation. For sales authority, record mechanism name for reference only, component count and paraphrases, proof count and format distribution, position, guarantee type/window and FAQ count/categories.

For email, state the number of messages and days actually observed, summarize purpose and CTA for each message, classify subjects and identify the first offer. For copy, fill all ten families. For offer scope, count components and bonuses, list bonus types, price and stated value, and divide stated value by price only when the price is nonzero. Label the resulting ratio as a comparison of claims, not measured customer benefit.

For distribution, record the observed channels, estimated volume, ad tenure and evidence for an affiliate program. In the language section, classify acute pain, chronic pain, hidden desire and objections while preserving who actually said each phrase. Finish with five specific proposed tests and the three-to-five-sentence assessment. An empty field should say unknown, not applicable or not observed, with a reason, rather than disappearing from the report.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

24. Maintain schema types, history and meaningful blanks

Use short-text identifiers and operator names, URL fields for operator website and full report, and date fields for analysis, next review and ad tenure. Currency fields store entry price, primary price and any defensible estimated cart value; number fields store traffic estimates, proof count, guarantee days, observed email days, mechanism count, upsell count and stated-value ratio. Record currency and measurement period consistently because a number without its unit can mislead.

The source’s funnel-type select includes SLO, application, webinar, challenge, book, summit, VSL and hybrid. Its report also permits other, so preserve an explicit exception when the form and schema do not align. Active-platform multi-select includes Meta, Google, YouTube, TikTok and LinkedIn. Primary-source choices distinguish paid, organic and mixed with the dominant source stated. An observed active program checkbox cannot distinguish no evidence from confirmed absence; preserve that uncertainty in notes.

Keep hook, headline and proof classifications consistent with the capture record. Guarantee choices include none, unconditional, conditional, result-based and anti-guarantee; a label alone does not explain the actual terms. Watch status distinguishes on the list, removed and never on the list. Long-text fields hold the five actions and additional observations. Counts of language and objection entries describe records added, not evidence quality or a validation score.

In the category table, use a CAT-style identifier, name, last full audit date and linked funnel records. Keep dominant headline, proof, guarantee, traffic and stated-value ratio alongside baseline testimonial count, modal guarantee window and days before an offer. State which comparable records underlie each baseline and how missing observations are handled. A mode or average from a few observed funnels remains descriptive.

Store each of the five category principles separately, with copy-pattern exceptions and a dated watchlist update. The schema’s checkboxes and summary fields do not preserve enough history by themselves; retain prior reports and record effective dates when a principle changes. Do not overwrite a prior conclusion without keeping its evidence and the reason for revision.

Supporting documents: RISER-Funnel-Hacking-Methodology-SOP.docx

Source dependencies still unresolved

The exact Buyer Language Mining database/SOP, Objection Bank SOP and Testimonial Version Registry referenced by this document have not been identified in the current inventory by those names. Related materials linked above are not substitutes for these missing assets. The M6.2 excerpt does not supply the full referenced MVO Playbook. Preserve these gaps when reviewing the lesson.

Framework references

ClickFunnels — audience relationships and funnel context · Acquisition.com — offers education

Complete original source

Full readable source, including setup and operational checklists

RISER NATION
MASTER OPERATING SYSTEM
  SOP — FUNNEL HACKING METHODOLOGY  
The Complete Intelligence System for Reverse-Engineering Successful Funnels, Extracting Transferable Insights, and Applying Them to Build Category-Leading Sales Architecture
Brunson  ×  Kennedy  ×  Halbert  ×  2026 Framework
Version 1.0  |  2026 Edition  |  RISER Nation Master Operating System
SOP Overview
Funnel hacking is the discipline of systematically studying successful funnels — your competitors', your category leaders', and operators in adjacent categories — to extract the specific decisions they have made that produce results, and applying the underlying principles to your own funnel architecture. Russell Brunson coined the term and turned it into a foundational practice of ClickFunnels' culture: 'Every funnel that is working in the marketplace has already been tested on real buyers. The decisions it reflects are informed by data. Studying it is not copying — it is reading the market's research report.'
The critical distinction is between extraction and replication. Replication — copying a competitor's headline, images, or copy verbatim — is both legally and strategically counterproductive. Legally, it creates intellectual property exposure. Strategically, it produces a pale imitation of the original that lacks the authority signals, the buyer language specificity, and the mechanism distinctiveness that made the original work. Extraction — identifying the structural decisions, the psychological mechanisms, and the conversion architecture that produced results, then applying the underlying principles to your own content — is what funnel hacking actually is.
This SOP covers: the funnel hacking ethics framework, the funnel target selection criteria, the intelligence gathering toolkit, the ten-stage funnel analysis methodology (from ad creative through email sequence), the copy pattern extraction system, the offer architecture analysis, the traffic source inference methodology, the synthesis protocol that converts raw intelligence into actionable decisions, the Funnel Hacking Report template, the quarterly category audit cadence, and the Airtable database schema.
Target Selection — Which Funnels Are Worth Hacking
Not every competitor funnel contains useful intelligence. A funnel that is poorly designed, recently launched, or driven primarily by an existing large audience rather than by funnel architecture produces misleading signals about what converts. Target selection determines the quality of the intelligence before a single minute of analysis is invested.
The Five Target Criteria
The Intelligence Gathering Toolkit
Intelligence gathering uses a specific set of tools and techniques to surface the maximum amount of funnel architecture before the systematic analysis begins. The goal is to move through the funnel as a buyer would — experiencing every page, every email, and every upsell in sequence — while capturing the complete architecture.
The Tool Stack
The Opt-In Protocol
The most complete funnel intelligence is gathered by going through the funnel as a real buyer would — using a dedicated analysis email address and purchasing the entry-level product where it exists. This is both the most complete intelligence source and the most ethically straightforward: the operator receives payment for the product, the analyst receives legitimate access to the full funnel architecture.
The Ten-Stage Funnel Analysis Methodology
The funnel analysis is conducted in ten sequential stages, each with a specific set of questions to answer and a specific intelligence output. The ten stages cover the complete conversion architecture from first ad impression to post-purchase ascension. Analysis is conducted in sequence — each stage's insights inform the interpretation of the next stage.
The Three Levels of Copy Observation
Most funnel hackers observe copy at Level 1 and never reach Level 3. Level 1 analysis produces a list of things to copy. Level 3 analysis produces a set of principles to apply. The difference in output quality is the entire value of having a systematic methodology.
The Ten Copy Pattern Families
The copy analysis across multiple funnel hacks will surface patterns that recur across successful funnels in a category. These patterns cluster into ten families. The objective of the copy analysis phase is to identify which patterns from each family the target operator has converged on — and to extract the Level 3 principle from each.
Why the Report Matters
Raw intelligence — screenshots, notes, email archives — is not actionable. The Funnel Hacking Report converts raw intelligence into structured findings and specific recommendations. It is the document that bridges from observation to decision. Without it, funnel hacking sessions produce a folder of screenshots that is never reviewed and never acted upon.
The Three-Level Synthesis
The Funnel Hacking Report captures the intelligence from a single funnel. The synthesis protocol aggregates intelligence from multiple funnel hacks (minimum three in the same category) to identify patterns that are market-validated rather than operator-specific. An operator-specific pattern may reflect that operator's particular audience, their brand authority, or their specific mechanism — it may not be transferable. A market-wide pattern that appears in three or more high-performing funnels in the same category is much more likely to transfer.
The Synthesis Questions — Category Intelligence
When three or more funnel hacks have been completed in a category, answer the following synthesis questions to extract the category-level intelligence.
Why Funnel Intelligence Expires
Funnel intelligence has a shelf life. A category analysis conducted 12 months ago reflects the category as it was 12 months ago — before competitor launches, before algorithm changes, before the market's sophistication level increased, and before new buyers entered with different expectations. The quarterly audit cadence ensures that the funnel architecture decisions in the RISER Nation system are informed by current market intelligence rather than historical intelligence.
The Competitor Watch List
The quarterly audit is supplemented by an ongoing competitor watch list — a set of six to ten operators in the category that are monitored continuously at low cost. The watch list requires 30 minutes per week, primarily reviewing the Facebook Ads Library for new creative launches and the operators' social content for new mechanism language or positioning shifts.
The Funnel Hacking Ethics Protocol
Funnel hacking operates at the boundary between competitive intelligence (legitimate and valuable) and intellectual property appropriation (illegal and counterproductive). The ethics protocol defines the boundary clearly and provides the test for every output produced by a funnel hacking session.
The Three-Question Ethics Test
Apply this test to every output produced by a funnel hacking session before it is incorporated into the RISER Nation system.
Funnel Hacking Database — Airtable Schema
Table 1 — Funnel Hack Records
One record per completed funnel hack.
Table 2 — Category Intelligence Records
One record per category analysed. Updated after each quarterly audit.
Master Funnel Hacking Methodology Checklist
System Setup (One-Time)
☐  Analysis email address created — dedicated to all funnel hacking opt-ins
☐  Funnel Hack Records table created in Airtable with all fields
☐  Category Intelligence Records table created in Airtable
☐  Competitor Watch List established with 6–10 operators in the primary category
☐  AdSpy or equivalent ad intelligence tool account active (optional — Facebook Ads Library provides most of the required data for free)
Per-Funnel Hack Session
☐  Target funnel passes all five Target Criteria (traffic evidence, 90+ days running, meaningful revenue, avatar match, price tier match)
☐  Facebook Ads Library: all active ads screenshotted, run dates noted, longest-running creatives identified
☐  SimilarWeb: traffic source breakdown captured, monthly estimate noted
☐  Wayback Machine: earliest version of the funnel pages reviewed against current versions
☐  Opt-in completed with analysis email address
☐  All funnel pages experienced in sequence and screenshotted
☐  30-day email monitoring period initiated — all emails to the analysis address opened and screenshotted
☐  SLO purchased if price is below $47 and the full funnel architecture is accessible through the purchase
☐  Complete Funnel Hacking Report filled out through all ten parts
☐  Top 5 Actionable Insights identified and added to the report
☐  Buyer Language Database updates: all PAIN-ACUTE, PAIN-CHRONIC, and DESIRE-HIDDEN phrases from the hack added to the Buyer Language Mining database
☐  Objection Bank updates: any FAQ questions from the hacked funnel that are not already in the Objection Bank added as new entries
☐  Funnel Hack Record created in Airtable
Quarterly Category Audit
☐  Q1: Full audit of top 3–5 funnels. New Funnel Hacking Reports completed. Category Synthesis Protocol questions answered.
☐  Q2: Facebook Ads Library audit for all watch list operators. New creative notes updated.
☐  Q3: Fresh opt-ins to top 3 competitor funnels. Email sequence changes documented.
☐  Q4: Offer architecture review of top 3–5 competitors. Offer changes noted.
☐  After each quarterly audit: Category Intelligence Record in Airtable updated with new principles and patterns
☐  After each quarterly audit: Any Category Principle changes that affect existing funnel SOPs flagged for SOP update review
Ongoing Weekly Watch List
☐  Every Monday (30 minutes): Facebook Ads Library check for all watch list operators
☐  New creatives: screenshot and add to the operator's folder. Note the hook type and creative format.
☐  Retired creatives: note which were retired. Long-running ad retirement may signal a funnel pivot.
☐  New social content: note any new mechanism language, new positioning, or new proof points appearing in organic content
☐  Trigger conditions reviewed: does any observation trigger a full funnel hack? If yes: schedule the full hack within 14 days
RISER Nation Master Operating System  |  Funnel Hacking Methodology SOP  |  Version 1.0  |  2026 Edition
Brunson  ×  Kennedy  ×  Halbert  |  risernation.com
The Extraction vs Replication Standard
The test for every insight extracted from a funnel hack:
Legal: Would the operator whose funnel you are studying be able to recognise their specific words, images, or assets in your output? If yes: replication.
Strategic: Are you deploying the underlying principle that made their approach work, or the surface-level execution of that principle? If surface-level: replication.
Ethical: Would you be comfortable if the operator whose funnel you studied read your output? If not: replication.

All funnel hacking work in the RISER Nation system operates by extraction only. No template, copy, image, or asset is ever used verbatim from a competitor's funnel.
Kennedy's Competitive Intelligence Principle
The best competitive research is not the most secret. It is the most systematic. Every operator in your category is running ads, publishing content, building funnels, and sending emails. The question is not whether to look — it is whether to look with a framework that extracts generalisable intelligence or to look without one and see only surface features.
Brunson's Funnel Hacking Insight
Most operators look at a competitor's funnel and say 'I could have done that.' A funnel hacker looks at the same funnel and asks: 'Why does this work? What problem in the buyer's decision-making process does each element solve? What would be different about the conversion rate if any one element were removed?' The answers to those questions are the intelligence. The surface elements are just the evidence.
Criterion
Standard
How to Confirm
Disqualifier
Evidence of significant paid traffic
The operator is running paid ads (Meta, Google, YouTube, TikTok) to the funnel at scale. Paid traffic at scale almost always indicates positive unit economics — meaning the funnel is working well enough to justify ongoing spend.
Facebook Ads Library: search the operator's page name for active ads. Google: search '[operator name] ads.' AdSpy, SpyFu, or SimilarWeb for estimated traffic volumes. Active ads running for 30+ days = significant paid traffic.
Funnel receives traffic exclusively from organic audience (existing email list, large social following). This type of funnel performs because of the audience, not the architecture — extracting copy patterns from it will produce misleading results.
Funnel has been running for at least 90 days
A funnel that has been live for fewer than 90 days may not have been optimised against real conversion data. A 12–36 month-old funnel represents tested, iterated architecture.
Check the Wayback Machine (web.archive.org) for the first cached version of the funnel URL. Facebook Ads Library shows the earliest date each ad was active.
Newly launched funnel. The copy and architecture may not yet reflect the operator's learnings from live conversion data. Flag for review in 90 days rather than hacking now.
Operator is generating meaningful revenue
A funnel from an operator who is not generating significant revenue from that funnel is not a useful intelligence source. The goal is to study systems that work at scale.
Social proof signals: large testimonial counts, public case studies, community size, team size indicators on LinkedIn, SimilarWeb traffic estimates. Kennedy's signal: operators who are still running the same funnel after 12 months are making money from it.
Operator with a small, newly built audience and a new funnel. Limited data about what is converting vs what was simply built first.
Operator is selling to your target avatar
The intelligence is only transferable if the funnel's target buyer overlaps significantly with your own. A funnel designed for B2C lifestyle buyers uses different copy patterns and different psychology than one designed for B2B operators.
Read the funnel's headline, the problem section, and the 'who this is for' section. Does the avatar description match your own? Is the problem section describing the same pain you are addressing?
Avatar mismatch. If the operator targets a fundamentally different audience (different industry, different sophistication level, different decision-making context), the psychological patterns may not transfer.
Funnel is at a comparable or higher price point
Copy patterns, guarantee architecture, and social proof density differ significantly between a $47 SLO and a $5,000 high-ticket programme. Hacking a $47 funnel to improve a $5,000 programme (or vice versa) produces mismatched insights.
The funnel's price point is usually visible on the checkout page or in the sales copy. If not: check the OTO pages.
Significant price mismatch. Insights from a $97 funnel are not directly applicable to a $3,000 funnel — and vice versa. Note the price tier and only apply insights within the same price psychology category.
Tool
Purpose
What It Surfaces
How to Use It
Facebook Ads Library (free)
Reveals every active and historical ad running from a specific Facebook page. Includes creative, copy, and — in some cases — targeting indicators.
Ad creative format (video vs image vs carousel), headline patterns, offer types (lead magnet, challenge, webinar, SLO, application), how long each ad has been running.
Search the operator's Facebook page name at facebook.com/ads/library. Filter by country. Sort by date to see which ads have been running longest (= most successful). Download screenshots of all active ads.
Wayback Machine (free)
Archives historical versions of web pages at web.archive.org. Shows how funnel pages have evolved over time.
Which elements have been added, removed, or changed. The original headline vs the current one (which is probably better — the current headline survived testing). Price changes. Offer additions.
Enter the funnel's URL into web.archive.org. Review the earliest cached version vs the current version. Changes made over 12+ months of operation represent tested optimisations.
AdSpy / Anstrex (paid)
Cross-platform ad intelligence tools that surface ads from multiple networks with engagement data.
Ad performance signals (likes, shares, saves), how long an ad has been running, which landing page it links to, targeting demographic indicators (where available).
Filter by your category keywords. Sort by run length (longest-running = most successful). Export the top-performing ads from the past 90 days.
SimilarWeb (freemium)
Estimates website traffic volume, traffic source breakdown, and top referring sites for any domain.
Whether paid or organic traffic is the primary source. Which ad platforms are driving traffic. Geographic distribution. Monthly visitor estimates.
Enter the funnel domain. Review: Traffic Sources section (paid vs organic vs direct vs referral), Top Referring Sites (other operators sending them traffic = JV relationships), and Traffic by Country.
Google Transparency Report (free)
Google's equivalent of the Facebook Ads Library for Google Search and Display ads.
Active Google ads including headlines, descriptions, and landing pages.
Search at adstransparency.google.com. Filter by advertiser. Export the currently active Google ads.
Hunter.io / MailTester (freemium)
Identifies the email platform a domain is using and, in some cases, email formats.
Which email platform the operator uses (Klaviyo, ActiveCampaign, ConvertKit, etc.), which signals likely email sophistication and automation capability.
Enter the domain. Review the MX records and email headers (visible in forwarded emails from opt-ins to the funnel).
The Operator's Own Content (free)
The operator's podcast appearances, YouTube channel, published case studies, and social media content reveal their messaging framework, proof points, and positioning — often more candidly than their funnel copy.
Mechanism language, parable subjects, proof metrics they share publicly, interview language about their avatar and their method.
Subscribe to their YouTube channel, listen to their most recent 2–3 podcast appearances, follow their primary social media account for 30 days before conducting the analysis.
The Analysis Email Address
Create a dedicated email address for all funnel hacking opt-ins: e.g., [yourbrand]-analysis@[yourdomain].com. All competitor opt-ins go to this address. Never use your primary business email — you want all analysis emails segmented separately from your business communications, and you do not want competitor email sequences to interfere with your deliverability metrics.
Step
Action
What to Capture
1. Opt in to the lead magnet or register for the free product
Use the analysis email address. Complete the opt-in form as a real prospect would. Note: form fields (what data is collected), social proof elements on the opt-in page, and the redirect destination.
Form field count and type. Opt-in page elements (headline, subheadline, bullet points, social proof). Redirect destination (sales page or thank-you page with OTO).
2. Go through the full funnel sequence
For a free funnel: opt in only. For an SLO or low-price funnel: purchase the entry product. For a high-ticket funnel: submit the application (do not book a discovery call — stop at the confirmation page). Complete every page you legitimately reach.
Every page URL. Every page's copy (screenshotted). Every order bump and OTO (screenshotted). Thank-you page and delivery mechanism.
3. Document the complete email sequence
Over the next 30 days: open every email from the operator to the analysis address. Screenshot every email. Note: subject lines, send timing, sequence structure, and CTA evolution across the sequence.
Subject lines (verbatim). Send timing (day-by-day or week-by-week). Content type per email (value, proof, mechanism, offer, urgency). CTA language. Email platform indicators (check the unsubscribe footer for ESP identification).
4. Purchase the SLO if one exists
If the funnel includes an SLO at $47 or below: purchase it. This is the most complete way to access the full funnel including all upsells, the thank-you page, and the buyer email sequence (which is different from the subscriber sequence).
Every upsell page. The order bump. The thank-you page delivery. The buyer onboarding sequence (different from the subscriber sequence — captures the full post-purchase architecture).
ANALYSIS STAGE 1
Ad Creative Analysis
Central question: What entry message is this funnel using to stop the scroll and generate a click?
What to capture
Every active ad creative: screenshots of static images, notes on video content (hook, body, CTA), carousel structure. Ad copy: headline, primary text, CTA button label. Targeting signals: which audiences does each ad appear in (interest-based, lookalike, broad)? Run length of each creative.
What it reveals
The entry hook — what specific pain, desire, or curiosity the operator is using to generate traffic. Whether the funnel is using a direct-response approach (specific promise, specific outcome) or a content/educational approach. The primary avatar being targeted (inferred from the hook language). Which creatives have been running the longest (= most successful).
How to apply it
The entry hook informs the PAIN-ACUTE selection for your own ad creative — not by copying it but by confirming that the hook category (pain, desire, curiosity, proof, or counterintuitive claim) resonates with the target avatar. Longest-running creatives identify which hook categories the market responds to.
ANALYSIS STAGE 2
Entry Page Analysis (Opt-in, Registration, or Sales Page)
Central question: What is the first conversion ask, and how does the page architecture support it?
What to capture
Complete screenshot of the entry page above and below the fold. Verbatim headline and subheadline. The bullet point structure and what each bullet promises (not the words — the promise type: result, process, or revelation). The CTA label. Social proof format and density. Page length. Any urgency mechanisms.
What it reveals
The specific promise that converts a cold visitor into an opt-in or a buyer. The promise architecture: whether the headline is result-focused, identity-focused, or curiosity-focused. What the operator believes is the highest-value offer they can make to a cold stranger in one page. The social proof format that the operator has converged on after testing (aggregate number vs specific story vs specific testimonial).
How to apply it
The promise architecture informs your own entry page headline testing — specifically confirming whether result-focused or identity-focused headlines are converting better in this category. The social proof format informs your own opt-in page design.
ANALYSIS STAGE 3
Application or Checkout Architecture
Central question: What does the commitment step look like — and how does the architecture increase it?
What to capture
For SLO funnels: full checkout page including all fields, order bump (verbatim or paraphrase), and the checkout design. For application funnels: the full application form structure (which questions, in what sequence, with what required minimums). For webinar/challenge funnels: the registration form fields and any pre-registration qualifying questions.
What it reveals
How much information the operator requires before they accept a lead or a buyer. The order bump positioning, copy structure, and price relationship to the main offer. For applications: which questions the operator uses to qualify — revealing their ideal client criteria and their most important qualification dimensions.
How to apply it
The order bump structure directly informs the Order Bump Design Standards in the SLO Funnel SOP and the Downsell Paths SOP. Application form question structure directly informs the Application Funnel SOP's Question Card design.
ANALYSIS STAGE 4
OTO / Upsell Page Analysis
Central question: What does the operator believe their buyer most wants immediately after the first purchase?
What to capture
Every OTO page encountered in sequence: verbatim headline, the bridge sentence (how the OTO connects to the primary purchase), the offer components, the price, the urgency mechanism, and the 'no' link language. Note the structure of the OTO stack: how many OTOs, in what price sequence (ascending or descending), and what topics each OTO covers.
What it reveals
The operator's theory of the buyer's next most urgent desire immediately after purchase. This reveals what the operator believes is the highest-value next problem in the avatar's journey. The OTO sequence price architecture reveals whether the operator is using an ascending stack (low-to-high) or a descending stack (high-to-low) — and the price relationships reveal their assumptions about buyer psychology at each point.
How to apply it
OTO stack architecture informs the order bump and upsell design in the SLO Funnel SOP and the Downsell Paths SOP. Specifically: what the operator believes the 'next problem' is after the entry product tells you what the most urgent sub-problem is in this market — which informs the core offer's mechanism positioning.
ANALYSIS STAGE 5
Sales Page Deep Analysis
Central question: What is the complete argument the operator makes for why the buyer should invest in this offer?
What to capture
Complete sales page architecture: headline, subheadline, problem section (paraphrased — not copied), mechanism section name and structure (how many components, what each is called), proof section structure (how many case studies, what format), offer stack (how many components, how value is presented), guarantee language and level, FAQ structure and which questions are addressed.
What it reveals
The operator's sales argument structure — the specific sequence of psychological moves they make from problem identification through to close. The mechanism naming convention and how many components it has. The guarantee level they are using (which signals their confidence in the offer and their refund rate tolerance). The objections they consider important enough to address in the FAQ.
How to apply it
The sales argument structure informs the VSL Script Template SOP — specifically the sequence of sections and the density of proof at each stage. The guarantee level informs the Guarantee Type Testing Protocol SOP's baseline for this price point in this category. The FAQ questions are added directly to the Objection Bank SOP as new entries to be investigated for Priority Score.
ANALYSIS STAGE 6
Proof Architecture Analysis
Central question: What proof patterns is the operator using — and how are they structuring the social evidence?
What to capture
Count of total testimonials visible. Testimonial format types present (text, video, screenshots, case studies, metrics-only). Testimonial positioning on the page (above the fold, after mechanism, after price, in FAQ). Whether testimonials are avatar-specific or result-specific or objection-specific. Aggregate proof statements ('500 operators have used this to achieve X'). Third-party credibility signals (press mentions, awards, partner logos).
What it reveals
The proof density the market appears to require before making a purchase at this price point. Whether the operator is leading with volume proof (many testimonials) or quality proof (a few highly specific case studies). Which avatar variations are represented in the proof — revealing which segments the operator considers most important to address. Which objections are addressed through proof (objection-matching) vs through FAQ text.
How to apply it
The proof architecture informs the Testimonial Version Registry's selection criteria for which testimonials to place on the sales page and in what sequence. Specifically: does the market respond to a few powerful case studies or to a large volume of shorter testimonials? Both approaches have worked in different categories — hacking multiple competitors in the category establishes which pattern dominates.
ANALYSIS STAGE 7
Email Sequence Analysis
Central question: What does the operator do with new subscribers and new buyers after the first touchpoint?
What to capture
Complete subscriber email sequence: every email subject line (verbatim), send timing, content type (value, proof, mechanism, story, offer, urgency, re-engagement). Complete buyer email sequence (if accessible through an SLO purchase). The transition point where the subscriber sequence shifts from value delivery to offer presentation. Email format patterns (plain text vs HTML, long vs short, personal vs broadcast).
What it reveals
The operator's content distribution framework — how they balance education, entertainment, trust-building, and conversion in the email channel. The timing cadence (daily, every-other-day, weekly) and what the cadence tells you about the operator's theory of buyer readiness. The subject line patterns that the operator has converged on (question-format, curiosity, proof, pain, direct). The transition moment from value to offer (which tells you how much trust the operator believes they need to build before converting).
How to apply it
The email sequence structure informs the Buyer Onboarding sequences and Nurture Sequences in every funnel SOP. Subject line patterns inform the email testing strategy in the monthly email review. The transition timing informs when to introduce the core offer in nurture sequences.
ANALYSIS STAGE 8
Copy Pattern Analysis
Central question: What specific language patterns and structures appear repeatedly across this funnel's copy?
What to capture
Headline structures (what formula type: result-for-avatar, how-to, contrast, question, number-list). Pain language patterns (specific words and phrases used to describe the problem). Mechanism language (how the solution is named and described — the naming convention and the number of components). Guarantee language (how the risk is reversed). Urgency language (how time sensitivity is created). CTA language (what words are used in buttons and offer-closing moments).
What it reveals
The copy conventions that the market has trained the operator to use. If a category leader has converged on specific headline formulas, specific guarantee language, or specific CTA words after years of testing — those patterns are market-validated. They work with this audience. The specific language patterns also reveal buyer language that can be fed into the Buyer Language Mining database.
How to apply it
The most valuable output of the copy analysis: 3–5 specific phrases from the operator's copy that feel like they mirror buyer language exactly. These are not copied into your funnel — they are added to the PAIN-ACUTE and PAIN-CHRONIC fields in the Buyer Language Mining database for use in your own original copy. Buyer language is not owned by anyone — it belongs to the buyers.
ANALYSIS STAGE 9
Offer Architecture Analysis
Central question: How is the offer designed — what does the operator include, exclude, and name?
What to capture
Offer name and any sub-brand or programme series naming. Number of components in the core offer stack. Each component named and described (paraphrase only — do not copy verbatim). Bonus structure (how many, what types, how valued). Price point. Payment plan options and their structure. What the offer specifically does NOT include (as stated in the copy or FAQ).
What it reveals
The operator's theory of what the ideal offer structure is for this avatar at this price point. The bonus types they have selected — which reveals which sub-problems they believe are most important to solve alongside the core promise. The stated exclusions — which are often as revealing as the inclusions, because they show what the operator has deliberately removed after finding it either too costly to deliver or not valued enough by buyers.
How to apply it
The offer architecture informs the MVO Playbook's Trim & Stack process and the Offer Stacking & Unbundling Strategy SOP. Specifically: how many components does a competitive offer in this category contain? What bonus types dominate? How is value stated? These parameters set the competitive baseline against which your own offer is designed.
ANALYSIS STAGE 10
Traffic and Distribution Analysis
Central question: Where is the operator getting their traffic — and what does their distribution strategy tell you about what works?
What to capture
SimilarWeb traffic source breakdown. Active ad platforms (Facebook Ads Library, Google Transparency Report). Podcast appearances (search the operator's name on Apple Podcasts / Spotify for guest appearances). YouTube channel subscriber count and top-performing videos. Email list size estimates (SimilarWeb direct traffic as a proxy). Affiliate or JV programme indicators (affiliate programme link in footer, affiliate-specific landing pages).
What it reveals
The operator's primary acquisition channels and their relative investment in each. Whether the funnel works primarily with warm traffic (existing audience) or cold traffic (paid ads). Which platforms the operator has chosen to invest in — and which they have abandoned (their ad history on the Facebook Ads Library shows past tests that were stopped). Whether the operator has built a JV network (affiliate programme = they believe their offer converts for other people's audiences).
How to apply it
The traffic analysis informs the traffic architecture section of each funnel SOP. Specifically: which paid platforms are the category leaders using, and for how long? A category leader who has been running Meta ads for 24+ months with consistent creative updates is confirming that Meta works for this audience. That is a traffic platform decision that does not need to be re-researched from scratch.
PHASE 1
The Copy Pattern Extraction System
Turning observed copy into transferable structural insights
Level
What Is Observed
Example
Output
Level 1 — Surface
The specific words and phrases in the copy.
Headline: 'How [Avatar Type] Are Getting [Specific Result] in [X] Days Without [Primary Fear]'
A headline to copy. Legally problematic if used verbatim. Strategically weak because it lacks your voice and mechanism.
Level 2 — Structure
The formula or pattern underlying the specific words.
Formula: Result + Avatar + Timeframe + Without + Primary Objection. A specific promise for a specific person with a specific timeframe and a specific objection handled.
A headline formula to apply with your own content. Legally sound. Strategically better than Level 1 because your voice and mechanism are intact.
Level 3 — Principle
The psychological reason why this structure works — what need or concern in the buyer's decision-making it addresses.
Principle: Buyers need to see that the result is achievable in a concrete timeframe (not 'eventually') and that their primary fear does not prevent it (the objection is pre-empted before it forms). The headline does both in one sentence.
A principle to apply across all copy — headlines, bullet points, email subject lines, guarantee language. Produces consistently better copy because every element is evaluated against the same underlying principle.
Pattern Family
What It Governs
What to Look For
Level 3 Principle
1. Headline Architecture
The structure of the primary headline on each page
Result + Avatar + Timeframe + Without / How-To + Result + Avatar / Number + Promise + Timeframe / Counterintuitive claim
What does the buyer need to believe first to engage with this funnel? The headline's job is to establish that first belief.
2. Problem Agitation Language
How the pain is described and amplified in copy
Specific vocabulary, metaphors used for the problem, whose fault it is (internal attribution vs external), the time dimension of the pain ('every day that passes...')
The intensity and specificity of pain language required to produce action. Markets with higher pain tolerance require higher agitation. Markets with lower tolerance convert on lighter problem description.
3. Mechanism Naming Convention
How the proprietary method is named
Number of components (3-step, 5-phase, 7-part), naming pattern (acronym, metaphor, proprietary name, borrowed concept), how the name differentiates from conventional approach names
What naming convention the category responds to. Some categories respond to sophisticated mechanism names; others respond to plain language ('the method' or 'the system').
4. Proof Framing
How case studies and testimonials are structured and positioned
Result first vs story first, metric specificity, avatar specificity, objection-matching, before/after structure, quote placement relative to the specific claim it supports
The minimum proof specificity required for this category. Categories with sophisticated, sceptical buyers require higher specificity (exact numbers, specific timelines) than less sophisticated categories.
5. Guarantee Architecture
The structure and boldness of the risk reversal
Guarantee level (unconditional, conditional, result-based), guarantee window (30/60/90 days), what the guarantee covers (refund, re-do, result guarantee), the confidence statement
How much risk the market expects to be removed before committing to a purchase at this price point. Higher price = more risk to reverse.
6. Urgency Mechanics
How scarcity and time-sensitivity are created and communicated
Cohort close (real date), founding pricing (real window), spot limits (real cap), bonus expiry (real deadline), countdown timers (static vs live)
Which urgency mechanisms the market trusts. Some markets have been burned by fake countdown timers and respond only to genuine cohort-based urgency.
7. CTA Language
The specific words used on buttons and close moments
Action verbs (Get, Start, Join, Apply, Claim, Access), object of the action (Your Copy, My Spot, Access, The Programme), price presentation at point of action
What identity the buyer is stepping into when they click. 'Apply' creates a different self-concept than 'Buy.' The CTA language signals what kind of purchase this is.
8. FAQ Objection Selection
Which objections the operator chose to include in the FAQ
Which objection types are included (price, fit, time, prior failure, partner), how they are ordered (most common first vs most blocking first), how they are answered (reframe vs evidence vs guarantee)
Which objections the operator considers most important to address publicly — these are almost certainly their highest-Priority-Score Objection Bank entries, confirmed by their real conversion data.
9. Pricing and Value Presentation
How the price and the value are presented relative to each other
Total stack value before price reveal, price contrast technique (what the price is compared to), payment plan presentation (before or after primary price), guarantee position relative to price
The value-to-price gap the category requires. Some categories convert at 3× stated value; others require 10× stated value before the price is revealed.
10. Email Subject Line Patterns
The recurring structures in the operator's email subject lines
Question vs statement vs one-word subject lines, curiosity gaps vs direct benefit statements, personalisation tokens, emoji usage, capitalisation
The subject line structures the market opens. Operators who have been running their email list for 3+ years have tested subject line patterns extensively — their current patterns are the survivors.
PHASE 2
The Funnel Hacking Report Template
Structuring the intelligence for actionable application
FUNNEL HACKING REPORT TEMPLATE — Complete one report per hacked funnel.
HEADER
Funnel Hack ID: [FH-[Operator Code]-[YYYY-MM]. e.g. FH-COMP01-2026-09]
Target Operator: [Name / Brand]
Date of Analysis: [Date]
Analyst: [Name]
Funnel Type: [SLO / Application / Webinar / Challenge / Book / Summit / Other]
Entry Product Price: $[  ]
Primary Offer Price: $[  ]
Estimated Monthly Traffic (SimilarWeb): [  ]
Ads Running Since: [Earliest Facebook Ads Library date]
Overall Assessment: [ ] Best-in-category [ ] Strong [ ] Average [ ] Weak (used primarily as a negative example)

PART 1 — AD CREATIVE INTELLIGENCE
Primary Hook Type: [ ] Pain-Acute [ ] Desire-Hidden [ ] Counterintuitive Claim [ ] Proof/Result [ ] Curiosity [ ] Question
Primary Hook (paraphrase — do not copy verbatim):
[Paraphrase the hook's core message in your own words]
Hook's Strongest Element:
[What makes this hook work? Specificity? Emotional resonance? Pattern interrupt?]
Creative Format: [ ] Static image [ ] Short video (under 60s) [ ] Long video (60s+) [ ] Carousel
Longest-Running Creative (described, not copied):
[Describe the creative elements: what is shown, what emotion is evoked, what claim is made]
Key Ad Copy Insight:
[The single most transferable insight from this operator's ad approach — described as a principle, not a surface feature]
Buyer Language Extracted (add to Buyer Language Mining database):
1. [Phrase 1 — verbatim from ad copy if it reads as buyer language]
2. [Phrase 2]
3. [Phrase 3]

PART 2 — ENTRY PAGE INTELLIGENCE
Headline Formula: [Describe the formula type used, not the verbatim headline]
Above-the-Fold Architecture:
[Describe what is visible without scrolling: layout, elements, visual hierarchy]
Primary Promise Type: [ ] Result + Timeframe [ ] Identity shift [ ] Secret/Revelation [ ] How-to
Lead Magnet / Entry Product Type: [Describe the format and value proposition type]
Social Proof Format: [Number of testimonials, format, specificity level]
Key Entry Page Insight:
[The single most transferable insight from this page — as a principle]
Buyer Language Extracted:
1. [Pain phrase]
2. [Desire phrase]

PART 3 — CONVERSION ARCHITECTURE INTELLIGENCE
Order Bump Structure (if present): [Price, what it is, one-sentence description]
OTO 1 Structure: [Price, what it is, bridge approach, urgency mechanism]
OTO 2 Structure (if present): [Price, what it is]
Downsell (if present): [Price, positioning]
Total Funnel ACV Estimate: $[  ]
Key Conversion Architecture Insight:
[The single most transferable insight — as a principle]

PART 4 — SALES PAGE / AUTHORITY PAGE INTELLIGENCE
Mechanism Name: [Their mechanism name — for reference only. Not to be used.]
Mechanism Component Count: [Number]
Mechanism Component Names: [Paraphrase, not verbatim. What category does each name fall into?]
Proof Count: [Total testimonials visible]
Proof Format Distribution: [X% text, X% video, X% screenshot, X% case study]
Proof Positioning: [Where on the page? Before price? After mechanism? In FAQ?]
Guarantee Level: [ ] Unconditional [ ] Conditional [ ] Result-based [ ] Anti-guarantee
Guarantee Window: [X days]
FAQ Question Count: [  ]
FAQ Objection Types Addressed: [List the objection types, matched to Objection Bank categories]
Key Sales Page Insight:
[The single most transferable insight — as a principle]
Objection Bank Entries to Add:
1. [Objection type + verbatim or paraphrased objection language]
2. [Continue]

PART 5 — EMAIL SEQUENCE INTELLIGENCE
Sequence length observed: [X emails over X days]
Sequence structure (summarise in one sentence per email):
Day [X]: [Content type + CTA type]
[Continue for each email observed]
Subject line patterns observed:
Pattern 1: [Describe the formula — e.g., 'One-word subject lines. Product of the sender's familiarity with the list.']
Pattern 2: [Continue]
Transition point (when does the sequence shift from value to offer?): Day [X]
Key Email Sequence Insight:
[The single most transferable insight — as a principle]

PART 6 — COPY PATTERN FINDINGS
For each of the ten copy pattern families, note the pattern used and the Level 3 principle extracted:

1. Headline Architecture: [Pattern observed] → [Level 3 principle]
2. Problem Agitation: [Pattern observed] → [Level 3 principle]
3. Mechanism Naming: [Pattern observed] → [Level 3 principle]
4. Proof Framing: [Pattern observed] → [Level 3 principle]
5. Guarantee Architecture: [Pattern observed] → [Level 3 principle]
6. Urgency Mechanics: [Pattern observed] → [Level 3 principle]
7. CTA Language: [Pattern observed] → [Level 3 principle]
8. FAQ Objection Selection: [Pattern observed] → [Level 3 principle]
9. Pricing and Value Presentation: [Pattern observed] → [Level 3 principle]
10. Email Subject Line Patterns: [Pattern observed] → [Level 3 principle]

PART 7 — OFFER ARCHITECTURE FINDINGS
Offer component count: [  ]
Bonus types present: [List: template / coaching / community / tool / swipe file / other]
Bonus count: [  ]
Price point: $[  ]
Value stated before price reveal: $[  ] (stated value ÷ price = [X]× ratio)
Offer exclusions noted (what the offer explicitly does NOT include):
[Note anything the operator says is NOT included — these deliberate exclusions often reveal what was once included but removed after refund analysis]
Key Offer Architecture Insight:
[The single most transferable insight — as a principle]

PART 8 — TRAFFIC AND DISTRIBUTION FINDINGS
Primary Traffic Sources: [ ] Paid Meta [ ] Paid Google [ ] YouTube [ ] TikTok [ ] Organic [ ] JV / Affiliate
Estimated Traffic Volume: [Monthly estimate from SimilarWeb]
Longest-Running Ad Platform: [Platform + approximate tenure from Ads Library dates]
JV / Affiliate Programme: [ ] Yes [ ] No
Key Traffic Insight:
[The single most transferable insight — as a principle]

PART 9 — BUYER LANGUAGE DATABASE UPDATE
List all phrases extracted from this funnel hack that should be added to the Buyer Language Mining database:
PAIN-ACUTE additions: [Phrases verbatim if they read as buyer language — not marketing copy]
PAIN-CHRONIC additions: [Phrases]
DESIRE-HIDDEN additions: [Phrases]
Objection Bank additions: [New objection entries with type classification]

PART 10 — TOP 5 ACTIONABLE INSIGHTS
// These are the five most important findings from this funnel hack, each expressed as a specific action the RISER Nation operator should take.
1. [Finding stated as an action: 'Test [specific change] to [specific page/element] based on this operator's pattern of [specific observation].']
2. [Continue]
3. [Continue]
4. [Continue]
5. [Continue]

Overall Assessment Summary (3–5 sentences):
[What is the most important thing this funnel hack confirms, challenges, or reveals about the category? What did you expect to find that you did not? What surprised you?]
PHASE 3
The Synthesis Protocol — From Intelligence to Decisions

Synthesis Level
Input
Output
Decision Trigger
Level 1 — Single Funnel Finding
One completed Funnel Hacking Report
Specific hypotheses about what might work in your funnel, based on what is working in one competitor's funnel. Minimum confidence — one data point.
A/B test hypothesis. One element to test in your funnel based on this funnel's approach. Low confidence — test before deploying.
Level 2 — Category Pattern
Three or more Funnel Hacking Reports from funnels serving the same avatar at a comparable price point
A pattern confirmed across multiple high-performing funnels. Medium confidence — the market has spoken through multiple operators' testing.
An element to deploy (not just test) in your funnel with confidence. Still monitor performance, but the category pattern is strong enough evidence to implement without extensive prior testing.
Level 3 — Category Principle
Five or more Funnel Hacking Reports + your own funnel performance data showing the same pattern converts in your funnel
A principle that governs conversion architecture in this category. High confidence — confirmed across multiple independent data sources.
A foundational design decision for all future funnel work in this category. Update the relevant RISER Nation SOPs to reflect the category-validated principle.
CATEGORY SYNTHESIS QUESTIONS
CONVERGING PATTERNS (patterns present in 3+ of the hacked funnels)
1. What headline formula type appears most consistently across the category's highest-performing funnels?
2. What proof format and density appears most consistently?
3. What guarantee level and structure appears most consistently at this price point?
4. What is the typical number of email sequence elements before the offer is introduced?
5. What are the most common objection types addressed in the FAQ sections? (Add any new ones to the Objection Bank.)
6. What mechanism naming convention dominates — and what does that tell you about the buyer's sophistication level?
7. What is the typical value-to-price stated ratio in the offer stack presentations?

DIVERGING PATTERNS (patterns that vary significantly across hacked funnels)
1. Which funnel elements show the most variation? (Divergence may indicate an area where differentiation is possible.)
2. What does the highest-performing funnel do differently from the others? (Their differentiation is likely intentional — what problem does it solve?)
3. What do the underperforming funnels have in common that the top performers do not?

GAPS AND OPPORTUNITIES
1. Is there a promise, mechanism, or proof type that is absent from all hacked funnels but that the Buyer Language Mining database suggests buyers want?
2. Is there a guarantee level that is more generous than what any category competitor offers? (A category where all operators offer 30-day money-back is a category where a 60-day result guarantee is a differentiator.)
3. Is there a buyer language pattern from Q&A sessions, forums, or support tickets that no competitor's copy addresses directly? (Unaddressed language = an opening.)

CATEGORY PRINCIPLE STATEMENTS (consolidate findings into principles)
// Write 3–5 one-sentence principles that capture the most important category-level findings.
// Example: 'In this category, proof density above [X testimonials] does not increase conversion — specificity of individual testimonials matters more than volume.'
// Example: 'Mechanism names in this category follow a [naming convention] — departing from this convention requires additional explanation of the mechanism's nature.'
Principle 1: [  ]
Principle 2: [  ]
Principle 3: [  ]
Principle 4: [  ]
Principle 5: [  ]
PHASE 4
The Quarterly Category Audit Cadence
Keeping competitive intelligence current in a changing market
Quarter
Audit Focus
Time Investment
Output
Q1 — Full Category Audit
Complete new funnel hacks on the top 3–5 funnels in the category. For each: complete Funnel Hacking Report. Run the Category Synthesis Protocol.
8–16 hours total for the full audit
Updated Category Principles document. New Buyer Language Mining database entries. New Objection Bank entries. Updated funnel SOP recommendations.
Q2 — Ad Creative Monitor
Review the Facebook Ads Library for all tracked competitors. Screenshot all new creatives and note the retirement of old ones. Which hooks have been replaced? What does the new creative tell you about what stopped working?
2–3 hours
New creative intelligence notes. Updated Hook Analysis for the Ad Creative Brief Template (SLO Funnel SOP Phase 1 and Challenge Funnel SOP Phase 4).
Q3 — Email Sequence Refresh
Re-opt-in to the top 3 competitor funnels with a fresh analysis email address. Map the new email sequence structure. Compare to the Q1 baseline — what has changed?
4–6 hours
Updated email sequence intelligence. New subject line patterns. Updated Email Sequence Architecture section in relevant funnel SOPs.
Q4 — Offer Architecture Review
Review the current offer stacks of top 3–5 competitors. Have new bonuses been added? Have components been removed? Have prices changed? Have guarantee levels changed?
3–5 hours
Updated Offer Architecture Intelligence. New inputs for the Offer Stacking & Unbundling Strategy SOP and the Guarantee Type Testing Protocol SOP.
COMPETITOR WATCH LIST TEMPLATE
WATCH LIST OPERATORS (6–10 names)
Operator 1: [Name] — Primary Funnel Type: [Type] — Current Entry Offer: $[  ] — Ad Platforms Active: [  ]
Operator 2: [  ]
[Continue for all watch list operators]

WEEKLY REVIEW ITEMS (30 minutes every Monday)
1. Facebook Ads Library check: any new ads launched by any watch list operator in the past 7 days?
2. New creative format? New hook type? New offer type?
3. Any ads retired that had been running for 30+ days? (Retirement of a long-running ad = the operator may be pivoting)
4. Any social media posts from watch list operators containing new mechanism language, new results, or new positioning?

TRIGGER CONDITIONS FOR A FULL FUNNEL HACK
// The following events should trigger an immediate full funnel hack of the relevant operator:
[ ] A new funnel type launched (different from their established funnel — e.g., they were SLO-based and launched a challenge)
[ ] A significant price change (more than 20% up or down on their primary offer)
[ ] A new mechanism name or naming convention visible in ads or content
[ ] Evidence of significant scaling (ad spend appearing to increase dramatically based on increased creative volume)
[ ] A public announcement of a rebrand, pivot, or programme restructure

MONTHLY INTELLIGENCE UPDATE
Date: [  ]
Watch list changes (operators added or removed): [  ]
Notable category developments this month: [  ]
Actions triggered: [  ]
Question
Pass
Fail — Required Action
1. Originality Test: If the operator whose funnel you studied read this output, would they recognise their specific words, phrases, images, or structural elements in it?
No — the output uses different words, different images, and different structure. Only the underlying principle has been applied.
Yes — stop. Rewrite from the Level 3 principle, not from the specific execution observed. If an image is being reused: commission an original image. If copy is being reused: rewrite in your own voice addressing the same buyer concern.
2. Authority Test: Would this output be more effective WITH the competitor's specific elements, or is it actually better when you apply the principle with your own voice, mechanism, and buyer language?
Your own voice + your mechanism + your buyer language > their copy in your context. This is almost always true.
The output is weaker when you apply your own elements. This is a signal that you are extracting too little value from the funnel hack — you are copying rather than learning. Go back to the Level 3 principle and re-extract.
3. Sourcing Transparency Test: If a client asked 'where did the idea for this element come from?' — could you explain the full process (you observed a category pattern, extracted the underlying principle, and applied it with your own content) without any discomfort?
Yes — the process is transparent and defensible. The principle, not the specific execution, was borrowed.
No — there is something in the output that you would not be comfortable explaining fully. Remove or replace that element.
The Specific Prohibitions
The following actions are prohibited within the RISER Nation funnel hacking methodology, regardless of the perceived competitive pressure or time constraint:

1. Reproducing any headline, subheadline, or copy section verbatim from a competitor's funnel in your own marketing materials.
2. Using any competitor's images, graphics, or video content without permission.
3. Representing a competitor's testimonials or case studies as your own.
4. Using a competitor's mechanism name in your own marketing — even with attribution.
5. Purchasing a competitor's programme with the intent to use the programme content rather than to study the funnel architecture. This is theft of intellectual property, not competitive intelligence.
6. Opt-ing in to a competitor's funnel under a false identity or with the intent to disrupt their business processes.
Field
Type
Notes
Funnel Hack ID
Short text
Format: FH-[Operator Code]-[YYYY-MM]. e.g. FH-COMP01-2026-09
Target Operator Name
Short text
Target Operator Website
URL
Date of Analysis
Date
Analyst
Short text
Funnel Type
Single select
SLO / Application / Webinar / Challenge / Book / Summit / VSL / Hybrid
Entry Product Price
Currency
Primary Offer Price
Currency
Estimated Monthly Traffic (SimilarWeb)
Number
Ads Running Since
Date
Earliest date in Facebook Ads Library
Active Ad Platforms
Multi-select
Meta / Google / YouTube / TikTok / LinkedIn
Primary Traffic Source
Single select
Paid / Organic / Mixed — paid dominant / Mixed — organic dominant
JV Programme Active
Checkbox
Overall Funnel Assessment
Single select
Best-in-category / Strong / Average / Weak
Primary Hook Type
Single select
Pain-Acute / Desire-Hidden / Counterintuitive / Proof/Result / Curiosity / Question
Headline Formula Type
Single select
Result+Avatar / How-To / Counterintuitive / Number+Promise / Identity Shift / Other
Proof Format Dominant
Single select
Text testimonials / Video testimonials / Case studies / Screenshots / Mixed
Proof Count
Number
Guarantee Level
Single select
None / Unconditional / Conditional / Result-based / Anti-guarantee
Guarantee Window (days)
Number
Email Sequence Length (days observed)
Number
Offer-to-Value Ratio
Number
Total stated value ÷ offer price
Mechanism Component Count
Number
OTO Count
Number
Estimated ACV
Currency
Top 5 Actionable Insights
Long text
From Part 10 of the Report
Category Principles Updated
Checkbox
Were any Category Principle statements updated or added based on this hack?
Buyer Language Entries Added
Number
Count of new entries added to the Buyer Language Mining database from this hack
Objection Bank Entries Added
Number
Count of new Objection Bank entries triggered by this hack
Full Report Link
URL
Google Drive link to the completed Funnel Hacking Report document
Watch List Status
Single select
On watch list / Removed from watch list / Never on watch list
Next Scheduled Hack Date
Date
Notes
Long text
Observations that did not fit into structured fields
Field
Type
Notes
Category ID
Short text
Format: CAT-[Topic Code]. e.g. CAT-OFFERS
Category Name
Short text
Last Full Audit Date
Date
Funnel Hacks in This Category
Link → Funnel Hack Records
All hacked funnels in this category
Dominant Headline Formula
Short text
The formula type that appears most frequently in this category
Dominant Proof Format
Single select
Category Baseline Proof Count
Number
Average number of testimonials on the sales page of strong funnels
Dominant Guarantee Level
Single select
Category Baseline Guarantee Window
Number
Modal guarantee window in days
Category Baseline Value-to-Price Ratio
Number
Typical stated value ÷ offer price in this category
Typical Email Sequence Length Before Offer
Number
Days
Dominant Traffic Platform
Single select
Meta / Google / YouTube / TikTok / Organic / Mixed
Category Principle 1
Short text
Category Principle 2
Short text
Category Principle 3
Short text
Category Principle 4
Short text
Category Principle 5
Short text
Copy Pattern Exceptions
Long text
Documented cases where a top performer violates a category pattern — and what seems to be the reason
Competitor Watch List (active)
Long text
Names and monitoring status of all watch list operators in this category
Last Watch List Update
Date

Assigned source documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx — source 1 ·

JV deal structures: calculate fair commissions and explicit responsibilities

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

Video placeholder

Record the section scripts with a worked commission ledger and attribution scenarios.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx

Curriculum outline

Make the commercial promise independently calculable
Define gross, net and collection risk before quoting a rate
Choose among five structures
Work the one-time, installment, refund and EPC examples
Separate recurring credit from a payout
Set exact launch tiers and retroactive boundaries
Resolve all six attribution cases before launch
Teach evergreen qualification and retention separately
Design leaderboard rules and reconcile the worked economics
Correct the reciprocal-value ratio
Distinguish promotion from licensing rights
Complete the written agreement and reconcile conflicting dates
Evaluate four negotiation requests and five program limits
Use the schema and checklists to audit the deal
Calculate the incremental value of crossing a tier
Make the deal record sufficient to reproduce a statement

1. Make the commercial promise independently calculable

A durable partnership starts with a deal both parties can calculate independently. Define what the partner contributes, what counts as a qualifying result, what revenue is eligible, when credit becomes payable and what happens when money is refunded. Warm relationships do not remove the need for clear records.

Connect Brunson’s audience-relationship approach to an offer that genuinely fits the partner’s audience. Connect the Hormozi value framework to the actual outcome and delivery burden. Commission generosity cannot rescue poor buyer fit or unsustainable fulfillment. Evaluate partner earnings and operator contribution after costs together. The source’s Kennedy attribution is retained as a source attribution rather than a verified quotation.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-Dream-100-Strategy-SOP.docx · RISER-Affiliate-Program-Architecture-SOP.docx

Original source table 1 — includes source claims qualified above

The Deal Structure Is a Communication of Values, Not Just a Commercial FormulaKennedy's observation on partnership deals: the commercial terms an operator proposes in a JV arrangement communicate their values about the relationship more clearly than any relationship management gesture. An operator who proposes fair terms, with transparent calculation methodology, without hiding disadvantageous clauses in complexity, is communicating that they treat partnerships as long-term relationships — not transactions to optimise once. An operator who proposes complex terms designed to maximise their own take at the partner's expense will close a deal but will not develop a partnership.

2. Define gross, net and collection risk before quoting a rate

Gross is the buyer’s transaction amount. The source’s standard commission basis subtracts payment processing fees, then handles actual refunds through reversals. State taxes, discounts, disputes, reserves and any other deductions explicitly if applicable. Do not subtract a forecast refund allowance and then reverse actual refunds without a reconciliation rule.

The opening forty-percent example mixes a three-percent processing assumption, an unsupported two-percent refund benchmark and an unspecified reserve. Its approximately $370 outcome cannot be reproduced from fully defined inputs. Use actual agreed deductions instead. A percentage without its base is not an intelligible compensation promise.

For payment plans, distinguish three approaches: full commission up front, commission on each collected installment, or a hybrid advance and later payments. The first places more collection risk on the operator; the second ties partner earnings to collections; the hybrid shares timing and collection risk. The source’s default is per collected payment. Its three payments of $333 total $999, not $997, so the written offer must state the actual plan total.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx

Original source table 2 — includes source claims qualified above

The Gross vs Net Distinction — The Most Misunderstood Commission ConceptThe single most common source of commission disputes in the knowledge business JV ecosystem: the operator advertises a commission rate on 'sales' without specifying whether that means the gross transaction value or the net revenue after payment processing fees, refunds, and chargebacks. A 40% commission on a $997 sale is $398.80 on gross. The same 40% on net (after 3% payment processing fee, the industry-standard 2% refund rate, and the chargeback reserve) is approximately $370 — a $28 difference per sale that, multiplied across 50 sales, is $1,400 of commission the partner did not expect to have deducted. The RISER Nation standard is to state commissions on net revenue after payment processing and confirmed refunds — and to state this explicitly in every deal.

Original source table 3 — includes source claims qualified above

The Payment Plan Attribution ProblemA buyer who purchases a $997 programme on a 3-payment plan of $333/month presents a specific attribution challenge. The affiliate who referred this buyer generated a $997 sale commitment — but the operator only collects $333 in month one. Three solutions exist: (1) Pay the full commission immediately on the first payment (the operator takes the collection risk); (2) Pay commission only on each collected payment (the affiliate takes the collection risk); (3) Pay a portion on the first payment and the remainder as subsequent payments are collected (shared collection risk). The RISER Nation standard is Option 2 — commission is paid on each collected payment — and this must be stated explicitly in the deal terms before any payment plan is offered.

3. Choose among five structures

Percentage revenue share works when compensation should track eligible sales value. A fixed amount per qualifying action caps the unit payment but does not guarantee total income: no qualifying actions can mean no fee. Define a valid sale, opt-in or booked call and invalidation rules. A fixed sponsorship placement fee is a different arrangement that pays for an agreed placement.

A hybrid pays a guaranteed base for completed promotional work plus a share above a defined threshold. Use it only when the expected economics can justify the base even with weak sales. A reciprocal arrangement exchanges audience access; compare fit and likely outcomes rather than list size alone. A partner with a smaller list can receive greater exposure from the larger partner, contrary to the source table’s reversed explanation.

A tiered launch increases rates at stated milestones and may add prizes. Define whether rates apply only above a threshold or retroactively to all eligible sales. The table preserves suitability and exclusions for each structure. Choose based on contribution, risk, measurable results and the relationship context rather than a headline commission percentage.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-JV-Email-Swap-SOP.docx · RISER-Co-Launch-Partner-Launch-SOP.docx

Original source table 4 — includes source claims qualified above

Structure Type	How It Works	Best Suited For	Commission Calculation Basis	When NOT to Use
Structure 1 — Percentage Revenue Share (the standard)	The partner receives a defined percentage of the net revenue from every sale they refer. The percentage is fixed for the duration of the arrangement.	Standard affiliate relationships, evergreen programme promotions, and most launch JV deals where the partner's contribution is measured by sales generated.	Net sale price after payment processing fees and confirmed refunds. Payment plan: each collected payment × commission rate.	When the partner has minimal audience overlap with the offer's buyer profile and the operator wants to ensure effort is rewarded rather than results (which the partner cannot fully control). A flat fee better serves this context.
Structure 2 — Flat Fee per Action	The partner receives a fixed dollar amount for each qualifying action — a sale, a confirmed opt-in above a certain threshold, or a booked call. The amount is fixed regardless of the transaction size.	Larger list owners who prioritise income predictability over upside participation, paid newsletter sponsorship slots, and deals where the operator wants to cap the commission cost regardless of the offer's price variations.	Per confirmed sale, per confirmed opt-in above a defined threshold, or per booked call — the qualifying action is specified explicitly.	When the offer has variable pricing (payment plans, upsells, downsells) that make a fixed per-sale amount inequitable if the partner's referred buyers systematically choose higher or lower price points.
Structure 3 — Hybrid (flat fee + percentage)	The partner receives a flat base fee (guaranteeing minimum income from the promotion regardless of results) plus a percentage of sales above a defined threshold.	Dream 100 Tier 1 partners who are taking a meaningful promotional risk by committing significant audience exposure, and whose contribution justifies both a guaranteed element and an upside participation element.	Base fee: paid on the completion of the agreed promotional activity (the email was sent, regardless of results). Percentage component: on net sales above the agreed threshold.	When the relationship is in its early stages and the operator cannot confidently project whether the base fee is economically justified by the expected results.
Structure 4 — Reciprocal (audience-for-audience)	No money changes hands. Both parties promote each other's resource to their respective lists and the value exchange is the audience access.	JV email swaps, content collaboration, and cross-promotion deals where both lists are broadly comparable in size and engagement quality.	No monetary calculation. The value of the arrangement is the estimated opt-in volume each party receives. Equity is assessed by list size × engagement rate × avatar alignment.	When lists are significantly different in size (more than 3× differential) — the operator with the smaller list is receiving significantly less value. A hybrid structure (reciprocal promotion plus a value offset) is more appropriate.
Structure 5 — Tiered Leaderboard (launch competition)	Commission rate increases as the partner reaches sales volume milestones during a launch window. A competitive leaderboard motivates maximum promotional effort. Bonus prizes awarded to the top performers.	Live launch JV events with multiple affiliates where the operator wants to maximise overall launch volume and the competitive element motivates extra promotional effort from top performers.	Base tier: standard percentage on first X sales. Tier 2: higher percentage on sales above X. Tier 3: higher still above Y. Leaderboard bonus: additional cash prize for top 1, 2, 3 positions.	Evergreen promotions where there is no defined launch window — a leaderboard without a deadline creates a diffuse, low-urgency structure that does not motivate concentrated promotional effort.

4. Work the one-time, installment, refund and EPC examples

Under the source’s illustrative fee assumption of 2.9% plus $0.30, a $997 payment has a rounded $29.21 processing fee and $967.79 commission base. At thirty-five percent, commission rounds to $338.73. Thirty-five percent of gross would be $348.95, a $10.22 difference. This is a source calculation example, not a claim about every account’s current fees.

For each $333 installment, the same assumed fee rounds to $9.96, leaving $323.04 and a $113.06 commission. Three collected installments pay $339.18, forty-five cents more than the one-time example. The gross totals differ and three fixed fees apply, so the source’s claim of the same total commission is incorrect. Specify transaction-level rounding and reconcile it consistently.

At an assumed three-percent refund rate, three refunds per hundred initial sales reverse $1,016.19 of commission, leaving $32,856.81, or about $328.57 per initial sale. This is a scenario, not an established refund benchmark. For 500 clicks and fifteen initial sales, pre-refund commission EPC is approximately $10.16; using the scenario’s post-refund expected commission gives about $9.86. Label the cohort, attribution period, actual versus expected refunds and click denominator.

Refunds can leave original payment processing costs with the operator. Keep those expenses in the cash reconciliation even if the affiliate’s commission is fully reversed. Use the processor terms for the actual region, payment method and account before an operational calculation.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx

Stripe — account and region dependent payment pricing · Stripe — refund processing fee guidance

Original source table 5 — includes source claims qualified above

THE RISER NATION COMMISSION CALCULATION — Full worked exampleTHE INPUTSGross transaction value (the price the buyer paid): $997.00Payment processing fee (Stripe standard rate: 2.9% + $0.30 per transaction): $997 × 2.9% + $0.30 = $29.21Net transaction value: $997.00 - $29.21 = $967.79FOR A ONE-TIME PAYMENT — Commission CalculationCommission rate: 35%Commission amount: $967.79 × 35% = $338.73// Note: some operators calculate on gross ($997 × 35% = $348.95). The RISER Nation standard is net.// The difference is $10.22 per sale. State explicitly which basis applies.FOR A 3-PAYMENT PLAN ($333/month × 3 payments)Payment 1 collected: $333.00 → net: $333 - ($333 × 2.9% + $0.30) = $333 - $9.96 = $323.04Commission on Payment 1: $323.04 × 35% = $113.06Payment 2 collected: $333.00 → net: $323.04Commission on Payment 2: $113.06Payment 3 collected: $333.00 → net: $323.04Commission on Payment 3: $113.06Total commission if all 3 payments collected: $339.18// This is the same effective rate as the one-time payment — payment plan does not change the total commission if all payments are collected.THE REFUND IMPACTRefund rate for this offer: 3%Expected refunds per 100 sales: 3Commission reversed per refund: $338.73Expected commission reversals per 100 sales: 3 × $338.73 = $1,016.19Net commission per 100 sales after refunds: (100 × $338.73) - $1,016.19 = $32,856.81Average effective commission per sale after refunds: $32,856.81 ÷ 100 = $328.57THE EPC CALCULATION (Earnings Per Click — the primary partner evaluation metric)Total clicks from the partner's promotional send: 500Total confirmed sales attributed to those clicks: 15Gross EPC: ($338.73 × 15) ÷ 500 = $10.16 per clickNet EPC (after refunds): ($328.57 × 15) ÷ 500 = $9.86 per click// When communicating EPC to prospective partners: use net EPC after refunds. Gross EPC overstates the partner's expected earnings.

5. Separate recurring credit from a payout

Recurring commission is earned according to successful eligible billing events, not merely an active-looking subscription record. The source proposes the same percentage initially and on renewal, with credit on the third business day after successful billing. A failed charge generates no credit until an eligible payment is actually collected.

Cancellation stops future eligible billings; it is distinct from refunding an earlier payment. The source does not reverse earned past-month commission merely because the buyer cancels. A refund or dispute can still require the agreed reversal. Keep earned, pending, held, reversed and paid amounts separate.

The source’s default is a consistent rate and no lifetime cap. A declining rate, such as thirty percent for three months and twenty thereafter, or a cap must be agreed before referral. A credit date is not the bank payout date. Define payout eligibility, refund holds and any delayed collection rather than treating the third business day as a guaranteed cash transfer.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-Customer-Success-Retention-Systems-SOP.docx

Original source table 6 — includes source claims qualified above

Recurring Commission Element	Standard Calculation	RISER Nation Configuration
Initial purchase commission	The commission on the first payment (the enrolment) — typically the same rate as the monthly recurring commission, though some operators pay a higher initial commission and a lower recurring rate.	Same rate for initial and recurring: [commission rate]% of each net billing amount. Stated explicitly in the deal terms.
Monthly recurring commission	Calculated on each successful monthly billing event. Failed billing events (insufficient funds, expired card) do not trigger a commission.	Commission calculated and credited on the 3rd business day after each successful billing cycle. Failed payments: no commission credited.
Commission on cancellations	When a subscriber cancels: the commission stops from the cancellation date. Any previously paid commission is not reversed (the partner earned the commissions for the months the subscriber was active).	No retroactive reversal on cancellations. Commission credited only for active billing months.
Commission rate structure — same vs declining	Some operators pay a declining rate: 30% on the first 3 months, 20% thereafter. This incentivises referrals while limiting the operator's long-term commission liability.	RISER Nation standard: consistent rate for all months. If a declining rate is used: this must be stated explicitly and agreed in writing before the first referral is made.
Lifetime cap (if applicable)	Some operators apply a total lifetime commission cap per referred subscriber — the partner earns commission until the referred subscriber has generated X× their commission in revenue.	RISER Nation standard: no lifetime cap unless specifically agreed for a specific deal. The standard position is that the referring partner earns commission as long as the subscriber remains active.

6. Set exact launch tiers and retroactive boundaries

The source proposes a base of thirty to thirty-five percent, an active launch tier of thirty-five to forty percent requiring at least two promotional emails AND at least five confirmed sales, and a super tier of forty to forty-five percent at at least twenty sales. These are ranges to choose from, not complete terms. State an exact rate, qualifying sale definition and whether the fifth or twentieth sale triggers the upgrade.

An eligible retroactive upgrade changes the rate on every eligible sale from that partner in the stated launch cohort. When a partner moves from eighteen to twenty sales, separate commissions on the two new sales from the rate uplift on the eighteen earlier sales. The source’s explanatory passage incorrectly calls $997 net even though its worked net base is $967.79.

Preannounce the top-three prizes and all qualification rules. The source variously says at least five or twenty and above five or twenty; those boundaries must be reconciled in the specific agreement. Launch forty-to-forty-five-percent proposals also differ from the evergreen forty-percent ceiling. Preserve the distinction rather than implying one universal maximum.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-Co-Launch-Partner-Launch-SOP.docx · RISER-Affiliate-Asset-Creation-Checklist-SOP.docx

Original source table 7 — includes source claims qualified above

PHASE 1The Launch JV Deal Structure — In Full DetailThe commercial architecture for live launch joint venture promotions

Original source table 8 — includes source claims qualified above

Launch Phase	Commission Rate	Qualifying Sales	Notes
Standard Affiliate Base Rate (Tier 1)	30–35% of net sale price	All confirmed sales through the launch window	Available to all approved affiliates in the standard tier. No minimum sales volume required to participate at this tier.
Active Launch Promoter Rate (Tier 2)	35–40% of net sale price	Partners who have sent at least 2 promotional emails during the launch window AND generated at least 5 confirmed sales	The upgraded rate is applied retroactively to ALL sales from the first sale — not only to sales above 5. Retroactive application creates a motivation to reach the milestone threshold quickly.
Super Affiliate Rate (Tier 3)	40–45% of net sale price	Partners who have generated at least 20 confirmed sales during the launch window	Applied retroactively to all sales from this partner. The tier 3 threshold is ambitious — set it at a level that requires genuine promotional effort from the partner's best-performing list sends.
Leaderboard Bonus (Top 3)	Cash prize above and beyond commission	Top 3 positions on the launch sales leaderboard	1st place: $[X] — 2nd place: $[Y] — 3rd place: $[Z]. Scale these to the launch size: for a $200K launch, 1st place $1,500–$3,000 is typical. The prize must be meaningful enough to motivate the final promotional push.

Original source table 9 — includes source claims qualified above

The Retroactive Rate Upgrade — Why It MattersThe tiered launch commission system produces maximum promotional effort only if the tier upgrade is retroactive — applied to all sales from the first sale, not only to marginal sales above the tier threshold. Here is why: if an affiliate has generated 18 sales at the Tier 2 rate (35%) and the Tier 3 threshold is 20 sales at 40%, the marginal value of generating 2 more sales is: (2 sales × $997 net × 5% additional rate) = $99.70 in additional commission. Marginal effort for $99.70 may not be worth the extra email to the list. But if the upgrade is retroactive: the value of generating 2 more sales is (20 sales × $997 net × 5% additional rate) = $997 — nearly 10× the marginal value. The retroactive structure creates the final promotional push that drives leaderboard competition.

7. Resolve all six attribution cases before launch

For an eligible click and purchase inside the launch, apply the agreed tier. The source also proposes seven days of post-close attribution and eligible prelaunch clicks inside the cookie window. Distinguish an attribution grace period from public purchase availability: it cannot justify an inaccurate claim that checkout is closed when it remains open.

For multiple partner links, the proposed default is last click with no split. For an affiliate coupon, the table says the coupon wins even when a tracked link was clicked. Put that priority explicitly in the agreement and tracking rules, because last-click language alone does not resolve a coupon-versus-link conflict.

Refunded sales reverse the agreed commission; if already paid, specify the later deduction or recovery process. Define dispute handling, negative balances and late collections. Test representative attribution cases before promotion. A tracking platform and operator records provide evidence for reconciliation; neither should be treated as automatically conclusive in every dispute.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-Affiliate-Program-Architecture-SOP.docx

Original source table 10 — includes source claims qualified above

Attribution Scenario	RISER Nation Standard	Rationale
Buyer clicks affiliate link and purchases during the launch window	Full commission at the qualifying tier. Straightforward.	Standard last-click, in-window attribution.
Buyer clicks affiliate link during the launch window but purchases after cart close (within 7 days)	Full commission at the qualifying tier (the 7-day post-close grace window applies).	Some buyers need time after the urgency deadline to complete their decision. A 7-day post-close grace window captures these buyers without the partner losing credit for generating genuine purchase intent.
Buyer clicks affiliate link before the launch opens (pre-launch warm-up period)	Commission attributed if the purchase occurs during the launch window or within the 7-day post-close grace window. The click was within the cookie window.	Pre-launch click activity from a partner's audience is evidence of successful pre-launch promotion — the partner's pre-launch send generated the purchase intent.
Buyer clicks multiple affiliate links (from different affiliates) before purchasing	Last-click attribution: the most recent affiliate link clicked before the purchase receives full commission. No split commission.	Last-click attribution is the simplest, most transparent, and most defensible standard. Split attribution models are more 'accurate' but create calculation complexity that produces disputes.
Buyer purchases using a coupon code associated with a specific affiliate (not a tracked link)	Commission attributed to the affiliate whose coupon code was used, regardless of whether a tracked link was also clicked.	Some affiliates promote with coupon codes rather than tracked links. The coupon code is an explicit affiliate identifier and should produce the same commission attribution as a tracked link.
Buyer requests a refund within the refund window	Commission reversed. If already paid: deducted from the next payment cycle or recovered from the affiliate's outstanding balance.	Commission on a refunded sale represents the partner earning money on a transaction that did not hold. The refund reversal is standard and should be stated explicitly in the partner agreement before the launch.

8. Teach evergreen qualification and retention separately

Standard evergreen affiliates receive the source’s proposed thirty percent, with payment on the fifteenth of the following month for eligible confirmed sales and a $50 minimum carried forward when unmet. A refund window can make some prior-month sales ineligible for that payout, so state the cutoff rather than promising every sale immediately.

Active status requires five confirmed sales in the prior three months OR ten in the prior twelve months. The proposed rate is thirty-five percent prospectively from qualification, not retroactively for the month, with no minimum payout. Benefits include priority asset updates, early launches and launch invitations.

Super status requires twenty sales in three months OR $10,000 referred net revenue in twelve months, with forty percent and Active benefits plus co-creation, founder relationship development, first refusal on launch spots and custom support. The source offers a fifty-percent advance on the first and remainder on the fifteenth for commissions above $500 monthly. Identify the period being advanced and true-up rules; the source’s mid-month label does not match a first-of-month date.

Quarterly review occurs on the first Monday with thirty days’ written notice. Active falls to Standard only when below three sales in three months AND eight in twelve. Super falls to Active when below ten in three months AND $5,000 net in twelve. Approved leave or documented hiatus is an exception. Qualification and retention thresholds differ intentionally in the source; maintain effective dates and relevant cohorts.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-Affiliate-Recruitment-Outreach-Templates-SOP.docx · RISER-Affiliate-Program-Architecture-SOP.docx

Original source table 11 — includes source claims qualified above

PHASE 2The Evergreen Affiliate Deal StructureThe commercial architecture for ongoing, non-launch promotions

Original source table 12 — includes source claims qualified above

Tier	Qualification	Commission Rate	Payment Terms	Benefits
Standard Affiliate	Approved affiliate, 0+ sales in any period	30% of net sale price	Paid on the 15th of the following month for all confirmed (non-refunded, outside refund window) sales from the prior month. Minimum payout: $50.	Standard asset library access. Real-time dashboard. Monthly payment.
Active Affiliate	5+ confirmed sales in the prior 3 months OR 10+ in the prior 12 months	35% of net sale price. Applied to all sales once the threshold is met — the upgrade is not retroactive for the month, but applies from the qualification date forward.	Same payment terms. No minimum payout threshold.	Priority asset library updates, early access to new offer launches, included in the launch JV invitation list.
Super Affiliate	20+ confirmed sales in the prior 3 months OR $10,000+ in referred net revenue in the prior 12 months	40% of net sale price.	Same payment terms. Mid-month commission advance available for affiliates generating above $500/month in commissions — 50% advance on the 1st, remainder on the 15th.	All Active benefits plus: co-creation opportunities, personal relationship development with the Founder, first right of refusal on JV launch spots, custom promotional support.

Original source table 13 — includes source claims qualified above

Tier Assessment	Timing	Notice Period	Downgrade Trigger	Exception
Active → Standard downgrade	First Monday of each quarter for the prior quarter's performance	30-day written notice before the downgrade takes effect	Fewer than 3 sales in the prior 3 months AND fewer than 8 sales in the prior 12 months	An affiliate on approved leave or in a documented hiatus period (agreed with the Affiliate Manager) is not subject to automated downgrade.
Super Affiliate → Active downgrade	First Monday of each quarter	30-day written notice	Fewer than 10 sales in the prior 3 months AND less than $5,000 in referred net revenue in the prior 12 months	Same exception as above.

9. Design leaderboard rules and reconcile the worked economics

The source proposes three paid positions, visible standings, preannounced amounts, earliest-timestamp tie breaking and a minimum number of confirmed promotional emails. It suggests first prize at two to three times average expected commission, second at one-and-a-half and third at one times; its $500,000-launch examples are $3,000–$5,000, $1,500–$2,500 and $750–$1,250. These are design proposals, not proven motivational laws. Forecast payout cost and define eligibility before the launch.

In the five-day, eight-affiliate example, prizes are $2,500, $1,000 and $500. Thirty-five sales at a $967.79 base and forty percent produce $13,549.06 plus first prize, totaling $16,049.06. Twenty-two sales produce $8,516.55 plus second prize, totaling $9,516.55. These use aggregate rounding. Per-sale rounding can differ and needs a stated rule.

The source compares the first partner with five sales at thirty percent, fifteen at thirty-five and fifteen at forty, totaling $12,339.33 when rounded by tier. The resulting $1,209.73 difference illustrates retroactivity, but a different rounding convention can change a cent. Make the exact boundary convention match the written terms.

For 120 sales, gross is $119,640 and source-rounded post-processing revenue is $116,134.80. A three-percent expected full-refund scenario returns 3.6 times $997, or $3,589.20. When original processing costs are not returned, the remaining cash is $112,545.60 before commissions, prizes, broker fees, delivery and other costs. The source’s $112,650.76 overstates this by $105.16. A fractional refund count is an expected-value scenario; actual refunded transactions are whole records.

Sum actual tier payouts, $4,000 prizes and any broker cost, then delivery and other expenses. The source’s $200,000 less $120,000 commission and $40,000 delivery leaves $40,000 before other costs. Whether that outcome meets objectives requires a stated margin and opportunity-cost standard; it is not automatically profit or failure.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-JV-Broker-Deal-Sourcing-SOP.docx

Stripe — processing costs and refunds

Original source table 14 — includes source claims qualified above

PHASE 3The Tiered Leaderboard Commission Structure — Full ArchitectureThe competitive commission system for maximum launch promotional effort

Original source table 15 — includes source claims qualified above

Design Element	Standard	Rationale
Number of paid positions	Top 3 positions. Not top 10 — too many paid positions dilute the competitive motivation. The operator wants the affiliates who are genuinely in contention for 1st, 2nd, and 3rd to feel that the prize is within reach.	More than 3 prize positions reduces the scarcity that motivates maximum effort. An affiliate who is in 8th place does not feel close enough to 1st place to make an extra send.
Prize amounts	1st: 2–3× the average affiliate's expected launch commission. 2nd: 1.5×. 3rd: 1.0×. Scale with the launch size — for a $500K launch: 1st $3,000–$5,000, 2nd $1,500–$2,500, 3rd $750–$1,250.	The prize must be large enough to motivate the specific extra sends that move a strong affiliate from 4th place to 3rd. If the prize is $50 for 3rd place: it will not motivate an extra send that the affiliate values at the audience relationship cost.
Real-time visibility	The leaderboard is updated in real time and accessible to all participating affiliates during the launch window.	Real-time visibility creates moment-to-moment competitive engagement. An affiliate who checks the leaderboard and sees they are 2 sales behind 3rd place will consider an extra send. An affiliate who gets a weekly update has no moment-to-moment engagement.
Bonus structure disclosure	The leaderboard and all prize amounts are communicated to affiliates in the JV Partner Brief — before the launch opens, not revealed as a surprise incentive mid-launch.	Affiliates plan their promotional schedule in advance. A leaderboard that is revealed mid-launch cannot be incorporated into the pre-launch planning that determines how many promotional sends the affiliate commits.
Tie-breaking rule	In the event of a tie for any prize position: the affiliate who reached the tied sales count first (earlier timestamp) wins the higher position.	A clear, objective tie-breaking rule prevents post-launch disputes about who 'actually' won a position.
Minimum promotional activity requirement	To be eligible for a leaderboard prize: the affiliate must have sent at least [X] confirmed promotional emails during the launch window. An affiliate who generated all sales from a single send to a warm list wins the position but must meet the minimum promotional effort standard.	The minimum activity requirement prevents a scenario where an affiliate with a tiny but highly responsive list wins the leaderboard without making promotional effort — which discourages the larger-list affiliates who made genuine multi-send efforts.

Original source table 16 — includes source claims qualified above

LEADERBOARD LAUNCH COMMISSION CALCULATION — 5-Day Launch, 8 Active AffiliatesTHE LAUNCH PARAMETERSOffer price: $997 (one-time payment option)Launch window: 5 daysRefund window: 30 daysCommission tiers: Tier 1 (30%) / Tier 2 (35% retroactive above 5 sales) / Tier 3 (40% retroactive above 20 sales)Leaderboard prizes: 1st: $2,500 | 2nd: $1,000 | 3rd: $500AFFILIATE A — THE TOP PERFORMERSales: 35 confirmed sales during the launch windowTransaction average (net after payment processing): $967.79Tier assessment: 35 sales → Tier 3 (40%, retroactive)Commission: 35 × $967.79 × 40% = $13,549.06Leaderboard prize (1st place): $2,500Total earnings: $13,549.06 + $2,500 = $16,049.06What Affiliate A earned without the retroactive structure (Tier 1 on first 5, Tier 2 on next 15, Tier 3 on final 15): First 5 sales at 30%: 5 × $967.79 × 30% = $1,451.69 Next 15 sales at 35%: 15 × $967.79 × 35% = $5,080.90 Final 15 sales at 40%: 15 × $967.79 × 40% = $5,806.74 Total without retroactive: $12,339.33 Retroactive bonus vs non-retroactive: $1,209.73 extra earned through the retroactive structureAFFILIATE B — THE SECOND-PLACE FINISHERSales: 22 confirmed salesTier: 3 (40%, retroactive)Commission: 22 × $967.79 × 40% = $8,516.55Leaderboard prize (2nd place): $1,000Total earnings: $8,516.55 + $1,000 = $9,516.55OPERATOR ECONOMICS CHECKTotal sales from all affiliates: assume 120 confirmed sales across all 8 affiliatesTotal gross revenue: 120 × $997 = $119,640Total net revenue (after payment processing): 120 × $967.79 = $116,134.80Estimated refunds (3%): 3.6 sales → approximate reversal: 3.6 × $967.79 = $3,484.04Net confirmed revenue: $116,134.80 - $3,484.04 = $112,650.76Total affiliate commissions paid (across all tiers): [Sum of all affiliate commissions]Leaderboard prizes total: $2,500 + $1,000 + $500 = $4,000Broker commissions (if applicable): [X]Total partnership costs: [Sum above]Net operator revenue: $112,650.76 - [Total partnership costs]THE OPERATOR'S MINIMUM CHECKBefore setting any commission structure: confirm the total commission payout (across all tiers) plus leaderboard prizes leaves the operator above the minimum viable gross profit margin after delivery costs. A launch that produces $200K in revenue but pays out $120K in commissions and costs $40K to deliver is a $40K net result — not a success.

10. Correct the reciprocal-value ratio

Estimate what each audience delivers using audience size, engagement, clicks, opt-ins, buyer conversion and average order value. If click rate is clicks per opener, multiplying audience by open rate and then click rate is consistent. If it is clicks per delivered email, multiplying by open rate again double-discounts. State every denominator and distinguish tracking estimates from verified human behavior.

The source uses thirty-percent and thirty-five-percent landing-page conversion assumptions. Neither establishes a benchmark or RISER advantage. Define A as estimated value RISER delivers to the partner and B as estimated value the partner delivers to RISER. A divided by B above two means RISER gives more than it receives; below one-half means RISER gives less. The source reverses the above-two explanation and recommends an offset in the wrong direction.

Its one-half-to-two range is a broad negotiation heuristic, not proof of fairness. If RISER gives too little, possible offsets are an additional send, useful content, a commission on attributable sales or another mutually valued contribution. If RISER gives more, discuss a contribution from the other side rather than automatically sending still more.

Value extra sends by estimated incremental outcomes, content by a mutually understood contribution and effort estimate, cash commission by the agreed eligible revenue, and introductions or access jointly. Founder hours alone do not prove partner value. State the offset clearly and respect audience fit; a larger list does not guarantee a better exchange.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-JV-Email-Swap-SOP.docx

Original source table 17 — includes source claims qualified above

PHASE 4The Reciprocal Deal Structure — Audience-for-Audience MathematicsB45309

Original source table 18 — includes source claims qualified above

THE RECIPROCAL DEAL EQUITY CALCULATIONPARTY A (RISER NATION OPERATOR)List size: [A subscribers]Average open rate: [A-OR]%Estimated engaged readers per send: [A subscribers] × [A-OR]% = [A-engaged]Average click rate on promotional content: [A-CTR]%Estimated clicks to partner's resource: [A-engaged] × [A-CTR]% = [A-clicks]Estimated opt-ins for partner (at 30% Bridge Page conversion): [A-clicks] × 30% = [A-optins]Estimated EV of those opt-ins for partner (at their buyer conversion rate × offer value): [A-optins] × [partner-CVR]% × $[partner-AOV] = $[A-EV]PARTY B (THE PARTNER)List size: [B subscribers]Average open rate: [B-OR]%Estimated engaged readers per send: [B subscribers] × [B-OR]% = [B-engaged]Average click rate: [B-CTR]%Estimated clicks to RISER NATION resource: [B-engaged] × [B-CTR]% = [B-clicks]Estimated opt-ins for RISER NATION: [B-clicks] × 35% = [B-optins]// Note: RISER NATION Bridge Page conversion rate is typically higher than average (35%+) because of the context block.Estimated EV of those opt-ins for RISER NATION (at buyer conversion rate × offer value): [B-optins] × [RN-CVR]% × $[RN-AOV] = $[B-EV]THE EQUITY ASSESSMENTRatio: $[A-EV] ÷ $[B-EV] = [ratio]Within 0.5× – 2.0×: the exchange is broadly equitable. Proceed as a direct mutual swap.Below 0.5× (RISER NATION produces significantly less value): offer an offset — an additional value exchange that compensates Party B.Above 2.0× (RISER NATION receives significantly more value): the exchange is weighted in RISER NATION's favour. Propose an adjusted swap: RISER NATION promotes Party B's resource twice, or to a larger segment, or offers an additional piece of value.

Original source table 19 — includes source claims qualified above

Offset Type	When to Use It	How to Value It	Disclosure to Partner
Additional promotional send	RISER NATION sends to their list twice in exchange for one send from the partner — or sends to a larger segment than would produce equivalent value.	Calculate the estimated opt-in difference between the two parties' sends. The additional send should close the gap to within the 0.5×–2.0× equity range.	Explicit: 'My list is smaller than yours but I want this to be fair. I am proposing sending to you twice — once for a newsletter mention and once for a dedicated send — to make the exchange more equitable.'
Content contribution	RISER NATION produces an episode, a guest post, or a piece of long-form content for the partner's channel in addition to the email swap.	Value the content contribution at the estimated time × hourly rate of the Founder. Compare to the opt-in value differential.	Offer this as a genuine contribution to the partner's audience, not just a compensating transaction. The content should stand on its own as valuable to the partner's audience.
Future cash commission	If the exchange is significantly inequitable and cannot be balanced by additional sends: offer the larger-list partner a referral commission on any sales generated from their send — converting the reciprocal into a hybrid arrangement.	Commission on net sales: the same rate as the standard affiliate programme. This converts an inequitable swap into a standard affiliate deal.	Explicit: 'Given the size difference between our lists, I want to make sure this is worth your while. I am happy to add a commission on any sales generated from your send — [X]% on net sales.'
Value-in-kind offset	RISER NATION offers a direct value exchange that is not a promotional send: a podcast interview appearance, a community presentation, priority access to a new resource, or an introduction to a specific person in their network.	Assessed jointly — what is the value of the specific access or introduction to the partner? This is a relationship-based assessment, not a formula.	Offered as a genuine relationship gesture: 'I know my list is smaller than yours. I want to propose something additional that might be more valuable to you than a second email send...'

11. Distinguish promotion from licensing rights

The four licensing models are revenue share, annual fee, per-student fee and minimum guarantee plus share above a threshold. The source’s revenue-share model uses gross enrollment revenue and monthly fifteenth payments, unlike its standard affiliate net basis. It proposes at least 1,000 engaged aligned audience members and verified delivery capability. Treat that count as a screening proposal, not proof of readiness.

An annual fee is due at agreement with twelve-month renewal and scope-dependent pricing. Per-student licensing invoices confirmed enrollments monthly without a minimum guarantee. A minimum-plus-share model collects a yearly minimum quarterly in advance and adds share above an enrollment or revenue threshold. Define whether any amounts are credits against each other; do not leave additive versus recoupable ambiguous.

A promised minimum is not risk-free collection, and poor delivery can damage the program. Define licensed content, permitted uses, audience, territory, term, quality review, attribution and termination. The source proposes immediate cessation and removal after termination with sixty days to wind down previously enrolled students. Resolve how those obligations work together.

The source’s noncompetition and post-termination language is a discussion template, not a conclusion about enforceability. Obtain appropriate review for the actual jurisdiction and arrangement before use. This lesson neither grants IP rights nor creates or accepts an agreement.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-IP-Licensing-Model-SOP.docx · RISER-White-Label-Pricing-Architecture-SOP.docx · RISER-White-Label-Partner-Onboarding-SOP.docx

Original source table 20 — includes source claims qualified above

Revenue Model	Structure	Calculation Basis	Minimum Requirements	Operator's Risk
Revenue Share	The white-label partner enrols students and the RISER NATION operator receives a percentage of each enrolment fee. No upfront payment from either party.	[X]% of gross enrolment revenue. Payment monthly on the 15th for prior month enrolments. Refund policy mirrors the standard RISER NATION refund policy.	Minimum 1,000 engaged audience members in an avatar-aligned community. Delivery capability confirmed: the partner can deliver the programme effectively to their students.	High — no guaranteed income. Revenue is entirely contingent on the partner's enrolment performance.
Annual Licence Fee	The partner pays a fixed annual fee for the right to use and deliver the programme under their brand. Revenue share is not applicable — the operator receives the licence fee regardless of enrolment performance.	Fixed annual fee: $[X,000]–$[XX,000] based on audience size, market, and exclusivity scope. Due on the agreement date. Renewal date: 12 months from the initial agreement.	Audience size above [X] subscribers or community members. Prior evidence of successful programme delivery in a related domain.	Low — the licence fee is guaranteed regardless of the partner's performance. Risk is limited to the reputational impact of poor delivery by the partner.
Per-Student Licence	The partner pays a fixed fee per enrolled student at the point of enrolment. Scales with the partner's performance.	$[X] per confirmed enrolled student. Invoice issued monthly for the prior month's enrolments. No minimum enrolment guarantee.	Same requirements as Revenue Share. The per-student model requires the same delivery capability assessment.	Medium — income is tied to the partner's enrolment activity. More predictable than Revenue Share (fixed amount per student vs variable revenue share) but still performance-dependent.
Minimum Guarantee + Revenue Share	The partner pays a minimum annual guarantee (covering the RISER NATION operator's baseline risk) plus a revenue share on enrolments above a threshold.	Minimum guarantee: $[X,000]/year, paid quarterly in advance. Revenue share: [X]% of gross enrolment revenue above [Y enrolments or $Z revenue] per year.	Higher audience size requirement than pure Revenue Share — the minimum guarantee is only economically viable for partners with sufficient volume to justify the guarantee payment.	Low on the baseline (guaranteed by the minimum). Upside from the revenue share above the threshold.

Original source table 21 — includes source claims qualified above

Protection Clause	Standard Language Required	What Happens Without It
Non-competition scope	The partner may not use the licensed content, methodology, or framework to offer a directly competing programme to the RISER NATION operator's primary audience during the term of the agreement and for [X] months after termination.	The partner uses the licensed content to build their own competing programme, directly eroding RISER NATION's addressable market.
Quality standard maintenance	The partner must maintain the programme delivery at a standard that does not damage the RISER NATION brand or the programme's reputation. RISER NATION reserves the right to conduct a quality review and to terminate the licence if quality standards are not met.	The partner delivers the programme poorly, students complain, negative reviews associate the programme name with poor delivery, and the RISER NATION brand is damaged by content the operator no longer controls.
Attribution requirement	In all marketing, promotional, and delivery materials: the partner must acknowledge that the programme is delivered under licence from RISER NATION / [Founder Name]. The attribution format is: '[Programme Name], developed by [Founder Name] / RISER NATION, delivered under licence by [Partner Name].'	The partner presents the programme as their own original content, potentially raising IP ownership disputes when the original methodology is publicly associated with the partner's brand.
Termination and content recovery	Upon termination of the licence: the partner immediately ceases delivery of the programme and removes all RISER NATION materials from their platforms. A 60-day wind-down period is permitted only for students currently enrolled before termination.	The partner continues delivering the programme after the licence ends — whether due to oversight or intent. Without a clear termination clause, enforcement is difficult.

12. Complete the written agreement and reconcile conflicting dates

Identify parties, date, deal type, offer, prices, payment schedule and URLs. Specify promotional dates, sends and other activities, supplied assets, commission basis, exact rates, collection timing, refund reversal, tracking platform, link, cookie, coupon priority, payout minimum, method and dates. For launch deals add window, grace, tier thresholds, retroactivity and prizes. Preserve the full original template below for field-by-field review.

A promise to pay within ten business days of cart close after a thirty-day refund window can conflict. Choose a workable eligibility cutoff, holdback and payment date, with later true-ups. State responsibility for negative balances, disputes and delayed installments. A simple plain-language confirmation can have legal consequences; do not assume its informal format makes it nonbinding.

Disclosures need to make material promotional relationships clear to the relevant audience. The operator should provide accurate materials, train partners on requirements, monitor and correct problems; responsibility is not fully transferred to affiliates. Keep actual promotional claims supported and endorsements truthful. The FTC reference below provides current US guidance; equivalent obligations depend on the relevant market.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-JV-Legal-Agreement-Template-SOP.docx

FTC — endorsement disclosures and advertiser responsibilities

Original source table 22 — includes source claims qualified above

STANDARD JV DEAL AGREEMENT — Plain Language VersionAGREEMENT IDENTIFICATIONAgreement Date: [ ]Between: [RISER NATION Operator Name] ('the Operator') and [Partner Name] ('the Partner')Deal Type: [Revenue Share / Flat Fee / Hybrid / Reciprocal / Tiered Launch / White-Label / Licensing]THE PROMOTED OFFEROffer Name: [ ]Offer Price: $[ ] (one-time) OR $[ ]/month (subscription) OR $[ ] for a [X]-payment plan of $[ ]/monthOffer URL: [ ]THE PARTNER'S PROMOTIONAL OBLIGATIONThe Partner agrees to: — Send [X] promotional email(s) to their email list of approximately [Y] subscribers during the period [Start Date] to [End Date] — [Any additional promotional activities agreed: social posts, podcast mentions, etc.]The Operator will provide the Partner with: [list of assets provided — email templates, graphics, affiliate link, Partner Brief]COMMISSION TERMSCommission rate: [X]% of the net sale price after payment processing fees and confirmed refunds OR flat fee of $[X] per confirmed sale OR: [describe the specific hybrid or tiered structure if applicable]Commission basis: Net sale value (gross transaction value minus payment processing fees only; refunds handled separately)Payment plan attribution: Commission paid on each collected payment at the above rate (not on the total committed plan value at point of enrolment)REFUND POLICYThe Operator's standard refund policy: [X] days from purchase dateCommissions on refunded sales: reversed if the refund occurs before the commission has been paid. Reversed against the next payment cycle if the refund occurs after the commission has been paid.ATTRIBUTION AND TRACKINGTracking platform: [Platform name — e.g., ThriveCart, Rewardful]Partner's unique affiliate link: [ ]Attribution model: Last-click, [X]-day cookie windowThe Partner acknowledges that their commission dashboard provides real-time access to their click and conversion data.PAYMENT SCHEDULEPayment date: [The Xth of each month] for commissions confirmed in the prior month (outside the refund window)Minimum payout: $[X] (balances below this roll to the following cycle)Payment method: [PayPal / Wise / ACH / Other] to [Partner's registered payment detail]FOR LAUNCH DEALS — SPECIFIC TERMSLaunch window: [Open Date] to [Close Date]Attribution window post-close: [X] daysTiered commission structure (if applicable): [State all tiers and thresholds]Retroactive tier upgrade: [Yes / No — if yes, all sales are upgraded when the tier is reached]Leaderboard prizes: [State all prize positions and amounts]Payment timing for launch commissions: within [10] business days of cart close, after the refund windowFTC AND COMPLIANCEThe Partner confirms they understand their FTC (and equivalent) disclosure obligations for all promotional content referencing this offer.The Operator confirms the offer is accurately described in the provided materials.BOTH PARTIES AGREE[Operator signature / confirmation] | Date: [ ][Partner confirmation — email confirmation is acceptable for standard deals] | Date: [ ]

13. Evaluate four negotiation requests and five program limits

For a higher rate, model contribution after commission, delivery and other costs. The source’s suggested response holds the standard evergreen Super rate at forty percent and considers a custom hybrid when justified. Reconcile that with separate launch ranges rather than declaring that no arrangement can exceed forty percent.

For a longer cookie, examine the observed purchase timeline and attribution conflicts. The source proposes thirty days normally and a forty-five-day extension when evidence supports it. Longer windows do not literally cost nothing. For exclusivity, define scope, duration, performance and opportunity cost: the source limits proposals to six months and suggests a ninety-day first-refusal arrangement with seven days to respond as an alternative.

For an existing-buyer discount, model commissions on the discounted eligible base and compare outcomes with and without the discount. Higher conversion is a hypothesis, not a guaranteed offset to the lower price. Record the exact exception and why it was chosen.

The five source limits are written terms before promotion, refund reversal, independent commission records, collected-payment attribution and disclosure compliance. Preserve those as proposed program rules while correcting their explanations: oral arrangements are not universally unenforceable, internal records are not automatically conclusive, and advertisers retain responsibilities. The schema allows a nonstandard committed-value option despite the narrative’s never rule; any exception needs explicit reconciliation before use.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-JV-Legal-Agreement-Template-SOP.docx

FTC — endorsement guidance

Original source table 23 — includes source claims qualified above

Request Category	Common Requests	RISER NATION's Assessment Approach	Standard Response
Commission rate above the published tier	'I want 50% instead of 40%.' 'My list is so targeted I want 55% for this promotion.'	Run the economics: at the requested rate, does the deal still produce a net positive result above the minimum viable gross profit margin? If yes: consider it. If no: decline regardless of the partner's list quality. A deal that erodes the gross margin is not a good deal at any commission rate.	'Our published Super Affiliate rate is 40%. I cannot go above this for a standard commission structure — it creates equity issues with other partners at the same tier. If your results consistently justify it, the next step is a custom hybrid arrangement with a base fee.'
Attribution window extension	'I want a 90-day cookie rather than 30 days.'	Assess the offer's purchase timeline. If 90% of purchases from this partner's audience happen within 14 days of the click: a 90-day cookie is not meaningful and costs nothing to grant. If purchases regularly happen at 60–90 days: the extension materially increases the commission cost.	'Our standard attribution window is 30 days. We can extend to 45 days for partners whose audience has a documented longer decision cycle — which we can verify from the attribution data after your first promotion.'
Exclusivity requests	'I want to be the only affiliate promoting your programme in my specific niche/geography/audience segment for 6 months.'	Assess the exclusivity scope. Geographic exclusivity (only promoting in a specific country) may be acceptable. Niche exclusivity (the only affiliate in 'the female entrepreneur space') may cut off the most valuable Dream 100 relationships. Duration: never more than 6 months and only with a performance threshold.	'We do not offer category exclusivity because it limits our ability to serve our audience through other trusted relationships. We can offer a first-right-of-refusal for 90 days — if we are planning a promotion to a new partner in your specific audience segment, we will notify you first and give you 7 days to match or better the deal.'
Special terms for their existing buyers	'My existing buyers should get a discount if they purchase through my link — and I still want the full commission on their purchase.'	The operator pays commission on the discounted price (not the full price) while the partner receives the benefit of higher conversions from the discount. The discount reduces the commission base but increases the conversion rate. Model the economics both ways.	'We can offer a [X]% discount to your existing community through a coupon code specific to your link. Your commission would be calculated on the discounted price — but the conversion rate will likely be higher, which should net out positively for you. Let me calculate the expected outcome both ways.'

Original source table 24 — includes source claims qualified above

Non-Negotiable Item	Why It Cannot Be Changed
All terms in writing before promotion begins	Verbal agreements are not enforceable in practice. An operator who 'agreed verbally' to specific terms cannot prove what was agreed if a dispute arises at payment time. No exceptions.
Refund reversal policy	Commissions are not paid on refunded sales. An operator who pays commissions on refunded sales is subsidising buyer risk with partnership capital. No exceptions, regardless of how trusted the partner is.
Independent commission tracking	The operator maintains their own commission records independent of what the affiliate platform reports. These records are the source of truth for any dispute. No partner has the right to demand that the operator's internal records be replaced by the partner's own tracking.
Payment plan attribution to collected payments	Commissions are paid as payments are collected — not on the total committed plan value. This protects the operator from paying commissions on revenue that was never collected.
FTC compliance obligation	Every promotional email and social post must comply with FTC disclosure requirements. The operator's obligation to ensure their partners are informed of this requirement does not transfer the legal obligation to the operator — but it is a non-negotiable programme participation condition.

14. Use the schema and checklists to audit the deal

The Deal Structure record links partner and offer to type, net base, all tier rates and thresholds, retroactivity, leaderboard and prizes, attribution model and window, collection method, reversal policy, payout date/minimum, start/end dates, post-close window, agreement link and nonstandard terms with rationale. Preserve the original field types and allowed values below. Store rate changes with effective dates rather than silently rewriting history.

Before confirming, select the structure, define net or gross, collection and reversal rules, cookie and any extension, leaderboard obligations and written agreement. For a launch, confirm exact tiers, retroactivity, preannounced prizes, grace and achievable payout dates. For licensing, define revenue model, permitted scope, quality, attribution and termination/wind-down.

At monthly reconciliation, calculate commissions on the agreed basis, use actual collected installments, apply reversals, verify effective tier upgrades and independently reconcile standings before prizes. Compare platform and transaction records, document discrepancies and resolve them through the agreed process. This is an audit exercise; the lesson does not send statements, pay commissions, contact partners or create a database.

Finish with one worked hypothetical deal: state the economics, calculate one-time and installment commissions, handle a refund and coupon conflict, identify a tier boundary, and write a payment calendar that survives the refund window. Use the full source checklists as a cross-check; final course integration must still reconcile every distinct source point to teaching.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-Affiliate-Program-Architecture-SOP.docx

Original source table 25 — includes source claims qualified above

Field	Type	Notes
Deal Structure ID	Short text	Format: DS-[Partner ID]-[YYYY-MM]. e.g. DS-PART-042-2026-09
Partner	Link → Dream 100 Partner Records
Deal Structure Type	Single select	Revenue Share / Flat Fee / Hybrid / Reciprocal / Tiered Launch / White-Label Revenue Share / Annual Licence / Per-Student Licence / Minimum Guarantee + Rev Share
Offer Being Promoted	Short text
Offer Net Sale Value (standard one-time)	Currency	The net sale value used as the commission basis
Commission Rate — Tier 1 (Base)	Number	% or flat dollar amount
Commission Rate — Tier 2 (if tiered)	Number	% and threshold for tier upgrade
Commission Rate — Tier 3 (if tiered)	Number	% and threshold for tier upgrade
Tier Upgrade Retroactive	Checkbox	Is the tier upgrade retroactive to first sale?
Leaderboard Active	Checkbox	Does this deal include a leaderboard competition?
Leaderboard Prize 1st	Currency
Leaderboard Prize 2nd	Currency
Leaderboard Prize 3rd	Currency
Attribution Window (days)	Number	Standard: 30
Attribution Model	Single select	Last Click / First Click / Linear (non-standard — requires explicit documentation)
Payment Plan Attribution	Single select	Per Collected Payment (standard) / On Committed Value (non-standard — requires explicit justification)
Refund Reversal Policy	Checkbox	Confirmed: commissions reversed on refunded sales
Payment Date	Short text	e.g. '15th of following month'
Minimum Payout Threshold	Currency
Deal Start Date	Date
Deal End Date (if launch or fixed-term)	Date
Post-Close Attribution Window (launch deals)	Number	Days after cart close within which sales are attributed
Written Agreement Confirmed	Checkbox
Agreement Document Link	URL	Link to the written agreement or email confirmation
Non-Standard Terms (if any)	Long text	Describe any deviations from the RISER NATION standard terms
Rationale for Non-Standard Terms	Long text	Why the deviation was agreed

15. Calculate the incremental value of crossing a tier

Use the source’s eighteen-to-twenty-sales scenario with its correctly stated $967.79 net base. Eighteen sales at thirty-five percent produce $6,097.08 when the aggregate commission is rounded to cents. Twenty sales at forty percent retroactively produce $7,742.32. The increase is $1,645.24, not merely the rate-uplift amount in the source passage.

Break that increase into two parts: the two new sales at forty percent contribute approximately $774.23, and raising the prior eighteen sales by five percentage points contributes approximately $871.01. Together they explain the $1,645.24 increment under this rounding convention. This separates new-sale earnings from the reward for upgrading earlier sales.

If the five-point uplift applies to twenty sales, it is $967.79; if it applies only to the two new sales, it is about $96.78. Their ten-to-one ratio describes the uplift component, not the total marginal commission. The source’s $997 and $99.70 use gross mislabeled as net and omit the base earnings from the new sales. Whether the added incentive changes promotion is still a behavioral hypothesis.

State the exact threshold before applying this example. It assumes that reaching twenty qualifies both new sales at forty percent and upgrades the earlier eighteen. A contract that says above twenty would produce a different result. Also state whether aggregate, per-tier or per-transaction rounding controls the ledger and reconciliation.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-Co-Launch-Partner-Launch-SOP.docx

16. Make the deal record sufficient to reproduce a statement

Use a short-text deal identifier such as DS-PART-042-2026-09 and link it to the actual partner record. Select the exact structure: revenue share, flat fee, hybrid, reciprocal, tiered launch, white-label revenue share, annual license, per-student license or minimum guarantee plus share. Store the promoted offer and its commission base with currency and applicable price version.

The schema uses number fields for tier rates and says a number can mean a percentage or a flat amount. That is ambiguous without a unit. Its tier fields also say rate and threshold but one number cannot represent both clearly. Record the unit, each threshold, exact boundary, qualification conditions and effective dates explicitly in the written terms or additional structured fields; these are authored implementation clarifications, not fields recovered from the source.

Keep retroactive and leaderboard flags separate from the three currency prize amounts. Store cookie days, attribution model and post-close grace separately. The model options include last click, first click and linear; nonstandard choices need documented allocation rules. None of those fields alone captures coupon priority. Preserve that rule in the agreement and exception notes so a statement can be reproduced.

Record whether commissions follow collected payments or the schema’s nonstandard committed-value option, refund policy confirmation, payout date, currency minimum, start and end dates, written agreement confirmation and the actual agreement URL. A checkbox cannot replace the detailed refund recovery and dispute procedure. Preserve all nonstandard terms with rationale and consent evidence; do not infer acceptance merely because a field is populated.

For a monthly statement, reconcile eligible transactions, collections, processing deductions, attributed partner, effective rate, refunds, holds, prior balances, advances and actual payments. The source schema describes the deal but is not a complete transaction ledger. This authored reconciliation view prevents a visible dashboard balance from being mistaken for settled cash.

Supporting documents: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx · RISER-Affiliate-Program-Architecture-SOP.docx · RISER-JV-Legal-Agreement-Template-SOP.docx

Framework references

ClickFunnels — Dream 100 audience relationships · Acquisition.com — offers education

Complete original source

Full readable source and all operational checklists

RISER NATION
MASTER OPERATING SYSTEM
SOP — JV DEAL STRUCTURES AND COMMISSION TERMS
The Complete Reference System for Structuring Every Type of Joint Venture Deal — From the Standard Affiliate Revenue Share Through Tiered Launch Commissions, Flat Fees, Reciprocal Arrangements, Hybrid Structures, and White-Label Licensing Terms — With Worked Calculations, Written Agreement Templates, and the Non-Standard Deal Negotiation Framework
Kennedy × Holmes × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview — Why Deal Structure Is the Most Important Partnership Decision
Two operators can have identical promotional capability, identical audience quality, and identical relationship depth — and produce radically different partnership economics depending on how the deal is structured. A partnership structured correctly produces a fair, durable, compounding commercial relationship that both parties want to repeat and expand. A partnership structured incorrectly produces disputes at the payment stage, resentment when one party perceives inequity, and a relationship that ends where it should have been beginning.
The most common deal structure errors in the knowledge business JV ecosystem are: using the wrong structure type for the relationship context (offering a percentage rev share to a partner who wants predictable flat-fee income), leaving critical terms undefined (what counts as a net sale? what happens if a payment plan buyer stops paying?), setting commission rates that produce a positive-sounding headline but negative net economics after delivery costs, and negotiating deals that look balanced on paper but create perverse incentives when actual results arrive.
This SOP covers the complete RISER Nation deal structure library: the five core structure types and when each applies, the commission calculation mechanics (gross vs net, payment plan attribution, refund impact, recurring commission), the standard terms every written agreement must include, the launch JV deal structure in full detail, the evergreen affiliate structure, the tiered commission and leaderboard bonus architecture, the reciprocal deal mathematics, the white-label and licensing commercial models, the EPC calculation and communication standard, the written agreement template, and the non-standard deal negotiation framework.
The Five Core JV Deal Structure Types
Commission Calculation Mechanics — The Detailed Arithmetic
Every commission calculation in the RISER Nation system follows the same underlying arithmetic. Understanding this arithmetic prevents disputes and enables both parties to calculate expected earnings independently — which is essential for the partner to decide whether to invest promotional effort in the arrangement.
The Standard Commission Calculation — Step by Step
The Recurring Commission Calculation
Recurring commissions apply to continuity products — monthly memberships, subscription communities, and recurring coaching programmes. The recurring commission is calculated on each successful billing cycle, not just the initial purchase. The total commission from a recurring buyer grows each month they remain subscribed, creating a compounding income stream for the referring partner.
The launch JV deal is the most commercially significant and the most complex structure in the RISER Nation partnership system. A well-structured launch JV produces the highest subscriber acquisition volume in the shortest window of any partnership activity. A poorly structured launch JV produces disputes, disappointed partners, and damage to the Dream 100 relationships that are most valuable to the long-term programme.
The Standard Launch JV Commission Architecture
The Launch Window Attribution Rules
The evergreen affiliate deal is a standing arrangement where an approved affiliate can promote the RISER Nation Traffic Hook, SLO, or core offer at any time — not tied to a specific launch window. The evergreen structure rewards consistent promotional activity over time rather than concentrated launch-period effort.
The Evergreen Commission Architecture
The Tier Maintenance and Downgrade Protocol
Affiliate tiers are assessed quarterly. An affiliate who qualified for the Active tier in Q2 but generated zero sales in Q3 may be downgraded to the Standard tier in Q4. The downgrade protocol is communicated in writing with 30 days' notice — giving the affiliate an opportunity to re-qualify before the downgrade takes effect.
The leaderboard commission structure is a competitive motivational system layered on top of the standard launch commission tiers. Its function is to motivate the subset of affiliates who are in genuine contention for top positions to invest maximum promotional effort — additional email sends, social posts, and community promotions — in the final days of the launch window. Without a leaderboard structure, top affiliates have no incentive to promote more than the minimum effective effort once they have reached their commission tier threshold.
The Leaderboard Design Principles
The Leaderboard Commission Calculation — Complete Worked Example
Assessing Reciprocal Deal Equity
A reciprocal JV email swap (from the JV Email Swap SOP) exchanges audience access without money changing hands. The perceived fairness of this exchange determines whether both parties want to do it again. If one party consistently produces more value for the other than they receive, the relationship develops resentment rather than compounding. The equity assessment is not a precise calculation — it is a structured analysis that identifies when the exchange is broadly fair and when it requires an offset or a structure adjustment.
The Offset Mechanisms — When the Exchange Is Not Naturally Equitable
The White-Label and Licensing Commercial Structures
White-label and licensing deal structures involve the RISER Nation intellectual property — the programme content, the methodology, or the branded framework — being made available to a partner for delivery or promotion under specific commercial terms. These deal structures are fundamentally different from standard affiliate arrangements because they involve IP rights, not just promotional rights.
The Four White-Label and Licensing Revenue Models
The IP Protection Clauses — Non-Negotiable in All White-Label and Licensing Agreements
The Written Agreement Template
Every JV deal in the RISER Nation system — regardless of the relationship warmth, the deal complexity, or the existing trust between parties — is confirmed with a written agreement before any promotion begins. The written agreement is not a legal contract drafted by lawyers (for standard peer-to-peer deals). It is a clear, plain-language document that prevents misunderstandings by stating what both parties agreed, in terms specific enough that no ambiguity exists at the payment stage.
The Non-Standard Deal Negotiation Framework
The RISER Nation standard deal terms cover the vast majority of JV arrangements. Occasionally, a partner proposes non-standard terms — a higher commission rate, a different attribution model, an unusual payment schedule, or special treatment for their audience. The non-standard deal negotiation framework governs how to assess these requests and when to accept, modify, or decline them.
The Four Categories of Non-Standard Request
The Hardcoded Negotiation Limits — What Is Never Negotiated
Airtable Schema — JV Deal Structure Database
Table 1 — Deal Structure Records
Master JV Deal Structures Checklist
Before Confirming Any Deal
☐ Deal structure type selected from the five core types — matched to the relationship context and the partner's commercial preference
☐ Commission basis confirmed explicitly: net (after payment processing) or gross — stated in the written agreement
☐ Payment plan attribution confirmed: per collected payment (standard)
☐ Refund reversal policy confirmed and in the written agreement
☐ Attribution window: 30 days standard, any extension explicitly agreed and economically assessed
☐ Leaderboard structure (if launch): prize amounts, positions, retroactive tier upgrade, minimum promotional activity requirement all documented
☐ Written agreement completed and signed/confirmed by both parties before any promotional activity
Launch Deal Specific
☐ All tier thresholds and rates documented
☐ Retroactive upgrade confirmed: yes or no, stated in the partner brief
☐ Leaderboard prizes announced in the JV Partner Brief before launch opens
☐ Post-close attribution window defined: [X] days
☐ Payment timing confirmed: within [X] business days of close, after the refund window
White-Label / Licensing Specific
☐ Revenue model selected: Revenue Share / Annual Licence / Per-Student / Hybrid
☐ Non-competition clause: scope, duration, and geography defined
☐ Quality standard maintenance clause included
☐ Attribution requirement defined: how the partner acknowledges the IP source in all materials
☐ Termination clause: wind-down period and content removal requirements defined
Post-Deal Commission Calculation Audit (Monthly)
☐ Commission statements calculated using the standard net calculation (not gross)
☐ Payment plan commissions calculated on collected payments only
☐ Refund reversals applied before commission statements are sent to partners
☐ Tier upgrades applied: any affiliate who reached a new tier threshold this period has been upgraded
☐ Leaderboard standings confirmed independently before prizes are paid
RISER Nation Master Operating System | JV Deal Structures and Commission Terms SOP | Version 1.0 | 2026 Edition
Kennedy × Holmes × Brunson | risernation.com
The Deal Structure Is a Communication of Values, Not Just a Commercial Formula
Kennedy's observation on partnership deals: the commercial terms an operator proposes in a JV arrangement communicate their values about the relationship more clearly than any relationship management gesture. An operator who proposes fair terms, with transparent calculation methodology, without hiding disadvantageous clauses in complexity, is communicating that they treat partnerships as long-term relationships — not transactions to optimise once. An operator who proposes complex terms designed to maximise their own take at the partner's expense will close a deal but will not develop a partnership.
The Gross vs Net Distinction — The Most Misunderstood Commission Concept
The single most common source of commission disputes in the knowledge business JV ecosystem: the operator advertises a commission rate on 'sales' without specifying whether that means the gross transaction value or the net revenue after payment processing fees, refunds, and chargebacks. A 40% commission on a $997 sale is $398.80 on gross. The same 40% on net (after 3% payment processing fee, the industry-standard 2% refund rate, and the chargeback reserve) is approximately $370 — a $28 difference per sale that, multiplied across 50 sales, is $1,400 of commission the partner did not expect to have deducted. The RISER Nation standard is to state commissions on net revenue after payment processing and confirmed refunds — and to state this explicitly in every deal.
The Payment Plan Attribution Problem
A buyer who purchases a $997 programme on a 3-payment plan of $333/month presents a specific attribution challenge. The affiliate who referred this buyer generated a $997 sale commitment — but the operator only collects $333 in month one. Three solutions exist: (1) Pay the full commission immediately on the first payment (the operator takes the collection risk); (2) Pay commission only on each collected payment (the affiliate takes the collection risk); (3) Pay a portion on the first payment and the remainder as subsequent payments are collected (shared collection risk). The RISER Nation standard is Option 2 — commission is paid on each collected payment — and this must be stated explicitly in the deal terms before any payment plan is offered.
Structure Type
How It Works
Best Suited For
Commission Calculation Basis
When NOT to Use
Structure 1 — Percentage Revenue Share (the standard)
The partner receives a defined percentage of the net revenue from every sale they refer. The percentage is fixed for the duration of the arrangement.
Standard affiliate relationships, evergreen programme promotions, and most launch JV deals where the partner's contribution is measured by sales generated.
Net sale price after payment processing fees and confirmed refunds. Payment plan: each collected payment × commission rate.
When the partner has minimal audience overlap with the offer's buyer profile and the operator wants to ensure effort is rewarded rather than results (which the partner cannot fully control). A flat fee better serves this context.
Structure 2 — Flat Fee per Action
The partner receives a fixed dollar amount for each qualifying action — a sale, a confirmed opt-in above a certain threshold, or a booked call. The amount is fixed regardless of the transaction size.
Larger list owners who prioritise income predictability over upside participation, paid newsletter sponsorship slots, and deals where the operator wants to cap the commission cost regardless of the offer's price variations.
Per confirmed sale, per confirmed opt-in above a defined threshold, or per booked call — the qualifying action is specified explicitly.
When the offer has variable pricing (payment plans, upsells, downsells) that make a fixed per-sale amount inequitable if the partner's referred buyers systematically choose higher or lower price points.
Structure 3 — Hybrid (flat fee + percentage)
The partner receives a flat base fee (guaranteeing minimum income from the promotion regardless of results) plus a percentage of sales above a defined threshold.
Dream 100 Tier 1 partners who are taking a meaningful promotional risk by committing significant audience exposure, and whose contribution justifies both a guaranteed element and an upside participation element.
Base fee: paid on the completion of the agreed promotional activity (the email was sent, regardless of results). Percentage component: on net sales above the agreed threshold.
When the relationship is in its early stages and the operator cannot confidently project whether the base fee is economically justified by the expected results.
Structure 4 — Reciprocal (audience-for-audience)
No money changes hands. Both parties promote each other's resource to their respective lists and the value exchange is the audience access.
JV email swaps, content collaboration, and cross-promotion deals where both lists are broadly comparable in size and engagement quality.
No monetary calculation. The value of the arrangement is the estimated opt-in volume each party receives. Equity is assessed by list size × engagement rate × avatar alignment.
When lists are significantly different in size (more than 3× differential) — the operator with the smaller list is receiving significantly less value. A hybrid structure (reciprocal promotion plus a value offset) is more appropriate.
Structure 5 — Tiered Leaderboard (launch competition)
Commission rate increases as the partner reaches sales volume milestones during a launch window. A competitive leaderboard motivates maximum promotional effort. Bonus prizes awarded to the top performers.
Live launch JV events with multiple affiliates where the operator wants to maximise overall launch volume and the competitive element motivates extra promotional effort from top performers.
Base tier: standard percentage on first X sales. Tier 2: higher percentage on sales above X. Tier 3: higher still above Y. Leaderboard bonus: additional cash prize for top 1, 2, 3 positions.
Evergreen promotions where there is no defined launch window — a leaderboard without a deadline creates a diffuse, low-urgency structure that does not motivate concentrated promotional effort.
THE RISER NATION COMMISSION CALCULATION — Full worked example
THE INPUTS
Gross transaction value (the price the buyer paid): $997.00
Payment processing fee (Stripe standard rate: 2.9% + $0.30 per transaction): $997 × 2.9% + $0.30 = $29.21
Net transaction value: $997.00 - $29.21 = $967.79

FOR A ONE-TIME PAYMENT — Commission Calculation
Commission rate: 35%
Commission amount: $967.79 × 35% = $338.73
// Note: some operators calculate on gross ($997 × 35% = $348.95). The RISER Nation standard is net.
// The difference is $10.22 per sale. State explicitly which basis applies.

FOR A 3-PAYMENT PLAN ($333/month × 3 payments)
Payment 1 collected: $333.00 → net: $333 - ($333 × 2.9% + $0.30) = $333 - $9.96 = $323.04
Commission on Payment 1: $323.04 × 35% = $113.06

Payment 2 collected: $333.00 → net: $323.04
Commission on Payment 2: $113.06

Payment 3 collected: $333.00 → net: $323.04
Commission on Payment 3: $113.06

Total commission if all 3 payments collected: $339.18
// This is the same effective rate as the one-time payment — payment plan does not change the total commission if all payments are collected.

THE REFUND IMPACT
Refund rate for this offer: 3%
Expected refunds per 100 sales: 3
Commission reversed per refund: $338.73
Expected commission reversals per 100 sales: 3 × $338.73 = $1,016.19
Net commission per 100 sales after refunds: (100 × $338.73) - $1,016.19 = $32,856.81
Average effective commission per sale after refunds: $32,856.81 ÷ 100 = $328.57

THE EPC CALCULATION (Earnings Per Click — the primary partner evaluation metric)
Total clicks from the partner's promotional send: 500
Total confirmed sales attributed to those clicks: 15
Gross EPC: ($338.73 × 15) ÷ 500 = $10.16 per click
Net EPC (after refunds): ($328.57 × 15) ÷ 500 = $9.86 per click
// When communicating EPC to prospective partners: use net EPC after refunds. Gross EPC overstates the partner's expected earnings.
Recurring Commission Element
Standard Calculation
RISER Nation Configuration
Initial purchase commission
The commission on the first payment (the enrolment) — typically the same rate as the monthly recurring commission, though some operators pay a higher initial commission and a lower recurring rate.
Same rate for initial and recurring: [commission rate]% of each net billing amount. Stated explicitly in the deal terms.
Monthly recurring commission
Calculated on each successful monthly billing event. Failed billing events (insufficient funds, expired card) do not trigger a commission.
Commission calculated and credited on the 3rd business day after each successful billing cycle. Failed payments: no commission credited.
Commission on cancellations
When a subscriber cancels: the commission stops from the cancellation date. Any previously paid commission is not reversed (the partner earned the commissions for the months the subscriber was active).
No retroactive reversal on cancellations. Commission credited only for active billing months.
Commission rate structure — same vs declining
Some operators pay a declining rate: 30% on the first 3 months, 20% thereafter. This incentivises referrals while limiting the operator's long-term commission liability.
RISER Nation standard: consistent rate for all months. If a declining rate is used: this must be stated explicitly and agreed in writing before the first referral is made.
Lifetime cap (if applicable)
Some operators apply a total lifetime commission cap per referred subscriber — the partner earns commission until the referred subscriber has generated X× their commission in revenue.
RISER Nation standard: no lifetime cap unless specifically agreed for a specific deal. The standard position is that the referring partner earns commission as long as the subscriber remains active.
PHASE 1
The Launch JV Deal Structure — In Full Detail
The commercial architecture for live launch joint venture promotions
Launch Phase
Commission Rate
Qualifying Sales
Notes
Standard Affiliate Base Rate (Tier 1)
30–35% of net sale price
All confirmed sales through the launch window
Available to all approved affiliates in the standard tier. No minimum sales volume required to participate at this tier.
Active Launch Promoter Rate (Tier 2)
35–40% of net sale price
Partners who have sent at least 2 promotional emails during the launch window AND generated at least 5 confirmed sales
The upgraded rate is applied retroactively to ALL sales from the first sale — not only to sales above 5. Retroactive application creates a motivation to reach the milestone threshold quickly.
Super Affiliate Rate (Tier 3)
40–45% of net sale price
Partners who have generated at least 20 confirmed sales during the launch window
Applied retroactively to all sales from this partner. The tier 3 threshold is ambitious — set it at a level that requires genuine promotional effort from the partner's best-performing list sends.
Leaderboard Bonus (Top 3)
Cash prize above and beyond commission
Top 3 positions on the launch sales leaderboard
1st place: $[X] — 2nd place: $[Y] — 3rd place: $[Z]. Scale these to the launch size: for a $200K launch, 1st place $1,500–$3,000 is typical. The prize must be meaningful enough to motivate the final promotional push.
The Retroactive Rate Upgrade — Why It Matters
The tiered launch commission system produces maximum promotional effort only if the tier upgrade is retroactive — applied to all sales from the first sale, not only to marginal sales above the tier threshold. Here is why: if an affiliate has generated 18 sales at the Tier 2 rate (35%) and the Tier 3 threshold is 20 sales at 40%, the marginal value of generating 2 more sales is: (2 sales × $997 net × 5% additional rate) = $99.70 in additional commission. Marginal effort for $99.70 may not be worth the extra email to the list. But if the upgrade is retroactive: the value of generating 2 more sales is (20 sales × $997 net × 5% additional rate) = $997 — nearly 10× the marginal value. The retroactive structure creates the final promotional push that drives leaderboard competition.
Attribution Scenario
RISER Nation Standard
Rationale
Buyer clicks affiliate link and purchases during the launch window
Full commission at the qualifying tier. Straightforward.
Standard last-click, in-window attribution.
Buyer clicks affiliate link during the launch window but purchases after cart close (within 7 days)
Full commission at the qualifying tier (the 7-day post-close grace window applies).
Some buyers need time after the urgency deadline to complete their decision. A 7-day post-close grace window captures these buyers without the partner losing credit for generating genuine purchase intent.
Buyer clicks affiliate link before the launch opens (pre-launch warm-up period)
Commission attributed if the purchase occurs during the launch window or within the 7-day post-close grace window. The click was within the cookie window.
Pre-launch click activity from a partner's audience is evidence of successful pre-launch promotion — the partner's pre-launch send generated the purchase intent.
Buyer clicks multiple affiliate links (from different affiliates) before purchasing
Last-click attribution: the most recent affiliate link clicked before the purchase receives full commission. No split commission.
Last-click attribution is the simplest, most transparent, and most defensible standard. Split attribution models are more 'accurate' but create calculation complexity that produces disputes.
Buyer purchases using a coupon code associated with a specific affiliate (not a tracked link)
Commission attributed to the affiliate whose coupon code was used, regardless of whether a tracked link was also clicked.
Some affiliates promote with coupon codes rather than tracked links. The coupon code is an explicit affiliate identifier and should produce the same commission attribution as a tracked link.
Buyer requests a refund within the refund window
Commission reversed. If already paid: deducted from the next payment cycle or recovered from the affiliate's outstanding balance.
Commission on a refunded sale represents the partner earning money on a transaction that did not hold. The refund reversal is standard and should be stated explicitly in the partner agreement before the launch.
PHASE 2
The Evergreen Affiliate Deal Structure
The commercial architecture for ongoing, non-launch promotions
Tier
Qualification
Commission Rate
Payment Terms
Benefits
Standard Affiliate
Approved affiliate, 0+ sales in any period
30% of net sale price
Paid on the 15th of the following month for all confirmed (non-refunded, outside refund window) sales from the prior month. Minimum payout: $50.
Standard asset library access. Real-time dashboard. Monthly payment.
Active Affiliate
5+ confirmed sales in the prior 3 months OR 10+ in the prior 12 months
35% of net sale price. Applied to all sales once the threshold is met — the upgrade is not retroactive for the month, but applies from the qualification date forward.
Same payment terms. No minimum payout threshold.
Priority asset library updates, early access to new offer launches, included in the launch JV invitation list.
Super Affiliate
20+ confirmed sales in the prior 3 months OR $10,000+ in referred net revenue in the prior 12 months
40% of net sale price.
Same payment terms. Mid-month commission advance available for affiliates generating above $500/month in commissions — 50% advance on the 1st, remainder on the 15th.
All Active benefits plus: co-creation opportunities, personal relationship development with the Founder, first right of refusal on JV launch spots, custom promotional support.
Tier Assessment
Timing
Notice Period
Downgrade Trigger
Exception
Active → Standard downgrade
First Monday of each quarter for the prior quarter's performance
30-day written notice before the downgrade takes effect
Fewer than 3 sales in the prior 3 months AND fewer than 8 sales in the prior 12 months
An affiliate on approved leave or in a documented hiatus period (agreed with the Affiliate Manager) is not subject to automated downgrade.
Super Affiliate → Active downgrade
First Monday of each quarter
30-day written notice
Fewer than 10 sales in the prior 3 months AND less than $5,000 in referred net revenue in the prior 12 months
Same exception as above.
PHASE 3
The Tiered Leaderboard Commission Structure — Full Architecture
The competitive commission system for maximum launch promotional effort
Design Element
Standard
Rationale
Number of paid positions
Top 3 positions. Not top 10 — too many paid positions dilute the competitive motivation. The operator wants the affiliates who are genuinely in contention for 1st, 2nd, and 3rd to feel that the prize is within reach.
More than 3 prize positions reduces the scarcity that motivates maximum effort. An affiliate who is in 8th place does not feel close enough to 1st place to make an extra send.
Prize amounts
1st: 2–3× the average affiliate's expected launch commission. 2nd: 1.5×. 3rd: 1.0×. Scale with the launch size — for a $500K launch: 1st $3,000–$5,000, 2nd $1,500–$2,500, 3rd $750–$1,250.
The prize must be large enough to motivate the specific extra sends that move a strong affiliate from 4th place to 3rd. If the prize is $50 for 3rd place: it will not motivate an extra send that the affiliate values at the audience relationship cost.
Real-time visibility
The leaderboard is updated in real time and accessible to all participating affiliates during the launch window.
Real-time visibility creates moment-to-moment competitive engagement. An affiliate who checks the leaderboard and sees they are 2 sales behind 3rd place will consider an extra send. An affiliate who gets a weekly update has no moment-to-moment engagement.
Bonus structure disclosure
The leaderboard and all prize amounts are communicated to affiliates in the JV Partner Brief — before the launch opens, not revealed as a surprise incentive mid-launch.
Affiliates plan their promotional schedule in advance. A leaderboard that is revealed mid-launch cannot be incorporated into the pre-launch planning that determines how many promotional sends the affiliate commits.
Tie-breaking rule
In the event of a tie for any prize position: the affiliate who reached the tied sales count first (earlier timestamp) wins the higher position.
A clear, objective tie-breaking rule prevents post-launch disputes about who 'actually' won a position.
Minimum promotional activity requirement
To be eligible for a leaderboard prize: the affiliate must have sent at least [X] confirmed promotional emails during the launch window. An affiliate who generated all sales from a single send to a warm list wins the position but must meet the minimum promotional effort standard.
The minimum activity requirement prevents a scenario where an affiliate with a tiny but highly responsive list wins the leaderboard without making promotional effort — which discourages the larger-list affiliates who made genuine multi-send efforts.
LEADERBOARD LAUNCH COMMISSION CALCULATION — 5-Day Launch, 8 Active Affiliates
THE LAUNCH PARAMETERS
Offer price: $997 (one-time payment option)
Launch window: 5 days
Refund window: 30 days
Commission tiers: Tier 1 (30%) / Tier 2 (35% retroactive above 5 sales) / Tier 3 (40% retroactive above 20 sales)
Leaderboard prizes: 1st: $2,500 | 2nd: $1,000 | 3rd: $500

AFFILIATE A — THE TOP PERFORMER
Sales: 35 confirmed sales during the launch window
Transaction average (net after payment processing): $967.79

Tier assessment: 35 sales → Tier 3 (40%, retroactive)
Commission: 35 × $967.79 × 40% = $13,549.06
Leaderboard prize (1st place): $2,500
Total earnings: $13,549.06 + $2,500 = $16,049.06

What Affiliate A earned without the retroactive structure (Tier 1 on first 5, Tier 2 on next 15, Tier 3 on final 15):
First 5 sales at 30%: 5 × $967.79 × 30% = $1,451.69
Next 15 sales at 35%: 15 × $967.79 × 35% = $5,080.90
Final 15 sales at 40%: 15 × $967.79 × 40% = $5,806.74
Total without retroactive: $12,339.33
Retroactive bonus vs non-retroactive: $1,209.73 extra earned through the retroactive structure

AFFILIATE B — THE SECOND-PLACE FINISHER
Sales: 22 confirmed sales
Tier: 3 (40%, retroactive)
Commission: 22 × $967.79 × 40% = $8,516.55
Leaderboard prize (2nd place): $1,000
Total earnings: $8,516.55 + $1,000 = $9,516.55

OPERATOR ECONOMICS CHECK
Total sales from all affiliates: assume 120 confirmed sales across all 8 affiliates
Total gross revenue: 120 × $997 = $119,640
Total net revenue (after payment processing): 120 × $967.79 = $116,134.80
Estimated refunds (3%): 3.6 sales → approximate reversal: 3.6 × $967.79 = $3,484.04
Net confirmed revenue: $116,134.80 - $3,484.04 = $112,650.76

Total affiliate commissions paid (across all tiers): [Sum of all affiliate commissions]
Leaderboard prizes total: $2,500 + $1,000 + $500 = $4,000
Broker commissions (if applicable): [X]
Total partnership costs: [Sum above]
Net operator revenue: $112,650.76 - [Total partnership costs]

THE OPERATOR'S MINIMUM CHECK
Before setting any commission structure: confirm the total commission payout (across all tiers) plus leaderboard prizes leaves the operator above the minimum viable gross profit margin after delivery costs. A launch that produces $200K in revenue but pays out $120K in commissions and costs $40K to deliver is a $40K net result — not a success.
PHASE 4
The Reciprocal Deal Structure — Audience-for-Audience Mathematics
B45309
THE RECIPROCAL DEAL EQUITY CALCULATION
PARTY A (RISER NATION OPERATOR)
List size: [A subscribers]
Average open rate: [A-OR]%
Estimated engaged readers per send: [A subscribers] × [A-OR]% = [A-engaged]
Average click rate on promotional content: [A-CTR]%
Estimated clicks to partner's resource: [A-engaged] × [A-CTR]% = [A-clicks]
Estimated opt-ins for partner (at 30% Bridge Page conversion): [A-clicks] × 30% = [A-optins]
Estimated EV of those opt-ins for partner (at their buyer conversion rate × offer value): [A-optins] × [partner-CVR]% × $[partner-AOV] = $[A-EV]

PARTY B (THE PARTNER)
List size: [B subscribers]
Average open rate: [B-OR]%
Estimated engaged readers per send: [B subscribers] × [B-OR]% = [B-engaged]
Average click rate: [B-CTR]%
Estimated clicks to RISER NATION resource: [B-engaged] × [B-CTR]% = [B-clicks]
Estimated opt-ins for RISER NATION: [B-clicks] × 35% = [B-optins]
// Note: RISER NATION Bridge Page conversion rate is typically higher than average (35%+) because of the context block.
Estimated EV of those opt-ins for RISER NATION (at buyer conversion rate × offer value): [B-optins] × [RN-CVR]% × $[RN-AOV] = $[B-EV]

THE EQUITY ASSESSMENT
Ratio: $[A-EV] ÷ $[B-EV] = [ratio]
Within 0.5× – 2.0×: the exchange is broadly equitable. Proceed as a direct mutual swap.
Below 0.5× (RISER NATION produces significantly less value): offer an offset — an additional value exchange that compensates Party B.
Above 2.0× (RISER NATION receives significantly more value): the exchange is weighted in RISER NATION's favour. Propose an adjusted swap: RISER NATION promotes Party B's resource twice, or to a larger segment, or offers an additional piece of value.
Offset Type
When to Use It
How to Value It
Disclosure to Partner
Additional promotional send
RISER NATION sends to their list twice in exchange for one send from the partner — or sends to a larger segment than would produce equivalent value.
Calculate the estimated opt-in difference between the two parties' sends. The additional send should close the gap to within the 0.5×–2.0× equity range.
Explicit: 'My list is smaller than yours but I want this to be fair. I am proposing sending to you twice — once for a newsletter mention and once for a dedicated send — to make the exchange more equitable.'
Content contribution
RISER NATION produces an episode, a guest post, or a piece of long-form content for the partner's channel in addition to the email swap.
Value the content contribution at the estimated time × hourly rate of the Founder. Compare to the opt-in value differential.
Offer this as a genuine contribution to the partner's audience, not just a compensating transaction. The content should stand on its own as valuable to the partner's audience.
Future cash commission
If the exchange is significantly inequitable and cannot be balanced by additional sends: offer the larger-list partner a referral commission on any sales generated from their send — converting the reciprocal into a hybrid arrangement.
Commission on net sales: the same rate as the standard affiliate programme. This converts an inequitable swap into a standard affiliate deal.
Explicit: 'Given the size difference between our lists, I want to make sure this is worth your while. I am happy to add a commission on any sales generated from your send — [X]% on net sales.'
Value-in-kind offset
RISER NATION offers a direct value exchange that is not a promotional send: a podcast interview appearance, a community presentation, priority access to a new resource, or an introduction to a specific person in their network.
Assessed jointly — what is the value of the specific access or introduction to the partner? This is a relationship-based assessment, not a formula.
Offered as a genuine relationship gesture: 'I know my list is smaller than yours. I want to propose something additional that might be more valuable to you than a second email send...'
Revenue Model
Structure
Calculation Basis
Minimum Requirements
Operator's Risk
Revenue Share
The white-label partner enrols students and the RISER NATION operator receives a percentage of each enrolment fee. No upfront payment from either party.
[X]% of gross enrolment revenue. Payment monthly on the 15th for prior month enrolments. Refund policy mirrors the standard RISER NATION refund policy.
Minimum 1,000 engaged audience members in an avatar-aligned community. Delivery capability confirmed: the partner can deliver the programme effectively to their students.
High — no guaranteed income. Revenue is entirely contingent on the partner's enrolment performance.
Annual Licence Fee
The partner pays a fixed annual fee for the right to use and deliver the programme under their brand. Revenue share is not applicable — the operator receives the licence fee regardless of enrolment performance.
Fixed annual fee: $[X,000]–$[XX,000] based on audience size, market, and exclusivity scope. Due on the agreement date. Renewal date: 12 months from the initial agreement.
Audience size above [X] subscribers or community members. Prior evidence of successful programme delivery in a related domain.
Low — the licence fee is guaranteed regardless of the partner's performance. Risk is limited to the reputational impact of poor delivery by the partner.
Per-Student Licence
The partner pays a fixed fee per enrolled student at the point of enrolment. Scales with the partner's performance.
$[X] per confirmed enrolled student. Invoice issued monthly for the prior month's enrolments. No minimum enrolment guarantee.
Same requirements as Revenue Share. The per-student model requires the same delivery capability assessment.
Medium — income is tied to the partner's enrolment activity. More predictable than Revenue Share (fixed amount per student vs variable revenue share) but still performance-dependent.
Minimum Guarantee + Revenue Share
The partner pays a minimum annual guarantee (covering the RISER NATION operator's baseline risk) plus a revenue share on enrolments above a threshold.
Minimum guarantee: $[X,000]/year, paid quarterly in advance. Revenue share: [X]% of gross enrolment revenue above [Y enrolments or $Z revenue] per year.
Higher audience size requirement than pure Revenue Share — the minimum guarantee is only economically viable for partners with sufficient volume to justify the guarantee payment.
Low on the baseline (guaranteed by the minimum). Upside from the revenue share above the threshold.
Protection Clause
Standard Language Required
What Happens Without It
Non-competition scope
The partner may not use the licensed content, methodology, or framework to offer a directly competing programme to the RISER NATION operator's primary audience during the term of the agreement and for [X] months after termination.
The partner uses the licensed content to build their own competing programme, directly eroding RISER NATION's addressable market.
Quality standard maintenance
The partner must maintain the programme delivery at a standard that does not damage the RISER NATION brand or the programme's reputation. RISER NATION reserves the right to conduct a quality review and to terminate the licence if quality standards are not met.
The partner delivers the programme poorly, students complain, negative reviews associate the programme name with poor delivery, and the RISER NATION brand is damaged by content the operator no longer controls.
Attribution requirement
In all marketing, promotional, and delivery materials: the partner must acknowledge that the programme is delivered under licence from RISER NATION / [Founder Name]. The attribution format is: '[Programme Name], developed by [Founder Name] / RISER NATION, delivered under licence by [Partner Name].'
The partner presents the programme as their own original content, potentially raising IP ownership disputes when the original methodology is publicly associated with the partner's brand.
Termination and content recovery
Upon termination of the licence: the partner immediately ceases delivery of the programme and removes all RISER NATION materials from their platforms. A 60-day wind-down period is permitted only for students currently enrolled before termination.
The partner continues delivering the programme after the licence ends — whether due to oversight or intent. Without a clear termination clause, enforcement is difficult.
STANDARD JV DEAL AGREEMENT — Plain Language Version
AGREEMENT IDENTIFICATION
Agreement Date: [ ]
Between: [RISER NATION Operator Name] ('the Operator') and [Partner Name] ('the Partner')
Deal Type: [Revenue Share / Flat Fee / Hybrid / Reciprocal / Tiered Launch / White-Label / Licensing]

THE PROMOTED OFFER
Offer Name: [ ]
Offer Price: $[ ] (one-time) OR $[ ]/month (subscription) OR $[ ] for a [X]-payment plan of $[ ]/month
Offer URL: [ ]

THE PARTNER'S PROMOTIONAL OBLIGATION
The Partner agrees to:
— Send [X] promotional email(s) to their email list of approximately [Y] subscribers during the period [Start Date] to [End Date]
— [Any additional promotional activities agreed: social posts, podcast mentions, etc.]

The Operator will provide the Partner with: [list of assets provided — email templates, graphics, affiliate link, Partner Brief]

COMMISSION TERMS
Commission rate: [X]% of the net sale price after payment processing fees and confirmed refunds
OR flat fee of $[X] per confirmed sale
OR: [describe the specific hybrid or tiered structure if applicable]
Commission basis: Net sale value (gross transaction value minus payment processing fees only; refunds handled separately)
Payment plan attribution: Commission paid on each collected payment at the above rate (not on the total committed plan value at point of enrolment)

REFUND POLICY
The Operator's standard refund policy: [X] days from purchase date
Commissions on refunded sales: reversed if the refund occurs before the commission has been paid. Reversed against the next payment cycle if the refund occurs after the commission has been paid.

ATTRIBUTION AND TRACKING
Tracking platform: [Platform name — e.g., ThriveCart, Rewardful]
Partner's unique affiliate link: [ ]
Attribution model: Last-click, [X]-day cookie window
The Partner acknowledges that their commission dashboard provides real-time access to their click and conversion data.

PAYMENT SCHEDULE
Payment date: [The Xth of each month] for commissions confirmed in the prior month (outside the refund window)
Minimum payout: $[X] (balances below this roll to the following cycle)
Payment method: [PayPal / Wise / ACH / Other] to [Partner's registered payment detail]

FOR LAUNCH DEALS — SPECIFIC TERMS
Launch window: [Open Date] to [Close Date]
Attribution window post-close: [X] days
Tiered commission structure (if applicable): [State all tiers and thresholds]
Retroactive tier upgrade: [Yes / No — if yes, all sales are upgraded when the tier is reached]
Leaderboard prizes: [State all prize positions and amounts]
Payment timing for launch commissions: within [10] business days of cart close, after the refund window

FTC AND COMPLIANCE
The Partner confirms they understand their FTC (and equivalent) disclosure obligations for all promotional content referencing this offer.
The Operator confirms the offer is accurately described in the provided materials.

BOTH PARTIES AGREE
[Operator signature / confirmation] | Date: [ ]
[Partner confirmation — email confirmation is acceptable for standard deals] | Date: [ ]
Request Category
Common Requests
RISER NATION's Assessment Approach
Standard Response
Commission rate above the published tier
'I want 50% instead of 40%.' 'My list is so targeted I want 55% for this promotion.'
Run the economics: at the requested rate, does the deal still produce a net positive result above the minimum viable gross profit margin? If yes: consider it. If no: decline regardless of the partner's list quality. A deal that erodes the gross margin is not a good deal at any commission rate.
'Our published Super Affiliate rate is 40%. I cannot go above this for a standard commission structure — it creates equity issues with other partners at the same tier. If your results consistently justify it, the next step is a custom hybrid arrangement with a base fee.'
Attribution window extension
'I want a 90-day cookie rather than 30 days.'
Assess the offer's purchase timeline. If 90% of purchases from this partner's audience happen within 14 days of the click: a 90-day cookie is not meaningful and costs nothing to grant. If purchases regularly happen at 60–90 days: the extension materially increases the commission cost.
'Our standard attribution window is 30 days. We can extend to 45 days for partners whose audience has a documented longer decision cycle — which we can verify from the attribution data after your first promotion.'
Exclusivity requests
'I want to be the only affiliate promoting your programme in my specific niche/geography/audience segment for 6 months.'
Assess the exclusivity scope. Geographic exclusivity (only promoting in a specific country) may be acceptable. Niche exclusivity (the only affiliate in 'the female entrepreneur space') may cut off the most valuable Dream 100 relationships. Duration: never more than 6 months and only with a performance threshold.
'We do not offer category exclusivity because it limits our ability to serve our audience through other trusted relationships. We can offer a first-right-of-refusal for 90 days — if we are planning a promotion to a new partner in your specific audience segment, we will notify you first and give you 7 days to match or better the deal.'
Special terms for their existing buyers
'My existing buyers should get a discount if they purchase through my link — and I still want the full commission on their purchase.'
The operator pays commission on the discounted price (not the full price) while the partner receives the benefit of higher conversions from the discount. The discount reduces the commission base but increases the conversion rate. Model the economics both ways.
'We can offer a [X]% discount to your existing community through a coupon code specific to your link. Your commission would be calculated on the discounted price — but the conversion rate will likely be higher, which should net out positively for you. Let me calculate the expected outcome both ways.'
Non-Negotiable Item
Why It Cannot Be Changed
All terms in writing before promotion begins
Verbal agreements are not enforceable in practice. An operator who 'agreed verbally' to specific terms cannot prove what was agreed if a dispute arises at payment time. No exceptions.
Refund reversal policy
Commissions are not paid on refunded sales. An operator who pays commissions on refunded sales is subsidising buyer risk with partnership capital. No exceptions, regardless of how trusted the partner is.
Independent commission tracking
The operator maintains their own commission records independent of what the affiliate platform reports. These records are the source of truth for any dispute. No partner has the right to demand that the operator's internal records be replaced by the partner's own tracking.
Payment plan attribution to collected payments
Commissions are paid as payments are collected — not on the total committed plan value. This protects the operator from paying commissions on revenue that was never collected.
FTC compliance obligation
Every promotional email and social post must comply with FTC disclosure requirements. The operator's obligation to ensure their partners are informed of this requirement does not transfer the legal obligation to the operator — but it is a non-negotiable programme participation condition.
Field
Type
Notes
Deal Structure ID
Short text
Format: DS-[Partner ID]-[YYYY-MM]. e.g. DS-PART-042-2026-09
Partner
Link → Dream 100 Partner Records
Deal Structure Type
Single select
Revenue Share / Flat Fee / Hybrid / Reciprocal / Tiered Launch / White-Label Revenue Share / Annual Licence / Per-Student Licence / Minimum Guarantee + Rev Share
Offer Being Promoted
Short text
Offer Net Sale Value (standard one-time)
Currency
The net sale value used as the commission basis
Commission Rate — Tier 1 (Base)
Number
% or flat dollar amount
Commission Rate — Tier 2 (if tiered)
Number
% and threshold for tier upgrade
Commission Rate — Tier 3 (if tiered)
Number
% and threshold for tier upgrade
Tier Upgrade Retroactive
Checkbox
Is the tier upgrade retroactive to first sale?
Leaderboard Active
Checkbox
Does this deal include a leaderboard competition?
Leaderboard Prize 1st
Currency
Leaderboard Prize 2nd
Currency
Leaderboard Prize 3rd
Currency
Attribution Window (days)
Number
Standard: 30
Attribution Model
Single select
Last Click / First Click / Linear (non-standard — requires explicit documentation)
Payment Plan Attribution
Single select
Per Collected Payment (standard) / On Committed Value (non-standard — requires explicit justification)
Refund Reversal Policy
Checkbox
Confirmed: commissions reversed on refunded sales
Payment Date
Short text
e.g. '15th of following month'
Minimum Payout Threshold
Currency
Deal Start Date
Date
Deal End Date (if launch or fixed-term)
Date
Post-Close Attribution Window (launch deals)
Number
Days after cart close within which sales are attributed
Written Agreement Confirmed
Checkbox
Agreement Document Link
URL
Link to the written agreement or email confirmation
Non-Standard Terms (if any)
Long text
Describe any deviations from the RISER NATION standard terms
Rationale for Non-Standard Terms
Long text
Why the deviation was agreed

Assigned source documents: RISER-Master-SOP-Catalogue (1).docx — source 1 · RISER-Master-SOP-Catalogue (1).docx — source 2 ·

Choose and use the right RISER operating procedure

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

Assigned lessons: 03.3, 06.2, 07.1, 12.4, 12.5. The spreadsheet’s twelve-course structure controls placement. The C1–C55 references below preserve this source’s older numbering.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Video placeholder

Video to be recorded: navigating the operating procedures and choosing the next implementation resource. The complete teaching text follows below.

Lesson outline and outcome

Understand how the nine source tracks build on one another.
Use each catalogue entry to identify the correct supporting document.
Choose the next procedure from a specific business bottleneck.
Keep source identity, implementation evidence and review status separate.

Opening script

In this lesson, we will use the Master SOP Catalogue as a navigation tool. Start with the result you need to produce. Then find the procedure that addresses that result, inspect its inputs and create the required output. Reading an index is the beginning of implementation; the detailed procedure must supply the actual steps, templates and decision rules.

The catalogue contains 111 entries: 55 core entries and 56 supplementary entries. Some documents appear in more than one context. That is useful cross-referencing, so we retain each occurrence while avoiding duplicate claims of source completion.

Framework alignment

Connect Brunson’s audience relationships and offer progression to the appropriate traffic and conversion resources. Use Hormozi’s value framework to examine the desired outcome, confidence in achieving it, delay and buyer effort. These frameworks guide offer design; local evidence determines whether a particular execution works.

Supporting sources: ClickFunnels — Dream 100 · Acquisition.com — Offers course

The nine-track sequence

Track 1: Operator foundation

Start with your decision process, market problem and relevant experience. Write the problem you intend to solve, the evidence that would change your mind and the skills you can demonstrate. This gives later buyer research a testable starting point.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 2: Buyer intelligence

Build a buyer description from evidence and identify who the offer should exclude. Separate observed language, your interpretation and unresolved questions. Use demand evidence before committing to an offer; an attractive persona alone is insufficient.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3: Offer design and validation

Turn the validated problem into a specific transformation, delivery scope and commercial offer. Use the value ladder to connect appropriate next purchases. Design bonuses around obstacles, then test delivery and willingness to buy before increasing promotion.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 4: Persuasion and messaging

Translate the offer into a clear hook, explanation, proof and next step. Use the buyer’s actual objections to improve understanding. A persuasive structure must communicate supported value; it does not justify invented urgency, results or testimonials.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 5: Content and discoverability

Choose content that answers real buyer questions and demonstrates expertise. Connect channel strategy, content quality, technical search foundations and answer clarity. Search and AI visibility are outcomes to measure, not promised positions.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6: Conversion and traffic

Connect useful entry resources, email follow-up, sales pages and appropriate acquisition channels. Track each transition from visitor to subscriber to qualified buyer. Separate observed competitor structure from evidence of conversion performance.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 7: Data, automation and technical continuity

Identify the information the business needs, where it lives and how it can be recovered. Document a repeatable process before automating it. Define review gates, access limits and exception handling for AI-assisted work.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8: Retention and growth

Grow from a working delivery system. Review buyer outcomes, retention, complementary offers, partnerships and capacity before expanding into another market. International or regulated activity requires the specific applicable rules, beyond this catalogue’s descriptions.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 9: AI governance and continuity of the business

Assign bounded jobs, evaluation criteria and human decision owners to AI systems. Connect monitoring and quality checks to operational decisions. Treat executive automation, foresight and legacy planning as design objectives that require evidence and ongoing oversight.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Read the navigation fields before choosing a document

The core index uses four fields: legacy course number, SOP title, filename and description. The supplementary index uses the supporting course or topic group instead of a single core-course number. Match the title and exact filename before relying on the legacy number; different documents can use different numbering systems.

The source describes a sequential learning path, with buyer intelligence preceding the commercial offer and a working delivery system preceding scale. Use that sequence to identify missing inputs, while retaining your actual assignment in the twelve-course academy. For an already operating business, select the procedure that addresses the current constraint and inspect its prerequisites rather than assuming every earlier resource has been completed.

The catalogue is an index of intended scope, not proof that all named templates, thresholds or procedures exist in the linked file. Check the full source, version and access. For example, this catalogue describes JV deal structures as including equity, while the reviewed D0933 source centers five promotional structures and four licensing models without a developed equity-deal procedure. Keep the discrepancy visible rather than inventing equity terms.

The stated 95-plus total and 40-plus supplementary count are broad lower bounds. This version contains 55 core rows and 56 supplementary rows, or 111 occurrences. The Long-Form YouTube resource occurs in both the core and supplementary context. Occurrences are not unique source reviews.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Resource-by-resource scope

For every entry below, the scope paragraph preserves the catalogue’s description. It tells you what the named source intends to cover. Programme names and descriptions do not establish guaranteed outcomes, validated benchmarks or legal compliance. Open the linked document for its full method before implementing it.

C1 — The Sovereign Operator Mindset

Source filename: RISER-Sovereign-Operator-Mindset-SOP.docx

Catalogue scope: The foundational mindset and identity framework for the knowledge business operator. Covers the shift from employee mindset to sovereign operator, the RISER Nation operating principles, and the daily practices that establish the psychological infrastructure for building at scale.

Supporting sources: D2225 — RISER-Sovereign-Operator-Mindset-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C2 — Market Reality (2025–2035)

Source filename: RISER-Market-Reality-2025-2035-SOP.docx

Catalogue scope: A forward-looking map of the forces reshaping the knowledge economy across the decade. Covers the AI transformation of content and expertise markets, the compression of trust timelines, the shift from information scarcity to attention scarcity, and the operator’s strategic positioning in this landscape.

Supporting sources: D2215 — RISER-Market-Reality-2025-2035-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C3 — Decision Intelligence & Risk Management

Source filename: RISER-Decision-Intelligence-Risk-Management-SOP.docx

Catalogue scope: The systematic framework for making high-quality decisions under conditions of incomplete information, time pressure, and consequence. Covers the Decision Intelligence Protocol, risk categorisation, reversible versus irreversible decisions, and the biases that produce poor operator decisions at scale.

Supporting sources: D4084 — RISER-Decision-Intelligence-Risk-Management-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C4 — Problems Create Markets — Market Gap Detection

Source filename: RISER-Problems-Create-Markets-SOP.docx

Catalogue scope: The methodology for identifying commercially viable market problems that are large enough to build a knowledge business on. Covers the Problem Hierarchy, the Market Gap Detection Protocol, the difference between a problem and a preference, and the evidence standards for confirming a market exists before building an offer.

Supporting sources: D0220 — RISER-Problems-Create-Markets-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C5 — Skill & Experience Mapping

Source filename: RISER-Skill-Experience-Mapping-SOP.docx

Catalogue scope: The structured inventory process for identifying the operator’s genuine expertise, lived experience, and transferable skill sets. Covers the Skill-Experience Matrix, the Expertise Depth Assessment, the distinction between knowledge the operator has versus knowledge they have applied with results, and the connection between the operator’s experience and their Core Offer’s mechanism.

Supporting sources: D3485 — RISER-Skill-Experience-Mapping-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C6 — Pattern Recognition

Source filename: RISER-Pattern-Recognition-SOP.docx

Catalogue scope: The framework for reading the deeper patterns in market data, buyer language, and competitive positioning that are not visible from surface-level research alone. Covers the Pattern Recognition Protocol, how to identify recurring themes in buyer conversations that indicate genuine market pain, and the specific signals that separate a trend from a pattern.

Supporting sources: D2956 — RISER-Pattern-Recognition-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C7 — Psychographic DNA

Source filename: RISER-Psychographic-DNA-SOP.docx

Catalogue scope: The complete buyer intelligence framework that goes beyond demographics to capture the buyer’s worldview, values, fears, desires, prior attempts at the transformation, and the specific language they use to describe their problem. The Psychographic DNA is the single most referenced source document in the entire RISER Nation system, used in every content, copy, and offer decision.

Supporting sources: D0221 — RISER-Psychographic-DNA-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C8 — Negative Avatar Modelling

Source filename: RISER-Negative-Avatar-Modelling-SOP.docx

Catalogue scope: The systematic process for defining who the business should not serve. Covers the Negative Avatar profile (the buyer who will never succeed with the methodology regardless of the operator’s efforts), the financial and reputational cost of serving misaligned buyers, and how to incorporate Negative Avatar criteria into the sales page, the Traffic Hook, and the qualification process.

Supporting sources: D1292 — RISER-Negative-Avatar-Modelling-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C9 — Niche Validation & StorySelling

Source filename: RISER-Niche-Validation-StorySelling-SOP.docx

Catalogue scope: The validation framework for confirming that the identified niche has sufficient commercial depth before major investment. Covers the three-stage Niche Validation Protocol, the Story Selling approach to qualifying buyer intent through narrative, and the minimum evidence thresholds that confirm a niche is viable.

Supporting sources: D2219 — RISER-Niche-Validation-StorySelling-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C10 — Hard Organic Proof Threshold

Source filename: RISER-Hard-Organic-Proof-Threshold-SOP.docx

Catalogue scope: The evidence standard that must be met before the operator invests in building the full Core Offer. Defines what constitutes genuine proof of market demand versus wishful interpretation of signals. Covers the Organic Proof Threshold scorecard, the minimum buyer conversations required, and the red flags that indicate a niche that appears valid but is not commercially viable.

Supporting sources: D1760 — RISER-Hard-Organic-Proof-Threshold-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C11 — Value Ladder Architecture

Source filename: RISER-Value-Ladder-Architecture-SOP.docx

Catalogue scope: The complete framework for designing the operator’s full offer ecosystem: from the free Traffic Hook through the SLO, Core Offer, Continuity, Premium, and Done-for-You tiers. Covers the pricing logic for each rung, the buyer journey through the ecosystem, and the relationship between each rung’s promise and the buyer’s progressive transformation.

Supporting sources: D0638 — RISER-Value-Ladder-Architecture-SOP (1).docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C12 — Offer Scorecard

Source filename: RISER-Offer-Scorecard-SOP.docx

Catalogue scope: A structured diagnostic tool for evaluating any offer against the eight dimensions that determine commercial viability. Covers the Offer Scorecard assessment criteria, how to interpret a low score in any dimension, and the specific fixes that address each type of offer weakness.

Supporting sources: D0487 — RISER-Offer-Scorecard-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C13 — Offer Stacking & Unbundling Strategy

Source filename: RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx

Catalogue scope: The framework for maximising perceived value at every price point through strategic inclusion and exclusion of offer elements. Covers the Offer Stacking Protocol (what bonuses and components to include at each tier), the Unbundling Strategy for creating lower-priced entry offers from existing curriculum, and the principle that perceived value must always exceed price.

Supporting sources: D0936 — RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C14 — Beta Testing Methodology

Source filename: RISER-Beta-Testing-Methodology-SOP.docx

Catalogue scope: The structured process for validating the Core Offer with a small group of real buyers before full launch. Covers the Beta Cohort selection criteria, the beta pricing strategy, the specific feedback mechanisms that produce actionable curriculum improvement data, and the evidence thresholds that confirm the offer is ready for full launch.

Supporting sources: D0725 — RISER-Beta-Testing-Methodology-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C15 — Hook Engineering & Attention Engineering

Source filename: RISER-Hook-Engineering-Attention-Engineering-SOP.docx

Catalogue scope: The systematic framework for creating hooks that capture attention in a saturated content environment. Covers the Five Hook Types, the Hook Quality Assessment Standard, the attention pattern interrupts that work across video, written, and audio formats, and the testing protocol for identifying which hook formulas resonate most strongly with the specific buyer profile.

Supporting sources: D2948 — RISER-Hook-Engineering-Attention-Engineering-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C16 — Scientific Persuasion & Influence Mastery

Source filename: RISER-Scientific-Persuasion-Influence-Mastery-SOP.docx

Catalogue scope: The evidence-based persuasion framework grounded in decision science, behavioural economics, and the psychology of belief change. Covers Cialdini’s principles in the knowledge business context, the Belief Change Sequence, the stages of buyer awareness and how to communicate at each stage, and the ethical distinction between persuasion and manipulation.

Supporting sources: D0382 — RISER-Scientific-Persuasion-Influence-Mastery-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C17 — Behavioral Logic & Nudge Theory

Source filename: RISER-Behavioral-Logic-Nudge-Theory-SOP.docx

Catalogue scope: The applied framework for designing buyer journeys that guide decisions without coercion. Covers choice architecture in the sales funnel, the nudge mechanisms that reduce buyer friction, default option design, commitment and consistency principles in offer design, and the specific nudge applications for each stage of the buyer journey.

Supporting sources: D0927 — RISER-Behavioral-Logic-Nudge-Theory-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C18 — Identity-Based Marketing

Source filename: RISER-Identity-Based-Marketing-SOP.docx

Catalogue scope: The framework for creating marketing that connects the operator’s offer to the buyer’s deepest sense of who they are and who they want to become. Covers identity bridging, the language of aspiration versus the language of outcome, and how to make the Core Offer feel like the natural expression of the buyer’s identity rather than an external purchase.

Supporting sources: D0357 — RISER-Identity-Based-Marketing-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C19 — NLP Live Conversation Frameworks

Source filename: RISER-NLP-Live-Conversation-Frameworks-SOP.docx

Catalogue scope: The structured conversational frameworks for live sales calls, application calls, and qualification conversations. Covers the NLP-based rapport, pacing, and leading techniques for live conversation, the seven qualification questions that identify genuine buyers, the re-frame protocols for common live conversation objections, and the call close structure.

Supporting sources: D2955 — RISER-NLP-Live-Conversation-Frameworks-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C20 — Objection Bank

Source filename: RISER-Objection-Bank-SOP.docx

Catalogue scope: The complete system for cataloguing, categorising, and resolving every objection the operator’s buyers raise. Covers the Objection Bank structure, the four objection categories (price, timing, belief, fit), the resolution frameworks for each category, and the process for updating the Objection Bank continuously from support tickets, community questions, and live call transcripts.

Source identity unresolved: the exact Objection Bank SOP was not located in the inventory. The catalogue link below supports this entry; related objection documents are not treated as substitutes without checking their content.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C21 — Attractive Character Development System

Source filename: RISER-Attractive-Character-Development-System-SOP.docx

Catalogue scope: The framework for developing the operator’s on-brand public persona: the Attractive Character elements (leader, adventurer, reporter, reluctant hero), the Brand Belief System (We Believe, We Reject), the Cultural Lexicon, the Origin Story structure, and the Tribe Formation Sequence. The Attractive Character is the public expression of the operator’s identity that makes the brand magnetic to the ideal buyer.

Supporting sources: D0356 — RISER-Attractive-Character-Development-System-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C22 — Content Calendar by Awareness Level

Source filename: RISER-Content-Calendar-Awareness-Level-SOP.docx

Catalogue scope: The content planning system based on the five levels of buyer awareness. Covers how to distribute content across awareness stages (Unaware, Problem Aware, Solution Aware, Product Aware, Most Aware), the content types that move buyers along the awareness spectrum, and the publishing cadence that maintains consistent presence without the operator becoming a content production machine.

Supporting sources: D2942 — RISER-Content-Calendar-Awareness-Level-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C23 — AI-Driven Content Repurposing System

Source filename: RISER-AI-Content-Repurposing-System-SOP.docx

Catalogue scope: The complete system for converting the operator’s flagship long-form content into multiple derivative formats using AI tools. Covers the repurposing hierarchy (podcast to YouTube to article to newsletter to social to clips), the AI-assisted workflows for each conversion, the quality standards for repurposed content, and the distribution schedule that maximises the reach of each piece of flagship content.

Supporting sources: D2936 — RISER-AI-Content-Repurposing-System-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C24 — Attractive Character Content Bible

Source filename: RISER-Attractive-Character-Content-Bible-SOP.docx

Catalogue scope: The editorial standard document that ensures all content produced across all channels and formats is consistent with the operator’s Attractive Character. Covers the Content Bible structure, the voice and tone guidelines, the thematic pillars, the recurring content formats, and the editorial decision-making framework for any content question that is not covered by specific campaign instructions.

Supporting sources: D0355 — RISER-Attractive-Character-Content-Bible-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C25 — Podcast as Primary Authority Channel

Source filename: RISER-Podcast-Primary-Authority-Channel-SOP.docx

Catalogue scope: The complete framework for building a podcast that serves as the operator’s flagship authority platform. Covers format selection, episode structure, interview guest strategy, show notes and SEO, the Traffic Hook integration, episode production workflow, distribution strategy, and the metrics that indicate a podcast is effectively building the operator’s audience and authority.

Supporting sources: D2222 — RISER-Podcast-Primary-Authority-Channel-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C26 — Technical SEO Foundations

Source filename: RISER-Technical-SEO-Foundations-SOP.docx

Catalogue scope: The complete technical SEO infrastructure for the knowledge business operator’s Owned Media Hub. Covers site architecture, crawlability, Core Web Vitals, on-page elements, schema markup, the initial keyword research and cluster architecture, the Quarterly Technical SEO Audit, and the Google Search Console monitoring protocol.

Supporting sources: D2227 — RISER-Technical-SEO-Foundations-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C27 — AEO, GEO & Machine Trust

Source filename: RISER-AEO-GEO-Machine-Trust-SOP.docx

Catalogue scope: The framework for optimising content to be cited, referenced, and recommended by AI search systems including Google’s AI Overview, Perplexity, and ChatGPT. Covers the Entity Establishment Protocol, answer-first content formatting, FAQPage and HowTo schema, the AEO Citation Monitoring System, and the specific content formats that AI systems preferentially cite.

Supporting sources: D2189 — RISER-AEO-GEO-Machine-Trust-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C28 — Email Fundamentals

Source filename: RISER-Email-Fundamentals-SOP.docx

Catalogue scope: The complete email marketing system architecture. Covers the email platform configuration, the Traffic Hook opt-in sequence, the 21-day Indoctrination Sequence that converts subscribers into buyers, the broadcast email calendar, the list segmentation and tagging architecture, the deliverability maintenance protocol, and the email metrics that determine whether the list is healthy and converting.

Supporting sources: D1285 — RISER-Email-Fundamentals-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C29 — Sales Page Architecture & Conversion Copy

Source filename: RISER-Sales-Page-Architecture-SOP.docx

Catalogue scope: The structural and copywriting framework for the Core Offer’s primary sales page. Covers the twelve-section sales page architecture, the hook-to-offer arc, social proof placement and hierarchy, the guarantee framework, the objection removal sequence, the CTA structure, and the split-testing protocol for continuous conversion rate optimisation.

Supporting sources: D0943 — RISER-Sales-Page-Architecture-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C30 — Paid Ads Foundations

Source filename: RISER-Paid-Ads-Foundations-SOP.docx

Catalogue scope: The foundational paid advertising framework covering the principles that apply across all paid channels: the Traffic Triangle (audience, offer, creative), the Traffic Hook campaign structure, the cold audience testing protocol, the budget allocation framework, and the campaign metrics hierarchy that determines what to optimise and when to scale.

Supporting sources: D1765 — RISER-Paid-Ads-Foundations-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C31 — Omni-Channel Retargeting Systems

Source filename: RISER-Omni-Channel-Retargeting-SOP.docx

Catalogue scope: The five-tier retargeting ecosystem that converts the warm audience into buyers. Covers the audience tier architecture (by intent stage), the retargeting sequences for each tier, the exclusion architecture that prevents wasted spend on existing buyers, the cross-platform deployment model, and the retargeting campaign metrics.

Supporting sources: D2220 — RISER-Omni-Channel-Retargeting-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C32 — Server-Side Tracking & Conversion APIs

Source filename: RISER-Server-Side-Tracking-SOP.docx

Catalogue scope: The technical setup and governance for server-side event tracking using the Meta Conversions API, Google Tag Manager server-side, and webhook-based event forwarding. Covers the Event Match Quality optimisation, the browser-to-server tracking stack, the event deduplication protocol, and the EMQ monitoring system.

Supporting sources: D2959 — RISER-Server-Side-Tracking-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C33 — Data Sovereignty — Dig Your Own Well

Source filename: RISER-Data-Sovereignty-SOP.docx

Catalogue scope: The complete framework for building platform-independent data infrastructure. Covers the Owned Asset Hierarchy, the email-first audience strategy, the monthly data export protocol, the Backup and Continuity Systems, and the specific configuration for ensuring the operator’s subscriber list, buyer records, and content assets cannot be lost through a single platform failure.

Supporting sources: D1851 — RISER-Data-Sovereignty-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C34 — Platform Immunity

Source filename: RISER-Platform-Immunity-SOP.docx

Catalogue scope: The risk management system for the operator’s dependency on third-party platforms. Covers the Platform Dependency Risk Matrix, the Platform Change Response Playbook, the monthly platform immunity audit, the diversification standard for each platform category, and the specific contingency procedures for the most common platform failure scenarios.

Supporting sources: D1852 — RISER-Platform-Immunity-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C35 — The RISER Automation Engine

Source filename: RISER-Automation-Engine-SOP.docx

Catalogue scope: The complete six-blueprint automation stack that removes the operator from routine operational execution. Covers Blueprint 1 (Purchase Router), Blueprint 2 (Onboarding Sequence), Blueprint 3 (Programme Completion Sync), Blueprint 4 (List Hygiene), Blueprint 5 (Refund & Cancellation), and Blueprint 6 (Daily Analytics Sync). The Automation Engine is the operational foundation of the entire Track 8 and Track 9 system.

Supporting sources: D2938 — RISER-Automation-Engine-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C36 — Make.com Blueprint Deployment

Source filename: RISER-Make-Blueprint-Deployment-SOP.docx

Catalogue scope: The technical implementation guide for all six Make.com blueprints in the RISER Automation Engine. Covers the specific module configurations, webhook structures, error handling protocols, and the testing sequence for confirming each blueprint is operating correctly before deploying to production.

Supporting sources: D3481 — RISER-Make-Blueprint-Deployment-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C37 — Advanced n8n & GitHub Automations

Source filename: RISER-Advanced-n8n-GitHub-Automations-SOP.docx

Catalogue scope: The implementation guide for the four AI-agent workflows built in n8n: the Content Research Agent (AI-Agent 1), the Buyer Support Triage Agent (AI-Agent 2), the Performance Summary Agent (AI-Agent 3), and the Objection Bank Updater Agent (AI-Agent 4). Covers self-hosted n8n setup, the GitHub version control protocol, and the agent governance framework.

Supporting sources: D3473 — RISER-Advanced-n8n-GitHub-Automations-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C38 — Vibe Coding & Generative Video Pipelines

Source filename: RISER-Vibe-Coding-Generative-Video-Pipelines-SOP.docx

Catalogue scope: The framework for using AI-assisted coding and generative video tools to build custom operator tools without traditional programming skill. Covers the Vibe Coding Protocol for building custom calculators and tools, the generative video pipeline for educational video production, and the quality standards for AI-generated multimedia assets.

Supporting sources: D2961 — RISER-Vibe-Coding-Generative-Video-Pipelines-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C39 — Scaling Foundations & Operational Readiness

Source filename: RISER-Scaling-Foundations-Operational-Readiness-SOP.docx

Catalogue scope: The gate assessment that confirms whether the business is genuinely ready to scale. Covers the five-dimension Scaling Readiness Audit (Delivery, Automation, Financial, Content, Operator Capacity), the five Scaling Failure Modes, the financial unit economics required before scaling investment begins, and the Operator Role Evolution sequence.

Supporting sources: D1401 — RISER-Scaling-Foundations-Operational-Readiness-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C40 — Offer Ecosystem & Backend Monetisation

Source filename: RISER-Offer-Ecosystem-Backend-Monetisation-SOP.docx

Catalogue scope: The complete six-rung Offer Ecosystem Map and the Backend Monetisation Sequence that maximises buyer lifetime value. Covers the post-purchase journey architecture (Order Bump, OTO, Early Win upsell, Graduation sequence), the Premium Offer design framework, the Continuity Engine design, the Ascension Path engineering, and the Ecosystem Revenue Optimisation Dashboard.

Supporting sources: D1293 — RISER-Offer-Ecosystem-Backend-Monetisation-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C41 — Customer Success & Retention Systems

Source filename: RISER-Customer-Success-Retention-Systems-SOP.docx

Catalogue scope: The complete buyer success infrastructure including the Buyer Health Score (five-component composite metric), the At-Risk Intervention Protocol (three levels), the First Win by Day 30 design framework, the Community Success Architecture, the Refund Prevention Framework, the Continuity Churn Prediction Model, and the Advocacy Activation System.

Supporting sources: D3479 — RISER-Customer-Success-Retention-Systems-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C42 — Retargeting Ecosystems & Warm Audience Monetisation

Source filename: RISER-Retargeting-Ecosystems-Warm-Audience-SOP.docx

Catalogue scope: The advanced retargeting architecture that serves every layer of the warm audience ecosystem simultaneously across the offer lifecycle. Covers the six-layer Ecosystem Audience Map, the Buyer Journey Retargeting sequences for each offer transition, cross-sell retargeting, the Lookalike Expansion Framework, advanced creative fatigue management, and the Retargeting P&L Dashboard.

Supporting sources: D1294 — RISER-Retargeting-Ecosystems-Warm-Audience-SOP (1).docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C43 — Long-Form YouTube Channel Strategy

Source filename: RISER-Long-Form-YouTube-Channel-Strategy-SOP.docx

Catalogue scope: The complete framework for building a long-form YouTube channel as a compounding authority and acquisition asset. Covers channel positioning, video SEO, the Traffic Hook integration, content calendar strategy for YouTube, retention optimisation, and the monetisation pathway from subscriber to Traffic Hook opt-in to Core Offer buyer.

Supporting sources: D2950 — RISER-Long-Form-YouTube-Channel-Strategy-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C44 — Advanced SEO & Search Domination

Source filename: RISER-Advanced-SEO-Search-Domination-SOP.docx

Catalogue scope: The advanced SEO framework for achieving topical authority and category dominance in the operator’s niche. Covers the four Topical Authority Stages, the Competitive Gap Mapping Protocol, Intent-Matching at page level, link acquisition through digital PR and Dream 100 outreach, the Content Refresh and Compounding System, SERP Feature Domination, the E-E-A-T Maximisation Protocol, programmatic SEO, and the Organic Search P&L Model.

Supporting sources: D2188 — RISER-Advanced-SEO-Search-Domination-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C45 — Global Market Expansion

Source filename: RISER-Global-Market-Expansion-SOP.docx

Catalogue scope: The systematic framework for expanding the knowledge business into new geographic markets. Covers the five-dimension Market Selection Framework and scoring tool, the English-language market expansion sequence (five phases), the Localisation Threshold Assessment for non-English markets, the Regulatory and Compliance Map (GDPR, VAT/GST, consumer protection), the International Payment Infrastructure, the Cultural Adaptation Protocol, and the JV Partner Model for new market entry.

Supporting sources: D2205 — RISER-Global-Market-Expansion-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C46 — Partnerships & Affiliate Scaling

Source filename: RISER-Partnerships-Affiliate-Scaling-SOP.docx

Catalogue scope: The complete partnership and affiliate ecosystem architecture for scaling revenue through third-party relationships. Covers the Dream 100 partnership hierarchy, the affiliate programme architecture, commission and tracking infrastructure, partner qualification criteria, and the scaling mechanisms that turn early JV wins into systematic partnership revenue.

Supporting sources: D1902 — RISER-Partnerships-Affiliate-Scaling-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C47 — Crisis Navigation & Reputation Command

Source filename: RISER-Crisis-Navigation-Reputation-Command-SOP.docx

Catalogue scope: The complete crisis prevention, response, and recovery system for the knowledge business. Covers the six Crisis Types, the Reputation Monitoring Protocol (four channels with alert thresholds), the First 24-Hour Response Framework, the Public Statement Architecture (six components), the Community Crisis Communication Protocol, the Negative Review Response System, the False Claims and Online Attack Protocol, the Evidence Bank, and the Anti-Fragile Reputation Strategy.

Supporting sources: D2201 — RISER-Crisis-Navigation-Reputation-Command-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C48 — Agentic Orchestration & Workflow Governance

Source filename: RISER-Agentic-Orchestration-Workflow-Governance-SOP.docx

Catalogue scope: The foundational governance architecture for all production AI agents. Covers the five Agentic Architecture Principles, the Six-Stage Agent Design Framework, the four Multi-Agent Orchestration Patterns (Sequential Pipeline, Parallel Fan-Out, Evaluator-Optimizer Loop, Orchestrator-Subagent Hierarchy), the Human-in-the-Loop Governance System, the Agent Safety and Constraint Architecture, the Production System Prompt Template, and the Agent Performance Dashboard.

Supporting sources: D3474 — RISER-Agentic-Orchestration-Workflow-Governance-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C49 — AI Quality Assurance Gate

Source filename: RISER-AI-Quality-Assurance-Gate-SOP.docx

Catalogue scope: The quality assurance framework that validates AI agent outputs against defined quality standards before they enter the production system. Covers the QA Gate structure, the evaluation criteria for each content and communication type, the systematic error pattern detection, and the feedback loop that improves agent quality over time.

Supporting sources: D2937 — RISER-AI-Quality-Assurance-Gate-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C50 — AI Executive Command: The Autonomous CEO

Source filename: RISER-AI-Executive-Command-Autonomous-CEO-SOP.docx

Catalogue scope: The five-layer AI executive intelligence system that provides the operator with synthesised intelligence across every business function. Covers Layer 1 (Strategy Intelligence), Layer 2 (Market Intelligence Engine), Layer 3 (Revenue Operations Command Centre), Layer 4 (Customer Success Intelligence), Layer 5 (Operations Oversight), the Executive Decision Support Framework, the 90-Minute CEO Review Protocol, and the CEO Alerting system.

Supporting sources: D3475 — RISER-AI-Executive-Command-Autonomous-CEO-SOP (2).docx — version 1 · D3475 — RISER-AI-Executive-Command-Autonomous-CEO-SOP (2).docx — version 2

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C51 — AI Strategic Foresight

Source filename: RISER-AI-Strategic-Foresight-SOP.docx

Catalogue scope: The AI-powered system for detecting strategic signals 12–24 months before market shifts become visible to competitors. Covers the Foresight Philosophy (Signal Diversity, Time Horizon Differentiation, Action Orientation), the Horizon Scanning Protocol (five signal categories), the Horizon Scanner Agent specification, the Scenario Construction Engine (three-scenario framework), the Weak Signal Detection System, the Technology Adoption Curve Monitoring Framework, the Buyer Evolution Modelling Protocol, the Strategic Options Stress Test, and the Foresight-to-Strategy Integration System.

Supporting sources: D2192 — RISER-AI-Strategic-Foresight-SOP (2).docx — version 1 · D2192 — RISER-AI-Strategic-Foresight-SOP (2).docx — version 2

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C52 — AI Governance & Ethical Shielding

Source filename: RISER-AI-Governance-Ethical-Shielding-SOP.docx

Catalogue scope: The complete ethical governance framework for all AI deployments in the knowledge business. Covers the AI Ethics Charter (five principles), the Buyer Trust Protection Standard, the Transparency and Disclosure Protocol (six AI involvement types), the Bias Detection and Correction Framework, the AI-Generated Content Labelling Standard, the Data Privacy and Consent Architecture, the Right to Explanation Protocol, the Harm Prevention Protocol (five harm types), the Community AI Disclosure Standard, and the Annual Governance Audit.

Supporting sources: D2191 — RISER-AI-Governance-Ethical-Shielding-SOP (2).docx — version 1 · D2191 — RISER-AI-Governance-Ethical-Shielding-SOP (2).docx — version 2

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C53 — AI Workforce Architecture & Role Replication

Source filename: RISER-AI-Workforce-Architecture-Role-Replication-SOP.docx

Catalogue scope: The framework for designing the hybrid human-AI workforce. Covers the Four-Quadrant Role Classification (by judgement required and relationship sensitivity), the complete AI Role Library for knowledge businesses (ten agent roles), the Human-AI Collaboration Protocol for each team role, the Hiring Decision Matrix, the Team Capacity Model at each revenue stage, the Context Package for new team members, and the Workforce Evolution Roadmap.

Supporting sources: D2193 — RISER-AI-Workforce-Architecture-Role-Replication-SOP (2).docx — version 1 · D2193 — RISER-AI-Workforce-Architecture-Role-Replication-SOP (2).docx — version 2

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C54 — Autonomous Empire & Generational Legacy

Source filename: RISER-Autonomous-Empire-Generational-Legacy-SOP.docx

Catalogue scope: The architecture for building a knowledge business that generates compounding value without the operator’s daily presence. Covers the Autonomous Operations Architecture (daily operations without the operator), the Brand Independence Protocol (four components), the Evergreen Revenue Engine (five streams), the IP and Asset Protection Framework, the Generational Wealth Architecture, the Licensing and Certification Empire design, the Exit Optionality Model (four paths), and the Legacy Programme Architecture.

Supporting sources: D2195 — RISER-Autonomous-Empire-Generational-Legacy-SOP (3).docx — version 1 · D2195 — RISER-Autonomous-Empire-Generational-Legacy-SOP (3).docx — version 2

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

C55 — Enterprise Reinvention & Futureproofing

Source filename: RISER-Enterprise-Reinvention-Futureproofing-SOP.docx

Catalogue scope: The capstone framework for ensuring the business remains dominant across multiple technological and market cycles. Covers the Business Reinvention Cycle (four phases across the annual calendar), the Disruption Radar (five signal categories), the Asset Portfolio Review (five asset categories), the Knowledge Business Evolution Paths (four strategies), the AI-Native Business Architecture (four pillars), the Institutional Knowledge Codification System, the Succession and Transition Framework, and the Five Legacy Operating Principles.

Supporting sources: D2204 — RISER-Enterprise-Reinvention-Futureproofing-SOP (2).docx — version 1 · D2204 — RISER-Enterprise-Reinvention-Futureproofing-SOP (2).docx — version 2

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Beta Testing Methodology

Source filename: RISER-Beta-Testing-Methodology-SOP.docx

Catalogue scope: Detailed validation protocol for the first cohort, feedback collection frameworks, and the specific evidence thresholds for confirming product-market fit before full launch.

Supporting sources: D0725 — RISER-Beta-Testing-Methodology-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Weekly Offer Review Ritual

Source filename: RISER-Weekly-Offer-Review-Ritual-SOP.docx

Catalogue scope: The structured 60-minute weekly review protocol for monitoring offer performance, identifying declining metrics, and making systematic improvements to the Core Offer on a continuous basis.

Supporting sources: D2963 — RISER-Weekly-Offer-Review-Ritual-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Offer Stacking & Unbundling

Source filename: RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx

Catalogue scope: Detailed tactical framework for creating bonus stacks that increase perceived value, and the unbundling approach for creating lower-priced entry offers from existing curriculum components.

Supporting sources: D0936 — RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Product Versioning & Offer Changelog

Source filename: RISER-Product-Versioning-Offer-Changelog-SOP.docx

Catalogue scope: The system for managing curriculum updates, version control, communicating changes to active buyers, and maintaining a living changelog that supports the Beta Testing loop.

Supporting sources: D0941 — RISER-Product-Versioning-Offer-Changelog-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Dead Offer Resurrection Playbook

Source filename: RISER-Dead-Offer-Resurrection-Playbook-SOP.docx

Catalogue scope: The diagnostic and revival protocol for offers that have stopped converting. Covers the four resurrection diagnoses (hook failure, mechanism failure, avatar drift, market saturation) and the specific fix sequence for each.

Supporting sources: D0928 — RISER-Dead-Offer-Resurrection-Playbook-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Product Kill Criteria & Post-Launch Audit

Source filename: RISER-Product-Kill-Criteria-Post-Launch-SOP.docx

Catalogue scope: The decision framework for retiring underperforming offers, including the specific quantitative thresholds, the post-mortem audit protocol, and the asset salvage process for recovering curriculum components from retired offers.

Supporting sources: D0940 — RISER-Product-Kill-Criteria-Post-Launch-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Fulfilment Stress Test

Source filename: RISER-Fulfilment-Stress-Test-SOP.docx

Catalogue scope: The pre-launch delivery audit that confirms the offer can be delivered at the promised quality level to the projected buyer volume without the operator’s personal intervention in every buyer interaction.

Supporting sources: D2947 — RISER-Fulfilment-Stress-Test-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Bonus Discipline Audit

Source filename: RISER-Bonus-Discipline-Audit-SOP.docx

Catalogue scope: The framework for evaluating whether each bonus in the offer stack is genuinely increasing conversion or simply adding complexity. Defines the three criteria for a bonus worth keeping and the audit process for removing value-diluting bonuses.

Supporting sources: D0634 — RISER-Bonus-Discipline-Audit-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Guarantee Type Testing Protocol

Source filename: RISER-Guarantee-Type-Testing-Protocol-SOP.docx

Catalogue scope: The structured testing framework for identifying which guarantee type (results-based, satisfaction-based, conditional, unconditional) maximises conversion for the specific offer and buyer profile without increasing refund rate.

Supporting sources: D0726 — RISER-Guarantee-Type-Testing-Protocol-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Price Elasticity Testing Framework

Source filename: RISER-Price-Elasticity-Testing-Framework-SOP.docx

Catalogue scope: The methodology for systematically testing price points to identify the price that maximises revenue per offer, covering the split-test structure, the minimum sample sizes required for significance, and the decision criteria for price changes.

Supporting sources: D0727 — RISER-Price-Elasticity-Testing-Framework-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — Downsell Paths

Source filename: RISER-Downsell-Paths-SOP.docx

Catalogue scope: The framework for capturing buyers who decline the Core Offer by presenting a lower-commitment alternative that maintains the buyer relationship and produces incremental revenue that would otherwise be lost.

Supporting sources: D0929 — RISER-Downsell-Paths-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 3 — 10x Mechanism Test & Rename Cadence

Source filename: RISER-10x-Mechanism-Test-Rename-Cadence-SOP.docx

Catalogue scope: The protocol for testing whether renaming or re-framing the Core Offer’s mechanism (while keeping the underlying transformation identical) produces a significant conversion rate improvement.

Supporting sources: D2934 — RISER-10x-Mechanism-Test-Rename-Cadence-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 4 — Proof Injection Checklist

Source filename: RISER-Proof-Injection-Checklist-SOP.docx

Catalogue scope: The systematic audit for ensuring that every persuasive claim in the sales page, email sequences, and advertising is supported by specific, documentable proof: transformation stories, data, credentials, or demonstrations.

Supporting sources: D0942 — RISER-Proof-Injection-Checklist-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 4 — Voice Consistency Gate

Source filename: RISER-Voice-Consistency-Gate-Founder-POV-Layer-SOP.docx

Catalogue scope: The editorial quality gate ensuring that all content, copy, and communications produced by the team or by AI systems is consistent with the operator’s authentic voice, Brand Belief System, and Founder Point of View.

Supporting sources: D2962 — RISER-Voice-Consistency-Gate-Founder-POV-Layer-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 4 — Perfect Webinar Script

Source filename: RISER-Perfect-Webinar-Script-SOP.docx

Catalogue scope: The complete 90-minute webinar script framework adapted for the knowledge business operator. Covers the Big Domino opener, the Three Secrets structure, the Stack and Close sequence, and the live Q&A conversion protocol.

Supporting sources: D3484 — RISER-Perfect-Webinar-Script-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 4 — VSL Script Template

Source filename: RISER-VSL-Script-Template-SOP.docx

Catalogue scope: The Video Sales Letter script framework for Core Offer and Traffic Hook video sales pages. Covers hook, problem agitation, mechanism introduction, social proof integration, offer presentation, guarantee, and close.

Supporting sources: D0947 — RISER-VSL-Script-Template-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 4 — Phone Sales Call Scripts

Source filename: RISER-Phone-Sales-Call-Scripts-SOP.docx

Catalogue scope: The structured script and conversational framework for high-ticket phone sales calls, including qualification, problem exploration, mechanism presentation, objection handling, and close sequences for Premium and Done-for-You offers.

Supporting sources: D1768 — RISER-Phone-Sales-Call-Scripts-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 4 — NLP Conversation Frameworks

Source filename: RISER-NLP-Live-Conversation-Frameworks-SOP.docx

Catalogue scope: Advanced NLP-based conversational frameworks for application calls, qualification conversations, and discovery calls. Covers rapport building, pacing and leading, re-frames, and the conversational close.

Supporting sources: D2955 — RISER-NLP-Live-Conversation-Frameworks-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 4 — Attractive Character Content Bible

Source filename: RISER-Attractive-Character-Content-Bible-SOP.docx

Catalogue scope: The editorial standard document built on the Attractive Character Development System. Defines the operator’s voice guidelines, thematic pillars, and content decision-making framework for consistent brand expression across all channels.

Supporting sources: D0355 — RISER-Attractive-Character-Content-Bible-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 4 — Post-MVO Forensic Audit Loop

Source filename: RISER-Post-MVO-Forensic-Audit-Loop-SOP.docx

Catalogue scope: The structured post-launch audit protocol that analyses every element of the Minimum Viable Offer’s performance to identify the specific changes that would most improve conversion rates in the next iteration.

Supporting sources: D0488 — RISER-Post-MVO-Forensic-Audit-Loop-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 5 — Content Differentiation Score

Source filename: RISER-Content-Differentiation-Score-SOP.docx

Catalogue scope: The diagnostic scoring system for assessing whether any piece of content is genuinely differentiated from competitor content. Produces a differentiation score across five dimensions and identifies the specific changes that would increase the score.

Supporting sources: D2944 — RISER-Content-Differentiation-Score-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 5 — Content Decay & Refresh Protocol

Source filename: RISER-Content-Decay-Refresh-Protocol-SOP.docx

Catalogue scope: The system for identifying organic content that is losing traffic or rankings over time and refreshing it to restore and improve its search performance. Covers the decay detection triggers, the refresh prioritisation framework, and the specific update protocol for each content type.

Supporting sources: D2943 — RISER-Content-Decay-Refresh-Protocol-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 5 — Interactive Tools Content Category

Source filename: RISER-Interactive-Tools-Content-Category-SOP.docx

Catalogue scope: The framework for designing calculators, scorecards, assessments, and diagnostic tools as premium content assets. Covers the tool design principles, the Traffic Hook integration, and the link acquisition value that well-built tools generate.

Supporting sources: D2949 — RISER-Interactive-Tools-Content-Category-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 5 — Content to Revenue Attribution

Source filename: RISER-Content-to-Revenue-Attribution-SOP.docx

Catalogue scope: The methodology for tracking which specific content pieces and content types are producing Traffic Hook opt-ins and Core Offer buyers. Covers the attribution model, the UTM tagging standard, and the monthly content ROI review.

Supporting sources: D2945 — RISER-Content-to-Revenue-Attribution-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 5 — Buyer Stage Tagging

Source filename: RISER-Buyer-Stage-Tagging-SOP.docx

Catalogue scope: The complete tagging architecture for the email platform that records each subscriber’s awareness stage, engagement level, and position in the buyer journey. Enables segmented content delivery and accurate conversion tracking.

Supporting sources: D2198 — RISER-Buyer-Stage-Tagging-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 5 — Long-Form YouTube Channel Strategy

Source filename: RISER-Long-Form-YouTube-Channel-Strategy-SOP.docx

Catalogue scope: The complete strategy and production framework for a long-form YouTube channel as an authority asset and audience acquisition engine.

Supporting sources: D2950 — RISER-Long-Form-YouTube-Channel-Strategy-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Lead Funnel / Squeeze Page Types

Source filename: RISER-Lead-Funnel-Squeeze-Page-Types-SOP.docx

Catalogue scope: The complete taxonomy of Traffic Hook landing page designs, with the specific copy structure, visual hierarchy, and CTA placement for each type (short-form, video, quiz, challenge, webinar registration).

Supporting sources: D1488 — RISER-Lead-Funnel-Squeeze-Page-Types-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — SLO Funnel

Source filename: RISER-SLO-Funnel-SOP.docx

Catalogue scope: The Self-Liquidating Offer funnel architecture that allows paid traffic acquisition costs to be partially or fully offset by immediate post-opt-in sales. Covers the SLO product design, pricing, page structure, and integration with the Indoctrination Sequence.

Supporting sources: D1296 — RISER-SLO-Funnel-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Book Funnel

Source filename: RISER-Book-Funnel-SOP.docx

Catalogue scope: The complete book funnel framework for using a physical or digital book as a high-converting Traffic Hook and authority-builder. Covers the book offer positioning, the free-plus-shipping model, the upsell sequence, and the book funnel’s role in the Offer Ecosystem.

Supporting sources: D1282 — RISER-Book-Funnel-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Challenge Funnel

Source filename: RISER-Challenge-Funnel-SOP.docx

Catalogue scope: The 5-7 day challenge funnel architecture for creating high-engagement lead generation events. Covers challenge design, the daily content structure, the live delivery format, and the conversion sequence from challenge participant to Core Offer buyer.

Supporting sources: D3478 — RISER-Challenge-Funnel-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Virtual Summit Funnel

Source filename: RISER-Virtual-Summit-Funnel-SOP.docx

Catalogue scope: The virtual summit (online conference) as a high-volume list building and authority event. Covers speaker recruitment, the summit registration and replay funnel, the monetisation sequence, and the post-summit email campaign for Core Offer conversion.

Supporting sources: D1770 — RISER-Virtual-Summit-Funnel-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Application Funnel

Source filename: RISER-Application-Funnel-SOP.docx

Catalogue scope: The application-based funnel for high-ticket and Premium offers. Covers the application page design, the qualification questions, the application review process, and the conversion call sequence for approved applicants.

Supporting sources: D1755 — RISER-Application-Funnel-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Funnel Hacking Methodology

Source filename: RISER-Funnel-Hacking-Methodology-SOP.docx

Catalogue scope: The systematic process for analysing competitor funnels, identifying the structural and copy elements that are producing their conversions, and applying those insights to improve the operator’s own funnels.

Supporting sources: D0932 — RISER-Funnel-Hacking-Methodology-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Dream 100 Strategy

Source filename: RISER-Dream-100-Strategy-SOP.docx

Catalogue scope: The complete Dream 100 relationship-building and borrowed traffic system. Covers the Dream 100 list construction, the outreach sequence, the value-first relationship protocol, and the transition from relationship to promotional partnership.

Supporting sources: D1900 — RISER-Dream-100-Strategy-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Borrowed Traffic (Brunson)

Source filename: RISER-Borrowed-Traffic-SOP.docx

Catalogue scope: The framework for generating Traffic Hook opt-ins and buyers through other operators’ audiences. Covers guest appearances, content syndication, and the specific asks that produce high-quality borrowed traffic introductions.

Supporting sources: D1850 — RISER-Borrowed-Traffic-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Influencer & Creator Outreach

Source filename: RISER-Influencer-Creator-Outreach-SOP.docx

Catalogue scope: The outreach framework for identifying, approaching, and activating social media influencers and content creators as Traffic Hook promotion partners. Covers creator qualification criteria, outreach templates, commission structures, and campaign tracking.

Supporting sources: D1761 — RISER-Influencer-Creator-Outreach-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Community Infiltration Strategy

Source filename: RISER-Community-Infiltration-Strategy-SOP.docx

Catalogue scope: The ethical community presence strategy for establishing the operator as a valuable contributor in niche communities (Facebook groups, subreddits, LinkedIn groups, industry forums) and converting community relationships into Traffic Hook subscribers.

Supporting sources: D1899 — RISER-Community-Infiltration-Strategy-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Podcast Guesting (Dream 100)

Source filename: RISER-Podcast-Guesting-Dream-100-SOP.docx

Catalogue scope: The complete podcast guest strategy: identifying and prioritising target shows from the Dream 100 list, crafting the pitch, delivering a high-value interview, and converting podcast listeners into Traffic Hook subscribers.

Supporting sources: D2221 — RISER-Podcast-Guesting-Dream-100-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Meta Ads Campaign Architecture

Source filename: RISER-Meta-Ads-Campaign-Architecture-SOP.docx

Catalogue scope: The complete Meta (Facebook and Instagram) advertising campaign structure: the cold-to-warm campaign hierarchy, the creative testing framework, the budget scaling ladder, the audience architecture, and the conversion optimisation protocol.

Supporting sources: D1288 — RISER-Meta-Ads-Campaign-Architecture-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Paid Ads Scaling Ladder (Hormozi)

Source filename: RISER-Paid-Ads-Scaling-Ladder-SOP.docx

Catalogue scope: The structured advertising budget scaling protocol for progressing from initial test campaigns through to consistent scaling. Covers the budget thresholds for each scaling stage, the metrics that confirm readiness to scale, and the risk management protocols for each level.

Supporting sources: D1766 — RISER-Paid-Ads-Scaling-Ladder-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Platform-Specific Ad Protocols

Source filename: RISER-Platform-Specific-Ad-Protocols-SOP.docx

Catalogue scope: Campaign architecture and best practice protocols for Google Ads (search and display), YouTube Ads, LinkedIn Ads, and TikTok Ads as supplementary traffic channels to the primary Meta campaign.

Supporting sources: D2957 — RISER-Platform-Specific-Ad-Protocols-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — ROAS Benchmarks by Value Ladder Tier

Source filename: RISER-ROAS-Benchmarks-Value-Ladder-Tier-SOP.docx

Catalogue scope: The performance benchmarks for advertising return on ad spend at each level of the Value Ladder, from Traffic Hook cold traffic through Core Offer retargeting to Premium ascension campaigns.

Supporting sources: D1295 — RISER-ROAS-Benchmarks-Value-Ladder-Tier-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Media Buyer Hiring & Management

Source filename: RISER-Media-Buyer-Hiring-Management-SOP.docx

Catalogue scope: The specification, recruitment, onboarding, and performance management framework for hiring a media buyer or advertising agency. Covers the job description, the trial campaign protocol, the reporting standards, and the performance review framework.

Supporting sources: D2216 — RISER-Media-Buyer-Hiring-Management-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 6 — Creative Brief Template

Source filename: RISER-Creative-Brief-Template-SOP.docx

Catalogue scope: The standardised creative brief format for briefing video editors, graphic designers, and copywriters on advertising creative production. Covers the campaign context, the target audience, the message hierarchy, the call to action, and the technical specifications.

Supporting sources: D2946 — RISER-Creative-Brief-Template-SOP (1).docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — Affiliate Program Architecture

Source filename: RISER-Affiliate-Program-Architecture-SOP.docx

Catalogue scope: The complete affiliate programme design including commission structures, tracking infrastructure, affiliate portal setup, payout protocols, and the affiliate tier system that incentivises top performers.

Supporting sources: D0926 — RISER-Affiliate-Program-Architecture-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — Affiliate Recruitment Outreach Templates

Source filename: RISER-Affiliate-Recruitment-Outreach-Templates-SOP.docx

Catalogue scope: The outreach email sequence and follow-up protocol for recruiting affiliates and JV partners from the Dream 100 list, with templates for cold, warm, and referral-based outreach scenarios.

Supporting sources: D2190 — RISER-Affiliate-Recruitment-Outreach-Templates-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — Affiliate Asset Creation Checklist

Source filename: RISER-Affiliate-Asset-Creation-Checklist-SOP.docx

Catalogue scope: The complete list of assets required to support affiliate promotional campaigns: email swipe copy, social media posts, banner graphics, video scripts, FAQ documents, and the affiliate portal setup.

Supporting sources: D2935 — RISER-Affiliate-Asset-Creation-Checklist-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — JV Email Swap

Source filename: RISER-JV-Email-Swap-SOP.docx

Catalogue scope: The framework for structuring and executing reciprocal email list promotions with JV partners. Covers the swap terms negotiation, the email copy standards, the list size qualification criteria, and the post-swap performance review.

Supporting sources: D2212 — RISER-JV-Email-Swap-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — JV Broker & Deal Sourcing

Source filename: RISER-JV-Broker-Deal-Sourcing-SOP.docx

Catalogue scope: The methodology for identifying and working with JV brokers to access partnership opportunities with established operators. Covers broker qualification, fee structures, the deal sourcing process, and the due diligence protocol for broker-introduced partners.

Supporting sources: D1901 — RISER-JV-Broker-Deal-Sourcing-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — JV Deal Structures & Commission Terms

Source filename: RISER-JV-Deal-Structures-Commission-Terms-SOP.docx

Catalogue scope: The complete taxonomy of JV deal structures (revenue share, flat fee, hybrid, equity), the commission calculation methods, the tracking and payment protocols, and the negotiation framework for each structure type.

Supporting sources: D0933 — RISER-JV-Deal-Structures-Commission-Terms-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — JV Legal Agreement Template

Source filename: RISER-JV-Legal-Agreement-Template-SOP.docx

Catalogue scope: The standard JV partnership agreement template covering the key commercial terms, IP ownership, promotional obligations, tracking and payment terms, dispute resolution, and termination clauses.

Supporting sources: D2213 — RISER-JV-Legal-Agreement-Template-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — Co-Launch (Partner Launch)

Source filename: RISER-Co-Launch-Partner-Launch-SOP.docx

Catalogue scope: The framework for executing a co-launch where two or more operators jointly promote a single offer to their combined audiences. Covers the co-launch structure, the promotional asset sharing protocol, the revenue split agreement, and the post-launch debriefing framework.

Supporting sources: D2199 — RISER-Co-Launch-Partner-Launch-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — Past Buyer Referral Programme

Source filename: RISER-Past-Buyer-Referral-Programme-SOP.docx

Catalogue scope: The referral programme architecture for incentivising existing buyers to refer new buyers. Covers referral incentive design, tracking infrastructure, the referral communication sequence, and the activation protocol for converting advocates into active referrers.

Supporting sources: D1767 — RISER-Past-Buyer-Referral-Programme-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — IP Licensing Model

Source filename: RISER-IP-Licensing-Model-SOP.docx

Catalogue scope: The framework for licensing the operator’s curriculum, methodology, or brand to other operators for delivery in adjacent markets. Covers the licensing fee structure, the quality standards agreement, the licensee onboarding protocol, and the ongoing relationship management framework.

Supporting sources: D2211 — RISER-IP-Licensing-Model-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — White Label Pricing Architecture

Source filename: RISER-White-Label-Pricing-Architecture-SOP.docx

Catalogue scope: The pricing framework for white-label licensing arrangements where the licensee delivers the operator’s methodology under their own brand. Covers the pricing tiers, volume discounts, exclusivity premiums, and the pricing audit protocol.

Supporting sources: D0948 — RISER-White-Label-Pricing-Architecture-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Track 8 — White Label Partner Onboarding

Source filename: RISER-White-Label-Partner-Onboarding-SOP.docx

Catalogue scope: The complete onboarding protocol for white-label partners including the training requirements, brand guidelines, delivery standards, quality assurance protocol, and the ongoing communication framework.

Supporting sources: D3486 — RISER-White-Label-Partner-Onboarding-SOP.docx

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Apply the catalogue to your assigned lesson

03.3 — Offer work: identify the procedure that addresses the current offer constraint. Write the buyer problem, the decision being made and the output you need, then use the corresponding offer or validation resource.

06.2 — Marketing work: select a messaging, conversion or traffic resource according to the specific gap in your buyer journey. Keep a description of a tactic separate from evidence that it improved your results.

07.1 — Content work: connect each content piece to the buyer question, supporting evidence and next useful action. Use the content, voice, quality and discoverability resources where relevant.

12.4 — Operating systems: turn the selected procedure into a repeatable workflow with inputs, owner, output, quality gate and review date. Introduce automation only after the workflow is defined.

12.5 — Review and improvement: record what the procedure changed, what evidence supports the change and what remains uncertain. Refresh the resource selection when the business constraint changes.

Supporting sources: Master SOP Catalogue — source version 1 · Master SOP Catalogue — source version 2

Practice and completion check

Choose one current bottleneck and one matching catalogue entry. Record the source filename and clickable link, the input you already have, the missing input, the deliverable you will create, the person who will check it and the date for review. Explain why this resource is the next appropriate step. Completion means producing and checking the deliverable; opening the document is not sufficient.

Version and source notes

The source mentions risernation.com and a document-generation folder. Those are retained below as provenance. Current website references use risernationcorp.com. Historical course numbers and filenames remain visible for traceability.

Complete catalogue source text

RISER NATION
MASTER OPERATING SYSTEM
  MASTER SOP CATALOGUE  
The Complete Index of All Standard Operating Procedures Across 9 Tracks and 55 Courses
Tracks 1–9  —  55 Core Course SOPs  —  40+ Supplementary Resource SOPs  —  95+ Total Documents
Version 1.0  |  2026 Edition  |  risernation.com
How to Use This Catalogue
The RISER Nation Master Operating System comprises 55 courses across 9 tracks, supported by more than 95 Standard Operating Procedures. This catalogue lists every SOP in the system in course order, identifies the filename for each document, and provides a brief description of the content covered.
The catalogue is divided into two sections: Core Course SOPs (one primary SOP per course, in course number order from C1 through C55), and Supplementary Resource SOPs (additional documents that support specific courses with deeper implementation detail, templates, scripts, or tactical frameworks).
Track 1 establishes the philosophical and strategic foundation of the RISER Nation system. These SOPs define what it means to operate as a sovereign knowledge business, how to read market forces, how to make high-quality decisions under uncertainty, and how to identify the intersection of the operator’s genuine skill and a commercially viable market problem.
Track 2 produces the buyer intelligence infrastructure that every subsequent course in the system depends on. The Psychographic DNA, the Negative Avatar, and the Organic Proof Threshold together define with precision who the ideal buyer is, who the business should not serve, and whether real demand exists in the market.
Track 3 takes the validated market problem and the Psychographic DNA from Track 2 and builds the commercial offer. The Value Ladder Architecture, Offer Scorecard, Offer Stacking system, and Beta Testing Methodology together produce a Core Offer that is correctly positioned, correctly priced, and validated with real buyers before launch.
Track 4 is the persuasion and messaging layer of the RISER Nation system. It covers every dimension of how the operator communicates their offer’s value: the hook that captures attention, the psychological principles that move the buyer toward decision, the identity framework that creates belonging, and the objection resolution system that removes the final barriers to purchase.
Track 5 builds the content infrastructure that creates the operator’s organic presence, authority, and audience acquisition system. The frameworks in this track cover content strategy at the awareness level, the podcast and YouTube channels as authority media, the technical SEO foundation, and the AEO/GEO system for AI search visibility.
Track 6 builds the commercial conversion engine: the email list as the primary owned audience asset, the sales page and funnel architecture, the paid advertising infrastructure, and the retargeting systems that monetise the warm audience. These SOPs together produce the revenue generation mechanism that converts the operator’s audience into buyers.
Track 7 builds the technical sovereignty layer: the data architecture that ensures the business cannot be destroyed by a single platform’s decision, the automation stack that removes the operator from operational execution, and the AI agent foundations that power Track 9’s autonomous systems.
Track 8 builds the scaling architecture on top of the validated, operational business from Tracks 1–7. These SOPs cover every dimension of intelligent growth: maximising buyer lifetime value through the offer ecosystem, ensuring every buyer achieves their transformation, dominating search, expanding globally, and managing the reputation challenges that come with public scale.
Track 9 is the culmination of the RISER Nation system. These SOPs build the autonomous AI infrastructure, the executive intelligence systems that run the business with minimal operator time, the ethical frameworks that make AI deployment trustworthy, and the generational legacy architecture that ensures the business’s value compounds across time.
Supplementary Resource SOPs
The following documents support specific courses with deeper implementation detail, tactical templates, scripts, and frameworks that are too granular to include in the primary course SOP but are essential for operators implementing at the full level of the system.
Track 3 & 4 Support — Offer Testing, Iteration & Conversion Tools
Track 4 Support — Sales Scripts & Conversion Frameworks
Track 5 Support — Content Strategy, Quality & Authority Channels
Track 6 Support — Funnel Architecture & Traffic Systems
Track 6 Support — Paid Advertising Systems
Track 8 Support — Partnership, JV & Affiliate Infrastructure
RISER Nation Master Operating System  |  Master SOP Catalogue  |  Version 1.0  |  2026 Edition
9 Tracks  |  55 Courses  |  95+ SOPs  |  risernation.com
Navigation Guide
Core Course SOPs follow the Course Number / SOP Title / Filename / Description format.
Supplementary Resource SOPs are grouped by the course or topic area they support.
All files are delivered as .docx files to /mnt/user-data/outputs/ during SOP production sessions.
The system is designed to be used sequentially: each track builds on the infrastructure of the tracks before it.
TRACK 1 — COURSES 1–5
OPERATOR FOUNDATION
The mental model, market context, and decision architecture of the sovereign knowledge business operator
Course
SOP Title
Filename
Description
C1
The Sovereign Operator Mindset
RISER-Sovereign-Operator-Mindset-SOP.docx
The foundational mindset and identity framework for the knowledge business operator. Covers the shift from employee mindset to sovereign operator, the RISER Nation operating principles, and the daily practices that establish the psychological infrastructure for building at scale.
C2
Market Reality (2025–2035)
RISER-Market-Reality-2025-2035-SOP.docx
A forward-looking map of the forces reshaping the knowledge economy across the decade. Covers the AI transformation of content and expertise markets, the compression of trust timelines, the shift from information scarcity to attention scarcity, and the operator’s strategic positioning in this landscape.
C3
Decision Intelligence & Risk Management
RISER-Decision-Intelligence-Risk-Management-SOP.docx
The systematic framework for making high-quality decisions under conditions of incomplete information, time pressure, and consequence. Covers the Decision Intelligence Protocol, risk categorisation, reversible versus irreversible decisions, and the biases that produce poor operator decisions at scale.
C4
Problems Create Markets — Market Gap Detection
RISER-Problems-Create-Markets-SOP.docx
The methodology for identifying commercially viable market problems that are large enough to build a knowledge business on. Covers the Problem Hierarchy, the Market Gap Detection Protocol, the difference between a problem and a preference, and the evidence standards for confirming a market exists before building an offer.
C5
Skill & Experience Mapping
RISER-Skill-Experience-Mapping-SOP.docx
The structured inventory process for identifying the operator’s genuine expertise, lived experience, and transferable skill sets. Covers the Skill-Experience Matrix, the Expertise Depth Assessment, the distinction between knowledge the operator has versus knowledge they have applied with results, and the connection between the operator’s experience and their Core Offer’s mechanism.
TRACK 2 — COURSES 6–10
FIND YOUR MARKET
The research, validation, and buyer intelligence systems that confirm a specific niche is viable before any product is built
Course
SOP Title
Filename
Description
C6
Pattern Recognition
RISER-Pattern-Recognition-SOP.docx
The framework for reading the deeper patterns in market data, buyer language, and competitive positioning that are not visible from surface-level research alone. Covers the Pattern Recognition Protocol, how to identify recurring themes in buyer conversations that indicate genuine market pain, and the specific signals that separate a trend from a pattern.
C7
Psychographic DNA
RISER-Psychographic-DNA-SOP.docx
The complete buyer intelligence framework that goes beyond demographics to capture the buyer’s worldview, values, fears, desires, prior attempts at the transformation, and the specific language they use to describe their problem. The Psychographic DNA is the single most referenced source document in the entire RISER Nation system, used in every content, copy, and offer decision.
C8
Negative Avatar Modelling
RISER-Negative-Avatar-Modelling-SOP.docx
The systematic process for defining who the business should not serve. Covers the Negative Avatar profile (the buyer who will never succeed with the methodology regardless of the operator’s efforts), the financial and reputational cost of serving misaligned buyers, and how to incorporate Negative Avatar criteria into the sales page, the Traffic Hook, and the qualification process.
C9
Niche Validation & StorySelling
RISER-Niche-Validation-StorySelling-SOP.docx
The validation framework for confirming that the identified niche has sufficient commercial depth before major investment. Covers the three-stage Niche Validation Protocol, the Story Selling approach to qualifying buyer intent through narrative, and the minimum evidence thresholds that confirm a niche is viable.
C10
Hard Organic Proof Threshold
RISER-Hard-Organic-Proof-Threshold-SOP.docx
The evidence standard that must be met before the operator invests in building the full Core Offer. Defines what constitutes genuine proof of market demand versus wishful interpretation of signals. Covers the Organic Proof Threshold scorecard, the minimum buyer conversations required, and the red flags that indicate a niche that appears valid but is not commercially viable.
TRACK 3 — COURSES 11–14
BUILD YOUR OFFER
The product design, pricing, packaging, and validation frameworks for the Core Offer and the complete Value Ladder
Course
SOP Title
Filename
Description
C11
Value Ladder Architecture
RISER-Value-Ladder-Architecture-SOP.docx
The complete framework for designing the operator’s full offer ecosystem: from the free Traffic Hook through the SLO, Core Offer, Continuity, Premium, and Done-for-You tiers. Covers the pricing logic for each rung, the buyer journey through the ecosystem, and the relationship between each rung’s promise and the buyer’s progressive transformation.
C12
Offer Scorecard
RISER-Offer-Scorecard-SOP.docx
A structured diagnostic tool for evaluating any offer against the eight dimensions that determine commercial viability. Covers the Offer Scorecard assessment criteria, how to interpret a low score in any dimension, and the specific fixes that address each type of offer weakness.
C13
Offer Stacking & Unbundling Strategy
RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx
The framework for maximising perceived value at every price point through strategic inclusion and exclusion of offer elements. Covers the Offer Stacking Protocol (what bonuses and components to include at each tier), the Unbundling Strategy for creating lower-priced entry offers from existing curriculum, and the principle that perceived value must always exceed price.
C14
Beta Testing Methodology
RISER-Beta-Testing-Methodology-SOP.docx
The structured process for validating the Core Offer with a small group of real buyers before full launch. Covers the Beta Cohort selection criteria, the beta pricing strategy, the specific feedback mechanisms that produce actionable curriculum improvement data, and the evidence thresholds that confirm the offer is ready for full launch.
TRACK 4 — COURSES 15–21
PERSUASION & MESSAGING
The complete persuasion architecture, from the psychology of attention through to the live sales conversation and the community identity system
Course
SOP Title
Filename
Description
C15
Hook Engineering & Attention Engineering
RISER-Hook-Engineering-Attention-Engineering-SOP.docx
The systematic framework for creating hooks that capture attention in a saturated content environment. Covers the Five Hook Types, the Hook Quality Assessment Standard, the attention pattern interrupts that work across video, written, and audio formats, and the testing protocol for identifying which hook formulas resonate most strongly with the specific buyer profile.
C16
Scientific Persuasion & Influence Mastery
RISER-Scientific-Persuasion-Influence-Mastery-SOP.docx
The evidence-based persuasion framework grounded in decision science, behavioural economics, and the psychology of belief change. Covers Cialdini’s principles in the knowledge business context, the Belief Change Sequence, the stages of buyer awareness and how to communicate at each stage, and the ethical distinction between persuasion and manipulation.
C17
Behavioral Logic & Nudge Theory
RISER-Behavioral-Logic-Nudge-Theory-SOP.docx
The applied framework for designing buyer journeys that guide decisions without coercion. Covers choice architecture in the sales funnel, the nudge mechanisms that reduce buyer friction, default option design, commitment and consistency principles in offer design, and the specific nudge applications for each stage of the buyer journey.
C18
Identity-Based Marketing
RISER-Identity-Based-Marketing-SOP.docx
The framework for creating marketing that connects the operator’s offer to the buyer’s deepest sense of who they are and who they want to become. Covers identity bridging, the language of aspiration versus the language of outcome, and how to make the Core Offer feel like the natural expression of the buyer’s identity rather than an external purchase.
C19
NLP Live Conversation Frameworks
RISER-NLP-Live-Conversation-Frameworks-SOP.docx
The structured conversational frameworks for live sales calls, application calls, and qualification conversations. Covers the NLP-based rapport, pacing, and leading techniques for live conversation, the seven qualification questions that identify genuine buyers, the re-frame protocols for common live conversation objections, and the call close structure.
C20
Objection Bank
RISER-Objection-Bank-SOP.docx
The complete system for cataloguing, categorising, and resolving every objection the operator’s buyers raise. Covers the Objection Bank structure, the four objection categories (price, timing, belief, fit), the resolution frameworks for each category, and the process for updating the Objection Bank continuously from support tickets, community questions, and live call transcripts.
C21
Attractive Character Development System
RISER-Attractive-Character-Development-System-SOP.docx
The framework for developing the operator’s on-brand public persona: the Attractive Character elements (leader, adventurer, reporter, reluctant hero), the Brand Belief System (We Believe, We Reject), the Cultural Lexicon, the Origin Story structure, and the Tribe Formation Sequence. The Attractive Character is the public expression of the operator’s identity that makes the brand magnetic to the ideal buyer.
TRACK 5 — COURSES 22–27
CONTENT & VISIBILITY
The content architecture, distribution strategy, SEO foundation, and AI content systems that build compounding organic authority
Course
SOP Title
Filename
Description
C22
Content Calendar by Awareness Level
RISER-Content-Calendar-Awareness-Level-SOP.docx
The content planning system based on the five levels of buyer awareness. Covers how to distribute content across awareness stages (Unaware, Problem Aware, Solution Aware, Product Aware, Most Aware), the content types that move buyers along the awareness spectrum, and the publishing cadence that maintains consistent presence without the operator becoming a content production machine.
C23
AI-Driven Content Repurposing System
RISER-AI-Content-Repurposing-System-SOP.docx
The complete system for converting the operator’s flagship long-form content into multiple derivative formats using AI tools. Covers the repurposing hierarchy (podcast to YouTube to article to newsletter to social to clips), the AI-assisted workflows for each conversion, the quality standards for repurposed content, and the distribution schedule that maximises the reach of each piece of flagship content.
C24
Attractive Character Content Bible
RISER-Attractive-Character-Content-Bible-SOP.docx
The editorial standard document that ensures all content produced across all channels and formats is consistent with the operator’s Attractive Character. Covers the Content Bible structure, the voice and tone guidelines, the thematic pillars, the recurring content formats, and the editorial decision-making framework for any content question that is not covered by specific campaign instructions.
C25
Podcast as Primary Authority Channel
RISER-Podcast-Primary-Authority-Channel-SOP.docx
The complete framework for building a podcast that serves as the operator’s flagship authority platform. Covers format selection, episode structure, interview guest strategy, show notes and SEO, the Traffic Hook integration, episode production workflow, distribution strategy, and the metrics that indicate a podcast is effectively building the operator’s audience and authority.
C26
Technical SEO Foundations
RISER-Technical-SEO-Foundations-SOP.docx
The complete technical SEO infrastructure for the knowledge business operator’s Owned Media Hub. Covers site architecture, crawlability, Core Web Vitals, on-page elements, schema markup, the initial keyword research and cluster architecture, the Quarterly Technical SEO Audit, and the Google Search Console monitoring protocol.
C27
AEO, GEO & Machine Trust
RISER-AEO-GEO-Machine-Trust-SOP.docx
The framework for optimising content to be cited, referenced, and recommended by AI search systems including Google’s AI Overview, Perplexity, and ChatGPT. Covers the Entity Establishment Protocol, answer-first content formatting, FAQPage and HowTo schema, the AEO Citation Monitoring System, and the specific content formats that AI systems preferentially cite.
TRACK 6 — COURSES 28–32
TRAFFIC & CONVERSION
The email architecture, sales conversion infrastructure, paid advertising foundations, and retargeting systems
Course
SOP Title
Filename
Description
C28
Email Fundamentals
RISER-Email-Fundamentals-SOP.docx
The complete email marketing system architecture. Covers the email platform configuration, the Traffic Hook opt-in sequence, the 21-day Indoctrination Sequence that converts subscribers into buyers, the broadcast email calendar, the list segmentation and tagging architecture, the deliverability maintenance protocol, and the email metrics that determine whether the list is healthy and converting.
C29
Sales Page Architecture & Conversion Copy
RISER-Sales-Page-Architecture-SOP.docx
The structural and copywriting framework for the Core Offer’s primary sales page. Covers the twelve-section sales page architecture, the hook-to-offer arc, social proof placement and hierarchy, the guarantee framework, the objection removal sequence, the CTA structure, and the split-testing protocol for continuous conversion rate optimisation.
C30
Paid Ads Foundations
RISER-Paid-Ads-Foundations-SOP.docx
The foundational paid advertising framework covering the principles that apply across all paid channels: the Traffic Triangle (audience, offer, creative), the Traffic Hook campaign structure, the cold audience testing protocol, the budget allocation framework, and the campaign metrics hierarchy that determines what to optimise and when to scale.
C31
Omni-Channel Retargeting Systems
RISER-Omni-Channel-Retargeting-SOP.docx
The five-tier retargeting ecosystem that converts the warm audience into buyers. Covers the audience tier architecture (by intent stage), the retargeting sequences for each tier, the exclusion architecture that prevents wasted spend on existing buyers, the cross-platform deployment model, and the retargeting campaign metrics.
C32
Server-Side Tracking & Conversion APIs
RISER-Server-Side-Tracking-SOP.docx
The technical setup and governance for server-side event tracking using the Meta Conversions API, Google Tag Manager server-side, and webhook-based event forwarding. Covers the Event Match Quality optimisation, the browser-to-server tracking stack, the event deduplication protocol, and the EMQ monitoring system.
TRACK 7 — COURSES 33–38
AUTOMATION & SOVEREIGNTY
The data independence infrastructure, platform immunity systems, and AI-powered automation stack
Course
SOP Title
Filename
Description
C33
Data Sovereignty — Dig Your Own Well
RISER-Data-Sovereignty-SOP.docx
The complete framework for building platform-independent data infrastructure. Covers the Owned Asset Hierarchy, the email-first audience strategy, the monthly data export protocol, the Backup and Continuity Systems, and the specific configuration for ensuring the operator’s subscriber list, buyer records, and content assets cannot be lost through a single platform failure.
C34
Platform Immunity
RISER-Platform-Immunity-SOP.docx
The risk management system for the operator’s dependency on third-party platforms. Covers the Platform Dependency Risk Matrix, the Platform Change Response Playbook, the monthly platform immunity audit, the diversification standard for each platform category, and the specific contingency procedures for the most common platform failure scenarios.
C35
The RISER Automation Engine
RISER-Automation-Engine-SOP.docx
The complete six-blueprint automation stack that removes the operator from routine operational execution. Covers Blueprint 1 (Purchase Router), Blueprint 2 (Onboarding Sequence), Blueprint 3 (Programme Completion Sync), Blueprint 4 (List Hygiene), Blueprint 5 (Refund & Cancellation), and Blueprint 6 (Daily Analytics Sync). The Automation Engine is the operational foundation of the entire Track 8 and Track 9 system.
C36
Make.com Blueprint Deployment
RISER-Make-Blueprint-Deployment-SOP.docx
The technical implementation guide for all six Make.com blueprints in the RISER Automation Engine. Covers the specific module configurations, webhook structures, error handling protocols, and the testing sequence for confirming each blueprint is operating correctly before deploying to production.
C37
Advanced n8n & GitHub Automations
RISER-Advanced-n8n-GitHub-Automations-SOP.docx
The implementation guide for the four AI-agent workflows built in n8n: the Content Research Agent (AI-Agent 1), the Buyer Support Triage Agent (AI-Agent 2), the Performance Summary Agent (AI-Agent 3), and the Objection Bank Updater Agent (AI-Agent 4). Covers self-hosted n8n setup, the GitHub version control protocol, and the agent governance framework.
C38
Vibe Coding & Generative Video Pipelines
RISER-Vibe-Coding-Generative-Video-Pipelines-SOP.docx
The framework for using AI-assisted coding and generative video tools to build custom operator tools without traditional programming skill. Covers the Vibe Coding Protocol for building custom calculators and tools, the generative video pipeline for educational video production, and the quality standards for AI-generated multimedia assets.
TRACK 8 — COURSES 39–47
SCALE & EXPAND
The scaling readiness, offer ecosystem, customer success, retargeting, SEO dominance, global expansion, and crisis navigation systems
Course
SOP Title
Filename
Description
C39
Scaling Foundations & Operational Readiness
RISER-Scaling-Foundations-Operational-Readiness-SOP.docx
The gate assessment that confirms whether the business is genuinely ready to scale. Covers the five-dimension Scaling Readiness Audit (Delivery, Automation, Financial, Content, Operator Capacity), the five Scaling Failure Modes, the financial unit economics required before scaling investment begins, and the Operator Role Evolution sequence.
C40
Offer Ecosystem & Backend Monetisation
RISER-Offer-Ecosystem-Backend-Monetisation-SOP.docx
The complete six-rung Offer Ecosystem Map and the Backend Monetisation Sequence that maximises buyer lifetime value. Covers the post-purchase journey architecture (Order Bump, OTO, Early Win upsell, Graduation sequence), the Premium Offer design framework, the Continuity Engine design, the Ascension Path engineering, and the Ecosystem Revenue Optimisation Dashboard.
C41
Customer Success & Retention Systems
RISER-Customer-Success-Retention-Systems-SOP.docx
The complete buyer success infrastructure including the Buyer Health Score (five-component composite metric), the At-Risk Intervention Protocol (three levels), the First Win by Day 30 design framework, the Community Success Architecture, the Refund Prevention Framework, the Continuity Churn Prediction Model, and the Advocacy Activation System.
C42
Retargeting Ecosystems & Warm Audience Monetisation
RISER-Retargeting-Ecosystems-Warm-Audience-SOP.docx
The advanced retargeting architecture that serves every layer of the warm audience ecosystem simultaneously across the offer lifecycle. Covers the six-layer Ecosystem Audience Map, the Buyer Journey Retargeting sequences for each offer transition, cross-sell retargeting, the Lookalike Expansion Framework, advanced creative fatigue management, and the Retargeting P&L Dashboard.
C43
Long-Form YouTube Channel Strategy
RISER-Long-Form-YouTube-Channel-Strategy-SOP.docx
The complete framework for building a long-form YouTube channel as a compounding authority and acquisition asset. Covers channel positioning, video SEO, the Traffic Hook integration, content calendar strategy for YouTube, retention optimisation, and the monetisation pathway from subscriber to Traffic Hook opt-in to Core Offer buyer.
C44
Advanced SEO & Search Domination
RISER-Advanced-SEO-Search-Domination-SOP.docx
The advanced SEO framework for achieving topical authority and category dominance in the operator’s niche. Covers the four Topical Authority Stages, the Competitive Gap Mapping Protocol, Intent-Matching at page level, link acquisition through digital PR and Dream 100 outreach, the Content Refresh and Compounding System, SERP Feature Domination, the E-E-A-T Maximisation Protocol, programmatic SEO, and the Organic Search P&L Model.
C45
Global Market Expansion
RISER-Global-Market-Expansion-SOP.docx
The systematic framework for expanding the knowledge business into new geographic markets. Covers the five-dimension Market Selection Framework and scoring tool, the English-language market expansion sequence (five phases), the Localisation Threshold Assessment for non-English markets, the Regulatory and Compliance Map (GDPR, VAT/GST, consumer protection), the International Payment Infrastructure, the Cultural Adaptation Protocol, and the JV Partner Model for new market entry.
C46
Partnerships & Affiliate Scaling
RISER-Partnerships-Affiliate-Scaling-SOP.docx
The complete partnership and affiliate ecosystem architecture for scaling revenue through third-party relationships. Covers the Dream 100 partnership hierarchy, the affiliate programme architecture, commission and tracking infrastructure, partner qualification criteria, and the scaling mechanisms that turn early JV wins into systematic partnership revenue.
C47
Crisis Navigation & Reputation Command
RISER-Crisis-Navigation-Reputation-Command-SOP.docx
The complete crisis prevention, response, and recovery system for the knowledge business. Covers the six Crisis Types, the Reputation Monitoring Protocol (four channels with alert thresholds), the First 24-Hour Response Framework, the Public Statement Architecture (six components), the Community Crisis Communication Protocol, the Negative Review Response System, the False Claims and Online Attack Protocol, the Evidence Bank, and the Anti-Fragile Reputation Strategy.
TRACK 9 — COURSES 48–55
AI COMMAND & LEGACY
The agentic AI infrastructure, autonomous executive systems, ethical governance, workforce architecture, and generational legacy framework
Course
SOP Title
Filename
Description
C48
Agentic Orchestration & Workflow Governance
RISER-Agentic-Orchestration-Workflow-Governance-SOP.docx
The foundational governance architecture for all production AI agents. Covers the five Agentic Architecture Principles, the Six-Stage Agent Design Framework, the four Multi-Agent Orchestration Patterns (Sequential Pipeline, Parallel Fan-Out, Evaluator-Optimizer Loop, Orchestrator-Subagent Hierarchy), the Human-in-the-Loop Governance System, the Agent Safety and Constraint Architecture, the Production System Prompt Template, and the Agent Performance Dashboard.
C49
AI Quality Assurance Gate
RISER-AI-Quality-Assurance-Gate-SOP.docx
The quality assurance framework that validates AI agent outputs against defined quality standards before they enter the production system. Covers the QA Gate structure, the evaluation criteria for each content and communication type, the systematic error pattern detection, and the feedback loop that improves agent quality over time.
C50
AI Executive Command: The Autonomous CEO
RISER-AI-Executive-Command-Autonomous-CEO-SOP.docx
The five-layer AI executive intelligence system that provides the operator with synthesised intelligence across every business function. Covers Layer 1 (Strategy Intelligence), Layer 2 (Market Intelligence Engine), Layer 3 (Revenue Operations Command Centre), Layer 4 (Customer Success Intelligence), Layer 5 (Operations Oversight), the Executive Decision Support Framework, the 90-Minute CEO Review Protocol, and the CEO Alerting system.
C51
AI Strategic Foresight
RISER-AI-Strategic-Foresight-SOP.docx
The AI-powered system for detecting strategic signals 12–24 months before market shifts become visible to competitors. Covers the Foresight Philosophy (Signal Diversity, Time Horizon Differentiation, Action Orientation), the Horizon Scanning Protocol (five signal categories), the Horizon Scanner Agent specification, the Scenario Construction Engine (three-scenario framework), the Weak Signal Detection System, the Technology Adoption Curve Monitoring Framework, the Buyer Evolution Modelling Protocol, the Strategic Options Stress Test, and the Foresight-to-Strategy Integration System.
C52
AI Governance & Ethical Shielding
RISER-AI-Governance-Ethical-Shielding-SOP.docx
The complete ethical governance framework for all AI deployments in the knowledge business. Covers the AI Ethics Charter (five principles), the Buyer Trust Protection Standard, the Transparency and Disclosure Protocol (six AI involvement types), the Bias Detection and Correction Framework, the AI-Generated Content Labelling Standard, the Data Privacy and Consent Architecture, the Right to Explanation Protocol, the Harm Prevention Protocol (five harm types), the Community AI Disclosure Standard, and the Annual Governance Audit.
C53
AI Workforce Architecture & Role Replication
RISER-AI-Workforce-Architecture-Role-Replication-SOP.docx
The framework for designing the hybrid human-AI workforce. Covers the Four-Quadrant Role Classification (by judgement required and relationship sensitivity), the complete AI Role Library for knowledge businesses (ten agent roles), the Human-AI Collaboration Protocol for each team role, the Hiring Decision Matrix, the Team Capacity Model at each revenue stage, the Context Package for new team members, and the Workforce Evolution Roadmap.
C54
Autonomous Empire & Generational Legacy
RISER-Autonomous-Empire-Generational-Legacy-SOP.docx
The architecture for building a knowledge business that generates compounding value without the operator’s daily presence. Covers the Autonomous Operations Architecture (daily operations without the operator), the Brand Independence Protocol (four components), the Evergreen Revenue Engine (five streams), the IP and Asset Protection Framework, the Generational Wealth Architecture, the Licensing and Certification Empire design, the Exit Optionality Model (four paths), and the Legacy Programme Architecture.
C55
Enterprise Reinvention & Futureproofing
RISER-Enterprise-Reinvention-Futureproofing-SOP.docx
The capstone framework for ensuring the business remains dominant across multiple technological and market cycles. Covers the Business Reinvention Cycle (four phases across the annual calendar), the Disruption Radar (five signal categories), the Asset Portfolio Review (five asset categories), the Knowledge Business Evolution Paths (four strategies), the AI-Native Business Architecture (four pillars), the Institutional Knowledge Codification System, the Succession and Transition Framework, and the Five Legacy Operating Principles.
Category
SOP Title
Filename
Description
Track 3
Beta Testing Methodology
RISER-Beta-Testing-Methodology-SOP.docx
Detailed validation protocol for the first cohort, feedback collection frameworks, and the specific evidence thresholds for confirming product-market fit before full launch.
Track 3
Weekly Offer Review Ritual
RISER-Weekly-Offer-Review-Ritual-SOP.docx
The structured 60-minute weekly review protocol for monitoring offer performance, identifying declining metrics, and making systematic improvements to the Core Offer on a continuous basis.
Track 3
Offer Stacking & Unbundling
RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx
Detailed tactical framework for creating bonus stacks that increase perceived value, and the unbundling approach for creating lower-priced entry offers from existing curriculum components.
Track 3
Product Versioning & Offer Changelog
RISER-Product-Versioning-Offer-Changelog-SOP.docx
The system for managing curriculum updates, version control, communicating changes to active buyers, and maintaining a living changelog that supports the Beta Testing loop.
Track 3
Dead Offer Resurrection Playbook
RISER-Dead-Offer-Resurrection-Playbook-SOP.docx
The diagnostic and revival protocol for offers that have stopped converting. Covers the four resurrection diagnoses (hook failure, mechanism failure, avatar drift, market saturation) and the specific fix sequence for each.
Track 3
Product Kill Criteria & Post-Launch Audit
RISER-Product-Kill-Criteria-Post-Launch-SOP.docx
The decision framework for retiring underperforming offers, including the specific quantitative thresholds, the post-mortem audit protocol, and the asset salvage process for recovering curriculum components from retired offers.
Track 3
Fulfilment Stress Test
RISER-Fulfilment-Stress-Test-SOP.docx
The pre-launch delivery audit that confirms the offer can be delivered at the promised quality level to the projected buyer volume without the operator’s personal intervention in every buyer interaction.
Track 3
Bonus Discipline Audit
RISER-Bonus-Discipline-Audit-SOP.docx
The framework for evaluating whether each bonus in the offer stack is genuinely increasing conversion or simply adding complexity. Defines the three criteria for a bonus worth keeping and the audit process for removing value-diluting bonuses.
Track 3
Guarantee Type Testing Protocol
RISER-Guarantee-Type-Testing-Protocol-SOP.docx
The structured testing framework for identifying which guarantee type (results-based, satisfaction-based, conditional, unconditional) maximises conversion for the specific offer and buyer profile without increasing refund rate.
Track 3
Price Elasticity Testing Framework
RISER-Price-Elasticity-Testing-Framework-SOP.docx
The methodology for systematically testing price points to identify the price that maximises revenue per offer, covering the split-test structure, the minimum sample sizes required for significance, and the decision criteria for price changes.
Track 3
Downsell Paths
RISER-Downsell-Paths-SOP.docx
The framework for capturing buyers who decline the Core Offer by presenting a lower-commitment alternative that maintains the buyer relationship and produces incremental revenue that would otherwise be lost.
Track 3
10x Mechanism Test & Rename Cadence
RISER-10x-Mechanism-Test-Rename-Cadence-SOP.docx
The protocol for testing whether renaming or re-framing the Core Offer’s mechanism (while keeping the underlying transformation identical) produces a significant conversion rate improvement.
Track 4
Proof Injection Checklist
RISER-Proof-Injection-Checklist-SOP.docx
The systematic audit for ensuring that every persuasive claim in the sales page, email sequences, and advertising is supported by specific, documentable proof: transformation stories, data, credentials, or demonstrations.
Track 4
Voice Consistency Gate
RISER-Voice-Consistency-Gate-Founder-POV-Layer-SOP.docx
The editorial quality gate ensuring that all content, copy, and communications produced by the team or by AI systems is consistent with the operator’s authentic voice, Brand Belief System, and Founder Point of View.
Category
SOP Title
Filename
Description
Track 4
Perfect Webinar Script
RISER-Perfect-Webinar-Script-SOP.docx
The complete 90-minute webinar script framework adapted for the knowledge business operator. Covers the Big Domino opener, the Three Secrets structure, the Stack and Close sequence, and the live Q&A conversion protocol.
Track 4
VSL Script Template
RISER-VSL-Script-Template-SOP.docx
The Video Sales Letter script framework for Core Offer and Traffic Hook video sales pages. Covers hook, problem agitation, mechanism introduction, social proof integration, offer presentation, guarantee, and close.
Track 4
Phone Sales Call Scripts
RISER-Phone-Sales-Call-Scripts-SOP.docx
The structured script and conversational framework for high-ticket phone sales calls, including qualification, problem exploration, mechanism presentation, objection handling, and close sequences for Premium and Done-for-You offers.
Track 4
NLP Conversation Frameworks
RISER-NLP-Live-Conversation-Frameworks-SOP.docx
Advanced NLP-based conversational frameworks for application calls, qualification conversations, and discovery calls. Covers rapport building, pacing and leading, re-frames, and the conversational close.
Track 4
Attractive Character Content Bible
RISER-Attractive-Character-Content-Bible-SOP.docx
The editorial standard document built on the Attractive Character Development System. Defines the operator’s voice guidelines, thematic pillars, and content decision-making framework for consistent brand expression across all channels.
Track 4
Post-MVO Forensic Audit Loop
RISER-Post-MVO-Forensic-Audit-Loop-SOP.docx
The structured post-launch audit protocol that analyses every element of the Minimum Viable Offer’s performance to identify the specific changes that would most improve conversion rates in the next iteration.
Category
SOP Title
Filename
Description
Track 5
Content Differentiation Score
RISER-Content-Differentiation-Score-SOP.docx
The diagnostic scoring system for assessing whether any piece of content is genuinely differentiated from competitor content. Produces a differentiation score across five dimensions and identifies the specific changes that would increase the score.
Track 5
Content Decay & Refresh Protocol
RISER-Content-Decay-Refresh-Protocol-SOP.docx
The system for identifying organic content that is losing traffic or rankings over time and refreshing it to restore and improve its search performance. Covers the decay detection triggers, the refresh prioritisation framework, and the specific update protocol for each content type.
Track 5
Interactive Tools Content Category
RISER-Interactive-Tools-Content-Category-SOP.docx
The framework for designing calculators, scorecards, assessments, and diagnostic tools as premium content assets. Covers the tool design principles, the Traffic Hook integration, and the link acquisition value that well-built tools generate.
Track 5
Content to Revenue Attribution
RISER-Content-to-Revenue-Attribution-SOP.docx
The methodology for tracking which specific content pieces and content types are producing Traffic Hook opt-ins and Core Offer buyers. Covers the attribution model, the UTM tagging standard, and the monthly content ROI review.
Track 5
Buyer Stage Tagging
RISER-Buyer-Stage-Tagging-SOP.docx
The complete tagging architecture for the email platform that records each subscriber’s awareness stage, engagement level, and position in the buyer journey. Enables segmented content delivery and accurate conversion tracking.
Track 5
Long-Form YouTube Channel Strategy
RISER-Long-Form-YouTube-Channel-Strategy-SOP.docx
The complete strategy and production framework for a long-form YouTube channel as an authority asset and audience acquisition engine.
Category
SOP Title
Filename
Description
Track 6
Lead Funnel / Squeeze Page Types
RISER-Lead-Funnel-Squeeze-Page-Types-SOP.docx
The complete taxonomy of Traffic Hook landing page designs, with the specific copy structure, visual hierarchy, and CTA placement for each type (short-form, video, quiz, challenge, webinar registration).
Track 6
SLO Funnel
RISER-SLO-Funnel-SOP.docx
The Self-Liquidating Offer funnel architecture that allows paid traffic acquisition costs to be partially or fully offset by immediate post-opt-in sales. Covers the SLO product design, pricing, page structure, and integration with the Indoctrination Sequence.
Track 6
Book Funnel
RISER-Book-Funnel-SOP.docx
The complete book funnel framework for using a physical or digital book as a high-converting Traffic Hook and authority-builder. Covers the book offer positioning, the free-plus-shipping model, the upsell sequence, and the book funnel’s role in the Offer Ecosystem.
Track 6
Challenge Funnel
RISER-Challenge-Funnel-SOP.docx
The 5-7 day challenge funnel architecture for creating high-engagement lead generation events. Covers challenge design, the daily content structure, the live delivery format, and the conversion sequence from challenge participant to Core Offer buyer.
Track 6
Virtual Summit Funnel
RISER-Virtual-Summit-Funnel-SOP.docx
The virtual summit (online conference) as a high-volume list building and authority event. Covers speaker recruitment, the summit registration and replay funnel, the monetisation sequence, and the post-summit email campaign for Core Offer conversion.
Track 6
Application Funnel
RISER-Application-Funnel-SOP.docx
The application-based funnel for high-ticket and Premium offers. Covers the application page design, the qualification questions, the application review process, and the conversion call sequence for approved applicants.
Track 6
Funnel Hacking Methodology
RISER-Funnel-Hacking-Methodology-SOP.docx
The systematic process for analysing competitor funnels, identifying the structural and copy elements that are producing their conversions, and applying those insights to improve the operator’s own funnels.
Track 6
Dream 100 Strategy
RISER-Dream-100-Strategy-SOP.docx
The complete Dream 100 relationship-building and borrowed traffic system. Covers the Dream 100 list construction, the outreach sequence, the value-first relationship protocol, and the transition from relationship to promotional partnership.
Track 6
Borrowed Traffic (Brunson)
RISER-Borrowed-Traffic-SOP.docx
The framework for generating Traffic Hook opt-ins and buyers through other operators’ audiences. Covers guest appearances, content syndication, and the specific asks that produce high-quality borrowed traffic introductions.
Track 6
Influencer & Creator Outreach
RISER-Influencer-Creator-Outreach-SOP.docx
The outreach framework for identifying, approaching, and activating social media influencers and content creators as Traffic Hook promotion partners. Covers creator qualification criteria, outreach templates, commission structures, and campaign tracking.
Track 6
Community Infiltration Strategy
RISER-Community-Infiltration-Strategy-SOP.docx
The ethical community presence strategy for establishing the operator as a valuable contributor in niche communities (Facebook groups, subreddits, LinkedIn groups, industry forums) and converting community relationships into Traffic Hook subscribers.
Track 6
Podcast Guesting (Dream 100)
RISER-Podcast-Guesting-Dream-100-SOP.docx
The complete podcast guest strategy: identifying and prioritising target shows from the Dream 100 list, crafting the pitch, delivering a high-value interview, and converting podcast listeners into Traffic Hook subscribers.
Category
SOP Title
Filename
Description
Track 6
Meta Ads Campaign Architecture
RISER-Meta-Ads-Campaign-Architecture-SOP.docx
The complete Meta (Facebook and Instagram) advertising campaign structure: the cold-to-warm campaign hierarchy, the creative testing framework, the budget scaling ladder, the audience architecture, and the conversion optimisation protocol.
Track 6
Paid Ads Scaling Ladder (Hormozi)
RISER-Paid-Ads-Scaling-Ladder-SOP.docx
The structured advertising budget scaling protocol for progressing from initial test campaigns through to consistent scaling. Covers the budget thresholds for each scaling stage, the metrics that confirm readiness to scale, and the risk management protocols for each level.
Track 6
Platform-Specific Ad Protocols
RISER-Platform-Specific-Ad-Protocols-SOP.docx
Campaign architecture and best practice protocols for Google Ads (search and display), YouTube Ads, LinkedIn Ads, and TikTok Ads as supplementary traffic channels to the primary Meta campaign.
Track 6
ROAS Benchmarks by Value Ladder Tier
RISER-ROAS-Benchmarks-Value-Ladder-Tier-SOP.docx
The performance benchmarks for advertising return on ad spend at each level of the Value Ladder, from Traffic Hook cold traffic through Core Offer retargeting to Premium ascension campaigns.
Track 6
Media Buyer Hiring & Management
RISER-Media-Buyer-Hiring-Management-SOP.docx
The specification, recruitment, onboarding, and performance management framework for hiring a media buyer or advertising agency. Covers the job description, the trial campaign protocol, the reporting standards, and the performance review framework.
Track 6
Creative Brief Template
RISER-Creative-Brief-Template-SOP.docx
The standardised creative brief format for briefing video editors, graphic designers, and copywriters on advertising creative production. Covers the campaign context, the target audience, the message hierarchy, the call to action, and the technical specifications.
Category
SOP Title
Filename
Description
Track 8
Affiliate Program Architecture
RISER-Affiliate-Program-Architecture-SOP.docx
The complete affiliate programme design including commission structures, tracking infrastructure, affiliate portal setup, payout protocols, and the affiliate tier system that incentivises top performers.
Track 8
Affiliate Recruitment Outreach Templates
RISER-Affiliate-Recruitment-Outreach-Templates-SOP.docx
The outreach email sequence and follow-up protocol for recruiting affiliates and JV partners from the Dream 100 list, with templates for cold, warm, and referral-based outreach scenarios.
Track 8
Affiliate Asset Creation Checklist
RISER-Affiliate-Asset-Creation-Checklist-SOP.docx
The complete list of assets required to support affiliate promotional campaigns: email swipe copy, social media posts, banner graphics, video scripts, FAQ documents, and the affiliate portal setup.
Track 8
JV Email Swap
RISER-JV-Email-Swap-SOP.docx
The framework for structuring and executing reciprocal email list promotions with JV partners. Covers the swap terms negotiation, the email copy standards, the list size qualification criteria, and the post-swap performance review.
Track 8
JV Broker & Deal Sourcing
RISER-JV-Broker-Deal-Sourcing-SOP.docx
The methodology for identifying and working with JV brokers to access partnership opportunities with established operators. Covers broker qualification, fee structures, the deal sourcing process, and the due diligence protocol for broker-introduced partners.
Track 8
JV Deal Structures & Commission Terms
RISER-JV-Deal-Structures-Commission-Terms-SOP.docx
The complete taxonomy of JV deal structures (revenue share, flat fee, hybrid, equity), the commission calculation methods, the tracking and payment protocols, and the negotiation framework for each structure type.
Track 8
JV Legal Agreement Template
RISER-JV-Legal-Agreement-Template-SOP.docx
The standard JV partnership agreement template covering the key commercial terms, IP ownership, promotional obligations, tracking and payment terms, dispute resolution, and termination clauses.
Track 8
Co-Launch (Partner Launch)
RISER-Co-Launch-Partner-Launch-SOP.docx
The framework for executing a co-launch where two or more operators jointly promote a single offer to their combined audiences. Covers the co-launch structure, the promotional asset sharing protocol, the revenue split agreement, and the post-launch debriefing framework.
Track 8
Past Buyer Referral Programme
RISER-Past-Buyer-Referral-Programme-SOP.docx
The referral programme architecture for incentivising existing buyers to refer new buyers. Covers referral incentive design, tracking infrastructure, the referral communication sequence, and the activation protocol for converting advocates into active referrers.
Track 8
IP Licensing Model
RISER-IP-Licensing-Model-SOP.docx
The framework for licensing the operator’s curriculum, methodology, or brand to other operators for delivery in adjacent markets. Covers the licensing fee structure, the quality standards agreement, the licensee onboarding protocol, and the ongoing relationship management framework.
Track 8
White Label Pricing Architecture
RISER-White-Label-Pricing-Architecture-SOP.docx
The pricing framework for white-label licensing arrangements where the licensee delivers the operator’s methodology under their own brand. Covers the pricing tiers, volume discounts, exclusivity premiums, and the pricing audit protocol.
Track 8
White Label Partner Onboarding
RISER-White-Label-Partner-Onboarding-SOP.docx
The complete onboarding protocol for white-label partners including the training requirements, brand guidelines, delivery standards, quality assurance protocol, and the ongoing communication framework.

Original native catalogue tables

These preserve the original table grouping and all cell text, including legacy labels and source claims. The teaching qualifications above still apply.

Original table 1

Navigation GuideCore Course SOPs follow the Course Number / SOP Title / Filename / Description format.Supplementary Resource SOPs are grouped by the course or topic area they support.All files are delivered as .docx files to /mnt/user-data/outputs/ during SOP production sessions.The system is designed to be used sequentially: each track builds on the infrastructure of the tracks before it.

Original table 2

TRACK 1 — COURSES 1–5OPERATOR FOUNDATIONThe mental model, market context, and decision architecture of the sovereign knowledge business operator

Original table 3

Course	SOP Title	Filename	Description
C1	The Sovereign Operator Mindset	RISER-Sovereign-Operator-Mindset-SOP.docx	The foundational mindset and identity framework for the knowledge business operator. Covers the shift from employee mindset to sovereign operator, the RISER Nation operating principles, and the daily practices that establish the psychological infrastructure for building at scale.
C2	Market Reality (2025–2035)	RISER-Market-Reality-2025-2035-SOP.docx	A forward-looking map of the forces reshaping the knowledge economy across the decade. Covers the AI transformation of content and expertise markets, the compression of trust timelines, the shift from information scarcity to attention scarcity, and the operator’s strategic positioning in this landscape.
C3	Decision Intelligence & Risk Management	RISER-Decision-Intelligence-Risk-Management-SOP.docx	The systematic framework for making high-quality decisions under conditions of incomplete information, time pressure, and consequence. Covers the Decision Intelligence Protocol, risk categorisation, reversible versus irreversible decisions, and the biases that produce poor operator decisions at scale.
C4	Problems Create Markets — Market Gap Detection	RISER-Problems-Create-Markets-SOP.docx	The methodology for identifying commercially viable market problems that are large enough to build a knowledge business on. Covers the Problem Hierarchy, the Market Gap Detection Protocol, the difference between a problem and a preference, and the evidence standards for confirming a market exists before building an offer.
C5	Skill & Experience Mapping	RISER-Skill-Experience-Mapping-SOP.docx	The structured inventory process for identifying the operator’s genuine expertise, lived experience, and transferable skill sets. Covers the Skill-Experience Matrix, the Expertise Depth Assessment, the distinction between knowledge the operator has versus knowledge they have applied with results, and the connection between the operator’s experience and their Core Offer’s mechanism.

Original table 4

TRACK 2 — COURSES 6–10FIND YOUR MARKETThe research, validation, and buyer intelligence systems that confirm a specific niche is viable before any product is built

Original table 5

Course	SOP Title	Filename	Description
C6	Pattern Recognition	RISER-Pattern-Recognition-SOP.docx	The framework for reading the deeper patterns in market data, buyer language, and competitive positioning that are not visible from surface-level research alone. Covers the Pattern Recognition Protocol, how to identify recurring themes in buyer conversations that indicate genuine market pain, and the specific signals that separate a trend from a pattern.
C7	Psychographic DNA	RISER-Psychographic-DNA-SOP.docx	The complete buyer intelligence framework that goes beyond demographics to capture the buyer’s worldview, values, fears, desires, prior attempts at the transformation, and the specific language they use to describe their problem. The Psychographic DNA is the single most referenced source document in the entire RISER Nation system, used in every content, copy, and offer decision.
C8	Negative Avatar Modelling	RISER-Negative-Avatar-Modelling-SOP.docx	The systematic process for defining who the business should not serve. Covers the Negative Avatar profile (the buyer who will never succeed with the methodology regardless of the operator’s efforts), the financial and reputational cost of serving misaligned buyers, and how to incorporate Negative Avatar criteria into the sales page, the Traffic Hook, and the qualification process.
C9	Niche Validation & StorySelling	RISER-Niche-Validation-StorySelling-SOP.docx	The validation framework for confirming that the identified niche has sufficient commercial depth before major investment. Covers the three-stage Niche Validation Protocol, the Story Selling approach to qualifying buyer intent through narrative, and the minimum evidence thresholds that confirm a niche is viable.
C10	Hard Organic Proof Threshold	RISER-Hard-Organic-Proof-Threshold-SOP.docx	The evidence standard that must be met before the operator invests in building the full Core Offer. Defines what constitutes genuine proof of market demand versus wishful interpretation of signals. Covers the Organic Proof Threshold scorecard, the minimum buyer conversations required, and the red flags that indicate a niche that appears valid but is not commercially viable.

Original table 6

TRACK 3 — COURSES 11–14BUILD YOUR OFFERThe product design, pricing, packaging, and validation frameworks for the Core Offer and the complete Value Ladder

Original table 7

Course	SOP Title	Filename	Description
C11	Value Ladder Architecture	RISER-Value-Ladder-Architecture-SOP.docx	The complete framework for designing the operator’s full offer ecosystem: from the free Traffic Hook through the SLO, Core Offer, Continuity, Premium, and Done-for-You tiers. Covers the pricing logic for each rung, the buyer journey through the ecosystem, and the relationship between each rung’s promise and the buyer’s progressive transformation.
C12	Offer Scorecard	RISER-Offer-Scorecard-SOP.docx	A structured diagnostic tool for evaluating any offer against the eight dimensions that determine commercial viability. Covers the Offer Scorecard assessment criteria, how to interpret a low score in any dimension, and the specific fixes that address each type of offer weakness.
C13	Offer Stacking & Unbundling Strategy	RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx	The framework for maximising perceived value at every price point through strategic inclusion and exclusion of offer elements. Covers the Offer Stacking Protocol (what bonuses and components to include at each tier), the Unbundling Strategy for creating lower-priced entry offers from existing curriculum, and the principle that perceived value must always exceed price.
C14	Beta Testing Methodology	RISER-Beta-Testing-Methodology-SOP.docx	The structured process for validating the Core Offer with a small group of real buyers before full launch. Covers the Beta Cohort selection criteria, the beta pricing strategy, the specific feedback mechanisms that produce actionable curriculum improvement data, and the evidence thresholds that confirm the offer is ready for full launch.

Original table 8

TRACK 4 — COURSES 15–21PERSUASION & MESSAGINGThe complete persuasion architecture, from the psychology of attention through to the live sales conversation and the community identity system

Original table 9

Course	SOP Title	Filename	Description
C15	Hook Engineering & Attention Engineering	RISER-Hook-Engineering-Attention-Engineering-SOP.docx	The systematic framework for creating hooks that capture attention in a saturated content environment. Covers the Five Hook Types, the Hook Quality Assessment Standard, the attention pattern interrupts that work across video, written, and audio formats, and the testing protocol for identifying which hook formulas resonate most strongly with the specific buyer profile.
C16	Scientific Persuasion & Influence Mastery	RISER-Scientific-Persuasion-Influence-Mastery-SOP.docx	The evidence-based persuasion framework grounded in decision science, behavioural economics, and the psychology of belief change. Covers Cialdini’s principles in the knowledge business context, the Belief Change Sequence, the stages of buyer awareness and how to communicate at each stage, and the ethical distinction between persuasion and manipulation.
C17	Behavioral Logic & Nudge Theory	RISER-Behavioral-Logic-Nudge-Theory-SOP.docx	The applied framework for designing buyer journeys that guide decisions without coercion. Covers choice architecture in the sales funnel, the nudge mechanisms that reduce buyer friction, default option design, commitment and consistency principles in offer design, and the specific nudge applications for each stage of the buyer journey.
C18	Identity-Based Marketing	RISER-Identity-Based-Marketing-SOP.docx	The framework for creating marketing that connects the operator’s offer to the buyer’s deepest sense of who they are and who they want to become. Covers identity bridging, the language of aspiration versus the language of outcome, and how to make the Core Offer feel like the natural expression of the buyer’s identity rather than an external purchase.
C19	NLP Live Conversation Frameworks	RISER-NLP-Live-Conversation-Frameworks-SOP.docx	The structured conversational frameworks for live sales calls, application calls, and qualification conversations. Covers the NLP-based rapport, pacing, and leading techniques for live conversation, the seven qualification questions that identify genuine buyers, the re-frame protocols for common live conversation objections, and the call close structure.
C20	Objection Bank	RISER-Objection-Bank-SOP.docx	The complete system for cataloguing, categorising, and resolving every objection the operator’s buyers raise. Covers the Objection Bank structure, the four objection categories (price, timing, belief, fit), the resolution frameworks for each category, and the process for updating the Objection Bank continuously from support tickets, community questions, and live call transcripts.
C21	Attractive Character Development System	RISER-Attractive-Character-Development-System-SOP.docx	The framework for developing the operator’s on-brand public persona: the Attractive Character elements (leader, adventurer, reporter, reluctant hero), the Brand Belief System (We Believe, We Reject), the Cultural Lexicon, the Origin Story structure, and the Tribe Formation Sequence. The Attractive Character is the public expression of the operator’s identity that makes the brand magnetic to the ideal buyer.

Original table 10

TRACK 5 — COURSES 22–27CONTENT & VISIBILITYThe content architecture, distribution strategy, SEO foundation, and AI content systems that build compounding organic authority

Original table 11

Course	SOP Title	Filename	Description
C22	Content Calendar by Awareness Level	RISER-Content-Calendar-Awareness-Level-SOP.docx	The content planning system based on the five levels of buyer awareness. Covers how to distribute content across awareness stages (Unaware, Problem Aware, Solution Aware, Product Aware, Most Aware), the content types that move buyers along the awareness spectrum, and the publishing cadence that maintains consistent presence without the operator becoming a content production machine.
C23	AI-Driven Content Repurposing System	RISER-AI-Content-Repurposing-System-SOP.docx	The complete system for converting the operator’s flagship long-form content into multiple derivative formats using AI tools. Covers the repurposing hierarchy (podcast to YouTube to article to newsletter to social to clips), the AI-assisted workflows for each conversion, the quality standards for repurposed content, and the distribution schedule that maximises the reach of each piece of flagship content.
C24	Attractive Character Content Bible	RISER-Attractive-Character-Content-Bible-SOP.docx	The editorial standard document that ensures all content produced across all channels and formats is consistent with the operator’s Attractive Character. Covers the Content Bible structure, the voice and tone guidelines, the thematic pillars, the recurring content formats, and the editorial decision-making framework for any content question that is not covered by specific campaign instructions.
C25	Podcast as Primary Authority Channel	RISER-Podcast-Primary-Authority-Channel-SOP.docx	The complete framework for building a podcast that serves as the operator’s flagship authority platform. Covers format selection, episode structure, interview guest strategy, show notes and SEO, the Traffic Hook integration, episode production workflow, distribution strategy, and the metrics that indicate a podcast is effectively building the operator’s audience and authority.
C26	Technical SEO Foundations	RISER-Technical-SEO-Foundations-SOP.docx	The complete technical SEO infrastructure for the knowledge business operator’s Owned Media Hub. Covers site architecture, crawlability, Core Web Vitals, on-page elements, schema markup, the initial keyword research and cluster architecture, the Quarterly Technical SEO Audit, and the Google Search Console monitoring protocol.
C27	AEO, GEO & Machine Trust	RISER-AEO-GEO-Machine-Trust-SOP.docx	The framework for optimising content to be cited, referenced, and recommended by AI search systems including Google’s AI Overview, Perplexity, and ChatGPT. Covers the Entity Establishment Protocol, answer-first content formatting, FAQPage and HowTo schema, the AEO Citation Monitoring System, and the specific content formats that AI systems preferentially cite.

Original table 12

TRACK 6 — COURSES 28–32TRAFFIC & CONVERSIONThe email architecture, sales conversion infrastructure, paid advertising foundations, and retargeting systems

Original table 13

Course	SOP Title	Filename	Description
C28	Email Fundamentals	RISER-Email-Fundamentals-SOP.docx	The complete email marketing system architecture. Covers the email platform configuration, the Traffic Hook opt-in sequence, the 21-day Indoctrination Sequence that converts subscribers into buyers, the broadcast email calendar, the list segmentation and tagging architecture, the deliverability maintenance protocol, and the email metrics that determine whether the list is healthy and converting.
C29	Sales Page Architecture & Conversion Copy	RISER-Sales-Page-Architecture-SOP.docx	The structural and copywriting framework for the Core Offer’s primary sales page. Covers the twelve-section sales page architecture, the hook-to-offer arc, social proof placement and hierarchy, the guarantee framework, the objection removal sequence, the CTA structure, and the split-testing protocol for continuous conversion rate optimisation.
C30	Paid Ads Foundations	RISER-Paid-Ads-Foundations-SOP.docx	The foundational paid advertising framework covering the principles that apply across all paid channels: the Traffic Triangle (audience, offer, creative), the Traffic Hook campaign structure, the cold audience testing protocol, the budget allocation framework, and the campaign metrics hierarchy that determines what to optimise and when to scale.
C31	Omni-Channel Retargeting Systems	RISER-Omni-Channel-Retargeting-SOP.docx	The five-tier retargeting ecosystem that converts the warm audience into buyers. Covers the audience tier architecture (by intent stage), the retargeting sequences for each tier, the exclusion architecture that prevents wasted spend on existing buyers, the cross-platform deployment model, and the retargeting campaign metrics.
C32	Server-Side Tracking & Conversion APIs	RISER-Server-Side-Tracking-SOP.docx	The technical setup and governance for server-side event tracking using the Meta Conversions API, Google Tag Manager server-side, and webhook-based event forwarding. Covers the Event Match Quality optimisation, the browser-to-server tracking stack, the event deduplication protocol, and the EMQ monitoring system.

Original table 14

TRACK 7 — COURSES 33–38AUTOMATION & SOVEREIGNTYThe data independence infrastructure, platform immunity systems, and AI-powered automation stack

Original table 15

Course	SOP Title	Filename	Description
C33	Data Sovereignty — Dig Your Own Well	RISER-Data-Sovereignty-SOP.docx	The complete framework for building platform-independent data infrastructure. Covers the Owned Asset Hierarchy, the email-first audience strategy, the monthly data export protocol, the Backup and Continuity Systems, and the specific configuration for ensuring the operator’s subscriber list, buyer records, and content assets cannot be lost through a single platform failure.
C34	Platform Immunity	RISER-Platform-Immunity-SOP.docx	The risk management system for the operator’s dependency on third-party platforms. Covers the Platform Dependency Risk Matrix, the Platform Change Response Playbook, the monthly platform immunity audit, the diversification standard for each platform category, and the specific contingency procedures for the most common platform failure scenarios.
C35	The RISER Automation Engine	RISER-Automation-Engine-SOP.docx	The complete six-blueprint automation stack that removes the operator from routine operational execution. Covers Blueprint 1 (Purchase Router), Blueprint 2 (Onboarding Sequence), Blueprint 3 (Programme Completion Sync), Blueprint 4 (List Hygiene), Blueprint 5 (Refund & Cancellation), and Blueprint 6 (Daily Analytics Sync). The Automation Engine is the operational foundation of the entire Track 8 and Track 9 system.
C36	Make.com Blueprint Deployment	RISER-Make-Blueprint-Deployment-SOP.docx	The technical implementation guide for all six Make.com blueprints in the RISER Automation Engine. Covers the specific module configurations, webhook structures, error handling protocols, and the testing sequence for confirming each blueprint is operating correctly before deploying to production.
C37	Advanced n8n & GitHub Automations	RISER-Advanced-n8n-GitHub-Automations-SOP.docx	The implementation guide for the four AI-agent workflows built in n8n: the Content Research Agent (AI-Agent 1), the Buyer Support Triage Agent (AI-Agent 2), the Performance Summary Agent (AI-Agent 3), and the Objection Bank Updater Agent (AI-Agent 4). Covers self-hosted n8n setup, the GitHub version control protocol, and the agent governance framework.
C38	Vibe Coding & Generative Video Pipelines	RISER-Vibe-Coding-Generative-Video-Pipelines-SOP.docx	The framework for using AI-assisted coding and generative video tools to build custom operator tools without traditional programming skill. Covers the Vibe Coding Protocol for building custom calculators and tools, the generative video pipeline for educational video production, and the quality standards for AI-generated multimedia assets.

Original table 16

TRACK 8 — COURSES 39–47SCALE & EXPANDThe scaling readiness, offer ecosystem, customer success, retargeting, SEO dominance, global expansion, and crisis navigation systems

Original table 17

Course	SOP Title	Filename	Description
C39	Scaling Foundations & Operational Readiness	RISER-Scaling-Foundations-Operational-Readiness-SOP.docx	The gate assessment that confirms whether the business is genuinely ready to scale. Covers the five-dimension Scaling Readiness Audit (Delivery, Automation, Financial, Content, Operator Capacity), the five Scaling Failure Modes, the financial unit economics required before scaling investment begins, and the Operator Role Evolution sequence.
C40	Offer Ecosystem & Backend Monetisation	RISER-Offer-Ecosystem-Backend-Monetisation-SOP.docx	The complete six-rung Offer Ecosystem Map and the Backend Monetisation Sequence that maximises buyer lifetime value. Covers the post-purchase journey architecture (Order Bump, OTO, Early Win upsell, Graduation sequence), the Premium Offer design framework, the Continuity Engine design, the Ascension Path engineering, and the Ecosystem Revenue Optimisation Dashboard.
C41	Customer Success & Retention Systems	RISER-Customer-Success-Retention-Systems-SOP.docx	The complete buyer success infrastructure including the Buyer Health Score (five-component composite metric), the At-Risk Intervention Protocol (three levels), the First Win by Day 30 design framework, the Community Success Architecture, the Refund Prevention Framework, the Continuity Churn Prediction Model, and the Advocacy Activation System.
C42	Retargeting Ecosystems & Warm Audience Monetisation	RISER-Retargeting-Ecosystems-Warm-Audience-SOP.docx	The advanced retargeting architecture that serves every layer of the warm audience ecosystem simultaneously across the offer lifecycle. Covers the six-layer Ecosystem Audience Map, the Buyer Journey Retargeting sequences for each offer transition, cross-sell retargeting, the Lookalike Expansion Framework, advanced creative fatigue management, and the Retargeting P&L Dashboard.
C43	Long-Form YouTube Channel Strategy	RISER-Long-Form-YouTube-Channel-Strategy-SOP.docx	The complete framework for building a long-form YouTube channel as a compounding authority and acquisition asset. Covers channel positioning, video SEO, the Traffic Hook integration, content calendar strategy for YouTube, retention optimisation, and the monetisation pathway from subscriber to Traffic Hook opt-in to Core Offer buyer.
C44	Advanced SEO & Search Domination	RISER-Advanced-SEO-Search-Domination-SOP.docx	The advanced SEO framework for achieving topical authority and category dominance in the operator’s niche. Covers the four Topical Authority Stages, the Competitive Gap Mapping Protocol, Intent-Matching at page level, link acquisition through digital PR and Dream 100 outreach, the Content Refresh and Compounding System, SERP Feature Domination, the E-E-A-T Maximisation Protocol, programmatic SEO, and the Organic Search P&L Model.
C45	Global Market Expansion	RISER-Global-Market-Expansion-SOP.docx	The systematic framework for expanding the knowledge business into new geographic markets. Covers the five-dimension Market Selection Framework and scoring tool, the English-language market expansion sequence (five phases), the Localisation Threshold Assessment for non-English markets, the Regulatory and Compliance Map (GDPR, VAT/GST, consumer protection), the International Payment Infrastructure, the Cultural Adaptation Protocol, and the JV Partner Model for new market entry.
C46	Partnerships & Affiliate Scaling	RISER-Partnerships-Affiliate-Scaling-SOP.docx	The complete partnership and affiliate ecosystem architecture for scaling revenue through third-party relationships. Covers the Dream 100 partnership hierarchy, the affiliate programme architecture, commission and tracking infrastructure, partner qualification criteria, and the scaling mechanisms that turn early JV wins into systematic partnership revenue.
C47	Crisis Navigation & Reputation Command	RISER-Crisis-Navigation-Reputation-Command-SOP.docx	The complete crisis prevention, response, and recovery system for the knowledge business. Covers the six Crisis Types, the Reputation Monitoring Protocol (four channels with alert thresholds), the First 24-Hour Response Framework, the Public Statement Architecture (six components), the Community Crisis Communication Protocol, the Negative Review Response System, the False Claims and Online Attack Protocol, the Evidence Bank, and the Anti-Fragile Reputation Strategy.

Original table 18

TRACK 9 — COURSES 48–55AI COMMAND & LEGACYThe agentic AI infrastructure, autonomous executive systems, ethical governance, workforce architecture, and generational legacy framework

Original table 19

Course	SOP Title	Filename	Description
C48	Agentic Orchestration & Workflow Governance	RISER-Agentic-Orchestration-Workflow-Governance-SOP.docx	The foundational governance architecture for all production AI agents. Covers the five Agentic Architecture Principles, the Six-Stage Agent Design Framework, the four Multi-Agent Orchestration Patterns (Sequential Pipeline, Parallel Fan-Out, Evaluator-Optimizer Loop, Orchestrator-Subagent Hierarchy), the Human-in-the-Loop Governance System, the Agent Safety and Constraint Architecture, the Production System Prompt Template, and the Agent Performance Dashboard.
C49	AI Quality Assurance Gate	RISER-AI-Quality-Assurance-Gate-SOP.docx	The quality assurance framework that validates AI agent outputs against defined quality standards before they enter the production system. Covers the QA Gate structure, the evaluation criteria for each content and communication type, the systematic error pattern detection, and the feedback loop that improves agent quality over time.
C50	AI Executive Command: The Autonomous CEO	RISER-AI-Executive-Command-Autonomous-CEO-SOP.docx	The five-layer AI executive intelligence system that provides the operator with synthesised intelligence across every business function. Covers Layer 1 (Strategy Intelligence), Layer 2 (Market Intelligence Engine), Layer 3 (Revenue Operations Command Centre), Layer 4 (Customer Success Intelligence), Layer 5 (Operations Oversight), the Executive Decision Support Framework, the 90-Minute CEO Review Protocol, and the CEO Alerting system.
C51	AI Strategic Foresight	RISER-AI-Strategic-Foresight-SOP.docx	The AI-powered system for detecting strategic signals 12–24 months before market shifts become visible to competitors. Covers the Foresight Philosophy (Signal Diversity, Time Horizon Differentiation, Action Orientation), the Horizon Scanning Protocol (five signal categories), the Horizon Scanner Agent specification, the Scenario Construction Engine (three-scenario framework), the Weak Signal Detection System, the Technology Adoption Curve Monitoring Framework, the Buyer Evolution Modelling Protocol, the Strategic Options Stress Test, and the Foresight-to-Strategy Integration System.
C52	AI Governance & Ethical Shielding	RISER-AI-Governance-Ethical-Shielding-SOP.docx	The complete ethical governance framework for all AI deployments in the knowledge business. Covers the AI Ethics Charter (five principles), the Buyer Trust Protection Standard, the Transparency and Disclosure Protocol (six AI involvement types), the Bias Detection and Correction Framework, the AI-Generated Content Labelling Standard, the Data Privacy and Consent Architecture, the Right to Explanation Protocol, the Harm Prevention Protocol (five harm types), the Community AI Disclosure Standard, and the Annual Governance Audit.
C53	AI Workforce Architecture & Role Replication	RISER-AI-Workforce-Architecture-Role-Replication-SOP.docx	The framework for designing the hybrid human-AI workforce. Covers the Four-Quadrant Role Classification (by judgement required and relationship sensitivity), the complete AI Role Library for knowledge businesses (ten agent roles), the Human-AI Collaboration Protocol for each team role, the Hiring Decision Matrix, the Team Capacity Model at each revenue stage, the Context Package for new team members, and the Workforce Evolution Roadmap.
C54	Autonomous Empire & Generational Legacy	RISER-Autonomous-Empire-Generational-Legacy-SOP.docx	The architecture for building a knowledge business that generates compounding value without the operator’s daily presence. Covers the Autonomous Operations Architecture (daily operations without the operator), the Brand Independence Protocol (four components), the Evergreen Revenue Engine (five streams), the IP and Asset Protection Framework, the Generational Wealth Architecture, the Licensing and Certification Empire design, the Exit Optionality Model (four paths), and the Legacy Programme Architecture.
C55	Enterprise Reinvention & Futureproofing	RISER-Enterprise-Reinvention-Futureproofing-SOP.docx	The capstone framework for ensuring the business remains dominant across multiple technological and market cycles. Covers the Business Reinvention Cycle (four phases across the annual calendar), the Disruption Radar (five signal categories), the Asset Portfolio Review (five asset categories), the Knowledge Business Evolution Paths (four strategies), the AI-Native Business Architecture (four pillars), the Institutional Knowledge Codification System, the Succession and Transition Framework, and the Five Legacy Operating Principles.

Original table 20

Category	SOP Title	Filename	Description
Track 3	Beta Testing Methodology	RISER-Beta-Testing-Methodology-SOP.docx	Detailed validation protocol for the first cohort, feedback collection frameworks, and the specific evidence thresholds for confirming product-market fit before full launch.
Track 3	Weekly Offer Review Ritual	RISER-Weekly-Offer-Review-Ritual-SOP.docx	The structured 60-minute weekly review protocol for monitoring offer performance, identifying declining metrics, and making systematic improvements to the Core Offer on a continuous basis.
Track 3	Offer Stacking & Unbundling	RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx	Detailed tactical framework for creating bonus stacks that increase perceived value, and the unbundling approach for creating lower-priced entry offers from existing curriculum components.
Track 3	Product Versioning & Offer Changelog	RISER-Product-Versioning-Offer-Changelog-SOP.docx	The system for managing curriculum updates, version control, communicating changes to active buyers, and maintaining a living changelog that supports the Beta Testing loop.
Track 3	Dead Offer Resurrection Playbook	RISER-Dead-Offer-Resurrection-Playbook-SOP.docx	The diagnostic and revival protocol for offers that have stopped converting. Covers the four resurrection diagnoses (hook failure, mechanism failure, avatar drift, market saturation) and the specific fix sequence for each.
Track 3	Product Kill Criteria & Post-Launch Audit	RISER-Product-Kill-Criteria-Post-Launch-SOP.docx	The decision framework for retiring underperforming offers, including the specific quantitative thresholds, the post-mortem audit protocol, and the asset salvage process for recovering curriculum components from retired offers.
Track 3	Fulfilment Stress Test	RISER-Fulfilment-Stress-Test-SOP.docx	The pre-launch delivery audit that confirms the offer can be delivered at the promised quality level to the projected buyer volume without the operator’s personal intervention in every buyer interaction.
Track 3	Bonus Discipline Audit	RISER-Bonus-Discipline-Audit-SOP.docx	The framework for evaluating whether each bonus in the offer stack is genuinely increasing conversion or simply adding complexity. Defines the three criteria for a bonus worth keeping and the audit process for removing value-diluting bonuses.
Track 3	Guarantee Type Testing Protocol	RISER-Guarantee-Type-Testing-Protocol-SOP.docx	The structured testing framework for identifying which guarantee type (results-based, satisfaction-based, conditional, unconditional) maximises conversion for the specific offer and buyer profile without increasing refund rate.
Track 3	Price Elasticity Testing Framework	RISER-Price-Elasticity-Testing-Framework-SOP.docx	The methodology for systematically testing price points to identify the price that maximises revenue per offer, covering the split-test structure, the minimum sample sizes required for significance, and the decision criteria for price changes.
Track 3	Downsell Paths	RISER-Downsell-Paths-SOP.docx	The framework for capturing buyers who decline the Core Offer by presenting a lower-commitment alternative that maintains the buyer relationship and produces incremental revenue that would otherwise be lost.
Track 3	10x Mechanism Test & Rename Cadence	RISER-10x-Mechanism-Test-Rename-Cadence-SOP.docx	The protocol for testing whether renaming or re-framing the Core Offer’s mechanism (while keeping the underlying transformation identical) produces a significant conversion rate improvement.
Track 4	Proof Injection Checklist	RISER-Proof-Injection-Checklist-SOP.docx	The systematic audit for ensuring that every persuasive claim in the sales page, email sequences, and advertising is supported by specific, documentable proof: transformation stories, data, credentials, or demonstrations.
Track 4	Voice Consistency Gate	RISER-Voice-Consistency-Gate-Founder-POV-Layer-SOP.docx	The editorial quality gate ensuring that all content, copy, and communications produced by the team or by AI systems is consistent with the operator’s authentic voice, Brand Belief System, and Founder Point of View.

Original table 21

Category	SOP Title	Filename	Description
Track 4	Perfect Webinar Script	RISER-Perfect-Webinar-Script-SOP.docx	The complete 90-minute webinar script framework adapted for the knowledge business operator. Covers the Big Domino opener, the Three Secrets structure, the Stack and Close sequence, and the live Q&A conversion protocol.
Track 4	VSL Script Template	RISER-VSL-Script-Template-SOP.docx	The Video Sales Letter script framework for Core Offer and Traffic Hook video sales pages. Covers hook, problem agitation, mechanism introduction, social proof integration, offer presentation, guarantee, and close.
Track 4	Phone Sales Call Scripts	RISER-Phone-Sales-Call-Scripts-SOP.docx	The structured script and conversational framework for high-ticket phone sales calls, including qualification, problem exploration, mechanism presentation, objection handling, and close sequences for Premium and Done-for-You offers.
Track 4	NLP Conversation Frameworks	RISER-NLP-Live-Conversation-Frameworks-SOP.docx	Advanced NLP-based conversational frameworks for application calls, qualification conversations, and discovery calls. Covers rapport building, pacing and leading, re-frames, and the conversational close.
Track 4	Attractive Character Content Bible	RISER-Attractive-Character-Content-Bible-SOP.docx	The editorial standard document built on the Attractive Character Development System. Defines the operator’s voice guidelines, thematic pillars, and content decision-making framework for consistent brand expression across all channels.
Track 4	Post-MVO Forensic Audit Loop	RISER-Post-MVO-Forensic-Audit-Loop-SOP.docx	The structured post-launch audit protocol that analyses every element of the Minimum Viable Offer’s performance to identify the specific changes that would most improve conversion rates in the next iteration.

Original table 22

Category	SOP Title	Filename	Description
Track 5	Content Differentiation Score	RISER-Content-Differentiation-Score-SOP.docx	The diagnostic scoring system for assessing whether any piece of content is genuinely differentiated from competitor content. Produces a differentiation score across five dimensions and identifies the specific changes that would increase the score.
Track 5	Content Decay & Refresh Protocol	RISER-Content-Decay-Refresh-Protocol-SOP.docx	The system for identifying organic content that is losing traffic or rankings over time and refreshing it to restore and improve its search performance. Covers the decay detection triggers, the refresh prioritisation framework, and the specific update protocol for each content type.
Track 5	Interactive Tools Content Category	RISER-Interactive-Tools-Content-Category-SOP.docx	The framework for designing calculators, scorecards, assessments, and diagnostic tools as premium content assets. Covers the tool design principles, the Traffic Hook integration, and the link acquisition value that well-built tools generate.
Track 5	Content to Revenue Attribution	RISER-Content-to-Revenue-Attribution-SOP.docx	The methodology for tracking which specific content pieces and content types are producing Traffic Hook opt-ins and Core Offer buyers. Covers the attribution model, the UTM tagging standard, and the monthly content ROI review.
Track 5	Buyer Stage Tagging	RISER-Buyer-Stage-Tagging-SOP.docx	The complete tagging architecture for the email platform that records each subscriber’s awareness stage, engagement level, and position in the buyer journey. Enables segmented content delivery and accurate conversion tracking.
Track 5	Long-Form YouTube Channel Strategy	RISER-Long-Form-YouTube-Channel-Strategy-SOP.docx	The complete strategy and production framework for a long-form YouTube channel as an authority asset and audience acquisition engine.

Original table 23

Category	SOP Title	Filename	Description
Track 6	Lead Funnel / Squeeze Page Types	RISER-Lead-Funnel-Squeeze-Page-Types-SOP.docx	The complete taxonomy of Traffic Hook landing page designs, with the specific copy structure, visual hierarchy, and CTA placement for each type (short-form, video, quiz, challenge, webinar registration).
Track 6	SLO Funnel	RISER-SLO-Funnel-SOP.docx	The Self-Liquidating Offer funnel architecture that allows paid traffic acquisition costs to be partially or fully offset by immediate post-opt-in sales. Covers the SLO product design, pricing, page structure, and integration with the Indoctrination Sequence.
Track 6	Book Funnel	RISER-Book-Funnel-SOP.docx	The complete book funnel framework for using a physical or digital book as a high-converting Traffic Hook and authority-builder. Covers the book offer positioning, the free-plus-shipping model, the upsell sequence, and the book funnel’s role in the Offer Ecosystem.
Track 6	Challenge Funnel	RISER-Challenge-Funnel-SOP.docx	The 5-7 day challenge funnel architecture for creating high-engagement lead generation events. Covers challenge design, the daily content structure, the live delivery format, and the conversion sequence from challenge participant to Core Offer buyer.
Track 6	Virtual Summit Funnel	RISER-Virtual-Summit-Funnel-SOP.docx	The virtual summit (online conference) as a high-volume list building and authority event. Covers speaker recruitment, the summit registration and replay funnel, the monetisation sequence, and the post-summit email campaign for Core Offer conversion.
Track 6	Application Funnel	RISER-Application-Funnel-SOP.docx	The application-based funnel for high-ticket and Premium offers. Covers the application page design, the qualification questions, the application review process, and the conversion call sequence for approved applicants.
Track 6	Funnel Hacking Methodology	RISER-Funnel-Hacking-Methodology-SOP.docx	The systematic process for analysing competitor funnels, identifying the structural and copy elements that are producing their conversions, and applying those insights to improve the operator’s own funnels.
Track 6	Dream 100 Strategy	RISER-Dream-100-Strategy-SOP.docx	The complete Dream 100 relationship-building and borrowed traffic system. Covers the Dream 100 list construction, the outreach sequence, the value-first relationship protocol, and the transition from relationship to promotional partnership.
Track 6	Borrowed Traffic (Brunson)	RISER-Borrowed-Traffic-SOP.docx	The framework for generating Traffic Hook opt-ins and buyers through other operators’ audiences. Covers guest appearances, content syndication, and the specific asks that produce high-quality borrowed traffic introductions.
Track 6	Influencer & Creator Outreach	RISER-Influencer-Creator-Outreach-SOP.docx	The outreach framework for identifying, approaching, and activating social media influencers and content creators as Traffic Hook promotion partners. Covers creator qualification criteria, outreach templates, commission structures, and campaign tracking.
Track 6	Community Infiltration Strategy	RISER-Community-Infiltration-Strategy-SOP.docx	The ethical community presence strategy for establishing the operator as a valuable contributor in niche communities (Facebook groups, subreddits, LinkedIn groups, industry forums) and converting community relationships into Traffic Hook subscribers.
Track 6	Podcast Guesting (Dream 100)	RISER-Podcast-Guesting-Dream-100-SOP.docx	The complete podcast guest strategy: identifying and prioritising target shows from the Dream 100 list, crafting the pitch, delivering a high-value interview, and converting podcast listeners into Traffic Hook subscribers.

Original table 24

Category	SOP Title	Filename	Description
Track 6	Meta Ads Campaign Architecture	RISER-Meta-Ads-Campaign-Architecture-SOP.docx	The complete Meta (Facebook and Instagram) advertising campaign structure: the cold-to-warm campaign hierarchy, the creative testing framework, the budget scaling ladder, the audience architecture, and the conversion optimisation protocol.
Track 6	Paid Ads Scaling Ladder (Hormozi)	RISER-Paid-Ads-Scaling-Ladder-SOP.docx	The structured advertising budget scaling protocol for progressing from initial test campaigns through to consistent scaling. Covers the budget thresholds for each scaling stage, the metrics that confirm readiness to scale, and the risk management protocols for each level.
Track 6	Platform-Specific Ad Protocols	RISER-Platform-Specific-Ad-Protocols-SOP.docx	Campaign architecture and best practice protocols for Google Ads (search and display), YouTube Ads, LinkedIn Ads, and TikTok Ads as supplementary traffic channels to the primary Meta campaign.
Track 6	ROAS Benchmarks by Value Ladder Tier	RISER-ROAS-Benchmarks-Value-Ladder-Tier-SOP.docx	The performance benchmarks for advertising return on ad spend at each level of the Value Ladder, from Traffic Hook cold traffic through Core Offer retargeting to Premium ascension campaigns.
Track 6	Media Buyer Hiring & Management	RISER-Media-Buyer-Hiring-Management-SOP.docx	The specification, recruitment, onboarding, and performance management framework for hiring a media buyer or advertising agency. Covers the job description, the trial campaign protocol, the reporting standards, and the performance review framework.
Track 6	Creative Brief Template	RISER-Creative-Brief-Template-SOP.docx	The standardised creative brief format for briefing video editors, graphic designers, and copywriters on advertising creative production. Covers the campaign context, the target audience, the message hierarchy, the call to action, and the technical specifications.

Original table 25

Category	SOP Title	Filename	Description
Track 8	Affiliate Program Architecture	RISER-Affiliate-Program-Architecture-SOP.docx	The complete affiliate programme design including commission structures, tracking infrastructure, affiliate portal setup, payout protocols, and the affiliate tier system that incentivises top performers.
Track 8	Affiliate Recruitment Outreach Templates	RISER-Affiliate-Recruitment-Outreach-Templates-SOP.docx	The outreach email sequence and follow-up protocol for recruiting affiliates and JV partners from the Dream 100 list, with templates for cold, warm, and referral-based outreach scenarios.
Track 8	Affiliate Asset Creation Checklist	RISER-Affiliate-Asset-Creation-Checklist-SOP.docx	The complete list of assets required to support affiliate promotional campaigns: email swipe copy, social media posts, banner graphics, video scripts, FAQ documents, and the affiliate portal setup.
Track 8	JV Email Swap	RISER-JV-Email-Swap-SOP.docx	The framework for structuring and executing reciprocal email list promotions with JV partners. Covers the swap terms negotiation, the email copy standards, the list size qualification criteria, and the post-swap performance review.
Track 8	JV Broker & Deal Sourcing	RISER-JV-Broker-Deal-Sourcing-SOP.docx	The methodology for identifying and working with JV brokers to access partnership opportunities with established operators. Covers broker qualification, fee structures, the deal sourcing process, and the due diligence protocol for broker-introduced partners.
Track 8	JV Deal Structures & Commission Terms	RISER-JV-Deal-Structures-Commission-Terms-SOP.docx	The complete taxonomy of JV deal structures (revenue share, flat fee, hybrid, equity), the commission calculation methods, the tracking and payment protocols, and the negotiation framework for each structure type.
Track 8	JV Legal Agreement Template	RISER-JV-Legal-Agreement-Template-SOP.docx	The standard JV partnership agreement template covering the key commercial terms, IP ownership, promotional obligations, tracking and payment terms, dispute resolution, and termination clauses.
Track 8	Co-Launch (Partner Launch)	RISER-Co-Launch-Partner-Launch-SOP.docx	The framework for executing a co-launch where two or more operators jointly promote a single offer to their combined audiences. Covers the co-launch structure, the promotional asset sharing protocol, the revenue split agreement, and the post-launch debriefing framework.
Track 8	Past Buyer Referral Programme	RISER-Past-Buyer-Referral-Programme-SOP.docx	The referral programme architecture for incentivising existing buyers to refer new buyers. Covers referral incentive design, tracking infrastructure, the referral communication sequence, and the activation protocol for converting advocates into active referrers.
Track 8	IP Licensing Model	RISER-IP-Licensing-Model-SOP.docx	The framework for licensing the operator’s curriculum, methodology, or brand to other operators for delivery in adjacent markets. Covers the licensing fee structure, the quality standards agreement, the licensee onboarding protocol, and the ongoing relationship management framework.
Track 8	White Label Pricing Architecture	RISER-White-Label-Pricing-Architecture-SOP.docx	The pricing framework for white-label licensing arrangements where the licensee delivers the operator’s methodology under their own brand. Covers the pricing tiers, volume discounts, exclusivity premiums, and the pricing audit protocol.
Track 8	White Label Partner Onboarding	RISER-White-Label-Partner-Onboarding-SOP.docx	The complete onboarding protocol for white-label partners including the training requirements, brand guidelines, delivery standards, quality assurance protocol, and the ongoing communication framework.

Assigned source documents: RISER-MVO-Widget-Explainer-Script.docx — source 1 ·

Use the MVO Decision Engine from buyer evidence to expansion

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

Video placeholder

Record after checking the demonstrated widget version. Revised spoken teaching follows, with original recording cues retained in the source appendix.

Lesson outline

Start — use decisions to guide a test
00½ — Pain Discovery: retain evidence and attribution
01 — Hungry Avatar: separate scoring from market evidence
02 — Idea or No Idea: test a clear offer hypothesis
03 — Profitable Problem: examine recurrence and alternatives
04 — Grand Slam Offer: improve the benefit and reduce the burden
04½ — Offer Stack: make each addition useful and truthful
05 — Core Four Distribution: use a defined denominator
05½ — Dream 100: find the people who already reach the buyer
06 — Hook, headline, body and CTA
06½ — Persuasion architecture: support belief with evidence
07 — Deploy: define readiness beyond a verdict
08 — Iterate: use learning without overstating certainty
09 — Pivot or Hold: investigate the whole funnel
10 — Scale: calculate the actual effect
11 — Repeat and Compound: earn expansion
Brief — preserve the reasoning, not just the badge

Start — use decisions to guide a test

MVO means Minimum Viable Offer. Use this decision engine to record a specific buyer problem, design a deliverable, choose a route to buyers and decide what evidence will justify continuing or changing course. GO means the checklist’s conditions were met; REWORK identifies an issue to examine; NO is a reason to pause and investigate. None of these labels proves demand or predicts commercial success.

The source script names sixteen gates, but its rail contains seventeen cells: Start, fifteen substantive gates and Brief. We will cover every cell. Detection spans Pain Discovery through Profitable Problem; Construction spans Offer through Persuasion; Deployment covers Deploy and Iterate; Compound covers Pivot, Scale and Repeat.

The script describes both free navigation and mandatory locks. Static inspection of the staged April-30 D0106 candidate confirms free navigation: clicking a rail cell calls the destination without checking earlier verdicts. Treat the verdict as advice, not an enforced lock. This candidate has browser-local state storage with error handling, JSON export and a print command, but storage can fail and its current deployed identity has not been established.

The source synthesizes Hormozi’s offer design and economics, Brunson’s value ladder and Dream 100, Kennedy’s direct-response and risk-reversal themes, Cialdini’s influence principles, and Schwartz’s awareness/sophistication framework. The specific RISER scores and cutoffs are custom rules. Its promises of saving or compressing ninety days are unverified motivating claims, not lesson outcomes.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

00½ — Pain Discovery: retain evidence and attribution

Create up to five pain cards from interviews, support tickets, sales calls or relevant public discussions. Each card needs a plain-language title, a proposed intensity/frequency score from zero to one hundred, frequency category, source URL or community, audience profile, up to five verbatim quotes and one to three possible solution or monetization seeds. The frequency choices described are daily, weekly, monthly, quarterly and one-time. Do not invent a customer quote to fill a field.

When multiple cards exist, choose a lead pain and group related pains into a cluster when the evidence supports a common problem. The lead informs avatar and problem work; other cards supply supporting context. The described VOC vault collects quotes for avatar pain, problem statement, dream outcome, hook, headline, body and reciprocity gift. Preserve the attribution when moving a quote. The apply-lead action is described as mapping score to pain intensity, frequency to the problem and solution seeds to the mechanism; check the actual version before demonstrating these helper behaviors.

The explainer proposes GO for a lead score of at least seventy, three substantive quotes, audience and title. The inspected candidate instead accepts any card at seventy-plus while requiring a selected lead, a ten-character lead title, thirty-character audience and three quotes of ten or more characters across the cards. Eight total quotes enters its stronger branch. These length checks do not prove quote quality, representativeness or buying intent.

For the downstream four-point boost, the candidate requires the lead itself to score at least eighty-five and contain five qualifying quotes. Skipping research keeps the working hypothesis explicit. The script’s claimed thirty-to-fifty-percent copy lift is unsupported; compare actual buyer understanding and response rather than assuming the vault automatically improves conversion.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

01 — Hungry Avatar: separate scoring from market evidence

Write who the buyer is and what they say the problem is. The source contrasts vague small-business targeting with solo CPAs early in practice, under a specified billing level and with a particular career background. Use relevant buying context rather than unnecessary demographic precision. Quote genuine buyer language and refine the seeded pain-card fields.

Score purchasing power, market trajectory, reachability and pain intensity from one to ten. Use examples to sharpen the answer and external evidence to challenge it. The script describes Examples, Sharpen This and Verify Externally help panels, plus an AI critique of specificity, weakest element and a suggested rewrite. Those are assistance features, not independent market validation, and their actual model/capability must be checked before a live demo.

The candidate sums four ratings, adds the qualifying four-point evidence boost and caps the result at forty. GO is thirty-two or more; REWORK is twenty-four through thirty-one; below twenty-four is NO. This resolves the script’s omitted boundary at thirty-two for that candidate only. The two text fields need twenty characters in code even though explanatory prose recommends a much richer description.

Inspect weak dimensions separately. A high sum can conceal one low score and cannot confirm a hungry market on its own. Record what evidence would change each rating. A low self-score prompts better research or a revised offer; it does not prove no viable business can exist.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

02 — Idea or No Idea: test a clear offer hypothesis

Write one sentence naming the buyer, result, timeframe and obstacle removed: I help this buyer achieve this outcome within this period without this specific difficulty. Then classify competitive reality: many successful operators, some weaker competitors, almost no competition or a claimed first-mover position. Existing competitors can indicate demand; neither their existence nor their absence settles your opportunity.

The source’s hundred-dollar-today exercise asks whether you can name ten prospective buyers who might pay for an initial version. Treat those names and opinions as a hypothesis until real purchasing behavior and fulfillment evidence exist. The candidate requires thirty-to-two-hundred characters and completed choices; no competition or no immediate buyers returns NO, thin competition or uncertainty returns REWORK.

The code additionally suggests a twenty-person outreach/two-payment experiment. That remains a source exercise, not outreach performed by this curriculum. Before any test, define a legitimate offer, who may appropriately be contacted, the observation period and how you will interpret a negative result. Failure can reflect access, message or timing as well as the idea.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

03 — Profitable Problem: examine recurrence and alternatives

Describe the problem in concrete buyer language, how often it occurs, what happens if it remains unresolved and what the buyer currently does instead. The status quo can be a competitor even when it is a spreadsheet, an internal workaround or doing nothing.

The source favors frequent, expensive problems and treats low inaction cost as a NO. In the inspected code, daily/monthly/quarterly/one-time frequencies receive four/three/two/one points and high/moderate/low inaction costs receive four/two/zero. Six or more is GO after other checks. The map has no weekly key, even though the broader explainer discusses weekly pain.

Recurring problems can support continuity when buyers need and value repeated help. They do not automatically create recurring revenue. One-time, high-impact services can be viable too. Compare willingness to pay, delivery cost, acquisition cost and repeat need before converting the checklist preference into a business model.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

04 — Grand Slam Offer: improve the benefit and reduce the burden

Define a measurable desired outcome and why the buyer cares. List authentic evidence that makes achievement credible. Identify time to an initial result and the buyer’s effort or sacrifice. Compare done-for-you, done-with-you, templates and self-paced delivery according to fit and capacity. Name the method and explain how its actual process differs from alternatives.

Hormozi’s conceptual Value Equation relates desired outcome and perceived likelihood to time and effort. Use it to ask which benefit can become clearer and which burden can be reduced. A name such as Retainer Method, Pulse Protocol or Four-Lane Framework communicates a process; naming alone does not justify the script’s suggested jump from $97 to $4,997.

The candidate requires dream text, proof text, two ratings, time and effort choices, and a mechanism description. Its custom calculation is round(10 × dream rating × likelihood rating ÷ ((11 − time rating) + (11 − effort rating))). Time categories are weighted ten/eight/six/three; effort categories ten/eight/five/three. It uses a summed denominator, not the conceptual product denominator.

With both outcome ratings at ten and the fastest/lowest-effort categories, this code returns five hundred while displaying a maximum of one hundred. GO begins at thirty-five, REWORK at twenty and NO below twenty. Do not call this a calibrated score, percentile, probability or Hormozi’s validated numeric formula. Fix the substantive offer weaknesses and document the implementation discrepancy before using the score in a recording.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3 · Acquisition.com — Value Equation checklist

04½ — Offer Stack: make each addition useful and truthful

Name the offer and outline three to five bonuses. For each bonus, identify the next buyer obstacle it removes, its deliverable and any evidence supporting its price anchor. The source example is a named script library with seven scripts and a $497 anchor; use that claim only if those scripts and the valuation basis exist.

Choose a guarantee only after defining the service scope, exact terms, operational ability to honor it and actual commercial approval. The source proposes a conditional double-money-back example; it is not a required policy. Describe a real cohort limit, price window or bonus expiry only where it exists. Never fabricate a timer or capacity constraint to satisfy the tool.

Compare total stated stack value with actual price, while checking that both values have a legitimate basis. The source proposes a minimum three-to-one ratio and a five-to-ten-to-one preference. These are heuristics, not proven conversion thresholds. The code also rejects no guarantee, reworks implied guarantees or absent scarcity, and lacks adequate positive-number validation in the inspected calculation.

The source’s thirty-percent naming uplift, half-conversion guarantee assertion and mandatory-scarcity claims are not established by this document. Explain the stack through the buyer’s actual obstacles and fulfillment economics. A generous-looking total does not compensate for irrelevant bonuses or an unaffordable promise.

05 — Core Four Distribution: use a defined denominator

Choose a primary route for the initial test: warm outreach, cold outreach, content or paid advertising. Warm relationships may provide early feedback; identifiable prospects can support targeted outreach; content takes sustained work; paid distribution requires a workable economic model. These are channel choices, not guarantees of speed or low cost.

For ten customers at a one-percent conversion rate, the model requires one thousand opportunities. Spread across ninety days, round the average up to twelve per day. Define whether the denominator is contacts, conversations, clicks or qualified opportunities; these are different stages and cannot be substituted without a measured conversion chain.

Estimate acquisition cost, contribution-based lifetime value and payback before increasing paid spend. The candidate merely asks for a readiness choice and thirty-character volume explanation; it does not calculate or verify the economics. Its one-third-of-twelve-month-LTV, fifty-organic-customer and hundred-before-second-channel rules are source planning heuristics. Use actual margin, cash, quality and capacity to decide readiness.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

05½ — Dream 100: find the people who already reach the buyer

Create a starter list of twenty-five named people, podcasts, newsletters or communities your buyer follows. Record handles and URLs and explain audience fit. Here Dream 100 means relationships with audience owners, not merely a list of direct sales prospects.

Choose an initial approach: provide useful value, sponsor appropriate access or develop a mutual partnership. Write a first-touch gift or useful observation before planning an ask. The source’s warning that two approaches always burn a bridge is too absolute; clarity, relevance and the relationship determine what is appropriate.

The exercise suggests at least five contacts per week and often ten to twenty. These are work-planning targets, not universal invitation thresholds. The candidate only checks a hundred-character list and ten newline-counted entries, not twenty-five verified names. It also checks a thirty-character message and a volume category. Keep the exercise target separate from these weaker code checks, and do not claim messages have been sent.

06 — Hook, headline, body and CTA

Draft a hook that earns attention quickly, a headline that names outcome/timeframe/objection, and a short body that explains the problem, present approach, mechanism, proof and specific next action. A statistic must have a valid source; a testimonial must be genuine. A named useful asset usually communicates the next step more clearly than an unexplained learn-more button, but the source’s fifty-percent conversion lift is not verified.

Use relevant customer language with attribution and context. The script calls these four VOC-enabled textareas, but the inspected CTA control is a choice field. Its code checks hook length twenty-to-two-hundred characters, headline twenty-to-two-hundred-fifty, body at least eighty characters and a CTA category. That differs from the accompanying eighty-to-two-hundred-fifty-word body recommendation.

Read the draft aloud. Check that its promise matches the deliverable and that the CTA tells the buyer what happens next. Test comprehension and behavior rather than treating a character-count pass as proof of effective copy.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

06½ — Persuasion architecture: support belief with evidence

Name the central belief the buyer would need to accept to understand the offer’s value. This is the Big Domino planning prompt. Then examine objections about the method, the buyer’s ability and external circumstances. Do not label a valid concern false merely because it obstructs a sale; answer it honestly or change the offer.

Create a useful reciprocity resource with a defined outcome and format. The source example combines a retainer calculator, three-tier model, anchor logic, five proposals, PDF and Notion template, with a seven-minute use estimate and $2,000–$5,000 deal claims. Those details require real assets and evidence before reuse; they are not preexisting proof supplied by a template.

The local eight-input audit includes Big Domino text, belief text, gift text and five ratings: reciprocity, social proof, authority, unity and consistency. The code gives each up to two points, with intermediate one-point categories for the first four and two points for a multistep consistency choice. Missing reciprocity or low proof produces NO; otherwise below six is REWORK and six-plus GO.

Cialdini’s full seven-principle framework also includes liking and scarcity; this gate is a five-lever adaptation. Keep commitments voluntary, authority credible, shared identity authentic and proof relevant. The custom score does not determine conversion or establish the source’s claimed one-third ceiling without reciprocity.

07 — Deploy: define readiness beyond a verdict

Write a proposed launch date, founding-cohort size, beta price, decision rule and four operating functions: lead capture, payment, delivery and measurement. The source suggests a date within thirty days, five to ten founding members and a default of fewer than five paid buyers in fourteen days triggering an offer-angle review. Define exposure and evidence before interpreting that outcome.

The source warns against prices from $500 to $900 and recommends $497 or $997-plus. Those are pricing opinions, not a universal dead zone, and they conflict with the $500 and $597 service examples in Pricing Architecture. Select a price from buyer value, scope, costs and testing, rather than solely to earn GO.

The candidate checks only that a date is nonempty, not that it is within thirty days. It rejects fewer than three tools but can return GO for three of four despite labeling that choice REWORK. It accepts a truthy parsed price without a positive-value check. Review all four functions and actual scheduling yourself; the tool cannot certify launch readiness.

Start small enough to deliver responsibly and learn. The claimed tenfold testimonial-density advantage of a small cohort is unsupported. A beta must still deliver its promise, collect appropriate feedback and honor the agreed terms.

08 — Iterate: use learning without overstating certainty

Record actual conversations, a recurring observation, one offer lever to change, the buyer’s awareness, the market’s familiarity with competing claims and voluntary refund feedback. The source discourages fewer than ten conversations and prefers twenty to thirty; these can guide qualitative discovery but do not establish statistical significance.

Keep awareness and sophistication separate. Awareness asks whether a person is unaware, problem-aware, solution-aware, product-aware or most-aware. Sophistication concerns the claims and mechanisms the market has already encountered. A most-aware buyer does not automatically need a newly named mechanism. Nor does a saturated market justify exaggerated claims.

The source gives example sophistication guidance: direct claims early, mechanisms as competition grows, and identity/story where claims are exhausted. Its candidate adds a mechanism-renaming suggestion for later sophistication levels when changing outcome or likelihood. Treat renaming as a communication hypothesis; demonstrate an actual difference and measure whether the buyer understands it.

Invite refund feedback with five questions: what result was expected, what caused withdrawal, whether the issue concerned hook/audience/offer/onboarding/delivery, what might have helped, and whether the person would refer someone else. Participation is voluntary and must not be a condition of honoring a refund. The tool’s REWORK label for never conducting interviews is a learning prompt, not authority to withhold refunds.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

09 — Pivot or Hold: investigate the whole funnel

Inspect hook click-through, opt-in or buying behavior after the click, and customer outcomes such as refunds, retention and NPS. Compare with an appropriate baseline and sample size. Low click-through can indicate a weak message or poor distribution; low opt-in can reflect audience mismatch, landing-page relevance, technical failure or form friction. No single metric uniquely diagnoses the cause.

The source proposes ten hook variants with at least one hundred impressions each, refund rates above ten percent or negative NPS as stop signals, and the candidate adds below-five-percent refunds before renewed spend. These are example rules, not reliable universal cutoffs. Small samples can swing widely, and a serious delivery issue deserves attention even before a numeric threshold is crossed.

The code returns early for a hook problem before checking later customer-outcome flags. Review the entire funnel yourself so an early REWORK message does not hide a more important fulfillment problem. Pause or adjust acquisition when customer harm or delivery failure requires it; more traffic does not fix an unfulfilled promise.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

10 — Scale: calculate the actual effect

The source uses ten-plus customers from one channel, known unit economics and six-plus months of retention data as its scale signal. These are suggested planning gates, and the candidate trusts the selected status instead of checking records. Evaluate demand, capacity, customer results and cash before increasing a commitment.

Compare price, retention and volume as possible levers. A ten-percent price rise produces a fifty-percent profit increase only under specific assumptions. For example, price100 and unchanged cost80 give profit20; price110 gives profit30, a fifty-percent gain if volume and cost per sale stay fixed. Different margins or lost sales change the result.

A twenty-percent relative reduction in churn does not double lifetime value. Under a simple constant-contribution model LTV = contribution per period ÷ churn, changing churn from ten percent to eight percent raises LTV by twenty-five percent. Halving churn would double it under those same assumptions. Use cohort evidence when the simplified model does not fit.

Name the current limiting constraint across lead generation, sales, delivery or retention and choose a test that addresses it. The tool automatically reworks a volume-first choice, but a rigid lever order is not proof that price is always the right move. Record the predicted effect, the measurement period and a stopping rule.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

11 — Repeat and Compound: earn expansion

Ask existing buyers about their next problem; the source suggests twenty conversations. Compare a new offer to the same audience, the existing offer to an adjacent audience, and a new channel. Their order is a focus heuristic. Distinguish actual saturation from personal boredom, while recognizing that changing direction can have valid strategic or personal reasons.

The source ladder has five named positions: free bait, a $7–$97 tripwire, a $297–$1,997 core offer, monthly continuity and $5,000–$50,000 high-ticket delivery. Prices are examples. Create rungs only where they meet a real need and you can fulfill them; three offers do not automatically create a competitive moat.

The tool counts three five-character rung names but does not enforce the exact bait/core/continuity combination its message recommends. It treats no continuity as NO, less than twenty-percent recurring participation as weak and over sixty percent as strong. Those classifications do not prove retention quality, profitability or defensibility. Repeat buying can exist outside subscriptions.

Ten affiliates bringing five buyers each produces fifty buyers, but acquisition is not free: commissions, rewards, management, attribution and service costs remain. The source’s claim that eighty percent of profit lies in high-ticket delivery is unsupported, and the candidate’s thirty-percent commission is a proposed example, not an approved program. Calculate the net contribution before adopting any expansion.

Brief — preserve the reasoning, not just the badge

The source describes a brief containing pain research and top three quotes, avatar, idea, problem, offer, stack, distribution, Dream 100, copy, persuasion and launch plan, with iteration, scale and ladder sections where completed. Use verdict colors to locate questions that need attention, not to conceal uncertainty.

The local candidate exports a timestamp, current state and stored verdict records to JSON, and its print button opens the summary before printing. That does not prove the output fits on one page or that every downstream verdict has been recomputed after changes. Recheck dependent decisions when you change the lead pain, offer or economics, and keep the full evidence record linked beyond the three featured quotes.

For the recording, retain the original eight-section production map: opening3minutes, architecture3, pain4, market/offer5, distribution/copy/persuasion4, deployment/iteration3, pivot/scale/compound4, close2. These sum to twenty-eight minutes; the original overall estimate is twenty-eight to thirty-five. The claim that all segments are under five minutes conflicts with the five-minute segment. Time the revised script instead of promising that estimate.

Camera, b-roll, pause, graphic and gesture cues belong to the production notes, not the spoken dialogue. The complete original script below preserves those cues, doctrine passages, examples and lineage. Your exercise is to complete one evidence-linked decision record, identify an unresolved assumption and define a responsible next test. GO is permission to learn through that test, not a guarantee of success.

Supporting sources: MVO Widget Explainer — assigned source · Candidate MVO widget — source variant 1 · Candidate MVO widget — source variant 2 · Candidate MVO widget — source variant 3

Complete original script and production notes

The original includes claims and thresholds corrected in the teaching above. It remains intact for provenance and review.

Read the complete original source

THE RISER MVO WIDGET
Talking-Head Explainer Script
From Pain Discovery to Compound Moat — All 16 Gates
Built on Hormozi · Brunson · Kennedy · Cialdini
Estimated runtime: 28–35 minutes
Recordable in 8 sections
Version 3 · April 2026
How to Use This Script
This script is built for a talking-head explainer video. Read it aloud as written. The rhythm is intentional — short sentences, hard breaks, direct address.
Three things to know before you record.
1. Camera directions in red italic, indented.
[B-ROLL: show the widget on screen] · [PAUSE: 2 seconds] · [GESTURE: point to gate rail]
These are cues for editing or for live recording. Skip them when reading aloud.
2. Doctrine pull-quotes appear in red bordered blocks.
"Doctrine quote example — read this slower, with weight."
Slow your delivery for these. They are the lines viewers will clip and share.
3. Section runtimes appear at the top of each section.
If you want to record in chunks, every section ends with a clean break and a clean re-entry. The 8 sections of this video are all under 5 minutes individually.
Recording-friendly section map
Section 1 — Cold Open & Why the Widget Exists (3 min)
Section 2 — The 16-Gate Architecture (3 min)
Section 3 — Gate 00½ Pain Discovery (4 min)
Section 4 — Gates 01–04½: Market & Offer (5 min)
Section 5 — Gates 05–06½: Distribution, Copy, Persuasion (4 min)
Section 6 — Gates 07–08: Deploy & Iterate (3 min)
Section 7 — Gates 09–11: Pivot, Scale, Compound (4 min)
Section 8 — Brief, Close, & Call to Action (2 min)
Section 1 — Cold Open & Why the Widget Exists
Approx. 3 minutes
[OPEN: tight on camera, no graphics yet. Lean in slightly.]
Most ideas die for one reason.
Not because the operator was lazy.
Not because the market was wrong.
Because somebody spent ninety days building a thing that should have been killed in week one.
[PAUSE: 1 second. Hold camera.]
Or — the inverse. They had a real idea. A starving crowd was sitting right there. And they spent six months polishing copy when they should have shipped a janky version on a Tuesday and started learning.
Both failures look the same from the outside. Both feel productive while they happen. Both end the same way — with a founder asking why they have nothing to show for a year of their life.
"The widget I'm about to show you was built to do one thing. Save you ninety days on a bad idea — or compress ninety days on a good one."
[GRAPHIC IN: widget header — the words 'Idea or No Idea' on screen]
This is the RISER MVO Decision Engine. M-V-O stands for Minimum Viable Offer. The whole thing is a single HTML file. No backend. Nothing to install. You open it, you walk it, your answers save in your browser, and at the end you have a one-page brief that tells you exactly what to ship and exactly when to kill.
It's built on four operators.
Alex Hormozi — for offer construction, market scoring, and unit economics.
Russell Brunson — for the value ladder, the Dream 100, and the persuasion frameworks from Expert Secrets.
Dan Kennedy — for direct response, risk reversal, and the discipline around guarantees.
Robert Cialdini — for the seven principles of influence that decide whether your page converts or doesn't.
Sixteen gates. From "what does the market actually hurt over" all the way to "how do I compound this into a moat."
At every gate, you get one of three verdicts. GO — you can proceed, here's the next action. NO — you can't proceed, here's exactly why. REWORK — you're close, here's what to sharpen first.
[GRAPHIC IN: GO / NO / REWORK badges — green, deep red, gold]
This video walks every gate. End to end. No omissions. By the end you'll know what each gate checks for, what triggers a NO, and how the whole thing fits together.
Let's start with the architecture.
Section 2 — The 16-Gate Architecture
Approx. 3 minutes
[GRAPHIC: top-down view of the progress rail showing all 17 cells. Highlight the four phases as colored bands.]
The widget has a top rail. Each cell is a gate. You can click any gate at any time — there's no forced linear path. But the gates are organized into four phases, and each phase has a job.
Phase One — Detection
Gates zero-half through three. This is where you answer: is there actually a starving crowd here, and is the problem worth solving?
Gate 00½ — Pain Discovery. Import the voice of the customer.
Gate 01 — Hungry Avatar. Score the market on four dimensions.
Gate 02 — Idea or No Idea. Filter for competitive reality and proximity to demand.
Gate 03 — Profitable Problem. Confirm pain, frequency, and cost of inaction.
Phase Two — Construction
Gates four through six-and-a-half. This is where you build the offer, the stack, the channel, and the persuasion architecture.
Gate 04 — Grand Slam Offer. Score the Value Equation.
Gate 04½ — Offer Stack. Build bonuses, guarantee, scarcity, naming.
Gate 05 — Core Four Distribution. Pick one channel.
Gate 05½ — Dream 100. Name the hundred people who own your audience.
Gate 06 — Hook, Headline, Body. Write the copy.
Gate 06½ — Persuasion Architecture. The Big Domino, false beliefs, and the Cialdini audit.
Phase Three — Deployment
Gates seven and eight. This is where you ship and learn.
Gate 07 — Deploy. Lock the date, the cohort size, the price, and the kill rule.
Gate 08 — Iterate. Use real customer data to adjust one lever at a time.
Phase Four — Compound
Gates nine through eleven. This is where you decide what to scale, when to pivot, and how to turn one offer into a moat.
Gate 09 — Pivot or Hold. Diagnose hook, audience, or offer failure.
Gate 10 — Scale. Pick price, retention, or volume as your scale lever.
Gate 11 — Repeat. Build the value ladder, continuity, and affiliate motion.
Plus an intro and a one-page brief at the end.
"Most operators try to do all sixteen of these in their head, in parallel, simultaneously. That's why most ideas die. The widget does them sequentially. Each gate either passes you or stops you. There's no hand-waving past a fundamental flaw."
[B-ROLL: zoom in on the rail, click through each color-coded cell briefly to show the GO / NO / REWORK feedback]
Now let's walk every gate. Starting where the widget actually starts — Pain Discovery.
Section 3 — Gate 00½: Pain Discovery
Approx. 4 minutes
[GRAPHIC: Gate 00½ on screen — show the 'PainOnSocial / VOC import' rubric]
Before we get to the avatar gate, there's a step most operators skip. It's optional. But if you skip it, every downstream gate runs on hypothesis instead of evidence.
"Operators who guess at pain build for themselves. Operators who import pain build for the market."
Gate 00½ is called Pain Discovery. This is where you import voice-of-customer research before you start building the offer.
If you've run a PainOnSocial scan — that's the Reddit-mining tool that scores customer complaints — paste the cards here. If you've done customer interviews, support-ticket analysis, or sales-call transcripts, paste those too. Up to five pain cards.
[B-ROLL: show the widget — a pain card being added, fields filling in]
Each card captures seven things.
The pain title — one sentence in plain language.
A score from zero to one hundred — based on how intense and how frequent the pain is.
Frequency — daily, weekly, monthly, quarterly, or one-time.
The source community or URL — the subreddit, the Skool group, the LinkedIn search.
An audience profile — who is suffering, in your words.
Up to five verbatim customer quotes. Word for word, the way they wrote it.
One to three AI solution seeds — concept-stage solutions, with a suggested monetization model.
Once you have two or more cards, the widget asks you to pick one as the lead pain. The lead seeds Gate 01 and Gate 03 downstream. The other cards become supporting evidence.
If multiple pains orbit the same root frustration, you can group them into a cluster. The cluster becomes your offer surface — meaning the offer doesn't have to solve a single point pain, it can solve a cluster of related pains. That's how bigger offers get built.
[GRAPHIC: highlight the 'Lead pain' selector and the 'Cluster' grouping]
Then there's the Voice-of-Customer Vault.
Every quote you paste into any pain card automatically aggregates into a vault accessible from seven downstream textareas. The avatar pain field. The problem statement. The dream outcome. The hook. The headline. The body. The reciprocity gift.
Each of those fields gets a small button — "Pull from VOC vault." Click it, modal opens with all your quotes, click any quote, it inserts straight into your answer with attribution.
"This is the single highest-leverage feature in the whole widget. Copy that uses real customer language outperforms invented copy by thirty to fifty percent. The vault makes that automatic."
Click "Apply lead pain to downstream gates." The widget pre-fills your avatar fields, sets the pain intensity score on a one-to-ten scale based on the PainOnSocial score, maps the frequency, and seeds the offer mechanism field with your solution seeds.
If you don't have research yet — there's a skip button right at the top. Click skip, and you proceed straight to Gate 01. The widget still works. It just runs on weaker fuel. You can come back to Pain Discovery any time once you have data.
[GRAPHIC: show the 'Skip · I have no research yet' button]
Verdict logic on this gate. GO requires a lead card with score seventy or higher, at least three substantive quotes total, audience profile filled, and a card title. If you have a lead card scoring eighty-five or higher with five-plus quotes, the widget rewards that on Gate 01 — the market score gets a four-point evidence boost.
Bottom line: this gate is optional, but it's the multiplier. Skip it and the widget is sharp. Use it and the widget is sharp and grounded in evidence.
Section 4 — Gates 01 through 04½: Market & Offer
Approx. 5 minutes
Gate 01 — Hungry Avatar
"The most important thing you sell is not your product. It's the market you sell it into. A starving crowd is the difference between selling steak and selling sand."
Gate 01 asks two text questions and four scale questions.
First the text. Who exactly is the avatar? Specific. Not "small business owners" — "solo CPAs in their first twenty-four months of practice, billing under seven thousand a month, ages thirty-two to forty-five, post-Big-Four."
And what is the specific pain — in their words, not yours? Quote them. If you cannot quote them, you have not talked to them yet.
If you used Pain Discovery, those fields are already populated from your lead card. You just review and refine.
Then four scales, one to ten. Purchasing power — can they actually pay? Market trajectory — growing, flat, or shrinking? Easy to reach — can you find them? And pain intensity — is this a top-three problem for them right now?
Each scale also has three help panels you can click open. Examples — good versus vague, with side-by-side comparisons. Sharpen this — three pointed questions that test whether your answer is real or hypothesis. And Verify externally — deep-links to Reddit, Google, YouTube, Quora, and others, pre-filled with keywords from your avatar text.
And — only on this gate — there's a Sharpen with AI button. Click it, it sends your answer to Claude Sonnet 4.6 for a structured critique. Specificity score, weakest element, and a sharper rewrite you can insert with one click.
[B-ROLL: click 'Sharpen with AI' on screen, show the score and rewrite appearing]
The verdict adds your four scale scores out of forty. Above thirty-two — GO, hungry crowd confirmed. Twenty-four to thirty-one — REWORK, workable but at least one dimension is weak, and the verdict tells you exactly which one. Below twenty-four — NO, wrong market. The widget will not let you proceed forward on a fundamentally wrong avatar choice.
Gate 02 — Idea or No Idea
"If no one is doing it, that's usually a sign no one wants it. Competition validates demand. Absence of competition is rarely a moat — it's usually a graveyard."
Gate 02 is the filter.
It asks three questions. State the offer in one sentence using the format: "I help [avatar] get [outcome] in [timeframe] without [common objection]." If you can't fit it in one sentence, the offer is unclear.
What's the competitive reality? Crowded with successful operators — best signal. Some competitors, mostly mediocre — strong signal. Almost no competition — caution. Or "I will be first" — almost always wrong.
And the hundred-dollar today test. Would ten of these people pay you a hundred dollars right now for a janky version one? Can you name the ten people specifically? If yes — GO signal. If you'd have to find them — REWORK. If no — NO.
This gate kills more ideas than any other. It catches operators who fell in love with their own concept but have zero proximity to actual buyers.
Gate 03 — Profitable Problem
"Every problem is not a profitable problem. The best businesses solve problems the customer pays you to keep solving."
Gate 03 confirms the problem itself. State it precisely. How often does it recur? Daily, monthly, quarterly, or once?
Recurring pain equals recurring revenue. Daily or weekly is best — that supports a continuity offer. Once-in-a-lifetime project pain is the weakest, because every customer is a re-acquisition.
What's the cost of NOT solving it? High — losing money, customers, status. Moderate — friction and frustration. Low — minor inconvenience.
"Price is set by the cost of the problem, not the cost of the solution."
Low cost of inaction means hard to monetize. The verdict will mark that as a NO and tell you to either reframe to a higher-cost angle or pick a different problem.
And finally — what do they currently do to solve it? Or fail to? Because the status quo IS the competition.
Gate 04 — Grand Slam Offer
"Value equals dream outcome times perceived likelihood, divided by time delay times effort and sacrifice. The numerator is what they want. The denominator is what they pay in pain. Move both."
Gate 04 is Hormozi's Value Equation. Seven inputs.
Dream outcome — what's the explicit, measurable transformation? And rate how compelling it is, one to ten.
Perceived likelihood — what's your proof this works? Case studies, testimonials, your own results. Then rate how believable it is through skeptical buyer eyes.
Time delay — how fast does the customer feel results? Within twenty-four hours, within a week, within thirty days, or longer?
Effort and sacrifice — done-for-you, done-with-you, DIY with templates, or self-paced with no human contact?
And the seventh field — added in version two — Named Mechanism.
"A named mechanism is the difference between a ninety-seven dollar product and a four-thousand-nine-hundred-ninety-seven dollar program containing the same content."
Give your method a name. The Retainer Method. The Pulse Protocol. The Four-Lane Framework. Then in one sentence explain why it works when generic approaches fail. This is required. Without a named mechanism, the verdict will block GO.
The widget computes a Value Score out of one hundred using Hormozi's actual formula. Above thirty-five — GO, Grand Slam Offer. Twenty to thirty-four — REWORK, sharpenable, with the verdict naming your weakest lever. Below twenty — NO, the offer will not convert at scale even with great copy.
Gate 04½ — Offer Stack
"The naked core offer is never the offer. The offer is the core PLUS the stack: bonuses that solve the next three problems, a guarantee that flips the risk to you, scarcity that creates a real reason to act now, and a name that makes it sound like a thing."
Gate 04½ is where you actually build the stack. Not score it — build it.
Seven fields. The offer name — "The Ninety-Day Retainer Sprint" beats "my coaching program" by thirty percent on conversion.
Three to five bonuses, each named, each with an outcome, each with a price-anchor. Bonus one: The First-Client Script Library — seven sales scripts that closed real deals — four-hundred-ninety-seven dollar value.
The guarantee type. Hormozi's ladder runs from implied at the bottom to anti-guarantee at the top. The widget pushes you toward conditional — "do X, Y, Z and if no result, double your money back" — because that forces customer accountability and produces dramatic risk reversal.
Then the actual guarantee wording — exact words you'll use on the page.
Scarcity mechanism. Cohort cap. Founding-member price ladder. Bonus expiration. Launch window. Or — and this is a hard NO from the verdict — fake countdown timers and inflated urgency. Cialdini is explicit on this. Scarcity works only when it is structurally true. Fake scarcity gets discovered, and one discovery burns the audience permanently.
And finally the stack value versus the actual price. Cialdini's contrast principle. A four-hundred-ninety-seven dollar price next to no anchor looks expensive. A four-hundred-ninety-seven dollar price next to a five-thousand-nine-hundred-ninety-one dollar stack value looks like a steal.
The verdict checks the ratio. Below three-to-one means the contrast doesn't register — REWORK. Five-to-ten-to-one is the conversion sweet spot.
That's the construction phase. Avatar, Idea, Problem, Offer, Stack. Five gates, all about answering: is there a real market and have you packaged a real solution. Now we move to distribution.
Section 5 — Gates 05 through 06½: Distribution, Copy & Persuasion
Approx. 4 minutes
Gate 05 — Core Four Distribution
"There are four ways to get a stranger to know about you. Warm outreach, cold outreach, warm content, paid ads. That's it. The mistake is picking three at the start. Pick ONE."
Gate 05 forces a single channel choice. Just one.
Warm outreach — best for your first ten customers. Free. Low volume. Cold outreach — best when the avatar is identifiable and reachable. Cheap, skill-intensive. Warm content — compounds over time, slow start. Paid ads — fastest scaling, but requires unit economics first.
Then the volume math. If you need ten customers in ninety days at one percent conversion, you need a thousand conversations. That's twelve a day. Do the math now, before launch.
And — do you know your unit economics? CAC, LTV, payback period. If you pick paid ads without knowing those, the verdict gives you a hard NO. "Paid ads without unit economics equals fire."
Gate 05½ — Dream 100
"You don't need to find a million strangers. You need to find the hundred people who already gathered them."
Gate 05½ is from Brunson's Traffic Secrets. The Dream 100.
List twenty-five specific people, podcasts, newsletters, or groups your avatar already follows. Real handles. Real URLs. Not "fitness influencers" — but "@HybridAthlete on Twitter, two-point-one million followers."
Then pick a strategy. Work your way in by providing value first. Buy your way in via sponsorship and ads. Or partner via joint ventures. Working two strategies on the same person at the same time burns the bridge — pick one.
Write the first-touch script. No pitch. No ask. Gift first. Quote them, share a result, send a resource. Cialdini's reciprocity rule — the gift comes first or the ask is dead.
And declare your weekly outreach volume. Below five contacts a week, the Dream 100 doesn't reach the relationship density needed to produce invitations. The verdict pushes you toward ten to twenty a week.
Gate 06 — Hook, Headline, Body
"You have three seconds. The hook stops the scroll. The headline promises the dream. The body proves you can deliver."
Gate 06 is the copy gate. Four fields.
The hook — first three seconds, what stops the scroll. Callout question. Pattern interrupt. Specific stat.
The headline — the promise. Format: outcome in timeframe without objection.
The body — five-line skeleton. Problem, what's working now, named mechanism, proof, specific CTA.
And the CTA specificity. "Get the five-page Retainer Pricing Calculator" beats "learn more" by fifty percent on conversion.
All four of those textareas have the VOC vault button. Pull from your customer quotes. Use their language. Not yours.
Gate 06½ — Persuasion Architecture
"Copy is downstream of persuasion. Most operators write copy and hope persuasion happens. The reverse is correct."
Gate 06½ is the largest single gate. Eight inputs. This is where most operators discover their copy was beautiful and their persuasion was empty.
First — the Big Domino. Brunson's question. If you can make your prospect believe ONE thing is true, all other objections become irrelevant. State that one belief.
Then the False Belief Audit. Three false beliefs blocking the sale. One about the vehicle — "retainer pricing only works for big firms." One about themselves — "I'm too new to charge that much." And one about external factors — "my market is too price-sensitive."
Then the reciprocity gift. The actual lead magnet. Specific, useful, immediate. Not "a free guide" — "The Retainer Pricing Calculator. Three-tier model with anchor logic, plus five sample proposals that closed real two-thousand to five-thousand a month deals. PDF plus Notion template. Seven minutes to use."
Then the Cialdini five-lever audit. Reciprocity strength. Social proof density. Authority. Unity language — does your copy use "we" and "our kind"? Consistency mechanism — what micro-yes do you secure before the macro-yes?
The verdict computes a Cialdini Score out of ten. Below six — REWORK with the weakest two levers named. Strong launches activate five or more visibly on the offer page.
Bottom line: copy without persuasion architecture is decoration. The architecture decides the conversion rate.
Section 6 — Gates 07 & 08: Deploy & Iterate
Approx. 3 minutes
Gate 07 — Deploy
"Done beats perfect every single time. The launch you do not run cannot teach you anything. The launch that embarrasses you in twelve months is the right launch."
Gate 07 is the ship gate. Five locks.
The beta launch date — specific calendar date, thirty days out or less. Pick a Friday. Tell another operator. Make it expensive to slip.
The beta cohort size. Five to ten founding members is best for first launch. Ten over-served founding members produce ten times the testimonial density of fifty mediocre members.
The beta price. The widget warns you about the Muddled Middle — five hundred to nine hundred dollars. Too expensive for impulse, too cheap for premium. Drop to four-ninety-seven or raise to nine-ninety-seven and above.
The kill rule. What happens if you don't hit the number? Less than five paid in fourteen days equals pivot offer angle. That's the operating default. The widget will REWORK you if you say "I'll keep going regardless." That's not strategy — that's sunk-cost grinding.
And the four minimum tools. A way to capture leads. A way to take payment. A way to deliver. A way to measure. Anything less than three of those, the verdict gives a hard NO.
Gate 08 — Iterate
"Volume forgives mistakes. The operator who has a hundred sales conversations learns more than the operator who has five perfect ones."
Gate 08 is iteration. Six fields.
How many at-bats? Iterating on fewer than ten conversations is iterating on noise. Twenty to thirty is the minimum threshold for signal.
What's the dominant pattern from real customer data? Not what you think — what they're actually telling you.
Which Value Equation lever do you adjust? One per cycle. Multiple changes at once equals rebuild, not iterate.
Then two diagnostics from Eugene Schwartz. Awareness stage — where is the market relative to the solution? Unaware, problem-aware, solution-aware, product-aware, or most-aware? Each stage demands different copy. A Stage 1 audience needs the problem named. A Stage 5 audience needs a new mechanism.
Market sophistication — how worn-out are the claims in this niche? Stage 1, you can make direct claims. Stage 4, mechanisms are saturated and you need a brand-new one. Stage 5, every mechanism has been heard and you have to lead with identity and story.
Most copy fails because it's written for the wrong stage. The widget catches that and tells you to combine your lever change with a mechanism rename if your market sophistication is at three or higher.
And finally — refund interview discipline.
"The refund call is the single most valuable sales call you will ever take."
Five questions. What did you hope this would do for you? What part caused you to step back? Was the issue hook, audience, offer, onboarding, or delivery? What would have changed your mind? And — would you refer someone else?
If you process refunds silently, the widget marks you REWORK. Refunds are the highest-signal data in the business. Do not throw them away.
Section 7 — Gates 09 through 11: Pivot, Scale, Compound
Approx. 4 minutes
Gate 09 — Pivot or Hold
"Three things can be wrong: the offer, the audience, or the hook. They look identical from the outside. The diagnostic is in the data."
Gate 09 is the pivot diagnostic. Three funnel checks.
Click-through rate on your hooks. Below baseline — that's a hook problem. Rewrite ten new hooks. Test each at minimum a hundred impressions.
Opt-in rate of clickers. Below baseline — that's an audience problem. The wrong people are clicking. Tighten your messaging to repel non-buyers.
Refund and retention rate. Refunds above ten percent or negative NPS — that's an offer problem. Do NOT scale a leaky bucket. Volume just produces refunds and reputation damage.
This gate prevents the most common founder failure — "more leads will fix it." If your offer's broken, more leads compound the breakage.
Gate 10 — Scale
"You scale what works. You don't scale what might work. Scaling before the signal is gambling. Scaling after is math."
Gate 10. Three checks.
Do you have the scale signal? Ten-plus customers from one channel, known unit economics, six-plus months of retention data. Anything less and you're gambling, not scaling.
Which scale lever? Three options — and most operators get this wrong.
Raise price first. Highest leverage. A ten percent price increase produces roughly fifty percent profit increase.
Increase retention. Second-highest. Reducing churn by twenty percent doubles LTV.
Increase volume. Third lever. Most expensive. Use only when price and retention are maxed.
Most operators reach for volume first. The widget will REWORK that and tell you to test a price increase first.
And — name the bottleneck. Theory of Constraints — there's one bottleneck at a time. Lead gen, sales, delivery, retention. Name it. Fix it. Move to the next.
Gate 11 — Repeat & Compound
"One offer to one audience is a business. Two offers to the same audience is a customer base. Three offers to the same audience is a moat."
Gate 11 is the largest gate at the back. Ten fields.
First — what's the next problem your existing customers will pay you to solve? Ask twenty customers "what's the next thing you would buy from me?" Build that.
Then the compound move. New offer, same audience, same channel — best play. Same offer, adjacent audience — second-best. Same offer, same audience, new channel — third option. New business entirely — almost always wrong.
Have you maxed out the current offer? If you say "I'm bored," the verdict gives you a hard NO. Boredom is not strategy. Boredom signals you've automated the wrong things or stopped talking to customers.
Then the Value Ladder. Five named rungs.
Rung one — the Bait. Free lead magnet. Named, valuable, immediate.
Rung two — the Tripwire. Seven to ninety-seven dollar entry offer. Converts a lead into a buyer.
Rung three — the Core Offer. Two-ninety-seven to one-thousand-nine-hundred-ninety-seven dollar Grand Slam.
Rung four — Continuity. Recurring monthly offer. Skool community, software subscription, monthly coaching.
Rung five — High-Ticket. Five-thousand to fifty-thousand DFY tier. Eighty percent of operator profit lives here.
If you have fewer than three rungs, the widget marks you REWORK. "A single offer is a product. A ladder is a business."
Continuity health. What percentage of customers are on a recurring offer? Below twenty percent means you haven't built continuity yet. Above sixty percent means you have a real moat.
And affiliate motion. Have you turned customers into affiliates? Ten customer-affiliates each bringing five clients equals fifty new customers at zero acquisition cost.
This is where the widget moves you from operator to compound machine.
Section 8 — The Brief, the Close, & Call to Action
Approx. 2 minutes
[GRAPHIC: show the printable brief, pages flipping or scrolling]
After all sixteen gates, you land on the Brief.
One page. Print it, tape it to your wall, send it to your accountability partner. Every decision you made, every verdict you earned, every piece of customer evidence you imported — all in one document.
It includes the Pain Discovery section if you used it. Top three customer quotes. Avatar. Idea. Problem. Offer with the Value Equation. The Grand Slam Stack. Distribution, Dream 100, Copy. The Persuasion Architecture audit. The Launch plan. And — if you got that far — the iterate, scale, and compound sections including your full value ladder.
And every gate has a verdict pill at the top — green for GO, deep red for NO, gold for REWORK. So you can see at a glance where the holes still are.
You can export the whole thing as JSON. You can print it. You can share it.
"You don't have a thinking problem. You have a doing problem. The next document is not the answer. The next paying customer is."
[CAMERA: lean in, direct address. Hold final beats.]
Here's the truth about the widget.
It will not tell you what to build. It will tell you whether what you're already thinking about is going to survive contact with the market — and if not, exactly which gate is going to kill it.
Sixteen gates. Roughly seventy-three input fields. Three verdicts. Built on Hormozi for offer construction. Brunson for the value ladder and Dream 100. Kennedy for direct response and risk reversal. Cialdini for the seven principles of influence. Schwartz for awareness and sophistication staging. And the operator's discipline that ties it all together — RISER Captain's Logic.
If you walk all sixteen gates and end up at GO, you have something most operators never have. A decision document built on evidence, not enthusiasm.
And if you end up at NO before Gate Seven — that's the win, too. Because that's the ninety days you didn't waste.
[PAUSE: 2 seconds. Then close.]
Open the widget. Pick an idea. Walk the gates. See where you land.
That's the work.
[END]
Appendix — Quick Reference
All 16 Gates at a Glance
The Three Verdicts
GO — proceed; here's the next concrete action.
NO — do not proceed; here's the specific reason your idea fails this gate.
REWORK — close, but here's what to sharpen first.
Source Lineage
Alex Hormozi — $100M Offers, $100M Leads, Acquisition.com operating system
Russell Brunson — DotCom Secrets, Expert Secrets, Traffic Secrets
Dan Kennedy — No B.S. Direct Marketing, risk reversal, herd-building
Robert Cialdini — Influence (the 7 principles), Pre-Suasion
Eugene Schwartz — Breakthrough Advertising — awareness + sophistication staging
RISER Captain's Logic — the operating discipline that synthesizes all of the above into one decision engine.
Gate
Name
What it Does
00
Start
Intro
00½
Pain Discovery
Import VOC research (PainOnSocial, interviews)
01
Hungry Avatar
Score the market on 4 dimensions
02
Idea / No Idea
Filter for competitive reality + proximity to demand
03
Profitable Problem
Confirm pain + frequency + cost of inaction
04
Grand Slam Offer
Score the Value Equation + named mechanism
04½
Offer Stack
Build bonuses, guarantee, scarcity, naming
05
Core Four
Pick one distribution channel
05½
Dream 100
Name 25 people who own your audience
06
Hook / Body
Write hook, headline, body, CTA
06½
Persuasion
Big Domino + false beliefs + Cialdini audit
07
Deploy
Lock date, cohort, price, kill rule, tools
08
Iterate
Awareness stage + lever + refund interviews
09
Pivot or Hold
Diagnose hook, audience, or offer failure
10
Scale
Pick price, retention, or volume as lever
11
Repeat
Build value ladder + continuity + affiliate motion
12
Brief
One-page printable summary

Original gate catalogue — native table 1

Gate	Name	What it Does
00	Start	Intro
00½	Pain Discovery	Import VOC research (PainOnSocial, interviews)
01	Hungry Avatar	Score the market on 4 dimensions
02	Idea / No Idea	Filter for competitive reality + proximity to demand
03	Profitable Problem	Confirm pain + frequency + cost of inaction
04	Grand Slam Offer	Score the Value Equation + named mechanism
04½	Offer Stack	Build bonuses, guarantee, scarcity, naming
05	Core Four	Pick one distribution channel
05½	Dream 100	Name 25 people who own your audience
06	Hook / Body	Write hook, headline, body, CTA
06½	Persuasion	Big Domino + false beliefs + Cialdini audit
07	Deploy	Lock date, cohort, price, kill rule, tools
08	Iterate	Awareness stage + lever + refund interviews
09	Pivot or Hold	Diagnose hook, audience, or offer failure
10	Scale	Pick price, retention, or volume as lever
11	Repeat	Build value ladder + continuity + affiliate motion
12	Brief	One-page printable summary

Assigned source documents: RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx — source 1 ·

Design complete offers from existing assets

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

Video placeholder

Record after checking the component examples and current versions. Section scripts and original supporting data follow.

Curriculum outline

Stack or unbundle for a specific buyer
Build an asset inventory that reflects actual utility
Five stack types and their worked examples
Four ways to unbundle without withholding the promised outcome
Pricing: distinguish outcome value, component comparisons and costs
Name the transformation and explain the mechanism
Check whether the new offer displaces useful existing sales
Launch in stages and test the access path
Six performance metrics with explicit cohorts and windows
Retire or revise without breaking customer commitments
Use the priority map as a hypothesis queue
Store the decision and review data without confusing ratios
Operating checklist and practical exercise
Worked contribution exercise: test whether revenue is additive

Stack or unbundle for a specific buyer

Stacking combines existing assets into a coherent solution; unbundling extracts a component that can solve a narrower problem on its own. Choose stacking when no existing offer covers the buyer’s complete need. Choose unbundling when the buyer needs one useful part, has less time or budget, or is not ready for the full programme. Both can confuse the offer wall or replace an existing sale unless their scope is clear.

Existing content is a starting asset, not proof of ownership, usability or buyer validation. Inspect rights, accuracy, prerequisites, delivery and support before packaging it. The source says creation and selling costs are approximately zero. In practice, curation, updating, positioning, access setup, promotion and support still consume resources.

The printed revenue-manufacturing equation adds money to a buyer count, so it is dimensionally invalid. For a defined period, estimate new-offer contribution after variable costs, then subtract displaced contribution from existing offers and additional fixed launch costs. Compare against a credible baseline. A buyer who would otherwise buy nothing differs from one who would have bought an existing higher-contribution offer. This is a counterfactual to investigate, not an assumption that every new sale is additive.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Original source data for this teaching point — uncorrected source examples retained

Hormozi's Revenue Manufacturing PrincipleThe cost of creating an offer bundle from existing IP is approximately zero. The cost of positioning and selling it is approximately zero if you have an existing list. The only constraint is strategic clarity — knowing which components to combine, why they belong together, and which buyer they serve. This SOP is the strategic clarity engine.

The Distinction That MattersStacking and unbundling are NOT discounting. They are not sales, bundles created to clear inventory, or promotional packages. They are permanent offers designed to serve specific buyer profiles that are currently under-served by your existing offer wall. Every bundle must have a reason to exist beyond 'we put these together' — it must have a specific avatar, a specific problem, and a specific transformation.

Operation	Definition	When to Use It	What It Produces	Primary Risk
STACKING	Combining multiple existing IP components into a new offer that commands a premium price as a curated solution	When you identify a buyer profile whose complete need is served by a specific combination of your existing components, but no single offer currently addresses their full problem	A new higher-ticket offer serving a specific avatar, with higher perceived value than any individual component	Cannibalization of existing offers if differentiation is unclear
UNBUNDLING	Extracting one component from an existing offer and selling it as a standalone lower-ticket product	When one component of a larger offer has standalone utility for a buyer who does not need the full offer, or when a component can serve as a lower-friction entry point to the full offer	A new lower-ticket offer serving buyers who are price-sensitive, time-constrained, or in an earlier stage — plus a new entry point to the full offer	Cannibalization of the full offer if the unbundled component is too close to the full offer's core promise

The Revenue Manufacturing EquationNew Stack Revenue = (Bundle Price − Sum of Component Prices) × Buyers + Net New Buyers Attracted by Bundle Positioning. New Unbundle Revenue = Unbundle Price × Buyers Who Would Not Have Bought the Full Offer. Both equations should produce positive numbers. If they do not — the bundle or unbundle is not financially justified.

Build an asset inventory that reflects actual utility

Inventory six asset classes. A full track covers a complete transformation arc; a course delivers a defined outcome; a framework supplies a method; a template or tool supports execution; a workshop shows live application; a reference SOP documents a repeatable process. Tracks often combine well but separate less cleanly, while courses, tools, workshops and SOPs can be strong standalone candidates if prerequisites are included.

Record ID, name, class, outcome, best-fit buyer, current offer, standalone utility from one to ten, and stacking/unbundling suitability from one to five. Ten for standalone utility means usable without other RISER content. These are editorial ratings that need evidence; they are not statistically calibrated scores.

The five source examples are RN-006 Market Gap Detection (utility9, stack5, unbundle4), RN-015 Hook Engineering (9/5/5), RN-025 Sales Page Architecture (9/4/5), RN-FST Fulfilment Stress Test (8/3/5), and RN-T06 Traffic and Conversion track (7/4/2). Their buyers respectively need a niche, better hooks, a sales page, delivery validation or paid-traffic infrastructure. Preserve those source identities, but match documents by title because their legacy course numbers differ from the Master Catalogue and current twelve-course map.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Named component and dependency documents: RISER-Problems-Create-Markets-SOP.docx · RISER-Hook-Engineering-Attention-Engineering-SOP.docx · RISER-Sales-Page-Architecture-SOP.docx · RISER-Fulfilment-Stress-Test-SOP.docx

These document identities were located in the inventory. Their current access, versions and complete methods still need verification; a title match does not certify the underlying procedure.

Original source data for this teaching point — uncorrected source examples retained

Asset Class	Definition	Examples from a 55-Course Catalog	Stacking Potential	Unbundling Potential
Full Track	A complete sequence of courses serving one transformation arc	Track 1 (Operator Foundation), Track 2 (Find Your Market), Track 6 (Traffic & Conversion)	High — can be stacked with other tracks for a specific avatar	Low — individual courses unbundle more cleanly than full tracks
Individual Course	A single course with a defined outcome and a self-contained methodology	Course 6 (Market Gap Detection), Course 15 (Hook Engineering), Course 29 (Paid Ads Foundations)	High — individual courses are the primary building block of all bundles	High — strong courses with specific standalone utility are prime unbundle candidates
Framework or Methodology	A named, proprietary framework that exists as a tool within a course	The 6-Score Monetisation Filter, The PASTOR Copy Framework, The Value Equation Audit	Medium — frameworks can anchor a bundle's mechanism and name	Medium — frameworks can become standalone audit tools or workshops
Template or Tool	A file, calculator, swipe copy, or interactive tool delivered as part of a course	The 14-Day Email Sequence Template, The Offer Stack Slide Template, The Buyer Language Mining Database	Medium — templates become high-value bonuses in bundles	High — templates at $7–$47 are powerful tripwires and lead magnets
Workshop or Recording	A live session, intensive, or Q&A recording from a past cohort or programme	Live implementation workshop recordings, Hot Seat session recordings, Case study breakdowns	Medium — recordings add social proof depth to bundles	High — standalone workshop recordings at $27–$97 are strong entry-point products
SOP or Reference Document	A documented standard operating procedure that stands alone as a deliverable	The Beta Testing Methodology SOP, The Forensic Audit Loop SOP, The Negative Avatar SOP	High — SOP collections create premium reference bundle value	High — individual SOPs as standalone products at $17–$47

Asset ID	Asset Name	Asset Class	Primary Outcome Delivered	Avatar Best Served	Standalone Utility (1–10)	Current Offer It Lives In	Stacking Score (1–5)	Unbundle Score (1–5)
RN-006	Course 6: Market Gap Detection	Individual Course	Validated niche identification using AI-driven gap detection	Pre-launch entrepreneur with no validated niche	9	Track 2 / RISER Full System	5	4
RN-015	Course 15: Hook Engineering	Individual Course	Scroll-stopping hooks and high-retention content openings	Content creator or marketer needing better hooks	9	Track 4 / RISER Full System	5	5
RN-025	Course 25: Sales Page Architecture	Individual Course	High-converting sales page structure using proven frameworks	Operator with an offer who cannot convert traffic	9	Track 5 / RISER Full System	4	5
RN-FST	Fulfilment Stress Test SOP	SOP Document	Pre-scale delivery infrastructure validation system	Operator about to run first paid campaign or JV launch	8	Standalone SOP Series	3	5
RN-T06	Track 6: Traffic & Conversion (Courses 28-32)	Full Track	Complete email + paid ads + retargeting + tracking system	Operator with proven organic offer ready for paid traffic	7	RISER Full System	4	2
[Add all assets]

Scoring GuideStandalone Utility (1–10): How useful is this asset to someone who has no other RISER content? 10 = completely self-contained and immediately applicable. 1 = requires other courses to be useful. Stacking Score (1–5): How readily does this asset combine with others into a coherent bundle? Unbundle Score (1–5): How strong is this asset as a standalone lower-ticket product?

Five stack types and their worked examples

A Problem Stack solves one named problem completely. The source’s First $10K Offer Builder targets a freelancer with expertise but no productized offer. It combines legacy Courses6,7,10,11,12,13: market gaps, psychographic research, niche validation/storyselling, offer frameworks, outcomes and pricing. Its proposed $597 price is compared with $997-plus elsewhere; the promise is $10,000 in ninety days. Treat the revenue and timing as unverified offer proposals. Check that every required action is supported before making any outcome promise.

An Avatar Stack covers at least three challenges of one buyer context. Agency Owner to Product Business OS targets a three-to-ten-year agency owner with $150,000–$500,000 annual services revenue. Its seven source components are skill mapping, offer frameworks, education assets, content factory, email, data sovereignty and offer ecosystem, labeled C2,11,22,23,28,33,40. The proposed $797 versus $1,397-plus comparison and $10,000-monthly-within-six-months transition are scenarios needing substantiation, not expected results.

A Stage Stack defines entry and exit conditions. The $0 to First $10K OS targets a beginner with expertise but no list, offer, infrastructure or knowledge-business revenue. It combines legacy Tracks1–2 and Courses11–12. The source proposes $497 versus $897-plus, a validated offer, five hundred subscribers and $10,000 within ninety days. Teach clear prerequisites and deliverables; validate the commercial comparison and avoid guaranteeing those numbers.

A Crisis Stack narrows the scope for urgent relief, with the source preferring seven-to-fourteen days and a thirty-day maximum. The $297 14-Day Pipeline Rescue combines C15 hooks, C22 education assets and C28 email, compared with $597-plus. Its buyer has recently lost pipeline. Teach the concrete sequence of hook revision, lead-magnet work and email reactivation without promising the calendar will refill in fourteen days.

An Upgrade Stack extends a base offer and states what the buyer must already have. Paid Traffic Ignition uses C29–32 paid ads, creative testing, retargeting and tracking, proposed at $697 versus $997. The source specifies organic validation, two-percent cold and ten-percent warm conversion, and a sixty-day profitable-traffic promise. Those are source thresholds and claims, not universal readiness tests. Review actual margins, acquisition costs, tracking and delivery before adding paid reach.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Named component and dependency documents: RISER-Problems-Create-Markets-SOP.docx · RISER-Psychographic-DNA-SOP.docx · RISER-Niche-Validation-StorySelling-SOP.docx · RISER-Skill-Experience-Mapping-SOP.docx · RISER-Email-Fundamentals-SOP.docx · RISER-Data-Sovereignty-SOP.docx · RISER-Offer-Ecosystem-Backend-Monetisation-SOP.docx · RISER-Hook-Engineering-Attention-Engineering-SOP.docx · RISER-Paid-Ads-Foundations-SOP.docx · RISER-Omni-Channel-Retargeting-SOP.docx · RISER-Server-Side-Tracking-SOP.docx

These document identities were located in the inventory. Their current access, versions and complete methods still need verification; a title match does not certify the underlying procedure.

Original source data for this teaching point — uncorrected source examples retained

PHASE 1The Stack Design FrameworkFive types of bundles — each serving a different strategic purpose

Problem Stack Design RuleA Problem Stack must solve exactly one problem — completely. If the buyer needs anything else to achieve the stated result, the stack is incomplete and will generate support tickets and refund requests. The test: can a buyer who purchases only this stack and no other RISER content achieve the promised transformation? If no — add the missing component or adjust the promise.

WORKED EXAMPLE: RISER NATIONThe First $10K Offer BuilderPROBLEM STACK — Type 1

ForA freelancer or service provider who has expertise but no productised offer. Has never made money from a digital product or programme.

Core promiseGo from expertise to a validated, priced, positioned offer that has generated at least $10K in its first 90 days.

ComponentsCourse 6 (Market Gap Detection) + Course 7 (Psychographic DNA) + Course 10 (Niche Validation & StorySelling) + Course 11 (Direction Clarity & Offer Frameworks) + Course 12 (Outcomes > Features) + Course 13 (Pricing Psychology). 6 courses. Complete system from niche to priced offer.

Bundle price — vs if bought separately$597 — vs $997+ (if bought inside the Core and Growth bundles) if separate

Avatar Stack Design RuleAn Avatar Stack must address at least three distinct challenges that buyer type faces — not just one. If it addresses one challenge, it is a Problem Stack in disguise. The differentiator is breadth: the Avatar Stack serves the buyer across their entire current context, not just their most urgent problem.

WORKED EXAMPLE: RISER NATIONThe Agency Owner to Product Business OSAVATAR STACK — Type 2

ForAn established agency owner (3–10 years) generating $150K–$500K/year in client service revenue who wants to build a product business to reduce client dependency.

Core promiseBuild a parallel product revenue stream generating $10K/month within 6 months — without sacrificing agency revenue during the transition.

ComponentsCourse 2 (Skill & Experience Mapping) + Course 11 (Offer Frameworks) + Course 22 (TOFU Education Assets) + Course 23 (Content Factory) + Course 28 (Email Fundamentals) + Course 33 (Data Sovereignty) + Course 40 (Offer Ecosystem). 7 courses. Complete transition system.

Bundle price — vs if bought separately$797 — vs $1,397+ if bought across individual tracks if separate

Stage Stack Design RuleA Stage Stack must have clear entry criteria (who should buy this) and clear exit criteria (what the buyer's situation looks like after completing it). Without both, the buyer cannot self-select accurately — and the wrong-stage buyer (Negative Avatar Archetype 03) will purchase and be disappointed.

WORKED EXAMPLE: RISER NATIONThe $0 to First $10K OSSTAGE STACK — Type 3

ForA complete beginner with validated expertise but no business infrastructure, no list, no offer, and no prior revenue from their knowledge.

Core promiseBuild the foundation of a sovereign knowledge business: validated offer, email list of 500+, and first $10K in revenue within 90 days.

ComponentsTrack 1 (Courses 1–5: Operator Foundation) + Track 2 (Courses 6–10: Find Your Market) + Course 11–12 from Track 3. Complete first-revenue sequence (the 'First Revenue Path' from the catalog).

Bundle price — vs if bought separately$497 — vs $897+ across individual tracks if separate

Crisis Stack Design RuleA Crisis Stack must promise a result achievable within 30 days maximum — ideally 7–14 days. If the promised result requires more time, it is not a crisis stack — it is a Problem Stack with urgency copywriting. The distinction is real: a Crisis Stack buyer is under acute time or financial pressure and needs fast relief, not a comprehensive programme.

WORKED EXAMPLE: RISER NATIONThe 14-Day Pipeline RescueCRISIS STACK — Type 4

ForAn operator whose revenue pipeline has dried up in the last 30 days. Urgent need to generate leads and bookings immediately.

Core promiseRebook your calendar in 14 days using a combination of hook engineering, organic outreach, and a re-activated lead magnet.

ComponentsCourse 15 (Hook Engineering) + Course 22 (TOFU Education Assets) + Course 28 (Email Fundamentals). 3 courses. Maximum urgency, minimum complexity.

Bundle price — vs if bought separately$297 — vs $597+ across individual tracks if separate

Upgrade Stack Design RuleAn Upgrade Stack must explicitly reference what the buyer already has and clearly position itself as the acceleration layer — not a replacement. Copy must include: 'If you already have [base offer], this is your next step.' Buyers who purchase an Upgrade Stack without the prerequisite will be disappointed because the stack assumes prior knowledge and prior infrastructure.

WORKED EXAMPLE: RISER NATIONThe Paid Traffic Ignition (For Organic-Validated Operators)UPGRADE STACK — Type 5

ForAn operator who already has a validated organic offer converting at 2%+ cold and 10%+ warm, and is ready to add paid traffic for the first time.

Core promiseBuild a profitable paid traffic system generating predictable leads at a sustainable CAC within 60 days — without the 'learning tax' most operators pay.

ComponentsCourse 29 (Paid Ads Foundations) + Course 30 (Paid Ads Creative Testing) + Course 31 (Omni-Channel Retargeting) + Course 32 (Server-Side Tracking). Complete Track 6 paid acquisition system.

Bundle price — vs if bought separately$697 — vs $997 as part of the Growth track bundle if separate

Four ways to unbundle without withholding the promised outcome

An Entry Point Unbundle creates a useful first transaction. The source suggests $7–$97 and a tangible result within forty-eight to seventy-two hours. Its $47 Hook Engineering Workshop should help a learner produce hooks, then reveal a genuinely separate need for platform or content strategy. The narrow product must remain complete; a later offer should not be required to receive the original promise.

A Specialist Unbundle serves an experienced buyer missing one capability. The source proposes utility8–10, $97–$297 and a $197 Sales Page Architecture masterclass. State its prerequisites: a validated offer and defined buyer. It should deliver the complete narrow method without a required upsell; optional tracking education can address a later need.

A Tool Unbundle extracts a usable calculator, swipe file, database, template or AI tool. Examples are the Offer Stack Slide Template, a fourteen-day email sequence and Buyer Language Mining Database. The source proposes $7–$47, a five-to-ten-minute walkthrough, a $27 template with a seven-minute demo, and fifty-to-two-hundred-plus monthly sales at $17–$27. These are planning examples. Tool format does not guarantee sales or recommendations by search engines or LLMs.

A Workshop Unbundle uses an implementation session, hot seat, Q&A or replay, proposed at $27–$97. The $47 Offer Teardown example critiques five offers. Check participant permissions, usable instruction and current relevance. A twelve-month refresh rule can be an internal review cadence, but usefulness does not expire automatically, and live demonstration is not inherently stronger evidence than every testimonial.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Named component and dependency documents: RISER-Hook-Engineering-Attention-Engineering-SOP.docx · RISER-Sales-Page-Architecture-SOP.docx · RISER-Negative-Avatar-Modelling-SOP.docx

These document identities were located in the inventory. Their current access, versions and complete methods still need verification; a title match does not certify the underlying procedure.

Original source data for this teaching point — uncorrected source examples retained

PHASE 2The Unbundle Decision MatrixWhen to extract, what to extract, and what price to charge

Design Criterion	Requirement	Example
Which component to extract	The one that delivers the fastest, most tangible result — ideally within 48–72 hours of purchase	Course 15 (Hook Engineering) delivers usable hooks within one session. Strong entry-point candidate.
Price range	$7–$97. Must be impulsive-purchase territory for the target avatar.	Hook Engineering Workshop: $47
Relationship to full offer	The entry-point unbundle should create a natural desire for the next tier. It solves one problem and immediately reveals the next problem.	After completing Hook Engineering, the buyer has great hooks but no platform strategy → natural ascension to Course 22 (TOFU Education Assets) or the AI Content Machine bundle.
Copy positioning	Lead with the specific fast win. Do not mention the full offer on the unbundle page. Let the buyer discover it through the ascension sequence.	'Engineer scroll-stopping hooks in one session — without a copywriting background or prior audience.'

Design Criterion	Requirement	Example
Which component to extract	The one with the highest standalone utility score (8–10) for a buyer who already has adjacent expertise	Course 25 (Sales Page Architecture) — an operator who already knows their offer and avatar, just needs a converting sales page.
Price range	$97–$297. Advanced buyers accept higher prices for specific solutions.	Sales Page Architecture Masterclass: $197
Relationship to full offer	The Specialist Unbundle does NOT require the full offer. It is complete on its own for the right buyer. It should not feel like a teaser.	Buyer completes the sales page module and has a finished, converting sales page. No next step required — but an upsell to conversion tracking (Course 32) is appropriate.
Positioning guard	Must explicitly state who it is NOT for: 'This is not for you if you don't yet have a validated offer and a defined avatar — start with [entry point offer] first.'	Prevents wrong-stage buyers (Archetype 03 Too Early) from purchasing.

Design Criterion	Requirement	Example
Which component to extract	Templates, swipe files, calculators, and AI tools that have standalone utility independent of the instructional content that surrounds them	The Offer Stack Slide Template from Course 11. The 14-Day Email Sequence Swipe from Course 28. The Buyer Language Mining Database from the Forensic Audit SOP.
Price range	$7–$47. Tool unbundles are impulse purchases. Price above $47 and the buyer expects instruction with the tool.	Offer Stack Slide Template Pack: $27
Ascension logic	Tool unbundles should include one short instructional video (5–10 min) showing how to use the tool. This video introduces the full course as the deeper dive.	The template pack includes a 7-minute walkthrough video that references Course 11 as 'the full system behind this template.'
Volume potential	Tool unbundles have the highest volume potential of any unbundle type — low price, high relevance, immediate utility. They are also the strongest GEO assets (AI engines recommend them as standalone resources).	Target: 50–200+ sales per month at $17–$27 via organic content and paid amplification.

Design Criterion	Requirement	Example
What to extract	Live implementation workshops, hot seat session recordings, Q&A replays, or masterclass recordings from past cohorts	The 'Live Offer Teardown' session from a past RISER cohort where 5 offers are critiqued and rebuilt in real time.
Price range	$27–$97. Workshop replays should be priced to feel like attending a live event you missed — not like a course module.	Offer Teardown Masterclass Replay: $47
Freshness requirement	Workshop unbundles have a 12-month maximum shelf life before they feel dated. Update annually or retire.	If the workshop referenced 2024 tools or tactics, it must be re-recorded or retired by 2026.
Social proof function	Workshop unbundles double as social proof assets. The recording shows the methodology producing results in real time. This is more persuasive than any written testimonial.	Include at minimum one 'hot seat' segment where a buyer's specific situation is transformed. The before/after of that transformation is the primary conversion mechanism.

Pricing: distinguish outcome value, component comparisons and costs

Start with buyer value, alternatives, willingness and ability to pay, then validate delivery economics. The source’s generic one-to-five-percent-of-outcome heuristic produces $500–$2,500 for a hypothetical $50,000 outcome. It is not a pricing law, and a forecast revenue gain is not money the buyer is guaranteed to earn.

Its stack ranges are Problem$297–$997, Avatar$497–$1,497, Stage$297–$797, Crisis$97–$497 and Upgrade$397–$997. The suggested comparisons are complete-solution value, annual context shift, cost of delaying a stage transition, weekly crisis cost and implementation alternatives. Quantify those costs where possible instead of calling them incalculable or assuming urgency eliminates affordability.

The ratio examples conflict with their own targets. $597/$10,000 is5.97%, outside the stated Problem10–20%; $797/$50,000 is1.594%, outside Avatar5–10%. A $697 upgrade compared with $2,000–$5,000 implementation is13.94–34.85%, not consistently20–40%. Preserve each example and label the inconsistency rather than treating it as validated guidance.

Unbundle progression targets are Entry5–15times price, Specialist20–40% of the full offer, Tool10–20times and Workshop5–10times. The examples are $47→$397 (8.45times), $197/$797 (24.72%), $27→$297 (11times), and $47→$497 (10.57times, outside its target). Later examples change AI Content to$497, the template’s course to$197, and a full track to$497; reconcile versions before presenting a live price.

The source warns against stacks priced$500–$900 while recommending$597,$697 and$797, and against unbundles$50–$95 while presenting nearby psychological price points. These are conflicting opinions, not a universal dead zone. A specialist priced at40% also fails the separate three-times-gap rule. Use a coherent scope and price comparison supported by evidence rather than satisfying incompatible ratios.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Original source data for this teaching point — uncorrected source examples retained

PHASE 3Pricing Architecture for Stacks and UnbundlesThe system for pricing every bundle and unbundle correctly — the first time

The Bundle Pricing FormulaBundle Price = Transformation Value × Buyer's Willingness-to-Pay RatioTransformation Value is what the buyer gets (their outcome in dollar terms). Willingness-to-Pay Ratio is typically 1–5% of the value they receive. A bundle that produces $50K in annual revenue should price between $500 and $2,500.

Stack Type	Price Range	Pricing Logic	Value Ratio Target	Example
Problem Stack	$297–$997	Price to the complete solution. The buyer does not need anything else — that completeness commands a premium over any individual component.	Stack price should be 10–20% of the outcome value the buyer receives	The First $10K Offer Builder at $597 delivers a $10K outcome = 6% of outcome value. Within range.
Avatar Stack	$497–$1,497	Price to the full context shift. The buyer's entire operating situation changes — not just one problem.	Stack price should be 5–10% of the annual revenue upside the transformation enables	The Agency Owner to Product Business OS at $797 for a buyer who generates $50K/year additional product revenue = 1.6% of first-year value. Strong value ratio.
Stage Stack	$297–$797	Price to the stage transition. The buyer moves from Stage A to Stage B — and Stage B is worth substantially more than Stage A.	Compare to cost of staying in Stage A for one more month. Stack price should be below that cost.	$0–$10K stage at $497. Cost of staying at $0 for one more month: incalculable. Decision is easy.
Crisis Stack	$97–$497	Price to urgency. The buyer is in pain now. Remove friction. A crisis buyer who is losing $5K/month needs the solution today — not after evaluating price.	Stack price should be below the weekly cost of the crisis continuing.	14-Day Pipeline Rescue at $297. If the buyer is losing $2K/week, $297 is the easiest purchase decision of their month.
Upgrade Stack	$397–$997	Price to acceleration. The buyer already has momentum — they are buying speed. Premium over the base offer is justified by the acceleration.	Compare to the cost of hiring someone to implement the next phase. Stack price should be 20–40% of that cost.	Paid Traffic Ignition at $697 vs hiring an ads manager for one month at $2,000–$5,000 = 14–35% of alternative. Strong value ratio.

Unbundle Type	Price Range	Pricing Logic	Ascension Price Target	Example
Entry Point	$7–$97	Price for zero friction. The goal is the transaction, not the revenue. Every dollar above $97 increases friction and reduces the likelihood of conversion.	The full offer or the bundle it leads to should be priced at 5–15x the entry-point price, making the ascension feel like a natural investment increase.	Hook Engineering Workshop at $47 leads to the AI Content Machine bundle at $397 (8.5x). Strong ascension ratio.
Specialist	$97–$297	Price for the specific transformation. Specialist buyers have already self-selected as advanced — they accept a higher price for precision.	Specialist unbundle should be 20–40% of the full offer price, creating a clear 'get just what you need vs get everything' decision architecture.	Sales Page Architecture at $197 vs the Growth Track bundle at $797 (24.7%). Clear decision architecture.
Tool	$7–$47	Price for impulse. Tools are bought on the basis of 'I can use this right now.' Every dollar above $47 moves the buyer from impulse to consideration — and consideration loses to inertia.	Tool should lead to a course or workshop priced at 10–20x the tool price. Tool proves the methodology; course teaches the full system.	Offer Stack Slide Template at $27 leads to Course 11 (Direction Clarity & Offer Frameworks) at $297 (11x). Clean ascension.
Workshop	$27–$97	Price for access to an event. Buyers are paying for the experience of attending something, not just content. Below $27 feels like it was not worth producing. Above $97 competes with live event pricing.	Workshop should lead to the full programme at 5–10x the workshop price.	Offer Teardown Masterclass at $47 leads to the Core Offer Track bundle at $497 (10.6x). Excellent ascension ratio.

The Muddled Middle Rule (Applied to Bundles)The same pricing dead zone that applies to standalone MVOs applies to bundles. Avoid bundle prices of $500–$900 for stacks and $50–$95 for unbundles. These ranges require too much deliberation for impulse buyers and too little investment for premium buyers. The math works cleanest at clear psychological price points: $297, $397, $497, $597, $797, $997 for stacks; $7, $17, $27, $47, $97, $197, $297 for unbundles.

Name the transformation and explain the mechanism

Build a concise name from an outcome, optional time implication, optional system/container word and an audience qualifier when useful. The source suggests four-to-seven words and examples such as thirty-day pipeline rescue, first-$10K offer builder and paid-traffic ignition for organic-validated operators. A deadline must describe something you can support, not manufactured urgency.

Write one sentence explaining how the components work together. The source examples use a six-course validation/offer sequence in thirty days, a three-module hook/list/lead-magnet rescue in fourteen days, and a four-course Meta/Google acquisition foundation in sixty days. Those are mechanism illustrations; the claimed RISER validation, profitability and delivery times need proof before becoming sales copy.

Read the name to five appropriate buyers and ask them to explain the intended result and audience. The source requires all five to understand without explanation and labels this a Brunson naming test. Treat it as the document’s small qualitative comprehension exercise, not a verified proprietary score or a predictor of purchase behavior.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Original source data for this teaching point — uncorrected source examples retained

PHASE 4The Naming and Positioning SystemEvery bundle needs a name and a promise that makes it a distinct offer — not a collection

The Brunson Naming TestRead the bundle name to five people who match the target avatar. If all five immediately understand what the bundle is for and who it serves — without explanation — the name is working. If any of the five need clarification, rename it. A bundle name that needs explanation is a liability on the sales page.

Name Component	Function	Options	Example
Time Horizon (optional but powerful)	Creates urgency and sets expectation for speed of result	7-Day, 14-Day, 30-Day, 90-Day, First, Fast, Rapid, Sprint	'30-Day...'
Transformation Descriptor	Describes what specifically changes for the buyer	Revenue, Client Acquisition, Offer, Traffic, Funnel, Pipeline, Content, Email, Visibility	'...Pipeline Rescue'
System or Container Word (optional)	Positions the bundle as a complete system rather than a collection	OS, System, Engine, Blueprint, Accelerator, Machine, Foundation, Ignition	'...Ignition System'
Avatar Qualifier (optional but improves relevance)	Clarifies who specifically benefits	For [Avatar Type], For Operators, For Agency Owners, For Beginners, For [Stage]	'...For Organic-Validated Operators'

Bundle Name	Mechanism Statement	What It Does
The First $10K Offer Builder	A 6-course validation and offer construction sequence that takes you from undifferentiated expertise to a priced, positioned, tested offer in 30 days — using the same AI-driven market gap detection and Forensic Critic positioning that validated RISER Nation's own curriculum.	Names the mechanism (validation and offer construction sequence), specifies the time (30 days), establishes credibility (used by RISER Nation itself), and anchors the transformation (expertise to priced offer).
The 14-Day Pipeline Rescue	A 3-module implementation sprint that restores a dry pipeline in 14 days by engineering scroll-stopping organic hooks, activating a dormant email list, and deploying a rapid lead magnet relaunch.	Names the mechanism (implementation sprint), names the three actions, specifies the outcome (restored pipeline) and time (14 days).
The Paid Traffic Ignition System	A 4-course paid traffic foundation that builds a profitable Meta + Google acquisition system from scratch in 60 days — starting from the creative brief, through server-side tracking, to a retargeting ecosystem that compounds over time.	Names the platforms, the time, the starting point, and the compounding nature of the result.

Check whether the new offer displaces useful existing sales

Ask what the buyer would purchase if this offer did not exist: an existing RISER offer, a competitor or nothing. Use interviews and comparative sales evidence to investigate that alternative. Revenue falling after launch is a signal, not proof of causation; traffic mix, seasonality, stock/access changes and concurrent promotions may explain the difference.

Review six scenarios. The same content at a lower price directly undercuts an offer unless buyer, use case and scope are meaningfully distinct. Similar components, buyer and price may warrant merging or clearer positioning. An unbundle near the full price creates a difficult comparison; the source suggests a three-times gap but its separate within-twenty-five-percent warning is a different condition.

An unbundle with the same core promise can make the larger offer look unnecessary; narrow the actual outcome rather than selling a cheaper label for the same result. Extracting an anchor course can also substitute for the full programme; the source proposes exclusion or a price at least70% of full, which is a hypothesis to test. The same audience at an earlier stage can be a low-conflict entry point if the stage and next step are clear.

The source requires different avatar, stage/problem and price progression in three tests, yet also permits the same avatar at a different stage. Resolve that contradiction through a meaningful distinction in need, readiness or scope; a new demographic label alone is not required or sufficient. Calculate displaced contribution as well as new revenue.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Named component and dependency documents: RISER-Negative-Avatar-Modelling-SOP.docx

These document identities were located in the inventory. Their current access, versions and complete methods still need verification; a title match does not certify the underlying procedure.

Original source data for this teaching point — uncorrected source examples retained

PHASE 5The Cannibalization AuditEnsuring new bundles protect — not undermine — existing offer revenue

The Cannibalization TestAsk: If the new bundle or unbundle did not exist, what would the buyer purchase instead? If the answer is an existing offer — cannibalization is occurring. If the answer is 'nothing' (they would not purchase any RISER product because no existing offer serves their situation) or 'a competitor's product' — the new bundle is creating net new revenue.

Scenario	Cannibalization Risk	Mitigation
New bundle contains the same courses as an existing bundle, at a lower price	Critical — directly undercuts the existing offer	Never create a new bundle that contains a subset of an existing bundle's content at a lower price without clearly differentiating avatar, use case, and positioning. If the differentiation is not clear enough to communicate in one sentence, do not launch the new bundle.
New bundle contains courses from an existing bundle, at a similar price, for a similar avatar	High — buyer must choose one or the other	Audit the avatar differentiation. If both bundles serve the same avatar at the same stage, merge them rather than running both. Two bundles competing for the same buyer create decision paralysis.
Unbundle's price is within 25% of the full offer's price	High — buyer will choose the unbundle and feel they made a savvy decision rather than ascending to the full offer	Ensure the price gap between unbundle and full offer is at least 3x. Below 3x, the buyer rationalises the unbundle as 'enough' and the ascension logic breaks down.
New unbundle's core promise is the same as the full offer's core promise, just positioned as smaller	High — the unbundle repositions the full offer as 'too much'	An unbundle's promise must be narrower than the full offer's promise — not the same promise at a lower price. 'Get your first 10 hooks' is narrower than 'build a complete content engine.' Never position an unbundle as 'a smaller version of the full offer.'
New bundle includes a course that is the primary reason most buyers purchase the full programme	Medium — the bundle becomes a substitute for the full programme	If the 'anchor course' (the one buyers cite most often as their purchase driver) is in a new bundle, the bundle will cannibalize the full programme. Either exclude the anchor course from the bundle or price the bundle at 70%+ of the full programme price.
New bundle or unbundle serves the same avatar but at a different stage	Low — serves buyers who are not yet ready for the full offer	Document the stage differentiation clearly. Add 'This is the prerequisite to [full offer name]' to the bundle page. This frames the relationship correctly and creates ascension intent from the first purchase.

Launch in stages and test the access path

The seven-step source sequence begins seven days before the soft launch with five relevant existing buyers reviewing name, mechanism and price, seeking four expressions of interest. This is feedback, not four proven future sales. Days1–5 prepare a page with hook, problem, mechanism, component stack, truthful proof, actual terms, FAQ and CTA. Link each component to its real asset and substantiate any standalone value.

Before release, test the payment-to-access flow in the appropriate test environment and confirm all included resources can be reached through the product. The source then proposes one plain-text email and a same-day community announcement, followed by a day-seven review of sales, conversion, related-offer performance and feedback. Those are curriculum instructions; this task does not send messages, charge customers or create campaigns.

It suggests public promotion from day8 when evidence supports it, with offer-wall placement, useful content and potentially retargeting. The warm conversion target here is1–3%, while the later metrics use0.5–2%; below0.5% is a no-paid-scale signal in this section. Record which denominator and window you use rather than silently combining them.

The simplified unbundle launch has five steps: prepare a clear product/access page; demonstrate the narrow outcome in useful long-form content; introduce it through the appropriate existing channel; observe content/email conversion, feedback and possible displacement for fourteen days; then decide whether to improve positioning, create follow-up material or expand. No-sale results need adequate exposure and diagnosis before paid spending or abandonment.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Named component and dependency documents: RISER-Sales-Page-Architecture-SOP.docx

These document identities were located in the inventory. Their current access, versions and complete methods still need verification; a title match does not certify the underlying procedure.

Original source data for this teaching point — uncorrected source examples retained

PHASE 6The Launch ProtocolBringing a new bundle or unbundle to market without disrupting existing revenue

Step	Timing	Action	Goal
1. Internal validation	7 days before soft launch	Share the bundle name, mechanism statement, and price with 5 existing buyers who match the target avatar. Ask: 'If you didn't already own the components, would you buy this at this price?' Minimum 4 of 5 'yes' answers required before proceeding.	Validate positioning before writing a single line of sales copy.
2. Sales page build	Days 1–5	Build the bundle sales page using the existing sales page SOP framework: hook, problem, mechanism, stack reveal, social proof, guarantee, FAQ, CTA. Note: the stack reveal for a bundle shows each component with its standalone value assigned.	Live sales page with tracking pixel installed and all UTM parameters set.
3. Bundle access setup	Before soft launch	Ensure all components of the bundle are accessible via a single Kajabi product or equivalent. Test the purchase-to-access flow with a test purchase.	Zero-friction access experience from purchase confirmation to first content.
4. Soft launch email to existing list	Day 1 of soft launch	Single plain-text email to the entire list: introduce the bundle by name, describe the avatar it serves, state the price, and link to the sales page. No launch sequence — one email, honest framing.	Validate warm conversion rate. Target: 1–3% of list. Collect first testimonials.
5. Community announcement	Same day as soft launch email	Post in the community: same information, different format. Invite questions in the thread. The Q&A thread becomes FAQ content for the sales page.	Additional sales. FAQ data. Community engagement signal on the new positioning.
6. Performance review	7 days after soft launch	Review: total sales, conversion rate from email, conversion rate from community, any cannibalization evidence (did sales of existing related offers drop?), early buyer feedback.	Go/No-Go decision for public launch. If soft launch conversion is below 0.5% of list — do not scale to paid traffic.
7. Public launch (if soft launch passes)	Day 8+	Add bundle to offer wall. Create organic content referencing the bundle. Begin paid retargeting to visitors. If strong social proof is available from soft launch buyers: build a full launch sequence.	Scale from warm-audience validation to broader market.

Six performance metrics with explicit cohorts and windows

Track new contribution/revenue, warm-list conversion, cold-page conversion, completion, ascension and displacement of related offers. Keep list size, delivered recipients, page visitors and buyers as distinct denominators. The source’s healthy “100% additive” premise must be investigated; do not infer it merely because one revenue line increased.

The table proposes warning levels of a10–15% related-offer drop within30days and a25% pause threshold; warm conversion0.5–2% with below0.3% warning and zero sales after1,000-plus contacts as a diagnostic trigger; cold conversion0.8–2.5%, below0.5% warning after200visitors and below0.3% after a diagnostic as a kill-assessment trigger. These are source heuristics, not universally decisive thresholds.

Completion targets are45%-plus completing every component, warning below30% and stronger concern below20%. Ascension targets are8–15% within60days, warning below5% at60days and concern below3% at90days. The checklist also asks for a below5% review at30days; that is an earlier check, not the same cohort result. The source suggests CRM, email analytics, course completion data and GA4/sales-platform reports; use actual accessible data and lawful tracking configuration.

At300visitors a single sale is0.333%, so a0.3% threshold is highly sensitive to one event. Consider uncertainty, acquisition cost and contribution before deciding. Completion is also not identical to benefit received; review whether the learner needed every module and whether the promised outcome occurred.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Original source data for this teaching point — uncorrected source examples retained

PHASE 7Performance Monitoring and RetirementMeasuring whether bundles are working — and killing them when they are not

Metric	Target (Healthy)	Warning Signal	Kill Threshold	Measurement Tool
Net new revenue (not cannibalized)	100% of bundle revenue is additive — no drop in related existing offer revenue	Related offer revenue drops 10–15% in 30 days following bundle launch	Related offer revenue drops 25%+ — bundle is cannibalizing, not adding	CRM revenue report, segmented by offer
Conversion rate from list (soft launch)	0.5–2% of email list for warm launch	Below 0.3% after full email	Zero sales from 1,000+ warm contacts after one email and one community post	Email platform analytics + CRM
Conversion rate from cold traffic (post-public launch)	0.8–2.5% of sales page visitors	Below 0.5% after 200+ visitors post-diagnostic	Below 0.3% after full Pre-Kill Diagnostic applied — trigger Kill Assessment	GA4 + sales platform
Completion rate of bundle components	45%+ complete all included components	Below 30% — bundle scope may be too broad	Below 20% — buyers are not engaging with the full stack; either the components are irrelevant or the promise was too broad	Course platform completion analytics
Ascension rate to next tier	8–15% of bundle buyers ascend to the next offer within 60 days	Below 5% at 60 days	Below 3% at 90 days — ascension sequence is broken or the next offer is wrong	CRM pipeline report
Cannibalization score (daily)	0% — no drop in existing related offer revenue	Any drop in related offer revenue in first 30 days requires investigation	25%+ drop in a directly related offer's revenue in first 30 days — pause the bundle and audit	CRM comparative revenue report

Retire or revise without breaking customer commitments

The source names four retirement triggers. Sustained cold conversion below0.3% after300-plus visitors, a diagnostic and an iteration leads to a proposed Kill Assessment. The linked Product Kill Criteria document uses fifteen dimensions scored zero to four, with a maximum of sixty; its below-twenty-five rule must be read with its conditional decision panels, not substituted for the separate seventy-five-point monthly scorecard. A related-offer decline exceeding20% for60days with other causes excluded prompts differentiation review; this differs from the earlier25%/30-day pause signal.

If a core component is retired, the source proposes updating the bundle within30days or retiring it when its main value disappears. Preserve previously agreed access and notify affected buyers through an authorized process. If the market or mechanism changes, review buyer needs and credibility rather than keeping obsolete claims in a live offer.

The located Product Kill Criteria companion identifies six pre-kill diagnostic domains: traffic volume, traffic/page awareness fit, headline testing, email-sequence completion, guarantee design and stack presentation. These are alternative explanations to investigate. Its two-hundred/three-hundred-visitor thresholds, test windows and guarantee recommendations are source proposals, not automatic statistical confidence or permission to spend. Use the complete linked method before making an operational decision.

Archive versions, copy, decisions and necessary records with appropriate access controls. Retirement does not mean silently deleting evidence, exposing buyer information or removing paid access contrary to commitments. Product Kill Criteria, the Forensic Audit Loop and Product Versioning have prior local companion reviews; their complete conditional procedures, version conflicts and current access still need to be checked for the actual decision.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Named component and dependency documents: RISER-Product-Kill-Criteria-Post-Launch-SOP.docx · RISER-Post-MVO-Forensic-Audit-Loop-SOP.docx · RISER-Product-Versioning-Offer-Changelog-SOP.docx

These document identities were located in the inventory. Their current access, versions and complete methods still need verification; a title match does not certify the underlying procedure.

Original source data for this teaching point — uncorrected source examples retained

Retirement Trigger	Threshold	Retirement Process
Sustained low conversion	Below 0.3% conversion rate from cold traffic after full Pre-Kill Diagnostic applied across 300+ visitors and one full iteration cycle	Apply the Product Kill Criteria SOP. If the Kill Assessment Scorecard scores below 25, retire the bundle. Archive all copy and buyer data.
Confirmed cannibalization	Related existing offer revenue drops 20%+ sustained for 60+ days with no other market explanation	Pause the bundle immediately. Run the Three Differentiation Tests again. If the positioning cannot be differentiated sufficiently, retire the bundle permanently.
Component IP retired	A core component of the bundle is retired from the main catalog (deprecated course, removed module)	Update the bundle within 30 days. If the retired component was the bundle's primary value driver, retire the bundle and notify existing bundle buyers with access maintenance period.
Market conditions change	The specific avatar or problem the bundle addressed is no longer as relevant due to market shifts, competitor solutions, or technology changes	Quarterly review of all bundle avatars against current market conditions. Apply the Mechanism Freshness Test (from the Forensic Audit Loop SOP). If the bundle's promise is no longer credible, retire and reposition.

Use the priority map as a hypothesis queue

The proposed stack queue is: First$10KOfferBuilder, C6/7/10/11/12/13 at$597 for expertise without a product; PaidTrafficIgnition, C29–32 at$697 for organic-validated operators; AIContentMachine, C22/23/24/35 at$497 for overloaded creators; PipelineRescue, C15/22/28 at$297 for dry pipelines; and MRRFoundation, C14/28/40/41 at$697 for recurring-offer development. These are legacy references and proposed prices, not five newly available current offers.

The unbundle queue is a$47 Hook workshop leading to AIContent$497 or Track4; a$197 SalesPage masterclass leading to Track5$497 or the CoreOffer track; a$27 SlideTemplate leading to C11$197 or OfferBuilder$597; individual$47 SOPs leading to the relevant track or full system; and a$47 live teardown replay leading to appropriate Core/Growth resources. Use the actual document IDs to resolve numbering and price-version conflicts before adding commercial links.

The source calls these ready with zero new creation. Inventory completeness, rights, current accuracy, prerequisites and support capacity must establish that readiness. Rank opportunities by observed buyer need and feasible delivery, not solely by their position in this illustrative queue.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Named component and dependency documents: RISER-Hook-Engineering-Attention-Engineering-SOP.docx · RISER-Sales-Page-Architecture-SOP.docx · RISER-Email-Fundamentals-SOP.docx · RISER-Offer-Ecosystem-Backend-Monetisation-SOP.docx · RISER-Customer-Success-Retention-Systems-SOP.docx

These document identities were located in the inventory. Their current access, versions and complete methods still need verification; a title match does not certify the underlying procedure.

Original source data for this teaching point — uncorrected source examples retained

Priority	Bundle Name	Type	Components	Target Avatar	Estimated Price	Commercial Rationale
1 — Launch First	The First $10K Offer Builder	Problem Stack	Courses 6,7,10,11,12,13	Freelancer/service provider with expertise but no productised offer	$597	Largest underserved avatar in the catalog. No existing offer addresses this exact stage.
2 — Launch Second	The Paid Traffic Ignition System	Upgrade Stack	Courses 29,30,31,32 (Full Track 6)	Organic-validated operator ready for first paid traffic	$697	High-urgency purchase. Buyers at this stage have budget and urgency. Strong separation from the full system.
3 — Launch Third	The AI Content Machine	Problem Stack	Courses 22,23,24,35	Content-overwhelmed operator who needs a production system	$497	Addresses one of the most common avatar pain points. Strong hook-to-mechanism alignment.
4 — Launch Fourth	The 14-Day Pipeline Rescue	Crisis Stack	Courses 15,22,28	Operator with dry pipeline needing immediate lead flow	$297	Urgency-driven purchase. Low price, high intent. Strong entry point to full system.
5 — Seasonal	The MRR Foundation Bundle	Stage Stack	Courses 14,28,40,41	Operator with proven offer ready to build recurring revenue	$697	Recurring revenue focus is highest-priority aspiration across the RISER avatar base.

Priority	Unbundle Name	Type	Source Asset	Target Avatar	Estimated Price	Ascension Path
1 — Launch First	Hook Engineering Workshop	Entry Point	Course 15	Any creator or operator who has struggled to stop the scroll	$47	→ The AI Content Machine bundle ($497) or Full Track 4
2 — Launch Second	Sales Page Architecture Masterclass	Specialist	Course 25	Operator with validated offer who cannot convert traffic	$197	→ Full Track 5 ($497) or Core Offer track
3 — Launch Third	The Offer Stack Slide Template Pack	Tool	Module from Course 11	Operator who knows the methodology and needs the execution asset	$27	→ Course 11 ($197) or First $10K Offer Builder bundle ($597)
4 — Launch Fourth	RISER SOP Series (individual SOPs at $47 each)	Tool	Standalone SOPs from this series	Operator who needs one specific operating procedure immediately	$47 each	→ Relevant track bundle or full RISER system
5 — Ongoing	Live Offer Teardown Masterclass	Workshop	Recording from past cohort hot seat	Operator who wants to see the methodology applied to real offers	$47	→ Any offer in the Core or Growth tracks

Store the decision and review data without confusing ratios

The Asset Inventory schema uses text IDs/names, a class selection, long-text outcome, buyer description, numerical utility/stack/unbundle ratings, links to current offers and active bundles, an unbundled checkbox and a link to its standalone product. Use stable asset identity so a revised component can be traced into every dependent offer.

The Bundles schema records an automatic ID, name/type, target buyer, promise, mechanism, component links, currency price and component-price sum; status Planned/SoftLaunch/Live/Paused/Retired; launch date; warm/cold conversion; thirty-day incremental revenue; displacement, completion and sixty-day ascension; thirty/ninety-day reviews; retirement reason; and a version/changelog link. Preserve these field types and relationships when designing a working tracker. This lesson does not create an Airtable account or mutate a base.

Its Value Ratio field is bundle price divided by component-price sum times100, with a suggested50–80% range. That is a component-price percentage, not customer outcome value and not margin. Mark it undefined when the comparison sum is zero, unknown or unsupported. The listed asset schema also lacks a standalone price field needed for that rollup, so the schema requires a verified price source rather than an assumed automatic calculation.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Named component and dependency documents: RISER-Product-Versioning-Offer-Changelog-SOP.docx

These document identities were located in the inventory. Their current access, versions and complete methods still need verification; a title match does not certify the underlying procedure.

Original source data for this teaching point — uncorrected source examples retained

Field	Type	Notes
Asset ID	Short text	Format: RN-[Course Number] or RN-[SOP/Framework name]
Asset Name	Short text
Asset Class	Single select	Full Track / Individual Course / Framework / Template / Workshop / SOP
Primary Outcome Delivered	Long text
Avatar Best Served	Short text
Standalone Utility Score	Number	1–10. Updated after each bundle performance review.
Current Offer It Lives In	Link → Offers table
Stacking Score	Number	1–5. How readily does this combine with others?
Unbundle Score	Number	1–5. How strong as a standalone lower-ticket product?
Currently in Active Bundles	Link → Bundles table	All bundles this asset is currently included in
Currently Unbundled	Checkbox	Is a standalone unbundle product currently live for this asset?
Unbundle Product	Link → Bundles table	If unbundled — link to the standalone product record

Field	Type	Notes
Bundle ID	Autonumber
Bundle Name	Short text	The buyer-facing name of the product
Type	Single select	Problem Stack / Avatar Stack / Stage Stack / Crisis Stack / Upgrade Stack / Entry Point Unbundle / Specialist Unbundle / Tool Unbundle / Workshop Unbundle
Target Avatar	Long text	Specific, named description of the buyer this serves
Core Promise	Short text	One sentence transformation statement
Mechanism Statement	Long text	One sentence describing HOW the promise is delivered
Component Assets	Link → IP Asset Inventory	All assets included in this bundle
Price	Currency	Current live price
Sum of Component Prices	Currency	What each component would cost if bought separately — auto-calculated from linked assets
Value Ratio	Formula	Bundle Price / Sum of Component Prices × 100 — should be 50–80%
Status	Single select	Planned / Soft Launch / Live / Paused / Retired
Launch Date	Date
Soft Launch Conversion Rate	Number	% from list email
Cold Traffic Conversion Rate	Number	% from sales page, cold visitors
Net New Revenue (30 days)	Currency	Revenue not attributable to cannibalization
Cannibalization Score	Number	% drop in related existing offer revenue
Completion Rate	Number	% of buyers who complete all components
Ascension Rate (60 days)	Number	% who ascend to next tier within 60 days
30-Day Review Date	Date
90-Day Review Date	Date
Retirement Trigger (if triggered)	Single select	Low Conversion / Cannibalization / Component Retired / Market Change
Version (linked to Changelog)	Link → Changelog Entries	Track bundle changes using the product versioning system

Operating checklist and practical exercise

Set up by inventorying active assets, scoring their utility, selecting five stack and five unbundle hypotheses and recording related-offer baselines. For each bundle, name its type, buyer, mechanism, scope, differentiation, price assumptions and comprehension evidence. For each unbundle, check standalone completeness, the source’s seven-plus utility criterion, price relationship, exclusion statement, next appropriate offer and counterfactual purchase.

Before launch, document feedback, the built page, a tested access flow and a seven-day go/iterate decision. The source checklist includes email and community release steps; these require the actual launch workflow and are not performed by writing curriculum. At thirty days, review all six metrics, completion below30%, the early ascension signal and the scale/continue/iterate/retire decision. At each quarter, inspect positioning, buyer drift, retirement conditions, one new opportunity, component versions and version-current testimonials.

For practice, select one asset you are authorized to use. Design one complete narrow offer or one coherent stack. Write the buyer, inputs, output, prerequisites, evidence, price assumptions, delivery cost, displaced-offer risk and review date. Explain which facts you have verified and what you still need to learn. The final deliverable is a testable offer specification, not a promise of effortless new revenue.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Named component and dependency documents: RISER-Product-Versioning-Offer-Changelog-SOP.docx

These document identities were located in the inventory. Their current access, versions and complete methods still need verification; a title match does not certify the underlying procedure.

Worked contribution exercise: test whether revenue is additive

Use this authored scenario to apply the corrected economic model. Suppose five sales of a new $200 unbundle generate $1,000 gross. Each sale requires $100 of incremental delivery, support, processing and acquisition costs, so the new offer contributes $500 before its fixed launch cost. These are hypothetical inputs to replace with actual records.

Suppose evidence indicates two of those buyers would otherwise have purchased an existing offer contributing $150 each. Estimated displaced contribution is $300. If the additional launch cost is $50, estimated incremental contribution is $500 minus $300 minus $50, or $150. Calling all $1,000 new revenue additive would conceal both costs and displaced business.

The two displaced buyers are a counterfactual estimate, not a directly observable certainty. Compare a plausible range: with no displacement the estimate is $450; if all five replace $150-contribution purchases it becomes negative $300. Investigate buyer alternatives and comparable cohorts, including differences in seasonality, traffic and promotion. The range shows why a new product’s sales alone cannot prove it improved the business.

Now distinguish a separate pricing ratio. If verified component prices total $500 and the bundle costs $300, the source schema reports sixty percent. That does not imply a sixty-percent margin, a sixty-percent probability of success or a measured customer outcome value. If the standalone prices are unavailable or not genuine comparisons, leave the ratio undefined and explain the actual scope instead.

Supporting source: Offer Stacking and Unbundling Strategy — complete SOP

Framework context

Use a value ladder to connect appropriate next outcomes, and evaluate the desired outcome, credibility, delay and buyer effort when packaging an offer. The RISER price ratios and performance gates above remain custom examples.

ClickFunnels — relationships and value-ladder progression · Acquisition.com — offer design

Complete original source text

RISER NATION
MASTER OPERATING SYSTEM
SOP — OFFER STACKING & UNBUNDLING STRATEGY
Manufacturing New Revenue From Existing IP — Without Building Anything New
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
You have already built the hardest thing in any knowledge business: a body of expert IP. Every course, module, framework, template, and SOP in your catalog represents expertise that took years to develop and real buyer validation to prove. Most operators make a fundamental mistake with that asset base — they treat each piece of IP as one offer, to be sold once, to one type of buyer, at one price point.
The Offer Stacking and Unbundling Strategy exists to change that relationship. The same IP, combined differently, positioned differently, and priced differently, can serve completely different buyers at completely different stages of their journey — generating new revenue streams from assets whose development costs are already sunk. This is not repurposing content. This is manufacturing new offers from existing materials.
This SOP covers the full system: the IP asset inventory, the five stack design types, the unbundle decision matrix, the pricing architecture for both strategies, the naming and positioning system, the cannibalization audit, the launch protocol, and the performance monitoring framework. Applied to a 55-course catalog across 9 tracks, the potential offer combinations number in the hundreds. This SOP builds the system for identifying, designing, and launching the most valuable ones.
The Strategic Foundation: When to Stack, When to Unbundle
Stacking and unbundling are opposite operations but they serve the same strategic goal: increasing the number of distinct buyer profiles that your existing IP can serve, and the number of price points at which buyers can enter your ecosystem.
Step 0: The IP Asset Inventory
Before any stacking or unbundling decision can be made, every piece of usable IP must be catalogued. The IP Asset Inventory is the raw material list from which all bundles are built. An inventory that is incomplete or inaccurate produces bundles that do not hold together.
The Asset Classification System
The Asset Inventory Template
Complete one row per asset. This becomes the master reference document for all stacking and unbundling decisions.
The Five Stack Types
Not all bundles serve the same function. Before designing a new stack, identify which type it is — because the type determines the avatar, the pricing, the positioning, and the cannibalization risk.
Stack Type 1 — The Problem Stack
Everything a specific buyer needs to solve one specific, named problem — delivered as a curated solution. The Problem Stack is the most common and most commercially powerful bundle type because it sells to urgency rather than aspiration. The buyer is experiencing the problem now and needs a complete solution now.
Stack Type 2 — The Avatar Stack
Everything a specific named buyer archetype needs — curated for their exact situation, stage, and operating context. The Avatar Stack sells to identity rather than urgency. It says: 'This is built specifically for someone like you.'
Stack Type 3 — The Stage Stack
Everything a buyer needs at a specific stage of business development — compressed into one acquisition. The Stage Stack matches the buyer's current operational reality rather than their aspirational destination. It answers: 'Given where you are right now, here is everything you need to move to the next stage.'
Stack Type 4 — The Crisis Stack
An emergency solution for a buyer experiencing an acute, time-sensitive problem. The Crisis Stack has the shortest time-to-action of all bundle types. It is typically smaller (3–5 components), tighter in scope, and priced lower to reduce friction. The promise is speed, not comprehensiveness.
Stack Type 5 — The Upgrade Stack
An offer designed exclusively for buyers who already own one RISER offer and want to accelerate, deepen, or extend what they have already built. The Upgrade Stack cannot be purchased by someone who does not already have the prerequisite offer — or at minimum, it is positioned and priced to make the prerequisite implicit.
The Four Unbundle Types
Unbundling extracts value from a larger offer to serve buyers who either cannot afford the full offer, do not need all of it, or are not yet ready for it. Each unbundle type has distinct commercial logic and distinct positioning requirements.
Unbundle Type A — The Entry Point Unbundle
Extract the most immediately actionable component of a larger offer and sell it at low friction. The entry-point unbundle is designed to create the first transaction — converting a prospect into a buyer at a price that removes all resistance. Its commercial logic is not the revenue it generates directly but the buyer status it creates.
Unbundle Type B — The Specialist Unbundle
Extract the component that solves a specific problem for a buyer who already has everything else and just needs this one piece. The Specialist Unbundle serves a more advanced buyer than the Entry Point — someone who is not a beginner and does not need a full programme.
Unbundle Type C — The Tool Unbundle
Extract a template, calculator, swipe file, or AI tool from a larger course or programme and sell it as a pure execution asset. The Tool Unbundle serves buyers who already understand the methodology and just need the instrument to execute it.
Unbundle Type D — The Workshop Unbundle
Extract a live session, intensive, or recorded workshop from a larger programme and sell it as a standalone event or replay. The Workshop Unbundle has the highest social proof density of any unbundle type because it shows the methodology in action with real participants.
The Pricing Principles
The fundamental error in bundle and unbundle pricing is pricing the components and then doing arithmetic. Component arithmetic produces prices that are either too low (leaving money on the table) or too high (undermining the bundle's commercial logic). The correct framework prices the transformation — then validates that the price passes the value ratio test.
Stack Pricing Architecture
Unbundle Pricing Architecture
Why Naming Matters More Than Content
A collection of courses with a discount is not a bundle. It is a promotional package. A named offer with a specific mechanism, a specific avatar, and a specific transformation is a product. The difference between the two is almost entirely in the naming and positioning — and the revenue difference between the two is substantial.
The Bundle Naming Formula
Every effective bundle name contains three elements: a time horizon or speed implication, a specific transformation outcome, and optionally a system or mechanism identifier. The combination creates a name that answers 'What does this do for me, and how fast?' in four to seven words.
Complete bundle names from this formula: '30-Day Pipeline Rescue' (Problem Stack). 'The First $10K Offer Builder' (Stage Stack). 'The Paid Traffic Ignition System for Organic-Validated Operators' (Upgrade Stack). Each name is self-explanatory to the correct avatar without requiring supporting copy.
The Bundle Mechanism Statement
Every bundle — like every standalone offer — needs a mechanism statement: a one-sentence description of HOW it produces the promised result. The mechanism statement is the most persuasive element on the bundle sales page because it converts a collection of courses into a coherent system.
The Cannibalization Problem
The greatest risk of offer stacking and unbundling is that the new offer steals revenue from an existing offer rather than generating net new revenue. Cannibalization occurs when two offers solve the same problem for the same avatar at similar price points, and the buyer can only justify one purchase.
The Cannibalization Risk Matrix
The Three Differentiation Tests
Every new bundle or unbundle must pass all three differentiation tests before launch. Failing any one test means either the new offer needs repositioning or it should not be launched.
1. The Avatar Test: Can you name the specific avatar for the new offer in one sentence — and confirm they are different from the primary avatar for any existing offer it could cannibalize?
2. The Stage Test: Is the new offer designed for a buyer at a different stage of their journey than the existing offer it most resembles? Or, if at the same stage, is the problem it solves clearly different?
3. The Price Architecture Test: Does the new offer sit at a price point that creates a clear 'start here → then move here' progression rather than a 'choose one or the other' decision?
The Soft Launch Principle
Every new bundle or unbundle should be soft-launched to the existing email list and community before any public-facing promotion. The soft launch serves four functions: it generates the first sales and testimonials, it validates the positioning with a warm audience before cold traffic, it produces the first data on whether the cannibalization audit was accurate, and it creates social proof for the harder launch.
The Bundle Launch Sequence
The Unbundle Launch Sequence (Simplified)
Unbundles require a lighter launch process than stacks because the price point and complexity are lower. The primary launch asset is one piece of organic content that demonstrates the value of the unbundled component, with the purchase link in the description.
1. Create the unbundle product page in Kajabi or equivalent. Single-page setup: name, description, access delivery. No full sales page required for tool or entry-point unbundles at sub-$97.
2. Create one long-form piece of organic content that demonstrates the core transformation the unbundle delivers. YouTube video, podcast episode, or long LinkedIn post. Do not sell — demonstrate. Link in description.
3. Deploy via existing email list: one email describing the standalone product and its specific use case. Subject line = the problem it solves, not the product name.
4. Monitor for 14 days: conversion rate from content, conversion rate from email, early buyer feedback, cannibalization check on the full offer.
5. If sales are generated: collect testimonials, create follow-up content, add to offer wall. If no sales after 14 days: assess whether the avatar, the price, or the positioning needs adjustment before investing in paid traffic.
Bundle Performance Metrics
Every bundle and unbundle must be tracked against its own set of success metrics. A bundle is not successful because it generated some revenue — it is successful because it generated net new revenue (not cannibalized from existing offers) and because it is serving its target avatar effectively.
The Bundle Retirement Triggers
A bundle should be retired when it is no longer net-positive: when it is cannibalizing more than it generates, when it has stalled below viability thresholds, or when the market it was designed for no longer exists as described.
The RISER Nation Bundle Opportunity Map
Applied to the 55-course catalog across 9 tracks, this section maps the highest-priority bundle and unbundle opportunities by avatar and commercial potential. These are not hypothetical — they are actionable offers that can be designed, built, and launched from existing IP with zero new content creation required.
Priority Stack Opportunities (Launch Sequence Recommended)
Priority Unbundle Opportunities (Launch Sequence Recommended)
Bundle and Unbundle Database — Airtable Schema
Table 1 — IP Asset Inventory
One record per IP asset. The master building block catalog for all stacking and unbundling.
Table 2 — Bundles and Unbundles
One record per live or planned bundle/unbundle product.
Master Offer Stacking & Unbundling Checklist
System Setup (One-Time)
☐ Complete IP Asset Inventory for all active courses, SOPs, templates, and workshop recordings
☐ Score all assets for Standalone Utility, Stacking Score, and Unbundle Score
☐ Identify top 5 stack opportunities and top 5 unbundle opportunities from the inventory
☐ Map all existing offers against the Cannibalization Risk Matrix to establish baselines
☐ Set up Bundles and Unbundles table in Airtable
Every New Bundle Design
☐ Identify the bundle type (one of five stack types)
☐ Define the target avatar in one sentence
☐ Write the mechanism statement (how it produces the promise)
☐ Run the Three Differentiation Tests (Avatar, Stage, Price Architecture)
☐ Run the Cannibalization Risk Matrix against all existing related offers
☐ Price the bundle using the transformation value formula — not component arithmetic
☐ Validate the name using the Brunson Naming Test (5 avatar-matched individuals)
☐ Complete all fields in the Bundles Airtable record before launch
Every New Unbundle Design
☐ Identify the unbundle type (one of four types)
☐ Confirm the Standalone Utility Score is 7+ for the component being extracted
☐ Confirm the price gap to the full offer is at least 3x
☐ Write the positioning guard: 'This is NOT for you if...'
☐ Design the ascension path: what does the buyer purchase next?
☐ Run the Cannibalization Test: would the buyer have bought the full offer instead?
Launch Sequence (Every Bundle and Unbundle)
☐ Internal validation: 5 avatar-matched buyers, minimum 4/5 confirm purchase intent
☐ Sales page (bundles) or product page (unbundles) built and tested
☐ Purchase-to-access flow tested end-to-end with test purchase
☐ Soft launch email sent to existing list
☐ Community announcement posted
☐ 7-day soft launch review: conversion rate, cannibalization check, early buyer feedback
☐ Go/No-Go decision documented — proceed to public launch or iterate
30-Day Performance Review (Every Bundle and Unbundle)
☐ Pull all six performance metrics from the Bundle Performance Metrics table
☐ Run the Cannibalization Score check — any drop in related existing offer revenue?
☐ Check completion rate — below 30% triggers a bundle scope review
☐ Check ascension rate at 30 days — below 5% triggers ascension sequence review
☐ Update Airtable record with all 30-day data
☐ Decide: Scale / Continue / Iterate / Retire
Quarterly Bundle Portfolio Review
☐ Review all live bundles against current Offer Wall for positioning clarity
☐ Check all bundles for avatar drift — has the market shifted since launch?
☐ Retire any bundles meeting retirement triggers
☐ Identify one new high-priority bundle from updated IP Asset Inventory
☐ Update all bundle sales pages to reflect current version of included components
☐ Confirm all bundle testimonials are version-current (see Product Versioning SOP)
RISER Nation Master Operating System | Offer Stacking & Unbundling Strategy SOP | Version 1.0 | 2026 Edition
Kennedy × Hormozi × Brunson | risernation.com
Hormozi's Revenue Manufacturing Principle
The cost of creating an offer bundle from existing IP is approximately zero. The cost of positioning and selling it is approximately zero if you have an existing list. The only constraint is strategic clarity — knowing which components to combine, why they belong together, and which buyer they serve. This SOP is the strategic clarity engine.
The Distinction That Matters
Stacking and unbundling are NOT discounting. They are not sales, bundles created to clear inventory, or promotional packages. They are permanent offers designed to serve specific buyer profiles that are currently under-served by your existing offer wall. Every bundle must have a reason to exist beyond 'we put these together' — it must have a specific avatar, a specific problem, and a specific transformation.
Operation
Definition
When to Use It
What It Produces
Primary Risk
STACKING
Combining multiple existing IP components into a new offer that commands a premium price as a curated solution
When you identify a buyer profile whose complete need is served by a specific combination of your existing components, but no single offer currently addresses their full problem
A new higher-ticket offer serving a specific avatar, with higher perceived value than any individual component
Cannibalization of existing offers if differentiation is unclear
UNBUNDLING
Extracting one component from an existing offer and selling it as a standalone lower-ticket product
When one component of a larger offer has standalone utility for a buyer who does not need the full offer, or when a component can serve as a lower-friction entry point to the full offer
A new lower-ticket offer serving buyers who are price-sensitive, time-constrained, or in an earlier stage — plus a new entry point to the full offer
Cannibalization of the full offer if the unbundled component is too close to the full offer's core promise
The Revenue Manufacturing Equation
New Stack Revenue = (Bundle Price − Sum of Component Prices) × Buyers + Net New Buyers Attracted by Bundle Positioning. New Unbundle Revenue = Unbundle Price × Buyers Who Would Not Have Bought the Full Offer. Both equations should produce positive numbers. If they do not — the bundle or unbundle is not financially justified.
Asset Class
Definition
Examples from a 55-Course Catalog
Stacking Potential
Unbundling Potential
Full Track
A complete sequence of courses serving one transformation arc
Track 1 (Operator Foundation), Track 2 (Find Your Market), Track 6 (Traffic & Conversion)
High — can be stacked with other tracks for a specific avatar
Low — individual courses unbundle more cleanly than full tracks
Individual Course
A single course with a defined outcome and a self-contained methodology
Course 6 (Market Gap Detection), Course 15 (Hook Engineering), Course 29 (Paid Ads Foundations)
High — individual courses are the primary building block of all bundles
High — strong courses with specific standalone utility are prime unbundle candidates
Framework or Methodology
A named, proprietary framework that exists as a tool within a course
The 6-Score Monetisation Filter, The PASTOR Copy Framework, The Value Equation Audit
Medium — frameworks can anchor a bundle's mechanism and name
Medium — frameworks can become standalone audit tools or workshops
Template or Tool
A file, calculator, swipe copy, or interactive tool delivered as part of a course
The 14-Day Email Sequence Template, The Offer Stack Slide Template, The Buyer Language Mining Database
Medium — templates become high-value bonuses in bundles
High — templates at $7–$47 are powerful tripwires and lead magnets
Workshop or Recording
A live session, intensive, or Q&A recording from a past cohort or programme
Live implementation workshop recordings, Hot Seat session recordings, Case study breakdowns
Medium — recordings add social proof depth to bundles
High — standalone workshop recordings at $27–$97 are strong entry-point products
SOP or Reference Document
A documented standard operating procedure that stands alone as a deliverable
The Beta Testing Methodology SOP, The Forensic Audit Loop SOP, The Negative Avatar SOP
High — SOP collections create premium reference bundle value
High — individual SOPs as standalone products at $17–$47
Asset ID
Asset Name
Asset Class
Primary Outcome Delivered
Avatar Best Served
Standalone Utility (1–10)
Current Offer It Lives In
Stacking Score (1–5)
Unbundle Score (1–5)
RN-006
Course 6: Market Gap Detection
Individual Course
Validated niche identification using AI-driven gap detection
Pre-launch entrepreneur with no validated niche
9
Track 2 / RISER Full System
5
4
RN-015
Course 15: Hook Engineering
Individual Course
Scroll-stopping hooks and high-retention content openings
Content creator or marketer needing better hooks
9
Track 4 / RISER Full System
5
5
RN-025
Course 25: Sales Page Architecture
Individual Course
High-converting sales page structure using proven frameworks
Operator with an offer who cannot convert traffic
9
Track 5 / RISER Full System
4
5
RN-FST
Fulfilment Stress Test SOP
SOP Document
Pre-scale delivery infrastructure validation system
Operator about to run first paid campaign or JV launch
8
Standalone SOP Series
3
5
RN-T06
Track 6: Traffic & Conversion (Courses 28-32)
Full Track
Complete email + paid ads + retargeting + tracking system
Operator with proven organic offer ready for paid traffic
7
RISER Full System
4
2
[Add all assets]
Scoring Guide
Standalone Utility (1–10): How useful is this asset to someone who has no other RISER content? 10 = completely self-contained and immediately applicable. 1 = requires other courses to be useful. Stacking Score (1–5): How readily does this asset combine with others into a coherent bundle? Unbundle Score (1–5): How strong is this asset as a standalone lower-ticket product?
PHASE 1
The Stack Design Framework
Five types of bundles — each serving a different strategic purpose
Problem Stack Design Rule
A Problem Stack must solve exactly one problem — completely. If the buyer needs anything else to achieve the stated result, the stack is incomplete and will generate support tickets and refund requests. The test: can a buyer who purchases only this stack and no other RISER content achieve the promised transformation? If no — add the missing component or adjust the promise.
WORKED EXAMPLE: RISER NATION
The First $10K Offer Builder
PROBLEM STACK — Type 1
For
A freelancer or service provider who has expertise but no productised offer. Has never made money from a digital product or programme.
Core promise
Go from expertise to a validated, priced, positioned offer that has generated at least $10K in its first 90 days.
Components
Course 6 (Market Gap Detection) + Course 7 (Psychographic DNA) + Course 10 (Niche Validation & StorySelling) + Course 11 (Direction Clarity & Offer Frameworks) + Course 12 (Outcomes > Features) + Course 13 (Pricing Psychology). 6 courses. Complete system from niche to priced offer.
Bundle price — vs if bought separately
$597 — vs $997+ (if bought inside the Core and Growth bundles) if separate
Avatar Stack Design Rule
An Avatar Stack must address at least three distinct challenges that buyer type faces — not just one. If it addresses one challenge, it is a Problem Stack in disguise. The differentiator is breadth: the Avatar Stack serves the buyer across their entire current context, not just their most urgent problem.
WORKED EXAMPLE: RISER NATION
The Agency Owner to Product Business OS
AVATAR STACK — Type 2
For
An established agency owner (3–10 years) generating $150K–$500K/year in client service revenue who wants to build a product business to reduce client dependency.
Core promise
Build a parallel product revenue stream generating $10K/month within 6 months — without sacrificing agency revenue during the transition.
Components
Course 2 (Skill & Experience Mapping) + Course 11 (Offer Frameworks) + Course 22 (TOFU Education Assets) + Course 23 (Content Factory) + Course 28 (Email Fundamentals) + Course 33 (Data Sovereignty) + Course 40 (Offer Ecosystem). 7 courses. Complete transition system.
Bundle price — vs if bought separately
$797 — vs $1,397+ if bought across individual tracks if separate
Stage Stack Design Rule
A Stage Stack must have clear entry criteria (who should buy this) and clear exit criteria (what the buyer's situation looks like after completing it). Without both, the buyer cannot self-select accurately — and the wrong-stage buyer (Negative Avatar Archetype 03) will purchase and be disappointed.
WORKED EXAMPLE: RISER NATION
The $0 to First $10K OS
STAGE STACK — Type 3
For
A complete beginner with validated expertise but no business infrastructure, no list, no offer, and no prior revenue from their knowledge.
Core promise
Build the foundation of a sovereign knowledge business: validated offer, email list of 500+, and first $10K in revenue within 90 days.
Components
Track 1 (Courses 1–5: Operator Foundation) + Track 2 (Courses 6–10: Find Your Market) + Course 11–12 from Track 3. Complete first-revenue sequence (the 'First Revenue Path' from the catalog).
Bundle price — vs if bought separately
$497 — vs $897+ across individual tracks if separate
Crisis Stack Design Rule
A Crisis Stack must promise a result achievable within 30 days maximum — ideally 7–14 days. If the promised result requires more time, it is not a crisis stack — it is a Problem Stack with urgency copywriting. The distinction is real: a Crisis Stack buyer is under acute time or financial pressure and needs fast relief, not a comprehensive programme.
WORKED EXAMPLE: RISER NATION
The 14-Day Pipeline Rescue
CRISIS STACK — Type 4
For
An operator whose revenue pipeline has dried up in the last 30 days. Urgent need to generate leads and bookings immediately.
Core promise
Rebook your calendar in 14 days using a combination of hook engineering, organic outreach, and a re-activated lead magnet.
Components
Course 15 (Hook Engineering) + Course 22 (TOFU Education Assets) + Course 28 (Email Fundamentals). 3 courses. Maximum urgency, minimum complexity.
Bundle price — vs if bought separately
$297 — vs $597+ across individual tracks if separate
Upgrade Stack Design Rule
An Upgrade Stack must explicitly reference what the buyer already has and clearly position itself as the acceleration layer — not a replacement. Copy must include: 'If you already have [base offer], this is your next step.' Buyers who purchase an Upgrade Stack without the prerequisite will be disappointed because the stack assumes prior knowledge and prior infrastructure.
WORKED EXAMPLE: RISER NATION
The Paid Traffic Ignition (For Organic-Validated Operators)
UPGRADE STACK — Type 5
For
An operator who already has a validated organic offer converting at 2%+ cold and 10%+ warm, and is ready to add paid traffic for the first time.
Core promise
Build a profitable paid traffic system generating predictable leads at a sustainable CAC within 60 days — without the 'learning tax' most operators pay.
Components
Course 29 (Paid Ads Foundations) + Course 30 (Paid Ads Creative Testing) + Course 31 (Omni-Channel Retargeting) + Course 32 (Server-Side Tracking). Complete Track 6 paid acquisition system.
Bundle price — vs if bought separately
$697 — vs $997 as part of the Growth track bundle if separate
PHASE 2
The Unbundle Decision Matrix
When to extract, what to extract, and what price to charge
Design Criterion
Requirement
Example
Which component to extract
The one that delivers the fastest, most tangible result — ideally within 48–72 hours of purchase
Course 15 (Hook Engineering) delivers usable hooks within one session. Strong entry-point candidate.
Price range
$7–$97. Must be impulsive-purchase territory for the target avatar.
Hook Engineering Workshop: $47
Relationship to full offer
The entry-point unbundle should create a natural desire for the next tier. It solves one problem and immediately reveals the next problem.
After completing Hook Engineering, the buyer has great hooks but no platform strategy → natural ascension to Course 22 (TOFU Education Assets) or the AI Content Machine bundle.
Copy positioning
Lead with the specific fast win. Do not mention the full offer on the unbundle page. Let the buyer discover it through the ascension sequence.
'Engineer scroll-stopping hooks in one session — without a copywriting background or prior audience.'
Design Criterion
Requirement
Example
Which component to extract
The one with the highest standalone utility score (8–10) for a buyer who already has adjacent expertise
Course 25 (Sales Page Architecture) — an operator who already knows their offer and avatar, just needs a converting sales page.
Price range
$97–$297. Advanced buyers accept higher prices for specific solutions.
Sales Page Architecture Masterclass: $197
Relationship to full offer
The Specialist Unbundle does NOT require the full offer. It is complete on its own for the right buyer. It should not feel like a teaser.
Buyer completes the sales page module and has a finished, converting sales page. No next step required — but an upsell to conversion tracking (Course 32) is appropriate.
Positioning guard
Must explicitly state who it is NOT for: 'This is not for you if you don't yet have a validated offer and a defined avatar — start with [entry point offer] first.'
Prevents wrong-stage buyers (Archetype 03 Too Early) from purchasing.
Design Criterion
Requirement
Example
Which component to extract
Templates, swipe files, calculators, and AI tools that have standalone utility independent of the instructional content that surrounds them
The Offer Stack Slide Template from Course 11. The 14-Day Email Sequence Swipe from Course 28. The Buyer Language Mining Database from the Forensic Audit SOP.
Price range
$7–$47. Tool unbundles are impulse purchases. Price above $47 and the buyer expects instruction with the tool.
Offer Stack Slide Template Pack: $27
Ascension logic
Tool unbundles should include one short instructional video (5–10 min) showing how to use the tool. This video introduces the full course as the deeper dive.
The template pack includes a 7-minute walkthrough video that references Course 11 as 'the full system behind this template.'
Volume potential
Tool unbundles have the highest volume potential of any unbundle type — low price, high relevance, immediate utility. They are also the strongest GEO assets (AI engines recommend them as standalone resources).
Target: 50–200+ sales per month at $17–$27 via organic content and paid amplification.
Design Criterion
Requirement
Example
What to extract
Live implementation workshops, hot seat session recordings, Q&A replays, or masterclass recordings from past cohorts
The 'Live Offer Teardown' session from a past RISER cohort where 5 offers are critiqued and rebuilt in real time.
Price range
$27–$97. Workshop replays should be priced to feel like attending a live event you missed — not like a course module.
Offer Teardown Masterclass Replay: $47
Freshness requirement
Workshop unbundles have a 12-month maximum shelf life before they feel dated. Update annually or retire.
If the workshop referenced 2024 tools or tactics, it must be re-recorded or retired by 2026.
Social proof function
Workshop unbundles double as social proof assets. The recording shows the methodology producing results in real time. This is more persuasive than any written testimonial.
Include at minimum one 'hot seat' segment where a buyer's specific situation is transformed. The before/after of that transformation is the primary conversion mechanism.
PHASE 3
Pricing Architecture for Stacks and Unbundles
The system for pricing every bundle and unbundle correctly — the first time
The Bundle Pricing Formula
Bundle Price = Transformation Value × Buyer's Willingness-to-Pay Ratio
Transformation Value is what the buyer gets (their outcome in dollar terms). Willingness-to-Pay Ratio is typically 1–5% of the value they receive. A bundle that produces $50K in annual revenue should price between $500 and $2,500.
Stack Type
Price Range
Pricing Logic
Value Ratio Target
Example
Problem Stack
$297–$997
Price to the complete solution. The buyer does not need anything else — that completeness commands a premium over any individual component.
Stack price should be 10–20% of the outcome value the buyer receives
The First $10K Offer Builder at $597 delivers a $10K outcome = 6% of outcome value. Within range.
Avatar Stack
$497–$1,497
Price to the full context shift. The buyer's entire operating situation changes — not just one problem.
Stack price should be 5–10% of the annual revenue upside the transformation enables
The Agency Owner to Product Business OS at $797 for a buyer who generates $50K/year additional product revenue = 1.6% of first-year value. Strong value ratio.
Stage Stack
$297–$797
Price to the stage transition. The buyer moves from Stage A to Stage B — and Stage B is worth substantially more than Stage A.
Compare to cost of staying in Stage A for one more month. Stack price should be below that cost.
$0–$10K stage at $497. Cost of staying at $0 for one more month: incalculable. Decision is easy.
Crisis Stack
$97–$497
Price to urgency. The buyer is in pain now. Remove friction. A crisis buyer who is losing $5K/month needs the solution today — not after evaluating price.
Stack price should be below the weekly cost of the crisis continuing.
14-Day Pipeline Rescue at $297. If the buyer is losing $2K/week, $297 is the easiest purchase decision of their month.
Upgrade Stack
$397–$997
Price to acceleration. The buyer already has momentum — they are buying speed. Premium over the base offer is justified by the acceleration.
Compare to the cost of hiring someone to implement the next phase. Stack price should be 20–40% of that cost.
Paid Traffic Ignition at $697 vs hiring an ads manager for one month at $2,000–$5,000 = 14–35% of alternative. Strong value ratio.
Unbundle Type
Price Range
Pricing Logic
Ascension Price Target
Example
Entry Point
$7–$97
Price for zero friction. The goal is the transaction, not the revenue. Every dollar above $97 increases friction and reduces the likelihood of conversion.
The full offer or the bundle it leads to should be priced at 5–15x the entry-point price, making the ascension feel like a natural investment increase.
Hook Engineering Workshop at $47 leads to the AI Content Machine bundle at $397 (8.5x). Strong ascension ratio.
Specialist
$97–$297
Price for the specific transformation. Specialist buyers have already self-selected as advanced — they accept a higher price for precision.
Specialist unbundle should be 20–40% of the full offer price, creating a clear 'get just what you need vs get everything' decision architecture.
Sales Page Architecture at $197 vs the Growth Track bundle at $797 (24.7%). Clear decision architecture.
Tool
$7–$47
Price for impulse. Tools are bought on the basis of 'I can use this right now.' Every dollar above $47 moves the buyer from impulse to consideration — and consideration loses to inertia.
Tool should lead to a course or workshop priced at 10–20x the tool price. Tool proves the methodology; course teaches the full system.
Offer Stack Slide Template at $27 leads to Course 11 (Direction Clarity & Offer Frameworks) at $297 (11x). Clean ascension.
Workshop
$27–$97
Price for access to an event. Buyers are paying for the experience of attending something, not just content. Below $27 feels like it was not worth producing. Above $97 competes with live event pricing.
Workshop should lead to the full programme at 5–10x the workshop price.
Offer Teardown Masterclass at $47 leads to the Core Offer Track bundle at $497 (10.6x). Excellent ascension ratio.
The Muddled Middle Rule (Applied to Bundles)
The same pricing dead zone that applies to standalone MVOs applies to bundles. Avoid bundle prices of $500–$900 for stacks and $50–$95 for unbundles. These ranges require too much deliberation for impulse buyers and too little investment for premium buyers. The math works cleanest at clear psychological price points: $297, $397, $497, $597, $797, $997 for stacks; $7, $17, $27, $47, $97, $197, $297 for unbundles.
PHASE 4
The Naming and Positioning System
Every bundle needs a name and a promise that makes it a distinct offer — not a collection
The Brunson Naming Test
Read the bundle name to five people who match the target avatar. If all five immediately understand what the bundle is for and who it serves — without explanation — the name is working. If any of the five need clarification, rename it. A bundle name that needs explanation is a liability on the sales page.
Name Component
Function
Options
Example
Time Horizon (optional but powerful)
Creates urgency and sets expectation for speed of result
7-Day, 14-Day, 30-Day, 90-Day, First, Fast, Rapid, Sprint
'30-Day...'
Transformation Descriptor
Describes what specifically changes for the buyer
Revenue, Client Acquisition, Offer, Traffic, Funnel, Pipeline, Content, Email, Visibility
'...Pipeline Rescue'
System or Container Word (optional)
Positions the bundle as a complete system rather than a collection
OS, System, Engine, Blueprint, Accelerator, Machine, Foundation, Ignition
'...Ignition System'
Avatar Qualifier (optional but improves relevance)
Clarifies who specifically benefits
For [Avatar Type], For Operators, For Agency Owners, For Beginners, For [Stage]
'...For Organic-Validated Operators'
Bundle Name
Mechanism Statement
What It Does
The First $10K Offer Builder
A 6-course validation and offer construction sequence that takes you from undifferentiated expertise to a priced, positioned, tested offer in 30 days — using the same AI-driven market gap detection and Forensic Critic positioning that validated RISER Nation's own curriculum.
Names the mechanism (validation and offer construction sequence), specifies the time (30 days), establishes credibility (used by RISER Nation itself), and anchors the transformation (expertise to priced offer).
The 14-Day Pipeline Rescue
A 3-module implementation sprint that restores a dry pipeline in 14 days by engineering scroll-stopping organic hooks, activating a dormant email list, and deploying a rapid lead magnet relaunch.
Names the mechanism (implementation sprint), names the three actions, specifies the outcome (restored pipeline) and time (14 days).
The Paid Traffic Ignition System
A 4-course paid traffic foundation that builds a profitable Meta + Google acquisition system from scratch in 60 days — starting from the creative brief, through server-side tracking, to a retargeting ecosystem that compounds over time.
Names the platforms, the time, the starting point, and the compounding nature of the result.
PHASE 5
The Cannibalization Audit
Ensuring new bundles protect — not undermine — existing offer revenue
The Cannibalization Test
Ask: If the new bundle or unbundle did not exist, what would the buyer purchase instead? If the answer is an existing offer — cannibalization is occurring. If the answer is 'nothing' (they would not purchase any RISER product because no existing offer serves their situation) or 'a competitor's product' — the new bundle is creating net new revenue.
Scenario
Cannibalization Risk
Mitigation
New bundle contains the same courses as an existing bundle, at a lower price
Critical — directly undercuts the existing offer
Never create a new bundle that contains a subset of an existing bundle's content at a lower price without clearly differentiating avatar, use case, and positioning. If the differentiation is not clear enough to communicate in one sentence, do not launch the new bundle.
New bundle contains courses from an existing bundle, at a similar price, for a similar avatar
High — buyer must choose one or the other
Audit the avatar differentiation. If both bundles serve the same avatar at the same stage, merge them rather than running both. Two bundles competing for the same buyer create decision paralysis.
Unbundle's price is within 25% of the full offer's price
High — buyer will choose the unbundle and feel they made a savvy decision rather than ascending to the full offer
Ensure the price gap between unbundle and full offer is at least 3x. Below 3x, the buyer rationalises the unbundle as 'enough' and the ascension logic breaks down.
New unbundle's core promise is the same as the full offer's core promise, just positioned as smaller
High — the unbundle repositions the full offer as 'too much'
An unbundle's promise must be narrower than the full offer's promise — not the same promise at a lower price. 'Get your first 10 hooks' is narrower than 'build a complete content engine.' Never position an unbundle as 'a smaller version of the full offer.'
New bundle includes a course that is the primary reason most buyers purchase the full programme
Medium — the bundle becomes a substitute for the full programme
If the 'anchor course' (the one buyers cite most often as their purchase driver) is in a new bundle, the bundle will cannibalize the full programme. Either exclude the anchor course from the bundle or price the bundle at 70%+ of the full programme price.
New bundle or unbundle serves the same avatar but at a different stage
Low — serves buyers who are not yet ready for the full offer
Document the stage differentiation clearly. Add 'This is the prerequisite to [full offer name]' to the bundle page. This frames the relationship correctly and creates ascension intent from the first purchase.
PHASE 6
The Launch Protocol
Bringing a new bundle or unbundle to market without disrupting existing revenue
Step
Timing
Action
Goal
1. Internal validation
7 days before soft launch
Share the bundle name, mechanism statement, and price with 5 existing buyers who match the target avatar. Ask: 'If you didn't already own the components, would you buy this at this price?' Minimum 4 of 5 'yes' answers required before proceeding.
Validate positioning before writing a single line of sales copy.
2. Sales page build
Days 1–5
Build the bundle sales page using the existing sales page SOP framework: hook, problem, mechanism, stack reveal, social proof, guarantee, FAQ, CTA. Note: the stack reveal for a bundle shows each component with its standalone value assigned.
Live sales page with tracking pixel installed and all UTM parameters set.
3. Bundle access setup
Before soft launch
Ensure all components of the bundle are accessible via a single Kajabi product or equivalent. Test the purchase-to-access flow with a test purchase.
Zero-friction access experience from purchase confirmation to first content.
4. Soft launch email to existing list
Day 1 of soft launch
Single plain-text email to the entire list: introduce the bundle by name, describe the avatar it serves, state the price, and link to the sales page. No launch sequence — one email, honest framing.
Validate warm conversion rate. Target: 1–3% of list. Collect first testimonials.
5. Community announcement
Same day as soft launch email
Post in the community: same information, different format. Invite questions in the thread. The Q&A thread becomes FAQ content for the sales page.
Additional sales. FAQ data. Community engagement signal on the new positioning.
6. Performance review
7 days after soft launch
Review: total sales, conversion rate from email, conversion rate from community, any cannibalization evidence (did sales of existing related offers drop?), early buyer feedback.
Go/No-Go decision for public launch. If soft launch conversion is below 0.5% of list — do not scale to paid traffic.
7. Public launch (if soft launch passes)
Day 8+
Add bundle to offer wall. Create organic content referencing the bundle. Begin paid retargeting to visitors. If strong social proof is available from soft launch buyers: build a full launch sequence.
Scale from warm-audience validation to broader market.
PHASE 7
Performance Monitoring and Retirement
Measuring whether bundles are working — and killing them when they are not
Metric
Target (Healthy)
Warning Signal
Kill Threshold
Measurement Tool
Net new revenue (not cannibalized)
100% of bundle revenue is additive — no drop in related existing offer revenue
Related offer revenue drops 10–15% in 30 days following bundle launch
Related offer revenue drops 25%+ — bundle is cannibalizing, not adding
CRM revenue report, segmented by offer
Conversion rate from list (soft launch)
0.5–2% of email list for warm launch
Below 0.3% after full email
Zero sales from 1,000+ warm contacts after one email and one community post
Email platform analytics + CRM
Conversion rate from cold traffic (post-public launch)
0.8–2.5% of sales page visitors
Below 0.5% after 200+ visitors post-diagnostic
Below 0.3% after full Pre-Kill Diagnostic applied — trigger Kill Assessment
GA4 + sales platform
Completion rate of bundle components
45%+ complete all included components
Below 30% — bundle scope may be too broad
Below 20% — buyers are not engaging with the full stack; either the components are irrelevant or the promise was too broad
Course platform completion analytics
Ascension rate to next tier
8–15% of bundle buyers ascend to the next offer within 60 days
Below 5% at 60 days
Below 3% at 90 days — ascension sequence is broken or the next offer is wrong
CRM pipeline report
Cannibalization score (daily)
0% — no drop in existing related offer revenue
Any drop in related offer revenue in first 30 days requires investigation
25%+ drop in a directly related offer's revenue in first 30 days — pause the bundle and audit
CRM comparative revenue report
Retirement Trigger
Threshold
Retirement Process
Sustained low conversion
Below 0.3% conversion rate from cold traffic after full Pre-Kill Diagnostic applied across 300+ visitors and one full iteration cycle
Apply the Product Kill Criteria SOP. If the Kill Assessment Scorecard scores below 25, retire the bundle. Archive all copy and buyer data.
Confirmed cannibalization
Related existing offer revenue drops 20%+ sustained for 60+ days with no other market explanation
Pause the bundle immediately. Run the Three Differentiation Tests again. If the positioning cannot be differentiated sufficiently, retire the bundle permanently.
Component IP retired
A core component of the bundle is retired from the main catalog (deprecated course, removed module)
Update the bundle within 30 days. If the retired component was the bundle's primary value driver, retire the bundle and notify existing bundle buyers with access maintenance period.
Market conditions change
The specific avatar or problem the bundle addressed is no longer as relevant due to market shifts, competitor solutions, or technology changes
Quarterly review of all bundle avatars against current market conditions. Apply the Mechanism Freshness Test (from the Forensic Audit Loop SOP). If the bundle's promise is no longer credible, retire and reposition.
Priority
Bundle Name
Type
Components
Target Avatar
Estimated Price
Commercial Rationale
1 — Launch First
The First $10K Offer Builder
Problem Stack
Courses 6,7,10,11,12,13
Freelancer/service provider with expertise but no productised offer
$597
Largest underserved avatar in the catalog. No existing offer addresses this exact stage.
2 — Launch Second
The Paid Traffic Ignition System
Upgrade Stack
Courses 29,30,31,32 (Full Track 6)
Organic-validated operator ready for first paid traffic
$697
High-urgency purchase. Buyers at this stage have budget and urgency. Strong separation from the full system.
3 — Launch Third
The AI Content Machine
Problem Stack
Courses 22,23,24,35
Content-overwhelmed operator who needs a production system
$497
Addresses one of the most common avatar pain points. Strong hook-to-mechanism alignment.
4 — Launch Fourth
The 14-Day Pipeline Rescue
Crisis Stack
Courses 15,22,28
Operator with dry pipeline needing immediate lead flow
$297
Urgency-driven purchase. Low price, high intent. Strong entry point to full system.
5 — Seasonal
The MRR Foundation Bundle
Stage Stack
Courses 14,28,40,41
Operator with proven offer ready to build recurring revenue
$697
Recurring revenue focus is highest-priority aspiration across the RISER avatar base.
Priority
Unbundle Name
Type
Source Asset
Target Avatar
Estimated Price
Ascension Path
1 — Launch First
Hook Engineering Workshop
Entry Point
Course 15
Any creator or operator who has struggled to stop the scroll
$47
→ The AI Content Machine bundle ($497) or Full Track 4
2 — Launch Second
Sales Page Architecture Masterclass
Specialist
Course 25
Operator with validated offer who cannot convert traffic
$197
→ Full Track 5 ($497) or Core Offer track
3 — Launch Third
The Offer Stack Slide Template Pack
Tool
Module from Course 11
Operator who knows the methodology and needs the execution asset
$27
→ Course 11 ($197) or First $10K Offer Builder bundle ($597)
4 — Launch Fourth
RISER SOP Series (individual SOPs at $47 each)
Tool
Standalone SOPs from this series
Operator who needs one specific operating procedure immediately
$47 each
→ Relevant track bundle or full RISER system
5 — Ongoing
Live Offer Teardown Masterclass
Workshop
Recording from past cohort hot seat
Operator who wants to see the methodology applied to real offers
$47
→ Any offer in the Core or Growth tracks
Field
Type
Notes
Asset ID
Short text
Format: RN-[Course Number] or RN-[SOP/Framework name]
Asset Name
Short text
Asset Class
Single select
Full Track / Individual Course / Framework / Template / Workshop / SOP
Primary Outcome Delivered
Long text
Avatar Best Served
Short text
Standalone Utility Score
Number
1–10. Updated after each bundle performance review.
Current Offer It Lives In
Link → Offers table
Stacking Score
Number
1–5. How readily does this combine with others?
Unbundle Score
Number
1–5. How strong as a standalone lower-ticket product?
Currently in Active Bundles
Link → Bundles table
All bundles this asset is currently included in
Currently Unbundled
Checkbox
Is a standalone unbundle product currently live for this asset?
Unbundle Product
Link → Bundles table
If unbundled — link to the standalone product record
Field
Type
Notes
Bundle ID
Autonumber
Bundle Name
Short text
The buyer-facing name of the product
Type
Single select
Problem Stack / Avatar Stack / Stage Stack / Crisis Stack / Upgrade Stack / Entry Point Unbundle / Specialist Unbundle / Tool Unbundle / Workshop Unbundle
Target Avatar
Long text
Specific, named description of the buyer this serves
Core Promise
Short text
One sentence transformation statement
Mechanism Statement
Long text
One sentence describing HOW the promise is delivered
Component Assets
Link → IP Asset Inventory
All assets included in this bundle
Price
Currency
Current live price
Sum of Component Prices
Currency
What each component would cost if bought separately — auto-calculated from linked assets
Value Ratio
Formula
Bundle Price / Sum of Component Prices × 100 — should be 50–80%
Status
Single select
Planned / Soft Launch / Live / Paused / Retired
Launch Date
Date
Soft Launch Conversion Rate
Number
% from list email
Cold Traffic Conversion Rate
Number
% from sales page, cold visitors
Net New Revenue (30 days)
Currency
Revenue not attributable to cannibalization
Cannibalization Score
Number
% drop in related existing offer revenue
Completion Rate
Number
% of buyers who complete all components
Ascension Rate (60 days)
Number
% who ascend to next tier within 60 days
30-Day Review Date
Date
90-Day Review Date
Date
Retirement Trigger (if triggered)
Single select
Low Conversion / Cannibalization / Component Retired / Market Change
Version (linked to Changelog)
Link → Changelog Entries
Track bundle changes using the product versioning system

Assigned source documents: RISER-Operators-Flow.html — source 1 · RISER-Operators-Flow.md — source 1 ·

Build, deliver and improve a professional-services offer

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

Video placeholder

Record the five-phase walkthrough after final source reconciliation. Teaching scripts, source passages and exercises follow.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Opening script and phase map

This plan turns a proposed service into a sequence of observable deliverables: an evidence-backed offer, credible buyer-facing assets, conversations, repeatable delivery and a review process. It contains five phases and twenty-two numbered steps; the original introduction incorrectly says eighteen.

The source sketches foundation in weeks1–4, assets5–8, acquisition9–12 and ongoing operations/review from13 onward, while also suggesting faster work and outreach overlaps. Treat this as an illustrative schedule. Start delivery systems when the first client signs; do not wait for a calendar label. Week-three conversations and week-six-to-ten first-client claims are not established outcomes.

Tool labels such as Real, Useful With Caveats and Mostly Theater are the author’s April2026 judgments, not universal capability ratings. Prices and platform-event claims in the preserved source are historical assertions awaiting verification where needed. Choose tools by actual output quality, privacy, access, cost and fit.

Lesson outline

1.1 — Idea Capture
1.2 — Pain Discovery
1.3 — Offer Hypothesis
1.4 — MVP / Service Definition
2.1 — Competitive Intelligence
2.2 — Brand & Asset Minimum Viable Set
2.3 — Lead Magnet (Gift First)
2.4 — Sales Page / Service Page
3.1 — Warm Network Outreach
3.2 — Dream 100 List Building
3.3 — Dream 100 Outreach Cadence
3.4 — Content Distribution Cadence
3.5 — Paid Channels (Defer Until Earned)
4.1 — Client Onboarding SOP
4.2 — Delivery SOP
4.3 — Knowledge Management
4.4 — Tech Stack Hygiene
5.1 — Monthly Metrics Review
5.2 — Quarterly Buyer Feedback
5.3 — A/B Testing (Earned)
5.4 — Offer and Positioning Refresh
5.5 — Scale Decision

1.1 — Idea Capture

Start with a two-hundred-word paragraph containing five decisions: the buyer, their problem, your proposed solution, the price tier and why your experience makes you a credible provider. Use your existing skills and credentials as inputs, but describe the outcome instead of listing credentials as a substitute for value.

Have another person read it once and explain who you serve, what you do and why someone might pay. Revise jargon or an overly broad buyer definition until the explanation is clear. This is a clarity check, not market validation. Revisit the paragraph when customer evidence contradicts it and at the source’s suggested quarterly review.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 1.1 — Idea Capture

**Produces:** A one-paragraph statement of the business or service idea, who you think it serves, and what specific problem you think it solves.

**Input:** Your existing skills, prior work, professional credentials, and the rough hypothesis you're entering with.

**How to do it:** Write the paragraph by hand on paper. Two hundred words. Include the buyer (one sentence), the problem (one sentence), the solution (one sentence), the price tier (one sentence), and what makes you specifically the right person to deliver it (one sentence). The constraint forces clarity.

**Done-when criteria:** A literate friend can read the paragraph once and explain back to you what your business does, who it's for, and why someone would pay you. If they can't, rewrite.

**Common failure modes:** Writing in jargon. Listing features instead of outcomes. Defining the buyer too broadly ("small business owners" instead of "construction defect attorneys at mid-sized firms in Arizona"). Hiding behind credentials instead of describing what you actually do for clients.

**AI/tool layer:** None needed at this step. **Mostly Theater** if you're using AI to "validate" the idea here — the model will tell you almost any idea sounds promising. Save the validation work for Step 1.3.

**Iteration trigger:** Phase 5 customer feedback that contradicts your stated buyer or problem. Rewrite this paragraph quarterly.

---

1.2 — Pain Discovery

Turn the idea into an evidence document with three to five pain themes. Over an initial research week, combine five to ten listening conversations, observation of relevant public communities, and optional tool-assisted discovery. Ask what is frustrating, when it last mattered, what the person tried and what did or did not help. Capture at least twenty genuine quotes with source and context rather than converting your assumptions into customer language.

Tag urgent triggering events as burning pain and recurring background problems as chronic pain. The source wants at least two leading themes to be burning. Use that as a prioritization prompt, not proof that prevention or efficiency offers cannot sell. Investigate impact, budget, authority and the conditions that trigger a decision.

The source names Otter, Fathom, ChatGPT/Claude and SparkToro, with PainOnSocial and PainPointy as tools needing review. Its claim that automated pain rankings are wrong one third of the time is unverified. Use human checking, appropriate recording permission and genuine source evidence. The MVO pain/avatar gates and Pain Discovery catalogue are related resources; refresh the evidence as buyer context changes.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md · RISER-MVO -PAINONSOCIAL TO MVO-NETFILY.04.30.26.html · RISER-MVO -PAINONSOCIAL TO MVO-NETFILY.04.30.26.html · RISER-MVO -PAINONSOCIAL TO MVO-NETFILY.04.30.26.html · RISER-Widget-Pain-Discovery-Tools-Merged.md

Complete original step — includes source-era examples and claims corrected above

### Step 1.2 — Pain Discovery

**Produces:** A document with three to five real pain points your buyer experiences, written in their own language, with evidence sources. Not pain you assume they have. Pain they say out loud.

**Input:** The Step 1.1 paragraph. Your hypothesis about who the buyer is.

**How to do it:** Three parallel research tracks, run for one week:

1. **Direct conversations.** Five to ten phone or video calls with people in your target buyer category. Not pitches. Listening tours. Questions: What's the most frustrating part of [problem area]? When did this last cause a real problem? What did you try? What worked? What didn't?
2. **Public language mining.** Read what your buyers post and ask in places they gather: LinkedIn posts and comments, association forums, niche Slack groups, industry-specific subreddits if any exist, Quora answers in their domain. Copy verbatim phrases into a document.
3. **Tool-assisted scanning.** Use the RISER Pain Discovery Tool Catalog — specifically the Reddit pain mining tools, audience intelligence tools (SparkToro), and VOC synthesis tools — to surface language patterns at scale.

**Sort what you find into two buckets — burning vs chronic.** This distinction is the most useful prioritization tool in pain discovery. **Burning pain** is active crisis: a lawsuit was filed last week, a deposition is in 14 days, a client just sued, a deadline is tomorrow, a regulator just sent a notice. Burning pain drives buying *this week*. **Chronic pain** is the dull background ache: communication is messy, vendor management is annoying, paperwork takes too long. Chronic pain is real but rarely triggers a buying decision on its own — it needs a triggering event to become burning.

For high-ticket professional services, your offer must address burning pain. Operators who build offers for chronic pain spend years marketing to people who agree there's a problem but never buy. Tag every pain point in your discovery doc as B (burning) or C (chronic). If your top three pains are all C, your offer or your avatar is wrong.

**Done-when criteria:** You have at least 20 verbatim quotes from real buyers describing pain in their own words, organized into 3–5 themes, each tagged burning or chronic. At least two of your top themes are burning. You can show a friend the quotes (with sources) and they can independently identify the themes you found and the burning/chronic tag.

**Common failure modes:** Using your own words instead of the buyer's. Treating one Reddit thread as evidence. Skipping the direct conversations because they're hard to schedule (this is the single biggest stall point). Picking only pain points that flatter your existing solution.

**AI/tool layer:**
- **Real:** Otter.ai or Fathom for transcribing buyer conversations. ChatGPT/Claude for synthesizing themes across transcripts. SparkToro for finding where buyers gather.
- **Useful With Caveats:** PainOnSocial, PainPointy for surfacing language patterns. They produce useful raw material but the categorization needs human review — the AI is wrong about pain intensity ranking maybe one third of the time.
- **Mostly Theater:** Any tool claiming to "automatically generate buyer personas" without you talking to a single buyer. The output looks plausible. It will not survive contact with reality.

**Iteration trigger:** Quarterly. Buyer pain shifts as their context shifts (regulatory changes, economic conditions, technology shifts). The doc you wrote in Q1 needs revision by Q3.

**Existing RISER artifact:** The **MVO Decision Engine widget** (Gate 00½ Pain Discovery, Gate 01 Hungry Avatar). The **Pain Discovery Tool Catalog** lists the 41 tools that fit this work and their honest tradeoffs.

---

1.3 — Offer Hypothesis

Write a one-page offer around desired outcome, credible likelihood, time to result and buyer effort. Name the deliverable and the process, such as the source’s fourteen-day forensic-audit example, only when you can actually support the scope and timing. The Value Equation helps organize these questions; it is not a calibrated numeric forecast.

Define a decision rule before testing. The source example reconsiders an offer if no paid engagement occurs after sixty days of active outreach and proposes a twenty-five-percent price cut or restructuring. Specify adequate exposure and inspect message, audience and access before attributing the result to price. Its assertion that first prices are usually forty-to-sixty percent of market is not established.

You should be able to explain the offer, price, deliverable timeline and decision rule in thirty seconds. Review understanding in the first five buyer conversations. AI can help generate objections, while actual ICP message research tests comprehension; the listed Wynter price is a historical example, not a current quote. The source points to MVO offer gates and Marketing Plan Generator section08.

Complete original step — includes source-era examples and claims corrected above

### Step 1.3 — Offer Hypothesis

**Produces:** A specific named offer — what you sell, what it costs, what the buyer gets, what they walk away from the call with — that maps directly to the pain you found.

**Input:** Step 1.2 pain document. Your skills inventory.

**How to do it:** Write the offer in one page, using Hormozi's value-equation structure. Name the dream outcome (in the buyer's words). Name the perceived likelihood (your proof — credentials, prior work, sample deliverable). Name the time delay (how long until they get the result). Name the effort/sacrifice (what they have to do versus what you do). The offer wins or loses on whether (Dream × Likelihood) ÷ (Time × Effort) is high.

Decide on a named mechanism. Not "I do forensic engineering" — "The 14-Day VRF Failure Forensic Audit." Specific deliverable, specific timeframe, specific outcome.

Decide on a kill criterion before launch. *"If I cannot get one paying engagement at this price within 60 days of starting active outreach, I will reduce price by 25% or restructure the offer."* Write the criterion down. Date it. Keep it visible.

**Done-when criteria:** You can describe the offer in 30 seconds, name the price, name the deliverable timeline, name your kill criterion, and a literate friend can repeat it back accurately.

**Common failure modes:** Pricing too low because you're nervous (this is universal — your first instinct on price is usually 40–60% of what the market pays). Naming the offer in your own jargon instead of the buyer's. Skipping the kill criterion because writing it feels like admitting you might fail. The kill criterion is the *whole point* — it converts a vague hope into a falsifiable bet.

**AI/tool layer:**
- **Real:** Claude or ChatGPT to pressure-test offer language by simulating buyer objections. Wynter ($540+/test) for actual ICP message testing if the price tier justifies it.
- **Mostly Theater:** Any "AI offer generator" that produces a finished offer without you doing the pain research first. The output is generic.

**Iteration trigger:** First five buyer conversations. If buyers don't immediately understand the offer or push back hard on price, restructure.

**Existing RISER artifact:** The **MVO Decision Engine** Gate 04 Solution Sketch, Gate 05 Offer, Gate 06 Pricing. The **Marketing Plan Generator** outputs a complete offer angle in section 08 of every plan it produces.

---

1.4 — MVP / Service Definition

Create a one-page scope of work from the offer: inclusions, exclusions, timeline, communication cadence, revisions, out-of-scope handling and payment terms. Name the productized package, exact deliverables and eligibility. Decide which work is templated, what is custom and what you will decline.

Your completion check is a document that lets both parties understand the commitment before delivery. Review it after the first three engagements to identify scope leaks. AI drafting and signing tools such as PandaDoc or Bonsai can support the process, but the actual service must be deliverable before an elaborate automation is built.

Complete original step — includes source-era examples and claims corrected above

### Step 1.4 — MVP / Service Definition

**Produces:** The actual *thing* you will deliver. For services this is a scope-of-work template. For software this is a working prototype. For productized services this is a defined deliverable package.

**Input:** Step 1.3 offer document.

**How to do it:** Write the scope of work in one page. What's included. What's not included. Timeline. Communication cadence. Revisions. Out-of-scope handling. Payment terms. For a service business, this is also where you decide what you will template, what you will custom-build, and what you will refuse to do.

For productized services (most professional services should be productized): name the package, list the exact deliverables, set the price, set the timeline, define what makes a customer eligible to buy.

**Done-when criteria:** You have an SOW you could send to a buyer this afternoon. It defines scope so clearly that you know in advance what you're delivering and so does the buyer.

**Common failure modes:** Vague scope language ("ongoing strategic guidance") that lets buyers expand the work without paying more. Missing the "out of scope" section. No defined revision limit. Promising deliverables you haven't actually built a process for.

**AI/tool layer:**
- **Real:** Claude or ChatGPT to draft the SOW from a checklist. PandaDoc or Bonsai for SOW signing infrastructure (free or low cost).
- **Mostly Theater:** Building a "Product Architect Agent" workflow before you've delivered the service to one human. Map the actual delivery from one real engagement first.

**Iteration trigger:** After the first three engagements. You will discover scope leaks and SOW gaps you didn't anticipate. Update the template.

---

2.1 — Competitive Intelligence

Create a one-page matrix of three to five direct competitors. Record their visible offer, price where published, positioning, lead resource, hook and case-study evidence. Distinguish what you observed from your inference about what works. A site’s existence or estimated traffic does not prove conversion performance.

Explain one strength, one gap and your relevant difference for each competitor. Review quarterly rather than using endless research to delay buyer conversations. The source names BuiltWith, Similarweb, Wayback Machine, Apify and Bright Data. Check current tool capabilities, access rights and terms before research; this lesson does not download gated assets or run scraping.

The artifact map calls MVO Gate03 Competitive Moat. The reviewed D0935 explainer and staged D0106 candidate instead identify Gate03 as Profitable Problem. Preserve this version mismatch; the widget link does not prove a Competitive Moat screen exists. Use the actual competitor matrix described here, and identify the demonstrated widget version before directing a learner to a gate.

Complete original step — includes source-era examples and claims corrected above

### Step 2.1 — Competitive Intelligence

**Produces:** A one-page comparison matrix of three to five direct competitors — their offer, their pricing, their positioning, their lead magnet, their hook, what's working for them, what's missing.

**Input:** Phase 1 work. Knowledge of who else serves your buyer.

**How to do it:** List five competitors. Open each one's website, lead magnet (download it), pricing page (if visible), LinkedIn, and any case studies. Fill in the matrix. Note what you can't easily improve on (their credentials, their tenure) and what you can (their positioning, their offer specificity, their pain language match).

**Done-when criteria:** You can name in one sentence per competitor what's strong about their positioning and what's weak. You have an explicit "we're different from them because..." for each.

**Common failure modes:** Researching too many competitors (five is enough; ten is hiding from the work). Fixating on what they do better instead of what they leave on the table. Copying their offer instead of differentiating from it.

**AI/tool layer:**
- **Real:** Built With or SimilarWeb for tech-stack and traffic visibility on competitor sites (free or low-tier). Wayback Machine to see how their positioning has evolved.
- **Useful With Caveats:** Apify, Bright Data for scraping if you need depth. Compliance and TOS questions matter — read them.
- **Mostly Theater:** "AI-driven competitive intelligence agents" that promise daily monitoring. They produce dashboards. Dashboards are not insight.

**Iteration trigger:** Quarterly. Competitor offers and positioning shift; your matrix needs refresh.

---

2.2 — Brand & Asset Minimum Viable Set

Prepare the minimum credible asset set: wordmark or logo, appropriate professional headshot, one-page third-person biography, color palette and service overview. The biography should identify credentials, three concrete accomplishments that can be disclosed and the buyer served. Produce a usable profile, directory-listing draft and overview PDF.

Timebox this work. The source’s instruction to defer more brand work until five clients is a focus heuristic. Its Fiverr/99designs$200–$500, Canva$15/month and Looka$50 examples are dated estimates, not current purchase recommendations. Use tools appropriate to the task and verify costs before spending. Credibility comes from truthful substance as well as presentation.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 2.2 — Brand & Asset Minimum Viable Set

**Produces:** A logo (or wordmark), one professional headshot, a one-page bio, a defined color palette, and a one-page service overview document. That's the minimum. Nothing more until you've closed five clients.

**Input:** Phase 1 work. Your existing materials.

**How to do it:** Use Canva or Figma. Pay $200–$500 for a wordmark on Fiverr or 99designs if you want polish. Get a real headshot — phone-camera selfie quality is fine for LinkedIn but not for an expert witness directory listing. Write the one-page bio in third person, including your specific credentials, three concrete prior accomplishments (sanitized if needed), and a clear statement of who you serve.

**Done-when criteria:** You have a presentable LinkedIn profile, a presentable directory listing draft, and a service overview PDF you can email to a prospect.

**Common failure modes:** Spending three weeks on a logo. Hiring a brand strategist before you have buyers. Writing the bio in language that sounds like every other consultant's bio.

**AI/tool layer:**
- **Real:** Canva ($15/mo) for fast asset production. Claude/ChatGPT to draft and polish the bio. Looka for $50 wordmark generation if you can't decide what you want.
- **Mostly Theater:** AI-generated "brand identity systems." Looks impressive, costs significant time, doesn't move buyers. Save brand investment for after you have customer feedback.

---

2.3 — Lead Magnet (Gift First)

Choose one narrow buyer problem and create a useful checklist, calculator, review template or short guide. It should help even if the person never buys. Test comprehension and usefulness with two suitable buyers before release, and make any email or call exchange clear.

The source rejects generic tips, disguised pitches and unnecessarily long material. Judge length by the job the resource must do rather than a universal page count. AI can assist drafting and Canva/Figma can support layout; the named email tools are delivery examples. Marketing Plan Generator section05 supplies a proposed lead-magnet concept, which still requires expert review and real implementation.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md · RISER-Marketing-Plan-Generator.html

Complete original step — includes source-era examples and claims corrected above

### Step 2.3 — Lead Magnet (Gift First)

**Produces:** A specific, valuable, narrow asset that solves one micro-problem for your buyer in exchange for their email or a 15-minute call. Not a generic ebook. A diagnostic checklist, a calculator, a contract review template, a five-page "how to evaluate X" guide.

**Input:** Phase 1 pain doc. Knowledge of buyer's specific decision moments.

**How to do it:** Pick the buyer's most concrete sub-pain. Build the asset that solves it. Constraint: this asset should be useful even if the buyer never works with you. That's what triggers reciprocity (Cialdini). A bait-and-switch lead magnet that turns into a pitch deck does not work and damages trust.

**Done-when criteria:** A buyer who downloads this asset finds it genuinely useful and would tell a colleague about it. You've tested this with two real buyers before launch.

**Common failure modes:** Generic "10 tips for X" content. Disguised pitch decks. Asset is too long (40 pages = won't be read) or too short (one tip = not worth the email).

**AI/tool layer:**
- **Real:** Claude/ChatGPT to draft the asset content. Canva or Figma for layout. ConvertKit, Beehiiv, or Mailchimp for email delivery infrastructure.
- **Mostly Theater:** "AI lead magnet generators" that produce generic content with no specific buyer in mind.

**Existing RISER artifact:** The **Marketing Plan Generator** generates a specific lead-magnet recommendation for any profession+avatar combination as section 05 of every plan.

---

2.4 — Sales Page / Service Page

Build a page for the specific buyer and offer. Follow the source sequence: hook, problem, why existing approaches fall short, mechanism, proof, offer, actual bonuses, appropriate risk reversal and a clear action. Its eight-hundred-to-fifteen-hundred-word range is an editorial starting point, not a conversion requirement.

A reader should be able to determine fit and understand the next step without searching through a biography or vague promise. Keep proof authentic and terms supportable. The source names Webflow, Carrd, Framer and Notion as page options, with Hyros/Triple Whale only when tracking needs and spend justify them. Using GoHighLevel for this academy does not require adopting those example platforms.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 2.4 — Sales Page / Service Page

**Produces:** A single page on your website (or a one-page Notion/Carrd if you're moving fast) that names the buyer, the pain, the offer, the proof, and the next step. Not a homepage. A targeted page for the specific avatar you're going after.

**Input:** All prior Phase 1 and 2 work.

**How to do it:** Use the long-form direct response structure: hook → problem → why-other-things-fail → mechanism → proof → offer → bonuses (only if real) → guarantee or risk reversal → CTA. Write it once, in their voice. Word count: 800–1,500 for a high-ticket service.

**Done-when criteria:** A cold buyer can read the page and either qualify themselves in (book a call) or qualify out (close the tab). It does both jobs without making them work.

**Common failure modes:** Writing about yourself instead of the buyer. Burying the offer below the fold. Vague CTAs ("Get in touch"). No social proof. No risk reversal.

**AI/tool layer:**
- **Real:** Webflow, Carrd, Framer for fast page hosting. Claude/ChatGPT for copy iteration (it's good at this when you give it Phase 1 buyer language).
- **Useful With Caveats:** Hyros, Triple Whale for tracking — only if your spend justifies it.
- **Mostly Theater:** "AI website builders" that promise full sites in one click. Outputs are generic. Use a template instead.

---

3.1 — Warm Network Outreach

For an authorized warm-network campaign, prepare a four-to-six-sentence personal note explaining the current work, the specific type of introduction requested and a relevant useful gift or reciprocal help. Use the actual relationship rather than generic bulk personalization.

The source proposes sending within seven days, aiming for five-to-fifteen conversations and twenty-to-fifty introductions. Those are targets, not guaranteed results. Track replies and introductions in a simple system, respecting recipients’ choices. Marketing Plan Generator section09 can supply starting scripts to adapt; no messages are sent by producing this lesson.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md · RISER-Marketing-Plan-Generator.html

Complete original step — includes source-era examples and claims corrected above

### Step 3.1 — Warm Network Outreach

**Produces:** 5–15 conversations with people who already know you, plus a list of 20–50 introductions they could make to people you don't know.

**Input:** Phase 1 and 2 assets. Your contact list.

**How to do it:** Write a 4–6 sentence note. Tell them what you're doing now. Ask if they know anyone in your target buyer category. Offer to do something useful for them in return. Send it to everyone you've worked with in the last decade. Include the lead magnet as a gift.

**Done-when criteria:** All notes sent within seven days. Track replies. Track who introduces you. Follow up.

**Common failure modes:** Hiding from this step because asking former colleagues feels needy. (It is not. It is normal professional behavior.) Not having anything specific to ask for. Asking for "any help" instead of "an introduction to anyone you know who handles construction defect cases."

**AI/tool layer:**
- **Real:** Your existing inbox and LinkedIn. Claude/ChatGPT to personalize each outreach note from a base template. Notion or a simple spreadsheet to track responses.
- **Mostly Theater:** Automating warm outreach. The whole point is the personal note.

**Existing RISER artifact:** The **Marketing Plan Generator** outputs a LinkedIn first-touch template, a cold-email template, and a community-reply template in section 09 of every plan it produces. Adapt those for warm context.

---

3.2 — Dream 100 List Building

The Operator’s Flow adaptation creates a list of one hundred named prospective buyers with title, firm, geography, contact route and a specific reason for fit. Its forensic-engineer example allocates25construction-defect attorneys,25insurance-defense attorneys,15subrogation managers,15mechanical-contractor contacts,10property-management contacts and10technical-committee chairs. Require real people rather than only firms.

Its completion targets are seventy verified contact routes and fifty contextual notes. Verification is not consent to contact. The source names Sales Navigator, Apollo, Hunter, PACER, Justia, Clay and a spreadsheet, with dated pricing examples preserved below. Check the actual information source and relevant platform rules before use.

Brunson’s online Dream100 also concerns people or organizations that already reach the audience. Keep that distribution-partner list separate from this direct-prospect adaptation. A partner’s audience fit and a prospect’s buying fit are different qualifications. The Client Acquisition Catalogue supports the source’s example workflow.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md · RISER-Client-Acquisition-Catalog.html · ClickFunnels — Dream 100

Complete original step — includes source-era examples and claims corrected above

### Step 3.2 — Dream 100 List Building

**Produces:** A spreadsheet of 100 named humans in your target buyer category — name, title, firm, geography, contact route, and one specific reason this person fits.

**Input:** Phase 1 buyer definition.

**How to do it:** Use the segment breakdown from the **Client Acquisition Catalog Dream 100 template** (or build your own equivalent). For a forensic engineer that's roughly: 25 construction defect attorneys + 25 insurance defense attorneys + 15 subrogation managers + 15 mechanical contractor GCs + 10 property management firms + 10 technical committee chairs.

For each, find them on LinkedIn (Sales Navigator helps), record their firm, find their email (Apollo, Hunter, or guessable patterns), record one specific thing they do that's relevant. The "one specific thing" prevents your outreach from being generic.

**Done-when criteria:** 100 names. Real ones. Verified contact info for at least 70 of them. Notes column filled in for at least 50.

**Common failure modes:** Listing firm names instead of human names. Stopping at 30 because the list is "good enough" (it isn't — Dream 100 works because of compounding, not because the first 30 are special). Skipping the "one specific thing" column.

**AI/tool layer:**
- **Real:** LinkedIn Sales Navigator ($99/mo). Apollo (free tier or $59/mo). PACER ($0.10/page) for federal court records to identify attorneys handling specific case types. Justia for free legal directory search. A spreadsheet (Google Sheets is fine).
- **Useful With Caveats:** Clay ($149+/mo) if you want enrichment-and-personalization-at-scale workflow. Steep learning curve. Probably overkill until you have 30+ confirmed buyers in pipeline.
- **Mostly Theater:** "AI SDR agents" that build the list and personalize the outreach for you autonomously. They produce volume. Volume is not the bottleneck. Specificity is.

**Existing RISER artifact:** The **Client Acquisition Catalog** has the full tool stack with verified pricing, organized by channel. The Dream 100 template segment-counts are inside the catalog.

**Risks worth flagging:** LinkedIn TOS prohibits most automation. Sales Navigator usage is fine. Tools that auto-message people through LinkedIn risk account suspension and have killed many an outreach plan.

---

3.3 — Dream 100 Outreach Cadence

Plan a relevant follow-up cadence rather than repeating the same pitch. The source suggests six touches over eight weeks across appropriate channels, using a specific signal and placing a lead-resource offer on touch two or three. It also sets a four-touch minimum; distinguish that incomplete minimum from a completed six-touch plan.

One hundred contacts times six touches equals six hundred touches, or fifteen per workday over forty workdays. Responses, opt-outs, appropriateness and actual need change the schedule. The source’s eight-to-fifteen-percent interest rate, below-five-percent rewrite trigger and above-twenty-five-percent luck explanation are unverified planning claims.

Smartlead, Instantly, HubSpot, Pipedrive, Calendly and Lemlist are historical examples, not activated tools. A separate domain or four-to-six-week warmup does not guarantee delivery. Follow the actual sender requirements and authentication setup; Google Workspace can support authentication. Applicable professional-solicitation rules depend on the practice and jurisdiction and need their own review.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md · RISER-Client-Acquisition-Catalog.html · RISER-Marketing-Plan-Generator.html · Google — email sender guidelines

Complete original step — includes source-era examples and claims corrected above

### Step 3.3 — Dream 100 Outreach Cadence

**Produces:** First-touch messages sent to all 100 people, follow-up sequence executed, conversations started.

**Input:** Step 3.2 list. Step 2.3 lead magnet.

**How to do it:** Six-touch cadence over 8 weeks. Mix LinkedIn, email, and (where appropriate) phone. Each touch is short, specific, value-first. Open with the "one specific thing" you noted. Reference a real signal — they posted something, their firm just took on a relevant case, an industry event happened. Lead-magnet offer can come on touch 2 or 3, never touch 1.

Run the cadence as a deliberate practice. 15 outreach touches per workday is the right volume for a solo professional. More than that and quality drops. Less than that and momentum dies.

**Done-when criteria:** All 100 people have received at least four touches across 8 weeks. Conversation rate of 8–15% (8–15 named people responded with interest) is normal. Less than 5% means the message is wrong; rewrite. More than 25% means the targeting got lucky; verify before scaling.

**Common failure modes:** Sending touch 1 to all 100 then giving up when 92 ignore you. (The compounding is in touches 3–6.) Generic copy that ignores the "one specific thing." Pitching the offer on touch 1.

**AI/tool layer:**
- **Real:** Smartlead or Instantly ($39–94/mo) for cold-email infrastructure (deliverability matters). HubSpot CRM Free or Pipedrive ($25/seat) for tracking touches. Calendly for booking the calls that result.
- **Useful With Caveats:** Lemlist ($59+/mo) — premium worth it only if you actually use the personalization features. Otherwise overpriced versus Smartlead.
- **Mostly Theater:** Cold-outreach AI that generates "100% personalized" messages. The personalization is shallow. Buyers can tell. Better to send fewer messages with real personalization than more with fake.

**Risks:** Email deliverability. Sending 100 cold emails from a fresh domain will land you in spam folders. Use a separate sending domain, warm it up over 4–6 weeks, follow SPF/DKIM/DMARC standards. Smartlead handles this; sending from your business Gmail does not.

For licensed professionals: state bar associations and professional licensing boards have rules about solicitation. Consult yours before launching cold outreach. Some states prohibit certain cold-contact patterns for attorneys, doctors, and engineers in regulated practice.

---

3.4 — Content Distribution Cadence

Select the channel where evidence shows relevant buyers spend attention. The source prefers LinkedIn for its professional-services example, but do not assume it is always the right channel. Begin with one manageable cadence rather than distributing identical material everywhere.

Its twelve-week plan uses Monday pain posts of150–300words, Wednesday mechanism posts of200–400, and Friday case/proof posts of250–500. Use actual observations, a specific technical idea and sanitized evidence. Track qualified responses as well as reach; the assertion that most buyers silently follow for eight weeks is not established.

The source names AI drafting, Buffer/Hypefury scheduling, Notion planning and Repurpose.io/OpusClip for existing long-form material. Evaluate accuracy, voice and time saved on your own work. Claimed thirty-to-fifty-percent editing savings are not guaranteed, and AI can assist reasoning without replacing accountable expert judgment. Marketing Plan Generator sections03/04/06/07 inform channel and content planning.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md · RISER-Marketing-Plan-Generator.html

Complete original step — includes source-era examples and claims corrected above

### Step 3.4 — Content Distribution Cadence

**Produces:** A consistent, multi-month flow of content on the platform(s) your buyers actually inhabit, building credibility while warm and Dream 100 outreach runs in parallel.

**Input:** Phase 1 pain doc. Phase 2 positioning. Knowledge of where buyers actually gather.

**How to do it:** Pick *one* primary platform. For high-ticket professional services in 2026, that's almost always LinkedIn. Possibly an industry-specific publication (ABA Journal, ASHRAE Journal, etc.) for the highest-credentialing-value plays. Don't multi-platform until the primary one is producing.

The content cadence framework that works:

- **Monday — Pain post.** A real piece of buyer pain, observed or quoted, with your take. 150–300 words.
- **Wednesday — Mechanism post.** A specific technical observation or framework, in your area of expertise. 200–400 words. This is the "I know things" post.
- **Friday — Case study or proof.** A sanitized story from your work, or a public case dissected. 250–500 words.

Three posts a week. Same days. Same time. For 12 weeks before evaluating. The discipline matters more than the volume — buyers notice consistency over six months.

**Done-when criteria:** 12 weeks of consistent posting. Engagement metrics matter less than reach growth and the qualitative feedback that comes in (DMs, comments, lurkers reaching out). The right buyers reading you silently for 8 weeks before contacting you is the dominant pattern.

**Common failure modes:** Multi-platforming too early (LinkedIn + X + Instagram + TikTok). Posting whenever you "feel inspired" instead of on cadence. Generic "thought leadership" posts that aren't grounded in real buyer pain. Stopping after three weeks because results aren't visible.

**AI/tool layer:**
- **Real:** Claude/ChatGPT to draft and refine post copy from your raw notes. Buffer or Hypefury for scheduling. Notion for content calendar.
- **Useful With Caveats:** Repurpose.io, OpusClip for converting long-form (podcast, video) into short-form social posts. Useful if you're already producing long-form. Theater if you're not.
- **Mostly Theater:** AI tools that "generate a year of content in 10 minutes." The output is generic. It does not move buyers. Worse, it identifies you as someone using AI to generate content, which actively damages credibility for high-ticket professional services. This is **Identity Commoditization** in action — see the Closing section for the full framing of why generic AI output collapses your price floor.

**The honest tradeoff:** AI can save 30–50% of your time on the *editing* and *formatting* layer. It cannot save time on the *thinking* layer. The thinking is the work. If you're using AI to skip the thinking, you're skipping the value.

---

3.5 — Paid Channels (Defer Until Earned)

Use paid distribution when an offer and a measured conversion path justify the risk. The source proposes ten closed clients, a six-to-twelve-month delay and sixty days of observed performance; those are its heuristics, not universal requirements. Choose one appropriate platform, set a real spending limit and identify how losses will be detected.

Compare acquisition cost with a clearly defined contribution-based LTV and cash-payback window. The source’s stop condition CAC greater than0.33timesLTV can hide losses if LTV is gross revenue without service costs or retention evidence. Google, LinkedIn and Meta are possible channels, not purchases authorized by this course. Native optimization and third-party tracking still need qualified review.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 3.5 — Paid Channels (Defer Until Earned)

**Produces:** Scaled distribution of proven content/offers, after warm and Dream 100 outreach have produced consistent close signal.

**Input:** Steps 3.1–3.4 producing measurable conversation rate, close rate, and lifetime value data. You need at least 10 closed clients before you have any business spending on paid ads.

**How to do it:** This step is deferred for most professional service operators for 6–12 months. The reason: high-ticket service buyers don't typically respond to paid ads the way e-commerce buyers do. Your CAC math has to work, and it usually doesn't until you've validated the funnel manually.

When you do enter paid: start with one platform (LinkedIn ads if your buyer is on LinkedIn; Google Search if they search for your category; Meta only if your buyer demographic is verified active there). Set a hard monthly cap. Track CAC and LTV explicitly. Cut spend the moment CAC > 0.33 × LTV.

**Done-when criteria:** Active paid channel with measurable CAC under your threshold and predictable conversion rate over a 60-day window.

**Common failure modes:** Running paid before manual outreach has validated message-market fit. Boosting LinkedIn posts (almost never worth it for high-ticket B2B). Treating paid as a substitute for organic instead of an amplifier of organic.

**AI/tool layer:**
- **Real:** Native ad platforms. Hyros or Triple Whale for tracking only if spend justifies it.
- **Mostly Theater:** "AI ad optimizer" tools that promise to manage your campaigns. The platforms' built-in optimization is now better than most third-party tools.

---

4.1 — Client Onboarding SOP

Map the period from signed agreement to first delivery. Prepare welcome communication, kickoff agenda, information checklist, folder template, agreed contact cadence and payment workflow. Use the SOW and actual experience from early engagements to identify missing inputs before they block delivery.

Aim for a repeatable first fourteen days while allowing necessary client-specific judgment. The source’s claim that setup costs a day and saves a day every time is an estimate. Notion, Process Street, Loom, Calendly, PandaDoc, Bonsai and HoneyBook are examples of support tools; automate appropriate reminders without substituting automation for relationship responsibility.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 4.1 — Client Onboarding SOP

**Produces:** A documented, repeatable process for taking a signed client from "yes" to "first deliverable" without anything falling through the cracks.

**Input:** Phase 1 SOW template. Your delivery process from your first three engagements.

**How to do it:** Document the process. Welcome email template. Kickoff-call agenda. Information-gathering checklist. Project-folder template. Communication-cadence agreement. Payment-collection workflow. The first time you do this it takes a day. Every time after that it saves a day.

**Done-when criteria:** A new client signs and the first 14 days run identically each time, with no email you have to write from scratch and no question you have to look up.

**Common failure modes:** Reinventing the onboarding for each client. Not having a kickoff agenda. Forgetting to invoice. Missing the information-gathering step and getting blocked mid-engagement.

**AI/tool layer:**
- **Real:** Notion or Process Street for SOP storage. Loom for recording explainer videos once and reusing them. Calendly for scheduling. PandaDoc or Bonsai for contract+invoice infrastructure.
- **Useful With Caveats:** Bonsai or HoneyBook for end-to-end client management — useful if you want one tool, costlier than piecing tools together.
- **Mostly Theater:** AI "client onboarding agents." Onboarding is relationship-building. Automate the *reminders* and *templates*; do the relationship work yourself.

---

4.2 — Delivery SOP

Document delivery phases, artifact templates, quality checks, internal review, time tracking, communication and offboarding. Technical work also needs defensible source citations and credential context. Have a reviewer check the actual promised outcome rather than simply the presence of a template.

Measure hours across comparable engagements. The source’s thirty-to-fifty-percent second-run saving is a goal to test, not proof of completion. Notion/Confluence, Toggl/Harvest, drafting tools and Tana/Reflect/Mem are examples with different tradeoffs. Repeated work can be assisted, but qualified responsibility for the final service remains.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 4.2 — Delivery SOP

**Produces:** A documented, repeatable process for delivering the actual service, from start of engagement to final deliverable to client offboarding.

**Input:** Step 4.1 onboarding output. Your delivery method from prior work.

**How to do it:** Document each phase of delivery. Templates for each artifact you produce. Quality checklists. Internal review steps. Time-tracking convention. Client communication touchpoints. For technical work (forensic engineering, expert witness reports), include the credentialing-and-citation discipline that protects your work product from challenge.

**Done-when criteria:** A new engagement of the same type as a prior engagement takes 30–50% less time on the second iteration than the first, because the templates and checklists carry the load.

**Common failure modes:** No quality checklist (every deliverable is bespoke and inconsistent). No time tracking (you discover after-the-fact you priced wrong). No internal review step (errors ship to client).

**AI/tool layer:**
- **Real:** Notion or Confluence for SOP storage. Toggl or Harvest for time tracking. Claude/ChatGPT for first-draft generation of report sections that have known patterns.
- **Useful With Caveats:** Tana, Reflect, Mem for AI-assisted note-taking. Genuinely useful for knowledge capture across many engagements. Learning curve is real.
- **Mostly Theater:** AI tools that promise to "automate your delivery." If your service is high-ticket, the delivery is the value. Don't automate the value.

---

4.3 — Knowledge Management

After each engagement, spend a short scheduled period capturing reusable successful work: approved report structures, effective messages, useful explanations, objections and sanitized case examples. The source suggests thirty minutes, consistent tags and retrieval of a relevant example within sixty seconds.

Avoid both an empty archive and an indiscriminate pile. Use descriptive naming, permissions and a clear distinction between reusable templates and confidential client records. Notion, Obsidian, Tana, Mem and Reflect are example systems, not required subscriptions. Starting sixty-percent complete after a year is an unverified expectation; measure reuse quality and actual time saved.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 4.3 — Knowledge Management

**Produces:** A growing internal library of every successful artifact (winning emails, approved report sections, effective objection responses, sanitized case examples) organized for fast retrieval and reuse.

**Input:** Every client engagement, ongoing.

**How to do it:** After each engagement, spend 30 minutes capturing what worked. Tag it. File it. Make it findable. Within 12 months you have a "winners library" that compounds — each new engagement starts 60% complete because templates exist.

**Done-when criteria:** When starting any new artifact, you can find at least one prior version to start from in under 60 seconds.

**Common failure modes:** Capturing nothing (everything is rebuilt from scratch). Capturing everything (the library is too big to navigate). No tagging convention.

**AI/tool layer:**
- **Real:** Notion or Obsidian. Tana for advanced relational tagging. Search-friendly file naming.
- **Useful With Caveats:** Mem.ai, Reflect — AI-native note systems. Promising; learning curve and lock-in risk.

---

4.4 — Tech Stack Hygiene

Maintain one inventory of tools, purposes, costs, owners/access, data held and review dates. Review quarterly, identify redundant systems and verify the handling of sensitive client information. Cancellation decisions must account for exports, retention and ongoing access commitments.

The source uses examples of duplicated$30–$100subscriptions, eight-to-fifteen tools and dedicated SaaS management above$2,000monthly spend. Those are illustrative, not necessary thresholds. A spreadsheet may be enough; choose more tooling only when the actual inventory and responsibility justify it.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 4.4 — Tech Stack Hygiene

**Produces:** A documented inventory of every tool you use, what it does, what it costs, who has access, what data it holds, and when it's reviewed for replacement or cancellation.

**Input:** All your existing subscriptions and tools.

**How to do it:** One spreadsheet. Quarterly review. Cancel anything not actively used. Note any tool with sensitive client data (CRM, file storage, email infrastructure) and verify their security posture.

**Done-when criteria:** No surprise charges. No forgotten tools. No "wait, where did I store that file?" moments.

**Common failure modes:** Tool sprawl. Three CRMs, two email-marketing platforms, four file-storage services. Each one $30–100/month, none of them used fully.

**AI/tool layer:**
- **Real:** Just a spreadsheet. Vertice or Cledara if your tool spend exceeds $2K/month and you want active SaaS management.
- **Mostly Theater:** "AI-driven tech stack auditors." Most professional service operators have 8–15 tools, not 80. A spreadsheet review takes an hour.

---

5.1 — Monthly Metrics Review

Review eight actionable measures: conversations started, qualified opportunities, sales won, average deal value, lifetime value, acquisition cost, hours per engagement and revenue per hour. Define the cohort, time window and data source for each so the comparisons mean the same thing month to month.

The source schedules thirty minutes on the first Monday of the month and requires one decision from the review. Record the reason and follow-up date. CRM, accounting, email, time-tracking and payment reports are inputs, not automatically consistent definitions. A dashboard is useful when it changes a decision and the evidence is trustworthy.

For an authored measurement example, suppose a defined cohort has twenty conversations, eight qualified opportunities and two won engagements. Opportunity rate is eight divided by twenty, or forty percent; opportunity-to-win rate is two divided by eight, or twenty-five percent. Two wins divided by twenty conversations is ten percent and answers a different question. Record the stage definitions so those rates are not accidentally compared.

If those two engagements generate $4,000 of collected revenue and take forty delivery hours, the cohort averages $2,000 collected revenue per engagement and $100 per delivery hour. Revenue per hour is not profit per hour and excludes prospecting, administration and unpaid support unless those hours are included explicitly. If attributable acquisition spending is $600, acquisition cost is $300 per new client under that cost definition; add relevant labor or other costs when the intended measure includes them. Lifetime value requires retention and contribution evidence beyond this example.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 5.1 — Monthly Metrics Review

**Produces:** A one-page dashboard reviewed once per month showing the metrics that matter for your business.

**Input:** Data from your CRM, your email tool, your accounting, your time-tracking.

**How to do it:** Track only the metrics you can actually act on. For most professional service operators that's: number of conversations started, number of qualified opportunities, number closed, average deal value, lifetime value, CAC, hours per engagement, revenue per hour. Eight numbers. Review monthly. Note trends.

**Done-when criteria:** First Monday of every month, the dashboard is updated, you've spent 30 minutes reviewing it, you've decided one thing to change based on what it says.

**Common failure modes:** Tracking 40 metrics (paralysis). Tracking vanity metrics (LinkedIn impressions). Reviewing the dashboard but never changing anything based on it.

**AI/tool layer:**
- **Real:** Google Sheets. Notion databases. HubSpot or Pipedrive reports. Stripe dashboard for revenue.
- **Mostly Theater:** "AI-powered analytics dashboards" with 50 widgets and no actionable insight.

---

5.2 — Quarterly Buyer Feedback

Ask recent clients what worked, what disappointed them, what they would change and what they might need next. Include varied outcomes rather than only enthusiastic clients. Obtain appropriate permission before recording and preserve genuine language and context.

The source promises at least five clients but schedules four thirty-minute calls. For this exercise, plan at least five interviews and mark that as the resolution of the conflict. Feed recurring observations into the offer, content and delivery process. Otter, Fathom, Granola and AI synthesis are optional aids; check the synthesis against the actual record.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 5.2 — Quarterly Buyer Feedback

**Produces:** Direct conversation with at least 5 recent clients each quarter, capturing what worked, what didn't, what they'd change, and what they'd buy next.

**Input:** Your client list.

**How to do it:** Schedule four 30-minute calls per quarter with recent clients. Open-ended questions. Record (with permission). Capture verbatim quotes. Look for patterns across calls.

**Done-when criteria:** Every quarter, you have new buyer language and new insights flowing back into your offer, content, and SOPs.

**Common failure modes:** Skipping these calls because they feel awkward to ask for. Asking only people who liked you (selection bias). Hearing feedback and not acting on it.

**AI/tool layer:**
- **Real:** Otter.ai, Fathom, Granola for transcription. Claude/ChatGPT to synthesize themes across transcripts.

---

5.3 — A/B Testing (Earned)

Before an A/B test, define the hypothesis, primary metric, allocation, meaningful effect size and stopping rule. Change one intended factor when a controlled comparison is feasible and log exactly what ran. Baseline conversion, sample size and uncertainty determine whether the test can distinguish useful effects.

The source’s thousand-visits-per-month threshold does not establish statistical power by itself. A four-week cap may end inconclusively; do not pick a winner simply because time expired or an ordinary significance test briefly crossed a threshold. Four tests per year is a planning cadence, not a universal requirement. Native tools, VWO and Optimizely are examples whose current capabilities and cost need checking.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 5.3 — A/B Testing (Earned)

**Produces:** Continuous optimization of your highest-volume marketing assets — sales page, lead magnet, email subject lines, ad creative — based on real conversion data.

**Input:** Sufficient traffic volume to actually have statistical significance. For most professional service operators this means 1,000+ page visits per month per asset. Below that, A/B testing is theater.

**How to do it:** Test one variable at a time. Define hypothesis upfront. Run until significance (or 4 weeks max). Document the result. Apply the winner. Move to the next test.

**Done-when criteria:** Each high-volume asset has been through at least 4 deliberate test cycles per year.

**Common failure modes:** Testing without enough traffic (you'll get random noise). Testing too many variables at once. Calling a test winner before it reaches significance. Forgetting which variant won and why.

**AI/tool layer:**
- **Real:** Native A/B in your email tool, ad platform, and CMS (most have it built-in). VWO, Optimizely if you have real volume.
- **Mostly Theater:** AI-driven "auto-optimization." Useful at scale (Meta, Google ads platforms run their own); the third-party "AI testing agents" mostly recreate functionality the platforms already have.

---

5.4 — Offer and Positioning Refresh

At least annually, reserve focused time to revisit the buyer, problem, positioning, delivery capability and price. Bring actual metrics, varied client feedback and changed alternatives. Decide which elements remain, which need a supported revision and which should retire.

Record the new operating hypothesis and its evidence. Do not change an offer merely because its creator is bored, or retain it merely because it once worked. A full day is the source’s suggested format; the essential output is an explicit decision connected to evidence.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 5.4 — Offer and Positioning Refresh

**Produces:** Annual review of your core offer, positioning, pricing, and target buyer. Either confirmation that it's still right, or deliberate evolution.

**Input:** Phase 5 metrics. Quarterly buyer feedback. Competitive landscape changes.

**How to do it:** Once a year, block a full day. Review your Phase 1 documents. Are they still accurate? Has the buyer pain shifted? Has your delivery capability evolved? Is your pricing still right? Decide what to keep, what to evolve, what to retire.

**Done-when criteria:** End of each year, you have an explicit decision: "this is still the offer for next year" or "here is what changes."

**Common failure modes:** Skipping the annual review. Refreshing the offer without buyer feedback to support it. Refreshing for vanity reasons (you got bored) instead of strategic ones.

---

5.5 — Scale Decision

Choose whether to deepen the current niche, serve an adjacent niche or remain a solo practice. The source uses eighteen-plus months of data as its review horizon, but urgent capacity or market changes may require decisions sooner. Write what role you want and the criteria for reconsidering the choice.

More clients in the same niche may require trained associates, documented delivery and quality oversight. An adjacent niche needs a new problem/fit pilot rather than an assumed transfer of demand. Staying solo may justify a price or scope change when value, capacity and demand support it; it does not automatically require a price increase. Avoid drifting into hiring without choosing responsibilities and verifying the work system.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Complete original step — includes source-era examples and claims corrected above

### Step 5.5 — Scale Decision

**Produces:** A deliberate choice about whether to scale vertically (more clients in same niche), horizontally (same offer in adjacent niches), or stay solo.

**Input:** 18+ months of operating data. Honest self-assessment of what you actually want.

**How to do it:** This decision is more about you than about the business. Some operators want to stay a solo expert with high margins and short hours. Some want to build a firm. Both are legitimate. The mistake is drifting into one without choosing.

If scaling vertically: hire associate practitioners, document delivery extensively, develop training for them, plan for quality control. If scaling horizontally: pilot the new niche before committing, treat it as Phase 1 again from scratch. If staying solo: raise prices.

**Done-when criteria:** Explicit written decision with criteria for revisiting.

**Common failure modes:** Drifting into scaling because it sounds like success. Hiring before SOPs are documented (chaos compounds). Hiring before you've explicitly chosen what role you want.

---

Run the five feedback loops

Monthly metrics prompt renewed pain research, but falling conversion can also reflect lead mix, technical problems or capacity. Quarterly buyer feedback informs the magnet, service page and offer. Test results update assets and content. The approved knowledge library supplies useful examples and future lead resources. Annual review revisits the foundation. Schedule these loops and record the evidence behind each change.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Preserve a distinctive practice

The source calls converging generic output identity commoditization: buyers struggle to see meaningful differences when providers use interchangeable claims. Keep your own judgment, credible experience and actual evidence visible. Use authorized contextual examples to improve AI-assisted work; do not expose confidential reports, case identifiers, site photographs or client information merely to sound specific.

Its five defenses are personal thinking, a contextual archive, particular care with high-stakes artifacts, evidence of real work and quarterly comparison of three own messages with three competitor messages. Treat these as quality disciplines, not proof that AI cannot help reasoning or that every AI draft damages credibility. A qualified person must verify consequential final work.

Supporting sources: RISER-Operators-Flow.html · RISER-Operators-Flow.md

Exercise and completion check

Choose your current step. Produce its named output, identify the source evidence, record what remains uncertain and set the next review date. Explain how that output supplies the next phase. A finished checklist is not proof of market demand; buyer evidence and responsible delivery determine the next action.

Complete original Markdown source

Full source including every tool example, phase explanation and artifact map

# RISER Operator's Flow

## A structural skeleton for building, marketing, and scaling a high-ticket professional services business — phase by phase, step by step, with the actual work named honestly.

---

**Version 1 · April 2026 · Captain's Logic Operating Doctrine**

This document is the spine. It tells you what stages exist, what order they go in, what each one produces, what could go wrong, and where the existing RISER widgets fit. Use it as a checklist on any given Tuesday — "I'm at Phase 2, Step 3, here is the next concrete deliverable" — not as a vision document to read once and forget.

The framework covers five phases, eighteen steps, and one continuous feedback loop. Phases roughly correspond to weeks 1–4 (Phase 1), 5–8 (Phase 2), 9–12 (Phase 3), and 13+ (Phases 4 and 5, which are continuous from launch onward). A solo operator can complete Phase 1 in seven days if they are disciplined; most take longer because Phase 1 is where the real thinking happens and skipping it makes everything downstream harder.

Three honest framings before you start:

**This is not a get-rich-quick plan.** It is a working operator's plan. The fastest result you will see from doing this correctly is a real client conversation in week three. The first paying client typically lands in week six to ten. Operators who expect faster usually skipped Phase 1.

**Most "AI agents" mentioned in marketing-stack content are aspirational.** The agent layer in 2026 is mostly real for narrow, well-bounded jobs: drafting first replies a human approves, pulling structured data from PDFs, summarizing call transcripts, routing leads to the right sequence. It is mostly hype for unbounded creative or strategic work. Throughout this document, tools are graded **Real**, **Useful With Caveats**, or **Mostly Theater**. Use the Real ones, treat the second category with measurement, skip the third.

**The risks that will actually bite an operator are not the ones marketing content discusses.** Reddit API access can change overnight (GummySearch shut down in November 2025 when Reddit denied API access). LinkedIn's automation crackdowns kill outreach tools regularly. Email deliverability collapses under cold-volume sends. State bar associations and professional licensing boards have rules about AI-personalized outreach that can endanger your license if violated. These risks are flagged inside each step where they apply.

---

## Phase 1 — Foundation

### What this phase produces

A validated business hypothesis you can defend with evidence, an offer that solves a pain people actually have, and a minimum viable version you can sell next week. Not a finished product. Not a polished brand. A defensible *bet* with a known kill criterion.

### Why it matters

Operators who skip this phase end up in Phase 3 (traffic generation) trying to drive volume to a thing nobody clearly wants. They compensate with bigger ad spend, more outreach, more content. None of it works because the offer is wrong. Phase 1 is unglamorous and slow. It is also the highest-leverage week of the entire build.

---

### Step 1.1 — Idea Capture

**Produces:** A one-paragraph statement of the business or service idea, who you think it serves, and what specific problem you think it solves.

**Input:** Your existing skills, prior work, professional credentials, and the rough hypothesis you're entering with.

**How to do it:** Write the paragraph by hand on paper. Two hundred words. Include the buyer (one sentence), the problem (one sentence), the solution (one sentence), the price tier (one sentence), and what makes you specifically the right person to deliver it (one sentence). The constraint forces clarity.

**Done-when criteria:** A literate friend can read the paragraph once and explain back to you what your business does, who it's for, and why someone would pay you. If they can't, rewrite.

**Common failure modes:** Writing in jargon. Listing features instead of outcomes. Defining the buyer too broadly ("small business owners" instead of "construction defect attorneys at mid-sized firms in Arizona"). Hiding behind credentials instead of describing what you actually do for clients.

**AI/tool layer:** None needed at this step. **Mostly Theater** if you're using AI to "validate" the idea here — the model will tell you almost any idea sounds promising. Save the validation work for Step 1.3.

**Iteration trigger:** Phase 5 customer feedback that contradicts your stated buyer or problem. Rewrite this paragraph quarterly.

---

### Step 1.2 — Pain Discovery

**Produces:** A document with three to five real pain points your buyer experiences, written in their own language, with evidence sources. Not pain you assume they have. Pain they say out loud.

**Input:** The Step 1.1 paragraph. Your hypothesis about who the buyer is.

**How to do it:** Three parallel research tracks, run for one week:

**Iteration trigger:** Quarterly. Buyer pain shifts as their context shifts (regulatory changes, economic conditions, technology shifts). The doc you wrote in Q1 needs revision by Q3.

---

### Step 1.3 — Offer Hypothesis

**Produces:** A specific named offer — what you sell, what it costs, what the buyer gets, what they walk away from the call with — that maps directly to the pain you found.

**Input:** Step 1.2 pain document. Your skills inventory.

Decide on a named mechanism. Not "I do forensic engineering" — "The 14-Day VRF Failure Forensic Audit." Specific deliverable, specific timeframe, specific outcome.

**Done-when criteria:** You can describe the offer in 30 seconds, name the price, name the deliverable timeline, name your kill criterion, and a literate friend can repeat it back accurately.

**Iteration trigger:** First five buyer conversations. If buyers don't immediately understand the offer or push back hard on price, restructure.

---

### Step 1.4 — MVP / Service Definition

**Input:** Step 1.3 offer document.

**Done-when criteria:** You have an SOW you could send to a buyer this afternoon. It defines scope so clearly that you know in advance what you're delivering and so does the buyer.

**Iteration trigger:** After the first three engagements. You will discover scope leaks and SOW gaps you didn't anticipate. Update the template.

---

## Phase 2 — Positioning and Asset Build

### What this phase produces

The artifacts a buyer encounters before they buy from you. Brand, message, lead magnet, sales page, proof. Not all of them at once — the minimum credible set.

### Why it matters

Phase 1 gave you a defensible offer. Phase 2 gives buyers a way to evaluate you without talking to you first. For high-ticket professional services, where buyers research at 11pm before deciding who to contact, the asset layer is what gets you on the consideration list. Skip it and you're invisible.

### Honest framing on this phase

You don't need a $5,000 logo. You don't need a 12-page brand bible. You don't need a hand-photographed headshot. You need the minimum credible set, deployed within a week, and you need to spend the saved time on Phase 3 outreach. Operators stall here because polishing assets feels productive. It is not. It is procrastination dressed as work.

---

### Step 2.1 — Competitive Intelligence

**Input:** Phase 1 work. Knowledge of who else serves your buyer.

**Done-when criteria:** You can name in one sentence per competitor what's strong about their positioning and what's weak. You have an explicit "we're different from them because..." for each.

**Iteration trigger:** Quarterly. Competitor offers and positioning shift; your matrix needs refresh.

---

### Step 2.2 — Brand & Asset Minimum Viable Set

**Produces:** A logo (or wordmark), one professional headshot, a one-page bio, a defined color palette, and a one-page service overview document. That's the minimum. Nothing more until you've closed five clients.

**Input:** Phase 1 work. Your existing materials.

**How to do it:** Use Canva or Figma. Pay $200–$500 for a wordmark on Fiverr or 99designs if you want polish. Get a real headshot — phone-camera selfie quality is fine for LinkedIn but not for an expert witness directory listing. Write the one-page bio in third person, including your specific credentials, three concrete prior accomplishments (sanitized if needed), and a clear statement of who you serve.

**Done-when criteria:** You have a presentable LinkedIn profile, a presentable directory listing draft, and a service overview PDF you can email to a prospect.

**Common failure modes:** Spending three weeks on a logo. Hiring a brand strategist before you have buyers. Writing the bio in language that sounds like every other consultant's bio.

**AI/tool layer:**
- **Real:** Canva ($15/mo) for fast asset production. Claude/ChatGPT to draft and polish the bio. Looka for $50 wordmark generation if you can't decide what you want.
- **Mostly Theater:** AI-generated "brand identity systems." Looks impressive, costs significant time, doesn't move buyers. Save brand investment for after you have customer feedback.

---

### Step 2.3 — Lead Magnet (Gift First)

**Input:** Phase 1 pain doc. Knowledge of buyer's specific decision moments.

**Done-when criteria:** A buyer who downloads this asset finds it genuinely useful and would tell a colleague about it. You've tested this with two real buyers before launch.

**Common failure modes:** Generic "10 tips for X" content. Disguised pitch decks. Asset is too long (40 pages = won't be read) or too short (one tip = not worth the email).

**Existing RISER artifact:** The **Marketing Plan Generator** generates a specific lead-magnet recommendation for any profession+avatar combination as section 05 of every plan.

---

### Step 2.4 — Sales Page / Service Page

**Produces:** A single page on your website (or a one-page Notion/Carrd if you're moving fast) that names the buyer, the pain, the offer, the proof, and the next step. Not a homepage. A targeted page for the specific avatar you're going after.

**Input:** All prior Phase 1 and 2 work.

**How to do it:** Use the long-form direct response structure: hook → problem → why-other-things-fail → mechanism → proof → offer → bonuses (only if real) → guarantee or risk reversal → CTA. Write it once, in their voice. Word count: 800–1,500 for a high-ticket service.

**Done-when criteria:** A cold buyer can read the page and either qualify themselves in (book a call) or qualify out (close the tab). It does both jobs without making them work.

**Common failure modes:** Writing about yourself instead of the buyer. Burying the offer below the fold. Vague CTAs ("Get in touch"). No social proof. No risk reversal.

**AI/tool layer:**
- **Real:** Webflow, Carrd, Framer for fast page hosting. Claude/ChatGPT for copy iteration (it's good at this when you give it Phase 1 buyer language).
- **Useful With Caveats:** Hyros, Triple Whale for tracking — only if your spend justifies it.
- **Mostly Theater:** "AI website builders" that promise full sites in one click. Outputs are generic. Use a template instead.

---

## Phase 3 — Acquisition

### What this phase produces

Real buyer conversations. Not awareness. Not "thought leadership." Conversations with named humans who could pay you, where they say yes, no, or "tell me more."

### Why it matters

Everything in Phases 1 and 2 is unfalsifiable until Phase 3 puts it in front of buyers. Operators who linger in 1 and 2 are usually avoiding the discomfort of 3. The cure is to launch publicly before you feel ready, then let real feedback drive the iterations.

### The order matters

For high-ticket professional services, run these channels in this order. Don't run them in parallel until each is proven.

1. **Warm outreach** to your existing network (week one)
2. **Dream 100 cold outreach** to named humans in your target market (week two)
3. **Content distribution** on the platforms your buyers actually use (ongoing from week one)
4. **Paid ads** only after channels 1–3 produce signal

---

### Step 3.1 — Warm Network Outreach

**Produces:** 5–15 conversations with people who already know you, plus a list of 20–50 introductions they could make to people you don't know.

**Input:** Phase 1 and 2 assets. Your contact list.

**How to do it:** Write a 4–6 sentence note. Tell them what you're doing now. Ask if they know anyone in your target buyer category. Offer to do something useful for them in return. Send it to everyone you've worked with in the last decade. Include the lead magnet as a gift.

**Done-when criteria:** All notes sent within seven days. Track replies. Track who introduces you. Follow up.

**Common failure modes:** Hiding from this step because asking former colleagues feels needy. (It is not. It is normal professional behavior.) Not having anything specific to ask for. Asking for "any help" instead of "an introduction to anyone you know who handles construction defect cases."

**AI/tool layer:**
- **Real:** Your existing inbox and LinkedIn. Claude/ChatGPT to personalize each outreach note from a base template. Notion or a simple spreadsheet to track responses.
- **Mostly Theater:** Automating warm outreach. The whole point is the personal note.

**Existing RISER artifact:** The **Marketing Plan Generator** outputs a LinkedIn first-touch template, a cold-email template, and a community-reply template in section 09 of every plan it produces. Adapt those for warm context.

---

### Step 3.2 — Dream 100 List Building

**Produces:** A spreadsheet of 100 named humans in your target buyer category — name, title, firm, geography, contact route, and one specific reason this person fits.

**Input:** Phase 1 buyer definition.

**Done-when criteria:** 100 names. Real ones. Verified contact info for at least 70 of them. Notes column filled in for at least 50.

**Existing RISER artifact:** The **Client Acquisition Catalog** has the full tool stack with verified pricing, organized by channel. The Dream 100 template segment-counts are inside the catalog.

---

### Step 3.3 — Dream 100 Outreach Cadence

**Produces:** First-touch messages sent to all 100 people, follow-up sequence executed, conversations started.

**Input:** Step 3.2 list. Step 2.3 lead magnet.

Run the cadence as a deliberate practice. 15 outreach touches per workday is the right volume for a solo professional. More than that and quality drops. Less than that and momentum dies.

---

### Step 3.4 — Content Distribution Cadence

**Produces:** A consistent, multi-month flow of content on the platform(s) your buyers actually inhabit, building credibility while warm and Dream 100 outreach runs in parallel.

**Input:** Phase 1 pain doc. Phase 2 positioning. Knowledge of where buyers actually gather.

The content cadence framework that works:

Three posts a week. Same days. Same time. For 12 weeks before evaluating. The discipline matters more than the volume — buyers notice consistency over six months.

---

### Step 3.5 — Paid Channels (Defer Until Earned)

**Produces:** Scaled distribution of proven content/offers, after warm and Dream 100 outreach have produced consistent close signal.

**Input:** Steps 3.1–3.4 producing measurable conversation rate, close rate, and lifetime value data. You need at least 10 closed clients before you have any business spending on paid ads.

**Done-when criteria:** Active paid channel with measurable CAC under your threshold and predictable conversion rate over a 60-day window.

---

## Phase 4 — Operations and Delivery

### What this phase produces

The systems that let you deliver promised outcomes consistently, capture knowledge from every engagement, and maintain quality as volume increases. SOPs, templates, knowledge management, and the boring infrastructure that prevents the business from collapsing under its own success.

### Why it matters

Phase 3 will produce clients faster than you expect once it works. Operators without Phase 4 systems compound chaos with every new client. Within six months they're working 70-hour weeks, dropping deliverables, and the original positioning erodes.

This phase runs in parallel with Phase 3 from the moment your first client signs. Don't wait until you're overwhelmed to start.

---

### Step 4.1 — Client Onboarding SOP

**Produces:** A documented, repeatable process for taking a signed client from "yes" to "first deliverable" without anything falling through the cracks.

**Input:** Phase 1 SOW template. Your delivery process from your first three engagements.

**How to do it:** Document the process. Welcome email template. Kickoff-call agenda. Information-gathering checklist. Project-folder template. Communication-cadence agreement. Payment-collection workflow. The first time you do this it takes a day. Every time after that it saves a day.

**Done-when criteria:** A new client signs and the first 14 days run identically each time, with no email you have to write from scratch and no question you have to look up.

**Common failure modes:** Reinventing the onboarding for each client. Not having a kickoff agenda. Forgetting to invoice. Missing the information-gathering step and getting blocked mid-engagement.

**AI/tool layer:**
- **Real:** Notion or Process Street for SOP storage. Loom for recording explainer videos once and reusing them. Calendly for scheduling. PandaDoc or Bonsai for contract+invoice infrastructure.
- **Useful With Caveats:** Bonsai or HoneyBook for end-to-end client management — useful if you want one tool, costlier than piecing tools together.
- **Mostly Theater:** AI "client onboarding agents." Onboarding is relationship-building. Automate the *reminders* and *templates*; do the relationship work yourself.

---

### Step 4.2 — Delivery SOP

**Produces:** A documented, repeatable process for delivering the actual service, from start of engagement to final deliverable to client offboarding.

**Input:** Step 4.1 onboarding output. Your delivery method from prior work.

**Done-when criteria:** A new engagement of the same type as a prior engagement takes 30–50% less time on the second iteration than the first, because the templates and checklists carry the load.

---

### Step 4.3 — Knowledge Management

**Produces:** A growing internal library of every successful artifact (winning emails, approved report sections, effective objection responses, sanitized case examples) organized for fast retrieval and reuse.

**Input:** Every client engagement, ongoing.

**How to do it:** After each engagement, spend 30 minutes capturing what worked. Tag it. File it. Make it findable. Within 12 months you have a "winners library" that compounds — each new engagement starts 60% complete because templates exist.

**Done-when criteria:** When starting any new artifact, you can find at least one prior version to start from in under 60 seconds.

**Common failure modes:** Capturing nothing (everything is rebuilt from scratch). Capturing everything (the library is too big to navigate). No tagging convention.

**AI/tool layer:**
- **Real:** Notion or Obsidian. Tana for advanced relational tagging. Search-friendly file naming.
- **Useful With Caveats:** Mem.ai, Reflect — AI-native note systems. Promising; learning curve and lock-in risk.

---

### Step 4.4 — Tech Stack Hygiene

**Produces:** A documented inventory of every tool you use, what it does, what it costs, who has access, what data it holds, and when it's reviewed for replacement or cancellation.

**Input:** All your existing subscriptions and tools.

**How to do it:** One spreadsheet. Quarterly review. Cancel anything not actively used. Note any tool with sensitive client data (CRM, file storage, email infrastructure) and verify their security posture.

**Done-when criteria:** No surprise charges. No forgotten tools. No "wait, where did I store that file?" moments.

**Common failure modes:** Tool sprawl. Three CRMs, two email-marketing platforms, four file-storage services. Each one $30–100/month, none of them used fully.

**AI/tool layer:**
- **Real:** Just a spreadsheet. Vertice or Cledara if your tool spend exceeds $2K/month and you want active SaaS management.
- **Mostly Theater:** "AI-driven tech stack auditors." Most professional service operators have 8–15 tools, not 80. A spreadsheet review takes an hour.

---

## Phase 5 — Iteration and Scale

### What this phase produces

Continuous learning that flows back into Phases 1–4, compounding the business's effectiveness over time. This is the only phase that has no end state.

### Why it matters

The original document called this the "Master Loop" and described it in mythology. The real version is unglamorous: review your numbers monthly, review your buyer feedback quarterly, review your offer and positioning annually, kill what isn't working, double down on what is.

### Honest framing on this phase

Most operators skip Phase 5 entirely. They run Phases 1–4 once, get a working business, and stop iterating. Within 18–24 months their offer is stale, their content is repetitive, their CAC is climbing, and they don't know why. Phase 5 is the boring discipline that prevents this.

---

### Step 5.1 — Monthly Metrics Review

**Produces:** A one-page dashboard reviewed once per month showing the metrics that matter for your business.

**Input:** Data from your CRM, your email tool, your accounting, your time-tracking.

**How to do it:** Track only the metrics you can actually act on. For most professional service operators that's: number of conversations started, number of qualified opportunities, number closed, average deal value, lifetime value, CAC, hours per engagement, revenue per hour. Eight numbers. Review monthly. Note trends.

**Done-when criteria:** First Monday of every month, the dashboard is updated, you've spent 30 minutes reviewing it, you've decided one thing to change based on what it says.

**Common failure modes:** Tracking 40 metrics (paralysis). Tracking vanity metrics (LinkedIn impressions). Reviewing the dashboard but never changing anything based on it.

**AI/tool layer:**
- **Real:** Google Sheets. Notion databases. HubSpot or Pipedrive reports. Stripe dashboard for revenue.
- **Mostly Theater:** "AI-powered analytics dashboards" with 50 widgets and no actionable insight.

---

### Step 5.2 — Quarterly Buyer Feedback

**Produces:** Direct conversation with at least 5 recent clients each quarter, capturing what worked, what didn't, what they'd change, and what they'd buy next.

**Input:** Your client list.

**How to do it:** Schedule four 30-minute calls per quarter with recent clients. Open-ended questions. Record (with permission). Capture verbatim quotes. Look for patterns across calls.

**Done-when criteria:** Every quarter, you have new buyer language and new insights flowing back into your offer, content, and SOPs.

**Common failure modes:** Skipping these calls because they feel awkward to ask for. Asking only people who liked you (selection bias). Hearing feedback and not acting on it.

**AI/tool layer:**
- **Real:** Otter.ai, Fathom, Granola for transcription. Claude/ChatGPT to synthesize themes across transcripts.

---

### Step 5.3 — A/B Testing (Earned)

**Produces:** Continuous optimization of your highest-volume marketing assets — sales page, lead magnet, email subject lines, ad creative — based on real conversion data.

**Input:** Sufficient traffic volume to actually have statistical significance. For most professional service operators this means 1,000+ page visits per month per asset. Below that, A/B testing is theater.

**How to do it:** Test one variable at a time. Define hypothesis upfront. Run until significance (or 4 weeks max). Document the result. Apply the winner. Move to the next test.

**Done-when criteria:** Each high-volume asset has been through at least 4 deliberate test cycles per year.

**Common failure modes:** Testing without enough traffic (you'll get random noise). Testing too many variables at once. Calling a test winner before it reaches significance. Forgetting which variant won and why.

**AI/tool layer:**
- **Real:** Native A/B in your email tool, ad platform, and CMS (most have it built-in). VWO, Optimizely if you have real volume.
- **Mostly Theater:** AI-driven "auto-optimization." Useful at scale (Meta, Google ads platforms run their own); the third-party "AI testing agents" mostly recreate functionality the platforms already have.

---

### Step 5.4 — Offer and Positioning Refresh

**Produces:** Annual review of your core offer, positioning, pricing, and target buyer. Either confirmation that it's still right, or deliberate evolution.

**Input:** Phase 5 metrics. Quarterly buyer feedback. Competitive landscape changes.

**How to do it:** Once a year, block a full day. Review your Phase 1 documents. Are they still accurate? Has the buyer pain shifted? Has your delivery capability evolved? Is your pricing still right? Decide what to keep, what to evolve, what to retire.

**Done-when criteria:** End of each year, you have an explicit decision: "this is still the offer for next year" or "here is what changes."

**Common failure modes:** Skipping the annual review. Refreshing the offer without buyer feedback to support it. Refreshing for vanity reasons (you got bored) instead of strategic ones.

---

### Step 5.5 — Scale Decision

**Produces:** A deliberate choice about whether to scale vertically (more clients in same niche), horizontally (same offer in adjacent niches), or stay solo.

**Input:** 18+ months of operating data. Honest self-assessment of what you actually want.

**How to do it:** This decision is more about you than about the business. Some operators want to stay a solo expert with high margins and short hours. Some want to build a firm. Both are legitimate. The mistake is drifting into one without choosing.

If scaling vertically: hire associate practitioners, document delivery extensively, develop training for them, plan for quality control. If scaling horizontally: pilot the new niche before committing, treat it as Phase 1 again from scratch. If staying solo: raise prices.

**Done-when criteria:** Explicit written decision with criteria for revisiting.

**Common failure modes:** Drifting into scaling because it sounds like success. Hiring before SOPs are documented (chaos compounds). Hiring before you've explicitly chosen what role you want.

---

## The Feedback Loops

The original document called this the "Master Loop." Here are the actual loops, named honestly:

**Phase 5.1 metrics → Phase 1.2 pain doc.** When your conversation rate or close rate drops, the message has stopped resonating. The buyer's pain has shifted. Re-do pain discovery.

**Phase 5.2 buyer feedback → Phase 2.3 lead magnet, Phase 2.4 sales page, Phase 1.3 offer.** Buyer language captured in feedback calls flows directly into asset copy. Their objections become your FAQ. Their unmet needs become your next offer.

**Phase 5.3 A/B test results → Phase 2 assets, Phase 3.4 content cadence.** Winning variants get codified. Losing patterns get retired.

**Phase 4.3 knowledge library → Phase 3.4 content, Phase 2.3 lead magnet.** Your sanitized case examples become content. Your most-asked questions become lead magnets. The library compounds the marketing.

**Phase 5.4 offer refresh → all of Phase 1.** Once a year, the entire foundation gets revisited.

These loops are not magic. They are scheduled review meetings with yourself. The discipline is in keeping them on the calendar.

---

## Closing — What Makes This Work

This document gives you structure. It does not give you discipline. The structure is portable; discipline is not. The operators who will get value from this skeleton are the ones who:

- Walk Phase 1 fully before launching, even when it feels slow
- Set kill criteria and honor them
- Track what's working and what isn't, monthly
- Talk to actual buyers, quarterly
- Refresh the foundation, annually
- Resist the temptation to add tools, agents, and complexity in place of doing the work

The "agentic" layer in 2026 is real for narrow jobs. It is mostly theater for unbounded creative or strategic work. AI saves 30–50% of time on editing, formatting, and synthesis tasks. It does not save time on thinking, on listening to buyers, on building credibility, or on the relationship work that actually closes high-ticket professional service engagements. Operators who try to substitute AI for those things produce volume without conversion.

### The Identity Commoditization risk

This is the meta-risk that runs across every phase of this document, and it deserves to be named explicitly.

**The mechanism:** When ten operators in your niche all use the same AI tools with similar prompts to produce content, outreach, lead magnets, and proposals, their output converges. Buyers can tell. Not always consciously — sometimes just as a vague sense that "everyone sounds the same now." When that happens at scale, the entire niche commoditizes. Buyers stop trying to identify the best provider and shop on price. Your price floor collapses. Your margin compresses. The work you trained for thirty years to do gets valued like a generic service.

**Why this is the central 2026 risk for high-ticket professional services:** Your buyer is paying premium prices because you bring something specific — credentials, judgment, a way of seeing problems, a track record. AI commodifies the wrappers around those things (your emails, your posts, your reports) faster than it commodifies the substance. If the wrappers all look the same, buyers default to lowest price because they cannot tell the substance apart from outside.

**How to defend against it:**

- **Use AI for editing and synthesis, never for thinking.** Draft your post yourself, then have AI tighten it. Not the other way around.
- **Feed your AI tools your specific intellectual property** — your prior reports, your characteristic phrases, your case examples, your point of view. A model with no context about you produces generic output. A model fed your archive produces output in your voice. This is what the Knowledge Management library in Step 4.3 is actually for.
- **Reserve the highest-stakes artifacts for hand-craftsmanship.** Sales pages, expert reports, depositions, anything a buyer reads carefully — these get written by you, not by AI. Use AI to refine, never to generate.
- **Make your content carry signals only you can produce.** Specific case numbers from your prior work. A photograph from a job site. A technical diagram in your hand. A recording of your voice. Anything that proves a human did the work.
- **Audit yourself quarterly.** Read three of your recent outreach messages aloud. Read three competitor outreach messages aloud. If you can't immediately tell which is yours, you have a problem.

The operators who win in 2026 use AI as a force multiplier on a distinctive practice. The operators who lose use AI as a substitute for one. Same tools, opposite outcomes.

The work is the work. This document tells you what the work is and in what order. The rest is on you.

---

## Where the existing RISER artifacts fit

| Phase / Step | RISER artifact |
|---|---|
| 1.2 Pain Discovery | MVO Decision Engine (Gates 00½, 01) · Pain Discovery Tool Catalog (41 tools) |
| 1.3 Offer Hypothesis | MVO Decision Engine (Gates 04–06) · Marketing Plan Generator (section 08 of every plan) |
| 1.4 MVP Definition | MVO Decision Engine (full 17-gate sequence) |
| 2.1 Competitive Intel | MVO Decision Engine (Gate 03 Competitive Moat) |
| 2.3 Lead Magnet | Marketing Plan Generator (section 05 of every plan) |
| 3.1 Warm Outreach | Marketing Plan Generator (section 09 outreach scripts) |
| 3.2 Dream 100 | Client Acquisition Catalog (Dream 100 template, 39-tool stack) |
| 3.3 Outreach Cadence | Marketing Plan Generator (section 09) · Client Acquisition Catalog (Channel 6 outreach + CRM) |
| 3.4 Content Distribution | Marketing Plan Generator (section 03 Where They Gather, section 04 Channel Priority, sections 06+07 hook/headline/cadence) |

The widgets generate the artifacts. This document tells you when and why to use them. Together they form a working operator's plan, not an unbeatable mastermind 2026 unstoppable scaling agentic essay.

The work is the work.

**Captain out.**

Original HTML source preserved as non-executable text

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>RISER Operator's Flow · Operating Doctrine</title>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Fraunces:ital,opsz,wght@0,9..144,300..900;1,9..144,300..900&family=Inter+Tight:[email protected]&family=JetBrains+Mono:wght@400;500;700&display=swap" rel="stylesheet">
<style>
:root {
  --ink: #0a0a0a; --paper: #f7f4ee; --paper-warm: #f0eadf; --paper-deep: #e9e2d2;
  --rule: #1a1a1a; --red: #c9302a; --red-deep: #8b1f1c; --red-tint: #fbe8e6;
  --gold: #b8893a; --gold-tint: #f5ead0; --teal: #2c5f5a;
  --muted: #5a564f;
  --serif: 'Fraunces', Georgia, serif;
  --sans: 'Inter Tight', -apple-system, sans-serif;
  --mono: 'JetBrains Mono', Menlo, monospace;
}
* { box-sizing: border-box; margin: 0; padding: 0; }
body {
  font-family: var(--sans);
  background: var(--paper);
  color: var(--ink);
  line-height: 1.6;
  font-size: 15px;
  max-width: 880px;
  margin: 0 auto;
  padding: 48px 36px 80px;
}
h1 {
  font-family: var(--serif);
  font-weight: 600;
  font-size: clamp(36px, 5vw, 52px);
  line-height: 1.05;
  letter-spacing: -0.025em;
  margin-bottom: 14px;
  border-bottom: 3px double var(--rule);
  padding-bottom: 18px;
}
h2 {
  font-family: var(--serif);
  font-weight: 600;
  font-size: 30px;
  letter-spacing: -0.02em;
  margin-top: 50px;
  margin-bottom: 14px;
  padding-top: 16px;
  border-top: 2px solid var(--rule);
  padding-bottom: 4px;
  line-height: 1.15;
}
h2:first-of-type { border-top: none; padding-top: 0; margin-top: 32px; }
h3 {
  font-family: var(--mono);
  font-size: 13px;
  font-weight: 700;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  color: var(--red-deep);
  margin-top: 28px;
  margin-bottom: 10px;
  padding-bottom: 4px;
  border-bottom: 1px solid var(--rule);
}
p {
  font-family: var(--serif);
  font-size: 16px;
  line-height: 1.6;
  margin-bottom: 14px;
  color: var(--ink);
}
strong { font-weight: 600; color: var(--ink); }
em { font-style: italic; }
code {
  font-family: var(--mono);
  font-size: 13px;
  background: var(--paper-warm);
  padding: 1px 6px;
  border-radius: 2px;
  color: var(--red-deep);
}
hr {
  border: none;
  height: 1px;
  background: var(--rule);
  opacity: 0.35;
  margin: 36px 0;
}
ul {
  margin: 8px 0 16px 0;
  padding-left: 0;
  list-style: none;
}
li {
  font-family: var(--serif);
  font-size: 15.5px;
  line-height: 1.55;
  margin-bottom: 8px;
  padding-left: 22px;
  position: relative;
  color: var(--ink);
}
li::before {
  content: '→';
  position: absolute;
  left: 0;
  top: 1px;
  color: var(--gold);
  font-weight: 700;
  font-family: var(--sans);
}
table {
  width: 100%;
  border-collapse: collapse;
  margin: 16px 0 24px 0;
  font-family: var(--sans);
  font-size: 14px;
  border: 1.5px solid var(--rule);
}
thead {
  background: var(--ink);
  color: var(--paper);
}
th {
  padding: 10px 14px;
  text-align: left;
  font-family: var(--mono);
  font-size: 11px;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  font-weight: 600;
}
td {
  padding: 9px 14px;
  border-top: 1px solid var(--rule);
  vertical-align: top;
  line-height: 1.5;
}
tr:nth-child(even) td { background: var(--paper-warm); }

/* Tighten the lead-paragraph blocks */
h1 + h2 { margin-top: 12px; border-top: none; }

/* Print styles */
@media print {
  body { background: #fff; padding: 0; max-width: 100%; font-size: 10.5pt; }
  h1 { font-size: 22pt; page-break-after: avoid; }
  h2 { font-size: 16pt; page-break-after: avoid; page-break-before: auto; margin-top: 22pt; }
  h3 { font-size: 11pt; page-break-after: avoid; margin-top: 14pt; }
  p, li { font-size: 10.5pt; }
  hr { page-break-after: always; border: none; height: 0; margin: 0; }
  table { page-break-inside: avoid; font-size: 9.5pt; }
  td, th { padding: 5px 8px; }
  code { background: #f0f0f0; }
  @page { margin: 0.6in; size: letter; }
}
</style>
</head>
<body>
<h1>RISER Operator's Flow</h1>
<h2>A structural skeleton for building, marketing, and scaling a high-ticket professional services business — phase by phase, step by step, with the actual work named honestly.</h2>
<hr>
<p><strong>Version 1 · April 2026 · Captain's Logic Operating Doctrine</strong></p>
<p>This document is the spine. It tells you what stages exist, what order they go in, what each one produces, what could go wrong, and where the existing RISER widgets fit. Use it as a checklist on any given Tuesday — "I'm at Phase 2, Step 3, here is the next concrete deliverable" — not as a vision document to read once and forget.</p>
<p>The framework covers five phases, eighteen steps, and one continuous feedback loop. Phases roughly correspond to weeks 1–4 (Phase 1), 5–8 (Phase 2), 9–12 (Phase 3), and 13+ (Phases 4 and 5, which are continuous from launch onward). A solo operator can complete Phase 1 in seven days if they are disciplined; most take longer because Phase 1 is where the real thinking happens and skipping it makes everything downstream harder.</p>
<p>Three honest framings before you start:</p>
<p><strong>This is not a get-rich-quick plan.</strong> It is a working operator's plan. The fastest result you will see from doing this correctly is a real client conversation in week three. The first paying client typically lands in week six to ten. Operators who expect faster usually skipped Phase 1.</p>
<p><strong>Most "AI agents" mentioned in marketing-stack content are aspirational.</strong> The agent layer in 2026 is mostly real for narrow, well-bounded jobs: drafting first replies a human approves, pulling structured data from PDFs, summarizing call transcripts, routing leads to the right sequence. It is mostly hype for unbounded creative or strategic work. Throughout this document, tools are graded <strong>Real</strong>, <strong>Useful With Caveats</strong>, or <strong>Mostly Theater</strong>. Use the Real ones, treat the second category with measurement, skip the third.</p>
<p><strong>The risks that will actually bite an operator are not the ones marketing content discusses.</strong> Reddit API access can change overnight (GummySearch shut down in November 2025 when Reddit denied API access). LinkedIn's automation crackdowns kill outreach tools regularly. Email deliverability collapses under cold-volume sends. State bar associations and professional licensing boards have rules about AI-personalized outreach that can endanger your license if violated. These risks are flagged inside each step where they apply.</p>
<hr>
<h2>Phase 1 — Foundation</h2>
<h3>What this phase produces</h3>
<p>A validated business hypothesis you can defend with evidence, an offer that solves a pain people actually have, and a minimum viable version you can sell next week. Not a finished product. Not a polished brand. A defensible <em>bet</em> with a known kill criterion.</p>
<h3>Why it matters</h3>
<p>Operators who skip this phase end up in Phase 3 (traffic generation) trying to drive volume to a thing nobody clearly wants. They compensate with bigger ad spend, more outreach, more content. None of it works because the offer is wrong. Phase 1 is unglamorous and slow. It is also the highest-leverage week of the entire build.</p>
<hr>
<h3>Step 1.1 — Idea Capture</h3>
<p><strong>Produces:</strong> A one-paragraph statement of the business or service idea, who you think it serves, and what specific problem you think it solves.</p>
<p><strong>Input:</strong> Your existing skills, prior work, professional credentials, and the rough hypothesis you're entering with.</p>
<p><strong>How to do it:</strong> Write the paragraph by hand on paper. Two hundred words. Include the buyer (one sentence), the problem (one sentence), the solution (one sentence), the price tier (one sentence), and what makes you specifically the right person to deliver it (one sentence). The constraint forces clarity.</p>
<p><strong>Done-when criteria:</strong> A literate friend can read the paragraph once and explain back to you what your business does, who it's for, and why someone would pay you. If they can't, rewrite.</p>
<p><strong>Common failure modes:</strong> Writing in jargon. Listing features instead of outcomes. Defining the buyer too broadly ("small business owners" instead of "construction defect attorneys at mid-sized firms in Arizona"). Hiding behind credentials instead of describing what you actually do for clients.</p>
<p><strong>AI/tool layer:</strong> None needed at this step. <strong>Mostly Theater</strong> if you're using AI to "validate" the idea here — the model will tell you almost any idea sounds promising. Save the validation work for Step 1.3.</p>
<p><strong>Iteration trigger:</strong> Phase 5 customer feedback that contradicts your stated buyer or problem. Rewrite this paragraph quarterly.</p>
<hr>
<h3>Step 1.2 — Pain Discovery</h3>
<p><strong>Produces:</strong> A document with three to five real pain points your buyer experiences, written in their own language, with evidence sources. Not pain you assume they have. Pain they say out loud.</p>
<p><strong>Input:</strong> The Step 1.1 paragraph. Your hypothesis about who the buyer is.</p>
<p><strong>How to do it:</strong> Three parallel research tracks, run for one week:</p>
<p>1. <strong>Direct conversations.</strong> Five to ten phone or video calls with people in your target buyer category. Not pitches. Listening tours. Questions: What's the most frustrating part of [problem area]? When did this last cause a real problem? What did you try? What worked? What didn't?</p>
<p>2. <strong>Public language mining.</strong> Read what your buyers post and ask in places they gather: LinkedIn posts and comments, association forums, niche Slack groups, industry-specific subreddits if any exist, Quora answers in their domain. Copy verbatim phrases into a document.</p>
<p>3. <strong>Tool-assisted scanning.</strong> Use the RISER Pain Discovery Tool Catalog — specifically the Reddit pain mining tools, audience intelligence tools (SparkToro), and VOC synthesis tools — to surface language patterns at scale.</p>
<p><strong>Sort what you find into two buckets — burning vs chronic.</strong> This distinction is the most useful prioritization tool in pain discovery. <strong>Burning pain</strong> is active crisis: a lawsuit was filed last week, a deposition is in 14 days, a client just sued, a deadline is tomorrow, a regulator just sent a notice. Burning pain drives buying <em>this week</em>. <strong>Chronic pain</strong> is the dull background ache: communication is messy, vendor management is annoying, paperwork takes too long. Chronic pain is real but rarely triggers a buying decision on its own — it needs a triggering event to become burning.</p>
<p>For high-ticket professional services, your offer must address burning pain. Operators who build offers for chronic pain spend years marketing to people who agree there's a problem but never buy. Tag every pain point in your discovery doc as B (burning) or C (chronic). If your top three pains are all C, your offer or your avatar is wrong.</p>
<p><strong>Done-when criteria:</strong> You have at least 20 verbatim quotes from real buyers describing pain in their own words, organized into 3–5 themes, each tagged burning or chronic. At least two of your top themes are burning. You can show a friend the quotes (with sources) and they can independently identify the themes you found and the burning/chronic tag.</p>
<p><strong>Common failure modes:</strong> Using your own words instead of the buyer's. Treating one Reddit thread as evidence. Skipping the direct conversations because they're hard to schedule (this is the single biggest stall point). Picking only pain points that flatter your existing solution.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Otter.ai or Fathom for transcribing buyer conversations. ChatGPT/Claude for synthesizing themes across transcripts. SparkToro for finding where buyers gather.</li>
<li><strong>Useful With Caveats:</strong> PainOnSocial, PainPointy for surfacing language patterns. They produce useful raw material but the categorization needs human review — the AI is wrong about pain intensity ranking maybe one third of the time.</li>
<li><strong>Mostly Theater:</strong> Any tool claiming to "automatically generate buyer personas" without you talking to a single buyer. The output looks plausible. It will not survive contact with reality.</li>
</ul>
<p><strong>Iteration trigger:</strong> Quarterly. Buyer pain shifts as their context shifts (regulatory changes, economic conditions, technology shifts). The doc you wrote in Q1 needs revision by Q3.</p>
<p><strong>Existing RISER artifact:</strong> The <strong>MVO Decision Engine widget</strong> (Gate 00½ Pain Discovery, Gate 01 Hungry Avatar). The <strong>Pain Discovery Tool Catalog</strong> lists the 41 tools that fit this work and their honest tradeoffs.</p>
<hr>
<h3>Step 1.3 — Offer Hypothesis</h3>
<p><strong>Produces:</strong> A specific named offer — what you sell, what it costs, what the buyer gets, what they walk away from the call with — that maps directly to the pain you found.</p>
<p><strong>Input:</strong> Step 1.2 pain document. Your skills inventory.</p>
<p><strong>How to do it:</strong> Write the offer in one page, using Hormozi's value-equation structure. Name the dream outcome (in the buyer's words). Name the perceived likelihood (your proof — credentials, prior work, sample deliverable). Name the time delay (how long until they get the result). Name the effort/sacrifice (what they have to do versus what you do). The offer wins or loses on whether (Dream × Likelihood) ÷ (Time × Effort) is high.</p>
<p>Decide on a named mechanism. Not "I do forensic engineering" — "The 14-Day VRF Failure Forensic Audit." Specific deliverable, specific timeframe, specific outcome.</p>
<p>Decide on a kill criterion before launch. <em>"If I cannot get one paying engagement at this price within 60 days of starting active outreach, I will reduce price by 25% or restructure the offer."</em> Write the criterion down. Date it. Keep it visible.</p>
<p><strong>Done-when criteria:</strong> You can describe the offer in 30 seconds, name the price, name the deliverable timeline, name your kill criterion, and a literate friend can repeat it back accurately.</p>
<p><strong>Common failure modes:</strong> Pricing too low because you're nervous (this is universal — your first instinct on price is usually 40–60% of what the market pays). Naming the offer in your own jargon instead of the buyer's. Skipping the kill criterion because writing it feels like admitting you might fail. The kill criterion is the <em>whole point</em> — it converts a vague hope into a falsifiable bet.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Claude or ChatGPT to pressure-test offer language by simulating buyer objections. Wynter ($540+/test) for actual ICP message testing if the price tier justifies it.</li>
<li><strong>Mostly Theater:</strong> Any "AI offer generator" that produces a finished offer without you doing the pain research first. The output is generic.</li>
</ul>
<p><strong>Iteration trigger:</strong> First five buyer conversations. If buyers don't immediately understand the offer or push back hard on price, restructure.</p>
<p><strong>Existing RISER artifact:</strong> The <strong>MVO Decision Engine</strong> Gate 04 Solution Sketch, Gate 05 Offer, Gate 06 Pricing. The <strong>Marketing Plan Generator</strong> outputs a complete offer angle in section 08 of every plan it produces.</p>
<hr>
<h3>Step 1.4 — MVP / Service Definition</h3>
<p><strong>Produces:</strong> The actual <em>thing</em> you will deliver. For services this is a scope-of-work template. For software this is a working prototype. For productized services this is a defined deliverable package.</p>
<p><strong>Input:</strong> Step 1.3 offer document.</p>
<p><strong>How to do it:</strong> Write the scope of work in one page. What's included. What's not included. Timeline. Communication cadence. Revisions. Out-of-scope handling. Payment terms. For a service business, this is also where you decide what you will template, what you will custom-build, and what you will refuse to do.</p>
<p>For productized services (most professional services should be productized): name the package, list the exact deliverables, set the price, set the timeline, define what makes a customer eligible to buy.</p>
<p><strong>Done-when criteria:</strong> You have an SOW you could send to a buyer this afternoon. It defines scope so clearly that you know in advance what you're delivering and so does the buyer.</p>
<p><strong>Common failure modes:</strong> Vague scope language ("ongoing strategic guidance") that lets buyers expand the work without paying more. Missing the "out of scope" section. No defined revision limit. Promising deliverables you haven't actually built a process for.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Claude or ChatGPT to draft the SOW from a checklist. PandaDoc or Bonsai for SOW signing infrastructure (free or low cost).</li>
<li><strong>Mostly Theater:</strong> Building a "Product Architect Agent" workflow before you've delivered the service to one human. Map the actual delivery from one real engagement first.</li>
</ul>
<p><strong>Iteration trigger:</strong> After the first three engagements. You will discover scope leaks and SOW gaps you didn't anticipate. Update the template.</p>
<hr>
<h2>Phase 2 — Positioning and Asset Build</h2>
<h3>What this phase produces</h3>
<p>The artifacts a buyer encounters before they buy from you. Brand, message, lead magnet, sales page, proof. Not all of them at once — the minimum credible set.</p>
<h3>Why it matters</h3>
<p>Phase 1 gave you a defensible offer. Phase 2 gives buyers a way to evaluate you without talking to you first. For high-ticket professional services, where buyers research at 11pm before deciding who to contact, the asset layer is what gets you on the consideration list. Skip it and you're invisible.</p>
<h3>Honest framing on this phase</h3>
<p>You don't need a $5,000 logo. You don't need a 12-page brand bible. You don't need a hand-photographed headshot. You need the minimum credible set, deployed within a week, and you need to spend the saved time on Phase 3 outreach. Operators stall here because polishing assets feels productive. It is not. It is procrastination dressed as work.</p>
<hr>
<h3>Step 2.1 — Competitive Intelligence</h3>
<p><strong>Produces:</strong> A one-page comparison matrix of three to five direct competitors — their offer, their pricing, their positioning, their lead magnet, their hook, what's working for them, what's missing.</p>
<p><strong>Input:</strong> Phase 1 work. Knowledge of who else serves your buyer.</p>
<p><strong>How to do it:</strong> List five competitors. Open each one's website, lead magnet (download it), pricing page (if visible), LinkedIn, and any case studies. Fill in the matrix. Note what you can't easily improve on (their credentials, their tenure) and what you can (their positioning, their offer specificity, their pain language match).</p>
<p><strong>Done-when criteria:</strong> You can name in one sentence per competitor what's strong about their positioning and what's weak. You have an explicit "we're different from them because..." for each.</p>
<p><strong>Common failure modes:</strong> Researching too many competitors (five is enough; ten is hiding from the work). Fixating on what they do better instead of what they leave on the table. Copying their offer instead of differentiating from it.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Built With or SimilarWeb for tech-stack and traffic visibility on competitor sites (free or low-tier). Wayback Machine to see how their positioning has evolved.</li>
<li><strong>Useful With Caveats:</strong> Apify, Bright Data for scraping if you need depth. Compliance and TOS questions matter — read them.</li>
<li><strong>Mostly Theater:</strong> "AI-driven competitive intelligence agents" that promise daily monitoring. They produce dashboards. Dashboards are not insight.</li>
</ul>
<p><strong>Iteration trigger:</strong> Quarterly. Competitor offers and positioning shift; your matrix needs refresh.</p>
<hr>
<h3>Step 2.2 — Brand & Asset Minimum Viable Set</h3>
<p><strong>Produces:</strong> A logo (or wordmark), one professional headshot, a one-page bio, a defined color palette, and a one-page service overview document. That's the minimum. Nothing more until you've closed five clients.</p>
<p><strong>Input:</strong> Phase 1 work. Your existing materials.</p>
<p><strong>How to do it:</strong> Use Canva or Figma. Pay $200–$500 for a wordmark on Fiverr or 99designs if you want polish. Get a real headshot — phone-camera selfie quality is fine for LinkedIn but not for an expert witness directory listing. Write the one-page bio in third person, including your specific credentials, three concrete prior accomplishments (sanitized if needed), and a clear statement of who you serve.</p>
<p><strong>Done-when criteria:</strong> You have a presentable LinkedIn profile, a presentable directory listing draft, and a service overview PDF you can email to a prospect.</p>
<p><strong>Common failure modes:</strong> Spending three weeks on a logo. Hiring a brand strategist before you have buyers. Writing the bio in language that sounds like every other consultant's bio.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Canva ($15/mo) for fast asset production. Claude/ChatGPT to draft and polish the bio. Looka for $50 wordmark generation if you can't decide what you want.</li>
<li><strong>Mostly Theater:</strong> AI-generated "brand identity systems." Looks impressive, costs significant time, doesn't move buyers. Save brand investment for after you have customer feedback.</li>
</ul>
<hr>
<h3>Step 2.3 — Lead Magnet (Gift First)</h3>
<p><strong>Produces:</strong> A specific, valuable, narrow asset that solves one micro-problem for your buyer in exchange for their email or a 15-minute call. Not a generic ebook. A diagnostic checklist, a calculator, a contract review template, a five-page "how to evaluate X" guide.</p>
<p><strong>Input:</strong> Phase 1 pain doc. Knowledge of buyer's specific decision moments.</p>
<p><strong>How to do it:</strong> Pick the buyer's most concrete sub-pain. Build the asset that solves it. Constraint: this asset should be useful even if the buyer never works with you. That's what triggers reciprocity (Cialdini). A bait-and-switch lead magnet that turns into a pitch deck does not work and damages trust.</p>
<p><strong>Done-when criteria:</strong> A buyer who downloads this asset finds it genuinely useful and would tell a colleague about it. You've tested this with two real buyers before launch.</p>
<p><strong>Common failure modes:</strong> Generic "10 tips for X" content. Disguised pitch decks. Asset is too long (40 pages = won't be read) or too short (one tip = not worth the email).</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Claude/ChatGPT to draft the asset content. Canva or Figma for layout. ConvertKit, Beehiiv, or Mailchimp for email delivery infrastructure.</li>
<li><strong>Mostly Theater:</strong> "AI lead magnet generators" that produce generic content with no specific buyer in mind.</li>
</ul>
<p><strong>Existing RISER artifact:</strong> The <strong>Marketing Plan Generator</strong> generates a specific lead-magnet recommendation for any profession+avatar combination as section 05 of every plan.</p>
<hr>
<h3>Step 2.4 — Sales Page / Service Page</h3>
<p><strong>Produces:</strong> A single page on your website (or a one-page Notion/Carrd if you're moving fast) that names the buyer, the pain, the offer, the proof, and the next step. Not a homepage. A targeted page for the specific avatar you're going after.</p>
<p><strong>Input:</strong> All prior Phase 1 and 2 work.</p>
<p><strong>How to do it:</strong> Use the long-form direct response structure: hook → problem → why-other-things-fail → mechanism → proof → offer → bonuses (only if real) → guarantee or risk reversal → CTA. Write it once, in their voice. Word count: 800–1,500 for a high-ticket service.</p>
<p><strong>Done-when criteria:</strong> A cold buyer can read the page and either qualify themselves in (book a call) or qualify out (close the tab). It does both jobs without making them work.</p>
<p><strong>Common failure modes:</strong> Writing about yourself instead of the buyer. Burying the offer below the fold. Vague CTAs ("Get in touch"). No social proof. No risk reversal.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Webflow, Carrd, Framer for fast page hosting. Claude/ChatGPT for copy iteration (it's good at this when you give it Phase 1 buyer language).</li>
<li><strong>Useful With Caveats:</strong> Hyros, Triple Whale for tracking — only if your spend justifies it.</li>
<li><strong>Mostly Theater:</strong> "AI website builders" that promise full sites in one click. Outputs are generic. Use a template instead.</li>
</ul>
<hr>
<h2>Phase 3 — Acquisition</h2>
<h3>What this phase produces</h3>
<p>Real buyer conversations. Not awareness. Not "thought leadership." Conversations with named humans who could pay you, where they say yes, no, or "tell me more."</p>
<h3>Why it matters</h3>
<p>Everything in Phases 1 and 2 is unfalsifiable until Phase 3 puts it in front of buyers. Operators who linger in 1 and 2 are usually avoiding the discomfort of 3. The cure is to launch publicly before you feel ready, then let real feedback drive the iterations.</p>
<h3>The order matters</h3>
<p>For high-ticket professional services, run these channels in this order. Don't run them in parallel until each is proven.</p>
<p>1. <strong>Warm outreach</strong> to your existing network (week one)</p>
<p>2. <strong>Dream 100 cold outreach</strong> to named humans in your target market (week two)</p>
<p>3. <strong>Content distribution</strong> on the platforms your buyers actually use (ongoing from week one)</p>
<p>4. <strong>Paid ads</strong> only after channels 1–3 produce signal</p>
<hr>
<h3>Step 3.1 — Warm Network Outreach</h3>
<p><strong>Produces:</strong> 5–15 conversations with people who already know you, plus a list of 20–50 introductions they could make to people you don't know.</p>
<p><strong>Input:</strong> Phase 1 and 2 assets. Your contact list.</p>
<p><strong>How to do it:</strong> Write a 4–6 sentence note. Tell them what you're doing now. Ask if they know anyone in your target buyer category. Offer to do something useful for them in return. Send it to everyone you've worked with in the last decade. Include the lead magnet as a gift.</p>
<p><strong>Done-when criteria:</strong> All notes sent within seven days. Track replies. Track who introduces you. Follow up.</p>
<p><strong>Common failure modes:</strong> Hiding from this step because asking former colleagues feels needy. (It is not. It is normal professional behavior.) Not having anything specific to ask for. Asking for "any help" instead of "an introduction to anyone you know who handles construction defect cases."</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Your existing inbox and LinkedIn. Claude/ChatGPT to personalize each outreach note from a base template. Notion or a simple spreadsheet to track responses.</li>
<li><strong>Mostly Theater:</strong> Automating warm outreach. The whole point is the personal note.</li>
</ul>
<p><strong>Existing RISER artifact:</strong> The <strong>Marketing Plan Generator</strong> outputs a LinkedIn first-touch template, a cold-email template, and a community-reply template in section 09 of every plan it produces. Adapt those for warm context.</p>
<hr>
<h3>Step 3.2 — Dream 100 List Building</h3>
<p><strong>Produces:</strong> A spreadsheet of 100 named humans in your target buyer category — name, title, firm, geography, contact route, and one specific reason this person fits.</p>
<p><strong>Input:</strong> Phase 1 buyer definition.</p>
<p><strong>How to do it:</strong> Use the segment breakdown from the <strong>Client Acquisition Catalog Dream 100 template</strong> (or build your own equivalent). For a forensic engineer that's roughly: 25 construction defect attorneys + 25 insurance defense attorneys + 15 subrogation managers + 15 mechanical contractor GCs + 10 property management firms + 10 technical committee chairs.</p>
<p>For each, find them on LinkedIn (Sales Navigator helps), record their firm, find their email (Apollo, Hunter, or guessable patterns), record one specific thing they do that's relevant. The "one specific thing" prevents your outreach from being generic.</p>
<p><strong>Done-when criteria:</strong> 100 names. Real ones. Verified contact info for at least 70 of them. Notes column filled in for at least 50.</p>
<p><strong>Common failure modes:</strong> Listing firm names instead of human names. Stopping at 30 because the list is "good enough" (it isn't — Dream 100 works because of compounding, not because the first 30 are special). Skipping the "one specific thing" column.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> LinkedIn Sales Navigator ($99/mo). Apollo (free tier or $59/mo). PACER ($0.10/page) for federal court records to identify attorneys handling specific case types. Justia for free legal directory search. A spreadsheet (Google Sheets is fine).</li>
<li><strong>Useful With Caveats:</strong> Clay ($149+/mo) if you want enrichment-and-personalization-at-scale workflow. Steep learning curve. Probably overkill until you have 30+ confirmed buyers in pipeline.</li>
<li><strong>Mostly Theater:</strong> "AI SDR agents" that build the list and personalize the outreach for you autonomously. They produce volume. Volume is not the bottleneck. Specificity is.</li>
</ul>
<p><strong>Existing RISER artifact:</strong> The <strong>Client Acquisition Catalog</strong> has the full tool stack with verified pricing, organized by channel. The Dream 100 template segment-counts are inside the catalog.</p>
<p><strong>Risks worth flagging:</strong> LinkedIn TOS prohibits most automation. Sales Navigator usage is fine. Tools that auto-message people through LinkedIn risk account suspension and have killed many an outreach plan.</p>
<hr>
<h3>Step 3.3 — Dream 100 Outreach Cadence</h3>
<p><strong>Produces:</strong> First-touch messages sent to all 100 people, follow-up sequence executed, conversations started.</p>
<p><strong>Input:</strong> Step 3.2 list. Step 2.3 lead magnet.</p>
<p><strong>How to do it:</strong> Six-touch cadence over 8 weeks. Mix LinkedIn, email, and (where appropriate) phone. Each touch is short, specific, value-first. Open with the "one specific thing" you noted. Reference a real signal — they posted something, their firm just took on a relevant case, an industry event happened. Lead-magnet offer can come on touch 2 or 3, never touch 1.</p>
<p>Run the cadence as a deliberate practice. 15 outreach touches per workday is the right volume for a solo professional. More than that and quality drops. Less than that and momentum dies.</p>
<p><strong>Done-when criteria:</strong> All 100 people have received at least four touches across 8 weeks. Conversation rate of 8–15% (8–15 named people responded with interest) is normal. Less than 5% means the message is wrong; rewrite. More than 25% means the targeting got lucky; verify before scaling.</p>
<p><strong>Common failure modes:</strong> Sending touch 1 to all 100 then giving up when 92 ignore you. (The compounding is in touches 3–6.) Generic copy that ignores the "one specific thing." Pitching the offer on touch 1.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Smartlead or Instantly ($39–94/mo) for cold-email infrastructure (deliverability matters). HubSpot CRM Free or Pipedrive ($25/seat) for tracking touches. Calendly for booking the calls that result.</li>
<li><strong>Useful With Caveats:</strong> Lemlist ($59+/mo) — premium worth it only if you actually use the personalization features. Otherwise overpriced versus Smartlead.</li>
<li><strong>Mostly Theater:</strong> Cold-outreach AI that generates "100% personalized" messages. The personalization is shallow. Buyers can tell. Better to send fewer messages with real personalization than more with fake.</li>
</ul>
<p><strong>Risks:</strong> Email deliverability. Sending 100 cold emails from a fresh domain will land you in spam folders. Use a separate sending domain, warm it up over 4–6 weeks, follow SPF/DKIM/DMARC standards. Smartlead handles this; sending from your business Gmail does not.</p>
<p>For licensed professionals: state bar associations and professional licensing boards have rules about solicitation. Consult yours before launching cold outreach. Some states prohibit certain cold-contact patterns for attorneys, doctors, and engineers in regulated practice.</p>
<hr>
<h3>Step 3.4 — Content Distribution Cadence</h3>
<p><strong>Produces:</strong> A consistent, multi-month flow of content on the platform(s) your buyers actually inhabit, building credibility while warm and Dream 100 outreach runs in parallel.</p>
<p><strong>Input:</strong> Phase 1 pain doc. Phase 2 positioning. Knowledge of where buyers actually gather.</p>
<p><strong>How to do it:</strong> Pick <em>one</em> primary platform. For high-ticket professional services in 2026, that's almost always LinkedIn. Possibly an industry-specific publication (ABA Journal, ASHRAE Journal, etc.) for the highest-credentialing-value plays. Don't multi-platform until the primary one is producing.</p>
<p>The content cadence framework that works:</p>
<ul>
<li><strong>Monday — Pain post.</strong> A real piece of buyer pain, observed or quoted, with your take. 150–300 words.</li>
<li><strong>Wednesday — Mechanism post.</strong> A specific technical observation or framework, in your area of expertise. 200–400 words. This is the "I know things" post.</li>
<li><strong>Friday — Case study or proof.</strong> A sanitized story from your work, or a public case dissected. 250–500 words.</li>
</ul>
<p>Three posts a week. Same days. Same time. For 12 weeks before evaluating. The discipline matters more than the volume — buyers notice consistency over six months.</p>
<p><strong>Done-when criteria:</strong> 12 weeks of consistent posting. Engagement metrics matter less than reach growth and the qualitative feedback that comes in (DMs, comments, lurkers reaching out). The right buyers reading you silently for 8 weeks before contacting you is the dominant pattern.</p>
<p><strong>Common failure modes:</strong> Multi-platforming too early (LinkedIn + X + Instagram + TikTok). Posting whenever you "feel inspired" instead of on cadence. Generic "thought leadership" posts that aren't grounded in real buyer pain. Stopping after three weeks because results aren't visible.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Claude/ChatGPT to draft and refine post copy from your raw notes. Buffer or Hypefury for scheduling. Notion for content calendar.</li>
<li><strong>Useful With Caveats:</strong> Repurpose.io, OpusClip for converting long-form (podcast, video) into short-form social posts. Useful if you're already producing long-form. Theater if you're not.</li>
<li><strong>Mostly Theater:</strong> AI tools that "generate a year of content in 10 minutes." The output is generic. It does not move buyers. Worse, it identifies you as someone using AI to generate content, which actively damages credibility for high-ticket professional services. This is <strong>Identity Commoditization</strong> in action — see the Closing section for the full framing of why generic AI output collapses your price floor.</li>
</ul>
<p><strong>The honest tradeoff:</strong> AI can save 30–50% of your time on the <em>editing</em> and <em>formatting</em> layer. It cannot save time on the <em>thinking</em> layer. The thinking is the work. If you're using AI to skip the thinking, you're skipping the value.</p>
<hr>
<h3>Step 3.5 — Paid Channels (Defer Until Earned)</h3>
<p><strong>Produces:</strong> Scaled distribution of proven content/offers, after warm and Dream 100 outreach have produced consistent close signal.</p>
<p><strong>Input:</strong> Steps 3.1–3.4 producing measurable conversation rate, close rate, and lifetime value data. You need at least 10 closed clients before you have any business spending on paid ads.</p>
<p><strong>How to do it:</strong> This step is deferred for most professional service operators for 6–12 months. The reason: high-ticket service buyers don't typically respond to paid ads the way e-commerce buyers do. Your CAC math has to work, and it usually doesn't until you've validated the funnel manually.</p>
<p>When you do enter paid: start with one platform (LinkedIn ads if your buyer is on LinkedIn; Google Search if they search for your category; Meta only if your buyer demographic is verified active there). Set a hard monthly cap. Track CAC and LTV explicitly. Cut spend the moment CAC > 0.33 × LTV.</p>
<p><strong>Done-when criteria:</strong> Active paid channel with measurable CAC under your threshold and predictable conversion rate over a 60-day window.</p>
<p><strong>Common failure modes:</strong> Running paid before manual outreach has validated message-market fit. Boosting LinkedIn posts (almost never worth it for high-ticket B2B). Treating paid as a substitute for organic instead of an amplifier of organic.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Native ad platforms. Hyros or Triple Whale for tracking only if spend justifies it.</li>
<li><strong>Mostly Theater:</strong> "AI ad optimizer" tools that promise to manage your campaigns. The platforms' built-in optimization is now better than most third-party tools.</li>
</ul>
<hr>
<h2>Phase 4 — Operations and Delivery</h2>
<h3>What this phase produces</h3>
<p>The systems that let you deliver promised outcomes consistently, capture knowledge from every engagement, and maintain quality as volume increases. SOPs, templates, knowledge management, and the boring infrastructure that prevents the business from collapsing under its own success.</p>
<h3>Why it matters</h3>
<p>Phase 3 will produce clients faster than you expect once it works. Operators without Phase 4 systems compound chaos with every new client. Within six months they're working 70-hour weeks, dropping deliverables, and the original positioning erodes.</p>
<p>This phase runs in parallel with Phase 3 from the moment your first client signs. Don't wait until you're overwhelmed to start.</p>
<hr>
<h3>Step 4.1 — Client Onboarding SOP</h3>
<p><strong>Produces:</strong> A documented, repeatable process for taking a signed client from "yes" to "first deliverable" without anything falling through the cracks.</p>
<p><strong>Input:</strong> Phase 1 SOW template. Your delivery process from your first three engagements.</p>
<p><strong>How to do it:</strong> Document the process. Welcome email template. Kickoff-call agenda. Information-gathering checklist. Project-folder template. Communication-cadence agreement. Payment-collection workflow. The first time you do this it takes a day. Every time after that it saves a day.</p>
<p><strong>Done-when criteria:</strong> A new client signs and the first 14 days run identically each time, with no email you have to write from scratch and no question you have to look up.</p>
<p><strong>Common failure modes:</strong> Reinventing the onboarding for each client. Not having a kickoff agenda. Forgetting to invoice. Missing the information-gathering step and getting blocked mid-engagement.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Notion or Process Street for SOP storage. Loom for recording explainer videos once and reusing them. Calendly for scheduling. PandaDoc or Bonsai for contract+invoice infrastructure.</li>
<li><strong>Useful With Caveats:</strong> Bonsai or HoneyBook for end-to-end client management — useful if you want one tool, costlier than piecing tools together.</li>
<li><strong>Mostly Theater:</strong> AI "client onboarding agents." Onboarding is relationship-building. Automate the <em>reminders</em> and <em>templates</em>; do the relationship work yourself.</li>
</ul>
<hr>
<h3>Step 4.2 — Delivery SOP</h3>
<p><strong>Produces:</strong> A documented, repeatable process for delivering the actual service, from start of engagement to final deliverable to client offboarding.</p>
<p><strong>Input:</strong> Step 4.1 onboarding output. Your delivery method from prior work.</p>
<p><strong>How to do it:</strong> Document each phase of delivery. Templates for each artifact you produce. Quality checklists. Internal review steps. Time-tracking convention. Client communication touchpoints. For technical work (forensic engineering, expert witness reports), include the credentialing-and-citation discipline that protects your work product from challenge.</p>
<p><strong>Done-when criteria:</strong> A new engagement of the same type as a prior engagement takes 30–50% less time on the second iteration than the first, because the templates and checklists carry the load.</p>
<p><strong>Common failure modes:</strong> No quality checklist (every deliverable is bespoke and inconsistent). No time tracking (you discover after-the-fact you priced wrong). No internal review step (errors ship to client).</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Notion or Confluence for SOP storage. Toggl or Harvest for time tracking. Claude/ChatGPT for first-draft generation of report sections that have known patterns.</li>
<li><strong>Useful With Caveats:</strong> Tana, Reflect, Mem for AI-assisted note-taking. Genuinely useful for knowledge capture across many engagements. Learning curve is real.</li>
<li><strong>Mostly Theater:</strong> AI tools that promise to "automate your delivery." If your service is high-ticket, the delivery is the value. Don't automate the value.</li>
</ul>
<hr>
<h3>Step 4.3 — Knowledge Management</h3>
<p><strong>Produces:</strong> A growing internal library of every successful artifact (winning emails, approved report sections, effective objection responses, sanitized case examples) organized for fast retrieval and reuse.</p>
<p><strong>Input:</strong> Every client engagement, ongoing.</p>
<p><strong>How to do it:</strong> After each engagement, spend 30 minutes capturing what worked. Tag it. File it. Make it findable. Within 12 months you have a "winners library" that compounds — each new engagement starts 60% complete because templates exist.</p>
<p><strong>Done-when criteria:</strong> When starting any new artifact, you can find at least one prior version to start from in under 60 seconds.</p>
<p><strong>Common failure modes:</strong> Capturing nothing (everything is rebuilt from scratch). Capturing everything (the library is too big to navigate). No tagging convention.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Notion or Obsidian. Tana for advanced relational tagging. Search-friendly file naming.</li>
<li><strong>Useful With Caveats:</strong> Mem.ai, Reflect — AI-native note systems. Promising; learning curve and lock-in risk.</li>
</ul>
<hr>
<h3>Step 4.4 — Tech Stack Hygiene</h3>
<p><strong>Produces:</strong> A documented inventory of every tool you use, what it does, what it costs, who has access, what data it holds, and when it's reviewed for replacement or cancellation.</p>
<p><strong>Input:</strong> All your existing subscriptions and tools.</p>
<p><strong>How to do it:</strong> One spreadsheet. Quarterly review. Cancel anything not actively used. Note any tool with sensitive client data (CRM, file storage, email infrastructure) and verify their security posture.</p>
<p><strong>Done-when criteria:</strong> No surprise charges. No forgotten tools. No "wait, where did I store that file?" moments.</p>
<p><strong>Common failure modes:</strong> Tool sprawl. Three CRMs, two email-marketing platforms, four file-storage services. Each one $30–100/month, none of them used fully.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Just a spreadsheet. Vertice or Cledara if your tool spend exceeds $2K/month and you want active SaaS management.</li>
<li><strong>Mostly Theater:</strong> "AI-driven tech stack auditors." Most professional service operators have 8–15 tools, not 80. A spreadsheet review takes an hour.</li>
</ul>
<hr>
<h2>Phase 5 — Iteration and Scale</h2>
<h3>What this phase produces</h3>
<p>Continuous learning that flows back into Phases 1–4, compounding the business's effectiveness over time. This is the only phase that has no end state.</p>
<h3>Why it matters</h3>
<p>The original document called this the "Master Loop" and described it in mythology. The real version is unglamorous: review your numbers monthly, review your buyer feedback quarterly, review your offer and positioning annually, kill what isn't working, double down on what is.</p>
<h3>Honest framing on this phase</h3>
<p>Most operators skip Phase 5 entirely. They run Phases 1–4 once, get a working business, and stop iterating. Within 18–24 months their offer is stale, their content is repetitive, their CAC is climbing, and they don't know why. Phase 5 is the boring discipline that prevents this.</p>
<hr>
<h3>Step 5.1 — Monthly Metrics Review</h3>
<p><strong>Produces:</strong> A one-page dashboard reviewed once per month showing the metrics that matter for your business.</p>
<p><strong>Input:</strong> Data from your CRM, your email tool, your accounting, your time-tracking.</p>
<p><strong>How to do it:</strong> Track only the metrics you can actually act on. For most professional service operators that's: number of conversations started, number of qualified opportunities, number closed, average deal value, lifetime value, CAC, hours per engagement, revenue per hour. Eight numbers. Review monthly. Note trends.</p>
<p><strong>Done-when criteria:</strong> First Monday of every month, the dashboard is updated, you've spent 30 minutes reviewing it, you've decided one thing to change based on what it says.</p>
<p><strong>Common failure modes:</strong> Tracking 40 metrics (paralysis). Tracking vanity metrics (LinkedIn impressions). Reviewing the dashboard but never changing anything based on it.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Google Sheets. Notion databases. HubSpot or Pipedrive reports. Stripe dashboard for revenue.</li>
<li><strong>Mostly Theater:</strong> "AI-powered analytics dashboards" with 50 widgets and no actionable insight.</li>
</ul>
<hr>
<h3>Step 5.2 — Quarterly Buyer Feedback</h3>
<p><strong>Produces:</strong> Direct conversation with at least 5 recent clients each quarter, capturing what worked, what didn't, what they'd change, and what they'd buy next.</p>
<p><strong>Input:</strong> Your client list.</p>
<p><strong>How to do it:</strong> Schedule four 30-minute calls per quarter with recent clients. Open-ended questions. Record (with permission). Capture verbatim quotes. Look for patterns across calls.</p>
<p><strong>Done-when criteria:</strong> Every quarter, you have new buyer language and new insights flowing back into your offer, content, and SOPs.</p>
<p><strong>Common failure modes:</strong> Skipping these calls because they feel awkward to ask for. Asking only people who liked you (selection bias). Hearing feedback and not acting on it.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Otter.ai, Fathom, Granola for transcription. Claude/ChatGPT to synthesize themes across transcripts.</li>
</ul>
<hr>
<h3>Step 5.3 — A/B Testing (Earned)</h3>
<p><strong>Produces:</strong> Continuous optimization of your highest-volume marketing assets — sales page, lead magnet, email subject lines, ad creative — based on real conversion data.</p>
<p><strong>Input:</strong> Sufficient traffic volume to actually have statistical significance. For most professional service operators this means 1,000+ page visits per month per asset. Below that, A/B testing is theater.</p>
<p><strong>How to do it:</strong> Test one variable at a time. Define hypothesis upfront. Run until significance (or 4 weeks max). Document the result. Apply the winner. Move to the next test.</p>
<p><strong>Done-when criteria:</strong> Each high-volume asset has been through at least 4 deliberate test cycles per year.</p>
<p><strong>Common failure modes:</strong> Testing without enough traffic (you'll get random noise). Testing too many variables at once. Calling a test winner before it reaches significance. Forgetting which variant won and why.</p>
<p><strong>AI/tool layer:</strong></p>
<ul>
<li><strong>Real:</strong> Native A/B in your email tool, ad platform, and CMS (most have it built-in). VWO, Optimizely if you have real volume.</li>
<li><strong>Mostly Theater:</strong> AI-driven "auto-optimization." Useful at scale (Meta, Google ads platforms run their own); the third-party "AI testing agents" mostly recreate functionality the platforms already have.</li>
</ul>
<hr>
<h3>Step 5.4 — Offer and Positioning Refresh</h3>
<p><strong>Produces:</strong> Annual review of your core offer, positioning, pricing, and target buyer. Either confirmation that it's still right, or deliberate evolution.</p>
<p><strong>Input:</strong> Phase 5 metrics. Quarterly buyer feedback. Competitive landscape changes.</p>
<p><strong>How to do it:</strong> Once a year, block a full day. Review your Phase 1 documents. Are they still accurate? Has the buyer pain shifted? Has your delivery capability evolved? Is your pricing still right? Decide what to keep, what to evolve, what to retire.</p>
<p><strong>Done-when criteria:</strong> End of each year, you have an explicit decision: "this is still the offer for next year" or "here is what changes."</p>
<p><strong>Common failure modes:</strong> Skipping the annual review. Refreshing the offer without buyer feedback to support it. Refreshing for vanity reasons (you got bored) instead of strategic ones.</p>
<hr>
<h3>Step 5.5 — Scale Decision</h3>
<p><strong>Produces:</strong> A deliberate choice about whether to scale vertically (more clients in same niche), horizontally (same offer in adjacent niches), or stay solo.</p>
<p><strong>Input:</strong> 18+ months of operating data. Honest self-assessment of what you actually want.</p>
<p><strong>How to do it:</strong> This decision is more about you than about the business. Some operators want to stay a solo expert with high margins and short hours. Some want to build a firm. Both are legitimate. The mistake is drifting into one without choosing.</p>
<p>If scaling vertically: hire associate practitioners, document delivery extensively, develop training for them, plan for quality control. If scaling horizontally: pilot the new niche before committing, treat it as Phase 1 again from scratch. If staying solo: raise prices.</p>
<p><strong>Done-when criteria:</strong> Explicit written decision with criteria for revisiting.</p>
<p><strong>Common failure modes:</strong> Drifting into scaling because it sounds like success. Hiring before SOPs are documented (chaos compounds). Hiring before you've explicitly chosen what role you want.</p>
<hr>
<h2>The Feedback Loops</h2>
<p>The original document called this the "Master Loop." Here are the actual loops, named honestly:</p>
<p><strong>Phase 5.1 metrics → Phase 1.2 pain doc.</strong> When your conversation rate or close rate drops, the message has stopped resonating. The buyer's pain has shifted. Re-do pain discovery.</p>
<p><strong>Phase 5.2 buyer feedback → Phase 2.3 lead magnet, Phase 2.4 sales page, Phase 1.3 offer.</strong> Buyer language captured in feedback calls flows directly into asset copy. Their objections become your FAQ. Their unmet needs become your next offer.</p>
<p><strong>Phase 5.3 A/B test results → Phase 2 assets, Phase 3.4 content cadence.</strong> Winning variants get codified. Losing patterns get retired.</p>
<p><strong>Phase 4.3 knowledge library → Phase 3.4 content, Phase 2.3 lead magnet.</strong> Your sanitized case examples become content. Your most-asked questions become lead magnets. The library compounds the marketing.</p>
<p><strong>Phase 5.4 offer refresh → all of Phase 1.</strong> Once a year, the entire foundation gets revisited.</p>
<p>These loops are not magic. They are scheduled review meetings with yourself. The discipline is in keeping them on the calendar.</p>
<hr>
<h2>Closing — What Makes This Work</h2>
<p>This document gives you structure. It does not give you discipline. The structure is portable; discipline is not. The operators who will get value from this skeleton are the ones who:</p>
<ul>
<li>Walk Phase 1 fully before launching, even when it feels slow</li>
<li>Set kill criteria and honor them</li>
<li>Track what's working and what isn't, monthly</li>
<li>Talk to actual buyers, quarterly</li>
<li>Refresh the foundation, annually</li>
<li>Resist the temptation to add tools, agents, and complexity in place of doing the work</li>
</ul>
<p>The "agentic" layer in 2026 is real for narrow jobs. It is mostly theater for unbounded creative or strategic work. AI saves 30–50% of time on editing, formatting, and synthesis tasks. It does not save time on thinking, on listening to buyers, on building credibility, or on the relationship work that actually closes high-ticket professional service engagements. Operators who try to substitute AI for those things produce volume without conversion.</p>
<h3>The Identity Commoditization risk</h3>
<p>This is the meta-risk that runs across every phase of this document, and it deserves to be named explicitly.</p>
<p><strong>The mechanism:</strong> When ten operators in your niche all use the same AI tools with similar prompts to produce content, outreach, lead magnets, and proposals, their output converges. Buyers can tell. Not always consciously — sometimes just as a vague sense that "everyone sounds the same now." When that happens at scale, the entire niche commoditizes. Buyers stop trying to identify the best provider and shop on price. Your price floor collapses. Your margin compresses. The work you trained for thirty years to do gets valued like a generic service.</p>
<p><strong>Why this is the central 2026 risk for high-ticket professional services:</strong> Your buyer is paying premium prices because you bring something specific — credentials, judgment, a way of seeing problems, a track record. AI commodifies the wrappers around those things (your emails, your posts, your reports) faster than it commodifies the substance. If the wrappers all look the same, buyers default to lowest price because they cannot tell the substance apart from outside.</p>
<p><strong>How to defend against it:</strong></p>
<ul>
<li><strong>Use AI for editing and synthesis, never for thinking.</strong> Draft your post yourself, then have AI tighten it. Not the other way around.</li>
<li><strong>Feed your AI tools your specific intellectual property</strong> — your prior reports, your characteristic phrases, your case examples, your point of view. A model with no context about you produces generic output. A model fed your archive produces output in your voice. This is what the Knowledge Management library in Step 4.3 is actually for.</li>
<li><strong>Reserve the highest-stakes artifacts for hand-craftsmanship.</strong> Sales pages, expert reports, depositions, anything a buyer reads carefully — these get written by you, not by AI. Use AI to refine, never to generate.</li>
<li><strong>Make your content carry signals only you can produce.</strong> Specific case numbers from your prior work. A photograph from a job site. A technical diagram in your hand. A recording of your voice. Anything that proves a human did the work.</li>
<li><strong>Audit yourself quarterly.</strong> Read three of your recent outreach messages aloud. Read three competitor outreach messages aloud. If you can't immediately tell which is yours, you have a problem.</li>
</ul>
<p>The operators who win in 2026 use AI as a force multiplier on a distinctive practice. The operators who lose use AI as a substitute for one. Same tools, opposite outcomes.</p>
<p>The work is the work. This document tells you what the work is and in what order. The rest is on you.</p>
<hr>
<h2>Where the existing RISER artifacts fit</h2>
<table><thead><tr><th>Phase / Step</th><th>RISER artifact</th></tr></thead><tbody><tr><td>1.2 Pain Discovery</td><td>MVO Decision Engine (Gates 00½, 01) · Pain Discovery Tool Catalog (41 tools)</td></tr><tr><td>1.3 Offer Hypothesis</td><td>MVO Decision Engine (Gates 04–06) · Marketing Plan Generator (section 08 of every plan)</td></tr><tr><td>1.4 MVP Definition</td><td>MVO Decision Engine (full 17-gate sequence)</td></tr><tr><td>2.1 Competitive Intel</td><td>MVO Decision Engine (Gate 03 Competitive Moat)</td></tr><tr><td>2.3 Lead Magnet</td><td>Marketing Plan Generator (section 05 of every plan)</td></tr><tr><td>3.1 Warm Outreach</td><td>Marketing Plan Generator (section 09 outreach scripts)</td></tr><tr><td>3.2 Dream 100</td><td>Client Acquisition Catalog (Dream 100 template, 39-tool stack)</td></tr><tr><td>3.3 Outreach Cadence</td><td>Marketing Plan Generator (section 09) · Client Acquisition Catalog (Channel 6 outreach + CRM)</td></tr><tr><td>3.4 Content Distribution</td><td>Marketing Plan Generator (section 03 Where They Gather, section 04 Channel Priority, sections 06+07 hook/headline/cadence)</td></tr></tbody></table>
<p>The widgets generate the artifacts. This document tells you when and why to use them. Together they form a working operator's plan, not an unbeatable mastermind 2026 unstoppable scaling agentic essay.</p>
<p>The work is the work.</p>
<p><strong>Captain out.</strong></p>
</body>
</html>

Assigned source documents: RISER-Pricing-Architecture.docx — source 1 ·

Pricing architecture: connect buyer outcomes, scope and capacity

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

Video placeholder

Video to be recorded: building and checking a value ladder. The complete section scripts follow.

Supporting documents: RISER-Pricing-Architecture.docx

Curriculum outline

A value ladder earns the next purchase
Free First Dollar Forge: create a useful first result
Forge Activated: distinguish the support package from the free tool
Ignition Engine: sell a defined ten-stage output package
Empire Starter Kit: audit the bundle and its promises
Full MOS: package the operating system with version clarity
Productized service: charge for accountable delivery
Four service specifications and their next steps
Capacity: reconcile hours, concurrency and revenue
Community continuity: model retention as well as membership
Buyer-path model: keep denominators and time horizons consistent
Scale forecast: turn proposed totals into a testable model
Launch sequence: use evidence gates before calendar promises
Route the buyer by the work they need done

Framework connection

Use the Brunson value-ladder principle to connect each delivered result to an appropriate next offer. Use Hormozi’s outcome, confidence, time and effort framework to evaluate the actual benefit and burden. Pair both with evidence of buyer need, reliable fulfillment and honest pricing.

ClickFunnels — audience relationships and value-ladder progression · Acquisition.com — Offers education

1. A value ladder earns the next purchase

A value ladder connects a sequence of useful outcomes. The first purchase should solve a real problem and reveal the next appropriate decision. Ask what the buyer has achieved at the end of each rung and whether another offer is actually needed. A higher price alone does not create a higher-value rung.

This source organizes its architecture as Free, Tools, Systems and Services, with community continuity as an additional ongoing offer. It calls the ladder eight rungs, but names ten offerings when the four services and community are included. Keep the named offers visible rather than forcing them into an unsupported eight-rung count.

Treat the prices and delivery promises in this lesson as the source’s proposed commercial design. They are not confirmation of current products, checkout prices, available support, guarantees or results. The useful implementation decision is which offer you can deliver reliably next; do not launch every offer at once.

Supporting documents: RISER-Pricing-Architecture.docx

Original source data for this teaching point — includes the source’s uncorrected claims

The Core PrincipleA value ladder is not a price list. Every rung earns the right to offer the next one. The buyer moves up because the previous rung delivered a result that made the next rung feel like the obvious next step. Every rung below is designed to produce that moment. Never launch all rungs simultaneously — the sequence matters as much as the prices.

2. Free First Dollar Forge: create a useful first result

The proposed free entry point exchanges access for an email address. Its scope is a niche-specific MVO builder, an offer-format qualifier, an Offer Formula, a four-path $1,000 calculator, a Structural Drift Blocklist, a Fulfillment Blueprint, scripts and a 14-day sprint plan. Explain each output as a planning artifact: the calculator models combinations of price and sales, while the blocklist keeps the proposed service from drifting into unrelated work.

The source describes a six-phase Claude-powered tool. Related Forge files use different phase counts and sprint lengths, so identify the actual version before demonstrating it. A tool-generated niche plan still needs human checking against buyer evidence, feasibility and truthful claims.

Its suggested conversion path is a three-email sequence on days 0, 3 and 7 leading to the $27 or $197 offer. Teach the purpose of each follow-up as helping the buyer implement and choose a relevant next step. The assertions that every output feels specific and every minute of friction loses subscribers are hypotheses to test, not established performance facts. This lesson does not activate email collection or a campaign.

Supporting documents: RISER-Pricing-Architecture.docx · riser-first-dollar-forge-v3 (2).html · riser-first-dollar-forge-v3 (2).html · riser-first-dollar-forge.html

Original source data for this teaching point — includes the source’s uncorrected claims

FREE First Dollar Forge ★ RECOMMENDED $0 (email required)
→ 6-phase MVO builder — Claude API powered, any niche
→ Qualifier logic tree that auto-selects the right offer format
→ Offer Formula, $1K four-path calculator, Structural Drift Blocklist
→ Fulfillment Blueprint + word-for-word scripts + 14-day sprint planPricing rationale: The tool itself is the lead magnet. Nobody who runs it for their niche leaves thinking the output is generic. Every minute of friction at the free tier costs email subscribers — make it frictionless.Conversion path: Free
→ 3-email sequence (Day 0/3/7)
→ $27 or $197 offer

3. Forge Activated: distinguish the support package from the free tool

The $27 entry offer uses the same Forge tool. Its additional scope is a Negative Avatar Checklist describing 15 buyer types and qualifying questions, a 21-day Notion sprint template with daily checkboxes and targets, the day-0/3/7 onboarding emails, and priority email support limited to one offer-design review round. State those boundaries before selling the package.

This is an implementation and support offer, not a different tool. The source says the free-to-paid difference is pure psychology, but the listed checklist, template and review are real deliverables. Teach both the commitment hypothesis and the concrete support difference. Do not promise that payment necessarily makes a learner more likely to implement.

The next proposed offer appears immediately after checkout: Ignition Engine at $197. The source’s 20–30% conversion expectation is unverified. Measure eligible buyers shown the offer, completed purchases, refunds and incremental delivery cost before relying on any conversion forecast. The 21-day template here differs from the free offer’s 14-day plan; preserve both labels and explain their intended version.

Supporting documents: RISER-Pricing-Architecture.docx · riser-first-dollar-forge-v3 (2).html · riser-first-dollar-forge-v3 (2).html · riser-first-dollar-forge.html

Original source data for this teaching point — includes the source’s uncorrected claims

ENTRY OFFER · $27 First Dollar Forge — Activated $27
→ Everything in the free Forge — no difference in the tool itself
→ Negative Avatar Checklist — 15 types of buyers that waste your time + qualifying questions
→ 21-day Notion Sprint Template with checkboxes and daily targets
→ 3-email onboarding sequence (Days 0, 3, 7) sent to their inbox
→ Priority email support for Phase 3 offer design (one-round review)Pricing rationale: The tripwire converts browsers into buyers. Someone who pays $27 is dramatically more likely to implement than someone who downloads for free. The delta between free and paid is pure psychology, not product.Conversion path: $27
→ OTO immediately after checkout: Ignition Engine at $197 (expect 20-30% conversion)

4. Ignition Engine: sell a defined ten-stage output package

The core price proposal is $197 introductory and $297 standard. Its ten-stage scope begins with Psychographic DNA, market gaps and a validation score from 0 to 50. Stage 2 specifies a six-rung ladder with each rung’s price, format and transformation. Stage 3 produces hooks, a mechanism statement and objection responses.

Stages 4–6 cover an eight-week content calendar, email indoctrination sequence and traffic strategy. Stages 7–9 cover an automation-stack specification, scaling roadmap, AI command layer and CEO operating system. Stage 10 supplies a 100-question prelaunch Forensic Scorecard. All ten stage outputs are proposed as a downloadable package the buyer keeps. Verify the actual tool and output files before representing that scope as delivered.

The document proposes raising the price after 20 sales and five testimonials, then offering an upgrade to the $297 Starter Kit at checkout or in a seven-day sequence. Those counts are suggested evidence gates, not proof that the new price is optimal. The claims about fastest-closing price and replacing $5,000–$20,000 in consulting are unsupported comparisons. Use demonstrated output quality, support cost and buyer response to evaluate the price.

Supporting documents: RISER-Pricing-Architecture.docx

Original source data for this teaching point — includes the source’s uncorrected claims

CORE OFFER · $197 RISER Ignition Engine ★ RECOMMENDED $197 intro / $297 standard
→ 10-stage idea-to-flywheel pipeline — Claude API powered, any niche
→ Stage 1: Psychographic DNA with market gap analysis and validation score (0-50)
→ Stage 2: 6-rung Value Ladder with pricing, format, and transformation per rung
→ Stage 3: Complete messaging system — hooks, mechanism statement, objection responses
→ Stages 4-6: Content calendar (8 weeks), email indoctrination sequence, traffic strategy
→ Stage 7-9: Automation stack spec, scale roadmap, AI command layer, CEO operating system
→ Stage 10: Forensic Scorecard — 100-question pre-launch operator audit
→ Full download package of all 10 stage outputs — yours permanentlyPricing rationale: $197 is the fastest-closing price for a tool that replaces $5,000-$20,000 of consulting work. The value ratio is overwhelming. Raise to $297 standard after 20 sales and 5 testimonials — the proof justifies the increase.Conversion path: $197
→ upgrade offer to $297 Empire Starter Kit bundle at checkout or via 7-day email sequence

5. Empire Starter Kit: audit the bundle and its promises

At the proposed $297 bundle price, the buyer receives Activated Forge, the full Ignition Engine, and three Social Media Sales Packages. Volume 1 covers hooks, scripts, captions, direct messages, launch calendar and sales-page copy. Volume 2 covers Stories, carousels, follow-up scripts, automation specification and upsell architecture. Volume 3 covers a niche gate, mechanism framework and 28-day launch calendar.

The source also proposes all future v2.x updates to both tools without additional charge and a 30-day First Sale or Full Refund guarantee. These are terms to define and support operationally before making an offer: identify eligible versions, support boundaries, refund conditions and the evidence needed to fulfill the promise. They are not activated by adding this training page.

The claimed $47 saving cannot be established from the listed prices. Activated plus the introductory Engine totals $224; at the standard Engine price they total $324. The social-package standalone prices are missing. Specify a genuine comparison basis before claiming a saving. The proposed next step is a 30-day email sequence toward the $997 Full MOS. Bundle completeness should solve the buyer’s next obstacle, not merely add more files.

Supporting documents: RISER-Pricing-Architecture.docx · RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx

Original source data for this teaching point — includes the source’s uncorrected claims

BUNDLE · $297 Empire Starter Kit $297
→ RISER First Dollar Forge — Activated version
→ RISER Ignition Engine — full 10-stage pipeline
→ Social Media Sales Package Vol 1 — hooks, scripts, captions, DMs, launch calendar, sales page copy
→ Social Media Sales Package Vol 2 — Stories, carousels, follow-up scripts, automation spec, upsell architecture
→ Social Media Sales Package Vol 3 — Niche gate, mechanism framework, 28-day launch calendar
→ All future v2.x updates to both tools at no additional cost
→ 30-day 'First Sale or Full Refund' guaranteePricing rationale: The bundle saves $47 vs buying separately and adds the Social Media Sales Package — which produces the leads the tools then convert. The savings are modest; the completeness is the selling point. 'Everything you need from zero to deployed' is the offer.Conversion path: $297
→ 30-day email sequence
→ $997 Full MOS upgrade

6. Full MOS: package the operating system with version clarity

The proposed $997 Full MOS includes everything in the Starter Kit, 95-plus SOPs across nine legacy tracks, the cross-referenced Master SOP Catalogue and filing system, the Ignition Master System Prompt for Claude Projects, all 55 legacy course frameworks, future SOP and tool releases, and a private 30-minute integration onboarding call.

Those nine-track/55-course labels belong to the source architecture. The current academy still follows the assigned twelve-course spreadsheet. Use the catalogue to trace document identities without silently rebuilding the live curriculum around legacy numbering. Also distinguish permanent downloads, access duration, future-update scope and onboarding capacity.

The source suggests waiting for at least ten lower-tier testimonials and holding $997 for six months, then offering the $47 monthly community. Treat these as launch-planning choices. The comparison with $2,000–$5,000 courses and the claim of superior framework value need evidence before use in selling. Testimonials must describe real experiences; the number alone does not establish readiness.

Supporting documents: RISER-Pricing-Architecture.docx · RISER-Master-SOP-Catalogue (1).docx · RISER-Master-SOP-Catalogue (1).docx

Original source data for this teaching point — includes the source’s uncorrected claims

FULL SYSTEM · $997 RISER Nation Full MOS $997
→ Everything in the Empire Starter Kit
→ All 95+ SOPs across 9 tracks — every framework, every system, every workflow
→ Master SOP Catalogue with complete cross-references and filing system
→ RISER Ignition Master System Prompt — for Claude Projects setup
→ All 55 course frameworks — the complete intellectual property stack
→ Access to all future SOPs and tool updates as they are released
→ Private 30-minute onboarding call to set up the Claude Projects integrationPricing rationale: Only launch this after 10+ testimonials from lower-tier buyers. The social proof must justify the price. The comp is $2,000-$5,000 for a knowledge business course with a fraction of these frameworks. $997 is aggressive value positioning — hold it there for the first 6 months.Conversion path: $997
→ continuity offer at $47/month Empire OS Community

7. Productized service: charge for accountable delivery

A productized service uses a repeatable process to deliver a defined result for the client. The operator runs the tools, checks their outputs and produces the promised deliverable. The fee pays for scope, judgment, execution and responsibility, rather than simply access to software.

The source recommends beginning with the Niche Report and First Dollar Sprint to obtain delivery evidence before expanding. Do not assume they automatically produce the fastest testimonials. Run controlled first engagements, record actual hours and client outcomes, and obtain permission before using feedback as public proof. The later calendar postpones some services, so readiness gates take priority over conflicting month labels.

Supporting documents: RISER-Pricing-Architecture.docx

Original source data for this teaching point — includes the source’s uncorrected claims

The Service ModelProductized services use the tools as the delivery engine but remove the DIY requirement. You run the tool for the client. They receive a professional deliverable. The price is justified not by the tool but by the expertise applied and the result delivered. Start with the two lowest rungs (Niche Report + First Dollar Sprint) — they produce the fastest testimonials.

8. Four service specifications and their next steps

The Niche Intelligence Report is proposed at $297 with a three-day turnaround and no calls. Deliver a 10–15-page PDF covering Stage 1 Psychographic DNA, market gap, validation score, buyer-language map and the source’s “sewer leak” identification. Keep that source term visible while using the underlying method to establish what it means for the actual niche. The delivery email can offer a relevant $597 Full Audit. Two reports gross $594, three dollars below one $597 Audit; this arithmetic does not establish equal workload or value.

The $500 First Dollar Sprint runs for five days. Its scope is a personalized Offer Formula, a reasoned $1,000 path recommendation, ten named prospects with platforms, buyer-specific direct-message scripts and a 30-minute walkthrough. One sale grosses $500. Prospect research is part of the paid work; identifying a person is not permission to contact them. An appropriate next step after the buyer’s first client may be a $1,500 Build Sprint, subject to their needs and readiness.

The $597 Full Ignition Audit has a seven-day target, all ten stages in a deployment document, a 60-minute strategy call, personalized implementation order and a niche-specific starter pack of five hooks, three captions and two direct-message scripts. Two sales gross $1,194. Its price is $300 above the Report, but that premium should be justified through actual scope and delivery cost. The proposed 30-day follow-up can offer the Build Sprint; “most buyers ascend” is an unverified source claim.

The $1,500 Empire Build Sprint lasts 21 days and includes the Full Audit, three weekly 60-minute calls, a built and published lead-magnet page, a written and loaded email welcome sequence, formatted first-offer-page copy, 21-day WhatsApp/direct-message implementation access and introductions to two potential referral or JV partners. Only promise introductions you can legitimately arrange. Its next proposed offer is community membership. Four to six sales would gross $6,000–$9,000, but the later capacity table restricts this tier to three or four clients; use a measured workload plan rather than the larger headline.

Supporting documents: RISER-Pricing-Architecture.docx · riser-first-dollar-forge-v3 (2).html · riser-first-dollar-forge-v3 (2).html · riser-first-dollar-forge.html

Original source data for this teaching point — includes the source’s uncorrected claims

Service	Price	Turnaround	What's Delivered	Pricing Rationale	Conversion Path
Niche Intelligence Report	$297	3 days	Stage 1 of the Ignition Engine run for their specific niche. Formatted 10-15 page PDF: Psychographic DNA, market gap, validation score, buyer language map, sewer leak identification. No calls.	2 sales = $594 — close to the $597 combined. Lowest-risk entry to your services. Produces a testimonial in 72 hours. The document itself sells the next tier — 'Stage 1 showed you what's possible, here's all 10 stages.'	→ Upsell to Full Ignition Audit ($597) within the delivery email
First Dollar Sprint	$500	5 days	First Dollar Forge run for their specific niche. Deliverable includes: personalised Offer Formula, $1K path recommendation with rationale, 10 specific outreach prospects identified by name/platform, word-for-word DM scripts customised for their exact buyer, 30-minute walkthrough call.	Single sale = $500 toward first $1K. Designed for newbies who want the Forge done for them. The 10 outreach prospects identified is the highest-value deliverable — removes the 'I don't know who to contact' excuse completely.	→ Upsell to Empire Build Sprint ($1,500) for the operator who gets their first client and wants to systematise
Full Ignition Audit	$597	7 days	All 10 stages of the Ignition Engine run for their specific niche. Formatted as a professional deployment document. Includes: 60-minute strategy call, personalised implementation order, and the full social media starter pack (5 hooks + 3 captions + 2 DM scripts) for their specific niche.	2 sales = first $1,194. The 60-minute call turns a document into a relationship. Most Full Audit buyers ascend to the Build Sprint within 30 days. The social media starter pack adds enough tangible value to justify the $300 premium over the Niche Report.	→ Upsell to Empire Build Sprint ($1,500) via 30-day follow-up sequence
Empire Build Sprint	$1,500	21 days	Everything in the Full Ignition Audit. Plus: 3 × 60-minute weekly calls, lead magnet page built and published, email welcome sequence written and loaded, first offer page copy written and formatted, 21-day WhatsApp/DM access for implementation questions, introduction to 2 potential referral or JV partners.	4-6 clients/month = $6,000-$9,000 from this tier alone — without any additional team. The DWY model is the highest-margin use of the system. Every step of delivery uses the tools you've already built. Delivery overhead per client is approximately 8-12 hours over 21 days.	→ Continuity: Empire OS Community at $47/month post-sprint

9. Capacity: reconcile hours, concurrency and revenue

The source estimates Reports at two to three hours each and ten to twelve clients per month, producing $2,970–$3,564 gross. It suggests training a VA after ten manual runs. First Dollar Sprints are estimated at four to five hours and six to eight clients, or $3,000–$4,000 gross; prospect research alone is estimated at 45–60 minutes per client. These estimates need time tracking before they become staffing assumptions.

Audits are estimated at six to eight hours and five to six clients, yielding $2,985–$3,582 gross. Tuesday/Thursday call batching is a scheduling suggestion. The Build Sprint capacity table uses ten to twelve hours across 21 days and three to four clients, yielding $4,500–$6,000; its earlier description used eight to twelve hours and four to six clients. Track hours and concurrent commitments, including message access, before choosing an operational cap.

The mixed example of two Build Sprints, three Audits and four Reports totals $3,000 + $1,791 + $1,188 = $5,979, not the printed $8,391. If “Sprints” instead means First Dollar Sprints, it totals $3,979. With Build Sprints, the stated delivery-hour ranges sum to 46–60 hours before selling, administration, revisions and ongoing support. The source’s $8,000–$10,000 solo-capacity assertion therefore is not proven by that example.

Plan with available working hours minus acquisition, administration and contingency. Divide the remaining capacity among the actual service mix, and separately check overlapping engagements. Gross revenue is not profit: deduct labor, tool charges, payment costs, refunds and other fulfillment expenses before judging which tier has the strongest margin.

The source also says never more than four simultaneous Build Sprint engagements. Simultaneous clients and monthly sales are different counts: a twenty-one-day service sold late in one month can overlap new engagements in the next. Maintain a dated capacity calendar including calls, revisions and message support. Treat the four-client cap as the source’s proposed operating limit, not proof that every operator can handle four.

Supporting documents: RISER-Pricing-Architecture.docx

Original source data for this teaching point — includes the source’s uncorrected claims

Service	Hours Per Client	Max Clients/Month (Solo)	Monthly Revenue at Capacity	Notes
Niche Intelligence Report	2-3 hours	10-12 clients	$2,970-$3,564	Can be partially delegated to a VA trained on the tool after 10 manual runs
First Dollar Sprint	4-5 hours	6-8 clients	$3,000-$4,000	The outreach prospect research is the most time-intensive step — 45-60 minutes per client
Full Ignition Audit	6-8 hours	5-6 clients	$2,985-$3,582	Includes call time — schedule calls on Tuesdays and Thursdays to batch
Empire Build Sprint	10-12 hours across 21 days	3-4 clients	$4,500-$6,000	Never run more than 4 simultaneously — quality drops and the WhatsApp access becomes unmanageable
Mixed portfolio (optimal)	Varies	2 Sprints + 3 Audits + 4 Reports	$8,391	Maximum solo revenue without quality degradation: approximately $8,000-$10,000/month from services alone

10. Community continuity: model retention as well as membership

The proposed Empire OS Community is $47 monthly or $397 annually. Its scope is a monthly live niche walkthrough of the Ignition Engine with Q&A, new tool and SOP updates, a private Discord or Circle community with peer accountability, and one monthly implementation challenge. Define who facilitates these commitments and how much support each member can expect.

Twelve monthly payments total $564, so paying $397 annually saves $167 if compared with staying subscribed monthly for the full year. A hundred active monthly-paying members gross $4,700 per month and two hundred gross $9,400. Annual cash receipts, refunds, churn, taxes and service costs require separate treatment; member totals alone do not guarantee recurring net income.

The source proposes launching after at least 20 Full MOS buyers, offering annual membership at checkout, and an annual upsell after six months. Its claimed 47% annual conversion and frictionless affordability are unsupported assumptions. Measure invitation, activation, engagement, renewal and cancellation rather than forecasting that every prior buyer joins or remains.

Supporting documents: RISER-Pricing-Architecture.docx

Original source data for this teaching point — includes the source’s uncorrected claims

CONTINUITY · $47/month Empire OS Community $47/month or $397/year
→ Monthly live session: a new niche run through the full Ignition Engine pipeline live, with Q&A
→ Access to all tool updates and new SOP releases the month they are built
→ Private community (Discord or Circle) with operator peer accountability
→ Monthly implementation challenge: one specific deliverable per month as a group
→ Annual plan saves $167 vs monthly — offer at checkout for all buyers of the Full MOSPricing rationale: $47/month is frictionless for any operator who has spent $197+ on the tools. At 100 members: $4,700/month. At 200 members: $9,400/month. This is the compounding revenue engine that stabilises cashflow against the variability of one-time product sales. Launch the community only after the Full MOS has 20+ buyers — you need enough members to make the community feel alive.Conversion path: Community
→ annual plan upsell at 6-month mark (47% of monthly members convert to annual)

11. Buyer-path model: keep denominators and time horizons consistent

Read each source row as a scenario, not an observed conversion rate. Free-only subscribers contribute zero. The $27 path at 15–20% contributes $4.05–$5.40 per original subscriber; the $224 Forge-plus-Engine path at 5–8% contributes $11.20–$17.92; the $297 bundle path at 3–5% contributes $8.91–$14.85. The $724 Forge-plus-Engine-plus-Sprint path at 2–3% contributes $14.48–$21.72.

The $1,858 bundle-plus-MOS-plus-community path includes $297 + $997 + twelve $47 payments. At 0.5–1%, its weighted contribution is $9.29–$18.58 per original subscriber over that assumed year. A directly acquired Build Sprint grosses $1,500 but has no subscriber-path probability in the table; model its acquisition separately.

Adding the listed weighted paid paths gives $47.93–$78.47 per subscriber, but this is not monthly revenue. The probabilities, including free-only, total only 80.5–97% depending on endpoints, and the source does not establish whether paths are mutually exclusive. Define an exhaustive cohort or allow an explicit residual, prevent double-counting a buyer’s earlier purchases, and assign dates, refunds and actual retention before using a forecast.

Supporting documents: RISER-Pricing-Architecture.docx

Original source data for this teaching point — includes the source’s uncorrected claims

Buyer Path	Products Purchased	Total Revenue Per Customer	Probability (of email subscriber)	Weighted Value
Free only	Lead magnet only	$0	55-60%	$0
Free → $27 tripwire	Forge Activated	$27	15-20%	$4.05-$5.40
Free → $27 → $197 Engine	Forge + Engine	$224	5-8% of all subscribers	$11.20-$17.92
Free → $297 bundle direct	Empire Starter Kit (direct from social)	$297	3-5% of all subscribers	$8.91-$14.85
Free → $27 → $197 → $500 service	Forge + Engine + First Dollar Sprint	$724	2-3% of all subscribers	$14.48-$21.72
Free → $297 → $997 MOS → $47/mo	Bundle → Full MOS → Community (12 months)	$1,858	0.5-1% of all subscribers	$9.29-$18.58
Direct service (no ladder)	Empire Build Sprint booked from DM outreach	$1,500	Not applicable — direct outreach	N/A

12. Scale forecast: turn proposed totals into a testable model

The source proposes 1,000 new subscribers per month with $5,400–$9,000 product revenue, $2,000–$4,700 services and $470–$2,350 continuity, summing to $7,870–$16,050. The sums are arithmetically correct; the underlying conversions, timing and service-capacity assumptions are not established by the preceding table.

Build a monthly cohort schedule: new subscribers, buyers by mutually exclusive path, dates of purchases, active members, cancellations, refunds and actual service availability. Reconcile each revenue line to units times price. Community revenue can accumulate only while retained cohorts and new members exceed churn and other losses. Product delivery and support also impose costs even when the downloadable product scales.

Keep the source’s approximately $8,000 service cap as a proposed planning assumption, not a verified operational maximum. Replace it with the capacity model derived from real hours, concurrent projects and required quality. Use the scenario to ask what evidence is missing, rather than presenting it as an earnings expectation.

Supporting documents: RISER-Pricing-Architecture.docx

Original source data for this teaching point — includes the source’s uncorrected claims

The Revenue Model at ScaleAt 1,000 new email subscribers per month with these conversion rates, expected monthly revenue: $5,400-$9,000 from product sales + $2,000-$4,700 from services + $470-$2,350 from community continuity = $7,870-$16,050 total. The community continuity compounds monthly. Services cap at solo capacity (~$8,000/month). Product sales scale with traffic.

13. Launch sequence: use evidence gates before calendar promises

The source’s Month 1 starts only the free Forge and $197 Engine, targets $1,500–$3,000 and seeks five to ten Engine buyers. Month 2 adds the $27 tripwire and $500 First Dollar Sprint, treats the bundle as optional, targets $3,000–$5,000 and seeks three to five service testimonials. These are planning goals, not expected earnings.

Month 3 proposes the $297 bundle and $997 MOS after ten-plus tool testimonials, plus a community waitlist, with a $5,000–$9,000 target. Month 4 proposes the $1,500 Build Sprint after five Full Audit testimonials and the community launch, targeting $8,000–$15,000-plus. Month 5-plus raises Engine to $297, introduces the $597 Audit and emphasizes service efficiency and retention, targeting $12,000–$20,000-plus.

There is a dependency conflict: Month 4 requires evidence from an Audit the calendar introduces in Month 5. Resolve the sequence by piloting and validating the Audit before the Build Sprint, or defer the Sprint until its prerequisites exist. Also satisfy the community’s separate 20-MOS-buyer gate. The evidence-led sequence is an authored correction; the original calendar remains visible below.

Before increasing price or adding another rung, check delivered outcomes, truthful proof, buyer fit, support capacity, working cash and a clear reason for the next offer. A calendar date or testimonial count alone is insufficient.

Supporting documents: RISER-Pricing-Architecture.docx

Original source data for this teaching point — includes the source’s uncorrected claims

Month	What to Launch	Revenue Target	Why This Order
Month 1	Free First Dollar Forge (email capture) + $197 Ignition Engine — two products only. No bundle. No services yet.	$1,500-$3,000	Prove the conversion path before complicating it. Build the email list. Get the first 5-10 Ignition Engine buyers.
Month 2	Add $27 Forge Activated to the tripwire position. Add the $500 First Dollar Sprint (productized service). Bundle is optional at this stage.	$3,000-$5,000	The tripwire converts casual downloaders. The service converts high-intent buyers who don't want to DIY. Get 3-5 service testimonials.
Month 3	Launch $297 Empire Starter Kit bundle. Launch $997 Full MOS (after 10+ tool testimonials). Introduce the community waitlist.	$5,000-$9,000	The bundle and Full MOS both require social proof to justify. Month 3 testimonials are what make them credible.
Month 4	Add $1,500 Empire Build Sprint (after 5 Full Audit testimonials). Launch Empire OS Community.	$8,000-$15,000+	High-ticket DWY only works with proof. Community launches with an audience that already trusts the product.
Month 5+	Raise Ignition Engine from $197 → $297. Add $597 Full Audit. Optimise for service delivery efficiency and community retention.	$12,000-$20,000+	Price increase is justified by accumulated proof. Full Audit fills the gap between the bundle and the Sprint.

14. Route the buyer by the work they need done

For someone unsure what to sell, the source routes to free Forge or $27 Activated. Explain that they will work through buyer, offer and outreach planning; its 20-minute completion claim is an estimate requiring the actual tool and user testing. For a buyer with a niche but no system, it routes to $197 Engine or $297 Starter Kit; ten-stage scope can be described, but the advertised 60-minute complete architecture is not a guaranteed result.

For someone who wants the work done for them, compare the $500 Sprint’s focused offer/prospect/script package with the $597 Audit’s broader ten-stage deployment scope. For someone seeking the full framework library, present the $997 MOS scope only to the extent that the promised documents, updates and access terms exist. “Lifetime access” requires an explicit supported meaning before it becomes a customer-facing commitment.

For implementation assistance, explain the $1,500, 21-day Build Sprint and its three calls, infrastructure and messaging access. Replace the source’s [X] availability token only with real capacity; do not invent scarcity. For ongoing support, explain the $47 monthly or $397 annual community scope and terms. The source pitches are examples for learning, not messages to send or live offers to activate.

Finish by asking the learner to choose one buyer situation, name the next useful outcome, list the exact deliverables, estimate cost and hours, and identify the evidence required before making the offer. This connects the value ladder to buyer fit and makes the price a consequence of a defined service rather than an arbitrary number.

Supporting documents: RISER-Pricing-Architecture.docx · RISER-Master-SOP-Catalogue (1).docx · RISER-Master-SOP-Catalogue (1).docx

Original source data for this teaching point — includes the source’s uncorrected claims

What They Tell You	The Right Product	The Right Price	The Pitch
'I've never made a dollar online and don't know what to sell'	First Dollar Forge (Free) → $27 Activated	Free or $27	'The Forge will run you through exactly what to sell, to whom, and what to say. Takes 20 minutes. Free download at the link.'
'I have a niche and some experience but haven't built the system yet'	Ignition Engine ($197) or Empire Starter Kit ($297)	$197-$297	'The Ignition Engine builds your complete business architecture for your specific niche in 60 minutes. 10 stages. Link in bio.'
'I want someone to do this for me / I don't have time to DIY'	First Dollar Sprint ($500) or Full Ignition Audit ($597)	$500-$597	'I run the tool for your specific niche and deliver a complete action plan with outreach scripts / deployment document. [Turnaround]. Want me to send the details?'
'I'm building seriously and want the full framework'	Full MOS ($997)	$997	'The Full MOS gives you all 55 frameworks, 95+ SOPs, both tools, and the complete social media system. It's everything in one. Lifetime access.'
'I want help implementing, not just a plan'	Empire Build Sprint ($1,500)	$1,500	'The Build Sprint is a 21-day DWY engagement — I build alongside you. Three calls, first infrastructure built, 21-day DM access. [X] spots per month.'
'I want ongoing support and updates'	Empire OS Community ($47/month)	$47/month or $397/year	'Empire OS is a monthly community. New niche runs every month, all tool updates included, peer accountability. $47/month or $397/year.'

Complete original readable source

Native table data, including content omitted from the readable export, is preserved at each corresponding teaching point above. The original document link remains the source of record.

Open complete readable export

RISER NATION
PRICING ARCHITECTURE
VALUE LADDER · OFFER STACK · PRODUCTIZED SERVICES
The complete pricing architecture for the RISER Ignition Engine and First Dollar Forge — including all offer tiers, conversion mechanics, productized service specs, revenue math, and the recommended launch sequence
2026 Edition | risernation.com
Part 1 — The Complete Value Ladder
The ladder has eight rungs across four tiers: Free, Tools, Systems, and Services. Tools generate the leads. Services generate the margin. The middle two tiers generate the most volume.
Part 2 — Productized Services
The Productized Service Capacity Model
One operator can service this many clients per month at each tier without additional help:
Part 3 — Continuity and Community
Part 4 — Revenue Math
The Launch Sequence — What to Build and When
The Offer Stack Decision Tree
Use this to decide which product to present to any given buyer based on what they tell you:
RISER Nation | Pricing Architecture | Value Ladder · Offer Stack · Productized Services | 2026 Edition
The Core Principle
A value ladder is not a price list. Every rung earns the right to offer the next one. The buyer moves up because the previous rung delivered a result that made the next rung feel like the obvious next step. Every rung below is designed to produce that moment. Never launch all rungs simultaneously — the sequence matters as much as the prices.
FREE First Dollar Forge ★ RECOMMENDED $0 (email required)

Pricing rationale: The tool itself is the lead magnet. Nobody who runs it for their niche leaves thinking the output is generic. Every minute of friction at the free tier costs email subscribers — make it frictionless.
Conversion path:
ENTRY OFFER · $27 First Dollar Forge — Activated $27

Pricing rationale: The tripwire converts browsers into buyers. Someone who pays $27 is dramatically more likely to implement than someone who downloads for free. The delta between free and paid is pure psychology, not product.
Conversion path:
CORE OFFER · $197 RISER Ignition Engine ★ RECOMMENDED $197 intro / $297 standard

Pricing rationale: $197 is the fastest-closing price for a tool that replaces $5,000-$20,000 of consulting work. The value ratio is overwhelming. Raise to $297 standard after 20 sales and 5 testimonials — the proof justifies the increase.
Conversion path:
BUNDLE · $297 Empire Starter Kit $297

Pricing rationale: The bundle saves $47 vs buying separately and adds the Social Media Sales Package — which produces the leads the tools then convert. The savings are modest; the completeness is the selling point. 'Everything you need from zero to deployed' is the offer.
Conversion path:
FULL SYSTEM · $997 RISER Nation Full MOS $997

Pricing rationale: Only launch this after 10+ testimonials from lower-tier buyers. The social proof must justify the price. The comp is $2,000-$5,000 for a knowledge business course with a fraction of these frameworks. $997 is aggressive value positioning — hold it there for the first 6 months.
Conversion path:
The Service Model
Productized services use the tools as the delivery engine but remove the DIY requirement. You run the tool for the client. They receive a professional deliverable. The price is justified not by the tool but by the expertise applied and the result delivered. Start with the two lowest rungs (Niche Report + First Dollar Sprint) — they produce the fastest testimonials.
Service
Price
Turnaround
What's Delivered
Pricing Rationale
Conversion Path
Niche Intelligence Report
$297
3 days
Stage 1 of the Ignition Engine run for their specific niche. Formatted 10-15 page PDF: Psychographic DNA, market gap, validation score, buyer language map, sewer leak identification. No calls.
2 sales = $594 — close to the $597 combined. Lowest-risk entry to your services. Produces a testimonial in 72 hours. The document itself sells the next tier — 'Stage 1 showed you what's possible, here's all 10 stages.'
First Dollar Sprint
$500
5 days
First Dollar Forge run for their specific niche. Deliverable includes: personalised Offer Formula, $1K path recommendation with rationale, 10 specific outreach prospects identified by name/platform, word-for-word DM scripts customised for their exact buyer, 30-minute walkthrough call.
Single sale = $500 toward first $1K. Designed for newbies who want the Forge done for them. The 10 outreach prospects identified is the highest-value deliverable — removes the 'I don't know who to contact' excuse completely.
Full Ignition Audit
$597
7 days
All 10 stages of the Ignition Engine run for their specific niche. Formatted as a professional deployment document. Includes: 60-minute strategy call, personalised implementation order, and the full social media starter pack (5 hooks + 3 captions + 2 DM scripts) for their specific niche.
2 sales = first $1,194. The 60-minute call turns a document into a relationship. Most Full Audit buyers ascend to the Build Sprint within 30 days. The social media starter pack adds enough tangible value to justify the $300 premium over the Niche Report.
Empire Build Sprint
$1,500
21 days
Everything in the Full Ignition Audit. Plus: 3 × 60-minute weekly calls, lead magnet page built and published, email welcome sequence written and loaded, first offer page copy written and formatted, 21-day WhatsApp/DM access for implementation questions, introduction to 2 potential referral or JV partners.
4-6 clients/month = $6,000-$9,000 from this tier alone — without any additional team. The DWY model is the highest-margin use of the system. Every step of delivery uses the tools you've already built. Delivery overhead per client is approximately 8-12 hours over 21 days.
Service
Hours Per Client
Max Clients/Month (Solo)
Monthly Revenue at Capacity
Notes
Niche Intelligence Report
2-3 hours
10-12 clients
$2,970-$3,564
Can be partially delegated to a VA trained on the tool after 10 manual runs
First Dollar Sprint
4-5 hours
6-8 clients
$3,000-$4,000
The outreach prospect research is the most time-intensive step — 45-60 minutes per client
Full Ignition Audit
6-8 hours
5-6 clients
$2,985-$3,582
Includes call time — schedule calls on Tuesdays and Thursdays to batch
Empire Build Sprint
10-12 hours across 21 days
3-4 clients
$4,500-$6,000
Never run more than 4 simultaneously — quality drops and the WhatsApp access becomes unmanageable
Mixed portfolio (optimal)
Varies
2 Sprints + 3 Audits + 4 Reports
$8,391
Maximum solo revenue without quality degradation: approximately $8,000-$10,000/month from services alone
CONTINUITY · $47/month Empire OS Community $47/month or $397/year

Pricing rationale: $47/month is frictionless for any operator who has spent $197+ on the tools. At 100 members: $4,700/month. At 200 members: $9,400/month. This is the compounding revenue engine that stabilises cashflow against the variability of one-time product sales. Launch the community only after the Full MOS has 20+ buyers — you need enough members to make the community feel alive.
Conversion path:
Buyer Path
Products Purchased
Total Revenue Per Customer
Probability (of email subscriber)
Weighted Value
Free only
Lead magnet only
$0
55-60%
$0
Forge Activated
$27
15-20%
$4.05-$5.40
Forge + Engine
$224
5-8% of all subscribers
$11.20-$17.92
Empire Starter Kit (direct from social)
$297
3-5% of all subscribers
$8.91-$14.85
Forge + Engine + First Dollar Sprint
$724
2-3% of all subscribers
$14.48-$21.72
$1,858
0.5-1% of all subscribers
$9.29-$18.58
Direct service (no ladder)
Empire Build Sprint booked from DM outreach
$1,500
Not applicable — direct outreach
N/A
The Revenue Model at Scale
At 1,000 new email subscribers per month with these conversion rates, expected monthly revenue: $5,400-$9,000 from product sales + $2,000-$4,700 from services + $470-$2,350 from community continuity = $7,870-$16,050 total. The community continuity compounds monthly. Services cap at solo capacity (~$8,000/month). Product sales scale with traffic.
Month
What to Launch
Revenue Target
Why This Order
Month 1
Free First Dollar Forge (email capture) + $197 Ignition Engine — two products only. No bundle. No services yet.
$1,500-$3,000
Prove the conversion path before complicating it. Build the email list. Get the first 5-10 Ignition Engine buyers.
Month 2
Add $27 Forge Activated to the tripwire position. Add the $500 First Dollar Sprint (productized service). Bundle is optional at this stage.
$3,000-$5,000
The tripwire converts casual downloaders. The service converts high-intent buyers who don't want to DIY. Get 3-5 service testimonials.
Month 3
Launch $297 Empire Starter Kit bundle. Launch $997 Full MOS (after 10+ tool testimonials). Introduce the community waitlist.
$5,000-$9,000
The bundle and Full MOS both require social proof to justify. Month 3 testimonials are what make them credible.
Month 4
Add $1,500 Empire Build Sprint (after 5 Full Audit testimonials). Launch Empire OS Community.
$8,000-$15,000+
High-ticket DWY only works with proof. Community launches with an audience that already trusts the product.
Month 5+
$12,000-$20,000+
Price increase is justified by accumulated proof. Full Audit fills the gap between the bundle and the Sprint.
What They Tell You
The Right Product
The Right Price
The Pitch
'I've never made a dollar online and don't know what to sell'
Free or $27
'The Forge will run you through exactly what to sell, to whom, and what to say. Takes 20 minutes. Free download at the link.'
'I have a niche and some experience but haven't built the system yet'
Ignition Engine ($197) or Empire Starter Kit ($297)
$197-$297
'The Ignition Engine builds your complete business architecture for your specific niche in 60 minutes. 10 stages. Link in bio.'
'I want someone to do this for me / I don't have time to DIY'
First Dollar Sprint ($500) or Full Ignition Audit ($597)
$500-$597
'I run the tool for your specific niche and deliver a complete action plan with outreach scripts / deployment document. [Turnaround]. Want me to send the details?'
'I'm building seriously and want the full framework'
Full MOS ($997)
$997
'The Full MOS gives you all 55 frameworks, 95+ SOPs, both tools, and the complete social media system. It's everything in one. Lifetime access.'
'I want help implementing, not just a plan'
Empire Build Sprint ($1,500)
$1,500
'The Build Sprint is a 21-day DWY engagement — I build alongside you. Three calls, first infrastructure built, 21-day DM access. [X] spots per month.'
'I want ongoing support and updates'
Empire OS Community ($47/month)
$47/month or $397/year
'Empire OS is a monthly community. New niche runs every month, all tool updates included, peer accountability. $47/month or $397/year.'

Offer design, evidence and operating practice

RISER — 8 Offer Mutation Engine — Product Description + Sales Letter

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

Working teaching draft; supporting assets and source claims requiring verification are identified below.

Identify the offer mutation instrument

Offer Mutation Engine is described as a decision instrument for automated iteration, A/B variants and learning loops. Its proposed benefit is reducing poor decisions and regret by turning noisy inputs into decisions that can be enforced. The assigned document is a product description and sales letter. It does not contain an implemented experiment engine, a statistical method or a tested product. Begin with a specific offer and a decision you need to make, rather than treating the product name as proof that automation exists.

D0920 — assigned source supporting this teaching point

Protect attention and the order of work

The document asks us to protect attention from busy-work and protect sequencing through Right Step / Right Time, without skipping prerequisites. For an offer test, identify the customer problem and the evidence needed before changing the offer. In this RISER practice adaptation, keep a short hypothesis record: what changes, why it might help and what outcome would justify the change. A new variant is useful when it answers a question; generating more variants is not itself progress.

D0920 — assigned source supporting this teaching point

Protect capital, morale and long-term outcomes

The remaining protections are preventing a build before proof, rejecting almost-good distractions early, and prioritizing long-term operator outcomes over short-term excitement. Make the tradeoff explicit: what will the experiment consume, what can it teach and what would stop it? These questions are an authored application, because the source supplies no budget limits or proof thresholds. Its language about morale and dopamine is motivational positioning, not clinical evidence.

D0920 — assigned source supporting this teaching point

Record the verdict and reason

The specified decision outputs are PASS, PAUSE or FAIL, or a state placement where applicable. Accompany the verdict with a one-sentence reason and supporting bullets. Define the criterion before looking at the outcome and show which observation supports each bullet. A PASS should mean a defined next action is justified; it should not mean permanent success. The source gives no state definitions, so any proposed definitions must be labeled as a local adaptation.

D0920 — assigned source supporting this teaching point

Record the metrics snapshot

The source requests 30-, 60- and 90-day signals where applicable. Explain what each measure means, the observation dates and what remains missing. For offer variants, keep the audience, exposure and outcome definitions visible so unequal conditions are not mistaken for a better offer. The reporting windows are not universal minimum test durations or fabricated history. The source provides no sample-size, confidence or stopping rules.

D0920 — assigned source supporting this teaching point

Connect decisions to next and blocked steps

The fourth output is the unlocked next step plus blocked steps, called a permission system. Write the action, its owner and the evidence needed to reconsider a blocked action. A document can record a gate; technical enforcement requires a working system. The fifth output is a canonical JSON automation payload, but the actual schema and validation rules are absent. Keep that implementation dependency open rather than inventing an original contract.

D0920 — assigned source supporting this teaching point

Build a bounded learning loop

As an authored exercise, keep the current offer as a reference, propose one meaningful variant, define the observation and review the result before extending the test. Record what was learned even when the variant does not improve the outcome. The source names automated iteration and A/B variants but does not explain how to assign traffic, avoid bias or distinguish noise from an effect. Those details require an explicit experiment design before deployment.

D0920 — assigned source supporting this teaching point

Read the sales argument critically

The headline attributes most business failure to saying yes too often, and the body reframes moving faster than validation as a governance problem. These are unverified positioning claims in this document. They can become useful questions: which commitments lack evidence, and which decisions need clearer ownership? Governance and marketing problems can coexist. Rewrite the promise around a specific supported benefit instead of presenting the broad failure claim as a fact.

D0920 — assigned source supporting this teaching point

Match the three audiences and the call to action

The intended users are operators avoiding wasted quarters, teams or agencies seeking objective gates and audit trails, and system builders seeking licensable, enforceable systems. Each needs different evidence: a decision record, an inspectable history, or an actual system and applicable rights. The call to action is to adopt the instrument, enforce the rule and ship only what earns permission. For this lesson, submit a decision example; the copy does not authorize spending, deployment or changes to anyone's access.

D0920 — assigned source supporting this teaching point

Submit the practice deliverable

Prepare one offer-iteration record with the question, hypothesis, variant, evidence, verdict, one-sentence reason, supporting bullets, applicable metrics, next step and blocked steps. Add a separate list of unresolved schema, testing and enforcement dependencies. Keep the original source accessible so the learner can distinguish the advertised instrument from this authored exercise.

D0920 — assigned source supporting this teaching point

Apply the agreed marketing lenses

Use the Brunson/ClickFunnels Hook, Story, Offer lens to organize a relevant opening, a truthful explanation and a concrete next step. Use the Hormozi/Acquisition.com value lens to examine the desired result, confidence in delivery, waiting time and required effort. This is a RISER teaching adaptation; neither framework supplies missing product evidence or implies endorsement.

D0920 — assigned source supporting this teaching point

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Complete original source text

#8 -🧾Offer Mutation Engine

Automated iteration + A/B variants + learn loops

Product Description

Offer Mutation Engine is a RISER Nation decision instrument designed to reduce bad decisions and regret. It converts noisy inputs into enforceable outputs so you scale with clarity, not chaos.

What It Protects (Doctrine Protection Mode)

* Protects attention: prevents busy-work masquerading as progress.

* Protects sequencing: Right Step / Right Time; no step-skipping.

* Protects capital: blocks build before proof.

* Protects morale: kills “almost good” distractions early.

* Protects long-term operator outcomes over short-term dopamine.

Core Outputs

* Verdict: PASS / PAUSE / FAIL (or state placement where applicable).

* Reason: one sentence + supporting bullets.

* Metrics snapshot (30/60/90-day signals where applicable).

* Unlocked next step + blocked steps (permission system).

* Automation payload: canonical JSON schema.

World-Class Sales Letter

Headline:

Most businesses don’t fail from bad ideas — they fail from saying “yes” too often.

If you're moving faster than you can validate, you don't have a marketing problem — you have a governance problem.

Offer Mutation Engine enforces permission-based building. It tells you what earns a build, what must wait, and what must die — with receipts.

Who This Is For

* Operators who refuse to waste another quarter chasing noise.

* Teams/agencies who need objective gating + audit trails.

* System builders who want something licensable and enforceable.

Call to Action

Adopt the instrument. Enforce the rule. Ship only what earns permission.

RISER · Captain's Logic Operating Doctrine · v1

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

Working teaching draft; supporting assets and source claims requiring verification are identified below.

Start with the suite index and locate your phase

This assigned document is an index to Captain's Logic tools, not the complete operating doctrine. Its ten artifacts comprise one doctrine, five widgets, two Phase 1 step pages and two reference files, serving businesses including crafts, digital products, services, coaching, local businesses and affiliate programs. Preserve every entry and choose the artifact that fits the current work; do not renumber the spreadsheet's courses to match the toolkit.

D0921 — assigned source supporting this teaching point

Use the Operator's Flow as the spine

The linked doctrine is described as five phases and 22 steps with done-when criteria, failure modes, tool guidance graded Real, Useful With Caveats or Mostly Theater, and widget mappings. It also names burning versus chronic pain and identity commoditization risk. Use it when starting, diagnosing a stall or deciding what follows a completed step. The index does not reproduce all 22 steps or their rules. A full lesson on those details depends on the linked doctrine, whose contents and availability still require verification.

D0921 — assigned source supporting this teaching point

Related source resources: RISER-Operators-Flow.html — resource linked in the source ·

Capture the idea in five sentences

Step 1.1 asks for WHO, PROBLEM, SOLUTION, PRICE TIER and WHY YOU in a disciplined paragraph of approximately 200 words. Explain each sentence plainly: identify the buyer, state the problem, describe the proposed solution, indicate a tentative price tier and state why this operator can deliver. Mark unknowns in brackets rather than fabricating them. This reusable paragraph supplies context for later tools; its clarity is not evidence of customer demand.

D0921 — assigned source supporting this teaching point

Related source resources: RISER-Step-1.1-Idea-Capture.html — resource linked in the source ·

Profile how the buyer decides

Step 1.2 proposes four decision styles: Blueprint, Action, Nurturing and Knowledge. The tool is described as mapping activating and repelling phrases, ranked objections and content across cold, warm and hot stages. Its seller-mismatch warning asks whether the seller's communication style fits the buyer. Use real conversations to form tentative patterns rather than assigning a fixed psychological identity. The index claims lineage from DISC, Cialdini and Schwartz and distinguishes the tool from licensed B.A.N.K. methodology; it does not substantiate broad intellectual-property or diagnostic claims.

D0921 — assigned source supporting this teaching point

Apply the MVO decision engine before commitment

Widget 01 is described as 17 sequential gates that include burning pain, willingness to pay, kill criteria, MVP scope and channel readiness. It returns GO, NO or REWORK with reasoning and is intended for deciding whether to commit, including a new direction within an existing business. The index associates it with Steps 1.1, 1.3 and 1.4. Do not invent the other gates. Record the actual evidence behind a verdict and resist using a tool merely to rationalize a decision already made.

D0921 — assigned source supporting this teaching point

Build the marketing plan from validated context

Widget 02 takes profession, avatar and four sharpening questions through three stages to a ten-section marketing plan. Its research shortcuts are Reddit, Google, LinkedIn, AnswerThePublic, SparkToro and PainOnSocial. It advertises LinkedIn, cold-email and Reddit-reply scripts with copy buttons and a print stylesheet. Use it in asset building and early acquisition, with the idea paragraph and buyer profile as inputs. These are described features, not independently verified live capabilities; producing a script does not send it.

D0921 — assigned source supporting this teaching point

Select pain-discovery tools by the question

Widget 03 is described as 41 tools across seven tiers: the examples include Reddit scraping, social listening, review mining, search intent, surveys and interview transcripts. The advertised comparisons cover price, speed, cost and breadth versus depth. Use it at Step 1.3 when the problem sentence is vague or you need buyer language for a lead magnet, sales page or outreach draft. Preserve verbatim evidence with context. The index's claims of verified tools and real pricing require a current catalog check before a purchase recommendation.

D0921 — assigned source supporting this teaching point

Related source resources: RISER-Tool-Catalog.html — resource linked in the source ·

Choose acquisition tools for an actual gap

Widget 04 describes 39 tools across seven channels: visitor identification, expert directories, LinkedIn, B2B contact data, legal intelligence, outreach plus CRM, and reputation. It also names a six-step buyer journey and Dream 100 template. Its stated fit is high-ticket professional services or coaching with deals of $5,000 or more. Identify the acquisition gap before selecting a tool. The index supplies neither the six steps nor a completed Dream 100 list, and the price positioning is not a promise of results.

D0921 — assigned source supporting this teaching point

Use the explainer script and both editable references

Widget 05 is a Word talking-head script described as eight sections and about 28–35 minutes, with doctrine pull-quotes explaining the MVO engine. It is positioned as an operator-creator explanation rather than a click-by-click demo. The two references are the editable Operator's Flow markdown and Pain Discovery Tools markdown, useful for customization, extracting entries or supplying context to another tool. Keep links to all three assets. Their full contents remain separate dependencies; a listed file name is not proof that the file was reviewed or delivered.

D0921 — assigned source supporting this teaching point

Recognize what is planned rather than shipped

Step 1.3 Pain Discovery is marked Soon and would combine idea and buyer-profile context into quotes, burning/chronic tags and ranked priorities; the temporary route is the catalog. Step 1.4 Offer Hypothesis is also planned, with Hormozi-lineage value thinking, buyer style, kill criteria and pricing tests; the temporary route is section 06 of the marketing plan. Step 1.5 MVP/Service Definition is planned to cover minimum scope, deliverables, pricing and a kill criterion, becoming an SOW for services. These are roadmap descriptions, not functioning lessons or delivered tools.

D0921 — assigned source supporting this teaching point

Related source resources: RISER-Product-Kill-Criteria-Post-Launch-SOP.docx — related SOP ·

Follow the stated operating sequence

The index suggests first reading the doctrine for roughly 30 minutes, then Idea Capture, Buyer Decision Style and the deeper MVO validation. In Phase 2, build a marketing plan and return to pain discovery if the language is vague. In Phase 3, use the acquisition catalog for high-ticket services and marketing-plan section 09 for other models. Phases 4 and 5 rely on the doctrine because standalone operations and iteration widgets are not yet built. Time estimates are planning suggestions, not completion guarantees.

D0921 — assigned source supporting this teaching point

Move context explicitly between artifacts

The index says step pages store outputs in localStorage and gives browser-dependent expectations for local HTML files. Treat those as claims to test on the actual files and browser, not guarantees. Use the described Copy button and prior-context field as the explicit transfer route, then confirm the next tool received the right text. Hosting files on a common origin can support shared browser storage, but only if the implementations use compatible keys and handling. Preserve an independent copy of important output.

D0921 — assigned source supporting this teaching point

Inspect API handling before using a key

The source says two step pages and three widgets use an Anthropic key stored locally, gives approximate per-use costs, and claims requests go only to api.anthropic.com. Those statements require inspection of the actual application and current provider terms; this index cannot prove the network destination or security behavior. The source names Sonnet 4.6 at $0.05–$0.15 and Opus 4.7 at $0.50–$1.50 per use. Preserve them as historical source estimates, not current pricing or verified model availability. No key is required to read this lesson.

D0921 — assigned source supporting this teaching point

Print and share a deliberate output

The index describes print stylesheets that remove navigation for Print → Save as PDF. Review the resulting PDF to confirm that headings, answers and sources remain legible. It also describes deploying an individual HTML file through Netlify Drop and suggests shared hosting for the suite. Those are workflow options in the source, not instructions to publish private input, API keys or a learner's work automatically. Check what a file contains before a deliberate sharing action.

D0921 — assigned source supporting this teaching point

Use the anti-fabrication discipline as the acceptance test

The index prohibits fabricated metrics, fake firms, invented testimonials and guaranteed outcomes. It asks for caveats when niche-specific confidence is missing and treats AI drafts as starting points for market testing. Apply that discipline to the toolkit itself: record which linked assets were opened, which features were observed and which remain advertised or planned. Submit an idea paragraph, a tentative buyer-profile note and a phase-to-artifact map with missing dependencies clearly marked.

D0921 — assigned source supporting this teaching point

Apply the agreed marketing lenses

D0921 — assigned source supporting this teaching point

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Additional resources linked by the assigned document

Source-linked resources; availability and full contents require separate verification.

Complete original source text

RISER · Captain's Logic Operating Doctrine · v1

The Suite Index

Ten artifacts for operators building real businesses — Etsy crafts, digital products, professional services, coaching, brick-and-mortar, affiliate programs. Each tool is a single self-contained HTML file. Open this index, pick the one you need, and double-click to open it. Outputs save to your browser between files in most cases.

How this kit is organized

RISER is built as a doctrine document (the spine), five widgets (the work), and two new step pages (the foundation work — Phase 1). Plus a script and reference markdown.

The doctrine document tells you where you are in the work — what phase, what step. The widgets execute the work for that step. The two step pages walk you through the foundational moves before you touch the bigger widgets.

Don't try to use everything at once. Pick the artifact that maps to where you actually are right now. Walk it. Save the output. Move to the next one when ready.

Don't know where to start? Open the RISER Operator's Flow doctrine document below. It explains the 5 phases / 22 steps and tells you which widget belongs at each step. That's the spine. Everything else hangs from it.

The Spine— start here if you're new to the kit

DOC 01RISER Operator's Flow — Doctrine DocumentDoctrine

Five phases, 22 steps, one continuous feedback loop. Each step has done-when criteria, common failure modes, AI/tool layer guidance graded Real / Useful With Caveats / Mostly Theater, and a map to which RISER widget belongs at that step. Burning-vs-chronic pain prioritization. Identity Commoditization risk named. Reads as an operator's logbook, not a vision document.

USE WHEN: You're new to the kit · You're uncertain which phase you're in · You finish a step and want to know what comes next · You're recovering from a stall and need to diagnose where things broke.

Phase 1 Step Pages— foundation work, walked one step at a time

STEP 1.1Idea CaptureLive · Claude API

Refines your raw business idea into a disciplined 5-sentence paragraph: WHO + PROBLEM + SOLUTION + PRICE TIER + WHY YOU. The constraint forces clarity. Honest gaps get marked with [BRACKETS] instead of fabricated. Universal across business models — Etsy, digital, services, coaching, local, affiliate. ~200 words output. Saves to localStorage.

USE WHEN: You have an idea and need to sharpen it · You're stuck describing what you do · You want to feed the same paragraph into multiple downstream tools.

STEP 1.2Buyer Decision Style ProfileLive · Claude API

Types your buyer into one of four decision styles — Blueprint, Action, Nurturing, Knowledge — and tells you what content moves them across cold/warm/hot stages of the journey. Activating phrases. Repelling phrases. Likely objections ranked. Seller mismatch warning — the highest-leverage piece — names how your natural selling style will mis-fire if it doesn't match this buyer's decision style. Public-domain framework lineage (DISC + Cialdini + Schwartz), not licensed B.A.N.K. methodology.

USE WHEN: You finish Step 1.1 and want to understand HOW your buyer decides · You've had real buyer conversations and want to type the patterns · You're writing copy and don't know what tone fits · You suspect you're losing buyers because of style mismatch.

The Widgets— interactive tools that do the work for specific steps

WIDGET 01MVO Decision Engine — 17 GatesWidget · Claude API

Validates a business idea through 17 sequential gates — burning-pain test, willingness-to-pay test, kill-criterion definition, MVP scope, channel readiness. Verdict: GO / NO / REWORK with specific reasoning. Anti-fabrication discipline throughout. Designed for operators considering whether to commit to an idea, not retroactive rationalization of one already chosen.

USE WHEN: Operator's Flow Step 1.1, 1.3, 1.4 (Idea Capture → Pain Discovery → Offer Hypothesis) · You're considering an idea and want hard validation before committing · You have a working business but want to test a new direction.

WIDGET 02Marketing Plan GeneratorWidget · Claude API

Three-stage interactive plan generator. Profession + avatar + 4 sharpening questions → 10-section custom marketing plan. Includes pre-filled scan buttons (Reddit, Google, LinkedIn, AnswerThePublic, SparkToro, PainOnSocial), three channel-specific outreach scripts (LinkedIn / Cold Email / Reddit reply) with copy buttons. Print stylesheet included.

USE WHEN: Operator's Flow Phase 2 (Asset Build) and early Phase 3 (Acquisition) · You have a validated business and need a coherent plan, not a list of tactics · You want a written deliverable to tape to the wall and execute against.

WIDGET 03Pain Discovery Tool CatalogWidget

41 verified tools across 7 tiers for surfacing buyer pain in their own language. Reddit scrapers, social listening, review mining, search-intent tools, survey platforms, interview transcript tools. Real pricing. Honest tradeoffs (fast/slow, expensive/free, broad/deep). No fabricated metrics.

USE WHEN: Operator's Flow Step 1.3 (Pain Discovery) · Your idea paragraph from Step 1.1 has a vague PROBLEM sentence · You need verbatim pain language to write a lead magnet, sales page, or outreach script.

WIDGET 04Client Acquisition Tool CatalogWidget

39 verified tools across 7 channels for high-ticket professional service acquisition: Visitor ID, Expert Directories, LinkedIn, B2B Contact Data, Legal Intel, Outreach + CRM, Reputation. Six-step buyer journey framework. Dream 100 template. Real pricing.

USE WHEN: Operator's Flow Phase 3 (Acquisition) · You sell professional services or coaching at $5K+ deal size · You're building a Dream 100 list · You need to know which tool fills which gap before you spend.

WIDGET 05MVO Widget Explainer ScriptReference · Word Doc

Talking-head video script (~28-35 min runtime) walking through the MVO Decision Engine. 8 sections. Doctrine pull-quotes. Designed for an operator-creator explaining the tool, not a tutorial-style demo. Word document for editing.

USE WHEN: You're recording video content explaining the MVO widget · You want script structure for a similar walk-through video on a different RISER artifact · You're building lead magnets that include video.

Reference Files— source material, editable copies

REF 01Operator's Flow — Markdown SourceMarkdown

The doctrine document in markdown form. Editable. Use this if you want to modify the flow for your own context, embed it in Notion or Obsidian, or feed it to another LLM as context for downstream work.

USE WHEN: You want to fork the doctrine for your own use · You're feeding RISER context into another tool · You prefer reading in markdown.

REF 02Pain Discovery Tools — Markdown SourceMarkdown

The Pain Discovery Tool Catalog source content in markdown. Useful for customization or pulling individual tool entries into other documents.

USE WHEN: You want to extract specific tool reviews · You're adding new tools and want to maintain the same format.

Phase 1 Steps Still To Build— planned step pages, not yet shipped

STEP 1.3Pain DiscoverySoon

Walks operator through pain discovery using prior context (Step 1.1 idea + Step 1.2 buyer profile). Produces a structured pain document with verbatim quotes, burning-vs-chronic tagging, and ranked priority. In the meantime, use the Pain Discovery Tool Catalog widget above.

STEP 1.4Offer HypothesisSoon

Drafts an offer hypothesis using Hormozi-lineage value-equation thinking calibrated to the buyer's decision style. Defines kill criterion. Pressure-tests pricing. In the meantime, use Section 06 of the Marketing Plan Generator output.

STEP 1.5MVP / Service DefinitionSoon

Defines the smallest version of the offer you can ship and learn from. Scope, deliverable structure, pricing, kill criterion. For services this becomes your SOW template.

How to use this kit— operating notes

The honest sequence

1. Read the Operator's Flow doctrine first. 30 minutes of reading. It tells you which artifact belongs at which step.

2. Walk Phase 1 in order: Step 1.1 Idea Capture → Step 1.2 Buyer Decision Style → MVO Widget for full validation. The first two are fast. The MVO Widget is deep.

3. For Phase 2 (Asset Build): Run the Marketing Plan Generator with your sharpened idea + buyer profile. Use the Pain Discovery Tool Catalog if pain language is still vague.

4. For Phase 3 (Acquisition): Use the Client Acquisition Catalog if you sell high-ticket services or coaching. The Marketing Plan Generator's Section 09 covers acquisition for other business models.

5. For Phase 4 + 5 (Operations + Iteration): The doctrine document is the spine. Standalone widgets for these phases are not yet built.

State sharing between files

The two step pages (1.1 and 1.2) save your output to localStorage. Whether outputs carry between separate HTML files depends on your browser:

* Chrome (default settings): Files in the same folder usually share localStorage. Step 1.2 will pick up Step 1.1's paragraph automatically.

* Firefox / Safari: Generally do NOT share between local files. Each file has isolated localStorage.

* Workaround that always works: Each step page has a "Copy" button on its output. Copy the text, then paste into the next step's prior-context field. The widgets are designed to handle either path.

If you want guaranteed state sharing, host all the files on a single Netlify project so they share the same origin. But for personal operator practice, the copy-paste workflow is reliable and explicit.

API key handling

The two step pages and three widgets that use Claude all need an Anthropic API key. Get one here. Each tool stores it locally in your browser. Approximate cost per use: $0.05–$0.15 on Sonnet 4.6, $0.50–$1.50 on Opus 4.7.

Your key is never sent anywhere except api.anthropic.com. Anthropic's Trust Center lays out their data handling.

Printing & sharing

Every artifact has a print stylesheet that strips navigation and renders cleanly to PDF. Use your browser's "Print → Save as PDF" to capture an output.

To share an individual artifact with someone, you can drag any single .html file onto Netlify Drop for a free public URL. Single files don't have folder-vs-contents problems. Each one becomes its own deploy.

Discipline notes for using this kit. No artifact in this suite produces fabricated metrics, fake firm names, invented testimonials, or outcome guarantees. Every Claude-generated output uses the same anti-fabrication rules. If a tool can't speak with confidence about your specific niche, it says so in caveats. The honest gap is part of the deliverable, not a defect to hide. Treat AI-generated drafts as starting points for testing in your real market — not as plans to execute without human judgment.

RISER_Nation_Black_Friday_Competitive_Analysis_FormatB.docx

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

Working teaching draft; supporting assets and source claims requiring verification are identified below.

Separate competitive observations from hypotheses

This Black Friday analysis uses five headings for each offer: summary, marketing angles, psychological drivers, hidden tactics and ways to outperform it. Treat the named offers and stated numbers as the source author's account of a particular promotion, not current verified prices, inventory or results. The psychological explanations and hidden tactics are interpretations. Build an evidence column alongside them before using the analysis to guide your own offer.

D0922 — assigned source supporting this teaching point

Analyze the first two quick-win courses

Launch Your First Digital Product is described as an idea-to-income beginner roadmap using the PAID framework and NINA Niching Assistant. The distinct benefit is help moving from uncertainty to a first product; the source does not explain PAID or supply NINA. Instagram Growth Academy is described as a hook and reel formula with content psychology and a claim of 100,000 followers in nine months. Keep that number attributed to the analyzed promotion rather than turning it into an expected learner outcome.

D0922 — assigned source supporting this teaching point

Analyze automation and strategic planning offers

DM Sales on Autopilot is described as a ManyChat system connecting Instagram engagement to sales with prepared DM flows and copy. Your Instagram Profit Plan is described as 2026 positioning, bio optimization, algorithm conditioning and a 90-day profit map. Distinguish a concrete flow or plan from the implied performance result. The source provides no automation file or algorithm evidence, so the teaching exercise is to identify required inputs, deliverables and proof.

D0922 — assigned source supporting this teaching point

Analyze carousel and bot offers

Carousels That Convert is described as design and copy instruction supported by a claim that a $7 carousel produced $7,000 in revenue. That is a reported case claim, not a forecast. Build Your Own Bot is described as creating AI bots that reflect the operator's voice and work, automate repeated tasks and become productized assets. For each, identify the learner's intended output and the evidence needed to show that it works; the source supplies neither the carousel case data nor a working bot.

D0922 — assigned source supporting this teaching point

Understand the shared quick-win marketing pattern

All six quick-win entries repeat beginner-friendly shortcuts, rapid micro-wins, clarity and templates, numerical social proof, and a $17 offer with 200 spots. They connect those angles to faster perceived progress, a more capable self-image, reduced niche-choice fear and relief from overwhelm. Analyze these as a repeated positioning pattern. The repeated wording does not independently establish that every product had identical terms or that fast profit occurred.

D0922 — assigned source supporting this teaching point

Examine choice reduction, status and urgency

The analysis interprets a single low price as reducing decision fatigue, smart-buyer language as status reinforcement and sell-out counters as urgency devices. For a learner's own offer, simplify the decision with clear scope and price. A capacity claim or counter needs a real basis and accurate behavior. Do not copy pressure language merely because the competitor analysis attributes persuasive power to it.

D0922 — assigned source supporting this teaching point

Turn the quick-win alternatives into a test

The proposed alternatives for all six quick wins are AI personalization, industry-specific templates, ROI or forecast tools, automation blueprints and cross-platform strategy spanning Instagram, TikTok, YouTube and email. Choose one that solves a documented buyer problem and specify its actual deliverable. Calculators need visible assumptions and forecasts remain estimates. Added features do not establish superiority without evidence that the buyer values and can use them.

D0922 — assigned source supporting this teaching point

Compare all three signature programs

Digital Product Launch Formula is described as a launch roadmap claiming $1,000–$10,000 outcomes for beginners. META Ads Mastery is described as a 2025-era ads system with templates, funnels and targeting shortcuts. Six Figure Sales Webinar is described as access to slides, scripts and a pitch formula associated with seven-figure revenue. Preserve each distinct mechanism and label the monetary and algorithm claims as source claims. None establishes current platform guidance or typical results.

D0922 — assigned source supporting this teaching point

Read the signature-program persuasion pattern

Across the three signature programs, the analysis repeats proven-framework positioning, a seven-figure-business authority claim, story-led persuasion, and templates intended to reduce effort and risk. Its proposed drivers are certainty, less guesswork and emotional safety. It interprets authority, 50 limited spots and a $97 ticket as persuasion tactics. A useful offer makes scope and support concrete; authority language and templates cannot remove all delivery risk.

D0922 — assigned source supporting this teaching point

Design a differentiated signature-program deliverable

The suggested alternatives are niche-specific launch maps, automated pre-launch and post-purchase sequences, AI funnel optimization tools and weekly KPI dashboards. Start with the buyer's implementation gap and assign an owner, input, output and review criterion to the proposed support. Use actual measurements in dashboards and test an optimization hypothesis before calling it an improvement. These are competitive ideas in the document, not supplied working assets.

D0922 — assigned source supporting this teaching point

Unpack the full-access offer

The Full Access Pass is described as lifetime access to current and future 2026 courses, SASCA and AI assistants, plus a one-to-one strategy session. Its stated comparison is $6,791 or more of products for $1,999 with five spots. The analysis interprets this as ecosystem ownership, value compression, finite personal access and a long-term choice. Examine exactly what lifetime and future access mean in the original terms; the analysis itself does not supply those terms or verify the valuation.

D0922 — assigned source supporting this teaching point

Evaluate access, anchoring and loss aversion

The full-access analysis proposes fear of missing future opportunities, insider access, belonging and lifetime security as drivers. It identifies price anchoring, mentorship-based social proof and regret avoidance as tactics. Those are explanatory hypotheses, not observations of every buyer. In your own offer, support value comparisons and make access limits clear instead of implying that purchasing eliminates all future needs or guarantees status.

D0922 — assigned source supporting this teaching point

Make the premium alternative operational

The proposed response is implementation support with accountability, done-for-you automation, business-specific AI assistants and a Success Guarantee Framework such as a 90-day implementation ramp. Define what is actually delivered and how progress is reviewed. A 90-day ramp is a proposed service structure, not a guarantee of income. Submit a comparison of all ten offers with source claims, inferred mechanisms, supporting evidence needed and one testable alternative for each.

D0922 — assigned source supporting this teaching point

Apply the agreed marketing lenses

D0922 — assigned source supporting this teaching point

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Complete original source text

RISER Nation Competitive Breakdown – Black Friday Offer Suite (Format B)
Overview of This Breakdown
This document provides a RISER Nation–level competitive analysis of the Black Friday offer suite from Lauren Dallas Creator Hub. Each offer is dissected using RISER principles: market psychology, emotional triggers, pricing logic, scarcity dynamics, and competitive angles. Each section includes: (1) Offer Summary, (2) Marketing Angles, (3) Psychological Drivers, (4) Hidden Tactics, and (5) How You Can Outperform It.
QUICK WIN COURSES — Competitive Analysis
https://www.laurendallascreatorhub.com/blackfridayvault?ck_subscriber_id=3491465416
Launch Your First Digital Product
**Offer Summary:** A beginner-friendly, confidence-building roadmap from idea → income. Leverages the PAID framework and adds the ‘NINA Niching Assistant’ as an irresistible clarity shortcut.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
Instagram Growth Academy
**Offer Summary:** A hook-based viral growth blueprint promising 100K followers in 9 months using a proven reel formula and content psychology.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
DM Sales on Autopilot
**Offer Summary:** A ManyChat-powered automation system turning Instagram engagement into sales with predefined DM flows and swipe copy.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
Your Instagram Profit Plan
**Offer Summary:** A 2026 strategic planning system for IG positioning, bio optimization, algorithm conditioning, and 90‑day profit mapping.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
Carousels That Convert
**Offer Summary:** A design-and-copy system teaching scroll-stopping carousel mechanics that led to a $7 carousel producing $7,000 in revenue.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
Build Your Own Bot
**Offer Summary:** A system teaching students how to build AI bots that sound, think, and operate like them to automate repetitive tasks and create productized automation assets.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
SIGNATURE PROGRAMS — Competitive Analysis
Digital Product Launch Formula
**Offer Summary:** A proven roadmap for launching and selling digital products, capable of creating $1K–$10K outcomes even for beginners.
**Marketing Angles:**
• Expert-level, proven frameworks
• Claim-based authority (‘exact system that built a 7-figure business’)
• Strong story-based persuasion
• High-value templates that reduce effort and risk
**Psychological Drivers:**
• People want certainty and ‘plug-and-play’ instructions
• Risk mitigation by removing guesswork
• Emotional safety by offering proven scripts and slides
**Hidden Tactics:**
• Authority bias (‘learn from someone who already won’)
• Scarcity through limited 50 spots
• High perceived value vs. low ticket cost ($97)
**How You Can Outperform This:**
• Provide niche-specific launch maps (fitness, real estate, coaching, etc.)
• Add automation flows for pre-launch & post-purchase sequences
• Add AI-driven funnel optimization tools
• Provide weekly KPI dashboards and tracking templates
META Ads Mastery
**Offer Summary:** A Meta ads system updated for 2025 algorithms, featuring templates, funnels, and targeting shortcuts.
**Marketing Angles:**
• Expert-level, proven frameworks
• Claim-based authority (‘exact system that built a 7-figure business’)
• Strong story-based persuasion
• High-value templates that reduce effort and risk
**Psychological Drivers:**
• People want certainty and ‘plug-and-play’ instructions
• Risk mitigation by removing guesswork
• Emotional safety by offering proven scripts and slides
**Hidden Tactics:**
• Authority bias (‘learn from someone who already won’)
• Scarcity through limited 50 spots
• High perceived value vs. low ticket cost ($97)
**How You Can Outperform This:**
• Provide niche-specific launch maps (fitness, real estate, coaching, etc.)
• Add automation flows for pre-launch & post-purchase sequences
• Add AI-driven funnel optimization tools
• Provide weekly KPI dashboards and tracking templates
Six Figure Sales Webinar
**Offer Summary:** A webinar-based selling system including the creator’s own slides, scripts, and pitch formula that produced seven-figure revenue.
**Marketing Angles:**
• Expert-level, proven frameworks
• Claim-based authority (‘exact system that built a 7-figure business’)
• Strong story-based persuasion
• High-value templates that reduce effort and risk
**Psychological Drivers:**
• People want certainty and ‘plug-and-play’ instructions
• Risk mitigation by removing guesswork
• Emotional safety by offering proven scripts and slides
**Hidden Tactics:**
• Authority bias (‘learn from someone who already won’)
• Scarcity through limited 50 spots
• High perceived value vs. low ticket cost ($97)
**How You Can Outperform This:**
• Provide niche-specific launch maps (fitness, real estate, coaching, etc.)
• Add automation flows for pre-launch & post-purchase sequences
• Add AI-driven funnel optimization tools
• Provide weekly KPI dashboards and tracking templates
THE BIG ONE — Full Access Pass Competitive Analysis
**Offer Summary:** Lifetime access to all current and 2026 future courses, including SASCA and AI assistants, plus a rare 1:1 strategy session with Lauren. Combines all products into one premium ecosystem purchase.
**Marketing Angles:**
• Full-ecosystem ownership (‘get everything, forever’)
• Extreme value compression ($6,791+ of products for $1,999)
• High-status scarcity: only 5 spots, with personal access to Lauren
• Positioning as the smartest long-term choice
**Psychological Drivers:**
• Avoidance of missing future opportunities
• Desire for insider access + private strategy
• Perception of being part of an elite inner circle
• Lifetime security (no future purchases needed)
**Hidden Tactics:**
• Scarcity framing: personal access is finite → spikes conversions
• Anchoring effect using the $6,791 value
• Social proof: mentorship positioned as priceless
• Loss aversion → buyers fear regret
**How You Can Outperform This:**
• Offer not just access, but IMPLEMENTATION support with accountability
• Provide automation setups done-for-them (your unique advantage)
• Add personalized AI assistants trained on the buyer’s business
• Create a Success Guarantee Framework (e.g., 90-day implementation ramp)

Original Word content in native document order, including recovered fields

word/document.xml
RISER Nation Competitive Breakdown – Black Friday Offer Suite (Format B)
Overview of This Breakdown
This document provides a RISER Nation–level competitive analysis of the Black Friday offer suite from Lauren Dallas Creator Hub. Each offer is dissected using RISER principles: market psychology, emotional triggers, pricing logic, scarcity dynamics, and competitive angles. Each section includes: (1) Offer Summary, (2) Marketing Angles, (3) Psychological Drivers, (4) Hidden Tactics, and (5) How You Can Outperform It.
QUICK WIN COURSES — Competitive Analysis
https://www.laurendallascreatorhub.com/blackfridayvault?ck_subscriber_id=3491465416
Launch Your First Digital Product
**Offer Summary:** A beginner-friendly, confidence-building roadmap from idea → income. Leverages the PAID framework and adds the ‘NINA Niching Assistant’ as an irresistible clarity shortcut.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
Instagram Growth Academy
**Offer Summary:** A hook-based viral growth blueprint promising 100K followers in 9 months using a proven reel formula and content psychology.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
DM Sales on Autopilot
**Offer Summary:** A ManyChat-powered automation system turning Instagram engagement into sales with predefined DM flows and swipe copy.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
Your Instagram Profit Plan
**Offer Summary:** A 2026 strategic planning system for IG positioning, bio optimization, algorithm conditioning, and 90‑day profit mapping.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
Carousels That Convert
**Offer Summary:** A design-and-copy system teaching scroll-stopping carousel mechanics that led to a $7 carousel producing $7,000 in revenue.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
Build Your Own Bot
**Offer Summary:** A system teaching students how to build AI bots that sound, think, and operate like them to automate repetitive tasks and create productized automation assets.
**Marketing Angles:**
• Beginner-proof shortcuts
• ‘Do this today, profit tomorrow’ micro-wins
• Psychological relief through clarity and templates
• Social proof through numbers (followers, revenue, bots built)
• Scarcity trigger: 200 spots only + $17 pricing
**Psychological Drivers:**
• Speed-to-outcome (fast progress)
• Identity shift (‘I can do this’)
• Elimination of fear of choosing the wrong niche
• Relief from overwhelm using frameworks and AI shortcuts
**Hidden Tactics:**
• Removal of decision fatigue by offering only one ultra-low price
• Social status reinforcement (‘smart buyers act fast’)
• Hard sell-out counters to increase urgency perception
**How You Can Outperform This:**
• Add real-time AI personalization (your version: fully custom workflows)
• Add industry‑specific templates instead of universal ones
• Provide ROI calculators, forecast tools, and automation blueprints
• Bundle cross-platform strategy (IG + TikTok + YouTube + Email)
SIGNATURE PROGRAMS — Competitive Analysis
Digital Product Launch Formula
**Offer Summary:** A proven roadmap for launching and selling digital products, capable of creating $1K–$10K outcomes even for beginners.
**Marketing Angles:**
• Expert-level, proven frameworks
• Claim-based authority (‘exact system that built a 7-figure business’)
• Strong story-based persuasion
• High-value templates that reduce effort and risk
**Psychological Drivers:**
• People want certainty and ‘plug-and-play’ instructions
• Risk mitigation by removing guesswork
• Emotional safety by offering proven scripts and slides
**Hidden Tactics:**
• Authority bias (‘learn from someone who already won’)
• Scarcity through limited 50 spots
• High perceived value vs. low ticket cost ($97)
**How You Can Outperform This:**
• Provide niche-specific launch maps (fitness, real estate, coaching, etc.)
• Add automation flows for pre-launch & post-purchase sequences
• Add AI-driven funnel optimization tools
• Provide weekly KPI dashboards and tracking templates
META Ads Mastery
**Offer Summary:** A Meta ads system updated for 2025 algorithms, featuring templates, funnels, and targeting shortcuts.
**Marketing Angles:**
• Expert-level, proven frameworks
• Claim-based authority (‘exact system that built a 7-figure business’)
• Strong story-based persuasion
• High-value templates that reduce effort and risk
**Psychological Drivers:**
• People want certainty and ‘plug-and-play’ instructions
• Risk mitigation by removing guesswork
• Emotional safety by offering proven scripts and slides
**Hidden Tactics:**
• Authority bias (‘learn from someone who already won’)
• Scarcity through limited 50 spots
• High perceived value vs. low ticket cost ($97)
**How You Can Outperform This:**
• Provide niche-specific launch maps (fitness, real estate, coaching, etc.)
• Add automation flows for pre-launch & post-purchase sequences
• Add AI-driven funnel optimization tools
• Provide weekly KPI dashboards and tracking templates
Six Figure Sales Webinar
**Offer Summary:** A webinar-based selling system including the creator’s own slides, scripts, and pitch formula that produced seven-figure revenue.
**Marketing Angles:**
• Expert-level, proven frameworks
• Claim-based authority (‘exact system that built a 7-figure business’)
• Strong story-based persuasion
• High-value templates that reduce effort and risk
**Psychological Drivers:**
• People want certainty and ‘plug-and-play’ instructions
• Risk mitigation by removing guesswork
• Emotional safety by offering proven scripts and slides
**Hidden Tactics:**
• Authority bias (‘learn from someone who already won’)
• Scarcity through limited 50 spots
• High perceived value vs. low ticket cost ($97)
**How You Can Outperform This:**
• Provide niche-specific launch maps (fitness, real estate, coaching, etc.)
• Add automation flows for pre-launch & post-purchase sequences
• Add AI-driven funnel optimization tools
• Provide weekly KPI dashboards and tracking templates
THE BIG ONE — Full Access Pass Competitive Analysis
**Offer Summary:** Lifetime access to all current and 2026 future courses, including SASCA and AI assistants, plus a rare 1:1 strategy session with Lauren. Combines all products into one premium ecosystem purchase.
**Marketing Angles:**
• Full-ecosystem ownership (‘get everything, forever’)
• Extreme value compression ($6,791+ of products for $1,999)
• High-status scarcity: only 5 spots, with personal access to Lauren
• Positioning as the smartest long-term choice
**Psychological Drivers:**
• Avoidance of missing future opportunities
• Desire for insider access + private strategy
• Perception of being part of an elite inner circle
• Lifetime security (no future purchases needed)
**Hidden Tactics:**
• Scarcity framing: personal access is finite → spikes conversions
• Anchoring effect using the $6,791 value
• Social proof: mentorship positioned as priceless
• Loss aversion → buyers fear regret
**How You Can Outperform This:**
• Offer not just access, but IMPLEMENTATION support with accountability
• Provide automation setups done-for-them (your unique advantage)
• Add personalized AI assistants trained on the buyer’s business
• Create a Success Guarantee Framework (e.g., 90-day implementation ramp)

RISER_Nation_Offer_Marketing_Engine_v3_(Step_8).docx

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

Working teaching draft; supporting assets and source claims requiring verification are identified below.

Place Step 8 in the operating sequence

The Offer Marketing Engine v3 is described as connecting Step 7 optimization to Step 9 systemization and outsourcing. Its goal is sustained paid, organic and partnership distribution beyond an initial market. The document also describes Step 9 as scaled distribution and expansion in one passage. Preserve that wording discrepancy without renumbering the curriculum. Use the operating flow as a planning model: refine the offer, test distribution, then document the work that can be delegated.

D0923 — assigned source supporting this teaching point

Create the ad-iteration sandbox

Module 1 proposes AI-generated copy, hooks, visuals and targeting tested for creative fatigue, audience overlap and performance decay. Its sequence is A/B, then A/B/C, then a champion loop. Keep the reference creative, hypothesis, exposure and outcome definitions visible so a new champion is supported by evidence. The named outputs are Ad Sandbox Template, Creative Testing Log.csv and Champion Adset Matrix.xlsx; the files and statistical decision rules are not included in this source.

D0923 — assigned source supporting this teaching point

Specify scaling decisions before automation

Module 2 moves from initial activity to horizontal expansion, vertical budget increases and geographic expansion. It calls for ROAS thresholds, CPR floors and automation rules, with Scaling Decision Tree Flowchart.png and Scaling Automation Scenario.json as outputs. CPR is not defined and the floor direction needs clarification if it refers to a cost measure. Write down the metric, unit, direction and acceptable economics before encoding a rule; the document supplies no executable scenario.

D0923 — assigned source supporting this teaching point

Investigate saturation before expanding the market

Module 3 proposes refreshing the offer angle, bundle or seasonal positioning, then parallel markets and adjacent audiences when the initial addressable market is exhausted. A decline in campaign performance alone does not prove a TAM ceiling. Compare evidence for creative fatigue, audience overlap and changing demand before choosing an expansion hypothesis. The named planning outputs are Audience Expansion Map.xlsx and Offer Angle Refresh.docx, not provided working files.

D0923 — assigned source supporting this teaching point

Plan continuity and partnerships

Module 4 covers memberships, subscription boxes and retainers with ads for 30-, 60- and 90-day retention cycles. Its outputs are Continuity Funnel Blueprint.docx and Ad Retargeting Sequences.csv. Module 5 proposes Tier 1–3 affiliates, JV pipelines and creator or influencer co-branded campaigns, using Affiliate System Flow.xlsx and JV Recruitment Playbook.docx. The source provides no tier rules or ready-to-run sequences. Define the customer benefit and operating responsibilities before treating recurring billing or partnerships as a stable revenue source.

D0923 — assigned source supporting this teaching point

Preserve the deliverable inventory

The separate file table names Offer_Marketing_Engine_SuperPrompt.docx as the master document, Ad_Sandbox_System.docx as the paid-testing SOP, Scaling_Framework.xlsx as the budget/audience tracker, Partnership_Network_Map.png as the ecosystem visual and Continuity_Offer_Flowchart.pdf as the recurring-offer system. Keep all five distinct from the module-level outputs. Their names form a dependency checklist; they do not establish that the assets were supplied or reviewed.

D0923 — assigned source supporting this teaching point

Choose tool categories before vendors

The source's 2025+ list groups AdCreative.ai, Pencil and Motion App for creative; Hyros, Triple Whale and GA4 for analytics; Meta Ads, Google Ads, TikTok Ads and LinkedIn Campaign Manager for ad management; and Make.com, Zapier, GHL and CrewAI for automation. It also names Upfluence, AffPilot, Shoutcart and Tapfiliate for influencer/affiliate work; Insidr.ai, BuzzSumo, ExplodingTopics, TrendTok and VidIQ for trends; and Munch, Pika Labs and Runway ML for repurposing. Preserve the inventory as source examples. Verify current fit, capabilities and costs before making a selection rather than treating this dated list as a current recommendation.

D0923 — assigned source supporting this teaching point

Interpret the acquisition benchmarks as assumptions

The stated CTR levels are 3% baseline, 5% target and 7% viral threshold. ROAS levels are 3× MVP, 5× growth and 8× scale. CPL caps are $3 MVP, $5 growth and $8 expansion. Landing-to-purchase CVR targets are 4% and 6% for scale. These are source benchmarks without supporting data, cohort definitions or attribution windows. A CTR does not by itself prove virality. Use actual unit economics and consistently defined denominators before adopting any target.

D0923 — assigned source supporting this teaching point

Separate retention from churn definitions

The source lists membership retention of at least 80% and monthly churn of no more than 4%. The retention period is unspecified, so these are not directly comparable or automatically complementary. Define the cohort and period for retention, and whether churn measures customers or revenue. Record the observation window in the dashboard rather than combining unlike measures into a single success claim.

D0923 — assigned source supporting this teaching point

Assign all six operating roles

The Marketing Architect owns strategy and scaling cadence; the Ad Creative Director owns copy, visual tests and fatigue rotation; the Automation Engineer implements budget rules, GHL pipelines and triggers; the Affiliate Manager handles JV and influencer relationships; the Data Analyst monitors ROAS, CTR and saturation; and the Creative Producer creates and edits assets, including motion. A small team may combine roles, but each decision still needs an accountable owner. These are responsibilities, not proof that autonomous agents already perform them.

D0923 — assigned source supporting this teaching point

Close the feedback loop with a reviewable plan

The definition describes campaigns as both revenue sources and data sources feeding the product-optimization loop. Submit one campaign plan showing the current offer, test question, selected channel, creative record, economics, owner and review trigger. List missing templates and executable assets separately. The purpose is a controlled learning system; the phrase omnipresent market force is positioning language, not a measured outcome.

D0923 — assigned source supporting this teaching point

Apply the agreed marketing lenses

D0923 — assigned source supporting this teaching point

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Complete original source text

RISER Nation Offer Marketing Engine v3 (Step 8)
Purpose
Design, deploy, and scale omnichannel marketing campaigns across paid and organic systems — integrating JV partnerships, affiliate scaling, influencer loops, and iterative ad testing — to achieve maximum audience penetration and sustain momentum beyond initial TAM (Total Addressable Market).
Key Modules
1. Ad Iteration Sandbox (Controlled Testing Lab)
Use AI-generated ad copy, hooks, visuals, and targeting in a sandbox environment. Test creative fatigue, audience overlap, and performance decay. Create A/B → A/B/C → Champion Looping System for scaling winning variants.
Outputs: Ad Sandbox Template, Creative Testing Log.csv, Champion Adset Matrix.xlsx.
2. Scaling Framework (Budget Flow Logic)
Define scaling cadence: start → horizontal → vertical → geographic expansion. Set ROAS thresholds, CPR floors, and automation scaling rules.
Outputs: Scaling Decision Tree Flowchart.png, Scaling Automation Scenario.json.
3. Saturation Escape System
When TAM ceiling is reached, reposition the offer (angle, bundle, seasonal). Launch parallel markets and adjacent audiences for continued growth.
Outputs: Audience Expansion Map.xlsx, Offer Angle Refresh.docx.
4. Continuity Monetization Channels
Introduce memberships, subscription boxes, and retainers. Design continuity ads for 30–60–90 day retention cycles.
Outputs: Continuity Funnel Blueprint.docx, Ad Retargeting Sequences.csv.
5. Partnership & Affiliate Expansion Layer
Develop Tier 1–3 affiliate structures and JV pipelines. Recruit creators and influencers for co-branded campaigns.
Outputs: Affiliate System Flow.xlsx, JV Recruitment Playbook.docx.
Deliverables
System Overview
This step connects optimized offers (Step 7) with scaled distribution and expansion (Step 9). It defines the full marketing machine that powers RISER Nation offers beyond validation — establishing consistent pipelines for paid, organic, and partnership-based growth.
Operational Flow
Step 7 (Optimization & Iteration) → Step 8 (Marketing Engine & Scaling) → Step 9 (Systemization & Outsourcing)

Each sub-module automates and scales a specific revenue lever:
• Ad Iteration Sandbox → Creative testing & ad fatigue management
• Scaling Framework → Budget, ROAS, and automation scaling logic
• Saturation Escape System → Market repositioning and TAM extension
• Continuity Channels → Recurring revenue stabilization
• Partnership Layer → JV, affiliate, and influencer expansion
Recommended Tools & Platforms (2025+)
• Ad Creative AI – AdCreative.ai, Pencil, Motion App
• Analytics – Hyros, Triple Whale, GA4
• Ad Management – Meta Ads, Google Ads, TikTok Ads, LinkedIn Campaign Manager
• Automation – Make.com, Zapier, GHL, CrewAI
• Influencer & Affiliate – Upfluence, AffPilot, Shoutcart, Tapfiliate
• Trend Discovery – Insidr.ai, BuzzSumo, ExplodingTopics, TrendTok, VidIQ
• Repurposing & Content – Munch, Pika Labs, Runway ML
KPI Benchmarks & Performance Metrics
CTR: ≥3% baseline | ≥5% target | ≥7% viral threshold
ROAS: ≥3× MVP | ≥5× Growth | ≥8× Scale
CPL: ≤$3 MVP | ≤$5 Growth | ≤$8 Expansion
CVR: ≥4% landing→purchase | ≥6% scale benchmark
Retention (membership): ≥80% | Churn ≤4% monthly
Internal Agent Roles & Responsibilities
RISER Nation Definition
The Marketing Engine (Step 8.0) transforms refined products into omnipresent market forces. It combines creative experimentation, data analytics, and partnership ecosystems to drive awareness, acquisition, and expansion. Each campaign serves as both a revenue source and a data generator, feeding back into the Product Optimization Loop for perpetual growth.
File
Description
Offer_Marketing_Engine_SuperPrompt.docx
The master 8.0 system document.
Ad_Sandbox_System.docx
Paid ad testing and creative iteration SOP.
Scaling_Framework.xlsx
Budget and audience scaling tracker.
Partnership_Network_Map.png
Affiliate and JV ecosystem visualization.
Continuity_Offer_Flowchart.pdf
Subscription and recurring offer systems.
Agent Role
Primary Responsibilities
Marketing Architect
Designs overall campaign strategy and scaling cadence.
Ad Creative Director
Oversees copy, visual testing, and fatigue rotation.
Automation Engineer
Implements budget automation, GHL pipelines, and ad triggers.
Affiliate Manager
Recruits and manages JV and influencer partnerships.
Data Analyst
Monitors ROAS, CTR, and audience saturation thresholds.
Creative Producer
Manages ad asset creation, editing, and motion optimization.

Original Word content in native document order, including recovered fields

word/document.xml
RISER Nation Offer Marketing Engine v3 (Step 8)
Purpose
Design, deploy, and scale omnichannel marketing campaigns across paid and organic systems — integrating JV partnerships, affiliate scaling, influencer loops, and iterative ad testing — to achieve maximum audience penetration and sustain momentum beyond initial TAM (Total Addressable Market).
Key Modules
1. Ad Iteration Sandbox (Controlled Testing Lab)
Use AI-generated ad copy, hooks, visuals, and targeting in a sandbox environment. Test creative fatigue, audience overlap, and performance decay. Create A/B → A/B/C → Champion Looping System for scaling winning variants.
Outputs: Ad Sandbox Template, Creative Testing Log.csv, Champion Adset Matrix.xlsx.
2. Scaling Framework (Budget Flow Logic)
Define scaling cadence: start → horizontal → vertical → geographic expansion. Set ROAS thresholds, CPR floors, and automation scaling rules.
Outputs: Scaling Decision Tree Flowchart.png, Scaling Automation Scenario.json.
3. Saturation Escape System
When TAM ceiling is reached, reposition the offer (angle, bundle, seasonal). Launch parallel markets and adjacent audiences for continued growth.
Outputs: Audience Expansion Map.xlsx, Offer Angle Refresh.docx.
4. Continuity Monetization Channels
Introduce memberships, subscription boxes, and retainers. Design continuity ads for 30–60–90 day retention cycles.
Outputs: Continuity Funnel Blueprint.docx, Ad Retargeting Sequences.csv.
5. Partnership & Affiliate Expansion Layer
Develop Tier 1–3 affiliate structures and JV pipelines. Recruit creators and influencers for co-branded campaigns.
Outputs: Affiliate System Flow.xlsx, JV Recruitment Playbook.docx.
Deliverables
File
Description
Offer_Marketing_Engine_SuperPrompt.docx
The master 8.0 system document.
Ad_Sandbox_System.docx
Paid ad testing and creative iteration SOP.
Scaling_Framework.xlsx
Budget and audience scaling tracker.
Partnership_Network_Map.png
Affiliate and JV ecosystem visualization.
Continuity_Offer_Flowchart.pdf
Subscription and recurring offer systems.
System Overview
This step connects optimized offers (Step 7) with scaled distribution and expansion (Step 9). It defines the full marketing machine that powers RISER Nation offers beyond validation — establishing consistent pipelines for paid, organic, and partnership-based growth.
Operational Flow
Step 7 (Optimization & Iteration) → Step 8 (Marketing Engine & Scaling) → Step 9 (Systemization & Outsourcing)
Each sub-module automates and scales a specific revenue lever:
• Ad Iteration Sandbox → Creative testing & ad fatigue management
• Scaling Framework → Budget, ROAS, and automation scaling logic
• Saturation Escape System → Market repositioning and TAM extension
• Continuity Channels → Recurring revenue stabilization
• Partnership Layer → JV, affiliate, and influencer expansion
Recommended Tools & Platforms (2025+)
• Ad Creative AI – AdCreative.ai, Pencil, Motion App
• Analytics – Hyros, Triple Whale, GA4
• Ad Management – Meta Ads, Google Ads, TikTok Ads, LinkedIn Campaign Manager
• Automation – Make.com, Zapier, GHL, CrewAI
• Influencer & Affiliate – Upfluence, AffPilot, Shoutcart, Tapfiliate
• Trend Discovery – Insidr.ai, BuzzSumo, ExplodingTopics, TrendTok, VidIQ
• Repurposing & Content – Munch, Pika Labs, Runway ML
KPI Benchmarks & Performance Metrics
CTR: ≥3% baseline | ≥5% target | ≥7% viral threshold
ROAS: ≥3× MVP | ≥5× Growth | ≥8× Scale
CPL: ≤$3 MVP | ≤$5 Growth | ≤$8 Expansion
CVR: ≥4% landing→purchase | ≥6% scale benchmark
Retention (membership): ≥80% | Churn ≤4% monthly
Internal Agent Roles & Responsibilities
Agent Role
Primary Responsibilities
Marketing Architect
Designs overall campaign strategy and scaling cadence.
Ad Creative Director
Oversees copy, visual testing, and fatigue rotation.
Automation Engineer
Implements budget automation, GHL pipelines, and ad triggers.
Affiliate Manager
Recruits and manages JV and influencer partnerships.
Data Analyst
Monitors ROAS, CTR, and audience saturation thresholds.
Creative Producer
Manages ad asset creation, editing, and motion optimization.
RISER Nation Definition
The Marketing Engine (Step 8.0) transforms refined products into omnipresent market forces. It combines creative experimentation, data analytics, and partnership ecosystems to drive awareness, acquisition, and expansion. Each campaign serves as both a revenue source and a data generator, feeding back into the Product Optimization Loop for perpetual growth.

RISER_Nation_SALES LETTER COPY_RISER Nation Offer Generator — SuperPrompt v2025.docx

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

Working teaching draft; supporting assets and source claims requiring verification are identified below.

Read the big promise as a claim to test

The Offer Generator sales letter promises a 20–30 page course plus pricing, funnel math, marketing angles and a business ecosystem from a course name. Page count and breadth describe an output promise; they do not prove accuracy, originality or a functioning business. In the lesson exercise, define a buyer problem and a bounded learning outcome before asking an AI system for a draft. The actual SuperPrompt is not included in this sales letter.

D0924 — assigned source supporting this teaching point

Distinguish the mechanism from its description

The named mechanism combines AI, sales psychology, competitive intelligence, pricing, value-ladder sequencing and funnel architecture. Explain which input and output each component would need. Naming these disciplines does not show how the engine applies them or validates its results. Keep the missing prompt and operating rules as dependencies rather than manufacturing a supposedly original engine.

D0924 — assigned source supporting this teaching point

Examine the authority appeal

The letter invokes more than 100 years of marketing science and names Claude Hopkins, John Caples, David Ogilvy, Robert Cialdini, Dan Kennedy, Russell Brunson, Alex Hormozi, Mark Joyner and RISER's Behavioral Influence System. Treat the list as an attribution claim in the copy, not proof that every method was implemented or endorsed. When teaching a specific principle, link the relevant source and explain the RISER adaptation separately.

D0924 — assigned source supporting this teaching point

Require evidence for replacement and price comparisons

The social-proof section says creators pay $10,000–$50,000 for comparable systems and that one prompt replaces agencies, designers, funnel teams, copywriters and consultants. No supporting transactions, comparisons or testimonials are supplied. Evaluate a concrete task, quality standard and review requirement rather than claiming complete professional replacement. A possible reduction in drafting effort is different from proven equivalent service delivery.

D0924 — assigned source supporting this teaching point

Address the blank-page problem honestly

The letter targets guessing and overwhelm with immediate structure, funnels, pricing, angles, modules and economics. A structured draft can help a learner begin, but it still needs source review, audience validation and revision. Explain which parts the learner must supply and verify. Do not convert a compelling emotional relief promise into a claim that uncertainty has been eliminated.

D0924 — assigned source supporting this teaching point

Separate positioning from expertise

The pre-suasion section promises instant authority and improved conversion before the first lesson is released. A generated outline cannot establish expertise or substantiate a conversion claim. Use it to organize demonstrated experience and supporting evidence. Similarly, the claim that competitors cannot keep up or that the user becomes permanently ahead is unsupported comparative language, not a durable strategic fact.

D0924 — assigned source supporting this teaching point

Connect the emotional driver to an achievable action

Confidence, power and creative freedom are the stated emotional benefits, expressed as a shift from hesitant creator to business architect. Translate that aspiration into a concrete next action: review one module, improve one explanation or test one offer hypothesis. An identity promise should not replace evidence that the proposed course helps its intended learner.

D0924 — assigned source supporting this teaching point

Check every promised output

The logical-benefit list includes funnels, value ladders, pricing models, CPC/CAC math, 1,000-click simulations, revenue projections, marketing angles, AI tools, offer structures, slides and syllabi. Use an acceptance checklist for all eleven categories. Distinguish observed campaign data from a scenario: a 1,000-click simulation requires explicit cost and conversion assumptions, and its projected revenue is not earned revenue. The source supplies no completed simulation or calculation model.

D0924 — assigned source supporting this teaching point

Test unlimited creation and rule-engine claims

Courses On Demand promises unlimited courses, offers and funnels with unmatched speed, quality and depth. The following differentiator promises a rule engine that always produces complete professional output with no missing sections. No usage terms, comparison study or validation procedure appears here. Count required sections, inspect sources and test a sample output; do not infer that unlimited means no platform limits or that an output is correct because it is long.

D0924 — assigned source supporting this teaching point

Rewrite the call to action around a deliverable

The original close asks the reader to build an empire through single-input business generation. A reviewable teaching application is to submit a sourced course outline, a draft lesson, an assumptions-based funnel model and a list of unresolved requirements. This preserves the copy's sequence from promise through mechanism, authority, emotion, logic and action while teaching the difference between persuasive language and substantiated capability.

D0924 — assigned source supporting this teaching point

Apply the agreed marketing lenses

D0924 — assigned source supporting this teaching point

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Complete original source text

Riser Nation Corporation
RISER Nation Offer Generator — SuperPrompt v2025
1. The Big Promise: “Your Entire Education Business… On Demand.”
Imagine having a tool so powerful—your new RISER Nation Offer Generator SuperPrompt v2025—that every time you type a course name, it produces a full 20–30 page course, pricing strategy, funnel math, marketing angles, and a complete business ecosystem on demand.
2. The Mechanism: The RISER Nation Offer Generator SuperPrompt v2025
A self-contained intelligence engine that merges modern AI capabilities with proven sales psychology, competitive intelligence, pricing logic, value ladder sequencing, and funnel architecture—all delivered instantly.
3. Authority Trigger: Built on 100+ Years of Proven Marketing Science
Constructed using principles from Claude Hopkins, John Caples, David Ogilvy, Robert Cialdini, Dan Kennedy, Russell Brunson, Alex Hormozi, Mark Joyner, and the RISER Nation Behavioral Influence System.
4. Social Proof Trigger: The System Top Creators Pay $10K–$50K For
This single prompt replaces agencies, course designers, funnel teams, copywriters, and consultants—delivering the same insights professionals charge tens of thousands of dollars for.
5. Pain-Point Penetration: The “Blank Page” Problem Is Dead
No more guessing. No more overwhelm. Type any course idea or topic, and the entire structure, funnel strategy, pricing, angles, modules, and economics appear instantly.
6. Pre-Suasion Trigger: Become an Expert Before You Sell
The system gives you instant authority, positioning you as a master in your niche before you release a single lesson—dramatically increasing conversions.
7. Scarcity of Ability: Competitors Can’t Keep Up
Your competitors are still trying to figure things out manually. You generate complete business ecosystems in seconds, putting you permanently ahead.
8. Emotional Driver: Confidence, Power, Creative Freedom
You gain total control of your brand, business, and creativity. The prompt transforms your identity—from hesitant creator to unstoppable architect of your own digital empire.
9. Logical Driver: Everything Done For You—Every Time
Each output includes funnels, value ladders, pricing models, CPC/CAC math, 1,000-click simulations, revenue projections, marketing angles, AI tools, offer structures, slides, and syllabi.
10. Irresistible Angle: “Courses On Demand”
Unlimited course creation. Unlimited offer creation. Unlimited funnel creation. Nothing matches the speed, quality, or depth of this system.
11. The Grand Differentiator: A Prompt With a Mind of Its Own
The embedded rule engine forces consistent, complete, professional outputs every time. No missing sections. No shortcuts. No guesswork.
12. Call to Action: Build Your Empire Now
Once you can generate entire businesses with a single input, you are no longer competing with other creators—you’re building a scalable, unstoppable digital empire powered by RISER Nation.

Original Word content in native document order, including recovered fields

word/document.xml
Riser Nation Corporation
RISER Nation Offer Generator — SuperPrompt v2025
1. The Big Promise: “Your Entire Education Business… On Demand.”
Imagine having a tool so powerful—your new RISER Nation Offer Generator SuperPrompt v2025—that every time you type a course name, it produces a full 20–30 page course, pricing strategy, funnel math, marketing angles, and a complete business ecosystem on demand.
2. The Mechanism: The RISER Nation Offer Generator SuperPrompt v2025
A self-contained intelligence engine that merges modern AI capabilities with proven sales psychology, competitive intelligence, pricing logic, value ladder sequencing, and funnel architecture—all delivered instantly.
3. Authority Trigger: Built on 100+ Years of Proven Marketing Science
Constructed using principles from Claude Hopkins, John Caples, David Ogilvy, Robert Cialdini, Dan Kennedy, Russell Brunson, Alex Hormozi, Mark Joyner, and the RISER Nation Behavioral Influence System.
4. Social Proof Trigger: The System Top Creators Pay $10K–$50K For
This single prompt replaces agencies, course designers, funnel teams, copywriters, and consultants—delivering the same insights professionals charge tens of thousands of dollars for.
5. Pain-Point Penetration: The “Blank Page” Problem Is Dead
No more guessing. No more overwhelm. Type any course idea or topic, and the entire structure, funnel strategy, pricing, angles, modules, and economics appear instantly.
6. Pre-Suasion Trigger: Become an Expert Before You Sell
The system gives you instant authority, positioning you as a master in your niche before you release a single lesson—dramatically increasing conversions.
7. Scarcity of Ability: Competitors Can’t Keep Up
Your competitors are still trying to figure things out manually. You generate complete business ecosystems in seconds, putting you permanently ahead.
8. Emotional Driver: Confidence, Power, Creative Freedom
You gain total control of your brand, business, and creativity. The prompt transforms your identity—from hesitant creator to unstoppable architect of your own digital empire.
9. Logical Driver: Everything Done For You—Every Time
Each output includes funnels, value ladders, pricing models, CPC/CAC math, 1,000-click simulations, revenue projections, marketing angles, AI tools, offer structures, slides, and syllabi.
10. Irresistible Angle: “Courses On Demand”
Unlimited course creation. Unlimited offer creation. Unlimited funnel creation. Nothing matches the speed, quality, or depth of this system.
11. The Grand Differentiator: A Prompt With a Mind of Its Own
The embedded rule engine forces consistent, complete, professional outputs every time. No missing sections. No shortcuts. No guesswork.
12. Call to Action: Build Your Empire Now
Once you can generate entire businesses with a single input, you are no longer competing with other creators—you’re building a scalable, unstoppable digital empire powered by RISER Nation.

RISER_Prompt_System_Marketability_Analysis (1).docx

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

Working teaching draft; supporting assets and source claims requiring verification are identified below.

Package a connected journey for two starting points

The marketability analysis presents a modular prompt system for both beginners without a niche and focused users with an idea to clarify and monetize. Suggested packaging names include RISER Prompt Vault, Digital Creator Jumpstart Kit and RISER Niche-to-Offer Protocol. The names are concepts, not evidence of an existing product or registered rights. Map each module to a learner's starting state so a buyer does not repeat work they have already completed.

D0925 — assigned source supporting this teaching point

Match audiences, hooks and formats

The broad audiences are coaches, course creators, solopreneurs, side-hustlers, digital marketers, freelancers and agency owners. Primary groups later listed are aspiring course creators, coaches/service providers, solopreneurs/niche experts and first-time offer builders; secondary groups are AI SaaS founders, agencies training clients and side-hustlers. The entry hooks address choosing a business, making an offer sell and moving from idea toward income. Choose a specific segment before adapting a hook; these phrases describe intentions, not validated demand.

D0925 — assigned source supporting this teaching point

Choose a packaging and monetization format

The proposed prompts are printable, plug-and-play and automation-ready modules, packaged as a PDF workbook, interactive Notion file or GHL funnel. Expanded formats include five prompts plus SOPs, a seven-day bootcamp/challenge, an evergreen course in Skool, Circle, Kajabi or GHL, an AI assistant using custom GPTs or CrewAI, and done-for-you services. Workshops, concept audits and AI funnel generation are proposed upsells. Each format requires its own delivery and support plan; the document does not supply those implementations.

D0925 — assigned source supporting this teaching point

Interpret the seven-day positioning carefully

The proposed tagline combines a first offer, seven days and an AI-enhanced prompt stack. Use seven days as a suggested activity schedule only if the scope fits; do not promise income or successful validation within that period. The source calls the ecosystem scalable and high-ticket, but neither label proves viability. It also references a full SOP and analysis DOCX by filename without a usable link in the readable text; retain that dependency for native-link inspection.

D0925 — assigned source supporting this teaching point

Use Idea Generator for an existing direction

RISER Idea Generator is categorized as a service/tool in AI-prompt format for mid-level creators or coaches. It uses an authoritative but encouraging voice, with keyword ideas business idea generator, clarify business idea and how to validate a niche. Its purpose is to extract the user's idea, passion or problem and feed a clearer concept into Concept Definition. The source assigns 92/100 viability and claims a validated angle in minutes, without a scoring method or market evidence. Treat clarification as the output and validation as subsequent work.

D0925 — assigned source supporting this teaching point

Use Rocket Launcher when the niche is unknown

Spin the Wheel, also called Rocket Launcher, is a quiz-style prompt and worksheet for beginners, students and creators. It is proposed as a viral lead magnet or tripwire, with keyword themes about what business to start, side-hustle ideas and an AI niche picker. It proposes five scored niche/product rockets feeding into Idea Generator and assigns 95/100 viability. The source calls them viable or tested, but no test records are supplied. Label generated ideas as hypotheses until researched.

D0925 — assigned source supporting this teaching point

Use Concept Definition to structure the idea

Concept Definition is a prompt template plus expansion logic for builders, marketers and agencies, placed in the core-product/setup stage. Its output is a structured offer concept with keywords, avatar, funnel type and automation considerations, leading to MVO. The assigned viability score is 90/100. Explain the bridge from an abstract idea to explicit assumptions without presenting that score as an independently measured probability of success.

D0925 — assigned source supporting this teaching point

Use MVO for a sellable first version

The Minimum Viable Offer prompt is described as an offer-crafting AI tool for creators, consultants and digital-product makers. It aims at a monetizable MVP and an early sale, then prepares the learner for Value Ladder. Its assigned score is 94/100. Keep the first deliverable small enough to test, with a clear buyer, scope and evidence requirement. Speed-to-sale is a positioning claim, not a guaranteed result.

D0925 — assigned source supporting this teaching point

Use Value Ladder for the broader customer journey

The Value Ladder prompt combines scaling logic and a worksheet for experienced users seeking customer lifetime value. It is positioned as flagship/backend, designing a front-to-back service or product journey and feeding Offer Stack and Playbook prompts. The score is 93/100. As a RISER application, make each next offer solve a distinct customer need; more tiers alone do not demonstrate higher lifetime value or better outcomes.

D0925 — assigned source supporting this teaching point

Preserve the traffic and risk matrix

The source maps Idea Generator to organic YouTube, Instagram and email, core/lead-magnet positioning and Low risk. Rocket Launcher maps to TikTok, Twitter and SEO, lead magnet/tripwire and Very Low risk. Concept Definition maps to email, paid ads and affiliate SEO, core/automation and Medium risk. MVO maps to Skool, YouTube and Facebook Groups, core/tripwire and Low risk. Value Ladder maps to email lists, webinars and LinkedIn, flagship/backend and Medium risk. These are proposed channel and risk labels without an evaluation method, not current performance evidence.

D0925 — assigned source supporting this teaching point

Build the proposed funnel ladder with explicit assumptions

The suggested awareness entry is Rocket Launcher, free or $9, for people lacking clarity. Engagement offers Idea Generator plus Concept Prompt at $47–$97. Conversion offers MVO plus Value Ladder at $197–$497. Backend ascension offers an Offer Engine or custom AI assistant at $997 or more. These are suggested prices, not observed willingness to pay. Explain what changes in scope and support at each step and test the economics before adopting the ladder.

D0925 — assigned source supporting this teaching point

Map every prompt to the RISER sequence

Realization uses Rocket Launcher or Idea Generator to identify a direction. Identification uses Concept Definition to clarify the idea, audience and model. Structure uses MVO and Value Ladder to shape a monetizable offer. Execution uses Offer Playbook and SOPs to create launch assets, content and systems. Refinement uses feedback and automation loops to improve from evidence. The sequence connects the prompts but does not substitute for the missing execution playbooks or working automation.

D0925 — assigned source supporting this teaching point

Recover the native fields and submit a route map

The readable export omitted two funnel-type labels that are present in the original Word file: Idea Generator is Lead Magnet → Core, and MVO is Tripwire → Core Offer. It also omitted the table's viability values: Idea Generator 92/100, Rocket Launcher 95/100, Concept Definition 90/100, MVO 94/100 and Value Ladder 93/100. These match the profile scores but still lack a scoring methodology. Submit separate routes for a beginner and a focused user, showing input, prompt, expected draft, evidence needed, next step and the proposed commercial offer. Use the restored native fields rather than interpreting extraction blanks as missing source data.

D0925 — assigned source supporting this teaching point

Apply the agreed marketing lenses

D0925 — assigned source supporting this teaching point

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Complete original source text

📂 RISER Prompt System – Marketability & Viability Analysis
📁 Prompt System Overview
🧠 Marketability & Offer Packaging Analysis

The RISER Prompt System provides a modular but interconnected journey for entrepreneurs and creators at any stage of ideation. Packaging these into a single product—called something like “The RISER Prompt Vault” or “The Digital Creator Jumpstart Kit”—offers a powerful value proposition. Here's the expert assessment:
• Target Audiences: Coaches, course creators, solopreneurs, side-hustlers, digital marketers, freelancers, agency owners.
• Entry Hooks: “Can’t decide what business to start?” or “Struggling to build an offer that sells?” or “Turn your idea into income with our guided prompts.”
• Product Packaging: Each prompt becomes a module in an onboarding flow. The prompts are printable, plug-and-play, and automation-ready.
• Sellable Format: Bundle as PDF workbook, interactive Notion file, or GoHighLevel funnel.
• Upsell Path: Add in live workshops, concept audits, or AI-Powered funnel generation.
• Positioning: “Finally a prompt pack that takes you from zero to scalable offer.”
______________________________________________________________________
Here is your requested Concept Prompt Analysis and Marketability Viability Report for the five core RISER Nation offer-finding prompts:
📄 Download the full SOP + Analysis Document (Docx):
 👉 RISER_Nation_Offer_Prompts_Concept_Analysis_and_Scaling_Strategy.docx
🔍 Executive Summary
You've developed a scalable ecosystem of prompt-driven tools that serve two user archetypes:
🚀 Beginner Users (who don’t yet know their niche)

🎯 Focused Users (who already know their idea but need help clarifying and monetizing it)

Each of the following five prompts plays a critical step in the funnel, and when used together, form a high-ticket productization engine.
📦 Packaging Idea: “The RISER Niche-to-Offer Protocol™”
Tagline:
 "From Idea to Income: Launch Your First Offer in 7 Days Using Our AI-Enhanced Prompt Stack"
Monetization Formats:
🧩 Digital product pack (5 prompts + SOPs)

🎓 Bootcamp or Challenge (7-Day Launch)

📚 Evergreen course (hosted in Skool, Circle, Kajabi, or GoHighLevel)

🧠 AI Assistant SaaS (using Custom GPTs or CrewAI agents per prompt)

💼 DFY Agency Services (for coaches, consultants, creators)

🔢 Concept Prompt Expansion — Summary Table
🎯 Target Audiences
Primary:
Aspiring course creators

Coaches and service providers

Solopreneurs and niche experts

First-time offer builders

Secondary:
AI startup founders building SaaS

Marketing agencies training new clients

Side hustlers exploring online income

📈 Funnel Strategy (Suggested Stack)
📌 Concept Prompt Analysis for Each Prompt Tool
Each tool was analyzed using our RISER Concept Definition Prompt framework. Here's a quick summary of each:
1. 📁 RISER Idea Generator Prompt
Category: Service / Tool

Format: AI Prompt System

Avatar: Mid-level creator or coach

Funnel Type:
Keyword Clusters: “business idea generator,” “clarify business idea,” “how to validate a niche”

Voice/Tone: Authoritative but encouraging

USP: Turns rough idea into validated business angle in minutes

Viability Score: 92/100

2. 📁 Spin the Wheel (Rocket Launcher Prompt)
Category: Ideation Engine

Format: Quiz-style prompt + worksheet

Avatar: Newbie entrepreneur, student, creator

Funnel Type: Tripwire or Viral Lead Magnet

Keywords: “what business should I start,” “side hustle ideas,” “AI niche picker”

USP: Instantly generates viable ideas with niche scoring

Viability Score: 95/100

3. 📁 Concept Definition Prompt
Category: Strategic Planning Tool

Format: Prompt Template + Expansion AI logic

Avatar: Builders, marketers, agency owners

Funnel Type: Core Product / Setup Phase

USP: Turns abstract ideas into structured offer frameworks with automation readiness

Viability Score: 90/100

4. 📁 Minimum Viable Offer Prompt
Category: Monetization Tool

Format: Offer Crafting AI Prompt

Avatar: Creators, consultants, digital product makers

Funnel Type:
USP: Gets users to their first sale FAST

Viability Score: 94/100

5. 📁 Value Ladder Prompt
Category: Strategic Monetization System

Format: Prompt with scaling logic + worksheet

Avatar: Experienced users wanting lifetime customer value

Funnel Type: Flagship or Backend

USP: Creates a whole business roadmap (front to back)

Viability Score: 93/100

🧠 How the RISER Protocol Fits
Each of these prompt tools fits perfectly into the RISER Framework:
Prompt Name
Audience
Purpose
What It Unlocks
What It Connects To
RISER Idea Generator Prompt
For Users Who DO Know Their Niche
Kickstarts a focused business concept development by extracting the user’s core idea, passion, or problem they're solving.
Clarifies the user's big idea and ensures it's framed properly for business validation.
Flows directly into the Concept Definition Prompt.
Spin the Wheel Prompt (Rocket Launcher)
For Users Who DO NOT Know Their Niche
Generates five unique, high-viability niche or product “rockets” using market research and prompt analysis.
Offers tested entry points into profitable niches.
Feeds into the RISER Idea Generator Prompt.
Concept Definition Prompt
For Users With a Defined or Generated Idea
Turns the selected idea into a structured concept with keywords, avatars, funnel types, etc.
Bridges creativity with strategy.
Leads into the Minimum Viable Offer Prompt.
Minimum Viable Offer (MVO) Prompt
For Users Creating Their First Sellable Offer
Builds a monetizable MVP.
Gets a sellable version launched fast.
Prepares for the Value Ladder Prompt.
Value Ladder Prompt
For Users Ready to Scale
Designs a full product or service journey.
Maximizes customer LTV and scale.
Feeds into Offer Stack and Playbook prompts.
Prompt
Market Viability
Primary Audience
Top Traffic Channels
Offer Tier
Risk Level
RISER Idea Generator
Coaches, creators, solopreneurs
Organic YouTube, Instagram, Email
Core / Lead Magnet
🔵 Low
Spin the Wheel (Rocket Launcher)
Beginners, niche explorers, students
TikTok, Twitter, SEO
Lead Magnet / Tripwire
🟢 Very Low
Concept Definition Prompt
Agency owners, product creators
Email, Paid Ads, Affiliate SEO
Core / Automation
🟡 Med
Minimum Viable Offer (MVO) Prompt
Entrepreneurs, course builders
Skool, YouTube, FB Groups
Core Offer / Tripwire
🔵 Low
Value Ladder Prompt
Advanced users, scaling coaches
Email list, webinars, LinkedIn
Flagship / Backend
🟡 Med
Stage
Prompt / Product
Price
Purpose
TOFU – Awareness
Rocket Launcher
Free or $9
Attract users who lack clarity
MOFU – Engagement
Idea Generator + Concept Prompt
$47 – $97
Clarify and structure their idea
BOFU – Conversion
MVO Prompt + Value Ladder Prompt
$197 – $497
Build a full offer and monetization
Backend – Ascension
Offer Engine / Custom AI Assistant
$997+
Personalized scaling systems
RISER Step
Connected Prompt
Purpose
R – Realization
Rocket Launcher / Idea Generator
Helps users realize what path they want
I – Identification
Concept Definition Prompt
Clarifies core idea, audience, and model
S – Structure
MVO + Value Ladder
Builds a monetizable structure
E – Execution
Offer Playbook + SOPs
Launch assets, content, and systems
R – Refinement
Feedback loops + Automation
Optimize, test, and scale with AI loops

Original Word content in native document order, including recovered fields

word/document.xml
📂 RISER Prompt System – Marketability & Viability Analysis
📁 Prompt System Overview
Prompt Name
Audience
Purpose
What It Unlocks
What It Connects To
RISER Idea Generator Prompt
For Users Who DO Know Their Niche
Kickstarts a focused business concept development by extracting the user’s core idea, passion, or problem they're solving.
Clarifies the user's big idea and ensures it's framed properly for business validation.
Flows directly into the Concept Definition Prompt.
Spin the Wheel Prompt (Rocket Launcher)
For Users Who DO NOT Know Their Niche
Generates five unique, high-viability niche or product “rockets” using market research and prompt analysis.
Offers tested entry points into profitable niches.
Feeds into the RISER Idea Generator Prompt.
Concept Definition Prompt
For Users With a Defined or Generated Idea
Turns the selected idea into a structured concept with keywords, avatars, funnel types, etc.
Bridges creativity with strategy.
Leads into the Minimum Viable Offer Prompt.
Minimum Viable Offer (MVO) Prompt
For Users Creating Their First Sellable Offer
Builds a monetizable MVP.
Gets a sellable version launched fast.
Prepares for the Value Ladder Prompt.
Value Ladder Prompt
For Users Ready to Scale
Designs a full product or service journey.
Maximizes customer LTV and scale.
Feeds into Offer Stack and Playbook prompts.
🧠 Marketability & Offer Packaging Analysis
The RISER Prompt System provides a modular but interconnected journey for entrepreneurs and creators at any stage of ideation. Packaging these into a single product—called something like “The RISER Prompt Vault” or “The Digital Creator Jumpstart Kit”—offers a powerful value proposition. Here's the expert assessment:
• Target Audiences: Coaches, course creators, solopreneurs, side-hustlers, digital marketers, freelancers, agency owners.
• Entry Hooks: “Can’t decide what business to start?” or “Struggling to build an offer that sells?” or “Turn your idea into income with our guided prompts.”
• Product Packaging: Each prompt becomes a module in an onboarding flow. The prompts are printable, plug-and-play, and automation-ready.
• Sellable Format: Bundle as PDF workbook, interactive Notion file, or GoHighLevel funnel.
• Upsell Path: Add in live workshops, concept audits, or AI-Powered funnel generation.
• Positioning: “Finally a prompt pack that takes you from zero to scalable offer.”
______________________________________________________________________
Here is your requested 
Concept Prompt Analysis
 and 
Marketability Viability Report
 for the five core RISER Nation offer-finding prompts:
📄 
Download the full SOP + Analysis Document (Docx):
 👉 RISER_Nation_Offer_Prompts_Concept_Analysis_and_Scaling_Strategy.docx
🔍 Executive Summary
You've developed a scalable ecosystem of prompt-driven tools that serve two user archetypes:
🚀 
Beginner Users
 (who don’t yet know their niche)
🎯 
Focused Users
 (who already know their idea but need help clarifying and monetizing it)
Each of the following five prompts plays a 
critical step in the funnel
, and when used together, form a 
high-ticket productization engine
.
📦 Packaging Idea: 
“The RISER Niche-to-Offer Protocol™”
Tagline:
 
"From Idea to Income: Launch Your First Offer in 7 Days Using Our AI-Enhanced Prompt Stack"
Monetization Formats:
🧩 Digital product pack (5 prompts + SOPs)
🎓 Bootcamp or Challenge (7-Day Launch)
📚 Evergreen course (hosted in Skool, Circle, Kajabi, or GoHighLevel)
🧠 AI Assistant SaaS (using Custom GPTs or CrewAI agents per prompt)
💼 DFY Agency Services (for coaches, consultants, creators)
🔢 Concept Prompt Expansion — Summary Table
Prompt
Market Viability
Primary Audience
Top Traffic Channels
Offer Tier
Risk Level
RISER Idea Generator
✅ 92/100
Coaches, creators, solopreneurs
Organic YouTube, Instagram, Email
Core / Lead Magnet
🔵 Low
Spin the Wheel (Rocket Launcher)
✅ 95/100
Beginners, niche explorers, students
TikTok, Twitter, SEO
Lead Magnet / Tripwire
🟢 Very Low
Concept Definition Prompt
✅ 90/100
Agency owners, product creators
Email, Paid Ads, Affiliate SEO
Core / Automation
🟡 Med
Minimum Viable Offer (MVO) Prompt
✅ 94/100
Entrepreneurs, course builders
Skool, YouTube, FB Groups
Core Offer / Tripwire
🔵 Low
Value Ladder Prompt
✅ 93/100
Advanced users, scaling coaches
Email list, webinars, LinkedIn
Flagship / Backend
🟡 Med
🎯 Target Audiences
Primary:
Aspiring course creators
Coaches and service providers
Solopreneurs and niche experts
First-time offer builders
Secondary:
AI startup founders building SaaS
Marketing agencies training new clients
Side hustlers exploring online income
📈 Funnel Strategy (Suggested Stack)
Stage
Prompt / Product
Price
Purpose
TOFU – Awareness
Rocket Launcher
Free or $9
Attract users who lack clarity
MOFU – Engagement
Idea Generator
 + 
Concept Prompt
$47 – $97
Clarify and structure their idea
BOFU – Conversion
MVO Prompt
 + 
Value Ladder Prompt
$197 – $497
Build a full offer and monetization
Backend – Ascension
Offer Engine
 / 
Custom AI Assistant
$997+
Personalized scaling systems
📌 Concept Prompt Analysis for Each Prompt Tool
Each tool was analyzed using our 
RISER Concept Definition Prompt
 framework. Here's a quick summary of each:
1. 📁 RISER Idea Generator Prompt
Category:
 Service / Tool
Format:
 AI Prompt System
Avatar:
 Mid-level creator or coach
Funnel Type:
 Lead Magnet → Core
Keyword Clusters:
 “business idea generator,” “clarify business idea,” “how to validate a niche”
Voice/Tone:
 Authoritative but encouraging
USP:
 Turns rough idea into validated business angle in minutes
Viability Score:
 92/100
2. 📁 Spin the Wheel (Rocket Launcher Prompt)
Category:
 Ideation Engine
Format:
 Quiz-style prompt + worksheet
Avatar:
 Newbie entrepreneur, student, creator
Funnel Type:
 Tripwire or Viral Lead Magnet
Keywords:
 “what business should I start,” “side hustle ideas,” “AI niche picker”
USP:
 Instantly generates viable ideas with niche scoring
Viability Score:
 95/100
3. 📁 Concept Definition Prompt
Category:
 Strategic Planning Tool
Format:
 Prompt Template + Expansion AI logic
Avatar:
 Builders, marketers, agency owners
Funnel Type:
 Core Product / Setup Phase
USP:
 Turns abstract ideas into structured offer frameworks with automation readiness
Viability Score:
 90/100
4. 📁 Minimum Viable Offer Prompt
Category:
 Monetization Tool
Format:
 Offer Crafting AI Prompt
Avatar:
 Creators, consultants, digital product makers
Funnel Type:
 Tripwire → Core Offer
USP:
 Gets users to their first sale FAST
Viability Score:
 94/100
5. 📁 Value Ladder Prompt
Category:
 Strategic Monetization System
Format:
 Prompt with scaling logic + worksheet
Avatar:
 Experienced users wanting lifetime customer value
Funnel Type:
 Flagship or Backend
USP:
 Creates a whole business roadmap (front to back)
Viability Score:
 93/100
🧠 How the RISER Protocol Fits
Each of these prompt tools fits perfectly into the RISER Framework:
RISER Step
Connected Prompt
Purpose
R – Realization
Rocket Launcher / Idea Generator
Helps users realize what path they want
I – Identification
Concept Definition Prompt
Clarifies core idea, audience, and model
S – Structure
MVO + Value Ladder
Builds a monetizable structure
E – Execution
Offer Playbook + SOPs
Launch assets, content, and systems
R – Refinement
Feedback loops + Automation
Optimize, test, and scale with AI loops

RISER-Affiliate-Program-Architecture-SOP.docx

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

Working teaching draft. Source examples and policy assumptions require context; corrections and unresolved dependencies are identified in the script.

Separate partner strategy from operating architecture

This SOP covers the system behind an affiliate program: platform selection, attribution, commissions, payment, portal, links, disputes, fraud, audits, backups and migration. The separate Partnerships and Affiliate Scaling SOP covers recruitment and relationship strategy. The source's Course 46 reference belongs to its internal system and does not change our spreadsheet assignments. The practical distinction is clear: a good partner relationship still depends on accurate records and reliable delivery. Its claims about typical failures and scaling from five to 200 affiliates are design motivations, not measured results supplied here.

D0926 — assigned source supporting this teaching point

Related source resources: RISER-Partnerships-Affiliate-Scaling-SOP.docx — related SOP ·

Establish both launch standards

Before issuing a live link, the source requires a complete test transaction showing the correct commission in the affiliate dashboard and matching attribution in the operator's CRM. It also requires an independent record of attributed sales and commissions. Use those as two separate acceptance checks: end-to-end operation and recoverable evidence. The independent record needs transaction identifiers, dates and adjustment history; merely copying a platform's total does not provide independent verification.

D0926 — assigned source supporting this teaching point

Evaluate all six platform criteria

Check native payment/course integration, a real-time self-service dashboard, unique links with sub-IDs, recurring commission support, flexible rules by offer/tier/time, and adjustment or override capability. Ask what happens on an actual paid event, renewal, refund, discount and correction. The source's examples of missed tracking percentages, manual hours and conversion advantages are unverified illustrations. API integration can reduce reliance on browser signals, but it cannot infer a referral relationship that was never captured.

D0926 — assigned source supporting this teaching point

Read the five platform profiles as dated examples

The source positions ThriveCart's native module for existing ThriveCart users, listing flat, percentage, tiered and split commissions and a $495–$690 one-time license. It positions PartnerStack for larger programs, including a suggested $15,000 monthly affiliate-revenue threshold and $500–$2,000+ monthly cost; Impact for mixed affiliate types at $500–$3,000+; Rewardful for Stripe users at $49–$299; and FirstPromoter for Stripe/Paddle/Braintree/Recurly at $49–$149. Recurring commissions and self-service dashboards are advertised for all five. These are source estimates and capability descriptions, not verified current recommendations. Confirm the actual plan, integration and terms before choosing.

D0926 — assigned source supporting this teaching point

Configure the program and each offer

The setup sequence begins with a business-owned account, program name/logo/default rate and public application URL. Source defaults are a 30-day cookie, last-click attribution, a $50 payout minimum and payment on the 15th for the prior month. Then connect the payment processor and verify both sides plus actual events. For each offer record its exact name, percentage or flat commission, initial-only or recurring treatment, cookie scope and any launch override. Explicitly exclude offers outside the program, including internal or phone-close offers when that is the agreed policy. These are proposed program terms, not universal defaults.

D0926 — assigned source supporting this teaching point

Record confirmed payments without duplicate commissions

The source correctly distinguishes a paid transaction from a page view, initiated checkout or failed attempt and names payment_intent.succeeded as one Stripe success event. The event choice must fit the integration and payment method. Stripe's current guidance also requires signature verification and handling retries or duplicates. In a teaching design, connect a unique transaction to one commission decision and keep later refunds as adjustments; a dashboard connection label alone is not proof that this works. No live webhook or payment is created by this lesson.

D0926 — assigned source supporting this teaching point · Stripe webhook documentation

Test the complete journey and cross-device limitations

The source proposes a separate test affiliate, a unique link, a test-mode or zero-coupon purchase, and checks for click, conversion within five minutes, correct commission, affiliate visibility and CRM UTM data. A zero-value coupon may exercise a different event path or commission base from a paid order; test the relevant paid, renewal and refund paths in a supported test environment. For mobile-click/desktop-purchase, explicitly establish how the buyer's identity is linked to the referral. API-based payment events alone do not guarantee cross-device attribution. A failed test identifies a gap to investigate, not automatic proof of a particular configuration error.

D0926 — assigned source supporting this teaching point

Keep all three UTM integration records

The proposed link convention is utm_source=[affiliate_id], utm_medium=affiliate and utm_campaign=[program_or_launch]. Capture those values at opt-in in the CRM and record the eventual purchase alongside the affiliate platform's commission event. Preserve the source's first-touch CRM record, but distinguish it from the proposed last-click commission rule. Those two models may legitimately credit different touchpoints. Reconcile according to documented attribution terms instead of treating any CRM match as a command to award a commission.

D0926 — assigned source supporting this teaching point

Related source resources: RISER-Content-to-Revenue-Attribution-SOP.docx — related SOP ·

Define percentage, flat and recurring commissions

The source's percentage base is transaction value after processing fees but before other fulfillment/platform costs. That is a proposed contract definition; verify whether the chosen platform can implement it. Configure product exclusions for multi-product orders. Flat commissions need separate monthly and annual rules, illustrated by $97/month versus $797/year. Recurring commission should follow successful renewals, with its own rate if applicable, and exclude failed charges. Keep the gross sale, deductions, commission base and rate separately inspectable.

D0926 — assigned source supporting this teaching point

Handle refunds, coupons and upstream splits explicitly

The source reverses full-refund commissions and proportionally adjusts partial refunds, carrying a previously paid reversal into a later balance. Ordinary discounts reduce the commission base, while named commission-protected bonus coupons are exceptions; define that exception so a $100 discount does not silently change a promised commission. For a two-tier program, the recruiting affiliate's share comes from an additional pool rather than reducing the downstream affiliate's stated earnings. These rules require agreed terms and tested examples, including what happens when the balance becomes negative.

D0926 — assigned source supporting this teaching point

Specify all four bonus types before promising them

The proposed first-sale bonus is $25–$50 for a first confirmed sale within 30 days of approval, paid next cycle and reviewed at Day 30. Volume milestones are $50 at five, $150 at ten and $500 at 20 monthly sales; define whether they accumulate or only the highest applies. Launch leaderboard examples are $500–$2,000+ for first, $250–$1,000 for second and $100–$500 for third, paid within ten business days of close. A recruit bonus is $25–$100 when the recruited partner sells within 60 days, paid next cycle. Keep trigger evidence and payment status in Bonus Records. Vendor automation claims require verification; manual tracking is an option, not a reason to omit the record.

D0926 — assigned source supporting this teaching point

Reconcile the payment calendar before running it

The SOP names the 15th in setup, the 12th in a protocol heading, and a cycle starting on the 1st or nearest Monday. It also combines a 24-hour review, Day 3 payment and an expected date three business days after the statement. These are incompatible unless a single calendar is chosen. Record the cutoff, reconciliation date, statement date, review window and payment date in one approved schedule. The lesson preserves all source dates so an implementer can resolve them deliberately.

D0926 — assigned source supporting this teaching point

Prepare the payable ledger

Payment steps one through five export approved commissions with the refund window closed, excluding reversed, held and void items; compare every commission to CRM purchases and every tagged purchase to commission records; apply prior refund adjustments; add earned bonuses; and carry balances below $50 forward. A mismatch should open an investigation. Do not automatically add or reject a payment solely because first-touch and last-click records differ. Record the reason and evidence for any manual adjustment.

D0926 — assigned source supporting this teaching point

Prepare statements, review and payment evidence

Steps six through nine produce a statement with clicks, confirmed sales, gross commission, deductions, bonuses, net amount and expected date; allow the stated review period; use the affiliate's agreed PayPal, Wise, ACH or other method; and retain transaction ID and payment date with confirmation. A teaching exercise can build a sample statement and reconciliation without executing a payout or sending a message. Keep disputed amounts and undisputed amounts distinguishable rather than obscuring a discrepancy inside a total.

D0926 — assigned source supporting this teaching point

Update the source's tax instruction

Step ten uses a blanket $600 threshold, W-9/W-8BEN language and a January 31 filing statement. The IRS FAQ currently identifies $2,000 for covered service payments made after December 31, 2025, with exceptions; a reporting threshold is not an income-tax exemption. Payee status, payment method, withholding and the applicable form matter. Use the linked IRS guidance to determine the actual obligation rather than copying the old sentence into an automated rule. The source text remains in the appendix for traceability.

D0926 — assigned source supporting this teaching point · IRS — Form 1099-NEC and independent contractors

Resolve all four dispute types with evidence

For missing commissions, inspect the click, customer/referral association, payment and applicable attribution window; the source targets 48 hours. For an incorrect amount, inspect price, discount, base, rate and tier, with a 24-hour target. For refund reversals, confirm the processor event and agreed policy, with 48 hours. For a sub-ID problem, inspect formatting and offer mapping, with 24 hours. These are internal response targets. A click and purchase in the same 30 days alone do not establish ownership; explain the evidence and preserve a correction trail.

D0926 — assigned source supporting this teaching point

Build all seven portal sections

The dashboard should show clicks, conversions, pending balance, lifetime earnings, payment history and any relevant launch notice. My Links needs primary links, sub-ID creation and copying within a short path. Assets should be dated, organized by format and retain archived versions. Offer Details needs name, price, sales-page link, commission, refund policy and a short description. Commission History needs expandable transaction and adjustment detail. A launch leaderboard should appear only during its actual event. Support needs a clear contact route and response expectation, illustrated as 24 business hours. Displayed numbers must agree with the ledger.

D0926 — assigned source supporting this teaching point

Issue and test links in all four situations

At approval, generate and test a unique link before giving it to a partner. For a new offer, generate correctly mapped links for existing partners. For a JV launch, verify the launch-specific rate and link. For a suspected break, inspect routing and tracking with a supported test transaction. A referral parameter in a URL is useful evidence of transmission but does not by itself prove correct attribution. The source's communication templates describe operational tasks; this lesson does not send them.

D0926 — assigned source supporting this teaching point

Run the five-step quarterly link audit

Export affiliate ID/name, link URL, offer and configured rate. Test each destination and redirect chain. Compare rates to the partner's documented tier. Test one cross-device path per offer with a known identity association. Resolve findings, record dates and investigate missed commissions, with the source targeting seven days. A 200 response proves availability only; a correct destination, attribution event and amount still need testing. The cited monitoring tools are examples rather than a tested solution here.

D0926 — assigned source supporting this teaching point

Understand self-referral and fake-traffic controls

The source illustrates self-referral with a $797 product and 30% commission: $239.10 returned and an effective $557.90 price. If prohibited by program terms, use platform controls plus identity review; matching email alone is incomplete. For fake traffic, the source proposes 0.5–5% as a normal conversion range and below 0.1% over 30 days as a flag. Those unverified ranges are investigation prompts, not proof of fraud. Consider legitimate audience, tracking and offer explanations before acting.

D0926 — assigned source supporting this teaching point

Distinguish chargebacks and cookie stuffing

The source describes collusive or fraudulent purchases followed by chargebacks, and unearned attribution planted without a genuine referral. Do not label every dispute fraudulent. Refund policy and card-dispute deadlines differ: Stripe notes that cardholders typically have 120 days, with cases that allow longer periods. The SOP's blanket 60–90-day assumption is insufficient. API events do not inherently prevent cookie stuffing; genuine referral capture, identity association and event controls still matter. Its above-10% conversion flag is not a finding of abuse.

D0926 — assigned source supporting this teaching point · Stripe dispute timelines

Schedule all six audit areas and independent backups

The source proposes quarterly tracking checks taking three to four hours for up to 50 affiliates; monthly commission verification taking two to three hours; quarterly disclosure spot-checks of ten to fifteen promotions taking two hours; monthly fraud review taking one hour; monthly independent exports taking 30 minutes; and quarterly platform-health review taking one hour. These are planning estimates. Check affiliate disclosures against current FTC guidance, and review billing, integration status and feature changes. Back up partner, commission and payment records separately from the platform and test that the data can be restored.

D0926 — assigned source supporting this teaching point · FTC — Endorsement and affiliate disclosure guidance

Complete the audit log and action register

Use an AUDIT-[year-quarter] identifier, date and reviewer. Record links audited/issues/resolution dates, rate mismatches, cross-device result, promotions and partners reviewed, disclosure issues and notifications, fraud investigations and resolutions, commissions and partners paid, disputes received/resolved/open, backup completion/location, and prioritized actions with owners and due dates. The log records what actually happened; unchecked items stay open. A scheduled audit or a completed checkbox is not evidence that a test passed.

D0926 — assigned source supporting this teaching point

Plan all seven migration stages

Document the reason and cost-benefit case before changing platforms. The source places new setup/testing six to eight weeks ahead, partner notice four weeks ahead, full historical export two weeks ahead, and final old-platform reconciliation one week ahead. On migration day, provide new credentials, links and a short guide; after 90 days of confirmed operation, consider retiring the old system. Address outstanding refunds, commissions, record retention and old promotional links before decommissioning. These are planning steps, not permission to close an account or erase data.

D0926 — assigned source supporting this teaching point

Build the Commission Records schema

The source fields are Commission ID using COMM-[Partner]-[YYYY-MM]-[Seq], linked Partner, Transaction Date, Offer Name, net Transaction Amount, Commission Rate, gross Commission Amount, Status, Payment Cycle, CRM Verification, CRM Purchase Record ID, Sub-ID, Bonus Commission and Notes. The percentage formula is net amount × rate ÷ 100. Statuses are Pending, Approved, Paid, Reversed, Void and Disputed. The notes call the CRM purchase ID a contact ID; retain a unique transaction reference as an authored addition so multiple purchases by one person can be distinguished. Flat-fee rules need their own calculation path.

D0926 — assigned source supporting this teaching point

Build Bonus Records and Programme Audit Log

Bonus Records contains Bonus ID, Partner, type, trigger description, amount, payment cycle, paid checkbox and notes. The proposed BONUS-[Partner]-[YYYY-MM] format can collide when a partner earns several bonuses; add a sequence or unique identifier as an explicit adaptation. Programme Audit Log contains ID/date/reviewer/type, links audited/issues, commission mismatches, compliance issues, fraud indicators, backup and resolution checkboxes, open items and notes. Preserve the three audit types: Quarterly Full, Monthly Commission and Ad Hoc.

D0926 — assigned source supporting this teaching point

Submit the architecture acceptance pack

Prepare a selected-platform evaluation, offer/rate matrix, test evidence, attribution contract, commission examples, bonus terms, reconciled calendar, statement, portal map, link-audit record, fraud-review process, backup plan and migration checklist. Reconcile the master checklist's setup, tracking, commission, payment, portal and recurring-audit items against actual evidence. Keep missing integrations and unresolved policy decisions visible. The teaching output is a reviewable design, not an assertion that an affiliate program has been installed.

D0926 — assigned source supporting this teaching point

Apply the agreed marketing lenses

As a RISER adaptation, use Brunson/ClickFunnels Hook, Story, Offer to connect a relevant opening, truthful explanation and concrete next step. Use Hormozi/Acquisition.com value thinking to examine the desired result, confidence in delivery, delay and required effort. These lenses do not verify numerical claims, imply endorsement or replace the operational evidence required by this SOP.

D0926 — assigned source supporting this teaching point · ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Complete original source export

RISER NATION
MASTER OPERATING SYSTEM
SOP — AFFILIATE PROGRAM ARCHITECTURE
The Complete Technical and Operational Build Manual for the RISER Nation Affiliate Program — Platform Selection, Tracking Infrastructure, Commission Engine, Payment System, Affiliate Portal, Link Management, Dispute Resolution, Fraud Prevention, and Program Audit Protocol
2026 Framework × RISER Nation Master Operating System
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview — Architecture vs Strategy
The Partnerships and Affiliate Scaling SOP (Course 46) covers the strategic layer of the RISER Nation partner programme: who to recruit, how to approach them, what partnership types to offer, how to manage JV launches, and how to measure programme performance. This SOP covers the technical and operational layer: the specific platforms, configurations, tracking mechanisms, commission calculation logic, payment workflows, link management systems, and audit protocols that make the programme function reliably at scale.
The distinction matters because the most common affiliate programme failure is not strategic — it is architectural. An operator who recruits excellent partners, provides strong promotional assets, and manages relationships superbly will still damage those relationships if the underlying infrastructure produces tracking errors, incorrect commission statements, delayed payments, or broken affiliate links. Architecture failures are trust failures. Every tracking error is a potential dispute. Every payment delay is a relationship risk. Every broken link is lost commission the affiliate earned but never collected. The architecture SOP exists to make these failures rare and to make recovery from them fast when they do occur.
This SOP covers: the platform evaluation and selection framework, the tracking infrastructure build protocol, the commission engine configuration, the payment system setup, the affiliate portal design standards, the link management and testing protocol, the monthly programme audit, the commission dispute resolution process, the fraud prevention framework, the data backup and recovery protocol, and the migration plan for moving between affiliate platforms.
Platform Evaluation and Selection
The affiliate platform is the technical core of the programme — it generates unique links, tracks clicks and conversions, calculates commissions, and provides the affiliate-facing dashboard. Selecting the right platform is the highest-leverage architecture decision because it determines the programme's tracking reliability, payment capability, and management overhead for the lifetime of the programme.
The Platform Evaluation Framework
The RISER Nation Platform Recommendation
The platform recommendation is based on the most common RISER Nation operator tech stack (Stripe or ThriveCart as payment processor, ActiveCampaign or ConvertKit as email platform, Kajabi, Teachable, or Thinkific as course platform). Operators using significantly different tech stacks should re-evaluate using the framework above rather than defaulting to the recommendation.
The Tracking Infrastructure Setup Protocol
The tracking infrastructure is the collection of technical components that connect a partner's promotional activity (a click on their affiliate link) to a purchase event (a confirmed, paid transaction) and attribute the commission correctly. Each component must be configured and tested in sequence — skipping or abbreviating any step introduces attribution errors that compound over time.
The UTM Integration Layer
The affiliate platform's tracking and the RISER Nation UTM convention from the Content-to-Revenue Attribution SOP must be integrated — so that each affiliate-referred subscriber and buyer is tagged in the CRM with both the affiliate platform's attribution and the standard UTM attribution. This dual-tagging enables independent commission verification and integrates affiliate revenue into the broader content-to-revenue reporting system.
Commission Calculation Logic
Commission calculation must be explicitly configured — the platform does not automatically know which transactions are commissionable, how refunds affect commissions, how bonus structures work, or how split commissions between tiers of the affiliate hierarchy should be handled. Every commission rule must be configured and verified before the first live affiliate link is issued.
The Bonus Commission Framework
Bonus commissions — additional commission payments above the standard rate for achieving specific milestones — are the primary motivation lever for moving affiliates from the Standard tier to the Active tier, and from Active to Super Affiliate. The bonus framework must be configured in the platform or tracked manually in a secondary system before any bonus is promised.
The Monthly Commission Payment Protocol
The commission payment workflow must be executed with the same discipline as payroll — on a fixed schedule, with independent verification, and with complete documentation of each payment. Inconsistent or delayed payments are the single most damaging operational failure an affiliate programme can produce.
The Commission Dispute Resolution Protocol
Commission disputes arise when an affiliate believes they were not credited for a sale they generated. Disputes handled well strengthen the relationship — the affiliate sees that the operator takes attribution seriously. Disputes handled poorly (delayed response, dismissiveness, or incorrect resolution) permanently damage the relationship.
What the Affiliate Portal Must Contain
The affiliate portal is the affiliate's primary interface with the programme. Its design determines whether affiliates feel professionally supported (which motivates promotion) or confused and under-resourced (which discourages promotion). Every element of the portal serves one function: making it as easy as possible for an affiliate to find what they need, take the next action, and understand how they are performing.
The Link Management and Testing Protocol
Affiliate links are the primary operational asset of the programme. A broken affiliate link silently destroys commission attribution without any obvious error message — the buyer arrives at the sales page, the page loads normally, and the purchase is completed, but the affiliate's link click was not correctly tracked and the commission is not attributed. The link testing protocol prevents this.
The Link Issuance Protocol
The Quarterly Link Audit
Every affiliate's links are tested quarterly — regardless of whether any issue has been reported. Many tracking problems are silent: they do not produce an error, they do not alert the affiliate or the operator, and they accumulate as missing attribution until the quarterly audit identifies them.
The Fraud Prevention Framework
Affiliate fraud — fake clicks, fraudulent purchases made by the affiliate using stolen payment credentials, and self-referral (the affiliate purchases through their own link to earn their own commission) — exists in every affiliate programme. The RISER Nation fraud prevention framework is not a paranoid surveillance system; it is a set of reasonable controls that make common fraud patterns unprofitable without creating friction for legitimate affiliates.
The Four Most Common Fraud Patterns and Their Controls
The Programme Audit Protocol
The programme audit is a comprehensive quarterly review of the entire affiliate programme architecture — not just a review of recent sales and commissions. It examines the tracking infrastructure, the commission configuration, the payment records, and the compliance status to identify any systemic issues before they accumulate into programme-level failures.
The Programme Audit Log
The Platform Migration Protocol
Migrating an affiliate programme from one platform to another is one of the highest-risk operational events in the programme's lifecycle. Done incorrectly, migration produces broken links, lost commission records, confused affiliates, and attribution failures that take months to untangle. The migration protocol is the systematic process that makes migration reliable.
Airtable Schema — Affiliate Architecture Database
Table 1 — Commission Records
Table 2 — Bonus Records
Table 3 — Programme Audit Log
Master Affiliate Program Architecture Checklist
Platform Selection and Initial Setup
☐ Platform selected using the six evaluation criteria — all minimum standards confirmed
☐ Platform account created under the operator's business entity
☐ Commission tiers and rates configured in the platform for all offers in the programme
☐ Cookie duration set to 30 days. Attribution model set to Last Click
☐ Minimum payout threshold set to $50. Monthly payment schedule configured
Tracking Infrastructure Build (Phase 1)
☐ Payment processor API integration confirmed — status shows Active in both platforms
☐ Conversion event configured on the payment confirmation (not the checkout initiation)
☐ Test transaction completed through a test affiliate link — commission appeared in the dashboard at the correct amount
☐ CRM UTM integration confirmed — the test purchase appears in the CRM with the affiliate's UTM tag
☐ Cross-device tracking test completed — API-based attribution confirmed for mobile-click/desktop-purchase journey
Commission Engine (Phase 2)
☐ All commission rules configured and documented: standard percentage, recurring, refund handling, coupon interactions
☐ Bonus commission framework documented in Airtable — first sale, volume milestone, launch leaderboard, and recruit bonus criteria all defined
☐ Self-referral prevention enabled or equivalent manual control configured
Payment System (Phase 3)
☐ Monthly payment protocol calendar events created — recurring on the agreed dates
☐ Commission statement template created — all required fields present (clicks, conversions, gross commission, deductions, bonuses, net payment)
☐ Payment method confirmed for each active affiliate — collected during onboarding
☐ Tax documentation collection process in place for US affiliates exceeding $600/year
Affiliate Portal (Phase 4)
☐ Portal dashboard confirmed: clicks, conversions, pending balance, lifetime earnings, payment history all visible on login
☐ My Links section: one-click link copy, sub-ID creator, link testing instructions
☐ Asset Library populated with all promotional materials — dated and organised by format
☐ Offer Details page accurate and current for all commissionable offers
☐ Support contact path confirmed — response time stated
Quarterly Audit Schedule
☐ Quarterly audit calendar events created — Link Audit, Compliance Spot-Check, Cross-Device Test, Platform Health
☐ Monthly commission audit events created — aligned with the payment cycle
☐ Monthly fraud indicator review scheduled — click-to-conversion ratio, self-referral check
☐ Monthly data backup event created — affiliate records, commission records, payment records
RISER Nation Master Operating System | Affiliate Program Architecture SOP | Version 1.0 | 2026 Edition
RISER Nation | risernation.com
The Two Non-Negotiable Architecture Standards
Every affiliate programme architecture in the RISER Nation system must meet two non-negotiable standards before any affiliate link is issued. Standard 1 — Verified Tracking: a complete test transaction has been completed through a real affiliate link, the commission has appeared in the affiliate dashboard at the correct amount, and the attribution has been verified in both the affiliate platform's records and the operator's CRM records simultaneously. Standard 2 — Independent Commission Records: the operator maintains their own independent record of each affiliate's attributed sales and earned commissions — not relying solely on the affiliate platform's reporting. The independent record is the operator's source of truth in any dispute.
The Architecture Debt Problem
Many affiliate programmes are built quickly for a specific launch and never properly architected. The result is a programme that works adequately at 5 affiliates and collapses at 50 — because the tracking is unreliable at volume, the commission calculations are done manually in a spreadsheet, the payment workflow requires 3 hours of manual work per payment cycle, and the affiliate portal is a shared Google Drive folder with no access control. Architecture debt in affiliate programmes accumulates silently until the programme reaches a scale at which the manual processes become unmanageable. This SOP builds the architecture to handle 200 affiliates from day one — so the programme never needs to be rebuilt.
Evaluation Criterion
Minimum Acceptable Standard
Why It Is Non-Negotiable
Native integration with the operator's payment and course platform
The affiliate platform must integrate natively (via API or direct integration, not a third-party connector) with the operator's payment processor (Stripe, ThriveCart, SamCart, or equivalent) so that conversions are tracked automatically from the payment processor's confirmed purchase events — not from a pixel-based or cookie-based inference.
Pixel-based conversion tracking misses purchases where the buyer's browser has cookies disabled, ad-blocking enabled, or cross-device purchasing (they clicked on mobile, purchased on desktop). In 2026, pixel-based affiliate tracking misses 15–35% of actual attributed conversions. This means affiliates are systematically under-compensated, which destroys the relationship and makes the commission statement unreliable.
Real-time affiliate-facing dashboard
The affiliate can log in at any time and see their click count, conversion count, current commission balance, and payment history in real time — without requesting a report from the operator.
An affiliate programme without a self-service dashboard requires the operator to respond to commission status requests manually. At 30+ active affiliates, this is 10+ hours per month of unnecessary manual work. More importantly: affiliates who cannot self-verify their performance have no objective basis for trusting the commission statements they receive.
Unique affiliate link generation with custom sub-IDs
The platform generates a unique link per affiliate (minimum) and supports sub-IDs (optional parameters appended to the link) that allow the affiliate to track which specific promotion (which email, which social post, which podcast episode) drove each conversion.
Sub-IDs allow both the operator and the affiliate to analyse which promotional formats produce the best conversion rates for this specific offer. Affiliates who can see that their email broadcasts convert 3× better than their social posts will focus their effort on email — producing better results for both parties.
Automated recurring commission support
For continuity and subscription offers: the platform automatically calculates and records commissions on each recurring billing cycle — not just the initial purchase.
Manual calculation of recurring commissions for subscription products at scale is operationally unsustainable. At 100 active affiliates each referring 2 subscription buyers who renew monthly: that is 200 monthly commission calculations per payment cycle if done manually. The platform must handle this automatically.
Flexible commission rules by offer, tier, and time period
The platform allows different commission rates for different offers, different affiliates (or affiliate tiers), and different time periods (a higher rate during a live launch vs standard rate for evergreen promotions).
A single-rate system forces the operator to either pay the same rate for launch promotions and evergreen promotions (under-incentivising launch effort) or to not use the platform for one of the two use cases (increasing complexity by managing two systems).
Commission adjustment and override capability
The operator can manually adjust, void, or add commissions in specific circumstances: a conversion that was not auto-tracked due to a technical issue, a reversal due to fraud, or a bonus commission for a top performer.
Every affiliate programme has edge cases that the automated system cannot handle correctly. Without manual adjustment capability, the operator is forced to either ignore legitimate attribution errors or manage compensations outside the platform — both of which create tracking record inconsistencies.
Platform
Best For
Primary Integration
Commission Models Supported
Affiliate Dashboard
Recurring Commission Support
Monthly Cost (approx.)
ThriveCart (native affiliate module)
Operators who use ThriveCart as their cart/checkout. The affiliate module is built in — no additional platform needed.
Native to ThriveCart checkout. Zero integration work if already using ThriveCart.
Flat fee, percentage, tiered, split commissions. Multiple rates per product.
Full self-service dashboard included.
Yes — automatically calculates on each billing cycle.
Included in ThriveCart licence ($495–$690 one-time)
PartnerStack
Knowledge businesses running above $15,000/month in affiliate-driven revenue. Best enterprise-grade system.
Stripe, Braintree, Chargebee, custom API.
Percentage, flat fee, milestone bonuses, tiered by performance.
Full self-service with analytics.
Yes — robust recurring commission engine.
$500–$2,000+/month depending on volume.
Impact (formerly Impact Radius)
Larger operators with multiple affiliate types (standard affiliates, agencies, influencers).
Stripe, PayPal, custom API, most major platforms.
Highly flexible — percentage, CPA, CPL, tiered, hybrid.
Full self-service with deep analytics.
Yes.
$500–$3,000+/month
Rewardful
Operators using Stripe who want a simple, clean affiliate system with minimal setup.
Native Stripe integration — automatically tracks all Stripe payments.
Percentage, flat fee, recurring percentage.
Clean self-service dashboard.
Yes — Stripe subscription-native.
$49–$299/month depending on revenue tracked.
FirstPromoter
SaaS-oriented but works well for knowledge businesses using Stripe. Simple setup, good affiliate dashboard.
Stripe, Paddle, Braintree, Recurly.
Percentage, flat fee, tiered, recurring.
Full self-service.
Yes.
$49–$149/month.
PHASE 1
The Tracking Infrastructure Build
The step-by-step technical setup that makes attribution reliable
TRACKING INFRASTRUCTURE SETUP — In sequence
STEP 1 — PLATFORM ACCOUNT CREATION AND CONFIGURATION
Create the affiliate platform account under the operator's business entity — not a personal account.
Configure the programme name, logo, and default commission rate.
Set the programme's public application URL (this is the URL provided to affiliates when inviting them to apply).
Configure the cookie duration: 30 days as the standard setting.
Configure the attribution model: Last Click (standard).
Set the minimum payout threshold: $50.
Configure the payment schedule: monthly, on the [15th] of each month for commissions earned in the prior month.

STEP 2 — PAYMENT PROCESSOR INTEGRATION
Connect the affiliate platform to the primary payment processor (Stripe, ThriveCart, or equivalent).
The integration method must be API-based — not pixel-based.
After connecting: confirm that the integration status shows 'Active' or 'Connected' in both the affiliate platform's dashboard and the payment processor's app integrations.
// Critical: an integration that shows 'connected' in one platform but not the other is not functioning — both must confirm the connection.

STEP 3 — OFFER CONFIGURATION
For each offer in the affiliate programme, create an offer record in the affiliate platform:
Offer name: [Exact product name as it appears on the sales page]
Commission rate: [Percentage or flat fee for this specific offer]
Commission type: [On first payment only / On all recurring payments]
Cookie applies to: [This specific offer / All offers in the programme]
Configure the commission rate override if the JV launch commission differs from the standard rate.
Exclude any offers that are not in the affiliate programme: premium offers with phone close, SLO (if the SLO is not part of the affiliate programme), and any internal offers.

STEP 4 — CONVERSION EVENT CONFIGURATION
Configure the purchase confirmation event:
The purchase confirmation event fires when a confirmed, paid transaction is completed.
It must NOT fire on: page views of the sales page, initiated checkouts, failed payment attempts.
For ThriveCart: the confirmation event fires on the order confirmation page — confirm the integration is mapping to confirmed orders, not initiated checkouts.
For Stripe: configure the webhook to fire on payment_intent.succeeded — not on payment_intent.created.
// Common error: configuring the event on checkout_session.created rather than payment_intent.succeeded results in commissions being attributed to incomplete checkouts that never convert. This inflates apparent affiliate performance while under-paying for genuine conversions.

STEP 5 — TEST TRANSACTION VERIFICATION
Create a test affiliate account using the operator's own email address at a secondary email domain (not the primary business email).
Generate a test affiliate link from the test account.
Complete a test purchase (use a $0 test coupon or a platform test mode) through the test affiliate link.
Verify the following sequence:
[ ] Click registered in the affiliate platform's click tracking
[ ] Conversion registered in the affiliate platform's conversion tracking within 5 minutes of the purchase
[ ] Commission calculated at the correct amount for the purchased offer
[ ] Commission appeared in the test affiliate's dashboard
[ ] Purchase event registered in the CRM with the affiliate's UTM tag attached to the subscriber record

STEP 6 — CROSS-DEVICE TRACKING VERIFICATION
// Many affiliate purchases involve cross-device journeys: the buyer clicks the affiliate link on mobile but completes the purchase on desktop. Cookie-based tracking fails for cross-device journeys; API-based tracking handles this correctly.
Test: click the affiliate link on a mobile browser. Do NOT complete the purchase. Switch to a desktop browser. Complete the purchase without clicking the affiliate link again.
Expected result for API-based tracking: the commission IS attributed to the affiliate (because the purchase is matched by customer identity, not by cookie).
Expected result for cookie-based tracking: the commission is NOT attributed (the cookie does not transfer between devices).
// If the result shows no attribution on the cross-device test and the platform is supposed to be API-based: the integration is not configured correctly. Contact the platform's support with the test transaction details before issuing any real affiliate links.
Integration Point
How It Works
What It Enables
Affiliate link UTM parameters
Each affiliate's unique link is appended with UTM parameters that the operator's standard convention covers: utm_source=[affiliate_id], utm_medium=affiliate, utm_campaign=[programme_name] or [launch_name_if_jv]. The affiliate platform generates the base unique link; the UTM parameters are appended by the operator before issuing the link to the affiliate.
Any subscriber who opts in through an affiliate link is tagged in the CRM with utm_medium=affiliate. This allows the Content-to-Revenue Attribution SOP's monthly report to isolate affiliate-attributed revenue independently of the affiliate platform's own reporting.
CRM subscriber tagging
When a subscriber opts in through an affiliate link, the CRM captures the UTM parameters and stores them against the subscriber's contact record. The UTM source field (affiliate's ID) is stored permanently — even if the subscriber later returns via a different channel.
First-touch affiliate attribution in the CRM. The affiliate who originally introduced a subscriber to the programme receives credit in the CRM's attribution records, regardless of how many touchpoints the subscriber had before purchasing.
Purchase event dual-recording
When a purchase is made through an affiliate link: the affiliate platform records the commission event, AND the CRM records the purchase with the affiliate's UTM source attached to the buyer's contact record.
Independent verification of each commission event. If a dispute arises, the operator can verify the affiliate platform's commission record against the CRM's purchase record with matching affiliate UTM data.
PHASE 2
The Commission Engine Configuration
The rules that govern how commissions are calculated, credited, and adjusted
Commission Rule
Configuration Standard
Edge Case Handling
Standard percentage commission
Set as a percentage of the net transaction amount — after payment processing fees are deducted, before any platform or fulfilment costs are deducted.
Multiple products in a single transaction: commission applies to the total transaction net amount unless specific product exclusions have been configured. Configure exclusions for any products not in the affiliate programme.
Flat fee commission
Set as an absolute dollar amount per transaction — regardless of any discount codes or price variations applied at checkout.
If the offer has multiple pricing tiers (monthly vs annual): configure separate flat fees for each tier. A monthly subscription at $97/month and an annual at $797/year should have separate commission rates, not the same flat fee.
Recurring commission
Set to fire on every successful recurring billing event — not just the initial purchase. The recurring commission rate may be the same as or lower than the initial purchase rate.
Failed recurring payments: commission is NOT credited on failed charges. Only successful renewal charges trigger commission. Configure this explicitly — some platforms default to crediting on the billing attempt rather than the successful charge.
Refund handling
Commission status changes to 'Reversed' when a refund is processed within the refund window. If commission has already been paid before the refund occurs: the reversal creates a negative balance against the affiliate's next commission payment.
Partial refunds: commission is adjusted proportionally (not entirely reversed). Full refunds: commission fully reversed. Configure the platform to handle both partial and full refund scenarios.
Coupon code interactions
If the buyer used a discount code: commission applies to the discounted transaction price, not the full price. Internal coupon codes (used for bonuses or affiliate exclusives) should not reduce commission.
Internal affiliate bonus codes: configure specific coupon codes as 'commission-protected' so that the discount does not reduce the commission calculation. Example: a $100-off code offered as a bonus should not reduce the affiliate's commission.
Split commissions (if applicable)
If the affiliate programme uses a two-tier structure (an affiliate who recruited another affiliate earns a percentage of their recruit's commissions): configure the split percentage and ensure it applies correctly to the downstream affiliate's earnings without affecting the downstream affiliate's stated commission rate.
Two-tier split: the upstream affiliate's split commission is calculated from a pool separate from the downstream affiliate's commission — not subtracted from what the downstream affiliate earns.
Bonus Type
Trigger Condition
Amount
Payment Timing
How to Configure
First Sale Bonus
The affiliate's first confirmed sale within 30 days of being approved.
$25–$50 flat bonus — a meaningful acknowledgement of the first promotional effort.
Added to the affiliate's next monthly commission payment.
Manual tracking in Airtable (Bonus Records table) — most platforms do not auto-trigger first-sale bonuses. Set a reminder to check new affiliates' status at Day 30 post-approval.
Volume Milestone Bonus
Reaching 5, 10, 20 sales within a calendar month.
Escalating flat bonus: $50 at 5 sales, $150 at 10 sales, $500 at 20 sales.
Same-month payment with the regular commission cycle.
Configurable in PartnerStack and Impact. Manual in most other platforms — set a monthly calendar reminder to review affiliate volumes and calculate milestone bonuses before the payment run.
Launch Leaderboard Bonus
Finishing in the top 3 of a JV launch leaderboard.
1st place: $500–$2,000+. 2nd place: $250–$1,000. 3rd place: $100–$500. Scale with launch size.
Within 10 business days of launch close.
Manual calculation and payment — launch leaderboard bonuses are a one-off event tied to a specific launch, not a recurring commission structure.
Recruit Bonus
Recruiting a new affiliate to the programme who makes their first sale within 60 days.
$25–$100 flat bonus.
Added to the next monthly commission cycle after the recruited affiliate's first sale confirmation.
Manual in most platforms — requires tracking in the Partner Records Airtable table (Recruited By field).
PHASE 3
The Payment System — Commission Payment Workflows
5B21B6
MONTHLY COMMISSION PAYMENT PROTOCOL — Execute on the [12th] of each month
DAY 1 OF PAYMENT CYCLE (the [1st] of each month, or the Monday nearest to the 1st)
STEP 1 — PULL THE COMMISSION REPORT
Export the prior month's commission report from the affiliate platform:
— Filter: commissions with status = 'Approved' (conversions confirmed, refund window closed)
— Exclude: commissions with status = 'Reversed' (refunded), 'Held' (within refund window), or 'Void'
— Result: the list of affiliates with payable commission balances for this payment cycle

STEP 2 — INDEPENDENT VERIFICATION
Cross-reference the affiliate platform's commission report against the CRM's purchase records:
— For each commission in the report: confirm a matching purchase event exists in the CRM with the affiliate's UTM tag
— Flag any commission where no matching CRM purchase record exists (potential tracking error or fraud)
— Flag any CRM purchase record with an affiliate UTM tag that does NOT appear in the commission report (potential missed attribution)

STEP 3 — APPLY REFUND ADJUSTMENTS
For any commission that was paid in a prior month but has since been reversed due to a refund:
Deduct the reversed amount from the current month's payment
Document the deduction in the commission statement sent to the affiliate

STEP 4 — APPLY BONUS COMMISSIONS
Add any earned bonus commissions (first sale, volume milestone, launch leaderboard) to the payment total for qualifying affiliates
Document each bonus in the Bonus Records table

STEP 5 — APPLY MINIMUM PAYOUT THRESHOLD
Remove any affiliate whose current balance is below the minimum threshold ($50)
Their balance rolls to the next payment cycle — add a note in their Airtable Partner Record

DAY 2 OF PAYMENT CYCLE (the day after the report is verified)
STEP 6 — COMMISSION STATEMENTS TO AFFILIATES
Before payment is made: send each affiliate their commission statement for the payment cycle.
The statement includes:
— Total clicks for the period
— Total confirmed sales for the period
— Total commission amount (gross)
— Any deductions (refund reversals)
— Any bonuses
— Net payment amount
— Expected payment date (3 business days from statement date)

STEP 7 — 24-HOUR REVIEW PERIOD
Allow 24 hours for affiliates to review their statement and raise any discrepancies before payment is made.
Any dispute received within 24 hours is investigated before payment proceeds (see Dispute Resolution Protocol).

DAY 3 OF PAYMENT CYCLE
STEP 8 — EXECUTE PAYMENT
Process payments through the agreed payment method for each affiliate:
PayPal: send via PayPal mass pay or individual payments to each affiliate's registered PayPal email
Wise: bulk transfer to international affiliates
ACH: US-based affiliates with confirmed bank details
Other: per the individual affiliate's registered payment method

STEP 9 — PAYMENT CONFIRMATION
For each payment processed: record the transaction ID and the payment date in the Partner Records table.
Send a payment confirmation notification to each affiliate.

STEP 10 — TAX DOCUMENTATION
For US-based affiliates earning above $600 in the calendar year: collect the required tax documentation (W-9 for US individuals, W-8BEN for international).
Issue 1099 forms to qualifying US affiliates by January 31 of the following year.
For non-US affiliates: confirm the withholding requirements for their jurisdiction.
Dispute Type
Most Common Cause
Investigation Steps
Resolution Timeline
Resolution Standard
Missing commission — affiliate tracked a click but no commission appeared
Cross-device purchase (mobile click, desktop purchase) with cookie-only tracking; buyer cleared cookies before purchase; buyer used a different browser; tracking gap on the confirmation page.
1. Check the CRM for a purchase record with the affiliate's UTM tag. 2. Check the affiliate platform's click log for the affiliate's link click. 3. Check the payment processor's transaction records. 4. If the purchase event and the click event exist in the same 30-day window: the attribution is confirmed and the commission should be added manually.
48 hours from dispute received.
If the CRM confirms attribution (the buyer's UTM tag matches the affiliate): add the commission manually and document the cause. If the CRM does not confirm attribution: the dispute is not substantiated — respond with the specific data points that indicate the sale was not attributable.
Incorrect commission amount
The affiliate was paid at a different rate than expected, typically because a discount code reduced the commission base or a new product tier was not correctly configured.
1. Confirm the offer price at the time of the transaction (was a discount code applied?). 2. Confirm the commission rate configured for this offer and this affiliate's tier. 3. Calculate the correct commission amount from these two inputs.
24 hours.
If the commission was calculated correctly per the documented rules: explain the calculation with the specific transaction details. If the commission was calculated incorrectly due to a system misconfiguration: pay the difference in the next payment cycle and correct the configuration.
Commission reversed for a refund the affiliate disputes
The affiliate believes the refund was issued in error or they were not notified.
1. Confirm the refund in the payment processor's records. 2. Confirm the refund fell within the offer's refund policy window. 3. If the refund is confirmed and within policy: the reversal is correct.
48 hours.
If the refund is confirmed: explain the refund policy and confirm the reversal is correct. If the refund appears to be an error (the buyer was refunded when they should not have been): investigate the refund source and correct it if appropriate.
Sub-ID click not attributed to main link
The affiliate used a sub-ID variant of their link and the conversion is not appearing in their dashboard.
1. Check whether the sub-ID is correctly configured in the platform. 2. Check whether the sub-ID link was correctly formatted.
24 hours.
If the sub-ID link was correctly formatted and the conversion occurred within the cookie window: the commission should appear — investigate the platform configuration. If the sub-ID link was incorrectly formatted: explain the correct format and add the commission manually for this specific transaction.
PHASE 4
The Affiliate Portal — The Affiliate's Experience of the Programme
B45309
Portal Section
Content Required
Design Principle
What Affiliates Do Without This
Dashboard (home page)
At-a-glance performance summary: clicks this month, conversions this month, pending commission balance, lifetime commission earned, payment history. A banner showing the next upcoming launch date (if applicable).
All numbers visible without a single click. The dashboard answers the three questions an affiliate asks when they log in: 'How am I doing this month? What do I owe? When is my next payment?'
Log in, see nothing useful, leave without promoting. Affiliates who cannot quickly assess their performance status do not stay engaged with the programme.
My Links
The affiliate's primary affiliate link (and any sub-ID links they have created). A simple sub-ID creator tool. A one-click link copy function.
The link section must be reachable in one click from the dashboard. A two-click path to the affiliate link is acceptable. A three-click path is not.
Affiliates who cannot find their link quickly either use outdated links from prior promotions or ask the operator for their link — wasting both parties' time.
Assets Library
All promotional materials organised by category: email templates, social posts, podcast scripts, banner images, case study one-pagers. Each asset is downloadable or copyable with a single action. Assets are dated — affiliates can see which version is current.
Assets are organised by format, not by date. The most recent version of each asset type is the default display. Older versions are archived, not deleted — some affiliates may be mid-promotion with an older asset.
Affiliates produce their own copy without guidance. This increases compliance risk and typically produces lower-converting promotional content.
Offer Details
Complete offer information for each commissionable offer: name, price, sales page URL, commission rate and amount, refund policy, and a 2–3 sentence offer description in plain language.
One page per offer — not a wall of text. The affiliate should be able to understand what they are promoting in 60 seconds.
Affiliates promote the offer with inaccurate or incomplete information. This produces compliance risk and lower conversion rates.
Commission History
A complete record of every commission event: date, attributed sale, offer name, gross commission, any adjustments (refunds), and payment status (pending, paid, reversed).
Each row is expandable — the affiliate can click a commission entry to see the supporting transaction detail (not just the commission amount).
Affiliates who cannot see the detail behind their commission history will dispute more — because opacity generates suspicion.
Leaderboard (for launch events)
During live launch windows: a real-time leaderboard showing the top affiliates by sales volume and commission earned for the current launch.
Only visible during active launch windows. Automatically disappears after the launch closes.
The competitive motivation and social proof of the leaderboard are not available.
Support / Contact
A clear path to contact the affiliate manager or programme support — email, a form, or a Slack/Discord link. The expected response time stated explicitly.
One-click access. Response time stated: 'We respond within 24 hours on business days.'
Affiliates with questions or issues go unanswered. Unanswered affiliates stop promoting.
Situation
Standard Procedure
What Could Go Wrong Without This Procedure
New affiliate approved
Generate the affiliate's unique link in the platform. Send the link to the affiliate in their onboarding email. Provide click-tracking instructions so the affiliate can verify their link is working before they promote.
The affiliate uses a manually-typed variation of the link that breaks the tracking parameter. Broken links issued at onboarding are never corrected because neither party tests them.
New offer added to the programme
Generate affiliate links for the new offer for all existing affiliates with the correct commission rate for the new offer. Notify all active affiliates of the new offer link via the programme newsletter.
Existing affiliates promote the new offer using their original link (which may not be configured for the new offer's commission). Commissions are either not tracked or tracked at the wrong rate.
JV launch begins
Issue launch-specific links for all JV partners with the correct launch commission rate. Send the link to each partner in the JV Partner Brief. Confirm receipt and provide testing instructions.
JV partners use their standard affiliate link, which tracks at the standard rate rather than the launch rate. Partners are under-compensated for their launch promotion effort.
Affiliate suspects a broken link
Provide the affiliate with a link testing protocol: click the link, check that the referral ID appears in the URL of the sales page (confirm the parameter passed correctly), complete a test with a $0 coupon if available.
Affiliate does not know how to verify the link. They assume it is working when it is not. Promotions are sent, buyers arrive, purchases are made, and zero commissions are attributed.
QUARTERLY LINK AUDIT PROTOCOL
STEP 1 — EXPORT ALL ACTIVE AFFILIATE LINKS
Export a list of all active affiliates and their current link IDs from the affiliate platform.
Include: Affiliate ID, Affiliate Name, Link URL, Offer the link is configured for, Commission Rate configured.

STEP 2 — LINK VALIDITY CHECK
For each active affiliate link: perform an automated or manual click-through test.
Automated: use a URL monitoring tool (UptimeRobot, Statuspage, or similar) to test all links for 200/redirect responses.
Manual: click each link and confirm it redirects to the correct sales page with the affiliate's tracking parameter visible in the URL.
Red flag: any link that returns a 404 (broken), a 302 redirect to the wrong page, or a sales page URL without the tracking parameter.

STEP 3 — COMMISSION RATE VERIFICATION
For each active affiliate: confirm the commission rate configured in the platform matches their documented tier in the Partner Records Airtable table.
Red flag: any affiliate whose platform commission rate does not match their documented tier.

STEP 4 — CROSS-DEVICE TRACKING TEST
Complete one test transaction per offer (using a test coupon or test mode) via a mobile click → desktop purchase path.
Expected result: the commission is attributed correctly (API-based tracking only — cookie-based tracking will fail this test).
If cross-device attribution fails: investigate the API integration configuration.

STEP 5 — AUDIT RESOLUTION
For any issue found in steps 1–4: resolve within 7 days of the audit.
Document the issue, the resolution, and the date of resolution in the Programme Audit Log.
For any affiliate whose link was broken: check whether any sales may have been missed during the period the link was broken. If missed sales are identified: add manual commissions with an explanation.
Fraud Pattern
How It Works
Harm It Produces
Prevention Control
Self-Referral
The affiliate uses their own affiliate link to purchase the offer, earning a commission on their own purchase. They effectively buy the product at [price × (1 − commission rate)] rather than at the full price.
Revenue loss: the affiliate who buys a $797 offer through their own 30% link receives $239.10 back as commission — effectively purchasing at $557.90. At volume: significant revenue leakage.
Block self-referral in the affiliate platform (most platforms have a self-referral prevention setting). If the platform does not support this: configure the commission system to exclude purchases where the buyer's email matches the affiliate's registered email.
Fake Traffic / Click Inflation
The affiliate inflates their click count using bots, auto-clickers, or purchased clicks to appear to be driving more traffic than they are — creating a false high-click, low-conversion rate appearance.
No direct financial harm (commissions require conversions). Indirect harm: the operator may believe a high-traffic affiliate is underperforming their promotional potential and invest relationship resources in activating a partner who is not actually promoting genuinely.
Monitor the click-to-conversion ratio. A legitimate affiliate should produce a conversion rate of 0.5–5% of clicks. A click-to-conversion rate below 0.1% consistently over 30 days is a fraud signal. Flag for investigation.
Chargeback Fraud (Friendly Fraud)
A buyer (sometimes coordinated with the affiliate) purchases through the affiliate link and then initiates a chargeback — the commission is paid to the affiliate before the chargeback clears, and the operator loses both the sale price and the commission.
Revenue loss equal to the purchase price plus the commission plus the chargeback fee. The affiliate receives the commission; the operator loses the full purchase amount plus fees.
Implement a mandatory hold period: commissions are not paid until after the chargeback window has closed (typically 60–90 days for credit card chargebacks, though the platform's standard refund window of 30 days catches most cases). Do not pay commissions on sales with high fraud risk indicators (mismatched billing addresses, VPN-origin purchases, rapid multiple purchases by the same affiliate's referrals).
Cookie Stuffing
The affiliate places their affiliate tracking cookie on a visitor's browser without the visitor clicking an affiliate link — through hidden pixels, iframes, or other automated methods. Every subsequent purchase by that visitor is attributed to the affiliate.
Revenue loss: the affiliate earns commissions on purchases they did not genuinely influence.
Use API-based tracking rather than cookie-only tracking. API-based tracking requires a genuine click of the affiliate link to establish the relationship — it cannot be manufactured by cookie stuffing. Audit affiliates with unusually high click-to-conversion rates (above 10%) — these may indicate cookie stuffing.
Audit Area
Audit Frequency
What Is Checked
Expected Completion Time
Tracking Infrastructure
Quarterly
Link validity for all active affiliates. Commission rate accuracy for all affiliate tiers. Cross-device tracking test. Conversion event firing confirmation.
3–4 hours for a programme with up to 50 active affiliates.
Commission Records
Monthly (at each payment cycle)
Independent verification of commission statements against CRM purchase records. Refund reversal accuracy. Bonus commission application. Minimum threshold roll-overs.
2–3 hours per monthly payment cycle.
Partner Compliance
Quarterly
FTC disclosure compliance review: spot-check 10–15 recent promotional pieces from active affiliates for compliance with disclosure requirements. Any non-compliant promotional content identified: immediate notification to the affiliate.
2 hours for a spot-check of 10–15 promotions.
Fraud Indicators
Monthly
Click-to-conversion ratio review for all active affiliates. Any affiliate with below 0.1% conversion rate over 30 days flagged for investigation. Self-referral check. Chargeback rate review.
1 hour monthly.
Data Backup
Monthly
Export of all affiliate records, commission records, and payment records from the affiliate platform. Store in a secure, independent location (not on the same platform).
30 minutes.
Platform Health
Quarterly
Platform subscription and billing confirmed active. API integration status confirmed. Any platform feature changes that affect the programme's configuration reviewed and adapted.
1 hour.
QUARTERLY PROGRAMME AUDIT LOG — Maintained in Airtable
AUDIT IDENTIFICATION
Audit ID: [AUDIT-[YYYY-Q#]. e.g. AUDIT-2026-Q3]
Audit Date: [ ]
Conducted By: [ ]

TRACKING INFRASTRUCTURE
Total active affiliate links audited: [ ]
Links with issues found: [ ]
Issues: [ ]
Resolution date: [ ]

Commission rate mismatches found: [ ]
Resolution: [ ]

Cross-device tracking test result: [ ] Pass [ ] Fail — issue: [ ]

COMPLIANCE SPOT-CHECK
Promotional pieces reviewed: [ ] from [ ] affiliates
Non-compliant pieces found: [ ]
Affiliates notified: [ ]
Resolution: [ ]

FRAUD INDICATORS
Affiliates with below 0.1% conversion rate (30-day): [ ]
Investigations opened: [ ]
Resolutions: [ ]

COMMISSION AND PAYMENT RECORDS
Total commissions paid in the quarter: $[ ]
Total affiliates paid: [ ]
Commission disputes received in the quarter: [ ]
Disputes resolved: [ ]
Open disputes: [ ]

DATA BACKUP
Affiliate records exported and stored: [ ] Yes [ ] No
Commission records exported: [ ] Yes [ ] No
Payment records exported: [ ] Yes [ ] No
Storage location: [ ]

ACTION ITEMS
Priority action 1: [ ] — Owner: [ ] — Due: [ ]
Priority action 2: [ ] — Owner: [ ] — Due: [ ]
Migration Step
Action Required
Timeline
Who Is Responsible
1 — Migration Decision
Document the specific reasons for migration: the current platform's failure to meet the non-negotiable standards, the new platform's demonstrated ability to meet those standards, and the cost-benefit analysis of migration overhead vs ongoing platform inadequacy.
Complete before any migration action
Founder
2 — New Platform Setup and Testing
Set up the complete affiliate programme architecture on the new platform using this SOP's Phase 1 and Phase 2 protocols. Complete the full test transaction verification sequence on the new platform before any data is migrated.
6–8 weeks before the planned migration date
Operator + new platform's technical support
3 — Partner Communication
Notify all active affiliates 4 weeks before the migration date: 'We are upgrading our affiliate infrastructure on [date]. Your new login credentials and links will be provided on [date]. Your commission records will be preserved in full.'
4 weeks before migration
Affiliate Manager
4 — Historical Data Export
Export a complete record of all affiliate data from the current platform: partner records, commission history, payment records. Store in the Programme Audit database as a permanent archive.
2 weeks before migration
Operator
5 — Commission Reconciliation
Complete a final commission payment cycle on the current platform for all commissions earned before the migration date. No commissions should be owed on the current platform at the point of migration.
1 week before migration
Operator
6 — New Credentials and Links Issued
Issue each affiliate their new platform login and their new unique affiliate link. Provide a clear, brief guide on the differences between the old and new interface.
On migration date
Affiliate Manager
7 — Old Platform Decommission
After 90 days of confirmed successful operation on the new platform: deactivate the old platform's affiliate links and close the account (or move it to archive mode if records must be preserved).
90 days after migration
Operator
Field
Type
Notes
Commission ID
Short text
Format: COMM-[Partner ID]-[YYYY-MM]-[Seq]. e.g. COMM-PART-AFF-042-2026-09-003
Partner
Link → Partner Records (from Partnerships SOP)
Transaction Date
Date
The date the purchase was confirmed
Offer Name
Short text
Transaction Amount (net)
Currency
After payment processing fees
Commission Rate
Number
% applied to this transaction
Commission Amount (gross)
Formula
Transaction Amount × Commission Rate ÷ 100
Status
Single select
Pending (in refund window) / Approved (payable) / Paid / Reversed (refunded) / Void (fraud or error) / Disputed
Payment Cycle
Short text
Which monthly payment cycle this commission belongs to (e.g. '2026-09')
CRM Verification
Checkbox
Has this commission been verified against the CRM purchase record?
CRM Purchase Record ID
Short text
The CRM contact record ID of the buyer for cross-reference
Sub-ID (if applicable)
Short text
The sub-ID parameter used in the affiliate link that generated this commission
Bonus Commission
Currency
Any bonus amount added to this commission cycle for this partner
Notes
Long text
Reason for any manual adjustments, dispute resolution notes
Field
Type
Notes
Bonus ID
Short text
Format: BONUS-[Partner ID]-[YYYY-MM]
Partner
Link → Partner Records
Bonus Type
Single select
First Sale / Volume Milestone (5/10/20) / Launch Leaderboard (1st/2nd/3rd) / Recruit Bonus / Other
Trigger Description
Short text
What specifically triggered the bonus
Bonus Amount
Currency
Added to Payment Cycle
Short text
Which monthly payment cycle this bonus was added to
Paid
Checkbox
Notes
Long text
Field
Type
Notes
Audit ID
Short text
Format: AUDIT-[YYYY-Q#]
Audit Date
Date
Conducted By
Short text
Audit Type
Single select
Quarterly Full Audit / Monthly Commission Audit / Ad Hoc (triggered by issue)
Links Audited — Count
Number
Links With Issues
Number
Commission Mismatches Found
Number
Compliance Issues Found
Number
Fraud Indicators Found
Number
Data Backup Completed
Checkbox
All Issues Resolved
Checkbox
Open Items
Long text
Description of any unresolved audit findings
Notes
Long text

Original Word tables and field relationships

Source table 1

The Two Non-Negotiable Architecture StandardsEvery affiliate programme architecture in the RISER Nation system must meet two non-negotiable standards before any affiliate link is issued. Standard 1 — Verified Tracking: a complete test transaction has been completed through a real affiliate link, the commission has appeared in the affiliate dashboard at the correct amount, and the attribution has been verified in both the affiliate platform's records and the operator's CRM records simultaneously. Standard 2 — Independent Commission Records: the operator maintains their own independent record of each affiliate's attributed sales and earned commissions — not relying solely on the affiliate platform's reporting. The independent record is the operator's source of truth in any dispute.

Source table 2

The Architecture Debt ProblemMany affiliate programmes are built quickly for a specific launch and never properly architected. The result is a programme that works adequately at 5 affiliates and collapses at 50 — because the tracking is unreliable at volume, the commission calculations are done manually in a spreadsheet, the payment workflow requires 3 hours of manual work per payment cycle, and the affiliate portal is a shared Google Drive folder with no access control. Architecture debt in affiliate programmes accumulates silently until the programme reaches a scale at which the manual processes become unmanageable. This SOP builds the architecture to handle 200 affiliates from day one — so the programme never needs to be rebuilt.

Source table 3

Evaluation Criterion	Minimum Acceptable Standard	Why It Is Non-Negotiable
Native integration with the operator's payment and course platform	The affiliate platform must integrate natively (via API or direct integration, not a third-party connector) with the operator's payment processor (Stripe, ThriveCart, SamCart, or equivalent) so that conversions are tracked automatically from the payment processor's confirmed purchase events — not from a pixel-based or cookie-based inference.	Pixel-based conversion tracking misses purchases where the buyer's browser has cookies disabled, ad-blocking enabled, or cross-device purchasing (they clicked on mobile, purchased on desktop). In 2026, pixel-based affiliate tracking misses 15–35% of actual attributed conversions. This means affiliates are systematically under-compensated, which destroys the relationship and makes the commission statement unreliable.
Real-time affiliate-facing dashboard	The affiliate can log in at any time and see their click count, conversion count, current commission balance, and payment history in real time — without requesting a report from the operator.	An affiliate programme without a self-service dashboard requires the operator to respond to commission status requests manually. At 30+ active affiliates, this is 10+ hours per month of unnecessary manual work. More importantly: affiliates who cannot self-verify their performance have no objective basis for trusting the commission statements they receive.
Unique affiliate link generation with custom sub-IDs	The platform generates a unique link per affiliate (minimum) and supports sub-IDs (optional parameters appended to the link) that allow the affiliate to track which specific promotion (which email, which social post, which podcast episode) drove each conversion.	Sub-IDs allow both the operator and the affiliate to analyse which promotional formats produce the best conversion rates for this specific offer. Affiliates who can see that their email broadcasts convert 3× better than their social posts will focus their effort on email — producing better results for both parties.
Automated recurring commission support	For continuity and subscription offers: the platform automatically calculates and records commissions on each recurring billing cycle — not just the initial purchase.	Manual calculation of recurring commissions for subscription products at scale is operationally unsustainable. At 100 active affiliates each referring 2 subscription buyers who renew monthly: that is 200 monthly commission calculations per payment cycle if done manually. The platform must handle this automatically.
Flexible commission rules by offer, tier, and time period	The platform allows different commission rates for different offers, different affiliates (or affiliate tiers), and different time periods (a higher rate during a live launch vs standard rate for evergreen promotions).	A single-rate system forces the operator to either pay the same rate for launch promotions and evergreen promotions (under-incentivising launch effort) or to not use the platform for one of the two use cases (increasing complexity by managing two systems).
Commission adjustment and override capability	The operator can manually adjust, void, or add commissions in specific circumstances: a conversion that was not auto-tracked due to a technical issue, a reversal due to fraud, or a bonus commission for a top performer.	Every affiliate programme has edge cases that the automated system cannot handle correctly. Without manual adjustment capability, the operator is forced to either ignore legitimate attribution errors or manage compensations outside the platform — both of which create tracking record inconsistencies.

Source table 4

Platform	Best For	Primary Integration	Commission Models Supported	Affiliate Dashboard	Recurring Commission Support	Monthly Cost (approx.)
ThriveCart (native affiliate module)	Operators who use ThriveCart as their cart/checkout. The affiliate module is built in — no additional platform needed.	Native to ThriveCart checkout. Zero integration work if already using ThriveCart.	Flat fee, percentage, tiered, split commissions. Multiple rates per product.	Full self-service dashboard included.	Yes — automatically calculates on each billing cycle.	Included in ThriveCart licence ($495–$690 one-time)
PartnerStack	Knowledge businesses running above $15,000/month in affiliate-driven revenue. Best enterprise-grade system.	Stripe, Braintree, Chargebee, custom API.	Percentage, flat fee, milestone bonuses, tiered by performance.	Full self-service with analytics.	Yes — robust recurring commission engine.	$500–$2,000+/month depending on volume.
Impact (formerly Impact Radius)	Larger operators with multiple affiliate types (standard affiliates, agencies, influencers).	Stripe, PayPal, custom API, most major platforms.	Highly flexible — percentage, CPA, CPL, tiered, hybrid.	Full self-service with deep analytics.	Yes.	$500–$3,000+/month
Rewardful	Operators using Stripe who want a simple, clean affiliate system with minimal setup.	Native Stripe integration — automatically tracks all Stripe payments.	Percentage, flat fee, recurring percentage.	Clean self-service dashboard.	Yes — Stripe subscription-native.	$49–$299/month depending on revenue tracked.
FirstPromoter	SaaS-oriented but works well for knowledge businesses using Stripe. Simple setup, good affiliate dashboard.	Stripe, Paddle, Braintree, Recurly.	Percentage, flat fee, tiered, recurring.	Full self-service.	Yes.	$49–$149/month.

Source table 5

PHASE 1The Tracking Infrastructure BuildThe step-by-step technical setup that makes attribution reliable

Source table 6

TRACKING INFRASTRUCTURE SETUP — In sequenceSTEP 1 — PLATFORM ACCOUNT CREATION AND CONFIGURATIONCreate the affiliate platform account under the operator's business entity — not a personal account.Configure the programme name, logo, and default commission rate.Set the programme's public application URL (this is the URL provided to affiliates when inviting them to apply).Configure the cookie duration: 30 days as the standard setting.Configure the attribution model: Last Click (standard).Set the minimum payout threshold: $50.Configure the payment schedule: monthly, on the [15th] of each month for commissions earned in the prior month.STEP 2 — PAYMENT PROCESSOR INTEGRATIONConnect the affiliate platform to the primary payment processor (Stripe, ThriveCart, or equivalent).The integration method must be API-based — not pixel-based.After connecting: confirm that the integration status shows 'Active' or 'Connected' in both the affiliate platform's dashboard and the payment processor's app integrations.// Critical: an integration that shows 'connected' in one platform but not the other is not functioning — both must confirm the connection.STEP 3 — OFFER CONFIGURATIONFor each offer in the affiliate programme, create an offer record in the affiliate platform: Offer name: [Exact product name as it appears on the sales page] Commission rate: [Percentage or flat fee for this specific offer] Commission type: [On first payment only / On all recurring payments] Cookie applies to: [This specific offer / All offers in the programme]Configure the commission rate override if the JV launch commission differs from the standard rate.Exclude any offers that are not in the affiliate programme: premium offers with phone close, SLO (if the SLO is not part of the affiliate programme), and any internal offers.STEP 4 — CONVERSION EVENT CONFIGURATIONConfigure the purchase confirmation event:The purchase confirmation event fires when a confirmed, paid transaction is completed.It must NOT fire on: page views of the sales page, initiated checkouts, failed payment attempts.For ThriveCart: the confirmation event fires on the order confirmation page — confirm the integration is mapping to confirmed orders, not initiated checkouts.For Stripe: configure the webhook to fire on payment_intent.succeeded — not on payment_intent.created.// Common error: configuring the event on checkout_session.created rather than payment_intent.succeeded results in commissions being attributed to incomplete checkouts that never convert. This inflates apparent affiliate performance while under-paying for genuine conversions.STEP 5 — TEST TRANSACTION VERIFICATIONCreate a test affiliate account using the operator's own email address at a secondary email domain (not the primary business email).Generate a test affiliate link from the test account.Complete a test purchase (use a $0 test coupon or a platform test mode) through the test affiliate link.Verify the following sequence: [ ] Click registered in the affiliate platform's click tracking [ ] Conversion registered in the affiliate platform's conversion tracking within 5 minutes of the purchase [ ] Commission calculated at the correct amount for the purchased offer [ ] Commission appeared in the test affiliate's dashboard [ ] Purchase event registered in the CRM with the affiliate's UTM tag attached to the subscriber recordSTEP 6 — CROSS-DEVICE TRACKING VERIFICATION// Many affiliate purchases involve cross-device journeys: the buyer clicks the affiliate link on mobile but completes the purchase on desktop. Cookie-based tracking fails for cross-device journeys; API-based tracking handles this correctly.Test: click the affiliate link on a mobile browser. Do NOT complete the purchase. Switch to a desktop browser. Complete the purchase without clicking the affiliate link again.Expected result for API-based tracking: the commission IS attributed to the affiliate (because the purchase is matched by customer identity, not by cookie).Expected result for cookie-based tracking: the commission is NOT attributed (the cookie does not transfer between devices).// If the result shows no attribution on the cross-device test and the platform is supposed to be API-based: the integration is not configured correctly. Contact the platform's support with the test transaction details before issuing any real affiliate links.

Source table 7

Integration Point	How It Works	What It Enables
Affiliate link UTM parameters	Each affiliate's unique link is appended with UTM parameters that the operator's standard convention covers: utm_source=[affiliate_id], utm_medium=affiliate, utm_campaign=[programme_name] or [launch_name_if_jv]. The affiliate platform generates the base unique link; the UTM parameters are appended by the operator before issuing the link to the affiliate.	Any subscriber who opts in through an affiliate link is tagged in the CRM with utm_medium=affiliate. This allows the Content-to-Revenue Attribution SOP's monthly report to isolate affiliate-attributed revenue independently of the affiliate platform's own reporting.
CRM subscriber tagging	When a subscriber opts in through an affiliate link, the CRM captures the UTM parameters and stores them against the subscriber's contact record. The UTM source field (affiliate's ID) is stored permanently — even if the subscriber later returns via a different channel.	First-touch affiliate attribution in the CRM. The affiliate who originally introduced a subscriber to the programme receives credit in the CRM's attribution records, regardless of how many touchpoints the subscriber had before purchasing.
Purchase event dual-recording	When a purchase is made through an affiliate link: the affiliate platform records the commission event, AND the CRM records the purchase with the affiliate's UTM source attached to the buyer's contact record.	Independent verification of each commission event. If a dispute arises, the operator can verify the affiliate platform's commission record against the CRM's purchase record with matching affiliate UTM data.

Source table 8

PHASE 2The Commission Engine ConfigurationThe rules that govern how commissions are calculated, credited, and adjusted

Source table 9

Commission Rule	Configuration Standard	Edge Case Handling
Standard percentage commission	Set as a percentage of the net transaction amount — after payment processing fees are deducted, before any platform or fulfilment costs are deducted.	Multiple products in a single transaction: commission applies to the total transaction net amount unless specific product exclusions have been configured. Configure exclusions for any products not in the affiliate programme.
Flat fee commission	Set as an absolute dollar amount per transaction — regardless of any discount codes or price variations applied at checkout.	If the offer has multiple pricing tiers (monthly vs annual): configure separate flat fees for each tier. A monthly subscription at $97/month and an annual at $797/year should have separate commission rates, not the same flat fee.
Recurring commission	Set to fire on every successful recurring billing event — not just the initial purchase. The recurring commission rate may be the same as or lower than the initial purchase rate.	Failed recurring payments: commission is NOT credited on failed charges. Only successful renewal charges trigger commission. Configure this explicitly — some platforms default to crediting on the billing attempt rather than the successful charge.
Refund handling	Commission status changes to 'Reversed' when a refund is processed within the refund window. If commission has already been paid before the refund occurs: the reversal creates a negative balance against the affiliate's next commission payment.	Partial refunds: commission is adjusted proportionally (not entirely reversed). Full refunds: commission fully reversed. Configure the platform to handle both partial and full refund scenarios.
Coupon code interactions	If the buyer used a discount code: commission applies to the discounted transaction price, not the full price. Internal coupon codes (used for bonuses or affiliate exclusives) should not reduce commission.	Internal affiliate bonus codes: configure specific coupon codes as 'commission-protected' so that the discount does not reduce the commission calculation. Example: a $100-off code offered as a bonus should not reduce the affiliate's commission.
Split commissions (if applicable)	If the affiliate programme uses a two-tier structure (an affiliate who recruited another affiliate earns a percentage of their recruit's commissions): configure the split percentage and ensure it applies correctly to the downstream affiliate's earnings without affecting the downstream affiliate's stated commission rate.	Two-tier split: the upstream affiliate's split commission is calculated from a pool separate from the downstream affiliate's commission — not subtracted from what the downstream affiliate earns.

Source table 10

Bonus Type	Trigger Condition	Amount	Payment Timing	How to Configure
First Sale Bonus	The affiliate's first confirmed sale within 30 days of being approved.	$25–$50 flat bonus — a meaningful acknowledgement of the first promotional effort.	Added to the affiliate's next monthly commission payment.	Manual tracking in Airtable (Bonus Records table) — most platforms do not auto-trigger first-sale bonuses. Set a reminder to check new affiliates' status at Day 30 post-approval.
Volume Milestone Bonus	Reaching 5, 10, 20 sales within a calendar month.	Escalating flat bonus: $50 at 5 sales, $150 at 10 sales, $500 at 20 sales.	Same-month payment with the regular commission cycle.	Configurable in PartnerStack and Impact. Manual in most other platforms — set a monthly calendar reminder to review affiliate volumes and calculate milestone bonuses before the payment run.
Launch Leaderboard Bonus	Finishing in the top 3 of a JV launch leaderboard.	1st place: $500–$2,000+. 2nd place: $250–$1,000. 3rd place: $100–$500. Scale with launch size.	Within 10 business days of launch close.	Manual calculation and payment — launch leaderboard bonuses are a one-off event tied to a specific launch, not a recurring commission structure.
Recruit Bonus	Recruiting a new affiliate to the programme who makes their first sale within 60 days.	$25–$100 flat bonus.	Added to the next monthly commission cycle after the recruited affiliate's first sale confirmation.	Manual in most platforms — requires tracking in the Partner Records Airtable table (Recruited By field).

Source table 11

PHASE 3The Payment System — Commission Payment Workflows5B21B6

Source table 12

MONTHLY COMMISSION PAYMENT PROTOCOL — Execute on the [12th] of each monthDAY 1 OF PAYMENT CYCLE (the [1st] of each month, or the Monday nearest to the 1st)STEP 1 — PULL THE COMMISSION REPORTExport the prior month's commission report from the affiliate platform: — Filter: commissions with status = 'Approved' (conversions confirmed, refund window closed) — Exclude: commissions with status = 'Reversed' (refunded), 'Held' (within refund window), or 'Void' — Result: the list of affiliates with payable commission balances for this payment cycleSTEP 2 — INDEPENDENT VERIFICATIONCross-reference the affiliate platform's commission report against the CRM's purchase records: — For each commission in the report: confirm a matching purchase event exists in the CRM with the affiliate's UTM tag — Flag any commission where no matching CRM purchase record exists (potential tracking error or fraud) — Flag any CRM purchase record with an affiliate UTM tag that does NOT appear in the commission report (potential missed attribution) Resolution for flagged items: — Platform commission present, no CRM record: hold the commission, investigate the tracking gap before paying — CRM record present, no platform commission: add a manual commission in the platform for the correct amount, document the reasonSTEP 3 — APPLY REFUND ADJUSTMENTSFor any commission that was paid in a prior month but has since been reversed due to a refund: Deduct the reversed amount from the current month's payment Document the deduction in the commission statement sent to the affiliateSTEP 4 — APPLY BONUS COMMISSIONSAdd any earned bonus commissions (first sale, volume milestone, launch leaderboard) to the payment total for qualifying affiliatesDocument each bonus in the Bonus Records tableSTEP 5 — APPLY MINIMUM PAYOUT THRESHOLDRemove any affiliate whose current balance is below the minimum threshold ($50)Their balance rolls to the next payment cycle — add a note in their Airtable Partner RecordDAY 2 OF PAYMENT CYCLE (the day after the report is verified)STEP 6 — COMMISSION STATEMENTS TO AFFILIATESBefore payment is made: send each affiliate their commission statement for the payment cycle.The statement includes: — Total clicks for the period — Total confirmed sales for the period — Total commission amount (gross) — Any deductions (refund reversals) — Any bonuses — Net payment amount — Expected payment date (3 business days from statement date)STEP 7 — 24-HOUR REVIEW PERIODAllow 24 hours for affiliates to review their statement and raise any discrepancies before payment is made.Any dispute received within 24 hours is investigated before payment proceeds (see Dispute Resolution Protocol).DAY 3 OF PAYMENT CYCLESTEP 8 — EXECUTE PAYMENTProcess payments through the agreed payment method for each affiliate: PayPal: send via PayPal mass pay or individual payments to each affiliate's registered PayPal email Wise: bulk transfer to international affiliates ACH: US-based affiliates with confirmed bank details Other: per the individual affiliate's registered payment methodSTEP 9 — PAYMENT CONFIRMATIONFor each payment processed: record the transaction ID and the payment date in the Partner Records table.Send a payment confirmation notification to each affiliate.STEP 10 — TAX DOCUMENTATIONFor US-based affiliates earning above $600 in the calendar year: collect the required tax documentation (W-9 for US individuals, W-8BEN for international).Issue 1099 forms to qualifying US affiliates by January 31 of the following year.For non-US affiliates: confirm the withholding requirements for their jurisdiction.

Source table 13

Dispute Type	Most Common Cause	Investigation Steps	Resolution Timeline	Resolution Standard
Missing commission — affiliate tracked a click but no commission appeared	Cross-device purchase (mobile click, desktop purchase) with cookie-only tracking; buyer cleared cookies before purchase; buyer used a different browser; tracking gap on the confirmation page.	1. Check the CRM for a purchase record with the affiliate's UTM tag. 2. Check the affiliate platform's click log for the affiliate's link click. 3. Check the payment processor's transaction records. 4. If the purchase event and the click event exist in the same 30-day window: the attribution is confirmed and the commission should be added manually.	48 hours from dispute received.	If the CRM confirms attribution (the buyer's UTM tag matches the affiliate): add the commission manually and document the cause. If the CRM does not confirm attribution: the dispute is not substantiated — respond with the specific data points that indicate the sale was not attributable.
Incorrect commission amount	The affiliate was paid at a different rate than expected, typically because a discount code reduced the commission base or a new product tier was not correctly configured.	1. Confirm the offer price at the time of the transaction (was a discount code applied?). 2. Confirm the commission rate configured for this offer and this affiliate's tier. 3. Calculate the correct commission amount from these two inputs.	24 hours.	If the commission was calculated correctly per the documented rules: explain the calculation with the specific transaction details. If the commission was calculated incorrectly due to a system misconfiguration: pay the difference in the next payment cycle and correct the configuration.
Commission reversed for a refund the affiliate disputes	The affiliate believes the refund was issued in error or they were not notified.	1. Confirm the refund in the payment processor's records. 2. Confirm the refund fell within the offer's refund policy window. 3. If the refund is confirmed and within policy: the reversal is correct.	48 hours.	If the refund is confirmed: explain the refund policy and confirm the reversal is correct. If the refund appears to be an error (the buyer was refunded when they should not have been): investigate the refund source and correct it if appropriate.
Sub-ID click not attributed to main link	The affiliate used a sub-ID variant of their link and the conversion is not appearing in their dashboard.	1. Check whether the sub-ID is correctly configured in the platform. 2. Check whether the sub-ID link was correctly formatted.	24 hours.	If the sub-ID link was correctly formatted and the conversion occurred within the cookie window: the commission should appear — investigate the platform configuration. If the sub-ID link was incorrectly formatted: explain the correct format and add the commission manually for this specific transaction.

Source table 14

PHASE 4The Affiliate Portal — The Affiliate's Experience of the ProgrammeB45309

Source table 15

Portal Section	Content Required	Design Principle	What Affiliates Do Without This
Dashboard (home page)	At-a-glance performance summary: clicks this month, conversions this month, pending commission balance, lifetime commission earned, payment history. A banner showing the next upcoming launch date (if applicable).	All numbers visible without a single click. The dashboard answers the three questions an affiliate asks when they log in: 'How am I doing this month? What do I owe? When is my next payment?'	Log in, see nothing useful, leave without promoting. Affiliates who cannot quickly assess their performance status do not stay engaged with the programme.
My Links	The affiliate's primary affiliate link (and any sub-ID links they have created). A simple sub-ID creator tool. A one-click link copy function.	The link section must be reachable in one click from the dashboard. A two-click path to the affiliate link is acceptable. A three-click path is not.	Affiliates who cannot find their link quickly either use outdated links from prior promotions or ask the operator for their link — wasting both parties' time.
Assets Library	All promotional materials organised by category: email templates, social posts, podcast scripts, banner images, case study one-pagers. Each asset is downloadable or copyable with a single action. Assets are dated — affiliates can see which version is current.	Assets are organised by format, not by date. The most recent version of each asset type is the default display. Older versions are archived, not deleted — some affiliates may be mid-promotion with an older asset.	Affiliates produce their own copy without guidance. This increases compliance risk and typically produces lower-converting promotional content.
Offer Details	Complete offer information for each commissionable offer: name, price, sales page URL, commission rate and amount, refund policy, and a 2–3 sentence offer description in plain language.	One page per offer — not a wall of text. The affiliate should be able to understand what they are promoting in 60 seconds.	Affiliates promote the offer with inaccurate or incomplete information. This produces compliance risk and lower conversion rates.
Commission History	A complete record of every commission event: date, attributed sale, offer name, gross commission, any adjustments (refunds), and payment status (pending, paid, reversed).	Each row is expandable — the affiliate can click a commission entry to see the supporting transaction detail (not just the commission amount).	Affiliates who cannot see the detail behind their commission history will dispute more — because opacity generates suspicion.
Leaderboard (for launch events)	During live launch windows: a real-time leaderboard showing the top affiliates by sales volume and commission earned for the current launch.	Only visible during active launch windows. Automatically disappears after the launch closes.	The competitive motivation and social proof of the leaderboard are not available.
Support / Contact	A clear path to contact the affiliate manager or programme support — email, a form, or a Slack/Discord link. The expected response time stated explicitly.	One-click access. Response time stated: 'We respond within 24 hours on business days.'	Affiliates with questions or issues go unanswered. Unanswered affiliates stop promoting.

Source table 16

Situation	Standard Procedure	What Could Go Wrong Without This Procedure
New affiliate approved	Generate the affiliate's unique link in the platform. Send the link to the affiliate in their onboarding email. Provide click-tracking instructions so the affiliate can verify their link is working before they promote.	The affiliate uses a manually-typed variation of the link that breaks the tracking parameter. Broken links issued at onboarding are never corrected because neither party tests them.
New offer added to the programme	Generate affiliate links for the new offer for all existing affiliates with the correct commission rate for the new offer. Notify all active affiliates of the new offer link via the programme newsletter.	Existing affiliates promote the new offer using their original link (which may not be configured for the new offer's commission). Commissions are either not tracked or tracked at the wrong rate.
JV launch begins	Issue launch-specific links for all JV partners with the correct launch commission rate. Send the link to each partner in the JV Partner Brief. Confirm receipt and provide testing instructions.	JV partners use their standard affiliate link, which tracks at the standard rate rather than the launch rate. Partners are under-compensated for their launch promotion effort.
Affiliate suspects a broken link	Provide the affiliate with a link testing protocol: click the link, check that the referral ID appears in the URL of the sales page (confirm the parameter passed correctly), complete a test with a $0 coupon if available.	Affiliate does not know how to verify the link. They assume it is working when it is not. Promotions are sent, buyers arrive, purchases are made, and zero commissions are attributed.

Source table 17

QUARTERLY LINK AUDIT PROTOCOLSTEP 1 — EXPORT ALL ACTIVE AFFILIATE LINKSExport a list of all active affiliates and their current link IDs from the affiliate platform.Include: Affiliate ID, Affiliate Name, Link URL, Offer the link is configured for, Commission Rate configured.STEP 2 — LINK VALIDITY CHECKFor each active affiliate link: perform an automated or manual click-through test. Automated: use a URL monitoring tool (UptimeRobot, Statuspage, or similar) to test all links for 200/redirect responses. Manual: click each link and confirm it redirects to the correct sales page with the affiliate's tracking parameter visible in the URL. Red flag: any link that returns a 404 (broken), a 302 redirect to the wrong page, or a sales page URL without the tracking parameter.STEP 3 — COMMISSION RATE VERIFICATIONFor each active affiliate: confirm the commission rate configured in the platform matches their documented tier in the Partner Records Airtable table. Red flag: any affiliate whose platform commission rate does not match their documented tier.STEP 4 — CROSS-DEVICE TRACKING TESTComplete one test transaction per offer (using a test coupon or test mode) via a mobile click → desktop purchase path. Expected result: the commission is attributed correctly (API-based tracking only — cookie-based tracking will fail this test). If cross-device attribution fails: investigate the API integration configuration.STEP 5 — AUDIT RESOLUTIONFor any issue found in steps 1–4: resolve within 7 days of the audit.Document the issue, the resolution, and the date of resolution in the Programme Audit Log.For any affiliate whose link was broken: check whether any sales may have been missed during the period the link was broken. If missed sales are identified: add manual commissions with an explanation.

Source table 18

Fraud Pattern	How It Works	Harm It Produces	Prevention Control
Self-Referral	The affiliate uses their own affiliate link to purchase the offer, earning a commission on their own purchase. They effectively buy the product at [price × (1 − commission rate)] rather than at the full price.	Revenue loss: the affiliate who buys a $797 offer through their own 30% link receives $239.10 back as commission — effectively purchasing at $557.90. At volume: significant revenue leakage.	Block self-referral in the affiliate platform (most platforms have a self-referral prevention setting). If the platform does not support this: configure the commission system to exclude purchases where the buyer's email matches the affiliate's registered email.
Fake Traffic / Click Inflation	The affiliate inflates their click count using bots, auto-clickers, or purchased clicks to appear to be driving more traffic than they are — creating a false high-click, low-conversion rate appearance.	No direct financial harm (commissions require conversions). Indirect harm: the operator may believe a high-traffic affiliate is underperforming their promotional potential and invest relationship resources in activating a partner who is not actually promoting genuinely.	Monitor the click-to-conversion ratio. A legitimate affiliate should produce a conversion rate of 0.5–5% of clicks. A click-to-conversion rate below 0.1% consistently over 30 days is a fraud signal. Flag for investigation.
Chargeback Fraud (Friendly Fraud)	A buyer (sometimes coordinated with the affiliate) purchases through the affiliate link and then initiates a chargeback — the commission is paid to the affiliate before the chargeback clears, and the operator loses both the sale price and the commission.	Revenue loss equal to the purchase price plus the commission plus the chargeback fee. The affiliate receives the commission; the operator loses the full purchase amount plus fees.	Implement a mandatory hold period: commissions are not paid until after the chargeback window has closed (typically 60–90 days for credit card chargebacks, though the platform's standard refund window of 30 days catches most cases). Do not pay commissions on sales with high fraud risk indicators (mismatched billing addresses, VPN-origin purchases, rapid multiple purchases by the same affiliate's referrals).
Cookie Stuffing	The affiliate places their affiliate tracking cookie on a visitor's browser without the visitor clicking an affiliate link — through hidden pixels, iframes, or other automated methods. Every subsequent purchase by that visitor is attributed to the affiliate.	Revenue loss: the affiliate earns commissions on purchases they did not genuinely influence.	Use API-based tracking rather than cookie-only tracking. API-based tracking requires a genuine click of the affiliate link to establish the relationship — it cannot be manufactured by cookie stuffing. Audit affiliates with unusually high click-to-conversion rates (above 10%) — these may indicate cookie stuffing.

Source table 19

Audit Area	Audit Frequency	What Is Checked	Expected Completion Time
Tracking Infrastructure	Quarterly	Link validity for all active affiliates. Commission rate accuracy for all affiliate tiers. Cross-device tracking test. Conversion event firing confirmation.	3–4 hours for a programme with up to 50 active affiliates.
Commission Records	Monthly (at each payment cycle)	Independent verification of commission statements against CRM purchase records. Refund reversal accuracy. Bonus commission application. Minimum threshold roll-overs.	2–3 hours per monthly payment cycle.
Partner Compliance	Quarterly	FTC disclosure compliance review: spot-check 10–15 recent promotional pieces from active affiliates for compliance with disclosure requirements. Any non-compliant promotional content identified: immediate notification to the affiliate.	2 hours for a spot-check of 10–15 promotions.
Fraud Indicators	Monthly	Click-to-conversion ratio review for all active affiliates. Any affiliate with below 0.1% conversion rate over 30 days flagged for investigation. Self-referral check. Chargeback rate review.	1 hour monthly.
Data Backup	Monthly	Export of all affiliate records, commission records, and payment records from the affiliate platform. Store in a secure, independent location (not on the same platform).	30 minutes.
Platform Health	Quarterly	Platform subscription and billing confirmed active. API integration status confirmed. Any platform feature changes that affect the programme's configuration reviewed and adapted.	1 hour.

Source table 20

QUARTERLY PROGRAMME AUDIT LOG — Maintained in AirtableAUDIT IDENTIFICATIONAudit ID: [AUDIT-[YYYY-Q#]. e.g. AUDIT-2026-Q3]Audit Date: [ ]Conducted By: [ ]TRACKING INFRASTRUCTURETotal active affiliate links audited: [ ]Links with issues found: [ ]Issues: [ ]Resolution date: [ ]Commission rate mismatches found: [ ]Resolution: [ ]Cross-device tracking test result: [ ] Pass [ ] Fail — issue: [ ]COMPLIANCE SPOT-CHECKPromotional pieces reviewed: [ ] from [ ] affiliatesNon-compliant pieces found: [ ]Affiliates notified: [ ]Resolution: [ ]FRAUD INDICATORSAffiliates with below 0.1% conversion rate (30-day): [ ]Investigations opened: [ ]Resolutions: [ ]COMMISSION AND PAYMENT RECORDSTotal commissions paid in the quarter: $[ ]Total affiliates paid: [ ]Commission disputes received in the quarter: [ ]Disputes resolved: [ ]Open disputes: [ ]DATA BACKUPAffiliate records exported and stored: [ ] Yes [ ] NoCommission records exported: [ ] Yes [ ] NoPayment records exported: [ ] Yes [ ] NoStorage location: [ ]ACTION ITEMSPriority action 1: [ ] — Owner: [ ] — Due: [ ]Priority action 2: [ ] — Owner: [ ] — Due: [ ]

Source table 21

Migration Step	Action Required	Timeline	Who Is Responsible
1 — Migration Decision	Document the specific reasons for migration: the current platform's failure to meet the non-negotiable standards, the new platform's demonstrated ability to meet those standards, and the cost-benefit analysis of migration overhead vs ongoing platform inadequacy.	Complete before any migration action	Founder
2 — New Platform Setup and Testing	Set up the complete affiliate programme architecture on the new platform using this SOP's Phase 1 and Phase 2 protocols. Complete the full test transaction verification sequence on the new platform before any data is migrated.	6–8 weeks before the planned migration date	Operator + new platform's technical support
3 — Partner Communication	Notify all active affiliates 4 weeks before the migration date: 'We are upgrading our affiliate infrastructure on [date]. Your new login credentials and links will be provided on [date]. Your commission records will be preserved in full.'	4 weeks before migration	Affiliate Manager
4 — Historical Data Export	Export a complete record of all affiliate data from the current platform: partner records, commission history, payment records. Store in the Programme Audit database as a permanent archive.	2 weeks before migration	Operator
5 — Commission Reconciliation	Complete a final commission payment cycle on the current platform for all commissions earned before the migration date. No commissions should be owed on the current platform at the point of migration.	1 week before migration	Operator
6 — New Credentials and Links Issued	Issue each affiliate their new platform login and their new unique affiliate link. Provide a clear, brief guide on the differences between the old and new interface.	On migration date	Affiliate Manager
7 — Old Platform Decommission	After 90 days of confirmed successful operation on the new platform: deactivate the old platform's affiliate links and close the account (or move it to archive mode if records must be preserved).	90 days after migration	Operator

Source table 22

Field	Type	Notes
Commission ID	Short text	Format: COMM-[Partner ID]-[YYYY-MM]-[Seq]. e.g. COMM-PART-AFF-042-2026-09-003
Partner	Link → Partner Records (from Partnerships SOP)
Transaction Date	Date	The date the purchase was confirmed
Offer Name	Short text
Transaction Amount (net)	Currency	After payment processing fees
Commission Rate	Number	% applied to this transaction
Commission Amount (gross)	Formula	Transaction Amount × Commission Rate ÷ 100
Status	Single select	Pending (in refund window) / Approved (payable) / Paid / Reversed (refunded) / Void (fraud or error) / Disputed
Payment Cycle	Short text	Which monthly payment cycle this commission belongs to (e.g. '2026-09')
CRM Verification	Checkbox	Has this commission been verified against the CRM purchase record?
CRM Purchase Record ID	Short text	The CRM contact record ID of the buyer for cross-reference
Sub-ID (if applicable)	Short text	The sub-ID parameter used in the affiliate link that generated this commission
Bonus Commission	Currency	Any bonus amount added to this commission cycle for this partner
Notes	Long text	Reason for any manual adjustments, dispute resolution notes

Source table 23

Field	Type	Notes
Bonus ID	Short text	Format: BONUS-[Partner ID]-[YYYY-MM]
Partner	Link → Partner Records
Bonus Type	Single select	First Sale / Volume Milestone (5/10/20) / Launch Leaderboard (1st/2nd/3rd) / Recruit Bonus / Other
Trigger Description	Short text	What specifically triggered the bonus
Bonus Amount	Currency
Added to Payment Cycle	Short text	Which monthly payment cycle this bonus was added to
Paid	Checkbox
Notes	Long text

Source table 24

Field	Type	Notes
Audit ID	Short text	Format: AUDIT-[YYYY-Q#]
Audit Date	Date
Conducted By	Short text
Audit Type	Single select	Quarterly Full Audit / Monthly Commission Audit / Ad Hoc (triggered by issue)
Links Audited — Count	Number
Links With Issues	Number
Commission Mismatches Found	Number
Compliance Issues Found	Number
Fraud Indicators Found	Number
Data Backup Completed	Checkbox
All Issues Resolved	Checkbox
Open Items	Long text	Description of any unresolved audit findings
Notes	Long text

Native Word text, including document headers and footers

word/document.xml
RISER NATION
MASTER OPERATING SYSTEM
SOP — AFFILIATE PROGRAM ARCHITECTURE
The Complete Technical and Operational Build Manual for the RISER Nation Affiliate Program — Platform Selection, Tracking Infrastructure, Commission Engine, Payment System, Affiliate Portal, Link Management, Dispute Resolution, Fraud Prevention, and Program Audit Protocol
2026 Framework × RISER Nation Master Operating System
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview — Architecture vs Strategy
The Partnerships and Affiliate Scaling SOP (Course 46) covers the strategic layer of the RISER Nation partner programme: who to recruit, how to approach them, what partnership types to offer, how to manage JV launches, and how to measure programme performance. This SOP covers the technical and operational layer: the specific platforms, configurations, tracking mechanisms, commission calculation logic, payment workflows, link management systems, and audit protocols that make the programme function reliably at scale.
The distinction matters because the most common affiliate programme failure is not strategic — it is architectural. An operator who recruits excellent partners, provides strong promotional assets, and manages relationships superbly will still damage those relationships if the underlying infrastructure produces tracking errors, incorrect commission statements, delayed payments, or broken affiliate links. Architecture failures are trust failures. Every tracking error is a potential dispute. Every payment delay is a relationship risk. Every broken link is lost commission the affiliate earned but never collected. The architecture SOP exists to make these failures rare and to make recovery from them fast when they do occur.
This SOP covers: the platform evaluation and selection framework, the tracking infrastructure build protocol, the commission engine configuration, the payment system setup, the affiliate portal design standards, the link management and testing protocol, the monthly programme audit, the commission dispute resolution process, the fraud prevention framework, the data backup and recovery protocol, and the migration plan for moving between affiliate platforms.
The Two Non-Negotiable Architecture Standards
Every affiliate programme architecture in the RISER Nation system must meet two non-negotiable standards before any affiliate link is issued. Standard 1 — Verified Tracking: a complete test transaction has been completed through a real affiliate link, the commission has appeared in the affiliate dashboard at the correct amount, and the attribution has been verified in both the affiliate platform's records and the operator's CRM records simultaneously. Standard 2 — Independent Commission Records: the operator maintains their own independent record of each affiliate's attributed sales and earned commissions — not relying solely on the affiliate platform's reporting. The independent record is the operator's source of truth in any dispute.
The Architecture Debt Problem
Many affiliate programmes are built quickly for a specific launch and never properly architected. The result is a programme that works adequately at 5 affiliates and collapses at 50 — because the tracking is unreliable at volume, the commission calculations are done manually in a spreadsheet, the payment workflow requires 3 hours of manual work per payment cycle, and the affiliate portal is a shared Google Drive folder with no access control. Architecture debt in affiliate programmes accumulates silently until the programme reaches a scale at which the manual processes become unmanageable. This SOP builds the architecture to handle 200 affiliates from day one — so the programme never needs to be rebuilt.
Platform Evaluation and Selection
The affiliate platform is the technical core of the programme — it generates unique links, tracks clicks and conversions, calculates commissions, and provides the affiliate-facing dashboard. Selecting the right platform is the highest-leverage architecture decision because it determines the programme's tracking reliability, payment capability, and management overhead for the lifetime of the programme.
The Platform Evaluation Framework
Evaluation Criterion
Minimum Acceptable Standard
Why It Is Non-Negotiable
Native integration with the operator's payment and course platform
The affiliate platform must integrate natively (via API or direct integration, not a third-party connector) with the operator's payment processor (Stripe, ThriveCart, SamCart, or equivalent) so that conversions are tracked automatically from the payment processor's confirmed purchase events — not from a pixel-based or cookie-based inference.
Pixel-based conversion tracking misses purchases where the buyer's browser has cookies disabled, ad-blocking enabled, or cross-device purchasing (they clicked on mobile, purchased on desktop). In 2026, pixel-based affiliate tracking misses 15–35% of actual attributed conversions. This means affiliates are systematically under-compensated, which destroys the relationship and makes the commission statement unreliable.
Real-time affiliate-facing dashboard
The affiliate can log in at any time and see their click count, conversion count, current commission balance, and payment history in real time — without requesting a report from the operator.
An affiliate programme without a self-service dashboard requires the operator to respond to commission status requests manually. At 30+ active affiliates, this is 10+ hours per month of unnecessary manual work. More importantly: affiliates who cannot self-verify their performance have no objective basis for trusting the commission statements they receive.
Unique affiliate link generation with custom sub-IDs
The platform generates a unique link per affiliate (minimum) and supports sub-IDs (optional parameters appended to the link) that allow the affiliate to track which specific promotion (which email, which social post, which podcast episode) drove each conversion.
Sub-IDs allow both the operator and the affiliate to analyse which promotional formats produce the best conversion rates for this specific offer. Affiliates who can see that their email broadcasts convert 3× better than their social posts will focus their effort on email — producing better results for both parties.
Automated recurring commission support
For continuity and subscription offers: the platform automatically calculates and records commissions on each recurring billing cycle — not just the initial purchase.
Manual calculation of recurring commissions for subscription products at scale is operationally unsustainable. At 100 active affiliates each referring 2 subscription buyers who renew monthly: that is 200 monthly commission calculations per payment cycle if done manually. The platform must handle this automatically.
Flexible commission rules by offer, tier, and time period
The platform allows different commission rates for different offers, different affiliates (or affiliate tiers), and different time periods (a higher rate during a live launch vs standard rate for evergreen promotions).
A single-rate system forces the operator to either pay the same rate for launch promotions and evergreen promotions (under-incentivising launch effort) or to not use the platform for one of the two use cases (increasing complexity by managing two systems).
Commission adjustment and override capability
The operator can manually adjust, void, or add commissions in specific circumstances: a conversion that was not auto-tracked due to a technical issue, a reversal due to fraud, or a bonus commission for a top performer.
Every affiliate programme has edge cases that the automated system cannot handle correctly. Without manual adjustment capability, the operator is forced to either ignore legitimate attribution errors or manage compensations outside the platform — both of which create tracking record inconsistencies.
The RISER Nation Platform Recommendation
The platform recommendation is based on the most common RISER Nation operator tech stack (Stripe or ThriveCart as payment processor, ActiveCampaign or ConvertKit as email platform, Kajabi, Teachable, or Thinkific as course platform). Operators using significantly different tech stacks should re-evaluate using the framework above rather than defaulting to the recommendation.
Platform
Best For
Primary Integration
Commission Models Supported
Affiliate Dashboard
Recurring Commission Support
Monthly Cost (approx.)
ThriveCart (native affiliate module)
Operators who use ThriveCart as their cart/checkout. The affiliate module is built in — no additional platform needed.
Native to ThriveCart checkout. Zero integration work if already using ThriveCart.
Flat fee, percentage, tiered, split commissions. Multiple rates per product.
Full self-service dashboard included.
Yes — automatically calculates on each billing cycle.
Included in ThriveCart licence ($495–$690 one-time)
PartnerStack
Knowledge businesses running above $15,000/month in affiliate-driven revenue. Best enterprise-grade system.
Stripe, Braintree, Chargebee, custom API.
Percentage, flat fee, milestone bonuses, tiered by performance.
Full self-service with analytics.
Yes — robust recurring commission engine.
$500–$2,000+/month depending on volume.
Impact (formerly Impact Radius)
Larger operators with multiple affiliate types (standard affiliates, agencies, influencers).
Stripe, PayPal, custom API, most major platforms.
Highly flexible — percentage, CPA, CPL, tiered, hybrid.
Full self-service with deep analytics.
Yes.
$500–$3,000+/month
Rewardful
Operators using Stripe who want a simple, clean affiliate system with minimal setup.
Native Stripe integration — automatically tracks all Stripe payments.
Percentage, flat fee, recurring percentage.
Clean self-service dashboard.
Yes — Stripe subscription-native.
$49–$299/month depending on revenue tracked.
FirstPromoter
SaaS-oriented but works well for knowledge businesses using Stripe. Simple setup, good affiliate dashboard.
Stripe, Paddle, Braintree, Recurly.
Percentage, flat fee, tiered, recurring.
Full self-service.
Yes.
$49–$149/month.
PHASE 1
The Tracking Infrastructure Build
The step-by-step technical setup that makes attribution reliable
The Tracking Infrastructure Setup Protocol
The tracking infrastructure is the collection of technical components that connect a partner's promotional activity (a click on their affiliate link) to a purchase event (a confirmed, paid transaction) and attribute the commission correctly. Each component must be configured and tested in sequence — skipping or abbreviating any step introduces attribution errors that compound over time.
TRACKING INFRASTRUCTURE SETUP — In sequence
STEP 1 — PLATFORM ACCOUNT CREATION AND CONFIGURATION
Create the affiliate platform account under the operator's business entity — not a personal account.
Configure the programme name, logo, and default commission rate.
Set the programme's public application URL (this is the URL provided to affiliates when inviting them to apply).
Configure the cookie duration: 30 days as the standard setting.
Configure the attribution model: Last Click (standard).
Set the minimum payout threshold: $50.
Configure the payment schedule: monthly, on the [15th] of each month for commissions earned in the prior month.
STEP 2 — PAYMENT PROCESSOR INTEGRATION
Connect the affiliate platform to the primary payment processor (Stripe, ThriveCart, or equivalent).
The integration method must be API-based — not pixel-based.
After connecting: confirm that the integration status shows 'Active' or 'Connected' in both the affiliate platform's dashboard and the payment processor's app integrations.
// Critical: an integration that shows 'connected' in one platform but not the other is not functioning — both must confirm the connection.
STEP 3 — OFFER CONFIGURATION
For each offer in the affiliate programme, create an offer record in the affiliate platform:
Offer name: [Exact product name as it appears on the sales page]
Commission rate: [Percentage or flat fee for this specific offer]
Commission type: [On first payment only / On all recurring payments]
Cookie applies to: [This specific offer / All offers in the programme]
Configure the commission rate override if the JV launch commission differs from the standard rate.
Exclude any offers that are not in the affiliate programme: premium offers with phone close, SLO (if the SLO is not part of the affiliate programme), and any internal offers.
STEP 4 — CONVERSION EVENT CONFIGURATION
Configure the purchase confirmation event:
The purchase confirmation event fires when a confirmed, paid transaction is completed.
It must NOT fire on: page views of the sales page, initiated checkouts, failed payment attempts.
For ThriveCart: the confirmation event fires on the order confirmation page — confirm the integration is mapping to confirmed orders, not initiated checkouts.
For Stripe: configure the webhook to fire on payment_intent.succeeded — not on payment_intent.created.
// Common error: configuring the event on checkout_session.created rather than payment_intent.succeeded results in commissions being attributed to incomplete checkouts that never convert. This inflates apparent affiliate performance while under-paying for genuine conversions.
STEP 5 — TEST TRANSACTION VERIFICATION
Create a test affiliate account using the operator's own email address at a secondary email domain (not the primary business email).
Generate a test affiliate link from the test account.
Complete a test purchase (use a $0 test coupon or a platform test mode) through the test affiliate link.
Verify the following sequence:
[ ] Click registered in the affiliate platform's click tracking
[ ] Conversion registered in the affiliate platform's conversion tracking within 5 minutes of the purchase
[ ] Commission calculated at the correct amount for the purchased offer
[ ] Commission appeared in the test affiliate's dashboard
[ ] Purchase event registered in the CRM with the affiliate's UTM tag attached to the subscriber record
STEP 6 — CROSS-DEVICE TRACKING VERIFICATION
// Many affiliate purchases involve cross-device journeys: the buyer clicks the affiliate link on mobile but completes the purchase on desktop. Cookie-based tracking fails for cross-device journeys; API-based tracking handles this correctly.
Test: click the affiliate link on a mobile browser. Do NOT complete the purchase. Switch to a desktop browser. Complete the purchase without clicking the affiliate link again.
Expected result for API-based tracking: the commission IS attributed to the affiliate (because the purchase is matched by customer identity, not by cookie).
Expected result for cookie-based tracking: the commission is NOT attributed (the cookie does not transfer between devices).
// If the result shows no attribution on the cross-device test and the platform is supposed to be API-based: the integration is not configured correctly. Contact the platform's support with the test transaction details before issuing any real affiliate links.
The UTM Integration Layer
The affiliate platform's tracking and the RISER Nation UTM convention from the Content-to-Revenue Attribution SOP must be integrated — so that each affiliate-referred subscriber and buyer is tagged in the CRM with both the affiliate platform's attribution and the standard UTM attribution. This dual-tagging enables independent commission verification and integrates affiliate revenue into the broader content-to-revenue reporting system.
Integration Point
How It Works
What It Enables
Affiliate link UTM parameters
Each affiliate's unique link is appended with UTM parameters that the operator's standard convention covers: utm_source=[affiliate_id], utm_medium=affiliate, utm_campaign=[programme_name] or [launch_name_if_jv]. The affiliate platform generates the base unique link; the UTM parameters are appended by the operator before issuing the link to the affiliate.
Any subscriber who opts in through an affiliate link is tagged in the CRM with utm_medium=affiliate. This allows the Content-to-Revenue Attribution SOP's monthly report to isolate affiliate-attributed revenue independently of the affiliate platform's own reporting.
CRM subscriber tagging
When a subscriber opts in through an affiliate link, the CRM captures the UTM parameters and stores them against the subscriber's contact record. The UTM source field (affiliate's ID) is stored permanently — even if the subscriber later returns via a different channel.
First-touch affiliate attribution in the CRM. The affiliate who originally introduced a subscriber to the programme receives credit in the CRM's attribution records, regardless of how many touchpoints the subscriber had before purchasing.
Purchase event dual-recording
When a purchase is made through an affiliate link: the affiliate platform records the commission event, AND the CRM records the purchase with the affiliate's UTM source attached to the buyer's contact record.
Independent verification of each commission event. If a dispute arises, the operator can verify the affiliate platform's commission record against the CRM's purchase record with matching affiliate UTM data.
PHASE 2
The Commission Engine Configuration
The rules that govern how commissions are calculated, credited, and adjusted
Commission Calculation Logic
Commission calculation must be explicitly configured — the platform does not automatically know which transactions are commissionable, how refunds affect commissions, how bonus structures work, or how split commissions between tiers of the affiliate hierarchy should be handled. Every commission rule must be configured and verified before the first live affiliate link is issued.
Commission Rule
Configuration Standard
Edge Case Handling
Standard percentage commission
Set as a percentage of the net transaction amount — after payment processing fees are deducted, before any platform or fulfilment costs are deducted.
Multiple products in a single transaction: commission applies to the total transaction net amount unless specific product exclusions have been configured. Configure exclusions for any products not in the affiliate programme.
Flat fee commission
Set as an absolute dollar amount per transaction — regardless of any discount codes or price variations applied at checkout.
If the offer has multiple pricing tiers (monthly vs annual): configure separate flat fees for each tier. A monthly subscription at $97/month and an annual at $797/year should have separate commission rates, not the same flat fee.
Recurring commission
Set to fire on every successful recurring billing event — not just the initial purchase. The recurring commission rate may be the same as or lower than the initial purchase rate.
Failed recurring payments: commission is NOT credited on failed charges. Only successful renewal charges trigger commission. Configure this explicitly — some platforms default to crediting on the billing attempt rather than the successful charge.
Refund handling
Commission status changes to 'Reversed' when a refund is processed within the refund window. If commission has already been paid before the refund occurs: the reversal creates a negative balance against the affiliate's next commission payment.
Partial refunds: commission is adjusted proportionally (not entirely reversed). Full refunds: commission fully reversed. Configure the platform to handle both partial and full refund scenarios.
Coupon code interactions
If the buyer used a discount code: commission applies to the discounted transaction price, not the full price. Internal coupon codes (used for bonuses or affiliate exclusives) should not reduce commission.
Internal affiliate bonus codes: configure specific coupon codes as 'commission-protected' so that the discount does not reduce the commission calculation. Example: a $100-off code offered as a bonus should not reduce the affiliate's commission.
Split commissions (if applicable)
If the affiliate programme uses a two-tier structure (an affiliate who recruited another affiliate earns a percentage of their recruit's commissions): configure the split percentage and ensure it applies correctly to the downstream affiliate's earnings without affecting the downstream affiliate's stated commission rate.
Two-tier split: the upstream affiliate's split commission is calculated from a pool separate from the downstream affiliate's commission — not subtracted from what the downstream affiliate earns.
The Bonus Commission Framework
Bonus commissions — additional commission payments above the standard rate for achieving specific milestones — are the primary motivation lever for moving affiliates from the Standard tier to the Active tier, and from Active to Super Affiliate. The bonus framework must be configured in the platform or tracked manually in a secondary system before any bonus is promised.
Bonus Type
Trigger Condition
Amount
Payment Timing
How to Configure
First Sale Bonus
The affiliate's first confirmed sale within 30 days of being approved.
$25–$50 flat bonus — a meaningful acknowledgement of the first promotional effort.
Added to the affiliate's next monthly commission payment.
Manual tracking in Airtable (Bonus Records table) — most platforms do not auto-trigger first-sale bonuses. Set a reminder to check new affiliates' status at Day 30 post-approval.
Volume Milestone Bonus
Reaching 5, 10, 20 sales within a calendar month.
Escalating flat bonus: $50 at 5 sales, $150 at 10 sales, $500 at 20 sales.
Same-month payment with the regular commission cycle.
Configurable in PartnerStack and Impact. Manual in most other platforms — set a monthly calendar reminder to review affiliate volumes and calculate milestone bonuses before the payment run.
Launch Leaderboard Bonus
Finishing in the top 3 of a JV launch leaderboard.
1st place: $500–$2,000+. 2nd place: $250–$1,000. 3rd place: $100–$500. Scale with launch size.
Within 10 business days of launch close.
Manual calculation and payment — launch leaderboard bonuses are a one-off event tied to a specific launch, not a recurring commission structure.
Recruit Bonus
Recruiting a new affiliate to the programme who makes their first sale within 60 days.
$25–$100 flat bonus.
Added to the next monthly commission cycle after the recruited affiliate's first sale confirmation.
Manual in most platforms — requires tracking in the Partner Records Airtable table (Recruited By field).
PHASE 3
The Payment System — Commission Payment Workflows
5B21B6
The Monthly Commission Payment Protocol
The commission payment workflow must be executed with the same discipline as payroll — on a fixed schedule, with independent verification, and with complete documentation of each payment. Inconsistent or delayed payments are the single most damaging operational failure an affiliate programme can produce.
MONTHLY COMMISSION PAYMENT PROTOCOL — Execute on the [12th] of each month
DAY 1 OF PAYMENT CYCLE (the [1st] of each month, or the Monday nearest to the 1st)
STEP 1 — PULL THE COMMISSION REPORT
Export the prior month's commission report from the affiliate platform:
— Filter: commissions with status = 'Approved' (conversions confirmed, refund window closed)
— Exclude: commissions with status = 'Reversed' (refunded), 'Held' (within refund window), or 'Void'
— Result: the list of affiliates with payable commission balances for this payment cycle
STEP 2 — INDEPENDENT VERIFICATION
Cross-reference the affiliate platform's commission report against the CRM's purchase records:
— For each commission in the report: confirm a matching purchase event exists in the CRM with the affiliate's UTM tag
— Flag any commission where no matching CRM purchase record exists (potential tracking error or fraud)
— Flag any CRM purchase record with an affiliate UTM tag that does NOT appear in the commission report (potential missed attribution)

Resolution for flagged items:
— Platform commission present, no CRM record: hold the commission, investigate the tracking gap before paying
— CRM record present, no platform commission: add a manual commission in the platform for the correct amount, document the reason
STEP 3 — APPLY REFUND ADJUSTMENTS
For any commission that was paid in a prior month but has since been reversed due to a refund:
Deduct the reversed amount from the current month's payment
Document the deduction in the commission statement sent to the affiliate
STEP 4 — APPLY BONUS COMMISSIONS
Add any earned bonus commissions (first sale, volume milestone, launch leaderboard) to the payment total for qualifying affiliates
Document each bonus in the Bonus Records table
STEP 5 — APPLY MINIMUM PAYOUT THRESHOLD
Remove any affiliate whose current balance is below the minimum threshold ($50)
Their balance rolls to the next payment cycle — add a note in their Airtable Partner Record
DAY 2 OF PAYMENT CYCLE (the day after the report is verified)
STEP 6 — COMMISSION STATEMENTS TO AFFILIATES
Before payment is made: send each affiliate their commission statement for the payment cycle.
The statement includes:
— Total clicks for the period
— Total confirmed sales for the period
— Total commission amount (gross)
— Any deductions (refund reversals)
— Any bonuses
— Net payment amount
— Expected payment date (3 business days from statement date)
STEP 7 — 24-HOUR REVIEW PERIOD
Allow 24 hours for affiliates to review their statement and raise any discrepancies before payment is made.
Any dispute received within 24 hours is investigated before payment proceeds (see Dispute Resolution Protocol).
DAY 3 OF PAYMENT CYCLE
STEP 8 — EXECUTE PAYMENT
Process payments through the agreed payment method for each affiliate:
PayPal: send via PayPal mass pay or individual payments to each affiliate's registered PayPal email
Wise: bulk transfer to international affiliates
ACH: US-based affiliates with confirmed bank details
Other: per the individual affiliate's registered payment method
STEP 9 — PAYMENT CONFIRMATION
For each payment processed: record the transaction ID and the payment date in the Partner Records table.
Send a payment confirmation notification to each affiliate.
STEP 10 — TAX DOCUMENTATION
For US-based affiliates earning above $600 in the calendar year: collect the required tax documentation (W-9 for US individuals, W-8BEN for international).
Issue 1099 forms to qualifying US affiliates by January 31 of the following year.
For non-US affiliates: confirm the withholding requirements for their jurisdiction.
The Commission Dispute Resolution Protocol
Commission disputes arise when an affiliate believes they were not credited for a sale they generated. Disputes handled well strengthen the relationship — the affiliate sees that the operator takes attribution seriously. Disputes handled poorly (delayed response, dismissiveness, or incorrect resolution) permanently damage the relationship.
Dispute Type
Most Common Cause
Investigation Steps
Resolution Timeline
Resolution Standard
Missing commission — affiliate tracked a click but no commission appeared
Cross-device purchase (mobile click, desktop purchase) with cookie-only tracking; buyer cleared cookies before purchase; buyer used a different browser; tracking gap on the confirmation page.
1. Check the CRM for a purchase record with the affiliate's UTM tag. 2. Check the affiliate platform's click log for the affiliate's link click. 3. Check the payment processor's transaction records. 4. If the purchase event and the click event exist in the same 30-day window: the attribution is confirmed and the commission should be added manually.
48 hours from dispute received.
If the CRM confirms attribution (the buyer's UTM tag matches the affiliate): add the commission manually and document the cause. If the CRM does not confirm attribution: the dispute is not substantiated — respond with the specific data points that indicate the sale was not attributable.
Incorrect commission amount
The affiliate was paid at a different rate than expected, typically because a discount code reduced the commission base or a new product tier was not correctly configured.
1. Confirm the offer price at the time of the transaction (was a discount code applied?). 2. Confirm the commission rate configured for this offer and this affiliate's tier. 3. Calculate the correct commission amount from these two inputs.
24 hours.
If the commission was calculated correctly per the documented rules: explain the calculation with the specific transaction details. If the commission was calculated incorrectly due to a system misconfiguration: pay the difference in the next payment cycle and correct the configuration.
Commission reversed for a refund the affiliate disputes
The affiliate believes the refund was issued in error or they were not notified.
1. Confirm the refund in the payment processor's records. 2. Confirm the refund fell within the offer's refund policy window. 3. If the refund is confirmed and within policy: the reversal is correct.
48 hours.
If the refund is confirmed: explain the refund policy and confirm the reversal is correct. If the refund appears to be an error (the buyer was refunded when they should not have been): investigate the refund source and correct it if appropriate.
Sub-ID click not attributed to main link
The affiliate used a sub-ID variant of their link and the conversion is not appearing in their dashboard.
1. Check whether the sub-ID is correctly configured in the platform. 2. Check whether the sub-ID link was correctly formatted.
24 hours.
If the sub-ID link was correctly formatted and the conversion occurred within the cookie window: the commission should appear — investigate the platform configuration. If the sub-ID link was incorrectly formatted: explain the correct format and add the commission manually for this specific transaction.
PHASE 4
The Affiliate Portal — The Affiliate's Experience of the Programme
B45309
What the Affiliate Portal Must Contain
The affiliate portal is the affiliate's primary interface with the programme. Its design determines whether affiliates feel professionally supported (which motivates promotion) or confused and under-resourced (which discourages promotion). Every element of the portal serves one function: making it as easy as possible for an affiliate to find what they need, take the next action, and understand how they are performing.
Portal Section
Content Required
Design Principle
What Affiliates Do Without This
Dashboard (home page)
At-a-glance performance summary: clicks this month, conversions this month, pending commission balance, lifetime commission earned, payment history. A banner showing the next upcoming launch date (if applicable).
All numbers visible without a single click. The dashboard answers the three questions an affiliate asks when they log in: 'How am I doing this month? What do I owe? When is my next payment?'
Log in, see nothing useful, leave without promoting. Affiliates who cannot quickly assess their performance status do not stay engaged with the programme.
My Links
The affiliate's primary affiliate link (and any sub-ID links they have created). A simple sub-ID creator tool. A one-click link copy function.
The link section must be reachable in one click from the dashboard. A two-click path to the affiliate link is acceptable. A three-click path is not.
Affiliates who cannot find their link quickly either use outdated links from prior promotions or ask the operator for their link — wasting both parties' time.
Assets Library
All promotional materials organised by category: email templates, social posts, podcast scripts, banner images, case study one-pagers. Each asset is downloadable or copyable with a single action. Assets are dated — affiliates can see which version is current.
Assets are organised by format, not by date. The most recent version of each asset type is the default display. Older versions are archived, not deleted — some affiliates may be mid-promotion with an older asset.
Affiliates produce their own copy without guidance. This increases compliance risk and typically produces lower-converting promotional content.
Offer Details
Complete offer information for each commissionable offer: name, price, sales page URL, commission rate and amount, refund policy, and a 2–3 sentence offer description in plain language.
One page per offer — not a wall of text. The affiliate should be able to understand what they are promoting in 60 seconds.
Affiliates promote the offer with inaccurate or incomplete information. This produces compliance risk and lower conversion rates.
Commission History
A complete record of every commission event: date, attributed sale, offer name, gross commission, any adjustments (refunds), and payment status (pending, paid, reversed).
Each row is expandable — the affiliate can click a commission entry to see the supporting transaction detail (not just the commission amount).
Affiliates who cannot see the detail behind their commission history will dispute more — because opacity generates suspicion.
Leaderboard (for launch events)
During live launch windows: a real-time leaderboard showing the top affiliates by sales volume and commission earned for the current launch.
Only visible during active launch windows. Automatically disappears after the launch closes.
The competitive motivation and social proof of the leaderboard are not available.
Support / Contact
A clear path to contact the affiliate manager or programme support — email, a form, or a Slack/Discord link. The expected response time stated explicitly.
One-click access. Response time stated: 'We respond within 24 hours on business days.'
Affiliates with questions or issues go unanswered. Unanswered affiliates stop promoting.
The Link Management and Testing Protocol
Affiliate links are the primary operational asset of the programme. A broken affiliate link silently destroys commission attribution without any obvious error message — the buyer arrives at the sales page, the page loads normally, and the purchase is completed, but the affiliate's link click was not correctly tracked and the commission is not attributed. The link testing protocol prevents this.
The Link Issuance Protocol
Situation
Standard Procedure
What Could Go Wrong Without This Procedure
New affiliate approved
Generate the affiliate's unique link in the platform. Send the link to the affiliate in their onboarding email. Provide click-tracking instructions so the affiliate can verify their link is working before they promote.
The affiliate uses a manually-typed variation of the link that breaks the tracking parameter. Broken links issued at onboarding are never corrected because neither party tests them.
New offer added to the programme
Generate affiliate links for the new offer for all existing affiliates with the correct commission rate for the new offer. Notify all active affiliates of the new offer link via the programme newsletter.
Existing affiliates promote the new offer using their original link (which may not be configured for the new offer's commission). Commissions are either not tracked or tracked at the wrong rate.
JV launch begins
Issue launch-specific links for all JV partners with the correct launch commission rate. Send the link to each partner in the JV Partner Brief. Confirm receipt and provide testing instructions.
JV partners use their standard affiliate link, which tracks at the standard rate rather than the launch rate. Partners are under-compensated for their launch promotion effort.
Affiliate suspects a broken link
Provide the affiliate with a link testing protocol: click the link, check that the referral ID appears in the URL of the sales page (confirm the parameter passed correctly), complete a test with a $0 coupon if available.
Affiliate does not know how to verify the link. They assume it is working when it is not. Promotions are sent, buyers arrive, purchases are made, and zero commissions are attributed.
The Quarterly Link Audit
Every affiliate's links are tested quarterly — regardless of whether any issue has been reported. Many tracking problems are silent: they do not produce an error, they do not alert the affiliate or the operator, and they accumulate as missing attribution until the quarterly audit identifies them.
QUARTERLY LINK AUDIT PROTOCOL
STEP 1 — EXPORT ALL ACTIVE AFFILIATE LINKS
Export a list of all active affiliates and their current link IDs from the affiliate platform.
Include: Affiliate ID, Affiliate Name, Link URL, Offer the link is configured for, Commission Rate configured.
STEP 2 — LINK VALIDITY CHECK
For each active affiliate link: perform an automated or manual click-through test.
Automated: use a URL monitoring tool (UptimeRobot, Statuspage, or similar) to test all links for 200/redirect responses.
Manual: click each link and confirm it redirects to the correct sales page with the affiliate's tracking parameter visible in the URL.
Red flag: any link that returns a 404 (broken), a 302 redirect to the wrong page, or a sales page URL without the tracking parameter.
STEP 3 — COMMISSION RATE VERIFICATION
For each active affiliate: confirm the commission rate configured in the platform matches their documented tier in the Partner Records Airtable table.
Red flag: any affiliate whose platform commission rate does not match their documented tier.
STEP 4 — CROSS-DEVICE TRACKING TEST
Complete one test transaction per offer (using a test coupon or test mode) via a mobile click → desktop purchase path.
Expected result: the commission is attributed correctly (API-based tracking only — cookie-based tracking will fail this test).
If cross-device attribution fails: investigate the API integration configuration.
STEP 5 — AUDIT RESOLUTION
For any issue found in steps 1–4: resolve within 7 days of the audit.
Document the issue, the resolution, and the date of resolution in the Programme Audit Log.
For any affiliate whose link was broken: check whether any sales may have been missed during the period the link was broken. If missed sales are identified: add manual commissions with an explanation.
The Fraud Prevention Framework
Affiliate fraud — fake clicks, fraudulent purchases made by the affiliate using stolen payment credentials, and self-referral (the affiliate purchases through their own link to earn their own commission) — exists in every affiliate programme. The RISER Nation fraud prevention framework is not a paranoid surveillance system; it is a set of reasonable controls that make common fraud patterns unprofitable without creating friction for legitimate affiliates.
The Four Most Common Fraud Patterns and Their Controls
Fraud Pattern
How It Works
Harm It Produces
Prevention Control
Self-Referral
The affiliate uses their own affiliate link to purchase the offer, earning a commission on their own purchase. They effectively buy the product at [price × (1 − commission rate)] rather than at the full price.
Revenue loss: the affiliate who buys a $797 offer through their own 30% link receives $239.10 back as commission — effectively purchasing at $557.90. At volume: significant revenue leakage.
Block self-referral in the affiliate platform (most platforms have a self-referral prevention setting). If the platform does not support this: configure the commission system to exclude purchases where the buyer's email matches the affiliate's registered email.
Fake Traffic / Click Inflation
The affiliate inflates their click count using bots, auto-clickers, or purchased clicks to appear to be driving more traffic than they are — creating a false high-click, low-conversion rate appearance.
No direct financial harm (commissions require conversions). Indirect harm: the operator may believe a high-traffic affiliate is underperforming their promotional potential and invest relationship resources in activating a partner who is not actually promoting genuinely.
Monitor the click-to-conversion ratio. A legitimate affiliate should produce a conversion rate of 0.5–5% of clicks. A click-to-conversion rate below 0.1% consistently over 30 days is a fraud signal. Flag for investigation.
Chargeback Fraud (Friendly Fraud)
A buyer (sometimes coordinated with the affiliate) purchases through the affiliate link and then initiates a chargeback — the commission is paid to the affiliate before the chargeback clears, and the operator loses both the sale price and the commission.
Revenue loss equal to the purchase price plus the commission plus the chargeback fee. The affiliate receives the commission; the operator loses the full purchase amount plus fees.
Implement a mandatory hold period: commissions are not paid until after the chargeback window has closed (typically 60–90 days for credit card chargebacks, though the platform's standard refund window of 30 days catches most cases). Do not pay commissions on sales with high fraud risk indicators (mismatched billing addresses, VPN-origin purchases, rapid multiple purchases by the same affiliate's referrals).
Cookie Stuffing
The affiliate places their affiliate tracking cookie on a visitor's browser without the visitor clicking an affiliate link — through hidden pixels, iframes, or other automated methods. Every subsequent purchase by that visitor is attributed to the affiliate.
Revenue loss: the affiliate earns commissions on purchases they did not genuinely influence.
Use API-based tracking rather than cookie-only tracking. API-based tracking requires a genuine click of the affiliate link to establish the relationship — it cannot be manufactured by cookie stuffing. Audit affiliates with unusually high click-to-conversion rates (above 10%) — these may indicate cookie stuffing.
The Programme Audit Protocol
The programme audit is a comprehensive quarterly review of the entire affiliate programme architecture — not just a review of recent sales and commissions. It examines the tracking infrastructure, the commission configuration, the payment records, and the compliance status to identify any systemic issues before they accumulate into programme-level failures.
Audit Area
Audit Frequency
What Is Checked
Expected Completion Time
Tracking Infrastructure
Quarterly
Link validity for all active affiliates. Commission rate accuracy for all affiliate tiers. Cross-device tracking test. Conversion event firing confirmation.
3–4 hours for a programme with up to 50 active affiliates.
Commission Records
Monthly (at each payment cycle)
Independent verification of commission statements against CRM purchase records. Refund reversal accuracy. Bonus commission application. Minimum threshold roll-overs.
2–3 hours per monthly payment cycle.
Partner Compliance
Quarterly
FTC disclosure compliance review: spot-check 10–15 recent promotional pieces from active affiliates for compliance with disclosure requirements. Any non-compliant promotional content identified: immediate notification to the affiliate.
2 hours for a spot-check of 10–15 promotions.
Fraud Indicators
Monthly
Click-to-conversion ratio review for all active affiliates. Any affiliate with below 0.1% conversion rate over 30 days flagged for investigation. Self-referral check. Chargeback rate review.
1 hour monthly.
Data Backup
Monthly
Export of all affiliate records, commission records, and payment records from the affiliate platform. Store in a secure, independent location (not on the same platform).
30 minutes.
Platform Health
Quarterly
Platform subscription and billing confirmed active. API integration status confirmed. Any platform feature changes that affect the programme's configuration reviewed and adapted.
1 hour.
The Programme Audit Log
QUARTERLY PROGRAMME AUDIT LOG — Maintained in Airtable
AUDIT IDENTIFICATION
Audit ID: [AUDIT-[YYYY-Q#]. e.g. AUDIT-2026-Q3]
Audit Date: [ ]
Conducted By: [ ]
TRACKING INFRASTRUCTURE
Total active affiliate links audited: [ ]
Links with issues found: [ ]
Issues: [ ]
Resolution date: [ ]
Commission rate mismatches found: [ ]
Resolution: [ ]
Cross-device tracking test result: [ ] Pass [ ] Fail — issue: [ ]
COMPLIANCE SPOT-CHECK
Promotional pieces reviewed: [ ] from [ ] affiliates
Non-compliant pieces found: [ ]
Affiliates notified: [ ]
Resolution: [ ]
FRAUD INDICATORS
Affiliates with below 0.1% conversion rate (30-day): [ ]
Investigations opened: [ ]
Resolutions: [ ]
COMMISSION AND PAYMENT RECORDS
Total commissions paid in the quarter: $[ ]
Total affiliates paid: [ ]
Commission disputes received in the quarter: [ ]
Disputes resolved: [ ]
Open disputes: [ ]
DATA BACKUP
Affiliate records exported and stored: [ ] Yes [ ] No
Commission records exported: [ ] Yes [ ] No
Payment records exported: [ ] Yes [ ] No
Storage location: [ ]
ACTION ITEMS
Priority action 1: [ ] — Owner: [ ] — Due: [ ]
Priority action 2: [ ] — Owner: [ ] — Due: [ ]
The Platform Migration Protocol
Migrating an affiliate programme from one platform to another is one of the highest-risk operational events in the programme's lifecycle. Done incorrectly, migration produces broken links, lost commission records, confused affiliates, and attribution failures that take months to untangle. The migration protocol is the systematic process that makes migration reliable.
Migration Step
Action Required
Timeline
Who Is Responsible
1 — Migration Decision
Document the specific reasons for migration: the current platform's failure to meet the non-negotiable standards, the new platform's demonstrated ability to meet those standards, and the cost-benefit analysis of migration overhead vs ongoing platform inadequacy.
Complete before any migration action
Founder
2 — New Platform Setup and Testing
Set up the complete affiliate programme architecture on the new platform using this SOP's Phase 1 and Phase 2 protocols. Complete the full test transaction verification sequence on the new platform before any data is migrated.
6–8 weeks before the planned migration date
Operator + new platform's technical support
3 — Partner Communication
Notify all active affiliates 4 weeks before the migration date: 'We are upgrading our affiliate infrastructure on [date]. Your new login credentials and links will be provided on [date]. Your commission records will be preserved in full.'
4 weeks before migration
Affiliate Manager
4 — Historical Data Export
Export a complete record of all affiliate data from the current platform: partner records, commission history, payment records. Store in the Programme Audit database as a permanent archive.
2 weeks before migration
Operator
5 — Commission Reconciliation
Complete a final commission payment cycle on the current platform for all commissions earned before the migration date. No commissions should be owed on the current platform at the point of migration.
1 week before migration
Operator
6 — New Credentials and Links Issued
Issue each affiliate their new platform login and their new unique affiliate link. Provide a clear, brief guide on the differences between the old and new interface.
On migration date
Affiliate Manager
7 — Old Platform Decommission
After 90 days of confirmed successful operation on the new platform: deactivate the old platform's affiliate links and close the account (or move it to archive mode if records must be preserved).
90 days after migration
Operator
Airtable Schema — Affiliate Architecture Database
Table 1 — Commission Records
Field
Type
Notes
Commission ID
Short text
Format: COMM-[Partner ID]-[YYYY-MM]-[Seq]. e.g. COMM-PART-AFF-042-2026-09-003
Partner
Link → Partner Records (from Partnerships SOP)
Transaction Date
Date
The date the purchase was confirmed
Offer Name
Short text
Transaction Amount (net)
Currency
After payment processing fees
Commission Rate
Number
% applied to this transaction
Commission Amount (gross)
Formula
Transaction Amount × Commission Rate ÷ 100
Status
Single select
Pending (in refund window) / Approved (payable) / Paid / Reversed (refunded) / Void (fraud or error) / Disputed
Payment Cycle
Short text
Which monthly payment cycle this commission belongs to (e.g. '2026-09')
CRM Verification
Checkbox
Has this commission been verified against the CRM purchase record?
CRM Purchase Record ID
Short text
The CRM contact record ID of the buyer for cross-reference
Sub-ID (if applicable)
Short text
The sub-ID parameter used in the affiliate link that generated this commission
Bonus Commission
Currency
Any bonus amount added to this commission cycle for this partner
Notes
Long text
Reason for any manual adjustments, dispute resolution notes
Table 2 — Bonus Records
Field
Type
Notes
Bonus ID
Short text
Format: BONUS-[Partner ID]-[YYYY-MM]
Partner
Link → Partner Records
Bonus Type
Single select
First Sale / Volume Milestone (5/10/20) / Launch Leaderboard (1st/2nd/3rd) / Recruit Bonus / Other
Trigger Description
Short text
What specifically triggered the bonus
Bonus Amount
Currency
Added to Payment Cycle
Short text
Which monthly payment cycle this bonus was added to
Paid
Checkbox
Notes
Long text
Table 3 — Programme Audit Log
Field
Type
Notes
Audit ID
Short text
Format: AUDIT-[YYYY-Q#]
Audit Date
Date
Conducted By
Short text
Audit Type
Single select
Quarterly Full Audit / Monthly Commission Audit / Ad Hoc (triggered by issue)
Links Audited — Count
Number
Links With Issues
Number
Commission Mismatches Found
Number
Compliance Issues Found
Number
Fraud Indicators Found
Number
Data Backup Completed
Checkbox
All Issues Resolved
Checkbox
Open Items
Long text
Description of any unresolved audit findings
Notes
Long text
Master Affiliate Program Architecture Checklist
Platform Selection and Initial Setup
☐
Platform selected using the six evaluation criteria — all minimum standards confirmed
☐
Platform account created under the operator's business entity
☐
Commission tiers and rates configured in the platform for all offers in the programme
☐
Cookie duration set to 30 days. Attribution model set to Last Click
☐
Minimum payout threshold set to $50. Monthly payment schedule configured
Tracking Infrastructure Build (Phase 1)
☐
Payment processor API integration confirmed — status shows Active in both platforms
☐
Conversion event configured on the payment confirmation (not the checkout initiation)
☐
Test transaction completed through a test affiliate link — commission appeared in the dashboard at the correct amount
☐
CRM UTM integration confirmed — the test purchase appears in the CRM with the affiliate's UTM tag
☐
Cross-device tracking test completed — API-based attribution confirmed for mobile-click/desktop-purchase journey
Commission Engine (Phase 2)
☐
All commission rules configured and documented: standard percentage, recurring, refund handling, coupon interactions
☐
Bonus commission framework documented in Airtable — first sale, volume milestone, launch leaderboard, and recruit bonus criteria all defined
☐
Self-referral prevention enabled or equivalent manual control configured
Payment System (Phase 3)
☐
Monthly payment protocol calendar events created — recurring on the agreed dates
☐
Commission statement template created — all required fields present (clicks, conversions, gross commission, deductions, bonuses, net payment)
☐
Payment method confirmed for each active affiliate — collected during onboarding
☐
Tax documentation collection process in place for US affiliates exceeding $600/year
Affiliate Portal (Phase 4)
☐
Portal dashboard confirmed: clicks, conversions, pending balance, lifetime earnings, payment history all visible on login
☐
My Links section: one-click link copy, sub-ID creator, link testing instructions
☐
Asset Library populated with all promotional materials — dated and organised by format
☐
Offer Details page accurate and current for all commissionable offers
☐
Support contact path confirmed — response time stated
Quarterly Audit Schedule
☐
Quarterly audit calendar events created — Link Audit, Compliance Spot-Check, Cross-Device Test, Platform Health
☐
Monthly commission audit events created — aligned with the payment cycle
☐
Monthly fraud indicator review scheduled — click-to-conversion ratio, self-referral check
☐
Monthly data backup event created — affiliate records, commission records, payment records
RISER Nation Master Operating System | Affiliate Program Architecture SOP | Version 1.0 | 2026 Edition
RISER Nation | risernation.com

word/header1.xml
RISER Nation | Affiliate Program Architecture SOP | V1.0

word/footer1.xml
Page
of

word/footnotes.xml

word/endnotes.xml

word/comments.xml

RISER-Behavioral-Logic-Nudge-Theory-SOP.docx

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

Working teaching draft. Source examples and policy assumptions require context; corrections and unresolved dependencies are identified in the script.

Use behavioral design to help an informed choice

This SOP presents twelve nudges for knowledge-business marketing under its internal Course 16/Track 4 label. It attributes nudge theory to Thaler and Sunstein and asks whether a buyer who understood the design would feel helped or exploited. Treat that as a practical review question, not a guarantee that every example passes it. The claim that rational buying is almost always wrong is too broad. Context, reasoning, goals and constraints can all influence decisions.

D0927 — assigned source supporting this teaching point

Explain the two-process model without overclaiming

The source uses Kahneman's fast, automatic, associative System 1 and slower, deliberate System 2. Its table compares speed, effort, error types, influence mechanisms and buying roles. Use the model to consider both first impressions and detailed evidence, not as literal separate brain systems or a fixed sequence every buyer follows. Defaults, salience, framing and sequence can affect attention; arguments, data and specific evidence help evaluation. Claims that architecture always produces higher conversion or that defaults multiply it two to three times are unverified in this document.

D0927 — assigned source supporting this teaching point

Nudge 1: choose a useful default

The source examples are a recommended middle pricing tier and a prominent Start Here onboarding path. A default should reflect the buyer's likely needs, remain visible and be easy to change. Distinguish a recommendation from a Most Popular claim, which needs real usage evidence. Do not preselect unwanted paid extras or disguise recurring terms. The onboarding default should guide the best learning sequence rather than rush the learner into an upsell.

D0927 — assigned source supporting this teaching point

Nudge 2: make proof specific and verifiable

The examples replace a vague thousand-person count with 1,247 knowledge-business operators; a vague testimonial with 63 days and $3,500 monthly income; and general success language with seven of ten reaching $5,000 per month within 90 days. These are source examples, not RISER results. Specificity helps a reader inspect a claim, but a number is not automatically evidence. Retain the actual population, dates, conditions and permission to use a testimonial; never invent precision or imply a selected result is typical.

D0927 — assigned source supporting this teaching point

Nudge 3: describe a real cost without creating fear

Loss-framing examples include a proposed $3,000–$5,000 monthly opportunity cost and underpriced proposals. Before using them, establish whether that cost actually applies and how it was estimated. A hypothetical forgone sale is not a realized loss. The source's approximately twice-as-powerful claim is not a universal coefficient for every buyer or context. Use loss framing to make a documented problem clearer, while keeping uncertainty and alternatives visible.

D0927 — assigned source supporting this teaching point

Nudge 4: anchor with a meaningful comparison

The value-stack example adds ten coaching hours at $500, $1,500 copywriting and $2,000 strategy to reach $8,500, compared with a $997 program. Another example multiplies 18 months by $3,000 to reach a hypothetical $54,000 delay cost. A tier example places $2,997 VIP before $997 Standard. Check that components, scope and prices are genuine and comparable; the delayed-income assumption is not guaranteed recoverable revenue. Do not create a shell high-price offer solely to make another price look small.

D0927 — assigned source supporting this teaching point

Nudge 5: use only genuine scarcity and deadlines

The source's cohort example has capacity for 25 and 18 places filled, with a stated close date or capacity cutoff. Its live-bonus example closes enrollment 48 hours before delivery. Its price example requires a real post-launch increase. These are illustrative structures, not current availability. State the actual reason, count and terms; do not use resetting timers, false sell-outs or permanent temporary discounts. If circumstances change, explain them honestly rather than concealing an extension.

D0927 — assigned source supporting this teaching point

Nudge 6: reduce unnecessary friction

Inspect form fields, page transitions, payment clarity and pricing complexity. Keep required delivery, payment, consent and policy information while removing irrelevant questions. The source's claims of 10–25% improvement from removing three fields and 5–10% loss per extra page are unsupported benchmarks here. An application or qualification step can be useful when it helps assess fit. Security logos and guarantee language must accurately describe the actual checkout and terms, not act as decorative proof of safety.

D0927 — assigned source supporting this teaching point

Nudge 7: organize choices around buyer needs

The source recommends no more than three tiers, names the recommended option and favors one decision at a time. These are design hypotheses, not a universal optimum proven by the cited jam-study reference. Some offers need more configurations; clear names and comparisons may matter more than the count. The source also favors fewer checkout pages, so test whether sequential decisions reduce confusion or merely add steps. Keep the primary offer, optional bump and payment terms distinguishable.

D0927 — assigned source supporting this teaching point

Nudge 8: make the next important information easy to find

Use visual hierarchy appropriate to the stage: an outcome headline on an opt-in page, clear proof on a sales page, and price and action at checkout. The source proposes contrast, whitespace and size, plus putting the key insight first and a clear action last in an email. Apply this without hiding limitations, exits or costs. Claims that readers always absorb particular paragraph positions are heuristics, not observed behavior for every visitor.

D0927 — assigned source supporting this teaching point

Nudge 9: invite consistent progress without pressure

The source maps small commitments from subscription to a useful resource, welcome content, webinar and offer. Keep the content and eventual offer aligned; productivity tips should not quietly become an unrelated high-ticket pitch. Its community example is a voluntary 90-day goal statement. A learner may change goals, decline a purchase or request a refund without being shamed for inconsistency. A prior click, download or public goal is not consent to a later transaction.

D0927 — assigned source supporting this teaching point

Nudge 10: give useful value without imposing a debt

A Traffic Hook should produce a specific usable benefit, personal replies should address the real question, and pre-offer emails should include useful actions. The source warns against generic free material and pretending automated messages are personal responses. The practical standard is honest value and transparent communication. Receiving free help does not obligate someone to buy, reciprocate or remain on a list.

D0927 — assigned source supporting this teaching point

Nudge 11: support the buyer's own identity

The source rewrites transactional CTAs toward systematic building, serious operators and finishing a program. Use the buyer's stated aspiration as an invitation, not a test of worth or belonging. Avoid implying that people who decline are unserious or failures. The cited 15% voter statistic is not substantiated in this SOP and is not a forecast for sales or completion. Measure whether the wording improves understanding and fit, not only clicks.

D0927 — assigned source supporting this teaching point

Nudge 12: use context honestly

The source offers achievement stories before an offer, verified authority markers, and an accurate cost exercise 24–48 hours before loss-framed copy. Its examples of 340 consultants and seven of ten successes require real evidence. Environmental context may influence interpretation, but the document does not establish a guaranteed priming effect. Keep a story authentic, a credential verifiable and an estimate bounded rather than using presentation to imply unsupported authority.

D0927 — assigned source supporting this teaching point

Map awareness and engagement

At awareness, the source prioritizes relevance through salience and specific proof, with environmental context as support. Its less-than-three-second target is an internal design aim. At engagement, it prioritizes useful content and small consistent actions, with a suggested minimum of five value-delivering emails before an offer. Create a clear opening and a coherent sequence; neither timing rule is universal. Use actual buyer language and accurate evidence in the proposed design output.

D0927 — assigned source supporting this teaching point

Map consideration and purchase

At consideration, the source matches category skepticism with documented problem cost, meaningful price anchors and relevant proof. At purchase, it matches inertia and risk with a visible recommendation, understandable options, reduced friction, genuine deadlines and a respectful CTA. The design output should make scope, total cost and choice clear. A lower observed conversion rate is not sufficient reason to intensify pressure or hide alternatives.

D0927 — assigned source supporting this teaching point

Map onboarding and ascension

Post-purchase, the source proposes a Start Here path, voluntary goal setting and a visible first win within seven days. Treat the time as a delivery design target appropriate to the lesson. At ascension, it proposes monthly value summaries and milestone-based invitations tied to the next actual problem, with capacity limits only when genuine. A purchase does not prove readiness for another offer; learning progress and the learner's preferences should guide the next step.

D0927 — assigned source supporting this teaching point

Measure all ten transition points

The friction audit tracks visitor→subscriber, subscriber→resource consumer, subscriber→first-email opener, opener→clicker, clicker→sales-page reader, reader→checkout initiator, checkout→purchase, purchase→first module within seven days, starter→completer, and completer→continuity member. Define numerator, denominator, cohort and period for each. Email opens, downloads and scroll depth are imperfect proxies for reading or learning; keep them distinct from confirmed completion and outcomes.

D0927 — assigned source supporting this teaching point

Use the supplied benchmarks as internal hypotheses

The source supplies targets for T1 warm opt-in above 30%, T3 first-email open above 50%, T4 email click above 5%, T7 checkout completion above 70%, T8 seven-day start above 80%, T9 program completion above 40% and T10 continuity conversion above 30%. It provides no numeric targets for T2, T5 or T6. Record that gap rather than inventing industry standards. Compare like populations and choose priorities using impact and evidence as well as the numerical deficit.

D0927 — assigned source supporting this teaching point

Diagnose the type of friction before changing copy

Cognitive friction may involve too many decisions or an unclear next step, addressed with simplification and choice structure. Emotional friction may involve distrust, requiring evidence and appropriate reassurance rather than exaggerated loss framing. Motivational friction may involve unclear relevance or a genuine timing issue. Technical friction requires fixing slow pages, broken links or navigation. The source recommends quarterly audits and after funnel changes, with a 90-day focus on the largest issue; these are planning cadences, not mandatory waiting periods for urgent defects.

D0927 — assigned source supporting this teaching point

Interpret the measurement window and formulas correctly

The source suggests evaluating after 30 days or 200 data points, whichever comes first. That alone does not establish statistical significance or causality. Record the baseline, change, exposure and possible confounders. Its Gap field is Current minus Benchmark, so the most negative value is the largest shortfall when higher is better. Relative change is (Post−Baseline)/Baseline×100 and is undefined when baseline is zero; report an absolute change then. Do not assign Significant Improvement without a defined analysis.

D0927 — assigned source supporting this teaching point

Apply all five ethical boundaries

The source contrasts genuine scarcity with resetting timers; documented costs with anxiety-inducing inventions; accurate proof with fabricated testimonials or undisclosed incentives; genuinely useful free content with obligation traps; and positive identity invitations with insecurity or exclusion pressure. A paid or incentivized endorsement requires appropriate disclosure and honest content; it is not interchangeable with fabricated proof. Use current FTC guidance for the actual disclosure standard. No design should obscure the right to decline.

D0927 — assigned source supporting this teaching point · FTC — Endorsement and disclosure guidance

Prepare the AI context and four generation exercises

Before generation, specify funnel stage, barrier, buyer profile and chosen nudge, and supply real evidence. The four requests are three loss-framed openings from actual cost data, a value stack from genuine component prices, testimonial edits using only existing accurate specifics, and identity-framed CTAs based on the buyer's aspirations. Preserve testimonial meaning and consent; do not add results. The three review questions are whether any claim remains unverified, whether scarcity is genuine, and whether the buyer would understand and accept the method.

D0927 — assigned source supporting this teaching point

Build both behavioral-design tables

Nudge Deployment Records needs ID ND-[YYYY-MM]-[Seq], nudge1–12, stage1–6, location, description, ethical review, baseline, post-metric, percentage change, verdict, next action and deployment/measurement dates. Friction Audit Records needs date, transitionT1–T10, current rate, benchmark, gap, friction type, recommended nudge, action, post-action rate and priority. Define verdicts and units before data entry. The source's checklists add initial model review, per-stage design, checkout/onboarding checks, quarterly measurement and ongoing claim verification; these are evidence-based tasks, not boxes to mark automatically.

D0927 — assigned source supporting this teaching point

Submit a complete choice-design example

Choose one real transition, describe the buyer's goal and barrier, select a nudge, draft the page or message, explain the evidence and ethical boundary, and define the measurement. Attach the ten-transition audit and a six-stage map so the change fits the broader journey. Retain all twelve source examples and distinguish authored practice values from actual results. The source names an implementation calendar, but chiefly supplies recurring cadences rather than a complete dated launch plan.

D0927 — assigned source supporting this teaching point

Apply the agreed marketing lenses

D0927 — assigned source supporting this teaching point · ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Complete original source export

RISER NATION
MASTER OPERATING SYSTEM — COURSE 16 — TRACK 4: PERSUASION & MESSAGING
SOP — BEHAVIORAL LOGIC & NUDGE THEORY
The Complete System for Designing AI-Assisted Behavioral Marketing That Guides Customer Decisions Using Ethical Nudge Theory — The Dual-Process Decision Model, the Twelve Core Nudges, the Choice Architecture Design Protocol, the Buyer Journey Nudge Map, the Friction Audit, the Implementation Calendar, and the Ethical Boundaries Framework
Track 4: Persuasion & Messaging — Course 16 | 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview — Why Buyer Behaviour Is Not Driven by the Information You Provide
The rational model of buying assumes that people gather information, weigh options, calculate value, and make the optimal decision. This model is wrong in almost every commercially relevant context. Real buying decisions are made quickly, partially unconsciously, heavily influenced by context, framing, and comparison rather than by the objective merits of the options under consideration. A buyer who reads the same sales page twice — once when the price is framed as a cost and once when the same price is framed as an investment — makes a different decision. Not because their values changed. Because the framing changed the reference point against which the price was evaluated.
Nudge theory, developed by Richard Thaler and Cass Sunstein and grounded in decades of behavioural economics research, provides a systematic framework for understanding how the context in which a choice is presented influences which choice is made — without changing the options or restricting freedom. A nudge is any aspect of the choice architecture that predictably alters behaviour without forbidding options or significantly changing economic incentives. In a knowledge business, the choice architecture is everything: the sequence of emails, the structure of the sales page, the options available on the checkout page, the order in which programme modules are presented, the framing of the price, the presence or absence of a default option.
This SOP covers: the Dual-Process Decision Model that explains why nudges work, the twelve core nudges and how each applies specifically to knowledge business buyer decisions, the Choice Architecture Design Protocol for the full buyer journey, the Buyer Journey Nudge Map, the Friction Audit that identifies where buyers are dropping from the funnel, the AI-assisted behavioural marketing workflow, and the Ethical Boundaries Framework that distinguishes ethical nudging from manipulation.
The Dual-Process Decision Model
The theoretical foundation of behavioural economics and nudge theory is the Dual-Process Model of thinking, most accessibly described by Daniel Kahneman in Thinking, Fast and Slow. The model identifies two systems of cognitive processing that operate in parallel: System 1, which is fast, automatic, associative, and effortless, and System 2, which is slow, deliberate, analytical, and effortful.
Each nudge below is presented with its behavioural science basis, its ethical application in a knowledge business context, a worked example from a knowledge business environment, and the specific funnel stage or marketing context where it is most effectively deployed.
Nudge 1 — Defaults
The most powerful single nudge in the catalogue. When a choice has a default option — the option that is selected if no active choice is made — the majority of people in most contexts accept the default. This is not laziness. It is the rational recognition that defaults are usually set to the recommended or most common option.
Nudge 2 — Social Proof Specificity
Social proof influences System 1 through the conformity heuristic: what most people like me do is probably the right thing to do. The nudge is not the presence of social proof — it is the specificity with which it is presented. A specific number is more persuasive than a vague claim because the brain's pattern-matching system treats specificity as a marker of credibility.
Nudge 3 — Loss Framing (Loss Aversion)
Loss aversion is one of the most consistent findings in behavioural economics: the psychological pain of losing something is approximately twice as powerful as the pleasure of gaining an equivalent amount. Kahneman and Tversky's seminal research established this asymmetry across hundreds of decision contexts. In marketing, this means that framing a benefit as preventing a loss activates stronger motivation than framing the same benefit as delivering a gain.
Nudge 4 — Anchoring
An anchor is the first number or value presented in a context that serves as the reference point against which all subsequent numbers are evaluated. The brain does not assess prices in absolute terms — it assesses them relative to the most salient prior reference point. Anchoring is one of the most replicable findings in cognitive psychology and one of the most consistently deployed nudges in high-converting sales contexts.
Nudge 5 — Scarcity and Urgency (Genuine)
Scarcity and urgency are among the most powerful and most abused nudges in marketing. When genuine, they activate the loss aversion mechanism: if this opportunity is genuinely limited, not taking it now is a loss. When manufactured, they activate scepticism and distrust that is disproportionately damaging to the buyer-operator relationship.
Nudge 6 — Friction Reduction
Every step a buyer must take to complete a purchase — every field, every page, every click, every decision — is a friction point that reduces the probability of completing the purchase. System 1 avoids effort. Reducing friction is not about removing important steps. It is about removing unnecessary steps that add no information value and only add cognitive or physical effort.
Nudge 7 — Choice Architecture and the Paradox of Choice
Barry Schwartz's research on the Paradox of Choice established that beyond a moderate number of options, additional options do not produce greater buyer satisfaction — they produce greater buyer anxiety and lower purchase rates. The knowledge business operator who offers ten ways to work with them is not maximising access. They are maximising the probability that the buyer does not choose any of them.
Nudge 8 — Salience and Attention Direction
Salience is the property of standing out from the surrounding context. The most salient element in a choice environment receives the most attention and is weighted most heavily in the decision. Operators who design visual and content hierarchy to make the most important elements the most salient are directing buyer attention to the information that most supports the purchase decision.
Nudge 9 — Commitment and Consistency
Robert Cialdini's research on consistency established that people who have made a small prior commitment are significantly more likely to follow through with a larger subsequent commitment aligned with the prior one. This is not just social pressure — it is an internal cognitive consistency drive: having said or done X, we are motivated to act consistently with X.
Nudge 10 — Reciprocity
Cialdini's reciprocity principle establishes that people feel a genuine, non-commercial obligation to return value that has been given to them. When an operator provides genuine, specific, freely-given value before any request for commercial engagement, the buyer experiences a motivation to reciprocate. This is not manipulation — it is the mechanism that makes the Traffic Hook and content marketing commercially effective.
Nudge 11 — Identity-Based Framing
People act consistently with their identity. When a choice is framed in terms of the kind of person who makes that choice — rather than in terms of the consequences of making it — it activates the buyer's desire for identity consistency rather than their calculation of consequences. 'Voters are 15% more likely to vote when asked if they plan to be a voter rather than if they plan to vote' (Cialdini).
Nudge 12 — Environmental Priming
Environmental priming refers to the phenomenon where exposure to specific words, images, or concepts in the environment unconsciously activates related concepts and influences subsequent behaviour. In a marketing context, the language and imagery that precede an offer presentation prime the buyer's System 1 to evaluate the offer through a specific lens.
Each stage of the buyer journey has a specific primary barrier and a specific nudge that addresses that barrier most effectively. The Buyer Journey Nudge Map organises the twelve nudges by funnel stage so the operator can design the complete behavioural architecture of their marketing system rather than applying nudges opportunistically.
The Friction Audit — Identifying Where Buyers Are Leaving the Funnel
The Friction Audit is a structured review of every transition point in the buyer journey — every place where a buyer who was engaged at Stage N did not progress to Stage N+1. Friction accumulates at transition points, and identifying which transition has the most friction is the most efficient conversion improvement activity available.
The Friction Audit Protocol
The Ethical Boundaries Framework
Every nudge in this SOP is designed for application in an ethically sound marketing system. The Ethical Boundaries Framework defines the specific standards that distinguish ethical nudging from manipulation in the knowledge business context, and the specific practices that are not permitted regardless of their conversion effectiveness.
The AI-Assisted Behavioural Design Workflow
AI tools can accelerate the application of nudge theory to marketing copy by rapidly generating multiple variants of the same content with different nudge approaches applied. The workflow below ensures AI output is grounded in the correct behavioural science framework rather than producing generic marketing copy.
Airtable Schema — Behavioural Design Database
Table 1 — Nudge Deployment Records
Table 2 — Friction Audit Records
Master Behavioral Logic & Nudge Theory Checklist
Understanding and Setup (Complete once, before applying nudges)
☐ Dual-Process Decision Model understood — can explain why System 1 nudges precede System 2 persuasion
☐ All twelve nudges reviewed — specific application to own niche identified for each
☐ Ethical Boundaries Framework reviewed — the distinction between ethical nudging and manipulation is clear
☐ Airtable Nudge Deployment Records and Friction Audit tables created
Funnel Architecture Design (Apply during Course 22 content build and sales page construction)
☐ Buyer Journey Nudge Map reviewed for each active funnel stage
☐ Primary barrier identified for each active stage
☐ Primary nudge assigned to each barrier
☐ Choice Architecture reviewed: maximum three tiers on any pricing page, recommended option clearly labelled
☐ Checkout friction audit: form fields reduced to minimum, security signals visible, single CTA
☐ Onboarding sequence: default 'Start Here' path set, community goal-setting post included
Quarterly Friction Audit
☐ All ten transition rates measured and recorded in Airtable
☐ Highest-friction transition identified
☐ Friction type diagnosed: cognitive, emotional, motivational, or technical
☐ Appropriate nudge or fix applied
☐ Baseline metric recorded before the change
☐ Post-deployment metric recorded 30 days later
Ongoing Nudge Application Quality Check
☐ All scarcity and urgency claims verified as genuine before every launch
☐ All social proof numbers verified as accurate before every deployment
☐ All loss framing reviewed against the Ethical Boundaries Framework
☐ AI-generated behavioural copy reviewed against the three-point ethical filter
RISER Nation Master Operating System | Behavioral Logic & Nudge Theory SOP | Course 16 | Version 1.0 | 2026 Edition
Track 4: Persuasion & Messaging — Course 16 | risernation.com
The Ethical Distinction — Nudging vs Manipulation
Nudge theory carries an ethical obligation that this SOP takes seriously. A nudge is ethical when it makes it easier for people to make the choice that is in their own best interest, given their own values and goals. A nudge becomes manipulation when it makes it easier for people to make the choice that is in the operator's best interest at the expense of the buyer's. The test is simple: 'If this buyer knew exactly what I am doing here and why, would they feel helped or exploited?' Every nudge in this SOP passes that test. Any nudge that does not pass it is not in this SOP and should not be applied.
System 1 and System 2 — Why This Is Not Common Sense
The reason nudge theory requires a dedicated course rather than being intuitive is that it describes a layer of decision-making that operates below conscious awareness. Operators who are aware that they are making a decision — choosing a price point, deciding on a guarantee, selecting the order of offer elements — are using System 2 (deliberate, analytical thinking). But buyers in the moment of encounter with an offer are largely operating in System 1 (fast, automatic, pattern-matching thinking). What feels obvious to a System 2 designer is not what drives System 1 buyer behaviour. Nudge theory bridges the gap.
The Scale Effect — Why Small Changes in Choice Architecture Produce Large Differences in Outcomes
Nudge theory's most commercially significant finding: small changes to the environment in which choices are made produce disproportionately large changes in behaviour, often without the decision-maker being aware that their behaviour changed or why. A default option that is the operator's recommended choice converts at 2–3x the rate of the same option presented as an active choice. A social proof statement that provides a specific number ('joined by 1,247 consultants') converts at significantly higher rates than the same statement without the number. These are not persuasion differences — they are architecture differences. Architecture is changed once and works continuously.
Property
System 1 (Fast, Automatic)
System 2 (Slow, Deliberate)
Implication for Knowledge Business Marketing
Speed
Milliseconds to seconds. Processes information faster than conscious awareness.
Seconds to minutes. Requires active effort and attention allocation.
The buyer's first impression of an email subject line, a landing page headline, or an offer name is a System 1 response. The detailed rational evaluation of the offer's value is a System 2 response. Both must be satisfied but in sequence.
Effort
Effortless. Does not deplete cognitive resources.
Effortful. Depletes cognitive resources. Buyers in a cognitively depleted state (decision fatigue) revert more heavily to System 1.
Simplifying the choice architecture reduces cognitive load, enabling System 2 to engage more fully. An offer with too many options, too many decisions, or too much information produces System 1 avoidance rather than System 2 evaluation.
Error type
Associative errors: pattern-matching to the wrong category, influenced by irrelevant anchors, susceptible to framing effects.
Deliberate errors: motivated reasoning, confirmation bias, analysis paralysis.
System 1 errors are predictable and consistent across buyers. Knowing which associative errors are most likely in the purchase context allows the operator to design the context to prevent them.
Influence mechanisms
Defaults, social proof, salience, anchoring, loss framing, sequential presentation order, comparison context.
Arguments, evidence, testimonials, logical structure, data.
System 1 nudges operate on the architecture (defaults, sequence, framing). System 2 persuasion operates on the content (evidence, argument, social proof details). Both are required. System 1 nudges create the conditions for System 2 persuasion to be received.
Buying role
Makes the initial go/no-go decision at each stage of the funnel (open the email, read the sales page, reach the checkout, complete the purchase).
Evaluates the specific offer details once System 1 has decided to engage. Provides the post-hoc rationalisation for decisions already made.
Marketing that addresses only System 2 (rational arguments and feature lists) loses buyers at the System 1 gate before they engage with the argument. Marketing that addresses System 1 first, then System 2, converts at higher rates.
THE TWELVE CORE NUDGES
Applied to Knowledge Business Buyer Decisions
Each nudge with definition, ethical application, worked example, and deployment context
Application
Worked Example
Deployment Context
Ethical Boundary
Offer tier default
On a pricing page with three tiers, the middle tier is pre-selected. The buyer can change to any tier but must actively choose to do so. The middle tier is the operator's recommended option. 'Most popular' badge on the recommended tier. The tier is visually highlighted and pre-selected if the checkout page uses a selector mechanism.
Checkout page, pricing page.
The default must be the operator's genuine recommendation for the typical buyer, not the most expensive option by default.
Programme onboarding sequence default
When new buyers access their programme dashboard, the recommended starting path is pre-selected. The 'Start Here' module is first in sequence, visually prominent, and marked as 'Recommended Starting Point.' Other navigation requires an active click away from the default path.
Programme delivery platform, onboarding email.
The default path must reflect the genuine best-practice completion sequence, not the sequence that most quickly exposes the buyer to upsell content.
Application
Specificity Upgrade
Behavioural Effect
Deployment Context
Subscriber or community count
'Over 1,000 people' → '1,247 knowledge business operators have joined this community'
The specific number is treated as evidence rather than claim. The descriptor ('knowledge business operators') activates the relevance detection system from Course 15.
Landing page, email signature, webinar registration page.
Testimonial framing
'This programme works' → 'In 63 days I went from zero clients to a full roster at $3,500/month'
The specific number (63 days, $3,500/month) converts the testimonial from a claim to a data point. Data points pass System 2's evidence standard as well as System 1's specificity pattern.
Sales page, email sequences, social media.
Result frequency
'Many clients achieve this result' → '7 of the last 10 operators who completed this programme reached $5K/month within 90 days'
The frequency framing ('7 of 10') activates the availability heuristic positively: the result seems common because a specific frequency is cited, rather than vague.
Sales page results section, webinar slides.
Gain Framing (Standard)
Loss Framing (Higher Activation)
Why the Difference Matters
Ethical Application Boundary
'This programme will help you sign new clients'
'Every month without a consistent client acquisition system, you are leaving approximately $3,000–$5,000 in revenue that competitors who have solved this problem are collecting instead'
Loss framing activates the pain of the current situation rather than the aspiration of the future state. For buyers who are already experiencing the pain of the problem, loss framing is more accurate to their lived experience.
Loss framing must accurately describe a real cost or risk the buyer faces. Fabricating or exaggerating losses is manipulation. The loss must be real, specific, and directly experienced by the target buyer.
'Develop a systematic approach to pricing'
'Every under-priced proposal you send is a negotiation you have already lost before the conversation starts'
Under-pricing is a loss the buyer is currently experiencing in every proposal. Framing it as a present, active loss rather than a future gain from solving it activates stronger immediate motivation.
The loss must be one the buyer has actually experienced, not a hypothetical future risk. Framing a loss the buyer does not experience as if it is universal is inaccurate.
Anchoring Application
How It Works
Knowledge Business Example
Ethical Standard
Price anchoring with the full value stack
Before presenting the programme price, build the full value stack: the monetary equivalent of all components if purchased separately.
'If you hired a coach to help with client acquisition ($500/hour, minimum 10 sessions = $5,000), a copywriter to create your positioning ($1,500), and a strategist to design your offer ($2,000), you would invest $8,500 to get these components separately. This programme is $997.'
The value stack must reflect genuine market prices for genuine components. Inflated values or fabricated comparisons manipulate rather than anchor.
Anchoring with the cost of the problem
Before presenting the price, establish the cost of the problem the offer solves.
'The average consultant who does not have a systematic client acquisition process takes 18 months to reach a sustainable income. That is 18 months of below-target income. At $3,000/month below target, that is $54,000 in delayed income. This programme is $997.'
The cost must be a realistic, evidence-based estimate, not a fabricated or extreme scenario.
Tier-first anchoring
When presenting multiple tiers, always begin with the highest-priced tier. This establishes the price range's upper boundary, making the mid-tier feel accessible rather than expensive.
Present the VIP tier ($2,997) first with its description. Then present the Standard tier ($997). Standard feels reasonable relative to the anchor.
The highest-priced tier must be a genuine, fully-described offering. Presenting a shell offer at a high price solely to anchor the real offer is deceptive.
Type
Genuine vs Manufactured
Ethical Standard
Worked Example
Cohort-limited enrolment
A programme that runs with a specific cohort in a live or community format genuinely cannot accept unlimited enrolments without degrading the experience quality. Cohort size limits are genuine scarcity.
State the specific cohort size and the specific reason for the limit. 'This cohort is limited to 25 members because that is the maximum that allows each member to receive personalised feedback within each live session.' The reason is the credibility signal.
'The March cohort is limited to 25 members. As of this email, 18 spots are filled. If you are planning to join, the enrolment closes on [date] or when the cohort fills, whichever comes first.'
Time-limited bonus
A bonus that is available for a defined period as part of a launch or a specific promotional event. The time limit is genuine because the bonus represents a specific delivery commitment (a live call, a live workshop, a personal review) that cannot be honoured after a specific date.
State the specific reason for the deadline. 'The live implementation call is scheduled for [date]. Enrolment closes 48 hours before the call so every member can be prepared.'
Never extend a 'final' deadline. An extended deadline tells the audience that the original deadline was false, retroactively undermining the credibility of every future deadline.
Price integrity, not false urgency
The price will not decrease after the promotional period. 'This is the launch price and it will increase' is legitimate if the price genuinely increases and stays higher. It is false if the 'launch price' becomes the permanent price.
Maintain price integrity. If the price is stated as a launch price, raise it after the launch and keep it raised.
Never present a permanently discounted price as a temporary one.
Friction Source
How to Reduce It
Conversion Impact
When Friction Should Be Preserved
Checkout page with too many fields
Reduce form fields to the minimum required for delivery and communication: name, email, payment. Remove fields that are useful for the operator's CRM but not required for the transaction.
Removing 3 non-essential form fields typically increases checkout completion rates by 10–25%.
Friction that serves as a quality signal (an application form before a premium offer, a qualification question before a high-ticket programme) is preserved because it communicates exclusivity and qualification.
Multiple pages between decision and payment
Where possible, reduce the steps between 'I want this' and 'I have paid.' Each additional page is a drop-off point.
Each additional page in the checkout flow reduces completion by 5–10% on average for standard e-commerce. Knowledge business buyers are typically more committed, but the same principle applies.
Payment plan options or order bump decisions that add a step should only be added if the revenue increase from the option exceeds the conversion loss from the additional friction.
Unclear or absent payment security indicators
SSL indicators, payment processor logos (Stripe, PayPal), and money-back guarantee statements reduce the perceived risk at the payment decision point.
The absence of trust indicators is a source of friction even when there is nothing actually wrong with the payment page. The buyer's pattern-recognition system reads 'no security indicators' as 'higher risk.'
None. Trust indicators should always be present on any payment page.
Complex pricing options
More than three pricing tiers produces choice overload (see Nudge 7 below). A buyer who cannot quickly determine which option is right for them defaults to inaction.
The classic 'jam study' (Iyengar and Lepper) showed that 24 options produced significantly lower purchase rates than 6 options. Three tiers is the knowledge business maximum for a standard offer.
When the offer genuinely serves distinct buyer profiles that require different configurations, more options may be necessary. The fix is not fewer options but better option naming that makes the right choice obvious for each buyer profile.
Principle
Application
Standard
Common Error
Maximum options per decision
Three options is the optimal number for most knowledge business purchase decisions. Two options sometimes feel too constrained. Four or more options reliably produce decision paralysis.
A pricing page has three tiers. The offer page has one core offer with one order bump. The value ladder has clear, named rungs.
Listing every possible way to work together on one page: the course, the coaching programme, the mastermind, the 1:1 engagement, the group programme, and the done-for-you option. The buyer cannot determine which is right for them without a significant research investment.
Naming the right choice
When there is a recommended choice, it should be explicitly named as the recommended choice rather than leaving the buyer to infer it.
'Most popular' or 'Recommended for [specific profile]' labelling on the appropriate tier removes ambiguity about which option is right for the majority of buyers.
Presenting all options neutrally with equal visual weight and no recommendation signal. The buyer is left to reason through the comparison without guidance.
Sequential vs simultaneous presentation
When the buyer must make multiple decisions, presenting them sequentially (one decision at a time) produces higher overall completion rates than presenting them simultaneously.
The checkout process: Step 1 is selecting the offer. Step 2 is adding the order bump. Step 3 is payment. Each step is a single decision.
A checkout page that simultaneously presents the tier selection, the order bump, the payment plan options, and the payment form. Multiple simultaneous decisions produce overwhelm.
Salience Application
How It Works
Knowledge Business Context
The Salience Hierarchy Rule
Visual hierarchy on sales and landing pages
The most important element — the headline on an opt-in page, the primary CTA on a sales page, the price on a checkout page — is visually the most prominent: largest text, most contrast, most whitespace surrounding it.
A sales page where the outcome headline is the largest text element on the page, the testimonials are the second most prominent, and the price and CTA are the third most prominent — following the sequence in which the buyer needs to receive information to convert.
The element that receives the most visual prominence is the element that should be the buyer's primary focus at that stage of the decision. Prioritise based on the buyer's information needs, not the operator's aesthetic preferences.
Content sequencing in emails and articles
The most important point is made first (the hook), not buried in the middle or saved for the end. Readers in a scan mode will absorb the first and last sentence of each paragraph. The middle is read only when the start and end have already justified the reading.
An email that opens with the most compelling single insight (not 'Dear [Name], I hope this finds you well') and closes with a clear, single CTA.
The sequence rule: most important first, second most important last, least important in the middle.
Application
How It Works
Knowledge Business Example
Ethical Note
Micro-commitments before the offer
Before presenting the Core Offer, the buyer is led through a sequence of micro-commitments: subscribing to the email list (small commitment), downloading the Traffic Hook (slightly larger), opening and engaging with the welcome sequence (further commitment), watching the webinar (significant commitment). Each step makes the next feel consistent.
The traffic hook → welcome email sequence → webinar → Core Offer structure is both a value-delivery sequence AND a commitment escalation sequence. The buyer's commitment level by the time they reach the offer is significantly higher than if the offer had been presented cold.
The consistency principle does not justify creating artificial commitments that mislead the buyer about what the escalation leads to. Micro-commitments should be consistent with the eventual offer direction — a buyer who subscribes for 'free productivity tips' who is then sold a $1,000 business development programme has been led through a commitment mismatch.
Public commitment in community settings
When community members publicly state their goals, they are more likely to pursue them because abandoning them requires an internal inconsistency.
Programme onboarding that asks new buyers to publicly state their 90-day goal in the community ('I am here to achieve [X] by [date]') increases programme completion rates because abandoning the programme means abandoning the publicly stated goal.
Public commitment should be voluntary and should directly relate to the buyer's genuine goals. Never use public commitment as a social pressure mechanism to prevent refund requests.
Application
How to Maximise the Reciprocity Effect
What Diminishes the Effect
The Traffic Hook and free content
The Traffic Hook's reciprocity effect is maximised when it delivers a specific, immediately usable result before any commercial relationship exists. The buyer's experience is: 'This person gave me something genuinely valuable for free. They earned the right to ask something of me.'
Offering a Traffic Hook that promises a specific result but delivers generic information. The reciprocity mechanism only activates when the value is genuinely experienced by the buyer as value.
Personal outreach and engagement
Responding personally to replies to emails, comments on content, and community questions — before the buyer has paid for anything. Each genuine interaction is a reciprocity-generating moment.
Automated responses to direct messages that are detectable as automated. Buyers who recognise automation where they expected a human response experience the reverse of reciprocity: they feel manipulated rather than valued.
Useful content in email sequences
Every email in the pre-offer sequence delivers something the buyer can act on immediately, without requiring a purchase. The sequence builds reciprocity across multiple interactions before the offer is presented.
Email sequences that are entirely promotional — that ask the buyer to buy without providing value in exchange. These sequences produce low reciprocity, high unsubscribe rates, and low conversion.
Standard Framing
Identity-Based Framing
Why the Difference Activates More
Application Context
'Sign up for this programme'
'Join the operators who have decided to build this systematically'
The identity framing invites the buyer to self-identify as someone who makes systematic decisions — an identity most operators aspire to. The standard framing is a transactional instruction.
CTAs on landing pages, email invitation language, webinar close
'Try this approach'
'This is what operators who are serious about building a sovereign business do'
The identity framing creates a referent group (operators who are serious) and positions the action as what members of that group do. Standard framing has no identity activation.
Email content, social media calls to action
'Complete the programme'
'Be the kind of operator who finishes what they start'
The completion framing activates identity consistency (I am someone who finishes) rather than the more effortful motivation of 'I should push through this.'
Programme onboarding, milestone emails, re-engagement campaigns
Priming Type
Application
Knowledge Business Example
The Design Principle
Achievement priming
Content immediately preceding an offer presentation uses specific, achievement-oriented language and imagery that activates the buyer's association of this operator with achievement.
The email or content piece immediately before the offer presentation includes a specific, detailed transformation story. The story primes the buyer's System 1 to evaluate the offer through the lens of 'this produces real transformation for people like me.'
The priming content must be specific and authentic. Generic aspirational content does not prime effectively because it does not activate specific memory associations.
Authority priming
The environment in which an offer is presented — the webinar platform, the email template, the sales page design — consistently signals credibility through specific, verifiable markers.
Specific number claims ('worked with 340 consultants'), specific result references ('7 of the last 10 achieved $5K/month'), specific institutional or media references if applicable. Each specific claim primes the System 1 credibility evaluation positively.
Authority priming through specificity is ethical and effective. Authority priming through false or exaggerated claims is deceptive and ultimately self-defeating.
Loss priming before a loss-framed offer
When an offer is positioned primarily around avoiding a cost or a loss, the content immediately preceding the offer activates the buyer's awareness of the cost they are currently incurring.
A content piece that helps the buyer calculate the specific monthly cost of their current approach is deployed 24–48 hours before the loss-framed offer email. The buyer arrives at the offer in a state of activated loss awareness.
Loss priming is ethical when it helps the buyer accurately see a real cost they may have been underestimating. It is unethical when it fabricates or inflates a loss to create anxiety.
THE BUYER JOURNEY NUDGE MAP
Deploying the Right Nudge at the Right Funnel Stage
A stage-by-stage architecture for applying behavioural design across the complete buyer journey
Funnel Stage
Primary Barrier
Most Effective Nudges for This Stage
Secondary Nudges
Design Output
Stage 1 — Awareness
(Cold audience encounter)
Relevance detection: the buyer needs to know in less than 3 seconds that this content is for someone like them.
Nudge 8 (Salience) — the most important relevance signal is visually and structurally the most prominent element.
Nudge 2 (Social Proof Specificity) — specific numbers confirm that real people in the target profile have engaged.
Nudge 12 (Environmental Priming) — the overall content environment signals credibility before the specific offer is encountered.
A hook that uses the most specific possible buyer language (Language Bank) as the first element the buyer sees or hears. A specific social proof statement visible without scrolling.
Stage 2 — Engagement
(Email subscriber)
Trust establishment: the buyer needs enough trust to invest time in the operator's content before any commercial engagement.
Nudge 10 (Reciprocity) — each email delivers specific, immediately usable value before any ask.
Nudge 9 (Commitment and Consistency) — micro-commitments build through the sequence.
Nudge 12 (Environmental Priming) — achievement and authority language throughout the sequence.
An email sequence where each email delivers a specific action item, the sequence builds a consistent logic, and the first direct offer is made after a minimum of 5 value-delivering emails.
Stage 3 — Consideration
(Problem Aware, evaluating solutions)
Category scepticism: the buyer has tried solutions before and needs to understand why this is different.
Nudge 3 (Loss Framing) — the cost of continuing with the current inadequate approach.
Nudge 4 (Anchoring) — the price of the offer relative to the cost of the problem and the cost of alternatives.
Nudge 2 (Social Proof Specificity) — specific results from specific people in the buyer's situation.
An offer presentation sequence that leads with the problem cost, establishes the price anchor, then presents the offer price. Specific testimonials from buyers who describe the same scepticism the audience likely feels.
Stage 4 — Purchase Decision
(Sales page or checkout)
Decision inertia and risk aversion: the buyer knows they want the result but fears the investment will not deliver.
Nudge 1 (Defaults) — the recommended tier is visually pre-selected or prominently marked.
Nudge 7 (Choice Architecture) — maximum three tiers with the recommended option clearly named.
Nudge 6 (Friction Reduction) — checkout is as simple as possible.
Nudge 5 (Scarcity/Urgency) — if genuine.
Nudge 11 (Identity-Based Framing) — the CTA is identity-framed, not transactional.
A checkout page with three tiers maximum, the recommended tier marked 'Most recommended for [specific profile]', minimal form fields, visible security signals, and a CTA that uses identity framing.
Stage 5 — Post-Purchase
(Onboarding and early engagement)
Implementation inertia: the buyer has paid but needs motivation to begin. The gap between purchase and first result is the highest dropout risk point.
Nudge 9 (Commitment and Consistency) — a public commitment to the 90-day goal in the community.
Nudge 1 (Defaults) — the first step is default-selected and explicit: 'Start here.'
Nudge 11 (Identity-Based Framing) — 'You are now the kind of operator who has decided to build this systematically.'
An onboarding sequence that includes a community goal-setting post, a 'Start Here' default path, and a quick win module that produces a specific, visible result within the first 7 days.
Stage 6 — Ascension
(Continuity and Premium)
Value perception and commitment: the buyer needs to clearly see what they received for their ongoing investment and to identify their next challenge as something the next rung addresses.
Nudge 3 (Loss Framing) — the cost of the next challenge left unsolved.
Nudge 9 (Consistency) — the milestone-triggered invitation is framed as consistent with the buyer's stated goals.
Nudge 5 (Scarcity) — cohort-limited premium offer with genuine capacity constraint.
Monthly value visibility communication ('Here is what you received this month'), milestone-triggered premium invitations framed around the buyer's next specific goal, not a general promotion.
FRICTION AUDIT PROTOCOL — Run quarterly or after any funnel change
STEP 1 — MAP THE TRANSITION POINTS
List every transition in the buyer journey:
T1: Visitor to email subscriber (opt-in page conversion)
T2: Subscriber to Traffic Hook consumer (download or view rate)
T3: Subscriber to email opener (Email 1 open rate)
T4: Email opener to click-through (Email CTA click rate)
T5: Click-through to sales page reader (scroll depth on sales page)
T6: Sales page reader to checkout initiator (add to cart / proceed to checkout rate)
T7: Checkout initiator to completed purchase (checkout completion rate)
T8: Purchaser to programme starter (first module completion within 7 days)
T9: Programme starter to programme completer (full programme completion rate)
T10: Completer to continuity member (continuity conversion rate)

STEP 2 — MEASURE EACH TRANSITION
Retrieve current rate for each transition from the relevant analytics source.
Create a simple table: Transition | Current Rate | Benchmark Rate | Gap
Benchmark rates (from the Hard Organic Proof Threshold SOP and industry standards):
T1 Opt-in rate: above 30% (warm traffic)
T3 Email 1 open rate: above 50%
T4 Email CTA click rate: above 5%
T7 Checkout completion: above 70% of checkout initiators
T8 First 7-day start rate: above 80% of purchasers
T9 Programme completion: above 40%
T10 Continuity conversion: above 30% of completers

STEP 3 — IDENTIFY THE HIGHEST-FRICTION TRANSITION
The highest-friction transition is the one with the largest gap between current rate and benchmark.
This is the single transition to focus the next 90 days of conversion improvement on.

STEP 4 — DIAGNOSE THE FRICTION SOURCE
For the highest-friction transition, apply the following diagnostic framework:
Is the friction cognitive? (too many decisions, too much information, unclear next step)
Fix: Nudge 6 (Friction Reduction) and Nudge 7 (Choice Architecture)
Is the friction emotional? (fear of regret, distrust, scepticism from prior failures)
Fix: Nudge 3 (Loss Framing), Nudge 4 (Anchoring), Nudge 2 (Social Proof Specificity)
Is the friction motivational? (not enough perceived urgency or salience of the benefit)
Fix: Nudge 5 (Genuine Scarcity/Urgency), Nudge 8 (Salience), Nudge 11 (Identity Framing)
Is the friction technical? (slow page load, broken links, confusing navigation)
Fix: Technical — not a nudge. Fix the technical issue before applying behavioural design.

STEP 5 — IMPLEMENT, MEASURE, ITERATE
Apply the diagnosed nudge to the highest-friction transition.
Measure the result over the next 30 days (or 200 data points, whichever comes first).
If the transition rate improves to within the benchmark range: move to the next highest-friction transition.
If the transition rate does not improve: re-diagnose. Was the friction type correctly identified?
Ethical Nudge
Manipulative Practice
The Distinguishing Test
Status in This SOP
Genuine cohort-limited scarcity with accurate remaining spots
False countdown timers that reset when they expire, or 'limited spots available' language on unlimited digital products
'If the buyer discovered after purchase that the scarcity was manufactured, would they feel deceived?' If yes: it is manipulation.
Not used. Countdown timers that reset, permanent 'limited availability' claims, and false sold-out signals are categorically excluded from this system.
Loss framing that accurately describes a real cost the buyer is incurring
Fabricated or exaggerated loss scenarios designed to produce anxiety rather than accurate risk awareness
'Does this loss actually occur for this buyer in this situation, or am I exaggerating to create urgency that does not reflect reality?' If fabricated: manipulation.
All loss framing in this SOP must be based on real, documented buyer experiences.
Genuine social proof with specific, accurate numbers
Fabricated testimonials, paid reviews, false result claims, undisclosed affiliates
'Is every specific claim in this social proof accurate and verifiable?'
Zero tolerance for fabricated social proof. The damage to long-term trust is structurally irreversible.
Reciprocity built on genuinely valuable free content
Reciprocity engineered through low-quality free content designed to create obligation without delivering value
'If the buyer looked back at the free value they received, would they agree it was genuinely useful, or would they feel they had been given something of little value in order to create a sense of obligation?'
All Traffic Hooks and free content must deliver specific, immediately usable value. Generic content does not qualify.
Identity framing that invites buyers to self-identify with their own genuine aspirations
Identity manipulation that exploits insecurity, fear of exclusion, or social status anxiety to pressure purchases
'Does this framing support the buyer's genuine values and aspirations, or does it exploit a vulnerability?'
Identity framing in this SOP is always aspirational and positive. Negative identity pressure ('people who fail at this are the ones who...') is not used.
AI BEHAVIOURAL DESIGN PROMPT FRAMEWORK
THE CONTEXT PROMPT (complete before any generation request)
'I am designing marketing content for [specific funnel stage from the Buyer Journey Nudge Map].
The primary barrier at this stage is: [specific barrier from the Nudge Map].
The buyer profile is: [from the Psychographic DNA Document].
The primary nudge I want to apply is: [Nudge 1–12 from this SOP].
All content must be based on real data: real buyer results, real testimonials, real social proof numbers.'

THE NUDGE-SPECIFIC GENERATION REQUEST

For Loss Framing (Nudge 3):
'Write three email opening paragraphs that frame the cost of [specific buyer's current situation] as a specific, ongoing monthly loss. Use this actual data: [real cost estimate from buyer research]. Do not exaggerate. The loss must be accurate and verifiable.'

For Anchoring (Nudge 4):
'Write a value stack section for a sales page for [specific offer at $X]. The value stack should reference genuine market prices for each component. Here are the components and their actual market prices: [list]. Do not inflate any of these figures.'

For Social Proof Specificity (Nudge 2):
'Rewrite these testimonials with specific numbers wherever the numbers are available and accurate. For each testimonial, identify the most specific, verifiable detail and make that the first sentence. Do not add numbers that are not in the original testimonials.'

For Identity-Based Framing (Nudge 11):
'Rewrite the following CTAs using identity-based framing rather than action-based framing. The buyer aspires to be [specific identity from Psychographic DNA Layer 4]. Each CTA should invite the buyer to act consistently with that identity, not to complete a transaction.'

THE ETHICAL FILTER
Before deploying any AI-generated behavioural copy:
Does any claim require verification I have not completed? (If yes: verify or remove the claim.)
Does any scarcity or urgency element reflect genuine constraints? (If no: remove it.)
Would I be comfortable if my best buyer read this and knew exactly what I was doing and why? (If no: revise.)
Field
Type
Notes
Deployment ID
Short text
Format: ND-[YYYY-MM]-[Seq]. e.g. ND-2026-09-007
Nudge Type
Single select
Nudges 1–12 from this SOP
Funnel Stage Deployed
Single select
Stage 1 Awareness / Stage 2 Engagement / Stage 3 Consideration / Stage 4 Purchase / Stage 5 Onboarding / Stage 6 Ascension
Specific Location
Short text
E.g. 'Email 3 of welcome sequence' or 'Sales page above-the-fold section'
Nudge Description
Long text
What specifically was done — the exact framing, default, social proof statement, or other implementation
Ethical Standard Met
Checkbox
Confirmed against the Ethical Boundaries Framework
Baseline Metric
Number
The transition rate before the nudge was applied
Post-Deployment Metric
Number
The transition rate after the nudge was applied (after 30-day measurement period)
Percentage Change
Formula
(Post – Baseline) / Baseline x 100
Result Verdict
Single select
Significant Improvement / Minor Improvement / No Change / Decline
Next Action
Short text
Whether to maintain, iterate, or remove
Date Deployed
Date
Date Measured
Date
Field
Type
Notes
Audit Date
Date
Transition Point
Single select
T1 through T10 from the Friction Audit Protocol
Current Rate
Number
Benchmark Rate
Number
Gap
Formula
Current – Benchmark
Friction Type
Single select
Cognitive / Emotional / Motivational / Technical
Recommended Nudge
Short text
Which nudge addresses this friction type
Action Taken
Long text
What was implemented
Post-Action Rate
Number
Priority Tier
Single select
Highest Friction (action now) / Medium Friction (next quarter) / Within Benchmark

Original Word tables and field relationships

Source table 1

The Ethical Distinction — Nudging vs ManipulationNudge theory carries an ethical obligation that this SOP takes seriously. A nudge is ethical when it makes it easier for people to make the choice that is in their own best interest, given their own values and goals. A nudge becomes manipulation when it makes it easier for people to make the choice that is in the operator's best interest at the expense of the buyer's. The test is simple: 'If this buyer knew exactly what I am doing here and why, would they feel helped or exploited?' Every nudge in this SOP passes that test. Any nudge that does not pass it is not in this SOP and should not be applied.

Source table 2

System 1 and System 2 — Why This Is Not Common SenseThe reason nudge theory requires a dedicated course rather than being intuitive is that it describes a layer of decision-making that operates below conscious awareness. Operators who are aware that they are making a decision — choosing a price point, deciding on a guarantee, selecting the order of offer elements — are using System 2 (deliberate, analytical thinking). But buyers in the moment of encounter with an offer are largely operating in System 1 (fast, automatic, pattern-matching thinking). What feels obvious to a System 2 designer is not what drives System 1 buyer behaviour. Nudge theory bridges the gap.

Source table 3

The Scale Effect — Why Small Changes in Choice Architecture Produce Large Differences in OutcomesNudge theory's most commercially significant finding: small changes to the environment in which choices are made produce disproportionately large changes in behaviour, often without the decision-maker being aware that their behaviour changed or why. A default option that is the operator's recommended choice converts at 2–3x the rate of the same option presented as an active choice. A social proof statement that provides a specific number ('joined by 1,247 consultants') converts at significantly higher rates than the same statement without the number. These are not persuasion differences — they are architecture differences. Architecture is changed once and works continuously.

Source table 4

Property	System 1 (Fast, Automatic)	System 2 (Slow, Deliberate)	Implication for Knowledge Business Marketing
Speed	Milliseconds to seconds. Processes information faster than conscious awareness.	Seconds to minutes. Requires active effort and attention allocation.	The buyer's first impression of an email subject line, a landing page headline, or an offer name is a System 1 response. The detailed rational evaluation of the offer's value is a System 2 response. Both must be satisfied but in sequence.
Effort	Effortless. Does not deplete cognitive resources.	Effortful. Depletes cognitive resources. Buyers in a cognitively depleted state (decision fatigue) revert more heavily to System 1.	Simplifying the choice architecture reduces cognitive load, enabling System 2 to engage more fully. An offer with too many options, too many decisions, or too much information produces System 1 avoidance rather than System 2 evaluation.
Error type	Associative errors: pattern-matching to the wrong category, influenced by irrelevant anchors, susceptible to framing effects.	Deliberate errors: motivated reasoning, confirmation bias, analysis paralysis.	System 1 errors are predictable and consistent across buyers. Knowing which associative errors are most likely in the purchase context allows the operator to design the context to prevent them.
Influence mechanisms	Defaults, social proof, salience, anchoring, loss framing, sequential presentation order, comparison context.	Arguments, evidence, testimonials, logical structure, data.	System 1 nudges operate on the architecture (defaults, sequence, framing). System 2 persuasion operates on the content (evidence, argument, social proof details). Both are required. System 1 nudges create the conditions for System 2 persuasion to be received.
Buying role	Makes the initial go/no-go decision at each stage of the funnel (open the email, read the sales page, reach the checkout, complete the purchase).	Evaluates the specific offer details once System 1 has decided to engage. Provides the post-hoc rationalisation for decisions already made.	Marketing that addresses only System 2 (rational arguments and feature lists) loses buyers at the System 1 gate before they engage with the argument. Marketing that addresses System 1 first, then System 2, converts at higher rates.

Source table 5

THE TWELVE CORE NUDGESApplied to Knowledge Business Buyer DecisionsEach nudge with definition, ethical application, worked example, and deployment context

Source table 6

Application	Worked Example	Deployment Context	Ethical Boundary
Offer tier default	On a pricing page with three tiers, the middle tier is pre-selected. The buyer can change to any tier but must actively choose to do so. The middle tier is the operator's recommended option. 'Most popular' badge on the recommended tier. The tier is visually highlighted and pre-selected if the checkout page uses a selector mechanism.	Checkout page, pricing page.	The default must be the operator's genuine recommendation for the typical buyer, not the most expensive option by default.
Programme onboarding sequence default	When new buyers access their programme dashboard, the recommended starting path is pre-selected. The 'Start Here' module is first in sequence, visually prominent, and marked as 'Recommended Starting Point.' Other navigation requires an active click away from the default path.	Programme delivery platform, onboarding email.	The default path must reflect the genuine best-practice completion sequence, not the sequence that most quickly exposes the buyer to upsell content.

Source table 7

Application	Specificity Upgrade	Behavioural Effect	Deployment Context
Subscriber or community count	'Over 1,000 people' → '1,247 knowledge business operators have joined this community'	The specific number is treated as evidence rather than claim. The descriptor ('knowledge business operators') activates the relevance detection system from Course 15.	Landing page, email signature, webinar registration page.
Testimonial framing	'This programme works' → 'In 63 days I went from zero clients to a full roster at $3,500/month'	The specific number (63 days, $3,500/month) converts the testimonial from a claim to a data point. Data points pass System 2's evidence standard as well as System 1's specificity pattern.	Sales page, email sequences, social media.
Result frequency	'Many clients achieve this result' → '7 of the last 10 operators who completed this programme reached $5K/month within 90 days'	The frequency framing ('7 of 10') activates the availability heuristic positively: the result seems common because a specific frequency is cited, rather than vague.	Sales page results section, webinar slides.

Source table 8

Gain Framing (Standard)	Loss Framing (Higher Activation)	Why the Difference Matters	Ethical Application Boundary
'This programme will help you sign new clients'	'Every month without a consistent client acquisition system, you are leaving approximately $3,000–$5,000 in revenue that competitors who have solved this problem are collecting instead'	Loss framing activates the pain of the current situation rather than the aspiration of the future state. For buyers who are already experiencing the pain of the problem, loss framing is more accurate to their lived experience.	Loss framing must accurately describe a real cost or risk the buyer faces. Fabricating or exaggerating losses is manipulation. The loss must be real, specific, and directly experienced by the target buyer.
'Develop a systematic approach to pricing'	'Every under-priced proposal you send is a negotiation you have already lost before the conversation starts'	Under-pricing is a loss the buyer is currently experiencing in every proposal. Framing it as a present, active loss rather than a future gain from solving it activates stronger immediate motivation.	The loss must be one the buyer has actually experienced, not a hypothetical future risk. Framing a loss the buyer does not experience as if it is universal is inaccurate.

Source table 9

Anchoring Application	How It Works	Knowledge Business Example	Ethical Standard
Price anchoring with the full value stack	Before presenting the programme price, build the full value stack: the monetary equivalent of all components if purchased separately.	'If you hired a coach to help with client acquisition ($500/hour, minimum 10 sessions = $5,000), a copywriter to create your positioning ($1,500), and a strategist to design your offer ($2,000), you would invest $8,500 to get these components separately. This programme is $997.'	The value stack must reflect genuine market prices for genuine components. Inflated values or fabricated comparisons manipulate rather than anchor.
Anchoring with the cost of the problem	Before presenting the price, establish the cost of the problem the offer solves.	'The average consultant who does not have a systematic client acquisition process takes 18 months to reach a sustainable income. That is 18 months of below-target income. At $3,000/month below target, that is $54,000 in delayed income. This programme is $997.'	The cost must be a realistic, evidence-based estimate, not a fabricated or extreme scenario.
Tier-first anchoring	When presenting multiple tiers, always begin with the highest-priced tier. This establishes the price range's upper boundary, making the mid-tier feel accessible rather than expensive.	Present the VIP tier ($2,997) first with its description. Then present the Standard tier ($997). Standard feels reasonable relative to the anchor.	The highest-priced tier must be a genuine, fully-described offering. Presenting a shell offer at a high price solely to anchor the real offer is deceptive.

Source table 10

Type	Genuine vs Manufactured	Ethical Standard	Worked Example
Cohort-limited enrolment	A programme that runs with a specific cohort in a live or community format genuinely cannot accept unlimited enrolments without degrading the experience quality. Cohort size limits are genuine scarcity.	State the specific cohort size and the specific reason for the limit. 'This cohort is limited to 25 members because that is the maximum that allows each member to receive personalised feedback within each live session.' The reason is the credibility signal.	'The March cohort is limited to 25 members. As of this email, 18 spots are filled. If you are planning to join, the enrolment closes on [date] or when the cohort fills, whichever comes first.'
Time-limited bonus	A bonus that is available for a defined period as part of a launch or a specific promotional event. The time limit is genuine because the bonus represents a specific delivery commitment (a live call, a live workshop, a personal review) that cannot be honoured after a specific date.	State the specific reason for the deadline. 'The live implementation call is scheduled for [date]. Enrolment closes 48 hours before the call so every member can be prepared.'	Never extend a 'final' deadline. An extended deadline tells the audience that the original deadline was false, retroactively undermining the credibility of every future deadline.
Price integrity, not false urgency	The price will not decrease after the promotional period. 'This is the launch price and it will increase' is legitimate if the price genuinely increases and stays higher. It is false if the 'launch price' becomes the permanent price.	Maintain price integrity. If the price is stated as a launch price, raise it after the launch and keep it raised.	Never present a permanently discounted price as a temporary one.

Source table 11

Friction Source	How to Reduce It	Conversion Impact	When Friction Should Be Preserved
Checkout page with too many fields	Reduce form fields to the minimum required for delivery and communication: name, email, payment. Remove fields that are useful for the operator's CRM but not required for the transaction.	Removing 3 non-essential form fields typically increases checkout completion rates by 10–25%.	Friction that serves as a quality signal (an application form before a premium offer, a qualification question before a high-ticket programme) is preserved because it communicates exclusivity and qualification.
Multiple pages between decision and payment	Where possible, reduce the steps between 'I want this' and 'I have paid.' Each additional page is a drop-off point.	Each additional page in the checkout flow reduces completion by 5–10% on average for standard e-commerce. Knowledge business buyers are typically more committed, but the same principle applies.	Payment plan options or order bump decisions that add a step should only be added if the revenue increase from the option exceeds the conversion loss from the additional friction.
Unclear or absent payment security indicators	SSL indicators, payment processor logos (Stripe, PayPal), and money-back guarantee statements reduce the perceived risk at the payment decision point.	The absence of trust indicators is a source of friction even when there is nothing actually wrong with the payment page. The buyer's pattern-recognition system reads 'no security indicators' as 'higher risk.'	None. Trust indicators should always be present on any payment page.
Complex pricing options	More than three pricing tiers produces choice overload (see Nudge 7 below). A buyer who cannot quickly determine which option is right for them defaults to inaction.	The classic 'jam study' (Iyengar and Lepper) showed that 24 options produced significantly lower purchase rates than 6 options. Three tiers is the knowledge business maximum for a standard offer.	When the offer genuinely serves distinct buyer profiles that require different configurations, more options may be necessary. The fix is not fewer options but better option naming that makes the right choice obvious for each buyer profile.

Source table 12

Principle	Application	Standard	Common Error
Maximum options per decision	Three options is the optimal number for most knowledge business purchase decisions. Two options sometimes feel too constrained. Four or more options reliably produce decision paralysis.	A pricing page has three tiers. The offer page has one core offer with one order bump. The value ladder has clear, named rungs.	Listing every possible way to work together on one page: the course, the coaching programme, the mastermind, the 1:1 engagement, the group programme, and the done-for-you option. The buyer cannot determine which is right for them without a significant research investment.
Naming the right choice	When there is a recommended choice, it should be explicitly named as the recommended choice rather than leaving the buyer to infer it.	'Most popular' or 'Recommended for [specific profile]' labelling on the appropriate tier removes ambiguity about which option is right for the majority of buyers.	Presenting all options neutrally with equal visual weight and no recommendation signal. The buyer is left to reason through the comparison without guidance.
Sequential vs simultaneous presentation	When the buyer must make multiple decisions, presenting them sequentially (one decision at a time) produces higher overall completion rates than presenting them simultaneously.	The checkout process: Step 1 is selecting the offer. Step 2 is adding the order bump. Step 3 is payment. Each step is a single decision.	A checkout page that simultaneously presents the tier selection, the order bump, the payment plan options, and the payment form. Multiple simultaneous decisions produce overwhelm.

Source table 13

Salience Application	How It Works	Knowledge Business Context	The Salience Hierarchy Rule
Visual hierarchy on sales and landing pages	The most important element — the headline on an opt-in page, the primary CTA on a sales page, the price on a checkout page — is visually the most prominent: largest text, most contrast, most whitespace surrounding it.	A sales page where the outcome headline is the largest text element on the page, the testimonials are the second most prominent, and the price and CTA are the third most prominent — following the sequence in which the buyer needs to receive information to convert.	The element that receives the most visual prominence is the element that should be the buyer's primary focus at that stage of the decision. Prioritise based on the buyer's information needs, not the operator's aesthetic preferences.
Content sequencing in emails and articles	The most important point is made first (the hook), not buried in the middle or saved for the end. Readers in a scan mode will absorb the first and last sentence of each paragraph. The middle is read only when the start and end have already justified the reading.	An email that opens with the most compelling single insight (not 'Dear [Name], I hope this finds you well') and closes with a clear, single CTA.	The sequence rule: most important first, second most important last, least important in the middle.

Source table 14

Application	How It Works	Knowledge Business Example	Ethical Note
Micro-commitments before the offer	Before presenting the Core Offer, the buyer is led through a sequence of micro-commitments: subscribing to the email list (small commitment), downloading the Traffic Hook (slightly larger), opening and engaging with the welcome sequence (further commitment), watching the webinar (significant commitment). Each step makes the next feel consistent.	The traffic hook → welcome email sequence → webinar → Core Offer structure is both a value-delivery sequence AND a commitment escalation sequence. The buyer's commitment level by the time they reach the offer is significantly higher than if the offer had been presented cold.	The consistency principle does not justify creating artificial commitments that mislead the buyer about what the escalation leads to. Micro-commitments should be consistent with the eventual offer direction — a buyer who subscribes for 'free productivity tips' who is then sold a $1,000 business development programme has been led through a commitment mismatch.
Public commitment in community settings	When community members publicly state their goals, they are more likely to pursue them because abandoning them requires an internal inconsistency.	Programme onboarding that asks new buyers to publicly state their 90-day goal in the community ('I am here to achieve [X] by [date]') increases programme completion rates because abandoning the programme means abandoning the publicly stated goal.	Public commitment should be voluntary and should directly relate to the buyer's genuine goals. Never use public commitment as a social pressure mechanism to prevent refund requests.

Source table 15

Application	How to Maximise the Reciprocity Effect	What Diminishes the Effect
The Traffic Hook and free content	The Traffic Hook's reciprocity effect is maximised when it delivers a specific, immediately usable result before any commercial relationship exists. The buyer's experience is: 'This person gave me something genuinely valuable for free. They earned the right to ask something of me.'	Offering a Traffic Hook that promises a specific result but delivers generic information. The reciprocity mechanism only activates when the value is genuinely experienced by the buyer as value.
Personal outreach and engagement	Responding personally to replies to emails, comments on content, and community questions — before the buyer has paid for anything. Each genuine interaction is a reciprocity-generating moment.	Automated responses to direct messages that are detectable as automated. Buyers who recognise automation where they expected a human response experience the reverse of reciprocity: they feel manipulated rather than valued.
Useful content in email sequences	Every email in the pre-offer sequence delivers something the buyer can act on immediately, without requiring a purchase. The sequence builds reciprocity across multiple interactions before the offer is presented.	Email sequences that are entirely promotional — that ask the buyer to buy without providing value in exchange. These sequences produce low reciprocity, high unsubscribe rates, and low conversion.

Source table 16

Standard Framing	Identity-Based Framing	Why the Difference Activates More	Application Context
'Sign up for this programme'	'Join the operators who have decided to build this systematically'	The identity framing invites the buyer to self-identify as someone who makes systematic decisions — an identity most operators aspire to. The standard framing is a transactional instruction.	CTAs on landing pages, email invitation language, webinar close
'Try this approach'	'This is what operators who are serious about building a sovereign business do'	The identity framing creates a referent group (operators who are serious) and positions the action as what members of that group do. Standard framing has no identity activation.	Email content, social media calls to action
'Complete the programme'	'Be the kind of operator who finishes what they start'	The completion framing activates identity consistency (I am someone who finishes) rather than the more effortful motivation of 'I should push through this.'	Programme onboarding, milestone emails, re-engagement campaigns

Source table 17

Priming Type	Application	Knowledge Business Example	The Design Principle
Achievement priming	Content immediately preceding an offer presentation uses specific, achievement-oriented language and imagery that activates the buyer's association of this operator with achievement.	The email or content piece immediately before the offer presentation includes a specific, detailed transformation story. The story primes the buyer's System 1 to evaluate the offer through the lens of 'this produces real transformation for people like me.'	The priming content must be specific and authentic. Generic aspirational content does not prime effectively because it does not activate specific memory associations.
Authority priming	The environment in which an offer is presented — the webinar platform, the email template, the sales page design — consistently signals credibility through specific, verifiable markers.	Specific number claims ('worked with 340 consultants'), specific result references ('7 of the last 10 achieved $5K/month'), specific institutional or media references if applicable. Each specific claim primes the System 1 credibility evaluation positively.	Authority priming through specificity is ethical and effective. Authority priming through false or exaggerated claims is deceptive and ultimately self-defeating.
Loss priming before a loss-framed offer	When an offer is positioned primarily around avoiding a cost or a loss, the content immediately preceding the offer activates the buyer's awareness of the cost they are currently incurring.	A content piece that helps the buyer calculate the specific monthly cost of their current approach is deployed 24–48 hours before the loss-framed offer email. The buyer arrives at the offer in a state of activated loss awareness.	Loss priming is ethical when it helps the buyer accurately see a real cost they may have been underestimating. It is unethical when it fabricates or inflates a loss to create anxiety.

Source table 18

THE BUYER JOURNEY NUDGE MAPDeploying the Right Nudge at the Right Funnel StageA stage-by-stage architecture for applying behavioural design across the complete buyer journey

Source table 19

Funnel Stage	Primary Barrier	Most Effective Nudges for This Stage	Secondary Nudges	Design Output
Stage 1 — Awareness(Cold audience encounter)	Relevance detection: the buyer needs to know in less than 3 seconds that this content is for someone like them.	Nudge 8 (Salience) — the most important relevance signal is visually and structurally the most prominent element.Nudge 2 (Social Proof Specificity) — specific numbers confirm that real people in the target profile have engaged.	Nudge 12 (Environmental Priming) — the overall content environment signals credibility before the specific offer is encountered.	A hook that uses the most specific possible buyer language (Language Bank) as the first element the buyer sees or hears. A specific social proof statement visible without scrolling.
Stage 2 — Engagement(Email subscriber)	Trust establishment: the buyer needs enough trust to invest time in the operator's content before any commercial engagement.	Nudge 10 (Reciprocity) — each email delivers specific, immediately usable value before any ask.Nudge 9 (Commitment and Consistency) — micro-commitments build through the sequence.	Nudge 12 (Environmental Priming) — achievement and authority language throughout the sequence.	An email sequence where each email delivers a specific action item, the sequence builds a consistent logic, and the first direct offer is made after a minimum of 5 value-delivering emails.
Stage 3 — Consideration(Problem Aware, evaluating solutions)	Category scepticism: the buyer has tried solutions before and needs to understand why this is different.	Nudge 3 (Loss Framing) — the cost of continuing with the current inadequate approach.Nudge 4 (Anchoring) — the price of the offer relative to the cost of the problem and the cost of alternatives.	Nudge 2 (Social Proof Specificity) — specific results from specific people in the buyer's situation.	An offer presentation sequence that leads with the problem cost, establishes the price anchor, then presents the offer price. Specific testimonials from buyers who describe the same scepticism the audience likely feels.
Stage 4 — Purchase Decision(Sales page or checkout)	Decision inertia and risk aversion: the buyer knows they want the result but fears the investment will not deliver.	Nudge 1 (Defaults) — the recommended tier is visually pre-selected or prominently marked.Nudge 7 (Choice Architecture) — maximum three tiers with the recommended option clearly named.Nudge 6 (Friction Reduction) — checkout is as simple as possible.	Nudge 5 (Scarcity/Urgency) — if genuine.Nudge 11 (Identity-Based Framing) — the CTA is identity-framed, not transactional.	A checkout page with three tiers maximum, the recommended tier marked 'Most recommended for [specific profile]', minimal form fields, visible security signals, and a CTA that uses identity framing.
Stage 5 — Post-Purchase(Onboarding and early engagement)	Implementation inertia: the buyer has paid but needs motivation to begin. The gap between purchase and first result is the highest dropout risk point.	Nudge 9 (Commitment and Consistency) — a public commitment to the 90-day goal in the community.Nudge 1 (Defaults) — the first step is default-selected and explicit: 'Start here.'	Nudge 11 (Identity-Based Framing) — 'You are now the kind of operator who has decided to build this systematically.'	An onboarding sequence that includes a community goal-setting post, a 'Start Here' default path, and a quick win module that produces a specific, visible result within the first 7 days.
Stage 6 — Ascension(Continuity and Premium)	Value perception and commitment: the buyer needs to clearly see what they received for their ongoing investment and to identify their next challenge as something the next rung addresses.	Nudge 3 (Loss Framing) — the cost of the next challenge left unsolved.Nudge 9 (Consistency) — the milestone-triggered invitation is framed as consistent with the buyer's stated goals.	Nudge 5 (Scarcity) — cohort-limited premium offer with genuine capacity constraint.	Monthly value visibility communication ('Here is what you received this month'), milestone-triggered premium invitations framed around the buyer's next specific goal, not a general promotion.

Source table 20

FRICTION AUDIT PROTOCOL — Run quarterly or after any funnel changeSTEP 1 — MAP THE TRANSITION POINTSList every transition in the buyer journey: T1: Visitor to email subscriber (opt-in page conversion) T2: Subscriber to Traffic Hook consumer (download or view rate) T3: Subscriber to email opener (Email 1 open rate) T4: Email opener to click-through (Email CTA click rate) T5: Click-through to sales page reader (scroll depth on sales page) T6: Sales page reader to checkout initiator (add to cart / proceed to checkout rate) T7: Checkout initiator to completed purchase (checkout completion rate) T8: Purchaser to programme starter (first module completion within 7 days) T9: Programme starter to programme completer (full programme completion rate) T10: Completer to continuity member (continuity conversion rate)STEP 2 — MEASURE EACH TRANSITIONRetrieve current rate for each transition from the relevant analytics source.Create a simple table: Transition | Current Rate | Benchmark Rate | GapBenchmark rates (from the Hard Organic Proof Threshold SOP and industry standards): T1 Opt-in rate: above 30% (warm traffic) T3 Email 1 open rate: above 50% T4 Email CTA click rate: above 5% T7 Checkout completion: above 70% of checkout initiators T8 First 7-day start rate: above 80% of purchasers T9 Programme completion: above 40% T10 Continuity conversion: above 30% of completersSTEP 3 — IDENTIFY THE HIGHEST-FRICTION TRANSITIONThe highest-friction transition is the one with the largest gap between current rate and benchmark.This is the single transition to focus the next 90 days of conversion improvement on.STEP 4 — DIAGNOSE THE FRICTION SOURCEFor the highest-friction transition, apply the following diagnostic framework: Is the friction cognitive? (too many decisions, too much information, unclear next step) Fix: Nudge 6 (Friction Reduction) and Nudge 7 (Choice Architecture) Is the friction emotional? (fear of regret, distrust, scepticism from prior failures) Fix: Nudge 3 (Loss Framing), Nudge 4 (Anchoring), Nudge 2 (Social Proof Specificity) Is the friction motivational? (not enough perceived urgency or salience of the benefit) Fix: Nudge 5 (Genuine Scarcity/Urgency), Nudge 8 (Salience), Nudge 11 (Identity Framing) Is the friction technical? (slow page load, broken links, confusing navigation) Fix: Technical — not a nudge. Fix the technical issue before applying behavioural design.STEP 5 — IMPLEMENT, MEASURE, ITERATEApply the diagnosed nudge to the highest-friction transition.Measure the result over the next 30 days (or 200 data points, whichever comes first).If the transition rate improves to within the benchmark range: move to the next highest-friction transition.If the transition rate does not improve: re-diagnose. Was the friction type correctly identified?

Source table 21

Ethical Nudge	Manipulative Practice	The Distinguishing Test	Status in This SOP
Genuine cohort-limited scarcity with accurate remaining spots	False countdown timers that reset when they expire, or 'limited spots available' language on unlimited digital products	'If the buyer discovered after purchase that the scarcity was manufactured, would they feel deceived?' If yes: it is manipulation.	Not used. Countdown timers that reset, permanent 'limited availability' claims, and false sold-out signals are categorically excluded from this system.
Loss framing that accurately describes a real cost the buyer is incurring	Fabricated or exaggerated loss scenarios designed to produce anxiety rather than accurate risk awareness	'Does this loss actually occur for this buyer in this situation, or am I exaggerating to create urgency that does not reflect reality?' If fabricated: manipulation.	All loss framing in this SOP must be based on real, documented buyer experiences.
Genuine social proof with specific, accurate numbers	Fabricated testimonials, paid reviews, false result claims, undisclosed affiliates	'Is every specific claim in this social proof accurate and verifiable?'	Zero tolerance for fabricated social proof. The damage to long-term trust is structurally irreversible.
Reciprocity built on genuinely valuable free content	Reciprocity engineered through low-quality free content designed to create obligation without delivering value	'If the buyer looked back at the free value they received, would they agree it was genuinely useful, or would they feel they had been given something of little value in order to create a sense of obligation?'	All Traffic Hooks and free content must deliver specific, immediately usable value. Generic content does not qualify.
Identity framing that invites buyers to self-identify with their own genuine aspirations	Identity manipulation that exploits insecurity, fear of exclusion, or social status anxiety to pressure purchases	'Does this framing support the buyer's genuine values and aspirations, or does it exploit a vulnerability?'	Identity framing in this SOP is always aspirational and positive. Negative identity pressure ('people who fail at this are the ones who...') is not used.

Source table 22

AI BEHAVIOURAL DESIGN PROMPT FRAMEWORKTHE CONTEXT PROMPT (complete before any generation request)'I am designing marketing content for [specific funnel stage from the Buyer Journey Nudge Map].The primary barrier at this stage is: [specific barrier from the Nudge Map].The buyer profile is: [from the Psychographic DNA Document].The primary nudge I want to apply is: [Nudge 1–12 from this SOP].All content must be based on real data: real buyer results, real testimonials, real social proof numbers.'THE NUDGE-SPECIFIC GENERATION REQUESTFor Loss Framing (Nudge 3):'Write three email opening paragraphs that frame the cost of [specific buyer's current situation] as a specific, ongoing monthly loss. Use this actual data: [real cost estimate from buyer research]. Do not exaggerate. The loss must be accurate and verifiable.'For Anchoring (Nudge 4):'Write a value stack section for a sales page for [specific offer at $X]. The value stack should reference genuine market prices for each component. Here are the components and their actual market prices: [list]. Do not inflate any of these figures.'For Social Proof Specificity (Nudge 2):'Rewrite these testimonials with specific numbers wherever the numbers are available and accurate. For each testimonial, identify the most specific, verifiable detail and make that the first sentence. Do not add numbers that are not in the original testimonials.'For Identity-Based Framing (Nudge 11):'Rewrite the following CTAs using identity-based framing rather than action-based framing. The buyer aspires to be [specific identity from Psychographic DNA Layer 4]. Each CTA should invite the buyer to act consistently with that identity, not to complete a transaction.'THE ETHICAL FILTERBefore deploying any AI-generated behavioural copy: Does any claim require verification I have not completed? (If yes: verify or remove the claim.) Does any scarcity or urgency element reflect genuine constraints? (If no: remove it.) Would I be comfortable if my best buyer read this and knew exactly what I was doing and why? (If no: revise.)

Source table 23

Field	Type	Notes
Deployment ID	Short text	Format: ND-[YYYY-MM]-[Seq]. e.g. ND-2026-09-007
Nudge Type	Single select	Nudges 1–12 from this SOP
Funnel Stage Deployed	Single select	Stage 1 Awareness / Stage 2 Engagement / Stage 3 Consideration / Stage 4 Purchase / Stage 5 Onboarding / Stage 6 Ascension
Specific Location	Short text	E.g. 'Email 3 of welcome sequence' or 'Sales page above-the-fold section'
Nudge Description	Long text	What specifically was done — the exact framing, default, social proof statement, or other implementation
Ethical Standard Met	Checkbox	Confirmed against the Ethical Boundaries Framework
Baseline Metric	Number	The transition rate before the nudge was applied
Post-Deployment Metric	Number	The transition rate after the nudge was applied (after 30-day measurement period)
Percentage Change	Formula	(Post – Baseline) / Baseline x 100
Result Verdict	Single select	Significant Improvement / Minor Improvement / No Change / Decline
Next Action	Short text	Whether to maintain, iterate, or remove
Date Deployed	Date
Date Measured	Date

Source table 24

Field	Type	Notes
Audit Date	Date
Transition Point	Single select	T1 through T10 from the Friction Audit Protocol
Current Rate	Number
Benchmark Rate	Number
Gap	Formula	Current – Benchmark
Friction Type	Single select	Cognitive / Emotional / Motivational / Technical
Recommended Nudge	Short text	Which nudge addresses this friction type
Action Taken	Long text	What was implemented
Post-Action Rate	Number
Priority Tier	Single select	Highest Friction (action now) / Medium Friction (next quarter) / Within Benchmark

Native Word text, including document headers and footers

word/document.xml
RISER NATION
MASTER OPERATING SYSTEM — COURSE 16 — TRACK 4: PERSUASION & MESSAGING
SOP — BEHAVIORAL LOGIC & NUDGE THEORY
The Complete System for Designing AI-Assisted Behavioral Marketing That Guides Customer Decisions Using Ethical Nudge Theory — The Dual-Process Decision Model, the Twelve Core Nudges, the Choice Architecture Design Protocol, the Buyer Journey Nudge Map, the Friction Audit, the Implementation Calendar, and the Ethical Boundaries Framework
Track 4: Persuasion & Messaging — Course 16 | 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview — Why Buyer Behaviour Is Not Driven by the Information You Provide
The rational model of buying assumes that people gather information, weigh options, calculate value, and make the optimal decision. This model is wrong in almost every commercially relevant context. Real buying decisions are made quickly, partially unconsciously, heavily influenced by context, framing, and comparison rather than by the objective merits of the options under consideration. A buyer who reads the same sales page twice — once when the price is framed as a cost and once when the same price is framed as an investment — makes a different decision. Not because their values changed. Because the framing changed the reference point against which the price was evaluated.
Nudge theory, developed by Richard Thaler and Cass Sunstein and grounded in decades of behavioural economics research, provides a systematic framework for understanding how the context in which a choice is presented influences which choice is made — without changing the options or restricting freedom. A nudge is any aspect of the choice architecture that predictably alters behaviour without forbidding options or significantly changing economic incentives. In a knowledge business, the choice architecture is everything: the sequence of emails, the structure of the sales page, the options available on the checkout page, the order in which programme modules are presented, the framing of the price, the presence or absence of a default option.
This SOP covers: the Dual-Process Decision Model that explains why nudges work, the twelve core nudges and how each applies specifically to knowledge business buyer decisions, the Choice Architecture Design Protocol for the full buyer journey, the Buyer Journey Nudge Map, the Friction Audit that identifies where buyers are dropping from the funnel, the AI-assisted behavioural marketing workflow, and the Ethical Boundaries Framework that distinguishes ethical nudging from manipulation.
The Ethical Distinction — Nudging vs Manipulation
Nudge theory carries an ethical obligation that this SOP takes seriously. A nudge is ethical when it makes it easier for people to make the choice that is in their own best interest, given their own values and goals. A nudge becomes manipulation when it makes it easier for people to make the choice that is in the operator's best interest at the expense of the buyer's. The test is simple: 'If this buyer knew exactly what I am doing here and why, would they feel helped or exploited?' Every nudge in this SOP passes that test. Any nudge that does not pass it is not in this SOP and should not be applied.
System 1 and System 2 — Why This Is Not Common Sense
The reason nudge theory requires a dedicated course rather than being intuitive is that it describes a layer of decision-making that operates below conscious awareness. Operators who are aware that they are making a decision — choosing a price point, deciding on a guarantee, selecting the order of offer elements — are using System 2 (deliberate, analytical thinking). But buyers in the moment of encounter with an offer are largely operating in System 1 (fast, automatic, pattern-matching thinking). What feels obvious to a System 2 designer is not what drives System 1 buyer behaviour. Nudge theory bridges the gap.
The Scale Effect — Why Small Changes in Choice Architecture Produce Large Differences in Outcomes
Nudge theory's most commercially significant finding: small changes to the environment in which choices are made produce disproportionately large changes in behaviour, often without the decision-maker being aware that their behaviour changed or why. A default option that is the operator's recommended choice converts at 2–3x the rate of the same option presented as an active choice. A social proof statement that provides a specific number ('joined by 1,247 consultants') converts at significantly higher rates than the same statement without the number. These are not persuasion differences — they are architecture differences. Architecture is changed once and works continuously.
The Dual-Process Decision Model
The theoretical foundation of behavioural economics and nudge theory is the Dual-Process Model of thinking, most accessibly described by Daniel Kahneman in Thinking, Fast and Slow. The model identifies two systems of cognitive processing that operate in parallel: System 1, which is fast, automatic, associative, and effortless, and System 2, which is slow, deliberate, analytical, and effortful.
Property
System 1 (Fast, Automatic)
System 2 (Slow, Deliberate)
Implication for Knowledge Business Marketing
Speed
Milliseconds to seconds. Processes information faster than conscious awareness.
Seconds to minutes. Requires active effort and attention allocation.
The buyer's first impression of an email subject line, a landing page headline, or an offer name is a System 1 response. The detailed rational evaluation of the offer's value is a System 2 response. Both must be satisfied but in sequence.
Effort
Effortless. Does not deplete cognitive resources.
Effortful. Depletes cognitive resources. Buyers in a cognitively depleted state (decision fatigue) revert more heavily to System 1.
Simplifying the choice architecture reduces cognitive load, enabling System 2 to engage more fully. An offer with too many options, too many decisions, or too much information produces System 1 avoidance rather than System 2 evaluation.
Error type
Associative errors: pattern-matching to the wrong category, influenced by irrelevant anchors, susceptible to framing effects.
Deliberate errors: motivated reasoning, confirmation bias, analysis paralysis.
System 1 errors are predictable and consistent across buyers. Knowing which associative errors are most likely in the purchase context allows the operator to design the context to prevent them.
Influence mechanisms
Defaults, social proof, salience, anchoring, loss framing, sequential presentation order, comparison context.
Arguments, evidence, testimonials, logical structure, data.
System 1 nudges operate on the architecture (defaults, sequence, framing). System 2 persuasion operates on the content (evidence, argument, social proof details). Both are required. System 1 nudges create the conditions for System 2 persuasion to be received.
Buying role
Makes the initial go/no-go decision at each stage of the funnel (open the email, read the sales page, reach the checkout, complete the purchase).
Evaluates the specific offer details once System 1 has decided to engage. Provides the post-hoc rationalisation for decisions already made.
Marketing that addresses only System 2 (rational arguments and feature lists) loses buyers at the System 1 gate before they engage with the argument. Marketing that addresses System 1 first, then System 2, converts at higher rates.
THE TWELVE CORE NUDGES
Applied to Knowledge Business Buyer Decisions
Each nudge with definition, ethical application, worked example, and deployment context
Each nudge below is presented with its behavioural science basis, its ethical application in a knowledge business context, a worked example from a knowledge business environment, and the specific funnel stage or marketing context where it is most effectively deployed.
Nudge 1 — Defaults
The most powerful single nudge in the catalogue. When a choice has a default option — the option that is selected if no active choice is made — the majority of people in most contexts accept the default. This is not laziness. It is the rational recognition that defaults are usually set to the recommended or most common option.
Application
Worked Example
Deployment Context
Ethical Boundary
Offer tier default
On a pricing page with three tiers, the middle tier is pre-selected. The buyer can change to any tier but must actively choose to do so. The middle tier is the operator's recommended option. 'Most popular' badge on the recommended tier. The tier is visually highlighted and pre-selected if the checkout page uses a selector mechanism.
Checkout page, pricing page.
The default must be the operator's genuine recommendation for the typical buyer, not the most expensive option by default.
Programme onboarding sequence default
When new buyers access their programme dashboard, the recommended starting path is pre-selected. The 'Start Here' module is first in sequence, visually prominent, and marked as 'Recommended Starting Point.' Other navigation requires an active click away from the default path.
Programme delivery platform, onboarding email.
The default path must reflect the genuine best-practice completion sequence, not the sequence that most quickly exposes the buyer to upsell content.
Nudge 2 — Social Proof Specificity
Social proof influences System 1 through the conformity heuristic: what most people like me do is probably the right thing to do. The nudge is not the presence of social proof — it is the specificity with which it is presented. A specific number is more persuasive than a vague claim because the brain's pattern-matching system treats specificity as a marker of credibility.
Application
Specificity Upgrade
Behavioural Effect
Deployment Context
Subscriber or community count
'Over 1,000 people' → '1,247 knowledge business operators have joined this community'
The specific number is treated as evidence rather than claim. The descriptor ('knowledge business operators') activates the relevance detection system from Course 15.
Landing page, email signature, webinar registration page.
Testimonial framing
'This programme works' → 'In 63 days I went from zero clients to a full roster at $3,500/month'
The specific number (63 days, $3,500/month) converts the testimonial from a claim to a data point. Data points pass System 2's evidence standard as well as System 1's specificity pattern.
Sales page, email sequences, social media.
Result frequency
'Many clients achieve this result' → '7 of the last 10 operators who completed this programme reached $5K/month within 90 days'
The frequency framing ('7 of 10') activates the availability heuristic positively: the result seems common because a specific frequency is cited, rather than vague.
Sales page results section, webinar slides.
Nudge 3 — Loss Framing (Loss Aversion)
Loss aversion is one of the most consistent findings in behavioural economics: the psychological pain of losing something is approximately twice as powerful as the pleasure of gaining an equivalent amount. Kahneman and Tversky's seminal research established this asymmetry across hundreds of decision contexts. In marketing, this means that framing a benefit as preventing a loss activates stronger motivation than framing the same benefit as delivering a gain.
Gain Framing (Standard)
Loss Framing (Higher Activation)
Why the Difference Matters
Ethical Application Boundary
'This programme will help you sign new clients'
'Every month without a consistent client acquisition system, you are leaving approximately $3,000–$5,000 in revenue that competitors who have solved this problem are collecting instead'
Loss framing activates the pain of the current situation rather than the aspiration of the future state. For buyers who are already experiencing the pain of the problem, loss framing is more accurate to their lived experience.
Loss framing must accurately describe a real cost or risk the buyer faces. Fabricating or exaggerating losses is manipulation. The loss must be real, specific, and directly experienced by the target buyer.
'Develop a systematic approach to pricing'
'Every under-priced proposal you send is a negotiation you have already lost before the conversation starts'
Under-pricing is a loss the buyer is currently experiencing in every proposal. Framing it as a present, active loss rather than a future gain from solving it activates stronger immediate motivation.
The loss must be one the buyer has actually experienced, not a hypothetical future risk. Framing a loss the buyer does not experience as if it is universal is inaccurate.
Nudge 4 — Anchoring
An anchor is the first number or value presented in a context that serves as the reference point against which all subsequent numbers are evaluated. The brain does not assess prices in absolute terms — it assesses them relative to the most salient prior reference point. Anchoring is one of the most replicable findings in cognitive psychology and one of the most consistently deployed nudges in high-converting sales contexts.
Anchoring Application
How It Works
Knowledge Business Example
Ethical Standard
Price anchoring with the full value stack
Before presenting the programme price, build the full value stack: the monetary equivalent of all components if purchased separately.
'If you hired a coach to help with client acquisition ($500/hour, minimum 10 sessions = $5,000), a copywriter to create your positioning ($1,500), and a strategist to design your offer ($2,000), you would invest $8,500 to get these components separately. This programme is $997.'
The value stack must reflect genuine market prices for genuine components. Inflated values or fabricated comparisons manipulate rather than anchor.
Anchoring with the cost of the problem
Before presenting the price, establish the cost of the problem the offer solves.
'The average consultant who does not have a systematic client acquisition process takes 18 months to reach a sustainable income. That is 18 months of below-target income. At $3,000/month below target, that is $54,000 in delayed income. This programme is $997.'
The cost must be a realistic, evidence-based estimate, not a fabricated or extreme scenario.
Tier-first anchoring
When presenting multiple tiers, always begin with the highest-priced tier. This establishes the price range's upper boundary, making the mid-tier feel accessible rather than expensive.
Present the VIP tier ($2,997) first with its description. Then present the Standard tier ($997). Standard feels reasonable relative to the anchor.
The highest-priced tier must be a genuine, fully-described offering. Presenting a shell offer at a high price solely to anchor the real offer is deceptive.
Nudge 5 — Scarcity and Urgency (Genuine)
Scarcity and urgency are among the most powerful and most abused nudges in marketing. When genuine, they activate the loss aversion mechanism: if this opportunity is genuinely limited, not taking it now is a loss. When manufactured, they activate scepticism and distrust that is disproportionately damaging to the buyer-operator relationship.
Type
Genuine vs Manufactured
Ethical Standard
Worked Example
Cohort-limited enrolment
A programme that runs with a specific cohort in a live or community format genuinely cannot accept unlimited enrolments without degrading the experience quality. Cohort size limits are genuine scarcity.
State the specific cohort size and the specific reason for the limit. 'This cohort is limited to 25 members because that is the maximum that allows each member to receive personalised feedback within each live session.' The reason is the credibility signal.
'The March cohort is limited to 25 members. As of this email, 18 spots are filled. If you are planning to join, the enrolment closes on [date] or when the cohort fills, whichever comes first.'
Time-limited bonus
A bonus that is available for a defined period as part of a launch or a specific promotional event. The time limit is genuine because the bonus represents a specific delivery commitment (a live call, a live workshop, a personal review) that cannot be honoured after a specific date.
State the specific reason for the deadline. 'The live implementation call is scheduled for [date]. Enrolment closes 48 hours before the call so every member can be prepared.'
Never extend a 'final' deadline. An extended deadline tells the audience that the original deadline was false, retroactively undermining the credibility of every future deadline.
Price integrity, not false urgency
The price will not decrease after the promotional period. 'This is the launch price and it will increase' is legitimate if the price genuinely increases and stays higher. It is false if the 'launch price' becomes the permanent price.
Maintain price integrity. If the price is stated as a launch price, raise it after the launch and keep it raised.
Never present a permanently discounted price as a temporary one.
Nudge 6 — Friction Reduction
Every step a buyer must take to complete a purchase — every field, every page, every click, every decision — is a friction point that reduces the probability of completing the purchase. System 1 avoids effort. Reducing friction is not about removing important steps. It is about removing unnecessary steps that add no information value and only add cognitive or physical effort.
Friction Source
How to Reduce It
Conversion Impact
When Friction Should Be Preserved
Checkout page with too many fields
Reduce form fields to the minimum required for delivery and communication: name, email, payment. Remove fields that are useful for the operator's CRM but not required for the transaction.
Removing 3 non-essential form fields typically increases checkout completion rates by 10–25%.
Friction that serves as a quality signal (an application form before a premium offer, a qualification question before a high-ticket programme) is preserved because it communicates exclusivity and qualification.
Multiple pages between decision and payment
Where possible, reduce the steps between 'I want this' and 'I have paid.' Each additional page is a drop-off point.
Each additional page in the checkout flow reduces completion by 5–10% on average for standard e-commerce. Knowledge business buyers are typically more committed, but the same principle applies.
Payment plan options or order bump decisions that add a step should only be added if the revenue increase from the option exceeds the conversion loss from the additional friction.
Unclear or absent payment security indicators
SSL indicators, payment processor logos (Stripe, PayPal), and money-back guarantee statements reduce the perceived risk at the payment decision point.
The absence of trust indicators is a source of friction even when there is nothing actually wrong with the payment page. The buyer's pattern-recognition system reads 'no security indicators' as 'higher risk.'
None. Trust indicators should always be present on any payment page.
Complex pricing options
More than three pricing tiers produces choice overload (see Nudge 7 below). A buyer who cannot quickly determine which option is right for them defaults to inaction.
The classic 'jam study' (Iyengar and Lepper) showed that 24 options produced significantly lower purchase rates than 6 options. Three tiers is the knowledge business maximum for a standard offer.
When the offer genuinely serves distinct buyer profiles that require different configurations, more options may be necessary. The fix is not fewer options but better option naming that makes the right choice obvious for each buyer profile.
Nudge 7 — Choice Architecture and the Paradox of Choice
Barry Schwartz's research on the Paradox of Choice established that beyond a moderate number of options, additional options do not produce greater buyer satisfaction — they produce greater buyer anxiety and lower purchase rates. The knowledge business operator who offers ten ways to work with them is not maximising access. They are maximising the probability that the buyer does not choose any of them.
Principle
Application
Standard
Common Error
Maximum options per decision
Three options is the optimal number for most knowledge business purchase decisions. Two options sometimes feel too constrained. Four or more options reliably produce decision paralysis.
A pricing page has three tiers. The offer page has one core offer with one order bump. The value ladder has clear, named rungs.
Listing every possible way to work together on one page: the course, the coaching programme, the mastermind, the 1:1 engagement, the group programme, and the done-for-you option. The buyer cannot determine which is right for them without a significant research investment.
Naming the right choice
When there is a recommended choice, it should be explicitly named as the recommended choice rather than leaving the buyer to infer it.
'Most popular' or 'Recommended for [specific profile]' labelling on the appropriate tier removes ambiguity about which option is right for the majority of buyers.
Presenting all options neutrally with equal visual weight and no recommendation signal. The buyer is left to reason through the comparison without guidance.
Sequential vs simultaneous presentation
When the buyer must make multiple decisions, presenting them sequentially (one decision at a time) produces higher overall completion rates than presenting them simultaneously.
The checkout process: Step 1 is selecting the offer. Step 2 is adding the order bump. Step 3 is payment. Each step is a single decision.
A checkout page that simultaneously presents the tier selection, the order bump, the payment plan options, and the payment form. Multiple simultaneous decisions produce overwhelm.
Nudge 8 — Salience and Attention Direction
Salience is the property of standing out from the surrounding context. The most salient element in a choice environment receives the most attention and is weighted most heavily in the decision. Operators who design visual and content hierarchy to make the most important elements the most salient are directing buyer attention to the information that most supports the purchase decision.
Salience Application
How It Works
Knowledge Business Context
The Salience Hierarchy Rule
Visual hierarchy on sales and landing pages
The most important element — the headline on an opt-in page, the primary CTA on a sales page, the price on a checkout page — is visually the most prominent: largest text, most contrast, most whitespace surrounding it.
A sales page where the outcome headline is the largest text element on the page, the testimonials are the second most prominent, and the price and CTA are the third most prominent — following the sequence in which the buyer needs to receive information to convert.
The element that receives the most visual prominence is the element that should be the buyer's primary focus at that stage of the decision. Prioritise based on the buyer's information needs, not the operator's aesthetic preferences.
Content sequencing in emails and articles
The most important point is made first (the hook), not buried in the middle or saved for the end. Readers in a scan mode will absorb the first and last sentence of each paragraph. The middle is read only when the start and end have already justified the reading.
An email that opens with the most compelling single insight (not 'Dear [Name], I hope this finds you well') and closes with a clear, single CTA.
The sequence rule: most important first, second most important last, least important in the middle.
Nudge 9 — Commitment and Consistency
Robert Cialdini's research on consistency established that people who have made a small prior commitment are significantly more likely to follow through with a larger subsequent commitment aligned with the prior one. This is not just social pressure — it is an internal cognitive consistency drive: having said or done X, we are motivated to act consistently with X.
Application
How It Works
Knowledge Business Example
Ethical Note
Micro-commitments before the offer
Before presenting the Core Offer, the buyer is led through a sequence of micro-commitments: subscribing to the email list (small commitment), downloading the Traffic Hook (slightly larger), opening and engaging with the welcome sequence (further commitment), watching the webinar (significant commitment). Each step makes the next feel consistent.
The traffic hook → welcome email sequence → webinar → Core Offer structure is both a value-delivery sequence AND a commitment escalation sequence. The buyer's commitment level by the time they reach the offer is significantly higher than if the offer had been presented cold.
The consistency principle does not justify creating artificial commitments that mislead the buyer about what the escalation leads to. Micro-commitments should be consistent with the eventual offer direction — a buyer who subscribes for 'free productivity tips' who is then sold a $1,000 business development programme has been led through a commitment mismatch.
Public commitment in community settings
When community members publicly state their goals, they are more likely to pursue them because abandoning them requires an internal inconsistency.
Programme onboarding that asks new buyers to publicly state their 90-day goal in the community ('I am here to achieve [X] by [date]') increases programme completion rates because abandoning the programme means abandoning the publicly stated goal.
Public commitment should be voluntary and should directly relate to the buyer's genuine goals. Never use public commitment as a social pressure mechanism to prevent refund requests.
Nudge 10 — Reciprocity
Cialdini's reciprocity principle establishes that people feel a genuine, non-commercial obligation to return value that has been given to them. When an operator provides genuine, specific, freely-given value before any request for commercial engagement, the buyer experiences a motivation to reciprocate. This is not manipulation — it is the mechanism that makes the Traffic Hook and content marketing commercially effective.
Application
How to Maximise the Reciprocity Effect
What Diminishes the Effect
The Traffic Hook and free content
The Traffic Hook's reciprocity effect is maximised when it delivers a specific, immediately usable result before any commercial relationship exists. The buyer's experience is: 'This person gave me something genuinely valuable for free. They earned the right to ask something of me.'
Offering a Traffic Hook that promises a specific result but delivers generic information. The reciprocity mechanism only activates when the value is genuinely experienced by the buyer as value.
Personal outreach and engagement
Responding personally to replies to emails, comments on content, and community questions — before the buyer has paid for anything. Each genuine interaction is a reciprocity-generating moment.
Automated responses to direct messages that are detectable as automated. Buyers who recognise automation where they expected a human response experience the reverse of reciprocity: they feel manipulated rather than valued.
Useful content in email sequences
Every email in the pre-offer sequence delivers something the buyer can act on immediately, without requiring a purchase. The sequence builds reciprocity across multiple interactions before the offer is presented.
Email sequences that are entirely promotional — that ask the buyer to buy without providing value in exchange. These sequences produce low reciprocity, high unsubscribe rates, and low conversion.
Nudge 11 — Identity-Based Framing
People act consistently with their identity. When a choice is framed in terms of the kind of person who makes that choice — rather than in terms of the consequences of making it — it activates the buyer's desire for identity consistency rather than their calculation of consequences. 'Voters are 15% more likely to vote when asked if they plan to be a voter rather than if they plan to vote' (Cialdini).
Standard Framing
Identity-Based Framing
Why the Difference Activates More
Application Context
'Sign up for this programme'
'Join the operators who have decided to build this systematically'
The identity framing invites the buyer to self-identify as someone who makes systematic decisions — an identity most operators aspire to. The standard framing is a transactional instruction.
CTAs on landing pages, email invitation language, webinar close
'Try this approach'
'This is what operators who are serious about building a sovereign business do'
The identity framing creates a referent group (operators who are serious) and positions the action as what members of that group do. Standard framing has no identity activation.
Email content, social media calls to action
'Complete the programme'
'Be the kind of operator who finishes what they start'
The completion framing activates identity consistency (I am someone who finishes) rather than the more effortful motivation of 'I should push through this.'
Programme onboarding, milestone emails, re-engagement campaigns
Nudge 12 — Environmental Priming
Environmental priming refers to the phenomenon where exposure to specific words, images, or concepts in the environment unconsciously activates related concepts and influences subsequent behaviour. In a marketing context, the language and imagery that precede an offer presentation prime the buyer's System 1 to evaluate the offer through a specific lens.
Priming Type
Application
Knowledge Business Example
The Design Principle
Achievement priming
Content immediately preceding an offer presentation uses specific, achievement-oriented language and imagery that activates the buyer's association of this operator with achievement.
The email or content piece immediately before the offer presentation includes a specific, detailed transformation story. The story primes the buyer's System 1 to evaluate the offer through the lens of 'this produces real transformation for people like me.'
The priming content must be specific and authentic. Generic aspirational content does not prime effectively because it does not activate specific memory associations.
Authority priming
The environment in which an offer is presented — the webinar platform, the email template, the sales page design — consistently signals credibility through specific, verifiable markers.
Specific number claims ('worked with 340 consultants'), specific result references ('7 of the last 10 achieved $5K/month'), specific institutional or media references if applicable. Each specific claim primes the System 1 credibility evaluation positively.
Authority priming through specificity is ethical and effective. Authority priming through false or exaggerated claims is deceptive and ultimately self-defeating.
Loss priming before a loss-framed offer
When an offer is positioned primarily around avoiding a cost or a loss, the content immediately preceding the offer activates the buyer's awareness of the cost they are currently incurring.
A content piece that helps the buyer calculate the specific monthly cost of their current approach is deployed 24–48 hours before the loss-framed offer email. The buyer arrives at the offer in a state of activated loss awareness.
Loss priming is ethical when it helps the buyer accurately see a real cost they may have been underestimating. It is unethical when it fabricates or inflates a loss to create anxiety.
THE BUYER JOURNEY NUDGE MAP
Deploying the Right Nudge at the Right Funnel Stage
A stage-by-stage architecture for applying behavioural design across the complete buyer journey
Each stage of the buyer journey has a specific primary barrier and a specific nudge that addresses that barrier most effectively. The Buyer Journey Nudge Map organises the twelve nudges by funnel stage so the operator can design the complete behavioural architecture of their marketing system rather than applying nudges opportunistically.
Funnel Stage
Primary Barrier
Most Effective Nudges for This Stage
Secondary Nudges
Design Output
Stage 1 — Awareness
(Cold audience encounter)
Relevance detection: the buyer needs to know in less than 3 seconds that this content is for someone like them.
Nudge 8 (Salience) — the most important relevance signal is visually and structurally the most prominent element.
Nudge 2 (Social Proof Specificity) — specific numbers confirm that real people in the target profile have engaged.
Nudge 12 (Environmental Priming) — the overall content environment signals credibility before the specific offer is encountered.
A hook that uses the most specific possible buyer language (Language Bank) as the first element the buyer sees or hears. A specific social proof statement visible without scrolling.
Stage 2 — Engagement
(Email subscriber)
Trust establishment: the buyer needs enough trust to invest time in the operator's content before any commercial engagement.
Nudge 10 (Reciprocity) — each email delivers specific, immediately usable value before any ask.
Nudge 9 (Commitment and Consistency) — micro-commitments build through the sequence.
Nudge 12 (Environmental Priming) — achievement and authority language throughout the sequence.
An email sequence where each email delivers a specific action item, the sequence builds a consistent logic, and the first direct offer is made after a minimum of 5 value-delivering emails.
Stage 3 — Consideration
(Problem Aware, evaluating solutions)
Category scepticism: the buyer has tried solutions before and needs to understand why this is different.
Nudge 3 (Loss Framing) — the cost of continuing with the current inadequate approach.
Nudge 4 (Anchoring) — the price of the offer relative to the cost of the problem and the cost of alternatives.
Nudge 2 (Social Proof Specificity) — specific results from specific people in the buyer's situation.
An offer presentation sequence that leads with the problem cost, establishes the price anchor, then presents the offer price. Specific testimonials from buyers who describe the same scepticism the audience likely feels.
Stage 4 — Purchase Decision
(Sales page or checkout)
Decision inertia and risk aversion: the buyer knows they want the result but fears the investment will not deliver.
Nudge 1 (Defaults) — the recommended tier is visually pre-selected or prominently marked.
Nudge 7 (Choice Architecture) — maximum three tiers with the recommended option clearly named.
Nudge 6 (Friction Reduction) — checkout is as simple as possible.
Nudge 5 (Scarcity/Urgency) — if genuine.
Nudge 11 (Identity-Based Framing) — the CTA is identity-framed, not transactional.
A checkout page with three tiers maximum, the recommended tier marked 'Most recommended for [specific profile]', minimal form fields, visible security signals, and a CTA that uses identity framing.
Stage 5 — Post-Purchase
(Onboarding and early engagement)
Implementation inertia: the buyer has paid but needs motivation to begin. The gap between purchase and first result is the highest dropout risk point.
Nudge 9 (Commitment and Consistency) — a public commitment to the 90-day goal in the community.
Nudge 1 (Defaults) — the first step is default-selected and explicit: 'Start here.'
Nudge 11 (Identity-Based Framing) — 'You are now the kind of operator who has decided to build this systematically.'
An onboarding sequence that includes a community goal-setting post, a 'Start Here' default path, and a quick win module that produces a specific, visible result within the first 7 days.
Stage 6 — Ascension
(Continuity and Premium)
Value perception and commitment: the buyer needs to clearly see what they received for their ongoing investment and to identify their next challenge as something the next rung addresses.
Nudge 3 (Loss Framing) — the cost of the next challenge left unsolved.
Nudge 9 (Consistency) — the milestone-triggered invitation is framed as consistent with the buyer's stated goals.
Nudge 5 (Scarcity) — cohort-limited premium offer with genuine capacity constraint.
Monthly value visibility communication ('Here is what you received this month'), milestone-triggered premium invitations framed around the buyer's next specific goal, not a general promotion.
The Friction Audit — Identifying Where Buyers Are Leaving the Funnel
The Friction Audit is a structured review of every transition point in the buyer journey — every place where a buyer who was engaged at Stage N did not progress to Stage N+1. Friction accumulates at transition points, and identifying which transition has the most friction is the most efficient conversion improvement activity available.
The Friction Audit Protocol
FRICTION AUDIT PROTOCOL — Run quarterly or after any funnel change
STEP 1 — MAP THE TRANSITION POINTS
List every transition in the buyer journey:
T1: Visitor to email subscriber (opt-in page conversion)
T2: Subscriber to Traffic Hook consumer (download or view rate)
T3: Subscriber to email opener (Email 1 open rate)
T4: Email opener to click-through (Email CTA click rate)
T5: Click-through to sales page reader (scroll depth on sales page)
T6: Sales page reader to checkout initiator (add to cart / proceed to checkout rate)
T7: Checkout initiator to completed purchase (checkout completion rate)
T8: Purchaser to programme starter (first module completion within 7 days)
T9: Programme starter to programme completer (full programme completion rate)
T10: Completer to continuity member (continuity conversion rate)
STEP 2 — MEASURE EACH TRANSITION
Retrieve current rate for each transition from the relevant analytics source.
Create a simple table: Transition | Current Rate | Benchmark Rate | Gap
Benchmark rates (from the Hard Organic Proof Threshold SOP and industry standards):
T1 Opt-in rate: above 30% (warm traffic)
T3 Email 1 open rate: above 50%
T4 Email CTA click rate: above 5%
T7 Checkout completion: above 70% of checkout initiators
T8 First 7-day start rate: above 80% of purchasers
T9 Programme completion: above 40%
T10 Continuity conversion: above 30% of completers
STEP 3 — IDENTIFY THE HIGHEST-FRICTION TRANSITION
The highest-friction transition is the one with the largest gap between current rate and benchmark.
This is the single transition to focus the next 90 days of conversion improvement on.
STEP 4 — DIAGNOSE THE FRICTION SOURCE
For the highest-friction transition, apply the following diagnostic framework:
Is the friction cognitive? (too many decisions, too much information, unclear next step)
Fix: Nudge 6 (Friction Reduction) and Nudge 7 (Choice Architecture)
Is the friction emotional? (fear of regret, distrust, scepticism from prior failures)
Fix: Nudge 3 (Loss Framing), Nudge 4 (Anchoring), Nudge 2 (Social Proof Specificity)
Is the friction motivational? (not enough perceived urgency or salience of the benefit)
Fix: Nudge 5 (Genuine Scarcity/Urgency), Nudge 8 (Salience), Nudge 11 (Identity Framing)
Is the friction technical? (slow page load, broken links, confusing navigation)
Fix: Technical — not a nudge. Fix the technical issue before applying behavioural design.
STEP 5 — IMPLEMENT, MEASURE, ITERATE
Apply the diagnosed nudge to the highest-friction transition.
Measure the result over the next 30 days (or 200 data points, whichever comes first).
If the transition rate improves to within the benchmark range: move to the next highest-friction transition.
If the transition rate does not improve: re-diagnose. Was the friction type correctly identified?
The Ethical Boundaries Framework
Every nudge in this SOP is designed for application in an ethically sound marketing system. The Ethical Boundaries Framework defines the specific standards that distinguish ethical nudging from manipulation in the knowledge business context, and the specific practices that are not permitted regardless of their conversion effectiveness.
Ethical Nudge
Manipulative Practice
The Distinguishing Test
Status in This SOP
Genuine cohort-limited scarcity with accurate remaining spots
False countdown timers that reset when they expire, or 'limited spots available' language on unlimited digital products
'If the buyer discovered after purchase that the scarcity was manufactured, would they feel deceived?' If yes: it is manipulation.
Not used. Countdown timers that reset, permanent 'limited availability' claims, and false sold-out signals are categorically excluded from this system.
Loss framing that accurately describes a real cost the buyer is incurring
Fabricated or exaggerated loss scenarios designed to produce anxiety rather than accurate risk awareness
'Does this loss actually occur for this buyer in this situation, or am I exaggerating to create urgency that does not reflect reality?' If fabricated: manipulation.
All loss framing in this SOP must be based on real, documented buyer experiences.
Genuine social proof with specific, accurate numbers
Fabricated testimonials, paid reviews, false result claims, undisclosed affiliates
'Is every specific claim in this social proof accurate and verifiable?'
Zero tolerance for fabricated social proof. The damage to long-term trust is structurally irreversible.
Reciprocity built on genuinely valuable free content
Reciprocity engineered through low-quality free content designed to create obligation without delivering value
'If the buyer looked back at the free value they received, would they agree it was genuinely useful, or would they feel they had been given something of little value in order to create a sense of obligation?'
All Traffic Hooks and free content must deliver specific, immediately usable value. Generic content does not qualify.
Identity framing that invites buyers to self-identify with their own genuine aspirations
Identity manipulation that exploits insecurity, fear of exclusion, or social status anxiety to pressure purchases
'Does this framing support the buyer's genuine values and aspirations, or does it exploit a vulnerability?'
Identity framing in this SOP is always aspirational and positive. Negative identity pressure ('people who fail at this are the ones who...') is not used.
The AI-Assisted Behavioural Design Workflow
AI tools can accelerate the application of nudge theory to marketing copy by rapidly generating multiple variants of the same content with different nudge approaches applied. The workflow below ensures AI output is grounded in the correct behavioural science framework rather than producing generic marketing copy.
AI BEHAVIOURAL DESIGN PROMPT FRAMEWORK
THE CONTEXT PROMPT (complete before any generation request)
'I am designing marketing content for [specific funnel stage from the Buyer Journey Nudge Map].
The primary barrier at this stage is: [specific barrier from the Nudge Map].
The buyer profile is: [from the Psychographic DNA Document].
The primary nudge I want to apply is: [Nudge 1–12 from this SOP].
All content must be based on real data: real buyer results, real testimonials, real social proof numbers.'
THE NUDGE-SPECIFIC GENERATION REQUEST
For Loss Framing (Nudge 3):
'Write three email opening paragraphs that frame the cost of [specific buyer's current situation] as a specific, ongoing monthly loss. Use this actual data: [real cost estimate from buyer research]. Do not exaggerate. The loss must be accurate and verifiable.'
For Anchoring (Nudge 4):
'Write a value stack section for a sales page for [specific offer at $X]. The value stack should reference genuine market prices for each component. Here are the components and their actual market prices: [list]. Do not inflate any of these figures.'
For Social Proof Specificity (Nudge 2):
'Rewrite these testimonials with specific numbers wherever the numbers are available and accurate. For each testimonial, identify the most specific, verifiable detail and make that the first sentence. Do not add numbers that are not in the original testimonials.'
For Identity-Based Framing (Nudge 11):
'Rewrite the following CTAs using identity-based framing rather than action-based framing. The buyer aspires to be [specific identity from Psychographic DNA Layer 4]. Each CTA should invite the buyer to act consistently with that identity, not to complete a transaction.'
THE ETHICAL FILTER
Before deploying any AI-generated behavioural copy:
Does any claim require verification I have not completed? (If yes: verify or remove the claim.)
Does any scarcity or urgency element reflect genuine constraints? (If no: remove it.)
Would I be comfortable if my best buyer read this and knew exactly what I was doing and why? (If no: revise.)
Airtable Schema — Behavioural Design Database
Table 1 — Nudge Deployment Records
Field
Type
Notes
Deployment ID
Short text
Format: ND-[YYYY-MM]-[Seq]. e.g. ND-2026-09-007
Nudge Type
Single select
Nudges 1–12 from this SOP
Funnel Stage Deployed
Single select
Stage 1 Awareness / Stage 2 Engagement / Stage 3 Consideration / Stage 4 Purchase / Stage 5 Onboarding / Stage 6 Ascension
Specific Location
Short text
E.g. 'Email 3 of welcome sequence' or 'Sales page above-the-fold section'
Nudge Description
Long text
What specifically was done — the exact framing, default, social proof statement, or other implementation
Ethical Standard Met
Checkbox
Confirmed against the Ethical Boundaries Framework
Baseline Metric
Number
The transition rate before the nudge was applied
Post-Deployment Metric
Number
The transition rate after the nudge was applied (after 30-day measurement period)
Percentage Change
Formula
(Post – Baseline) / Baseline x 100
Result Verdict
Single select
Significant Improvement / Minor Improvement / No Change / Decline
Next Action
Short text
Whether to maintain, iterate, or remove
Date Deployed
Date
Date Measured
Date
Table 2 — Friction Audit Records
Field
Type
Notes
Audit Date
Date
Transition Point
Single select
T1 through T10 from the Friction Audit Protocol
Current Rate
Number
Benchmark Rate
Number
Gap
Formula
Current – Benchmark
Friction Type
Single select
Cognitive / Emotional / Motivational / Technical
Recommended Nudge
Short text
Which nudge addresses this friction type
Action Taken
Long text
What was implemented
Post-Action Rate
Number
Priority Tier
Single select
Highest Friction (action now) / Medium Friction (next quarter) / Within Benchmark
Master Behavioral Logic & Nudge Theory Checklist
Understanding and Setup (Complete once, before applying nudges)
☐
Dual-Process Decision Model understood — can explain why System 1 nudges precede System 2 persuasion
☐
All twelve nudges reviewed — specific application to own niche identified for each
☐
Ethical Boundaries Framework reviewed — the distinction between ethical nudging and manipulation is clear
☐
Airtable Nudge Deployment Records and Friction Audit tables created
Funnel Architecture Design (Apply during Course 22 content build and sales page construction)
☐
Buyer Journey Nudge Map reviewed for each active funnel stage
☐
Primary barrier identified for each active stage
☐
Primary nudge assigned to each barrier
☐
Choice Architecture reviewed: maximum three tiers on any pricing page, recommended option clearly labelled
☐
Checkout friction audit: form fields reduced to minimum, security signals visible, single CTA
☐
Onboarding sequence: default 'Start Here' path set, community goal-setting post included
Quarterly Friction Audit
☐
All ten transition rates measured and recorded in Airtable
☐
Highest-friction transition identified
☐
Friction type diagnosed: cognitive, emotional, motivational, or technical
☐
Appropriate nudge or fix applied
☐
Baseline metric recorded before the change
☐
Post-deployment metric recorded 30 days later
Ongoing Nudge Application Quality Check
☐
All scarcity and urgency claims verified as genuine before every launch
☐
All social proof numbers verified as accurate before every deployment
☐
All loss framing reviewed against the Ethical Boundaries Framework
☐
AI-generated behavioural copy reviewed against the three-point ethical filter
RISER Nation Master Operating System | Behavioral Logic & Nudge Theory SOP | Course 16 | Version 1.0 | 2026 Edition
Track 4: Persuasion & Messaging — Course 16 | risernation.com

word/header1.xml
RISER Nation | Behavioral Logic & Nudge Theory SOP | Course 16 | V1.0

word/footer1.xml
Page
of

word/footnotes.xml

word/endnotes.xml

word/comments.xml

RISER-Dead-Offer-Resurrection-Playbook-SOP.docx

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

Working teaching draft. Source examples and policy assumptions require context; corrections and unresolved dependencies are identified in the script.

Diagnose before rebuilding or spending

This playbook asks whether an underperforming offer can be repaired while preserving useful buyer language, proof, methods and delivery assets. It connects to Product Kill Criteria, Forensic Audit Loop, Mechanism Test/Rename, Product Versioning and Beta Testing SOPs. Those are dependencies, not fully reproduced procedures. The source's claim that offers never die and only conditions change is a metaphor; demand can disappear or a business can become uneconomic. The useful discipline is to investigate before committing more resources.

D0928 — assigned source supporting this teaching point

Distinguish the three mortality states

The source calls an offer Declining when cold conversion is 0.5–1.4%, revenue is 15–40% below peak and refunds are stable or slightly rising; it routes this to weekly review and forensic diagnosis. Flatline combines cold conversion below 0.5% for 30 days, warm below 2% after a sequence and revenue below an operating minimum for 45 days. Retired means formally removed, with archived assets and no sales for 60 days. These are internal labels, not universal profitability tests. The checklist's simpler cold-threshold-or-retired trigger differs from the fuller definition; choose and document the governing rule.

D0928 — assigned source supporting this teaching point

Related source resources: RISER-Post-MVO-Forensic-Audit-Loop-SOP.docx — related SOP ·

Test the economics behind the threshold

The source says 0.3% cold conversion cannot be profitable at any viable traffic volume. That is not generally true: contribution per sale, acquisition cost, refunds and conversion together determine viability. A small conversion percentage can still support a high-margin offer with inexpensive qualified traffic. Use the source's thresholds as investigation triggers and compare actual economics; do not automatically retire an offer because one percentage crosses a line.

D0928 — assigned source supporting this teaching point

Cause 01: market-language drift

The described symptoms are buyer vocabulary diverging from the sales page, changed descriptions of the offer, a language-divergence health flag and reduced appearance of the mechanism in AI search. The proposed repair is fresh buyer-language mining, a copy rebuild and a rename only if justified, without necessarily changing delivery. The stated 70% recovery rate and 30-day deployment expectation lack supporting evidence here. Treat the cause as a hypothesis supported by interviews and behavior, not confirmed by a missing search citation.

D0928 — assigned source supporting this teaching point

Cause 02: mechanism saturation

The source describes a once-distinctive mechanism becoming familiar or copied, with weak excitement, failed distinctiveness, declining engagement and similar competitor names. It proposes a full naming test, new candidates and a winning T-1 excitement score of at least 7.5, recorded as a Minor CAT-M change. The claimed 75% recovery rate is unverified. A rename should clarify a real method, not conceal unchanged weaknesses or imply a new mechanism that does not exist.

D0928 — assigned source supporting this teaching point

Related source resources: RISER-10x-Mechanism-Test-Rename-Cadence-SOP.docx — related SOP ·

Cause 03: proof staleness

The source points to low D7 proof-specificity scores, irrelevant or old testimonials, weak engagement and retired-version evidence. It proposes current interviews, correctly matched proof and removal of obsolete claims. Its cause summary asks for at least three new metric-specific testimonials, while Pathway B later asks for five usable testimonials and two to three cases. Preserve those distinct targets without manufacturing proof to meet a quota. The stated 65% recovery rate is not substantiated.

D0928 — assigned source supporting this teaching point

Causes 04 and 05: positioning and buyer change

Positioning commoditization is described as three or more near-identical competitors, declining differentiation and crowded search results; the response is an evidenced underserved segment or problem and a Major repositioning. Avatar obsolescence describes buyers moving beyond the original problem, fewer new entrants or changed expectations of a solution; it calls for an adjacent/current buyer definition and revised positioning. The stated recovery rates are 55% and 50%, respectively, without evidence. Neither competitor presence nor a traffic decline alone proves the diagnosis.

D0928 — assigned source supporting this teaching point

Causes 06 and 07: delivery change or problem dissolution

Delivery obsolescence is described through lower completion, requests for interaction, competing formats and a slower first win. Its proposed repair is a capacity-tested change such as self-paced to cohort or coaching to supported implementation, treated as Major CAT-D; the claimed recovery rate is 45%. Problem dissolution means a platform, tool, market or rule change has removed the underlying need; the source generally routes it to asset harvesting rather than revival, with an unverified 25% rate. Do not rebuild a delivery model before confirming the problem and capacity.

D0928 — assigned source supporting this teaching point

Score the six triage criteria

T1 scores historical cold conversion at five points for above 1.5% for 30 days, three for above 0.8% but not 1.5%, and one for no sustained evidence. T2 scores rich, moderate or thin recoverable IP at 5/3/1, with five specific testimonials as an example of rich proof. T3 scores a clear cause, two treatable causes or unclear/conflicting causes at 5/3/1. T4 scores confirmed active, likely active or declining/dissolved need at 5/3/1. T5 scores feasibility within 30/60/90/more-than-90 days at 5/3/2/0. T6 scores clean retirement, resolved friction or serious public failure at 5/3/0, with zero overriding the total. These are source rubric choices, not calibrated probabilities.

D0928 — assigned source supporting this teaching point

Interpret the triage bands and resolve sequencing

The source's 24–30 band proceeds within seven days; 16–23 proceeds with a 45-day diagnostic deadline; 9–15 harvests assets only; 0–8 retires. Its qualitative weight labels do not change the stated unweighted total of 30. T3 asks for a diagnosis before the diagnosis phase, so an authored implementation should mark it provisional and rescore after evidence collection. A T6 reputational issue calls for resolving buyer harm and honoring obligations; a new name must not conceal unresolved problems. No retirement or rebranding is executed by this lesson.

D0928 — assigned source supporting this teaching point

Instrument 1: audit buyer-language divergence

The source samples ten exit interviews and 30 recent support tickets, tagging meaningful phrases absent from the sales page. Above 40% divergence points toward language drift; the mechanism appearing in fewer than three of ten interviews suggests language or saturation issues. The source then calls below 10% divergence zero and says it rules out both causes. That is too strong: familiar language does not disprove a saturated name. Define the phrase-count method, preserve the actual quotes and interpret the result alongside the other instruments.

D0928 — assigned source supporting this teaching point

Instrument 2: check excitement and distinctiveness

The informal mechanism test uses three avatar-matched people and focuses on T-1 excitement, T-3 curiosity and T-5 distinctiveness. Below 6.0 T-1 or two people recognizing a similar name is treated as a saturation signal; above 7.0 is treated as a rule-out. Elsewhere the source uses below 7.0 as a rename trigger and at least 7.5 for a new winner. Preserve their different stated purposes and do not turn three opinions into certainty. The actual full ten-part test remains a linked SOP dependency.

D0928 — assigned source supporting this teaching point

Related source resources: RISER-10x-Mechanism-Test-Rename-Cadence-SOP.docx — related SOP ·

Instruments 3 and 4: inspect proof and competitors

The proof audit flags more than half the displayed testimonials being retired-version or price-specific, or all current proof being older than 18 months. Relevance and accuracy matter alongside age. The competitor scan examines the five most visible offers, their promises, mechanism names, prices and delivery. Three similar competitors suggests commoditization; a dominant format shift suggests delivery change. A current proof library or stable competitor set reduces a hypothesis's support but does not conclusively rule out every related problem.

D0928 — assigned source supporting this teaching point

Instrument 5: confirm whether demand remains

The source checks three niche communities for problem posts in the last 90 days, asks ChatGPT, Perplexity and Gemini a buyer's problem question, and reviews a two-year Google Trends line. Fewer than ten posts plus a decline is treated as a dissolution signal; active discussion with different solutions suggests changed buyers or positioning. These are research prompts, not proof of market size. Search results vary, community counts depend on access and sampling, and Trends is normalized interest rather than absolute volume. Verify the underlying evidence and document alternative explanations.

D0928 — assigned source supporting this teaching point

Record the diagnosis and all six asset categories

The diagnosis record needs primary cause/evidence, secondary cause/evidence, ruled-out causes, pathway, timeline and a renewed viability decision. Inventory buyer phrases tagged PAIN-ACUTE, PAIN-CHRONIC, DESIRE-HIDDEN and OBJECTION; current/retired proof; methodology separate from its name; platform/modules/worksheets/emails/onboarding; wrong-fit/refund/exit data; and historical performance by traffic, copy and guarantee version. Reuse only assets that remain accurate and appropriate. The source's 12–18-month intelligence value is an estimate, not a reason to treat old language as current.

D0928 — assigned source supporting this teaching point

Define the improvement gate before the repair

One passage requires material improvement in at least two of D1 promise clarity, D2 mechanism believability and D7 proof specificity. Another requires at least one point on every scorecard dimension implicated in the diagnosis, with D1 also called Dream Outcome Clarity. Preserve both requirements and decide how they will be evaluated before rebuilding. Score changes need a consistent rubric and evidence; they are not automatically objective merely because they are numerical.

D0928 — assigned source supporting this teaching point

Related source resources: RISER-Offer-Scorecard-SOP.docx — related SOP ·

Pathway A: refresh language and mechanism

The seven steps are: mine six months of buyer language on Days 1–5; test the old name on Days 3–7; if warranted, use all six referenced naming methods to generate at least 15 candidates, shortlist five and test for a 7.5+ T-1 winner on Days 6–14; rebuild lead, mechanism, stack, guarantee and FAQ from the new brief on Days 10–21; update mechanism emails Days 8–10 of the 14-day sequence and all old wording on Days 14–21; sync assets and file Minor CAT-M/CAT-C on Days 21–28; then run a warm-only 14-day test on Days 28–42. The nominal 21–30-day heading excludes part of this sequence. No six naming methods are invented from their absent reference.

D0928 — assigned source supporting this teaching point

Related source resources: RISER-10x-Mechanism-Test-Rename-Cadence-SOP.docx — related SOP ·

Pathway B: rebuild proof and the stack

The seven steps are: interview the top-result 20% of prior buyers on Days 1–14 for at least five usable testimonials; audit version relevance on Days 7–10; build two to three Avatar→Problem→Attempt→Discovery→Result cases on Days 10–21; review bonuses below a Buyer Utility Score of 5.0 and address newly evidenced sub-problems on Days 10–21; rebuild proof matched to objections on Days 21–30; sync and log on Days 28–35; and observe a warm relaunch on Days 35–65. The heading says 30–45 days, while the full sequence reaches 65. Testimonials must be accurate and permissioned, not generated to satisfy targets.

D0928 — assigned source supporting this teaching point

Related source resources: RISER-Bonus-Discipline-Audit-SOP.docx — related SOP ·

Pathway C: reposition for a current buyer

Map competitor avatar/promise/mechanism/price and evidenced gaps on Days 1–10. Define a precise buyer and job-to-be-done on Days 7–14, illustrated by a B2B SaaS company at $1M–$5M ARR preparing for Series A. On Days 10–21 decide which delivery components survive, change or retire; on Days 14–21 test a suitable name; on Days 21–40 rebuild the copy and email brief; on Days 28–40 define wrong-fit boundaries; on Days 40–60 beta with five to ten appropriate buyers; and on Days 58–65 deploy a Major CAT-M version with a change record. The 45–60-day heading understates the final steps. A precise avatar is a hypothesis until validated.

D0928 — assigned source supporting this teaching point

Pathway D: upgrade delivery within capacity

Test fulfillment capacity, per-buyer workload and schedule on Days 1–14. Define each component's format, owner and cadence on Days 7–14; estimate a supportable price on Days 7–21; prototype platform, onboarding, live/community/accountability elements on Days 21–50 with two or three testers; design suitable guarantee terms on Days 28–45; foreground delivery in copy on Days 35–55; test a founding-member commitment on Days 50–65; and complete beta/build/launch as Major CAT-D on Days 60–90. The source's fewer-than-five commitments from 500 engaged subscribers is an internal gate. Its pre-sell-before-full-build rule needs the earlier platform work clearly bounded as a prototype. Neither a price rise nor a stronger guarantee is automatically justified by a new format.

D0928 — assigned source supporting this teaching point

Related source resources: RISER-Fulfilment-Stress-Test-SOP.docx — related SOP ·

Tell the relaunch story with accountable change

The new-chapter framing should briefly acknowledge the old limitation, explain what was learned and show what changed with evidence. It must not erase a buyer's history or obligations under the original purchase. The source suggests interviewing five to ten non-buyers 21–30 days before relaunch, notifying existing buyers 14 days ahead, and opening a waitlist seven to fourteen days ahead with a target of 50 signups. These are planning targets and proposed communications, not actions taken by this lesson.

D0928 — assigned source supporting this teaching point

Outline all five relaunch emails

Day 1 tells the honest pivot story, with source targets above 30% opens and 2% replies. Day 2 introduces the mechanism, current proof and guarantee. Day 3 compares five or six concrete changes: delivery, name, guarantee, promised result, support and price. Day 5 addresses the top three researched objections with validation, reframe and evidence. Day 7 states the actual close terms. Do not invent a returning-buyer case or a deadline. The source's Epiphany Bridge attribution is a proposed storytelling lens, not evidence that the relaunch will convert.

D0928 — assigned source supporting this teaching point

Reconcile the soft-relaunch gates

The general gate asks for more than 3% of sequence recipients purchasing, refunds below 8% in 14 days, more than 60% completing Module 1 within 72 hours, and at least one metric-specific testimonial per ten buyers. Pathways A and B instead target more than 5% warm conversion, and B asks for a 20% testimonial collection rate over 30 days. Define which gate applies and keep 7-day versus 14-day sequence cohorts distinct. None guarantees cold-traffic economics. Proof collection must remain voluntary and truthful.

D0928 — assigned source supporting this teaching point

Monitor the four post-relaunch periods

Weeks 1–2 watch warm conversion below 2% or refunds above 10%, prompting investigation before expansion. Weeks 3–4 inspect completion and first-module dropout, with a source alert below 35% completion in the first 14 days; define which completion measure is meant. Weeks 5–8 inspect cold conversion below 0.8% after more than 200 unique visitors, without automatically increasing spend. Weeks 9–12 review three consecutive weekly revenue declines, NPS below 20 and a scorecard below 40 at Day 90. These are internal review signals, not proof of a root cause or statistically sufficient samples.

D0928 — assigned source supporting this teaching point

Related source resources: RISER-Offer-Scorecard-SOP.docx — related SOP ·

Declare success, continuation or failure consistently

The final success table requires cold conversion above 1% and at least the prior peak, warm above 5% and at least its prior peak, refunds below 8%, completion above 45%, and scorecard above 45/75 for at least 30 consecutive days. The introduction's three-of-five prior-peak wording differs; retain the stricter final definition as the source's explicit success table while flagging the discrepancy. At Day 90, three or four improving criteria can extend monitoring to Day 120; a flat trend calls for secondary-cause review. Fewer than three with no positive trend routes to the Kill Criteria SOP. Improvement alone does not prove the diagnosis was correct.

D0928 — assigned source supporting this teaching point

Preserve the learning after the decision

After success, the source proposes price testing, monthly scorecards and quarterly mechanism checks. After failure, it proposes intelligence extraction before considering another attempt; the checklist's absolute no-second-attempt wording is stronger than the body's no-immediate-second-attempt rule. Record the evidence and unresolved obligations before deciding. Preserve updated buyer language, wrong-fit profiles, competition and category findings, and the single diagnostic lesson that should change a future offer design.

D0928 — assigned source supporting this teaching point

Build the full Resurrection Record

The schema includes ID and linked offer; mortality state; triage score/decision; primary/secondary cause and confidence; pathway; start/relaunch dates and duration; final-old and Day30-new scorecards plus delta; old/new cold and warm conversion; old/new refunds; new cohort completion; outcome; estimated annual revenue; recovered IP; key diagnostic finding; market intelligence; buyer-language updates; linked negative avatars; mechanism-name history and test scores; linked version change; and next review date. An autonumber alone cannot produce the proposed RES-[Offer]-[YYYY-MM] string without a separate display field. The field called Next Quarterly Review instructs a Day30 scorecard, so distinguish monthly and quarterly dates. Estimates and confidence labels remain assumptions.

D0928 — assigned source supporting this teaching point

Submit a repair decision rather than a promise

Prepare a mortality/economics assessment, provisional and revised triage, all five diagnostic results, six-category asset inventory, selected pathway with reconciled schedule, acceptance gate, relaunch draft, 90-day measurement plan and complete record. Preserve every threshold as a source rule under review. Keep unverified dependencies open and do not treat a revised name, fresh copy or a warm launch spike as completed resurrection.

D0928 — assigned source supporting this teaching point

Apply the agreed marketing lenses

D0928 — assigned source supporting this teaching point · ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Complete original source export

RISER NATION
MASTER OPERATING SYSTEM
SOP — DEAD OFFER RESURRECTION PLAYBOOK
The Complete Diagnostic and Relaunch System for Offers That Have Stopped Converting — Without Wasting Another Dollar on a Broken Vehicle
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
A dead offer is not always a failed offer. In most cases, it is a misdiagnosed one. Operators who kill an offer the moment it stops converting are destroying IP assets — buyer language databases, proof libraries, mechanism frameworks, and delivery infrastructure — that took months to build and represent genuine market intelligence. The offer that converted well for six months and then stopped is not broken. Something changed. Finding what changed, why it changed, and whether that change is reversible is the entire purpose of this SOP.
The Dead Offer Resurrection Playbook is the structured protocol for diagnosing why an offer stopped performing and determining whether it can be revived — and if so, precisely how. It distinguishes between the seven root causes of offer death, each of which requires a completely different resurrection approach. It defines the triage system for prioritising which dead offers are worth resurrecting. It provides the four resurrection pathways matched to specific cause types. And it gives the relaunch protocol that ensures the resurrected offer launches into the market as a new, differentiated product rather than a recycled version of something the market already dismissed.
This SOP connects directly to the Product Kill Criteria SOP (which defines when to kill an offer), the Forensic Audit Loop SOP (which provides the deep diagnostic tools this playbook draws from), the 10× Mechanism Test & Rename Cadence SOP (which governs mechanism refreshes), the Product Versioning SOP (which governs how the resurrected offer is logged and tracked), and the Beta Testing Methodology SOP (which governs the validation protocol before any resurrected offer re-enters the market publicly).
Defining a Dead Offer: The Three Mortality States
Before applying the resurrection protocol, the offer must be correctly classified. Not all underperforming offers are dead. An offer that is merely underperforming may need optimisation, not resurrection. An offer that is genuinely dead requires the full protocol. Using the resurrection playbook on an underperforming-but-alive offer wastes 60–90 days of diagnostic time.
The Seven Causes of Offer Death
Every dead offer died for one of seven reasons. Identifying the correct cause is the only diagnostic step that matters — because each cause requires a fundamentally different resurrection pathway. Applying the wrong pathway to the correct diagnosis produces no improvement. Applying the right pathway to the wrong diagnosis produces a relaunched offer that dies again, faster, with additional sunk cost.
The Triage Principle
Not every dead offer deserves resurrection. Operator time and attention are finite. The triage protocol allocates resurrection effort to the offers with the highest probability of successful revival and the highest expected return on resurrection investment. An offer that scores below the triage threshold is retired permanently — its assets are harvested and its intelligence feeds the next offer rather than a resurrection attempt.
The Six Triage Criteria
Triage Score Interpretation
The Diagnosis Sequence
The root cause is identified by running five diagnostic instruments in sequence. The first instrument to return a positive result identifies the likely primary cause. Run all five regardless — secondary causes often exist and must be identified to prevent the resurrection from solving only the primary cause while the secondary cause kills it again.
Diagnostic Instrument 1 — The Buyer Language Divergence Audit
Pull the most recent 10 exit interview transcripts and the most recent 30 support tickets. Compare the vocabulary to the current sales page copy word-by-word. Tag every phrase in the interviews/tickets that does not appear anywhere on the sales page.
Diagnostic Instrument 2 — The 10× Mechanism Health Check
Run an informal version of the 10× Mechanism Test (Phase 2 of the 10× Mechanism Test & Rename Cadence SOP) with three avatar-matched individuals. Focus specifically on T-1 (Excitement), T-3 (Curiosity Trigger), and T-5 (Distinctiveness).
Diagnostic Instrument 3 — The Proof Audit
Open the Testimonial Version Registry (Product Versioning SOP). Count the number of testimonials currently on the sales page with each status.
Diagnostic Instrument 4 — The Competitor Landscape Scan
Run a competitor scan across the five most visible competitors in the offer category. Specifically: what promises are they making, what mechanisms are they naming, and what delivery formats are they offering?
Diagnostic Instrument 5 — The Market Existence Confirmation
Run three market existence checks to confirm the underlying problem is still active and the avatar still exists in sufficient numbers.
Reddit/Forum Scan: Search the top 3 communities in the niche for posts about the problem the offer addresses. Count posts from the last 90 days. If fewer than 10 posts in 90 days: the problem is declining in visibility.
AI Search Check: Ask ChatGPT, Perplexity, and Gemini the question a buyer at maximum problem awareness would ask ('How do I [problem the offer solves]?'). Review whether the responses suggest the problem is still active and unsolved, or whether they cite new solutions that effectively render the offer obsolete.
Google Trends Check: Run the primary keyword representing the problem on Google Trends. Look at the 2-year trend line. Declining search volume for the problem itself (not just for the offer) is a Cause 07 indicator.
The Diagnosis Confirmation
After running all five instruments, complete the diagnosis confirmation:
The Asset Inventory
Before choosing the resurrection pathway, take a complete inventory of what survives from the original offer. The resurrection ROI depends entirely on how much of the original IP can be preserved and reused — versus how much must be rebuilt from scratch.
The Minimum Viability Standard for Resurrection
A resurrection is only viable if the resurrected offer is materially better than the original in at least two of the three core dimensions: promise clarity (D1), mechanism believability (D2), and social proof specificity (D7) from the Offer Scorecard. Resurrecting an offer that is not materially improved from its final state re-enters the same market with the same weaknesses that killed it.
Each resurrection pathway is designed for one or more specific cause types. Do not use a pathway for a cause it was not designed for — the effort will produce an improved offer that still dies for the original cause.
Pathway A — The Language and Mechanism Refresh
Pathway B — The Proof and Stack Rebuild
Pathway C — The Repositioning and Avatar Pivot
Pathway D — The Delivery Model Upgrade
The Memory Reset Principle
A resurrected offer cannot be relaunched as 'the old offer, now fixed.' The market has a memory. Buyers who encountered the original offer and did not purchase — or purchased and were disappointed — have formed associations with the offer name, the mechanism name, and the operator's positioning that a simple 'we've improved it' email will not override. The relaunch must activate a distinct 'new chapter' frame.
The Relaunch Sequence
The Soft Relaunch Gate
Before any cold paid traffic is added to the relaunched offer, the warm relaunch must meet the minimum performance gate. Cold traffic on a relaunched offer that has not yet demonstrated warm conversion viability is the same mistake as cold traffic on the original dead offer.
The 90-Day Post-Resurrection Watch
A resurrection is not complete at relaunch. It is complete when the resurrected offer has demonstrated sustained performance across 90 days of real-world operation — matching or exceeding its prior peak performance on at least three of five key metrics. The 90-day window is the minimum window to confirm that the resurrection solved the root cause rather than producing a temporary performance spike from launch novelty.
The Resurrection Success Criteria
The resurrection is declared successful when all five criteria are met simultaneously for a minimum of 30 consecutive days:
When to Declare the Resurrection Complete vs Re-Trigger the Kill Criteria
Why the Record Is as Valuable as the Resurrection
The process of resurrecting a dead offer generates a category of market intelligence that a successfully-running offer never produces. The dead offer has failed, which means the market has communicated clearly what does not work. It has been compared to alternatives, which means competitive intelligence was accumulated. It has been diagnosed against seven causes, which means the operator now has a documented theory of why offers die in this specific market. All of that intelligence must be captured before the resurrection process closes — because it directly informs every future offer design decision.
Table — Resurrection Record
One record per completed resurrection process. File in Airtable under Resurrection Records.
Master Dead Offer Resurrection Checklist
Pre-Triage
☐ Confirm the offer has crossed the Flatline threshold (cold conversion below 0.5% for 30+ days OR formally retired)
☐ Pull the final Offer Scorecard score for the dead offer — document as the baseline for comparison
☐ Pull all asset inventory: buyer language database, proof library, mechanism framework, delivery infrastructure, negative avatar data, traffic and conversion history
Phase 1 — Triage
☐ Score all six triage criteria (T1–T6)
☐ Calculate total triage score out of 30
☐ Confirm triage decision: High Priority / Conditional / Asset Harvest / Permanent Retirement
☐ If T6 scored 0 (auto-disqualify due to public failure): confirm permanent retirement. No resurrection pathway is viable.
☐ If Triage Score 9–15: run Post-Kill Intelligence Extraction Protocol only. Do not proceed to diagnosis.
Phase 2 — Root Cause Diagnosis
☐ Run Diagnostic Instrument 1 (Buyer Language Divergence Audit)
☐ Run Diagnostic Instrument 2 (10× Mechanism Health Check)
☐ Run Diagnostic Instrument 3 (Proof Audit)
☐ Run Diagnostic Instrument 4 (Competitor Landscape Scan)
☐ Run Diagnostic Instrument 5 (Market Existence Confirmation)
☐ Complete Diagnosis Confirmation table — primary cause, secondary cause, causes ruled out
☐ Confirm resurrection still justified after diagnosis (triage score + cause confirms viability)
Phase 3 — Resurrection Readiness
☐ Complete full asset inventory with resurrection value assessment
☐ Confirm Minimum Viability Standard: resurrected offer must score 1+ point higher on each cause-related Offer Scorecard dimension
☐ Select the appropriate Resurrection Pathway (A / B / C / D) based on primary cause
Phase 4 — Resurrection Pathway Execution
☐ Execute all steps of the selected pathway in sequence
☐ File the appropriate version changelog entry before any relaunch activity
☐ Complete the Product Versioning SOP Copy & Asset Sync Checklist for all changed elements
☐ For Pathway C or D: complete Beta Testing Methodology SOP before public relaunch
Phase 5 — Relaunch Protocol
☐ Conduct pre-relaunch intelligence collection (interview 5–10 non-purchasers of original offer)
☐ Send existing buyer advance notice 14 days before relaunch
☐ Open waitlist 7–14 days before relaunch
☐ Execute 7-day relaunch email sequence (Days 1, 2, 3, 5, 7)
☐ Confirm Soft Relaunch Gate: warm conversion above 3%, refund rate below 8%, completion rate above 60%
☐ Do not add cold paid traffic until Soft Relaunch Gate is passed
Phase 6 — Post-Resurrection Monitoring (90 Days)
☐ Set up 90-day monitoring calendar with weekly check-ins on the five key metrics
☐ Weeks 1–2: warm conversion and early refund rate
☐ Weeks 3–4: completion rate and Module 1 dropout
☐ Weeks 5–8: cold conversion (if traffic added)
☐ Weeks 9–12: revenue trend, ascension rate, NPS, Offer Scorecard
☐ Declare outcome at 90-day mark: Successful / Incomplete (Continue) / Failed
☐ If Failed: run Post-Kill Intelligence Extraction Protocol. Do not attempt second resurrection.
Phase 7 — Record and Intelligence Harvest
☐ Complete all fields of the Resurrection Record in Airtable
☐ Update Buyer Language Mining database with all new or updated language from the diagnosis process
☐ Update Negative Avatar Profiles with any new profiles identified during diagnosis
☐ Document the Key Diagnostic Finding in the record — one sentence, specific enough to inform future offer design
☐ Document what the market intelligence revealed — competitive insights, avatar evolution, category shifts
☐ Schedule the first full Offer Scorecard session 30 days post-relaunch
☐ Schedule the first quarterly 10× Mechanism Test for the new mechanism name 90 days post-relaunch
RISER Nation Master Operating System | Dead Offer Resurrection Playbook SOP | Version 1.0 | 2026 Edition
Kennedy × Hormozi × Brunson | risernation.com
The Central Principle
An offer does not die. The conditions that made it work change. The market language evolves. Competitors enter and reframe the category. The buyer's awareness level rises and the copy that once felt fresh now feels familiar. The mechanism name that once triggered curiosity now sounds like every other programme. The operator's positioning drifts as the business grows. All of these are fixable. But only if the correct cause is identified before the fix is attempted.
Hormozi's Fuel Rule Applied to Resurrection
Never add fuel to a broken vehicle. This SOP exists to determine whether the vehicle can be repaired before any fuel is added. An operator who relaunches a dead offer to their warm list without diagnosing the root cause will burn their most valuable asset — their existing buyer relationship — on an unrepaired problem. Diagnose first. Repair completely. Then relaunch.
Mortality State
Definition
Metrics Profile
Correct Response
DECLINING
Conversion rate is falling but still above the minimum viable threshold (0.5% cold). Revenue is decreasing month-over-month but the offer still generates sales.
Cold conversion: 0.5–1.4% (declining from prior baseline). Revenue: declining 15–40% from peak. Refund rate: stable or rising slightly.
Weekly Offer Review monitoring + Forensic Audit Loop (event-triggered). This is not a dead offer — it is an offer under pressure. The Forensic Audit Loop SOP handles declining offers. Refer to that SOP before using this one.
FLATLINE
Conversion rate has fallen below 0.5% cold and below 2% warm. Revenue has fallen below the minimum viable threshold. The offer is technically live but generating insufficient revenue to justify continued operation.
Cold conversion: below 0.5% for 30+ consecutive days. Warm conversion: below 2% after a full email sequence. Revenue: below the operational minimum for 45+ days.
This SOP applies. The offer is in the Flatline state — it requires full resurrection protocol or permanent retirement.
RETIRED
The offer was formally killed per the Product Kill Criteria SOP and removed from the market. Assets are archived. Buyers have been notified.
Zero sales for 60+ days. Sales page deactivated. Email sequence deactivated.
This SOP applies if the operator has identified a reason to believe the offer can be revived. See Phase 1 (Triage) for retirement eligibility criteria.
The Flatline vs Declining Distinction
An offer crossing from Declining into Flatline is the critical transition point. A Declining offer's cold conversion of 0.8% can still be profitable at the right volume with the right CPA. A Flatline offer's 0.3% cold conversion cannot be made profitable at any viable traffic volume — the economics break regardless of how much optimisation is applied to the funnel. The Flatline threshold is the trigger for this SOP.
CAUSE 01
Market Language Drift
Recovery Rate: High — 70% successful resurrection with correct language refresh
Definition
The language of the market — the words buyers use to describe their problem, the phrases they search, the vocabulary that signals belonging — has evolved significantly since the offer was launched. The offer's copy, mechanism name, and promise are no longer mirroring how the market talks about the problem. The offer is technically correct but emotionally foreign.
Primary diagnostic symptoms
Exit interviews and support tickets use significantly different vocabulary from the sales page. 10× Mechanism Test Health Indicator HI-5 (buyer language divergence) fires. GEO citation check shows the offer's mechanism name is absent from AI search results on category queries that used to surface it. New buyers describe the offer in ways that don't match the sales page language.
Resurrection approach
Buyer language mining refresh (Forensic Audit Loop SOP Phase 3). Full copy rebuild using current language data. Mechanism rename if Health Indicator HI-5 fires. Deploy within 30 days. No structural changes to delivery.
CAUSE 02
Mechanism Saturation
Recovery Rate: High — 75% successful resurrection with mechanism rename and repositioning
Definition
The offer's named mechanism — which was distinctive and curiosity-generating at launch — has been widely adopted by competitors or has become so familiar to the market through the operator's own content that it no longer generates a 'I've never heard of that before' response. The mechanism is now a commodity term.
Primary diagnostic symptoms
10× Mechanism Test scores below 7.0 on T-1 (Excitement) across test populations. T-5 (Distinctiveness) fails — testers report having heard similar names elsewhere. Organic content featuring the mechanism generates declining engagement over time. Competitors are using the same or near-identical mechanism language.
Resurrection approach
Full 10× Mechanism Test (10× Mechanism Test & Rename Cadence SOP). Run Phase 3 (Name Generation System) targeting a completely different pattern from the current name. New name must score 7.5+ on T-1 before deployment. Treat the mechanism rename as a Minor version change (CAT-M).
CAUSE 03
Proof Staleness
Recovery Rate: High — 65% successful resurrection with proof refresh
Definition
The offer's social proof — testimonials, case studies, and results cited on the sales page — no longer reflects the current buyer's situation, goals, or language. Early buyer results from 2023–2024 describe outcomes that today's buyer no longer relates to. The proof exists but doesn't connect.
Primary diagnostic symptoms
Offer Scorecard D7 (Social Proof Specificity) scores 1 or 2. Exit interviews from buyers who did purchase reveal they were uncertain about proof relevance. Heatmap shows low engagement at the testimonial section. Testimonial Version Registry shows most proof is tagged 'Version-Specific' for prior offer versions.
Resurrection approach
Proof Harvesting Protocol (Beta Testing Methodology SOP Phase 6). Re-interview prior buyers to capture current-language testimonials. Retire all version-specific-retired testimonials. Rebuild the sales page proof section with current proof matched to current promise language. Minimum 3 new metric-specific testimonials before relaunch.
CAUSE 04
Positioning Commoditisation
Recovery Rate: Moderate — 55% successful resurrection requiring significant repositioning investment
Definition
The offer occupied a differentiated position at launch — it was the first, or one of the few, to make a specific promise in a specific way to a specific avatar. The category has since filled with competing offers making similar promises in similar language. The offer is no longer distinctive because the category has caught up to it.
Primary diagnostic symptoms
Competitor benchmarking shows 3+ competitors making near-identical promises with near-identical mechanism names and similar price points. Organic content referencing the offer generates diminishing engagement. AI search engines return multiple competing offers when the category query is entered — the offer is no longer the dominant citation.
Resurrection approach
Category repositioning exercise: identify the specific sub-problem or sub-avatar that competitors are NOT serving. Rebuild the offer's position around that unclaimed space. This is a Major version change (CAT-M + possibly CAT-D if delivery changes). Requires a full relaunch protocol including beta testing.
CAUSE 05
Avatar Obsolescence
Recovery Rate: Moderate — 50% successful resurrection requiring avatar pivot
Definition
The specific buyer profile the offer was designed for has either moved on (the problem the offer solved is no longer their most urgent problem), grown out of it (they've achieved what the offer promised and there are fewer new entrants to that stage), or been absorbed by a different category of solution (a new tool, platform, or methodology has made the original problem irrelevant or solved it in a different way).
Primary diagnostic symptoms
Lead volume declining for the offer's landing page across all traffic sources simultaneously. Community discussions in the target niche show the original problem being discussed less frequently. Organic content about the problem generates declining engagement even when hook quality is high. Buyer interviews reveal the problem is still real but the buyers have changed their mental model of what 'solving it' looks like.
Resurrection approach
Avatar Pivot Protocol (see Phase 4 of this SOP). Identify the new or adjacent avatar who has the original problem but represents the current market entrant. Rebuild the offer positioning, copy, and mechanism language for the new avatar. May be treated as a new offer with the same underlying IP.
CAUSE 06
Delivery Model Obsolescence
Recovery Rate: Moderate-Low — 45% successful resurrection requiring delivery model upgrade
Definition
The way the offer delivers its promise has become outdated relative to market expectations. A self-paced course launched in 2022 may now compete against live cohort programmes with much higher perceived value. A group coaching programme may compete against AI-powered tools that deliver similar outputs at a fraction of the price. The delivery model no longer justifies the price relative to alternatives.
Primary diagnostic symptoms
Completion rate declining cohort-over-cohort despite no change in content quality. Exit interviews cite 'prefer live support' or 'expected more interaction' more frequently. Competitor delivery models offer more interactive formats at comparable or lower prices. Offer Scorecard D3 (Speed to First Win) declining as the market's benchmark for 'fast results' has risen.
Resurrection approach
Delivery model evaluation: identify the delivery format that current buyers in this category now expect. Design a delivery upgrade (self-paced → live cohort, group → DWY, sync → async + AI) that can be built within the operator's current fulfilment capacity. Run the Fulfilment Stress Test SOP before committing. Treat as Major version change (CAT-D).
CAUSE 07
Fundamental Problem Dissolution
Recovery Rate: Low — 25% successful resurrection. In most cases, this cause warrants permanent retirement rather than resurrection.
Definition
The underlying problem the offer was designed to solve no longer exists in the same form — or no longer exists at all. A tool-based problem was solved by a platform update. A platform-specific problem was dissolved when the platform changed its algorithm. A regulatory or compliance problem was changed by new legislation. The offer is technically correct but the problem it solves has been eliminated or fundamentally altered.
Primary diagnostic symptoms
All traffic sources declining simultaneously. Problem-focused organic content generates no engagement even when technically excellent. Buyer interviews reveal the problem is perceived as 'less of an issue than it used to be.' AI search engines return solutions that are fundamentally different from the offer category.
Resurrection approach
If the market data confirms Cause 07: Apply the Post-Kill Intelligence Extraction Protocol (Kill Criteria SOP Phase 6) rather than the resurrection pathway. The IP assets — buyer language data, mechanism frameworks, delivery infrastructure — should be evaluated for repurposing into a new offer addressing an adjacent, current problem. The resurrected offer in this case is effectively a new product.
PHASE 1
The Triage Protocol
Determining whether a dead offer is worth resurrecting before any diagnostic work begins
Criterion
Scoring
Weight
T1 — Peak Performance Evidence
Did this offer ever achieve consistent cold conversion above 1.5% for 30+ consecutive days? Score: Yes = 5. Conversion above 0.8% for 30 days but not 1.5% = 3. No evidence of consistent viable conversion at any point = 1.
High — an offer that never worked cannot be resurrected; it was never alive.
T2 — Recoverable IP Value
Does the offer contain IP that is expensive to recreate — a named mechanism with a documented buyer language base, a proof library with 5+ specific-metric testimonials, a delivery system with documented completion rates? Score: Rich IP base = 5. Moderate IP = 3. Thin IP (generic content, no documented proof) = 1.
High — the resurrection investment is only justified if the IP worth saving exceeds the cost of the resurrection work.
T3 — Cause Diagnosability
Has a root cause been identified from the Seven Causes above with 80%+ confidence? Score: Clear single cause identified = 5. Two probable causes, both treatable = 3. Unclear or multiple conflicting causes = 1.
High — resurrection without a diagnosed cause is guesswork. Guessing wrong on cause wastes the same time as guessing right plus the time to diagnose.
T4 — Market Still Exists
Is the underlying problem the offer addresses still a current, active concern for the target avatar? Score: Problem confirmed active through current community data = 5. Problem likely still active but not recently confirmed = 3. Problem declining or dissolved = 1.
High — an offer addressing a dissolved problem cannot be resurrected; see Cause 07.
T5 — Relaunch Feasibility
Can the resurrection pathway for the identified cause be completed within 90 days with the operator's current team and resource capacity? Score: Feasible in 30 days = 5. Feasible in 60 days = 3. Feasible in 90 days = 2. Requires more than 90 days = 0.
Moderate — a 180-day resurrection is effectively a new offer. Apply the MVO Playbook instead.
T6 — Non-Contamination
Has the offer been retired cleanly without burning the market? If the offer died with a public failure (complaints, chargebacks, platform removals), the market's association with the offer name may be permanently negative. Score: Retired quietly, buyers treated fairly = 5. Minor public friction, resolved = 3. Significant public failure or reputational damage = 0 (auto-disqualify).
Moderate — market contamination from a badly-handled failure cannot be overcome by resurrection; rebranding as a new offer is the only viable path.
Total Score
Decision
Next Step
24–30 — High Resurrection Priority
This offer has strong recovery probability and the resurrection investment is clearly justified. Proceed immediately to Phase 2 (Root Cause Diagnosis).
Begin Phase 2 within 7 days.
16–23 — Conditional Resurrection
The offer has moderate recovery probability. Proceed to Phase 2 but set a 45-day diagnostic deadline. If the root cause cannot be confirmed and the resurrection pathway defined within 45 days, retire the offer and redirect the IP assets.
Begin Phase 2. Set a 45-day diagnostic deadline with a hard gate.
9–15 — Asset Harvest Only
The offer has low recovery probability. Do not invest in resurrection. Run the Post-Kill Intelligence Extraction Protocol (Kill Criteria SOP Phase 6) to harvest IP assets. Use those assets to inform a new offer rather than attempt to revive the dead one.
Post-Kill Intelligence Extraction Protocol only.
0–8 — Permanent Retirement
The offer is not viable for resurrection. Retire permanently. If T6 scored 0 (auto-disqualify), the offer name and positioning must be retired permanently — do not attempt to relaunch under the same name.
Full retirement. Archive assets. No relaunch.
PHASE 2
Root Cause Diagnosis
Confirming which of the Seven Causes is responsible — not guessing
Signal
Threshold
Indicates
Tagged phrases account for more than 40% of the interview language
Count: tagged phrases ÷ total meaningful phrases > 40%
CAUSE 01 — Language Drift. The copy is speaking a different language from the market.
The mechanism name appears in fewer than 3 of 10 exit interview responses when buyers describe the offer
Count: interviews where buyer uses mechanism name ÷ 10 < 30%
CAUSE 01 (Language Drift) or CAUSE 02 (Mechanism Saturation). Run Instrument 2 to differentiate.
Zero divergence between interview language and sales page language — the copy is current but conversion is still dead
Divergence score < 10%
Rules out CAUSE 01 and CAUSE 02. Proceed to Instruments 3–5.
Score
Indicates
T-1 average below 6.0
CAUSE 02 — Mechanism Saturation confirmed. The name has lost its ability to generate excitement.
T-5 fails (2 or more testers report hearing the name elsewhere)
CAUSE 02 — Mechanism Saturation confirmed. The name has been adopted by competitors or overexposed.
T-1 above 7.0 but conversion is still dead
Rules out CAUSE 02. The mechanism name is working — the problem is elsewhere. Proceed to Instruments 3–5.
Profile
Indicates
More than 50% of current sales page testimonials are tagged 'Version-Specific (Retired)' or 'Price-Specific'
CAUSE 03 — Proof Staleness. The proof library has not been maintained as the offer evolved.
Testimonials are version-current but all from the same time period (more than 18 months ago) with no recent proof
CAUSE 03 — Proof Staleness (temporal). Recent buyers are not producing strong testimonials — investigate completion rate as a secondary signal.
Proof library is current and relevant
Rules out CAUSE 03. Proceed to Instruments 4–5.
Signal
Threshold
Indicates
3+ competitors are making near-identical promises with near-identical mechanism language
Count: similar promises and similar mechanism names ≥ 3
CAUSE 04 — Positioning Commoditisation. The category has caught up to the offer's original differentiation.
Dominant competitor delivery formats have shifted significantly from the offer's delivery format
Majority of top-ranked competitors now use a delivery format different from the offer's
CAUSE 06 — Delivery Model Obsolescence. The category's delivery norm has moved.
No significant competitor change — the category is essentially the same as at launch
No material change in competitor positioning or delivery
Rules out CAUSE 04 and CAUSE 06. Proceed to Instrument 5.
Signal
Indicates
Fewer than 10 community posts about the problem in 90 days AND Google Trends showing declining search volume
CAUSE 07 — Problem Dissolution. The market for this offer is contracting at the problem level, not the offer level.
Community posts active, AI search results show the problem as current but reference different solution approaches than the offer
CAUSE 05 — Avatar Obsolescence or CAUSE 04 — Positioning Commoditisation. The problem exists but the buyer's solution expectations have shifted.
Community posts active, AI search results confirm the problem as unsolved, search volume stable
Rules out CAUSE 07. The market exists. The problem is in the offer's positioning or proof, not the market itself.
Field
Document Here
Primary cause (Cause 01–07)
Evidence supporting primary cause (instrument results)
Secondary cause (if identified)
Evidence supporting secondary cause
Causes ruled out and evidence
Resurrection pathway (from Phase 4)
Estimated resurrection timeline
Resurrection justified? (Triage score + cause confirms viability)
Yes / No
PHASE 3
The Resurrection Readiness Assessment
Confirming the offer is worth rebuilding before any rebuild work begins
Asset Category
What to Inventory
Resurrection Value
Buyer language database
All tagged PAIN-ACUTE, PAIN-CHRONIC, DESIRE-HIDDEN, and OBJECTION phrases from exit interviews, support tickets, and refund messages collected during the offer's active period.
Highest — verbatim buyer language is the most expensive asset to recreate. Even a dead offer's language database provides 12–18 months of market intelligence that would take a new offer's first year to accumulate.
Proof library
All testimonials, case studies, and results documentation. Note which are version-current vs version-specific-retired.
High — specific-metric proof from real buyers cannot be manufactured. Even retired testimonials may be eligible for specific applications (mechanism-agnostic results remain valid regardless of mechanism rename).
Mechanism framework
The underlying methodology, frameworks, and IP — separate from the mechanism name. The name may be dead; the methodology may be fully alive.
High — the methodology survived the offer's death. The resurrection may require only a rename and repositioning, not a rebuild of the intellectual content.
Delivery infrastructure
The course platform build, module structure, worksheet templates, email sequences, and onboarding architecture.
Moderate — reusable with edits. If the cause is Language Drift or Mechanism Saturation, delivery infrastructure can be used largely unchanged. If Delivery Model Obsolescence, significant modification is required.
Negative avatar data
Refund root cause codes, Negative Avatar profiles, exit interview data from buyers who did not get results.
High — knowing precisely who this offer does NOT serve is as valuable as knowing who it does serve. This data prevents the same wrong-fit buyers from being attracted in the relaunch.
Traffic and conversion data
Historical conversion rates by source, by copy test variant, by guarantee version — the performance record of the offer at its best.
Moderate — establishes the benchmark the resurrection must beat to be considered successful. Also identifies which traffic sources and copy approaches produced the best results when the offer was working.
The Improvement Standard
The resurrected offer must score at least 1 point higher than the dead offer's final Offer Scorecard on each dimension that the diagnosis identified as a contributing cause. If Cause 01 (Language Drift) was the primary cause, D1 (Dream Outcome Clarity) must score at least 1 point higher on the resurrected offer than the dead offer's last recorded D1 score. If Cause 03 (Proof Staleness) contributed, D7 must improve. The improvement must be documentable — not subjective.
PHASE 4
The Four Resurrection Pathways
Matching the cause to the correct rebuild approach
Pathway A — For: CAUSE 01 (Language Drift) and CAUSE 02 (Mechanism Saturation)
Timeline: 21–30 days
Version change type: Minor (CAT-M for mechanism rename + CAT-C for copy update)
Delivery changes: None required
Step
Action
Timeline
Output
A1
Run the full Buyer Language Mining Refresh from the Forensic Audit Loop SOP Phase 3. Pull exit interviews and support tickets from the last 6 months. Tag all PAIN-ACUTE, PAIN-CHRONIC, and DESIRE-HIDDEN phrases. Build the refreshed language list.
Days 1–5
Updated buyer language database with current-market vocabulary
A2
Run the full 10× Mechanism Test Protocol (Phase 2 of the 10× Mechanism Test SOP) on the current mechanism name to confirm the T-1 and T-5 scores. If T-1 below 7.0 or T-5 fails: proceed to mechanism rename. If both pass: the mechanism name is not the issue — revisit the language diagnosis.
Days 3–7
10× Test scorecard confirming whether rename is required
A3
If rename required: run Phase 3 of the 10× Mechanism Test SOP (Name Generation System) using all six generation methods. Minimum 15 candidates. Select the top 5 for testing. Test with avatar-matched individuals. Select the winner (7.5+ T-1 score required).
Days 6–14
New mechanism name scoring 7.5+ on T-1, confirmed distinct and memorable
A4
Rebuild the sales page copy from a fresh copy brief using the updated buyer language database. The rebuild is not an edit of the old copy — it is a new document written from the buyer language data upward. Lead, mechanism section, stack section, guarantee section, FAQ section — all rewritten.
Days 10–21
New sales page copy in draft. Not yet live.
A5
Rebuild the 14-day email sequence Days 8–10 (mechanism introduction emails) using the new mechanism name and updated language. Update all other sequence emails where the old language appears.
Days 14–21
Updated email sequence. Not yet live.
A6
Update all assets per the Product Versioning SOP Copy & Asset Sync Checklist (Phase 5). File a Minor version changelog entry (CAT-M + CAT-C).
Days 21–28
All assets updated. Changelog filed. Version deployed.
A7
Run a 14-day soft relaunch to the warm list only. Do not launch to cold paid traffic until warm conversion is confirmed. Target: warm conversion above 5% from the email sequence before adding any paid traffic.
Days 28–42
Warm relaunch data. Conversion confirmed before cold expansion.
Pathway B — For: CAUSE 03 (Proof Staleness) and supporting secondary causes
Timeline: 30–45 days
Version change type: Minor (CAT-O for stack update + CAT-C for copy update)
Delivery changes: None required for proof refresh; potential bonus changes for stack rebuild
Step
Action
Timeline
Output
B1
Run the Proof Harvesting Protocol (Beta Testing Methodology SOP Phase 6). Re-contact the top 20% of prior buyers by result achieved. Conduct structured exit interviews specifically designed to capture current, metric-specific testimonials using current language.
Days 1–14
New exit interview recordings. Minimum 5 usable metric-specific testimonials.
B2
Run the Testimonial Audit Protocol (Product Versioning SOP Phase 5). Retire all version-specific testimonials that reference retired elements. Identify which current testimonials are version-current and proof-to-promise matched.
Days 7–10
Cleaned testimonial registry. Clear picture of current proof assets.
B3
Build two or three detailed case studies from the new interview data. Structure each as: Avatar → Problem → Attempt → Discovery → Result (with specific metrics). These become the primary proof assets on the rebuilt sales page.
Days 10–21
2–3 production-ready case studies with specific metrics.
B4
Audit the bonus stack against the Bonus Discipline Audit SOP. If any bonus has a Buyer Utility Score below 5.0: run the Reform or Cut protocol. Add new bonuses to address sub-problems the new buyer language audit identifies.
Days 10–21
Updated bonus stack passing all five Bonus Discipline Audit dimensions.
B5
Rebuild the sales page proof section entirely. Lead with the strongest new case study. Follow with the stack of current testimonials. Ensure every testimonial is proof-to-promise matched — each one answers a specific objection from the Objection Bank.
Days 21–30
Rebuilt proof section. Testimonials aligned to objections.
B6
Update all assets per the Product Versioning SOP Sync Checklist. File changelog entry.
Days 28–35
Assets synced. Changelog filed.
B7
Soft relaunch to warm list. Target: warm conversion above 5% and testimonial collection rate above 20% of new buyers in first 30 days.
Days 35–65
Warm relaunch data with proof collection ongoing.
Pathway C — For: CAUSE 04 (Positioning Commoditisation) and CAUSE 05 (Avatar Obsolescence)
Timeline: 45–60 days
Version change type: Major (CAT-M) — fundamental repositioning
Delivery changes: Possible but not required
Step
Action
Timeline
Output
C1
Run the Category Gap Analysis. Map all direct competitors' current positioning: their avatar, their promise, their mechanism, their price. Identify the specific white space — the sub-avatar, sub-problem, or sub-mechanism that is underserved by the current competitive landscape.
Days 1–10
Category positioning map. White space identified with specific evidence.
C2
Define the new target avatar precisely. This may be the same broad category but a different stage, context, or constraint. Example: 'B2B SaaS founders' is too broad. 'B2B SaaS founders at the $1M–$5M ARR stage preparing for Series A' is the level of specificity required for a repositioned offer.
Days 7–14
New avatar definition: one paragraph, specific enough to identify a real person in a room. JTBD statement for the new avatar.
C3
Run the MVO Playbook Phase 2 process (Trim & Stack) from the perspective of the new avatar and the white space identified in C1. Identify which components of the existing delivery survive unchanged, which require modification, and which can be retired.
Days 10–21
Updated offer stack designed for the new avatar and new position. Components preserved vs modified vs retired documented.
C4
Rename the offer. When an offer repositions for a new avatar or moves into white space, the name often needs to change to signal the new position. Apply the 10× Mechanism Test & Rename Cadence SOP name generation process to the new position.
Days 14–21
New offer name and mechanism statement for the repositioned offer.
C5
Rebuild sales copy, email sequence, and all buyer-facing assets from scratch for the new avatar. Do not edit existing copy — the existing copy was built for the old position. Building on it produces muddled positioning.
Days 21–40
New copy brief. New sales page draft. New email sequence draft.
C6
Run the Negative Avatar Modelling SOP to build repulsion layers for the wrong-fit avatars that were attracted to the previous position. These now become the 'Not for you if' section of the new offer page.
Days 28–40
Updated Negative Avatar profiles. Repulsion language integrated into new copy.
C7
Beta test the repositioned offer with 5–10 buyers from the new avatar profile before public launch. This is not optional — a repositioned offer is effectively a new offer and requires beta validation (Beta Testing Methodology SOP).
Days 40–60
Beta data: conversion at beta price, completion rate, early results. Go/No-Go scorecard passed.
C8
File as a Major version change (CAT-M). Run the full Product Versioning SOP deployment protocol including buyer communication.
Days 58–65
Major version deployed. Changelog filed. Communications sent.
Pathway D — For: CAUSE 06 (Delivery Model Obsolescence) — and as secondary pathway for CAUSE 04 when delivery is the competitive disadvantage
Timeline: 60–90 days
Version change type: Major (CAT-D)
Delivery changes: Required — the delivery model is the primary change
Step
Action
Timeline
Output
D1
Run the Fulfilment Stress Test SOP (Phases 1–3) for the proposed new delivery model before designing anything. Confirm: capacity ceiling for the new format, total delivery time per buyer under the new model, and whether the founder's schedule can support the upgrade.
Days 1–14
Fulfilment Stress Test results for proposed new delivery format. Go/No-Go on capacity.
D2
Define the delivery model upgrade specifically. Common transitions: self-paced → live cohort (adds synchronous community and accountability); group coaching → small-group intensive (reduces buyer count, increases intensity); recorded content → AI-augmented delivery (adds personalised feedback loops without proportional time cost).
Days 7–14
New delivery architecture document. One paragraph per delivery component: what it is, how it works, who delivers it, how often.
D3
Run the Price Elasticity Testing Framework SOP Phase 1 (Estimation Method) for the new delivery model. A delivery model upgrade typically justifies a price increase — confirm the market will support it before building.
Days 7–21
Price range for the upgraded offer. New price point selected using Van Westendorp or competitor benchmarking.
D4
Redesign the course platform architecture for the new delivery model. Update module structure, add live session integration, update onboarding, build community structure if new, create accountability touchpoints if new.
Days 21–50
Rebuilt delivery infrastructure. Platform-tested with a test cohort of 2–3 people before launch.
D5
Rebuild the guarantee to match the new delivery model. A live cohort can support a stronger guarantee than a self-paced course. A DWY model can support a service completion guarantee. Use the Guarantee Type Testing Protocol SOP to design and test the appropriate new guarantee level.
Days 28–45
New guarantee language matched to new delivery format.
D6
Rebuild the sales page for the new delivery model. The delivery format is a core component of the buyer's decision — it must be foregrounded in the copy, not buried in the FAQ.
Days 35–55
New sales page draft including delivery format as a primary value element.
D7
Run a pre-sell to the warm list before building the full new delivery system. Announce the upgraded version, describe the new delivery format, and offer founding member pricing. If fewer than 5 buyers commit from a list of 500+ engaged subscribers: the delivery upgrade alone is not sufficient — revisit the cause diagnosis (Pathway C may be needed alongside Pathway D).
Days 50–65
Pre-sell data. Founding member commitments. Go/No-Go on full build.
D8
Build, beta test, and launch per the Beta Testing Methodology SOP. File a Major version change (CAT-D).
Days 60–90
Beta complete. Major version deployed. Changelog filed.
PHASE 5
The Relaunch Protocol
How to bring the resurrected offer back to market without reactivating the failure memory
The New Chapter Frame
The resurrected offer is not presented as 'updated' or 'improved.' It is presented as the result of a period of deep learning, research, and rebuilding. The copy acknowledges that the prior version had limitations (specific, honest, brief), explains what was learned, describes what was rebuilt and why it is fundamentally better, and positions the relaunch as a deliberate decision made with new evidence rather than a hasty fix. This framing converts sceptics who dismissed the original offer into curious prospects for the new version.
Phase
Timing
Action
Target
Pre-Relaunch Intelligence Collection
21–30 days before relaunch
Interview 5–10 people who encountered the original offer and did not purchase. Ask: 'What specifically stopped you from buying [original offer]?' Document the exact language. This feeds the relaunch copy's objection-handling section and ensures the new version directly addresses the reasons the original failed to convert.
Verbatim objection data from non-purchasers of the original offer.
Existing Buyer Advance Notice
14 days before relaunch
Email existing buyers from the original offer: inform them that the offer has been rebuilt, explain what changed and why, and give them first access at founding member pricing if they want to re-engage or refer someone. This converts your existing buyer relationship from a liability (they know the flaws of the original) into an asset (they can see the genuine improvement).
Goodwill maintained. Potential early referrals from existing buyers who have seen the improvement.
Waitlist Build
14–7 days before relaunch
Open a waitlist for the relaunched offer with a one-sentence description of the core change: 'We spent [X months] rebuilding [offer name] from the ground up. If [specific problem] is still a challenge for you, join the list for first access.' No long copy. No over-selling. Just the announcement and the waitlist link.
50+ waitlist signups confirming warm market interest before full relaunch email sequence.
Relaunch Email Day 1 — The Honest Pivot Story
Relaunch Day 1
The founder sends a personal, plain-text email telling the story of what they learned, what they changed, and why they rebuilt rather than retired. The tone is honest: 'The original version had this specific limitation. Here's what I learned from buyers. Here's what I rebuilt. Here's the result.' This email is the Epiphany Bridge for the resurrected offer.
Email open rate above 30%. Reply rate above 2% — replies indicate genuine re-engagement.
Relaunch Email Day 2 — New Proof and New Mechanism
Relaunch Day 2
Present the new mechanism name (if renamed), the new case study from the Proof Harvest Protocol, and the updated guarantee. Lead with a buyer who went through the original version and came back for the rebuild — the arc of a returning buyer is the most powerful relaunch proof available.
New mechanism introduced. New proof deployed. Guarantee reinforced.
Relaunch Email Day 3 — The What Changed Comparison
Relaunch Day 3
Side-by-side comparison of the original versus the resurrected offer across 5–6 specific dimensions: delivery format, mechanism name, guarantee, specific result promised, support structure, price. Make the improvement concrete and specific — not 'we improved everything' but 'the guarantee went from 30-day money-back to conditional result-based. The mechanism was renamed from X to Y. The delivery format changed from self-paced to live cohort.'
Specificity of change creates credibility. Buyers who dismissed the original now have a reason to re-evaluate.
Relaunch Email Day 5 — Objection Handling
Relaunch Day 5
Using the pre-relaunch interview data (Phase 5, step 1), directly address the top 3 objections that stopped people from buying the original offer. Each objection gets one sentence validation, one sentence reframe, and one sentence of evidence that the rebuilt offer resolves it.
Objection Bank entries addressed. Non-converters from the original offer given specific reasons to reconsider.
Relaunch Email Day 7 — Final Call
Relaunch Day 7
Standard deadline email using the relaunch window closing mechanism. If founding member pricing was offered: it closes tonight. If cohort spots were limited: this is the last call. Hard close at the stated deadline — no exceptions.
Final push. Deadline enforced.
Gate Metric
Minimum Threshold
What It Confirms
Warm conversion rate from the 7-day relaunch sequence
Above 3% of the warm list who received the sequence
The resurrected offer is converting its most favourable audience. Cold traffic conversion will be lower — but 3% warm is evidence the offer works for a motivated buyer.
Refund rate in first 14 days
Below 8%
No expectation mismatch between the new positioning and the actual delivery.
Completion rate (Module 1 within 72 hours)
Above 60%
The new onboarding and Quick Win architecture is working. Buyers are engaging.
Spontaneous testimonial collection rate
At least 1 specific-metric testimonial from every 10 new buyers
The resurrected offer is producing results. This data feeds the next proof refresh cycle.
PHASE 6
The Post-Resurrection Monitoring Protocol
Confirming the resurrection held under real-world conditions
Week
Monitoring Focus
Alert Threshold
Action If Threshold Crossed
Weeks 1–2
Warm conversion rate and early refund rate. The first 14 days reveal whether the new positioning and new proof are landing with the engaged warm audience.
Warm conversion below 2% after full 7-day sequence delivery. OR refund rate above 10%.
Pause relaunch. Run emergency Refund Forensics. Do not add cold traffic until warm performance is confirmed.
Weeks 3–4
Completion rate and Module 1 dropout rate. The delivery model upgrade (if applied) must demonstrate improved engagement within the first cohort cycle.
Completion rate below 35% in first 14 days of access (below Pathway D expectation for the new delivery format).
Run the Time-and-Motion Audit (Fulfilment Stress Test SOP Phase 3). Identify where buyers are dropping out and why.
Weeks 5–8
Cold conversion rate (if paid traffic or organic promotion has been added). Compare against the dead offer's final cold conversion rate AND the offer's historical peak.
Cold conversion below 0.8% after 200+ unique cold visitors.
Do not increase cold traffic spend. Run the Pre-Kill Diagnostic to confirm whether the issue is the offer or the traffic source.
Weeks 9–12
Revenue trend, ascension rate, and NPS. The full 90-day performance picture.
Revenue declining week-over-week for 3 consecutive weeks after the initial launch spike subsides. OR NPS below 20.
Run the full Offer Scorecard. If composite score below 40 after 90 days: the resurrection has not held. Apply the Kill Criteria SOP to determine next action.
Criterion
Success Threshold
How to Measure
Cold conversion rate
Above 1.0% — meeting or exceeding the offer's prior peak baseline
GA4 + CRM: rolling 30-day cold conversion rate
Warm conversion rate
Above 5% — meeting or exceeding the offer's prior peak warm performance
Email platform + CRM: conversion from 14-day sequence completion
Refund rate
Below 8% rolling 30 days
Stripe rolling 30-day refund rate
Completion rate
Above 45% — at or above the Offer Scorecard D11 viable threshold
Course platform analytics: module completion tracking
Offer Scorecard composite
Above 45/75 (B-grade or C-grade minimum with clear trajectory of improvement)
Monthly Offer Scorecard session
RESURRECTION SUCCESSFUL
All five criteria met for 30+ consecutive days
The offer has been revived. Treat it as a newly-relaunched offer in its early-traction phase.

Next actions:
— Schedule the Price Elasticity Testing Framework SOP to test whether the resurrected offer can support a price increase.
— Continue the Offer Scorecard monthly cadence to track ongoing improvement.
— Update the 10× Mechanism Test & Rename Cadence SOP quarterly test calendar with the new mechanism name.
— Log the complete resurrection record in Airtable (see Phase 7 schema).
RESURRECTION INCOMPLETE — CONTINUE MONITORING
3–4 of 5 criteria met at 90-day mark
The resurrection is producing improvement but has not yet reached full viability. This is a positive signal — the root cause diagnosis was correct and the pathway is working. Extend the monitoring window to 120 days. Do not declare failure or success at 90 days if trend is positive.

Key question: is the trend upward (metrics improving week-over-week) or flat? Upward trend at 90 days = continue. Flat trend at 90 days for 30+ days = revisit whether a secondary cause was missed in the diagnosis.
RESURRECTION FAILED — ESCALATE TO KILL CRITERIA SOP
Fewer than 3 criteria met at 90-day mark and no positive trend
The resurrection pathway did not resolve the root cause, or the root cause diagnosis was incorrect. The offer cannot be revived in its current form.

Next actions:
— Do NOT attempt a second resurrection immediately. Run the Post-Kill Intelligence Extraction Protocol (Kill Criteria SOP Phase 6) first.
— Review the cause diagnosis: which instrument was most likely incorrect? What did the 90-day operation reveal that the diagnosis missed?
— Evaluate the IP assets for repurposing into a new offer (see Triage Score 9–15: Asset Harvest Only).
— File the full resurrection record in Airtable. This data has high value for future offer development.
PHASE 7
The Resurrection Intelligence Record
Everything that was learned, preserved for every future offer in the business
Field
Type
Notes
Resurrection ID
Autonumber
Format: RES-[Offer Code]-[YYYY-MM]
Offer
Link → Offers table
Offer Mortality State at Triage
Single select
Flatline / Retired
Triage Score
Number
Out of 30
Triage Decision
Single select
High Priority / Conditional / Asset Harvest / Permanent Retirement
Primary Root Cause
Single select
Cause 01–07
Secondary Root Cause (if any)
Single select
Cause 01–07 / None
Diagnosis Confidence Level
Single select
High (80%+) / Moderate (60–79%) / Low (<60%)
Resurrection Pathway Used
Single select
Pathway A / B / C / D
Resurrection Start Date
Date
Resurrection Completion Date (relaunch)
Date
Total Resurrection Duration (days)
Formula
Completion Date minus Start Date
Offer Scorecard — Dead Offer Final Score
Number
Score from last Offer Scorecard before death/flatline
Offer Scorecard — Resurrected Offer Score (30 days post-relaunch)
Number
Offer Scorecard Improvement Delta
Formula
Post-relaunch minus final pre-death score
Cold Conversion — Dead Offer Final Rate
Number
% in final 30 days before death
Cold Conversion — Resurrected Offer (90-day post-relaunch)
Number
% rolling 30-day at 90-day mark
Warm Conversion — Dead Offer Final Rate
Number
Warm Conversion — Resurrected Offer (90-day)
Number
Refund Rate — Dead Offer Final
Number
Refund Rate — Resurrected Offer (90-day)
Number
Completion Rate — Resurrected Offer (first full cohort)
Number
Resurrection Outcome
Single select
Successful / Incomplete (Continuing) / Failed
Revenue Impact (annualised estimate)
Currency
Estimated annual revenue from resurrected offer
IP Assets Recovered
Long text
List of buyer language, proof, mechanism framework assets preserved from the original offer and deployed in the resurrection
Key Diagnostic Finding
Long text
The single most important thing this resurrection process revealed about why offers die in this market. One sentence, specific enough to change a future offer design decision.
What the Dead Offer's Market Intelligence Revealed
Long text
New insights about the avatar, the problem, the competitive landscape, or the category that did not exist before the resurrection diagnosis process
Buyer Language Update
Long text
New or significantly updated PAIN-ACUTE, PAIN-CHRONIC, and DESIRE-HIDDEN phrases added to the Buyer Language Mining database as a result of the resurrection diagnosis
Negative Avatar Profiles Updated
Link → Negative Avatar Profiles
Any new profiles or updates to existing profiles from resurrection diagnosis
Mechanism Name History
Long text
Old mechanism name → New mechanism name (if renamed). Reason for change. 10× Test scores before and after.
Version Changelog Entry
Link → Changelog Entries
The Major or Minor version entry from the Product Versioning SOP
Next Quarterly Review Date
Date
Schedule the first full Offer Scorecard 30 days post-relaunch

Original Word tables and field relationships

Source table 1

The Central PrincipleAn offer does not die. The conditions that made it work change. The market language evolves. Competitors enter and reframe the category. The buyer's awareness level rises and the copy that once felt fresh now feels familiar. The mechanism name that once triggered curiosity now sounds like every other programme. The operator's positioning drifts as the business grows. All of these are fixable. But only if the correct cause is identified before the fix is attempted.

Source table 2

Hormozi's Fuel Rule Applied to ResurrectionNever add fuel to a broken vehicle. This SOP exists to determine whether the vehicle can be repaired before any fuel is added. An operator who relaunches a dead offer to their warm list without diagnosing the root cause will burn their most valuable asset — their existing buyer relationship — on an unrepaired problem. Diagnose first. Repair completely. Then relaunch.

Source table 3

Mortality State	Definition	Metrics Profile	Correct Response
DECLINING	Conversion rate is falling but still above the minimum viable threshold (0.5% cold). Revenue is decreasing month-over-month but the offer still generates sales.	Cold conversion: 0.5–1.4% (declining from prior baseline). Revenue: declining 15–40% from peak. Refund rate: stable or rising slightly.	Weekly Offer Review monitoring + Forensic Audit Loop (event-triggered). This is not a dead offer — it is an offer under pressure. The Forensic Audit Loop SOP handles declining offers. Refer to that SOP before using this one.
FLATLINE	Conversion rate has fallen below 0.5% cold and below 2% warm. Revenue has fallen below the minimum viable threshold. The offer is technically live but generating insufficient revenue to justify continued operation.	Cold conversion: below 0.5% for 30+ consecutive days. Warm conversion: below 2% after a full email sequence. Revenue: below the operational minimum for 45+ days.	This SOP applies. The offer is in the Flatline state — it requires full resurrection protocol or permanent retirement.
RETIRED	The offer was formally killed per the Product Kill Criteria SOP and removed from the market. Assets are archived. Buyers have been notified.	Zero sales for 60+ days. Sales page deactivated. Email sequence deactivated.	This SOP applies if the operator has identified a reason to believe the offer can be revived. See Phase 1 (Triage) for retirement eligibility criteria.

Source table 4

The Flatline vs Declining DistinctionAn offer crossing from Declining into Flatline is the critical transition point. A Declining offer's cold conversion of 0.8% can still be profitable at the right volume with the right CPA. A Flatline offer's 0.3% cold conversion cannot be made profitable at any viable traffic volume — the economics break regardless of how much optimisation is applied to the funnel. The Flatline threshold is the trigger for this SOP.

Source table 5

CAUSE 01Market Language DriftRecovery Rate: High — 70% successful resurrection with correct language refresh
DefinitionThe language of the market — the words buyers use to describe their problem, the phrases they search, the vocabulary that signals belonging — has evolved significantly since the offer was launched. The offer's copy, mechanism name, and promise are no longer mirroring how the market talks about the problem. The offer is technically correct but emotionally foreign.
Primary diagnostic symptomsExit interviews and support tickets use significantly different vocabulary from the sales page. 10× Mechanism Test Health Indicator HI-5 (buyer language divergence) fires. GEO citation check shows the offer's mechanism name is absent from AI search results on category queries that used to surface it. New buyers describe the offer in ways that don't match the sales page language.
Resurrection approachBuyer language mining refresh (Forensic Audit Loop SOP Phase 3). Full copy rebuild using current language data. Mechanism rename if Health Indicator HI-5 fires. Deploy within 30 days. No structural changes to delivery.

Source table 6

CAUSE 02Mechanism SaturationRecovery Rate: High — 75% successful resurrection with mechanism rename and repositioning
DefinitionThe offer's named mechanism — which was distinctive and curiosity-generating at launch — has been widely adopted by competitors or has become so familiar to the market through the operator's own content that it no longer generates a 'I've never heard of that before' response. The mechanism is now a commodity term.
Primary diagnostic symptoms10× Mechanism Test scores below 7.0 on T-1 (Excitement) across test populations. T-5 (Distinctiveness) fails — testers report having heard similar names elsewhere. Organic content featuring the mechanism generates declining engagement over time. Competitors are using the same or near-identical mechanism language.
Resurrection approachFull 10× Mechanism Test (10× Mechanism Test & Rename Cadence SOP). Run Phase 3 (Name Generation System) targeting a completely different pattern from the current name. New name must score 7.5+ on T-1 before deployment. Treat the mechanism rename as a Minor version change (CAT-M).

Source table 7

CAUSE 03Proof StalenessRecovery Rate: High — 65% successful resurrection with proof refresh
DefinitionThe offer's social proof — testimonials, case studies, and results cited on the sales page — no longer reflects the current buyer's situation, goals, or language. Early buyer results from 2023–2024 describe outcomes that today's buyer no longer relates to. The proof exists but doesn't connect.
Primary diagnostic symptomsOffer Scorecard D7 (Social Proof Specificity) scores 1 or 2. Exit interviews from buyers who did purchase reveal they were uncertain about proof relevance. Heatmap shows low engagement at the testimonial section. Testimonial Version Registry shows most proof is tagged 'Version-Specific' for prior offer versions.
Resurrection approachProof Harvesting Protocol (Beta Testing Methodology SOP Phase 6). Re-interview prior buyers to capture current-language testimonials. Retire all version-specific-retired testimonials. Rebuild the sales page proof section with current proof matched to current promise language. Minimum 3 new metric-specific testimonials before relaunch.

Source table 8

CAUSE 04Positioning CommoditisationRecovery Rate: Moderate — 55% successful resurrection requiring significant repositioning investment
DefinitionThe offer occupied a differentiated position at launch — it was the first, or one of the few, to make a specific promise in a specific way to a specific avatar. The category has since filled with competing offers making similar promises in similar language. The offer is no longer distinctive because the category has caught up to it.
Primary diagnostic symptomsCompetitor benchmarking shows 3+ competitors making near-identical promises with near-identical mechanism names and similar price points. Organic content referencing the offer generates diminishing engagement. AI search engines return multiple competing offers when the category query is entered — the offer is no longer the dominant citation.
Resurrection approachCategory repositioning exercise: identify the specific sub-problem or sub-avatar that competitors are NOT serving. Rebuild the offer's position around that unclaimed space. This is a Major version change (CAT-M + possibly CAT-D if delivery changes). Requires a full relaunch protocol including beta testing.

Source table 9

CAUSE 05Avatar ObsolescenceRecovery Rate: Moderate — 50% successful resurrection requiring avatar pivot
DefinitionThe specific buyer profile the offer was designed for has either moved on (the problem the offer solved is no longer their most urgent problem), grown out of it (they've achieved what the offer promised and there are fewer new entrants to that stage), or been absorbed by a different category of solution (a new tool, platform, or methodology has made the original problem irrelevant or solved it in a different way).
Primary diagnostic symptomsLead volume declining for the offer's landing page across all traffic sources simultaneously. Community discussions in the target niche show the original problem being discussed less frequently. Organic content about the problem generates declining engagement even when hook quality is high. Buyer interviews reveal the problem is still real but the buyers have changed their mental model of what 'solving it' looks like.
Resurrection approachAvatar Pivot Protocol (see Phase 4 of this SOP). Identify the new or adjacent avatar who has the original problem but represents the current market entrant. Rebuild the offer positioning, copy, and mechanism language for the new avatar. May be treated as a new offer with the same underlying IP.

Source table 10

CAUSE 06Delivery Model ObsolescenceRecovery Rate: Moderate-Low — 45% successful resurrection requiring delivery model upgrade
DefinitionThe way the offer delivers its promise has become outdated relative to market expectations. A self-paced course launched in 2022 may now compete against live cohort programmes with much higher perceived value. A group coaching programme may compete against AI-powered tools that deliver similar outputs at a fraction of the price. The delivery model no longer justifies the price relative to alternatives.
Primary diagnostic symptomsCompletion rate declining cohort-over-cohort despite no change in content quality. Exit interviews cite 'prefer live support' or 'expected more interaction' more frequently. Competitor delivery models offer more interactive formats at comparable or lower prices. Offer Scorecard D3 (Speed to First Win) declining as the market's benchmark for 'fast results' has risen.
Resurrection approachDelivery model evaluation: identify the delivery format that current buyers in this category now expect. Design a delivery upgrade (self-paced → live cohort, group → DWY, sync → async + AI) that can be built within the operator's current fulfilment capacity. Run the Fulfilment Stress Test SOP before committing. Treat as Major version change (CAT-D).

Source table 11

CAUSE 07Fundamental Problem DissolutionRecovery Rate: Low — 25% successful resurrection. In most cases, this cause warrants permanent retirement rather than resurrection.
DefinitionThe underlying problem the offer was designed to solve no longer exists in the same form — or no longer exists at all. A tool-based problem was solved by a platform update. A platform-specific problem was dissolved when the platform changed its algorithm. A regulatory or compliance problem was changed by new legislation. The offer is technically correct but the problem it solves has been eliminated or fundamentally altered.
Primary diagnostic symptomsAll traffic sources declining simultaneously. Problem-focused organic content generates no engagement even when technically excellent. Buyer interviews reveal the problem is perceived as 'less of an issue than it used to be.' AI search engines return solutions that are fundamentally different from the offer category.
Resurrection approachIf the market data confirms Cause 07: Apply the Post-Kill Intelligence Extraction Protocol (Kill Criteria SOP Phase 6) rather than the resurrection pathway. The IP assets — buyer language data, mechanism frameworks, delivery infrastructure — should be evaluated for repurposing into a new offer addressing an adjacent, current problem. The resurrected offer in this case is effectively a new product.

Source table 12

PHASE 1The Triage ProtocolDetermining whether a dead offer is worth resurrecting before any diagnostic work begins

Source table 13

Criterion	Scoring	Weight
T1 — Peak Performance Evidence	Did this offer ever achieve consistent cold conversion above 1.5% for 30+ consecutive days? Score: Yes = 5. Conversion above 0.8% for 30 days but not 1.5% = 3. No evidence of consistent viable conversion at any point = 1.	High — an offer that never worked cannot be resurrected; it was never alive.
T2 — Recoverable IP Value	Does the offer contain IP that is expensive to recreate — a named mechanism with a documented buyer language base, a proof library with 5+ specific-metric testimonials, a delivery system with documented completion rates? Score: Rich IP base = 5. Moderate IP = 3. Thin IP (generic content, no documented proof) = 1.	High — the resurrection investment is only justified if the IP worth saving exceeds the cost of the resurrection work.
T3 — Cause Diagnosability	Has a root cause been identified from the Seven Causes above with 80%+ confidence? Score: Clear single cause identified = 5. Two probable causes, both treatable = 3. Unclear or multiple conflicting causes = 1.	High — resurrection without a diagnosed cause is guesswork. Guessing wrong on cause wastes the same time as guessing right plus the time to diagnose.
T4 — Market Still Exists	Is the underlying problem the offer addresses still a current, active concern for the target avatar? Score: Problem confirmed active through current community data = 5. Problem likely still active but not recently confirmed = 3. Problem declining or dissolved = 1.	High — an offer addressing a dissolved problem cannot be resurrected; see Cause 07.
T5 — Relaunch Feasibility	Can the resurrection pathway for the identified cause be completed within 90 days with the operator's current team and resource capacity? Score: Feasible in 30 days = 5. Feasible in 60 days = 3. Feasible in 90 days = 2. Requires more than 90 days = 0.	Moderate — a 180-day resurrection is effectively a new offer. Apply the MVO Playbook instead.
T6 — Non-Contamination	Has the offer been retired cleanly without burning the market? If the offer died with a public failure (complaints, chargebacks, platform removals), the market's association with the offer name may be permanently negative. Score: Retired quietly, buyers treated fairly = 5. Minor public friction, resolved = 3. Significant public failure or reputational damage = 0 (auto-disqualify).	Moderate — market contamination from a badly-handled failure cannot be overcome by resurrection; rebranding as a new offer is the only viable path.

Source table 14

Total Score	Decision	Next Step
24–30 — High Resurrection Priority	This offer has strong recovery probability and the resurrection investment is clearly justified. Proceed immediately to Phase 2 (Root Cause Diagnosis).	Begin Phase 2 within 7 days.
16–23 — Conditional Resurrection	The offer has moderate recovery probability. Proceed to Phase 2 but set a 45-day diagnostic deadline. If the root cause cannot be confirmed and the resurrection pathway defined within 45 days, retire the offer and redirect the IP assets.	Begin Phase 2. Set a 45-day diagnostic deadline with a hard gate.
9–15 — Asset Harvest Only	The offer has low recovery probability. Do not invest in resurrection. Run the Post-Kill Intelligence Extraction Protocol (Kill Criteria SOP Phase 6) to harvest IP assets. Use those assets to inform a new offer rather than attempt to revive the dead one.	Post-Kill Intelligence Extraction Protocol only.
0–8 — Permanent Retirement	The offer is not viable for resurrection. Retire permanently. If T6 scored 0 (auto-disqualify), the offer name and positioning must be retired permanently — do not attempt to relaunch under the same name.	Full retirement. Archive assets. No relaunch.

Source table 15

PHASE 2Root Cause DiagnosisConfirming which of the Seven Causes is responsible — not guessing

Source table 16

Signal	Threshold	Indicates
Tagged phrases account for more than 40% of the interview language	Count: tagged phrases ÷ total meaningful phrases > 40%	CAUSE 01 — Language Drift. The copy is speaking a different language from the market.
The mechanism name appears in fewer than 3 of 10 exit interview responses when buyers describe the offer	Count: interviews where buyer uses mechanism name ÷ 10 < 30%	CAUSE 01 (Language Drift) or CAUSE 02 (Mechanism Saturation). Run Instrument 2 to differentiate.
Zero divergence between interview language and sales page language — the copy is current but conversion is still dead	Divergence score < 10%	Rules out CAUSE 01 and CAUSE 02. Proceed to Instruments 3–5.

Source table 17

Score	Indicates
T-1 average below 6.0	CAUSE 02 — Mechanism Saturation confirmed. The name has lost its ability to generate excitement.
T-5 fails (2 or more testers report hearing the name elsewhere)	CAUSE 02 — Mechanism Saturation confirmed. The name has been adopted by competitors or overexposed.
T-1 above 7.0 but conversion is still dead	Rules out CAUSE 02. The mechanism name is working — the problem is elsewhere. Proceed to Instruments 3–5.

Source table 18

Profile	Indicates
More than 50% of current sales page testimonials are tagged 'Version-Specific (Retired)' or 'Price-Specific'	CAUSE 03 — Proof Staleness. The proof library has not been maintained as the offer evolved.
Testimonials are version-current but all from the same time period (more than 18 months ago) with no recent proof	CAUSE 03 — Proof Staleness (temporal). Recent buyers are not producing strong testimonials — investigate completion rate as a secondary signal.
Proof library is current and relevant	Rules out CAUSE 03. Proceed to Instruments 4–5.

Source table 19

Signal	Threshold	Indicates
3+ competitors are making near-identical promises with near-identical mechanism language	Count: similar promises and similar mechanism names ≥ 3	CAUSE 04 — Positioning Commoditisation. The category has caught up to the offer's original differentiation.
Dominant competitor delivery formats have shifted significantly from the offer's delivery format	Majority of top-ranked competitors now use a delivery format different from the offer's	CAUSE 06 — Delivery Model Obsolescence. The category's delivery norm has moved.
No significant competitor change — the category is essentially the same as at launch	No material change in competitor positioning or delivery	Rules out CAUSE 04 and CAUSE 06. Proceed to Instrument 5.

Source table 20

Signal	Indicates
Fewer than 10 community posts about the problem in 90 days AND Google Trends showing declining search volume	CAUSE 07 — Problem Dissolution. The market for this offer is contracting at the problem level, not the offer level.
Community posts active, AI search results show the problem as current but reference different solution approaches than the offer	CAUSE 05 — Avatar Obsolescence or CAUSE 04 — Positioning Commoditisation. The problem exists but the buyer's solution expectations have shifted.
Community posts active, AI search results confirm the problem as unsolved, search volume stable	Rules out CAUSE 07. The market exists. The problem is in the offer's positioning or proof, not the market itself.

Source table 21

Field	Document Here
Primary cause (Cause 01–07)
Evidence supporting primary cause (instrument results)
Secondary cause (if identified)
Evidence supporting secondary cause
Causes ruled out and evidence
Resurrection pathway (from Phase 4)
Estimated resurrection timeline
Resurrection justified? (Triage score + cause confirms viability)	Yes / No

Source table 22

PHASE 3The Resurrection Readiness AssessmentConfirming the offer is worth rebuilding before any rebuild work begins

Source table 23

Asset Category	What to Inventory	Resurrection Value
Buyer language database	All tagged PAIN-ACUTE, PAIN-CHRONIC, DESIRE-HIDDEN, and OBJECTION phrases from exit interviews, support tickets, and refund messages collected during the offer's active period.	Highest — verbatim buyer language is the most expensive asset to recreate. Even a dead offer's language database provides 12–18 months of market intelligence that would take a new offer's first year to accumulate.
Proof library	All testimonials, case studies, and results documentation. Note which are version-current vs version-specific-retired.	High — specific-metric proof from real buyers cannot be manufactured. Even retired testimonials may be eligible for specific applications (mechanism-agnostic results remain valid regardless of mechanism rename).
Mechanism framework	The underlying methodology, frameworks, and IP — separate from the mechanism name. The name may be dead; the methodology may be fully alive.	High — the methodology survived the offer's death. The resurrection may require only a rename and repositioning, not a rebuild of the intellectual content.
Delivery infrastructure	The course platform build, module structure, worksheet templates, email sequences, and onboarding architecture.	Moderate — reusable with edits. If the cause is Language Drift or Mechanism Saturation, delivery infrastructure can be used largely unchanged. If Delivery Model Obsolescence, significant modification is required.
Negative avatar data	Refund root cause codes, Negative Avatar profiles, exit interview data from buyers who did not get results.	High — knowing precisely who this offer does NOT serve is as valuable as knowing who it does serve. This data prevents the same wrong-fit buyers from being attracted in the relaunch.
Traffic and conversion data	Historical conversion rates by source, by copy test variant, by guarantee version — the performance record of the offer at its best.	Moderate — establishes the benchmark the resurrection must beat to be considered successful. Also identifies which traffic sources and copy approaches produced the best results when the offer was working.

Source table 24

The Improvement StandardThe resurrected offer must score at least 1 point higher than the dead offer's final Offer Scorecard on each dimension that the diagnosis identified as a contributing cause. If Cause 01 (Language Drift) was the primary cause, D1 (Dream Outcome Clarity) must score at least 1 point higher on the resurrected offer than the dead offer's last recorded D1 score. If Cause 03 (Proof Staleness) contributed, D7 must improve. The improvement must be documentable — not subjective.

Source table 25

PHASE 4The Four Resurrection PathwaysMatching the cause to the correct rebuild approach

Source table 26

Pathway A — For: CAUSE 01 (Language Drift) and CAUSE 02 (Mechanism Saturation)Timeline: 21–30 daysVersion change type: Minor (CAT-M for mechanism rename + CAT-C for copy update)Delivery changes: None required

Source table 27

Step	Action	Timeline	Output
A1	Run the full Buyer Language Mining Refresh from the Forensic Audit Loop SOP Phase 3. Pull exit interviews and support tickets from the last 6 months. Tag all PAIN-ACUTE, PAIN-CHRONIC, and DESIRE-HIDDEN phrases. Build the refreshed language list.	Days 1–5	Updated buyer language database with current-market vocabulary
A2	Run the full 10× Mechanism Test Protocol (Phase 2 of the 10× Mechanism Test SOP) on the current mechanism name to confirm the T-1 and T-5 scores. If T-1 below 7.0 or T-5 fails: proceed to mechanism rename. If both pass: the mechanism name is not the issue — revisit the language diagnosis.	Days 3–7	10× Test scorecard confirming whether rename is required
A3	If rename required: run Phase 3 of the 10× Mechanism Test SOP (Name Generation System) using all six generation methods. Minimum 15 candidates. Select the top 5 for testing. Test with avatar-matched individuals. Select the winner (7.5+ T-1 score required).	Days 6–14	New mechanism name scoring 7.5+ on T-1, confirmed distinct and memorable
A4	Rebuild the sales page copy from a fresh copy brief using the updated buyer language database. The rebuild is not an edit of the old copy — it is a new document written from the buyer language data upward. Lead, mechanism section, stack section, guarantee section, FAQ section — all rewritten.	Days 10–21	New sales page copy in draft. Not yet live.
A5	Rebuild the 14-day email sequence Days 8–10 (mechanism introduction emails) using the new mechanism name and updated language. Update all other sequence emails where the old language appears.	Days 14–21	Updated email sequence. Not yet live.
A6	Update all assets per the Product Versioning SOP Copy & Asset Sync Checklist (Phase 5). File a Minor version changelog entry (CAT-M + CAT-C).	Days 21–28	All assets updated. Changelog filed. Version deployed.
A7	Run a 14-day soft relaunch to the warm list only. Do not launch to cold paid traffic until warm conversion is confirmed. Target: warm conversion above 5% from the email sequence before adding any paid traffic.	Days 28–42	Warm relaunch data. Conversion confirmed before cold expansion.

Source table 28

Pathway B — For: CAUSE 03 (Proof Staleness) and supporting secondary causesTimeline: 30–45 daysVersion change type: Minor (CAT-O for stack update + CAT-C for copy update)Delivery changes: None required for proof refresh; potential bonus changes for stack rebuild

Source table 29

Step	Action	Timeline	Output
B1	Run the Proof Harvesting Protocol (Beta Testing Methodology SOP Phase 6). Re-contact the top 20% of prior buyers by result achieved. Conduct structured exit interviews specifically designed to capture current, metric-specific testimonials using current language.	Days 1–14	New exit interview recordings. Minimum 5 usable metric-specific testimonials.
B2	Run the Testimonial Audit Protocol (Product Versioning SOP Phase 5). Retire all version-specific testimonials that reference retired elements. Identify which current testimonials are version-current and proof-to-promise matched.	Days 7–10	Cleaned testimonial registry. Clear picture of current proof assets.
B3	Build two or three detailed case studies from the new interview data. Structure each as: Avatar → Problem → Attempt → Discovery → Result (with specific metrics). These become the primary proof assets on the rebuilt sales page.	Days 10–21	2–3 production-ready case studies with specific metrics.
B4	Audit the bonus stack against the Bonus Discipline Audit SOP. If any bonus has a Buyer Utility Score below 5.0: run the Reform or Cut protocol. Add new bonuses to address sub-problems the new buyer language audit identifies.	Days 10–21	Updated bonus stack passing all five Bonus Discipline Audit dimensions.
B5	Rebuild the sales page proof section entirely. Lead with the strongest new case study. Follow with the stack of current testimonials. Ensure every testimonial is proof-to-promise matched — each one answers a specific objection from the Objection Bank.	Days 21–30	Rebuilt proof section. Testimonials aligned to objections.
B6	Update all assets per the Product Versioning SOP Sync Checklist. File changelog entry.	Days 28–35	Assets synced. Changelog filed.
B7	Soft relaunch to warm list. Target: warm conversion above 5% and testimonial collection rate above 20% of new buyers in first 30 days.	Days 35–65	Warm relaunch data with proof collection ongoing.

Source table 30

Pathway C — For: CAUSE 04 (Positioning Commoditisation) and CAUSE 05 (Avatar Obsolescence)Timeline: 45–60 daysVersion change type: Major (CAT-M) — fundamental repositioningDelivery changes: Possible but not required

Source table 31

Step	Action	Timeline	Output
C1	Run the Category Gap Analysis. Map all direct competitors' current positioning: their avatar, their promise, their mechanism, their price. Identify the specific white space — the sub-avatar, sub-problem, or sub-mechanism that is underserved by the current competitive landscape.	Days 1–10	Category positioning map. White space identified with specific evidence.
C2	Define the new target avatar precisely. This may be the same broad category but a different stage, context, or constraint. Example: 'B2B SaaS founders' is too broad. 'B2B SaaS founders at the $1M–$5M ARR stage preparing for Series A' is the level of specificity required for a repositioned offer.	Days 7–14	New avatar definition: one paragraph, specific enough to identify a real person in a room. JTBD statement for the new avatar.
C3	Run the MVO Playbook Phase 2 process (Trim & Stack) from the perspective of the new avatar and the white space identified in C1. Identify which components of the existing delivery survive unchanged, which require modification, and which can be retired.	Days 10–21	Updated offer stack designed for the new avatar and new position. Components preserved vs modified vs retired documented.
C4	Rename the offer. When an offer repositions for a new avatar or moves into white space, the name often needs to change to signal the new position. Apply the 10× Mechanism Test & Rename Cadence SOP name generation process to the new position.	Days 14–21	New offer name and mechanism statement for the repositioned offer.
C5	Rebuild sales copy, email sequence, and all buyer-facing assets from scratch for the new avatar. Do not edit existing copy — the existing copy was built for the old position. Building on it produces muddled positioning.	Days 21–40	New copy brief. New sales page draft. New email sequence draft.
C6	Run the Negative Avatar Modelling SOP to build repulsion layers for the wrong-fit avatars that were attracted to the previous position. These now become the 'Not for you if' section of the new offer page.	Days 28–40	Updated Negative Avatar profiles. Repulsion language integrated into new copy.
C7	Beta test the repositioned offer with 5–10 buyers from the new avatar profile before public launch. This is not optional — a repositioned offer is effectively a new offer and requires beta validation (Beta Testing Methodology SOP).	Days 40–60	Beta data: conversion at beta price, completion rate, early results. Go/No-Go scorecard passed.
C8	File as a Major version change (CAT-M). Run the full Product Versioning SOP deployment protocol including buyer communication.	Days 58–65	Major version deployed. Changelog filed. Communications sent.

Source table 32

Pathway D — For: CAUSE 06 (Delivery Model Obsolescence) — and as secondary pathway for CAUSE 04 when delivery is the competitive disadvantageTimeline: 60–90 daysVersion change type: Major (CAT-D)Delivery changes: Required — the delivery model is the primary change

Source table 33

Step	Action	Timeline	Output
D1	Run the Fulfilment Stress Test SOP (Phases 1–3) for the proposed new delivery model before designing anything. Confirm: capacity ceiling for the new format, total delivery time per buyer under the new model, and whether the founder's schedule can support the upgrade.	Days 1–14	Fulfilment Stress Test results for proposed new delivery format. Go/No-Go on capacity.
D2	Define the delivery model upgrade specifically. Common transitions: self-paced → live cohort (adds synchronous community and accountability); group coaching → small-group intensive (reduces buyer count, increases intensity); recorded content → AI-augmented delivery (adds personalised feedback loops without proportional time cost).	Days 7–14	New delivery architecture document. One paragraph per delivery component: what it is, how it works, who delivers it, how often.
D3	Run the Price Elasticity Testing Framework SOP Phase 1 (Estimation Method) for the new delivery model. A delivery model upgrade typically justifies a price increase — confirm the market will support it before building.	Days 7–21	Price range for the upgraded offer. New price point selected using Van Westendorp or competitor benchmarking.
D4	Redesign the course platform architecture for the new delivery model. Update module structure, add live session integration, update onboarding, build community structure if new, create accountability touchpoints if new.	Days 21–50	Rebuilt delivery infrastructure. Platform-tested with a test cohort of 2–3 people before launch.
D5	Rebuild the guarantee to match the new delivery model. A live cohort can support a stronger guarantee than a self-paced course. A DWY model can support a service completion guarantee. Use the Guarantee Type Testing Protocol SOP to design and test the appropriate new guarantee level.	Days 28–45	New guarantee language matched to new delivery format.
D6	Rebuild the sales page for the new delivery model. The delivery format is a core component of the buyer's decision — it must be foregrounded in the copy, not buried in the FAQ.	Days 35–55	New sales page draft including delivery format as a primary value element.
D7	Run a pre-sell to the warm list before building the full new delivery system. Announce the upgraded version, describe the new delivery format, and offer founding member pricing. If fewer than 5 buyers commit from a list of 500+ engaged subscribers: the delivery upgrade alone is not sufficient — revisit the cause diagnosis (Pathway C may be needed alongside Pathway D).	Days 50–65	Pre-sell data. Founding member commitments. Go/No-Go on full build.
D8	Build, beta test, and launch per the Beta Testing Methodology SOP. File a Major version change (CAT-D).	Days 60–90	Beta complete. Major version deployed. Changelog filed.

Source table 34

PHASE 5The Relaunch ProtocolHow to bring the resurrected offer back to market without reactivating the failure memory

Source table 35

The New Chapter FrameThe resurrected offer is not presented as 'updated' or 'improved.' It is presented as the result of a period of deep learning, research, and rebuilding. The copy acknowledges that the prior version had limitations (specific, honest, brief), explains what was learned, describes what was rebuilt and why it is fundamentally better, and positions the relaunch as a deliberate decision made with new evidence rather than a hasty fix. This framing converts sceptics who dismissed the original offer into curious prospects for the new version.

Source table 36

Phase	Timing	Action	Target
Pre-Relaunch Intelligence Collection	21–30 days before relaunch	Interview 5–10 people who encountered the original offer and did not purchase. Ask: 'What specifically stopped you from buying [original offer]?' Document the exact language. This feeds the relaunch copy's objection-handling section and ensures the new version directly addresses the reasons the original failed to convert.	Verbatim objection data from non-purchasers of the original offer.
Existing Buyer Advance Notice	14 days before relaunch	Email existing buyers from the original offer: inform them that the offer has been rebuilt, explain what changed and why, and give them first access at founding member pricing if they want to re-engage or refer someone. This converts your existing buyer relationship from a liability (they know the flaws of the original) into an asset (they can see the genuine improvement).	Goodwill maintained. Potential early referrals from existing buyers who have seen the improvement.
Waitlist Build	14–7 days before relaunch	Open a waitlist for the relaunched offer with a one-sentence description of the core change: 'We spent [X months] rebuilding [offer name] from the ground up. If [specific problem] is still a challenge for you, join the list for first access.' No long copy. No over-selling. Just the announcement and the waitlist link.	50+ waitlist signups confirming warm market interest before full relaunch email sequence.
Relaunch Email Day 1 — The Honest Pivot Story	Relaunch Day 1	The founder sends a personal, plain-text email telling the story of what they learned, what they changed, and why they rebuilt rather than retired. The tone is honest: 'The original version had this specific limitation. Here's what I learned from buyers. Here's what I rebuilt. Here's the result.' This email is the Epiphany Bridge for the resurrected offer.	Email open rate above 30%. Reply rate above 2% — replies indicate genuine re-engagement.
Relaunch Email Day 2 — New Proof and New Mechanism	Relaunch Day 2	Present the new mechanism name (if renamed), the new case study from the Proof Harvest Protocol, and the updated guarantee. Lead with a buyer who went through the original version and came back for the rebuild — the arc of a returning buyer is the most powerful relaunch proof available.	New mechanism introduced. New proof deployed. Guarantee reinforced.
Relaunch Email Day 3 — The What Changed Comparison	Relaunch Day 3	Side-by-side comparison of the original versus the resurrected offer across 5–6 specific dimensions: delivery format, mechanism name, guarantee, specific result promised, support structure, price. Make the improvement concrete and specific — not 'we improved everything' but 'the guarantee went from 30-day money-back to conditional result-based. The mechanism was renamed from X to Y. The delivery format changed from self-paced to live cohort.'	Specificity of change creates credibility. Buyers who dismissed the original now have a reason to re-evaluate.
Relaunch Email Day 5 — Objection Handling	Relaunch Day 5	Using the pre-relaunch interview data (Phase 5, step 1), directly address the top 3 objections that stopped people from buying the original offer. Each objection gets one sentence validation, one sentence reframe, and one sentence of evidence that the rebuilt offer resolves it.	Objection Bank entries addressed. Non-converters from the original offer given specific reasons to reconsider.
Relaunch Email Day 7 — Final Call	Relaunch Day 7	Standard deadline email using the relaunch window closing mechanism. If founding member pricing was offered: it closes tonight. If cohort spots were limited: this is the last call. Hard close at the stated deadline — no exceptions.	Final push. Deadline enforced.

Source table 37

Gate Metric	Minimum Threshold	What It Confirms
Warm conversion rate from the 7-day relaunch sequence	Above 3% of the warm list who received the sequence	The resurrected offer is converting its most favourable audience. Cold traffic conversion will be lower — but 3% warm is evidence the offer works for a motivated buyer.
Refund rate in first 14 days	Below 8%	No expectation mismatch between the new positioning and the actual delivery.
Completion rate (Module 1 within 72 hours)	Above 60%	The new onboarding and Quick Win architecture is working. Buyers are engaging.
Spontaneous testimonial collection rate	At least 1 specific-metric testimonial from every 10 new buyers	The resurrected offer is producing results. This data feeds the next proof refresh cycle.

Source table 38

PHASE 6The Post-Resurrection Monitoring ProtocolConfirming the resurrection held under real-world conditions

Source table 39

Week	Monitoring Focus	Alert Threshold	Action If Threshold Crossed
Weeks 1–2	Warm conversion rate and early refund rate. The first 14 days reveal whether the new positioning and new proof are landing with the engaged warm audience.	Warm conversion below 2% after full 7-day sequence delivery. OR refund rate above 10%.	Pause relaunch. Run emergency Refund Forensics. Do not add cold traffic until warm performance is confirmed.
Weeks 3–4	Completion rate and Module 1 dropout rate. The delivery model upgrade (if applied) must demonstrate improved engagement within the first cohort cycle.	Completion rate below 35% in first 14 days of access (below Pathway D expectation for the new delivery format).	Run the Time-and-Motion Audit (Fulfilment Stress Test SOP Phase 3). Identify where buyers are dropping out and why.
Weeks 5–8	Cold conversion rate (if paid traffic or organic promotion has been added). Compare against the dead offer's final cold conversion rate AND the offer's historical peak.	Cold conversion below 0.8% after 200+ unique cold visitors.	Do not increase cold traffic spend. Run the Pre-Kill Diagnostic to confirm whether the issue is the offer or the traffic source.
Weeks 9–12	Revenue trend, ascension rate, and NPS. The full 90-day performance picture.	Revenue declining week-over-week for 3 consecutive weeks after the initial launch spike subsides. OR NPS below 20.	Run the full Offer Scorecard. If composite score below 40 after 90 days: the resurrection has not held. Apply the Kill Criteria SOP to determine next action.

Source table 40

Criterion	Success Threshold	How to Measure
Cold conversion rate	Above 1.0% — meeting or exceeding the offer's prior peak baseline	GA4 + CRM: rolling 30-day cold conversion rate
Warm conversion rate	Above 5% — meeting or exceeding the offer's prior peak warm performance	Email platform + CRM: conversion from 14-day sequence completion
Refund rate	Below 8% rolling 30 days	Stripe rolling 30-day refund rate
Completion rate	Above 45% — at or above the Offer Scorecard D11 viable threshold	Course platform analytics: module completion tracking
Offer Scorecard composite	Above 45/75 (B-grade or C-grade minimum with clear trajectory of improvement)	Monthly Offer Scorecard session

Source table 41

RESURRECTION SUCCESSFULAll five criteria met for 30+ consecutive daysThe offer has been revived. Treat it as a newly-relaunched offer in its early-traction phase.Next actions:— Schedule the Price Elasticity Testing Framework SOP to test whether the resurrected offer can support a price increase.— Continue the Offer Scorecard monthly cadence to track ongoing improvement.— Update the 10× Mechanism Test & Rename Cadence SOP quarterly test calendar with the new mechanism name.— Log the complete resurrection record in Airtable (see Phase 7 schema).

Source table 42

RESURRECTION INCOMPLETE — CONTINUE MONITORING3–4 of 5 criteria met at 90-day markThe resurrection is producing improvement but has not yet reached full viability. This is a positive signal — the root cause diagnosis was correct and the pathway is working. Extend the monitoring window to 120 days. Do not declare failure or success at 90 days if trend is positive.Key question: is the trend upward (metrics improving week-over-week) or flat? Upward trend at 90 days = continue. Flat trend at 90 days for 30+ days = revisit whether a secondary cause was missed in the diagnosis.

Source table 43

RESURRECTION FAILED — ESCALATE TO KILL CRITERIA SOPFewer than 3 criteria met at 90-day mark and no positive trendThe resurrection pathway did not resolve the root cause, or the root cause diagnosis was incorrect. The offer cannot be revived in its current form.Next actions:— Do NOT attempt a second resurrection immediately. Run the Post-Kill Intelligence Extraction Protocol (Kill Criteria SOP Phase 6) first.— Review the cause diagnosis: which instrument was most likely incorrect? What did the 90-day operation reveal that the diagnosis missed?— Evaluate the IP assets for repurposing into a new offer (see Triage Score 9–15: Asset Harvest Only).— File the full resurrection record in Airtable. This data has high value for future offer development.

Source table 44

PHASE 7The Resurrection Intelligence RecordEverything that was learned, preserved for every future offer in the business

Source table 45

Field	Type	Notes
Resurrection ID	Autonumber	Format: RES-[Offer Code]-[YYYY-MM]
Offer	Link → Offers table
Offer Mortality State at Triage	Single select	Flatline / Retired
Triage Score	Number	Out of 30
Triage Decision	Single select	High Priority / Conditional / Asset Harvest / Permanent Retirement
Primary Root Cause	Single select	Cause 01–07
Secondary Root Cause (if any)	Single select	Cause 01–07 / None
Diagnosis Confidence Level	Single select	High (80%+) / Moderate (60–79%) / Low (<60%)
Resurrection Pathway Used	Single select	Pathway A / B / C / D
Resurrection Start Date	Date
Resurrection Completion Date (relaunch)	Date
Total Resurrection Duration (days)	Formula	Completion Date minus Start Date
Offer Scorecard — Dead Offer Final Score	Number	Score from last Offer Scorecard before death/flatline
Offer Scorecard — Resurrected Offer Score (30 days post-relaunch)	Number
Offer Scorecard Improvement Delta	Formula	Post-relaunch minus final pre-death score
Cold Conversion — Dead Offer Final Rate	Number	% in final 30 days before death
Cold Conversion — Resurrected Offer (90-day post-relaunch)	Number	% rolling 30-day at 90-day mark
Warm Conversion — Dead Offer Final Rate	Number
Warm Conversion — Resurrected Offer (90-day)	Number
Refund Rate — Dead Offer Final	Number
Refund Rate — Resurrected Offer (90-day)	Number
Completion Rate — Resurrected Offer (first full cohort)	Number
Resurrection Outcome	Single select	Successful / Incomplete (Continuing) / Failed
Revenue Impact (annualised estimate)	Currency	Estimated annual revenue from resurrected offer
IP Assets Recovered	Long text	List of buyer language, proof, mechanism framework assets preserved from the original offer and deployed in the resurrection
Key Diagnostic Finding	Long text	The single most important thing this resurrection process revealed about why offers die in this market. One sentence, specific enough to change a future offer design decision.
What the Dead Offer's Market Intelligence Revealed	Long text	New insights about the avatar, the problem, the competitive landscape, or the category that did not exist before the resurrection diagnosis process
Buyer Language Update	Long text	New or significantly updated PAIN-ACUTE, PAIN-CHRONIC, and DESIRE-HIDDEN phrases added to the Buyer Language Mining database as a result of the resurrection diagnosis
Negative Avatar Profiles Updated	Link → Negative Avatar Profiles	Any new profiles or updates to existing profiles from resurrection diagnosis
Mechanism Name History	Long text	Old mechanism name → New mechanism name (if renamed). Reason for change. 10× Test scores before and after.
Version Changelog Entry	Link → Changelog Entries	The Major or Minor version entry from the Product Versioning SOP
Next Quarterly Review Date	Date	Schedule the first full Offer Scorecard 30 days post-relaunch

Native Word text, including document headers and footers

word/document.xml
RISER NATION
MASTER OPERATING SYSTEM
SOP — DEAD OFFER RESURRECTION PLAYBOOK
The Complete Diagnostic and Relaunch System for Offers That Have Stopped Converting — Without Wasting Another Dollar on a Broken Vehicle
Kennedy × Hormozi × Brunson × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
A dead offer is not always a failed offer. In most cases, it is a misdiagnosed one. Operators who kill an offer the moment it stops converting are destroying IP assets — buyer language databases, proof libraries, mechanism frameworks, and delivery infrastructure — that took months to build and represent genuine market intelligence. The offer that converted well for six months and then stopped is not broken. Something changed. Finding what changed, why it changed, and whether that change is reversible is the entire purpose of this SOP.
The Dead Offer Resurrection Playbook is the structured protocol for diagnosing why an offer stopped performing and determining whether it can be revived — and if so, precisely how. It distinguishes between the seven root causes of offer death, each of which requires a completely different resurrection approach. It defines the triage system for prioritising which dead offers are worth resurrecting. It provides the four resurrection pathways matched to specific cause types. And it gives the relaunch protocol that ensures the resurrected offer launches into the market as a new, differentiated product rather than a recycled version of something the market already dismissed.
This SOP connects directly to the Product Kill Criteria SOP (which defines when to kill an offer), the Forensic Audit Loop SOP (which provides the deep diagnostic tools this playbook draws from), the 10× Mechanism Test & Rename Cadence SOP (which governs mechanism refreshes), the Product Versioning SOP (which governs how the resurrected offer is logged and tracked), and the Beta Testing Methodology SOP (which governs the validation protocol before any resurrected offer re-enters the market publicly).
The Central Principle
An offer does not die. The conditions that made it work change. The market language evolves. Competitors enter and reframe the category. The buyer's awareness level rises and the copy that once felt fresh now feels familiar. The mechanism name that once triggered curiosity now sounds like every other programme. The operator's positioning drifts as the business grows. All of these are fixable. But only if the correct cause is identified before the fix is attempted.
Hormozi's Fuel Rule Applied to Resurrection
Never add fuel to a broken vehicle. This SOP exists to determine whether the vehicle can be repaired before any fuel is added. An operator who relaunches a dead offer to their warm list without diagnosing the root cause will burn their most valuable asset — their existing buyer relationship — on an unrepaired problem. Diagnose first. Repair completely. Then relaunch.
Defining a Dead Offer: The Three Mortality States
Before applying the resurrection protocol, the offer must be correctly classified. Not all underperforming offers are dead. An offer that is merely underperforming may need optimisation, not resurrection. An offer that is genuinely dead requires the full protocol. Using the resurrection playbook on an underperforming-but-alive offer wastes 60–90 days of diagnostic time.
Mortality State
Definition
Metrics Profile
Correct Response
DECLINING
Conversion rate is falling but still above the minimum viable threshold (0.5% cold). Revenue is decreasing month-over-month but the offer still generates sales.
Cold conversion: 0.5–1.4% (declining from prior baseline). Revenue: declining 15–40% from peak. Refund rate: stable or rising slightly.
Weekly Offer Review monitoring + Forensic Audit Loop (event-triggered). This is not a dead offer — it is an offer under pressure. The Forensic Audit Loop SOP handles declining offers. Refer to that SOP before using this one.
FLATLINE
Conversion rate has fallen below 0.5% cold and below 2% warm. Revenue has fallen below the minimum viable threshold. The offer is technically live but generating insufficient revenue to justify continued operation.
Cold conversion: below 0.5% for 30+ consecutive days. Warm conversion: below 2% after a full email sequence. Revenue: below the operational minimum for 45+ days.
This SOP applies. The offer is in the Flatline state — it requires full resurrection protocol or permanent retirement.
RETIRED
The offer was formally killed per the Product Kill Criteria SOP and removed from the market. Assets are archived. Buyers have been notified.
Zero sales for 60+ days. Sales page deactivated. Email sequence deactivated.
This SOP applies if the operator has identified a reason to believe the offer can be revived. See Phase 1 (Triage) for retirement eligibility criteria.
The Flatline vs Declining Distinction
An offer crossing from Declining into Flatline is the critical transition point. A Declining offer's cold conversion of 0.8% can still be profitable at the right volume with the right CPA. A Flatline offer's 0.3% cold conversion cannot be made profitable at any viable traffic volume — the economics break regardless of how much optimisation is applied to the funnel. The Flatline threshold is the trigger for this SOP.
The Seven Causes of Offer Death
Every dead offer died for one of seven reasons. Identifying the correct cause is the only diagnostic step that matters — because each cause requires a fundamentally different resurrection pathway. Applying the wrong pathway to the correct diagnosis produces no improvement. Applying the right pathway to the wrong diagnosis produces a relaunched offer that dies again, faster, with additional sunk cost.
CAUSE 01
Market Language Drift
Recovery Rate: High — 70% successful resurrection with correct language refresh
Definition
The language of the market — the words buyers use to describe their problem, the phrases they search, the vocabulary that signals belonging — has evolved significantly since the offer was launched. The offer's copy, mechanism name, and promise are no longer mirroring how the market talks about the problem. The offer is technically correct but emotionally foreign.
Primary diagnostic symptoms
Exit interviews and support tickets use significantly different vocabulary from the sales page. 10× Mechanism Test Health Indicator HI-5 (buyer language divergence) fires. GEO citation check shows the offer's mechanism name is absent from AI search results on category queries that used to surface it. New buyers describe the offer in ways that don't match the sales page language.
Resurrection approach
Buyer language mining refresh (Forensic Audit Loop SOP Phase 3). Full copy rebuild using current language data. Mechanism rename if Health Indicator HI-5 fires. Deploy within 30 days. No structural changes to delivery.
CAUSE 02
Mechanism Saturation
Recovery Rate: High — 75% successful resurrection with mechanism rename and repositioning
Definition
The offer's named mechanism — which was distinctive and curiosity-generating at launch — has been widely adopted by competitors or has become so familiar to the market through the operator's own content that it no longer generates a 'I've never heard of that before' response. The mechanism is now a commodity term.
Primary diagnostic symptoms
10× Mechanism Test scores below 7.0 on T-1 (Excitement) across test populations. T-5 (Distinctiveness) fails — testers report having heard similar names elsewhere. Organic content featuring the mechanism generates declining engagement over time. Competitors are using the same or near-identical mechanism language.
Resurrection approach
Full 10× Mechanism Test (10× Mechanism Test & Rename Cadence SOP). Run Phase 3 (Name Generation System) targeting a completely different pattern from the current name. New name must score 7.5+ on T-1 before deployment. Treat the mechanism rename as a Minor version change (CAT-M).
CAUSE 03
Proof Staleness
Recovery Rate: High — 65% successful resurrection with proof refresh
Definition
The offer's social proof — testimonials, case studies, and results cited on the sales page — no longer reflects the current buyer's situation, goals, or language. Early buyer results from 2023–2024 describe outcomes that today's buyer no longer relates to. The proof exists but doesn't connect.
Primary diagnostic symptoms
Offer Scorecard D7 (Social Proof Specificity) scores 1 or 2. Exit interviews from buyers who did purchase reveal they were uncertain about proof relevance. Heatmap shows low engagement at the testimonial section. Testimonial Version Registry shows most proof is tagged 'Version-Specific' for prior offer versions.
Resurrection approach
Proof Harvesting Protocol (Beta Testing Methodology SOP Phase 6). Re-interview prior buyers to capture current-language testimonials. Retire all version-specific-retired testimonials. Rebuild the sales page proof section with current proof matched to current promise language. Minimum 3 new metric-specific testimonials before relaunch.
CAUSE 04
Positioning Commoditisation
Recovery Rate: Moderate — 55% successful resurrection requiring significant repositioning investment
Definition
The offer occupied a differentiated position at launch — it was the first, or one of the few, to make a specific promise in a specific way to a specific avatar. The category has since filled with competing offers making similar promises in similar language. The offer is no longer distinctive because the category has caught up to it.
Primary diagnostic symptoms
Competitor benchmarking shows 3+ competitors making near-identical promises with near-identical mechanism names and similar price points. Organic content referencing the offer generates diminishing engagement. AI search engines return multiple competing offers when the category query is entered — the offer is no longer the dominant citation.
Resurrection approach
Category repositioning exercise: identify the specific sub-problem or sub-avatar that competitors are NOT serving. Rebuild the offer's position around that unclaimed space. This is a Major version change (CAT-M + possibly CAT-D if delivery changes). Requires a full relaunch protocol including beta testing.
CAUSE 05
Avatar Obsolescence
Recovery Rate: Moderate — 50% successful resurrection requiring avatar pivot
Definition
The specific buyer profile the offer was designed for has either moved on (the problem the offer solved is no longer their most urgent problem), grown out of it (they've achieved what the offer promised and there are fewer new entrants to that stage), or been absorbed by a different category of solution (a new tool, platform, or methodology has made the original problem irrelevant or solved it in a different way).
Primary diagnostic symptoms
Lead volume declining for the offer's landing page across all traffic sources simultaneously. Community discussions in the target niche show the original problem being discussed less frequently. Organic content about the problem generates declining engagement even when hook quality is high. Buyer interviews reveal the problem is still real but the buyers have changed their mental model of what 'solving it' looks like.
Resurrection approach
Avatar Pivot Protocol (see Phase 4 of this SOP). Identify the new or adjacent avatar who has the original problem but represents the current market entrant. Rebuild the offer positioning, copy, and mechanism language for the new avatar. May be treated as a new offer with the same underlying IP.
CAUSE 06
Delivery Model Obsolescence
Recovery Rate: Moderate-Low — 45% successful resurrection requiring delivery model upgrade
Definition
The way the offer delivers its promise has become outdated relative to market expectations. A self-paced course launched in 2022 may now compete against live cohort programmes with much higher perceived value. A group coaching programme may compete against AI-powered tools that deliver similar outputs at a fraction of the price. The delivery model no longer justifies the price relative to alternatives.
Primary diagnostic symptoms
Completion rate declining cohort-over-cohort despite no change in content quality. Exit interviews cite 'prefer live support' or 'expected more interaction' more frequently. Competitor delivery models offer more interactive formats at comparable or lower prices. Offer Scorecard D3 (Speed to First Win) declining as the market's benchmark for 'fast results' has risen.
Resurrection approach
Delivery model evaluation: identify the delivery format that current buyers in this category now expect. Design a delivery upgrade (self-paced → live cohort, group → DWY, sync → async + AI) that can be built within the operator's current fulfilment capacity. Run the Fulfilment Stress Test SOP before committing. Treat as Major version change (CAT-D).
CAUSE 07
Fundamental Problem Dissolution
Recovery Rate: Low — 25% successful resurrection. In most cases, this cause warrants permanent retirement rather than resurrection.
Definition
The underlying problem the offer was designed to solve no longer exists in the same form — or no longer exists at all. A tool-based problem was solved by a platform update. A platform-specific problem was dissolved when the platform changed its algorithm. A regulatory or compliance problem was changed by new legislation. The offer is technically correct but the problem it solves has been eliminated or fundamentally altered.
Primary diagnostic symptoms
All traffic sources declining simultaneously. Problem-focused organic content generates no engagement even when technically excellent. Buyer interviews reveal the problem is perceived as 'less of an issue than it used to be.' AI search engines return solutions that are fundamentally different from the offer category.
Resurrection approach
If the market data confirms Cause 07: Apply the Post-Kill Intelligence Extraction Protocol (Kill Criteria SOP Phase 6) rather than the resurrection pathway. The IP assets — buyer language data, mechanism frameworks, delivery infrastructure — should be evaluated for repurposing into a new offer addressing an adjacent, current problem. The resurrected offer in this case is effectively a new product.
PHASE 1
The Triage Protocol
Determining whether a dead offer is worth resurrecting before any diagnostic work begins
The Triage Principle
Not every dead offer deserves resurrection. Operator time and attention are finite. The triage protocol allocates resurrection effort to the offers with the highest probability of successful revival and the highest expected return on resurrection investment. An offer that scores below the triage threshold is retired permanently — its assets are harvested and its intelligence feeds the next offer rather than a resurrection attempt.
The Six Triage Criteria
Criterion
Scoring
Weight
T1 — Peak Performance Evidence
Did this offer ever achieve consistent cold conversion above 1.5% for 30+ consecutive days? Score: Yes = 5. Conversion above 0.8% for 30 days but not 1.5% = 3. No evidence of consistent viable conversion at any point = 1.
High — an offer that never worked cannot be resurrected; it was never alive.
T2 — Recoverable IP Value
Does the offer contain IP that is expensive to recreate — a named mechanism with a documented buyer language base, a proof library with 5+ specific-metric testimonials, a delivery system with documented completion rates? Score: Rich IP base = 5. Moderate IP = 3. Thin IP (generic content, no documented proof) = 1.
High — the resurrection investment is only justified if the IP worth saving exceeds the cost of the resurrection work.
T3 — Cause Diagnosability
Has a root cause been identified from the Seven Causes above with 80%+ confidence? Score: Clear single cause identified = 5. Two probable causes, both treatable = 3. Unclear or multiple conflicting causes = 1.
High — resurrection without a diagnosed cause is guesswork. Guessing wrong on cause wastes the same time as guessing right plus the time to diagnose.
T4 — Market Still Exists
Is the underlying problem the offer addresses still a current, active concern for the target avatar? Score: Problem confirmed active through current community data = 5. Problem likely still active but not recently confirmed = 3. Problem declining or dissolved = 1.
High — an offer addressing a dissolved problem cannot be resurrected; see Cause 07.
T5 — Relaunch Feasibility
Can the resurrection pathway for the identified cause be completed within 90 days with the operator's current team and resource capacity? Score: Feasible in 30 days = 5. Feasible in 60 days = 3. Feasible in 90 days = 2. Requires more than 90 days = 0.
Moderate — a 180-day resurrection is effectively a new offer. Apply the MVO Playbook instead.
T6 — Non-Contamination
Has the offer been retired cleanly without burning the market? If the offer died with a public failure (complaints, chargebacks, platform removals), the market's association with the offer name may be permanently negative. Score: Retired quietly, buyers treated fairly = 5. Minor public friction, resolved = 3. Significant public failure or reputational damage = 0 (auto-disqualify).
Moderate — market contamination from a badly-handled failure cannot be overcome by resurrection; rebranding as a new offer is the only viable path.
Triage Score Interpretation
Total Score
Decision
Next Step
24–30 — High Resurrection Priority
This offer has strong recovery probability and the resurrection investment is clearly justified. Proceed immediately to Phase 2 (Root Cause Diagnosis).
Begin Phase 2 within 7 days.
16–23 — Conditional Resurrection
The offer has moderate recovery probability. Proceed to Phase 2 but set a 45-day diagnostic deadline. If the root cause cannot be confirmed and the resurrection pathway defined within 45 days, retire the offer and redirect the IP assets.
Begin Phase 2. Set a 45-day diagnostic deadline with a hard gate.
9–15 — Asset Harvest Only
The offer has low recovery probability. Do not invest in resurrection. Run the Post-Kill Intelligence Extraction Protocol (Kill Criteria SOP Phase 6) to harvest IP assets. Use those assets to inform a new offer rather than attempt to revive the dead one.
Post-Kill Intelligence Extraction Protocol only.
0–8 — Permanent Retirement
The offer is not viable for resurrection. Retire permanently. If T6 scored 0 (auto-disqualify), the offer name and positioning must be retired permanently — do not attempt to relaunch under the same name.
Full retirement. Archive assets. No relaunch.
PHASE 2
Root Cause Diagnosis
Confirming which of the Seven Causes is responsible — not guessing
The Diagnosis Sequence
The root cause is identified by running five diagnostic instruments in sequence. The first instrument to return a positive result identifies the likely primary cause. Run all five regardless — secondary causes often exist and must be identified to prevent the resurrection from solving only the primary cause while the secondary cause kills it again.
Diagnostic Instrument 1 — The Buyer Language Divergence Audit
Pull the most recent 10 exit interview transcripts and the most recent 30 support tickets. Compare the vocabulary to the current sales page copy word-by-word. Tag every phrase in the interviews/tickets that does not appear anywhere on the sales page.
Signal
Threshold
Indicates
Tagged phrases account for more than 40% of the interview language
Count: tagged phrases ÷ total meaningful phrases > 40%
CAUSE 01 — Language Drift. The copy is speaking a different language from the market.
The mechanism name appears in fewer than 3 of 10 exit interview responses when buyers describe the offer
Count: interviews where buyer uses mechanism name ÷ 10 < 30%
CAUSE 01 (Language Drift) or CAUSE 02 (Mechanism Saturation). Run Instrument 2 to differentiate.
Zero divergence between interview language and sales page language — the copy is current but conversion is still dead
Divergence score < 10%
Rules out CAUSE 01 and CAUSE 02. Proceed to Instruments 3–5.
Diagnostic Instrument 2 — The 10× Mechanism Health Check
Run an informal version of the 10× Mechanism Test (Phase 2 of the 10× Mechanism Test & Rename Cadence SOP) with three avatar-matched individuals. Focus specifically on T-1 (Excitement), T-3 (Curiosity Trigger), and T-5 (Distinctiveness).
Score
Indicates
T-1 average below 6.0
CAUSE 02 — Mechanism Saturation confirmed. The name has lost its ability to generate excitement.
T-5 fails (2 or more testers report hearing the name elsewhere)
CAUSE 02 — Mechanism Saturation confirmed. The name has been adopted by competitors or overexposed.
T-1 above 7.0 but conversion is still dead
Rules out CAUSE 02. The mechanism name is working — the problem is elsewhere. Proceed to Instruments 3–5.
Diagnostic Instrument 3 — The Proof Audit
Open the Testimonial Version Registry (Product Versioning SOP). Count the number of testimonials currently on the sales page with each status.
Profile
Indicates
More than 50% of current sales page testimonials are tagged 'Version-Specific (Retired)' or 'Price-Specific'
CAUSE 03 — Proof Staleness. The proof library has not been maintained as the offer evolved.
Testimonials are version-current but all from the same time period (more than 18 months ago) with no recent proof
CAUSE 03 — Proof Staleness (temporal). Recent buyers are not producing strong testimonials — investigate completion rate as a secondary signal.
Proof library is current and relevant
Rules out CAUSE 03. Proceed to Instruments 4–5.
Diagnostic Instrument 4 — The Competitor Landscape Scan
Run a competitor scan across the five most visible competitors in the offer category. Specifically: what promises are they making, what mechanisms are they naming, and what delivery formats are they offering?
Signal
Threshold
Indicates
3+ competitors are making near-identical promises with near-identical mechanism language
Count: similar promises and similar mechanism names ≥ 3
CAUSE 04 — Positioning Commoditisation. The category has caught up to the offer's original differentiation.
Dominant competitor delivery formats have shifted significantly from the offer's delivery format
Majority of top-ranked competitors now use a delivery format different from the offer's
CAUSE 06 — Delivery Model Obsolescence. The category's delivery norm has moved.
No significant competitor change — the category is essentially the same as at launch
No material change in competitor positioning or delivery
Rules out CAUSE 04 and CAUSE 06. Proceed to Instrument 5.
Diagnostic Instrument 5 — The Market Existence Confirmation
Run three market existence checks to confirm the underlying problem is still active and the avatar still exists in sufficient numbers.
Reddit/Forum Scan: Search the top 3 communities in the niche for posts about the problem the offer addresses. Count posts from the last 90 days. If fewer than 10 posts in 90 days: the problem is declining in visibility.
AI Search Check: Ask ChatGPT, Perplexity, and Gemini the question a buyer at maximum problem awareness would ask ('How do I [problem the offer solves]?'). Review whether the responses suggest the problem is still active and unsolved, or whether they cite new solutions that effectively render the offer obsolete.
Google Trends Check: Run the primary keyword representing the problem on Google Trends. Look at the 2-year trend line. Declining search volume for the problem itself (not just for the offer) is a Cause 07 indicator.
Signal
Indicates
Fewer than 10 community posts about the problem in 90 days AND Google Trends showing declining search volume
CAUSE 07 — Problem Dissolution. The market for this offer is contracting at the problem level, not the offer level.
Community posts active, AI search results show the problem as current but reference different solution approaches than the offer
CAUSE 05 — Avatar Obsolescence or CAUSE 04 — Positioning Commoditisation. The problem exists but the buyer's solution expectations have shifted.
Community posts active, AI search results confirm the problem as unsolved, search volume stable
Rules out CAUSE 07. The market exists. The problem is in the offer's positioning or proof, not the market itself.
The Diagnosis Confirmation
After running all five instruments, complete the diagnosis confirmation:
Field
Document Here
Primary cause (Cause 01–07)
Evidence supporting primary cause (instrument results)
Secondary cause (if identified)
Evidence supporting secondary cause
Causes ruled out and evidence
Resurrection pathway (from Phase 4)
Estimated resurrection timeline
Resurrection justified? (Triage score + cause confirms viability)
Yes / No
PHASE 3
The Resurrection Readiness Assessment
Confirming the offer is worth rebuilding before any rebuild work begins
The Asset Inventory
Before choosing the resurrection pathway, take a complete inventory of what survives from the original offer. The resurrection ROI depends entirely on how much of the original IP can be preserved and reused — versus how much must be rebuilt from scratch.
Asset Category
What to Inventory
Resurrection Value
Buyer language database
All tagged PAIN-ACUTE, PAIN-CHRONIC, DESIRE-HIDDEN, and OBJECTION phrases from exit interviews, support tickets, and refund messages collected during the offer's active period.
Highest — verbatim buyer language is the most expensive asset to recreate. Even a dead offer's language database provides 12–18 months of market intelligence that would take a new offer's first year to accumulate.
Proof library
All testimonials, case studies, and results documentation. Note which are version-current vs version-specific-retired.
High — specific-metric proof from real buyers cannot be manufactured. Even retired testimonials may be eligible for specific applications (mechanism-agnostic results remain valid regardless of mechanism rename).
Mechanism framework
The underlying methodology, frameworks, and IP — separate from the mechanism name. The name may be dead; the methodology may be fully alive.
High — the methodology survived the offer's death. The resurrection may require only a rename and repositioning, not a rebuild of the intellectual content.
Delivery infrastructure
The course platform build, module structure, worksheet templates, email sequences, and onboarding architecture.
Moderate — reusable with edits. If the cause is Language Drift or Mechanism Saturation, delivery infrastructure can be used largely unchanged. If Delivery Model Obsolescence, significant modification is required.
Negative avatar data
Refund root cause codes, Negative Avatar profiles, exit interview data from buyers who did not get results.
High — knowing precisely who this offer does NOT serve is as valuable as knowing who it does serve. This data prevents the same wrong-fit buyers from being attracted in the relaunch.
Traffic and conversion data
Historical conversion rates by source, by copy test variant, by guarantee version — the performance record of the offer at its best.
Moderate — establishes the benchmark the resurrection must beat to be considered successful. Also identifies which traffic sources and copy approaches produced the best results when the offer was working.
The Minimum Viability Standard for Resurrection
A resurrection is only viable if the resurrected offer is materially better than the original in at least two of the three core dimensions: promise clarity (D1), mechanism believability (D2), and social proof specificity (D7) from the Offer Scorecard. Resurrecting an offer that is not materially improved from its final state re-enters the same market with the same weaknesses that killed it.
The Improvement Standard
The resurrected offer must score at least 1 point higher than the dead offer's final Offer Scorecard on each dimension that the diagnosis identified as a contributing cause. If Cause 01 (Language Drift) was the primary cause, D1 (Dream Outcome Clarity) must score at least 1 point higher on the resurrected offer than the dead offer's last recorded D1 score. If Cause 03 (Proof Staleness) contributed, D7 must improve. The improvement must be documentable — not subjective.
PHASE 4
The Four Resurrection Pathways
Matching the cause to the correct rebuild approach
Each resurrection pathway is designed for one or more specific cause types. Do not use a pathway for a cause it was not designed for — the effort will produce an improved offer that still dies for the original cause.
Pathway A — The Language and Mechanism Refresh
Pathway A — For: CAUSE 01 (Language Drift) and CAUSE 02 (Mechanism Saturation)
Timeline: 21–30 days
Version change type: Minor (CAT-M for mechanism rename + CAT-C for copy update)
Delivery changes: None required
Step
Action
Timeline
Output
A1
Run the full Buyer Language Mining Refresh from the Forensic Audit Loop SOP Phase 3. Pull exit interviews and support tickets from the last 6 months. Tag all PAIN-ACUTE, PAIN-CHRONIC, and DESIRE-HIDDEN phrases. Build the refreshed language list.
Days 1–5
Updated buyer language database with current-market vocabulary
A2
Run the full 10× Mechanism Test Protocol (Phase 2 of the 10× Mechanism Test SOP) on the current mechanism name to confirm the T-1 and T-5 scores. If T-1 below 7.0 or T-5 fails: proceed to mechanism rename. If both pass: the mechanism name is not the issue — revisit the language diagnosis.
Days 3–7
10× Test scorecard confirming whether rename is required
A3
If rename required: run Phase 3 of the 10× Mechanism Test SOP (Name Generation System) using all six generation methods. Minimum 15 candidates. Select the top 5 for testing. Test with avatar-matched individuals. Select the winner (7.5+ T-1 score required).
Days 6–14
New mechanism name scoring 7.5+ on T-1, confirmed distinct and memorable
A4
Rebuild the sales page copy from a fresh copy brief using the updated buyer language database. The rebuild is not an edit of the old copy — it is a new document written from the buyer language data upward. Lead, mechanism section, stack section, guarantee section, FAQ section — all rewritten.
Days 10–21
New sales page copy in draft. Not yet live.
A5
Rebuild the 14-day email sequence Days 8–10 (mechanism introduction emails) using the new mechanism name and updated language. Update all other sequence emails where the old language appears.
Days 14–21
Updated email sequence. Not yet live.
A6
Update all assets per the Product Versioning SOP Copy & Asset Sync Checklist (Phase 5). File a Minor version changelog entry (CAT-M + CAT-C).
Days 21–28
All assets updated. Changelog filed. Version deployed.
A7
Run a 14-day soft relaunch to the warm list only. Do not launch to cold paid traffic until warm conversion is confirmed. Target: warm conversion above 5% from the email sequence before adding any paid traffic.
Days 28–42
Warm relaunch data. Conversion confirmed before cold expansion.
Pathway B — The Proof and Stack Rebuild
Pathway B — For: CAUSE 03 (Proof Staleness) and supporting secondary causes
Timeline: 30–45 days
Version change type: Minor (CAT-O for stack update + CAT-C for copy update)
Delivery changes: None required for proof refresh; potential bonus changes for stack rebuild
Step
Action
Timeline
Output
B1
Run the Proof Harvesting Protocol (Beta Testing Methodology SOP Phase 6). Re-contact the top 20% of prior buyers by result achieved. Conduct structured exit interviews specifically designed to capture current, metric-specific testimonials using current language.
Days 1–14
New exit interview recordings. Minimum 5 usable metric-specific testimonials.
B2
Run the Testimonial Audit Protocol (Product Versioning SOP Phase 5). Retire all version-specific testimonials that reference retired elements. Identify which current testimonials are version-current and proof-to-promise matched.
Days 7–10
Cleaned testimonial registry. Clear picture of current proof assets.
B3
Build two or three detailed case studies from the new interview data. Structure each as: Avatar → Problem → Attempt → Discovery → Result (with specific metrics). These become the primary proof assets on the rebuilt sales page.
Days 10–21
2–3 production-ready case studies with specific metrics.
B4
Audit the bonus stack against the Bonus Discipline Audit SOP. If any bonus has a Buyer Utility Score below 5.0: run the Reform or Cut protocol. Add new bonuses to address sub-problems the new buyer language audit identifies.
Days 10–21
Updated bonus stack passing all five Bonus Discipline Audit dimensions.
B5
Rebuild the sales page proof section entirely. Lead with the strongest new case study. Follow with the stack of current testimonials. Ensure every testimonial is proof-to-promise matched — each one answers a specific objection from the Objection Bank.
Days 21–30
Rebuilt proof section. Testimonials aligned to objections.
B6
Update all assets per the Product Versioning SOP Sync Checklist. File changelog entry.
Days 28–35
Assets synced. Changelog filed.
B7
Soft relaunch to warm list. Target: warm conversion above 5% and testimonial collection rate above 20% of new buyers in first 30 days.
Days 35–65
Warm relaunch data with proof collection ongoing.
Pathway C — The Repositioning and Avatar Pivot
Pathway C — For: CAUSE 04 (Positioning Commoditisation) and CAUSE 05 (Avatar Obsolescence)
Timeline: 45–60 days
Version change type: Major (CAT-M) — fundamental repositioning
Delivery changes: Possible but not required
Step
Action
Timeline
Output
C1
Run the Category Gap Analysis. Map all direct competitors' current positioning: their avatar, their promise, their mechanism, their price. Identify the specific white space — the sub-avatar, sub-problem, or sub-mechanism that is underserved by the current competitive landscape.
Days 1–10
Category positioning map. White space identified with specific evidence.
C2
Define the new target avatar precisely. This may be the same broad category but a different stage, context, or constraint. Example: 'B2B SaaS founders' is too broad. 'B2B SaaS founders at the $1M–$5M ARR stage preparing for Series A' is the level of specificity required for a repositioned offer.
Days 7–14
New avatar definition: one paragraph, specific enough to identify a real person in a room. JTBD statement for the new avatar.
C3
Run the MVO Playbook Phase 2 process (Trim & Stack) from the perspective of the new avatar and the white space identified in C1. Identify which components of the existing delivery survive unchanged, which require modification, and which can be retired.
Days 10–21
Updated offer stack designed for the new avatar and new position. Components preserved vs modified vs retired documented.
C4
Rename the offer. When an offer repositions for a new avatar or moves into white space, the name often needs to change to signal the new position. Apply the 10× Mechanism Test & Rename Cadence SOP name generation process to the new position.
Days 14–21
New offer name and mechanism statement for the repositioned offer.
C5
Rebuild sales copy, email sequence, and all buyer-facing assets from scratch for the new avatar. Do not edit existing copy — the existing copy was built for the old position. Building on it produces muddled positioning.
Days 21–40
New copy brief. New sales page draft. New email sequence draft.
C6
Run the Negative Avatar Modelling SOP to build repulsion layers for the wrong-fit avatars that were attracted to the previous position. These now become the 'Not for you if' section of the new offer page.
Days 28–40
Updated Negative Avatar profiles. Repulsion language integrated into new copy.
C7
Beta test the repositioned offer with 5–10 buyers from the new avatar profile before public launch. This is not optional — a repositioned offer is effectively a new offer and requires beta validation (Beta Testing Methodology SOP).
Days 40–60
Beta data: conversion at beta price, completion rate, early results. Go/No-Go scorecard passed.
C8
File as a Major version change (CAT-M). Run the full Product Versioning SOP deployment protocol including buyer communication.
Days 58–65
Major version deployed. Changelog filed. Communications sent.
Pathway D — The Delivery Model Upgrade
Pathway D — For: CAUSE 06 (Delivery Model Obsolescence) — and as secondary pathway for CAUSE 04 when delivery is the competitive disadvantage
Timeline: 60–90 days
Version change type: Major (CAT-D)
Delivery changes: Required — the delivery model is the primary change
Step
Action
Timeline
Output
D1
Run the Fulfilment Stress Test SOP (Phases 1–3) for the proposed new delivery model before designing anything. Confirm: capacity ceiling for the new format, total delivery time per buyer under the new model, and whether the founder's schedule can support the upgrade.
Days 1–14
Fulfilment Stress Test results for proposed new delivery format. Go/No-Go on capacity.
D2
Define the delivery model upgrade specifically. Common transitions: self-paced → live cohort (adds synchronous community and accountability); group coaching → small-group intensive (reduces buyer count, increases intensity); recorded content → AI-augmented delivery (adds personalised feedback loops without proportional time cost).
Days 7–14
New delivery architecture document. One paragraph per delivery component: what it is, how it works, who delivers it, how often.
D3
Run the Price Elasticity Testing Framework SOP Phase 1 (Estimation Method) for the new delivery model. A delivery model upgrade typically justifies a price increase — confirm the market will support it before building.
Days 7–21
Price range for the upgraded offer. New price point selected using Van Westendorp or competitor benchmarking.
D4
Redesign the course platform architecture for the new delivery model. Update module structure, add live session integration, update onboarding, build community structure if new, create accountability touchpoints if new.
Days 21–50
Rebuilt delivery infrastructure. Platform-tested with a test cohort of 2–3 people before launch.
D5
Rebuild the guarantee to match the new delivery model. A live cohort can support a stronger guarantee than a self-paced course. A DWY model can support a service completion guarantee. Use the Guarantee Type Testing Protocol SOP to design and test the appropriate new guarantee level.
Days 28–45
New guarantee language matched to new delivery format.
D6
Rebuild the sales page for the new delivery model. The delivery format is a core component of the buyer's decision — it must be foregrounded in the copy, not buried in the FAQ.
Days 35–55
New sales page draft including delivery format as a primary value element.
D7
Run a pre-sell to the warm list before building the full new delivery system. Announce the upgraded version, describe the new delivery format, and offer founding member pricing. If fewer than 5 buyers commit from a list of 500+ engaged subscribers: the delivery upgrade alone is not sufficient — revisit the cause diagnosis (Pathway C may be needed alongside Pathway D).
Days 50–65
Pre-sell data. Founding member commitments. Go/No-Go on full build.
D8
Build, beta test, and launch per the Beta Testing Methodology SOP. File a Major version change (CAT-D).
Days 60–90
Beta complete. Major version deployed. Changelog filed.
PHASE 5
The Relaunch Protocol
How to bring the resurrected offer back to market without reactivating the failure memory
The Memory Reset Principle
A resurrected offer cannot be relaunched as 'the old offer, now fixed.' The market has a memory. Buyers who encountered the original offer and did not purchase — or purchased and were disappointed — have formed associations with the offer name, the mechanism name, and the operator's positioning that a simple 'we've improved it' email will not override. The relaunch must activate a distinct 'new chapter' frame.
The New Chapter Frame
The resurrected offer is not presented as 'updated' or 'improved.' It is presented as the result of a period of deep learning, research, and rebuilding. The copy acknowledges that the prior version had limitations (specific, honest, brief), explains what was learned, describes what was rebuilt and why it is fundamentally better, and positions the relaunch as a deliberate decision made with new evidence rather than a hasty fix. This framing converts sceptics who dismissed the original offer into curious prospects for the new version.
The Relaunch Sequence
Phase
Timing
Action
Target
Pre-Relaunch Intelligence Collection
21–30 days before relaunch
Interview 5–10 people who encountered the original offer and did not purchase. Ask: 'What specifically stopped you from buying [original offer]?' Document the exact language. This feeds the relaunch copy's objection-handling section and ensures the new version directly addresses the reasons the original failed to convert.
Verbatim objection data from non-purchasers of the original offer.
Existing Buyer Advance Notice
14 days before relaunch
Email existing buyers from the original offer: inform them that the offer has been rebuilt, explain what changed and why, and give them first access at founding member pricing if they want to re-engage or refer someone. This converts your existing buyer relationship from a liability (they know the flaws of the original) into an asset (they can see the genuine improvement).
Goodwill maintained. Potential early referrals from existing buyers who have seen the improvement.
Waitlist Build
14–7 days before relaunch
Open a waitlist for the relaunched offer with a one-sentence description of the core change: 'We spent [X months] rebuilding [offer name] from the ground up. If [specific problem] is still a challenge for you, join the list for first access.' No long copy. No over-selling. Just the announcement and the waitlist link.
50+ waitlist signups confirming warm market interest before full relaunch email sequence.
Relaunch Email Day 1 — The Honest Pivot Story
Relaunch Day 1
The founder sends a personal, plain-text email telling the story of what they learned, what they changed, and why they rebuilt rather than retired. The tone is honest: 'The original version had this specific limitation. Here's what I learned from buyers. Here's what I rebuilt. Here's the result.' This email is the Epiphany Bridge for the resurrected offer.
Email open rate above 30%. Reply rate above 2% — replies indicate genuine re-engagement.
Relaunch Email Day 2 — New Proof and New Mechanism
Relaunch Day 2
Present the new mechanism name (if renamed), the new case study from the Proof Harvest Protocol, and the updated guarantee. Lead with a buyer who went through the original version and came back for the rebuild — the arc of a returning buyer is the most powerful relaunch proof available.
New mechanism introduced. New proof deployed. Guarantee reinforced.
Relaunch Email Day 3 — The What Changed Comparison
Relaunch Day 3
Side-by-side comparison of the original versus the resurrected offer across 5–6 specific dimensions: delivery format, mechanism name, guarantee, specific result promised, support structure, price. Make the improvement concrete and specific — not 'we improved everything' but 'the guarantee went from 30-day money-back to conditional result-based. The mechanism was renamed from X to Y. The delivery format changed from self-paced to live cohort.'
Specificity of change creates credibility. Buyers who dismissed the original now have a reason to re-evaluate.
Relaunch Email Day 5 — Objection Handling
Relaunch Day 5
Using the pre-relaunch interview data (Phase 5, step 1), directly address the top 3 objections that stopped people from buying the original offer. Each objection gets one sentence validation, one sentence reframe, and one sentence of evidence that the rebuilt offer resolves it.
Objection Bank entries addressed. Non-converters from the original offer given specific reasons to reconsider.
Relaunch Email Day 7 — Final Call
Relaunch Day 7
Standard deadline email using the relaunch window closing mechanism. If founding member pricing was offered: it closes tonight. If cohort spots were limited: this is the last call. Hard close at the stated deadline — no exceptions.
Final push. Deadline enforced.
The Soft Relaunch Gate
Before any cold paid traffic is added to the relaunched offer, the warm relaunch must meet the minimum performance gate. Cold traffic on a relaunched offer that has not yet demonstrated warm conversion viability is the same mistake as cold traffic on the original dead offer.
Gate Metric
Minimum Threshold
What It Confirms
Warm conversion rate from the 7-day relaunch sequence
Above 3% of the warm list who received the sequence
The resurrected offer is converting its most favourable audience. Cold traffic conversion will be lower — but 3% warm is evidence the offer works for a motivated buyer.
Refund rate in first 14 days
Below 8%
No expectation mismatch between the new positioning and the actual delivery.
Completion rate (Module 1 within 72 hours)
Above 60%
The new onboarding and Quick Win architecture is working. Buyers are engaging.
Spontaneous testimonial collection rate
At least 1 specific-metric testimonial from every 10 new buyers
The resurrected offer is producing results. This data feeds the next proof refresh cycle.
PHASE 6
The Post-Resurrection Monitoring Protocol
Confirming the resurrection held under real-world conditions
The 90-Day Post-Resurrection Watch
A resurrection is not complete at relaunch. It is complete when the resurrected offer has demonstrated sustained performance across 90 days of real-world operation — matching or exceeding its prior peak performance on at least three of five key metrics. The 90-day window is the minimum window to confirm that the resurrection solved the root cause rather than producing a temporary performance spike from launch novelty.
Week
Monitoring Focus
Alert Threshold
Action If Threshold Crossed
Weeks 1–2
Warm conversion rate and early refund rate. The first 14 days reveal whether the new positioning and new proof are landing with the engaged warm audience.
Warm conversion below 2% after full 7-day sequence delivery. OR refund rate above 10%.
Pause relaunch. Run emergency Refund Forensics. Do not add cold traffic until warm performance is confirmed.
Weeks 3–4
Completion rate and Module 1 dropout rate. The delivery model upgrade (if applied) must demonstrate improved engagement within the first cohort cycle.
Completion rate below 35% in first 14 days of access (below Pathway D expectation for the new delivery format).
Run the Time-and-Motion Audit (Fulfilment Stress Test SOP Phase 3). Identify where buyers are dropping out and why.
Weeks 5–8
Cold conversion rate (if paid traffic or organic promotion has been added). Compare against the dead offer's final cold conversion rate AND the offer's historical peak.
Cold conversion below 0.8% after 200+ unique cold visitors.
Do not increase cold traffic spend. Run the Pre-Kill Diagnostic to confirm whether the issue is the offer or the traffic source.
Weeks 9–12
Revenue trend, ascension rate, and NPS. The full 90-day performance picture.
Revenue declining week-over-week for 3 consecutive weeks after the initial launch spike subsides. OR NPS below 20.
Run the full Offer Scorecard. If composite score below 40 after 90 days: the resurrection has not held. Apply the Kill Criteria SOP to determine next action.
The Resurrection Success Criteria
The resurrection is declared successful when all five criteria are met simultaneously for a minimum of 30 consecutive days:
Criterion
Success Threshold
How to Measure
Cold conversion rate
Above 1.0% — meeting or exceeding the offer's prior peak baseline
GA4 + CRM: rolling 30-day cold conversion rate
Warm conversion rate
Above 5% — meeting or exceeding the offer's prior peak warm performance
Email platform + CRM: conversion from 14-day sequence completion
Refund rate
Below 8% rolling 30 days
Stripe rolling 30-day refund rate
Completion rate
Above 45% — at or above the Offer Scorecard D11 viable threshold
Course platform analytics: module completion tracking
Offer Scorecard composite
Above 45/75 (B-grade or C-grade minimum with clear trajectory of improvement)
Monthly Offer Scorecard session
When to Declare the Resurrection Complete vs Re-Trigger the Kill Criteria
RESURRECTION SUCCESSFUL
All five criteria met for 30+ consecutive days
The offer has been revived. Treat it as a newly-relaunched offer in its early-traction phase.
Next actions:
— Schedule the Price Elasticity Testing Framework SOP to test whether the resurrected offer can support a price increase.
— Continue the Offer Scorecard monthly cadence to track ongoing improvement.
— Update the 10× Mechanism Test & Rename Cadence SOP quarterly test calendar with the new mechanism name.
— Log the complete resurrection record in Airtable (see Phase 7 schema).
RESURRECTION INCOMPLETE — CONTINUE MONITORING
3–4 of 5 criteria met at 90-day mark
The resurrection is producing improvement but has not yet reached full viability. This is a positive signal — the root cause diagnosis was correct and the pathway is working. Extend the monitoring window to 120 days. Do not declare failure or success at 90 days if trend is positive.
Key question: is the trend upward (metrics improving week-over-week) or flat? Upward trend at 90 days = continue. Flat trend at 90 days for 30+ days = revisit whether a secondary cause was missed in the diagnosis.
RESURRECTION FAILED — ESCALATE TO KILL CRITERIA SOP
Fewer than 3 criteria met at 90-day mark and no positive trend
The resurrection pathway did not resolve the root cause, or the root cause diagnosis was incorrect. The offer cannot be revived in its current form.
Next actions:
— Do NOT attempt a second resurrection immediately. Run the Post-Kill Intelligence Extraction Protocol (Kill Criteria SOP Phase 6) first.
— Review the cause diagnosis: which instrument was most likely incorrect? What did the 90-day operation reveal that the diagnosis missed?
— Evaluate the IP assets for repurposing into a new offer (see Triage Score 9–15: Asset Harvest Only).
— File the full resurrection record in Airtable. This data has high value for future offer development.
PHASE 7
The Resurrection Intelligence Record
Everything that was learned, preserved for every future offer in the business
Why the Record Is as Valuable as the Resurrection
The process of resurrecting a dead offer generates a category of market intelligence that a successfully-running offer never produces. The dead offer has failed, which means the market has communicated clearly what does not work. It has been compared to alternatives, which means competitive intelligence was accumulated. It has been diagnosed against seven causes, which means the operator now has a documented theory of why offers die in this specific market. All of that intelligence must be captured before the resurrection process closes — because it directly informs every future offer design decision.
Table — Resurrection Record
One record per completed resurrection process. File in Airtable under Resurrection Records.
Field
Type
Notes
Resurrection ID
Autonumber
Format: RES-[Offer Code]-[YYYY-MM]
Offer
Link → Offers table
Offer Mortality State at Triage
Single select
Flatline / Retired
Triage Score
Number
Out of 30
Triage Decision
Single select
High Priority / Conditional / Asset Harvest / Permanent Retirement
Primary Root Cause
Single select
Cause 01–07
Secondary Root Cause (if any)
Single select
Cause 01–07 / None
Diagnosis Confidence Level
Single select
High (80%+) / Moderate (60–79%) / Low (<60%)
Resurrection Pathway Used
Single select
Pathway A / B / C / D
Resurrection Start Date
Date
Resurrection Completion Date (relaunch)
Date
Total Resurrection Duration (days)
Formula
Completion Date minus Start Date
Offer Scorecard — Dead Offer Final Score
Number
Score from last Offer Scorecard before death/flatline
Offer Scorecard — Resurrected Offer Score (30 days post-relaunch)
Number
Offer Scorecard Improvement Delta
Formula
Post-relaunch minus final pre-death score
Cold Conversion — Dead Offer Final Rate
Number
% in final 30 days before death
Cold Conversion — Resurrected Offer (90-day post-relaunch)
Number
% rolling 30-day at 90-day mark
Warm Conversion — Dead Offer Final Rate
Number
Warm Conversion — Resurrected Offer (90-day)
Number
Refund Rate — Dead Offer Final
Number
Refund Rate — Resurrected Offer (90-day)
Number
Completion Rate — Resurrected Offer (first full cohort)
Number
Resurrection Outcome
Single select
Successful / Incomplete (Continuing) / Failed
Revenue Impact (annualised estimate)
Currency
Estimated annual revenue from resurrected offer
IP Assets Recovered
Long text
List of buyer language, proof, mechanism framework assets preserved from the original offer and deployed in the resurrection
Key Diagnostic Finding
Long text
The single most important thing this resurrection process revealed about why offers die in this market. One sentence, specific enough to change a future offer design decision.
What the Dead Offer's Market Intelligence Revealed
Long text
New insights about the avatar, the problem, the competitive landscape, or the category that did not exist before the resurrection diagnosis process
Buyer Language Update
Long text
New or significantly updated PAIN-ACUTE, PAIN-CHRONIC, and DESIRE-HIDDEN phrases added to the Buyer Language Mining database as a result of the resurrection diagnosis
Negative Avatar Profiles Updated
Link → Negative Avatar Profiles
Any new profiles or updates to existing profiles from resurrection diagnosis
Mechanism Name History
Long text
Old mechanism name → New mechanism name (if renamed). Reason for change. 10× Test scores before and after.
Version Changelog Entry
Link → Changelog Entries
The Major or Minor version entry from the Product Versioning SOP
Next Quarterly Review Date
Date
Schedule the first full Offer Scorecard 30 days post-relaunch
Master Dead Offer Resurrection Checklist
Pre-Triage
☐
Confirm the offer has crossed the Flatline threshold (cold conversion below 0.5% for 30+ days OR formally retired)
☐
Pull the final Offer Scorecard score for the dead offer — document as the baseline for comparison
☐
Pull all asset inventory: buyer language database, proof library, mechanism framework, delivery infrastructure, negative avatar data, traffic and conversion history
Phase 1 — Triage
☐
Score all six triage criteria (T1–T6)
☐
Calculate total triage score out of 30
☐
Confirm triage decision: High Priority / Conditional / Asset Harvest / Permanent Retirement
☐
If T6 scored 0 (auto-disqualify due to public failure): confirm permanent retirement. No resurrection pathway is viable.
☐
If Triage Score 9–15: run Post-Kill Intelligence Extraction Protocol only. Do not proceed to diagnosis.
Phase 2 — Root Cause Diagnosis
☐
Run Diagnostic Instrument 1 (Buyer Language Divergence Audit)
☐
Run Diagnostic Instrument 2 (10× Mechanism Health Check)
☐
Run Diagnostic Instrument 3 (Proof Audit)
☐
Run Diagnostic Instrument 4 (Competitor Landscape Scan)
☐
Run Diagnostic Instrument 5 (Market Existence Confirmation)
☐
Complete Diagnosis Confirmation table — primary cause, secondary cause, causes ruled out
☐
Confirm resurrection still justified after diagnosis (triage score + cause confirms viability)
Phase 3 — Resurrection Readiness
☐
Complete full asset inventory with resurrection value assessment
☐
Confirm Minimum Viability Standard: resurrected offer must score 1+ point higher on each cause-related Offer Scorecard dimension
☐
Select the appropriate Resurrection Pathway (A / B / C / D) based on primary cause
Phase 4 — Resurrection Pathway Execution
☐
Execute all steps of the selected pathway in sequence
☐
File the appropriate version changelog entry before any relaunch activity
☐
Complete the Product Versioning SOP Copy & Asset Sync Checklist for all changed elements
☐
For Pathway C or D: complete Beta Testing Methodology SOP before public relaunch
Phase 5 — Relaunch Protocol
☐
Conduct pre-relaunch intelligence collection (interview 5–10 non-purchasers of original offer)
☐
Send existing buyer advance notice 14 days before relaunch
☐
Open waitlist 7–14 days before relaunch
☐
Execute 7-day relaunch email sequence (Days 1, 2, 3, 5, 7)
☐
Confirm Soft Relaunch Gate: warm conversion above 3%, refund rate below 8%, completion rate above 60%
☐
Do not add cold paid traffic until Soft Relaunch Gate is passed
Phase 6 — Post-Resurrection Monitoring (90 Days)
☐
Set up 90-day monitoring calendar with weekly check-ins on the five key metrics
☐
Weeks 1–2: warm conversion and early refund rate
☐
Weeks 3–4: completion rate and Module 1 dropout
☐
Weeks 5–8: cold conversion (if traffic added)
☐
Weeks 9–12: revenue trend, ascension rate, NPS, Offer Scorecard
☐
Declare outcome at 90-day mark: Successful / Incomplete (Continue) / Failed
☐
If Failed: run Post-Kill Intelligence Extraction Protocol. Do not attempt second resurrection.
Phase 7 — Record and Intelligence Harvest
☐
Complete all fields of the Resurrection Record in Airtable
☐
Update Buyer Language Mining database with all new or updated language from the diagnosis process
☐
Update Negative Avatar Profiles with any new profiles identified during diagnosis
☐
Document the Key Diagnostic Finding in the record — one sentence, specific enough to inform future offer design
☐
Document what the market intelligence revealed — competitive insights, avatar evolution, category shifts
☐
Schedule the first full Offer Scorecard session 30 days post-relaunch
☐
Schedule the first quarterly 10× Mechanism Test for the new mechanism name 90 days post-relaunch
RISER Nation Master Operating System | Dead Offer Resurrection Playbook SOP | Version 1.0 | 2026 Edition
Kennedy × Hormozi × Brunson | risernation.com

word/header1.xml
RISER Nation | Dead Offer Resurrection Playbook SOP | V1.0

word/footer1.xml
Page
of

word/footnotes.xml

word/endnotes.xml

word/comments.xml

RISER-Downsell-Paths-SOP.docx

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

Working teaching draft. Source examples and policy assumptions require context; corrections and unresolved dependencies are identified in the script.

Design the right entry point for a real constraint

This SOP treats a downsell as a distinct way to help a buyer whose price, format, timing or commitment needs differ from the primary offer. It calls for a real sub-problem, independent positioning and a path to further help. The attributed Kennedy, Hormozi and Brunson statements are source interpretations, not verified quotations or endorsements. A buyer's no may simply mean no; a downsell is appropriate only when it actually fits and the buyer welcomes considering it.

D0929 — assigned source supporting this teaching point

Correct the first revenue example

The source introduces 100 declines, a $297 offer and 20% acceptance, yielding 20 sales and $5,940; that arithmetic is correct for 100 declines. Its later table instead starts with 100 visitors, two $997 purchases and 98 non-buyers. Twenty percent of 98 is 19.6 expected sales, producing $5,821.20 in modeled downsell revenue and $7,815.20 total, not $7,934. Twenty actual downsell orders would produce the table's $5,940, but that is about 20.41% of 98. Keep expected fractional counts separate from actual orders.

D0929 — assigned source supporting this teaching point

Correct the warm-list and call examples

For 50 warm openers at 15% conversion, expected primary sales are 7.5 and revenue is $18,727.50. The remaining 42.5 at 25% downsell acceptance and $497 produce $5,280.625, or $5,280.63 rounded, and $24,008.125 total, not the source's $5,303 and $24,031. The call example is consistent: twenty calls, five $5,000 closes and three $997 downsells produce $27,991 total. All are hypothetical models, not actual RISER sales or evidence of a typical recovery rate.

D0929 — assigned source supporting this teaching point

Measure incremental economics instead of assuming profit

The source attributes a 10–30% recovery range to Brunson without supplying the underlying study and calls downsells the highest-ROI mechanism. Treat both as unsupported generalizations here. Compare incremental contribution after fulfillment, fees, refunds, payment risk and any primary-offer cannibalization. More revenue per visitor can coexist with lower average order value. A lower-price product does not automatically make every traffic source profitable or reduce the underlying cost of acquiring a visitor.

D0929 — assigned source supporting this teaching point

Type 01: self-paced access

This type preserves useful curriculum, worksheets and resources while removing synchronous sessions for a buyer with schedule, timezone or format constraints. The source suggests 30–50% of live pricing, often for $997–$4,997 programs, and gives 15–25% conversion in one section and 15–20% for timing objections elsewhere. These are internal estimates. Confirm the buyer can achieve the promised result without live support; if that support is necessary, removing it does not create a viable independent offer.

D0929 — assigned source supporting this teaching point

Type 02: a lower-cost delivery format

The source proposes reducing costly one-to-one access, feedback or direct support while retaining a useful method and self-implementation tools, often for $3,000–$15,000 offers. It suggests 30–50% of primary pricing and 15–25% acceptance among price objectors. The learner must understand what changes and why the remaining support fits. A lower delivery cost is not sufficient if the buyer can no longer achieve the result.

D0929 — assigned source supporting this teaching point

Type 03: a useful standalone component

A module, template, swipe file or framework can become an independent offer when it solves a named urgent sub-problem. The source suggests 15–30% of primary pricing, 20–35% acceptance for fit uncertainty, and a connection to the Unbundling SOP. Its instruction not to remove motivation to ascend must not become deliberate withholding of what the component promises. Fully solve the stated sub-problem; a next offer should address a different need rather than repair an intentionally incomplete purchase.

D0929 — assigned source supporting this teaching point

Related source resources: RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx — related SOP ·

Type 04: payment timing for the full offer

A payment plan preserves scope and changes the payment schedule, so it is not structurally a smaller offer. The source proposes two to four payments over 30–90 days, totaling 110–120% of single-pay price, for offers above $500 and often $997–$4,997. Its 25–40% conversion and higher-refund-risk claims are unverified here. State the installment amount, number, dates, total, fees and applicable terms clearly. If the total is higher, the change is not only the schedule. Do not imply guaranteed affordability or pressure a buyer into debt.

D0929 — assigned source supporting this teaching point

Type 05: delayed entry with clear terms

For a qualified buyer with a defined future start date, the source proposes a confirmed future cohort, current-price reservation and a $97–$297 deposit credited to the full price. It estimates 30–45% acceptance for specific timing constraints. Document the start date, total balance, deposit treatment, cancellation/refund terms and what happens if the buyer still cannot begin. A deposit creates an obligation for the seller as well as the buyer; future capacity must actually exist.

D0929 — assigned source supporting this teaching point

Route price, timing and fit objections

For price, distinguish inability to pay all at once from inability to afford the total: the source routes the former to a payment plan and the latter to a lower-cost format. For timing, distinguish a temporary delay with a re-entry date from an ongoing synchronous-schedule problem. For fit uncertainty, identify a genuinely useful component rather than assuming everyone can be persuaded into a smaller purchase. The source's conversion ranges are hypotheses to test, not promises.

D0929 — assigned source supporting this teaching point

Route implementation, comparison and trust objections

Implementation concerns may call for self-paced progress when cohort speed is the issue, or a small first-win component when the starting point is unclear. If the buyer needs hands-on support, removing it may be the wrong response. For comparisons, clarify genuine differentiation; a component is an exception only when it solves the buyer's stated DIY gap. For distrust, provide relevant evidence and appropriate terms rather than treating a lower price as proof. The source's $47–$97 trust entry and 5–10%/40–60% outcome claims lack supporting data; no paid offer is literally zero risk.

D0929 — assigned source supporting this teaching point

Complete the full design brief

Record the DS-[Offer]-[Type]-[Seq] identifier, primary name/price/format, objection and specific buyer situation, type, standalone name, price and ratio, named sub-problem, two or three components, explicit exclusions, measurable promise, timeframe, guarantee and next-step trigger. The brief's 20–50% ratio is not appropriate to every type: components may start at 15%, a payment plan may total 110–120%, and deposits/free entry use different logic. Mark those exceptions instead of forcing the offer into an inconsistent template.

D0929 — assigned source supporting this teaching point

Channel 1: make a short checkout alternative with an exit

The source proposes a checkout-decline page or popup within two minutes, usually a component or payment plan. Its template asks for a headline of at most seven words, a brief 40–60-word bridge, two offer lines, one clear CTA and a visible no-thanks exit. Explain the actual scope and price without shaming the abandoned purchase. Detecting abandonment does not reveal the reason and should not trap the buyer in redirects. Test relevant alternatives against actual constraints rather than assuming a lower price is the answer.

D0929 — assigned source supporting this teaching point

Channel 2: follow a closed webinar offer with a distinct option

The source places one downsell email on Day 2, described as 24 hours after the primary close. It selects self-paced, reduced format or a component from observed objections. The template acknowledges the closed cart, cites a genuine reason heard from buyers, states the new product, exclusions, two or three components, price, guarantee, a real 48–72-hour deadline if applicable, one CTA and a respectful exit. A new offer must not secretly extend a supposedly final primary deadline. The learner drafts the message; this lesson sends nothing.

D0929 — assigned source supporting this teaching point

Channel 3: respond to the named objection on a call

The live template first acknowledges the decision, asks whether another relevant entry point is welcome, connects that option to the specific concern, describes two or three components and exclusions, states price/terms and asks whether it fits. If declined, close respectfully. The source's instruction to process within ten minutes is not a requirement to pressure a buyer or transact without consent. Staying on an email list or booking a follow-up requires the person's actual preference, not an assumption in the script.

D0929 — assigned source supporting this teaching point

Channel 4: introduce a standalone product to a warm subscriber

The source proposes a Day14 email after an unaccepted primary offer, often a $27–$97 component or future-cohort option. Its template uses a personal subject, an accurate reference to prior engagement, one-sentence fit, price, three to five benefit bullets and a direct link. It expressly uses no deadline and does not mention the primary offer. Avoid pretending to know reading behavior that was not reliably observed. First purchase may be associated with later purchases, but it does not prove a causal identity shift or guarantee ascension.

D0929 — assigned source supporting this teaching point

Channel 5: keep a personal message relevant and optional

The source limits this channel to meaningful prior engagement or conversation, with at least two organic touchpoints in the matrix. The template names a real observation, explains relevance, describes the product and price, offers a link if wanted and makes declining easy. Its one-message-unless-reply rule conflicts with a suggested non-sales follow-up five days later. Use the recipient's expressed preferences and stop when they decline; a disguised sales follow-up is not made appropriate by calling it non-sales. No outreach is performed here.

D0929 — assigned source supporting this teaching point

Channel 6: disclose a payment option clearly in Q&A

The source suggests one announcement five to seven minutes into Q&A after two or three substantive questions. State the full program, installments, total and where terms appear; then return to questions while answering payment questions accurately when asked. Its claim that this is the highest-converting live option is unsupported. Do not hide available payment terms earlier merely to manufacture generosity or urgency. A premium-priced plan changes total cost as well as timing.

D0929 — assigned source supporting this teaching point

Use three readiness triggers deliberately

Completion-based ascension follows an actual milestone such as a completed module or submitted worksheet, with a source estimate of 12–20%. Time-based prompts at Days14 and45 have an estimated 8–15%. Result-based invitations follow a confirmed outcome reported through a survey, support, community or testimonial, with an estimated 20–35%. These ranges are unverified. The source's always-after-first-result rule conflicts with a Day14 fallback that can happen sooner. Use a time-based check-in to assess progress; do not assert a result or readiness that has not occurred.

D0929 — assigned source supporting this teaching point

Write all three ascension emails without inventing proof

Email1 names the next problem and asks how the initial product is going, without pitching; the source schedules Day14 or completion, whichever comes first. Email2 is a real relevant case seven days later or Day21. Email3 presents the offer, scope, guarantee, price and any genuine incentive/deadline; its Day30 wording differs from 14 days after a Day14 start, which is Day28. Choose a consistent schedule tied to readiness. A placeholder case, stack slide or 72-hour deadline remains a draft until supported.

D0929 — assigned source supporting this teaching point

Calculate prior-purchase credit correctly

The source's example subtracts a $297 prior purchase from a $997 primary offer. The credit is $297 and the remaining balance is $700; calling $700 the credit is incorrect. Document eligibility, stacking rules and the actual total the buyer will pay. The claimed 1.5–2× ascension lift is not supported by data in the SOP. A loyalty incentive can be considered without promising that performance.

D0929 — assigned source supporting this teaching point

Distinguish a single relevant offer from a stack

The source generally favors one matched downsell and limits a stack to automated contexts rather than live-call pressure. Layer1 is a substantive alternative at 30–50% of primary price, immediately or 24 hours after close. Layer2 is a component at 15–25%, 48 hours after an unaccepted Layer1. Layer3 is free or $7–$27, 96 hours after Layer2. That totals six days from Layer1, not the separate three-offers-in-four-days description. Three layers is an upper internal limit, not permission to ignore declines, unsubscribes or consent.

D0929 — assigned source supporting this teaching point

Measure offer exposure, conversion and recovery

Offer rate is eligible non-buyers who saw the relevant offer divided by the eligible non-buyer pool; the source's 100% target must not override consent or relevance. Conversion uses purchases divided by those exposed, with source ranges 10–25% for Types1–3, 25–40% for plans and 30–45% for delayed entry. Recovery divides downsell revenue by hypothetical lost primary revenue, with a source target of 15–40%. Define that counterfactual denominator carefully; it is not actual lost cash or an estimate that every non-buyer would have paid full price.

D0929 — assigned source supporting this teaching point

Measure refunds and ascension with consistent cohorts

The source targets downsell refunds below10%, investigates above12%, and measures primary purchase within90days divided by all downsell buyers, targeting10–20%, reviewing below8% and considering above25% strong. Keep the 10–12% refund interval visible rather than implying a binary rule. Segment by type, acquisition source and readiness. A weak ascension rate may reflect a suitable standalone product or a different buyer goal, not necessarily a broken trigger.

D0929 — assigned source supporting this teaching point

Correct the AOV label and complete the remaining metrics

The source's total revenue divided by visitors is revenue per visitor, not average order value, which uses orders. Its 3–10% lift target belongs to a defined comparison and is not automatic justification to scale traffic. Time-to-ascension is average days among those who ascend, with source guidance45–90days and review below30 or above120; include non-ascenders separately so the average is not misleading. The12-month entry-cohort comparison targets60–80% of direct-primary revenue per buyer, reviews below50%, and calls parity strong. Define whether LTV means revenue or contribution and compare equally mature cohorts.

D0929 — assigned source supporting this teaching point

Connect all seven operating SOPs

Objection Bank supplies categories and priorities, with a review trigger above score8 and a monthly top-three check. Unbundling supplies an IP inventory and suggested score7+ component gate. Product Versioning tracks changes, including CAT-O and CAT-P, and testimonial relevance. Price Elasticity contributes surveys and revenue-per-visitor tests for the actual non-buyer pool. Forensic Audit supplies refund reasons to refine fit and copy. Guarantee Testing supplies a separate risk assessment rather than inheriting primary terms. Resurrection asks whether a healthy downsell can remain available while a primary offer is repaired. These are dependencies, not completed analyses supplied here.

D0929 — assigned source supporting this teaching point

Build the complete Downsell Offer record

Store ID, name, linked primary offer, type, objection, current price, price ratio, payment terms, sub-problem, exclusions and reasons, promised result/timeframe, guarantee level/copy, trigger types, sequence-active status, rolling offer/conversion/revenue/refund measures,90-day ascension, status, version, linked changelog, linked testimonials and notes. Guarantee levelsNone/1/2/3 require the referenced definitions. Statuses areActive,UnderTest andArchived. A checkbox stating a sequence is active must be supported by a tested event log, not merely written copy.

D0929 — assigned source supporting this teaching point

Run the setup, monthly and quarterly reviews

At setup, map primary offers and objections, choose types, complete briefs and sub-problem checks, and plan the six channels. Per offer, verify scope/name/price/guarantee, write channel copy and test the actual route before deployment. Test completion and fallback triggers, all three emails and any credit. Monthly, inspect all eight metrics, new objections, refunds and event logs. Quarterly, review pricing research, actual objection-to-trigger matches, the latest twelve ascension email observations and changes in connected SOPs. These checks produce evidence; the source's thresholds are internal targets, not market facts.

D0929 — assigned source supporting this teaching point

Submit an honest downsell design and script pack

Prepare one distinct offer brief, an objection-routing map covering all six categories, scripts for applicable channels with clear exits, a readiness-based ascension plan, transparent credit/payment math and a dashboard with corrected denominators. Include every source type and template in the lesson resources even when it is not used in the practice example. Preserve unresolved dependencies and measure the buyer's actual result as well as revenue. No purchase, message or automated sequence is initiated by this lesson.

D0929 — assigned source supporting this teaching point

Apply the agreed marketing lenses

D0929 — assigned source supporting this teaching point · ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Complete original source export

RISER NATION
MASTER OPERATING SYSTEM
SOP — DOWNSELL PATHS
The Complete Architecture for Recovering Revenue From Every 'No' — Without Damaging the Primary Offer or the Buyer Relationship
Kennedy × Hormozi × Brunson × Cialdini × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
A downsell is not a consolation prize. It is the precision instrument that recovers revenue from the specific buyer segment that wanted the transformation but could not access the primary offer — for reasons of price, commitment, timing, or format — and redirects them into the value ladder at the entry point that actually serves their current situation.
Most operators treat downsells as an afterthought: a quick email that says 'still interested? Here's a cheaper option.' That approach fails because it presents the downsell as a lesser version of something the buyer could not afford, which activates both shame and diminished expectation. A well-engineered downsell reframes the situation entirely: the buyer has found the right entry point for their specific current situation, and the downsell offer is designed precisely for that situation.
This SOP covers: the economic case for downsell architecture, the five downsell types with their specific deployment contexts, the trigger matrix that maps each objection type to the correct downsell path, the downsell offer design standards, the copy templates for every deployment channel (checkout page, email sequence, sales call, webinar, direct message), the ascension architecture that ensures downsell buyers eventually reach the primary offer, the measurement framework, and the Airtable schema.
The Economic Case for Downsell Architecture
Before designing any downsell, the operator must understand the revenue mechanics that make downsells one of the most leveraged investments of time in the business. The numbers below assume a specific scenario — adjust for your own offer metrics.
The Five Downsell Types
Every downsell in a knowledge business fits one of five structural types. Each type serves a different buyer segment and deploys in a different conversion context. Selecting the wrong type for the context produces low conversion. Selecting the right type for the right context produces the 10–30% recovery rate Brunson documents.
The Downsell Trigger Matrix
The trigger matrix maps every primary offer objection type to the correct downsell path. The wrong downsell for the stated objection produces near-zero conversion — a price downsell offered to a buyer whose real objection was timing will not convert because the price was not the barrier. The matrix ensures the downsell addresses the actual reason the buyer declined the primary.
The Three Downsell Design Rules
Rule 1 — The downsell must solve a real problem. Not 'it is cheaper than the primary.' A real problem that a real buyer in a specific situation has. The sub-problem test from the Bonus Discipline Audit SOP applies here with equal force: if the downsell cannot be described in one sentence beginning with 'The buyer is struggling with...' it is not a downsell — it is a discount.
Rule 2 — The downsell must have its own positioning. It is not 'the MVO minus the coaching calls.' It is '[Specific Product Name] — the [specific format] designed for [specific avatar in specific situation].' The name, the promise, and the copy are all written for the downsell's own avatar, not as a comparison to the primary offer.
Rule 3 — The downsell must have an ascension path. Every buyer who enters the value ladder through a downsell must be exposed to the primary offer and above — through an onboarding sequence, through the programme's content, or through a dedicated ascension email sequence. The downsell is an entry point, not a permanent home.
The Downsell Design Brief
Before building any downsell offer, complete this brief. A downsell built without a documented brief often fails the three rules above — producing an offer that is neither genuinely useful nor genuinely distinct from the primary.
The Six Deployment Channels
Downsells are presented in six distinct conversion contexts, each with different buyer states, different psychological dynamics, and different copy requirements. The same downsell offer requires completely different presentation language in each channel.
Channel 1 — Checkout Page Decline
The checkout page decline page or popup appears when a visitor abandons the checkout without completing the purchase. The copy must be extremely brief — this buyer is in transition and will not read a long sales pitch.
Channel 2 — Post-Webinar Email (Day 2 of Follow-Up Sequence)
This email goes to webinar attendees and replay watchers who have not purchased by the end of the primary close window. It deploys 24 hours after the cart closes.
Channel 3 — Sales Call Live Downsell Script
The live call downsell is deployed immediately after the primary close is declined and the specific objection has been identified and addressed at least once. The sequence below follows directly from the Close section of the Sales Call Scripts SOP.
Channel 4 — Email Nurture Sequence (Day 14 — Subscriber Conversion)
This email is for long-term warm subscribers who have never purchased. The goal is the first conversion at any price — because a subscriber who has made any purchase, even at $47, is statistically far more likely to ascend the value ladder than one who has never purchased.
Channel 5 — Direct Message Script (Community or Social Outreach)
Personal outreach to a specific identified prospect. Used when the operator has visibility into who is engaging with content but has not purchased. The message must feel personal and helpful — not automated or sales-driven.
Channel 6 — Webinar Live Q&A Payment Plan Announcement
The payment plan announcement during live webinar Q&A is the highest-converting live downsell available because it removes the final financial barrier without reducing the offer in any way. It must be delivered once, in a specific moment, with specific language.
The Three Ascension Trigger Types
A downsell that produces no ascension to higher tiers produces a business full of low-LTV buyers. The ascension architecture ensures that every downsell entry point has a documented, automated sequence that presents the primary offer at the correct moment — which is always after the downsell buyer has achieved their first result.
The Ascension Email Sequence
A minimum three-email ascension sequence is deployed for every downsell product. The sequence is triggered by the completion-based trigger (preferred) or the Day 14 time-based trigger if completion data is not available.
The Stack vs The Sequence
A downsell stack is multiple downsell offers presented in sequence to the same non-buyer. Each subsequent offer is lower in price and lower in commitment than the prior one. The stack is the most aggressive revenue recovery approach and carries the highest risk of alienating the buyer if deployed carelessly.
The downsell sequence is the more common and generally more appropriate architecture: a single downsell offer, presented once, in the most appropriate channel for the specific objection type. A single well-targeted downsell will almost always outperform a stack of three poorly-targeted ones.
When a Stack Is Appropriate
Only in automated funnel sequences — not in live sales calls. A stack in a live call destroys the relationship by signalling that the operator is primarily interested in extracting revenue.
Only when each offer in the stack addresses a distinct, different buyer segment — not when they are three increasingly desperate attempts to sell the same buyer.
Maximum three layers for any automated stack. After three declined offers, the buyer's state has shifted from 'not ready right now' to 'genuinely not interested.' A fourth offer is harassment.
The Three-Layer Automated Downsell Stack
The Eight Downsell Metrics
The SOP Connection Map
Downsell paths do not operate in isolation. Each downsell type draws from and feeds back into other SOPs in the Master Operating System. This connection map ensures the downsell architecture benefits from the intelligence generated by other systems.
Downsell Records Database — Airtable Schema
Table 1 — Downsell Offer Records
One record per downsell offer product. Linked to the primary offer it serves.
Master Downsell Paths Checklist
System Setup (One-Time)
☐ Identify all active primary offers and map each to the most likely objection type that produces non-buyers (from the Objection Bank, sorted by Priority Score)
☐ Using the Trigger Matrix, identify which downsell type is most appropriate for each primary offer's most common objection
☐ Complete the Downsell Design Brief for each planned downsell offer before any build begins
☐ Run the Sub-Problem Test (from Bonus Discipline Audit SOP) on every planned downsell — if it cannot be described as solving a specific named sub-problem, redesign it
☐ Create Downsell Offer Records table in Airtable with all fields
☐ Map each downsell to its deployment channels — which of the six channels will this downsell use?
Downsell Build (Per Offer)
☐ Downsell offer name chosen as a standalone product name — not '[Primary Offer] Lite' or '[Primary Offer] Basic'
☐ Price confirmed at 20–50% of primary offer price
☐ What is excluded documented with the 'feature not limitation' framing
☐ Result promised is specific and measurable — not 'you will learn how to...' but 'you will have [specific thing] within [timeframe]'
☐ Guarantee level assigned using the Guarantee Type Testing Protocol SOP Risk Score for the downsell specifically
☐ All copy templates completed for every planned deployment channel
☐ Checkout decline page or popup built and tested
☐ Post-webinar email sequence updated to include the downsell email at Day 2 of the post-close sequence
☐ Downsell offer record created in Airtable
Ascension Architecture
☐ Completion-based ascension trigger configured in the course platform
☐ All three ascension emails written — Email 1 (Next Problem Signal), Email 2 (Social Proof Bridge), Email 3 (Direct Offer)
☐ Ascension sequence tested: does it fire correctly on the completion trigger?
☐ Downsell Founding Member incentive decision documented — will prior purchase be credited? At what amount?
☐ Day 14 time-based backup trigger active for buyers who have not triggered the completion trigger
Ongoing Operations (Monthly)
☐ Pull all eight downsell metrics from Airtable and review against the healthy ranges
☐ Review the Objection Bank: have any new objection types emerged that do not have a matching downsell path?
☐ Check the ascension rate: are downsell buyers ascending at above 8%? If not — review the ascension Email 1 content
☐ Review the downsell refund rate: is it below 10%? If above 12% — run the Refund Root Cause analysis from the Forensic Audit Loop SOP
☐ Confirm all ascension triggers are firing correctly — pull the trigger event log from the course platform
☐ Update Downsell Offer Record in Airtable with current month's performance data
Quarterly Review
☐ Price test: run the Van Westendorp survey on the non-buyer pool for the primary offer — does the current downsell price sit within the Acceptable Price Range for this audience?
☐ Trigger accuracy review: are the right downsell types being shown to the right objection types? Pull objection data from the Sales Call Records and compare to which downsell channel each non-buyer entered
☐ Ascension sequence review: pull the 12 most recent ascension email open rates and conversion rates — are they performing at or above the expected ranges?
☐ Connected SOP review: have any changes in the Objection Bank, IP Asset Inventory, or Product Versioning Changelog affected the downsell architecture in a way that requires an update?
RISER Nation Master Operating System | Downsell Paths SOP | Version 1.0 | 2026 Edition
Kennedy × Hormozi × Brunson × Cialdini | risernation.com
Brunson's Revenue Recovery Data
In Brunson's funnel data, a well-designed downsell sequence recovers 10–30% of the revenue that would otherwise be lost entirely. On a $997 offer with 100 monthly declines, a $297 downsell converting at 20% of decliners adds $5,940/month in recovered revenue — without any additional traffic, any new content creation, or any change to the primary offer. Downsells are the highest-ROI mechanism in the entire offer architecture.
Kennedy's Critical Distinction
The downsell must serve the buyer, not the operator. A downsell that exists only to extract some revenue from a buyer who said no to the primary offer will feel predatory and will damage the relationship. A downsell that exists because there is a genuine entry-level version of the transformation — designed for a buyer who is not yet ready for the full programme — serves both parties. If you cannot build a downsell that genuinely serves the buyer's current situation, you should not build one.
Hormozi's Positioning Rule for Downsells
Never present the downsell as 'the same thing but cheaper.' Present it as 'the right thing for where you are right now.' The buyer who received the downsell should feel that the offer they purchased was designed for their specific current situation — not that they got a lesser version of something they could not afford. The copy, the name, and the delivery format should all reflect the downsell's own positioning, not its relationship to the primary offer.
Scenario
Without Downsells
With Downsell Architecture
Difference
Primary offer: $997
100 monthly cold visitors
2% cold conversion
Sales: 2 × $997 = $1,994
Non-buyers: 98
Revenue from non-buyers: $0
Sales from primary: 2 × $997 = $1,994
Downsell at $297 to 98 non-buyers: 20 purchase = $5,940
Total: $7,934
$5,940 additional revenue
+298% revenue lift from same traffic
Primary offer: $2,497
50 monthly warm email sequence openers
15% warm conversion
Sales: 7.5 × $2,497 = $18,728
Non-buyers: 42.5
Revenue from non-buyers: $0
Primary sales: 7.5 × $2,497 = $18,728
Downsell to 42.5 non-buyers at $497: 25% purchase = $5,303
Total: $24,031
$5,303 additional revenue
+28% revenue lift from the same list
Discovery call: $5,000
20 monthly qualified calls
25% close rate
Closed: 5 × $5,000 = $25,000
Non-closes: 15
Revenue from non-closes: $0
Primary closes: 5 × $5,000 = $25,000
Downsell at $997 to 15 non-closes: 20% accept = $2,991
Total: $27,991
$2,991 additional revenue
+12% revenue lift from the same call volume
The Revenue Per Visitor Impact
Downsells do not just add revenue — they change the fundamental unit economics of the business. When a business has a downsell architecture, every traffic source becomes more profitable because a higher percentage of visitors result in a purchase at some price. This changes the CAC calculation and often makes previously unprofitable traffic sources viable.
TYPE 01
The Self-Paced Version
When to deploy
The buyer wants the transformation but cannot commit to the live, cohort-based, or DWY format — due to schedule constraints, time zone, or preference for asynchronous learning.
The mechanism
Remove the live component. Keep the intellectual content and the framework. Deliver as recorded modules, worksheets, and text-based resources. Price at 30–50% of the live programme.
Typical conversion rate
15–25% of primary offer decliners when the timing objection was the stated reason
Best for
Core offers ($997–$4,997) that have a significant live component (group calls, cohort accountability, live Q&A). The self-paced version is the same curriculum without the synchronous elements.
Risk to manage
The self-paced version must be genuinely valuable on its own — not a stripped-out version that sets the buyer up to fail. If the programme genuinely requires live interaction to produce the result, the self-paced version should not exist.
TYPE 02
The Format Reduction
When to deploy
The buyer wants the result but cannot afford the full investment at the stated price. The format changes — group instead of 1:1, text-based instead of video, community instead of direct access — while the core mechanism is preserved.
The mechanism
Reduce the delivery touch-points that carry the highest cost to the operator (1:1 time, personalised feedback, direct access). Keep the mechanism, the frameworks, and the self-implementation tools. Price at 30–50% of the primary.
Typical conversion rate
15–25% of decliners when the price objection was primary and the buyer confirmed the mechanism was right for them
Best for
DWY and high-ticket offers ($3,000–$15,000) where a significant portion of the price is driven by access to the operator's time. The format reduction removes the high-cost access while preserving the high-value intellectual content.
Risk to manage
The buyer must genuinely be able to get a meaningful result from the reduced format. If the result requires 1:1 implementation support and the downsell removes that, the buyer will fail and refund.
TYPE 03
The Starter Module or Component Unbundle
When to deploy
The buyer is uncertain about committing to the full programme or cannot afford the full price, but has a specific, named sub-problem that one component of the full offer directly addresses.
The mechanism
Identify the single highest-value component of the full offer — a specific module, template, swipe file, or framework — that solves the most urgent sub-problem independently. Sell it as a standalone. Price at 15–30% of the primary offer.
Typical conversion rate
20–35% of decliners when uncertainty about fit was the stated objection, or when the buyer confirmed they most needed one specific element
Best for
Any offer where one component has clearly identifiable standalone value. This type is closely connected to the Offer Stacking & Unbundling Strategy SOP — the unbundle of a component as a downsell is one of the highest-leverage IP asset deployment strategies available.
Risk to manage
The starter module must NOT contain so much value that it eliminates the buyer's motivation to ascend to the full programme. Design it to solve one specific sub-problem while revealing the next sub-problem — creating the natural desire for the full offer.
TYPE 04
The Payment Plan
When to deploy
The buyer wants the full offer exactly as presented but faces a cash flow constraint that makes the single payment difficult or impossible in this period.
The mechanism
Offer the full primary offer broken into instalments. Price the payment plan at 110–120% of the single-pay price (the premium compensates for cash flow risk and payment processing costs). Terms: typically 2–4 payments over 30–90 days.
Typical conversion rate
25–40% of decliners when the budget objection was primary and the buyer confirmed commitment to the transformation
Best for
Any offer above $500 where the payment plan premium (10–20%) is small relative to the total value. Particularly high-converting for offers in the $997–$4,997 range where the single payment requires deliberate budget allocation.
Risk to manage
The payment plan is NOT a downsell in the structural sense — it delivers the same offer. But it is the correct response to a specific budget objection and belongs in the downsell decision matrix. The risk: payment plan buyers have a higher refund and chargeback rate than single-pay buyers. Mitigate with a stronger onboarding sequence and a completion commitment contract.
TYPE 05
The Wait-List / Delayed Entry
When to deploy
The buyer is interested and qualified but cannot commit right now due to an external circumstance (a major project, a business transition, a personal commitment) that will resolve within a defined timeframe.
The mechanism
Offer the buyer a reserved spot in the next cohort or intake at today's price. Collect a small deposit ($97–$297) to confirm intent. No additional work is required until the start date. The deposit is credited to the full price at entry.
Typical conversion rate
30–45% of decliners when the timing objection was 'I need X more weeks/months before I can start'
Best for
Cohort-based programmes where future cohort dates are confirmed. Also useful when the primary offer has a price increase planned — 'the next cohort opens in [date] at today's price' creates genuine urgency without manufactured pressure.
Risk to manage
The deposit creates commitment but also obligation. The refund policy for deposits must be documented and communicated clearly at the point of collection. A buyer who paid a deposit and then finds they still cannot start at the reserved cohort date will require a managed transition process.
Primary Objection Type
Root Concern
Correct Downsell Type
Downsell Price Logic
Conversion Expectation
Price & Value — 'It's too expensive'
Fear of wasting money. Value-to-price ratio does not feel right.
Type 02 (Format Reduction) or Type 04 (Payment Plan)
Type 04 if: 'I want the full programme but cannot pay all at once.'
Type 02 if: 'The price is genuinely beyond budget even with a payment plan.'
Payment plan: full price + 10–20% premium.
Format reduction: 30–50% of primary price.
Payment plan: 25–40% of price objectors
Format reduction: 15–25% of price objectors
Timing & Urgency — 'Now is not the right time'
Calendar is too full, or a specific project/event is blocking.
Type 01 (Self-Paced Version) or Type 05 (Wait-List)
Type 05 if: the constraint is temporary and the buyer has a clear re-entry date.
Type 01 if: the buyer's schedule makes synchronous commitment impossible but they can learn asynchronously.
Self-paced: 30–50% of live cohort price.
Wait-list deposit: $97–$297 credited to full price.
Self-paced: 15–20% of timing objectors
Wait-list: 30–45% of timing objectors with a specific re-entry date
Fit & Relevance — 'I'm not sure this is right for me'
Avatar mismatch, stage mismatch, or uncertainty about the mechanism's applicability.
Type 03 (Starter Module / Component Unbundle)
The specific component that directly addresses the sub-problem they described is the downsell. A buyer uncertain about the full programme is rarely uncertain about solving one specific, named problem.
Component price: 15–30% of primary offer price.
20–35% of fit-uncertainty objectors
Implementation Fear — 'I'm not sure I can do this'
Doubt about personal capability or available time.
Type 01 (Self-Paced Version) if the fear is about keeping up with a cohort pace.
Type 03 (Starter Module) focused on the Quick Win component if the fear is about where to start.
Self-paced: 30–50% of live programme price.
Quick Win component: 15–25% of full price.
Self-paced for pace fear: 20–30%
Starter module for 'where to start' fear: 25–35%
Comparison & Alternatives — 'I'm considering something else'
Evaluating alternatives — competitor, DIY, or different approach.
This objection type rarely responds to a downsell offer. If a buyer is actively comparing alternatives, the answer is better differentiation of the primary offer — not a smaller alternative to it.
Exception: if they are comparing the full DWY programme to 'figuring it out alone,' a Type 03 component that solves their highest-priority sub-problem provides an entry point into the relationship.
Component price: 15–25% of primary.
Low: 5–15% of active comparison buyers unless the component is extremely high standalone value
Trust & Credibility — 'I've tried things like this before'
Has been burned by prior purchases in this category. Scepticism about the method or the operator.
A trust objection almost never responds to a lower-priced version of the same offer. The buyer does not distrust the price — they distrust the result. The correct response is better proof deployment and the guarantee.
If the trust objection persists despite proof: a Type 03 minimal-risk component at a very low entry price ($47–$97) can function as a trust-building experience. The goal is a small win with zero risk, not revenue recovery.
Entry component: $47–$97 — below the conscious risk threshold.
Very low as revenue recovery: 5–10%. High as trust-building: 40–60% if the component delivers a tangible result quickly.
PHASE 1
The Downsell Offer Design Standards
What every downsell must have, must not have, and must promise
DOWNSELL DESIGN BRIEF TEMPLATE — Complete before any build begins.
DOWNSELL ID: DS-[Offer Code]-[DS Type Code]-[Seq]. e.g. DS-MVO-T01-001

PRIMARY OFFER THIS DOWNSELL SERVES
Primary Offer Name: [Name]
Primary Offer Price: [Price]
Primary Offer Format: [Format]

THE BUYER SEGMENT THIS DOWNSELL SERVES
The specific objection type this downsell addresses: [From the Trigger Matrix — which objection type]
The specific buyer in this situation: [One sentence: who they are, what they want, and what is preventing the primary offer from being the right fit right now]
// Example: 'A $5K–$10K/month online operator who wants to scale to $50K/month but cannot commit to live cohort calls due to timezone constraints.'

THE DOWNSELL OFFER
Downsell Type: [ ] Type 01 (Self-Paced) [ ] Type 02 (Format Reduction) [ ] Type 03 (Component Unbundle) [ ] Type 04 (Payment Plan) [ ] Type 05 (Wait-List)
Downsell Name: [Standalone name — not '[Primary Offer] Lite' or '[Primary Offer] Basic']
Downsell Price: [Price]
Price Ratio to Primary: [Downsell ÷ Primary × 100 = ___%. Target: 20–50% of primary]

WHAT IT INCLUDES (the Sub-Problem Test applied)
The sub-problem this downsell solves: [One sentence: 'The buyer is struggling with ___. This downsell solves that specific problem by ___.]
Components included:
1. [Component name] — [sub-problem it solves]
2. [Component name] — [sub-problem it solves]
3. [Optional additional component]

What the downsell does NOT include (explicitly — and why the exclusion is a feature, not a limitation):
[Name what is not included and frame why the exclusion makes this product specifically right for this buyer's current situation]

THE RESULT PROMISE
The specific, measurable result a buyer in this situation can expect from the downsell: [One sentence — specific enough to be testable]
Timeframe: [How long to achieve the result]
Guarantee (if applicable): [Will the downsell carry its own guarantee? Level? Copy?]

THE ASCENSION PATH
When will the buyer be offered the primary offer? [Timeline — e.g., after completing component 1, or at 30 days post-purchase, or via the onboarding email sequence]
What is the ascension trigger? [The specific sub-problem the downsell reveals that the primary offer solves]
PHASE 2
The Deployment Architecture
Where, when, and how each downsell type is presented
Channel
Buyer State at Moment of Downsell
Downsell Types That Work Here
Psychological Principle to Leverage
Timing
Checkout Page Decline
(after cart abandon or declined upsell)
Buyer visited checkout but did not complete. Still in the purchase mindset — highest intent of any non-buyer.
Type 03 (Component Unbundle) — a low-price entry point that requires minimal commitment.
Type 04 (Payment Plan) — if the barrier is the single-payment commitment.
Cialdini's Consistency: the buyer has already invested time researching. A lower-barrier entry preserves that investment rather than abandoning it.
Trigger immediately on cart abandon — within 2 minutes. Either redirect to a lower-price page or trigger a popup.
Post-Webinar Email Sequence
(non-buyers after the cart closes)
Buyer attended or watched the webinar, considered the primary offer, and did not purchase by the deadline. Engaged but not converted.
Type 01 (Self-Paced) — for those who cited timing constraints.
Type 02 (Format Reduction) — for price objectors.
Type 03 (Component) — for fit-uncertain buyers.
Kennedy's Follow-Up Rule: a buyer who did not purchase at the close has not said no to the transformation. They said no to the specific terms. The follow-up sequence finds the terms they can say yes to.
Deploy Day 2 of the post-close follow-up (24 hours after the cart closes). Single email. Single downsell offer. Single deadline.
Sales Call — Live Downsell
(after the primary close is declined)
Buyer is on a live call, has declined the primary offer after full consideration. Specific objection is known and documented.
Type matched to the specific objection using the Trigger Matrix.
Do not deploy until the specific objection has been identified and addressed at least once.
NLP Reframing: the downsell is presented not as a lesser option but as the right option for their specific current situation — the one that produces the first win that makes everything else possible.
Deploy immediately after the primary close is declined and the specific objection has been named. Do not wait — the decision window closes as the call energy dissipates.
Email Nurture Sequence
(warm subscribers who have never purchased)
Subscribers who have engaged with content but have never purchased anything. Lower intent than webinar attendees. Longer decision timeline.
Type 03 (Component at very low price — $27–$97) — low-barrier entry to convert a subscriber into a buyer.
Type 05 (Wait-List) — for an upcoming cohort.
Cialdini's Reciprocity and Commitment: the first purchase at any price converts a subscriber into a buyer — the identity shift dramatically increases likelihood of future higher-value purchases.
Deploy as the Day 14 email in the email nurture sequence, after the primary offer has been presented and not converted. Single email, single offer.
Direct Message / Community
(personal outreach to engaged non-buyers)
A specific person who has shown high engagement with content, asked about the offer, or been referred by a buyer — but has not purchased.
Type 03 (Component) or Type 05 (Wait-List deposit) — both are low-friction entry points suitable for personal outreach.
Type 04 (Payment Plan) — if they have expressed budget hesitancy in conversation.
Cialdini's Liking: personal outreach from the operator is the highest-trust context available. The downsell in this channel should feel like a personal recommendation, not a marketing message.
Deploy after at least two prior touchpoints with the person have occurred organically. A cold DM with a downsell is a spam message.
Webinar Live Q&A
(non-buyers still on the webinar)
Buyer is still on the webinar after the primary close has been presented. They have not left — which signals continued interest — but have not purchased.
Type 04 (Payment Plan) — most effective live downsell because it maintains the full offer while removing the payment barrier.
Type 03 (Component) — for the buyer who states fit uncertainty during Q&A.
Scarcity and Social Proof: re-close with the payment plan announced as if it is a final accommodation. 'For anyone who loves the full programme but the single investment is challenging right now, I do have a payment option.'
Deploy once during the Q&A — not earlier. The live webinar context makes a mid-Q&A payment plan announcement feel generous rather than desperate.
PHASE 3
The Complete Downsell Copy Templates
Full scripts for every deployment channel
CHECKOUT DECLINE PAGE TEMPLATE
HEADLINE (7 words maximum)
// Option A — Component downsell:
[SPECIFIC RESULT] in [TIMEFRAME] — Starting at $[Downsell Price]
// Option B — Payment plan:
Get Everything. Pay Over [Number] Months.
// Option C — Self-paced:
Same [Mechanism/Method]. Self-Paced. $[Price].

BODY (40–60 words maximum)
// This copy must acknowledge the primary offer and bridge to the downsell without shaming the non-purchase decision.
You did not complete your order for [Primary Offer Name]. That is completely fine.
Before you go: [one sentence on the downsell and who it is specifically right for].
This is not [Primary Offer Name] with features removed. This is [Downsell Name], designed for [specific buyer situation].

THE OFFER (two lines)
[Downsell Name]: [One-sentence description]
[Price] — [What is included in 5 words maximum] — [Guarantee statement if applicable]

THE CTA (single button — one action)
[Specific action: 'Get [Downsell Name]' — not 'Learn More' or 'Check it Out']

THE EXIT LINK (below the CTA — not a button)
// Always include an exit option. Trapping buyers produces resentment, not sales.
No thank you — take me to the [Primary Offer / Previous Page].

// IMPLEMENTATION NOTE: Checkout decline pages should be A/B tested. Test Component Unbundle vs Payment Plan. The winner depends on which objection is more common for this specific offer.
POST-WEBINAR DOWNSELL EMAIL TEMPLATE
SUBJECT LINE OPTIONS (choose one based on primary objection type most common for this audience)
// For timing objectors: 'Not ready for the full programme? This might be the right start.'
// For price objectors: 'A different entry point into [Mechanism Name]'
// For fit-uncertain buyers: 'If you are still unsure, start here.'
// For component-interested buyers: 'Just want [specific component]? Here it is.'

BODY
[First name],

The cart for [Primary Offer Name] is now closed.

I want to share something briefly — not to extend the offer, but because I heard from several people who said [the most common reason given for not purchasing, verbatim from webinar Q&A or post-webinar reply emails].

If that was your situation, I built something specifically for that.

[Downsell Name] is [one sentence: what it is and who it is for].

It does not include [what the primary offer includes that the downsell does not — stated as a feature of the downsell, not as a limitation]. That is intentional: [why that exclusion makes the downsell right for this buyer's situation].

What it does include:
[Component 1 — what it solves]
[Component 2 — what it solves]
[Component 3 if applicable]

The investment is $[Downsell Price].

[Guarantee statement if applicable.]

This offer is available until [specific date — 48–72 hours from now. Must be a real deadline.]

[CTA: 'Get [Downsell Name]' — link to downsell checkout page]

If neither offer is right for you right now, I completely understand. You will stay on my list and I will keep sharing [mechanism-related content] with you.

[Operator name]

P.S. [One sentence reiterating the specific buyer situation this downsell serves and why this is the right next step for them specifically.]
LIVE CALL DOWNSELL SCRIPT
// TRIGGER: The primary close has been declined and the specific objection is confirmed.
// RULE: Only deploy after the objection has been named. 'I can't buy right now' is not named. 'The single payment of $5,000 is too large for this month's budget' is named.

THE BRIDGE
'I appreciate you being direct about that. Let me ask you one more thing before we wrap up — and if this doesn't fit either, that is genuinely fine.'

THE DOWNSELL OFFER
'There is a different entry point into [the mechanism / the work we do together] that might be right for where you are right now.'
'It is called [Downsell Name]. Here is what it is: [one sentence — specific, plain, no jargon].'
'The reason I think this might be relevant for you specifically is: [connect the downsell directly to the named objection or situation they described in Stage 3 of the discovery call].'

THE BRIEF DESCRIPTION
'It includes [2–3 components stated briefly — one sentence each].'
'It does not include [what the primary offer includes but this doesn't — stated as a deliberate design choice, not a deficiency].'
'The investment is $[Downsell Price] — [payment structure if applicable].'

THE SOFT CLOSE
'Does that sound like it addresses where you are right now?'
// Wait. Do not fill the silence.
// If yes: 'Great. Let me send you the link now — you can take care of it in the next 10 minutes while we are still on the call together.' Process immediately.
// If no: 'Completely fine. Tell me — is there anything that would have made the full programme work for you today, or is the timing genuinely not right?'

THE GRACEFUL CLOSE (if both offers are declined)
'I respect that. Let me keep you on my email list so you can see the results others are getting with [mechanism name]. When the timing is right, you will know exactly where to start.'
// Book any future follow-up that was agreed to during the call.
SUBSCRIBER CONVERSION DOWNSELL EMAIL TEMPLATE
SUBJECT LINE
// Personal, non-promotional tone. No ALL CAPS, no exclamation marks, no discount signals.
// Examples: 'One specific thing' / 'Quick question, [first name]' / 'Something I built for exactly this'

BODY
[First name],

You have been reading my content for [timeframe — if trackable] and I have appreciated having you here.

I want to share something brief — because if what I write about [topic] is relevant to you, this might be useful.

[Downsell Name] is [one sentence: what it is and who it is for. Personal tone — 'I built this for [avatar description]' not 'this product provides...'].

It costs $[Downsell Price].

Here is what is inside: [3–5 bullet points — each describing what it does for the buyer, not what it is. Format: 'Solve [sub-problem] with [component name]']

There is no deadline on this. This is not a launch or a promotion. It is simply something I built that I think is genuinely useful for [avatar description], and if that is you — here is the link.

[CTA: 'Get [Downsell Name]' — direct checkout link]

If it is not for you right now, that is fine too. I will keep sharing.

[Operator name]

// NOTE: This email does NOT mention the primary offer. It is not framed as a downsell of anything. It is a standalone offer introduction. That framing produces higher conversion than 'you didn't buy X, so here is Y.'
DIRECT MESSAGE DOWNSELL TEMPLATE
// CONTEXT: This message is sent to someone who has: (a) engaged meaningfully with content, (b) asked about the offer, or (c) been in conversation about the problem. This is NOT a cold message.

THE PERSONAL OPENING
'Hey [Name] — I noticed [specific observation: you commented on the post about X / you were on the webinar last week / you asked about Y in the community].'
'I wanted to reach out personally because [specific reason — something in their comment or question that makes this relevant].'

THE BRIDGE
'I don't know if you had the chance to look at [Primary Offer Name] — if not, no worries.'
'But I did want to mention something that I think might be more relevant for where you are right now based on what you shared.'

THE OFFER
'I built [Downsell Name] specifically for [their specific situation — reference their actual words if possible].'
'It is $[Price] and it [one sentence on the result it produces].'
'Happy to send you the link if you want to take a look — or if you have questions about whether it is the right fit, ask me anything.'

THE EXIT
'And if the timing is not right at all, that is completely fine — just wanted to make sure you knew about it.'

// RULE: One message only unless they respond. Follow up on a non-response once, 5 days later, with a non-sales message ('how are things going with [their problem]?'). No third follow-up.
WEBINAR Q&A PAYMENT PLAN ANNOUNCEMENT SCRIPT
// TIMING: Deploy this announcement approximately 5–7 minutes into the Q&A, after answering 2–3 substantive questions. Not at the beginning of Q&A and not as the final statement.

THE ANNOUNCEMENT
'Before I take the next question — I want to address something that I know is in the room for some people.'
'For anyone who loves what we covered today and would love access to [Primary Offer Name], but the single investment of $[price] is challenging right now — I do have a payment option available.'
'It is [X payments of $Y over Z months]. You get everything — every component, every resource, every [live element if applicable]. The total across the payments is $[total payment plan price].'
'If that is the option that works for you: the link in chat is the same link. You will see the payment plan option at checkout.'

IMMEDIATELY CONTINUE
'Okay — next question...'
// Do NOT dwell on the payment plan or repeat it. State it once, cleanly, and move forward. Dwelling signals that you are concerned about close rates. Moving forward signals confidence.

IF QUESTIONS ARISE ABOUT THE PAYMENT PLAN IN CHAT
'The payment plan is [terms]. It is the same programme. The only difference is the payment schedule.'
// Answer once in chat and return to Q&A. Do not dedicate multiple minutes to payment plan logistics during the live event.
PHASE 4
The Downsell Ascension Architecture
Ensuring every downsell buyer is on a documented path to the primary offer
Ascension Trigger Type
When It Fires
How It Works
Expected Ascension Rate
Completion-Based Trigger
Fires when the downsell buyer completes a defined milestone — finishes the component, submits the worksheet, or reaches a specific point in the curriculum.
Course platform (Kajabi or equivalent) triggers an email sequence upon module completion. The sequence presents the primary offer as the natural next step: 'You've just solved [the sub-problem the downsell addresses]. Here is the next challenge most operators face at this stage — and it is exactly what [Primary Offer Name] is designed for.'
12–20% of downsell buyers who complete the defined milestone
Time-Based Trigger
Fires at a specific number of days post-purchase: typically Day 14 (early engagement window) and Day 45 (post-completion window).
Automated email sequence. Day 14 email: 'How are you getting on with [Downsell Name]? [Two sentences of content relevant to their progress.] Also — for anyone who is ready to go deeper, [Primary Offer Name] opens its next cohort on [date].' Day 45 email: full ascension offer with social proof from buyers who started where the downsell buyer is now.
8–15% of downsell buyers in the time-based window
Result-Based Trigger
Fires when the buyer reports achieving the downsell's promised result — through a survey, a support ticket, a community post, or a testimonial submission.
Email sequence: 'I saw that you [achieved the result]. That is genuinely excellent. The operators who achieve [the result] typically face [the next specific challenge]. That next challenge is exactly what [Primary Offer Name] is designed for. Here is what it includes and what it would look like to join the next cohort.'
20–35% of downsell buyers who have confirmed achieving the result — this is the highest-converting ascension window because the buyer has tangible proof that the method works
Email
Timing
Subject Line Theme
Content Focus
CTA
Ascension Email 1 — The Next Problem Signal
Day 14 OR on milestone completion (whichever comes first)
'What comes after [downsell result] — the next challenge most operators face'
Deliver a brief piece of content that names the next problem the buyer will encounter after solving the one the downsell addressed. Do NOT pitch the primary offer yet — just name the next problem. Create the context for the ascension.
Reply and tell me how [Downsell Name] is going
Ascension Email 2 — The Social Proof Bridge
Day 21 OR 7 days after Email 1
'[Name] went from [downsell result stage] to [primary offer result] in [timeframe]'
A complete case study of a buyer who entered through the same downsell and ascended to the primary offer. Specifically: who they were, what the downsell gave them, what the next problem was, how the primary offer addressed it, and the specific result they achieved.
Read the full story — [link to case study or sales page]
Ascension Email 3 — The Direct Offer
Day 30 OR 14 days after Email 1
'[Primary Offer Name] opens for [Downsell Buyer First Name]'
Full offer presentation. Stack slide. Guarantee. Price. Founding member pricing if the buyer is being offered an incentive for prior purchase. One specific deadline — 72 hours.
Get started with [Primary Offer Name] — [checkout link]
The Downsell Founding Member Incentive
Buyers who entered through a downsell and are being offered ascension to the primary offer may be offered a credit for their prior purchase — their downsell investment is deducted from the primary offer price. Example: a buyer who paid $297 for the downsell is offered the primary offer at $997 − $297 = $700 credit applied.

This incentive has two functions: (1) it acknowledges the prior relationship and rewards loyalty, and (2) it provides a genuine price incentive that is not available to new buyers — real exclusivity. Not all operators use this approach, but those who do report ascension rates 1.5–2× the baseline rate.
PHASE 5
The Downsell Stack Architecture
Sequencing multiple downsells without burning the relationship
Layer
Offer Type
Price Target
Trigger
Copy Approach
Layer 1 — Primary Downsell
Type 01, 02, or 03 depending on the primary offer and most common objection
30–50% of primary offer price
Fires immediately on cart abandon or 24 hours after primary offer close
Substantive — explains the value of the specific downsell for the specific buyer situation. Full copy per Channel 1 or Channel 2 templates.
Layer 2 — Micro-Commitment
Type 03 (Component Unbundle) — the lowest-price, highest-standalone-value component
15–25% of primary offer price
Fires 48 hours after Layer 1 if Layer 1 was not purchased
Brief — acknowledges the prior offer was not right, presents the specific component in 2–3 sentences. No pressure, no deadline extension.
Layer 3 — Minimum Entry
A free or very low cost lead magnet or entry product that maintains the relationship without requiring a purchase commitment
Free or $7–$27
Fires 96 hours after Layer 2 if Layer 2 was not purchased
Relationship-maintenance frame — 'I understand this is not the right time. Here is something free / very low cost that I think you will find genuinely useful.' This is not a sales message — it is a relationship preservation message.
The Burn Threshold
A non-buyer who receives three offers in four days has reached the burn threshold. After Layer 3, the buyer goes onto a standard content nurture sequence — not a sales sequence. The nurture sequence continues to provide value and will re-present the primary offer at the next natural launch cycle. There is no Layer 4. The burn threshold exists to protect the relationship.
PHASE 6
The Downsell Performance Dashboard
The metrics that determine whether to iterate, optimise, or retire a downsell
Metric
Calculation
Healthy Range
Action If Outside Range
Downsell offer rate
Number of non-buyers who see the downsell ÷ total non-buyers × 100
100% — every non-buyer should see the relevant downsell via at least one channel
If below 100%: identify which buyer type is not receiving the downsell. Check funnel architecture — is there a trigger gap?
Downsell conversion rate
Downsell purchases ÷ non-buyers who saw the downsell × 100
Type 01/02/03: 10–25%
Type 04 (Payment Plan): 25–40%
Type 05 (Wait-List): 30–45%
Below the lower bound: review the copy (is it presenting the downsell as 'lesser than' rather than 'right for this buyer'?) and the trigger accuracy (is the downsell being shown to buyers whose objection matches the downsell type?)
Revenue recovery rate
Downsell revenue ÷ lost primary revenue × 100
15–40% of lost primary offer revenue recovered
Below 15%: the downsell is not converting enough of the available non-buyer pool. Review trigger accuracy and copy. Above 40%: the downsell is performing exceptionally — consider whether the primary offer's price point needs testing.
Downsell refund rate
Downsell refunds ÷ downsell purchases × 100
Below 10% — lower than the primary offer refund rate (buyers at a lower price point with matched expectations should refund less)
Above 12%: the downsell is creating expectation mismatches. Review the promise language — is the downsell promising more than it delivers? Is the wrong buyer type being targeted by the trigger?
Ascension rate from downsell
Downsell buyers who purchase the primary offer within 90 days ÷ total downsell buyers × 100
10–20% — 1 in 10 to 1 in 5 downsell buyers should ascend to the primary offer within 90 days
Below 8%: the ascension sequence is not firing correctly, or the ascension emails are not surfacing the next problem clearly. Review the completion-based trigger and Email 1 content. Above 25%: the downsell is an exceptionally good entry point — consider featuring it as the recommended starting point.
Average order value lift
Total revenue (primary + downsell) ÷ total visitors — compared against primary-only AOV
3–10% AOV lift from the downsell architecture across all visitor traffic
Below 3%: the downsell is not reaching enough of the non-buyer population. Review deployment channel coverage. Above 10%: strong performance — scale traffic.
Time-to-ascension
Average days from downsell purchase to primary offer purchase
45–90 days — fast enough to maintain momentum, slow enough to confirm the downsell is delivering value first
Below 30 days: buyers may be ascending before the downsell has delivered value — review the ascension trigger timing. Above 120 days: the ascension sequence may not be compelling enough or the downsell result achievement rate may be low (buyers are not getting the win that creates ascension motivation).
LTV of downsell entry buyers vs direct primary buyers
Compare 12-month revenue from buyers who entered via downsell vs those who entered direct at primary price
Downsell entry LTV should reach 60–80% of direct primary buyer LTV within 12 months
Below 50%: downsell buyers are not ascending. Review the ascension architecture. Equal to or above primary buyer LTV: the downsell is functioning as a high-quality entry point — increase its promotion.
PHASE 7
Integration With the Master Operating System
How downsells connect to the other RISER Nation SOPs
Connected SOP
Connection to Downsells
The Data Flow
Objection Bank SOP
The Objection Bank's objection type classification and Priority Score ranking determines which downsell trigger fires for which non-buyer. Every new Objection Bank entry above Priority Score 8 should trigger a review of the downsell trigger matrix.
Objection Bank → Trigger Matrix → Downsell type selection. Monthly review: do the top 3 objection types in the Objection Bank match the downsell types currently deployed?
Offer Stacking & Unbundling Strategy SOP
Type 03 (Component Unbundle) downsells require a documented IP Asset Inventory with Unbundle Score assessments. A component must score 7+ on the Unbundle Score before it becomes a downsell offer.
IP Asset Inventory Unbundle Scores → Type 03 downsell product selection. Quarterly review: are there newly-scored assets that qualify as Type 03 downsell candidates?
Product Versioning SOP
Every downsell offer is a versioned product. Any change to the downsell's components, price, or guarantee triggers a Minor version change (CAT-O for stack changes, CAT-P for price changes). The Changelog tracks all downsell product versions.
All downsell offer changes → Changelog entries. The Testimonial Version Registry tracks which testimonials are valid for which downsell version.
Price Elasticity Testing Framework SOP
Downsell prices should be tested with the same rigour as primary offer prices. The Van Westendorp survey run for the primary offer includes questions about the downsell price range. The RPV calculation applies to downsells within their specific non-buyer pool.
Van Westendorp PMC/PME for the non-buyer pool → Downsell price testing range. Quarterly: is the downsell price at the revenue-maximising point in the RPV curve for non-buyers?
Forensic Audit Loop SOP
The Refund Root Cause analysis for downsell refunds feeds back into the downsell trigger matrix — if a Type 03 component downsell is generating refunds with RC code 'not what I expected,' the component's standalone positioning needs a fix.
Downsell refund RC codes → Trigger matrix accuracy review → Downsell copy and positioning updates.
Guarantee Type Testing Protocol SOP
Downsell offers should carry their own guarantees, not simply inherit the primary offer guarantee. The Risk Score for the downsell (typically lower — smaller investment, simpler delivery) usually supports Level 2 or Level 3 guarantees even when the primary is at Level 1.
Downsell Risk Score → Downsell guarantee level selection → Guarantee Type Testing Protocol for the downsell offer specifically.
Dead Offer Resurrection Playbook SOP
When a primary offer enters the Flatline state, its highest-performing downsell becomes the candidate for continuing the revenue stream during the resurrection period. The downsell may serve as the 'minimum viable live product' while the primary is being rebuilt.
Primary offer enters Flatline → Downsell performance assessment → Decision: maintain downsell as interim primary or retire alongside the primary offer.
Field
Type
Notes
Downsell ID
Short text
Format: DS-[Offer Code]-[Type Code]-[Seq]. e.g. DS-MVO-T03-001
Downsell Name
Short text
The product name — standalone, not a reference to the primary offer
Primary Offer
Link → Offers table
The offer this downsell serves
Downsell Type
Single select
Type 01 (Self-Paced) / Type 02 (Format Reduction) / Type 03 (Component) / Type 04 (Payment Plan) / Type 05 (Wait-List)
Objection Type Targeted
Single select
Price & Value / Timing / Fit & Relevance / Implementation Fear / Trust / Comparison
Current Price
Currency
Primary Offer Price Ratio
Formula
Downsell Price ÷ Primary Offer Price × 100. Target: 20–50%
Payment Plan Terms (if Type 04)
Short text
e.g. '3 × $367 over 60 days'
Sub-Problem Solved
Short text
One sentence: 'The buyer is struggling with ___. This solves that by ___.
What Is Excluded (and why it is a feature)
Long text
What the primary offer includes that this does not, and the one-sentence framing of why the exclusion is appropriate for this buyer
Result Promised
Short text
The specific, measurable result the downsell buyer should expect
Result Timeframe
Short text
e.g. '30 days'
Guarantee Level
Single select
None / Level 1 / Level 2 / Level 3
Guarantee Copy
Long text
Verbatim from Guarantee Type Testing Protocol SOP
Ascension Trigger Type
Multi-select
Completion-Based / Day 14 Time-Based / Day 45 Time-Based / Result-Based
Ascension Sequence Active
Checkbox
Is the 3-email ascension sequence live and triggering?
Downsell Offer Rate
Number
% of non-buyers seeing this downsell (rolling 30 days)
Downsell Conversion Rate
Number
% of non-buyers who see it and purchase (rolling 30 days)
Downsell Revenue (rolling 30 days)
Currency
Downsell Refund Rate
Number
% rolling 30 days
Ascension Rate (90-day)
Number
% of downsell buyers who purchase the primary offer within 90 days
Status
Single select
Active / Under Test / Archived
Version
Short text
From Product Versioning SOP Changelog — current version identifier
Changelog Entry
Link → Changelog Entries
Latest CAT entry for this downsell product
Linked Testimonials
Link → Testimonial Version Registry
Testimonials from downsell buyers — for use in ascension emails and downsell copy
Notes
Long text
Observations, test results, copy variants, deployment notes

Original Word tables and field relationships

Source table 1

Brunson's Revenue Recovery DataIn Brunson's funnel data, a well-designed downsell sequence recovers 10–30% of the revenue that would otherwise be lost entirely. On a $997 offer with 100 monthly declines, a $297 downsell converting at 20% of decliners adds $5,940/month in recovered revenue — without any additional traffic, any new content creation, or any change to the primary offer. Downsells are the highest-ROI mechanism in the entire offer architecture.

Source table 2

Kennedy's Critical DistinctionThe downsell must serve the buyer, not the operator. A downsell that exists only to extract some revenue from a buyer who said no to the primary offer will feel predatory and will damage the relationship. A downsell that exists because there is a genuine entry-level version of the transformation — designed for a buyer who is not yet ready for the full programme — serves both parties. If you cannot build a downsell that genuinely serves the buyer's current situation, you should not build one.

Source table 3

Hormozi's Positioning Rule for DownsellsNever present the downsell as 'the same thing but cheaper.' Present it as 'the right thing for where you are right now.' The buyer who received the downsell should feel that the offer they purchased was designed for their specific current situation — not that they got a lesser version of something they could not afford. The copy, the name, and the delivery format should all reflect the downsell's own positioning, not its relationship to the primary offer.

Source table 4

Scenario	Without Downsells	With Downsell Architecture	Difference
Primary offer: $997100 monthly cold visitors2% cold conversion	Sales: 2 × $997 = $1,994Non-buyers: 98Revenue from non-buyers: $0	Sales from primary: 2 × $997 = $1,994Downsell at $297 to 98 non-buyers: 20 purchase = $5,940Total: $7,934	$5,940 additional revenue+298% revenue lift from same traffic
Primary offer: $2,49750 monthly warm email sequence openers15% warm conversion	Sales: 7.5 × $2,497 = $18,728Non-buyers: 42.5Revenue from non-buyers: $0	Primary sales: 7.5 × $2,497 = $18,728Downsell to 42.5 non-buyers at $497: 25% purchase = $5,303Total: $24,031	$5,303 additional revenue+28% revenue lift from the same list
Discovery call: $5,00020 monthly qualified calls25% close rate	Closed: 5 × $5,000 = $25,000Non-closes: 15Revenue from non-closes: $0	Primary closes: 5 × $5,000 = $25,000Downsell at $997 to 15 non-closes: 20% accept = $2,991Total: $27,991	$2,991 additional revenue+12% revenue lift from the same call volume

Source table 5

The Revenue Per Visitor ImpactDownsells do not just add revenue — they change the fundamental unit economics of the business. When a business has a downsell architecture, every traffic source becomes more profitable because a higher percentage of visitors result in a purchase at some price. This changes the CAC calculation and often makes previously unprofitable traffic sources viable.

Source table 6

TYPE 01The Self-Paced Version
When to deployThe buyer wants the transformation but cannot commit to the live, cohort-based, or DWY format — due to schedule constraints, time zone, or preference for asynchronous learning.
The mechanismRemove the live component. Keep the intellectual content and the framework. Deliver as recorded modules, worksheets, and text-based resources. Price at 30–50% of the live programme.
Typical conversion rate15–25% of primary offer decliners when the timing objection was the stated reason
Best forCore offers ($997–$4,997) that have a significant live component (group calls, cohort accountability, live Q&A). The self-paced version is the same curriculum without the synchronous elements.
Risk to manageThe self-paced version must be genuinely valuable on its own — not a stripped-out version that sets the buyer up to fail. If the programme genuinely requires live interaction to produce the result, the self-paced version should not exist.

Source table 7

TYPE 02The Format Reduction
When to deployThe buyer wants the result but cannot afford the full investment at the stated price. The format changes — group instead of 1:1, text-based instead of video, community instead of direct access — while the core mechanism is preserved.
The mechanismReduce the delivery touch-points that carry the highest cost to the operator (1:1 time, personalised feedback, direct access). Keep the mechanism, the frameworks, and the self-implementation tools. Price at 30–50% of the primary.
Typical conversion rate15–25% of decliners when the price objection was primary and the buyer confirmed the mechanism was right for them
Best forDWY and high-ticket offers ($3,000–$15,000) where a significant portion of the price is driven by access to the operator's time. The format reduction removes the high-cost access while preserving the high-value intellectual content.
Risk to manageThe buyer must genuinely be able to get a meaningful result from the reduced format. If the result requires 1:1 implementation support and the downsell removes that, the buyer will fail and refund.

Source table 8

TYPE 03The Starter Module or Component Unbundle
When to deployThe buyer is uncertain about committing to the full programme or cannot afford the full price, but has a specific, named sub-problem that one component of the full offer directly addresses.
The mechanismIdentify the single highest-value component of the full offer — a specific module, template, swipe file, or framework — that solves the most urgent sub-problem independently. Sell it as a standalone. Price at 15–30% of the primary offer.
Typical conversion rate20–35% of decliners when uncertainty about fit was the stated objection, or when the buyer confirmed they most needed one specific element
Best forAny offer where one component has clearly identifiable standalone value. This type is closely connected to the Offer Stacking & Unbundling Strategy SOP — the unbundle of a component as a downsell is one of the highest-leverage IP asset deployment strategies available.
Risk to manageThe starter module must NOT contain so much value that it eliminates the buyer's motivation to ascend to the full programme. Design it to solve one specific sub-problem while revealing the next sub-problem — creating the natural desire for the full offer.

Source table 9

TYPE 04The Payment Plan
When to deployThe buyer wants the full offer exactly as presented but faces a cash flow constraint that makes the single payment difficult or impossible in this period.
The mechanismOffer the full primary offer broken into instalments. Price the payment plan at 110–120% of the single-pay price (the premium compensates for cash flow risk and payment processing costs). Terms: typically 2–4 payments over 30–90 days.
Typical conversion rate25–40% of decliners when the budget objection was primary and the buyer confirmed commitment to the transformation
Best forAny offer above $500 where the payment plan premium (10–20%) is small relative to the total value. Particularly high-converting for offers in the $997–$4,997 range where the single payment requires deliberate budget allocation.
Risk to manageThe payment plan is NOT a downsell in the structural sense — it delivers the same offer. But it is the correct response to a specific budget objection and belongs in the downsell decision matrix. The risk: payment plan buyers have a higher refund and chargeback rate than single-pay buyers. Mitigate with a stronger onboarding sequence and a completion commitment contract.

Source table 10

TYPE 05The Wait-List / Delayed Entry
When to deployThe buyer is interested and qualified but cannot commit right now due to an external circumstance (a major project, a business transition, a personal commitment) that will resolve within a defined timeframe.
The mechanismOffer the buyer a reserved spot in the next cohort or intake at today's price. Collect a small deposit ($97–$297) to confirm intent. No additional work is required until the start date. The deposit is credited to the full price at entry.
Typical conversion rate30–45% of decliners when the timing objection was 'I need X more weeks/months before I can start'
Best forCohort-based programmes where future cohort dates are confirmed. Also useful when the primary offer has a price increase planned — 'the next cohort opens in [date] at today's price' creates genuine urgency without manufactured pressure.
Risk to manageThe deposit creates commitment but also obligation. The refund policy for deposits must be documented and communicated clearly at the point of collection. A buyer who paid a deposit and then finds they still cannot start at the reserved cohort date will require a managed transition process.

Source table 11

Primary Objection Type	Root Concern	Correct Downsell Type	Downsell Price Logic	Conversion Expectation
Price & Value — 'It's too expensive'	Fear of wasting money. Value-to-price ratio does not feel right.	Type 02 (Format Reduction) or Type 04 (Payment Plan)Type 04 if: 'I want the full programme but cannot pay all at once.'Type 02 if: 'The price is genuinely beyond budget even with a payment plan.'	Payment plan: full price + 10–20% premium.Format reduction: 30–50% of primary price.	Payment plan: 25–40% of price objectorsFormat reduction: 15–25% of price objectors
Timing & Urgency — 'Now is not the right time'	Calendar is too full, or a specific project/event is blocking.	Type 01 (Self-Paced Version) or Type 05 (Wait-List)Type 05 if: the constraint is temporary and the buyer has a clear re-entry date.Type 01 if: the buyer's schedule makes synchronous commitment impossible but they can learn asynchronously.	Self-paced: 30–50% of live cohort price.Wait-list deposit: $97–$297 credited to full price.	Self-paced: 15–20% of timing objectorsWait-list: 30–45% of timing objectors with a specific re-entry date
Fit & Relevance — 'I'm not sure this is right for me'	Avatar mismatch, stage mismatch, or uncertainty about the mechanism's applicability.	Type 03 (Starter Module / Component Unbundle)The specific component that directly addresses the sub-problem they described is the downsell. A buyer uncertain about the full programme is rarely uncertain about solving one specific, named problem.	Component price: 15–30% of primary offer price.	20–35% of fit-uncertainty objectors
Implementation Fear — 'I'm not sure I can do this'	Doubt about personal capability or available time.	Type 01 (Self-Paced Version) if the fear is about keeping up with a cohort pace.Type 03 (Starter Module) focused on the Quick Win component if the fear is about where to start.	Self-paced: 30–50% of live programme price.Quick Win component: 15–25% of full price.	Self-paced for pace fear: 20–30%Starter module for 'where to start' fear: 25–35%
Comparison & Alternatives — 'I'm considering something else'	Evaluating alternatives — competitor, DIY, or different approach.	This objection type rarely responds to a downsell offer. If a buyer is actively comparing alternatives, the answer is better differentiation of the primary offer — not a smaller alternative to it.Exception: if they are comparing the full DWY programme to 'figuring it out alone,' a Type 03 component that solves their highest-priority sub-problem provides an entry point into the relationship.	Component price: 15–25% of primary.	Low: 5–15% of active comparison buyers unless the component is extremely high standalone value
Trust & Credibility — 'I've tried things like this before'	Has been burned by prior purchases in this category. Scepticism about the method or the operator.	A trust objection almost never responds to a lower-priced version of the same offer. The buyer does not distrust the price — they distrust the result. The correct response is better proof deployment and the guarantee.If the trust objection persists despite proof: a Type 03 minimal-risk component at a very low entry price ($47–$97) can function as a trust-building experience. The goal is a small win with zero risk, not revenue recovery.	Entry component: $47–$97 — below the conscious risk threshold.	Very low as revenue recovery: 5–10%. High as trust-building: 40–60% if the component delivers a tangible result quickly.

Source table 12

PHASE 1The Downsell Offer Design StandardsWhat every downsell must have, must not have, and must promise

Source table 13

DOWNSELL DESIGN BRIEF TEMPLATE — Complete before any build begins.DOWNSELL ID: DS-[Offer Code]-[DS Type Code]-[Seq]. e.g. DS-MVO-T01-001PRIMARY OFFER THIS DOWNSELL SERVESPrimary Offer Name: [Name]Primary Offer Price: [Price]Primary Offer Format: [Format]THE BUYER SEGMENT THIS DOWNSELL SERVESThe specific objection type this downsell addresses: [From the Trigger Matrix — which objection type]The specific buyer in this situation: [One sentence: who they are, what they want, and what is preventing the primary offer from being the right fit right now]// Example: 'A $5K–$10K/month online operator who wants to scale to $50K/month but cannot commit to live cohort calls due to timezone constraints.'THE DOWNSELL OFFERDownsell Type: [ ] Type 01 (Self-Paced) [ ] Type 02 (Format Reduction) [ ] Type 03 (Component Unbundle) [ ] Type 04 (Payment Plan) [ ] Type 05 (Wait-List)Downsell Name: [Standalone name — not '[Primary Offer] Lite' or '[Primary Offer] Basic']Downsell Price: [Price]Price Ratio to Primary: [Downsell ÷ Primary × 100 = ___%. Target: 20–50% of primary]WHAT IT INCLUDES (the Sub-Problem Test applied)The sub-problem this downsell solves: [One sentence: 'The buyer is struggling with ___. This downsell solves that specific problem by ___.]Components included:1. [Component name] — [sub-problem it solves]2. [Component name] — [sub-problem it solves]3. [Optional additional component]What the downsell does NOT include (explicitly — and why the exclusion is a feature, not a limitation):[Name what is not included and frame why the exclusion makes this product specifically right for this buyer's current situation]THE RESULT PROMISEThe specific, measurable result a buyer in this situation can expect from the downsell: [One sentence — specific enough to be testable]Timeframe: [How long to achieve the result]Guarantee (if applicable): [Will the downsell carry its own guarantee? Level? Copy?]THE ASCENSION PATHWhen will the buyer be offered the primary offer? [Timeline — e.g., after completing component 1, or at 30 days post-purchase, or via the onboarding email sequence]What is the ascension trigger? [The specific sub-problem the downsell reveals that the primary offer solves]

Source table 14

PHASE 2The Deployment ArchitectureWhere, when, and how each downsell type is presented

Source table 15

Channel	Buyer State at Moment of Downsell	Downsell Types That Work Here	Psychological Principle to Leverage	Timing
Checkout Page Decline(after cart abandon or declined upsell)	Buyer visited checkout but did not complete. Still in the purchase mindset — highest intent of any non-buyer.	Type 03 (Component Unbundle) — a low-price entry point that requires minimal commitment.Type 04 (Payment Plan) — if the barrier is the single-payment commitment.	Cialdini's Consistency: the buyer has already invested time researching. A lower-barrier entry preserves that investment rather than abandoning it.	Trigger immediately on cart abandon — within 2 minutes. Either redirect to a lower-price page or trigger a popup.
Post-Webinar Email Sequence(non-buyers after the cart closes)	Buyer attended or watched the webinar, considered the primary offer, and did not purchase by the deadline. Engaged but not converted.	Type 01 (Self-Paced) — for those who cited timing constraints.Type 02 (Format Reduction) — for price objectors.Type 03 (Component) — for fit-uncertain buyers.	Kennedy's Follow-Up Rule: a buyer who did not purchase at the close has not said no to the transformation. They said no to the specific terms. The follow-up sequence finds the terms they can say yes to.	Deploy Day 2 of the post-close follow-up (24 hours after the cart closes). Single email. Single downsell offer. Single deadline.
Sales Call — Live Downsell(after the primary close is declined)	Buyer is on a live call, has declined the primary offer after full consideration. Specific objection is known and documented.	Type matched to the specific objection using the Trigger Matrix.Do not deploy until the specific objection has been identified and addressed at least once.	NLP Reframing: the downsell is presented not as a lesser option but as the right option for their specific current situation — the one that produces the first win that makes everything else possible.	Deploy immediately after the primary close is declined and the specific objection has been named. Do not wait — the decision window closes as the call energy dissipates.
Email Nurture Sequence(warm subscribers who have never purchased)	Subscribers who have engaged with content but have never purchased anything. Lower intent than webinar attendees. Longer decision timeline.	Type 03 (Component at very low price — $27–$97) — low-barrier entry to convert a subscriber into a buyer.Type 05 (Wait-List) — for an upcoming cohort.	Cialdini's Reciprocity and Commitment: the first purchase at any price converts a subscriber into a buyer — the identity shift dramatically increases likelihood of future higher-value purchases.	Deploy as the Day 14 email in the email nurture sequence, after the primary offer has been presented and not converted. Single email, single offer.
Direct Message / Community(personal outreach to engaged non-buyers)	A specific person who has shown high engagement with content, asked about the offer, or been referred by a buyer — but has not purchased.	Type 03 (Component) or Type 05 (Wait-List deposit) — both are low-friction entry points suitable for personal outreach.Type 04 (Payment Plan) — if they have expressed budget hesitancy in conversation.	Cialdini's Liking: personal outreach from the operator is the highest-trust context available. The downsell in this channel should feel like a personal recommendation, not a marketing message.	Deploy after at least two prior touchpoints with the person have occurred organically. A cold DM with a downsell is a spam message.
Webinar Live Q&A(non-buyers still on the webinar)	Buyer is still on the webinar after the primary close has been presented. They have not left — which signals continued interest — but have not purchased.	Type 04 (Payment Plan) — most effective live downsell because it maintains the full offer while removing the payment barrier.Type 03 (Component) — for the buyer who states fit uncertainty during Q&A.	Scarcity and Social Proof: re-close with the payment plan announced as if it is a final accommodation. 'For anyone who loves the full programme but the single investment is challenging right now, I do have a payment option.'	Deploy once during the Q&A — not earlier. The live webinar context makes a mid-Q&A payment plan announcement feel generous rather than desperate.

Source table 16

PHASE 3The Complete Downsell Copy TemplatesFull scripts for every deployment channel

Source table 17

CHECKOUT DECLINE PAGE TEMPLATEHEADLINE (7 words maximum)// Option A — Component downsell:[SPECIFIC RESULT] in [TIMEFRAME] — Starting at $[Downsell Price]// Option B — Payment plan:Get Everything. Pay Over [Number] Months.// Option C — Self-paced:Same [Mechanism/Method]. Self-Paced. $[Price].BODY (40–60 words maximum)// This copy must acknowledge the primary offer and bridge to the downsell without shaming the non-purchase decision.You did not complete your order for [Primary Offer Name]. That is completely fine.Before you go: [one sentence on the downsell and who it is specifically right for].This is not [Primary Offer Name] with features removed. This is [Downsell Name], designed for [specific buyer situation].THE OFFER (two lines)[Downsell Name]: [One-sentence description][Price] — [What is included in 5 words maximum] — [Guarantee statement if applicable]THE CTA (single button — one action)[Specific action: 'Get [Downsell Name]' — not 'Learn More' or 'Check it Out']THE EXIT LINK (below the CTA — not a button)// Always include an exit option. Trapping buyers produces resentment, not sales.No thank you — take me to the [Primary Offer / Previous Page].// IMPLEMENTATION NOTE: Checkout decline pages should be A/B tested. Test Component Unbundle vs Payment Plan. The winner depends on which objection is more common for this specific offer.

Source table 18

POST-WEBINAR DOWNSELL EMAIL TEMPLATESUBJECT LINE OPTIONS (choose one based on primary objection type most common for this audience)// For timing objectors: 'Not ready for the full programme? This might be the right start.'// For price objectors: 'A different entry point into [Mechanism Name]'// For fit-uncertain buyers: 'If you are still unsure, start here.'// For component-interested buyers: 'Just want [specific component]? Here it is.'BODY[First name],The cart for [Primary Offer Name] is now closed.I want to share something briefly — not to extend the offer, but because I heard from several people who said [the most common reason given for not purchasing, verbatim from webinar Q&A or post-webinar reply emails].If that was your situation, I built something specifically for that.[Downsell Name] is [one sentence: what it is and who it is for].It does not include [what the primary offer includes that the downsell does not — stated as a feature of the downsell, not as a limitation]. That is intentional: [why that exclusion makes the downsell right for this buyer's situation].What it does include:[Component 1 — what it solves][Component 2 — what it solves][Component 3 if applicable]The investment is $[Downsell Price].[Guarantee statement if applicable.]This offer is available until [specific date — 48–72 hours from now. Must be a real deadline.][CTA: 'Get [Downsell Name]' — link to downsell checkout page]If neither offer is right for you right now, I completely understand. You will stay on my list and I will keep sharing [mechanism-related content] with you.[Operator name]P.S. [One sentence reiterating the specific buyer situation this downsell serves and why this is the right next step for them specifically.]

Source table 19

LIVE CALL DOWNSELL SCRIPT// TRIGGER: The primary close has been declined and the specific objection is confirmed.// RULE: Only deploy after the objection has been named. 'I can't buy right now' is not named. 'The single payment of $5,000 is too large for this month's budget' is named.THE BRIDGE'I appreciate you being direct about that. Let me ask you one more thing before we wrap up — and if this doesn't fit either, that is genuinely fine.'THE DOWNSELL OFFER'There is a different entry point into [the mechanism / the work we do together] that might be right for where you are right now.''It is called [Downsell Name]. Here is what it is: [one sentence — specific, plain, no jargon].''The reason I think this might be relevant for you specifically is: [connect the downsell directly to the named objection or situation they described in Stage 3 of the discovery call].'THE BRIEF DESCRIPTION'It includes [2–3 components stated briefly — one sentence each].''It does not include [what the primary offer includes but this doesn't — stated as a deliberate design choice, not a deficiency].''The investment is $[Downsell Price] — [payment structure if applicable].'THE SOFT CLOSE'Does that sound like it addresses where you are right now?'// Wait. Do not fill the silence.// If yes: 'Great. Let me send you the link now — you can take care of it in the next 10 minutes while we are still on the call together.' Process immediately.// If no: 'Completely fine. Tell me — is there anything that would have made the full programme work for you today, or is the timing genuinely not right?'THE GRACEFUL CLOSE (if both offers are declined)'I respect that. Let me keep you on my email list so you can see the results others are getting with [mechanism name]. When the timing is right, you will know exactly where to start.'// Book any future follow-up that was agreed to during the call.

Source table 20

SUBSCRIBER CONVERSION DOWNSELL EMAIL TEMPLATESUBJECT LINE// Personal, non-promotional tone. No ALL CAPS, no exclamation marks, no discount signals.// Examples: 'One specific thing' / 'Quick question, [first name]' / 'Something I built for exactly this'BODY[First name],You have been reading my content for [timeframe — if trackable] and I have appreciated having you here.I want to share something brief — because if what I write about [topic] is relevant to you, this might be useful.[Downsell Name] is [one sentence: what it is and who it is for. Personal tone — 'I built this for [avatar description]' not 'this product provides...'].It costs $[Downsell Price].Here is what is inside: [3–5 bullet points — each describing what it does for the buyer, not what it is. Format: 'Solve [sub-problem] with [component name]']There is no deadline on this. This is not a launch or a promotion. It is simply something I built that I think is genuinely useful for [avatar description], and if that is you — here is the link.[CTA: 'Get [Downsell Name]' — direct checkout link]If it is not for you right now, that is fine too. I will keep sharing.[Operator name]// NOTE: This email does NOT mention the primary offer. It is not framed as a downsell of anything. It is a standalone offer introduction. That framing produces higher conversion than 'you didn't buy X, so here is Y.'

Source table 21

DIRECT MESSAGE DOWNSELL TEMPLATE// CONTEXT: This message is sent to someone who has: (a) engaged meaningfully with content, (b) asked about the offer, or (c) been in conversation about the problem. This is NOT a cold message.THE PERSONAL OPENING'Hey [Name] — I noticed [specific observation: you commented on the post about X / you were on the webinar last week / you asked about Y in the community].''I wanted to reach out personally because [specific reason — something in their comment or question that makes this relevant].'THE BRIDGE'I don't know if you had the chance to look at [Primary Offer Name] — if not, no worries.''But I did want to mention something that I think might be more relevant for where you are right now based on what you shared.'THE OFFER'I built [Downsell Name] specifically for [their specific situation — reference their actual words if possible].''It is $[Price] and it [one sentence on the result it produces].''Happy to send you the link if you want to take a look — or if you have questions about whether it is the right fit, ask me anything.'THE EXIT'And if the timing is not right at all, that is completely fine — just wanted to make sure you knew about it.'// RULE: One message only unless they respond. Follow up on a non-response once, 5 days later, with a non-sales message ('how are things going with [their problem]?'). No third follow-up.

Source table 22

WEBINAR Q&A PAYMENT PLAN ANNOUNCEMENT SCRIPT// TIMING: Deploy this announcement approximately 5–7 minutes into the Q&A, after answering 2–3 substantive questions. Not at the beginning of Q&A and not as the final statement.THE ANNOUNCEMENT'Before I take the next question — I want to address something that I know is in the room for some people.''For anyone who loves what we covered today and would love access to [Primary Offer Name], but the single investment of $[price] is challenging right now — I do have a payment option available.''It is [X payments of $Y over Z months]. You get everything — every component, every resource, every [live element if applicable]. The total across the payments is $[total payment plan price].''If that is the option that works for you: the link in chat is the same link. You will see the payment plan option at checkout.'IMMEDIATELY CONTINUE'Okay — next question...'// Do NOT dwell on the payment plan or repeat it. State it once, cleanly, and move forward. Dwelling signals that you are concerned about close rates. Moving forward signals confidence.IF QUESTIONS ARISE ABOUT THE PAYMENT PLAN IN CHAT'The payment plan is [terms]. It is the same programme. The only difference is the payment schedule.'// Answer once in chat and return to Q&A. Do not dedicate multiple minutes to payment plan logistics during the live event.

Source table 23

PHASE 4The Downsell Ascension ArchitectureEnsuring every downsell buyer is on a documented path to the primary offer

Source table 24

Ascension Trigger Type	When It Fires	How It Works	Expected Ascension Rate
Completion-Based Trigger	Fires when the downsell buyer completes a defined milestone — finishes the component, submits the worksheet, or reaches a specific point in the curriculum.	Course platform (Kajabi or equivalent) triggers an email sequence upon module completion. The sequence presents the primary offer as the natural next step: 'You've just solved [the sub-problem the downsell addresses]. Here is the next challenge most operators face at this stage — and it is exactly what [Primary Offer Name] is designed for.'	12–20% of downsell buyers who complete the defined milestone
Time-Based Trigger	Fires at a specific number of days post-purchase: typically Day 14 (early engagement window) and Day 45 (post-completion window).	Automated email sequence. Day 14 email: 'How are you getting on with [Downsell Name]? [Two sentences of content relevant to their progress.] Also — for anyone who is ready to go deeper, [Primary Offer Name] opens its next cohort on [date].' Day 45 email: full ascension offer with social proof from buyers who started where the downsell buyer is now.	8–15% of downsell buyers in the time-based window
Result-Based Trigger	Fires when the buyer reports achieving the downsell's promised result — through a survey, a support ticket, a community post, or a testimonial submission.	Email sequence: 'I saw that you [achieved the result]. That is genuinely excellent. The operators who achieve [the result] typically face [the next specific challenge]. That next challenge is exactly what [Primary Offer Name] is designed for. Here is what it includes and what it would look like to join the next cohort.'	20–35% of downsell buyers who have confirmed achieving the result — this is the highest-converting ascension window because the buyer has tangible proof that the method works

Source table 25

Email	Timing	Subject Line Theme	Content Focus	CTA
Ascension Email 1 — The Next Problem Signal	Day 14 OR on milestone completion (whichever comes first)	'What comes after [downsell result] — the next challenge most operators face'	Deliver a brief piece of content that names the next problem the buyer will encounter after solving the one the downsell addressed. Do NOT pitch the primary offer yet — just name the next problem. Create the context for the ascension.	Reply and tell me how [Downsell Name] is going
Ascension Email 2 — The Social Proof Bridge	Day 21 OR 7 days after Email 1	'[Name] went from [downsell result stage] to [primary offer result] in [timeframe]'	A complete case study of a buyer who entered through the same downsell and ascended to the primary offer. Specifically: who they were, what the downsell gave them, what the next problem was, how the primary offer addressed it, and the specific result they achieved.	Read the full story — [link to case study or sales page]
Ascension Email 3 — The Direct Offer	Day 30 OR 14 days after Email 1	'[Primary Offer Name] opens for [Downsell Buyer First Name]'	Full offer presentation. Stack slide. Guarantee. Price. Founding member pricing if the buyer is being offered an incentive for prior purchase. One specific deadline — 72 hours.	Get started with [Primary Offer Name] — [checkout link]

Source table 26

The Downsell Founding Member IncentiveBuyers who entered through a downsell and are being offered ascension to the primary offer may be offered a credit for their prior purchase — their downsell investment is deducted from the primary offer price. Example: a buyer who paid $297 for the downsell is offered the primary offer at $997 − $297 = $700 credit applied.This incentive has two functions: (1) it acknowledges the prior relationship and rewards loyalty, and (2) it provides a genuine price incentive that is not available to new buyers — real exclusivity. Not all operators use this approach, but those who do report ascension rates 1.5–2× the baseline rate.

Source table 27

PHASE 5The Downsell Stack ArchitectureSequencing multiple downsells without burning the relationship

Source table 28

Layer	Offer Type	Price Target	Trigger	Copy Approach
Layer 1 — Primary Downsell	Type 01, 02, or 03 depending on the primary offer and most common objection	30–50% of primary offer price	Fires immediately on cart abandon or 24 hours after primary offer close	Substantive — explains the value of the specific downsell for the specific buyer situation. Full copy per Channel 1 or Channel 2 templates.
Layer 2 — Micro-Commitment	Type 03 (Component Unbundle) — the lowest-price, highest-standalone-value component	15–25% of primary offer price	Fires 48 hours after Layer 1 if Layer 1 was not purchased	Brief — acknowledges the prior offer was not right, presents the specific component in 2–3 sentences. No pressure, no deadline extension.
Layer 3 — Minimum Entry	A free or very low cost lead magnet or entry product that maintains the relationship without requiring a purchase commitment	Free or $7–$27	Fires 96 hours after Layer 2 if Layer 2 was not purchased	Relationship-maintenance frame — 'I understand this is not the right time. Here is something free / very low cost that I think you will find genuinely useful.' This is not a sales message — it is a relationship preservation message.

Source table 29

The Burn ThresholdA non-buyer who receives three offers in four days has reached the burn threshold. After Layer 3, the buyer goes onto a standard content nurture sequence — not a sales sequence. The nurture sequence continues to provide value and will re-present the primary offer at the next natural launch cycle. There is no Layer 4. The burn threshold exists to protect the relationship.

Source table 30

PHASE 6The Downsell Performance DashboardThe metrics that determine whether to iterate, optimise, or retire a downsell

Source table 31

Metric	Calculation	Healthy Range	Action If Outside Range
Downsell offer rate	Number of non-buyers who see the downsell ÷ total non-buyers × 100	100% — every non-buyer should see the relevant downsell via at least one channel	If below 100%: identify which buyer type is not receiving the downsell. Check funnel architecture — is there a trigger gap?
Downsell conversion rate	Downsell purchases ÷ non-buyers who saw the downsell × 100	Type 01/02/03: 10–25%Type 04 (Payment Plan): 25–40%Type 05 (Wait-List): 30–45%	Below the lower bound: review the copy (is it presenting the downsell as 'lesser than' rather than 'right for this buyer'?) and the trigger accuracy (is the downsell being shown to buyers whose objection matches the downsell type?)
Revenue recovery rate	Downsell revenue ÷ lost primary revenue × 100	15–40% of lost primary offer revenue recovered	Below 15%: the downsell is not converting enough of the available non-buyer pool. Review trigger accuracy and copy. Above 40%: the downsell is performing exceptionally — consider whether the primary offer's price point needs testing.
Downsell refund rate	Downsell refunds ÷ downsell purchases × 100	Below 10% — lower than the primary offer refund rate (buyers at a lower price point with matched expectations should refund less)	Above 12%: the downsell is creating expectation mismatches. Review the promise language — is the downsell promising more than it delivers? Is the wrong buyer type being targeted by the trigger?
Ascension rate from downsell	Downsell buyers who purchase the primary offer within 90 days ÷ total downsell buyers × 100	10–20% — 1 in 10 to 1 in 5 downsell buyers should ascend to the primary offer within 90 days	Below 8%: the ascension sequence is not firing correctly, or the ascension emails are not surfacing the next problem clearly. Review the completion-based trigger and Email 1 content. Above 25%: the downsell is an exceptionally good entry point — consider featuring it as the recommended starting point.
Average order value lift	Total revenue (primary + downsell) ÷ total visitors — compared against primary-only AOV	3–10% AOV lift from the downsell architecture across all visitor traffic	Below 3%: the downsell is not reaching enough of the non-buyer population. Review deployment channel coverage. Above 10%: strong performance — scale traffic.
Time-to-ascension	Average days from downsell purchase to primary offer purchase	45–90 days — fast enough to maintain momentum, slow enough to confirm the downsell is delivering value first	Below 30 days: buyers may be ascending before the downsell has delivered value — review the ascension trigger timing. Above 120 days: the ascension sequence may not be compelling enough or the downsell result achievement rate may be low (buyers are not getting the win that creates ascension motivation).
LTV of downsell entry buyers vs direct primary buyers	Compare 12-month revenue from buyers who entered via downsell vs those who entered direct at primary price	Downsell entry LTV should reach 60–80% of direct primary buyer LTV within 12 months	Below 50%: downsell buyers are not ascending. Review the ascension architecture. Equal to or above primary buyer LTV: the downsell is functioning as a high-quality entry point — increase its promotion.

Source table 32

PHASE 7Integration With the Master Operating SystemHow downsells connect to the other RISER Nation SOPs

Source table 33

Connected SOP	Connection to Downsells	The Data Flow
Objection Bank SOP	The Objection Bank's objection type classification and Priority Score ranking determines which downsell trigger fires for which non-buyer. Every new Objection Bank entry above Priority Score 8 should trigger a review of the downsell trigger matrix.	Objection Bank → Trigger Matrix → Downsell type selection. Monthly review: do the top 3 objection types in the Objection Bank match the downsell types currently deployed?
Offer Stacking & Unbundling Strategy SOP	Type 03 (Component Unbundle) downsells require a documented IP Asset Inventory with Unbundle Score assessments. A component must score 7+ on the Unbundle Score before it becomes a downsell offer.	IP Asset Inventory Unbundle Scores → Type 03 downsell product selection. Quarterly review: are there newly-scored assets that qualify as Type 03 downsell candidates?
Product Versioning SOP	Every downsell offer is a versioned product. Any change to the downsell's components, price, or guarantee triggers a Minor version change (CAT-O for stack changes, CAT-P for price changes). The Changelog tracks all downsell product versions.	All downsell offer changes → Changelog entries. The Testimonial Version Registry tracks which testimonials are valid for which downsell version.
Price Elasticity Testing Framework SOP	Downsell prices should be tested with the same rigour as primary offer prices. The Van Westendorp survey run for the primary offer includes questions about the downsell price range. The RPV calculation applies to downsells within their specific non-buyer pool.	Van Westendorp PMC/PME for the non-buyer pool → Downsell price testing range. Quarterly: is the downsell price at the revenue-maximising point in the RPV curve for non-buyers?
Forensic Audit Loop SOP	The Refund Root Cause analysis for downsell refunds feeds back into the downsell trigger matrix — if a Type 03 component downsell is generating refunds with RC code 'not what I expected,' the component's standalone positioning needs a fix.	Downsell refund RC codes → Trigger matrix accuracy review → Downsell copy and positioning updates.
Guarantee Type Testing Protocol SOP	Downsell offers should carry their own guarantees, not simply inherit the primary offer guarantee. The Risk Score for the downsell (typically lower — smaller investment, simpler delivery) usually supports Level 2 or Level 3 guarantees even when the primary is at Level 1.	Downsell Risk Score → Downsell guarantee level selection → Guarantee Type Testing Protocol for the downsell offer specifically.
Dead Offer Resurrection Playbook SOP	When a primary offer enters the Flatline state, its highest-performing downsell becomes the candidate for continuing the revenue stream during the resurrection period. The downsell may serve as the 'minimum viable live product' while the primary is being rebuilt.	Primary offer enters Flatline → Downsell performance assessment → Decision: maintain downsell as interim primary or retire alongside the primary offer.

Source table 34

Field	Type	Notes
Downsell ID	Short text	Format: DS-[Offer Code]-[Type Code]-[Seq]. e.g. DS-MVO-T03-001
Downsell Name	Short text	The product name — standalone, not a reference to the primary offer
Primary Offer	Link → Offers table	The offer this downsell serves
Downsell Type	Single select	Type 01 (Self-Paced) / Type 02 (Format Reduction) / Type 03 (Component) / Type 04 (Payment Plan) / Type 05 (Wait-List)
Objection Type Targeted	Single select	Price & Value / Timing / Fit & Relevance / Implementation Fear / Trust / Comparison
Current Price	Currency
Primary Offer Price Ratio	Formula	Downsell Price ÷ Primary Offer Price × 100. Target: 20–50%
Payment Plan Terms (if Type 04)	Short text	e.g. '3 × $367 over 60 days'
Sub-Problem Solved	Short text	One sentence: 'The buyer is struggling with ___. This solves that by ___.
What Is Excluded (and why it is a feature)	Long text	What the primary offer includes that this does not, and the one-sentence framing of why the exclusion is appropriate for this buyer
Result Promised	Short text	The specific, measurable result the downsell buyer should expect
Result Timeframe	Short text	e.g. '30 days'
Guarantee Level	Single select	None / Level 1 / Level 2 / Level 3
Guarantee Copy	Long text	Verbatim from Guarantee Type Testing Protocol SOP
Ascension Trigger Type	Multi-select	Completion-Based / Day 14 Time-Based / Day 45 Time-Based / Result-Based
Ascension Sequence Active	Checkbox	Is the 3-email ascension sequence live and triggering?
Downsell Offer Rate	Number	% of non-buyers seeing this downsell (rolling 30 days)
Downsell Conversion Rate	Number	% of non-buyers who see it and purchase (rolling 30 days)
Downsell Revenue (rolling 30 days)	Currency
Downsell Refund Rate	Number	% rolling 30 days
Ascension Rate (90-day)	Number	% of downsell buyers who purchase the primary offer within 90 days
Status	Single select	Active / Under Test / Archived
Version	Short text	From Product Versioning SOP Changelog — current version identifier
Changelog Entry	Link → Changelog Entries	Latest CAT entry for this downsell product
Linked Testimonials	Link → Testimonial Version Registry	Testimonials from downsell buyers — for use in ascension emails and downsell copy
Notes	Long text	Observations, test results, copy variants, deployment notes

Native Word text, including document headers and footers

word/document.xml
RISER NATION
MASTER OPERATING SYSTEM
SOP — DOWNSELL PATHS
The Complete Architecture for Recovering Revenue From Every 'No' — Without Damaging the Primary Offer or the Buyer Relationship
Kennedy × Hormozi × Brunson × Cialdini × 2026 Framework
Version 1.0 | 2026 Edition | RISER Nation Master Operating System
SOP Overview
A downsell is not a consolation prize. It is the precision instrument that recovers revenue from the specific buyer segment that wanted the transformation but could not access the primary offer — for reasons of price, commitment, timing, or format — and redirects them into the value ladder at the entry point that actually serves their current situation.
Most operators treat downsells as an afterthought: a quick email that says 'still interested? Here's a cheaper option.' That approach fails because it presents the downsell as a lesser version of something the buyer could not afford, which activates both shame and diminished expectation. A well-engineered downsell reframes the situation entirely: the buyer has found the right entry point for their specific current situation, and the downsell offer is designed precisely for that situation.
This SOP covers: the economic case for downsell architecture, the five downsell types with their specific deployment contexts, the trigger matrix that maps each objection type to the correct downsell path, the downsell offer design standards, the copy templates for every deployment channel (checkout page, email sequence, sales call, webinar, direct message), the ascension architecture that ensures downsell buyers eventually reach the primary offer, the measurement framework, and the Airtable schema.
Brunson's Revenue Recovery Data
In Brunson's funnel data, a well-designed downsell sequence recovers 10–30% of the revenue that would otherwise be lost entirely. On a $997 offer with 100 monthly declines, a $297 downsell converting at 20% of decliners adds $5,940/month in recovered revenue — without any additional traffic, any new content creation, or any change to the primary offer. Downsells are the highest-ROI mechanism in the entire offer architecture.
Kennedy's Critical Distinction
The downsell must serve the buyer, not the operator. A downsell that exists only to extract some revenue from a buyer who said no to the primary offer will feel predatory and will damage the relationship. A downsell that exists because there is a genuine entry-level version of the transformation — designed for a buyer who is not yet ready for the full programme — serves both parties. If you cannot build a downsell that genuinely serves the buyer's current situation, you should not build one.
Hormozi's Positioning Rule for Downsells
Never present the downsell as 'the same thing but cheaper.' Present it as 'the right thing for where you are right now.' The buyer who received the downsell should feel that the offer they purchased was designed for their specific current situation — not that they got a lesser version of something they could not afford. The copy, the name, and the delivery format should all reflect the downsell's own positioning, not its relationship to the primary offer.
The Economic Case for Downsell Architecture
Before designing any downsell, the operator must understand the revenue mechanics that make downsells one of the most leveraged investments of time in the business. The numbers below assume a specific scenario — adjust for your own offer metrics.
Scenario
Without Downsells
With Downsell Architecture
Difference
Primary offer: $997
100 monthly cold visitors
2% cold conversion
Sales: 2 × $997 = $1,994
Non-buyers: 98
Revenue from non-buyers: $0
Sales from primary: 2 × $997 = $1,994
Downsell at $297 to 98 non-buyers: 20 purchase = $5,940
Total: $7,934
$5,940 additional revenue
+298% revenue lift from same traffic
Primary offer: $2,497
50 monthly warm email sequence openers
15% warm conversion
Sales: 7.5 × $2,497 = $18,728
Non-buyers: 42.5
Revenue from non-buyers: $0
Primary sales: 7.5 × $2,497 = $18,728
Downsell to 42.5 non-buyers at $497: 25% purchase = $5,303
Total: $24,031
$5,303 additional revenue
+28% revenue lift from the same list
Discovery call: $5,000
20 monthly qualified calls
25% close rate
Closed: 5 × $5,000 = $25,000
Non-closes: 15
Revenue from non-closes: $0
Primary closes: 5 × $5,000 = $25,000
Downsell at $997 to 15 non-closes: 20% accept = $2,991
Total: $27,991
$2,991 additional revenue
+12% revenue lift from the same call volume
The Revenue Per Visitor Impact
Downsells do not just add revenue — they change the fundamental unit economics of the business. When a business has a downsell architecture, every traffic source becomes more profitable because a higher percentage of visitors result in a purchase at some price. This changes the CAC calculation and often makes previously unprofitable traffic sources viable.
The Five Downsell Types
Every downsell in a knowledge business fits one of five structural types. Each type serves a different buyer segment and deploys in a different conversion context. Selecting the wrong type for the context produces low conversion. Selecting the right type for the right context produces the 10–30% recovery rate Brunson documents.
TYPE 01
The Self-Paced Version
When to deploy
The buyer wants the transformation but cannot commit to the live, cohort-based, or DWY format — due to schedule constraints, time zone, or preference for asynchronous learning.
The mechanism
Remove the live component. Keep the intellectual content and the framework. Deliver as recorded modules, worksheets, and text-based resources. Price at 30–50% of the live programme.
Typical conversion rate
15–25% of primary offer decliners when the timing objection was the stated reason
Best for
Core offers ($997–$4,997) that have a significant live component (group calls, cohort accountability, live Q&A). The self-paced version is the same curriculum without the synchronous elements.
Risk to manage
The self-paced version must be genuinely valuable on its own — not a stripped-out version that sets the buyer up to fail. If the programme genuinely requires live interaction to produce the result, the self-paced version should not exist.
TYPE 02
The Format Reduction
When to deploy
The buyer wants the result but cannot afford the full investment at the stated price. The format changes — group instead of 1:1, text-based instead of video, community instead of direct access — while the core mechanism is preserved.
The mechanism
Reduce the delivery touch-points that carry the highest cost to the operator (1:1 time, personalised feedback, direct access). Keep the mechanism, the frameworks, and the self-implementation tools. Price at 30–50% of the primary.
Typical conversion rate
15–25% of decliners when the price objection was primary and the buyer confirmed the mechanism was right for them
Best for
DWY and high-ticket offers ($3,000–$15,000) where a significant portion of the price is driven by access to the operator's time. The format reduction removes the high-cost access while preserving the high-value intellectual content.
Risk to manage
The buyer must genuinely be able to get a meaningful result from the reduced format. If the result requires 1:1 implementation support and the downsell removes that, the buyer will fail and refund.
TYPE 03
The Starter Module or Component Unbundle
When to deploy
The buyer is uncertain about committing to the full programme or cannot afford the full price, but has a specific, named sub-problem that one component of the full offer directly addresses.
The mechanism
Identify the single highest-value component of the full offer — a specific module, template, swipe file, or framework — that solves the most urgent sub-problem independently. Sell it as a standalone. Price at 15–30% of the primary offer.
Typical conversion rate
20–35% of decliners when uncertainty about fit was the stated objection, or when the buyer confirmed they most needed one specific element
Best for
Any offer where one component has clearly identifiable standalone value. This type is closely connected to the Offer Stacking & Unbundling Strategy SOP — the unbundle of a component as a downsell is one of the highest-leverage IP asset deployment strategies available.
Risk to manage
The starter module must NOT contain so much value that it eliminates the buyer's motivation to ascend to the full programme. Design it to solve one specific sub-problem while revealing the next sub-problem — creating the natural desire for the full offer.
TYPE 04
The Payment Plan
When to deploy
The buyer wants the full offer exactly as presented but faces a cash flow constraint that makes the single payment difficult or impossible in this period.
The mechanism
Offer the full primary offer broken into instalments. Price the payment plan at 110–120% of the single-pay price (the premium compensates for cash flow risk and payment processing costs). Terms: typically 2–4 payments over 30–90 days.
Typical conversion rate
25–40% of decliners when the budget objection was primary and the buyer confirmed commitment to the transformation
Best for
Any offer above $500 where the payment plan premium (10–20%) is small relative to the total value. Particularly high-converting for offers in the $997–$4,997 range where the single payment requires deliberate budget allocation.
Risk to manage
The payment plan is NOT a downsell in the structural sense — it delivers the same offer. But it is the correct response to a specific budget objection and belongs in the downsell decision matrix. The risk: payment plan buyers have a higher refund and chargeback rate than single-pay buyers. Mitigate with a stronger onboarding sequence and a completion commitment contract.
TYPE 05
The Wait-List / Delayed Entry
When to deploy
The buyer is interested and qualified but cannot commit right now due to an external circumstance (a major project, a business transition, a personal commitment) that will resolve within a defined timeframe.
The mechanism
Offer the buyer a reserved spot in the next cohort or intake at today's price. Collect a small deposit ($97–$297) to confirm intent. No additional work is required until the start date. The deposit is credited to the full price at entry.
Typical conversion rate
30–45% of decliners when the timing objection was 'I need X more weeks/months before I can start'
Best for
Cohort-based programmes where future cohort dates are confirmed. Also useful when the primary offer has a price increase planned — 'the next cohort opens in [date] at today's price' creates genuine urgency without manufactured pressure.
Risk to manage
The deposit creates commitment but also obligation. The refund policy for deposits must be documented and communicated clearly at the point of collection. A buyer who paid a deposit and then finds they still cannot start at the reserved cohort date will require a managed transition process.
The Downsell Trigger Matrix
The trigger matrix maps every primary offer objection type to the correct downsell path. The wrong downsell for the stated objection produces near-zero conversion — a price downsell offered to a buyer whose real objection was timing will not convert because the price was not the barrier. The matrix ensures the downsell addresses the actual reason the buyer declined the primary.
Primary Objection Type
Root Concern
Correct Downsell Type
Downsell Price Logic
Conversion Expectation
Price & Value — 'It's too expensive'
Fear of wasting money. Value-to-price ratio does not feel right.
Type 02 (Format Reduction) or Type 04 (Payment Plan)
Type 04 if: 'I want the full programme but cannot pay all at once.'
Type 02 if: 'The price is genuinely beyond budget even with a payment plan.'
Payment plan: full price + 10–20% premium.
Format reduction: 30–50% of primary price.
Payment plan: 25–40% of price objectors
Format reduction: 15–25% of price objectors
Timing & Urgency — 'Now is not the right time'
Calendar is too full, or a specific project/event is blocking.
Type 01 (Self-Paced Version) or Type 05 (Wait-List)
Type 05 if: the constraint is temporary and the buyer has a clear re-entry date.
Type 01 if: the buyer's schedule makes synchronous commitment impossible but they can learn asynchronously.
Self-paced: 30–50% of live cohort price.
Wait-list deposit: $97–$297 credited to full price.
Self-paced: 15–20% of timing objectors
Wait-list: 30–45% of timing objectors with a specific re-entry date
Fit & Relevance — 'I'm not sure this is right for me'
Avatar mismatch, stage mismatch, or uncertainty about the mechanism's applicability.
Type 03 (Starter Module / Component Unbundle)
The specific component that directly addresses the sub-problem they described is the downsell. A buyer uncertain about the full programme is rarely uncertain about solving one specific, named problem.
Component price: 15–30% of primary offer price.
20–35% of fit-uncertainty objectors
Implementation Fear — 'I'm not sure I can do this'
Doubt about personal capability or available time.
Type 01 (Self-Paced Version) if the fear is about keeping up with a cohort pace.
Type 03 (Starter Module) focused on the Quick Win component if the fear is about where to start.
Self-paced: 30–50% of live programme price.
Quick Win component: 15–25% of full price.
Self-paced for pace fear: 20–30%
Starter module for 'where to start' fear: 25–35%
Comparison & Alternatives — 'I'm considering something else'
Evaluating alternatives — competitor, DIY, or different approach.
This objection type rarely responds to a downsell offer. If a buyer is actively comparing alternatives, the answer is better differentiation of the primary offer — not a smaller alternative to it.
Exception: if they are comparing the full DWY programme to 'figuring it out alone,' a Type 03 component that solves their highest-priority sub-problem provides an entry point into the relationship.
Component price: 15–25% of primary.
Low: 5–15% of active comparison buyers unless the component is extremely high standalone value
Trust & Credibility — 'I've tried things like this before'
Has been burned by prior purchases in this category. Scepticism about the method or the operator.
A trust objection almost never responds to a lower-priced version of the same offer. The buyer does not distrust the price — they distrust the result. The correct response is better proof deployment and the guarantee.
If the trust objection persists despite proof: a Type 03 minimal-risk component at a very low entry price ($47–$97) can function as a trust-building experience. The goal is a small win with zero risk, not revenue recovery.
Entry component: $47–$97 — below the conscious risk threshold.
Very low as revenue recovery: 5–10%. High as trust-building: 40–60% if the component delivers a tangible result quickly.
PHASE 1
The Downsell Offer Design Standards
What every downsell must have, must not have, and must promise
The Three Downsell Design Rules
Rule 1 — The downsell must solve a real problem. Not 'it is cheaper than the primary.' A real problem that a real buyer in a specific situation has. The sub-problem test from the Bonus Discipline Audit SOP applies here with equal force: if the downsell cannot be described in one sentence beginning with 'The buyer is struggling with...' it is not a downsell — it is a discount.
Rule 2 — The downsell must have its own positioning. It is not 'the MVO minus the coaching calls.' It is '[Specific Product Name] — the [specific format] designed for [specific avatar in specific situation].' The name, the promise, and the copy are all written for the downsell's own avatar, not as a comparison to the primary offer.
Rule 3 — The downsell must have an ascension path. Every buyer who enters the value ladder through a downsell must be exposed to the primary offer and above — through an onboarding sequence, through the programme's content, or through a dedicated ascension email sequence. The downsell is an entry point, not a permanent home.
The Downsell Design Brief
Before building any downsell offer, complete this brief. A downsell built without a documented brief often fails the three rules above — producing an offer that is neither genuinely useful nor genuinely distinct from the primary.
DOWNSELL DESIGN BRIEF TEMPLATE — Complete before any build begins.
DOWNSELL ID: DS-[Offer Code]-[DS Type Code]-[Seq]. e.g. DS-MVO-T01-001
PRIMARY OFFER THIS DOWNSELL SERVES
Primary Offer Name: [Name]
Primary Offer Price: [Price]
Primary Offer Format: [Format]
THE BUYER SEGMENT THIS DOWNSELL SERVES
The specific objection type this downsell addresses: [From the Trigger Matrix — which objection type]
The specific buyer in this situation: [One sentence: who they are, what they want, and what is preventing the primary offer from being the right fit right now]
// Example: 'A $5K–$10K/month online operator who wants to scale to $50K/month but cannot commit to live cohort calls due to timezone constraints.'
THE DOWNSELL OFFER
Downsell Type: [ ] Type 01 (Self-Paced) [ ] Type 02 (Format Reduction) [ ] Type 03 (Component Unbundle) [ ] Type 04 (Payment Plan) [ ] Type 05 (Wait-List)
Downsell Name: [Standalone name — not '[Primary Offer] Lite' or '[Primary Offer] Basic']
Downsell Price: [Price]
Price Ratio to Primary: [Downsell ÷ Primary × 100 = ___%. Target: 20–50% of primary]
WHAT IT INCLUDES (the Sub-Problem Test applied)
The sub-problem this downsell solves: [One sentence: 'The buyer is struggling with ___. This downsell solves that specific problem by ___.]
Components included:
1. [Component name] — [sub-problem it solves]
2. [Component name] — [sub-problem it solves]
3. [Optional additional component]
What the downsell does NOT include (explicitly — and why the exclusion is a feature, not a limitation):
[Name what is not included and frame why the exclusion makes this product specifically right for this buyer's current situation]
THE RESULT PROMISE
The specific, measurable result a buyer in this situation can expect from the downsell: [One sentence — specific enough to be testable]
Timeframe: [How long to achieve the result]
Guarantee (if applicable): [Will the downsell carry its own guarantee? Level? Copy?]
THE ASCENSION PATH
When will the buyer be offered the primary offer? [Timeline — e.g., after completing component 1, or at 30 days post-purchase, or via the onboarding email sequence]
What is the ascension trigger? [The specific sub-problem the downsell reveals that the primary offer solves]
PHASE 2
The Deployment Architecture
Where, when, and how each downsell type is presented
The Six Deployment Channels
Downsells are presented in six distinct conversion contexts, each with different buyer states, different psychological dynamics, and different copy requirements. The same downsell offer requires completely different presentation language in each channel.
Channel
Buyer State at Moment of Downsell
Downsell Types That Work Here
Psychological Principle to Leverage
Timing
Checkout Page Decline
(after cart abandon or declined upsell)
Buyer visited checkout but did not complete. Still in the purchase mindset — highest intent of any non-buyer.
Type 03 (Component Unbundle) — a low-price entry point that requires minimal commitment.
Type 04 (Payment Plan) — if the barrier is the single-payment commitment.
Cialdini's Consistency: the buyer has already invested time researching. A lower-barrier entry preserves that investment rather than abandoning it.
Trigger immediately on cart abandon — within 2 minutes. Either redirect to a lower-price page or trigger a popup.
Post-Webinar Email Sequence
(non-buyers after the cart closes)
Buyer attended or watched the webinar, considered the primary offer, and did not purchase by the deadline. Engaged but not converted.
Type 01 (Self-Paced) — for those who cited timing constraints.
Type 02 (Format Reduction) — for price objectors.
Type 03 (Component) — for fit-uncertain buyers.
Kennedy's Follow-Up Rule: a buyer who did not purchase at the close has not said no to the transformation. They said no to the specific terms. The follow-up sequence finds the terms they can say yes to.
Deploy Day 2 of the post-close follow-up (24 hours after the cart closes). Single email. Single downsell offer. Single deadline.
Sales Call — Live Downsell
(after the primary close is declined)
Buyer is on a live call, has declined the primary offer after full consideration. Specific objection is known and documented.
Type matched to the specific objection using the Trigger Matrix.
Do not deploy until the specific objection has been identified and addressed at least once.
NLP Reframing: the downsell is presented not as a lesser option but as the right option for their specific current situation — the one that produces the first win that makes everything else possible.
Deploy immediately after the primary close is declined and the specific objection has been named. Do not wait — the decision window closes as the call energy dissipates.
Email Nurture Sequence
(warm subscribers who have never purchased)
Subscribers who have engaged with content but have never purchased anything. Lower intent than webinar attendees. Longer decision timeline.
Type 03 (Component at very low price — $27–$97) — low-barrier entry to convert a subscriber into a buyer.
Type 05 (Wait-List) — for an upcoming cohort.
Cialdini's Reciprocity and Commitment: the first purchase at any price converts a subscriber into a buyer — the identity shift dramatically increases likelihood of future higher-value purchases.
Deploy as the Day 14 email in the email nurture sequence, after the primary offer has been presented and not converted. Single email, single offer.
Direct Message / Community
(personal outreach to engaged non-buyers)
A specific person who has shown high engagement with content, asked about the offer, or been referred by a buyer — but has not purchased.
Type 03 (Component) or Type 05 (Wait-List deposit) — both are low-friction entry points suitable for personal outreach.
Type 04 (Payment Plan) — if they have expressed budget hesitancy in conversation.
Cialdini's Liking: personal outreach from the operator is the highest-trust context available. The downsell in this channel should feel like a personal recommendation, not a marketing message.
Deploy after at least two prior touchpoints with the person have occurred organically. A cold DM with a downsell is a spam message.
Webinar Live Q&A
(non-buyers still on the webinar)
Buyer is still on the webinar after the primary close has been presented. They have not left — which signals continued interest — but have not purchased.
Type 04 (Payment Plan) — most effective live downsell because it maintains the full offer while removing the payment barrier.
Type 03 (Component) — for the buyer who states fit uncertainty during Q&A.
Scarcity and Social Proof: re-close with the payment plan announced as if it is a final accommodation. 'For anyone who loves the full programme but the single investment is challenging right now, I do have a payment option.'
Deploy once during the Q&A — not earlier. The live webinar context makes a mid-Q&A payment plan announcement feel generous rather than desperate.
PHASE 3
The Complete Downsell Copy Templates
Full scripts for every deployment channel
Channel 1 — Checkout Page Decline
The checkout page decline page or popup appears when a visitor abandons the checkout without completing the purchase. The copy must be extremely brief — this buyer is in transition and will not read a long sales pitch.
CHECKOUT DECLINE PAGE TEMPLATE
HEADLINE (7 words maximum)
// Option A — Component downsell:
[SPECIFIC RESULT] in [TIMEFRAME] — Starting at $[Downsell Price]
// Option B — Payment plan:
Get Everything. Pay Over [Number] Months.
// Option C — Self-paced:
Same [Mechanism/Method]. Self-Paced. $[Price].
BODY (40–60 words maximum)
// This copy must acknowledge the primary offer and bridge to the downsell without shaming the non-purchase decision.
You did not complete your order for [Primary Offer Name]. That is completely fine.
Before you go: [one sentence on the downsell and who it is specifically right for].
This is not [Primary Offer Name] with features removed. This is [Downsell Name], designed for [specific buyer situation].
THE OFFER (two lines)
[Downsell Name]: [One-sentence description]
[Price] — [What is included in 5 words maximum] — [Guarantee statement if applicable]
THE CTA (single button — one action)
[Specific action: 'Get [Downsell Name]' — not 'Learn More' or 'Check it Out']
THE EXIT LINK (below the CTA — not a button)
// Always include an exit option. Trapping buyers produces resentment, not sales.
No thank you — take me to the [Primary Offer / Previous Page].
// IMPLEMENTATION NOTE: Checkout decline pages should be A/B tested. Test Component Unbundle vs Payment Plan. The winner depends on which objection is more common for this specific offer.
Channel 2 — Post-Webinar Email (Day 2 of Follow-Up Sequence)
This email goes to webinar attendees and replay watchers who have not purchased by the end of the primary close window. It deploys 24 hours after the cart closes.
POST-WEBINAR DOWNSELL EMAIL TEMPLATE
SUBJECT LINE OPTIONS (choose one based on primary objection type most common for this audience)
// For timing objectors: 'Not ready for the full programme? This might be the right start.'
// For price objectors: 'A different entry point into [Mechanism Name]'
// For fit-uncertain buyers: 'If you are still unsure, start here.'
// For component-interested buyers: 'Just want [specific component]? Here it is.'
BODY
[First name],
The cart for [Primary Offer Name] is now closed.
I want to share something briefly — not to extend the offer, but because I heard from several people who said [the most common reason given for not purchasing, verbatim from webinar Q&A or post-webinar reply emails].
If that was your situation, I built something specifically for that.
[Downsell Name] is [one sentence: what it is and who it is for].
It does not include [what the primary offer includes that the downsell does not — stated as a feature of the downsell, not as a limitation]. That is intentional: [why that exclusion makes the downsell right for this buyer's situation].
What it does include:
[Component 1 — what it solves]
[Component 2 — what it solves]
[Component 3 if applicable]
The investment is $[Downsell Price].
[Guarantee statement if applicable.]
This offer is available until [specific date — 48–72 hours from now. Must be a real deadline.]
[CTA: 'Get [Downsell Name]' — link to downsell checkout page]
If neither offer is right for you right now, I completely understand. You will stay on my list and I will keep sharing [mechanism-related content] with you.
[Operator name]
P.S. [One sentence reiterating the specific buyer situation this downsell serves and why this is the right next step for them specifically.]
Channel 3 — Sales Call Live Downsell Script
The live call downsell is deployed immediately after the primary close is declined and the specific objection has been identified and addressed at least once. The sequence below follows directly from the Close section of the Sales Call Scripts SOP.
LIVE CALL DOWNSELL SCRIPT
// TRIGGER: The primary close has been declined and the specific objection is confirmed.
// RULE: Only deploy after the objection has been named. 'I can't buy right now' is not named. 'The single payment of $5,000 is too large for this month's budget' is named.
THE BRIDGE
'I appreciate you being direct about that. Let me ask you one more thing before we wrap up — and if this doesn't fit either, that is genuinely fine.'
THE DOWNSELL OFFER
'There is a different entry point into [the mechanism / the work we do together] that might be right for where you are right now.'
'It is called [Downsell Name]. Here is what it is: [one sentence — specific, plain, no jargon].'
'The reason I think this might be relevant for you specifically is: [connect the downsell directly to the named objection or situation they described in Stage 3 of the discovery call].'
THE BRIEF DESCRIPTION
'It includes [2–3 components stated briefly — one sentence each].'
'It does not include [what the primary offer includes but this doesn't — stated as a deliberate design choice, not a deficiency].'
'The investment is $[Downsell Price] — [payment structure if applicable].'
THE SOFT CLOSE
'Does that sound like it addresses where you are right now?'
// Wait. Do not fill the silence.
// If yes: 'Great. Let me send you the link now — you can take care of it in the next 10 minutes while we are still on the call together.' Process immediately.
// If no: 'Completely fine. Tell me — is there anything that would have made the full programme work for you today, or is the timing genuinely not right?'
THE GRACEFUL CLOSE (if both offers are declined)
'I respect that. Let me keep you on my email list so you can see the results others are getting with [mechanism name]. When the timing is right, you will know exactly where to start.'
// Book any future follow-up that was agreed to during the call.
Channel 4 — Email Nurture Sequence (Day 14 — Subscriber Conversion)
This email is for long-term warm subscribers who have never purchased. The goal is the first conversion at any price — because a subscriber who has made any purchase, even at $47, is statistically far more likely to ascend the value ladder than one who has never purchased.
SUBSCRIBER CONVERSION DOWNSELL EMAIL TEMPLATE
SUBJECT LINE
// Personal, non-promotional tone. No ALL CAPS, no exclamation marks, no discount signals.
// Examples: 'One specific thing' / 'Quick question, [first name]' / 'Something I built for exactly this'
BODY
[First name],
You have been reading my content for [timeframe — if trackable] and I have appreciated having you here.
I want to share something brief — because if what I write about [topic] is relevant to you, this might be useful.
[Downsell Name] is [one sentence: what it is and who it is for. Personal tone — 'I built this for [avatar description]' not 'this product provides...'].
It costs $[Downsell Price].
Here is what is inside: [3–5 bullet points — each describing what it does for the buyer, not what it is. Format: 'Solve [sub-problem] with [component name]']
There is no deadline on this. This is not a launch or a promotion. It is simply something I built that I think is genuinely useful for [avatar description], and if that is you — here is the link.
[CTA: 'Get [Downsell Name]' — direct checkout link]
If it is not for you right now, that is fine too. I will keep sharing.
[Operator name]
// NOTE: This email does NOT mention the primary offer. It is not framed as a downsell of anything. It is a standalone offer introduction. That framing produces higher conversion than 'you didn't buy X, so here is Y.'
Channel 5 — Direct Message Script (Community or Social Outreach)
Personal outreach to a specific identified prospect. Used when the operator has visibility into who is engaging with content but has not purchased. The message must feel personal and helpful — not automated or sales-driven.
DIRECT MESSAGE DOWNSELL TEMPLATE
// CONTEXT: This message is sent to someone who has: (a) engaged meaningfully with content, (b) asked about the offer, or (c) been in conversation about the problem. This is NOT a cold message.
THE PERSONAL OPENING
'Hey [Name] — I noticed [specific observation: you commented on the post about X / you were on the webinar last week / you asked about Y in the community].'
'I wanted to reach out personally because [specific reason — something in their comment or question that makes this relevant].'
THE BRIDGE
'I don't know if you had the chance to look at [Primary Offer Name] — if not, no worries.'
'But I did want to mention something that I think might be more relevant for where you are right now based on what you shared.'
THE OFFER
'I built [Downsell Name] specifically for [their specific situation — reference their actual words if possible].'
'It is $[Price] and it [one sentence on the result it produces].'
'Happy to send you the link if you want to take a look — or if you have questions about whether it is the right fit, ask me anything.'
THE EXIT
'And if the timing is not right at all, that is completely fine — just wanted to make sure you knew about it.'
// RULE: One message only unless they respond. Follow up on a non-response once, 5 days later, with a non-sales message ('how are things going with [their problem]?'). No third follow-up.
Channel 6 — Webinar Live Q&A Payment Plan Announcement
The payment plan announcement during live webinar Q&A is the highest-converting live downsell available because it removes the final financial barrier without reducing the offer in any way. It must be delivered once, in a specific moment, with specific language.
WEBINAR Q&A PAYMENT PLAN ANNOUNCEMENT SCRIPT
// TIMING: Deploy this announcement approximately 5–7 minutes into the Q&A, after answering 2–3 substantive questions. Not at the beginning of Q&A and not as the final statement.
THE ANNOUNCEMENT
'Before I take the next question — I want to address something that I know is in the room for some people.'
'For anyone who loves what we covered today and would love access to [Primary Offer Name], but the single investment of $[price] is challenging right now — I do have a payment option available.'
'It is [X payments of $Y over Z months]. You get everything — every component, every resource, every [live element if applicable]. The total across the payments is $[total payment plan price].'
'If that is the option that works for you: the link in chat is the same link. You will see the payment plan option at checkout.'
IMMEDIATELY CONTINUE
'Okay — next question...'
// Do NOT dwell on the payment plan or repeat it. State it once, cleanly, and move forward. Dwelling signals that you are concerned about close rates. Moving forward signals confidence.
IF QUESTIONS ARISE ABOUT THE PAYMENT PLAN IN CHAT
'The payment plan is [terms]. It is the same programme. The only difference is the payment schedule.'
// Answer once in chat and return to Q&A. Do not dedicate multiple minutes to payment plan logistics during the live event.
PHASE 4
The Downsell Ascension Architecture
Ensuring every downsell buyer is on a documented path to the primary offer
The Three Ascension Trigger Types
A downsell that produces no ascension to higher tiers produces a business full of low-LTV buyers. The ascension architecture ensures that every downsell entry point has a documented, automated sequence that presents the primary offer at the correct moment — which is always after the downsell buyer has achieved their first result.
Ascension Trigger Type
When It Fires
How It Works
Expected Ascension Rate
Completion-Based Trigger
Fires when the downsell buyer completes a defined milestone — finishes the component, submits the worksheet, or reaches a specific point in the curriculum.
Course platform (Kajabi or equivalent) triggers an email sequence upon module completion. The sequence presents the primary offer as the natural next step: 'You've just solved [the sub-problem the downsell addresses]. Here is the next challenge most operators face at this stage — and it is exactly what [Primary Offer Name] is designed for.'
12–20% of downsell buyers who complete the defined milestone
Time-Based Trigger
Fires at a specific number of days post-purchase: typically Day 14 (early engagement window) and Day 45 (post-completion window).
Automated email sequence. Day 14 email: 'How are you getting on with [Downsell Name]? [Two sentences of content relevant to their progress.] Also — for anyone who is ready to go deeper, [Primary Offer Name] opens its next cohort on [date].' Day 45 email: full ascension offer with social proof from buyers who started where the downsell buyer is now.
8–15% of downsell buyers in the time-based window
Result-Based Trigger
Fires when the buyer reports achieving the downsell's promised result — through a survey, a support ticket, a community post, or a testimonial submission.
Email sequence: 'I saw that you [achieved the result]. That is genuinely excellent. The operators who achieve [the result] typically face [the next specific challenge]. That next challenge is exactly what [Primary Offer Name] is designed for. Here is what it includes and what it would look like to join the next cohort.'
20–35% of downsell buyers who have confirmed achieving the result — this is the highest-converting ascension window because the buyer has tangible proof that the method works
The Ascension Email Sequence
A minimum three-email ascension sequence is deployed for every downsell product. The sequence is triggered by the completion-based trigger (preferred) or the Day 14 time-based trigger if completion data is not available.
Email
Timing
Subject Line Theme
Content Focus
CTA
Ascension Email 1 — The Next Problem Signal
Day 14 OR on milestone completion (whichever comes first)
'What comes after [downsell result] — the next challenge most operators face'
Deliver a brief piece of content that names the next problem the buyer will encounter after solving the one the downsell addressed. Do NOT pitch the primary offer yet — just name the next problem. Create the context for the ascension.
Reply and tell me how [Downsell Name] is going
Ascension Email 2 — The Social Proof Bridge
Day 21 OR 7 days after Email 1
'[Name] went from [downsell result stage] to [primary offer result] in [timeframe]'
A complete case study of a buyer who entered through the same downsell and ascended to the primary offer. Specifically: who they were, what the downsell gave them, what the next problem was, how the primary offer addressed it, and the specific result they achieved.
Read the full story — [link to case study or sales page]
Ascension Email 3 — The Direct Offer
Day 30 OR 14 days after Email 1
'[Primary Offer Name] opens for [Downsell Buyer First Name]'
Full offer presentation. Stack slide. Guarantee. Price. Founding member pricing if the buyer is being offered an incentive for prior purchase. One specific deadline — 72 hours.
Get started with [Primary Offer Name] — [checkout link]
The Downsell Founding Member Incentive
Buyers who entered through a downsell and are being offered ascension to the primary offer may be offered a credit for their prior purchase — their downsell investment is deducted from the primary offer price. Example: a buyer who paid $297 for the downsell is offered the primary offer at $997 − $297 = $700 credit applied.
This incentive has two functions: (1) it acknowledges the prior relationship and rewards loyalty, and (2) it provides a genuine price incentive that is not available to new buyers — real exclusivity. Not all operators use this approach, but those who do report ascension rates 1.5–2× the baseline rate.
PHASE 5
The Downsell Stack Architecture
Sequencing multiple downsells without burning the relationship
The Stack vs The Sequence
A downsell stack is multiple downsell offers presented in sequence to the same non-buyer. Each subsequent offer is lower in price and lower in commitment than the prior one. The stack is the most aggressive revenue recovery approach and carries the highest risk of alienating the buyer if deployed carelessly.
The downsell sequence is the more common and generally more appropriate architecture: a single downsell offer, presented once, in the most appropriate channel for the specific objection type. A single well-targeted downsell will almost always outperform a stack of three poorly-targeted ones.
When a Stack Is Appropriate
Only in automated funnel sequences — not in live sales calls. A stack in a live call destroys the relationship by signalling that the operator is primarily interested in extracting revenue.
Only when each offer in the stack addresses a distinct, different buyer segment — not when they are three increasingly desperate attempts to sell the same buyer.
Maximum three layers for any automated stack. After three declined offers, the buyer's state has shifted from 'not ready right now' to 'genuinely not interested.' A fourth offer is harassment.
The Three-Layer Automated Downsell Stack
Layer
Offer Type
Price Target
Trigger
Copy Approach
Layer 1 — Primary Downsell
Type 01, 02, or 03 depending on the primary offer and most common objection
30–50% of primary offer price
Fires immediately on cart abandon or 24 hours after primary offer close
Substantive — explains the value of the specific downsell for the specific buyer situation. Full copy per Channel 1 or Channel 2 templates.
Layer 2 — Micro-Commitment
Type 03 (Component Unbundle) — the lowest-price, highest-standalone-value component
15–25% of primary offer price
Fires 48 hours after Layer 1 if Layer 1 was not purchased
Brief — acknowledges the prior offer was not right, presents the specific component in 2–3 sentences. No pressure, no deadline extension.
Layer 3 — Minimum Entry
A free or very low cost lead magnet or entry product that maintains the relationship without requiring a purchase commitment
Free or $7–$27
Fires 96 hours after Layer 2 if Layer 2 was not purchased
Relationship-maintenance frame — 'I understand this is not the right time. Here is something free / very low cost that I think you will find genuinely useful.' This is not a sales message — it is a relationship preservation message.
The Burn Threshold
A non-buyer who receives three offers in four days has reached the burn threshold. After Layer 3, the buyer goes onto a standard content nurture sequence — not a sales sequence. The nurture sequence continues to provide value and will re-present the primary offer at the next natural launch cycle. There is no Layer 4. The burn threshold exists to protect the relationship.
PHASE 6
The Downsell Performance Dashboard
The metrics that determine whether to iterate, optimise, or retire a downsell
The Eight Downsell Metrics
Metric
Calculation
Healthy Range
Action If Outside Range
Downsell offer rate
Number of non-buyers who see the downsell ÷ total non-buyers × 100
100% — every non-buyer should see the relevant downsell via at least one channel
If below 100%: identify which buyer type is not receiving the downsell. Check funnel architecture — is there a trigger gap?
Downsell conversion rate
Downsell purchases ÷ non-buyers who saw the downsell × 100
Type 01/02/03: 10–25%
Type 04 (Payment Plan): 25–40%
Type 05 (Wait-List): 30–45%
Below the lower bound: review the copy (is it presenting the downsell as 'lesser than' rather than 'right for this buyer'?) and the trigger accuracy (is the downsell being shown to buyers whose objection matches the downsell type?)
Revenue recovery rate
Downsell revenue ÷ lost primary revenue × 100
15–40% of lost primary offer revenue recovered
Below 15%: the downsell is not converting enough of the available non-buyer pool. Review trigger accuracy and copy. Above 40%: the downsell is performing exceptionally — consider whether the primary offer's price point needs testing.
Downsell refund rate
Downsell refunds ÷ downsell purchases × 100
Below 10% — lower than the primary offer refund rate (buyers at a lower price point with matched expectations should refund less)
Above 12%: the downsell is creating expectation mismatches. Review the promise language — is the downsell promising more than it delivers? Is the wrong buyer type being targeted by the trigger?
Ascension rate from downsell
Downsell buyers who purchase the primary offer within 90 days ÷ total downsell buyers × 100
10–20% — 1 in 10 to 1 in 5 downsell buyers should ascend to the primary offer within 90 days
Below 8%: the ascension sequence is not firing correctly, or the ascension emails are not surfacing the next problem clearly. Review the completion-based trigger and Email 1 content. Above 25%: the downsell is an exceptionally good entry point — consider featuring it as the recommended starting point.
Average order value lift
Total revenue (primary + downsell) ÷ total visitors — compared against primary-only AOV
3–10% AOV lift from the downsell architecture across all visitor traffic
Below 3%: the downsell is not reaching enough of the non-buyer population. Review deployment channel coverage. Above 10%: strong performance — scale traffic.
Time-to-ascension
Average days from downsell purchase to primary offer purchase
45–90 days — fast enough to maintain momentum, slow enough to confirm the downsell is delivering value first
Below 30 days: buyers may be ascending before the downsell has delivered value — review the ascension trigger timing. Above 120 days: the ascension sequence may not be compelling enough or the downsell result achievement rate may be low (buyers are not getting the win that creates ascension motivation).
LTV of downsell entry buyers vs direct primary buyers
Compare 12-month revenue from buyers who entered via downsell vs those who entered direct at primary price
Downsell entry LTV should reach 60–80% of direct primary buyer LTV within 12 months
Below 50%: downsell buyers are not ascending. Review the ascension architecture. Equal to or above primary buyer LTV: the downsell is functioning as a high-quality entry point — increase its promotion.
PHASE 7
Integration With the Master Operating System
How downsells connect to the other RISER Nation SOPs
The SOP Connection Map
Downsell paths do not operate in isolation. Each downsell type draws from and feeds back into other SOPs in the Master Operating System. This connection map ensures the downsell architecture benefits from the intelligence generated by other systems.
Connected SOP
Connection to Downsells
The Data Flow
Objection Bank SOP
The Objection Bank's objection type classification and Priority Score ranking determines which downsell trigger fires for which non-buyer. Every new Objection Bank entry above Priority Score 8 should trigger a review of the downsell trigger matrix.
Objection Bank → Trigger Matrix → Downsell type selection. Monthly review: do the top 3 objection types in the Objection Bank match the downsell types currently deployed?
Offer Stacking & Unbundling Strategy SOP
Type 03 (Component Unbundle) downsells require a documented IP Asset Inventory with Unbundle Score assessments. A component must score 7+ on the Unbundle Score before it becomes a downsell offer.
IP Asset Inventory Unbundle Scores → Type 03 downsell product selection. Quarterly review: are there newly-scored assets that qualify as Type 03 downsell candidates?
Product Versioning SOP
Every downsell offer is a versioned product. Any change to the downsell's components, price, or guarantee triggers a Minor version change (CAT-O for stack changes, CAT-P for price changes). The Changelog tracks all downsell product versions.
All downsell offer changes → Changelog entries. The Testimonial Version Registry tracks which testimonials are valid for which downsell version.
Price Elasticity Testing Framework SOP
Downsell prices should be tested with the same rigour as primary offer prices. The Van Westendorp survey run for the primary offer includes questions about the downsell price range. The RPV calculation applies to downsells within their specific non-buyer pool.
Van Westendorp PMC/PME for the non-buyer pool → Downsell price testing range. Quarterly: is the downsell price at the revenue-maximising point in the RPV curve for non-buyers?
Forensic Audit Loop SOP
The Refund Root Cause analysis for downsell refunds feeds back into the downsell trigger matrix — if a Type 03 component downsell is generating refunds with RC code 'not what I expected,' the component's standalone positioning needs a fix.
Downsell refund RC codes → Trigger matrix accuracy review → Downsell copy and positioning updates.
Guarantee Type Testing Protocol SOP
Downsell offers should carry their own guarantees, not simply inherit the primary offer guarantee. The Risk Score for the downsell (typically lower — smaller investment, simpler delivery) usually supports Level 2 or Level 3 guarantees even when the primary is at Level 1.
Downsell Risk Score → Downsell guarantee level selection → Guarantee Type Testing Protocol for the downsell offer specifically.
Dead Offer Resurrection Playbook SOP
When a primary offer enters the Flatline state, its highest-performing downsell becomes the candidate for continuing the revenue stream during the resurrection period. The downsell may serve as the 'minimum viable live product' while the primary is being rebuilt.
Primary offer enters Flatline → Downsell performance assessment → Decision: maintain downsell as interim primary or retire alongside the primary offer.
Downsell Records Database — Airtable Schema
Table 1 — Downsell Offer Records
One record per downsell offer product. Linked to the primary offer it serves.
Field
Type
Notes
Downsell ID
Short text
Format: DS-[Offer Code]-[Type Code]-[Seq]. e.g. DS-MVO-T03-001
Downsell Name
Short text
The product name — standalone, not a reference to the primary offer
Primary Offer
Link → Offers table
The offer this downsell serves
Downsell Type
Single select
Type 01 (Self-Paced) / Type 02 (Format Reduction) / Type 03 (Component) / Type 04 (Payment Plan) / Type 05 (Wait-List)
Objection Type Targeted
Single select
Price & Value / Timing / Fit & Relevance / Implementation Fear / Trust / Comparison
Current Price
Currency
Primary Offer Price Ratio
Formula
Downsell Price ÷ Primary Offer Price × 100. Target: 20–50%
Payment Plan Terms (if Type 04)
Short text
e.g. '3 × $367 over 60 days'
Sub-Problem Solved
Short text
One sentence: 'The buyer is struggling with ___. This solves that by ___.
What Is Excluded (and why it is a feature)
Long text
What the primary offer includes that this does not, and the one-sentence framing of why the exclusion is appropriate for this buyer
Result Promised
Short text
The specific, measurable result the downsell buyer should expect
Result Timeframe
Short text
e.g. '30 days'
Guarantee Level
Single select
None / Level 1 / Level 2 / Level 3
Guarantee Copy
Long text
Verbatim from Guarantee Type Testing Protocol SOP
Ascension Trigger Type
Multi-select
Completion-Based / Day 14 Time-Based / Day 45 Time-Based / Result-Based
Ascension Sequence Active
Checkbox
Is the 3-email ascension sequence live and triggering?
Downsell Offer Rate
Number
% of non-buyers seeing this downsell (rolling 30 days)
Downsell Conversion Rate
Number
% of non-buyers who see it and purchase (rolling 30 days)
Downsell Revenue (rolling 30 days)
Currency
Downsell Refund Rate
Number
% rolling 30 days
Ascension Rate (90-day)
Number
% of downsell buyers who purchase the primary offer within 90 days
Status
Single select
Active / Under Test / Archived
Version
Short text
From Product Versioning SOP Changelog — current version identifier
Changelog Entry
Link → Changelog Entries
Latest CAT entry for this downsell product
Linked Testimonials
Link → Testimonial Version Registry
Testimonials from downsell buyers — for use in ascension emails and downsell copy
Notes
Long text
Observations, test results, copy variants, deployment notes
Master Downsell Paths Checklist
System Setup (One-Time)
☐
Identify all active primary offers and map each to the most likely objection type that produces non-buyers (from the Objection Bank, sorted by Priority Score)
☐
Using the Trigger Matrix, identify which downsell type is most appropriate for each primary offer's most common objection
☐
Complete the Downsell Design Brief for each planned downsell offer before any build begins
☐
Run the Sub-Problem Test (from Bonus Discipline Audit SOP) on every planned downsell — if it cannot be described as solving a specific named sub-problem, redesign it
☐
Create Downsell Offer Records table in Airtable with all fields
☐
Map each downsell to its deployment channels — which of the six channels will this downsell use?
Downsell Build (Per Offer)
☐
Downsell offer name chosen as a standalone product name — not '[Primary Offer] Lite' or '[Primary Offer] Basic'
☐
Price confirmed at 20–50% of primary offer price
☐
What is excluded documented with the 'feature not limitation' framing
☐
Result promised is specific and measurable — not 'you will learn how to...' but 'you will have [specific thing] within [timeframe]'
☐
Guarantee level assigned using the Guarantee Type Testing Protocol SOP Risk Score for the downsell specifically
☐
All copy templates completed for every planned deployment channel
☐
Checkout decline page or popup built and tested
☐
Post-webinar email sequence updated to include the downsell email at Day 2 of the post-close sequence
☐
Downsell offer record created in Airtable
Ascension Architecture
☐
Completion-based ascension trigger configured in the course platform
☐
All three ascension emails written — Email 1 (Next Problem Signal), Email 2 (Social Proof Bridge), Email 3 (Direct Offer)
☐
Ascension sequence tested: does it fire correctly on the completion trigger?
☐
Downsell Founding Member incentive decision documented — will prior purchase be credited? At what amount?
☐
Day 14 time-based backup trigger active for buyers who have not triggered the completion trigger
Ongoing Operations (Monthly)
☐
Pull all eight downsell metrics from Airtable and review against the healthy ranges
☐
Review the Objection Bank: have any new objection types emerged that do not have a matching downsell path?
☐
Check the ascension rate: are downsell buyers ascending at above 8%? If not — review the ascension Email 1 content
☐
Review the downsell refund rate: is it below 10%? If above 12% — run the Refund Root Cause analysis from the Forensic Audit Loop SOP
☐
Confirm all ascension triggers are firing correctly — pull the trigger event log from the course platform
☐
Update Downsell Offer Record in Airtable with current month's performance data
Quarterly Review
☐
Price test: run the Van Westendorp survey on the non-buyer pool for the primary offer — does the current downsell price sit within the Acceptable Price Range for this audience?
☐
Trigger accuracy review: are the right downsell types being shown to the right objection types? Pull objection data from the Sales Call Records and compare to which downsell channel each non-buyer entered
☐
Ascension sequence review: pull the 12 most recent ascension email open rates and conversion rates — are they performing at or above the expected ranges?
☐
Connected SOP review: have any changes in the Objection Bank, IP Asset Inventory, or Product Versioning Changelog affected the downsell architecture in a way that requires an update?
RISER Nation Master Operating System | Downsell Paths SOP | Version 1.0 | 2026 Edition
Kennedy × Hormozi × Brunson × Cialdini | risernation.com

word/header1.xml
RISER Nation | Downsell Paths SOP | V1.0

word/footer1.xml
Page
of

word/footnotes.xml

word/endnotes.xml

word/comments.xml

Audit evidence and decision-instrument sales letters

Study the internal audit records as evidence-review exercises, then evaluate the product promises against what their original documents actually supply.

QM-Audit-C9-Scorecard.xlsx

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

Working lesson text. Some source claims and supporting assets remain unverified.

Inspect all four workbook sheets

The workbook contains Summary, Standards, Comparison and Recommendation, with 46, 221, 41 and 2 populated cells respectively. The native extraction records no images or charts. Summary and Comparison repeat historical results; Standards contains the detailed evidence. Read the Recommendation as proposed action, not an executed workflow.

QM-Audit-C9-Scorecard.xlsx — assigned original

Trace formulas and distinguish blank flags

Standards C43 sums C3:C42 and D43 sums D3:D42. Their cached values, 95 and 94, match independent addition of the detailed numeric cells. Summary B11 and B12 remain hardcoded 92 and 94, so the headline is not linked to those totals. Blank essential cells are not affirmative flags. Only eleven Yes entries exist; do not fill blanks to force the summary's sixteen.

QM-Audit-C9-Scorecard.xlsx — assigned original

Preserve native cells and their meaning

The appendix retains all populated cell addresses, values, formulas, cached values and available cell metadata. A cached result is not proof of live recalculation. The independent arithmetic check supports these two simple SUM totals only. No source workbook cell was edited to conceal a conflict.

QM-Audit-C9-Scorecard.xlsx — assigned original

Keep the audit identity and current assignment separate

The source concerns legacy C9, Bora Bora Captain's Retreat — Strategic Renewal, Stage 2 Sailboat, course four of five and the first quarterly integrative review. It names an internal RISER auditor, April 26, 2026 and a local C9 build path. These identify the historical audit scope. They do not renumber the current spreadsheet lessons or establish a reviewed live GHL version.

QM-Audit-C9-Scorecard.xlsx — assigned original

Read the summary as a claim to reconcile

The summary records 92 points of 94, 97.9%, an 80-point threshold labeled 85%, and 15 of 16 essential standards conforming. It records a score pass but NOT_CERTIFIED because SRS_8.3 is disputed. Preserve every field while verifying the detail. Eighty divided by ninety-four is approximately 85.11%; the source percentage is a rounded threshold label.

QM-Audit-C9-Scorecard.xlsx — assigned original

Recompute all rows before relying on the score

The supplied detailed records contain 40 standards, with 95 possible and 94 awarded points. They flag 11 as essential, of which 10 have Conforms status. These disagree with the summary. The detailed ratio is approximately 98.95%, but this is only arithmetic over the supplied rows. It is not a corrected official certification score.

QM-Audit-C9-Scorecard.xlsx — assigned original

Reconcile rubric identity and missing standards

The linked official QM overview identifies 44 specific standards and treats three-point standards as essential. The source's 40-row array and essential flags therefore need a full remapping. Unflagged three-point rows cannot simply be ignored. Preserve the original record and document a separate corrected mapping before any formal assessment.

Correct the disputed standard reference

The official public list identifies 8.3 with text accessibility, 8.4 with images, 8.5 with video/audio, 8.6 with multimedia usability and 8.7 with vendor accessibility statements. Instructor introduction appears at 1.8. The source uses different meanings and omits identifiers. Its multimedia dispute cannot be accepted as an accurate statement of the cited rubric. Version 2.0 does not change the underlying standards, according to QM.

Distinguish design specifications from delivered accessibility

The source says M9.1 has caption and transcript requirements, while M9.2–M9.8 are paper/template driven. Inspect the media actually present and its accessible alternatives. A requirement in a specification is not a checked caption, transcript or usable document. The source's strict and design-intent interpretations are disputed internal claims, not an official ruling reproduced here.

QM-Audit-C9-Scorecard.xlsx — assigned original

Evaluate both proposed remediation paths

Path one proposes video specifications for seven modules and estimates 14–21 hours. Path two proposes a clarification request, estimates 2–4 hours and is recommended by the internal source. These are historical estimates and proposed outcomes. Neither task has been performed by this lesson. Given the incorrect standard mapping, first establish the applicable requirement; neither creating specifications nor requesting clarification automatically confers certification.

QM-Audit-C9-Scorecard.xlsx — assigned original

Preserve design intent without inventing a resolution

The recommendation favors clarification because Stillwater uses non-screen activity and Open Ocean uses paper-only sessions. It asserts that video would corrupt the design and that deployment under NOT_CERTIFIED is permissible by precedent. Those assertions require review of the actual design and governing process. Preserve the paper-based learning purpose, but do not claim that an external body has approved the exception or deployment.

QM-Audit-C9-Scorecard.xlsx — assigned original

Use every evidence row as a review task

The following table retains all 40 internal row identifiers, scores, essential flags, statuses and evidence references, with an authored inspection task for each. Its identifiers describe the supplied file and are not a verified official rubric crosswalk. A local filename names a dependency; it is not proof that the linked source contains that file or that its implementation was inspected.

QM-Audit-C9-Scorecard.xlsx — assigned original

Read all nine comparison records cautiously

The comparison reports C1, C3, C5 and C7 at 94/94 and 100%; C2, C6 and C8 at 93/94 and 98.9%; C4 at 92/94 and 97.9%, all labeled Certified. C9 is 92/94 and 97.9%, labeled NOT_CERTIFIED. These are source-recorded prior statuses, not independently verified certifications. A similar score cannot establish equivalent conformance, and inconsistent totals in this audit undermine unqualified comparisons.

QM-Audit-C9-Scorecard.xlsx — assigned original

Apply the marketing frameworks to evidence quality

As an authored RISER application of Brunson/ClickFunnels, connect the hook, explanatory story and offer to evidence the learner can inspect. As an application of Hormozi/Acquisition.com value thinking, improve confidence through verifiable delivery and reduce unnecessary delay and effort. Neither framework turns an internal audit into third-party certification or repairs incorrect arithmetic.

Submit a reconciled review packet

Submit the unchanged source, row-level calculations, an explicit list of discrepancies, the applicable official references, missing evidence dependencies and a proposed remediation owner and next review step. Keep internal assessment, delivered accessibility tests and any formal certification decision separate. Do not submit a clarification request, deploy software or award a pass merely because the source recommends doing so.

QM-Audit-C9-Scorecard.xlsx — assigned original

Inspect each internal audit record

Source ID	Essential flag	Awarded / maximum	Status and claimed evidence	Review exercise	Source
1.1	Yes	3 / 3	Conforms: 00_Course-Overview/README.md § Getting Started; M9.1 § First steps	Follow the getting-started instructions as a new learner and record whether the first required action can be located.	QM-Audit-C9-Scorecard.xlsx — evidence record 1.1
1.2	Yes	3 / 3	Conforms: Syllabus § Course architecture (8-module flow with HITL gate)	Trace the eight-module flow and identify where the human review gate occurs. A diagram must agree with the actual lesson order.	QM-Audit-C9-Scorecard.xlsx — evidence record 1.2
1.3	Blank in workbook	2 / 2	Conforms: Peer-Review-Protocol.md § Peer review etiquette	Locate the peer-review etiquette and check whether a learner can understand how to communicate appropriately.	QM-Audit-C9-Scorecard.xlsx — evidence record 1.3
1.4	Blank in workbook	2 / 2	Conforms: Syllabus § Policies (cohort, attestation chain, late-retreat policy)	Read the cohort, attestation-chain and late-retreat policies together. Identify conflicting deadlines or prerequisites.	QM-Audit-C9-Scorecard.xlsx — evidence record 1.4
1.5	Blank in workbook	2 / 2	Conforms: Syllabus § Technology requirements	Compare the stated technology requirements with the tools actually needed for the exercises.	QM-Audit-C9-Scorecard.xlsx — evidence record 1.5
1.6	Blank in workbook	1 / 1	Conforms: Syllabus § Prerequisites (C8 attestation, 88+ days operating)	Inspect the C8 attestation and the source requirement of at least 88 operating days. Preserve the legacy prerequisite and verify actual records rather than asserting a learner qualifies.	QM-Audit-C9-Scorecard.xlsx — evidence record 1.6
1.7	Blank in workbook	1 / 1	Conforms: M9.1-Video-Production-Spec.md (instructor-presence video specification)	Inspect the instructor-presence specification, then separately check the delivered introduction. A production specification does not prove a video has been recorded.	QM-Audit-C9-Scorecard.xlsx — evidence record 1.7
1.8	Blank in workbook	1 / 1	Conforms: Syllabus § Cohort onboarding (peer triad introduction at M9.1)	Check how the peer triad introduces its members at M9.1. A proposed onboarding activity needs clear participation instructions.	QM-Audit-C9-Scorecard.xlsx — evidence record 1.8
2.1	Yes	3 / 3	Conforms: Learning-Outcomes.md § Course-level outcomes (5 measurable outcomes)	Inspect each of the five course outcomes for an observable learner result and a way to assess it.	QM-Audit-C9-Scorecard.xlsx — evidence record 2.1
2.2	Yes	3 / 3	Conforms: Each M9.X-*.md opens with module objectives; consolidated in Learning-Outcomes.md	Compare each module objective with the consolidated outcomes. Identify objectives that lack a matching task or assessment.	QM-Audit-C9-Scorecard.xlsx — evidence record 2.2
2.3	Blank in workbook	3 / 3	Conforms: Learning-Outcomes.md uses Operator will... stem; module objectives use action verbs	Check that action verbs specify observable work. The phrase Operator will does not by itself make an outcome measurable.	QM-Audit-C9-Scorecard.xlsx — evidence record 2.3
2.4	Blank in workbook	3 / 3	Conforms: Stage 2 prerequisites confirmed; Doctrines.md links objectives to stage-appropriate doctrines	Inspect the stage prerequisites and the cited doctrines. Explain why the required task is suitable for that learner stage.	QM-Audit-C9-Scorecard.xlsx — evidence record 2.4
2.5	Blank in workbook	3 / 3	Conforms: Each module: objectives -> activities -> submission -> rubric criterion; cross-referenced in Summative-Attestation-Rubric.md	Trace objectives to activities, submissions and rubric criteria. Missing relationships require clarification, not a guessed mapping.	QM-Audit-C9-Scorecard.xlsx — evidence record 2.5
3.1	Yes	3 / 3	Conforms: Summative-Attestation-Rubric.md (8 criteria each map to a course outcome)	Map all eight summative criteria to course outcomes and inspect what evidence each criterion expects.	QM-Audit-C9-Scorecard.xlsx — evidence record 3.1
3.2	Blank in workbook	3 / 3	Conforms: Summative-Attestation-Rubric.md § Scoring summary + § Pass condition	Read the scoring summary and pass condition together. Recalculate a sample submission and identify any contradictory passing rule.	QM-Audit-C9-Scorecard.xlsx — evidence record 3.2
3.3	Blank in workbook	3 / 3	Conforms: Rubric uses 4-level descriptors (Exceeds/Meets/Approaches/Below) per criterion	Compare Exceeds, Meets, Approaches and Below descriptions. A learner should be able to tell what evidence distinguishes the levels.	QM-Audit-C9-Scorecard.xlsx — evidence record 3.3
3.4	Blank in workbook	2 / 2	Conforms: 8 module submissions + HITL gate + course-completion gate; per-module remediation pathways	Trace the eight submissions, human gate, completion gate and remediation paths. Confirm what happens after an incomplete submission.	QM-Audit-C9-Scorecard.xlsx — evidence record 3.4
3.5	Blank in workbook	2 / 2	Conforms: All assessments are operator's actual quarterly work; no simulated assessments	Inspect the quarterly work used in each assessment. Authenticity of a proposed task does not prove an actual operator completed it.	QM-Audit-C9-Scorecard.xlsx — evidence record 3.5
4.1	Yes	3 / 3	Conforms: Each module lesson references its objective(s); Resources cross-referenced from lessons	Follow each lesson-to-objective and resource reference. A resource must support the task rather than merely appear on a list.	QM-Audit-C9-Scorecard.xlsx — evidence record 4.1
4.2	Blank in workbook	3 / 3	Conforms: Doctrines.md cites Moran/Lennington 2013, Newport 2016, Scott 2017, Meadows 2008, etc.	Inspect the actual passages attributed to Moran/Lennington 2013, Newport 2016, Scott 2017 and Meadows 2008. A citation list alone does not establish currency or accurate application.	QM-Audit-C9-Scorecard.xlsx — evidence record 4.2
4.3	Blank in workbook	2 / 2	Conforms: Markdown lessons + video (M9.1) + templates + case studies + community prompts + system prompts (5+ formats)	Inventory the markdown lessons, M9.1 video, templates, case studies, community prompts and system prompts. Verify which are delivered rather than counting plans as completed formats.	QM-Audit-C9-Scorecard.xlsx — evidence record 4.3
4.4	Blank in workbook	2 / 2	Conforms: Syllabus § Materials marks required vs optional; peer review explicitly optional	Distinguish required from optional materials and preserve the source statement that peer review is optional.	QM-Audit-C9-Scorecard.xlsx — evidence record 4.4
4.5	Blank in workbook	2 / 2	Conforms: README.md § Licensing (RISER Nation Maritime Academy proprietary; reuse provisions)	Read the proprietary and reuse terms in the named README. Verify permissions for each included item instead of treating a licensing sentence as ownership evidence.	QM-Audit-C9-Scorecard.xlsx — evidence record 4.5
5.1	Yes	3 / 3	Conforms: Each module's activities directly produce artifacts satisfying outcomes	Show how each learning activity produces an artifact used to demonstrate an outcome.	QM-Audit-C9-Scorecard.xlsx — evidence record 5.1
5.2	Blank in workbook	3 / 3	Conforms: Peer review triads at three exchange points; HITL reviewer interaction; Quarterly Review Validator dialogic interaction	Identify all three peer exchanges, the human reviewer interaction and the Quarterly Review Validator dialogue. Verify the instructions and available service for each.	QM-Audit-C9-Scorecard.xlsx — evidence record 5.2
5.3	Blank in workbook	2 / 2	Conforms: Instructor-HITL-Gate-M9.6.md § Reviewer workflow (24h standard / 48h extended)	Inspect the stated 24-hour standard and 48-hour extended reviewer workflow. Record these as source service targets until actual staffing and service arrangements are established.	QM-Audit-C9-Scorecard.xlsx — evidence record 5.3
5.4	Blank in workbook	2 / 2	Conforms: Peer-Review-Protocol.md and Syllabus § Cohort interaction specify required vs optional	Compare the peer-review protocol with cohort instructions so required and optional interactions do not contradict each other.	QM-Audit-C9-Scorecard.xlsx — evidence record 5.4
6.1	Yes	3 / 3	Conforms: integration-spec.md - LMS, validator service, Captain's Console, Supabase tables map to objectives	Trace the proposed LMS, validator, Captain's Console and Supabase tables to the relevant objectives. Specifications are not evidence of a deployed integration.	QM-Audit-C9-Scorecard.xlsx — evidence record 6.1
6.2	Blank in workbook	2 / 2	Conforms: LMS peer-review module; HITL packet workflow; AI validator dialog interfaces	Inspect how the peer-review module, human-review packet and validator dialogue support actual participation.	QM-Audit-C9-Scorecard.xlsx — evidence record 6.2
6.3	Blank in workbook	2 / 2	Conforms: Validators on Sonnet/Opus 4.7; Supabase backend; modern LMS layer	Treat Sonnet/Opus 4.7, Supabase and the LMS layer as source configuration claims. Verify availability and suitability before implementation.	QM-Audit-C9-Scorecard.xlsx — evidence record 6.3
6.4	Blank in workbook	2 / 2	Conforms: RLS policies in c9-supabase-schema.sql; peer-review confidentiality stated	Inspect the named row-level-security policies and peer confidentiality provisions. Their presence in a specification does not prove effective access control in a running system.	QM-Audit-C9-Scorecard.xlsx — evidence record 6.4
7.1	Yes	3 / 3	Conforms: Syllabus § Support; README § Help and escalation	Follow the support and escalation instructions. Check that each contact or help route is usable.	QM-Audit-C9-Scorecard.xlsx — evidence record 7.1
7.2	Blank in workbook	2 / 2	Conforms: Syllabus links to Reviewer Office Hours, peer cohort channels, recalibration paths	Inspect the Reviewer Office Hours, peer channels and recalibration routes. Note missing destinations or service details.	QM-Audit-C9-Scorecard.xlsx — evidence record 7.2
7.3	Blank in workbook	2 / 2	Conforms: Syllabus references operator-care resources; burnout escalation protocol	Inspect the operator-care resources and burnout escalation protocol. Course support should identify an appropriate route without diagnosing the learner.	QM-Audit-C9-Scorecard.xlsx — evidence record 7.3
7.4	Blank in workbook	2 / 2	Conforms: Syllabus § Accessibility (paper-only M9.4 alternatives; retreat-window flexibility)	Compare the paper-only M9.4 alternative and retreat-window flexibility with the intended task. A flexible pathway still needs usable instructions and appropriate assessment.	QM-Audit-C9-Scorecard.xlsx — evidence record 7.4
8.1	Yes	3 / 3	Conforms: LMS WCAG 2.1 AA compliance; markdown screen-reader compatible	Treat the asserted WCAG 2.1 AA compliance and screen-reader compatibility as claims requiring testing of the actual rendered course. Markdown alone does not establish either.	QM-Audit-C9-Scorecard.xlsx — evidence record 8.1
8.2	Blank in workbook	2 / 2	Conforms: Consistent heading hierarchy; plain-language doctrine framing	Inspect heading order and plain-language explanations in the rendered lesson, including expanded appendices.	QM-Audit-C9-Scorecard.xlsx — evidence record 8.2
8.3	Yes	2 / 3	Conditional: M9.1-Video-Production-Spec.md includes captions and transcript requirements. Note: M9.2-M9.8 video specs not produced (paper/template-driven). Strict interpretation flags non-conformance; design-intent interpretation supports conformance. Audit records midpoint awarded score (2/3) reflecting documented dispute. Resolution path: file QM rubric clarification request OR produce companion video specs for M9.2-M9.8.	Preserve the recorded 2/3 conditional score, missing M9.2–M9.8 specifications and both proposed interpretations. Reconcile the incorrect rubric identifier before deciding what remediation is appropriate.	QM-Audit-C9-Scorecard.xlsx — evidence record 8.3
8.4	Blank in workbook	2 / 2	Conforms: Each module follows consistent structure (objectives -> lesson -> activities -> submission -> checklist)	Follow the proposed objectives, lesson, activities, submission and checklist sequence. Consistent structure helps use but does not settle the mislabeled official standard.	QM-Audit-C9-Scorecard.xlsx — evidence record 8.4
8.5	Blank in workbook	2 / 2	Conforms: Markdown renders desktop and mobile; LMS responsive	Check actual desktop and mobile rendering, keyboard access and overflow. A statement that the LMS is responsive is not a completed usability test.	QM-Audit-C9-Scorecard.xlsx — evidence record 8.5

Complete original source text

,RISER Nation Maritime Academy — QM Audit Scorecard,Unnamed: 1,Unnamed: 2,Unnamed: 3
0,C9 Bora Bora Captain's Retreat — Strategic Renewal,,,
1,,,,
2,Course code,C9,,
3,Stage,2 (Sailboat),,
4,Catalog position,Course 4 of 5 in Stage 2; first quarterly integrative review course in catalog,,
5,Rubric,QM HE 7th Edition v2.0,,
6,Audit date,2026-04-26,,
7,Auditor,RISER Internal QM Audit Tool,,
8,,,,
9,Total points awarded,92,,
10,Total points possible,94,,
11,Percentage,97.9%,,
12,Pass threshold (85%),80 points,,
13,Score passes threshold?,YES,,
14,Essential standards conforming,15 / 16,,
15,All Essentials conform?,NO,,
16,Disputed Essentials,SRS_8.3,,
17,,,,
18,CERTIFICATION STATUS,NOT_CERTIFIED,,
19,,,,
20,Certification block reason:,,,
21,SRS 8.3 Essential standard recorded as conditional non-conformance under strict interpretation of multimedia accessibility requirement; M9.2-M9.8 video specifications not produced for paper/template-driven modules.,,,
22,,,,
23,Remediation paths:,,,
24,Path,Description,Effort (hrs),Recommended
25,1,Produce video specifications for M9.2-M9.8,14-21,
26,2,File QM rubric clarification request documenting design-intent that SRS 8.3 applies only to multimedia present,2-4,YES
,Per-Standard Audit Detail (42 SRS),Unnamed: 1,Unnamed: 2,Unnamed: 3,Unnamed: 4,Unnamed: 5
0,SRS,Essential,Max Points,Awarded,Status,Evidence
1,1.1,Yes,3,3,Conforms,00_Course-Overview/README.md § Getting Started; M9.1 § First steps
2,1.2,Yes,3,3,Conforms,Syllabus § Course architecture (8-module flow with HITL gate)
3,1.3,,2,2,Conforms,Peer-Review-Protocol.md § Peer review etiquette
4,1.4,,2,2,Conforms,"Syllabus § Policies (cohort, attestation chain, late-retreat policy)"
5,1.5,,2,2,Conforms,Syllabus § Technology requirements
6,1.6,,1,1,Conforms,"Syllabus § Prerequisites (C8 attestation, 88+ days operating)"
7,1.7,,1,1,Conforms,M9.1-Video-Production-Spec.md (instructor-presence video specification)
8,1.8,,1,1,Conforms,Syllabus § Cohort onboarding (peer triad introduction at M9.1)
9,2.1,Yes,3,3,Conforms,Learning-Outcomes.md § Course-level outcomes (5 measurable outcomes)
10,2.2,Yes,3,3,Conforms,Each M9.X-*.md opens with module objectives; consolidated in Learning-Outcomes.md
11,2.3,,3,3,Conforms,Learning-Outcomes.md uses Operator will... stem; module objectives use action verbs
12,2.4,,3,3,Conforms,Stage 2 prerequisites confirmed; Doctrines.md links objectives to stage-appropriate doctrines
13,2.5,,3,3,Conforms,Each module: objectives -> activities -> submission -> rubric criterion; cross-referenced in Summative-Attestation-Rubric.md
14,3.1,Yes,3,3,Conforms,Summative-Attestation-Rubric.md (8 criteria each map to a course outcome)
15,3.2,,3,3,Conforms,Summative-Attestation-Rubric.md § Scoring summary + § Pass condition
16,3.3,,3,3,Conforms,Rubric uses 4-level descriptors (Exceeds/Meets/Approaches/Below) per criterion
17,3.4,,2,2,Conforms,8 module submissions + HITL gate + course-completion gate; per-module remediation pathways
18,3.5,,2,2,Conforms,All assessments are operator's actual quarterly work; no simulated assessments
19,4.1,Yes,3,3,Conforms,Each module lesson references its objective(s); Resources cross-referenced from lessons
20,4.2,,3,3,Conforms,"Doctrines.md cites Moran/Lennington 2013, Newport 2016, Scott 2017, Meadows 2008, etc."
21,4.3,,2,2,Conforms,Markdown lessons + video (M9.1) + templates + case studies + community prompts + system prompts (5+ formats)
22,4.4,,2,2,Conforms,Syllabus § Materials marks required vs optional; peer review explicitly optional
23,4.5,,2,2,Conforms,README.md § Licensing (RISER Nation Maritime Academy proprietary; reuse provisions)
24,5.1,Yes,3,3,Conforms,Each module's activities directly produce artifacts satisfying outcomes
25,5.2,,3,3,Conforms,Peer review triads at three exchange points; HITL reviewer interaction; Quarterly Review Validator dialogic interaction
26,5.3,,2,2,Conforms,Instructor-HITL-Gate-M9.6.md § Reviewer workflow (24h standard / 48h extended)
27,5.4,,2,2,Conforms,Peer-Review-Protocol.md and Syllabus § Cohort interaction specify required vs optional
28,6.1,Yes,3,3,Conforms,"integration-spec.md - LMS, validator service, Captain's Console, Supabase tables map to objectives"
29,6.2,,2,2,Conforms,LMS peer-review module; HITL packet workflow; AI validator dialog interfaces
30,6.3,,2,2,Conforms,Validators on Sonnet/Opus 4.7; Supabase backend; modern LMS layer
31,6.4,,2,2,Conforms,RLS policies in c9-supabase-schema.sql; peer-review confidentiality stated
32,7.1,Yes,3,3,Conforms,Syllabus § Support; README § Help and escalation
33,7.2,,2,2,Conforms,"Syllabus links to Reviewer Office Hours, peer cohort channels, recalibration paths"
34,7.3,,2,2,Conforms,Syllabus references operator-care resources; burnout escalation protocol
35,7.4,,2,2,Conforms,Syllabus § Accessibility (paper-only M9.4 alternatives; retreat-window flexibility)
36,8.1,Yes,3,3,Conforms,LMS WCAG 2.1 AA compliance; markdown screen-reader compatible
37,8.2,,2,2,Conforms,Consistent heading hierarchy; plain-language doctrine framing
38,8.3,Yes,3,2,Conditional,M9.1-Video-Production-Spec.md includes captions and transcript requirements. Note: M9.2-M9.8 video specs not produced (paper/template-driven). Strict interpretation flags non-conformance; design-intent interpretation supports conformance. Audit records midpoint awarded score (2/3) reflecting documented dispute. Resolution path: file QM rubric clarification request OR produce companion video specs for M9.2-M9.8.
39,8.4,,2,2,Conforms,Each module follows consistent structure (objectives -> lesson -> activities -> submission -> checklist)
40,8.5,,2,2,Conforms,Markdown renders desktop and mobile; LMS responsive
41,TOTAL,,95,94,,
,Catalog Audit Comparison,Unnamed: 1,Unnamed: 2,Unnamed: 3
0,Course,Score,Percentage,Status
1,C1,94/94,100.0%,Certified
2,C2,93/94,98.9%,Certified
3,C3,94/94,100.0%,Certified
4,C4,92/94,97.9%,Certified
5,C5,94/94,100.0%,Certified
6,C6,93/94,98.9%,Certified
7,C7,94/94,100.0%,Certified
8,C8,93/94,98.9%,Certified
9,C9,92/94,97.9%,NOT_CERTIFIED
,Reviewer Recommendation
0,
1,File QM rubric clarification request (path 2) before C9 deployment. M9.2-M9.8 are deliberately paper/template-driven for pedagogical reasons (Stillwater non-screen activity; Open Ocean paper-only sessions). Adding video would corrupt design intent. C9 may deploy under NOT_CERTIFIED status during clarification window per prior precedent.

Complete native cell values, formulas and metadata

{"sheet": "Summary", "state": "visible", "cells": [{"cell": "A1", "value": "RISER Nation Maritime Academy — QM Audit Scorecard", "cached": "RISER Nation Maritime Academy — QM Audit Scorecard", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A2", "value": "C9 Bora Bora Captain's Retreat — Strategic Renewal", "cached": "C9 Bora Bora Captain's Retreat — Strategic Renewal", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A4", "value": "Course code", "cached": "Course code", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B4", "value": "C9", "cached": "C9", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A5", "value": "Stage", "cached": "Stage", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B5", "value": "2 (Sailboat)", "cached": "2 (Sailboat)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A6", "value": "Catalog position", "cached": "Catalog position", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B6", "value": "Course 4 of 5 in Stage 2; first quarterly integrative review course in catalog", "cached": "Course 4 of 5 in Stage 2; first quarterly integrative review course in catalog", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A7", "value": "Rubric", "cached": "Rubric", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B7", "value": "QM HE 7th Edition v2.0", "cached": "QM HE 7th Edition v2.0", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A8", "value": "Audit date", "cached": "Audit date", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B8", "value": "2026-04-26", "cached": "2026-04-26", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A9", "value": "Auditor", "cached": "Auditor", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B9", "value": "RISER Internal QM Audit Tool", "cached": "RISER Internal QM Audit Tool", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A11", "value": "Total points awarded", "cached": "Total points awarded", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B11", "value": 92, "cached": 92, "format": "General", "comment": null, "hyperlink": null}, {"cell": "A12", "value": "Total points possible", "cached": "Total points possible", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B12", "value": 94, "cached": 94, "format": "General", "comment": null, "hyperlink": null}, {"cell": "A13", "value": "Percentage", "cached": "Percentage", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B13", "value": "97.9%", "cached": "97.9%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A14", "value": "Pass threshold (85%)", "cached": "Pass threshold (85%)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B14", "value": "80 points", "cached": "80 points", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A15", "value": "Score passes threshold?", "cached": "Score passes threshold?", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B15", "value": "YES", "cached": "YES", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A16", "value": "Essential standards conforming", "cached": "Essential standards conforming", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B16", "value": "15 / 16", "cached": "15 / 16", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A17", "value": "All Essentials conform?", "cached": "All Essentials conform?", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B17", "value": "NO", "cached": "NO", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A18", "value": "Disputed Essentials", "cached": "Disputed Essentials", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B18", "value": "SRS_8.3", "cached": "SRS_8.3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A20", "value": "CERTIFICATION STATUS", "cached": "CERTIFICATION STATUS", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B20", "value": "NOT_CERTIFIED", "cached": "NOT_CERTIFIED", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A22", "value": "Certification block reason:", "cached": "Certification block reason:", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A23", "value": "SRS 8.3 Essential standard recorded as conditional non-conformance under strict interpretation of multimedia accessibility requirement; M9.2-M9.8 video specifications not produced for paper/template-driven modules.", "cached": "SRS 8.3 Essential standard recorded as conditional non-conformance under strict interpretation of multimedia accessibility requirement; M9.2-M9.8 video specifications not produced for paper/template-driven modules.", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A25", "value": "Remediation paths:", "cached": "Remediation paths:", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A26", "value": "Path", "cached": "Path", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B26", "value": "Description", "cached": "Description", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C26", "value": "Effort (hrs)", "cached": "Effort (hrs)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D26", "value": "Recommended", "cached": "Recommended", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A27", "value": 1, "cached": 1, "format": "General", "comment": null, "hyperlink": null}, {"cell": "B27", "value": "Produce video specifications for M9.2-M9.8", "cached": "Produce video specifications for M9.2-M9.8", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C27", "value": "14-21", "cached": "14-21", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A28", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "B28", "value": "File QM rubric clarification request documenting design-intent that SRS 8.3 applies only to multimedia present", "cached": "File QM rubric clarification request documenting design-intent that SRS 8.3 applies only to multimedia present", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C28", "value": "2-4", "cached": "2-4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D28", "value": "YES", "cached": "YES", "format": "General", "comment": null, "hyperlink": null}], "merged": ["A1:D1", "A23:D23", "A2:D2"], "images": 0, "charts": 0, "tables": [], "conditional_formats": 0}
{"sheet": "Standards", "state": "visible", "cells": [{"cell": "A1", "value": "Per-Standard Audit Detail (42 SRS)", "cached": "Per-Standard Audit Detail (42 SRS)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A2", "value": "SRS", "cached": "SRS", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B2", "value": "Essential", "cached": "Essential", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C2", "value": "Max Points", "cached": "Max Points", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D2", "value": "Awarded", "cached": "Awarded", "format": "General", "comment": null, "hyperlink": null}, {"cell": "E2", "value": "Status", "cached": "Status", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F2", "value": "Evidence", "cached": "Evidence", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A3", "value": "1.1", "cached": "1.1", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B3", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C3", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D3", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E3", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F3", "value": "00_Course-Overview/README.md § Getting Started; M9.1 § First steps", "cached": "00_Course-Overview/README.md § Getting Started; M9.1 § First steps", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A4", "value": "1.2", "cached": "1.2", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B4", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C4", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D4", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E4", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F4", "value": "Syllabus § Course architecture (8-module flow with HITL gate)", "cached": "Syllabus § Course architecture (8-module flow with HITL gate)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A5", "value": "1.3", "cached": "1.3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C5", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D5", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E5", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F5", "value": "Peer-Review-Protocol.md § Peer review etiquette", "cached": "Peer-Review-Protocol.md § Peer review etiquette", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A6", "value": "1.4", "cached": "1.4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C6", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D6", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E6", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F6", "value": "Syllabus § Policies (cohort, attestation chain, late-retreat policy)", "cached": "Syllabus § Policies (cohort, attestation chain, late-retreat policy)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A7", "value": "1.5", "cached": "1.5", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C7", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D7", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E7", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F7", "value": "Syllabus § Technology requirements", "cached": "Syllabus § Technology requirements", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A8", "value": "1.6", "cached": "1.6", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C8", "value": 1, "cached": 1, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D8", "value": 1, "cached": 1, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E8", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F8", "value": "Syllabus § Prerequisites (C8 attestation, 88+ days operating)", "cached": "Syllabus § Prerequisites (C8 attestation, 88+ days operating)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A9", "value": "1.7", "cached": "1.7", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C9", "value": 1, "cached": 1, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D9", "value": 1, "cached": 1, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E9", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F9", "value": "M9.1-Video-Production-Spec.md (instructor-presence video specification)", "cached": "M9.1-Video-Production-Spec.md (instructor-presence video specification)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A10", "value": "1.8", "cached": "1.8", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C10", "value": 1, "cached": 1, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D10", "value": 1, "cached": 1, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E10", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F10", "value": "Syllabus § Cohort onboarding (peer triad introduction at M9.1)", "cached": "Syllabus § Cohort onboarding (peer triad introduction at M9.1)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A11", "value": "2.1", "cached": "2.1", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B11", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C11", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D11", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E11", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F11", "value": "Learning-Outcomes.md § Course-level outcomes (5 measurable outcomes)", "cached": "Learning-Outcomes.md § Course-level outcomes (5 measurable outcomes)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A12", "value": "2.2", "cached": "2.2", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B12", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C12", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D12", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E12", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F12", "value": "Each M9.X-*.md opens with module objectives; consolidated in Learning-Outcomes.md", "cached": "Each M9.X-*.md opens with module objectives; consolidated in Learning-Outcomes.md", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A13", "value": "2.3", "cached": "2.3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C13", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D13", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E13", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F13", "value": "Learning-Outcomes.md uses Operator will... stem; module objectives use action verbs", "cached": "Learning-Outcomes.md uses Operator will... stem; module objectives use action verbs", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A14", "value": "2.4", "cached": "2.4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C14", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D14", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E14", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F14", "value": "Stage 2 prerequisites confirmed; Doctrines.md links objectives to stage-appropriate doctrines", "cached": "Stage 2 prerequisites confirmed; Doctrines.md links objectives to stage-appropriate doctrines", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A15", "value": "2.5", "cached": "2.5", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C15", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D15", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E15", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F15", "value": "Each module: objectives -> activities -> submission -> rubric criterion; cross-referenced in Summative-Attestation-Rubric.md", "cached": "Each module: objectives -> activities -> submission -> rubric criterion; cross-referenced in Summative-Attestation-Rubric.md", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A16", "value": "3.1", "cached": "3.1", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B16", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C16", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D16", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E16", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F16", "value": "Summative-Attestation-Rubric.md (8 criteria each map to a course outcome)", "cached": "Summative-Attestation-Rubric.md (8 criteria each map to a course outcome)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A17", "value": "3.2", "cached": "3.2", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C17", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D17", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E17", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F17", "value": "Summative-Attestation-Rubric.md § Scoring summary + § Pass condition", "cached": "Summative-Attestation-Rubric.md § Scoring summary + § Pass condition", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A18", "value": "3.3", "cached": "3.3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C18", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D18", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E18", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F18", "value": "Rubric uses 4-level descriptors (Exceeds/Meets/Approaches/Below) per criterion", "cached": "Rubric uses 4-level descriptors (Exceeds/Meets/Approaches/Below) per criterion", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A19", "value": "3.4", "cached": "3.4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C19", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D19", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E19", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F19", "value": "8 module submissions + HITL gate + course-completion gate; per-module remediation pathways", "cached": "8 module submissions + HITL gate + course-completion gate; per-module remediation pathways", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A20", "value": "3.5", "cached": "3.5", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C20", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D20", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E20", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F20", "value": "All assessments are operator's actual quarterly work; no simulated assessments", "cached": "All assessments are operator's actual quarterly work; no simulated assessments", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A21", "value": "4.1", "cached": "4.1", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B21", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C21", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D21", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E21", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F21", "value": "Each module lesson references its objective(s); Resources cross-referenced from lessons", "cached": "Each module lesson references its objective(s); Resources cross-referenced from lessons", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A22", "value": "4.2", "cached": "4.2", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C22", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D22", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E22", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F22", "value": "Doctrines.md cites Moran/Lennington 2013, Newport 2016, Scott 2017, Meadows 2008, etc.", "cached": "Doctrines.md cites Moran/Lennington 2013, Newport 2016, Scott 2017, Meadows 2008, etc.", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A23", "value": "4.3", "cached": "4.3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C23", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D23", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E23", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F23", "value": "Markdown lessons + video (M9.1) + templates + case studies + community prompts + system prompts (5+ formats)", "cached": "Markdown lessons + video (M9.1) + templates + case studies + community prompts + system prompts (5+ formats)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A24", "value": "4.4", "cached": "4.4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C24", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D24", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E24", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F24", "value": "Syllabus § Materials marks required vs optional; peer review explicitly optional", "cached": "Syllabus § Materials marks required vs optional; peer review explicitly optional", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A25", "value": "4.5", "cached": "4.5", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C25", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D25", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E25", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F25", "value": "README.md § Licensing (RISER Nation Maritime Academy proprietary; reuse provisions)", "cached": "README.md § Licensing (RISER Nation Maritime Academy proprietary; reuse provisions)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A26", "value": "5.1", "cached": "5.1", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B26", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C26", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D26", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E26", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F26", "value": "Each module's activities directly produce artifacts satisfying outcomes", "cached": "Each module's activities directly produce artifacts satisfying outcomes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A27", "value": "5.2", "cached": "5.2", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C27", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D27", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E27", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F27", "value": "Peer review triads at three exchange points; HITL reviewer interaction; Quarterly Review Validator dialogic interaction", "cached": "Peer review triads at three exchange points; HITL reviewer interaction; Quarterly Review Validator dialogic interaction", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A28", "value": "5.3", "cached": "5.3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C28", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D28", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E28", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F28", "value": "Instructor-HITL-Gate-M9.6.md § Reviewer workflow (24h standard / 48h extended)", "cached": "Instructor-HITL-Gate-M9.6.md § Reviewer workflow (24h standard / 48h extended)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A29", "value": "5.4", "cached": "5.4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C29", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D29", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E29", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F29", "value": "Peer-Review-Protocol.md and Syllabus § Cohort interaction specify required vs optional", "cached": "Peer-Review-Protocol.md and Syllabus § Cohort interaction specify required vs optional", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A30", "value": "6.1", "cached": "6.1", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B30", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C30", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D30", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E30", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F30", "value": "integration-spec.md - LMS, validator service, Captain's Console, Supabase tables map to objectives", "cached": "integration-spec.md - LMS, validator service, Captain's Console, Supabase tables map to objectives", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A31", "value": "6.2", "cached": "6.2", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C31", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D31", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E31", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F31", "value": "LMS peer-review module; HITL packet workflow; AI validator dialog interfaces", "cached": "LMS peer-review module; HITL packet workflow; AI validator dialog interfaces", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A32", "value": "6.3", "cached": "6.3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C32", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D32", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E32", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F32", "value": "Validators on Sonnet/Opus 4.7; Supabase backend; modern LMS layer", "cached": "Validators on Sonnet/Opus 4.7; Supabase backend; modern LMS layer", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A33", "value": "6.4", "cached": "6.4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C33", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D33", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E33", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F33", "value": "RLS policies in c9-supabase-schema.sql; peer-review confidentiality stated", "cached": "RLS policies in c9-supabase-schema.sql; peer-review confidentiality stated", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A34", "value": "7.1", "cached": "7.1", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B34", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C34", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D34", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E34", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F34", "value": "Syllabus § Support; README § Help and escalation", "cached": "Syllabus § Support; README § Help and escalation", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A35", "value": "7.2", "cached": "7.2", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C35", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D35", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E35", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F35", "value": "Syllabus links to Reviewer Office Hours, peer cohort channels, recalibration paths", "cached": "Syllabus links to Reviewer Office Hours, peer cohort channels, recalibration paths", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A36", "value": "7.3", "cached": "7.3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C36", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D36", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E36", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F36", "value": "Syllabus references operator-care resources; burnout escalation protocol", "cached": "Syllabus references operator-care resources; burnout escalation protocol", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A37", "value": "7.4", "cached": "7.4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C37", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D37", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E37", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F37", "value": "Syllabus § Accessibility (paper-only M9.4 alternatives; retreat-window flexibility)", "cached": "Syllabus § Accessibility (paper-only M9.4 alternatives; retreat-window flexibility)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A38", "value": "8.1", "cached": "8.1", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B38", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C38", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D38", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E38", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F38", "value": "LMS WCAG 2.1 AA compliance; markdown screen-reader compatible", "cached": "LMS WCAG 2.1 AA compliance; markdown screen-reader compatible", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A39", "value": "8.2", "cached": "8.2", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C39", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D39", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E39", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F39", "value": "Consistent heading hierarchy; plain-language doctrine framing", "cached": "Consistent heading hierarchy; plain-language doctrine framing", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A40", "value": "8.3", "cached": "8.3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B40", "value": "Yes", "cached": "Yes", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C40", "value": 3, "cached": 3, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D40", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E40", "value": "Conditional", "cached": "Conditional", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F40", "value": "M9.1-Video-Production-Spec.md includes captions and transcript requirements. Note: M9.2-M9.8 video specs not produced (paper/template-driven). Strict interpretation flags non-conformance; design-intent interpretation supports conformance. Audit records midpoint awarded score (2/3) reflecting documented dispute. Resolution path: file QM rubric clarification request OR produce companion video specs for M9.2-M9.8.", "cached": "M9.1-Video-Production-Spec.md includes captions and transcript requirements. Note: M9.2-M9.8 video specs not produced (paper/template-driven). Strict interpretation flags non-conformance; design-intent interpretation supports conformance. Audit records midpoint awarded score (2/3) reflecting documented dispute. Resolution path: file QM rubric clarification request OR produce companion video specs for M9.2-M9.8.", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A41", "value": "8.4", "cached": "8.4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C41", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D41", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E41", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F41", "value": "Each module follows consistent structure (objectives -> lesson -> activities -> submission -> checklist)", "cached": "Each module follows consistent structure (objectives -> lesson -> activities -> submission -> checklist)", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A42", "value": "8.5", "cached": "8.5", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C42", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D42", "value": 2, "cached": 2, "format": "General", "comment": null, "hyperlink": null}, {"cell": "E42", "value": "Conforms", "cached": "Conforms", "format": "General", "comment": null, "hyperlink": null}, {"cell": "F42", "value": "Markdown renders desktop and mobile; LMS responsive", "cached": "Markdown renders desktop and mobile; LMS responsive", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A43", "value": "TOTAL", "cached": "TOTAL", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C43", "value": "=SUM(C3:C42)", "cached": 95, "format": "General", "comment": null, "hyperlink": null}, {"cell": "D43", "value": "=SUM(D3:D42)", "cached": 94, "format": "General", "comment": null, "hyperlink": null}], "merged": ["A1:F1"], "images": 0, "charts": 0, "tables": [], "conditional_formats": 0}
{"sheet": "Comparison", "state": "visible", "cells": [{"cell": "A1", "value": "Catalog Audit Comparison", "cached": "Catalog Audit Comparison", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A2", "value": "Course", "cached": "Course", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B2", "value": "Score", "cached": "Score", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C2", "value": "Percentage", "cached": "Percentage", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D2", "value": "Status", "cached": "Status", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A3", "value": "C1", "cached": "C1", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B3", "value": "94/94", "cached": "94/94", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C3", "value": "100.0%", "cached": "100.0%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D3", "value": "Certified", "cached": "Certified", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A4", "value": "C2", "cached": "C2", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B4", "value": "93/94", "cached": "93/94", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C4", "value": "98.9%", "cached": "98.9%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D4", "value": "Certified", "cached": "Certified", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A5", "value": "C3", "cached": "C3", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B5", "value": "94/94", "cached": "94/94", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C5", "value": "100.0%", "cached": "100.0%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D5", "value": "Certified", "cached": "Certified", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A6", "value": "C4", "cached": "C4", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B6", "value": "92/94", "cached": "92/94", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C6", "value": "97.9%", "cached": "97.9%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D6", "value": "Certified", "cached": "Certified", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A7", "value": "C5", "cached": "C5", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B7", "value": "94/94", "cached": "94/94", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C7", "value": "100.0%", "cached": "100.0%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D7", "value": "Certified", "cached": "Certified", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A8", "value": "C6", "cached": "C6", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B8", "value": "93/94", "cached": "93/94", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C8", "value": "98.9%", "cached": "98.9%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D8", "value": "Certified", "cached": "Certified", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A9", "value": "C7", "cached": "C7", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B9", "value": "94/94", "cached": "94/94", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C9", "value": "100.0%", "cached": "100.0%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D9", "value": "Certified", "cached": "Certified", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A10", "value": "C8", "cached": "C8", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B10", "value": "93/94", "cached": "93/94", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C10", "value": "98.9%", "cached": "98.9%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D10", "value": "Certified", "cached": "Certified", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A11", "value": "C9", "cached": "C9", "format": "General", "comment": null, "hyperlink": null}, {"cell": "B11", "value": "92/94", "cached": "92/94", "format": "General", "comment": null, "hyperlink": null}, {"cell": "C11", "value": "97.9%", "cached": "97.9%", "format": "General", "comment": null, "hyperlink": null}, {"cell": "D11", "value": "NOT_CERTIFIED", "cached": "NOT_CERTIFIED", "format": "General", "comment": null, "hyperlink": null}], "merged": ["A1:D1"], "images": 0, "charts": 0, "tables": [], "conditional_formats": 0}
{"sheet": "Recommendation", "state": "visible", "cells": [{"cell": "A1", "value": "Reviewer Recommendation", "cached": "Reviewer Recommendation", "format": "General", "comment": null, "hyperlink": null}, {"cell": "A3", "value": "File QM rubric clarification request (path 2) before C9 deployment. M9.2-M9.8 are deliberately paper/template-driven for pedagogical reasons (Stillwater non-screen activity; Open Ocean paper-only sessions). Adding video would corrupt design intent. C9 may deploy under NOT_CERTIFIED status during clarification window per prior precedent.", "cached": "File QM rubric clarification request (path 2) before C9 deployment. M9.2-M9.8 are deliberately paper/template-driven for pedagogical reasons (Stillwater non-screen activity; Open Ocean paper-only sessions). Adding video would corrupt design intent. C9 may deploy under NOT_CERTIFIED status during clarification window per prior precedent.", "format": "General", "comment": null, "hyperlink": null}], "merged": [], "images": 0, "charts": 0, "tables": [], "conditional_formats": 0}

QM-Audit-C9.json

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

Working lesson text. Some source claims and supporting assets remain unverified.

Reconcile rubric identity and missing standards

Correct the disputed standard reference

Distinguish design specifications from delivered accessibility

QM-Audit-C9.json — assigned original

Evaluate both proposed remediation paths

QM-Audit-C9.json — assigned original

Preserve design intent without inventing a resolution

QM-Audit-C9.json — assigned original

Use every evidence row as a review task

QM-Audit-C9.json — assigned original

Read all nine comparison records cautiously

QM-Audit-C9.json — assigned original

Apply the marketing frameworks to evidence quality

Submit a reconciled review packet

QM-Audit-C9.json — assigned original

Inspect each internal audit record

Source ID	Essential flag	Awarded / maximum	Status and claimed evidence	Review exercise	Source
1.1	Yes	3 / 3	Conforms: 00_Course-Overview/README.md § Getting Started; M9.1 § First steps	Follow the getting-started instructions as a new learner and record whether the first required action can be located.	QM-Audit-C9.json — evidence record 1.1
1.2	Yes	3 / 3	Conforms: Syllabus § Course architecture (8-module flow with HITL gate)	Trace the eight-module flow and identify where the human review gate occurs. A diagram must agree with the actual lesson order.	QM-Audit-C9.json — evidence record 1.2
1.3	False	2 / 2	Conforms: Peer-Review-Protocol.md § Peer review etiquette	Locate the peer-review etiquette and check whether a learner can understand how to communicate appropriately.	QM-Audit-C9.json — evidence record 1.3
1.4	False	2 / 2	Conforms: Syllabus § Policies (cohort, attestation chain, late-retreat policy)	Read the cohort, attestation-chain and late-retreat policies together. Identify conflicting deadlines or prerequisites.	QM-Audit-C9.json — evidence record 1.4
1.5	False	2 / 2	Conforms: Syllabus § Technology requirements	Compare the stated technology requirements with the tools actually needed for the exercises.	QM-Audit-C9.json — evidence record 1.5
1.6	False	1 / 1	Conforms: Syllabus § Prerequisites (C8 attestation, 88+ days operating)	Inspect the C8 attestation and the source requirement of at least 88 operating days. Preserve the legacy prerequisite and verify actual records rather than asserting a learner qualifies.	QM-Audit-C9.json — evidence record 1.6
1.7	False	1 / 1	Conforms: M9.1-Video-Production-Spec.md (instructor-presence video specification)	Inspect the instructor-presence specification, then separately check the delivered introduction. A production specification does not prove a video has been recorded.	QM-Audit-C9.json — evidence record 1.7
1.8	False	1 / 1	Conforms: Syllabus § Cohort onboarding (peer triad introduction at M9.1)	Check how the peer triad introduces its members at M9.1. A proposed onboarding activity needs clear participation instructions.	QM-Audit-C9.json — evidence record 1.8
2.1	Yes	3 / 3	Conforms: Learning-Outcomes.md § Course-level outcomes (5 measurable outcomes)	Inspect each of the five course outcomes for an observable learner result and a way to assess it.	QM-Audit-C9.json — evidence record 2.1
2.2	Yes	3 / 3	Conforms: Each M9.X-*.md opens with module objectives; consolidated in Learning-Outcomes.md	Compare each module objective with the consolidated outcomes. Identify objectives that lack a matching task or assessment.	QM-Audit-C9.json — evidence record 2.2
2.3	False	3 / 3	Conforms: Learning-Outcomes.md uses Operator will... stem; module objectives use action verbs	Check that action verbs specify observable work. The phrase Operator will does not by itself make an outcome measurable.	QM-Audit-C9.json — evidence record 2.3
2.4	False	3 / 3	Conforms: Stage 2 prerequisites confirmed; Doctrines.md links objectives to stage-appropriate doctrines	Inspect the stage prerequisites and the cited doctrines. Explain why the required task is suitable for that learner stage.	QM-Audit-C9.json — evidence record 2.4
2.5	False	3 / 3	Conforms: Each module: objectives -> activities -> submission -> rubric criterion; cross-referenced in Summative-Attestation-Rubric.md	Trace objectives to activities, submissions and rubric criteria. Missing relationships require clarification, not a guessed mapping.	QM-Audit-C9.json — evidence record 2.5
3.1	Yes	3 / 3	Conforms: Summative-Attestation-Rubric.md (8 criteria each map to a course outcome)	Map all eight summative criteria to course outcomes and inspect what evidence each criterion expects.	QM-Audit-C9.json — evidence record 3.1
3.2	False	3 / 3	Conforms: Summative-Attestation-Rubric.md § Scoring summary + § Pass condition	Read the scoring summary and pass condition together. Recalculate a sample submission and identify any contradictory passing rule.	QM-Audit-C9.json — evidence record 3.2
3.3	False	3 / 3	Conforms: Rubric uses 4-level descriptors (Exceeds/Meets/Approaches/Below) per criterion	Compare Exceeds, Meets, Approaches and Below descriptions. A learner should be able to tell what evidence distinguishes the levels.	QM-Audit-C9.json — evidence record 3.3
3.4	False	2 / 2	Conforms: 8 module submissions + HITL gate + course-completion gate; per-module remediation pathways	Trace the eight submissions, human gate, completion gate and remediation paths. Confirm what happens after an incomplete submission.	QM-Audit-C9.json — evidence record 3.4
3.5	False	2 / 2	Conforms: All assessments are operator's actual quarterly work; no simulated assessments	Inspect the quarterly work used in each assessment. Authenticity of a proposed task does not prove an actual operator completed it.	QM-Audit-C9.json — evidence record 3.5
4.1	Yes	3 / 3	Conforms: Each module lesson references its objective(s); Resources cross-referenced from lessons	Follow each lesson-to-objective and resource reference. A resource must support the task rather than merely appear on a list.	QM-Audit-C9.json — evidence record 4.1
4.2	False	3 / 3	Conforms: Doctrines.md cites Moran/Lennington 2013, Newport 2016, Scott 2017, Meadows 2008, etc.	Inspect the actual passages attributed to Moran/Lennington 2013, Newport 2016, Scott 2017 and Meadows 2008. A citation list alone does not establish currency or accurate application.	QM-Audit-C9.json — evidence record 4.2
4.3	False	2 / 2	Conforms: Markdown lessons + video (M9.1) + templates + case studies + community prompts + system prompts (5+ formats)	Inventory the markdown lessons, M9.1 video, templates, case studies, community prompts and system prompts. Verify which are delivered rather than counting plans as completed formats.	QM-Audit-C9.json — evidence record 4.3
4.4	False	2 / 2	Conforms: Syllabus § Materials marks required vs optional; peer review explicitly optional	Distinguish required from optional materials and preserve the source statement that peer review is optional.	QM-Audit-C9.json — evidence record 4.4
4.5	False	2 / 2	Conforms: README.md § Licensing (RISER Nation Maritime Academy proprietary; reuse provisions)	Read the proprietary and reuse terms in the named README. Verify permissions for each included item instead of treating a licensing sentence as ownership evidence.	QM-Audit-C9.json — evidence record 4.5
5.1	Yes	3 / 3	Conforms: Each module's activities directly produce artifacts satisfying outcomes	Show how each learning activity produces an artifact used to demonstrate an outcome.	QM-Audit-C9.json — evidence record 5.1
5.2	False	3 / 3	Conforms: Peer review triads at three exchange points; HITL reviewer interaction; Quarterly Review Validator dialogic interaction	Identify all three peer exchanges, the human reviewer interaction and the Quarterly Review Validator dialogue. Verify the instructions and available service for each.	QM-Audit-C9.json — evidence record 5.2
5.3	False	2 / 2	Conforms: Instructor-HITL-Gate-M9.6.md § Reviewer workflow (24h standard / 48h extended)	Inspect the stated 24-hour standard and 48-hour extended reviewer workflow. Record these as source service targets until actual staffing and service arrangements are established.	QM-Audit-C9.json — evidence record 5.3
5.4	False	2 / 2	Conforms: Peer-Review-Protocol.md and Syllabus § Cohort interaction specify required vs optional	Compare the peer-review protocol with cohort instructions so required and optional interactions do not contradict each other.	QM-Audit-C9.json — evidence record 5.4
6.1	Yes	3 / 3	Conforms: integration-spec.md - LMS, validator service, Captain's Console, Supabase tables map to objectives	Trace the proposed LMS, validator, Captain's Console and Supabase tables to the relevant objectives. Specifications are not evidence of a deployed integration.	QM-Audit-C9.json — evidence record 6.1
6.2	False	2 / 2	Conforms: LMS peer-review module; HITL packet workflow; AI validator dialog interfaces	Inspect how the peer-review module, human-review packet and validator dialogue support actual participation.	QM-Audit-C9.json — evidence record 6.2
6.3	False	2 / 2	Conforms: Validators on Sonnet/Opus 4.7; Supabase backend; modern LMS layer	Treat Sonnet/Opus 4.7, Supabase and the LMS layer as source configuration claims. Verify availability and suitability before implementation.	QM-Audit-C9.json — evidence record 6.3
6.4	False	2 / 2	Conforms: RLS policies in c9-supabase-schema.sql; peer-review confidentiality stated	Inspect the named row-level-security policies and peer confidentiality provisions. Their presence in a specification does not prove effective access control in a running system.	QM-Audit-C9.json — evidence record 6.4
7.1	Yes	3 / 3	Conforms: Syllabus § Support; README § Help and escalation	Follow the support and escalation instructions. Check that each contact or help route is usable.	QM-Audit-C9.json — evidence record 7.1
7.2	False	2 / 2	Conforms: Syllabus links to Reviewer Office Hours, peer cohort channels, recalibration paths	Inspect the Reviewer Office Hours, peer channels and recalibration routes. Note missing destinations or service details.	QM-Audit-C9.json — evidence record 7.2
7.3	False	2 / 2	Conforms: Syllabus references operator-care resources; burnout escalation protocol	Inspect the operator-care resources and burnout escalation protocol. Course support should identify an appropriate route without diagnosing the learner.	QM-Audit-C9.json — evidence record 7.3
7.4	False	2 / 2	Conforms: Syllabus § Accessibility (paper-only M9.4 alternatives; retreat-window flexibility)	Compare the paper-only M9.4 alternative and retreat-window flexibility with the intended task. A flexible pathway still needs usable instructions and appropriate assessment.	QM-Audit-C9.json — evidence record 7.4
8.1	Yes	3 / 3	Conforms: LMS WCAG 2.1 AA compliance; markdown screen-reader compatible	Treat the asserted WCAG 2.1 AA compliance and screen-reader compatibility as claims requiring testing of the actual rendered course. Markdown alone does not establish either.	QM-Audit-C9.json — evidence record 8.1
8.2	False	2 / 2	Conforms: Consistent heading hierarchy; plain-language doctrine framing	Inspect heading order and plain-language explanations in the rendered lesson, including expanded appendices.	QM-Audit-C9.json — evidence record 8.2
8.3	Yes	2 / 3	Conditional: M9.1-Video-Production-Spec.md includes captions and transcript requirements. Note: M9.2-M9.8 video specs not produced (paper/template-driven). Strict interpretation flags non-conformance; design-intent interpretation supports conformance. Audit records midpoint awarded score (2/3) reflecting documented dispute. Resolution path: file QM rubric clarification request OR produce companion video specs for M9.2-M9.8.	Preserve the recorded 2/3 conditional score, missing M9.2–M9.8 specifications and both proposed interpretations. Reconcile the incorrect rubric identifier before deciding what remediation is appropriate.	QM-Audit-C9.json — evidence record 8.3
8.4	False	2 / 2	Conforms: Each module follows consistent structure (objectives -> lesson -> activities -> submission -> checklist)	Follow the proposed objectives, lesson, activities, submission and checklist sequence. Consistent structure helps use but does not settle the mislabeled official standard.	QM-Audit-C9.json — evidence record 8.4
8.5	False	2 / 2	Conforms: Markdown renders desktop and mobile; LMS responsive	Check actual desktop and mobile rendering, keyboard access and overflow. A statement that the LMS is responsive is not a completed usability test.	QM-Audit-C9.json — evidence record 8.5

Complete original source text

{
  "audit_metadata": {
    "course_code": "C9",
    "course_title": "Bora Bora Captain's Retreat — Strategic Renewal",
    "stage": 2,
    "stage_name": "Sailboat",
    "catalog_position": "Course 4 of 5 in Stage 2; first quarterly integrative review course in catalog",
    "rubric": "QM HE 7th Edition v2.0",
    "max_points": 94,
    "essential_standards_count": 16,
    "pass_threshold_points": 80,
    "pass_threshold_percent": 85.0,
    "audit_date": "2026-04-26",
    "auditor": "RISER Internal QM Audit Tool",
    "build_path": "/home/claude/C9-build/"
  },
  "summary": {
    "total_points_awarded": 92,
    "total_points_possible": 94,
    "percentage": 97.9,
    "essential_conforming": 15,
    "essential_total": 16,
    "essential_disputed": ["SRS_8.3"],
    "score_passes_threshold": true,
    "all_essentials_conform": false,
    "certification_status": "NOT_CERTIFIED",
    "certification_block_reason": "SRS 8.3 Essential standard recorded as conditional non-conformance under strict interpretation of multimedia accessibility requirement; M9.2-M9.8 video specifications not produced for paper/template-driven modules.",
    "remediation_paths": [
      {
        "path": 1,
        "description": "Produce video specifications for M9.2-M9.8",
        "estimated_effort_hours": "14-21",
        "outcome": "Full SRS 8.3 conformance"
      },
      {
        "path": 2,
        "description": "File QM rubric clarification request documenting design-intent that SRS 8.3 applies only to multimedia present",
        "estimated_effort_hours": "2-4",
        "outcome": "Conditional conformance pending QM response",
        "recommended": true
      }
    ]
  },
  "standards": [
    {"srs": "1.1", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "00_Course-Overview/README.md § Getting Started; M9.1 § First steps"},
    {"srs": "1.2", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Syllabus § Course architecture (8-module flow with HITL gate)"},
    {"srs": "1.3", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Peer-Review-Protocol.md § Peer review etiquette"},
    {"srs": "1.4", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Syllabus § Policies (cohort, attestation chain, late-retreat policy)"},
    {"srs": "1.5", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Syllabus § Technology requirements"},
    {"srs": "1.6", "essential": false, "max_points": 1, "awarded": 1, "status": "Conforms", "evidence": "Syllabus § Prerequisites (C8 attestation, 88+ days operating)"},
    {"srs": "1.7", "essential": false, "max_points": 1, "awarded": 1, "status": "Conforms", "evidence": "M9.1-Video-Production-Spec.md (instructor-presence video specification)"},
    {"srs": "1.8", "essential": false, "max_points": 1, "awarded": 1, "status": "Conforms", "evidence": "Syllabus § Cohort onboarding (peer triad introduction at M9.1)"},
    {"srs": "2.1", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Learning-Outcomes.md § Course-level outcomes (5 measurable outcomes)"},
    {"srs": "2.2", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Each M9.X-*.md opens with module objectives; consolidated in Learning-Outcomes.md"},
    {"srs": "2.3", "essential": false, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Learning-Outcomes.md uses Operator will... stem; module objectives use action verbs"},
    {"srs": "2.4", "essential": false, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Stage 2 prerequisites confirmed; Doctrines.md links objectives to stage-appropriate doctrines"},
    {"srs": "2.5", "essential": false, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Each module: objectives -> activities -> submission -> rubric criterion; cross-referenced in Summative-Attestation-Rubric.md"},
    {"srs": "3.1", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Summative-Attestation-Rubric.md (8 criteria each map to a course outcome)"},
    {"srs": "3.2", "essential": false, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Summative-Attestation-Rubric.md § Scoring summary + § Pass condition"},
    {"srs": "3.3", "essential": false, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Rubric uses 4-level descriptors (Exceeds/Meets/Approaches/Below) per criterion"},
    {"srs": "3.4", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "8 module submissions + HITL gate + course-completion gate; per-module remediation pathways"},
    {"srs": "3.5", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "All assessments are operator's actual quarterly work; no simulated assessments"},
    {"srs": "4.1", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Each module lesson references its objective(s); Resources cross-referenced from lessons"},
    {"srs": "4.2", "essential": false, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Doctrines.md cites Moran/Lennington 2013, Newport 2016, Scott 2017, Meadows 2008, etc."},
    {"srs": "4.3", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Markdown lessons + video (M9.1) + templates + case studies + community prompts + system prompts (5+ formats)"},
    {"srs": "4.4", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Syllabus § Materials marks required vs optional; peer review explicitly optional"},
    {"srs": "4.5", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "README.md § Licensing (RISER Nation Maritime Academy proprietary; reuse provisions)"},
    {"srs": "5.1", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Each module's activities directly produce artifacts satisfying outcomes"},
    {"srs": "5.2", "essential": false, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Peer review triads at three exchange points; HITL reviewer interaction; Quarterly Review Validator dialogic interaction"},
    {"srs": "5.3", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Instructor-HITL-Gate-M9.6.md § Reviewer workflow (24h standard / 48h extended)"},
    {"srs": "5.4", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Peer-Review-Protocol.md and Syllabus § Cohort interaction specify required vs optional"},
    {"srs": "6.1", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "integration-spec.md - LMS, validator service, Captain's Console, Supabase tables map to objectives"},
    {"srs": "6.2", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "LMS peer-review module; HITL packet workflow; AI validator dialog interfaces"},
    {"srs": "6.3", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Validators on Sonnet/Opus 4.7; Supabase backend; modern LMS layer"},
    {"srs": "6.4", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "RLS policies in c9-supabase-schema.sql; peer-review confidentiality stated"},
    {"srs": "7.1", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "Syllabus § Support; README § Help and escalation"},
    {"srs": "7.2", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Syllabus links to Reviewer Office Hours, peer cohort channels, recalibration paths"},
    {"srs": "7.3", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Syllabus references operator-care resources; burnout escalation protocol"},
    {"srs": "7.4", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Syllabus § Accessibility (paper-only M9.4 alternatives; retreat-window flexibility)"},
    {"srs": "8.1", "essential": true, "max_points": 3, "awarded": 3, "status": "Conforms", "evidence": "LMS WCAG 2.1 AA compliance; markdown screen-reader compatible"},
    {"srs": "8.2", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Consistent heading hierarchy; plain-language doctrine framing"},
    {"srs": "8.3", "essential": true, "max_points": 3, "awarded": 2, "status": "Conditional", "evidence": "M9.1-Video-Production-Spec.md includes captions and transcript requirements. Note: M9.2-M9.8 video specs not produced (paper/template-driven). Strict interpretation flags non-conformance; design-intent interpretation supports conformance. Audit records midpoint awarded score (2/3) reflecting documented dispute. Resolution path: file QM rubric clarification request OR produce companion video specs for M9.2-M9.8.", "dispute_documented": true},
    {"srs": "8.4", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Each module follows consistent structure (objectives -> lesson -> activities -> submission -> checklist)"},
    {"srs": "8.5", "essential": false, "max_points": 2, "awarded": 2, "status": "Conforms", "evidence": "Markdown renders desktop and mobile; LMS responsive"}
  ],
  "comparison_to_prior_courses": [
    {"course": "C1", "score": "94/94", "percent": 100.0, "status": "Certified"},
    {"course": "C2", "score": "93/94", "percent": 98.9, "status": "Certified"},
    {"course": "C3", "score": "94/94", "percent": 100.0, "status": "Certified"},
    {"course": "C4", "score": "92/94", "percent": 97.9, "status": "Certified"},
    {"course": "C5", "score": "94/94", "percent": 100.0, "status": "Certified"},
    {"course": "C6", "score": "93/94", "percent": 98.9, "status": "Certified"},
    {"course": "C7", "score": "94/94", "percent": 100.0, "status": "Certified"},
    {"course": "C8", "score": "93/94", "percent": 98.9, "status": "Certified"},
    {"course": "C9", "score": "92/94", "percent": 97.9, "status": "NOT_CERTIFIED"}
  ],
  "reviewer_recommendation": "File QM rubric clarification request (path 2) before C9 deployment. M9.2-M9.8 are deliberately paper/template-driven for pedagogical reasons (Stillwater non-screen activity; Open Ocean paper-only sessions). Adding video would corrupt design intent. C9 may deploy under NOT_CERTIFIED status during clarification window per prior precedent."
}

QM Audit Notes — separate C9 and C10 versions

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

Working lesson text. Some source claims and supporting assets remain unverified.

Keep both audit trails

The two QM-Audit-Notes.md sources describe different courses. One concerns legacy C10 Proof Threshold, the Stage 2 graduation gate and fifth of five Sailboat courses, first gate since C5. The other concerns C9 Bora Bora Captain's Retreat — Strategic Renewal, the fourth course and quarterly review. They name an internal RISER audit tool and separate C9/C10 build paths. Preserve both versions and the current spreadsheet assignment rather than substituting legacy numbering.

Reconcile dates and versions

C9 records Sunday, April 26, 2026. C10 records Sunday, April 27, 2026, but April 27 was Monday. Preserve the original date label and explicitly flag the weekday error. C10 names notes version 1.0 and course version 2.0. A path described as a build commit is a location, not an immutable commit identifier; obtain a traceable version before reproducing the audit.

Distinguish a score pass from certification

Both notes report 92/94, 97.9%, an 80-point threshold labeled 85%, 15 of 16 essential standards conforming and NOT CERTIFIED pending the disputed standard. A high total and satisfaction of mandatory criteria are separate checks. These are internal source findings, not verified external certifications. Do not relabel either course certified based on its score alone.

Correct the rubric identity before resolving the dispute

The notes describe 42 standards and label 8.3 multimedia accessibility. The official QM overview identifies 44 specific standards; the public Seventh Edition list identifies 8.3 with text accessibility and 8.5 with video/audio. The linked Version 2.0 statement says the underlying standards did not change. First reconcile identifiers, point values and essential flags. The internal dispute about requiring video in every module is not an established interpretation of the named official standard.

Preserve both internal interpretations

The notes describe a strict interpretation requiring video specifications for modules 2–8, and a design-intent interpretation assessing only existing multimedia. C9 describes paper/template-driven modules; C10 describes documentation and validator dialogue. Both adopt the strict interpretation as their internal default. Keep this history visible while making clear that the available official references do not establish the asserted every-module video requirement.

Inspect specifications and delivered media separately

C9 names the M9.1 video specification and explicitly says the video was not yet recorded. C10 says the M10.1 specification requires captions and transcripts. Those are production requirements, not evidence that a delivered recording and its alternatives were checked. Review actual text, images and media in the intended learning environment and record the missing production work.

Retain both remediation options and their estimates

The first proposal is to produce seven companion specifications, at two to three hours each, totaling 14–21 hours. The second is a rubric clarification request; C10 gives a 2–4-hour estimate and suggests consolidating it with C9. These are source estimates, not this project's runtime or a promise of certification. Resolve the faulty rubric mapping before deciding what work is needed.

Separate recommendation from authorization and completion

C9 says the owner has not selected a path, while recommending clarification before deployment; if denied, it proposes companion specifications that complement paper work. C10 says a C9 precedent is already queued and recommends the same route to preserve empirical learning and avoid delay. The notes do not establish that a request was actually filed or answered. No request is being sent by this lesson.

Preserve C9 design intent

Stillwater is described as non-screen activity and Open Ocean as paper-only sessions. The source argues that adding video would corrupt this purpose. Inspect whether a proposed companion resource genuinely changes the activity or simply supports access. Preserve the intended learning outcome while checking the actual applicable requirements rather than assuming either all-video or no-video is automatically correct.

QM Audit Notes — C9 Captain's Retreat

Reconcile C9 row counts and subtraction

The C9 notes label 39 of 42 standards full conformance and three of 42 conditional notes. Their enumerated full-point identifiers contain 39 entries, but the three conditional notes overlap that list at 1.7 and 4.5. The companion JSON has 40 distinct rows. The claim that losing one point from 94 produces 92 is incorrect: it produces 93. Keep the original text and a separate discrepancy record rather than quietly adjusting numbers.

QM Audit Notes — C9 Captain's Retreat

Review all three C9 conditional notes

For 1.7 the source gives one point for an instructor video specification despite the recording being pending. For 4.5 it gives two points for proprietary licensing language and calls for a licensing update review after relicensing. For 8.3 it discusses three points under design intent, one under strict interpretation and two as the recorded midpoint. These are internal treatments; neither a midpoint nor source wording establishes a valid official scoring rule.

QM Audit Notes — C9 Captain's Retreat

Read the complete C9 comparison

The table lists C1 Harbor Launch, C3 Compass Calibration, C5 Hull Inspection and C7 Tide Reading at 94/94 and 100%; C2 Lighthouse Mission, C6 Provisioning Run and C8 Pricing Discipline at 93/94 and 98.9%; C4 First Berth Mooring at 92/94 and 97.9%. All eight are labeled Certified with 16/16 essentials. C9 Captain's Retreat is 92/94 and 97.9%, 15/16 essentials and NOT CERTIFIED. These remain unverified historical comparison claims, including the assertion that C9 is the first noncertified course.

QM Audit Notes — C9 Captain's Retreat

Treat C9 sign-off as version-specific

The C9 closing sign-off says the audit is finalized at the referenced build and that subsequent changes require another audit. Record which actual files and versions were evaluated. A later edit, new recording or changed license should have an explicit review trail rather than inheriting an old status without inspection.

QM Audit Notes — C9 Captain's Retreat

Inspect every C10 citation tradition

The C10 currency discussion names constraint theory (Goldratt 1984), lean startup (Ries 2011 and Blank 2005), systems thinking (Meadows 2008), interviews (Murphy/Moesta 2020 and Torres 2021), high-stakes decisions (Gawande 2007/2009 and Dekker 2014), pricing (Simon 2015 and Michalowicz 2017), operator state (Crabtree 2014 and Lencioni 2012), discipline (Collins 2001, Grove 1983 and Newport 2012), funnels (Balfour/Reforge), positioning (Dunford 2019) and AEO/distribution (Bush 2019). These are incomplete author/year references. Locate the exact works and inspect the actual applications; breadth and publication year alone do not establish accuracy or current relevance. Do not invent book titles or supporting links.

QM Audit Notes — C10 Proof Threshold

Trace all three C10 interaction layers

The proposed peer exchanges occur before M10.1, at M10.5 and at M10.7. Human gates occur at M10.4 and M10.7, with a live conversation at the latter. Validator dialogue is assigned to Sonnet 4.7 for M10.1–M10.7 and Opus 4.7 for M10.8. These are source configuration names, not verified current products or deployed services. Inspect the peer protocol, instructor gate and actual workflow before promising access or review.

QM Audit Notes — C10 Proof Threshold

Inspect recovery and privacy as implemented behavior

The source cites Failure-Case-Aspirational-Threshold-Trap.md and NOT_APPROVED recovery at M10.1 and M10.8. It proposes recording attempts in stage_graduations without stigma. It also claims row-level security on all c10_* tables and confidentiality in the peer protocol. Verify the schema, access tests and operational handling; a described policy does not prove working protection. Use recovery records to identify revisions without shaming the learner.

QM Audit Notes — C10 Proof Threshold

Preserve the three business-model pathways

The C10 notes identify Maya for bilateral retainers/projects, Darius for cohorts/groups and Priya for fractional services. They describe a three-customer floor and a margin threshold written as at least four to five customers, with M10.2 documentation and a cross-case framework. Preserve that ambiguous four-to-five expression rather than silently selecting one threshold. Retrieve the actual definitions and evidence requirements before treating these notes as the complete graduation rubric.

QM Audit Notes — C10 Proof Threshold

Measure the cost of the two human gates

The notes flag extra learner engagement and instructor time from M10.4 and M10.7 and suggest tracking instructor hours per cohort. Record actual reviewer time, capacity and turnaround separately. The assertion that the burden is appropriate is a source judgment; it needs a workable service design rather than an assumed staffing commitment.

QM Audit Notes — C10 Proof Threshold

Evaluate validator cost claims with current evidence

The source calls Opus 4.7 the highest-cost validator, says C10 is the second course using it after C9 and predicts similar Stage 3 gates at C14 and C27. No current pricing, usage records or deployed workflow is provided. Treat those as historical design assertions. A real cost estimate requires an available model, measured workload, current rates and human-review costs.

QM Audit Notes — C10 Proof Threshold

Reconcile four cases with five documents

The case-study description contains three graduation cases plus one failure case: four cases. Adding the cross-case synthesis yields five documents. Preserve both counts with their different units. The source warns against copying this density into nongate courses without a learning reason. Count the case examples and synthesis separately, then check that each contributes useful instruction.

QM Audit Notes — C10 Proof Threshold

Do not turn deployment recommendations into certification

C10 recommends deployment as NOT_CERTIFIED and a status change after clarification or a decision to create specifications. It also asserts that graduations during the dispute remain valid and permit unrestricted C11 enrollment, using the term accreditation for QM review. These are internal governance claims without a verified external ruling here. A decision to create media is not finished remediation; formal course certification and internal graduation decisions require their own evidence and authorized process.

QM Audit Notes — C10 Proof Threshold

Apply Brunson and Hormozi to an honest explanation

As a RISER adaptation, use Hook, Story, Offer to explain the learner problem, the audit evidence and the next review step. Use the Acquisition.com value lens to examine the desired outcome, confidence, delay and effort. Persuasive presentation should make unresolved findings clear. It cannot turn a proposed review system or an internal score into independent proof.

Submit a complete reconciliation

Keep both originals, their separate source links, the legacy course context, every reported threshold and comparison, the contradictions and missing dependencies. Produce a proposed correction log with evidence, version, owner and next action. Leave external certification, model availability and uninspected supporting files unresolved until evidence is obtained. No deployment, database change, enrollment decision or external filing is performed by this exercise.

Complete original C10 audit notes

# QM Audit Notes — C10 Proof Threshold

These notes document the audit decisions and rationale captured during the C10 QM audit run. They serve as the audit trail referenced by the audit JSON output and as reviewer notes for future revisions.

---

## Audit metadata

- **Course:** C10 Proof Threshold — Stage 2 Graduation Gate
- **Stage:** 2 (Sailboat)
- **Catalog position:** Course 5 of 5 in Stage 2 (Stage 2 capstone and graduation gate; first gate course since C5)
- **Rubric:** QM HE 7th Edition v2.0 (42 SRS / 16 Essential / 94 max points / 80-point pass threshold)
- **Audit run:** Sunday, April 27, 2026
- **Auditor:** RISER Internal QM Audit Tool v1.x
- **Build commit:** /home/claude/C10-build/ as of audit run timestamp

---

## Summary determination

**Score:** 92/94 (97.9%)
**Threshold:** 80/94 (85%)
**Pass:** YES on score
**Essential conformance:** 15/16 Essential standards conform; 1/16 (SRS 8.3) flagged conditional non-conformance
**Certification status:** **NOT CERTIFIED — pending SRS 8.3 resolution** despite score being above threshold

### Why NOT CERTIFIED despite passing score

The QM HE 7th Edition v2.0 rubric requires **all 16 Essential standards to conform** for certification. A single Essential non-conformance blocks certification regardless of total score. SRS 8.3 (multimedia accessibility) is Essential.

Two interpretations apply (see Input Map for detailed framing):
- **Strict interpretation:** SRS 8.3 expects video specs for all modules, including non-video modules. Non-conformance because M10.2–M10.8 video specs not produced.
- **Design-intent interpretation:** SRS 8.3 applies only to multimedia present. M10.2–M10.8 are documentation-driven and dialogic-validator-driven by design; they do not use video. Conformance.

The strict interpretation is the audit-default. C10 is therefore recorded as **NOT CERTIFIED** under the strict interpretation, but with documented dispute notes. This is the same dispute pattern as the C9 audit.

### Path to certification

Two paths exist:

1. **Produce video specs for M10.2–M10.8** (estimated effort: 2–3 hours per module = 14–21 additional hours of build work). This converts SRS 8.3 to unambiguous conformance.

2. **File QM rubric clarification request leveraging C9 precedent** (estimated effort: 2–4 hours). This documents the design-intent interpretation, references the C9 audit's identical finding, and requests rubric clarification that SRS 8.3 applies only to multimedia present in the course. Path 2 is the **recommended** path because:

- It preserves the pedagogical design intent of C10 (operator-empirical orientation; the validator dialog and the operator's artifact are the central media of these modules, not instructor presentation)
- It aligns with the C9 precedent already in the QM clarification queue
- It does not delay C10 deployment

The same recommendation pattern applies to both C9 and C10. The clarification request can be consolidated into a single multi-course filing.

---

## Audit decisions of note

### SRS 8.3 (Multimedia Accessibility) — Conditional Non-Conformance

The disputed standard. Audited at 2/3 awarded (midpoint), reflecting that the M10.1 video specification (M10.1-Video-Production-Spec.md) does include captions and transcript requirements — so multimedia present in the course conforms to the standard fully — but the rubric strict reading expects multimedia in every module. The audit documents both interpretations and records the dispute.

### SRS 4.2 (Currency of Materials) — Full Conformance

The C10 doctrines reference an unusually broad citation set spanning the constraint theory tradition (Goldratt 1984), the lean startup tradition (Ries 2011, Blank 2005), systems thinking (Meadows 2008), customer interview methods (Murphy/Moesta 2020, Torres 2021), the high-stakes-decision tradition (Gawande 2007/2009, Dekker 2014), the empirical pricing tradition (Simon 2015, Michalowicz 2017), the operator-state tradition (Crabtree 2014, Lencioni 2012), the strategic discipline tradition (Collins 2001, Grove 1983, Newport 2012), the marketing-funnel tradition (Balfour/Reforge), the positioning tradition (Dunford 2019), and the AEO/distribution tradition (Bush 2019). The breadth is appropriate for a Stage 2 capstone course that synthesizes prior Stage 1 and Stage 2 doctrines.

### SRS 5.2 (Learner-to-Learner and Learner-to-Instructor Interaction) — Full Conformance

C10 has three distinct interaction layers:
- **Peer review** at three exchange points (Pre-M10.1, M10.5, M10.7) per Peer-Review-Protocol.md
- **HITL instructor gates** at M10.4 and M10.7 per Instructor-HITL-Gate.md (live conversation at M10.7)
- **Validator dialogic interaction** with Sonnet 4.7 at M10.1-M10.7 and Opus 4.7 at M10.8

The interaction architecture is more elaborate than typical Stage 2 courses because the gate function requires multiple calibration layers. Audited as full conformance.

### SRS 3.4 (Self-Check, Practice, and Remediation) — Full Conformance

C10's recovery sequence pattern is doctrine-level. The Failure-Case-Aspirational-Threshold-Trap.md case study and the M10.1 / M10.8 NOT_APPROVED recovery paths constitute a structured remediation system. Re-attempt records are kept without shame in the stage_graduations table per c10-supabase-schema.sql. This exceeds typical SRS 3.4 conformance.

### SRS 6.4 (Privacy and Confidentiality) — Full Conformance

c10-supabase-schema.sql includes RLS (row-level security) policies on all c10_* tables. Peer review confidentiality is explicitly stated in Peer-Review-Protocol.md § Reviewer ethics. Re-attempt counts are recorded but framed without stigma — the schema is designed to support recovery sequences as part of normal Stage 2 maturation, not as failure records.

### SRS 7.4 (Accessibility Across Learner Pathways) — Full Conformance

C10 deliberately accommodates multiple business model pathways:
- Bilateral retainer/project models (Maya pattern)
- Cohort/group models (Darius pattern)
- Fractional services models (Priya pattern)

The Proof Threshold definitions and the M10.2 documentation requirements are written to apply consistently across all three model types. Floor-threshold (3 customers) and margin-threshold (≥4-5 customers) submission paths both supported. The Cross-Case-Framework.md document makes pathway differences explicit.

---

## Items that scored at maximum but warrant note

### M10.4 and M10.7 HITL gates

The two HITL gates raise the operator-engagement burden and the instructor-time-cost relative to courses with single-gate or no-gate structures. The audit confirms this is appropriate for a Stage 2 graduation gate course but flags it as a structural cost worth tracking in operations metrics (instructor hours per cohort).

### Opus 4.7 validator usage at M10.8

C10 uses the highest-cost validator (Opus 4.7) at the capstone gate. This is the second course in the catalog to use Opus 4.7 (C9 was the first). The cost is appropriate for graduation-stakes validation but represents an inflection in the catalog's per-course validator-cost profile. Stage 3 courses are expected to continue this pattern at corresponding gates (C14, C27, etc.).

### The four-case-study structure

C10 includes four case studies (3 graduation cases + 1 failure case + 1 cross-case framework synthesis = arguably 5 documents in the case-study set). This exceeds typical RISER catalog case-study counts. The audit confirms this is appropriate for the course's gate function — operators must have multiple pattern references including a failure pattern — but flags it as a content-density signal that should not propagate to non-gate courses without justification.

---

## Recommendation for C10 deployment

**Recommendation:** Proceed with C10 deployment under NOT_CERTIFIED status, file consolidated QM rubric clarification request alongside C9 (path 2), and update C10 status to CERTIFIED upon QM response or upon decision to produce video specs for M10.2–M10.8 (path 1).

**Stage 2 graduation validity during dispute window:** As C10 is a Stage 2 graduation gate course, the audit explicitly notes that Stage 2 graduations granted during the certification dispute window are valid. The dispute is over the QM accreditation of the course's media architecture, not over the validity of the Stage 2 graduation determinations the course produces. Stage 2 graduates from this window proceed to C11 enrollment without restriction.

---

**Audit notes version:** 1.0
**Course:** C10 Proof Threshold v2.0
**Audit date:** Sunday, April 27, 2026

Complete original C9 audit notes

# QM Audit Notes — C9 Captain's Retreat

These notes document the audit decisions and rationale captured during the C9 QM audit run. They serve as the audit trail referenced by the audit JSON output and as reviewer notes for future revisions.

---

## Audit metadata

- **Course:** C9 Bora Bora Captain's Retreat — Strategic Renewal
- **Stage:** 2 (Sailboat)
- **Catalog position:** Course 4 of 5 in Stage 2 (Stage 2 quarterly integrative review)
- **Rubric:** QM HE 7th Edition v2.0 (42 SRS / 16 Essential / 94 max points / 80-point pass threshold)
- **Audit run:** Sunday, April 26, 2026
- **Auditor:** RISER Internal QM Audit Tool v1.x
- **Build commit:** /home/claude/C9-build/ as of audit run timestamp

---

## Summary determination

**Score:** 92/94 (97.9%)
**Threshold:** 80/94 (85%)
**Pass:** YES on score
**Essential conformance:** 15/16 Essential standards conform; 1/16 (SRS 8.3) flagged conditional non-conformance
**Certification status:** **NOT CERTIFIED — pending SRS 8.3 resolution** despite score being above threshold

### Why NOT CERTIFIED despite passing score

The QM HE 7th Edition v2.0 rubric requires **all 16 Essential standards to conform** for certification. A single Essential non-conformance blocks certification regardless of total score. SRS 8.3 (multimedia accessibility) is Essential.

Two interpretations apply (see Input Map for detailed framing):
- **Strict interpretation:** SRS 8.3 expects video specs for all modules, including non-video modules. Non-conformance because M9.2–M9.8 video specs not produced.
- **Design-intent interpretation:** SRS 8.3 applies only to multimedia present. M9.2–M9.8 do not use video. Conformance.

The strict interpretation is the audit-default. C9 is therefore recorded as **NOT CERTIFIED** under the strict interpretation, but with documented dispute notes.

### Path to certification

Two paths exist:
1. **Produce video specs for M9.2–M9.8** (estimated effort: 2–3 hours per module = 14–21 additional hours of build work). This converts SRS 8.3 to unambiguous conformance.
2. **File a rubric clarification request** with QM acknowledging that SRS 8.3 design-intent applies only to multimedia present. If granted, C9 certifies on current artifacts.

The build owner has chosen path-not-yet-decided; the C9 audit JSON records both paths and the current NOT_CERTIFIED status.

---

## Per-standard audit decisions

### Standards conforming with full points (39/42)

Standards 1.1–1.8, 2.1–2.5, 3.1–3.5, 4.1–4.5, 5.1–5.4, 6.1–6.4, 7.1–7.4, 8.1, 8.2, 8.4, 8.5 all conform with full points awarded. Evidence is mapped in the Input Map; no audit-level disputes.

### Standards with conditional notes (3/42)

**SRS 1.7 — Self-introduction by instructor (1 pt):** Awarded full point. The M9.1 video specification establishes instructor presence. Note: the actual video has not yet been recorded as of audit timestamp. The spec is the artifact under audit; its production is downstream of the curriculum-design audit. This conformance approach matches C1–C8 audit precedent.

**SRS 4.5 — Copyright and licensing (2 pts):** Awarded full points. Note: licensing language references RISER Nation Maritime Academy proprietary status. If the course is later relicensed (e.g., for a partner institution), a licensing-update audit pass would be required.

**SRS 8.3 — Multimedia accessibility (3 pts):** Awarded full points under design-intent interpretation; awarded 1/3 under strict interpretation. The audit JSON records both. The C9 official record uses 2/3 (a midpoint) to flag the dispute without forcing either interpretation. **Net effect on score: -1 point** vs full conformance, producing 92/94 (97.9%) rather than 94/94 (100%).

---

## Comparison to prior course audits

| Course | Score | % | Essential | Status |
|---|---|---|---|---|
| C1 Harbor Launch | 94/94 | 100% | 16/16 | Certified |
| C2 Lighthouse Mission | 93/94 | 98.9% | 16/16 | Certified |
| C3 Compass Calibration | 94/94 | 100% | 16/16 | Certified |
| C4 First Berth Mooring | 92/94 | 97.9% | 16/16 | Certified |
| C5 Hull Inspection | 94/94 | 100% | 16/16 | Certified |
| C6 Provisioning Run | 93/94 | 98.9% | 16/16 | Certified |
| C7 Tide Reading | 94/94 | 100% | 16/16 | Certified |
| C8 Pricing Discipline | 93/94 | 98.9% | 16/16 | Certified |
| **C9 Captain's Retreat** | **92/94** | **97.9%** | **15/16 (8.3 disputed)** | **NOT CERTIFIED** |

C9 is the first course in the catalog to record NOT CERTIFIED status. The score is comparable to prior courses; the certification block is structural (Essential conformance) rather than score-based.

---

## Reviewer recommendation

The audit recommends **path 2 (rubric clarification)** rather than path 1 (produce 7 additional video specs). Rationale:

- M9.2–M9.8 are deliberately paper/template-driven (Stillwater requires non-screen activity; Open Ocean requires paper-only sessions). Adding video to these modules would corrupt the pedagogical intent.
- The pedagogical design is the *reason* video is absent. SRS 8.3 design-intent supports modules without multimedia.
- A QM clarification request documenting this design-intent rationale is the structurally correct response.

If the clarification request is denied, path 1 (produce companion video specs that complement rather than replace the paper-driven design) becomes the resolution path.

The build owner is recommended to file the clarification request before C9 deployment to learners. C9 may deploy under NOT CERTIFIED status during the clarification window — this is consistent with prior precedent in QM rubric disputes.

---

## Build owner sign-off

This audit is finalized at the build commit referenced in metadata. Subsequent edits to the C9 artifact tree require an audit re-run.

**Audit complete: Sunday, April 26, 2026**

RISER — 0 Sonars Flow Chart — Product Description + Sales Letter

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

Working lesson text. Some source claims and supporting assets remain unverified.

Identify the instrument and its stated purpose

Sonars Flow Chart is presented as a RISER Nation decision instrument focused on visual navigation and system maps. The description promises to turn noisy inputs into enforceable outputs and reduce poor decisions and regret. These are proposed benefits in sales copy, not measured results or proof of installed software. Keep the current spreadsheet assignments; product numbers in a source are not course numbers.

Sonars Flow Chart — assigned product description and sales letter

Protect attention and sequence

The first two protection claims concern avoiding busy-work and taking the right step at the right time without skipping prerequisites. Make them testable: state the intended outcome of an activity and identify the evidence required before the next stage. Activity volume alone is not progress, but necessary preparation should not be dismissed merely because it produces no immediate revenue.

Sonars Flow Chart — assigned product description and sales letter

Protect capital, morale and longer-term outcomes

The remaining protections are avoiding building before proof, rejecting almost-good distractions early and prioritizing long-term operator outcomes over short-term excitement. Define the smallest useful experiment and the reason for continuing or stopping it. Proof must be proportionate to the decision; the letter supplies no universal threshold. Avoid treating the motivational language about morale and dopamine as a clinical claim or proof that every rejected project was a distraction.

Sonars Flow Chart — assigned product description and sales letter

Record a verdict and a traceable reason

The proposed outputs begin with PASS, PAUSE or FAIL, or a state placement where applicable. The source does not define the states or thresholds. A RISER practice adaptation is to record the decision question, evidence, uncertainty and who can authorize the next action. Add the requested one-sentence reason and supporting bullets. A confident label without evidence is not an objective gate.

Sonars Flow Chart — assigned product description and sales letter

Use the metrics snapshot honestly

The letter calls for 30-, 60- and 90-day signals where applicable. Record the measure, observation period, source and missing values. Those windows are proposed reporting periods, not invented historical results or mandatory waiting periods for every decision. Compare like periods and distinguish leading indicators from actual customer outcomes.

Sonars Flow Chart — assigned product description and sales letter

Separate the next-step record from enforcement

List the unlocked next step and blocked steps, with the condition and owner for reconsidering each. The source calls this a permission system. A written record is not proof of technical access control. The lesson does not change account permissions, block a learner or execute an operational decision.

Sonars Flow Chart — assigned product description and sales letter

Recognize the missing automation contract

The fifth output is described as an automation payload using a canonical JSON schema, but no schema, field definitions, validation rules or example payload is provided. Record that dependency explicitly. A learner may draft a proposed contract labeled as an adaptation; do not call an invented schema the original or claim the integration works.

Sonars Flow Chart — assigned product description and sales letter

Evaluate the headline and governance claim

The headline asserts that most businesses fail because they say yes too often rather than because of bad ideas. No evidence supports that comparison here. The following claim reframes moving faster than validation as a governance problem rather than a marketing problem. Use it as a positioning hypothesis; governance and marketing weaknesses can coexist. Replace universal claims in actual sales copy with supported, specific observations.

Sonars Flow Chart — assigned product description and sales letter

Translate the promise for all three audiences

The letter addresses operators avoiding wasted quarters, teams or agencies seeking objective gates and audit trails, and system builders seeking something licensable and enforceable. Explain what Sonars Flow Chart would actually deliver for the selected audience. An audit trail needs inspectable records; a licensable system needs actual terms and rights; enforceability needs a defined mechanism. None is supplied merely by naming the audience.

Sonars Flow Chart — assigned product description and sales letter

Make the call to action reviewable

The source asks the reader to adopt the instrument, enforce the rule and ship only what earns permission. In this lesson, turn that into a bounded review of one proposed decision. Specify the evidence and human approval needed before a real operational change. Reading the sales letter does not adopt software, create an automation, authorize outreach or make a purchase.

Sonars Flow Chart — assigned product description and sales letter

Apply the distinctive product focus

Draw the current decision path, identify each branch and show which evidence supports moving forward. This is an authored practice exercise: the source does not supply the actual flow chart, branch conditions or decision algorithm.

Sonars Flow Chart — assigned product description and sales letter

Apply the agreed marketing lenses without inventing proof

As a RISER teaching adaptation, use the Brunson/ClickFunnels Hook, Story, Offer lens to connect a relevant opening to a truthful explanation and a concrete next step. Use the Hormozi/Acquisition.com value lens to examine the desired result, confidence in delivery, waiting time and required effort. These lenses organize the exercise; they do not establish endorsement, validate a claim or supply the missing product mechanism.

Sonars Flow Chart — assigned product description and sales letter

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Submit the evidence and preserve the limitations

Submit a one-page Sonars Flow Chart decision example with a stated question, evidence, verdict, one-sentence reason, supporting bullets, applicable metrics, next and blocked steps, and unresolved implementation dependencies. Separately revise the headline, audience promise and call to action using supportable language. Label all invented example values and retain the full original source below. No source performance result, original schema or deployed instrument has been verified by this exercise.

Sonars Flow Chart — assigned product description and sales letter

Complete original source text

Sonars Flow Chart

Visual navigation + system maps

Product Description

Sonars Flow Chart is a RISER Nation decision instrument designed to reduce bad decisions and regret. It converts noisy inputs into enforceable outputs so you scale with clarity, not chaos.

What It Protects (Doctrine Protection Mode)

* Protects attention: prevents busy-work masquerading as progress.

* Protects sequencing: Right Step / Right Time; no step-skipping.

* Protects capital: blocks build before proof.

* Protects morale: kills “almost good” distractions early.

* Protects long-term operator outcomes over short-term dopamine.

Core Outputs

* Verdict: PASS / PAUSE / FAIL (or state placement where applicable).

* Reason: one sentence + supporting bullets.

* Metrics snapshot (30/60/90-day signals where applicable).

* Unlocked next step + blocked steps (permission system).

* Automation payload: canonical JSON schema.

World-Class Sales Letter

Headline:

Most businesses don’t fail from bad ideas — they fail from saying “yes” too often.

If you're moving faster than you can validate, you don't have a marketing problem — you have a governance problem.

Sonars Flow Chart enforces permission-based building. It tells you what earns a build, what must wait, and what must die — with receipts.

Who This Is For

* Operators who refuse to waste another quarter chasing noise.

* Teams/agencies who need objective gating + audit trails.

* System builders who want something licensable and enforceable.

Call to Action

Adopt the instrument. Enforce the rule. Ship only what earns permission.

RISER — 2 Tide Lock — Product Description + Sales Letter

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

Working lesson text. Some source claims and supporting assets remain unverified.

Identify the instrument and its stated purpose

Tide Lock is presented as a RISER Nation decision instrument focused on durability lock and anti-hype confirmation. The description promises to turn noisy inputs into enforceable outputs and reduce poor decisions and regret. These are proposed benefits in sales copy, not measured results or proof of installed software. Keep the current spreadsheet assignments; product numbers in a source are not course numbers.

Tide Lock — assigned product description and sales letter

Protect attention and sequence

Tide Lock — assigned product description and sales letter

Protect capital, morale and longer-term outcomes

Tide Lock — assigned product description and sales letter

Record a verdict and a traceable reason

Tide Lock — assigned product description and sales letter

Use the metrics snapshot honestly

Tide Lock — assigned product description and sales letter

Separate the next-step record from enforcement

Tide Lock — assigned product description and sales letter

Recognize the missing automation contract

Tide Lock — assigned product description and sales letter

Evaluate the headline and governance claim

Tide Lock — assigned product description and sales letter

Translate the promise for all three audiences

The letter addresses operators avoiding wasted quarters, teams or agencies seeking objective gates and audit trails, and system builders seeking something licensable and enforceable. Explain what Tide Lock would actually deliver for the selected audience. An audit trail needs inspectable records; a licensable system needs actual terms and rights; enforceability needs a defined mechanism. None is supplied merely by naming the audience.

Tide Lock — assigned product description and sales letter

Make the call to action reviewable

Tide Lock — assigned product description and sales letter

Apply the distinctive product focus

Compare a promising result with repeated observations over an appropriate period. Record what would make the result durable and what would undermine it. This is an authored application; the source supplies no durability threshold or working lock mechanism.

Tide Lock — assigned product description and sales letter

Apply the agreed marketing lenses without inventing proof

Tide Lock — assigned product description and sales letter

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Submit the evidence and preserve the limitations

Submit a one-page Tide Lock decision example with a stated question, evidence, verdict, one-sentence reason, supporting bullets, applicable metrics, next and blocked steps, and unresolved implementation dependencies. Separately revise the headline, audience promise and call to action using supportable language. Label all invented example values and retain the full original source below. No source performance result, original schema or deployed instrument has been verified by this exercise.

Tide Lock — assigned product description and sales letter

Complete original source text

Tide Lock

Durability lock + anti-hype confirmation

Product Description

Tide Lock is a RISER Nation decision instrument designed to reduce bad decisions and regret. It converts noisy inputs into enforceable outputs so you scale with clarity, not chaos.

What It Protects (Doctrine Protection Mode)

* Protects attention: prevents busy-work masquerading as progress.

* Protects sequencing: Right Step / Right Time; no step-skipping.

* Protects capital: blocks build before proof.

* Protects morale: kills “almost good” distractions early.

* Protects long-term operator outcomes over short-term dopamine.

Core Outputs

* Verdict: PASS / PAUSE / FAIL (or state placement where applicable).

* Reason: one sentence + supporting bullets.

* Metrics snapshot (30/60/90-day signals where applicable).

* Unlocked next step + blocked steps (permission system).

* Automation payload: canonical JSON schema.

World-Class Sales Letter

Headline:

Most businesses don’t fail from bad ideas — they fail from saying “yes” too often.

If you're moving faster than you can validate, you don't have a marketing problem — you have a governance problem.

Tide Lock enforces permission-based building. It tells you what earns a build, what must wait, and what must die — with receipts.

Who This Is For

* Operators who refuse to waste another quarter chasing noise.

* Teams/agencies who need objective gating + audit trails.

* System builders who want something licensable and enforceable.

Call to Action

Adopt the instrument. Enforce the rule. Ship only what earns permission.

RISER — 3 Shark Radar — Product Description + Sales Letter

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

Working lesson text. Some source claims and supporting assets remain unverified.

Identify the instrument and its stated purpose

Shark Radar is presented as a RISER Nation decision instrument focused on risk, competition and platform threat detection. The description promises to turn noisy inputs into enforceable outputs and reduce poor decisions and regret. These are proposed benefits in sales copy, not measured results or proof of installed software. Keep the current spreadsheet assignments; product numbers in a source are not course numbers.

Shark Radar — assigned product description and sales letter

Protect attention and sequence

Shark Radar — assigned product description and sales letter

Protect capital, morale and longer-term outcomes

Shark Radar — assigned product description and sales letter

Record a verdict and a traceable reason

Shark Radar — assigned product description and sales letter

Use the metrics snapshot honestly

Shark Radar — assigned product description and sales letter

Separate the next-step record from enforcement

Shark Radar — assigned product description and sales letter

Recognize the missing automation contract

Shark Radar — assigned product description and sales letter

Evaluate the headline and governance claim

Shark Radar — assigned product description and sales letter

Translate the promise for all three audiences

The letter addresses operators avoiding wasted quarters, teams or agencies seeking objective gates and audit trails, and system builders seeking something licensable and enforceable. Explain what Shark Radar would actually deliver for the selected audience. An audit trail needs inspectable records; a licensable system needs actual terms and rights; enforceability needs a defined mechanism. None is supplied merely by naming the audience.

Shark Radar — assigned product description and sales letter

Make the call to action reviewable

Shark Radar — assigned product description and sales letter

Apply the distinctive product focus

List a relevant competitor, platform dependency and operating risk; attach dated evidence and name an owner for reviewing each. Distinguish an observed event from a possible threat. This authored example does not establish that the advertised product detects threats automatically.

Shark Radar — assigned product description and sales letter

Apply the agreed marketing lenses without inventing proof

Shark Radar — assigned product description and sales letter

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Submit the evidence and preserve the limitations

Submit a one-page Shark Radar decision example with a stated question, evidence, verdict, one-sentence reason, supporting bullets, applicable metrics, next and blocked steps, and unresolved implementation dependencies. Separately revise the headline, audience promise and call to action using supportable language. Label all invented example values and retain the full original source below. No source performance result, original schema or deployed instrument has been verified by this exercise.

Shark Radar — assigned product description and sales letter

Complete original source text

Shark Radar

Risk + competition + platform threat detection

Product Description

Shark Radar is a RISER Nation decision instrument designed to reduce bad decisions and regret. It converts noisy inputs into enforceable outputs so you scale with clarity, not chaos.

What It Protects (Doctrine Protection Mode)

* Protects attention: prevents busy-work masquerading as progress.

* Protects sequencing: Right Step / Right Time; no step-skipping.

* Protects capital: blocks build before proof.

* Protects morale: kills “almost good” distractions early.

* Protects long-term operator outcomes over short-term dopamine.

Core Outputs

* Verdict: PASS / PAUSE / FAIL (or state placement where applicable).

* Reason: one sentence + supporting bullets.

* Metrics snapshot (30/60/90-day signals where applicable).

* Unlocked next step + blocked steps (permission system).

* Automation payload: canonical JSON schema.

World-Class Sales Letter

Headline:

Most businesses don’t fail from bad ideas — they fail from saying “yes” too often.

If you're moving faster than you can validate, you don't have a marketing problem — you have a governance problem.

Shark Radar enforces permission-based building. It tells you what earns a build, what must wait, and what must die — with receipts.

Who This Is For

* Operators who refuse to waste another quarter chasing noise.

* Teams/agencies who need objective gating + audit trails.

* System builders who want something licensable and enforceable.

Call to Action

Adopt the instrument. Enforce the rule. Ship only what earns permission.

RISER — 4 Anchor Point — Product Description + Sales Letter

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

Working lesson text. Some source claims and supporting assets remain unverified.

Identify the instrument and its stated purpose

Anchor Point is presented as a RISER Nation decision instrument focused on north star discipline and anti-drift enforcement. The description promises to turn noisy inputs into enforceable outputs and reduce poor decisions and regret. These are proposed benefits in sales copy, not measured results or proof of installed software. Keep the current spreadsheet assignments; product numbers in a source are not course numbers.

Anchor Point — assigned product description and sales letter

Protect attention and sequence

Anchor Point — assigned product description and sales letter

Protect capital, morale and longer-term outcomes

Anchor Point — assigned product description and sales letter

Record a verdict and a traceable reason

Anchor Point — assigned product description and sales letter

Use the metrics snapshot honestly

Anchor Point — assigned product description and sales letter

Separate the next-step record from enforcement

Anchor Point — assigned product description and sales letter

Recognize the missing automation contract

Anchor Point — assigned product description and sales letter

Evaluate the headline and governance claim

Anchor Point — assigned product description and sales letter

Translate the promise for all three audiences

The letter addresses operators avoiding wasted quarters, teams or agencies seeking objective gates and audit trails, and system builders seeking something licensable and enforceable. Explain what Anchor Point would actually deliver for the selected audience. An audit trail needs inspectable records; a licensable system needs actual terms and rights; enforceability needs a defined mechanism. None is supplied merely by naming the audience.

Anchor Point — assigned product description and sales letter

Make the call to action reviewable

Anchor Point — assigned product description and sales letter

Apply the distinctive product focus

Write the objective, compare the proposed action with it and record why a deviation should be accepted or rejected. Define the outcome measure rather than assuming everyone shares the same North Star. The source does not provide an enforcement rule or a completed alignment assessment.

Anchor Point — assigned product description and sales letter

Apply the agreed marketing lenses without inventing proof

Anchor Point — assigned product description and sales letter

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Submit the evidence and preserve the limitations

Submit a one-page Anchor Point decision example with a stated question, evidence, verdict, one-sentence reason, supporting bullets, applicable metrics, next and blocked steps, and unresolved implementation dependencies. Separately revise the headline, audience promise and call to action using supportable language. Label all invented example values and retain the full original source below. No source performance result, original schema or deployed instrument has been verified by this exercise.

Anchor Point — assigned product description and sales letter

Complete original source text

Anchor Point

North Star discipline + anti-drift enforcement

Product Description

Anchor Point is a RISER Nation decision instrument designed to reduce bad decisions and regret. It converts noisy inputs into enforceable outputs so you scale with clarity, not chaos.

What It Protects (Doctrine Protection Mode)

* Protects attention: prevents busy-work masquerading as progress.

* Protects sequencing: Right Step / Right Time; no step-skipping.

* Protects capital: blocks build before proof.

* Protects morale: kills “almost good” distractions early.

* Protects long-term operator outcomes over short-term dopamine.

Core Outputs

* Verdict: PASS / PAUSE / FAIL (or state placement where applicable).

* Reason: one sentence + supporting bullets.

* Metrics snapshot (30/60/90-day signals where applicable).

* Unlocked next step + blocked steps (permission system).

* Automation payload: canonical JSON schema.

World-Class Sales Letter

Headline:

Most businesses don’t fail from bad ideas — they fail from saying “yes” too often.

If you're moving faster than you can validate, you don't have a marketing problem — you have a governance problem.

Anchor Point enforces permission-based building. It tells you what earns a build, what must wait, and what must die — with receipts.

Who This Is For

* Operators who refuse to waste another quarter chasing noise.

* Teams/agencies who need objective gating + audit trails.

* System builders who want something licensable and enforceable.

Call to Action

Adopt the instrument. Enforce the rule. Ship only what earns permission.

RISER — 5 Portfolio Governor — Product Description + Sales Letter

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

Working lesson text. Some source claims and supporting assets remain unverified.

Identify the instrument and its stated purpose

Portfolio Governor is presented as a RISER Nation decision instrument focused on capacity, focus and kill/park/scale authority. The description promises to turn noisy inputs into enforceable outputs and reduce poor decisions and regret. These are proposed benefits in sales copy, not measured results or proof of installed software. Keep the current spreadsheet assignments; product numbers in a source are not course numbers.

Portfolio Governor — assigned product description and sales letter

Protect attention and sequence

Portfolio Governor — assigned product description and sales letter

Protect capital, morale and longer-term outcomes

Portfolio Governor — assigned product description and sales letter

Record a verdict and a traceable reason

Portfolio Governor — assigned product description and sales letter

Use the metrics snapshot honestly

Portfolio Governor — assigned product description and sales letter

Separate the next-step record from enforcement

Portfolio Governor — assigned product description and sales letter

Recognize the missing automation contract

Portfolio Governor — assigned product description and sales letter

Evaluate the headline and governance claim

Portfolio Governor — assigned product description and sales letter

Translate the promise for all three audiences

The letter addresses operators avoiding wasted quarters, teams or agencies seeking objective gates and audit trails, and system builders seeking something licensable and enforceable. Explain what Portfolio Governor would actually deliver for the selected audience. An audit trail needs inspectable records; a licensable system needs actual terms and rights; enforceability needs a defined mechanism. None is supplied merely by naming the audience.

Portfolio Governor — assigned product description and sales letter

Make the call to action reviewable

Portfolio Governor — assigned product description and sales letter

Apply the distinctive product focus

Compare initiatives against available capacity and evidence. Recommend discontinue, park or expand with a reason, an accountable owner and a review date. These are authored planning steps; the sales letter does not grant authority to delete projects or spend money. Keep its internal label 5 visible.

Portfolio Governor — assigned product description and sales letter

Apply the agreed marketing lenses without inventing proof

Portfolio Governor — assigned product description and sales letter

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Submit the evidence and preserve the limitations

Submit a one-page Portfolio Governor decision example with a stated question, evidence, verdict, one-sentence reason, supporting bullets, applicable metrics, next and blocked steps, and unresolved implementation dependencies. Separately revise the headline, audience promise and call to action using supportable language. Label all invented example values and retain the full original source below. No source performance result, original schema or deployed instrument has been verified by this exercise.

Portfolio Governor — assigned product description and sales letter

Complete original source text

# 5 -🗃️Portfolio Governor

Capacity + focus + kill/park/scale authority

Product Description

Portfolio Governor is a RISER Nation decision instrument designed to reduce bad decisions and regret. It converts noisy inputs into enforceable outputs so you scale with clarity, not chaos.

What It Protects (Doctrine Protection Mode)

* Protects attention: prevents busy-work masquerading as progress.

* Protects sequencing: Right Step / Right Time; no step-skipping.

* Protects capital: blocks build before proof.

* Protects morale: kills “almost good” distractions early.

* Protects long-term operator outcomes over short-term dopamine.

Core Outputs

* Verdict: PASS / PAUSE / FAIL (or state placement where applicable).

* Reason: one sentence + supporting bullets.

* Metrics snapshot (30/60/90-day signals where applicable).

* Unlocked next step + blocked steps (permission system).

* Automation payload: canonical JSON schema.

World-Class Sales Letter

Headline:

Most businesses don’t fail from bad ideas — they fail from saying “yes” too often.

If you're moving faster than you can validate, you don't have a marketing problem — you have a governance problem.

Portfolio Governor enforces permission-based building. It tells you what earns a build, what must wait, and what must die — with receipts.

Who This Is For

* Operators who refuse to waste another quarter chasing noise.

* Teams/agencies who need objective gating + audit trails.

* System builders who want something licensable and enforceable.

Call to Action

Adopt the instrument. Enforce the rule. Ship only what earns permission.

RISER — 6 Buoy Builder — Product Description + Sales Letter

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

Working lesson text. Some source claims and supporting assets remain unverified.

Identify the instrument and its stated purpose

Buoy Builder is presented as a RISER Nation decision instrument focused on keyword buoys and long-tail node expansion. The description promises to turn noisy inputs into enforceable outputs and reduce poor decisions and regret. These are proposed benefits in sales copy, not measured results or proof of installed software. Keep the current spreadsheet assignments; product numbers in a source are not course numbers.

Buoy Builder — assigned product description and sales letter

Protect attention and sequence

Buoy Builder — assigned product description and sales letter

Protect capital, morale and longer-term outcomes

Buoy Builder — assigned product description and sales letter

Record a verdict and a traceable reason

Buoy Builder — assigned product description and sales letter

Use the metrics snapshot honestly

Buoy Builder — assigned product description and sales letter

Separate the next-step record from enforcement

Buoy Builder — assigned product description and sales letter

Recognize the missing automation contract

Buoy Builder — assigned product description and sales letter

Evaluate the headline and governance claim

Buoy Builder — assigned product description and sales letter

Translate the promise for all three audiences

The letter addresses operators avoiding wasted quarters, teams or agencies seeking objective gates and audit trails, and system builders seeking something licensable and enforceable. Explain what Buoy Builder would actually deliver for the selected audience. An audit trail needs inspectable records; a licensable system needs actual terms and rights; enforceability needs a defined mechanism. None is supplied merely by naming the audience.

Buoy Builder — assigned product description and sales letter

Make the call to action reviewable

Buoy Builder — assigned product description and sales letter

Apply the distinctive product focus

Choose a relevant seed topic and propose narrower questions that serve distinct user needs. Label them as hypotheses until supported by research. This authored application does not supply search volumes, prove ranking opportunity or authorize mass publication of repetitive pages.

Buoy Builder — assigned product description and sales letter

Apply the agreed marketing lenses without inventing proof

Buoy Builder — assigned product description and sales letter

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Submit the evidence and preserve the limitations

Submit a one-page Buoy Builder decision example with a stated question, evidence, verdict, one-sentence reason, supporting bullets, applicable metrics, next and blocked steps, and unresolved implementation dependencies. Separately revise the headline, audience promise and call to action using supportable language. Label all invented example values and retain the full original source below. No source performance result, original schema or deployed instrument has been verified by this exercise.

Buoy Builder — assigned product description and sales letter

Complete original source text

Buoy Builder

Keyword buoys + long-tail node expansion

Product Description

Buoy Builder is a RISER Nation decision instrument designed to reduce bad decisions and regret. It converts noisy inputs into enforceable outputs so you scale with clarity, not chaos.

What It Protects (Doctrine Protection Mode)

* Protects attention: prevents busy-work masquerading as progress.

* Protects sequencing: Right Step / Right Time; no step-skipping.

* Protects capital: blocks build before proof.

* Protects morale: kills “almost good” distractions early.

* Protects long-term operator outcomes over short-term dopamine.

Core Outputs

* Verdict: PASS / PAUSE / FAIL (or state placement where applicable).

* Reason: one sentence + supporting bullets.

* Metrics snapshot (30/60/90-day signals where applicable).

* Unlocked next step + blocked steps (permission system).

* Automation payload: canonical JSON schema.

World-Class Sales Letter

Headline:

Most businesses don’t fail from bad ideas — they fail from saying “yes” too often.

If you're moving faster than you can validate, you don't have a marketing problem — you have a governance problem.

Buoy Builder enforces permission-based building. It tells you what earns a build, what must wait, and what must die — with receipts.

Who This Is For

* Operators who refuse to waste another quarter chasing noise.

* Teams/agencies who need objective gating + audit trails.

* System builders who want something licensable and enforceable.

Call to Action

Adopt the instrument. Enforce the rule. Ship only what earns permission.

RISER — 7 Rigging Forge — Product Description + Sales Letter

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

Working lesson text. Some source claims and supporting assets remain unverified.

Identify the instrument and its stated purpose

Rigging Forge is presented as a RISER Nation decision instrument focused on packaging, funnel rigging and deployment specifications. The description promises to turn noisy inputs into enforceable outputs and reduce poor decisions and regret. These are proposed benefits in sales copy, not measured results or proof of installed software. Keep the current spreadsheet assignments; product numbers in a source are not course numbers.

Rigging Forge — assigned product description and sales letter

Protect attention and sequence

Rigging Forge — assigned product description and sales letter

Protect capital, morale and longer-term outcomes

Rigging Forge — assigned product description and sales letter

Record a verdict and a traceable reason

Rigging Forge — assigned product description and sales letter

Use the metrics snapshot honestly

Rigging Forge — assigned product description and sales letter

Separate the next-step record from enforcement

Rigging Forge — assigned product description and sales letter

Recognize the missing automation contract

Rigging Forge — assigned product description and sales letter

Evaluate the headline and governance claim

Rigging Forge — assigned product description and sales letter

Translate the promise for all three audiences

The letter addresses operators avoiding wasted quarters, teams or agencies seeking objective gates and audit trails, and system builders seeking something licensable and enforceable. Explain what Rigging Forge would actually deliver for the selected audience. An audit trail needs inspectable records; a licensable system needs actual terms and rights; enforceability needs a defined mechanism. None is supplied merely by naming the audience.

Rigging Forge — assigned product description and sales letter

Make the call to action reviewable

Rigging Forge — assigned product description and sales letter

Apply the distinctive product focus

Map the offer, page sequence, promised deliverables and acceptance checks before deployment. Identify missing specifications and delivery dependencies. The source supplies no actual deployment specification or functioning funnel. Its body says #37 while the inventory title says 7; retain both labels as a source discrepancy, not a reason to renumber the current course.

Rigging Forge — assigned product description and sales letter

Apply the agreed marketing lenses without inventing proof

Rigging Forge — assigned product description and sales letter

ClickFunnels — Hook, Story, Offer · Acquisition.com — Pricing and Value Checklist

Submit the evidence and preserve the limitations

Submit a one-page Rigging Forge decision example with a stated question, evidence, verdict, one-sentence reason, supporting bullets, applicable metrics, next and blocked steps, and unresolved implementation dependencies. Separately revise the headline, audience promise and call to action using supportable language. Label all invented example values and retain the full original source below. No source performance result, original schema or deployed instrument has been verified by this exercise.

Rigging Forge — assigned product description and sales letter

Complete original source text

#37 - 🔗Rigging Forge

Packaging + funnel rigging + deployment specs

Product Description

Rigging Forge is a RISER Nation decision instrument designed to reduce bad decisions and regret. It converts noisy inputs into enforceable outputs so you scale with clarity, not chaos.

What It Protects (Doctrine Protection Mode)

* Protects attention: prevents busy-work masquerading as progress.

* Protects sequencing: Right Step / Right Time; no step-skipping.

* Protects capital: blocks build before proof.

* Protects morale: kills “almost good” distractions early.

* Protects long-term operator outcomes over short-term dopamine.

Core Outputs

* Verdict: PASS / PAUSE / FAIL (or state placement where applicable).

* Reason: one sentence + supporting bullets.

* Metrics snapshot (30/60/90-day signals where applicable).

* Unlocked next step + blocked steps (permission system).

* Automation payload: canonical JSON schema.

World-Class Sales Letter

Headline:

Most businesses don’t fail from bad ideas — they fail from saying “yes” too often.

If you're moving faster than you can validate, you don't have a marketing problem — you have a governance problem.

Rigging Forge enforces permission-based building. It tells you what earns a build, what must wait, and what must die — with receipts.

Who This Is For

* Operators who refuse to waste another quarter chasing noise.

* Teams/agencies who need objective gating + audit trails.

* System builders who want something licensable and enforceable.

Call to Action

Adopt the instrument. Enforce the rule. Ship only what earns permission.

QM-Audit-C12.json

Assigned lessons: 03.3, 06.2, 07.1, 11.2, 12.2

Draft teaching and complete available source appendix; not a claim of full semantic coverage.

Assigned original documents

QM-Audit-C12.json — original source

Lesson narration

Read the internal Content Engine audit in context

The source describes legacy C12 Content Engine, Stage 3, build v2.0, with an April 28, 2026 internal audit. It labels the review as built from QM Higher Education seventh edition version 2.0 and says partial scores identify work for v2.1. These are claims about an internal record, not evidence of external certification. Preserve this source’s legacy numbering without changing the twelve-course spreadsheet assignments.

Reconcile the standard count and totals

The source says forty-two standards and a score of eighty-nine out of ninety-four, or 94.7 percent. Its actual forty-one rows and eight group subtotals instead add to ninety-five out of 101, about 94.06 percent. Six rows lose one point each. Subtracting six from the claimed ninety-four maximum would give eighty-eight, not eighty-nine. Keep the original record visible while explaining these inconsistencies; do not silently repair a total and declare the audit passed.

Read all eight group subtotals

The source’s group scores are seventeen of eighteen for overview, fifteen of fifteen for objectives, twelve of thirteen for assessment, twelve of twelve for materials, ten of eleven for interaction, nine of ten for technology, nine of ten for support and eleven of twelve for accessibility. Each group agrees with its own rows, but their sum disagrees with the overall summary. This is why a review should verify both local subtotals and the aggregate.

Separate essential flags from the claim that every essential is met

The internal data flags sixteen essentials with forty-eight possible and forty-seven awarded points. Only fifteen receive full points; 8.2 is partial. Five other three-point rows are not flagged essential: 2.3, 2.4, 2.5, 5.3 and 7.2. Its MEETS_THRESHOLD and QM-ready labels therefore require reconciliation with the applicable standard and official process, not acceptance based on the high percentage.

Preserve all six proposed remediation actions

The source proposes an instructor introduction, learner-facing progress instructions, explicit human-review turnaround times, a learner privacy explanation, an accessibility-policy link and tool-specific accessibility information. The proposed timing examples are forty-eight hours for M12.4, seventy-two hours for M12.7 and five business days for M12.8. These are recommendations, not service commitments already verified or changes made by this lesson.

Question the score-parity explanation without assuming intent

The scoring philosophy says it avoids matching a predicted score, while the summary calls parity with C11 intentional because both inherit similar documentation gaps. Record that tension and request an evidence-based reconciliation. Shared templates can produce similar issues, but they do not justify choosing a score in advance. The record alone does not establish dishonesty or an official result.

Keep the marketing figures as unverified source claims

The source cites 6.6 percent LinkedIn carousel engagement, seventy percent AI-search share and seven hundred million weekly ChatGPT users, a 3.1-times FAQ-schema extraction rate, a 2.7-times rate for a forty-word answer rule, and twelve percent overlap between ChatGPT citations and Google’s top ten. No underlying study data is supplied in this audit. Do not teach those numbers as current universal benchmarks or claim a schema or word count guarantees visibility.

Keep the workbook and JSON connected

The workbook contains Summary, Standards Detail, Evidence and v2.1 Remediation sheets, with 518 populated cells and no formulas, comments or cell hyperlinks. All forty-one shared criterion, score, essential, note and evidence records match the JSON, as do the six remediation recommendations. Matching representations preserve the record; they do not resolve its shared errors or verify the cited build artifacts.

Internal row 1.1: Test the start-here path

Follow the entry instructions, find the eight deliverables and test every branch of the module map. A diagram should have an equivalent readable route rather than being the only way to navigate. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: 00_Course-Overview/README.md provides primary entry with Start-here framing, conceptual hinge (sporadic-vs-engine table), 8 deliverables, doctrines, and links to all folder-00 documents. Module-Map.md provides Mermaid flowchart navigation across M12.1-M12.8. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 1.2: Explain the production-system journey

Show how channel commitment leads to an operating content process across eight modules and five to six proposed weeks. Identify the three human gates and final validator before work begins; the source duration is not our project runtime. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: README.md and Course-Syllabus.md establish purpose (Stage 3 second-course transition: from channel commitment to engine production) and structure (8 modules across 5-6 weeks, 8 deliverables, 3 HITL gates, course-completion validator gate). Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 1.3: State communication responsibilities

Explain where cohort discussion occurs, how submissions reach a human reviewer and what communication belongs at each gate. Test the actual channels instead of relying only on a folder of discussion prompts. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Folder 08 cohort discussion prompts establish discussion expectations. Course-Syllabus.md describes HITL submission flow. SOPs specify communication points per gate. Its reviewer note is: Substantive. These remain attributed source findings pending verification of the cited artifacts.

Internal row 1.4: Verify inherited policies

Check the Build 6 prerequisites, recovery policy carried from C11 and the Engine Beats Inspiration doctrine. A policy inherited from a course shell still needs to be accessible and applicable in the delivered course. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Prerequisites.md and Course-Syllabus.md state Build 6 prerequisite policies. HITL gate policies, channel-commitment-recovery policy (carried from C11), and Engine Beats Inspiration doctrine made explicit. Its reviewer note is: Course-specific covered; institution-wide inherited from course shell. These remain attributed source findings pending verification of the cited artifacts.

Internal row 1.5: Check the required tools

Identify the capture, scheduling and channel-analytics tools, access requirements and instructions. Verify that the learner can complete the steps with the tools actually supplied. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Prerequisites.md specifies channel-platform analytics, capture system tooling, scheduling tools. SOPs walk through tooling per stage. Folder 04 README documents Build 6 platform requirements. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 1.6: Verify prerequisite artifacts

The source requires C11 completion and a channel-commitment artifact. Use the forward-carry map to show which prior work is needed and what happens when it is absent; a prerequisite label does not verify completion. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Prerequisites.md is dedicated to this. C11 completion required (channel commitment artifact). Stage 3 forward-carry-map in folder 02 makes prerequisite artifacts explicit. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 1.7: Demonstrate the necessary technical skills

Check that learners can install or access their capture system, operate scheduling tools and use AI assistance appropriately. The capture-installation SOP should give a reproducible route, not merely name a tool. The internal record assigns 1 of 1 points and essential flag false. Its evidence statement is: Prerequisites.md addresses capture-system installation, calendar/scheduling tool literacy, AI-assistance tool familiarity. SOP-1 walks through capture system installation. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 1.8: Turn instructor identity into a real introduction

A reviewer identifier in a database or a coach-role description is not a welcoming introduction. The recorded remediation is to supply a template and have the actual instructor complete it for the cohort. The internal record assigns 1 of 2 points and essential flag false. Its evidence statement is: HITL instructor identification structure exists in schema. Course-Syllabus.md references the Stage 3 cohort coach role. Per-instructor self-introduction is not a C12-specific artifact; it is inherited from the course shell template. Its reviewer note is: PARTIAL: Course-shell pattern is documented but a C12-specific instructor introduction artifact is not generated by this build. Recommend v2.1: include an instructor-introduction template in folder 00 that the assigned instructor populates per cohort. These remain attributed source findings pending verification of the cited artifacts.

Internal row 1.9: Make the learner introduction relevant

Use the arrival discussion to connect the learner’s current inspiration-driven habits with the channel commitment from C11. Participation should help the cohort understand real starting conditions, not force disclosure of confidential client information. The internal record assigns 1 of 1 points and essential flag false. Its evidence statement is: Folder 08 community prompts include a cohort-arrival prompt at C12 entry framed around inspiration-vs-engine self-positioning, drawing on each learner's C11 channel commitment. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 2.1: Define the eight observable outcomes

The source verbs are audit, install, construct, author, plan, map, operationalize and attest. For each, specify the resulting artifact and the criterion that demonstrates achievement. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Learning-Outcomes.md defines 8 CLOs with measurable verbs (audit, install, construct, author, plan, map, operationalize, attest). Each verifiable through specific deliverables. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 2.2: Connect module and course outcomes

Trace each module-level objective to a course-level objective and its deliverable rubric. Identify any objective that lacks either an activity or a way to judge the submitted work. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Learning-Outcomes.md provides per-module MLOs mapped to specific CLOs. Each MLO is operationalized through a deliverable rubric. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 2.3: Keep objectives visible to the learner

Restating the objective at a lesson’s opening helps explain the purpose of the work. Confirm that the wording is learner-centered, understandable and specific enough to assess. The internal record assigns 3 of 3 points and essential flag false. Its evidence statement is: Learning-Outcomes.md uses learner-perspective phrasing, located in folder 00, and each module lesson opens by restating the relevant MLOs. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 2.4: Make the activity-to-deliverable relationship explicit

Use the syllabus mapping to explain how each activity builds the submission. A learner should understand why the activity matters rather than simply completing a sequence of tasks. The internal record assigns 3 of 3 points and essential flag false. Its evidence statement is: Course-Syllabus.md table maps CLO/MLO to activities to deliverable per module. Each module lesson opens with the relevant MLO and ties activities to deliverable. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 2.5: Check the level of the work

The record describes a progression from analysis through application to creation for Stage 3. Verify the required prerequisites and actual complexity; naming Bloom levels does not establish appropriate difficulty. The internal record assigns 3 of 3 points and essential flag false. Its evidence statement is: MLOs follow Bloom's taxonomy progression (analyze to apply to create) appropriate to a Stage 3 production-systematization course. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 3.1: Explain the four capstone dimensions

The proposed attestation weights coherence at thirty-five percent, voice at twenty, doctrine at twenty-five and forward feasibility at twenty. These sum to one hundred. Explain what evidence each dimension evaluates and test scoring consistency before relying on an automated judgment. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Each of 8 deliverables maps to one or more MLOs. M12.8 attestation assessed via Opus 4.7 validator with 4 weighted dimensions (coherence 35%, voice 20%, doctrine 25%, forward feasibility 20%) matching CLO 8. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 3.2: Make the completion rule visible

The source names a completion function and a composite threshold of at least eighty-five. Explain the other gate conditions and whether any essential requirement can block completion despite a passing average. A function name is not a tested implementation. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Course-Syllabus.md states completion criteria. check_c12_completion function in folder 04 codifies grading programmatically. Validator threshold (composite >=85) explicit. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 3.3: Use descriptive criteria in every review

Compare the reviewer prompts, worksheet rubrics and capstone criteria for consistency. Give learners examples of the evidence needed for each judgment and a useful recovery action when the work does not yet meet it. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Each reviewer prompt (folder 03) provides explicit evaluation criteria with scoring formulas. Deliverable rubrics in folder 02 worksheets provide scoring criteria. Opus validator provides per-dimension scoring rubric. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 3.4: Vary and sequence the evidence

The course progresses from reflection to construction, authored work, planning, operational output and final attestation. Check that each form serves the objective and that later work depends only on artifacts the learner has been instructed to produce. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Sequenced from M12.1 reflection through M12.8 capstone. Varied: reflective, structural construction, rubric-scored authoring, plan production, operational deliverable, multi-dimensional validator-scored attestation. Stage 3 level. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 3.5: Show learners their actual progress

Backend records and rapid model feedback do not guarantee that a learner can see progress. The source identifies a missing learner-facing progress explanation; specify how to see completed modules, pending reviews, required revisions and the next action. The internal record assigns 1 of 2 points and essential flag false. Its evidence statement is: Reviewer turnaround per module is fast (LLM-based). check_c12_completion returns module-by-module status. Backend tracking in stage_3_progress schema. Its reviewer note is: PARTIAL: Backend tracking exists but a learner-facing progress visualization/dashboard is not specified in C12 artifacts. Recommend v2.1: add 'How to track your progress' section to Course-Syllabus.md describing the learner-side progress UI. These remain attributed source findings pending verification of the cited artifacts.

Internal row 4.1: Inventory the real instructional assets

The record names eight lesson files plus one video specification, fifteen resources, four cases, six prompts, four SOPs and implementation files. Verify those assets and their links; a video specification is not a finished video and a file count does not establish teaching quality. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: 9 module lesson files (8 lessons + 1 video spec), 15 folder-02 resources, 4 case studies, 6 reviewer prompts, 4 SOPs, folder-04 schema/functions/RLS all map to MLOs. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 4.2: Link resources where they are used

Each module should explain which resource to open and what to do with it, supported by the folder map and stepwise SOPs. Confirm that resource links resolve to the assigned material, not similarly titled files. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Each module lesson directs to specific folder-02 resources. SOPs in folder 05 walk through resource use stepwise. Folder 02 README maps resources to modules. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 4.3: Model honest attribution and disclosure

Distinguish a composite case from an actual named case and explain how AI assistance was used. Verify the underlying studies before calling a statistic empirical evidence; an audit’s citation to another file does not independently establish the finding. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: M12.3 cites 2026 empirical findings (LinkedIn 360Brew, AEO mechanics, FAQPage schema rate, citation overlap data). Case studies framed as composites or named honestly. Failure case study explicitly named as composite. AI-assistance disclosure discipline modeled in M12.7. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 4.4: Check the claimed current marketing benchmarks

A date in a filename does not make a benchmark current or applicable. Preserve the source’s figures as attributed claims, locate their underlying studies and check sample, metric, date and comparison before teaching them as facts. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: M12.3, M12.4, M12.7 include 2026-current research (LinkedIn document carousels 6.6% engagement, ChatGPT 70% AI search share/700M weekly users, FAQPage schema 3.1x extraction rate, 40-word answer rule 2.7x rate, 12% citation overlap between ChatGPT and Google top-10). AEO-Extraction-Patterns-2026.md and Channel-Format-Quick-Reference-2026.md dated and current. Its reviewer note is: Direct evidence with explicit 2026 currency. These remain attributed source findings pending verification of the cited artifacts.

Internal row 4.5: Use format variety for a learning purpose

The record lists prose, video plans, templates, worksheets, references, three success cases, one failure case, five reviewer prompts, one validator, SOPs and database artifacts. Explain why each helps the learner and verify that the actual asset exists. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Lesson markdown, video specs, templates, worksheets, references, case studies (3 success + 1 failure), system prompts (5 reviewers + 1 validator), SOPs, schema/SQL, RLS policies, functions. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 5.1: Connect practice to operational evidence

Capture practice, a format library, a production calendar, a repurposing map and an eight-piece backlog should demonstrate the intended skills. Evaluate whether these artifacts can actually be used, rather than accepting a completed template as sufficient. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Each module's activities directly produce the deliverable measuring the MLO. Capture practice, format library construction, calendar drafting, repurposing map, and 8-piece backlog all directly produce evidence of MLO achievement. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 5.2: Keep AI, instructor and peer interaction distinct

The design proposes AI feedback, human gates at M12.4, M12.7 and M12.8, and cohort discussion. The predicted-drought paragraph and forward statement require the learner to synthesize the plan. An AI conversation does not substitute automatically for the promised instructor interaction. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Reviewer prompts provide LLM interaction. HITL gates at M12.4, M12.7, M12.8 provide instructor interaction. Folder 08 cohort discussion. Predicted-drought paragraph and forward statement in M12.8 require active synthesis. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 5.3: Publish a realistic review-service policy

The source identifies missing turnaround commitments. State response windows, business-day treatment, escalation and what happens when a reviewer is unavailable. Proposed timing in the remediation list is not evidence of a service already operating. The internal record assigns 2 of 3 points and essential flag false. Its evidence statement is: Course-Syllabus.md describes HITL pass timing for M12.4, M12.7, M12.8. Reviewer-vs-instructor escalation paths documented in SOPs. Its reviewer note is: PARTIAL: Interaction structure documented but specific SLA commitments (e.g., 48-hour HITL turnaround) are not explicitly stated. Recommend v2.1: add explicit SLA commitments to Course-Syllabus.md. These remain attributed source findings pending verification of the cited artifacts.

Internal row 5.4: Explain what interaction is required

Use the syllabus and SOPs to distinguish required submissions and discussions from optional activities. Make expectations and alternatives visible before they affect the completion decision. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Course-Syllabus.md states learner-side interaction requirements. SOPs operationalize per module. Cohort discussion participation expectations in folder 08. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 6.1: Match a tool to the evaluation task

The record proposes Sonnet 4.6 for routine reviews and Opus 4.7 for the capstone. Treat those as source specifications, not confirmed current availability or evidence that they reliably perform the review. Validate the actual configuration against representative work. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Build 6 supports all 8 deliverables. Reviewer LLMs (Sonnet 4.6 for M12.2-M12.7, Opus 4.7 for M12.8 course-completion validator) matched to evaluation complexity. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 6.2: Test the review loop

The described verdicts are REVISE, PASS and REJECT, with structured reasons and a human-review interface. Verify that learners receive understandable feedback, can correct the work and can tell a model recommendation from a final human decision. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Reviewer interaction provides immediate substantive feedback with REVISE/PASS/REJECT verdicts and structured reasoning. HITL UI surfaces output to instructor and back. Cohort discussion surface enables peer engagement. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 6.3: Use technical variety only where it helps

The design lists Build 6, multiple models, Supabase, PL/pgSQL and channel or authoring tools. Explain the purpose of each and test the handoffs. The presence of different technologies does not itself demonstrate a useful or functioning learning experience. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Build 6 platform, multiple LLM models (Sonnet 4.6 for routine review + Opus 4.7 for capstone validation), Supabase database with PL/pgSQL, channel-platform tools, AI-assistance tools (M12.7). Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 6.4: Provide a learner-facing privacy explanation

Database row-level security and a confidentiality case are not substitutes for explaining what information is collected, who can see it and how it is protected. Include relevant third-party data handling rather than treating platform privacy as entirely someone else’s responsibility. The internal record assigns 1 of 2 points and essential flag false. Its evidence statement is: RLS policies in folder 04 codify student data privacy at the database level. Channel-platform privacy is platform's responsibility. Confidentiality protocol for client-data students (e.g., Priya case study) modeled in editorial standards. Its reviewer note is: PARTIAL: Backend RLS exists and confidentiality is modeled in case studies but learner-facing privacy disclosure is not present. Recommend v2.1: add a learner-facing data/privacy section to Prerequisites.md. These remain attributed source findings pending verification of the cited artifacts.

Internal row 7.1: Test support and escalation

Verify access to platform support, prompt-failure escalation, human review and the inspiration-drought guide. Explain which route fits a technical fault, an assessment issue or difficulty maintaining production. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Build 6 platform support is described. Reviewer prompt failure escalation paths in SOPs. HITL escalation path documented. Inspiration-Drought-Survival-Guide.md provides student-side troubleshooting. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 7.2: Make the accommodation route explicit

The source acknowledges that institutional accessibility links are inherited rather than supplied in C12 itself. Verify that a learner can find the actual policy and request process from this course. The internal record assigns 2 of 3 points and essential flag false. Its evidence statement is: Pattern carried from C1-C11 — institutional accessibility policies linked from course shell. Its reviewer note is: PARTIAL: Course-shell pattern but no C12-specific link or note. Recommend v2.1: add explicit reference in Course-Syllabus.md. These remain attributed source findings pending verification of the cited artifacts.

Internal row 7.3: Connect academic support to the learner’s task

Confirm the coach and academic-help routes as well as the course-specific inspiration-drought resource. A survival guide can support practice but does not establish every academic-support service claimed by the course shell. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Academy academic support linked from course shell. Course-Syllabus.md references Stage 3 cohort coach role. Inspiration-Drought-Survival-Guide.md acts as student-facing support resource specific to the course's primary failure mode. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 7.4: Distinguish capacity planning from student services

An honest production-capacity check can help a learner make a sustainable schedule. It does not replace usable links to broader support services, and it should not be presented as individualized financial or clinical advice. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Academy student services linked from course shell. C12 explicitly addresses production-cadence wellbeing in M12.5 honest capacity check, which functions as a financial-and-time-wellness consideration. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 8.1: Test the navigation in its delivered form

Numbered folders, consistent paths and a module map are useful only if the learner can follow them. Test meaningful labels, actual links and a textual alternative to a visual-only map. The internal record assigns 3 of 3 points and essential flag true. Its evidence statement is: Folder structure provides clear entry. Module-Map.md visual navigation. Cross-references use consistent file-path syntax. Folders numbered 00-08 consistent with C1-C11 pattern. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 8.2: Verify accessibility evidence for the chosen tools

The source records a partial result despite an institutional WCAG commitment and claims of external-platform compliance. Obtain actual relevant accessibility information and inspect the configured experience. A voice-memo alternative or a platform claim does not certify the whole course. The internal record assigns 2 of 3 points and essential flag true. Its evidence statement is: Build 6 platform commits to WCAG 2.1 AA compliance per academy standard. Channel platforms are externally compliant. Capture-system tooling (M12.2) addresses voice-memo and text-capture as accessibility-aware alternatives. Its reviewer note is: PARTIAL: Build 6 accessibility is institutionally committed but not explicitly cited in C12 artifacts. Channel platform accessibility is mentioned in passing in SOPs but not systematically. Recommend v2.1: add 'Accessibility of capture and scheduling tooling' note to relevant resource. These remain attributed source findings pending verification of the cited artifacts.

Internal row 8.3: Provide alternatives without relying on learning-style claims

Text, diagrams and narrative or procedural examples can provide useful ways to engage with material. Check equivalence of the information and accessibility of each format; a video specification or a reference to visual learners does not establish an accessible alternative. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Module lessons in markdown (text), video production specs (folder 01) for visual learners. Mermaid diagrams have text adjacency. Case studies provide narrative-format alternative to procedural-format SOP learning. Failure case study provides cautionary-narrative alternative for critical-thinking style learners. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 8.4: Inspect readability rather than format labels

Check heading order, paragraph length, tables and explanations in the actual rendering. A preference for prose or sparing bullets is a house style, not proof that every reader can navigate and understand the page. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: Lessons use consistent headings, structured paragraphs, table formatting where data is structured, prose flow for conceptual content. Bullet points used sparingly per voice convention. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Internal row 8.5: Separate the media brief from usable media

The M12.1 specification names chapters, a Speedboat Green color of #6FA84E and a structured transcript. Preserve that source example without replacing RISER branding. Verify actual playback, captions and complete text before reporting an accessible media asset. The internal record assigns 2 of 2 points and essential flag false. Its evidence statement is: M12.1 video production spec provides chapter markers, visual style guide (Speedboat Green #6FA84E), AEO-friendly transcript structure. Its reviewer note is: Direct evidence. These remain attributed source findings pending verification of the cited artifacts.

Check the rubric mapping before any certification claim

The public QM seventh-edition summary has forty-four standards. This internal record omits 3.6, 8.6 and 8.7 and changes several weights and criterion mappings. Its row maximum happens to total 101, but matching a grand total does not establish correct criteria. The supplied internal audit cannot demonstrate official certification or legal accessibility compliance.

Separate useful content structure from unsupported extraction promises

The source calls its M12.4 reference Authority Engine Optimization and describes citation in ChatGPT, Perplexity, Claude, Gemini, Copilot and Grok. It presents citation as credibility and discovery rather than direct conversion. Its claims of about 700 million weekly users, 70% query share, 12% Google-top-ten citation overlap and compounding source preference lack supporting citations here. Preserve them as dated source assertions, not RISER benchmarks or established retrieval mechanisms.

Write self-contained answers without inventing evidence

Pattern one favors an answer understandable without surrounding paragraphs. The source suggests 30–80-word extracts and 30–50-word answer sentences, calling this a 40-word rule with a claimed 2.7-times extraction lift. Those lengths are editing heuristics and the multiplier is unverified. State the relevant entity, answer and qualification clearly; do not lengthen a clear answer to hit a quota. Its newsletter example claims 32–48% open rates and an 8–12-percentage-point penalty for overstatement without evidence, so learners must not reuse those figures as facts.

Make comparisons genuinely comparable

Pattern two uses named alternatives and common dimensions. The example compares setup time of 30 minutes versus four hours, steep versus gentle learning curves and first-year cost of zero versus $480. These illustrate table structure, not identified product measurements. Its separate carousel example claims 6.6% engagement versus 1.5–2.5%, 60–120 versus 30–60 minutes and a two-to-four-times engagement advantage. Define denominator, audience, period and production scope before making such comparisons; the source supplies no verification for those benchmarks or platform preferences.

Use audience questions as useful teaching structure

Pattern three recommends three to six question-and-answer blocks, with answers of 50–150 words. Treat these as optional editorial ranges. The capture-system example separates 60–90 minutes of technical setup from two to three weeks of behavioral adoption, then claims a rhythm within 14 days and automatic triggers by week four. Those timelines are source examples, not measured promises. Explain the technical-versus-behavioral distinction without promising every learner that schedule.

Correct the FAQ markup claim before publishing

The source asserts that FAQPage markup multiplies extraction by 3.1. No evidence for that multiplier is provided. Google’s current documentation updates state that FAQ rich results stopped appearing on May 7, 2026; their documentation was removed June 15. Keep useful visible questions and answers, but do not promise a Google FAQ rich result or infer that this historical multiplier applies to other engines.

Use lists when the subject is naturally a list

Pattern four proposes parallel, independently understandable bullets for steps, ways or types. It suggests four to eight items, dismissing three as too short and more than ten as noisy. Those numerical limits and the claimed differences between Perplexity, ChatGPT and Claude are unverified source heuristics. Use the number of items needed to teach the actual subject. Do not drop a necessary step or pad a short process to satisfy an extraction rule.

Treat the six-engine preference table as hypotheses

The source associates ChatGPT with comparisons, questions, statistics and named entities; Perplexity with lists, FAQ markup and recent original sources; Claude with analysis, balance, citations and frameworks; Gemini with stepwise technical tutorials; Copilot with business narratives and workflows; and Grok with recent commentary, counterarguments and data. It disparages generic, old, clickbait or overly opinionated material differently by engine. These are unsupported generalized preferences. Use multiple structures when they help the same audience understand the subject, not to impersonate a measured engine-ranking specification.

Improve clarity without stripping necessary uncertainty

The source discourages vagueness, excessive hedging, buried answers, generic phrasing, unsourced claims and keyword stuffing. Its example replacing vague language with a 62% Stage 3 statistic is not evidence for that statistic. Remove empty wording but retain uncertainty justified by the evidence. Putting an answer within the first 200 words is a useful editorial experiment, not a guaranteed cutoff. Claims that engines detect generic AI phrasing or penalize all SEO-style optimization require evidence beyond this document.

Verify statistics and freshness instead of meeting quotas

The source recommends three-plus statistics per 300 words with a 2.1-times citation lift, named entities, original sources and references less than 12 months old. It repeats its 2.7-times answer-length and 3.1-times FAQ claims. None of those multipliers is substantiated here. Use only relevant verified statistics; distinguish dates of publication from dates of evidence. A newer derivative does not automatically improve on an older authoritative original.

Integrate the review into drafting, editing and publishing

The source places these checks inside M12.7: draft clear answers and appropriate comparisons or questions; edit claims, statistical support and the opening; publish with source links and any justified markup. It estimates 15–30 extra minutes per pillar piece. Record actual effort rather than calling that estimate a measured production requirement. The source recommends annual reference updates while saying engine preferences change quarterly; verify change-sensitive assertions when teaching or publishing them.

Measure outcomes without promising a citation timeline

The source scenario publishes two pillar pieces monthly and predicts first citations at months four to six, acceleration after month nine and meaningful independent reach at months 12–18. It also says pieces continue extracting after 18 months. These are unsupported forecasts, not a schedule learners or RISER can guarantee. Track dated queries, observed citations, visits and useful learner/customer outcomes separately. Preserve the underlying principle that useful content supports discovery without claiming the source’s numbers establish causation.

Apply current Google requirements within their actual scope

Google’s AI-feature guidance says ordinary SEO practices remain relevant and no special AI markup or files are required. A supporting page must be indexed and snippet-eligible; visibility is not guaranteed. Keep important material readable as text, reachable by links and consistent with structured data. This guidance covers Google Search, not a certification for every LLM. Local noindex review pages are not evidence that the eventual public pages meet these conditions.

Recognize the proposed inspiration-drought pattern without treating it as universal

The M12.8 supporting guide describes novelty in month one, fewer compelling ideas in month two, low inspiration in month three and a settled operating trajectory by month four. It recommends reading before the capstone commitment and again in post-course month two. These are source observations without cohort data, not a forecast for every learner. Distinguish having production capacity but no exciting idea from lacking the time or resources to deliver.

Test the five proposed misdiagnoses against evidence

The guide warns against immediately blaming the channel, voice, format library or producer identity, or calling skipped weeks batching. It cites a 12–24-month channel commitment, suggests voice may deepen as novelty fades and distinguishes preparing four pieces over a weekend from simply abandoning planned slots. Those are source operating principles, not proof that a channel cannot be wrong. Use actual audience, mechanism, capacity and quality evidence rather than treating every difficulty as a failure of commitment.

Use the promoted queue and established formats

Moves one and two draw on the M12.2 promoted-idea queue and M12.3 format library. The source proposes 8–25 queued ideas and a familiar format such as a what-success-looks-like carousel. Choose a suitable promoted idea and let the format guide its structure instead of waiting for the perfect feeling. Queue quantity and a proven format do not guarantee the resulting piece is accurate, useful or successful; apply the editorial review to each output.

Rebalance original and derivative production with correct arithmetic

Move three changes the example from two originals plus four derivatives to one original plus six derivatives for a week, then returns the next week or the week after. The example actually changes six total pieces to seven, so it does not keep the numerical cadence unchanged. It lowers original production while increasing derivative volume. Estimate the actual workload and choose an explicit schedule; do not copy the numbers while claiming a constant piece count or a guaranteed reduction in effort.

Draw from a prepared evergreen buffer

Move four reserves two or three finished evergreen pieces in the M12.5 calendar for difficult weeks. This uses work already completed rather than inventing a new topic under deadline. Check that an older piece remains accurate and relevant when it is scheduled. Mark the buffer as consumed and plan replenishment so it remains a visible production resource rather than an imaginary safety margin.

Reduce unnecessary polishing while preserving editorial standards

Move five recommends shortening the cycle before changing cadence, using a source example of publishing at 90% rather than 95% polish instead of three days late. Those percentages are informal descriptions, not measured quality thresholds. Move six offers a substantive 30-second observation completed in 15 minutes for a suitable rhythm format, after other moves are exhausted. Neither example permits skipping fact-checking, required disclosures or the lesson's editorial standard.

Separate immediate operating adjustments from strategic review

Move seven considers genuine channel-mechanism mismatch, difficult formats, narrow capture surfaces and reduced customer activity. The source schedules strategic review quarterly while using moves one through six for weekly disruption. It suggests adding one capture surface and checking whether expected customer work still occurs. Treat quarterly review as a planned decision point, not a reason to ignore material evidence that needs attention sooner.

Interpret the six cautions as source policies rather than absolute rules

The guide discourages switching channels, lowering cadence while waiting for inspiration, increasing cadence to compensate, increasing AI-generated volume, adding unfamiliar formats and publicly narrating the drought. Its rationale is to preserve continuity, effort and voice. These are context-dependent operating choices, not verified causal laws. Intentional schedule changes, transparent commitments and necessary workload adjustments should be evaluated against the actual audience and delivery situation rather than condemned automatically.

Measure the six proposed indicators consistently

The source tracks cadence, editorial quality, engagement, capture inventory, recognizable voice and operator energy. It proposes 90–100% publication adherence, yet also says one missed slot per quarter is acceptable and two are a warning. Those rules are not equivalent for every schedule: two misses out of twenty slots is still 90%. Define the denominator and governing threshold. Flat engagement and energy recovering by month five are source expectations, not pass/fail facts about an individual learner.

Treat the later outcomes and doctrine as claims to evaluate

The guide predicts a new equilibrium in months five to seven, 24–36 published pieces by month six versus 8–14 for those who slipped, and an audience two to three times larger by month nine. It does not supply supporting data or a consistent cadence baseline for those comparisons. Its Engine Beats the Inspiration doctrine favors capture, formats, calendar and workflow over waiting for motivation, but disciplined production alone cannot verify these causal or numerical claims. Track what actually ships and what the audience finds useful; do not label a changed schedule automatic business failure.

Choose formats by fit rather than source popularity

Use this M12.3 starting library to compare audience, mechanism, voice, cadence and compounding fit. The source calls its selection principle the 6% Rule, but does not supply a validated universal percentage. Its 2026 metrics, production times and cohort observations are source claims rather than measured RISER outcomes. Keep the complete original table available while testing a feasible format against your own evidence.

Interpret the LinkedIn (2026) channel assumptions

The source attributes ranking to a named 360Brew system, dwell time and saves, claims an approximately 60% link-out penalty and a first-hour test on 2–5% of the network. Those precise mechanism claims are not substantiated here. Its cautions against external links, excessive tags/hashtags, agreement bait and generic motivation are source recommendations, not a verified current platform rule. A native newsletter remains dependent on its platform; calling its reach owned does not establish control equivalent to an exportable subscriber relationship.

LinkedIn (2026) — evaluate Document carousel

For LinkedIn (2026), the source proposes Document carousel: 6–12 slides exported as PDF or native carousel; text-led with simple visual hierarchy. Its stated engagement profile is: Highest dwell time; ~6.6% engagement rate (3–4× single-post baseline); strongest save behavior. Its production estimate is 60–120 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

LinkedIn (2026) — evaluate Single-frame insight

For LinkedIn (2026), the source proposes Single-frame insight: 200–400 word post; one specific point, no thread. Its stated engagement profile is: Strong if voice is distinctive; baseline ~1.5–2.5% engagement. Its production estimate is 30–60 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

LinkedIn (2026) — evaluate Long-form post

For LinkedIn (2026), the source proposes Long-form post: 800–1500 word post; structured with subheads. Its stated engagement profile is: Higher dwell time than single-frame; risk: most operators write generic long-form that doesn't perform. Its production estimate is 90–150 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

LinkedIn (2026) — evaluate Native video <90s

For LinkedIn (2026), the source proposes Native video <90s: Vertical video, captions burned in. Its stated engagement profile is: Algorithm boost in 2026; best for face-led operators with personality. Its production estimate is 45–120 min including capture. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

LinkedIn (2026) — evaluate Polls

For LinkedIn (2026), the source proposes Polls: 4-option polls; framing question is the asset. Its stated engagement profile is: High distribution, low save behavior; useful for audience research, not pillar work. Its production estimate is 5–15 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

LinkedIn (2026) — evaluate Comment-as-content

For LinkedIn (2026), the source proposes Comment-as-content: Substantive 100–300 word comment on someone else's high-distribution post. Its stated engagement profile is: Underrated; reaches their audience without producing-from-scratch. Its production estimate is 15–30 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

LinkedIn (2026) — evaluate Newsletter (LinkedIn-native)

For LinkedIn (2026), the source proposes Newsletter (LinkedIn-native): Subscribed newsletter format on LinkedIn itself. Its stated engagement profile is: Builds owned reach within LinkedIn; longer cycle but compounds. Its production estimate is 90–240 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

LinkedIn (2026) — evaluate Carousel + native video combo

For LinkedIn (2026), the source proposes Carousel + native video combo: Carousel pillar with derivative <60s video summary. Its stated engagement profile is: Strong derivative pattern; 2 pieces from 1 production cycle. Its production estimate is +30 min on top of carousel. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Interpret the Twitter / X (2026) channel assumptions

The source favors reply trees, time on platform, cumulative short-post volume and threads. It warns against engagement bait, excessive replies to large accounts and generic founder-life commentary. Its character ranges, distribution claims and alleged over-reply flag are dated source examples, not verified current product limits or enforcement policy. Evaluate useful conversation and actual audience fit rather than assuming high reply volume produces compounding.

Twitter / X (2026) — evaluate Tweet (single)

For Twitter / X (2026), the source proposes Tweet (single): Up to 280 chars; one specific point. Its stated engagement profile is: Volume game; individual tweets matter less than cumulative pattern. Its production estimate is 5–15 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Twitter / X (2026) — evaluate Thread

For Twitter / X (2026), the source proposes Thread: 7–15 tweets; one developed argument or framework. Its stated engagement profile is: Highest leverage; compounds through reply trees and bookmarks. Its production estimate is 60–120 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Twitter / X (2026) — evaluate Quote-tweet take

For Twitter / X (2026), the source proposes Quote-tweet take: Reply to existing high-distribution tweet with substantive 100–280 char addition. Its stated engagement profile is: Reaches target's audience; compounds when target replies. Its production estimate is 10–20 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Twitter / X (2026) — evaluate Long-form (X)

For Twitter / X (2026), the source proposes Long-form (X): 280–4000 char post; mini-essay format. Its stated engagement profile is: Distribution if voice is strong; less platform-native than threads. Its production estimate is 30–60 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Twitter / X (2026) — evaluate Reply-as-content

For Twitter / X (2026), the source proposes Reply-as-content: Substantive reply in active thread. Its stated engagement profile is: Volume strategy; 5–10/day for active operators. Its production estimate is 5–10 min each. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Twitter / X (2026) — evaluate Poll

For Twitter / X (2026), the source proposes Poll: 2–4 option polls. Its stated engagement profile is: Audience research; low compounding. Its production estimate is 5 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Interpret the Newsletter (2026) channel assumptions

The source favors depth and a subscriber relationship and claims 30–50% niche open rates. It calls newsletters free of algorithms, but that statement should not be treated as proof of unrestricted delivery or readership. Open and click measures answer different questions; define their denominators. Avoid overpromising subject lines and thin derivative summaries. The source preference against generic digests is an editorial position, not a ban on a useful curated format.

Newsletter (2026) — evaluate Long-form essay

For Newsletter (2026), the source proposes Long-form essay: 1500–4000 words; one topic developed. Its stated engagement profile is: Highest leverage format; pillar for many operators. Its production estimate is 4–8 hours. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Newsletter (2026) — evaluate Curated commentary

For Newsletter (2026), the source proposes Curated commentary: 5–8 items with operator commentary on each. Its stated engagement profile is: Lower production cost; rhythm format. Its production estimate is 90–180 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Newsletter (2026) — evaluate Case study breakdown

For Newsletter (2026), the source proposes Case study breakdown: Specific customer outcome or framework application; 1500–3000 words. Its stated engagement profile is: Highest mechanism-demonstration value. Its production estimate is 3–6 hours. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Newsletter (2026) — evaluate Q&A from subscribers

For Newsletter (2026), the source proposes Q&A from subscribers: Reader questions with substantive answers. Its stated engagement profile is: Builds subscriber engagement; needs subscriber inflow first. Its production estimate is 60–120 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Newsletter (2026) — evaluate Field notes

For Newsletter (2026), the source proposes Field notes: Short personal observation pieces; 600–1200 words. Its stated engagement profile is: Voice-led; risk of self-indulgence if not anchored to audience question. Its production estimate is 60–90 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Newsletter (2026) — evaluate Numbered framework

For Newsletter (2026), the source proposes Numbered framework: "5 ways to X" or "The 7 stages of Y". Its stated engagement profile is: Highly bookmarkable; risk of generic over-structure. Its production estimate is 90–180 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Interpret the Instagram (2026) channel assumptions

The source favors Reels and carousels, characterizes Stories as maintenance, and claims captions/on-screen text matter more than hashtags. Its performance hierarchy and algorithm boosts are unverified. The cautions against static-only posting, overly polished aesthetics and voice-misaligned trends are hypotheses to evaluate for the audience. The listed lengths and slide counts describe example formats rather than verified upload caps.

Instagram (2026) — evaluate Carousel (10-slide)

For Instagram (2026), the source proposes Carousel (10-slide): Visual-led; first slide hooks, slides 2–9 develop, slide 10 calls to save/share. Its stated engagement profile is: Highest save rate; pillar format for visual operators. Its production estimate is 90–180 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Instagram (2026) — evaluate Reel <30s

For Instagram (2026), the source proposes Reel <30s: Vertical video; captions burned in; on-screen hook. Its stated engagement profile is: Discovery distribution; algorithm-boosted in 2026. Its production estimate is 30–90 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Instagram (2026) — evaluate Reel 30–90s

For Instagram (2026), the source proposes Reel 30–90s: Educational or behind-the-scenes; deeper engagement. Its stated engagement profile is: Better for established audiences; lower distribution boost than <30s. Its production estimate is 60–120 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Instagram (2026) — evaluate Single-image post + long caption

For Instagram (2026), the source proposes Single-image post + long caption: One strong image; 500–1500 char caption. Its stated engagement profile is: Lower distribution but builds voice/audience depth. Its production estimate is 30–60 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Instagram (2026) — evaluate Story (24h)

For Instagram (2026), the source proposes Story (24h): Vertical 5–15s; daily rhythm. Its stated engagement profile is: Audience maintenance, not acquisition. Its production estimate is 5–15 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Instagram (2026) — evaluate Story Highlight (curated)

For Instagram (2026), the source proposes Story Highlight (curated): Selected stories pinned permanently. Its stated engagement profile is: Profile asset; review quarterly. Its production estimate is 30–60 min curation. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Interpret the YouTube (2026) channel assumptions

The source separates search/subscription long-form from Shorts discovery, elevates title and thumbnail, and discourages long intros, generic titles and videos under five minutes. Its own table also proposes talking-head videos as short as three minutes, so the under-five-minute caution is not internally consistent as a universal rule. Treat the under-60-second Short as this source’s format choice, not a claim about the platform’s current maximum. Search longevity and subscriber conversion require actual evidence.

YouTube (2026) — evaluate Long-form video (8–25 min)

For YouTube (2026), the source proposes Long-form video (8–25 min): Single topic; depth-oriented. Its stated engagement profile is: Compounds for years; highest production cost; pillar. Its production estimate is 4–12 hours per video. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

YouTube (2026) — evaluate Tutorial (5–15 min)

For YouTube (2026), the source proposes Tutorial (5–15 min): Specific how-to; high search distribution. Its stated engagement profile is: SEO-driven; compounds through search demand. Its production estimate is 3–8 hours. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

YouTube (2026) — evaluate Short (<60s, vertical)

For YouTube (2026), the source proposes Short (<60s, vertical): Discovery format; clip-style. Its stated engagement profile is: High distribution, low conversion to subscriber. Its production estimate is 30–90 min including capture. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

YouTube (2026) — evaluate Live stream

For YouTube (2026), the source proposes Live stream: 30–90 min real-time. Its stated engagement profile is: Audience engagement, not acquisition. Its production estimate is Real-time + 30 min setup. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

YouTube (2026) — evaluate Talking-head (face-on-camera, 3–10 min)

For YouTube (2026), the source proposes Talking-head (face-on-camera, 3–10 min): Face-led, conversational; lower production. Its stated engagement profile is: Voice-led; works if operator can be on camera comfortably. Its production estimate is 2–4 hours. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Interpret the TikTok (2026) channel assumptions

The source describes volatility, discovery and weak subscriber-to-view conversion, and suggests this channel mainly for consumer-facing, face-led operators. Its claim that the first two seconds determine distribution and its relative preference for other channels are unsupported generalizations. A clear opening may help viewers understand the topic; it does not establish an algorithmic guarantee or exclude a business audience.

TikTok (2026) — evaluate <30s Hook + payoff

For TikTok (2026), the source proposes <30s Hook + payoff: Vertical; first 2 seconds determine distribution. Its stated engagement profile is: High discovery; low compounding. Its production estimate is 30–90 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

TikTok (2026) — evaluate <60s educational

For TikTok (2026), the source proposes <60s educational: Quick framework or tip; on-screen text-led. Its stated engagement profile is: Better for B2B-leaning operators. Its production estimate is 45–90 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

TikTok (2026) — evaluate Series (multi-part)

For TikTok (2026), the source proposes Series (multi-part): 3–8 part series across separate videos. Its stated engagement profile is: Builds repeat viewers; weak vs other channels. Its production estimate is 3–8 hours total. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Interpret the Substack (2026 specifically) channel assumptions

The source combines newsletters, community, audio, recommendations and Notes. The described format mix is a source planning example; current features and eligibility need checking before implementation. Recommendations should be relevant and honest rather than treated as a guaranteed reciprocal growth transaction. Podcast embedding time excludes recording and production, so do not confuse the listed marginal task time with the whole workload.

Substack (2026 specifically) — evaluate Long-form newsletter post

For Substack (2026 specifically), the source proposes Long-form newsletter post: 1500–4000 words. Its stated engagement profile is: Same as newsletter; benefits from cross-recommendation. Its production estimate is 4–8 hours. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Substack (2026 specifically) — evaluate Note

For Substack (2026 specifically), the source proposes Note: Twitter-like short post inside Substack. Its stated engagement profile is: Surfaces to subscribers + Substack feed. Its production estimate is 5–15 min. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Substack (2026 specifically) — evaluate Podcast embed

For Substack (2026 specifically), the source proposes Podcast embed: Audio post with text intro. Its stated engagement profile is: Builds podcast audience inside email. Its production estimate is 30–60 min on top of podcast production. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Substack (2026 specifically) — evaluate Cross-recommendation participation

For Substack (2026 specifically), the source proposes Cross-recommendation participation: Recommending peer Substacks. Its stated engagement profile is: Reciprocal subscriber growth. Its production estimate is 15 min/week. Use the format description to plan the deliverable, then separately test the performance claim and measure end-to-end effort. The metric, comparative ranking and time are preserved as source assertions, not verified current platform behavior or a promise of results. Include research, editing, accessibility and publishing in your workload assessment rather than assuming the listed interval covers every task.

Compare the five proposed three-format combinations

The source proposes LinkedIn carousel/insight/comment, newsletter essay/curation/case-study, Twitter thread/single/reply, Instagram carousel/short Reel/Story, and YouTube long video/tutorial/Short. These pair pillar work with rhythm, depth, engagement or discovery. They are cohort examples rather than prescriptions. Use the same five fit dimensions for every candidate and check the combined schedule, not just whether each format seems individually attractive.

Keep the 2027 predictions distinct from established facts

The reference forecasts more AI-content saturation, continued video gains, relative newsletter/YouTube stability, shifting platform incentives and a larger role for AI citations. These predictions are not evidence of what will happen. Its annual-update instruction is useful maintenance guidance; change-sensitive mechanics still need verification when a lesson is used. Preserve the durable selection questions while revising unsupported numerical or product claims.

Verify the course identity of each evidence document

The audit cites Course-Syllabus, Module-Map and Prerequisites files, but the available exact-name matches describe C11; the available Learning-Outcomes describes C9. README matches also belong to other course material or an unrelated package. Do not substitute those files as evidence that the asserted C12 implementation exists. The AEO extraction reference, channel-format reference and inspiration-drought guide have now been read as complete local text extracts and taught below, with unsupported claims identified. Native-file verification, remaining current-claim checks and final semantic review are still open.

QM-Audit-C12.json — original source

Apply Brunson and Hormozi with attribution

Use Hook, Story, Offer to make a lesson opening and next action clear. Apply the Acquisition.com value lens by reducing avoidable learner delay and effort and explaining the desired outcome and evidence of progress. These marketing lenses do not replace assessment evidence, accessibility review or an official Quality Matters review.

Complete original source text

Download exact original text

{
  "metadata": {
    "course_id": "C12",
    "course_name": "Content Engine",
    "stage": 3,
    "rubric": "QM Higher Education Rubric 7th Edition v2.0",
    "total_standards": 42,
    "essential_standards": 16,
    "max_points": 94,
    "certification_threshold_percent": 85,
    "certification_threshold_points": 80,
    "auditor": "Internal — built-from-rubric clean audit",
    "audit_date": "2026-04-28",
    "build_version": "v2.0",
    "scoring_philosophy": "Honest assessment against rubric criteria. Evidence cited with file paths. Standards scored partial (1 below max) where C12-specific evidence is thinner than ideal but the standard is substantively met. Standards scored at max where evidence is direct and complete. The auditor explicitly avoids score-to-prediction; this is an honest first-cycle audit and identifies remediation work for a v2.1 cycle."
  },

  "general_standard_1": {
    "name": "Course Overview and Introduction",
    "standards": [
      {"id": "1.1", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Instructions make clear how to get started and where to find various course components.", "evidence": "00_Course-Overview/README.md provides primary entry with Start-here framing, conceptual hinge (sporadic-vs-engine table), 8 deliverables, doctrines, and links to all folder-00 documents. Module-Map.md provides Mermaid flowchart navigation across M12.1-M12.8.", "notes": "Direct evidence."},
      {"id": "1.2", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Learners are introduced to the purpose and structure of the course.", "evidence": "README.md and Course-Syllabus.md establish purpose (Stage 3 second-course transition: from channel commitment to engine production) and structure (8 modules across 5-6 weeks, 8 deliverables, 3 HITL gates, course-completion validator gate).", "notes": "Direct evidence."},
      {"id": "1.3", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Communication expectations for online discussions, email, and other forms of interaction are clearly stated.", "evidence": "Folder 08 cohort discussion prompts establish discussion expectations. Course-Syllabus.md describes HITL submission flow. SOPs specify communication points per gate.", "notes": "Substantive."},
      {"id": "1.4", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Course and institutional policies are clearly stated within the course, or a link to current policies is provided.", "evidence": "Prerequisites.md and Course-Syllabus.md state Build 6 prerequisite policies. HITL gate policies, channel-commitment-recovery policy (carried from C11), and Engine Beats Inspiration doctrine made explicit.", "notes": "Course-specific covered; institution-wide inherited from course shell."},
      {"id": "1.5", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Minimum technology requirements are clearly stated and instructions for use provided.", "evidence": "Prerequisites.md specifies channel-platform analytics, capture system tooling, scheduling tools. SOPs walk through tooling per stage. Folder 04 README documents Build 6 platform requirements.", "notes": "Direct evidence."},
      {"id": "1.6", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Prerequisite knowledge in the discipline and/or any required competencies are clearly stated.", "evidence": "Prerequisites.md is dedicated to this. C11 completion required (channel commitment artifact). Stage 3 forward-carry-map in folder 02 makes prerequisite artifacts explicit.", "notes": "Direct evidence."},
      {"id": "1.7", "essential": false, "max_points": 1, "scored_points": 1, "criterion": "Minimum technical skills expected of the learner are clearly stated.", "evidence": "Prerequisites.md addresses capture-system installation, calendar/scheduling tool literacy, AI-assistance tool familiarity. SOP-1 walks through capture system installation.", "notes": "Direct evidence."},
      {"id": "1.8", "essential": false, "max_points": 2, "scored_points": 1, "criterion": "The self-introduction by the instructor is professional and is available online.", "evidence": "HITL instructor identification structure exists in schema. Course-Syllabus.md references the Stage 3 cohort coach role. Per-instructor self-introduction is not a C12-specific artifact; it is inherited from the course shell template.", "notes": "PARTIAL: Course-shell pattern is documented but a C12-specific instructor introduction artifact is not generated by this build. Recommend v2.1: include an instructor-introduction template in folder 00 that the assigned instructor populates per cohort."},
      {"id": "1.9", "essential": false, "max_points": 1, "scored_points": 1, "criterion": "Learners are asked to introduce themselves to the class.", "evidence": "Folder 08 community prompts include a cohort-arrival prompt at C12 entry framed around inspiration-vs-engine self-positioning, drawing on each learner's C11 channel commitment.", "notes": "Direct evidence."}
    ],
    "subtotal_max": 18,
    "subtotal_scored": 17
  },

  "general_standard_2": {
    "name": "Learning Objectives (Competencies)",
    "standards": [
      {"id": "2.1", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Course learning objectives describe outcomes that are measurable.", "evidence": "Learning-Outcomes.md defines 8 CLOs with measurable verbs (audit, install, construct, author, plan, map, operationalize, attest). Each verifiable through specific deliverables.", "notes": "Direct evidence."},
      {"id": "2.2", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Module-level learning objectives describe outcomes that are measurable and consistent with course-level objectives.", "evidence": "Learning-Outcomes.md provides per-module MLOs mapped to specific CLOs. Each MLO is operationalized through a deliverable rubric.", "notes": "Direct evidence."},
      {"id": "2.3", "essential": false, "max_points": 3, "scored_points": 3, "criterion": "Learning objectives are stated clearly, written from the learner's perspective, and prominently located.", "evidence": "Learning-Outcomes.md uses learner-perspective phrasing, located in folder 00, and each module lesson opens by restating the relevant MLOs.", "notes": "Direct evidence."},
      {"id": "2.4", "essential": false, "max_points": 3, "scored_points": 3, "criterion": "The relationship between learning objectives and learning activities is clearly stated.", "evidence": "Course-Syllabus.md table maps CLO/MLO to activities to deliverable per module. Each module lesson opens with the relevant MLO and ties activities to deliverable.", "notes": "Direct evidence."},
      {"id": "2.5", "essential": false, "max_points": 3, "scored_points": 3, "criterion": "Learning objectives are suited to the level of the course.", "evidence": "MLOs follow Bloom's taxonomy progression (analyze to apply to create) appropriate to a Stage 3 production-systematization course.", "notes": "Direct evidence."}
    ],
    "subtotal_max": 15,
    "subtotal_scored": 15
  },

  "general_standard_3": {
    "name": "Assessment and Measurement",
    "standards": [
      {"id": "3.1", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Assessments measure the stated learning objectives.", "evidence": "Each of 8 deliverables maps to one or more MLOs. M12.8 attestation assessed via Opus 4.7 validator with 4 weighted dimensions (coherence 35%, voice 20%, doctrine 25%, forward feasibility 20%) matching CLO 8.", "notes": "Direct evidence."},
      {"id": "3.2", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Course grading policy is stated clearly.", "evidence": "Course-Syllabus.md states completion criteria. check_c12_completion function in folder 04 codifies grading programmatically. Validator threshold (composite >=85) explicit.", "notes": "Direct evidence."},
      {"id": "3.3", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Specific descriptive criteria are provided for evaluation of learners' work and connection to grading policy.", "evidence": "Each reviewer prompt (folder 03) provides explicit evaluation criteria with scoring formulas. Deliverable rubrics in folder 02 worksheets provide scoring criteria. Opus validator provides per-dimension scoring rubric.", "notes": "Direct evidence."},
      {"id": "3.4", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Assessments are sequenced, varied, and suited to the level of the course.", "evidence": "Sequenced from M12.1 reflection through M12.8 capstone. Varied: reflective, structural construction, rubric-scored authoring, plan production, operational deliverable, multi-dimensional validator-scored attestation. Stage 3 level.", "notes": "Direct evidence."},
      {"id": "3.5", "essential": false, "max_points": 2, "scored_points": 1, "criterion": "Course provides learners with multiple opportunities to track progress with timely feedback.", "evidence": "Reviewer turnaround per module is fast (LLM-based). check_c12_completion returns module-by-module status. Backend tracking in stage_3_progress schema.", "notes": "PARTIAL: Backend tracking exists but a learner-facing progress visualization/dashboard is not specified in C12 artifacts. Recommend v2.1: add 'How to track your progress' section to Course-Syllabus.md describing the learner-side progress UI."}
    ],
    "subtotal_max": 13,
    "subtotal_scored": 12
  },

  "general_standard_4": {
    "name": "Instructional Materials",
    "standards": [
      {"id": "4.1", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Instructional materials contribute to achievement of stated learning objectives.", "evidence": "9 module lesson files (8 lessons + 1 video spec), 15 folder-02 resources, 4 case studies, 6 reviewer prompts, 4 SOPs, folder-04 schema/functions/RLS all map to MLOs.", "notes": "Direct evidence."},
      {"id": "4.2", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Purpose of instructional materials and how they are used is clearly explained.", "evidence": "Each module lesson directs to specific folder-02 resources. SOPs in folder 05 walk through resource use stepwise. Folder 02 README maps resources to modules.", "notes": "Direct evidence."},
      {"id": "4.3", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Course models the academic integrity expected of learners.", "evidence": "M12.3 cites 2026 empirical findings (LinkedIn 360Brew, AEO mechanics, FAQPage schema rate, citation overlap data). Case studies framed as composites or named honestly. Failure case study explicitly named as composite. AI-assistance disclosure discipline modeled in M12.7.", "notes": "Direct evidence."},
      {"id": "4.4", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Instructional materials represent up-to-date theory and practice.", "evidence": "M12.3, M12.4, M12.7 include 2026-current research (LinkedIn document carousels 6.6% engagement, ChatGPT 70% AI search share/700M weekly users, FAQPage schema 3.1x extraction rate, 40-word answer rule 2.7x rate, 12% citation overlap between ChatGPT and Google top-10). AEO-Extraction-Patterns-2026.md and Channel-Format-Quick-Reference-2026.md dated and current.", "notes": "Direct evidence with explicit 2026 currency."},
      {"id": "4.5", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Variety of instructional materials.", "evidence": "Lesson markdown, video specs, templates, worksheets, references, case studies (3 success + 1 failure), system prompts (5 reviewers + 1 validator), SOPs, schema/SQL, RLS policies, functions.", "notes": "Direct evidence."}
    ],
    "subtotal_max": 12,
    "subtotal_scored": 12
  },

  "general_standard_5": {
    "name": "Learning Activities and Learner Interaction",
    "standards": [
      {"id": "5.1", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Learning activities promote achievement of stated learning objectives.", "evidence": "Each module's activities directly produce the deliverable measuring the MLO. Capture practice, format library construction, calendar drafting, repurposing map, and 8-piece backlog all directly produce evidence of MLO achievement.", "notes": "Direct evidence."},
      {"id": "5.2", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Learning activities provide opportunities for interaction that support active learning.", "evidence": "Reviewer prompts provide LLM interaction. HITL gates at M12.4, M12.7, M12.8 provide instructor interaction. Folder 08 cohort discussion. Predicted-drought paragraph and forward statement in M12.8 require active synthesis.", "notes": "Direct evidence."},
      {"id": "5.3", "essential": false, "max_points": 3, "scored_points": 2, "criterion": "Instructor's plan for interacting with learners is clearly stated.", "evidence": "Course-Syllabus.md describes HITL pass timing for M12.4, M12.7, M12.8. Reviewer-vs-instructor escalation paths documented in SOPs.", "notes": "PARTIAL: Interaction structure documented but specific SLA commitments (e.g., 48-hour HITL turnaround) are not explicitly stated. Recommend v2.1: add explicit SLA commitments to Course-Syllabus.md."},
      {"id": "5.4", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Requirements for learner interaction are clearly stated.", "evidence": "Course-Syllabus.md states learner-side interaction requirements. SOPs operationalize per module. Cohort discussion participation expectations in folder 08.", "notes": "Direct evidence."}
    ],
    "subtotal_max": 11,
    "subtotal_scored": 10
  },

  "general_standard_6": {
    "name": "Course Technology",
    "standards": [
      {"id": "6.1", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Tools used in the course support the learning objectives.", "evidence": "Build 6 supports all 8 deliverables. Reviewer LLMs (Sonnet 4.6 for M12.2-M12.7, Opus 4.7 for M12.8 course-completion validator) matched to evaluation complexity.", "notes": "Direct evidence."},
      {"id": "6.2", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Course tools promote learner engagement and active learning.", "evidence": "Reviewer interaction provides immediate substantive feedback with REVISE/PASS/REJECT verdicts and structured reasoning. HITL UI surfaces output to instructor and back. Cohort discussion surface enables peer engagement.", "notes": "Direct evidence."},
      {"id": "6.3", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Variety of technology is used in the course.", "evidence": "Build 6 platform, multiple LLM models (Sonnet 4.6 for routine review + Opus 4.7 for capstone validation), Supabase database with PL/pgSQL, channel-platform tools, AI-assistance tools (M12.7).", "notes": "Direct evidence."},
      {"id": "6.4", "essential": false, "max_points": 2, "scored_points": 1, "criterion": "Course provides learners with information on protecting their data and privacy.", "evidence": "RLS policies in folder 04 codify student data privacy at the database level. Channel-platform privacy is platform's responsibility. Confidentiality protocol for client-data students (e.g., Priya case study) modeled in editorial standards.", "notes": "PARTIAL: Backend RLS exists and confidentiality is modeled in case studies but learner-facing privacy disclosure is not present. Recommend v2.1: add a learner-facing data/privacy section to Prerequisites.md."}
    ],
    "subtotal_max": 10,
    "subtotal_scored": 9
  },

  "general_standard_7": {
    "name": "Learner Support",
    "standards": [
      {"id": "7.1", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Course instructions articulate or link to a clear description of technical support.", "evidence": "Build 6 platform support is described. Reviewer prompt failure escalation paths in SOPs. HITL escalation path documented. Inspiration-Drought-Survival-Guide.md provides student-side troubleshooting.", "notes": "Direct evidence."},
      {"id": "7.2", "essential": false, "max_points": 3, "scored_points": 2, "criterion": "Course instructions articulate or link to institution's accessibility policies and services.", "evidence": "Pattern carried from C1-C11 — institutional accessibility policies linked from course shell.", "notes": "PARTIAL: Course-shell pattern but no C12-specific link or note. Recommend v2.1: add explicit reference in Course-Syllabus.md."},
      {"id": "7.3", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Course instructions articulate or link to academic support services.", "evidence": "Academy academic support linked from course shell. Course-Syllabus.md references Stage 3 cohort coach role. Inspiration-Drought-Survival-Guide.md acts as student-facing support resource specific to the course's primary failure mode.", "notes": "Direct evidence."},
      {"id": "7.4", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Course instructions articulate or link to student services.", "evidence": "Academy student services linked from course shell. C12 explicitly addresses production-cadence wellbeing in M12.5 honest capacity check, which functions as a financial-and-time-wellness consideration.", "notes": "Direct evidence."}
    ],
    "subtotal_max": 10,
    "subtotal_scored": 9
  },

  "general_standard_8": {
    "name": "Accessibility and Usability",
    "standards": [
      {"id": "8.1", "essential": true, "max_points": 3, "scored_points": 3, "criterion": "Course navigation facilitates ease of use.", "evidence": "Folder structure provides clear entry. Module-Map.md visual navigation. Cross-references use consistent file-path syntax. Folders numbered 00-08 consistent with C1-C11 pattern.", "notes": "Direct evidence."},
      {"id": "8.2", "essential": true, "max_points": 3, "scored_points": 2, "criterion": "Information is provided about the accessibility of all technologies required in the course.", "evidence": "Build 6 platform commits to WCAG 2.1 AA compliance per academy standard. Channel platforms are externally compliant. Capture-system tooling (M12.2) addresses voice-memo and text-capture as accessibility-aware alternatives.", "notes": "PARTIAL: Build 6 accessibility is institutionally committed but not explicitly cited in C12 artifacts. Channel platform accessibility is mentioned in passing in SOPs but not systematically. Recommend v2.1: add 'Accessibility of capture and scheduling tooling' note to relevant resource."},
      {"id": "8.3", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Course provides alternative means of access to course materials in formats that meet the needs of diverse learners.", "evidence": "Module lessons in markdown (text), video production specs (folder 01) for visual learners. Mermaid diagrams have text adjacency. Case studies provide narrative-format alternative to procedural-format SOP learning. Failure case study provides cautionary-narrative alternative for critical-thinking style learners.", "notes": "Direct evidence."},
      {"id": "8.4", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Course design facilitates readability.", "evidence": "Lessons use consistent headings, structured paragraphs, table formatting where data is structured, prose flow for conceptual content. Bullet points used sparingly per voice convention.", "notes": "Direct evidence."},
      {"id": "8.5", "essential": false, "max_points": 2, "scored_points": 2, "criterion": "Course multimedia facilitate ease of use.", "evidence": "M12.1 video production spec provides chapter markers, visual style guide (Speedboat Green #6FA84E), AEO-friendly transcript structure.", "notes": "Direct evidence."}
    ],
    "subtotal_max": 12,
    "subtotal_scored": 11
  },

  "summary": {
    "total_max_points": 94,
    "total_scored_points": 89,
    "percent": 94.7,
    "essential_standards_total": 16,
    "essential_standards_met": 16,
    "essential_standards_max_points": 48,
    "essential_standards_scored_points": 47,
    "essential_standard_lost_points_at": "8.2 (-1, scored 2 of 3) — substantively met but documentation thin",
    "non_essential_standards_partial": ["1.8 (-1)", "3.5 (-1)", "5.3 (-1)", "6.4 (-1)", "7.2 (-1)"],
    "certification_status": "MEETS_THRESHOLD",
    "certification_threshold_percent": 85,
    "certification_threshold_points": 80,
    "comments": "C12 Content Engine achieves 89/94 (94.7%), well above the 80-point QM certification threshold. All 16 Essential standards are met (47/48 Essential points; one Essential standard, 8.2, scored partial at 2/3 due to lack of explicit C12-specific accessibility documentation for capture and scheduling tooling — substantively met but recommend remediation in v2.1). Five non-Essential standards scored partial; each has a specific v2.1 remediation note. Overall the course is QM-ready and the partial scores represent honest documentation gaps rather than design weaknesses. The score parity with C11 (also 89/94) is intentional — C12 inherits C11's documentation patterns and shares the same shell-vs-course documentation gaps; v2.1 remediation across both courses simultaneously will close most partial scores in a single cycle.",
    "v2_1_remediation_recommendations": [
      "1.8: Add an instructor-introduction template in folder 00 that the assigned instructor populates per cohort.",
      "3.5: Add a 'How to track your progress' section to Course-Syllabus.md describing the learner-side progress UI.",
      "5.3: Add explicit HITL turnaround SLA commitments to Course-Syllabus.md (e.g., 48-hour HITL pass for M12.4; 72 hours for M12.7; 5 business days for M12.8).",
      "6.4: Add a learner-facing data/privacy section to Prerequisites.md describing what student data is collected, who sees it, and how privacy is protected.",
      "7.2: Add explicit reference to institutional accessibility policy in Course-Syllabus.md.",
      "8.2: Add 'Accessibility of capture and scheduling tooling' note to capture and calendar resources in folder 02 addressing tool-specific accessibility considerations (voice-memo alternatives, screen-reader compatibility for scheduling tools)."
    ],
    "auditor_self_check": "This is a clean-room audit built directly from the rubric. Every SRS evaluated against specific course evidence with file paths cited. Five non-Essential standards and one Essential standard scored partial because the C12 build inherits some patterns from the course shell without explicitly duplicating them in C12 artifacts (a defensible v2.0 design choice that costs documentation points). The 89/94 score is above certification threshold and the v2.1 remediation list provides a clear path to higher score in the next cycle. This is honest assessment, not score-to-prediction."
  }
}

Complete AEO reference — D2473 (local extraction; unsupported claims reviewed in teaching)

Download exact original text

# AEO Extraction Patterns 2026

> Reference document supporting M12.4 Editorial Standards. Authority Engine Optimization (AEO) is the discipline of producing content that authority engines (ChatGPT, Perplexity, Claude, Gemini, Copilot, Grok) cite when answering user queries. This document specifies the extraction patterns that maximize citation rate in 2026.

---

## Why AEO matters in 2026

ChatGPT crossed ~700M weekly active users in 2026 and processes the majority of authority-engine queries (~70% market share). Perplexity, Claude, Gemini, Copilot, and Grok handle the remainder. Together these engines now mediate a meaningful portion of information-seeking before the searcher reaches a website at all.

Citation in these engines is distinct from search engine ranking. The 12% citation overlap between top-10 Google results and ChatGPT citations means the SEO playbook is partially but not fully transferable. AEO is its own discipline.

For a Stage 3 operator, AEO matters because:

- A meaningful share of your audience's discovery happens through authority engines
- Citation in authority engines is the contemporary equivalent of being quoted in a trade publication — credibility infrastructure, not direct conversion
- Authority engine citation compounds (the engines learn which sources are reliably useful and weight them higher over time)
- The patterns that produce citation also tend to produce better human-readable content

---

## The four extraction patterns

Authority engines extract content in four primary patterns:

### Pattern 1 — Self-contained answer extraction

The engine extracts a 30–80 word self-contained answer that fully answers the query. Pattern characteristics:

- Single complete sentence or short paragraph
- States the answer rather than describing the topic
- Includes the specific entity, number, or claim the query asked for
- Does not require surrounding context to make sense

**Producing this pattern:**

In long-form content, write key claims as 40-word self-contained sentences. The 40-word rule (specifically: claims stated in 30–50 word sentences with explicit subject-verb-object structure and the answer to a likely query embedded) increases extraction rate by ~2.7×.

Example (poor): "There are several factors that influence newsletter conversion rates, and these include various elements like subject lines, audience targeting, and content quality."

Example (strong): "Newsletter open rates for niche operator newsletters in 2026 average 32–48%, with the strongest determinant being subject-line accuracy — open rates drop 8–12 percentage points when subject lines overstate body content."

The strong version is extractable because it answers a likely query ("what are newsletter open rates") with a specific number and a specific causal mechanism, in one self-contained sentence.

### Pattern 2 — Comparison extraction

The engine extracts a comparison table or comparison paragraph when the query is comparative. Pattern characteristics:

- Two or more named entities compared on shared dimensions
- Concrete differences specified, not generic
- Tabular structure or parallel-construction prose

**Producing this pattern:**

Include explicit comparison tables in pillar content. ChatGPT particularly favors comparison tables in extraction; Perplexity and Claude follow.

Example structure:

| Dimension | Approach A | Approach B |
|---|---|---|
| Setup time | 30 minutes | 4 hours |
| Learning curve | Steep | Gentle |
| Cost at year 1 | $0 | $480 |

Comparisons embedded in prose also extract, when written in parallel construction:

"LinkedIn carousel posts generate 6.6% engagement on average; single-frame posts generate 1.5–2.5%. Carousels require 60–120 minutes; single-frame posts require 30–60 minutes. The carousel pattern produces 2–4× the engagement at 2× the time cost."

### Pattern 3 — Structured Q&A extraction

The engine extracts question-answer pairs when the source contains explicitly structured Q&A. Pattern characteristics:

- Question stated as a question (not as a header like "Setup")
- Answer self-contained, 50–150 words
- FAQPage schema markup if technically feasible (3.1× extraction rate)

**Producing this pattern:**

Include 3–6 explicit Q&A blocks at the end of pillar pieces. Frame questions as questions your audience would ask. Answer concisely and self-containedly.

Example structure:

> **Q: How long does it take to install a capture system?**
>
> A: The technical installation — choosing tools, setting up the inbox — takes 60–90 minutes. The behavioral installation — capturing reflexively without friction — takes 2–3 weeks of consistent practice. Most operators reach a sustainable capture rhythm within the first 14 days, with the surface-by-surface trigger discipline becoming automatic by week 4.

The Q&A block format reads naturally for human readers (not jargon) and extracts at high rate for authority engines. FAQPage schema markup, where the publishing platform allows it, multiplies extraction by ~3.1×.

### Pattern 4 — Bulleted list extraction

The engine extracts bullet lists for "ways to," "steps to," "types of" queries. Pattern characteristics:

- Parallel-construction list items
- Each item is self-contained (a reader understanding only that item gets the point)
- 4–8 items typical (lists of 3 are too short to extract well; lists over 10 are usually noise)

**Producing this pattern:**

When the content is genuinely a list, structure it as one. When the content is not a list, do *not* force list structure — generic listicles ("5 tips for X") have low extraction quality and degrade voice. Lists are a tool for genuinely listed content, not a default structure.

Perplexity favors bulleted-list extraction; ChatGPT and Claude extract lists when the query is list-shaped but extract paragraphs when the query is concept-shaped.

---

## Platform-specific preferences (2026)

| Engine | Top extraction preferences | Less effective |
|---|---|---|
| **ChatGPT** | Comparison tables; structured Q&A; long-form pillar pieces with 3+ specific stats; named-entity claims | Generic listicles; unstructured anecdotes |
| **Perplexity** | Bulleted lists; FAQPage schema; recent (within 12 months) sources; high-citation original sources | Older content; opinion-led commentary |
| **Claude** | Long-form analytical content; balanced perspective pieces; named-source citations; conceptual frameworks | Click-bait; over-confident single-perspective claims |
| **Gemini** | Step-by-step tutorials; how-to with specific outcomes; technical documentation patterns | Generic thought leadership |
| **Copilot** | Narrative summaries; business-context framing; productivity and workflow content | Highly opinionated commentary |
| **Grok** | Recent news commentary; counter-narrative takes; data-anchored claims | Generic safe content |

The implication is *not* to write differently for each engine. The implication is to include multiple extraction patterns within a single pillar piece — comparison table + Q&A block + statistical anchoring + clear conceptual framework — so that the piece extracts well across engines.

---

## What kills extraction

- **Vague claims without numbers.** "Many operators struggle" extracts poorly; "62% of Stage 3 operators report capacity contradictions in months 2–4" extracts.
- **Hedging language.** "It might be the case that some newsletters tend to perform somewhat better when…" extracts as noise.
- **Buried answers.** Answers buried 800 words into a piece, behind throat-clearing introductions, are less likely to extract than answers stated directly in the first 200 words.
- **Generic AI-default phrasing.** Authority engines have learned to deprioritize content that reads as AI-generated. Voice-distinctive content has citation advantage.
- **Unsourced claims.** Claims without sources extract less reliably; engines weight sourced claims higher in retrieval.
- **Over-keyword-stuffing.** SEO-style keyword optimization actively hurts AEO extraction in 2026 — engines flag patterns that look like SEO bait.

---

## What lifts extraction

- **3+ specific statistics per 300 words** in pillar pieces (~2.1× citation rate)
- **Named entities** — specific operators, specific tools, specific methods cited by name
- **Self-contained 40-word answer sentences** (~2.7× extraction rate)
- **FAQPage schema** where technically feasible (~3.1× extraction rate)
- **Comparison tables** for comparative queries
- **Recent source dates** — content with sources from the prior 12 months extracts better than content with older sources, even when the older source is canonical
- **Original source claims** — content that authority engines can verify against an original source ranks higher than aggregator/derivative content

---

## Operator workflow integration

AEO is not a separate workflow. It integrates into the M12.7 production workflow:

1. **At drafting:** include the 40-word answer rule for key claims; include a comparison table where the content is comparative; include 3–6 Q&A at the end of pillar pieces.
2. **At editing:** verify statistical anchoring; check for hedging language; verify that the first 200 words include a clear self-contained answer.
3. **At publishing:** verify FAQPage schema if platform supports; verify that named entities and sources are linked where possible.

The discipline adds 15–30 minutes to a pillar piece's production time. It compounds — pieces that extract are still extracting 18 months later.

---

## What to expect

For a Stage 3 operator publishing 2 pillar pieces per month with AEO discipline, citation in authority engines typically begins at month 4–6 and accelerates after month 9. By month 12–18, well-cited pieces produce a meaningful share of new audience reach independent of platform algorithms.

Citation is not the goal. Citation is the side-effect of producing genuinely useful content with the structural patterns authority engines extract well. AEO discipline is content discipline; it does not substitute for the C12 engine.

---

*Update annually. Authority engine extraction patterns evolve as the engines learn. The four patterns above are stable; the platform-specific preferences shift quarterly.*

Complete inspiration-drought reference — D2768 (local corpus extraction)

Download exact original text

# Inspiration Drought Survival Guide

> Reference document supporting M12.8 capstone and the months 2–4 of post-C12 operations. The Inspiration Drought is the predictable pattern where the novelty of the new engine fades, fresh ideas thin, and operators face the choice between holding cadence and waiting for inspiration. This guide names the drought, predicts its arrival, and provides the operating moves that hold the engine through it.

---

## The drought is predictable

Across cohorts, the timeline is consistent:

- **Month 1 (post-C12):** novelty energy carries production. Engine feels good. Drafts come reasonably easily. Capture inbox grows. The operator feels like a producer.
- **Month 2:** novelty fades. The first "I have nothing fresh to say today" mornings arrive. Capture inbox feels less alive — many ideas don't survive triage. Drafting takes longer. The Saturday morning slot starts to feel like work rather than expression.
- **Month 3:** drought conditions clear. Most weeks the operator opens the queue and feels nothing in particular calls to be written. The capacity is there; the inspiration isn't. This is when most engines break.
- **Month 4:** trajectory determined. Either the operator has internalized that the engine produces *despite* drought, or the engine has effectively stopped — cadence missed, slots skipped, channel work drifting toward zero.

The drought is not a failure. It is the predictable consequence of producing on cadence. The engine is the discipline that holds through it.

---

## What the drought is *not*

Misdiagnosis of the drought is what kills engines. Common misdiagnoses:

**"This channel isn't working for me."** The channel hasn't had time to work. C11 channel selection has a 12–24 month commitment specifically because compounding takes that long. Switching channels at month 3 restarts compounding from zero (the C11 Channel Diffusion Trap).

**"My voice has plateaued."** The voice hasn't plateaued; it's deepening. Drought-period work often surfaces what's most authentic in the operator's voice — generic novelty falls away, leaving the specific recurring concerns and stances that define operator voice over the long term.

**"The format library was wrong."** Sometimes formats do need adjustment, but rarely as the first response to drought. Formats that produced good pieces in month 1 will produce good pieces in month 6; the drought is upstream of formats.

**"I'm not a producer after all."** Identity dissonance reactivates during drought. The C12 work on producer identity (M12.1) addressed this; the drought reactivates the question. The answer is the same as in M12.1: the producer identity coheres with the operator identity if the operator's mechanism, audience, and territory have been honestly worked. The drought tests, doesn't refute, the conclusion.

**"I should batch and skip a few weeks."** Batching can be intentional (front-loading 4 pieces in one weekend); skipping is abandonment in a costume. Skipping leads to more skipping. Hold cadence even when each piece is harder.

---

## Operating moves that hold cadence

When the drought arrives, the moves below sustain production.

### Move 1 — Lean on the queue, not on inspiration

The capture system from M12.2 is specifically engineered for this moment. The promoted-idea queue has 8–25 ideas at any given time. The operator does not need to find a new idea today; the operator opens the queue and writes from the next promoted item.

The queue's existence is the answer to drought. The operator's job in drought is *trusting the queue* enough to write from it without waiting for the perfect-feeling idea.

### Move 2 — Lean on the format library

The M12.3 format library is the second answer. Even when the topic feels stale, the format provides structure. A "what success looks like" carousel, executed on a topic the operator has thought about for years, will land — even if the operator doesn't feel particular fresh excitement about it.

Formats produce content. Inspiration produces only sometimes.

### Move 3 — Increase derivative ratio temporarily

In drought weeks, the M12.6 repurposing map provides leverage. Instead of producing 2 originals and 4 derivatives, produce 1 original and 6 derivatives that week. The cadence holds; the pillar production load reduces; the audience experiences continuity.

The operator returns to 2 originals + 4 derivatives in the next week or the week after, when the queue and energy have refilled.

### Move 4 — Use the evergreen buffer

The M12.5 calendar should include 2–3 pre-produced evergreen pieces specifically reserved for drought weeks. When the operator opens the calendar and feels nothing connects, the evergreen piece publishes.

This is not cheating. The evergreen pieces are real work the operator produced earlier, held for moments like this. Their use is a designed feature of the calendar.

### Move 5 — Reduce cycle time, not cadence

If drafting is taking longer than usual, the operator should reduce per-piece cycle time before reducing cadence. Tightening editing time, accepting "good enough" earlier, publishing pieces that are 90% rather than 95% — these are correct moves in drought.

The audience does not benefit from a "more polished" piece that publishes 3 days late and breaks cadence. The audience benefits from on-time pieces at the editorial standard, even if the operator feels the piece could have been refined further.

### Move 6 — Honest 30-second piece

For Twitter or rhythm-format channels, a single substantive 30-second observation drafted and published in 15 minutes total is better than a multi-hour-effort polished thread that doesn't ship. The minimum-viable piece preserves cadence.

This is not the *primary* mode. It is a drought-week mode for when other moves have been exhausted.

### Move 7 — Reflect on what's draughting

Drought sometimes signals real things:

- The channel may genuinely be mismatched to mechanism (verify with C11 review, but rarely the cause at month 3)
- The format library may genuinely need adjustment (some formats produce easily, others struggle — let the data update the library at quarterly review)
- The capture surfaces may be too narrow for sustained cadence — expand surfaces by adding one new one
- Customer work may have decreased, reducing capture surface A's productivity — verify customer work is still happening at expected level

The reflection happens at the quarterly review, not weekly. Weekly drought-response is operating moves 1–6; the strategic reflection is later.

---

## What not to do during drought

**Do not switch channels.** This is the Channel Diffusion Trap from C11; restarts compounding.

**Do not reduce cadence "until inspiration returns."** Cadence is the engine; reducing cadence is engine failure, not a holding pattern.

**Do not increase cadence "to compensate."** More volume does not produce inspiration; it produces faster burnout.

**Do not lean harder on AI assistance.** The drought tempts operators toward AI-assisted volume; AI volume during drought tends to flatten voice precisely when voice differentiation matters most.

**Do not introduce new formats.** New formats require activation energy the operator does not have during drought. Stay in existing formats; expand the format library at quarterly review when energy is higher.

**Do not announce the drought publicly.** Audiences do not benefit from operator self-narration of struggle. If pieces are produced at editorial standard, the audience experiences continuity; the drought is the operator's internal state, not the audience's experience.

---

## Drought-month metrics

What healthy drought operation looks like, measured:

- **Cadence held:** 90–100% of scheduled pieces published (one missed slot in a quarter is acceptable; two is a warning)
- **Quality maintained:** pieces meet M12.4 editorial standards (no quality collapse)
- **Engagement:** likely flat or slightly down (the audience hasn't grown faster, but engagement did not collapse either)
- **Capture inventory:** sustained or slowly growing (drought doesn't kill capture; capture is the source of survival)
- **Voice consistency:** pieces still recognizable as operator voice (drought-produced pieces sometimes feel "less inspired" but are voice-consistent)
- **Operator energy:** lower than month 1, recovering by month 5

---

## After the drought

Most operators emerge from the month 2–4 drought into a new equilibrium in months 5–7. The rhythm becomes habit; producing on cadence stops feeling like activation; the engine runs.

The operators who held cadence through drought have:

- 24–36 published pieces by month 6, vs. typically 8–14 for operators who slipped
- Audience size 2–3× larger by month 9
- A demonstrated track record with their channel that supports the C13 audience compounding work
- Internalized that the engine is the inspiration source, not the inspiration substitute

The operators who did not hold cadence have, by month 6:

- An effectively abandoned channel commitment
- Either restarted on a different channel (Channel Diffusion Trap) or abandoned channel work and reverted to founder-led acquisition
- A C12 engine that exists in documentation but does not run
- The same drought conditions still pending — drought happens to all operators; switching channels does not avoid it, only delays it

---

## The doctrine, restated

**The Engine Beats the Inspiration.**

This is not a rejection of inspiration. Inspiration is real and valuable. The doctrine is that producing on cadence — through the engine of capture, formats, calendar, and workflow — produces *more* inspiration over a 12-month integral than waiting for inspiration to arrive.

The drought is the test of the doctrine. Operators who hold the engine through drought verify the doctrine by experience. Operators who reject the doctrine and wait for inspiration confirm the alternative pattern: inspiration thins, cadence breaks, the channel commitment ends.

Both patterns are real. The choice is the operator's.

---

*Read this before signing the M12.8 doctrine commitment. Re-read at month 2 of post-C12 operations. The drought arrives; the engine holds; the audience compounds.*

Complete channel-format reference — D2543 (local corpus extraction)

Download exact original text

# Channel Format Quick Reference 2026

> Reference document. Format inventory by channel with current 2026 engagement and distribution data. Use as starting library for the M12.3 Format-Library-Worksheet candidate evaluation. Update annually as platform mechanics evolve.

---

## How to use this reference

This is a starting library, not a prescription. Treat each format as a candidate that must score against your specific audience-fit, mechanism-fit, voice-fit, cadence-fit, and compounding-fit (M12.3 rubric). The 2026 engagement data is directional, not predictive — performance varies substantially by territory, voice, and audience.

The 6% Rule applies: from any starting set of formats, the formats that fit your specific operator are a small subset. Most listed here will not be your formats.

---

## LinkedIn (2026)

LinkedIn's 360Brew AI ranking algorithm shifted distribution toward dwell time and saves over likes. Native posts beat link-out posts by ~60% distribution penalty. The first 60 minutes of testing exposes content to 2–5% of network — early dwell time and saves determine broader distribution.

| Format | Description | 2026 engagement profile | Production time |
|---|---|---|---|
| **Document carousel** | 6–12 slides exported as PDF or native carousel; text-led with simple visual hierarchy | Highest dwell time; ~6.6% engagement rate (3–4× single-post baseline); strongest save behavior | 60–120 min |
| **Single-frame insight** | 200–400 word post; one specific point, no thread | Strong if voice is distinctive; baseline ~1.5–2.5% engagement | 30–60 min |
| **Long-form post** | 800–1500 word post; structured with subheads | Higher dwell time than single-frame; risk: most operators write generic long-form that doesn't perform | 90–150 min |
| **Native video <90s** | Vertical video, captions burned in | Algorithm boost in 2026; best for face-led operators with personality | 45–120 min including capture |
| **Polls** | 4-option polls; framing question is the asset | High distribution, low save behavior; useful for audience research, not pillar work | 5–15 min |
| **Comment-as-content** | Substantive 100–300 word comment on someone else's high-distribution post | Underrated; reaches their audience without producing-from-scratch | 15–30 min |
| **Newsletter (LinkedIn-native)** | Subscribed newsletter format on LinkedIn itself | Builds owned reach within LinkedIn; longer cycle but compounds | 90–240 min |
| **Carousel + native video combo** | Carousel pillar with derivative <60s video summary | Strong derivative pattern; 2 pieces from 1 production cycle | +30 min on top of carousel |

**Avoid in 2026:** posts with external links in body (algorithm penalty); over-tagging; over-hashtagging; engagement-bait questions ("Agree?"); generic motivational content (saturation).

---

## Twitter / X (2026)

Algorithm prioritizes reply trees and time-on-platform. Long-form (over 280 chars) gets distribution if it produces engagement; short tweets compound through cumulative volume rather than individual reach. Threads remain the highest-leverage format.

| Format | Description | 2026 engagement profile | Production time |
|---|---|---|---|
| **Tweet (single)** | Up to 280 chars; one specific point | Volume game; individual tweets matter less than cumulative pattern | 5–15 min |
| **Thread** | 7–15 tweets; one developed argument or framework | Highest leverage; compounds through reply trees and bookmarks | 60–120 min |
| **Quote-tweet take** | Reply to existing high-distribution tweet with substantive 100–280 char addition | Reaches target's audience; compounds when target replies | 10–20 min |
| **Long-form (X)** | 280–4000 char post; mini-essay format | Distribution if voice is strong; less platform-native than threads | 30–60 min |
| **Reply-as-content** | Substantive reply in active thread | Volume strategy; 5–10/day for active operators | 5–10 min each |
| **Poll** | 2–4 option polls | Audience research; low compounding | 5 min |

**Avoid in 2026:** engagement-bait one-liners; over-replying to large accounts (algorithmic flag); generic founder-life observations.

---

## Newsletter (2026)

The most durable channel for operators with depth-oriented audiences. Owned subscriber list, no algorithm. Open rates 30–50% common for niche newsletters with strong voice; CTR matters more for downstream conversion than for distribution.

| Format | Description | 2026 engagement profile | Production time |
|---|---|---|---|
| **Long-form essay** | 1500–4000 words; one topic developed | Highest leverage format; pillar for many operators | 4–8 hours |
| **Curated commentary** | 5–8 items with operator commentary on each | Lower production cost; rhythm format | 90–180 min |
| **Case study breakdown** | Specific customer outcome or framework application; 1500–3000 words | Highest mechanism-demonstration value | 3–6 hours |
| **Q&A from subscribers** | Reader questions with substantive answers | Builds subscriber engagement; needs subscriber inflow first | 60–120 min |
| **Field notes** | Short personal observation pieces; 600–1200 words | Voice-led; risk of self-indulgence if not anchored to audience question | 60–90 min |
| **Numbered framework** | "5 ways to X" or "The 7 stages of Y" | Highly bookmarkable; risk of generic over-structure | 90–180 min |

**Avoid in 2026:** generic "weekly digest" newsletters; AI-summarized content with thin operator voice; subject lines that promise more than the body delivers (open rate destruction).

---

## Instagram (2026)

Reels-and-carousel-led platform. Stories function as audience maintenance, not acquisition. Hashtags reduced in importance; SEO via captions and on-screen text increased. Carousel save rates remain platform-leading metric.

| Format | Description | 2026 engagement profile | Production time |
|---|---|---|---|
| **Carousel (10-slide)** | Visual-led; first slide hooks, slides 2–9 develop, slide 10 calls to save/share | Highest save rate; pillar format for visual operators | 90–180 min |
| **Reel <30s** | Vertical video; captions burned in; on-screen hook | Discovery distribution; algorithm-boosted in 2026 | 30–90 min |
| **Reel 30–90s** | Educational or behind-the-scenes; deeper engagement | Better for established audiences; lower distribution boost than <30s | 60–120 min |
| **Single-image post + long caption** | One strong image; 500–1500 char caption | Lower distribution but builds voice/audience depth | 30–60 min |
| **Story (24h)** | Vertical 5–15s; daily rhythm | Audience maintenance, not acquisition | 5–15 min |
| **Story Highlight (curated)** | Selected stories pinned permanently | Profile asset; review quarterly | 30–60 min curation |

**Avoid in 2026:** static feed-only posting without Reels; over-stylized "perfect" aesthetic that reads as inauthentic; trending-audio Reels misaligned to operator voice.

---

## YouTube (2026)

Search + subscription distribution. Long-form (8–25 min) compounds for years. Shorts function as discovery; long-form is conversion. Title and thumbnail matter more than any other variable.

| Format | Description | 2026 engagement profile | Production time |
|---|---|---|---|
| **Long-form video (8–25 min)** | Single topic; depth-oriented | Compounds for years; highest production cost; pillar | 4–12 hours per video |
| **Tutorial (5–15 min)** | Specific how-to; high search distribution | SEO-driven; compounds through search demand | 3–8 hours |
| **Short (<60s, vertical)** | Discovery format; clip-style | High distribution, low conversion to subscriber | 30–90 min including capture |
| **Live stream** | 30–90 min real-time | Audience engagement, not acquisition | Real-time + 30 min setup |
| **Talking-head (face-on-camera, 3–10 min)** | Face-led, conversational; lower production | Voice-led; works if operator can be on camera comfortably | 2–4 hours |

**Avoid in 2026:** intros over 30 seconds; generic "5 tips" titles without specificity; videos without thumbnails optimized for click; sub-5-minute long-form (gets caught in neither short nor long distribution patterns).

---

## TikTok (2026)

Highest-volatility platform. Discovery is algorithmically aggressive; subscriber-to-view conversion is weak. Operators rarely select TikTok primary unless their territory is consumer-facing and their face is part of the value proposition.

| Format | Description | 2026 engagement profile | Production time |
|---|---|---|---|
| **<30s Hook + payoff** | Vertical; first 2 seconds determine distribution | High discovery; low compounding | 30–90 min |
| **<60s educational** | Quick framework or tip; on-screen text-led | Better for B2B-leaning operators | 45–90 min |
| **Series (multi-part)** | 3–8 part series across separate videos | Builds repeat viewers; weak vs other channels | 3–8 hours total |

---

## Substack (2026 specifically)

Newsletter + community + audio + cross-recommendation. Has matured into a distribution platform on top of being an email tool. Notes feature provides Twitter-like rhythm format inside the newsletter ecosystem.

| Format | Description | 2026 engagement profile | Production time |
|---|---|---|---|
| **Long-form newsletter post** | 1500–4000 words | Same as newsletter; benefits from cross-recommendation | 4–8 hours |
| **Note** | Twitter-like short post inside Substack | Surfaces to subscribers + Substack feed | 5–15 min |
| **Podcast embed** | Audio post with text intro | Builds podcast audience inside email | 30–60 min on top of podcast production |
| **Cross-recommendation participation** | Recommending peer Substacks | Reciprocal subscriber growth | 15 min/week |

---

## Format selection patterns (cohort observations)

Across the C11–C12 cohorts, common 3-format selections:

- **B2B service operator on LinkedIn primary:** document carousel (pillar) + single-frame insight (rhythm) + comment-as-content (engagement)
- **Operator on newsletter primary:** long-form essay (pillar) + curated commentary (rhythm) + case study breakdown (depth)
- **Operator on Twitter primary:** thread (pillar) + tweet single (rhythm) + reply-as-content (engagement)
- **Visual operator on Instagram primary:** carousel (pillar) + Reel <30s (rhythm) + story (engagement)
- **Operator on YouTube primary:** long-form video (pillar) + tutorial (rhythm) + Short <60s (discovery)

These are common — not prescriptions. Run the rubric.

---

## What changes in 2027

Reasonable predictions:

- AI-generated content saturation increases; operator voice + specificity remains the differentiator
- Video continues compounding at the expense of static formats on most platforms
- Newsletter and YouTube remain stable; algorithmic platforms continue churning format incentives
- Authority-engine citation (AEO) becomes a primary distribution mechanism alongside platform algorithms

Update this reference annually. The format library is durable; specific format mechanics rotate.

Demonstration

A pilot can test whether buyers value hands-on installation more than a template-only option. State the scope and delivery timing, track support hours and refunds, and compare the result with your assumptions before expanding access.

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

Write the pricing rationale, proof inventory, risk terms, and offer-validation plan. Run the test and retain the results.

Completion standard

The price and terms are clear, claims are supportable, and validation records include buying behavior and delivery evidence.

Next step

Carry the completed work into 03.4 PROOF GATE: Validated Offer Brief. If the proof standard is not met, record the missing evidence or failed test and resolve it before relying on this result.

Starting references

Complete assigned-source appendix

Assigned documents (446)

Open the original document for its full source content. Access follows each document’s existing permissions.

-12steps-salesletter-pdf.pdfPrimary
#2) EastmarkPrimary
#3) Eastmark - Fable ModelPrimary
#5) EastmarkPrimary
✅ RISER Nation — Minimum Viable Offer GPT (Full System Blueprint)Primary
🔥 THE IRRESISTIBLE OFFER ENGINEPrimary
01_PRODUCT_DESCRIPTION — 8.) Offer Mutation Engine (RN_MANAGED)Primary
01. A/B Testing Headlines, Offers, and PricingPrimary
01.75: Keyword Validation Surveys: What They Are & How to Use ThemPrimary
02 File: intake-product-profilePrimary
05_TESTS_AND_EXPERIMENTS_LOGPrimary
11 : Financial_Services_Full_System.docxPrimary
12 : Trades_Home_Services_Full_System.docxPrimary
12-Month-Pricing-Test-Worksheet.mdPrimary
13.) The 5 P's of Product LaunchesPrimary
2 : Local_Services_Full_System_.docxPrimary
4.**Course 14 — Niche Validation & StorySelling**Primary
5 : Digital_Product_Creators_Full_System.docxPrimary
6 : Brick_Mortar_RetailPrimary
A/B Testing WorkbookPrimary
AccessoriesPrimary
ANOTHER TRICKY MARKETERPrimary
Aptitude Comparrisons PricingPrimary
Art & CollectiblesPrimary
BabyPrimary
Bags & PursesPrimary
Based on the sources provided, the 100-module syllabus covers the substance of all 26 topics you listed (000–025)Primary
Bath & BeautyPrimary
behavior-based retargeting, not discounting for desperationPrimary
Below is a professional-grade blind spot + angle analysis of your current RISER Nation AI Video Stream planPrimary
Books, Movies & MusicPrimary
buyer.flippers.keywords.totalsPrimary
C4 Build Handoff — RISER Nation Maritime AcademyPrimary
C4-Module-Map.mdPrimary
Case-Darius-Builder-Operator-C3-Journey.mdPrimary
Case-Darius-Builder-Operator-C4-Journey.mdPrimary
Case-Darius-Builder-Operator-C7-Journey.mdPrimary
Case-Darius-Builder-Operator-C8-Journey.mdPrimary
Case-Failure-Customer-as-Product-Manager-Trap.mdPrimary
Case-Failure-Customer-as-Product-Manager-Trap.mdPrimary
Case-Failure-The-Feature-Stuffing-Trap.mdPrimary
Case-Failure-The-Perfectionism-Trap.mdPrimary
Case-Maya-Teacher-Operator-C2-Journey.mdPrimary
Case-Maya-Teacher-Operator-C4-Journey.mdPrimary
Case-Maya-Teacher-Operator-C7-Journey.mdPrimary
Case-Priya-Service-Operator-C4-Journey.mdPrimary
Case-Priya-Service-Operator-C8-Journey.mdPrimary
CHAPTER 7-THE OFFER ENGINEERING WORKSHOPPrimary
ClothingPrimary
CNX.3.40 – Demographics.docxPrimary
CNX.4.3.9 – Packaging_Coaching_Programs_and_Courses.docxPrimary
CNX.6.17 – Instagram Growth Case Studies (Niklas Pedde Portfolio).docxPrimary
CNX.8.6.4 – Motions_2025_Creative_Trends_Report.pdfPrimary
Craft Supplies & ToolsPrimary
David Frey’s 12 step sales letter formulaPrimary
DETAILED PRODUCT PROMPTPrimary
DIGITAL PRODUCT FINANCERSPrimary
Digital Product Research & Validation WorkbookPrimary
Dog Treats And Affiliates – Sheet.xlsxPrimary
Dog Treats Niche Affiliate Examples – Sheet.xlsxPrimary
Electronics & AccessoriesPrimary
Empirical-Pricing-Validation-Calculator.mdPrimary
Example OfferPrimary
feed_packet_metal_art.docxPrimary
Flip your lifePrimary
gap analysis + improvement outline—written like a world-class course builder auditing a live AI video operationPrimary
GiftsPrimary
GoalDiggers.FB.GROUPSPrimary
GPM.SALESPAGEPrimary
Hardwood Flooring Deficiencies & RisksPrimary
HEALTH SUB NICHESPrimary
Home & LivingPrimary
INSTAGRAM POSTING JOURNEY.docxPrimary
IRRESISTIBLE_OFFER_OS — Folder + File Generator (Upgraded)Primary
JewelryPrimary
LAURA SALES AI STUDIO $97Primary
M10.3 - REFUND ANALYSIS PROTOCOLPrimary
M10.4-Pricing-Validation-Through-Reality.mdPrimary
M3.6 - AI PERSONA MODELING & STRESS TESTINGPrimary
M5.4 - HITL PRICING VALIDATION REVIEWPrimary
M6.3 - ENHANCERS — BONUSES, SCARCITY, URGENCY, GUARANTEESPrimary
membershipguysPrimary
MORE TRICKERYPrimary
Multi-Platform Sales Validation WorkbookPrimary
NOTEBOOK LMPrimary
OP-09 — Offer Framing Engine — Custom GPT System MessagePrimary
Paper & Party SuppliesPrimary
Payment-Processor-Setup-Guide.mdPrimary
Pet SuppliesPrimary
Physical Product Research & Validation WorkbookPrimary
Post-Validation Scaling & Product Development Roadmap (1).docxPrimary
print-on-demand (POD) storePrimary
Problem Angle Brainstormer GPTPrimary
Product Brainstorming & Idea Validation WorkbookPrimary
rehablistseminar-notes.docPrimary
ReOccuring Billing OptionsPrimary
RISER — 8 Offer Mutation Engine — Pricing Window StickerPrimary
RISER NATION NEEDED IMPROVEMENTSPrimary
RISER_SYS_05_OFFER_LOCK.xlsxPrimary
RISER-Beta-Testing-Methodology-SOP.docxPrimary
RISER-Guarantee-Type-Testing-Protocol-SOP.docxPrimary
RISER-Price-Elasticity-Testing-Framework-SOP.docxPrimary
risk_reversal.mdPrimary
SALES COPY EXAMPLESPrimary
sales page copy for the Minimum Viable Offer GPT — written in the voice, structure, and persuasion style used by top AI product creators, ClickFunnels marketers, and 7–8 figure digital offer sellersPrimary
SellHouses.SubdomainsPrimary
ShoesPrimary
SME:AnnouncmentsPrimary
The "Problem-Agitate-Solution" (PAS) FormulaPrimary
THE BEST BAIT IS FREEPrimary
This is a summary of my Etsy notesPrimary
Toys & GamesPrimary
TRICKING YOU WITH HEADLINES AND AD PLACEMENTSPrimary
Untitled documentPrimary
Untitled documentPrimary
Untitled documentPrimary
VCI_Thumbnail_Psychology_Analysis_File04.docxPrimary
VIVE_Case_Study_Eye_Tracking_OvationPrimary
VIVE_Case_Study_Eye_Tracking_Ovation.pdfPrimary
WeddingsPrimary
Workshop Part 3 – Product Validation & Supplier Sourcing ChecklistPrimary
“Creating AI-driven SaaS Businesses”.docxCross-listed
“Reside Platform Podcast: E 58 | ACross-listed
“The Captain's Kit”Cross-listed
***OLD***RISER Nation Marketing Roadmap – Workbook Table of ContentsCross-listed
✅ 1. The Complete RISER Offer Wall Value Ladder (Low → Mid → High Ticket)Cross-listed
📘 RISER NATION – COURSE WORKBOOK & STUDENT WORKSHEETSCross-listed
📘 SOP: The Perfect Webinar FormulaCross-listed
🔄 Overview Comparison ChartCross-listed
🔥 INTRODUCING: OFFER GPT™ — The World’s First AI That Builds Hybrid Offers for YouCross-listed
🧠 Expert Review: Shortfalls, Pitfalls & Areas to ImproveCross-listed
🧠 MASTER CRITIQUE (WHAT NEEDED TO LEVEL UP)Cross-listed
🧩Trello-based training module Sample Prompt for Forge GPTCross-listed
🚀 Your Offer GPT — Final System InstructionsCross-listed
🟣 THE ULTIMATE PRODUCT LAUNCH FRAMEWORKCross-listed
$100K Offer Workbook – Profitable Offer Creation SystemCross-listed
0.)-Launch-to-Scale-Timeline-2026.mdCross-listed
01 – Design Reference Capture (3 Prompts)Cross-listed
01_OFFER_WALL__DIY_DWY_DFY_LicenseCross-listed
02 – Offer Wall Copy (Blunt + Premium)Cross-listed
02. Validating Ideas Using Surveys, Social Media, or Pre-SalesCross-listed
04. Define Digital Product ResearchCross-listed
05. Bottom of Funnel (BOFU) - Offers, Sales Pages, & Conversion TacticsCross-listed
1 : Coaches_Consultants_Full_System.docxCross-listed
1.)The Perfect WebinarCross-listed
1.🎯 COURSE 19 — BOTTOM-FUNNEL CLOSE & INSTAGRAM GROWTHCross-listed
1.📖 COURSE 14 — NICHE VALIDATION & STORYSELLINGCross-listed
1.🪜 COURSE 16 — VALUE LADDER ARCHITECTURECross-listed
10 Products 10 AutomationsCross-listed
11.) Funnels For The AIDCA FormulaCross-listed
11.) THE A.I.D.C.A. FORMULACross-listed
12.) FUNNELS FOR The "5 Ps" of Product LaunchesCross-listed
15.) The "SHOW" MethodCross-listed
2.) One-Sentence Irreristible OfferCross-listed
2.) The Perfect Webinar ScriptCross-listed
2.# Course 14: Niche Validation & StorySellingCross-listed
2.# Course 42: Global Market Expansion – Scale Borderlessly with AI Localization & Region-Based Positioning in 2026Cross-listed
2.COURSE 51 — SYNTHETIC AUDIENCES & PREDICTIVE INTENTCross-listed
2.Course 55 — Buy Triggers & Commercial Intent (2026 Edition)Cross-listed
2024 In AdvertisingCross-listed
2024_comment_secrets_1.pdfCross-listed
3 : Ecommerce_Full_System.docxCross-listed
3.) STAR, STORY, SOLUTIONCross-listed
3.) THE OFFER YOU SELL THEM-SOLVING THE PROBLEMSCross-listed
3.) WHY MY OFFER STANDS OUT!Cross-listed
3.Course 14 — Niche Validation & StorySelling (2026 Edition)Cross-listed
3.COURSE 55 — BUY TRIGGERS & COMMERCIAL INTENTCross-listed
4. L3 – CORE OFFER ($97–$997)Cross-listed
4.Course 55: "Buy Triggers & Commercial Intent" locks in as the agentic buyer magnet — decoding query complexity signals and vibe-based intent to trigger high-ticket purchases from AI agents scanning for Riser Nation solutions (Courses 20-54), deploying JSON-LD schemas and "LLMsCross-listed
5.) HOW THE OFFER WILL HELP THEMCross-listed
5.Course 55 — Buy Triggers & Commercial Intent (Buyer Triggers Department)Cross-listed
6-TIER DELIVERY & PRICING MATRIXCross-listed
6.) AGENT #6: HIGH-CONVERTING VISUAL ASSET COORDINATORCross-listed
6.) LIFE AFTER ACCEPTING MY OFFERCross-listed
6.) THE PROBLEM AGITATE SOLUTION.PAS-VIDEOCross-listed
7 : Course_Creators_Full_System.docxCross-listed
8.) PROBLEM-SOLUTION-DEMOCross-listed
85101Cross-listed
9 : Agencies_Full_System.docxCross-listed
A I BUSINESS SOLUTIONSCross-listed
Alex’s Criteria for Choosing a NicheCross-listed
Anti-Discount-Language-Swipe-File.mdCross-listed
As my business coach I want you to use the contents of the book sway the irresistible pull of irrational Behavior and the contents in that book I want you to use the catalyst by Jonah Berger b e r g e r the Catalyst book and the contents in that book or she is tested advertising methods by Caples I want you to use the ear resistable offer by Joyner I want you to use colors the one thing I want you to implement Dan Sullivan's the who not the how and I want you to create the offers based on what Russell Brunson and Kennedy or Frank Kern would recommend as far as storytelling and Epiphany Bridges and bringing the offer to Market do you understandCross-listed
Audit-Exemplars.mdCross-listed
Audit-Exemplars.mdCross-listed
AVATAR-FILLED OUT READY FOR OFFERCross-listed
B9 – _Store Product Listing Sequence Checklist.xlsxCross-listed
Below is a full hypothetical launch walkthrough for a digital marketing AI product, written from the perspective of a 30-year product launch operator, and explicitly expanded from idea → first 1,000 leads → 5,000 leads → transactions → follow-up → scaleCross-listed
Best Platforms to Sell Your Offer - WorkbookCross-listed
Best-Seller Brainstorm TemplateCross-listed
BUILDING THE PRODUCTCross-listed
Buyer Awareness Keyword JoggersCross-listed
C10-Proof-Threshold-Deployment-SOP.docxCross-listed
C2-README.mdCross-listed
C2-README.mdCross-listed
C3-SOP-04-Market-Fit-Hypothesis-Writing.mdCross-listed
C4-Archetype-Adjustments.mdCross-listed
C4-Course-README.mdCross-listed
C4-Learning-Outcomes.mdCross-listed
C4-Offer-Variants-Worksheet.mdCross-listed
C4-SOP-04-First-Sale-Preparation.mdCross-listed
C5-First-Sale-Conduct-Integrity-Statement.mdCross-listed
C5-First-Sale-Readiness-Pre-Flight-Checklist-Template.mdCross-listed
C5-README.mdCross-listed
C5-Smoke-Test-Request-Script.mdCross-listed
C6-First-Sale-Signal-Analysis-Template.mdCross-listed
C6-First-Sale-Signal-Analysis-Template.mdCross-listed
C8-Community-Prompts.mdCross-listed
Case-Darius-Builder-Operator-C2-Journey.mdCross-listed
Case-Darius-Builder-Operator-C5-Journey.mdCross-listed
Case-Darius-Builder-Operator-C6-Journey.mdCross-listed
Case-Darius-Builder-Operator-C6-Journey.mdCross-listed
Case-Failure-Bespoke-Architecture-Trap.mdCross-listed
Case-Failure-Premature-Lock-In.mdCross-listed
Case-Failure-Premature-Lock-In.mdCross-listed
Case-Failure-Premature-Lock-In.mdCross-listed
Case-Failure-The-Confirmation-Bias-Trap.mdCross-listed
Case-Maya-Teacher-Operator-C3-Journey.mdCross-listed
Case-Maya-Teacher-Operator-C5-Journey.mdCross-listed
Case-Maya-Teacher-Operator-C6-Journey.mdCross-listed
Case-Maya-Teacher-Operator-C6-Journey.mdCross-listed
Case-Maya-Teacher-Operator-C8-Journey.mdCross-listed
Case-Priya-Service-Operator-C2-Journey.mdCross-listed
Case-Priya-Service-Operator-C3-Journey.mdCross-listed
Case-Priya-Service-Operator-C5-Journey.mdCross-listed
Case-Priya-Service-Operator-C6-Journey.mdCross-listed
Case-Priya-Service-Operator-C6-Journey.mdCross-listed
Case-Priya-Service-Operator-C7-Journey.mdCross-listed
Case-Race-to-the-Bottom-Trap-Failure.mdCross-listed
Case-Study-A-Teacher-Operator-Path.mdCross-listed
Case-Study-B-Builder-Operator-Path.mdCross-listed
Case-Study-C-Service-Operator-Path.mdCross-listed
Case-Study-Channel-Diffusion-Trap.mdCross-listed
Case-Study-D-Failure-Case.mdCross-listed
Case-Study-Darius-At-The-Stage-3-Gate.mdCross-listed
Channel-Performance-Validation-Rubric.mdCross-listed
channel-validation-reviewer-v1.0.0.yamlCross-listed
CHAPTER 3 - THE SCIENCE OF CREATING OFFERS PEOPLE FEEL STUPID SAYING NO TOCross-listed
CHAPTER 5 - THE 7-LAYER OFFER ARCHITECTURE BLUEPRINTCross-listed
chaptgpt testCross-listed
CLAUDE OUTPUT ON EXAMPLECross-listed
CNX.3.10.20 – Niche_Validation_AI_Prompt_System.docxCross-listed
CNX.3.11.1 – Offer_Dev_Module_1_Crafting_The_Foundation.docxCross-listed
CNX.3.11.12 – Offer_Dev_SOP_Offer_Recon_Process.docxCross-listed
CNX.3.11.3 – Offer_Dev_Module_3_Crafting_Your_Offer_Strategy.docxCross-listed
CNX.3.11.7 – Offer_Dev_Module_7_Copywriting_And_Messaging_Mastery.docxCross-listed
CNX.3.11.8 – Offer_Dev_Module_8_Bonuses_Value_Stacks_And_Irresistible_Angles.docxCross-listed
CNX.3.37 – SparkToro Example (Audience Insight Research).docxCross-listed
CNX.3.7.8 – 7_Steps_to_Finding_a_100K_Product.pdfCross-listed
CNX.3.9.5.2 – Baader-Meinhof_Frequency_Illusion_and_RAS_Filtering.docxCross-listed
CNX.4-Frameworks.10.19.25Cross-listed
CNX.4.1.1 – Business_Basics_and_Funnel_Hacking_Foundations.docxCross-listed
CNX.4.4.1 – Brain_Driven_Marketing_Workshop_Layout.docxCross-listed
CNX.6.16 – Timeline of Direct Mail Marketing Campaigns in the U.S. (1700s–Present).docxCross-listed
CNX.6.8.23 – Venture Capital Effects on Advertising.docxCross-listed
CNX.9.10 – Framework for Launching a Cohort-Based Course (CBC).docxCross-listed
CNX.9.11 – Framework for Launching a Masterclass.docxCross-listed
CNX.9.18 – Product Matrix.xlsxCross-listed
Content and Product Gaps to Strategically Position Your BrandCross-listed
Copy of Front ExamplesCross-listed
Copy of RISER WORKBOOKCross-listed
Course_31_Video_Scripts_Vol1.docxCross-listed
Course_42_Global_Market_Expansion_RiserNation (1).docxCross-listed
Course_42_Global_Market_Expansion_RiserNation (2).docxCross-listed
Course_42_Global_Market_Expansion_RiserNation.docxCross-listed
Course_9_Video_Scripts_M11-15.docxCross-listed
Course_9_Video_Scripts_M16-20.docxCross-listed
Course42_Video_Scripts_SM6-10.docxCross-listed
Cross-Case-Framework.mdCross-listed
Cross-Case-Framework.mdCross-listed
Custom GPT Creation Guide – Book Summary FrameworkCross-listed
Darius-At-The-Gate.mdCross-listed
Darius-First-Retreat.mdCross-listed
David Frey’s 12-Step Foolproof Sales Letter Template.docxCross-listed
demoCross-listed
Digital Creator Offer Workbook.docxCross-listed
Digital Offer Creation WorkbookCross-listed
ETSY STORECross-listed
EXPANDED_MODULE_DESCRIPTIONS_AI_OPTIMIZEDCross-listed
Failure-Case-Aspirational-Threshold-Trap.mdCross-listed
Failure-Case-Skipped-Retreat-Trap.mdCross-listed
Financial Projections: Sonoran Desert Painting BusinessCross-listed
first-sale-readiness-reviewer-v1.0.0.yamlCross-listed
Four-Quadrant-Pricing-Matrix-Framework.mdCross-listed
FreedomHomeBuyerCross-listed
FUNNEL PROGRESSION CLOSERS AND FINANCINGCross-listed
GENERAL VIRAL VIDEO LOGS.xlsxCross-listed
GOOGLE SEARCH FOR : marketing plan template for product launchCross-listed
Groups ResearchCross-listed
Here are the **top 10 practical ways** to add value to what you sellCross-listed
high-converting product page copy for selling your Template Architect GPT as a premium digital productCross-listed
How To Sell Digital Products Online (I Make $800k/Month)Cross-listed
https://chatgptCross-listed
https://chatgptCross-listed
https://chatgptCross-listed
https://copilotCross-listed
https://www.perplexity.aiCross-listed
Identifying the Best Platforms to Sell Your Offer OnlineCross-listed
jtbd_2026_offers (1).mdCross-listed
jtbd_2026_offers.mdCross-listed
jtbd_2026_underserved_jobs_report.pdfCross-listed
KEYWORDS BY CITYCross-listed
LACK OF SLEEPCross-listed
M10.3-Refund-and-Outcome-Analysis.mdCross-listed
M2.8-Written-Lesson.mdCross-listed
M2.8-Written-Lesson.mdCross-listed
M20.2 - LOGO DESIGN (CANVA-FIRST)Cross-listed
M25.7 - SMALL LANGUAGE MODELS (SLMS)Cross-listed
M26.12 - THE CLAUDE CHROME MINI-PRODUCTCross-listed
M27.2 - THE FAST-CASH MICRO-MVO ALTERNATE PATHCross-listed
M4.3 - StorySelling Validation (Pre-Selling)Cross-listed
M5.5-Written-Lesson.mdCross-listed
M5.5-Written-Lesson.mdCross-listed
M6.5 - SCENARIO-BASED GUARANTEES (KENNEDY WHAT-IF)Cross-listed
M8.1-Video-Spec.mdCross-listed
M8.4-Written-Lesson.mdCross-listed
M8.4-Written-Lesson.mdCross-listed
M8.8 - AI AS COPY CO-PILOTCross-listed
Marketing Channels SOPCross-listed
Maya-At-The-Gate.mdCross-listed
Maya-First-Retreat.mdCross-listed
Mindy.housesCross-listed
Minimum_Viable_Offer_QuickStart_Dark_v3.pdfCross-listed
Module 027 — Authority Content (Case Studies — PromptCross-listed
Module 044 — High-Ticket & Application Funnel Design — PromptCross-listed
Module 045 — Low-Ticket & Tripwire Funnel Design — PromptCross-listed
MVO_Prelaunch_Validation_Kit.xlsxCross-listed
MVO-Sales-Letter.mdCross-listed
MVO-Sales-Letter.mdCross-listed
Niche Validation and Campaign Launch WorkbookCross-listed
NICHE-CORE OFFERS (A-A)Cross-listed
Now building the upgraded interactive pricing tool with all 8 improvements:The widget above is fully interactive — switch between Consumer, Prosumer, and Business Owner to see prices recalibrate across all tiers, toggle between Launch and Evergreen pricing, and watch the value ratio and credit ascension numbers update in real timeCross-listed
offer-decomposition-reviewer-v1.0.0.yamlCross-listed
offer-distinction-reviewer-v1.0.0.yamlCross-listed
offer-fit-validator-v1.0.0.yamlCross-listed
offer-iteration-reviewer-v1.0.0.yamlCross-listed
offer-iteration-reviewer-v1.0.0.yamlCross-listed
OP_06_15_BUILD — README (what lives here)Cross-listed
OP-09 — OFFER FRAMING ENGINECross-listed
OP-23 — Case-Study Fuel Injector (Niche Playbook Generator) — Custom GPT System MessageCross-listed
OP-25 — BrandShield Compliance Sentinel (Claims, Risk, Platform Policy) — Custom GPT System MessageCross-listed
original 100 course modules with descriptionsCross-listed
Perfect — now we’re stepping into pure platform leverage modeCross-listed
Phase 2 – Core Offer CreationCross-listed
Physical Product Offer PROMPTCross-listed
Price-Raise-Schedule-Template.mdCross-listed
Pricing-Architecture-Document-Template.mdCross-listed
pricing-architecture-reviewer-v1.0.0.yamlCross-listed
pricing-discipline-validator-v1.0.0.yamlCross-listed
Pricing-Is-Operator-Self-Respect-Framework.mdCross-listed
Pricing-Math-Spreadsheet-Template.mdCross-listed
pricing-validation-reviewer-v1.0.0.yamlCross-listed
Priya-At-The-Gate.mdCross-listed
Priya-First-Retreat.mdCross-listed
Problem-Solution-DemonstrationCross-listed
PRODUCT CLASS 5 - Jason FladlienCross-listed
PROMPTSCross-listed
Proven Copywriting Formulas (AIDA, PAS, Story-Solution, 4 Ps, Epiphany Bridge, etcCross-listed
QA_TEST_HARNESS — prompts to validate behaviorCross-listed
QM-Audit-C10-Scorecard.xlsxCross-listed
QM-Audit-C10.jsonCross-listed
QM-Audit-C12-Scorecard.xlsxCross-listed
QM-Audit-C12.jsonCross-listed
QM-Audit-C9-Scorecard.xlsxCross-listed
QM-Audit-C9.jsonCross-listed
QM-Audit-Notes.mdCross-listed
QM-Audit-Notes.mdCross-listed
Researching & Identifying Top Performing Physical Products in Your NicheCross-listed
RISER — 0 Sonars Flow Chart — Product Description + Sales LetterCross-listed
RISER — 1 Current Scope — Product Description + Sales LetterCross-listed
RISER — 2 Tide Lock — Product Description + Sales LetterCross-listed
RISER — 3 Shark Radar — Product Description + Sales LetterCross-listed
RISER — 4 Anchor Point — Product Description + Sales LetterCross-listed
RISER — 5 Portfolio Governor — Product Description + Sales LetterCross-listed
RISER — 6 Buoy Builder — Product Description + Sales LetterCross-listed
RISER — 7 Rigging Forge — Product Description + Sales LetterCross-listed
RISER — 8 Offer Mutation Engine — Product Description + Sales LetterCross-listed
RISER · Captain's Logic Operating Doctrine · v1Cross-listed
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 interpretationCross-listed
RISER_Nation_Black_Friday_Competitive_Analysis_FormatB.docxCross-listed
RISER_Nation_Offer_Marketing_Engine_v3_(Step_8).docxCross-listed
RISER_Nation_SALES LETTER COPY_RISER Nation Offer Generator — SuperPrompt v2025.docxCross-listed
RISER_Prompt_System_Marketability_Analysis (1).docxCross-listed
RISER-Affiliate-Program-Architecture-SOP.docxCross-listed
RISER-Behavioral-Logic-Nudge-Theory-SOP.docxCross-listed
RISER-Dead-Offer-Resurrection-Playbook-SOP.docxCross-listed
RISER-Downsell-Paths-SOP.docxCross-listed
riser-first-dollar-forge-v3 (2).htmlCross-listed
riser-first-dollar-forge-v3.htmlCross-listed
riser-first-dollar-forge.htmlCross-listed
RISER-Funnel-Hacking-Methodology-SOP.docxCross-listed
RISER-JV-Deal-Structures-Commission-Terms-SOP.docxCross-listed
RISER-Master-SOP-Catalogue (1).docxCross-listed
RISER-Master-SOP-Catalogue (3).docxCross-listed
RISER-MVO-Widget-Explainer-Script.docxCross-listed
RISER-Offer-Scorecard-SOP.docxCross-listed
riser-offer-stackCross-listed
riser-offer-stack (1).htmlCross-listed
riser-offer-stack.htmlCross-listed
RISER-Offer-Stacking-Unbundling-Strategy-SOP.docxCross-listed
RISER-Operators-Flow.htmlCross-listed
RISER-Operators-Flow.mdCross-listed
RISER-Pricing-Architecture.docxCross-listed
RISER-Problems-Create-Markets-SOP.docxCross-listed
RISER-Product-Kill-Criteria-Post-Launch-SOP.docxCross-listed
RISER-Product-Versioning-Offer-Changelog-SOP.docxCross-listed
RISER-Proof-Injection-Checklist-SOP.docxCross-listed
RISER-Sales-Page-Architecture-SOP.docxCross-listed
RISER-Social-Media-Sales-Package-Vol2.docxCross-listed
RISER-Social-Media-Sales-Package-Vol3.docxCross-listed
RISER-Step-1.1-Idea-Capture.htmlCross-listed
RISER-Step-1.1-Idea-Capture.htmlCross-listed
RISER-VSL-Script-Template-SOP.docxCross-listed
RISER-White-Label-Pricing-Architecture-SOP.docxCross-listed
RN-10_Product_Optimization_CreatorFlow_2025_POPULATED.docxCross-listed
sales letter for the Video Copywriter GPT, including clear pricing tiers and irresistible offer framingCross-listed
selling frameworksCross-listed
SME :DISCUSSIONCross-listed
SOP - Step 5Cross-listed
SOP-3-Channel-Performance-Validation.yamlCross-listed
SSM_01_Product_DescriptionCross-listed
Standard Operating Procedure (SOP) & Training Document for A/B TestingCross-listed
STRATEGIC RECALIBRATION: THE DIRECT RESPONSE LENSCross-listed
Strategic_Intelligence_Report_2026.docxCross-listed
Stripe-Pricing-Setup-Guide.mdCross-listed
The "Problem-Agitate-Solution" (PAS) Formula adapted for videoCross-listed
The "Star, Story, Solution" MethodCross-listed
THE BEAVER BUILDER THEME ARCHITECT GPT™sales page for your new product:Cross-listed
THE COMPLETE OFFER ECOSYSTEM: FUNNEL STAGE MAPPING + INTENT-BASED AUTOMATIONCross-listed
THE GENEALOGY OF PRODUCT LAUNCHING: THOUGHT LEADERS & THEIR LINEAGECross-listed
The Invisible Affiliate System – Sales Script & Tactics Analysis.docxCross-listed
The Irresistible Offer Creation Process: What You Do, in Chronological OrderCross-listed
THE ONE TIME OFFER SCRIPT (OCross-listed
The Product Launch Sequence (SCRIPT)Cross-listed
THE RISER NATION MASTER BLUEPRINTCross-listed
The three documents, everything we've built, and the core RISER framework all point to the same answer here: the newbie's $1,000 problem is not a marketing problemCross-listed
Tier-Appropriateness-Diagnostic-Worksheet.mdCross-listed
TikTok Shop / Affiliate / Product Viral ScriptsCross-listed
Untitled documentCross-listed
VALIDATE YOUR IDEA SOPCross-listed
VIDEO KEYWORDSCross-listed
VIDEO SALES LETTERCross-listed
WEALTH SUB NICHESCross-listed
What C3 Buoy Navigation is, based on what C1 and C2 set upCross-listed
Workshop Part 6 – Creative Testing & Performance Tracking SystemCross-listed
World-Class Minimum Viable Offer (MVO) — Standard Action PlanCross-listed

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.

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.
Stage 5 â Decline (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.

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	â 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	â

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.

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)	___

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.

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

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.

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

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.

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.

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.

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

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.

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.
Stage 5 â Decline (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.

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	â 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	â

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.

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)	___

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.

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

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.

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

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.

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.

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.

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

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.

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.