RISER NATION CORP

“IF YOU AREN'T BUILDING, YOU ARE DESTROYING”

COURSE 12 OF 12

Ceo, Agents & Scale

Offer development and operating practice — source-linked curriculum

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

Lesson 12.4

riser-first-dollar-forge-v3 (2).html — source 1 · riser-first-dollar-forge-v3 (2).html — source 2 · Study in lesson 12.4
riser-first-dollar-forge.html — source 1 · Study in lesson 12.4
RISER-Funnel-Hacking-Methodology-SOP.docx — source 1 · Study in lesson 12.4
RISER-JV-Deal-Structures-Commission-Terms-SOP.docx — source 1 · Study in lesson 12.4
RISER-Master-SOP-Catalogue (1).docx — source 1 · RISER-Master-SOP-Catalogue (1).docx — source 2 · Study in lesson 12.4
RISER-MVO-Widget-Explainer-Script.docx — source 1 · Study in lesson 12.4
RISER-Offer-Stacking-Unbundling-Strategy-SOP.docx — source 1 · Study in lesson 12.4
RISER-Operators-Flow.html — source 1 · Study in lesson 12.4
RISER-Operators-Flow.md — source 1 · Study in lesson 12.4

Lesson 12.5

Offer design and operating-system resources

Open each assigned source or its teaching section.

Lesson 12.1

Lesson 12.2

Lesson 12.4

Lesson 12.5

RISER · Captain's Logic Operating Doctrine · v1 — source · Study this source in lesson 12.5

Assigned audit and sales-letter resources

Open the supporting documents or go directly to their teaching sections. These resources follow the course and lesson assignments.

Lesson 12.1

QM-Audit-C9-Scorecard.xlsx — original document · Study QM-Audit-C9-Scorecard.xlsx in Lesson 12.1

Lesson 12.2

Lesson 12.4

RISER — 0 Sonars Flow Chart — Product Description + Sales Letter — original document · Study RISER — 0 Sonars Flow Chart — Product Description + Sales Letter in Lesson 12.4

Course 12 — sources for the added teaching sections

Course 12 — offer design, launch and retention sources

Real-estate and creation platforms referenced in this course

Course 12 — sources for the added teaching sections

Operate the business through evidence, clear ownership, supervised agents, and quarterly priorities.

Start with: Bring the completed course deliverables, current business numbers, and open risks.

Framework connection: Connect the full market-to-MRR system. Use constraint-based operating decisions to protect the offer, acquisition economics, delivery quality, and continuing customer value.

What will you learn in Ceo, Agents & Scale?

Operate the business through evidence, clear ownership, supervised agents, and quarterly priorities.

What should you complete first?

Bring the completed course deliverables, current business numbers, and open risks.

How do you use the lessons?

Follow the course outline in order. Open each lesson for its written teaching, implementation tasks, and assigned source links. Source access follows the original document permissions.

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)	___

Ceo, Agents & Scale

Offer development and operating practice — source-linked curriculum

Lesson 12.4

Lesson 12.5

Offer design and operating-system resources

Lesson 12.1

Lesson 12.2

Lesson 12.4

Lesson 12.5

Assigned audit and sales-letter resources

Lesson 12.1

Lesson 12.2

Lesson 12.4

What will you learn in Ceo, Agents & Scale?

What should you complete first?

How do you use the lessons?

Course curriculum

Lessons and implementation

Supporting documents and teaching sections

Supporting documents and teaching sections

Full lesson teaching and supporting documents

Supporting documents and teaching sections

Supporting documents and teaching sections

Full lesson teaching and supporting documents

Full lesson teaching and supporting documents

Assigned documents and teaching

Supporting documents and teaching sections

Supporting documents and teaching sections

Full lesson teaching and supporting documents

Assigned documents and teaching

Supporting documents and teaching sections

Full lesson teaching and supporting documents

Additional assigned lesson teaching and sources

RISER-Product-Kill-Criteria-Post-Launch-SOP

Assess an underperforming offer and preserve what the evidence teaches

Separate the next decision from the past investment

Identify six forms of sunk-cost reasoning

Match the review to the offerâs stage

Phase 1 â Examine six fixable problems

Phase 2 â Read all seven hard-trigger conditions precisely

Phase 3 â Use the fifteen-dimension, sixty-point scorecard

Read the qualifiers as well as the total

Phase 4 â Distinguish retirement, structural change and targeted iteration

Phase 5 â Preserve buyers and records when studying closure

Phase 6 â Record what happened without claiming more than the evidence shows

Phase 7 â Examine every relaunch requirement

Phase 8 â Review inactive offers without confusing silence with failure

Preserve the separate database schema

Review the complete source checklist

Resources and turn-in

D0940 â complete original document appendix

word/header1.xml

word/footer1.xml

word/footnotes.xml

word/endnotes.xml

word/comments.xml

RISER-Product-Versioning-Offer-Changelog-SOP

Keep an offerâs promises, delivery and records aligned as it changes

Identify what changed, why and who is affected

Phase 1 â Distinguish major, minor and patch changes

Phase 2 â Classify the change and flag ambiguous cases

Phase 3 â Record the complete changelog entry

Phase 4 â Check all four affected groups

Phase 5 â Keep every affected asset synchronized

Preserve testimonial context

Phase 6 â Match communication to the actual change

Phase 7 â Keep a usable archive and version timeline

Phase 8 â Investigate a possible rollback

Phase 9 â Review the history at the right cadence

Preserve all three database specifications

Use the complete master checklist

Resources and turn-in

D0941 â complete original document appendix

word/header1.xml

word/footer1.xml

word/footnotes.xml

word/endnotes.xml

word/comments.xml

Offer development and operating practice — source-linked curriculum

Lesson 12.1

Match the review to the offerâs stage

Phase 1 â Examine six fixable problems

Phase 2 â Read all seven hard-trigger conditions precisely

Phase 3 â Use the fifteen-dimension, sixty-point scorecard

Phase 4 â Distinguish retirement, structural change and targeted iteration

Phase 5 â Preserve buyers and records when studying closure

Phase 6 â Record what happened without claiming more than the evidence shows

Phase 7 â Examine every relaunch requirement

Phase 8 â Review inactive offers without confusing silence with failure

D0940 â complete original document appendix

Keep an offerâs promises, delivery and records aligned as it changes

Phase 1 â Distinguish major, minor and patch changes

Phase 2 â Classify the change and flag ambiguous cases

Phase 3 â Record the complete changelog entry

Phase 4 â Check all four affected groups

Phase 5 â Keep every affected asset synchronized

Phase 6 â Match communication to the actual change

Phase 7 â Keep a usable archive and version timeline

Phase 8 â Investigate a possible rollback

Phase 9 â Review the history at the right cadence

D0941 â complete original document appendix

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.