← Vault Index
Source: frameworks/kit-slo-page-production/03-slo-page-production-golden-example.md

03 — GOLDEN EXAMPLE: SLO Page Production Cascade

This golden example shows what a properly executed cascade looks like — from audit through strategy through build through final QC report. It demonstrates the AUDIT phase catching a missing pixel AND a missing compliance link before the build begins.


The Brief

Page: OTO1 page for Scale Checklist 2.0 funnel — 26 Keys diagnostic at $97
Page type: oto-page
SFB component: Component 5 — OTO1
Slug: /scale-checklist-oto1
Brand: AOS (charcoal/cream/gold, Cormorant Garamond + Inter)
Meta Pixel ID: 614207384629153
CTA: "Yes! Add 26 Keys for $97" --> SamCart OTO accept URL
Secondary: "No thanks, skip this offer" --> next OTO page
Funnel position: Post-checkout, OTO1 of 3 (ascending: $97 → $297 → $297)
noindex: Yes
Compliance entity: Advisory OS
OTO video status: Filmed (60s, webcam-over-slides, Loom)
Take rate target: 10-15%

PHASE 1: AUDIT (SFB 6-Layer Framework)

Before building this OTO1 page, audit the existing funnel state. What exists? What's missing? What has gaps?

Existing Funnel State (Gathered From Brief + Funnel Inventory)

Component 1 — Tripwire Product:     Scale Checklist 2.0, $7-27, checklist format ✅
Component 2 — Sales Page:           EXISTS — needs audit ⚠️
Component 3 — SamCart Checkout:      EXISTS — bumps configured ✅
Component 4 — Order Bumps:          Bump 1 configured, take rate healthy ✅
Component 5 — OTOs:                 OTO1 page BUILDING NOW. OTO2 exists. OTO3 exists.
Component 6 — OTO Videos:           OTO1 filmed ✅. OTO2 filmed ✅. OTO3 NOT FILMED 🔴
Component 7 — Compliance Footer:    AUDIT NEEDED ⚠️
Component 8 — Post-Purchase Emails: 10 emails configured ✅

Layer-by-Layer Audit

LAYER 1 — Tripwire Product: GREEN

LAYER 2 — Sales Page: YELLOW

BLOCKING FINDING: Sales page has 4 of 5 compliance links. Contact link is missing. This must be fixed on the existing sales page AND included on the OTO1 page being built. SFB Failure Mode #8: "Skipping compliance footer — Meta CPMs spike 2-3x."

LAYER 3 — Checkout + Bumps: GREEN

LAYER 4 — OTOs: YELLOW

CRITICAL FINDING: OTO3 video not filmed. Take rate at 0%. This is SFB Failure Mode #1: "Skipping OTO videos — single biggest revenue leak. Ben's own OTO3 lesson." Flag for immediate video production.

LAYER 5 — Post-Purchase Sequence: GREEN

LAYER 6 — Back-End Ascension: GREEN

Audit Summary

─────────────────────────────────────
FUNNEL AUDIT — SCALE CHECKLIST 2.0
─────────────────────────────────────
OVERALL: YELLOW — two blocking issues found before build

LAYER 1 — Tripwire Product:        🟢 GREEN
LAYER 2 — Sales Page:              🟡 YELLOW (compliance footer incomplete — 4/5 links)
LAYER 3 — Checkout + Bumps:        🟢 GREEN
LAYER 4 — OTOs (videos check):     🟡 YELLOW (OTO3 video not filmed — 0% take rate)
LAYER 5 — Post-Purchase Sequence:  🟢 GREEN
LAYER 6 — Back-End Ascension:      🟢 GREEN

BLOCKING ISSUES (must fix before/during build):
1. Sales page missing Contact link in compliance footer (4/5) — fix NOW
2. OTO3 video not filmed — take rate 0% — schedule filming

NON-BLOCKING (track):
3. OTO2 and OTO3 same price ($297) — acceptable per SFB model but monitor

PHASE 2: STRATEGY (Gap-to-Component Mapping)

Build Order

Based on the audit, here is the prioritized build plan:

PriorityWhatSFB ComponentBuild ModeStatus
1Fix compliance footer on existing sales page (add Contact link)Component 7Mode 6 — Compliance FooterBlocking — fix first
2Build OTO1 page (this brief)Component 5Mode 2 — Sales Page (OTO variant)The page we're building
3Film OTO3 video (60-90s, Loom)Component 6Mode 4 — OTO Sales VideosFlag to Kathryn — requires human action

Acceptance Criteria for OTO1 Page (from SFB)

RequirementSourceCriterion
60-90s sales video embeddedSFB Component 6Video present, follows Hook/Reframe/Offer/Risk/CTA formula
Compliance footer (5 links)SFB Component 7All 5 links: Privacy, Terms, Disclaimer, Returns/Refunds, Contact
Meta Pixel with correct eventsCampaign launch playbookPageView (OTO pages fire PageView only — conversion tracked at checkout)
OTO ascending logic visibleSFB Component 5Price context: "$97 — normally $197" with yes/no CTA
"No thanks" link small + below foldSFB audit Layer 4De-emphasized skip link
Risk reversalSFB Component 5Guarantee language present
Take rate targetSFB benchmarks10-15% (track after launch)

PHASE 3: BUILD

Step 1: Brief Validation (Pre-Build Gate)

CheckResultNotes
Pixel ID present and numericPASS614207384629153 (15 digits)
Page type maps to known typePASSoto-page
SFB component mapping explicitPASSComponent 5 — OTO1
CTA destination URL confirmedPASSSamCart OTO accept URL confirmed live
Compliance entity confirmedPASS"Advisory OS"
Convertri slug confirmedPASS/scale-checklist-oto1 configured in Convertri
Brand system specifiedPASSAOS
OTO video status confirmedPASSFilmed, 60s, Loom

Pre-build gate: PASS. Proceeding to build.

Audit-driven pre-build action: Before building this page, fix the existing sales page compliance footer (add Contact link). Confirmed done. Proceeding.


Step 2: Requirements Identification

RequirementValue
Page typeoto-page
SFB componentComponent 5 — OTO1
Required pixel eventsPageView
Purchase value neededNo (OTO conversion tracked via SamCart, not page pixel)
Compliance footerFull 5-link set
Meta disclaimerYes (page is in paid funnel)
Anthropic disclaimerNo (no AI tools referenced on OTO page)
Earnings disclaimerYes (diagnostic implies business outcomes)
noindex/nofollowYes
Terminology contextPaid (no LLM brand names)
OTO videoRequired — confirmed filmed

Step 3: HTML Build

Page built following SFB Build Skill Mode 2 (Sales Page, OTO variant) + page-type kit. Key structural elements:

Head section contains:

<meta name="robots" content="noindex, nofollow">

<!-- Meta Pixel Code -->
<script>
!function(f,b,e,v,n,t,s)
{if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};
if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';
n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];
s.parentNode.insertBefore(t,s)}(window, document,'script',
'https://connect.facebook.net/en_US/fbevents.js');
fbq('init', '614207384629153');
fbq('track', 'PageView');
</script>
<noscript><img height="1" width="1" style="display:none"
src="https://www.facebook.com/tr?id=614207384629153&ev=PageView&noscript=1"
/></noscript>
<!-- End Meta Pixel Code -->

OTO video section (SFB Component 6 — NON-NEGOTIABLE):

<section class="oto-video">
  <h2>Wait! Before you go...</h2>
  <div class="video-embed">
    <!-- 60s Loom embed — Hook/Reframe/Offer/Risk/CTA formula -->
    <div style="position: relative; padding-bottom: 56.25%; height: 0;">
      <iframe src="https://www.loom.com/embed/[VIDEO_ID]"
        frameborder="0" webkitallowfullscreen mozallowfullscreen
        allowfullscreen style="position: absolute; top: 0; left: 0;
        width: 100%; height: 100%;"></iframe>
    </div>
  </div>
</section>

Footer contains (SFB Component 7 — all 5 links):

<footer>
  <p>&copy; 2026 Advisory OS. All rights reserved.</p>
  <div class="footer-links">
    <a href="/privacy">Privacy Policy</a>
    <a href="/terms">Terms of Service</a>
    <a href="/disclaimer">Disclaimer</a>
    <a href="/returns">Returns & Refunds</a>
    <a href="/contact">Contact</a>
  </div>
  <p class="disclaimer">This site is not a part of the Facebook website
  or Facebook Inc. Additionally, this site is NOT endorsed by Facebook
  in any way. FACEBOOK is a trademark of FACEBOOK, INC.</p>
  <p class="disclaimer">Results vary. The examples shared are not
  guarantees of specific outcomes.</p>
</footer>

Responsive CSS uses class selectors:

/* Correct -- class selectors */
@media (max-width: 1024px) {
  .oto-content { max-width: 100%; padding: 40px 20px; }
  .video-embed { max-width: 100%; }
}
@media (max-width: 768px) {
  .oto-headline { font-size: 1.6rem; }
  .cta-yes { width: 100%; }
  .cta-no { width: 100%; }
}
@media (max-width: 480px) {
  .oto-headline { font-size: 1.3rem; }
  .footer-links { flex-direction: column; }
}

Step 4: Gate Results

Gate 1 — Meta Pixel Verification

CheckResult
Pixel base code present in PASS
Pixel ID matches brief (614207384629153)PASS
fbq('init', '614207384629153') presentPASS
fbq('track', 'PageView') presentPASS
No conversion event (correct for oto-page — conversion tracked via SamCart)PASS
PASS

Gate 1: PASS

Gate 2 — Compliance Footer (SFB Component 7)

CheckResult
Privacy Policy link presentPASS
Terms of Service link presentPASS
Disclaimer link presentPASS
Returns & Refunds link presentPASS
Contact link presentPASS
All 5 links present (not 4, not 3)PASS — count verified: 5
Copyright line with correct entity namePASS
Meta disclaimer presentPASS
Earnings disclaimer presentPASS

Gate 2: PASS

Gate 3 — SFB Component Check (OTO-Specific)

CheckResult
OTO video embedded (60-90s)PASS — 60s Loom embed present
Video follows Hook/Reframe/Offer/Risk/CTA formulaPASS — verified against script
OTO ascending logic: price context visiblePASS — "$97 — normally $197"
"Yes" CTA prominentPASS
"No thanks" link small + below foldPASS
Risk reversal / guarantee presentPASS

Gate 3: PASS

Gate 4 — Terminology Sweep

CheckResult
Zero instances of "AI assistant"PASS
Zero instances of "Claude" (paid context)PASS
Zero instances of "ChatGPT" (paid context)PASS
Zero instances of "Gemini" (paid context)PASS
Zero instances of old pricingPASS
Zero instances of old URLsPASS

Gate 4: PASS

Gate 5 — Copy QC (11 Patterns)

PatternSeverityResult
P1: TwinningP1PASS
P1: Mirror ReversalP1PASS
P1: Question-Revelation ArcP1PASS
P2: Three-Beat Parallel ListsP2PASS
P2: Not Because X. Because Y.P2PASS
P2: Over-ValidationP2PASS (N/A)
P2: Formulaic SetupP2PASS
P2: Trying-to-Be-QuotableP2PASS
P3: Dramatic Single-Word BeatsP3PASS
P3: Rhetorical Hand-HoldingP3PASS
P3: Identical Sentence OpenersP3PASS
Compound checkP1PASS

Gate 5: PASS

Gate 6 — Sentence Editor (8 Rules)

RuleResult
Sentence length variationPASS
No filler wordsPASS
Active voicePASS
No weak openingsPASS
Specific over vaguePASS
No hedging in CTAPASS
Concrete nounsPASS
Every sentence earns its placePASS

Gate 6: PASS

Gate 7 — Mobile/Responsive Check

CheckResult
1024px breakpointPASS
768px breakpointPASS
480px breakpointPASS
Class selectors onlyPASS
No var() CSSPASS
Video responsive on mobilePASS

Gate 7: PASS

Gate 8 — Link Verification

LinkDestinationResult
"Yes" CTASamCart OTO accept URLPASS
"No thanks"Next OTO pagePASS
Privacy Policy/privacyPASS
Terms of Service/termsPASS
Disclaimer/disclaimerPASS
Returns & Refunds/returnsPASS
Contact/contactPASS

Gate 8: PASS

Gate 9 — Pixel Event Verification (MANUAL)

Expected EventFiresValue
PageViewConfirm in Pixel Helper--

Gate 9: MANUAL CONFIRMATION REQUIRED

Gate 10 — Visual Check (Desktop + Mobile) (MANUAL)

Gate 10: MANUAL CONFIRMATION REQUIRED


Final QC Report

PAGE PRODUCTION CASCADE — QC REPORT
=====================================

PAGE: /scale-checklist-oto1 (OTO1 — 26 Keys Diagnostic $97)
TYPE: oto-page
SFB COMPONENT: Component 5 — OTO1
BRAND: AOS
PIXEL EVENTS: PageView

SFB AUDIT SUMMARY:
  Funnel: Scale Checklist 2.0
  Layer 1 — Tripwire: GREEN
  Layer 2 — Sales Page: YELLOW → FIXED (Contact link added to compliance footer)
  Layer 3 — Checkout + Bumps: GREEN
  Layer 4 — OTOs: YELLOW (OTO3 video not filmed — flagged for production)
  Layer 5 — Post-Purchase: GREEN
  Layer 6 — Back-End: GREEN
  Blocking issues found and resolved before build: 1 (compliance footer)
  Blocking issues flagged for separate action: 1 (OTO3 video)

GATE RESULTS:
  1. Meta Pixel Verification        PASS
  2. Compliance Footer (5 links)    PASS (all 5 verified by count)
  3. SFB Component Check (OTO)      PASS (video present, ascending logic, risk reversal)
  4. Terminology Sweep              PASS
  5. Copy QC (11 patterns)          PASS
  6. Sentence Editor (8 rules)      PASS
  7. Mobile/Responsive Check        PASS
  8. Link Verification              PASS
  9. Pixel Event Verification       PENDING (manual — Pixel Helper)
  10. Visual Check (Desktop+Mobile) PENDING (manual)

AUTOMATED GATES: 8/8 PASS
MANUAL GATES: 2 awaiting confirmation

SCORE: 95/100 (automated checks)
STATUS: Ready for manual verification, then Kathryn approval

BLOCKING FAILURES: 0

LINKS VERIFIED:
  "Yes" CTA → SamCart OTO accept URL
  "No thanks" → next OTO page
  Privacy Policy → /privacy
  Terms of Service → /terms
  Disclaimer → /disclaimer
  Returns & Refunds → /returns
  Contact → /contact

PIXEL CONFIGURATION:
  Pixel ID: 614207384629153
  Events: PageView

COMPLIANCE:
  Footer links: 5/5 ✅
  Meta disclaimer: present
  Earnings disclaimer: present
  Anthropic disclaimer: N/A

ACTION ITEMS (from audit, separate from this page):
  1. OTO3 video needs filming (60-90s, Loom, webcam-over-slides)
     Current take rate: 0%. Expected with video: 2-5%+.
     Revenue impact: single biggest leak in funnel per SFB.

What This Example Demonstrates

  1. The AUDIT phase caught two problems before the build started. The sales page was missing a Contact link in its compliance footer (4/5 links instead of 5/5). The OTO3 video was not filmed (0% take rate). Both were identified and addressed — one fixed immediately, one flagged for separate action.
  2. The STRATEGY phase mapped each gap to a specific SFB component and build mode. Compliance footer gap → Component 7, Mode 6. OTO3 video gap → Component 6, Mode 4. The OTO1 build → Component 5, Mode 2.
  3. The BUILD phase enforced every gate including SFB-specific checks. Gate 3 (SFB Component Check) verified the OTO video was present, the ascending price logic was visible, and the "No thanks" link was de-emphasized — checks that come from the SFB architecture, not just generic page QC.
  4. The compliance footer was verified by count, not by eyeballing. "All 5 links present" is a counted check. The audit caught the missing Contact link precisely because it counted 4 instead of 5.
  5. The QC report includes the SFB audit summary. Kathryn can see the full funnel state, not just the page state. She knows what else needs attention (OTO3 video) even though this specific page passed all gates.
  6. The page doesn't ship until all gates pass — including the manual ones.

Golden Example Needed

The above is a constructed reference showing the cascade process. The first production run that passes all gates (including manual verification) should replace this file with a reference to the actual page, via Mode 2.

When that happens, update this file to point to: