LOFI-01 · Offer Blueprint

LOFI BLUEPRINT · Section 3 · Tier 1locked

Purpose: Turn raw offer intake (Block D) into a scored, structured offer — the single artifact every downstream conversion asset reads. If the offer math is wrong here, every page, email, and ad inherits the error. This is the keystone.

Cascades to: 3B (Productize) · 3C (Automation/COGS) · 12 (125-word explanation) · 22A (Sales Page) · 22B (Pitch Deck).

Inputs → Output

Reads

Block D · OfferBlock A.guarantee

Prompts

SP (system)P1 · Part 3BIG-PAPI · Offer suite

Writes

what.offerwhat.processwhat.pricingwhat.transformation

Pipeline

Load anchors

SP loaded as system message (voice anchor, Rule 4). P1 Part 3 + BIG-PAPI Offer prompts loaded as task context. Pull ≥3 reference IDs from CL-MASTER / CL-EXAMPLES (Rule 2).

Score the offer

Run the Hormozi $100M Offers formula on Block D: Dream Outcome × Perceived Likelihood ÷ (Time Delay × Effort & Sacrifice). Produce the Offer Score.

Build the 12-section explainer

Generate the full 12-section Offer Explainer from Block D + Block A.guarantee. Process phases = 3 (max 4). Pricing tiers = exactly 3 (Rule 8). Enforce ≥75% gross margin (Rule 9).

QA gate

Section 25 auto-runs QA L1 (24 checkpoints) + L2 (6 brand gates). Any L2 fail = REJECT → rewrite. On pass → ready for human review.

Cascade

Locked offer object becomes read-only input to 3B, 3C, 12, 22A, 22B. Offer name must be identical across all (cross-section consistency check).

Technical Reference

Generation contract (machine-executable)

section: 3
id: offer-blueprint
state: LOFI_BLUEPRINT
tier: 1
sources:
  system: SP                 # loaded every call, no exception (Rule 4)
  task: [P1.part3, BIG-PAPI.offer_suite]
inputs:
  required:
    - block_d.current_offer_name
    - block_d.current_pricing      # {tier1, tier2, tier3}
    - block_d.pricing_model        # hourly|flat|subscription|cohort
    - block_d.core_components
    - block_d.deliverables
    - block_d.transformation       # {from, to, in}
    - block_d.obstacles_eliminated # >=3
    - block_d.process_phases       # 3, max 4: {name, objective, milestone, prize, timeframe}
    - block_d.roi_quantitative     # {30d, 90d, 365d, lifetime}
    - block_d.roi_qualitative
    - block_d.success_metrics
  optional:
    - block_a.guarantee
    - block_d.early_adopter_terms
output:
  offer_score: hormozi_100m         # dream*likelihood / (time*effort)
  explainer: 12_section
  fields: [offer, process, pricing, transformation]
cascades_to: [3B, 3C, 12, 22A, 22B]

Validation rules enforced (from Part 7)

Rule 1  NULL > FABRICATION    empty intake field -> "Not measured" / "Pending intake"
Rule 2  CITATION >= 3         cite >=3 ref IDs from CL-MASTER or CL-EXAMPLES
Rule 4  VOICE ANCHOR          SP loaded as system message
Rule 5  NO PREAMBLE           dive straight in
Rule 8  THREE IS MAGIC        process phases = 3 (max 4); pricing tiers = exactly 3
Rule 9  >=75% GROSS MARGIN    P1 Part 3 + BIG-PAPI Offer Automation enforce
Rule 10 COMPLIANCE            no overpromising; claims grounded in reference data
Rule 11 QA GATE               must pass L1 + L2 before marked ready

Supabase sync map (from Part 10)

Section 3 ->
  brand.what.offer          (jsonb)
  brand.what.process        (jsonb)
  brand.what.pricing        (jsonb)
  brand.what.transformation (jsonb)

SCHEMA NOTE: verify all jsonb paths against live Supabase before write. Flag missing columns in the PR; do NOT create new columns without review.

12-section Offer Explainer structure

1.  Offer Name (branded)            7.  Pricing — exactly 3 tiers
2.  Dream Outcome                   8.  Value Stack vs price (>=10x)
3.  Transformation (from -> to -> in)  9.  Guarantee / risk reversal
4.  Core Components / Deliverables  10. Bonuses / early-adopter terms
5.  Process — 3 phases (max 4)      11. Scarcity / urgency (real only)
6.  ROI (30d / 90d / 365d / lifetime)  12. Primary CTA

Warning

This is a LOFI artifact: its consumer is the next generation call, not a customer. It is reviewed at the Doc/wizard LOFI gate before any HIFI section reads it. Per QA before POC — QA always precedes POC review.

Next in the pair → HIFI-01 · Sales / Landing Page consumes this blueprint.